[Desktop-packages] [Bug 1800101] Re: gnome-shell uses 100% CPU

[Daniel van Vugt]

René,

You need to have logged in from another machine (via ssh) and run gdb
from there. That way gdb won't hang when you stop the shell with Ctrl+C.

Please also remember to try uninstalling the nvidia driver (briefly) so
as to compare with nouveau.

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

Title:
  gnome-shell uses 100% CPU

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  For no obvious reason gnome-shell starts to use 100% CPU.

  This is a standard install of Ubuntu 18.04 with no special extensions
  installed.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.28.3-0ubuntu0.18.04.2
  ProcVersionSignature: Ubuntu 4.15.0-38.41-generic 4.15.18
  Uname: Linux 4.15.0-38-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7.4
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Oct 26 10:03:02 2018
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  InstallationDate: Installed on 2018-08-15 (71 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  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/1800101/+subscriptions

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

[Desktop-packages] [Bug 1800101] Re: gnome-shell uses 100% CPU

[René Schultz Madsen]

Daniel,

Now I have experienced the 100% CPU to more times and both times I tried
to follow the guide here
https://wiki.ubuntu.com/Backtrace#Already_running_programs but it's not
possible to go to do "If the program hangs but doesn't crash you can
press ctrl+c in gdb while the program is frozen and then continue with
the next step."

Then gdb hangs :-P so no luck there. See attatched gdb log file. Any
suggestions what to do next?

The thing I have noticed now with the 100% CPU usage is that it's always
after restarting a VM several times in VirtualBox.

** Attachment added: "gdb-gnome-shell.txt"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1800101/+attachment/5223458/+files/gdb-gnome-shell.txt

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

Title:
  gnome-shell uses 100% CPU

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  For no obvious reason gnome-shell starts to use 100% CPU.

  This is a standard install of Ubuntu 18.04 with no special extensions
  installed.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.28.3-0ubuntu0.18.04.2
  ProcVersionSignature: Ubuntu 4.15.0-38.41-generic 4.15.18
  Uname: Linux 4.15.0-38-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7.4
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Oct 26 10:03:02 2018
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  InstallationDate: Installed on 2018-08-15 (71 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  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/1800101/+subscriptions

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

[Desktop-packages] [Bug 1795668] Re: Enable bubblewrap in gnome-desktop3 for Ubuntu 18.04 LTS

[Nicolas Bernaerts]

I've also encountered the same trouble with some of my external
thumbnailers (lo-thumbnailer, msoffice-thumbnailer, ...).

I realised that bwarp calls fail under Ubuntu and Debian because of
--symlink options used on /bin and /sbin. --ro-bind should be used
instead of --symlink.

Till problem is solved on the Nautilus side, I've written a small
article to explain how to get back external thumbnailers under 18.04 and
18.10 with the help of a bwrap wrapper under /usr/local/bin.

http://bernaerts.dyndns.org/linux/360-ubuntu-nautilus-external-
thumbnailer-failure

Hope it helps

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

Title:
  Enable bubblewrap in gnome-desktop3 for Ubuntu 18.04 LTS

Status in bubblewrap package in Ubuntu:
  Fix Released
Status in gnome-desktop3 package in Ubuntu:
  Fix Released

Bug description:
  Impact
  ==
  gnome-desktop 3.26 hardened the thumbnailers with bubblewrap to mitigate 
several vulnerabilities. Ubuntu had to disable that feature until bubblewrap 
could be promoted to main.

  bubblewrap is now in main for 18.10 and the feature is now enabled
  there. The intention has been for that change to be backported to
  18.04 LTS as a security fix.

  The bubblewrap MIR is https://launchpad.net/bugs/1709164

  We'll need to promote bubblewrap to main before this update should be
  pushed to bionic.

  Can you sponsor directly from the git repo instead of with a debdiff?

  gbp clone https://git.launchpad.net/~ubuntu-desktop/ubuntu/+source
  /gnome-desktop3

  git checkout ubuntu/bionic

  gbp clone https://git.launchpad.net/~ubuntu-
  desktop/ubuntu/+source/bubblewrap

  Testing Done
  
  I test built bubblewrap and its autopkgtest passes:
  
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic-jbicha-arch/bionic/amd64/b/bubblewrap/20181002_153548_f5821@/log.gz

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

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

[Desktop-packages] [Bug 1799693] Re: Stable libopus-1.3 released

[Bug Watch Updater]

** Changed in: opus (Debian)
   Status: New => Fix Released

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

Title:
  Stable libopus-1.3 released

Status in opus package in Ubuntu:
  Triaged
Status in opus package in Debian:
  Fix Released

Bug description:
  Cosmic is currently shipping libopus-1.3~beta+20180518-1 which is now 
outdated and technically marked as a beta. 
  http://opus-codec.org/release/stable/2018/10/18/libopus-1_3.html

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

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

[Desktop-packages] [Bug 1731940] Re: [P7xxDM2(-G), Realtek ALC898, Headphone Jack, External] No sound at all

[Dennis Mungai Lin.Jr.]

A possible work-around: Update the jack's description to PulseAudio, as
shown:

Create the file `/usr/share/pulseaudio/alsa-mixer/paths/iec958-stereo-
output.conf` and populate it with:

```
# This file is part of PulseAudio.
#
# PulseAudio is free software; you can redistribute it and/or modify
# it under the terms of the GNU Lesser General Public License as
# published by the Free Software Foundation; either version 2.1 of the
# License, or (at your option) any later version.
#
# PulseAudio is distributed in the hope that it will be useful, but
# WITHOUT ANY WARRANTY; without even the implied warranty of
# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU
# General Public License for more details.
#
# You should have received a copy of the GNU Lesser General Public License
# along with PulseAudio; if not, see .


[General]
description = Headphones + Digital Output (S/PDIF)

[Element IEC958]
switch = mute
```

Then set the model definition at `/etc/modprobe.d/sound.conf` with the
following entries:

`options snd-hda-intel model=no-primary-hp enable=1 index=0`

When done, issue a reboot.

For current HDA model lists, see http://git.alsa-project.org/?p=alsa-
kernel.git;a=blob;f=Documentation/sound/alsa/HD-Audio-
Models.txt;hb=HEAD.

Will test and report back.

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

Title:
  [P7xxDM2(-G), Realtek ALC898, Headphone Jack, External] No sound at
  all

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  Hello there,

  I have Ubuntu 16.04LTS installed on the Clevo P751DM2-G, also marketed
  as the Schenker XMG U507, the System76's Serval WS (2017 model), the
  Eurocom Sky X4E2, among others.

  The sound card is the Realtek ALC898 with the following output
  configuration:

  1. One SPDIF/headphone combo jack (to the right)
  2. One Line Out.
  3. One Line-In.
  4. One Mic-In.

  Background information:

  On Windows, one can use the Realtek HD Audio control panel pop-up menu
  on jack detection to set the output type when an audio device is
  plugged in to an appropriate jack, combined with Sound Blaster X-Fi
  MB5 software to enable post-processing effects such as Bass, noise
  cancellation, etc.

  What I have tried so far:

  1. Setting the model definition at /etc/modprobe.d/sound.conf with the
  following entries:

  options snd-hda-intel model=no-primary-hp enable=1 index=0

  Using such a line worked before on an MSI GS43VR 6RE Phantom Pro that
  also has the same (or a similar) ESS Sabre Audio DAC component.

  Expected behavior:

  When plugged into the microphone jack, the ESS Sabre DAC should be
  activated and sound should be routed to the headset.

  Observed anomaly:

  Sound comes out through the speakers instead.

  However, the line-out output works. In that case, when plugged into
  the line out, Audio works as expected.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  Uname: Linux 4.14.0 x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  lin2199 F pulseaudio
   /dev/snd/controlC0:  lin2199 F pulseaudio
  CurrentDesktop: GNOME
  Date: Mon Nov 13 17:34:53 2017
  InstallationDate: Installed on 2017-07-25 (111 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  gdm1812 F pulseaudio
lin2199 F pulseaudio
   /dev/snd/controlC0:  gdm1812 F pulseaudio
lin2199 F pulseaudio
  Symptom_Jack: Speaker, Internal
  Symptom_Type: No sound at all
  Title: [P7xxDM2(-G), Realtek ALC898, Speaker, Internal] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/21/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1.06.04
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: P7xxDM2(-G)
  dmi.board.vendor: Notebook
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: No Enclosure
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.06.04:bd12/21/2016:svnNotebook:pnP7xxDM2(-G):pvrNotApplicable:rvnNotebook:rnP7xxDM2(-G):rvrNotApplicable:cvnNoEnclosure:ct10:cvrN/A:
  dmi.product.family: Not Applicable
  dmi.product.name: P7xxDM2(-G)
  dmi.product.version: Not Applicable
  dmi.sys.vendor: Notebook

To manage 

[Desktop-packages] [Bug 1809073] [NEW] package xbrlapi 5.5-4ubuntu2.0.1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration

[Vikramjit Roy]

Public bug reported:

I am not able to back up

ProblemType: Package
DistroRelease: Ubuntu 18.04
Package: xbrlapi 5.5-4ubuntu2.0.1
ProcVersionSignature: Ubuntu 4.15.0-39.42-generic 4.15.18
Uname: Linux 4.15.0-39-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.5
Architecture: amd64
Date: Wed Dec 19 11:16:56 2018
DuplicateSignature:
 package:xbrlapi:5.5-4ubuntu2.0.1
 Unpacking python-gi (3.26.1-2) ...
 dpkg: error processing package xbrlapi (--configure):
  package is in a very bad inconsistent state; you should
ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
InstallationDate: Installed on 2018-11-16 (32 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
Python3Details: /usr/bin/python3.6, Python 3.6.6, python3-minimal, 
3.6.5-3ubuntu1
PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
RelatedPackageVersions:
 dpkg 1.19.0.5ubuntu2.1
 apt  1.6.6
SourcePackage: brltty
Title: package xbrlapi 5.5-4ubuntu2.0.1 failed to install/upgrade: package is 
in a very bad inconsistent state; you should  reinstall it before attempting 
configuration
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-package bionic need-duplicate-check

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

Title:
  package xbrlapi 5.5-4ubuntu2.0.1 failed to install/upgrade: package is
  in a very bad inconsistent state; you should  reinstall it before
  attempting configuration

Status in brltty package in Ubuntu:
  New

Bug description:
  I am not able to back up

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: xbrlapi 5.5-4ubuntu2.0.1
  ProcVersionSignature: Ubuntu 4.15.0-39.42-generic 4.15.18
  Uname: Linux 4.15.0-39-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  Date: Wed Dec 19 11:16:56 2018
  DuplicateSignature:
   package:xbrlapi:5.5-4ubuntu2.0.1
   Unpacking python-gi (3.26.1-2) ...
   dpkg: error processing package xbrlapi (--configure):
package is in a very bad inconsistent state; you should
  ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
  InstallationDate: Installed on 2018-11-16 (32 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  Python3Details: /usr/bin/python3.6, Python 3.6.6, python3-minimal, 
3.6.5-3ubuntu1
  PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu2.1
   apt  1.6.6
  SourcePackage: brltty
  Title: package xbrlapi 5.5-4ubuntu2.0.1 failed to install/upgrade: package is 
in a very bad inconsistent state; you should  reinstall it before attempting 
configuration
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 903651] Re: When opening files from network share, applications try to cache entire file locally

[Launchpad Bug Tracker]

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

** Changed in: file-roller (Ubuntu)
   Status: New => Confirmed

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

Title:
  When opening files from network share, applications try to cache
  entire file locally

Status in file-roller package in Ubuntu:
  Confirmed

Bug description:
  Say you have a 80gb tar file.

  Say this tar file is on a SAMBA share on the network.

  Trying to open the tar using file-roller is something you will deeply
  regret.

  1) file-roller VERY SLOWLY attempts to cache the entire file locally (I mean 
it takes it ages)
  2) file-roller does not check that the local drive can store the file its 
copying

  File-roller has no good reason to copy locally, and the practice is
  entirely counter productive, and in the case of multi-GB files can
  lead to

  a) access to the samba share for other applications (say a media player) 
being overwhelmed and causing them to error
  b) makes file-roller appear hung
  c) leaves massive files in your local cache ("~/.cache/.fr-randomcharacters") 
and no way to clear them except manually
  d) can cause your machine to run out of diskspace
  e) is very very slow, copying the file locally, manually is many times faster 
and doesn't cause other applications to error (see a)
  f) very bad user experience

  ProblemType: Bug
  DistroRelease: Ubuntu 11.10
  Package: file-roller 3.2.1-0ubuntu1
  ProcVersionSignature: Ubuntu 3.0.0-13.22-generic 3.0.6
  Uname: Linux 3.0.0-13-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 1.23-0ubuntu4
  Architecture: amd64
  Date: Tue Dec 13 10:37:10 2011
  ExecutablePath: /usr/bin/file-roller
  InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  SourcePackage: file-roller
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1784485] Re: [ZenBook S UX391UA, Realtek ALC294, Mic, Internal] No sound at all

[VanVan]

It's already commited, check here :
http://mailman.alsa-project.org/pipermail/alsa-devel/2018-December/143282.html

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

Title:
  [ZenBook S UX391UA, Realtek ALC294, Mic, Internal] No sound at all

Status in alsa-driver package in Ubuntu:
  Fix Committed
Status in linux package in Ubuntu:
  Fix Committed

Bug description:
  Internal speaker - not sound at all
  Cable Headphonse - realy quiet disorted sound
  Bluetooth headphones - sound works fine

  On Windows 10 everything works fine.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18
  Uname: Linux 4.15.0-29-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  pmichalski   7964 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Jul 30 22:32:10 2018
  InstallationDate: Installed on 2018-07-17 (12 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=pl_PL.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaRecordingTest: ALSA recording test through plughw:PCH failed
  Symptom_Card: Wbudowany dźwięk - HDA Intel PCH
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gdm2988 F pulseaudio
pmichalski   7964 F pulseaudio
  Symptom_Jack: Mic, Internal
  Symptom_Type: No sound at all
  Title: [ZenBook S UX391UA, Realtek ALC294, Mic, Internal] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/18/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX391UA.204
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX391UA
  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.:bvrUX391UA.204:bd05/18/2018:svnASUSTeKCOMPUTERINC.:pnZenBookSUX391UA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX391UA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: ZenBook S
  dmi.product.name: ZenBook S UX391UA
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

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

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

[Desktop-packages] [Bug 374079] Re: Internal microphone doesn't work at all

[Daniel van Vugt]

David,

Please log your own new bug from an affected machine by running:

  ubuntu-bug pulseaudio


** Changed in: alsa-driver (Ubuntu)
   Status: Confirmed => Invalid

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

Title:
  Internal microphone doesn't work at all

Status in alsa-driver package in Ubuntu:
  Invalid

Bug description:
  My computer is Acer TravelMate 7520G. Ubuntu 9.04 Jaunty Jackalope.

  Sound card is working otherwise ok, but the internal microphone does't
  work at all. I've tired modifying the alsa-base.conf file's last row
  to read like: options snd-hda-intel model=acer-aspire, options snd-
  hda-intel model=acer and the third one for digital built-in acer mic.
  None of the above have worked.

  
  From the user's point of wiev it seems like the microphone cannot be 
activated at all. If I try to activate my microphone from sound menu (from top 
right corner on desk top) -> volume control -> record (tab), the microphone is 
allways showing a red cross (like it is muted). The red cross can be removed, 
but the red cross appears back after closing the control panel. 

  After test recording with mic activated the result is only static
  noise during play-back.

  ProblemType: Bug
  AplayDevices:
    Luettelo PLAYBACK laitteista 
   kortti 0: SB [HDA ATI SB], laite 0: ALC268 Analog [ALC268 Analog]
 Alalaitteet: 1/1
 Alalaite #0: subdevice #0
  Architecture: i386
  ArecordDevices:
    Luettelo CAPTURE laitteista 
   kortti 0: SB [HDA ATI SB], laite 0: ALC268 Analog [ALC268 Analog]
 Alalaitteet: 1/1
 Alalaite #0: subdevice #0
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  kone   3631 F mixer_applet2
  Card0.Amixer.info:
   Card hw:0 'SB'/'HDA ATI SB at 0xf060 irq 16'
 Mixer name : 'Realtek ALC268'
 Components : 'HDA:10ec0268,10250124,0013 
HDA:14f12c06,10250093,0010'
 Controls  : 11
 Simple ctrls  : 8
  CurrentDmesg:
   [   26.471439] sky2 eth0: enabling interface
   [   26.471669] ADDRCONF(NETDEV_UP): eth0: link is not ready
   [   31.097025] eth1: no IPv6 routers present
   [   84.500043] Clocksource tsc unstable (delta = -288762894 ns)
  DistroRelease: Ubuntu 9.04
  NonfreeKernelModules: fglrx
  Package: alsa-base 1.0.18.dfsg-1ubuntu8
  PackageArchitecture: all
  ProcEnviron:
   LANG=fi_FI.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Uname: Linux 2.6.28-11-generic i686

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

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

[Desktop-packages] [Bug 1808990] Re: Xorg freeze

[Daniel van Vugt]

If you can't log in remotely any more then that sounds like a kernel
issue. But regardless, please:

 1. Reproduce the freeze again.

 2. Reboot

 3. Run this command to collect the system log from the previous
(frozen) boot:

journalctl -b-1 > prevboot.txt

 4. Attach the file 'prevboot.txt' to the bug here.


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

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

** Tags added: nouveau

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

Title:
  Xorg freeze

Status in Ubuntu:
  Incomplete

Bug description:
  The screen appears to freeze, with possible SSH access from another machine 
during the first minutes. After that, the system totally freezes, with not even 
ethernet connection anymore.
  Only hard reboot helps to solve the issue, with normal functionality 
afterwards.
  It occurs in a random way.

  Ubuntu version 18.04.1 LTS.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-42.45-generic 4.15.18
  Uname: Linux 4.15.0-42-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  BootLog: Error: [Errno 13] Permiso denegado: '/var/log/boot.log'
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Dec 18 15:32:13 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox, 5.2.18, 4.15.0-39-generic, x86_64: installed
   virtualbox, 5.2.18, 4.15.0-42-generic, x86_64: installed
  ExtraDebuggingInterest: I just need to know a workaround
  GpuHangFrequency: Once a week
  GpuHangReproducibility: Seems to happen randomly
  GpuHangStarted: Immediately after installing this version of Ubuntu
  GraphicsCard:
   NVIDIA Corporation GK208 [GeForce GT 730] [10de:1287] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: ASUSTeK Computer Inc. GK208B [GeForce GT 730] [1043:850c]
  InstallationDate: Installed on 2018-11-14 (34 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 046d:c016 Logitech, Inc. Optical Wheel Mouse
   Bus 001 Device 003: ID 046d:c31c Logitech, Inc. Keyboard K120
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: System manufacturer System Product Name
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=es_ES.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-42-generic 
root=UUID=7af5a6a3-c5c3-48e2-9477-704034a9e379 ro quiet splash vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/07/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1804
  dmi.board.asset.tag: Default string
  dmi.board.name: Z170-P
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1804:bd06/07/2016:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ170-P:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.91-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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

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

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

[Daniel van Vugt]

This bug needs to stay closed (Invalid) per comment #2 because we were
unable to debug the crash report. It would help if you are able to
reproduce the problem and then log a new bug for it. Some handy
instructions for logging a new crash report are here:

https://wiki.ubuntu.com/Bugs/Responses#Missing_a_crash_report_or_having_a_.crash_attachment

I suspect it might turn out to be a duplicate of bug 1783673 or bug
1809058.

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

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

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

Status in gnome-shell package in Ubuntu:
  Invalid

Bug description:
  I pressed a button on my Wacom tablet at the Gnome shell lock screen.
  Once it crashed I was able to see the apps/desktop for a while until
  the lock screen appeared again.

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.28.3-0ubuntu0.18.04.2
  ProcVersionSignature: Ubuntu 4.15.0-38.41-generic 4.15.18
  Uname: Linux 4.15.0-38-generic x86_64
  NonfreeKernelModules: lkp_Ubuntu_4_15_0_38_41_generic_45
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Nov 19 18:38:17 2018
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  InstallationDate: Installed on 2017-03-13 (616 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  ProcCmdline: /usr/bin/gnome-shell
  SegvAnalysis:
   Segfault happened at: 0x7fa27d2b2b38:cmp%ebp,0x8(%rax)
   PC (0x7fa27d2b2b38) ok
   source "%ebp" ok
   destination "0x8(%rax)" (0x0008) not located in a known VMA region 
(needed writable region)!
  SegvReason: writing NULL VMA
  Signal: 11
  SourcePackage: gnome-shell
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/mutter/libmutter-clutter-2.so
   ?? () from /usr/lib/x86_64-linux-gnu/mutter/libmutter-clutter-2.so
   ?? () from /usr/lib/x86_64-linux-gnu/mutter/libmutter-clutter-2.so
   clutter_x11_handle_event () from 
/usr/lib/x86_64-linux-gnu/mutter/libmutter-clutter-2.so
   ?? () from /usr/lib/x86_64-linux-gnu/libmutter-2.so.0
  Title: gnome-shell crashed with SIGSEGV in clutter_x11_handle_event()
  UpgradeStatus: Upgraded to bionic on 2018-08-24 (87 days ago)
  UserGroups: adm cdrom dip libvirt libvirtd lpadmin plugdev sambashare sudo

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

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

[Desktop-packages] [Bug 1808908] Re: Screen not locked when coming out of suspend/hibernate

[Eben Cowley]

In case it's relevant, I'm on a Lenovo Y700 laptop. When I set my password
from the Settings GUI it sets both the root password and the password that
I use to unlock the laptop. At least with the version of gnome that I'm
using, Ubuntu has a lock screen where it shows a wallpaper and the time,
and a login screen which has the user logged in and a field where you type
your password.

Yesterday my password was a string, X. I opened my laptop, entered the
first character of X, expecting the lock screen to transition to the login
screen. The lock screen did not transition into the login screen. I typed
the first character again, and nothing happened. I pressed the spacebar to
try to get the laptop to respond, and it unlocked (without me ever typing
in the password). This was really unnerving because it meant that the
laptop was completely vulnerable, so I rebooted.

After rebooting, I tried entering a random string to log in and it didn't
work. I entered X and it unlocked. I promptly changed both my root password
and my login to the string Y via the Settings GUI. I ran a sudo command and
the terminal would only accept Y as the password. Just a few minutes ago, I
tried unlocking the laptop with X and it worked.

This is really upsetting because it means there's a chance that any random
person could walk up to my laptop and unlock it, regardless of what the
password is. I'm going to upgrade to 18.10 soon, but I think it's pretty
necessary to report this problem. By the way, the bug report says that the
faulty package is gnome-screensaver, but that it's not installed. I don't
know which package is responsible, so I changed that in the bug report.


** Description changed:

  Ubuntu 18.04.1
  
  Just a few minutes ago, I typed the first character of my password, and
  the lock screen didn't change to the login screen. I typed the character
  again and nothing happened, so I pressed the spacebar to try to get the
  thing's attention.
  
- 
  Then it unlocked.
  
- 
- This is spooked me, so I restarted my laptop and tried logging in with a 
random string, and nothing happened. I logged in with my regular password and 
then promptly changed it.
+ This is spooked me, so I restarted my laptop and tried logging in with a
+ random string, and nothing happened. I logged in with my regular
+ password and then promptly changed it.
  
  I tried unlocking my system with my old password, and it worked.
  However, the terminal only recognizes my new root password.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
- Package: gnome-screensaver (not installed)
+ Package: unknown
  ProcVersionSignature: Ubuntu 4.15.0-42.45-generic 4.15.18
  Uname: Linux 4.15.0-42-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Dec 17 23:10:46 2018
  InstallationDate: Installed on 2018-09-15 (94 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  ProcEnviron:
-  PATH=(custom, no user)
-  XDG_RUNTIME_DIR=
-  LANG=en_US.UTF-8
-  SHELL=/bin/bash
+  PATH=(custom, no user)
+  XDG_RUNTIME_DIR=
+  LANG=en_US.UTF-8
+  SHELL=/bin/bash
  SourcePackage: gnome-screensaver
  Symptom: security
  Title: Screen not locked when coming out of suspend/hibernate
  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-screensaver in Ubuntu.
https://bugs.launchpad.net/bugs/1808908

Title:
  Screen not locked when coming out of suspend/hibernate

Status in gnome-screensaver package in Ubuntu:
  New

Bug description:
  Ubuntu 18.04.1

  Just a few minutes ago, I typed the first character of my password,
  and the lock screen didn't change to the login screen. I typed the
  character again and nothing happened, so I pressed the spacebar to try
  to get the thing's attention.

  Then it unlocked.

  This is spooked me, so I restarted my laptop and tried logging in with
  a random string, and nothing happened. I logged in with my regular
  password and then promptly changed it.

  I tried unlocking my system with my old password, and it worked.
  However, the terminal only recognizes my new root password.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: unknown
  ProcVersionSignature: Ubuntu 4.15.0-42.45-generic 4.15.18
  Uname: Linux 4.15.0-42-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Dec 17 23:10:46 2018
  InstallationDate: Installed on 2018-09-15 (94 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-screensaver
  Symptom: security
  Title: Screen not locked when coming out of suspend/hibernate
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug 

[Desktop-packages] [Bug 1783673] Re: gnome-shell crashed with SIGSEGV in clutter_input_device_xi2_get_current_tool → clutter_device_manager_xi2_translate_event → clutter_backend_real_translate_event →

[Daniel van Vugt]

** Summary changed:

- gnome-shell crashed with SIGSEGV in 
clutter_input_device_xi2_get_current_tool()
+ gnome-shell crashed with SIGSEGV in clutter_input_device_xi2_get_current_tool 
→ clutter_device_manager_xi2_translate_event → 
clutter_backend_real_translate_event → clutter_x11_handle_event → 
handle_host_xevent

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

Title:
  gnome-shell crashed with SIGSEGV in
  clutter_input_device_xi2_get_current_tool →
  clutter_device_manager_xi2_translate_event →
  clutter_backend_real_translate_event → clutter_x11_handle_event →
  handle_host_xevent

Status in gnome-shell package in Ubuntu:
  Confirmed

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

  ProblemType: Crash
  DistroRelease: Ubuntu 18.10
  Package: gnome-shell 3.28.3-0ubuntu2
  ProcVersionSignature: Ubuntu 4.17.0-4.5-generic 4.17.3
  Uname: Linux 4.17.0-4-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.20.10-0ubuntu7
  Architecture: amd64
  CurrentDesktop: GNOME-Greeter:GNOME
  Date: Wed Jul 25 21:54:39 2018
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  GsettingsChanges:

  InstallationDate: Installed on 2018-06-18 (37 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  ProcCmdline: /usr/bin/gnome-shell
  SegvAnalysis:
   Segfault happened at: 0x7f3325479e50:mov0x128(%rdi),%rax
   PC (0x7f3325479e50) ok
   source "0x128(%rdi)" (0x0128) not located in a known VMA region (needed 
readable region)!
   destination "%rax" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: gnome-shell
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/mutter/libmutter-clutter-2.so
   ?? () from /usr/lib/x86_64-linux-gnu/mutter/libmutter-clutter-2.so
   ?? () from /usr/lib/x86_64-linux-gnu/mutter/libmutter-clutter-2.so
   clutter_x11_handle_event () from 
/usr/lib/x86_64-linux-gnu/mutter/libmutter-clutter-2.so
   ?? () from /usr/lib/x86_64-linux-gnu/libmutter-2.so.0
  Title: gnome-shell crashed with SIGSEGV in clutter_x11_handle_event()
  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/1783673/+subscriptions

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

[Desktop-packages] [Bug 1809058] Re: gnome-shell crashed with SIGSEGV in _clutter_input_device_reset_scroll_info() from clutter_device_manager_xi2_translate_event() from clutter_backend_real_translate

[Daniel van Vugt]

** Summary changed:

- 
/usr/bin/gnome-shell:11:_clutter_input_device_reset_scroll_info:clutter_device_manager_xi2_translate_event:clutter_backend_real_translate_event:clutter_x11_handle_event:handle_host_xevent
+ gnome-shell crashed with SIGSEGV in _clutter_input_device_reset_scroll_info() 
from clutter_device_manager_xi2_translate_event() from 
clutter_backend_real_translate_event() from clutter_x11_handle_event() from 
handle_host_xevent()

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

Title:
  gnome-shell crashed with SIGSEGV in
  _clutter_input_device_reset_scroll_info() from
  clutter_device_manager_xi2_translate_event() from
  clutter_backend_real_translate_event() from clutter_x11_handle_event()
  from handle_host_xevent()

Status in gnome-shell package in Ubuntu:
  New

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

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

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

[Desktop-packages] [Bug 1809058] [NEW] gnome-shell crashed with SIGSEGV in _clutter_input_device_reset_scroll_info() from clutter_device_manager_xi2_translate_event() from clutter_backend_real_transla

[errors.ubuntu.com bug bridge]

Public bug reported:

The Ubuntu Error Tracker has been receiving reports about a problem regarding 
gnome-shell.  This problem was most recently seen with package version 
3.30.1-2ubuntu1.18.10.1, the problem page at 
https://errors.ubuntu.com/problem/aee56838cf05d6e1bf41d5249802782ca978ba03 
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: gnome-shell (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: artful bionic cosmic vivid wily xenial yakkety zesty

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

Title:
  gnome-shell crashed with SIGSEGV in
  _clutter_input_device_reset_scroll_info() from
  clutter_device_manager_xi2_translate_event() from
  clutter_backend_real_translate_event() from clutter_x11_handle_event()
  from handle_host_xevent()

Status in gnome-shell package in Ubuntu:
  New

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

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

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

[Desktop-packages] [Bug 1784485] Re: [ZenBook S UX391UA, Realtek ALC294, Mic, Internal] No sound at all

[VanVan]

** Changed in: alsa-driver (Ubuntu)
   Status: Confirmed => Fix Committed

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

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

Title:
  [ZenBook S UX391UA, Realtek ALC294, Mic, Internal] No sound at all

Status in alsa-driver package in Ubuntu:
  Fix Committed
Status in linux package in Ubuntu:
  Fix Committed

Bug description:
  Internal speaker - not sound at all
  Cable Headphonse - realy quiet disorted sound
  Bluetooth headphones - sound works fine

  On Windows 10 everything works fine.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18
  Uname: Linux 4.15.0-29-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  pmichalski   7964 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Jul 30 22:32:10 2018
  InstallationDate: Installed on 2018-07-17 (12 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=pl_PL.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaRecordingTest: ALSA recording test through plughw:PCH failed
  Symptom_Card: Wbudowany dźwięk - HDA Intel PCH
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gdm2988 F pulseaudio
pmichalski   7964 F pulseaudio
  Symptom_Jack: Mic, Internal
  Symptom_Type: No sound at all
  Title: [ZenBook S UX391UA, Realtek ALC294, Mic, Internal] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/18/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX391UA.204
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX391UA
  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.:bvrUX391UA.204:bd05/18/2018:svnASUSTeKCOMPUTERINC.:pnZenBookSUX391UA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX391UA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: ZenBook S
  dmi.product.name: ZenBook S UX391UA
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

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

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

[Desktop-packages] [Bug 1797882] Re: At dual monitor intel_do_flush_locked failed: Resource deadlock avoided

[Daniel van Vugt]

Gert,

Please report the problem to the Mesa developers who will best be able
to help:

  https://bugs.freedesktop.org/enter_bug.cgi?product=Mesa

and then let us know the new bug ID.

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

Title:
  At dual monitor intel_do_flush_locked failed: Resource deadlock
  avoided

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

Bug description:
  Using ubuntu wayland with dual monitors, configured above each other.
  Dock is configured at both displays, not hiding.
  Icons for "terminal" and "libreofffice Writer" are present at the dock.

  Start terminal on primary screen by mouseclick on dock.
  Start libreoffice Writer on primary screen by mouseclick on dock.
  Terminate libreoffice Witer by mouseclick on X.
  Repeat the starting and stopping of Writer.

  Login-screen will appear. Syslog shows:
  Oct 15 00:09:51 Gert2 org.gnome.Shell.desktop[5892]: intel_do_flush_locked 
failed: Resource deadlock avoided
  Oct 15 00:09:51 Gert2 gnome-terminal-[6439]: Error reading events from 
display: Connection reset by peer
  Oct 15 00:09:51 Gert2 systemd[5755]: gnome-terminal-server.service: Main 
process exited, code=exited, status=1/FAILURE

  This problem doesnot occur in a dual monitor-session without wayland.
  It also doesnot occur, if only one monitor used with wayland
  It also doesnot occur, if the dock is only present at the primary screen.
  It also doesnot occur if second started application is present at the dock 
and doesnot add an icon to the dock (as libreoffice does).

  All other dual monitor/dock configurations seem to have this problem.

  No idea if this is helpful info, but the used graphics card does not support 
OpenGL version 2.1:
  Oct 15 00:02:32 Gert2 org.gnome.Shell.desktop[4426]: Require OpenGL version 
2.1 or later.
  Oct 15 00:02:32 Gert2 org.gnome.Shell.desktop[4426]: Failed to initialize 
glamor
  Oct 15 00:02:32 Gert2 org.gnome.Shell.desktop[4426]: Failed to initialize 
glamor, falling back to sw

  glxinfo:
  OpenGL vendor string: VMware, Inc.
  OpenGL renderer string: llvmpipe (LLVM 7.0, 128 bits)
  OpenGL core profile version string: 3.3 (Core Profile) Mesa 18.2.2
  OpenGL core profile shading language version string: 3.30
  OpenGL core profile context flags: (none)
  OpenGL core profile profile mask: core profile
  OpenGL core profile extensions:
  OpenGL version string: 3.1 Mesa 18.2.2
  OpenGL shading language version string: 1.40
  OpenGL context flags: (none)
  OpenGL extensions:
  OpenGL ES profile version string: OpenGL ES 3.0 Mesa 18.2.2
  OpenGL ES profile shading language version string: OpenGL ES GLSL ES 3.00
  OpenGL ES profile extensions:

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: gnome-shell 3.30.1-2ubuntu1
  ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12
  Uname: Linux 4.18.0-10-generic i686
  ApportVersion: 2.20.10-0ubuntu13
  Architecture: i386
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Oct 15 13:25:10 2018
  DisplayManager: gdm3
  GsettingsChanges:
   b'org.gnome.shell' b'command-history' redacted by apport
   b'org.gnome.shell' b'app-picker-view' b'uint32 1'
   b'org.gnome.shell' b'favorite-apps' redacted by apport
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
  ProcEnviron:
   LANGUAGE=en_US:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1807250] Re: At some point in the 18.04 cycle, /sys/bus/iio has disappeared from my system

[Your full name]

https://news.ycombinator.com/item?id=18711970

The sad state of being able to use Ubuntu on touch devices (hint: you
can't)

https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1807250

So, apparently support for an entire bus class has been missing since
ubuntu bionic (18.04 LTS) was released in april. Using kernels from
other distros or ubuntus old xenial 4.4.0-134 all provide access to
sensor data, suggesting the issue is with current (and shipped) kernels.
Three weeks into this not much is happening even though the issue also
affect canonical-specific 4,18 kernels.

This all suggests that pretty much no one has been using ubuntu on touch
devices otherwise i wouldn't be the first one to notice this. Now that
the devs know this they have no time for it...


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

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

Title:
  At some point in the 18.04 cycle, /sys/bus/iio has disappeared from my
  system

Status in gdm3 package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I have a Yoga 900-13ISK and a Thinkpad T470s. Both have had working
  screen rotation in the past. However, I noticed today while supporting
  a user in #ubuntu, neither do now. No icon in the Gnome menu and:

  # G_MESSAGES_DEBUG=all iio-sensor-proxy 
  ** (process:14877): DEBUG: 12:31:21.603: Could not find any supported sensors

  Indeed, /sys/bus/iio does not exist! I believe this is distinct from
  LP: #1792813, as I have just tested mainline 4.19 and it also does not
  work.

  I am working on getting more data, including testing older kernels
  from 18.04, but it might take me some time.

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

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

[Desktop-packages] [Bug 1809054] Re: package libsane1 1.0.27-1~experimental3ubuntu2 [modified: lib/udev/rules.d/60-libsane1.rules] failed to install/upgrade: trying to overwrite shared '/lib/udev/rule

[Ubuntu Foundations Team Bug Bot]

Thank you for taking the time to report this bug and helping to make
Ubuntu better.  Reviewing your dmesg attachment in this bug report it
seems that there is a problem with your hardware.  I recommend
performing a back up and then investigating the situation.  Measures you
might take include checking cable connections and using software tools
to investigate the health of your hardware.  In the event that is is not
in fact an error with your hardware please set the bug's status back to
New.  Thanks and good luck!

[This is an automated message.  I apologize if it reached you
inappropriately; please just reply to this message indicating so.]

** Tags added: hardware-error

** Changed in: sane-backends (Ubuntu)
   Importance: Undecided => Low

** Changed in: sane-backends (Ubuntu)
   Status: New => Invalid

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

Title:
  package libsane1 1.0.27-1~experimental3ubuntu2 [modified:
  lib/udev/rules.d/60-libsane1.rules] failed to install/upgrade: trying
  to overwrite shared '/lib/udev/rules.d/60-libsane1.rules', which is
  different from other instances of package libsane1:i386

Status in sane-backends package in Ubuntu:
  Invalid

Bug description:
  I tried to install wine and this happened.

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: libsane1 1.0.27-1~experimental3ubuntu2 [modified: 
lib/udev/rules.d/60-libsane1.rules]
  ProcVersionSignature: Ubuntu 4.15.0-42.45-generic 4.15.18
  Uname: Linux 4.15.0-42-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  Date: Tue Dec 18 17:12:18 2018
  DuplicateSignature:
   package:libsane1:1.0.27-1~experimental3ubuntu2 [modified: 
lib/udev/rules.d/60-libsane1.rules]
   Unpacking libsane1:i386 (1.0.27-1~experimental3ubuntu2) ...
   dpkg: error processing archive 
/var/cache/apt/archives/libsane1_1.0.27-1~experimental3ubuntu2_i386.deb 
(--unpack):
trying to overwrite shared '/lib/udev/rules.d/60-libsane1.rules', which is 
different from other instances of package libsane1:i386
  ErrorMessage: trying to overwrite shared 
'/lib/udev/rules.d/60-libsane1.rules', which is different from other instances 
of package libsane1:i386
  InstallationDate: Installed on 2018-07-17 (154 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-3ubuntu1
  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.3ubuntu0.1
  SourcePackage: sane-backends
  Title: package libsane1 1.0.27-1~experimental3ubuntu2 [modified: 
lib/udev/rules.d/60-libsane1.rules] failed to install/upgrade: trying to 
overwrite shared '/lib/udev/rules.d/60-libsane1.rules', which is different from 
other instances of package libsane1:i386
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1808908] Re: Screen not locked when coming out of suspend/hibernate

[Seth Arnold]

Hmm, I don't follow the chain of events here.

Ubuntu by default doesn't have a root password; if you've set one,
that's fine, but it's probably a distraction here.

Can you describe what specifically happened?

Thanks

** Information type changed from Private Security to Public Security

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

Title:
  Screen not locked when coming out of suspend/hibernate

Status in gnome-screensaver package in Ubuntu:
  New

Bug description:
  Ubuntu 18.04.1

  Just a few minutes ago, I typed the first character of my password,
  and the lock screen didn't change to the login screen. I typed the
  character again and nothing happened, so I pressed the spacebar to try
  to get the thing's attention.

  
  Then it unlocked.

  
  This is spooked me, so I restarted my laptop and tried logging in with a 
random string, and nothing happened. I logged in with my regular password and 
then promptly changed it.

  I tried unlocking my system with my old password, and it worked.
  However, the terminal only recognizes my new root password.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-screensaver (not installed)
  ProcVersionSignature: Ubuntu 4.15.0-42.45-generic 4.15.18
  Uname: Linux 4.15.0-42-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Dec 17 23:10:46 2018
  InstallationDate: Installed on 2018-09-15 (94 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-screensaver
  Symptom: security
  Title: Screen not locked when coming out of suspend/hibernate
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1804715] Re: package desktop-file-utils 0.22-1ubuntu5.1 failed to install/upgrade: dependency problems - leaving triggers unprocessed

[Launchpad Bug Tracker]

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

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

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

Title:
  package desktop-file-utils 0.22-1ubuntu5.1 failed to install/upgrade:
  dependency problems - leaving triggers unprocessed

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

Bug description:
  Just tried running a simple apt update && upgrade and it failed to
  upgrade properly

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: desktop-file-utils 0.22-1ubuntu5.1
  ProcVersionSignature: Ubuntu 4.4.0-122.146-generic 4.4.117
  Uname: Linux 4.4.0-122-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.16
  Architecture: amd64
  Date: Fri Nov 23 09:58:52 2018
  ErrorMessage: dependency problems - leaving triggers unprocessed
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.5
   apt  1.2.29
  SourcePackage: desktop-file-utils
  Title: package desktop-file-utils 0.22-1ubuntu5.1 failed to install/upgrade: 
dependency problems - leaving triggers unprocessed
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1809054] [NEW] package libsane1 1.0.27-1~experimental3ubuntu2 [modified: lib/udev/rules.d/60-libsane1.rules] failed to install/upgrade: trying to overwrite shared '/lib/udev/ru

[Tom Huber]

Public bug reported:

I tried to install wine and this happened.

ProblemType: Package
DistroRelease: Ubuntu 18.04
Package: libsane1 1.0.27-1~experimental3ubuntu2 [modified: 
lib/udev/rules.d/60-libsane1.rules]
ProcVersionSignature: Ubuntu 4.15.0-42.45-generic 4.15.18
Uname: Linux 4.15.0-42-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.2
Architecture: amd64
Date: Tue Dec 18 17:12:18 2018
DuplicateSignature:
 package:libsane1:1.0.27-1~experimental3ubuntu2 [modified: 
lib/udev/rules.d/60-libsane1.rules]
 Unpacking libsane1:i386 (1.0.27-1~experimental3ubuntu2) ...
 dpkg: error processing archive 
/var/cache/apt/archives/libsane1_1.0.27-1~experimental3ubuntu2_i386.deb 
(--unpack):
  trying to overwrite shared '/lib/udev/rules.d/60-libsane1.rules', which is 
different from other instances of package libsane1:i386
ErrorMessage: trying to overwrite shared '/lib/udev/rules.d/60-libsane1.rules', 
which is different from other instances of package libsane1:i386
InstallationDate: Installed on 2018-07-17 (154 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-3ubuntu1
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.3ubuntu0.1
SourcePackage: sane-backends
Title: package libsane1 1.0.27-1~experimental3ubuntu2 [modified: 
lib/udev/rules.d/60-libsane1.rules] failed to install/upgrade: trying to 
overwrite shared '/lib/udev/rules.d/60-libsane1.rules', which is different from 
other instances of package libsane1:i386
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: sane-backends (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package bionic need-duplicate-check package-conflict 
third-party-packages

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

Title:
  package libsane1 1.0.27-1~experimental3ubuntu2 [modified:
  lib/udev/rules.d/60-libsane1.rules] failed to install/upgrade: trying
  to overwrite shared '/lib/udev/rules.d/60-libsane1.rules', which is
  different from other instances of package libsane1:i386

Status in sane-backends package in Ubuntu:
  New

Bug description:
  I tried to install wine and this happened.

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: libsane1 1.0.27-1~experimental3ubuntu2 [modified: 
lib/udev/rules.d/60-libsane1.rules]
  ProcVersionSignature: Ubuntu 4.15.0-42.45-generic 4.15.18
  Uname: Linux 4.15.0-42-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  Date: Tue Dec 18 17:12:18 2018
  DuplicateSignature:
   package:libsane1:1.0.27-1~experimental3ubuntu2 [modified: 
lib/udev/rules.d/60-libsane1.rules]
   Unpacking libsane1:i386 (1.0.27-1~experimental3ubuntu2) ...
   dpkg: error processing archive 
/var/cache/apt/archives/libsane1_1.0.27-1~experimental3ubuntu2_i386.deb 
(--unpack):
trying to overwrite shared '/lib/udev/rules.d/60-libsane1.rules', which is 
different from other instances of package libsane1:i386
  ErrorMessage: trying to overwrite shared 
'/lib/udev/rules.d/60-libsane1.rules', which is different from other instances 
of package libsane1:i386
  InstallationDate: Installed on 2018-07-17 (154 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-3ubuntu1
  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.3ubuntu0.1
  SourcePackage: sane-backends
  Title: package libsane1 1.0.27-1~experimental3ubuntu2 [modified: 
lib/udev/rules.d/60-libsane1.rules] failed to install/upgrade: trying to 
overwrite shared '/lib/udev/rules.d/60-libsane1.rules', which is different from 
other instances of package libsane1:i386
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1726380] Re: Option “-e” is deprecated and might be removed in a later version of gnome-terminal

[Bug Watch Updater]

** Changed in: gnome-terminal
   Status: Unknown => Confirmed

** Changed in: gnome-terminal
   Importance: Unknown => Medium

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

Title:
  Option “-e” is deprecated and might be removed in a later version of
  gnome-terminal

Status in GNOME Terminal:
  Confirmed
Status in gnome-terminal package in Ubuntu:
  Confirmed

Bug description:
  After upgrading from Ubuntu 17.04 to 17.10, I get a warning about that
  option -e is deprecated when starting gnome-terminal from the command
  line. For example, assume I want to open a gnome-terminal with two
  tabs, and running separate commands in each tab:

  
  $ gnome-terminal --tab --active -e 'bash -c "echo Hello; exec bash"' --tab -e 
'bash -c "echo Hello2; exec bash"'
  Option “-e” is deprecated and might be removed in a later version of 
gnome-terminal.
  Use “-- ” to terminate the options and put the command line to execute after 
it.
  Option “-e” is deprecated and might be removed in a later version of 
gnome-terminal.
  Use “-- ” to terminate the options and put the command line to execute after 
it.

  But how can I run separate commands for each tab if I am supposed to use -- 
to terminate the options? For example, the following does not work:
  
  $ gnome-terminal --tab --active -- bash -c "echo Hello; exec bash" --tab -- 
bash -c "echo Hello2; exec bash"
  It just opens a single tab.

  See also:

  https://askubuntu.com/q/968032/156688

  
  --- System information:

  $ lsb_release -rd
  Description:  Ubuntu 17.10
  Release:  17.10

  $ apt-cache policy gnome-terminal
  gnome-terminal:
Installed: 3.24.2-0ubuntu4
Candidate: 3.24.2-0ubuntu4
Version table:
   *** 3.24.2-0ubuntu4 500
  500 http://no.archive.ubuntu.com/ubuntu artful/main amd64 Packages
  100 /var/lib/dpkg/status

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

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

[Desktop-packages] [Bug 374079] Re: Internal microphone doesn't work at all

[David VANTYGHEM]

As explained in https://elubuntero.wordpress.com/tag/realtek-alc268/ , I
tried to add linux-backports-modules-*** but this package isn't anymore
in Ubuntu and Mint repositories.

I tried all options as explained in https://doc.ubuntu-
fr.org/audio_intel_hda , no result. Please heelp.

** Changed in: alsa-driver (Ubuntu)
   Status: Invalid => Confirmed

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

Title:
  Internal microphone doesn't work at all

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  My computer is Acer TravelMate 7520G. Ubuntu 9.04 Jaunty Jackalope.

  Sound card is working otherwise ok, but the internal microphone does't
  work at all. I've tired modifying the alsa-base.conf file's last row
  to read like: options snd-hda-intel model=acer-aspire, options snd-
  hda-intel model=acer and the third one for digital built-in acer mic.
  None of the above have worked.

  
  From the user's point of wiev it seems like the microphone cannot be 
activated at all. If I try to activate my microphone from sound menu (from top 
right corner on desk top) -> volume control -> record (tab), the microphone is 
allways showing a red cross (like it is muted). The red cross can be removed, 
but the red cross appears back after closing the control panel. 

  After test recording with mic activated the result is only static
  noise during play-back.

  ProblemType: Bug
  AplayDevices:
    Luettelo PLAYBACK laitteista 
   kortti 0: SB [HDA ATI SB], laite 0: ALC268 Analog [ALC268 Analog]
 Alalaitteet: 1/1
 Alalaite #0: subdevice #0
  Architecture: i386
  ArecordDevices:
    Luettelo CAPTURE laitteista 
   kortti 0: SB [HDA ATI SB], laite 0: ALC268 Analog [ALC268 Analog]
 Alalaitteet: 1/1
 Alalaite #0: subdevice #0
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  kone   3631 F mixer_applet2
  Card0.Amixer.info:
   Card hw:0 'SB'/'HDA ATI SB at 0xf060 irq 16'
 Mixer name : 'Realtek ALC268'
 Components : 'HDA:10ec0268,10250124,0013 
HDA:14f12c06,10250093,0010'
 Controls  : 11
 Simple ctrls  : 8
  CurrentDmesg:
   [   26.471439] sky2 eth0: enabling interface
   [   26.471669] ADDRCONF(NETDEV_UP): eth0: link is not ready
   [   31.097025] eth1: no IPv6 routers present
   [   84.500043] Clocksource tsc unstable (delta = -288762894 ns)
  DistroRelease: Ubuntu 9.04
  NonfreeKernelModules: fglrx
  Package: alsa-base 1.0.18.dfsg-1ubuntu8
  PackageArchitecture: all
  ProcEnviron:
   LANG=fi_FI.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Uname: Linux 2.6.28-11-generic i686

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

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

[Desktop-packages] [Bug 374079] Re: Internal microphone doesn't work at all

[David VANTYGHEM]

I have this problem with Ubuntu 18.04, 18.10 and Linux Mint 19, on 2 computers :
HP Pavilion dv6700 and Acer Extensa 5620Z, both with a Realtek ALC268 chipset.
Audio is working but not internal microphone (and on HP Pavilion, external 
microphone doesn't work too).

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

Title:
  Internal microphone doesn't work at all

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  My computer is Acer TravelMate 7520G. Ubuntu 9.04 Jaunty Jackalope.

  Sound card is working otherwise ok, but the internal microphone does't
  work at all. I've tired modifying the alsa-base.conf file's last row
  to read like: options snd-hda-intel model=acer-aspire, options snd-
  hda-intel model=acer and the third one for digital built-in acer mic.
  None of the above have worked.

  
  From the user's point of wiev it seems like the microphone cannot be 
activated at all. If I try to activate my microphone from sound menu (from top 
right corner on desk top) -> volume control -> record (tab), the microphone is 
allways showing a red cross (like it is muted). The red cross can be removed, 
but the red cross appears back after closing the control panel. 

  After test recording with mic activated the result is only static
  noise during play-back.

  ProblemType: Bug
  AplayDevices:
    Luettelo PLAYBACK laitteista 
   kortti 0: SB [HDA ATI SB], laite 0: ALC268 Analog [ALC268 Analog]
 Alalaitteet: 1/1
 Alalaite #0: subdevice #0
  Architecture: i386
  ArecordDevices:
    Luettelo CAPTURE laitteista 
   kortti 0: SB [HDA ATI SB], laite 0: ALC268 Analog [ALC268 Analog]
 Alalaitteet: 1/1
 Alalaite #0: subdevice #0
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  kone   3631 F mixer_applet2
  Card0.Amixer.info:
   Card hw:0 'SB'/'HDA ATI SB at 0xf060 irq 16'
 Mixer name : 'Realtek ALC268'
 Components : 'HDA:10ec0268,10250124,0013 
HDA:14f12c06,10250093,0010'
 Controls  : 11
 Simple ctrls  : 8
  CurrentDmesg:
   [   26.471439] sky2 eth0: enabling interface
   [   26.471669] ADDRCONF(NETDEV_UP): eth0: link is not ready
   [   31.097025] eth1: no IPv6 routers present
   [   84.500043] Clocksource tsc unstable (delta = -288762894 ns)
  DistroRelease: Ubuntu 9.04
  NonfreeKernelModules: fglrx
  Package: alsa-base 1.0.18.dfsg-1ubuntu8
  PackageArchitecture: all
  ProcEnviron:
   LANG=fi_FI.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Uname: Linux 2.6.28-11-generic i686

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

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

[Desktop-packages] [Bug 1765304] Re: Ubuntu 18.04's ibus package breaks password fields in Firefox (by lowering & raising window whenever they're focused)

[Brian Murray]

Hello Daniel, or anyone else affected,

Accepted gnome-shell into cosmic-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/gnome-
shell/3.30.1-2ubuntu1.18.10.2 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-cosmic to verification-done-cosmic. If it does not
fix the bug for you, please add a comment stating that, and change the
tag to verification-failed-cosmic. In either case, without details of
your testing we will not be able to proceed.

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

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

** Changed in: gnome-shell (Ubuntu Cosmic)
   Status: In Progress => Fix Committed

** Tags added: verification-needed-cosmic

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

Title:
  Ubuntu 18.04's ibus package breaks password fields in Firefox (by
  lowering & raising window whenever they're focused)

Status in gnome-shell package in Ubuntu:
  Fix Released
Status in ibus package in Ubuntu:
  Invalid
Status in gnome-shell source package in Bionic:
  Fix Committed
Status in gnome-shell source package in Cosmic:
  Fix Committed
Status in ibus source package in Cosmic:
  Invalid

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

  ---

  tl;dr: starting in Ubuntu 18.04, "ibus" seems to lower and raise
  Firefox, whenever the user tries to focus an 
  field on a web page.  This is not a regression in Firefox, as the same
  Firefox version runs just fine in Ubuntu 17.10 -- it seems to be a bug
  in ibus, because it only happens (in 18.04) when the environmental
  variable GTK_IM_MODULE is at its default value (which is "ibus").  It
  had this same value in 17.10 but the bug didn't happen there; hence,
  I'm guessing there was a change in ibus (or a related package) that
  caused this breakage / lowering+raising.

  This is pretty bad, because in some cases, the focus-loss can mean
  users are simply unable to fill in password fields that previously
  were working fine. (see "ACTUAL RESULTS" below)

  STEPS TO REPRODUCE #1, via "BitWarden" Firefox extension:
  =
   1. Start Firefox. (fresh profile if you like)
   2. Install BitWarden from 
https://addons.mozilla.org/en-US/firefox/addon/bitwarden-password-manager/
   3. Click the BitWarden toolbar icon to spawn a menu-pane.
   4. Click "Log in" at the bottom of that pane.
   5. Click the "Master Password" field.

  ACTUAL RESULTS:
   The menu pane disappears as soon as the Master Password field receives focus.
  EXPECTED RESULTS:
   I should be able to type in a password; pane shouldn't disappear.

  STEPS TO REPRODUCE #2, via Reddit:
  =
   1. Visit https://www.reddit.com/r/firefox/ (or any reddit page)
   2. Click "Log in or sign up in seconds" at the extreme upper right of the 
page.
    (click the "Log in" part of that sentence)
   3. Try to click the password field (or "tab" into it) and type in some text.

  ACTUAL RESULTS:
   Try as you might, the password field never receives focus.
  EXPECTED RESULTS:
   Password field should accept focus & let me type text into it.

  If I run firefox from the command line with env var GTK_IM_MODULE="",
  then I get "expected results".  But with the default value of that env
  var, I get "actual results" (broken behavior, unable to enter
  passwords).

  I initially reported this in Firefox, here:
  https://bugzilla.mozilla.org/show_bug.cgi?id=1451466 (with a few
  dependent bugs for the usage-specific STR quoted above).  But I think
  it's a bug in ibus, hence filing here now.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: ibus 1.5.17-3ubuntu3
  ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15
  Uname: Linux 4.15.0-15-generic x86_64
  ApportVersion: 2.20.9-0ubuntu5
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Apr 18 23:22:05 2018
  InstallationDate: Installed on 2018-04-17 (1 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180416)
  SourcePackage: ibus
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:

[Desktop-packages] [Bug 1809044] [NEW] DVD playback error: unable to play . . . DVD source is required . . .

[Chris Rainey]

Public bug reported:

Successful installation of libdvd-pkg and dpkg-reconfigure, afterwards,
to complete compilation.

Inserted known-good DVD and clicked on "Open in Videos" which launched
the Totem player.

Error msg:  "Unable to play the file, DVD source is required, but is not
installed."

DVD will play normally in VLC player after installation on same machine.

ProblemType: Bug
DistroRelease: Ubuntu 18.10
Package: libgstreamer1.0-0 1.14.4-1
ProcVersionSignature: Ubuntu 4.18.0-12.13-generic 4.18.17
Uname: Linux 4.18.0-12-generic x86_64
ApportVersion: 2.20.10-0ubuntu13.1
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Tue Dec 18 15:21:45 2018
InstallationDate: Installed on 2018-11-13 (34 days ago)
InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3)
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: gstreamer1.0
UpgradeStatus: No upgrade log present (probably fresh install)
XorgLog: Error: [Errno 2] No such file or directory: '/var/log/Xorg.0.log'

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


** Tags: amd64 apport-bug cosmic

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

Title:
  DVD playback error:  unable to play . . . DVD source is required . . .

Status in gstreamer1.0 package in Ubuntu:
  New

Bug description:
  Successful installation of libdvd-pkg and dpkg-reconfigure,
  afterwards, to complete compilation.

  Inserted known-good DVD and clicked on "Open in Videos" which launched
  the Totem player.

  Error msg:  "Unable to play the file, DVD source is required, but is
  not installed."

  DVD will play normally in VLC player after installation on same
  machine.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: libgstreamer1.0-0 1.14.4-1
  ProcVersionSignature: Ubuntu 4.18.0-12.13-generic 4.18.17
  Uname: Linux 4.18.0-12-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13.1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Dec 18 15:21:45 2018
  InstallationDate: Installed on 2018-11-13 (34 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gstreamer1.0
  UpgradeStatus: No upgrade log present (probably fresh install)
  XorgLog: Error: [Errno 2] No such file or directory: '/var/log/Xorg.0.log'

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

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

[Desktop-packages] [Bug 1774242] Re: Wacom touchscreens should use libinput, not wacom driver

[Greg]

I deleted the whole section as suggested by Shawn, and also deleted the
similar one with "USB". Now my touchscreen and everything else are
working great.

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

Title:
  Wacom touchscreens should use libinput, not wacom driver

Status in xf86-input-wacom package in Ubuntu:
  Confirmed

Bug description:
  /usr/share/X11/xorg.conf.d/70-wacom.conf as shipped, has this:

  Section "InputClass"
  Identifier "Wacom touchscreen class"
  MatchProduct "Wacom|WACOM|PTK-540WL|ISD-V4"
  MatchDevicePath "/dev/input/event*"
  MatchIsTouchscreen "true"
  Driver "wacom"
  EndSection

  The result is that on my Yoga 920, in a plain X11 session (running
  openbox in my case), the touchscreen acts like a broken mouse: there
  is no multi-touch capability in Qt Quick applications, and clicking
  isn't quite right either.  I also verified it with Peter Hutterer's
  old cairo-based mt-touch test program.

  I suspect we will get some users mistakenly writing up Qt bugs about
  this if you don't ship a fix.  (Seems to me that already happened at
  least once, actually.)

  Yes, the touchscreen is made by Wacom, but wacom_drv.so has
  historically been only for Wacom tablets and in-screen stylus
  digitizers, and IMO that continues to be the case.  libinput is a much
  better choice of driver for this hardware (so is evdev for that
  matter), so I changed it to Driver "libinput" and got it working.
  (Wayland uses libinput, so in a wayland session, touch already works
  fine in Qt apps on this hardware.)

  I'm one of the Qt Quick maintainers, most concerned with touch
  handling, and I've also written some of the Qt xcb code for dealing
  with XInput touch and tablet devices.  So if you think that there's
  something wrong with Qt, such that it should still work anyway to use
  a wacom driver for a Wacom touchscreen, let me know.  These AES
  devices are still new to me (that's why I got a Yoga, to try it out).

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xserver-xorg-input-wacom 1:0.36.1-0ubuntu1 [modified: 
usr/share/X11/xorg.conf.d/70-wacom.conf]
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  Uname: Linux 4.15.0-22-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  Date: Wed May 30 19:40:51 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  MachineType: LENOVO 80Y7
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-22-generic 
root=ZFS=rpool/ROOT/ubuntu ro
  SourcePackage: xf86-input-wacom
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/22/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 5NCN38WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40709 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 31
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo YOGA 920-13IKB
  dmi.modalias: 
dmi:bvnLENOVO:bvr5NCN38WW:bd02/22/2018:svnLENOVO:pn80Y7:pvrLenovoYOGA920-13IKB:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct31:cvrLenovoYOGA920-13IKB:
  dmi.product.family: YOGA 920-13IKB
  dmi.product.name: 80Y7
  dmi.product.version: Lenovo YOGA 920-13IKB
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.91-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.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

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xf86-input-wacom/+bug/1774242/+subscriptions

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

[Desktop-packages] [Bug 1808710] Re: !xcb_xlib_threads_sequence_lost error

[Ilya Kotov]

** Description changed:

- Several applications randomly crash with same error. See attached files.
+ Some gkt2 applications randomly crash with same error. See attached
+ files.

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

Title:
  !xcb_xlib_threads_sequence_lost error

Status in gtk+2.0 package in Ubuntu:
  New

Bug description:
  Some gkt2 applications randomly crash with same error. See attached
  files.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gtk+2.0/+bug/1808710/+subscriptions

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

[Desktop-packages] [Bug 1808880] Re: Got unknown content type text/html from reviews.ubuntu.com

[Sebastien Bacher]

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

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

Title:
  Got unknown content type text/html from reviews.ubuntu.com

Status in gnome-software package in Ubuntu:
  New

Bug description:
  see screenshot

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-software 3.28.1-0ubuntu4.18.04.8
  ProcVersionSignature: Ubuntu 4.15.0-42.45-generic 4.15.18
  Uname: Linux 4.15.0-42-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Dec 18 01:25:58 2018
  InstallationDate: Installed on 2018-12-16 (1 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  InstalledPlugins:
   gnome-software-plugin-flatpak N/A
   gnome-software-plugin-limba   N/A
   gnome-software-plugin-snap3.28.1-0ubuntu4.18.04.8
  SourcePackage: gnome-software
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1808710] Re: !xcb_xlib_threads_sequence_lost error

[Ilya Kotov]

** Attachment added: "_usr_bin_gpicview.1000.crash"
   
https://bugs.launchpad.net/ubuntu/+source/freecad/+bug/1808710/+attachment/522/+files/_usr_bin_gpicview.1000.crash

** Package changed: freecad (Ubuntu) => gtk+2.0 (Ubuntu)

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

Title:
  !xcb_xlib_threads_sequence_lost error

Status in gtk+2.0 package in Ubuntu:
  New

Bug description:
  Some gkt2 applications randomly crash with same error. See attached
  files.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gtk+2.0/+bug/1808710/+subscriptions

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

[Desktop-packages] [Bug 1809025] Re: Files Failed to Be Moved to The Desktop

[Sebastien Bacher]

What's the output of that command?

$ dpkg -l | grep nautilus

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

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

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

Title:
  Files Failed to Be Moved to The Desktop

Status in nautilus package in Ubuntu:
  Incomplete

Bug description:
  I was trying to move a downloaded file from the "Downloads" folder to
  the actual desktop background and the file(s) wouldn't move from any
  folder to there. Please make a fix for this as its already a
  workaround. [By the way, this happens when you change from the the
  default wallpaper].

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: xorg 1:7.7+19ubuntu8
  ProcVersionSignature: Ubuntu 4.19.0-9.10-generic 4.19.8
  Uname: Linux 4.19.0-9-generic x86_64
  ApportVersion: 2.20.10-0ubuntu14
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Dec 18 13:52:46 2018
  DistUpgraded: Fresh install
  DistroCodename: disco
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company 3rd Gen Core processor Graphics 
Controller [103c:179b]
  InstallationDate: Installed on 2018-12-18 (0 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20181218)
  MachineType: Hewlett-Packard HP EliteBook 8470p
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.19.0-9-generic 
root=UUID=6c7fa075-d8d0-47c2-b828-83d330564545 ro quiet splash vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/07/2013
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: 68ICF Ver. F.45
  dmi.board.name: 179B
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 42.36
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvr68ICFVer.F.45:bd10/07/2013:svnHewlett-Packard:pnHPEliteBook8470p:pvrA1019DD202:rvnHewlett-Packard:rn179B:rvrKBCVersion42.36:cvnHewlett-Packard:ct10:cvr:
  dmi.product.family: 103C_5336AN G=N L=BUS B=HP S=ELI
  dmi.product.name: HP EliteBook 8470p
  dmi.product.sku: D2E04UP#ABA
  dmi.product.version: A1019DD202
  dmi.sys.vendor: Hewlett-Packard
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.95-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.6-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.3-1ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20180925-2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-3

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

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

[Desktop-packages] [Bug 1808710] [NEW] !xcb_xlib_threads_sequence_lost error

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

Several applications randomly crash with same error. See attached files.

** Affects: gtk+2.0 (Ubuntu)
 Importance: Undecided
 Status: New

-- 
!xcb_xlib_threads_sequence_lost error
https://bugs.launchpad.net/bugs/1808710
You received this bug notification because you are a member of Desktop 
Packages, which is subscribed to gtk+2.0 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 1809038] [NEW] [snap] Cannot install extension: 'Could not create download directory'

[Glotzbach]

Public bug reported:

I tried installing an extension from the Chrome web store (which I
believe normally should work), but when clicking 'Add to Chrome' and
confirming, Chromium gives an error:

"An error has occurred
Could not create download directory"

I guess this has to do with the advanced security features of snaps?

Version: Version 71.0.3578.80 (Official Build) snap (64-bit)

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


** Tags: permissions snap

** Description changed:

  I tried installing an extension from the Chrome web store (which I
  believe normally should work), but when clicking 'Add to Chrome' and
  confirming, Chromium gives an error:
  
  "An error has occurred
  Could not create download directory"
  
  I guess this has to do with the advanced security features of snaps?
+ 
+ Version: Version 71.0.3578.80 (Official Build) snap (64-bit)

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

Title:
  [snap] Cannot install extension: 'Could not create download directory'

Status in chromium-browser package in Ubuntu:
  New

Bug description:
  I tried installing an extension from the Chrome web store (which I
  believe normally should work), but when clicking 'Add to Chrome' and
  confirming, Chromium gives an error:

  "An error has occurred
  Could not create download directory"

  I guess this has to do with the advanced security features of snaps?

  Version: Version 71.0.3578.80 (Official Build) snap (64-bit)

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

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

[Desktop-packages] [Bug 1767648] Re: Top bar and shell dialogs are not displayed properly when zoom is enabled

[Leona]

Hi
I have a visual impairment which requires me to use the magnification 
accessibility extension.
I have 2 machines, my desktop currently running Mint 18.3 and my laptop (Acer 
Switch Alpha 12) running Ubuntu 18.04

I have noticed the bug as reported here as being the same one that I
experience on the laptop running gnome.

This doesn't happen in Mint (different desktop, Cinemon not gnome).
I had used previous versions of the Gnome variant of Ubuntu 15.10 and up before 
and saw this happening on them, I was hoping this issue would be fixed by now.

This problem means I'm unable to use my laptop

Thanks
Leona.

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

Title:
  Top bar and shell dialogs are not displayed properly when zoom is
  enabled

Status in Mutter:
  In Progress
Status in mutter package in Ubuntu:
  In Progress
Status in mutter source package in Bionic:
  In Progress

Bug description:
  When zoom is enabled, the top bar and some shell dialogs (wireless
  network selection, shutdown dialog, etc.) are not displayed properly.
  (See the attached screenshots.)

  Steps to reproduce the issue:
  1. Enable Zoom in Setting > Universal Access
  2. (Optional) Set zoom factor to around 3 (or higher)
  3. Look at the top bar. You will notice that all texts and icons are now 
gone. If you move your cursor to the right of the top bar, and then click on 
the status menu, you will see that only a portion of the menu is shown.
  4. For the shell dialogs, go to the Settings app. In the Wifi section, choose 
one of the secured network available. You will see that the password dialog is 
not displayed in its entirety.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.28.1-0ubuntu2
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CasperVersion: 1.394
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Apr 28 12:54:24 2018
  DisplayManager: gdm3
  GsettingsChanges:
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
   b'org.gnome.desktop.interface' b'cursor-size' b'96'
  LiveMediaBuild: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1809025] Re: Files Failed to Be Moved to The Desktop

[Juhani Numminen]

Reassigning to nautilus which I believe manages the desktop on GNOME.

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

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

Title:
  Files Failed to Be Moved to The Desktop

Status in nautilus package in Ubuntu:
  New

Bug description:
  I was trying to move a downloaded file from the "Downloads" folder to
  the actual desktop background and the file(s) wouldn't move from any
  folder to there. Please make a fix for this as its already a
  workaround. [By the way, this happens when you change from the the
  default wallpaper].

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: xorg 1:7.7+19ubuntu8
  ProcVersionSignature: Ubuntu 4.19.0-9.10-generic 4.19.8
  Uname: Linux 4.19.0-9-generic x86_64
  ApportVersion: 2.20.10-0ubuntu14
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Dec 18 13:52:46 2018
  DistUpgraded: Fresh install
  DistroCodename: disco
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company 3rd Gen Core processor Graphics 
Controller [103c:179b]
  InstallationDate: Installed on 2018-12-18 (0 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20181218)
  MachineType: Hewlett-Packard HP EliteBook 8470p
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.19.0-9-generic 
root=UUID=6c7fa075-d8d0-47c2-b828-83d330564545 ro quiet splash vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/07/2013
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: 68ICF Ver. F.45
  dmi.board.name: 179B
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 42.36
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvr68ICFVer.F.45:bd10/07/2013:svnHewlett-Packard:pnHPEliteBook8470p:pvrA1019DD202:rvnHewlett-Packard:rn179B:rvrKBCVersion42.36:cvnHewlett-Packard:ct10:cvr:
  dmi.product.family: 103C_5336AN G=N L=BUS B=HP S=ELI
  dmi.product.name: HP EliteBook 8470p
  dmi.product.sku: D2E04UP#ABA
  dmi.product.version: A1019DD202
  dmi.sys.vendor: Hewlett-Packard
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.95-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.6-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.3-1ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20180925-2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-3

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

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

[Desktop-packages] [Bug 1797882] Re: At dual monitor intel_do_flush_locked failed: Resource deadlock avoided

[Ubuntu Foundations Team Bug Bot]

The attachment "dirty_patch.txt" seems to be a patch.  If it isn't,
please remove the "patch" flag from the attachment, remove the "patch"
tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the
team.

[This is an automated message performed by a Launchpad user owned by
~brian-murray, for any issues please contact him.]

** Tags added: patch

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

Title:
  At dual monitor intel_do_flush_locked failed: Resource deadlock
  avoided

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

Bug description:
  Using ubuntu wayland with dual monitors, configured above each other.
  Dock is configured at both displays, not hiding.
  Icons for "terminal" and "libreofffice Writer" are present at the dock.

  Start terminal on primary screen by mouseclick on dock.
  Start libreoffice Writer on primary screen by mouseclick on dock.
  Terminate libreoffice Witer by mouseclick on X.
  Repeat the starting and stopping of Writer.

  Login-screen will appear. Syslog shows:
  Oct 15 00:09:51 Gert2 org.gnome.Shell.desktop[5892]: intel_do_flush_locked 
failed: Resource deadlock avoided
  Oct 15 00:09:51 Gert2 gnome-terminal-[6439]: Error reading events from 
display: Connection reset by peer
  Oct 15 00:09:51 Gert2 systemd[5755]: gnome-terminal-server.service: Main 
process exited, code=exited, status=1/FAILURE

  This problem doesnot occur in a dual monitor-session without wayland.
  It also doesnot occur, if only one monitor used with wayland
  It also doesnot occur, if the dock is only present at the primary screen.
  It also doesnot occur if second started application is present at the dock 
and doesnot add an icon to the dock (as libreoffice does).

  All other dual monitor/dock configurations seem to have this problem.

  No idea if this is helpful info, but the used graphics card does not support 
OpenGL version 2.1:
  Oct 15 00:02:32 Gert2 org.gnome.Shell.desktop[4426]: Require OpenGL version 
2.1 or later.
  Oct 15 00:02:32 Gert2 org.gnome.Shell.desktop[4426]: Failed to initialize 
glamor
  Oct 15 00:02:32 Gert2 org.gnome.Shell.desktop[4426]: Failed to initialize 
glamor, falling back to sw

  glxinfo:
  OpenGL vendor string: VMware, Inc.
  OpenGL renderer string: llvmpipe (LLVM 7.0, 128 bits)
  OpenGL core profile version string: 3.3 (Core Profile) Mesa 18.2.2
  OpenGL core profile shading language version string: 3.30
  OpenGL core profile context flags: (none)
  OpenGL core profile profile mask: core profile
  OpenGL core profile extensions:
  OpenGL version string: 3.1 Mesa 18.2.2
  OpenGL shading language version string: 1.40
  OpenGL context flags: (none)
  OpenGL extensions:
  OpenGL ES profile version string: OpenGL ES 3.0 Mesa 18.2.2
  OpenGL ES profile shading language version string: OpenGL ES GLSL ES 3.00
  OpenGL ES profile extensions:

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: gnome-shell 3.30.1-2ubuntu1
  ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12
  Uname: Linux 4.18.0-10-generic i686
  ApportVersion: 2.20.10-0ubuntu13
  Architecture: i386
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Oct 15 13:25:10 2018
  DisplayManager: gdm3
  GsettingsChanges:
   b'org.gnome.shell' b'command-history' redacted by apport
   b'org.gnome.shell' b'app-picker-view' b'uint32 1'
   b'org.gnome.shell' b'favorite-apps' redacted by apport
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
  ProcEnviron:
   LANGUAGE=en_US:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1800179] Re: Search in recent files list only works with lowercase letters

[Paul White]

Downloaded gedit 3.28.1-1ubuntu1.1 and tested on Ubuntu 18.04 with
various combinations of upper/lower case characters within the filename
and extension. Search of recently used files is now caseless.


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

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

Title:
  Search in recent files list only works with lowercase letters

Status in gedit package in Ubuntu:
  Fix Released
Status in gedit source package in Bionic:
  Fix Committed
Status in gedit source package in Cosmic:
  Fix Committed

Bug description:
  * Impact
  The document filter is case sensitive which is confusing/not convenient

  * Test case
  - Open a document with an Uppercase letter
  - close it
  - click on 'open' and type the name with an Uppercase

  -> it should list the document

  * Regression potential
  The code change is in the filtering code, just test that.

  

  When clicking “Open” and typing to search the recently opened files,
  any search involving uppercase letters fails to return any result,
  even if files with uppercase letters in their file names have recently
  been opened. Searching for the same file names, but using all-
  lowercase letters, does yield results (see attached screenshot). So it
  seems that gedit converts the recently used file names to lowercase
  before comparing to the search term, which is incorrect.

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

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

[Desktop-packages] [Bug 1809011] Re: package cups 2.2.7-1ubuntu2.1 failed to install/upgrade: read error in '/var/lib/dpkg/info/cups.triggers': Input/output error

[Ubuntu Foundations Team Bug Bot]

Thank you for taking the time to report this bug and helping to make
Ubuntu better.  Reviewing your dmesg attachment in this bug report it
seems that there is a problem with your hardware.  I recommend
performing a back up and then investigating the situation.  Measures you
might take include checking cable connections and using software tools
to investigate the health of your hardware.  In the event that is is not
in fact an error with your hardware please set the bug's status back to
New.  Thanks and good luck!

[This is an automated message.  I apologize if it reached you
inappropriately; please just reply to this message indicating so.]

** Tags added: hardware-error

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

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

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

Title:
  package cups 2.2.7-1ubuntu2.1 failed to install/upgrade: read error in
  '/var/lib/dpkg/info/cups.triggers': Input/output error

Status in cups package in Ubuntu:
  Invalid

Bug description:
  Mientrasactualizaba el sistema recien instalado

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: cups 2.2.7-1ubuntu2.1
  ProcVersionSignature: Ubuntu 4.15.0-42.45-generic 4.15.18
  Uname: Linux 4.15.0-42-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  Date: Tue Dec 18 17:50:57 2018
  DuplicateSignature:
   package:cups:2.2.7-1ubuntu2.1
   Preparing to unpack .../074-cups_2.2.7-1ubuntu2.2_amd64.deb ...
   dpkg: error processing archive 
/tmp/apt-dpkg-install-0IVoPc/074-cups_2.2.7-1ubuntu2.2_amd64.deb (--unpack):
read error in '/var/lib/dpkg/info/cups.triggers': Input/output error
  ErrorMessage: read error in '/var/lib/dpkg/info/cups.triggers': Input/output 
error
  Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: No 
destinations added.
  MachineType: Packard Bell EasyNote TS44HR
  Papersize: a4
  ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-4.15.0-42-generic 
root=UUID=f9b48e7f-1e8e-46a2-b720-967fe70d5dde ro quiet splash vt.handoff=1
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-42-generic 
root=UUID=f9b48e7f-1e8e-46a2-b720-967fe70d5dde ro quiet splash vt.handoff=1
  Python3Details: /usr/bin/python3.6, Python 3.6.7, python3-minimal, 
3.6.5-3ubuntu1
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu2.1
   apt  1.6.6
  SourcePackage: cups
  Title: package cups 2.2.7-1ubuntu2.1 failed to install/upgrade: read error in 
'/var/lib/dpkg/info/cups.triggers': Input/output error
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/24/2011
  dmi.bios.vendor: Packard Bell
  dmi.bios.version: V1.11
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: SJV50_HR
  dmi.board.vendor: Packard Bell
  dmi.board.version: Base Board Version
  dmi.chassis.type: 10
  dmi.chassis.vendor: Packard Bell
  dmi.chassis.version: V1.11
  dmi.modalias: 
dmi:bvnPackardBell:bvrV1.11:bd05/24/2011:svnPackardBell:pnEasyNoteTS44HR:pvrV1.11:rvnPackardBell:rnSJV50_HR:rvrBaseBoardVersion:cvnPackardBell:ct10:cvrV1.11:
  dmi.product.name: EasyNote TS44HR
  dmi.product.version: V1.11
  dmi.sys.vendor: Packard Bell

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

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

[Desktop-packages] [Bug 1736164] Re: deja-dup/duplicity backup fails with UnicodeDecodeError

[Alexander Adam]

This bug is rather https://bugs.launchpad.net/duplicity/+bug/1386373 —
right?

As it seems that there's a fix in Fedora somewhere[1]: is there any
chance to get this upstream fix on Ubuntu 18.04 LTS as well?

I mean, I would love to have a working backup solution again. ;)

Also the error message seems to be caused by totally different
problems!?

1. a read encoding issue: https://bugs.launchpad.net/duplicity/+bug/1386373 
(because the suggested fix seem to work for Eugene)
2. readonly mount 
https://bugs.launchpad.net/deja-dup/+bug/1769891#yui_3_10_3_1_1545160806792_1239
 and https://bugs.launchpad.net/deja-dup/+bug/1741769

So I guess the error message in general is or was very misleading!?

[1] Should the patch be visible on
https://bugzilla.redhat.com/show_bug.cgi?id=1470873 ? I can't see it!?

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

Title:
  deja-dup/duplicity backup fails with UnicodeDecodeError

Status in Déjà Dup:
  Triaged
Status in Duplicity:
  New
Status in deja-dup package in Ubuntu:
  Triaged
Status in deja-dup package in Fedora:
  Fix Released

Bug description:
  See: https://bugzilla.redhat.com/show_bug.cgi?id=1470873

  
  Description of problem:
  With the update from Fedora 25 to Fedora 26 Workstation, backups with 
deja-dup/duplicity are failing

  
  Version-Release number of selected component (if applicable):
  duplicity 0.7.13.1
  deja-dup 34.3

  How reproducible:
  Always (scheduled and manually started backup)

  
  Steps to Reproduce:
  1. Wait for the scheduled backup to start or start it via the "Backup now" 
button
  2. Some or a large number of files might get backed up, then the backup stops 
with "Failed with an unknown error"
  3.

  Actual results:
  Backup fails

  Expected results:
  Backup completes as it always did

  
  Additional info:
  Traceback (most recent call last):
File "/usr/bin/duplicity", line 1540, in 
  with_tempdir(main)
File "/usr/bin/duplicity", line 1534, in with_tempdir
  fn()
File "/usr/bin/duplicity", line 1385, in main
  do_backup(action)
File "/usr/bin/duplicity", line 1516, in do_backup
  incremental_backup(sig_chain)
File "/usr/bin/duplicity", line 668, in incremental_backup
  globals.backend)
File "/usr/bin/duplicity", line 453, in write_multivol
  (tdp, dest_filename, vol_num)))
File "/usr/lib64/python2.7/site-packages/duplicity/asyncscheduler.py", line 
146, in schedule_task
  return self.__run_synchronously(fn, params)
File "/usr/lib64/python2.7/site-packages/duplicity/asyncscheduler.py", line 
172, in __run_synchronously
  ret = fn(*params)
File "/usr/bin/duplicity", line 452, in 
  vol_num: put(tdp, dest_filename, vol_num),
File "/usr/bin/duplicity", line 341, in put
  backend.put(tdp, dest_filename)
File "/usr/lib64/python2.7/site-packages/duplicity/backend.py", line 376, 
in inner_retry
  % exception_traceback())
File "/usr/lib64/python2.7/site-packages/duplicity/util.py", line 51, in 
exception_traceback
  return uexc(msg)
File "/usr/lib64/python2.7/site-packages/duplicity/util.py", line 79, in 
uexc
  e = unicode(e).encode('utf-8')
  UnicodeDecodeError: 'ascii' codec can't decode byte 0xe2 in position 746: 
ordinal not in range(128)

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

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

[Desktop-packages] [Bug 1807460] Re: Filenames with spaces not accepted when connecting to certificate-authenticated wifi

[Michael T]

Howdy! Apologies for the slow response.

I downloaded and installed the .deb files from #5 and found that it
fixed the problem where I couldn't connect to the network.

Although the changed files fix the most important problem, filenames are
still displayed URL-encoded in the applet window after a file with
spaces is selected, as the attached screenshot shows.

** Attachment added: "wpa-spaces-urlencoded.png"
   
https://bugs.launchpad.net/ubuntu/+source/network-manager-applet/+bug/1807460/+attachment/5223324/+files/wpa-spaces-urlencoded.png

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

Title:
  Filenames with spaces not accepted when connecting to certificate-
  authenticated wifi

Status in network-manager-applet package in Ubuntu:
  Fix Released
Status in network-manager-applet source package in Bionic:
  Incomplete

Bug description:
  This bug was encountered on a fresh install of Ubuntu 18.04.1 LTS

  When connecting to a certificate-authenticated wifi network (WPA/WPA2
  Enterprise, authentication TLS) for the first time, the "Wi-Fi Network
  Authentication Required" dialogue is displayed, prompting the user to
  select their CA and user certificates.

  Unexpected behaviour: If any of the files have spaces in their
  filenames, after choosing them in the file picker the field is
  highlighted by a red box, and the 'Connect' button is greyed out.

  This is depicted in the attachment network-authentication-red-box-
  spaces-filename.png

  There is also no explanation offered for why the red box highlight is
  present - no tooltip, no help from pressing F1, no popup, and as far
  as I can find no logs.

  If you move/rename the file, so there are no spaces in the filename,
  the problem is worked around.

  The problem is not present on the edit connection dialogue; filenames
  with spaces are acceptable there.

  The problem was also not present on Ubuntu 16.04, and users who
  upgrade from 16.04 to 18.04 will find their connection keeps working.
  It is only when creating an entirely new connection (or after
  forgetting the connection and recreating it) that the problem dialog
  appears.

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

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

[Desktop-packages] [Bug 1796499] Re: Keyboard calculator button not working

[Launchpad Bug Tracker]

This bug was fixed in the package gnome-settings-daemon -
3.30.1.2-1ubuntu3

---
gnome-settings-daemon (3.30.1.2-1ubuntu3) cosmic; urgency=medium

  * debian/patches/ubuntu_calculator_snap.patch:
- teach gsd about the gnome-calculator snap .desktop name, so it knows
  how to start the calculator from its keybinding (lp: #1796499)

 -- Sebastien Bacher   Thu, 25 Oct 2018 13:56:39
+0200

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

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

Title:
  Keyboard calculator button not working

Status in gnome-settings-daemon package in Ubuntu:
  Fix Released
Status in gnome-settings-daemon source package in Cosmic:
  Fix Released

Bug description:
  * Impact
  The calculator keybinding doesn't work with the gnome-calculator snap

  * Test case
  - go to gnome-control-center, keyboard and configure a keybinding to start 
the calculator (or use the default one which is the calculator key if you have 
a keyboard including one of those)
  - install gnome-calculator as a snap and remove the deb (should be the case 
on the default installation)
  - press the configured key

  -> the calculator should start

  * Regression potential
  The code allows trying 2 .desktop name, upstream renamed their in the 3.23 
which was in zesty, they still include the fallback but Ubuntu hasn't been 
needed it since zesty, the patch changes to know about the current .deb name 
and about the snap one. If users had pinned an years old version of the 
calculator then their keybinding is going to stop working

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

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

[Desktop-packages] [Bug 1796499] Update Released

[Brian Murray]

The verification of the Stable Release Update for gnome-settings-daemon
has completed successfully and the package has now been released to
-updates.  Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report.  In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

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

Title:
  Keyboard calculator button not working

Status in gnome-settings-daemon package in Ubuntu:
  Fix Released
Status in gnome-settings-daemon source package in Cosmic:
  Fix Released

Bug description:
  * Impact
  The calculator keybinding doesn't work with the gnome-calculator snap

  * Test case
  - go to gnome-control-center, keyboard and configure a keybinding to start 
the calculator (or use the default one which is the calculator key if you have 
a keyboard including one of those)
  - install gnome-calculator as a snap and remove the deb (should be the case 
on the default installation)
  - press the configured key

  -> the calculator should start

  * Regression potential
  The code allows trying 2 .desktop name, upstream renamed their in the 3.23 
which was in zesty, they still include the fallback but Ubuntu hasn't been 
needed it since zesty, the patch changes to know about the current .deb name 
and about the snap one. If users had pinned an years old version of the 
calculator then their keybinding is going to stop working

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

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

[Desktop-packages] [Bug 1808880] Re: Got unknown content type text/html from reviews.ubuntu.com

[Sergey Ivanov]

Yes, tried to write feedback and receive message constantly.

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

Title:
  Got unknown content type text/html from reviews.ubuntu.com

Status in gnome-software package in Ubuntu:
  Incomplete

Bug description:
  see screenshot

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-software 3.28.1-0ubuntu4.18.04.8
  ProcVersionSignature: Ubuntu 4.15.0-42.45-generic 4.15.18
  Uname: Linux 4.15.0-42-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Dec 18 01:25:58 2018
  InstallationDate: Installed on 2018-12-16 (1 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  InstalledPlugins:
   gnome-software-plugin-flatpak N/A
   gnome-software-plugin-limba   N/A
   gnome-software-plugin-snap3.28.1-0ubuntu4.18.04.8
  SourcePackage: gnome-software
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1809025] [NEW] Files Failed to Be Moved to The Desktop

[Vanilla Summers]

Public bug reported:

I was trying to move a downloaded file from the "Downloads" folder to
the actual desktop background and the file(s) wouldn't move from any
folder to there. Please make a fix for this as its already a workaround.
[By the way, this happens when you change from the the default
wallpaper].

ProblemType: Bug
DistroRelease: Ubuntu 19.04
Package: xorg 1:7.7+19ubuntu8
ProcVersionSignature: Ubuntu 4.19.0-9.10-generic 4.19.8
Uname: Linux 4.19.0-9-generic x86_64
ApportVersion: 2.20.10-0ubuntu14
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Tue Dec 18 13:52:46 2018
DistUpgraded: Fresh install
DistroCodename: disco
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GraphicsCard:
 Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 
09) (prog-if 00 [VGA controller])
   Subsystem: Hewlett-Packard Company 3rd Gen Core processor Graphics 
Controller [103c:179b]
InstallationDate: Installed on 2018-12-18 (0 days ago)
InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20181218)
MachineType: Hewlett-Packard HP EliteBook 8470p
ProcEnviron:
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.19.0-9-generic 
root=UUID=6c7fa075-d8d0-47c2-b828-83d330564545 ro quiet splash vt.handoff=1
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 10/07/2013
dmi.bios.vendor: Hewlett-Packard
dmi.bios.version: 68ICF Ver. F.45
dmi.board.name: 179B
dmi.board.vendor: Hewlett-Packard
dmi.board.version: KBC Version 42.36
dmi.chassis.type: 10
dmi.chassis.vendor: Hewlett-Packard
dmi.modalias: 
dmi:bvnHewlett-Packard:bvr68ICFVer.F.45:bd10/07/2013:svnHewlett-Packard:pnHPEliteBook8470p:pvrA1019DD202:rvnHewlett-Packard:rn179B:rvrKBCVersion42.36:cvnHewlett-Packard:ct10:cvr:
dmi.product.family: 103C_5336AN G=N L=BUS B=HP S=ELI
dmi.product.name: HP EliteBook 8470p
dmi.product.sku: D2E04UP#ABA
dmi.product.version: A1019DD202
dmi.sys.vendor: Hewlett-Packard
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.95-1
version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.6-1ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.20.3-1ubuntu1
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.1.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20180925-2
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-3

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


** Tags: amd64 apport-bug disco has-workaround single-occurrence ubuntu 
wayland-session

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

Title:
  Files Failed to Be Moved to The Desktop

Status in xorg package in Ubuntu:
  New

Bug description:
  I was trying to move a downloaded file from the "Downloads" folder to
  the actual desktop background and the file(s) wouldn't move from any
  folder to there. Please make a fix for this as its already a
  workaround. [By the way, this happens when you change from the the
  default wallpaper].

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: xorg 1:7.7+19ubuntu8
  ProcVersionSignature: Ubuntu 4.19.0-9.10-generic 4.19.8
  Uname: Linux 4.19.0-9-generic x86_64
  ApportVersion: 2.20.10-0ubuntu14
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Dec 18 13:52:46 2018
  DistUpgraded: Fresh install
  DistroCodename: disco
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company 3rd Gen Core processor Graphics 
Controller [103c:179b]
  InstallationDate: Installed on 2018-12-18 (0 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20181218)
  MachineType: Hewlett-Packard HP EliteBook 8470p
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.19.0-9-generic 
root=UUID=6c7fa075-d8d0-47c2-b828-83d330564545 ro quiet splash vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/07/2013
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: 68ICF Ver. F.45
  dmi.board.name: 179B
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 42.36
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:

[Desktop-packages] [Bug 1807460] Re: Filenames with spaces not accepted when connecting to certificate-authenticated wifi

[Brian Murray]

While the issue seems straight forward to recreate from the description
the bug is still missing Regression Potential information which is
required for the SRU process.

** Also affects: network-manager-applet (Ubuntu Bionic)
   Importance: Undecided
   Status: New

** Changed in: network-manager-applet (Ubuntu Bionic)
   Status: New => Incomplete

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

Title:
  Filenames with spaces not accepted when connecting to certificate-
  authenticated wifi

Status in network-manager-applet package in Ubuntu:
  Fix Released
Status in network-manager-applet source package in Bionic:
  Incomplete

Bug description:
  This bug was encountered on a fresh install of Ubuntu 18.04.1 LTS

  When connecting to a certificate-authenticated wifi network (WPA/WPA2
  Enterprise, authentication TLS) for the first time, the "Wi-Fi Network
  Authentication Required" dialogue is displayed, prompting the user to
  select their CA and user certificates.

  Unexpected behaviour: If any of the files have spaces in their
  filenames, after choosing them in the file picker the field is
  highlighted by a red box, and the 'Connect' button is greyed out.

  This is depicted in the attachment network-authentication-red-box-
  spaces-filename.png

  There is also no explanation offered for why the red box highlight is
  present - no tooltip, no help from pressing F1, no popup, and as far
  as I can find no logs.

  If you move/rename the file, so there are no spaces in the filename,
  the problem is worked around.

  The problem is not present on the edit connection dialogue; filenames
  with spaces are acceptable there.

  The problem was also not present on Ubuntu 16.04, and users who
  upgrade from 16.04 to 18.04 will find their connection keeps working.
  It is only when creating an entirely new connection (or after
  forgetting the connection and recreating it) that the problem dialog
  appears.

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

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

[Desktop-packages] [Bug 1809013] Re: WhatsApp web failing on Ubuntu Chromium due to modified User Agent string

[Juhani Numminen]

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

** This bug has been marked a duplicate of bug 1808853
   Buggy WhatsApp misdetects Chromium with Ubuntu's patched useragent

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

Title:
  WhatsApp web failing on Ubuntu Chromium due to modified  User Agent
  string

Status in chromium-browser package in Ubuntu:
  New

Bug description:
  Dear Maintainer,

  WhatsApp Web is not working out of the box on Chromium on Ubuntu. This is due 
to User Agent detection on WhatsApp side which block non supported browser. 
  The Ubuntu Chromium modify the User Agent string to insert Ubuntu Chromium 
instead of Chrome. 
  I can see the will of showing the presence of chromium on the web, however, 
it comes at the cost of frustrating user that might download regular Chrome 
since their website doens't seem to work on Chromium. 
  Would you consider not modifying the original User Agent of the Chromium 
release ?

  Best regards,

  Nicolas Badoux

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

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

[Desktop-packages] [Bug 1808853] Re: Buggy WhatsApp misdetects Chromium with Ubuntu's patched useragent

[Launchpad Bug Tracker]

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

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

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

Title:
  Buggy WhatsApp misdetects Chromium with Ubuntu's patched useragent

Status in chromium-browser package in Ubuntu:
  Confirmed

Bug description:
  Starting about a week ago, https://web.whatsapp.com stopped working
  with Ubuntu's Chromium, it suggests to install Google Chrome.

  If change useragent from
  userAgent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like 
Gecko) Ubuntu Chromium/70.0.3538.110 Chrome/70.0.3538.110 Safari/537.36
  to
  userAgent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like 
Gecko) Chrome/70.0.3538.110 Safari/537.36

  or rebuild chromium-browser without chromium_useragent.patch, than
  this piece of buggy shit starts to work with Chromium

  I tried to reach WhatsApp monkeys by writing to
  webclient_...@support.whatsapp.com, but did not get an answer from
  human.

  Sorry, but I hate WhatsApp.

  I've made this bug just to inform you about the problems that the
  patched useragent may cause and to help other people solve the
  problem.

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

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

[Desktop-packages] [Bug 1766107] Re: 'orientation-requested' and 'print-quality' has value '0'

[Andrea Bocci]

I have the same problem with Ubuntu 18.04, CUPS 2.2.7, printing on a
LaserJet Pro MFP M281fdw.

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

Title:
  'orientation-requested' and 'print-quality' has value '0'

Status in system-config-printer package in Ubuntu:
  New

Bug description:
  Hi,

  CUPS stopped working suddenly. So I opened the settings of my printer
  in the system-config-printer utility which welcomes me with two error
  messages.

  First dialog:
  > Option 'orientation-requested' has value '0' and cannot be edited.

  Second dialog:
  > Option 'print-quality' has value '0' and cannot be edited.

  After clicking OK two times Apport reported an error in
  > /usr/share/system-config-printer/system-config-printer.py

  because of
  > system-config-printer.py crashed with TypeError in __init__(): debugprint() 
takes 1 positional argument but 2 were given

  CupsErrorLog:
  > [cups-deviced] PID 19691 (gutenprint52+usb) stopped with status 1!
  > Unable to create "/etc/cups/subscriptions.conf.N": No such file or directory

  
  Any ideas to fix this?

  Regards,
  Atalanttore
  --- 
  ApportVersion: 2.20.7-0ubuntu3.8
  Architecture: amd64
  CupsErrorLog:
   E [21/Apr/2018:21:26:10 +0200] [cups-deviced] PID 19691 (gutenprint52+usb) 
stopped with status 1!
   E [22/Apr/2018:19:11:12 +0200] Unable to create 
"/etc/cups/subscriptions.conf.N": No such file or directory
  CurrentDesktop: Unity:Unity7:ubuntu
  DistroRelease: Ubuntu 17.10
  EcryptfsInUse: Yes
  Lpstat: device for Samsung_SCX_3400_Series_SEC001599E7B363_: 
ipp://SEC001599E7B363.local:631/ipp/printer
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 046d:c245 Logitech, Inc. G400 Optical Mouse
   Bus 001 Device 003: ID 8087:0a2b Intel Corp. 
   Bus 001 Device 002: ID 5986:055c Acer, Inc 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Notebook W65_W67RZ
  Package: system-config-printer 1.5.9+20170825-0ubuntu1
  PackageArchitecture: all
  Papersize: a4
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-38-generic 
root=UUID=462560f8-ccdb-4115-a3c9-46fce6a630d2 ro rw quiet splash 
acpi_os_name=Linux acpi_osi= acpi_backlight=vendor vt.handoff=7
  ProcVersionSignature: Ubuntu 4.13.0-38.43-generic 4.13.16
  Tags: third-party-packages artful
  Uname: Linux 4.13.0-38-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 05/27/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1.05.09
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: W65_W67RZ
  dmi.board.vendor: Notebook
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Notebook
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.05.09:bd05/27/2016:svnNotebook:pnW65_W67RZ:pvrNotApplicable:rvnNotebook:rnW65_W67RZ:rvrNotApplicable:cvnNotebook:ct10:cvrN/A:
  dmi.product.family: Not Applicable
  dmi.product.name: W65_W67RZ
  dmi.product.version: Not Applicable
  dmi.sys.vendor: Notebook

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/system-config-printer/+bug/1766107/+subscriptions

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

[Desktop-packages] [Bug 1804685] Please test proposed package

[Brian Murray]

Hello Dan, or anyone else affected,

Accepted nautilus into bionic-proposed. The package will build now and
be available at
https://launchpad.net/ubuntu/+source/nautilus/1:3.26.4-0~ubuntu18.04.3
in a few hours, and then in the -proposed repository.

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

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

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

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

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

Title:
  Icon View Captions display in the wrong positions

Status in nautilus package in Ubuntu:
  Fix Released
Status in nautilus source package in Bionic:
  Fix Committed
Status in nautilus source package in Cosmic:
  Fix Committed

Bug description:
  * Impact
  The nautilus view doesn't display the informations with the selected layout

  * Test case
  1. Change to 100% zoom
  2. Go to Preferences > Icon View Captions
  3. There are three captions: First, Second & Third

  When selecting details for those they should reflect in the right
  order

  * Regression potential
  The code change is only the order of the widget in the preference, check that 
the preferency/views tab is not buggy

  ---

  
  In the Preferences for Nautilus, under the Views tab, the user has the option 
to select information to appear in the "First", "Second", and "Third" position 
beneath icons.  However, in icon view,  whatever the user selects to appear in 
the "First" position will appear in the second location beneath the icon.  
Whatever the user selects to appear in the "Second" position will appear in the 
third, or bottom, position.  Whatever the user selects to appear in the "Third" 
position will appear in the first, or top, position.

  I'm on

  Ubuntu 18.04.1 LTS
  Nautilus 3.26.4-0~ubuntu18.04.2

  Thanks!

  Upstream bugs:
  https://gitlab.gnome.org/GNOME/nautilus/issues/343
  https://gitlab.gnome.org/GNOME/nautilus/issues/766

  Upstream Fix:
  
https://gitlab.gnome.org/GNOME/nautilus/commit/86080e646a81679761e09aee4071abf68a2dac3b

  Steps to reproduce:
  1. Change to 100% zoom
  2. Go to Preferences > Icon View Captions
  3. There are three captions: First, Second & Third
  I expect to see that the 1st caption is displayed just below the file/folder 
name, 2nd is below 1st and 3rd is below 2nd.

  Current behaviour:
  The order of the captions is mixed up.
  The current order is this:
  - File/Folder Name
  - Third caption
  - First caption
  - Second caption

  Expected behaviour:
  - File/Folder Name
  - First caption
  - Second caption
  - Third caption

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

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

[Desktop-packages] [Bug 1804685] Re: Icon View Captions display in the wrong positions

[Brian Murray]

Hello Dan, or anyone else affected,

Accepted nautilus into cosmic-proposed. The package will build now and
be available at
https://launchpad.net/ubuntu/+source/nautilus/1:3.26.4-0ubuntu7.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-cosmic to verification-done-cosmic. If it does not
fix the bug for you, please add a comment stating that, and change the
tag to verification-failed-cosmic. In either case, without details of
your testing we will not be able to proceed.

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

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

** Changed in: nautilus (Ubuntu Cosmic)
   Status: New => Fix Committed

** Tags added: verification-needed verification-needed-cosmic

** Changed in: nautilus (Ubuntu Bionic)
   Status: New => Fix Committed

** Tags added: verification-needed-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/1804685

Title:
  Icon View Captions display in the wrong positions

Status in nautilus package in Ubuntu:
  Fix Released
Status in nautilus source package in Bionic:
  Fix Committed
Status in nautilus source package in Cosmic:
  Fix Committed

Bug description:
  * Impact
  The nautilus view doesn't display the informations with the selected layout

  * Test case
  1. Change to 100% zoom
  2. Go to Preferences > Icon View Captions
  3. There are three captions: First, Second & Third

  When selecting details for those they should reflect in the right
  order

  * Regression potential
  The code change is only the order of the widget in the preference, check that 
the preferency/views tab is not buggy

  ---

  
  In the Preferences for Nautilus, under the Views tab, the user has the option 
to select information to appear in the "First", "Second", and "Third" position 
beneath icons.  However, in icon view,  whatever the user selects to appear in 
the "First" position will appear in the second location beneath the icon.  
Whatever the user selects to appear in the "Second" position will appear in the 
third, or bottom, position.  Whatever the user selects to appear in the "Third" 
position will appear in the first, or top, position.

  I'm on

  Ubuntu 18.04.1 LTS
  Nautilus 3.26.4-0~ubuntu18.04.2

  Thanks!

  Upstream bugs:
  https://gitlab.gnome.org/GNOME/nautilus/issues/343
  https://gitlab.gnome.org/GNOME/nautilus/issues/766

  Upstream Fix:
  
https://gitlab.gnome.org/GNOME/nautilus/commit/86080e646a81679761e09aee4071abf68a2dac3b

  Steps to reproduce:
  1. Change to 100% zoom
  2. Go to Preferences > Icon View Captions
  3. There are three captions: First, Second & Third
  I expect to see that the 1st caption is displayed just below the file/folder 
name, 2nd is below 1st and 3rd is below 2nd.

  Current behaviour:
  The order of the captions is mixed up.
  The current order is this:
  - File/Folder Name
  - Third caption
  - First caption
  - Second caption

  Expected behaviour:
  - File/Folder Name
  - First caption
  - Second caption
  - Third caption

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

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

[Desktop-packages] [Bug 1800179] Re: Search in recent files list only works with lowercase letters

[Brian Murray]

Hello Simon, or anyone else affected,

Accepted gedit into cosmic-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/gedit/3.30.2-0ubuntu0.18.10.2 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-cosmic to verification-done-cosmic. If it does not
fix the bug for you, please add a comment stating that, and change the
tag to verification-failed-cosmic. In either case, without details of
your testing we will not be able to proceed.

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

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

** Changed in: gedit (Ubuntu Cosmic)
   Status: New => Fix Committed

** Tags added: verification-needed verification-needed-cosmic

** Changed in: gedit (Ubuntu Bionic)
   Status: New => Fix Committed

** Tags added: verification-needed-bionic

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

Title:
  Search in recent files list only works with lowercase letters

Status in gedit package in Ubuntu:
  Fix Released
Status in gedit source package in Bionic:
  Fix Committed
Status in gedit source package in Cosmic:
  Fix Committed

Bug description:
  * Impact
  The document filter is case sensitive which is confusing/not convenient

  * Test case
  - Open a document with an Uppercase letter
  - close it
  - click on 'open' and type the name with an Uppercase

  -> it should list the document

  * Regression potential
  The code change is in the filtering code, just test that.

  

  When clicking “Open” and typing to search the recently opened files,
  any search involving uppercase letters fails to return any result,
  even if files with uppercase letters in their file names have recently
  been opened. Searching for the same file names, but using all-
  lowercase letters, does yield results (see attached screenshot). So it
  seems that gedit converts the recently used file names to lowercase
  before comparing to the search term, which is incorrect.

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

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

[Desktop-packages] [Bug 1800179] Please test proposed package

[Brian Murray]

Hello Simon, or anyone else affected,

Accepted gedit into bionic-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/gedit/3.28.1-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 for helping!

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

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

Title:
  Search in recent files list only works with lowercase letters

Status in gedit package in Ubuntu:
  Fix Released
Status in gedit source package in Bionic:
  Fix Committed
Status in gedit source package in Cosmic:
  Fix Committed

Bug description:
  * Impact
  The document filter is case sensitive which is confusing/not convenient

  * Test case
  - Open a document with an Uppercase letter
  - close it
  - click on 'open' and type the name with an Uppercase

  -> it should list the document

  * Regression potential
  The code change is in the filtering code, just test that.

  

  When clicking “Open” and typing to search the recently opened files,
  any search involving uppercase letters fails to return any result,
  even if files with uppercase letters in their file names have recently
  been opened. Searching for the same file names, but using all-
  lowercase letters, does yield results (see attached screenshot). So it
  seems that gedit converts the recently used file names to lowercase
  before comparing to the search term, which is incorrect.

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

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

[Desktop-packages] [Bug 1808075] Re: Backport Unicode/Emoji 11 updates

[Brian Murray]

Hello Jeremy, or anyone else affected,

Accepted pango1.0 into cosmic-proposed. The package will build now and
be available at
https://launchpad.net/ubuntu/+source/pango1.0/1.42.4-3ubuntu1 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-cosmic to verification-done-cosmic. If it does not
fix the bug for you, please add a comment stating that, and change the
tag to verification-failed-cosmic. In either case, without details of
your testing we will not be able to proceed.

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

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

** Changed in: pango1.0 (Ubuntu Cosmic)
   Status: In Progress => Fix Committed

** Tags added: verification-needed verification-needed-cosmic

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

Title:
  Backport Unicode/Emoji 11 updates

Status in pango1.0 package in Ubuntu:
  Fix Released
Status in pango1.0 source package in Cosmic:
  Fix Committed

Bug description:
  Impact
  ==
  Once a year, there is a new Unicode and Emoji release. 2018's release is 
Unicode 11.

  Ubuntu 18.04 LTS and 18.10 already include Google's color emoji font
  for Unicode 11 (LP: #1788256) but neither Ubuntu 18.10 nor 18.04 LTS
  are able to display the new combinations introduced in Unicode 11 such
  as red-haired people.

  Test Case
  =
  Copy and paste the red-hair man ‍聆 into gedit. It should show as a single 
character.

  Regression Potential
  
  Although the code was written several weeks ago, it was only released in 
pango 1.43 (a development release) today so it's not seen many users yet.

  On the other hand, pango does have a test suite run during the build
  and as autopkgtest and those tests still pass. I haven't seen any
  issues yet and we'll work to fix any issues that do develop.

  A significant portion of the change set comes from the Unicode data
  sets and from the Chromium Unicode/Emoji parser. Both of those parts
  have received wider testing and use over several months.

  Other Info
  ==
  This issue is easy to fix with Ubuntu 18.10 but it may not be practical to 
try to update Ubuntu 18.04 LTS for this feature.

  GTK's "Insert Emoji" feature will need to be updated to offer these
  new emoji.

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

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

[Desktop-packages] [Bug 1693235] Re: Caps Lock Light not turning up during 16.04 LTS install

[David W. Mann]

I am also having this issue:

During an ISO install of Ubuntu, the CAPS LOCK indicator becomes
disabled (although CAPS LOCK itself is still working). The CAPS LOCK
indicator works as expected just prior to and immediately after the ISO
install.  The CAPS LOCK indicator works during an ISO install in ubuntu
12.04, but does not work in ubuntu 14.05, 16.04, 18.04.

Would this be an xorg-server issue or an issue with kernel settings for
the default keyboard?

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

Title:
  Caps Lock Light not turning up during 16.04 LTS install

Status in xorg-server package in Ubuntu:
  Confirmed

Bug description:
  when installing ubuntu 16.04 LTS server after the graphical select what to 
install screen the caps lock key does not toggle the caps lock light on the 
keyboard when pressed but it does toggle caps lock.
  in ubuntu 12.04 the caps lock light worked as expected during install.

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

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

[Desktop-packages] [Bug 1693235] Re: Caps Lock Light not turning up during 16.04 LTS install

[Launchpad Bug Tracker]

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

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

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

Title:
  Caps Lock Light not turning up during 16.04 LTS install

Status in xorg-server package in Ubuntu:
  Confirmed

Bug description:
  when installing ubuntu 16.04 LTS server after the graphical select what to 
install screen the caps lock key does not toggle the caps lock light on the 
keyboard when pressed but it does toggle caps lock.
  in ubuntu 12.04 the caps lock light worked as expected during install.

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

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

[Desktop-packages] [Bug 1807127] Re: Fixing bug #1795668 breaks thumbnail creation on 32-bit Ubuntu

[Brian Murray]

Hello Eugene, or anyone else affected,

Accepted gnome-desktop3 into cosmic-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/gnome-
desktop3/3.30.2-0ubuntu1 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-cosmic to verification-done-cosmic. If it does not
fix the bug for you, please add a comment stating that, and change the
tag to verification-failed-cosmic. In either case, without details of
your testing we will not be able to proceed.

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

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

** Changed in: gnome-desktop3 (Ubuntu Cosmic)
   Status: In Progress => Fix Committed

** Tags added: verification-needed verification-needed-cosmic

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

Title:
  Fixing bug #1795668 breaks thumbnail creation on 32-bit Ubuntu

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

Bug description:
  Impact
  ==
  Thumbnailing doesn't work on Ubuntu 18.04 LTS or 18.10 on 32-bit installs.

  Test Case
  =
  Install Ubuntu 18.10 32-bit
  Install the update. Log out and log back in.
  Download a picture from the internet.
  Open your file browser to the directory that contains the picture. The file 
should show a thumbnail preview.

  Regression Potential
  
  This fix was cherry-picked to the stable gnome-3-30 branch.
  It was additionally tested by Iain Lane on usrmerged and non-usrmerged 
systems. (We don't support usrmerge for Ubuntu 18.04 LTS or 18.10.)

  Other Info
  ==
  Triaged as Critical for 18.04 LTS since this was a regression introduced in 
the security update that backported the bubblewrap hardening to the 
gnome-desktop3 thumbnailer.

  Original Bug Report
  ===
  Fixing bug #1795668 breaks thumbnail creation on 32-bit Ubuntu.

  Looks like same issue in upstream -
  https://bugzilla.redhat.com/show_bug.cgi?id=1651952

  Cause - bubblewrap runs with --ro-bind /lib64 option, then fails.
  Workaround - create empty /lib64 directory at root.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: libgnome-desktop-3-17 3.28.2-0ubuntu1.1
  ProcVersionSignature: Ubuntu 4.15.0-42.45-generic 4.15.18
  Uname: Linux 4.15.0-42-generic i686
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: i386
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Dec  6 12:07:28 2018
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-desktop3
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1809013] Re: WhatsApp web failing on Ubuntu Chromium due to modified User Agent string

[Nicolas Badoux]

More info -> https://groups.google.com/a/chromium.org/forum/#!topic
/chromium-discuss/MbfH-OZGbLc

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

Title:
  WhatsApp web failing on Ubuntu Chromium due to modified  User Agent
  string

Status in chromium-browser package in Ubuntu:
  New

Bug description:
  Dear Maintainer,

  WhatsApp Web is not working out of the box on Chromium on Ubuntu. This is due 
to User Agent detection on WhatsApp side which block non supported browser. 
  The Ubuntu Chromium modify the User Agent string to insert Ubuntu Chromium 
instead of Chrome. 
  I can see the will of showing the presence of chromium on the web, however, 
it comes at the cost of frustrating user that might download regular Chrome 
since their website doens't seem to work on Chromium. 
  Would you consider not modifying the original User Agent of the Chromium 
release ?

  Best regards,

  Nicolas Badoux

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

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

[Desktop-packages] [Bug 1807983] Re: Update gnome-desktop3 to 3.30.2

[Brian Murray]

Hello Jeremy, or anyone else affected,

Accepted gnome-desktop3 into cosmic-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/gnome-
desktop3/3.30.2-0ubuntu1 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-cosmic to verification-done-cosmic. If it does not
fix the bug for you, please add a comment stating that, and change the
tag to verification-failed-cosmic. In either case, without details of
your testing we will not be able to proceed.

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

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

** Changed in: gnome-desktop3 (Ubuntu Cosmic)
   Status: In Progress => Fix Committed

** Tags added: verification-needed verification-needed-cosmic

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

Title:
  Update gnome-desktop3 to 3.30.2

Status in gnome-desktop3 package in Ubuntu:
  Fix Released
Status in gnome-desktop3 source package in Cosmic:
  Fix Committed

Bug description:
  Impact
  ==
  This updates the GNOME version number reported in Settings > Details > About 
to 3.30.2

  This is the final scheduled point release for GNOME 3.30.

  I'm also cherry-picking a potential crash bug fix from the gnome-3-30
  branch since there might not be another 3.30 release tarball.

  This also includes the fix for LP: #1807127

  Test Case
  =
  From Ubuntu 18.10, open the Settings app.
  Navigate to Details > About
  The GNOME version number should say 3.30.2

  Regression Potential
  
  There is a micro-release exception for GNOME:
  https://wiki.ubuntu.com/StableReleaseUpdates#GNOME

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

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

[Desktop-packages] [Bug 1809013] [NEW] WhatsApp web failing on Ubuntu Chromium due to modified User Agent string

[Nicolas Badoux]

Public bug reported:

Dear Maintainer,

WhatsApp Web is not working out of the box on Chromium on Ubuntu. This is due 
to User Agent detection on WhatsApp side which block non supported browser. 
The Ubuntu Chromium modify the User Agent string to insert Ubuntu Chromium 
instead of Chrome. 
I can see the will of showing the presence of chromium on the web, however, it 
comes at the cost of frustrating user that might download regular Chrome since 
their website doens't seem to work on Chromium. 
Would you consider not modifying the original User Agent of the Chromium 
release ?

Best regards,

Nicolas Badoux

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

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

Title:
  WhatsApp web failing on Ubuntu Chromium due to modified  User Agent
  string

Status in chromium-browser package in Ubuntu:
  New

Bug description:
  Dear Maintainer,

  WhatsApp Web is not working out of the box on Chromium on Ubuntu. This is due 
to User Agent detection on WhatsApp side which block non supported browser. 
  The Ubuntu Chromium modify the User Agent string to insert Ubuntu Chromium 
instead of Chrome. 
  I can see the will of showing the presence of chromium on the web, however, 
it comes at the cost of frustrating user that might download regular Chrome 
since their website doens't seem to work on Chromium. 
  Would you consider not modifying the original User Agent of the Chromium 
release ?

  Best regards,

  Nicolas Badoux

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

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

[Desktop-packages] [Bug 1809011] [NEW] package cups 2.2.7-1ubuntu2.1 failed to install/upgrade: read error in '/var/lib/dpkg/info/cups.triggers': Input/output error

[Alberto José Marrufo García]

Public bug reported:

Mientrasactualizaba el sistema recien instalado

ProblemType: Package
DistroRelease: Ubuntu 18.04
Package: cups 2.2.7-1ubuntu2.1
ProcVersionSignature: Ubuntu 4.15.0-42.45-generic 4.15.18
Uname: Linux 4.15.0-42-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.2
Architecture: amd64
Date: Tue Dec 18 17:50:57 2018
DuplicateSignature:
 package:cups:2.2.7-1ubuntu2.1
 Preparing to unpack .../074-cups_2.2.7-1ubuntu2.2_amd64.deb ...
 dpkg: error processing archive 
/tmp/apt-dpkg-install-0IVoPc/074-cups_2.2.7-1ubuntu2.2_amd64.deb (--unpack):
  read error in '/var/lib/dpkg/info/cups.triggers': Input/output error
ErrorMessage: read error in '/var/lib/dpkg/info/cups.triggers': Input/output 
error
Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: No 
destinations added.
MachineType: Packard Bell EasyNote TS44HR
Papersize: a4
ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-4.15.0-42-generic 
root=UUID=f9b48e7f-1e8e-46a2-b720-967fe70d5dde ro quiet splash vt.handoff=1
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-42-generic 
root=UUID=f9b48e7f-1e8e-46a2-b720-967fe70d5dde ro quiet splash vt.handoff=1
Python3Details: /usr/bin/python3.6, Python 3.6.7, python3-minimal, 
3.6.5-3ubuntu1
PythonDetails: N/A
RelatedPackageVersions:
 dpkg 1.19.0.5ubuntu2.1
 apt  1.6.6
SourcePackage: cups
Title: package cups 2.2.7-1ubuntu2.1 failed to install/upgrade: read error in 
'/var/lib/dpkg/info/cups.triggers': Input/output error
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 05/24/2011
dmi.bios.vendor: Packard Bell
dmi.bios.version: V1.11
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: SJV50_HR
dmi.board.vendor: Packard Bell
dmi.board.version: Base Board Version
dmi.chassis.type: 10
dmi.chassis.vendor: Packard Bell
dmi.chassis.version: V1.11
dmi.modalias: 
dmi:bvnPackardBell:bvrV1.11:bd05/24/2011:svnPackardBell:pnEasyNoteTS44HR:pvrV1.11:rvnPackardBell:rnSJV50_HR:rvrBaseBoardVersion:cvnPackardBell:ct10:cvrV1.11:
dmi.product.name: EasyNote TS44HR
dmi.product.version: V1.11
dmi.sys.vendor: Packard Bell

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


** Tags: amd64 apport-package bionic need-duplicate-check

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

Title:
  package cups 2.2.7-1ubuntu2.1 failed to install/upgrade: read error in
  '/var/lib/dpkg/info/cups.triggers': Input/output error

Status in cups package in Ubuntu:
  New

Bug description:
  Mientrasactualizaba el sistema recien instalado

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: cups 2.2.7-1ubuntu2.1
  ProcVersionSignature: Ubuntu 4.15.0-42.45-generic 4.15.18
  Uname: Linux 4.15.0-42-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  Date: Tue Dec 18 17:50:57 2018
  DuplicateSignature:
   package:cups:2.2.7-1ubuntu2.1
   Preparing to unpack .../074-cups_2.2.7-1ubuntu2.2_amd64.deb ...
   dpkg: error processing archive 
/tmp/apt-dpkg-install-0IVoPc/074-cups_2.2.7-1ubuntu2.2_amd64.deb (--unpack):
read error in '/var/lib/dpkg/info/cups.triggers': Input/output error
  ErrorMessage: read error in '/var/lib/dpkg/info/cups.triggers': Input/output 
error
  Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: No 
destinations added.
  MachineType: Packard Bell EasyNote TS44HR
  Papersize: a4
  ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-4.15.0-42-generic 
root=UUID=f9b48e7f-1e8e-46a2-b720-967fe70d5dde ro quiet splash vt.handoff=1
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-42-generic 
root=UUID=f9b48e7f-1e8e-46a2-b720-967fe70d5dde ro quiet splash vt.handoff=1
  Python3Details: /usr/bin/python3.6, Python 3.6.7, python3-minimal, 
3.6.5-3ubuntu1
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu2.1
   apt  1.6.6
  SourcePackage: cups
  Title: package cups 2.2.7-1ubuntu2.1 failed to install/upgrade: read error in 
'/var/lib/dpkg/info/cups.triggers': Input/output error
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/24/2011
  dmi.bios.vendor: Packard Bell
  dmi.bios.version: V1.11
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: SJV50_HR
  dmi.board.vendor: Packard Bell
  dmi.board.version: Base Board Version
  dmi.chassis.type: 10
  dmi.chassis.vendor: Packard Bell
  dmi.chassis.version: V1.11
  dmi.modalias: 
dmi:bvnPackardBell:bvrV1.11:bd05/24/2011:svnPackardBell:pnEasyNoteTS44HR:pvrV1.11:rvnPackardBell:rnSJV50_HR:rvrBaseBoardVersion:cvnPackardBell:ct10:cvrV1.11:
  dmi.product.name: EasyNote TS44HR
  dmi.product.version: V1.11
  dmi.sys.vendor: Packard Bell

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

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

[Desktop-packages] [Bug 1796648] Re: network-manager-openvpn leaks DNS information on Ubuntu 18.04

[Sebastien Bacher]

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

** This bug has been marked a duplicate of bug 1754671
   Full-tunnel VPN DNS leakage regression

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

Title:
  network-manager-openvpn leaks DNS information on Ubuntu 18.04

Status in network-manager-openvpn package in Ubuntu:
  Confirmed

Bug description:
  By default when adding a VPN configuration on Ubuntu 18.04 the DNS
  configuration supplied by DHCP is not used, resulting in DNS leakage.

  How to reproduce:

  * Add VPN configuration, for example, import a ovpn file
  * activate
  * Check for DNS leakage at for example https://www.dnsleaktest.com/

  This has been reported at various locations:

  https://github.com/systemd/systemd/issues/7182
  https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1690860
  https://github.com/eduvpn/python-eduvpn-client/issues/160

  The issue has been solved since network-manage-open version 1.12.0:

  https://gitlab.gnome.org/GNOME/NetworkManager-openvpn/issues/10

  This version or a more recent version is part of Ubuntu 18.10 which
  doesn't have this issue.

  A workaround is to run:

  $ systemd-resolve -i tun2 --set-domain=~.

  where tun2 is your VPN interface.

  We think this is a security issue and at least a backport of network-
  manage-open > 1.12.0 should be uploaded to the archive.

  greetings,

   - Gijs

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: network-manager 1.10.6-2ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18
  Uname: Linux 4.15.0-36-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7.4
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Oct  8 11:19:00 2018
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2018-06-06 (123 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  IpRoute:
   default via 192.168.178.1 dev enp6s0 proto dhcp metric 100 
   169.254.0.0/16 dev virbr0 scope link metric 1000 linkdown 
   172.17.0.0/16 dev docker0 proto kernel scope link src 172.17.0.1 linkdown 
   192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1 
linkdown 
   192.168.178.0/24 dev enp6s0 proto kernel scope link src 192.168.178.61 
metric 100
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  RfKill:
   
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.10.6   connected  started  full  enabled enabled  
enabled  enabled  enabled

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

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

[Desktop-packages] [Bug 942856] Re: NetworkManager does not support AES-encrypted private keys for WPA 802.1x authentication

[Sebastien Bacher]

Those keys are handled since 1.10.10 and Ubuntu 18.10
https://gitlab.freedesktop.org/NetworkManager/NetworkManager/commit/9b46af1a

That update is being SRUed to bionic

** Changed in: network-manager (Ubuntu)
   Status: Confirmed => Fix Released

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

Title:
  NetworkManager does not support AES-encrypted private keys for WPA
  802.1x authentication

Status in NetworkManager:
  Confirmed
Status in network-manager package in Ubuntu:
  Fix Released

Bug description:
  NetworkManager does not appear to support private keys encrypted with
  AES.  At the very least, it will not validate such a key in nm-util
  when setting up a WPA 802.1x TLS wifi connection.

  To test:

  1. Start with a working (cleartext or DES-3) private key/cert for a network.  
Set up a connection and verify that everything works.
  2. Re-encrypt the key with AES-256 with this command: "openssl rsa -in 
working-key.pem -out aes-key.pem -aes256" (the output should have a line 
starting with "DEK-Info: AES-256-CBC,")
  3. Delete the settings for the test network and attempt to reconnect using 
the new key.  Even with the correct passphrase, the "Connect" button will 
remain disabled; debugging will determine that nm-util is failing to validate 
the private key.

To manage notifications about this bug go to:
https://bugs.launchpad.net/network-manager/+bug/942856/+subscriptions

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

[Desktop-packages] [Bug 1317552] Re: usb modem doesn't recognized by system until wired network connected

[Sebastien Bacher]

Thank you for your bug report. There has been no activity nor new report
in a few years, could you try if that's still an issue using newer
ubuntu versions?

** Changed in: network-manager (Ubuntu)
   Importance: Undecided => Low

** Changed in: network-manager (Ubuntu)
   Status: Confirmed => Incomplete

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

Title:
  usb modem doesn't recognized by system until wired network connected

Status in network-manager package in Ubuntu:
  Incomplete

Bug description:
  I have an usb 3g modem huawei, configured as standalone network
  device. When I connect it, dmesg shows some error messages, but
  nothing happens. After connect and futher disconnect wired network
  (eth0), it succesful recognized by the system as eth1 device and all
  works fine. Problem is that sometimes I have no wired network to start
  usb-3g connection this way.

  Part of dmesg with connect/disconnect manipulations

  [   27.606224] init: libvirt-bin main process (979) terminated with status 127
  [   27.606239] init: libvirt-bin main process ended, respawning
  [   27.915799] r8169 :01:00.0 eth0: link down
  [   27.915869] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
  [   27.916229] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
  [   27.938186] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
  [   27.941688] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
  [   28.566084] usb 1-1.1: New USB device found, idVendor=0cf3, idProduct=0036
  [   28.566089] usb 1-1.1: New USB device strings: Mfr=0, Product=0, 
SerialNumber=0
  [   28.775155] init: plymouth-upstart-bridge main process ended, respawning
  [   34.989561] FAT-fs (sdb1): Volume was not properly unmounted. Some data 
may be corrupt. Please run fsck.
  [   55.380263] usb 3-3: new high-speed USB device number 3 using xhci_hcd
  [   55.397190] usb 3-3: New USB device found, idVendor=12d1, idProduct=1f01
  [   55.397202] usb 3-3: New USB device strings: Mfr=2, Product=1, 
SerialNumber=0
  [   55.397207] usb 3-3: Product: HUAWEI HiLink
  [   55.397212] usb 3-3: Manufacturer: HUAWEI
  [   55.465739] usb-storage 3-3:1.0: USB Mass Storage device detected
  [   55.465795] scsi7 : usb-storage 3-3:1.0
  [   55.465865] usbcore: registered new interface driver usb-storage
  [   56.464794] scsi 7:0:0:0: CD-ROMHUAWEI   Mass Storage 2.31 
PQ: 0 ANSI: 2
  [   56.472835] sr1: scsi-1 drive
  [   56.472989] sr 7:0:0:0: Attached scsi CD-ROM sr1
  [   56.473080] sr 7:0:0:0: Attached scsi generic sg3 type 5
  [   56.558838] audit_printk_skb: 156 callbacks suppressed
  [   56.558842] type=1400 audit(1399561168.962:64): apparmor="STATUS" 
operation="profile_replace" profile="unconfined" 
name="/usr/lib/cups/backend/cups-pdf" pid=2017 comm="apparmor_parser"
  [   56.558850] type=1400 audit(1399561168.962:65): apparmor="STATUS" 
operation="profile_replace" profile="unconfined" name="/usr/sbin/cupsd" 
pid=2017 comm="apparmor_parser"
  [   56.559369] type=1400 audit(1399561168.962:66): apparmor="STATUS" 
operation="profile_replace" profile="unconfined" name="/usr/sbin/cupsd" 
pid=2017 comm="apparmor_parser"
  [   56.638660] Buffer I/O error on device sr1, logical block 0
  [   56.638668] Buffer I/O error on device sr1, logical block 0
  [   56.638685] Buffer I/O error on device sr1, logical block 0
  [   56.638693] Buffer I/O error on device sr1, logical block 0
  [   56.638701] Buffer I/O error on device sr1, logical block 1
  [   56.638708] Buffer I/O error on device sr1, logical block 1
  [   56.638716] Buffer I/O error on device sr1, logical block 512
  [   56.640490] systemd-udevd[2001]: Failed to apply ACL on /dev/sr1: No such 
file or directory
  [   56.640501] systemd-udevd[2001]: Failed to apply ACL on /dev/sr1: No such 
file or directory
  [   56.651401] systemd-udevd[1987]: Failed to apply ACL on /dev/sr1: No such 
file or directory
  [   56.651427] systemd-udevd[1987]: Failed to apply ACL on /dev/sr1: No such 
file or directory
  [  107.810564] usb 3-3: USB disconnect, device number 3
  [  116.952712] usb 3-3: new high-speed USB device number 4 using xhci_hcd
  [  116.969698] usb 3-3: New USB device found, idVendor=12d1, idProduct=1f01
  [  116.969709] usb 3-3: New USB device strings: Mfr=2, Product=1, 
SerialNumber=0
  [  116.969715] usb 3-3: Product: HUAWEI HiLink
  [  116.969720] usb 3-3: Manufacturer: HUAWEI
  [  116.971391] usb-storage 3-3:1.0: USB Mass Storage device detected
  [  116.971653] scsi8 : usb-storage 3-3:1.0
  [  117.969336] scsi 8:0:0:0: CD-ROMHUAWEI   Mass Storage 2.31 
PQ: 0 ANSI: 2
  [  117.971006] sr1: scsi-1 drive
  [  117.971389] sr 8:0:0:0: Attached scsi CD-ROM sr1
  [  117.974632] sr 8:0:0:0: Attached scsi generic sg3 type 5
  [  118.063825] quiet_error: 1 callbacks suppressed
  [  118.063836] Buffer I/O error on device sr1, logical block 9
  [  

[Desktop-packages] [Bug 1688265] Re: Wifi disconnects when screen is locked

[Sebastien Bacher]

Thank you for your bug report. What desktop environment are you using?
Is it still an issue in newer Ubuntu series?

** Changed in: network-manager (Ubuntu)
   Importance: Undecided => Low

** Changed in: network-manager (Ubuntu)
   Status: New => Incomplete

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

Title:
  Wifi disconnects when screen is locked

Status in network-manager package in Ubuntu:
  Incomplete

Bug description:
  Ubuntu: 17.04
  Wifi Chipset: Intel 7260 rev bb
  Driver: iwlwifi 4.10.0-19-generic

  If I lock my screen overnight, the following morning my Wifi will be
  disconnected and is slow to reconnect and often requires multiple
  connection attempts. Locking my screen for a short period of time
  (minutes or hours) doesn't trigger the behavior.

  Dmesg:

  
  ```
  [1256404.227085] wlp5s0: authenticate with 00:25:9c:xx:xx:xx
  [1256404.229298] wlp5s0: send auth to 00:25:9c:xx:xx:xx (try 1/3)
  [1256404.230281] wlp5s0: authenticated
  [1256404.843347] wlp5s0: Connection to AP 00:25:9c:xx:xx:xx lost
  [1256409.234035] wlp5s0: aborting authentication with 00:25:9c:xx:xx:xx by 
local choice (Reason: 3=DEAUTH_LEAVING)
  [1256413.045691] wlp5s0: authenticate with 00:25:9c:xx:xx:xx
  [1256413.047962] wlp5s0: send auth to 00:25:9c:xx:xx:xx (try 1/3)
  [1256413.048999] wlp5s0: authenticated
  [1256413.661996] wlp5s0: Connection to AP 00:25:9c:xx:xx:xx lost
  [1256418.051499] wlp5s0: aborting authentication with 00:25:9c:xx:xx:xx by 
local choice (Reason: 3=DEAUTH_LEAVING)
  [1256422.361848] wlp5s0: authenticate with 00:25:9c:xx:xx:xx
  [1256422.364062] wlp5s0: send auth to 00:25:9c:xx:xx:xx (try 1/3)
  [1256422.365122] wlp5s0: authenticated
  [1256422.978086] wlp5s0: Connection to AP 00:25:9c:xx:xx:xx lost
  [1256426.516541] wlp5s0: aborting authentication with 00:25:9c:xx:xx:xx by 
local choice (Reason: 3=DEAUTH_LEAVING)
  [1256426.518958] IPv6: ADDRCONF(NETDEV_UP): wlp5s0: link is not ready
  [1256426.524074] IPv6: ADDRCONF(NETDEV_UP): wlp5s0: link is not ready
  [1256426.544019] IPv6: ADDRCONF(NETDEV_UP): wlp5s0: link is not ready
  [1256426.578930] wlp5s0: authenticate with 00:25:9c:xx:xx:xx
  [1256426.581309] wlp5s0: send auth to 00:25:9c:xx:xx:xx (try 1/3)
  [1256426.582424] wlp5s0: authenticated
  [1256426.582716] wlp5s0: associate with 00:25:9c:xx:xx:xx (try 1/3)
  [1256426.583584] wlp5s0: RX AssocResp from 00:25:9c:xx:xx:xx (capab=0x11 
status=0 aid=1)
  [1256426.584763] wlp5s0: associated
  [1256426.584867] IPv6: ADDRCONF(NETDEV_CHANGE): wlp5s0: link becomes ready
  [1256426.630815] bridge-wlp5s0: device is wireless, enabling SMAC
  [1256426.630817] bridge-wlp5s0: up
  [1256426.630823] bridge-wlp5s0: attached
  ```

  There are hundreds of lines like this. It looks like it gets into a
  loop where it disconnects every 5 seconds. Once I log in and reconnect
  using the applet in the menu bar, the connection is pretty reliable
  for hours -- I generally work a full day without wifi dropping.

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

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

[Desktop-packages] [Bug 1370953] Re: layout switch is delayed

[Max]

I'm experiencing same bug on elementary OS 5.0. It really driving me nuts.
Added initial bounty on this.
https://www.bountysource.com/issues/63898369-slow-keyboard-layouts-switch

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

Title:
  layout switch is delayed

Status in console-setup package in Ubuntu:
  Confirmed
Status in gconf package in Ubuntu:
  Confirmed

Bug description:
  I have two layouts configured En and Ru with Ctrl-Shift as layout
  switch combo.

  When I start typing in wrong layout I notice it, hit Ctrl-Shift and type 
again, but more often than not it is wrong layout again.
  I repeat the action, but there is no luck. On the third attemt it usually 
either works OR the first letter is still in wrong layout, but the second is in 
correct one - i.e. layout switches as I type.

  The explanation for this is that layout switch takes very unreasonable
  time - much longer than it is needed to move your fingers from  one
  key to the other. Each time I encounter the error I retry slower so on
  the third attempt it is slow enough to actually recognize that layout
  switch is happening, but with a delay.

  This is extremely annoying and unacceptable. If someone knows how to
  work around it - please post your suggestions here. It would be nice
  to have a solution for 3+ layouts setup as well.

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

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

[Desktop-packages] [Bug 1794478] Re: Automatic ipv4 not assigned to bond interface is manual ipv6 is assigned to it

[Sebastien Bacher]

The issue looks like it could be what is fixed by
https://gitlab.freedesktop.org/NetworkManager/NetworkManager/commit/34ca1680
(the change is included in 1.10.8 which is currently not yet in bionic
but being SRUed)

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

Title:
  Automatic ipv4 not assigned to bond interface is manual ipv6 is
  assigned to it

Status in Ubuntu on IBM z Systems:
  Incomplete
Status in network-manager package in Ubuntu:
  Incomplete

Bug description:
  ---Problem Description---
  Bond interface with automatic ipv4 mode and manual ipv6 mode fails to get 
automatic ipv4 assigned from dhcp server.
   
  ---uname output---
  Linux NetworkTest 4.15.0-33-generic #36-Ubuntu SMP Wed Aug 15 13:42:17 UTC 
2018 s390x s390x s390x GNU/Linux
   
  Machine Type = s390x 
   
  ---Debugger---
  A debugger is not configured
   
  ---Steps to Reproduce---
   When user configures ipv4 as automatic and ipv6 as manual for bond interface 
automatic ipv4 is not getting assigned.
  Looks like dhcp client request for ipv4 is not done to dhcp server after 
maunal ipv6 is assigned quickly to bond interface

  This issue will not happen in below cases:
  1)with ipv4 automatic and ipv6 manual configuration for ethernet or vlan 
interface.
  2)with ipv4 automatic and ipv6 automatic configuration for bond interface
  3)with ipv4 automatic and ipv6 disabled configuration for bond interface

  Configuration:
  Bond interface, ipv4 automatic mode and ipv6 automatic mode

  root@NetworkTest:/etc/NetworkManager/system-connections# cat test_bond 
  [connection]
  id=test_bond
  uuid=63e54542-5135-47ac-a954-b861c3937be2
  type=bond
  interface-name=test_bond
  permissions=
  timestamp=1537944121

  [ethernet]
  mac-address-blacklist=

  [bond]
  downdelay=0
  fail_over_mac=none
  miimon=100
  mode=active-backup
  num_grat_arp=0
  primary_reselect=always
  updelay=0

  [ipv4]
  dns-search=
  method=auto

  [ipv6]
  addr-gen-mode=stable-privacy
  dns-search=
  method=auto

  From /var/log/syslog, we can see ip got assigned:

  Sep 26 06:26:26 NetworkTest dhclient[8663]: DHCPDISCOVER on test_bond to 
255.255.255.255 port 67 interval 3 (xid=0x5e04bf1e)
  Sep 26 06:26:26 NetworkTest dhclient[8663]: DHCPREQUEST of 10.2.3.55 on 
test_bond to 255.255.255.255 port 67 (xid=0x5e04bf1e)
  Sep 26 06:26:26 NetworkTest dhclient[8663]: DHCPOFFER of 10.2.3.55 from 
10.2.3.1
  Sep 26 06:26:26 NetworkTest dhclient[8663]: DHCPACK of 10.2.3.55 from 10.2.3.1

  root@NetworkTest:/etc/NetworkManager/system-connections# ip a s test_bond
  28: test_bond:  mtu 1500 qdisc 
noqueue state UP group default qlen 1000
  link/ether 02:00:00:b3:b5:22 brd ff:ff:ff:ff:ff:ff
  inet 10.2.3.55/24 brd 10.2.3.255 scope global dynamic noprefixroute 
test_bond
 valid_lft 353sec preferred_lft 353sec
  inet6 fe80::ff:feb3:b522/64 scope link 
 valid_lft forever preferred_lft forever

  
  
+++
  Bond interface, ipv4 automatic mode and ipv6 manual mode

  root@NetworkTest:/etc/NetworkManager/system-connections# cat test_bond 
  [connection]
  id=test_bond
  uuid=3efb153a-a6e4-48fb-aa04-f0b8cb549bab
  type=bond
  interface-name=test_bond
  permissions=
  timestamp=1537943300

  [ethernet]
  mac-address-blacklist=

  [bond]
  downdelay=0
  fail_over_mac=none
  miimon=100
  mode=active-backup
  num_grat_arp=0
  primary_reselect=always
  updelay=0

  [ipv4]
  dns-search=
  method=auto

  [ipv6]
  addr-gen-mode=stable-privacy
  address1=fe81::32a5:bc5f:287f:8db8/64
  dns-search=
  method=manual

  No automatic ip assigned to ipv4 and no requests to dhcp server seen in 
/var/log/syslog
  root@NetworkTest:/etc/NetworkManager/system-connections# ip a s test_bond
  29: test_bond:  mtu 1500 qdisc 
noqueue state UP group default qlen 1000
  link/ether 02:00:00:b3:b5:22 brd ff:ff:ff:ff:ff:ff
  inet6 fe81::32a5:bc5f:287f:8db8/64 scope link noprefixroute 
 valid_lft forever preferred_lft forever

  
  ==> Correct LP-Package need to be assigned...!

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1794478/+subscriptions

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

[Desktop-packages] [Bug 1790098] Re: vlan created on bond fails auto activation on updating parent network bond

[Sebastien Bacher]

The issue looks like it could be what is fixed by
https://gitlab.freedesktop.org/NetworkManager/NetworkManager/commit/34ca1680
(the change is included in 1.10.8 which is currently not yet in bionic
but being SRUed)

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

Title:
  vlan created on bond fails auto activation on updating parent network
  bond

Status in Ubuntu on IBM z Systems:
  Incomplete
Status in network-manager package in Ubuntu:
  Incomplete

Bug description:
  Auto activation of Vlan created over network-bond fails if bond is 
deactivated and reactivated.
   
  Contact Information = Abhiram Kulkarni(abhir...@in.ibm.com), Mandar 
Deshpande(manda...@in.ibm.com) 
   
  ---uname output---
  Linux S36MANDAR 4.15.0-20-generic #21-Ubuntu SMP Tue Apr 24 06:14:23 UTC 2018 
s390x s390x s390x GNU/Linux
   
  Machine Type = s390x 
   
  ---Debugger---
  A debugger is not configured
   
  ---Steps to Reproduce---
   1. Created a network bond with static IP address (and no IPv6 address); 
active backup mode; ARP polling; single slave.

  2. Created a VLAN using said network bond with static IPv4 address
  (and no IPv6 address).

  3. Can ping from the appliance to a target on both links (the parent
  bond and the VLAN).

  4. Switched to another slave for the created bond

  5. Can still ping from the appliance to a target via the parent bond;
  however, cannot ping to the target via the VLAN.

  =
  Detailed steps:

  1. Initial setup:
  
  root@S36MANDAR:~# nmcli c s
  NAMEUUID  TYPE  DEVICE  
  enc1a80 c3a2037d-60a3-3cb4-9234-45aed55f7093  ethernet  enc1a80 
  enc8f00 2423add6-1464-3765-877c-a214dc497492  ethernet  enc8f00 
  enc1d40 ff2d70f8-130e-3dc6-ab24-1dba07563605  ethernet  --  

  2. Create Netwrok-bond with one slave:
  
  root@S36MANDAR:~# nmcli c add type bond con-name mybond1 ifname mybond1 
ipv4.method disabled ipv6.method ignore
  Connection 'mybond1' (4b918a65-43a6-4ec3-b3c4-388ed52b116d) successfully 
added.

  root@S36MANDAR:~# nmcli con add type ethernet ifname enc1d40 master mybond1
  Connection 'bond-slave-enc1d40' (cfe4b245-3dda-4f45-b7b4-6d40d144a02f) 
successfully added.
  root@S36MANDAR:~# nmcli con up bond-slave-enc1d40
  Connection successfully activated (D-Bus active path: 
/org/freedesktop/NetworkManager/ActiveConnection/18)
  root@S36MANDAR:~# nmcli c s
  NAMEUUID  TYPE  DEVICE  
  bond-slave-enc1d40  cfe4b245-3dda-4f45-b7b4-6d40d144a02f  ethernet  enc1d40 
  enc1a80 c3a2037d-60a3-3cb4-9234-45aed55f7093  ethernet  enc1a80 
  enc8f00 2423add6-1464-3765-877c-a214dc497492  ethernet  enc8f00 
  mybond1 4b918a65-43a6-4ec3-b3c4-388ed52b116d  bond  mybond1 
  enc1d40 ff2d70f8-130e-3dc6-ab24-1dba07563605  ethernet  --  

  3. Create vlan over mybond1:
  ===
  root@S36MANDAR:~# nmcli con add type vlan con-name vlanbond.100 ifname 
vlanbond.100 dev mybond1 id 100  ipv4.method disabled ipv6.method ignore
  Connection 'vlanbond.100' (e054df42-97a0-492b-b2c9-b9571077493e) successfully 
added.
  root@S36MANDAR:~# nmcli c s
  NAMEUUID  TYPE  DEVICE
   
  bond-slave-enc1d40  cfe4b245-3dda-4f45-b7b4-6d40d144a02f  ethernet  enc1d40   
   
  enc1a80 c3a2037d-60a3-3cb4-9234-45aed55f7093  ethernet  enc1a80   
   
  enc8f00 2423add6-1464-3765-877c-a214dc497492  ethernet  enc8f00   
   
  mybond1 4b918a65-43a6-4ec3-b3c4-388ed52b116d  bond  mybond1   
   
  vlanbond.100e054df42-97a0-492b-b2c9-b9571077493e  vlan  
vlanbond.100 
  enc1d40 ff2d70f8-130e-3dc6-ab24-1dba07563605  ethernet  --
   

  4. Reactivate bond : 
  =
  root@S36MANDAR:~# nmcli con up mybond1
  Connection successfully activated (master waiting for slaves) (D-Bus active 
path: /org/freedesktop/NetworkManager/ActiveConnection/30)

  root@S36MANDAR:~# nmcli c s
  NAMEUUID  TYPE  DEVICE  
  enc1a80 c3a2037d-60a3-3cb4-9234-45aed55f7093  ethernet  enc1a80 
  enc1d40 ff2d70f8-130e-3dc6-ab24-1dba07563605  ethernet  enc1d40 
  enc8f00 2423add6-1464-3765-877c-a214dc497492  ethernet  enc8f00 
  mybond1 4b918a65-43a6-4ec3-b3c4-388ed52b116d  bond  mybond1 
  bond-slave-enc1d40  cfe4b245-3dda-4f45-b7b4-6d40d144a02f  ethernet  --  
  encw18104ddeb38e-d5f7-3814-abb7-be50b8da874e  ethernet  --  
  vlanbond.100e054df42-97a0-492b-b2c9-b9571077493e  vlan  --  

  As is seen, vlan(vlanbond.100) did not get activated

[Desktop-packages] [Bug 1797882] Re: At dual monitor intel_do_flush_locked failed: Resource deadlock avoided

[Gert van de Kraats]

Trace

** Attachment added: "trace at forced coredump"
   
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1797882/+attachment/5223254/+files/wayland_stacktrace.txt

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

Title:
  At dual monitor intel_do_flush_locked failed: Resource deadlock
  avoided

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

Bug description:
  Using ubuntu wayland with dual monitors, configured above each other.
  Dock is configured at both displays, not hiding.
  Icons for "terminal" and "libreofffice Writer" are present at the dock.

  Start terminal on primary screen by mouseclick on dock.
  Start libreoffice Writer on primary screen by mouseclick on dock.
  Terminate libreoffice Witer by mouseclick on X.
  Repeat the starting and stopping of Writer.

  Login-screen will appear. Syslog shows:
  Oct 15 00:09:51 Gert2 org.gnome.Shell.desktop[5892]: intel_do_flush_locked 
failed: Resource deadlock avoided
  Oct 15 00:09:51 Gert2 gnome-terminal-[6439]: Error reading events from 
display: Connection reset by peer
  Oct 15 00:09:51 Gert2 systemd[5755]: gnome-terminal-server.service: Main 
process exited, code=exited, status=1/FAILURE

  This problem doesnot occur in a dual monitor-session without wayland.
  It also doesnot occur, if only one monitor used with wayland
  It also doesnot occur, if the dock is only present at the primary screen.
  It also doesnot occur if second started application is present at the dock 
and doesnot add an icon to the dock (as libreoffice does).

  All other dual monitor/dock configurations seem to have this problem.

  No idea if this is helpful info, but the used graphics card does not support 
OpenGL version 2.1:
  Oct 15 00:02:32 Gert2 org.gnome.Shell.desktop[4426]: Require OpenGL version 
2.1 or later.
  Oct 15 00:02:32 Gert2 org.gnome.Shell.desktop[4426]: Failed to initialize 
glamor
  Oct 15 00:02:32 Gert2 org.gnome.Shell.desktop[4426]: Failed to initialize 
glamor, falling back to sw

  glxinfo:
  OpenGL vendor string: VMware, Inc.
  OpenGL renderer string: llvmpipe (LLVM 7.0, 128 bits)
  OpenGL core profile version string: 3.3 (Core Profile) Mesa 18.2.2
  OpenGL core profile shading language version string: 3.30
  OpenGL core profile context flags: (none)
  OpenGL core profile profile mask: core profile
  OpenGL core profile extensions:
  OpenGL version string: 3.1 Mesa 18.2.2
  OpenGL shading language version string: 1.40
  OpenGL context flags: (none)
  OpenGL extensions:
  OpenGL ES profile version string: OpenGL ES 3.0 Mesa 18.2.2
  OpenGL ES profile shading language version string: OpenGL ES GLSL ES 3.00
  OpenGL ES profile extensions:

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: gnome-shell 3.30.1-2ubuntu1
  ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12
  Uname: Linux 4.18.0-10-generic i686
  ApportVersion: 2.20.10-0ubuntu13
  Architecture: i386
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Oct 15 13:25:10 2018
  DisplayManager: gdm3
  GsettingsChanges:
   b'org.gnome.shell' b'command-history' redacted by apport
   b'org.gnome.shell' b'app-picker-view' b'uint32 1'
   b'org.gnome.shell' b'favorite-apps' redacted by apport
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
  ProcEnviron:
   LANGUAGE=en_US:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1797882] Re: At dual monitor intel_do_flush_locked failed: Resource deadlock avoided

[Gert van de Kraats]

Without solving this problem, wayland cannot be used after logon, when
using dual monitor. The sesssion stops very easy and often. Work is
lost; you have to logon again. E.g. the simple switching between 2
overlapping windows causes the end of the session.

I changed src/mesa/drivers/dri/i915/intel_batchbuffer.c to force a coredump in 
this case. The stacktrace is added to this bug-report.
Linenumbers might deviate a little bit because of extra coding of tracing.
The deadlock always occurs at cogl_onscreen_swap_buffers calling cogl_flush(), 
at the first journal-batch-flush for the offscreen-framebuffer.

The deadlock disappeared as soon as cogl is compiled with disabled batching!
To minimize this disabling of batching, I made a very dirty but working patch, 
which is attached to this bug.
At program clutter_stage_cogl_redraw_view  routine paint_stage is called for 
the "Unclipped stage paint".
This call is manipulated to flush immedately the first journal-entry of the 
default onscreen framebuffer.
This is done by misusing and changing program cogl_framebuffer_set_viewport and 
by changing _cogl_journal_flush.
Apparenly this early flushing causes a lock to be set which avoids the deadlock.

I do not know how to see which locks are held and by which process, so I
cannot solve the root-cause of thhe problem, but I assume some extra
lock must be set in this case to avoid deadlock.

With this dirty patch combined with other suggested (simple) patches at 
#1790525, #1795774 and #1795760 wayland can be run without any problems on dual 
monitor and "old" intel graphic card.
It performs better than lightdm, specially if the monitors are positioned aside 
of each other.


** Attachment added: "dirty_patch.txt"
   
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1797882/+attachment/5223253/+files/dirty_patch.txt

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

Title:
  At dual monitor intel_do_flush_locked failed: Resource deadlock
  avoided

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

Bug description:
  Using ubuntu wayland with dual monitors, configured above each other.
  Dock is configured at both displays, not hiding.
  Icons for "terminal" and "libreofffice Writer" are present at the dock.

  Start terminal on primary screen by mouseclick on dock.
  Start libreoffice Writer on primary screen by mouseclick on dock.
  Terminate libreoffice Witer by mouseclick on X.
  Repeat the starting and stopping of Writer.

  Login-screen will appear. Syslog shows:
  Oct 15 00:09:51 Gert2 org.gnome.Shell.desktop[5892]: intel_do_flush_locked 
failed: Resource deadlock avoided
  Oct 15 00:09:51 Gert2 gnome-terminal-[6439]: Error reading events from 
display: Connection reset by peer
  Oct 15 00:09:51 Gert2 systemd[5755]: gnome-terminal-server.service: Main 
process exited, code=exited, status=1/FAILURE

  This problem doesnot occur in a dual monitor-session without wayland.
  It also doesnot occur, if only one monitor used with wayland
  It also doesnot occur, if the dock is only present at the primary screen.
  It also doesnot occur if second started application is present at the dock 
and doesnot add an icon to the dock (as libreoffice does).

  All other dual monitor/dock configurations seem to have this problem.

  No idea if this is helpful info, but the used graphics card does not support 
OpenGL version 2.1:
  Oct 15 00:02:32 Gert2 org.gnome.Shell.desktop[4426]: Require OpenGL version 
2.1 or later.
  Oct 15 00:02:32 Gert2 org.gnome.Shell.desktop[4426]: Failed to initialize 
glamor
  Oct 15 00:02:32 Gert2 org.gnome.Shell.desktop[4426]: Failed to initialize 
glamor, falling back to sw

  glxinfo:
  OpenGL vendor string: VMware, Inc.
  OpenGL renderer string: llvmpipe (LLVM 7.0, 128 bits)
  OpenGL core profile version string: 3.3 (Core Profile) Mesa 18.2.2
  OpenGL core profile shading language version string: 3.30
  OpenGL core profile context flags: (none)
  OpenGL core profile profile mask: core profile
  OpenGL core profile extensions:
  OpenGL version string: 3.1 Mesa 18.2.2
  OpenGL shading language version string: 1.40
  OpenGL context flags: (none)
  OpenGL extensions:
  OpenGL ES profile version string: OpenGL ES 3.0 Mesa 18.2.2
  OpenGL ES profile shading language version string: OpenGL ES GLSL ES 3.00
  OpenGL ES profile extensions:

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: gnome-shell 3.30.1-2ubuntu1
  ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12
  Uname: Linux 4.18.0-10-generic i686
  ApportVersion: 2.20.10-0ubuntu13
  Architecture: i386
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Oct 15 13:25:10 2018
  DisplayManager: gdm3
  GsettingsChanges:
   b'org.gnome.shell' b'command-history' redacted by apport
   b'org.gnome.shell' b'app-picker-view' b'uint32 1'
   b'org.gnome.shell' b'favorite-apps' redacted by apport
   

[Desktop-packages] [Bug 1808147] Re: autopkgtests fail on s390x

[Brian Murray]

Hello Olivier, or anyone else affected,

Accepted libreoffice into cosmic-proposed. The package will build now
and be available at
https://launchpad.net/ubuntu/+source/libreoffice/1:6.1.3-0ubuntu0.18.10.2
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-cosmic to verification-done-cosmic. If it does not
fix the bug for you, please add a comment stating that, and change the
tag to verification-failed-cosmic. In either case, without details of
your testing we will not be able to proceed.

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

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

** Changed in: libreoffice (Ubuntu Cosmic)
   Status: New => Fix Committed

** Tags added: verification-needed verification-needed-cosmic

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

Title:
  autopkgtests fail on s390x

Status in libreoffice package in Ubuntu:
  Fix Released
Status in libreoffice source package in Cosmic:
  Fix Committed

Bug description:
  libreoffice autopkgtests on s390x started failing reliably on
  2018-12-11.

  This corresponds to when a new version of autopkgtest was deployed to
  the production infrastructure: https://lists.ubuntu.com/archives
  /ubuntu-devel/2018-December/040564.html

  The failing test is "smoketest". It has the "skippable" restriction,
  which was previously unknown, and as a result the test was skipped
  altogether. "skippable" is now a valid and understood restriction, so
  the test is being run, but it fails:

  […]
  mkdir -p 
/tmp/autopkgtest.A1jy64/build.urp/src/workdir/CustomTarget/i18npool/textconversion/
  S=/tmp/autopkgtest.A1jy64/build.urp/src && I=$S/instdir && W=$S/workdir &&  
touch $W/Headers/Library/libcollator_data.so
  S=/tmp/autopkgtest.A1jy64/build.urp/src && I=$S/instdir && W=$S/workdir &&  
touch $W/Headers/Library/libdict_ja.so
  S=/tmp/autopkgtest.A1jy64/build.urp/src && I=$S/instdir && W=$S/workdir &&  
touch $W/Headers/Library/libdict_zh.so
  S=/tmp/autopkgtest.A1jy64/build.urp/src && I=$S/instdir && W=$S/workdir &&  
touch $W/Headers/Library/libindex_data.so
  S=/tmp/autopkgtest.A1jy64/build.urp/src && I=$S/instdir && W=$S/workdir &&  
touch $W/Headers/Library/liblocaledata_en.so
  /tmp/autopkgtest.A1jy64/build.urp/src/solenv/gbuild/Package.mk:82: *** 
Something depends on package test_unittest which does not exist..  Stop.
  make[1]: *** Waiting for unfinished jobs
  S=/tmp/autopkgtest.A1jy64/build.urp/src && I=$S/instdir && W=$S/workdir &&  
touch $W/Headers/Library/libtextconv_dict.so
  [build PKG] test_unittest
  make[1]: Leaving directory '/tmp/autopkgtest.A1jy64/build.urp/src'
  make: *** [Makefile:112: i18npool.all] Error 2
  autopkgtest [13:27:33]: test smoketest: ---]
  autopkgtest [13:27:34]: test smoketest:  - - - - - - - - - - results - - - - 
- - - - - -
  smoketestFAIL non-zero exit status 1

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

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

[Desktop-packages] [Bug 1808147] Please test proposed package

[Brian Murray]

Hello Olivier, or anyone else affected,

Accepted libreoffice-l10n into cosmic-proposed. The package will build
now and be available at https://launchpad.net/ubuntu/+source
/libreoffice-l10n/1:6.1.3-0ubuntu0.18.10.2 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-cosmic to verification-done-cosmic. If it does not
fix the bug for you, please add a comment stating that, and change the
tag to verification-failed-cosmic. In either case, without details of
your testing we will not be able to proceed.

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

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

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

Title:
  autopkgtests fail on s390x

Status in libreoffice package in Ubuntu:
  Fix Released
Status in libreoffice source package in Cosmic:
  Fix Committed

Bug description:
  libreoffice autopkgtests on s390x started failing reliably on
  2018-12-11.

  This corresponds to when a new version of autopkgtest was deployed to
  the production infrastructure: https://lists.ubuntu.com/archives
  /ubuntu-devel/2018-December/040564.html

  The failing test is "smoketest". It has the "skippable" restriction,
  which was previously unknown, and as a result the test was skipped
  altogether. "skippable" is now a valid and understood restriction, so
  the test is being run, but it fails:

  […]
  mkdir -p 
/tmp/autopkgtest.A1jy64/build.urp/src/workdir/CustomTarget/i18npool/textconversion/
  S=/tmp/autopkgtest.A1jy64/build.urp/src && I=$S/instdir && W=$S/workdir &&  
touch $W/Headers/Library/libcollator_data.so
  S=/tmp/autopkgtest.A1jy64/build.urp/src && I=$S/instdir && W=$S/workdir &&  
touch $W/Headers/Library/libdict_ja.so
  S=/tmp/autopkgtest.A1jy64/build.urp/src && I=$S/instdir && W=$S/workdir &&  
touch $W/Headers/Library/libdict_zh.so
  S=/tmp/autopkgtest.A1jy64/build.urp/src && I=$S/instdir && W=$S/workdir &&  
touch $W/Headers/Library/libindex_data.so
  S=/tmp/autopkgtest.A1jy64/build.urp/src && I=$S/instdir && W=$S/workdir &&  
touch $W/Headers/Library/liblocaledata_en.so
  /tmp/autopkgtest.A1jy64/build.urp/src/solenv/gbuild/Package.mk:82: *** 
Something depends on package test_unittest which does not exist..  Stop.
  make[1]: *** Waiting for unfinished jobs
  S=/tmp/autopkgtest.A1jy64/build.urp/src && I=$S/instdir && W=$S/workdir &&  
touch $W/Headers/Library/libtextconv_dict.so
  [build PKG] test_unittest
  make[1]: Leaving directory '/tmp/autopkgtest.A1jy64/build.urp/src'
  make: *** [Makefile:112: i18npool.all] Error 2
  autopkgtest [13:27:33]: test smoketest: ---]
  autopkgtest [13:27:34]: test smoketest:  - - - - - - - - - - results - - - - 
- - - - - -
  smoketestFAIL non-zero exit status 1

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

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

[Desktop-packages] [Bug 1803142] Please test proposed package

[Brian Murray]

Hello Olivier, or anyone else affected,

Accepted libreoffice into cosmic-proposed. The package will build now
and be available at
https://launchpad.net/ubuntu/+source/libreoffice/1:6.1.3-0ubuntu0.18.10.2
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-cosmic to verification-done-cosmic. If it does not
fix the bug for you, please add a comment stating that, and change the
tag to verification-failed-cosmic. In either case, without details of
your testing we will not be able to proceed.

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

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

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

Title:
  [SRU] libreoffice 6.1.3 for cosmic

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

Bug description:
  [Impact]

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

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

  [Test Case]

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

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

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

  [Regression Potential]

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

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

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

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

[Desktop-packages] [Bug 1803142] Please test proposed package

[Brian Murray]

Hello Olivier, or anyone else affected,

Accepted libreoffice-l10n into cosmic-proposed. The package will build
now and be available at https://launchpad.net/ubuntu/+source
/libreoffice-l10n/1:6.1.3-0ubuntu0.18.10.2 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-cosmic to verification-done-cosmic. If it does not
fix the bug for you, please add a comment stating that, and change the
tag to verification-failed-cosmic. In either case, without details of
your testing we will not be able to proceed.

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

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

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

Title:
  [SRU] libreoffice 6.1.3 for cosmic

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

Bug description:
  [Impact]

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

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

  [Test Case]

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

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

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

  [Regression Potential]

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

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

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

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

[Desktop-packages] [Bug 66566]

[Gijskruitbosch+bugs]

(In reply to smmalis37 from comment #150)
> > What happened so shift+enter and ctrl+shift+enter?
> > Up to know shift+enter did .net and ctrl+shift+enter did .org.. now it does
> > open a new window or simply use .com.
> 
> I've been a Firefox user for years now. I use these keyboard shortcuts
> daily. net and org are still extremely common TLDs, even with others
> becoming more common. This change is annoying enough for me to seriously
> consider downgrading to 63. I ask the Firefox team to please consider
> reverting this change until there is a way for this functionality to be
> supported by an extension.

I don't see this happening. Consistency both with other browsers and
other shortcuts trumps the need for alternative domain autocompleting
(and really, without the other browsers it would probably have trumped
.com autocomplete, too).

I'm also really quite confused by the .net / .org case - do you turn off
autocomplete and/or history (in the location bar), or something? Why
can't you just hit "normal" enter when the domain you want gets
autocompleted? Do you just visit new .net/.org domains (where you
somehow do know the exact TLD you want, so you don't use a search
engine, but you have never visited before) every day? That seems like a
very niche usecase...

In terms of add-ons, it'd be pretty trivial to write an add-on that just
provided you a toolbar button that, when clicked (or activated via a new
shortcut of the add-on's choosing), provided an alternative input, where
you could type anything and it'd just suffix '.net' or '.org' and
navigate the current URL to it. I accept that's quite kludgy, but if you
really can't use autocomplete / history for this and are annoyed at
typing '.net' or '.org' after URLs, I think that might currently be your
best option.

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

Title:
  Inconsistent shortcuts for new tab

Status in Mozilla Firefox:
  Fix Released
Status in firefox package in Ubuntu:
  Won't Fix
Status in firefox-3.0 package in Ubuntu:
  Won't Fix
Status in firefox-3.5 package in Ubuntu:
  Won't Fix

Bug description:
  There are currently too many shortcuts when opening a link in a new
  tab:

   - location bar:  + 
   - GO button:  + click
   - search bar:  + 
   - SEARCH button  + click
   - links:  + click
   - menu bar:  + click
   - BACKWARD/FORWARD button:  + click

  This is one of the reasons I'm keeping with Opera. There it is always
  the shift key and I have to remember only one key.

  Thanks for reading!

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

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

[Desktop-packages] [Bug 66566]

[smmalis37]

> What happened so shift+enter and ctrl+shift+enter?
> Up to know shift+enter did .net and ctrl+shift+enter did .org.. now it does
> open a new window or simply use .com.

I've been a Firefox user for years now. I use these keyboard shortcuts
daily. net and org are still extremely common TLDs, even with others
becoming more common. This change is annoying enough for me to seriously
consider downgrading to 63. I ask the Firefox team to please consider
reverting this change until there is a way for this functionality to be
supported by an extension. I'll even write the extension myself, but
judging by https://bugzilla.mozilla.org/show_bug.cgi?id=1215061 such an
extension isn't possible yet.

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

Title:
  Inconsistent shortcuts for new tab

Status in Mozilla Firefox:
  Fix Released
Status in firefox package in Ubuntu:
  Won't Fix
Status in firefox-3.0 package in Ubuntu:
  Won't Fix
Status in firefox-3.5 package in Ubuntu:
  Won't Fix

Bug description:
  There are currently too many shortcuts when opening a link in a new
  tab:

   - location bar:  + 
   - GO button:  + click
   - search bar:  + 
   - SEARCH button  + click
   - links:  + click
   - menu bar:  + click
   - BACKWARD/FORWARD button:  + click

  This is one of the reasons I'm keeping with Opera. There it is always
  the shift key and I have to remember only one key.

  Thanks for reading!

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

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

[Desktop-packages] [Bug 1809002] [NEW] Enable privacy step for the Ubuntu wizard

[Sebastien Bacher]

Public bug reported:

Without enabling the location service some desktop features are not
working (automatic timezone change, color shift according to day time),
since the setting is not something most users known about it makes sense
to ask them if they want to enable it on first login.

** Affects: gnome-initial-setup (Ubuntu)
 Importance: Wishlist
 Assignee: Sebastien Bacher (seb128)
 Status: In Progress

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

** Changed in: gnome-initial-setup (Ubuntu)
   Status: New => In Progress

** Changed in: gnome-initial-setup (Ubuntu)
 Assignee: (unassigned) => Sebastien Bacher (seb128)

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

Title:
  Enable privacy step for the Ubuntu wizard

Status in gnome-initial-setup package in Ubuntu:
  In Progress

Bug description:
  Without enabling the location service some desktop features are not
  working (automatic timezone change, color shift according to day
  time), since the setting is not something most users known about it
  makes sense to ask them if they want to enable it on first login.

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

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

[Desktop-packages] [Bug 1768637] Re: /etc/modprobe.d is not a file

[Sebastien Bacher]

** Changed in: ubuntu-drivers-common (Ubuntu)
 Assignee: (unassigned) => Alberto Milone (albertomilone)

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

Title:
  /etc/modprobe.d is not a file

Status in ubuntu-drivers-common package in Ubuntu:
  Confirmed

Bug description:
  Hello, I noticed the following entries in my journal after upgrading
  to 18.04 LTS from 16.04 LTS:

  May 02 12:06:31 hunt gpu-manager[1112]: /etc/modprobe.d is not a file
  May 02 12:06:31 hunt gpu-manager[1112]: /etc/modprobe.d is not a file
  May 02 12:06:31 hunt gpu-manager[1112]: /etc/modprobe.d is not a file
  May 02 12:06:31 hunt gpu-manager[1112]: /etc/modprobe.d is not a file
  May 02 12:06:31 hunt gpu-manager[1112]: Error: can't open 
/lib/modules/4.15.0-20-generic/updates/dkms
  May 02 12:06:31 hunt audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 
ses=4294967295 msg='unit=gpu-manager comm="systemd" exe="/lib/systemd/systemd" 
hostname=? addr=? terminal=? res=success'
  May 02 12:06:31 hunt audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 
ses=4294967295 msg='unit=gpu-manager comm="systemd" exe="/lib/systemd/systemd" 
hostname=? addr=? terminal=? res=success'
  May 02 12:06:32 hunt gpu-manager[1170]: /etc/modprobe.d is not a file
  May 02 12:06:32 hunt gpu-manager[1170]: /etc/modprobe.d is not a file
  May 02 12:06:32 hunt gpu-manager[1170]: /etc/modprobe.d is not a file
  May 02 12:06:32 hunt gpu-manager[1170]: /etc/modprobe.d is not a file
  May 02 12:06:32 hunt gpu-manager[1170]: Error: can't open 
/lib/modules/4.15.0-20-generic/updates/dkms
  May 02 12:06:32 hunt audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 
ses=4294967295 msg='unit=gpu-manager comm="systemd" exe="/lib/systemd/systemd" 
hostname=? addr=? terminal=? res=success'
  May 02 12:06:32 hunt audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 
ses=4294967295 msg='unit=gpu-manager comm="systemd" exe="/lib/systemd/systemd" 
hostname=? addr=? terminal=? res=success'
  May 02 12:06:32 hunt gpu-manager[1254]: /etc/modprobe.d is not a file
  May 02 12:06:32 hunt gpu-manager[1254]: /etc/modprobe.d is not a file
  May 02 12:06:32 hunt gpu-manager[1254]: /etc/modprobe.d is not a file
  May 02 12:06:32 hunt gpu-manager[1254]: /etc/modprobe.d is not a file
  May 02 12:06:32 hunt gpu-manager[1254]: Error: can't open 
/lib/modules/4.15.0-20-generic/updates/dkms
  May 02 12:06:32 hunt audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 
ses=4294967295 msg='unit=gpu-manager comm="systemd" exe="/lib/systemd/systemd" 
hostname=? addr=? terminal=? res=success'
  May 02 12:06:32 hunt audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 
ses=4294967295 msg='unit=gpu-manager comm="systemd" exe="/lib/systemd/systemd" 
hostname=? addr=? terminal=? res=success'
  May 02 12:06:32 hunt gpu-manager[1316]: /etc/modprobe.d is not a file
  May 02 12:06:32 hunt gpu-manager[1316]: /etc/modprobe.d is not a file
  May 02 12:06:32 hunt gpu-manager[1316]: /etc/modprobe.d is not a file
  May 02 12:06:32 hunt gpu-manager[1316]: /etc/modprobe.d is not a file
  May 02 12:06:32 hunt gpu-manager[1316]: Error: can't open 
/lib/modules/4.15.0-20-generic/updates/dkms
  May 02 12:06:33 hunt audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 
ses=4294967295 msg='unit=gpu-manager comm="systemd" exe="/lib/systemd/systemd" 
hostname=? addr=? terminal=? res=success'
  May 02 12:06:33 hunt audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 
ses=4294967295 msg='unit=gpu-manager comm="systemd" exe="/lib/systemd/systemd" 
hostname=? addr=? terminal=? res=success'
  May 02 12:06:33 hunt systemd[1]: gpu-manager.service: Start request repeated 
too quickly.
  May 02 12:06:33 hunt systemd[1]: gpu-manager.service: Failed with result 
'start-limit-hit'.

  
  The referenced dkms path does not exist:

  sarnold@hunt:~$ ls -l /lib/modules/4.15.0-20-generic/updates/dkms
  ls: cannot access '/lib/modules/4.15.0-20-generic/updates/dkms': No such file 
or directory
  sarnold@hunt:~$ ls -l /lib/modules/4.15.0-20-generic/updates/
  ls: cannot access '/lib/modules/4.15.0-20-generic/updates/': No such file or 
directory
  sarnold@hunt:~$ ls -l /lib/modules/4.15.0-20-generic/
  total 5292
  lrwxrwxrwx  1 root root  40 Apr 23 21:56 build -> 
/usr/src/linux-headers-4.15.0-20-generic
  drwxr-xr-x  2 root root4096 Apr 23 21:56 initrd
  drwxr-xr-x 15 root root4096 May  1 18:23 kernel
  -rw-r--r--  1 root root 1253762 May  1 18:36 modules.alias
  -rw-r--r--  1 root root 1235639 May  1 18:36 modules.alias.bin
  -rw-r--r--  1 root root7594 Apr 23 21:56 modules.builtin
  -rw-r--r--  1 root root9600 May  1 18:36 modules.builtin.bin
  -rw-r--r--  1 root root  552117 May  1 18:36 modules.dep
  -rw-r--r--  1 root root  780401 May  1 18:36 modules.dep.bin
  -rw-r--r--  1 root root 317 May  1 18:36 modules.devname
  -rw-r--r--  1 root root  206162 Apr 23 21:56 modules.order
  

[Desktop-packages] [Bug 1808874] Re: nvidia-detector doesn't seem to detect nvidia

[Sebastien Bacher]

** Changed in: ubuntu-drivers-common (Ubuntu)
   Importance: Undecided => Low

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

Title:
  nvidia-detector doesn't seem to detect nvidia

Status in ubuntu-drivers-common package in Ubuntu:
  New

Bug description:
  bdmurray@flash:~$ grep nvidia /proc/modules 
  nvidia_uvm 757760 0 - Live 0x (POE)
  nvidia_drm 40960 1 - Live 0x (POE)
  nvidia_modeset 1110016 3 nvidia_drm, Live 0x (POE)
  nvidia 14360576 84 nvidia_uvm,nvidia_modeset, Live 0x (POE)
  drm_kms_helper 172032 1 nvidia_drm, Live 0x
  drm 401408 4 nvidia_drm,drm_kms_helper, Live 0x
  ipmi_msghandler 53248 2 nvidia,ipmi_devintf, Live 0x
  bdmurray@flash:~$ nvidia-detector
  none
  bdmurray@flash:~$ cat /etc/lsb-release 
  DISTRIB_ID=Ubuntu
  DISTRIB_RELEASE=18.04
  DISTRIB_CODENAME=bionic
  DISTRIB_DESCRIPTION="Ubuntu 18.04.1 LTS"

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

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

[Desktop-packages] [Bug 1808861] Re: chromium-browser crash Unreportable - Invalid core dump: BFD: warning: apport_core is truncated

[Brian Murray]

The log file /var/log/apport.log might be helpful in sorting out why an
incomplete core was written. Could you please add it as an attachment?

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

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

Title:
  chromium-browser crash Unreportable - Invalid core dump: BFD: warning:
  apport_core is truncated

Status in apport package in Ubuntu:
  Incomplete
Status in chromium-browser package in Ubuntu:
  New

Bug description:
  Trying to report a crash in chromium-browser, get Unreportable reason
  Invalid core dump: BFD: warning apport_core is truncated (see
  screenshot, can't copy message from apport dialog - bug # 1273752).

  UnreportableReason:
   Invalid core dump: BFD: warning: /tmp/apport_core_6yb3cl_7 is truncated: 
expected core file size >= 1245646848, found: 760283136
   warning: core file may not match specified executable file.

  
  Expected: able to report ?

  
  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: apport 2.20.9-0ubuntu7.5
  ProcVersionSignature: User Name 4.15.0-42.45-generic 4.15.18
  Uname: Linux 4.15.0-42-generic x86_64
  ApportLog:
   ERROR: apport (pid 31805) Mon Dec 17 15:14:09 2018: called for pid 15848, 
signal 5, core limit 0, dump mode 1
   ERROR: apport (pid 31805) Mon Dec 17 15:14:09 2018: executable: 
/usr/lib/chromium-browser/chromium-browser (command line 
"/usr/lib/chromium-browser/chromium-browser\ --enable-pinch")
   ERROR: apport (pid 31805) Mon Dec 17 15:14:09 2018: is_closing_session(): no 
DBUS_SESSION_BUS_ADDRESS in environment
   ERROR: apport (pid 31805) Mon Dec 17 15:15:23 2018: wrote report 
/var/crash/_usr_lib_chromium-browser_chromium-browser.1000.crash
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Dec 17 15:30:28 2018
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2018-09-12 (96 days ago)
  InstallationMedia: Ubuntu 16.04.5 LTS "Xenial Xerus" - Release amd64 
(20180731)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: apport
  UpgradeStatus: Upgraded to bionic on 2018-09-28 (80 days ago)

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

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

[Desktop-packages] [Bug 1795760] Re: Xwayland crashed with SIGABRT in OsAbort()

[Gert van de Kraats]

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

This is not a duplicate. It is a crash at OsAbort, but that is the only 
coincidence with #1745799.
The cause is different.
It contains a working solution.
PLease do something with it and do not mark it as duplicate.

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

Title:
  Xwayland crashed with SIGABRT in OsAbort()

Status in xorg-server package in Ubuntu:
  New

Bug description:
  This bug contains a crash related to bug 1795089.
  Local code is used for libmutter, to solve bug 1790525 and to display 
buffersizes at module setup_spans at cogl/cogl/cogl-texture-2d-sliced.c and at 
module allocate_from_bitmap at cogl/cogl/driver/gl/cogl-texture-2d-gl.c .

  Dual monitor is used without a monitors.xml files usable by gdm3 with
  wayland.

  After logging in using ubuntu with wayland both screens are shown, but
  crash after a short time without user doing anything.

  At syslog we see the displayed buffersizes which are too large before
  the crash:

  Oct  2 23:57:42 Gert2 gnome-shell[2636]: GK_allocate_from_bitmap 2560 1024
  Oct  2 23:57:42 Gert2 gnome-shell[2636]: GK_cogl_set_error Failed to create 
texture 2d due to size/format constraints
  Oct  2 23:57:42 Gert2 gnome-shell[2636]: Failed to allocate texture: Failed 
to create texture 2d due to size/format constraints

  ProblemType: Crash
  DistroRelease: Ubuntu 18.10
  Package: xwayland 2:1.20.1-3ubuntu1
  ProcVersionSignature: Ubuntu 4.18.0-8.9-generic 4.18.7
  Uname: Linux 4.18.0-8-generic i686
  ApportVersion: 2.20.10-0ubuntu11
  Architecture: i386
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Oct  2 23:57:24 2018
  DistUpgraded: Fresh install
  DistroCodename: cosmic
  DistroVariant: ubuntu
  ExecutablePath: /usr/bin/Xwayland
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation Mobile 945GM/GMS, 943/940GML Express Integrated Graphics 
Controller [8086:27a2] (rev 03) (prog-if 00 [VGA controller])
     Subsystem: Dell Mobile 945GM/GMS, 943/940GML Express Integrated Graphics 
Controller [1028:01c2]
     Subsystem: Dell Mobile 945GM/GMS/GME, 943/940GML Express Integrated 
Graphics Controller [1028:01c2]
  MachineType: Dell Inc. Latitude D620
  PccardctlIdent:
   Socket 0:
     no product info available
  PccardctlStatus:
   Socket 0:
     no card
  ProcCmdline: /usr/bin/Xwayland :0 -rootless -terminate -accessx -core -listen 
4 -listen 5 -displayfd 6
  ProcEnviron:
   LANGUAGE=en_US:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-8-generic 
root=UUID=4ccc6cca-be3d-4471-9677-1012a53ebfd7 ro splash quiet vt.handoff=1
  Signal: 6
  SourcePackage: xorg-server
  StacktraceTop:
   OsAbort ()
   ?? ()
   FatalError ()
   _start ()
  Title: Xwayland crashed with SIGABRT in OsAbort()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  dmi.bios.date: 04/11/2006
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A02
  dmi.board.name: 0TD761
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA02:bd04/11/2006:svnDellInc.:pnLatitudeD620:pvr:rvnDellInc.:rn0TD761:rvr:cvnDellInc.:ct8:cvr:
  dmi.product.name: Latitude D620
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.94-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.1-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.1-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.1-3ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1build1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-3

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

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

[Desktop-packages] [Bug 1808785] Re: Searching for emoji in the snap yields no results 

[Will Cooke]

On a clean install of 18.04 this works as expected.

It's something I've done on my machine by removing the old deb.


** Changed in: gnome-characters (Ubuntu)
   Status: Confirmed => Triaged

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

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

Title:
  Searching for emoji in the snap yields no results 

Status in gnome-characters package in Ubuntu:
  Triaged

Bug description:
  In the snap version, searching for an emoji by name does not generate
  any results.

  If I do the same search in the deb version then things work as
  expected.

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

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

[Desktop-packages] [Bug 1768637] Re: /etc/modprobe.d is not a file

[Will Cooke]

Not a release bug, so marking as notfixing.  This can still be worked on
and fixed though, only that it's not considered a release blocker.


** Tags removed: rls-dd-incoming
** Tags added: rls-dd-notfixing

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

Title:
  /etc/modprobe.d is not a file

Status in ubuntu-drivers-common package in Ubuntu:
  Confirmed

Bug description:
  Hello, I noticed the following entries in my journal after upgrading
  to 18.04 LTS from 16.04 LTS:

  May 02 12:06:31 hunt gpu-manager[1112]: /etc/modprobe.d is not a file
  May 02 12:06:31 hunt gpu-manager[1112]: /etc/modprobe.d is not a file
  May 02 12:06:31 hunt gpu-manager[1112]: /etc/modprobe.d is not a file
  May 02 12:06:31 hunt gpu-manager[1112]: /etc/modprobe.d is not a file
  May 02 12:06:31 hunt gpu-manager[1112]: Error: can't open 
/lib/modules/4.15.0-20-generic/updates/dkms
  May 02 12:06:31 hunt audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 
ses=4294967295 msg='unit=gpu-manager comm="systemd" exe="/lib/systemd/systemd" 
hostname=? addr=? terminal=? res=success'
  May 02 12:06:31 hunt audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 
ses=4294967295 msg='unit=gpu-manager comm="systemd" exe="/lib/systemd/systemd" 
hostname=? addr=? terminal=? res=success'
  May 02 12:06:32 hunt gpu-manager[1170]: /etc/modprobe.d is not a file
  May 02 12:06:32 hunt gpu-manager[1170]: /etc/modprobe.d is not a file
  May 02 12:06:32 hunt gpu-manager[1170]: /etc/modprobe.d is not a file
  May 02 12:06:32 hunt gpu-manager[1170]: /etc/modprobe.d is not a file
  May 02 12:06:32 hunt gpu-manager[1170]: Error: can't open 
/lib/modules/4.15.0-20-generic/updates/dkms
  May 02 12:06:32 hunt audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 
ses=4294967295 msg='unit=gpu-manager comm="systemd" exe="/lib/systemd/systemd" 
hostname=? addr=? terminal=? res=success'
  May 02 12:06:32 hunt audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 
ses=4294967295 msg='unit=gpu-manager comm="systemd" exe="/lib/systemd/systemd" 
hostname=? addr=? terminal=? res=success'
  May 02 12:06:32 hunt gpu-manager[1254]: /etc/modprobe.d is not a file
  May 02 12:06:32 hunt gpu-manager[1254]: /etc/modprobe.d is not a file
  May 02 12:06:32 hunt gpu-manager[1254]: /etc/modprobe.d is not a file
  May 02 12:06:32 hunt gpu-manager[1254]: /etc/modprobe.d is not a file
  May 02 12:06:32 hunt gpu-manager[1254]: Error: can't open 
/lib/modules/4.15.0-20-generic/updates/dkms
  May 02 12:06:32 hunt audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 
ses=4294967295 msg='unit=gpu-manager comm="systemd" exe="/lib/systemd/systemd" 
hostname=? addr=? terminal=? res=success'
  May 02 12:06:32 hunt audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 
ses=4294967295 msg='unit=gpu-manager comm="systemd" exe="/lib/systemd/systemd" 
hostname=? addr=? terminal=? res=success'
  May 02 12:06:32 hunt gpu-manager[1316]: /etc/modprobe.d is not a file
  May 02 12:06:32 hunt gpu-manager[1316]: /etc/modprobe.d is not a file
  May 02 12:06:32 hunt gpu-manager[1316]: /etc/modprobe.d is not a file
  May 02 12:06:32 hunt gpu-manager[1316]: /etc/modprobe.d is not a file
  May 02 12:06:32 hunt gpu-manager[1316]: Error: can't open 
/lib/modules/4.15.0-20-generic/updates/dkms
  May 02 12:06:33 hunt audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 
ses=4294967295 msg='unit=gpu-manager comm="systemd" exe="/lib/systemd/systemd" 
hostname=? addr=? terminal=? res=success'
  May 02 12:06:33 hunt audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 
ses=4294967295 msg='unit=gpu-manager comm="systemd" exe="/lib/systemd/systemd" 
hostname=? addr=? terminal=? res=success'
  May 02 12:06:33 hunt systemd[1]: gpu-manager.service: Start request repeated 
too quickly.
  May 02 12:06:33 hunt systemd[1]: gpu-manager.service: Failed with result 
'start-limit-hit'.

  
  The referenced dkms path does not exist:

  sarnold@hunt:~$ ls -l /lib/modules/4.15.0-20-generic/updates/dkms
  ls: cannot access '/lib/modules/4.15.0-20-generic/updates/dkms': No such file 
or directory
  sarnold@hunt:~$ ls -l /lib/modules/4.15.0-20-generic/updates/
  ls: cannot access '/lib/modules/4.15.0-20-generic/updates/': No such file or 
directory
  sarnold@hunt:~$ ls -l /lib/modules/4.15.0-20-generic/
  total 5292
  lrwxrwxrwx  1 root root  40 Apr 23 21:56 build -> 
/usr/src/linux-headers-4.15.0-20-generic
  drwxr-xr-x  2 root root4096 Apr 23 21:56 initrd
  drwxr-xr-x 15 root root4096 May  1 18:23 kernel
  -rw-r--r--  1 root root 1253762 May  1 18:36 modules.alias
  -rw-r--r--  1 root root 1235639 May  1 18:36 modules.alias.bin
  -rw-r--r--  1 root root7594 Apr 23 21:56 modules.builtin
  -rw-r--r--  1 root root9600 May  1 18:36 modules.builtin.bin
  -rw-r--r--  1 root root  552117 May  1 18:36 modules.dep
  -rw-r--r--  1 root root  780401 May  1 18:36 modules.dep.bin
  -rw-r--r--  1 root root   

[Desktop-packages] [Bug 1808874] Re: nvidia-detector doesn't seem to detect nvidia

[Will Cooke]

Not a release blocker, so marking as not fixing.  tseliot has said he
would work on this though.


** Changed in: ubuntu-drivers-common (Ubuntu)
 Assignee: (unassigned) => Alberto Milone (albertomilone)

** Tags removed: rls-dd-incoming
** Tags added: rls-dd-notfixing

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

Title:
  nvidia-detector doesn't seem to detect nvidia

Status in ubuntu-drivers-common package in Ubuntu:
  New

Bug description:
  bdmurray@flash:~$ grep nvidia /proc/modules 
  nvidia_uvm 757760 0 - Live 0x (POE)
  nvidia_drm 40960 1 - Live 0x (POE)
  nvidia_modeset 1110016 3 nvidia_drm, Live 0x (POE)
  nvidia 14360576 84 nvidia_uvm,nvidia_modeset, Live 0x (POE)
  drm_kms_helper 172032 1 nvidia_drm, Live 0x
  drm 401408 4 nvidia_drm,drm_kms_helper, Live 0x
  ipmi_msghandler 53248 2 nvidia,ipmi_devintf, Live 0x
  bdmurray@flash:~$ nvidia-detector
  none
  bdmurray@flash:~$ cat /etc/lsb-release 
  DISTRIB_ID=Ubuntu
  DISTRIB_RELEASE=18.04
  DISTRIB_CODENAME=bionic
  DISTRIB_DESCRIPTION="Ubuntu 18.04.1 LTS"

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

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

[Desktop-packages] [Bug 1808990] [NEW] Xorg freeze

[AlejandroHueto]

Public bug reported:

The screen appears to freeze, with possible SSH access from another machine 
during the first minutes. After that, the system totally freezes, with not even 
ethernet connection anymore.
Only hard reboot helps to solve the issue, with normal functionality afterwards.
It occurs in a random way.

Ubuntu version 18.04.1 LTS.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xorg 1:7.7+19ubuntu7.1
ProcVersionSignature: Ubuntu 4.15.0-42.45-generic 4.15.18
Uname: Linux 4.15.0-42-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.5
Architecture: amd64
BootLog: Error: [Errno 13] Permiso denegado: '/var/log/boot.log'
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Tue Dec 18 15:32:13 2018
DistUpgraded: Fresh install
DistroCodename: bionic
DistroVariant: ubuntu
DkmsStatus:
 virtualbox, 5.2.18, 4.15.0-39-generic, x86_64: installed
 virtualbox, 5.2.18, 4.15.0-42-generic, x86_64: installed
ExtraDebuggingInterest: I just need to know a workaround
GpuHangFrequency: Once a week
GpuHangReproducibility: Seems to happen randomly
GpuHangStarted: Immediately after installing this version of Ubuntu
GraphicsCard:
 NVIDIA Corporation GK208 [GeForce GT 730] [10de:1287] (rev a1) (prog-if 00 
[VGA controller])
   Subsystem: ASUSTeK Computer Inc. GK208B [GeForce GT 730] [1043:850c]
InstallationDate: Installed on 2018-11-14 (34 days ago)
InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725)
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 002: ID 046d:c016 Logitech, Inc. Optical Wheel Mouse
 Bus 001 Device 003: ID 046d:c31c Logitech, Inc. Keyboard K120
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: System manufacturer System Product Name
ProcEnviron:
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=es_ES.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-42-generic 
root=UUID=7af5a6a3-c5c3-48e2-9477-704034a9e379 ro quiet splash vt.handoff=1
SourcePackage: xorg
Symptom: display
Title: Xorg freeze
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 06/07/2016
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 1804
dmi.board.asset.tag: Default string
dmi.board.name: Z170-P
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: Rev X.0x
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 3
dmi.chassis.vendor: Default string
dmi.chassis.version: Default string
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1804:bd06/07/2016:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ170-P:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: System Product Name
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.91-2
version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1
version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1
version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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


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

Title:
  Xorg freeze

Status in xorg package in Ubuntu:
  New

Bug description:
  The screen appears to freeze, with possible SSH access from another machine 
during the first minutes. After that, the system totally freezes, with not even 
ethernet connection anymore.
  Only hard reboot helps to solve the issue, with normal functionality 
afterwards.
  It occurs in a random way.

  Ubuntu version 18.04.1 LTS.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-42.45-generic 4.15.18
  Uname: Linux 4.15.0-42-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  BootLog: Error: [Errno 13] Permiso denegado: '/var/log/boot.log'
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Dec 18 15:32:13 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox, 5.2.18, 4.15.0-39-generic, x86_64: installed
   virtualbox, 5.2.18, 4.15.0-42-generic, x86_64: installed
  ExtraDebuggingInterest: I just need to know a workaround
  GpuHangFrequency: Once a week
  GpuHangReproducibility: Seems to happen randomly
  

[Desktop-packages] [Bug 1753776] Re: Graphics corruption just before login animation to Xorg sessions (Intel gen9 GPUs only)

[Bug Watch Updater]

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

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

Title:
  Graphics corruption just before login animation to Xorg sessions
  (Intel gen9 GPUs only)

Status in Mesa:
  Unknown
Status in gdm3 package in Ubuntu:
  Invalid
Status in mesa package in Ubuntu:
  Fix Released
Status in wayland package in Ubuntu:
  Invalid
Status in gdm3 source package in Bionic:
  Invalid
Status in mesa source package in Bionic:
  Fix Released
Status in wayland source package in Bionic:
  Invalid

Bug description:
  Immediately after login (I enter the password and hit enter) the screen 
"crumbles" for few seconds, then all becomes normal and the system works fine. 
I have done apt update+upgrade many times, also with proposed enabled, I have 
also installed a new ISO (now i'm using the Alpha dated 20180305) but the 
problem remains. The problem happens with the x11 session but not with wayland. 
  Also problem does not show with different hardware. 

  corrado@corrado-p7-bb-0305:~$ inxi -Fx
  System:Host: corrado-p7-bb-0305 Kernel: 4.15.0-10-generic x86_64 bits: 64 
gcc: 7.3.0
 Desktop: Gnome 3.27.92 (Gtk 3.22.28-1ubuntu3) Distro: Ubuntu 
Bionic Beaver (development branch)
  Machine:   Device: desktop Mobo: ASRock model: H110M-G/M.2 serial: N/A UEFI: 
American Megatrends v: P1.10 date: 05/11/2017
  CPU:   Dual core Intel Core i3-7100 (-MT-MCP-) arch: Skylake rev.9 cache: 
3072 KB
 flags: (lm nx sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx) bmips: 15648
 clock speeds: max: 3900 MHz 1: 1018 MHz 2: 3150 MHz 3: 3153 MHz 4: 
3081 MHz
  Graphics:  Card: Intel HD Graphics 630 bus-ID: 00:02.0
 Display Server: x11 (X.Org 1.19.6 ) driver: i915 Resolution: 
1920x1080@60.00hz
 OpenGL: renderer: Mesa DRI Intel HD Graphics 630 (Kaby Lake GT2)
 version: 4.5 Mesa 18.0.0-rc4 Direct Render: Yes
  Audio: Card Intel Sunrise Point-H HD Audio driver: snd_hda_intel bus-ID: 
00:1f.3
 Sound: Advanced Linux Sound Architecture v: k4.15.0-10-generic
  Network:   Card: Intel Ethernet Connection (2) I219-V driver: e1000e v: 
3.2.6-k bus-ID: 00:1f.6
 IF: enp0s31f6 state: up speed: 100 Mbps duplex: full mac: 
70:85:c2:44:7b:86
  Drives:HDD Total Size: 1000.2GB (1.3% used)
 ID-1: /dev/sda model: TOSHIBA_DT01ACA1 size: 1000.2GB
  Partition: ID-1: / size: 32G used: 4.3G (15%) fs: ext4 dev: /dev/sda7
 ID-2: swap-1 size: 8.59GB used: 0.00GB (0%) fs: swap dev: /dev/sda2
  RAID:  No RAID devices: /proc/mdstat, md_mod kernel module present
  Sensors:   System Temperatures: cpu: 38.5C mobo: N/A
 Fan Speeds (in rpm): cpu: N/A
  Info:  Processes: 234 Uptime: 11 min Memory: 1144.7/7680.8MB Init: 
systemd runlevel: 5 Gcc sys: N/A
 Client: Shell (bash 4.4.181) inxi: 2.3.56 
  corrado@corrado-p7-bb-0305:~$

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu5
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Mar  6 15:47:50 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation HD Graphics 630 [8086:5912] (rev 04) (prog-if 00 [VGA 
controller])
 Subsystem: ASRock Incorporation HD Graphics 630 [1849:5912]
  InstallationDate: Installed on 2018-03-05 (0 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180305)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 046d:c016 Logitech, Inc. Optical Wheel Mouse
   Bus 001 Device 002: ID 058f:6377 Alcor Micro Corp. AU6375 4-LUN card reader
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-10-generic.efi.signed 
root=UUID=9a36b498-59f5-4a36-81db-3046ff6bdeaa ro quiet splash
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/11/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P1.10
  dmi.board.name: H110M-G/M.2
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP1.10:bd05/11/2017:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnH110M-G/M.2:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To 

[Desktop-packages] [Bug 1753776]

[Gitlab-migration]

-- GitLab Migration Automatic Message --

This bug has been migrated to freedesktop.org's GitLab instance and has
been closed from further activity.

You can subscribe and participate further through the new bug through
this link to our GitLab instance:
https://gitlab.freedesktop.org/xorg/xserver/issues/33.

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

Title:
  Graphics corruption just before login animation to Xorg sessions
  (Intel gen9 GPUs only)

Status in Mesa:
  Unknown
Status in gdm3 package in Ubuntu:
  Invalid
Status in mesa package in Ubuntu:
  Fix Released
Status in wayland package in Ubuntu:
  Invalid
Status in gdm3 source package in Bionic:
  Invalid
Status in mesa source package in Bionic:
  Fix Released
Status in wayland source package in Bionic:
  Invalid

Bug description:
  Immediately after login (I enter the password and hit enter) the screen 
"crumbles" for few seconds, then all becomes normal and the system works fine. 
I have done apt update+upgrade many times, also with proposed enabled, I have 
also installed a new ISO (now i'm using the Alpha dated 20180305) but the 
problem remains. The problem happens with the x11 session but not with wayland. 
  Also problem does not show with different hardware. 

  corrado@corrado-p7-bb-0305:~$ inxi -Fx
  System:Host: corrado-p7-bb-0305 Kernel: 4.15.0-10-generic x86_64 bits: 64 
gcc: 7.3.0
 Desktop: Gnome 3.27.92 (Gtk 3.22.28-1ubuntu3) Distro: Ubuntu 
Bionic Beaver (development branch)
  Machine:   Device: desktop Mobo: ASRock model: H110M-G/M.2 serial: N/A UEFI: 
American Megatrends v: P1.10 date: 05/11/2017
  CPU:   Dual core Intel Core i3-7100 (-MT-MCP-) arch: Skylake rev.9 cache: 
3072 KB
 flags: (lm nx sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx) bmips: 15648
 clock speeds: max: 3900 MHz 1: 1018 MHz 2: 3150 MHz 3: 3153 MHz 4: 
3081 MHz
  Graphics:  Card: Intel HD Graphics 630 bus-ID: 00:02.0
 Display Server: x11 (X.Org 1.19.6 ) driver: i915 Resolution: 
1920x1080@60.00hz
 OpenGL: renderer: Mesa DRI Intel HD Graphics 630 (Kaby Lake GT2)
 version: 4.5 Mesa 18.0.0-rc4 Direct Render: Yes
  Audio: Card Intel Sunrise Point-H HD Audio driver: snd_hda_intel bus-ID: 
00:1f.3
 Sound: Advanced Linux Sound Architecture v: k4.15.0-10-generic
  Network:   Card: Intel Ethernet Connection (2) I219-V driver: e1000e v: 
3.2.6-k bus-ID: 00:1f.6
 IF: enp0s31f6 state: up speed: 100 Mbps duplex: full mac: 
70:85:c2:44:7b:86
  Drives:HDD Total Size: 1000.2GB (1.3% used)
 ID-1: /dev/sda model: TOSHIBA_DT01ACA1 size: 1000.2GB
  Partition: ID-1: / size: 32G used: 4.3G (15%) fs: ext4 dev: /dev/sda7
 ID-2: swap-1 size: 8.59GB used: 0.00GB (0%) fs: swap dev: /dev/sda2
  RAID:  No RAID devices: /proc/mdstat, md_mod kernel module present
  Sensors:   System Temperatures: cpu: 38.5C mobo: N/A
 Fan Speeds (in rpm): cpu: N/A
  Info:  Processes: 234 Uptime: 11 min Memory: 1144.7/7680.8MB Init: 
systemd runlevel: 5 Gcc sys: N/A
 Client: Shell (bash 4.4.181) inxi: 2.3.56 
  corrado@corrado-p7-bb-0305:~$

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu5
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Mar  6 15:47:50 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation HD Graphics 630 [8086:5912] (rev 04) (prog-if 00 [VGA 
controller])
 Subsystem: ASRock Incorporation HD Graphics 630 [1849:5912]
  InstallationDate: Installed on 2018-03-05 (0 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180305)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 046d:c016 Logitech, Inc. Optical Wheel Mouse
   Bus 001 Device 002: ID 058f:6377 Alcor Micro Corp. AU6375 4-LUN card reader
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-10-generic.efi.signed 
root=UUID=9a36b498-59f5-4a36-81db-3046ff6bdeaa ro quiet splash
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/11/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P1.10
  dmi.board.name: H110M-G/M.2
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be 

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

[Shock]

The same thing happened without extensions.

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

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

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

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  I pressed a button on my Wacom tablet at the Gnome shell lock screen.
  Once it crashed I was able to see the apps/desktop for a while until
  the lock screen appeared again.

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.28.3-0ubuntu0.18.04.2
  ProcVersionSignature: Ubuntu 4.15.0-38.41-generic 4.15.18
  Uname: Linux 4.15.0-38-generic x86_64
  NonfreeKernelModules: lkp_Ubuntu_4_15_0_38_41_generic_45
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Nov 19 18:38:17 2018
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  InstallationDate: Installed on 2017-03-13 (616 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  ProcCmdline: /usr/bin/gnome-shell
  SegvAnalysis:
   Segfault happened at: 0x7fa27d2b2b38:cmp%ebp,0x8(%rax)
   PC (0x7fa27d2b2b38) ok
   source "%ebp" ok
   destination "0x8(%rax)" (0x0008) not located in a known VMA region 
(needed writable region)!
  SegvReason: writing NULL VMA
  Signal: 11
  SourcePackage: gnome-shell
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/mutter/libmutter-clutter-2.so
   ?? () from /usr/lib/x86_64-linux-gnu/mutter/libmutter-clutter-2.so
   ?? () from /usr/lib/x86_64-linux-gnu/mutter/libmutter-clutter-2.so
   clutter_x11_handle_event () from 
/usr/lib/x86_64-linux-gnu/mutter/libmutter-clutter-2.so
   ?? () from /usr/lib/x86_64-linux-gnu/libmutter-2.so.0
  Title: gnome-shell crashed with SIGSEGV in clutter_x11_handle_event()
  UpgradeStatus: Upgraded to bionic on 2018-08-24 (87 days ago)
  UserGroups: adm cdrom dip libvirt libvirtd lpadmin plugdev sambashare sudo

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

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

[Desktop-packages] [Bug 1702873] Re: [snap] artifacts when using HiDPI display

[Ken VanDine]

The fix has been merged, now we need snaps to be rebuilt.

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

Title:
  [snap] artifacts when using HiDPI display

Status in libreoffice package in Ubuntu:
  In Progress

Bug description:
  I am using a HiDPI display. At scale 2.
  The cursor is tiny when inside the window of the app.
  Many icons on the toolbar are blurry, more than usual.

  I report these commands' output as requested:
lsb_release -a
snap info --verbose libreoffice core

  luca@xpsluca:~$ lsb_release -a
  No LSB modules are available.
  Distributor ID:   Ubuntu
  Description:  Ubuntu 16.10
  Release:  16.10
  Codename: yakkety
  luca@xpsluca:~$ snap info --verbose libreoffice core
  name:  libreoffice
  summary:   "LibreOffice is a powerful office suite including word processing 
and creation of spreadsheets, slideshows and databases"
  publisher: canonical
  contact:   http://www.libreoffice.org/get-help/community-support/
  description: |
LibreOffice is a powerful office suite – its clean interface and
feature-rich tools help you unleash your creativity and enhance your
productivity. LibreOffice includes several applications that make it the 
most
powerful Free and Open Source office suite on the market: Writer (word
processing), Calc (spreadsheets), Impress (presentations), Draw (vector
graphics and flowcharts), Base (databases), and Math (formula editing).
  commands:
- libreoffice.base
- libreoffice.calc
- libreoffice.draw
- libreoffice.impress
- libreoffice
- libreoffice.math
- libreoffice.writer
  notes:  
private:  false
confinement:  strict
devmode:  false
jailmode: false
trymode:  false
enabled:  true
broken:   false
  tracking:   beta
  installed:  5.3.4.2 (21) 368MB 
  refreshed:  2017-07-01 19:14:41 +0200 CEST
  channels:
latest/stable:5.3.2.2 (19) 375MB -
latest/candidate: 5.3.2.2 (19) 375MB -
latest/beta:  5.3.4.2 (21) 368MB -
latest/edge:  5.3.2.2 (19) 375MB -
  ---
  name:  core
  summary:   "snapd runtime environment"
  publisher: canonical
  contact:   snappy-canonical-storeacco...@canonical.com
  description: |
The core runtime environment for snapd
  type:   core
  notes:  
private:  false
confinement:  strict
devmode:  false
jailmode: false
trymode:  false
enabled:  true
broken:   false
  tracking:   stable
  installed:  16-2 (2312) 83MB 
  refreshed:  2017-04-11 14:28:54 +0200 CEST
  channels:   
latest/stable:16-2 (2312) 83MB -
latest/candidate: 16-2.26.8(2329) 84MB -
latest/beta:  16-2.26.8(2329) 84MB -
latest/edge:  16-2.26.8+git258.fa4bcff (2343) 85MB -

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

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

[Desktop-packages] [Bug 1118150] Re: gnome-control-center crashed with SIGSEGV in finish_with_cleanup()

[Sebastien Bacher]

The bug is old without recent report, closing. Better to open a new
report if there is still a similar issue in recent Ubuntu versions

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

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

Title:
  gnome-control-center crashed with SIGSEGV in finish_with_cleanup()

Status in gnome-control-center package in Ubuntu:
  Invalid

Bug description:
  Steps to reproduce :

  Open Gnome Control Center
  Add Online Accounts
  Add Google account
  before the login page comes, close Window or click on All Settings tab

  The crash appears.

  ProblemType: Crash
  DistroRelease: Ubuntu 13.04
  Package: gnome-control-center 1:3.6.3-0ubuntu12
  ProcVersionSignature: Ubuntu 3.8.0-4.9-generic 3.8.0-rc6
  Uname: Linux 3.8.0-4-generic x86_64
  ApportVersion: 2.8-0ubuntu4
  Architecture: amd64
  Date: Thu Feb  7 14:23:01 2013
  ExecutablePath: /usr/bin/gnome-control-center
  InstallationDate: Installed on 2013-02-05 (1 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Alpha amd64 (20130128)
  MarkForUpload: True
  ProcCmdline: gnome-control-center
  ProcEnviron:
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
   PATH=(custom, no user)
   LANGUAGE=en_IN:en
   LANG=en_IN
  SegvAnalysis:
   Segfault happened at: 0x7fedc172a1e5:mov0x28(%rbx),%rdi
   PC (0x7fedc172a1e5) ok
   source "0x28(%rbx)" (0xaad2) not located in a known VMA region 
(needed readable region)!
   destination "%rdi" ok
  SegvReason: reading unknown VMA
  Signal: 11
  SourcePackage: gnome-control-center
  StacktraceTop:
   ?? () from /usr/lib/libaccount-plugin-1.0.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libsignon-glib.so.1
   g_simple_async_result_complete () from 
/usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
   g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
  Title: gnome-control-center crashed with SIGSEGV in 
g_simple_async_result_complete()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  usr_lib_gnome-control-center:
   activity-log-manager-control-center 0.9.4-0ubuntu6.1
   deja-dup25.5-0ubuntu1
   gnome-control-center-signon 0.1.2bzr12.12.05-0ubuntu1
   gnome-control-center-unity  1.2-0ubuntu1
   indicator-datetime  12.10.3daily13.02.06-0ubuntu1

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

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

[Desktop-packages] [Bug 1126954] Re: [printers]: gnome-control-center crashed with SIGSEGV in g_strdup()

[Sebastien Bacher]

The bug is old without recent report, closing. Better to open a new
report if there is still a similar issue in recent Ubuntu versions

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

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

Title:
  [printers]: gnome-control-center crashed with SIGSEGV in g_strdup()

Status in gnome-control-center package in Ubuntu:
  Invalid

Bug description:
  I tried to use GNOME3 printer setting with Ricoh Aficio MP 9002 PCL XL
  PPD in OpenPrinting (attached), port file:///tmp/test.prn (my CUPS is
  FileDevice enabled).  Option Finisher SR4080 is installed.

  Select the printer, press "Option" button to set default options. I would 
like to try UI constraints handling feature so I selected "Paper Type" as 
"Labels" in "Page Setup" group and "Z-fold" as "Left Fold" in "Advanced" tab 
(because MP 9002 can't allow Z-fold with Label paper type; they should be 
conflict).
  I saw conflict indicator (red triangle exclamation mark) appeared, but I 
ignored and press "OK", so GNOME3 printer settting is gone.

  Again I tried to reproduce, but I can't.  So I'm not sure UI
  constraints handling has any relation about the issue.

  ProblemType: Crash
  DistroRelease: Ubuntu 13.04
  Package: gnome-control-center 1:3.6.3-0ubuntu13
  ProcVersionSignature: Ubuntu 3.8.0-6.13-generic 3.8.0-rc7
  Uname: Linux 3.8.0-6-generic i686
  ApportVersion: 2.8-0ubuntu4
  Architecture: i386
  Date: Sat Feb 16 14:26:18 2013
  ExecutablePath: /usr/bin/gnome-control-center
  InstallationDate: Installed on 2013-01-31 (15 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Alpha i386 (20130128)
  MarkForUpload: True
  ProcCmdline: gnome-control-center
  ProcEnviron:
   SHELL=/bin/zsh
   XDG_RUNTIME_DIR=
   PATH=(custom, no user)
   LANG=ja_JP.UTF-8
  SegvAnalysis:
   Segfault happened at: 0xb6bb61a6:movdqu (%edi),%xmm1
   PC (0xb6bb61a6) ok
   source "(%edi)" (0x6262ff62) not located in a known VMA region (needed 
readable region)!
   destination "%xmm1" ok
  SegvReason: reading unknown VMA
  Signal: 11
  SourcePackage: gnome-control-center
  StacktraceTop:
   ?? () from /lib/i386-linux-gnu/libc.so.6
   g_strdup () from /lib/i386-linux-gnu/libglib-2.0.so.0
   ?? () from /usr/lib/control-center-1/panels/libprinters.so
   ?? () from /usr/lib/control-center-1/panels/libprinters.so
   ?? () from /usr/lib/control-center-1/panels/libprinters.so
  Title: [printers]: gnome-control-center crashed with SIGSEGV in g_strdup()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm lpadmin sambashare sudo
  usr_lib_gnome-control-center:
   activity-log-manager-control-center 0.9.4-0ubuntu6.1
   deja-dup25.5-0ubuntu1
   gnome-control-center-signon 0.1.2bzr12.12.05-0ubuntu1
   gnome-control-center-unity  1.2daily13.02.15-0ubuntu1
   indicator-datetime  12.10.3daily13.02.06-0ubuntu1

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

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

[Desktop-packages] [Bug 1159230] Re: gnome-control-center crashed with SIGSEGV in signon_auth_session_cancel()

[Sebastien Bacher]

The bug is old without recent report, closing. Better to open a new
report if there is still a similar issue in recent Ubuntu versions

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

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

Title:
  gnome-control-center crashed with SIGSEGV in
  signon_auth_session_cancel()

Status in gnome-control-center package in Ubuntu:
  Invalid

Bug description:
  That happened in twitter account setup specially if you click back
  while adding account , I mean when canceling.

  ProblemType: Crash
  DistroRelease: Ubuntu 13.04
  Package: gnome-control-center 1:3.6.3-0ubuntu16
  ProcVersionSignature: Ubuntu 3.8.0-14.24-generic 3.8.4
  Uname: Linux 3.8.0-14-generic i686
  ApportVersion: 2.9.2-0ubuntu2
  Architecture: i386
  Date: Sat Mar 23 22:39:50 2013
  ExecutablePath: /usr/bin/gnome-control-center
  InstallationDate: Installed on 2013-03-23 (0 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Alpha i386 (20130321)
  MarkForUpload: True
  ProcCmdline: gnome-control-center
  SegvAnalysis:
   Segfault happened at: 0xa2169bc7 :mov
(%esi),%edx
   PC (0xa2169bc7) ok
   source "(%esi)" (0x2d77ff02) not located in a known VMA region (needed 
readable region)!
   destination "%edx" ok
  SegvReason: reading unknown VMA
  Signal: 11
  SourcePackage: gnome-control-center
  StacktraceTop:
   signon_auth_session_cancel () from 
/usr/lib/i386-linux-gnu/libsignon-glib.so.1
   ?? () from /usr/lib/libaccount-plugin-1.0.so.0
   ?? () from /usr/lib/libaccount-plugin-1.0.so.0
   g_simple_async_result_complete () from 
/usr/lib/i386-linux-gnu/libgio-2.0.so.0
   ?? () from /usr/lib/i386-linux-gnu/libgio-2.0.so.0
  Title: gnome-control-center crashed with SIGSEGV in 
signon_auth_session_cancel()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  usr_lib_gnome-control-center:
   activity-log-manager-control-center 0.9.4-0ubuntu6.1
   deja-dup25.5-0ubuntu1
   gnome-control-center-signon 0.1.4-0ubuntu1
   gnome-control-center-unity  1.2daily13.02.15-0ubuntu1
   indicator-datetime  12.10.3daily13.03.07-0ubuntu1

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

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

[Desktop-packages] [Bug 1129684] Re: Displays shows extra monitor

[Sebastien Bacher]

The bug is old without recent report, closing. Better to open a new
report if there is still a similar issue in recent Ubuntu versions

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

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

Title:
  Displays shows extra monitor

Status in gnome-control-center package in Ubuntu:
  Invalid

Bug description:
  $ lsb_release -rd
  Description:  Ubuntu Raring Ringtail (development branch)
  Release:  13.04

  $ apt-cache policy gnome-control-center
  gnome-control-center:
Installed: 1:3.6.3-0ubuntu13
Candidate: 1:3.6.3-0ubuntu13
Version table:
   *** 1:3.6.3-0ubuntu13 0
  500 http://us.archive.ubuntu.com/ubuntu/ raring/main amd64 Packages
  100 /var/lib/dpkg/status

  An additional monitor appears inside gnome-control-center Displays.

  Doesn't seem to be effecting the other screens.  I can still
  successfully extend and mirror my laptop screen with my hp monitor.  I
  attached a picture showing the ghost screen.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: gnome-control-center 1:3.6.3-0ubuntu13
  ProcVersionSignature: Ubuntu 3.8.0-6.13-generic 3.8.0-rc7
  Uname: Linux 3.8.0-6-generic x86_64
  ApportVersion: 2.8-0ubuntu4
  Architecture: amd64
  Date: Mon Feb 18 20:08:37 2013
  ExecutablePath: /usr/bin/gnome-control-center
  InstallationDate: Installed on 2012-12-08 (72 days ago)
  InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5)
  MarkForUpload: True
  ProcEnviron:
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
   PATH=(custom, user)
   LANG=en_US.UTF-8
  SourcePackage: gnome-control-center
  UpgradeStatus: Upgraded to raring on 2013-02-18 (0 days ago)
  usr_lib_gnome-control-center:
   activity-log-manager-control-center 0.9.4-0ubuntu6.1
   deja-dup25.5-0ubuntu1
   gnome-control-center-signon 0.1.2bzr12.12.05-0ubuntu1
   gnome-control-center-unity  1.2daily13.02.15-0ubuntu1
   indicator-datetime  12.10.3daily13.02.06-0ubuntu1

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

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

[Desktop-packages] [Bug 1161624] Re: gnome-control-center crashed with SIGSEGV in store_authentication_parameters()

[Sebastien Bacher]

The bug is old without recent report, closing. Better to open a new
report if there is still a similar issue in recent Ubuntu versions

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

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

Title:
  gnome-control-center crashed with SIGSEGV in
  store_authentication_parameters()

Status in gnome-control-center package in Ubuntu:
  Invalid

Bug description:
  Don't know what I did

  ProblemType: Crash
  DistroRelease: Ubuntu 13.04
  Package: gnome-control-center 1:3.6.3-0ubuntu18
  ProcVersionSignature: Ubuntu 3.8.0-15.25-generic 3.8.4
  Uname: Linux 3.8.0-15-generic x86_64
  ApportVersion: 2.9.2-0ubuntu5
  Architecture: amd64
  Date: Thu Mar 28 21:45:37 2013
  ExecutablePath: /usr/bin/gnome-control-center
  InstallationDate: Installed on 2013-02-15 (41 days ago)
  InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5)
  MarkForUpload: True
  ProcCmdline: gnome-control-center credentials
  SegvAnalysis:
   Segfault happened at: 0x7fda1e057059:mov0x18(%rbx),%r11d
   PC (0x7fda1e057059) ok
   source "0x18(%rbx)" (0x0018) not located in a known VMA region (needed 
readable region)!
   destination "%r11d" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: gnome-control-center
  StacktraceTop:
   ?? () from /usr/lib/libaccount-plugin-1.0.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libsignon-glib.so.1
   g_simple_async_result_complete () from 
/usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
   g_simple_async_result_complete () from 
/usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
  Title: gnome-control-center crashed with SIGSEGV in 
g_simple_async_result_complete()
  UpgradeStatus: Upgraded to raring on 2013-02-20 (36 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  usr_lib_gnome-control-center:
   activity-log-manager-control-center 0.9.4-0ubuntu6.1
   deja-dup25.5-0ubuntu1
   gnome-control-center-signon 0.1.5-0ubuntu1
   gnome-control-center-unity  1.2daily13.02.15-0ubuntu1
   indicator-datetime  12.10.3daily13.03.26-0ubuntu1

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

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

[Desktop-packages] [Bug 1112443] Re: gnome-control-center crashed with SIGSEGV in in ??()

[Sebastien Bacher]

The bug is old without recent report, closing. Better to open a new
report if there is still a similar issue in recent Ubuntu versions

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

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

Title:
  gnome-control-center crashed with SIGSEGV in  in ??()

Status in gnome-control-center package in Ubuntu:
  Invalid

Bug description:
  .

  ProblemType: Crash
  DistroRelease: Ubuntu 13.04
  Package: gnome-control-center 1:3.6.3-0ubuntu12
  Uname: Linux 3.1.10-9-nexus7 armv7l
  ApportVersion: 2.8-0ubuntu3
  Architecture: armhf
  Date: Fri Feb  1 12:52:19 2013
  ExecutablePath: /usr/bin/gnome-control-center
  MarkForUpload: True
  ProcCmdline: gnome-control-center --overview
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  Signal: 11
  SourcePackage: gnome-control-center
  StacktraceTop:
   ?? () from /usr/lib/libgnome-bluetooth.so.11
   g_type_instance_get_private () from 
/usr/lib/arm-linux-gnueabihf/libgobject-2.0.so.0
   ?? ()
   ?? ()
  Title: gnome-control-center crashed with SIGSEGV in 
g_type_instance_get_private()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  usr_lib_gnome-control-center:
   activity-log-manager-control-center 0.9.4-0ubuntu6.1
   deja-dup25.3-0ubuntu1
   gnome-control-center-signon 0.1.2bzr12.12.05-0ubuntu1
   gnome-control-center-unity  1.2-0ubuntu1
   indicator-datetime  12.10.3daily13.01.25-0ubuntu1

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

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

[Desktop-packages] [Bug 1155953] Re: [background]: gnome-control-center crashed with SIGSEGV in on_screenshot_finished()

[Sebastien Bacher]

The bug is old without recent report, closing. Better to open a new
report if there is still a similar issue in recent Ubuntu versions

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

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

Title:
  [background]: gnome-control-center crashed with SIGSEGV in
  on_screenshot_finished()

Status in gnome-control-center package in Ubuntu:
  Invalid

Bug description:
  I don't know.
  Maybe because I was in the guest account before.

  ProblemType: Crash
  DistroRelease: Ubuntu 13.04
  Package: gnome-control-center 1:3.6.3-0ubuntu15
  ProcVersionSignature: Ubuntu 3.8.0-12.21-generic 3.8.2
  Uname: Linux 3.8.0-12-generic x86_64
  ApportVersion: 2.9.1-0ubuntu1
  Architecture: amd64
  Date: Sat Mar 16 14:23:40 2013
  ExecutablePath: /usr/bin/gnome-control-center
  InstallationDate: Installed on 2011-10-21 (511 days ago)
  InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
  MarkForUpload: True
  ProcCmdline: gnome-control-center --overview
  SegvAnalysis:
   Segfault happened at: 0x7fc0c234f837:mov0x8(%r14),%rdi
   PC (0x7fc0c234f837) ok
   source "0x8(%r14)" (0xaab2) not located in a known VMA region 
(needed readable region)!
   destination "%rdi" ok
  SegvReason: reading unknown VMA
  Signal: 11
  SourcePackage: gnome-control-center
  StacktraceTop:
   ?? () from /usr/lib/control-center-1/panels/libbackground.so
   g_simple_async_result_complete () from 
/usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
   g_simple_async_result_complete () from 
/usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
  Title: [background]: gnome-control-center crashed with SIGSEGV in 
g_simple_async_result_complete()
  UpgradeStatus: Upgraded to raring on 2013-01-20 (54 days ago)
  UserGroups:
   
  usr_lib_gnome-control-center:
   activity-log-manager-control-center 0.9.4-0ubuntu6.1
   deja-dup25.5-0ubuntu1
   gnome-control-center-signon 0.1.2bzr12.12.05-0ubuntu1
   gnome-control-center-unity  1.2daily13.02.15-0ubuntu1
   indicator-datetime  12.10.3daily13.03.07-0ubuntu1

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

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

[Desktop-packages] [Bug 1162498] Re: gnome-control-center crashed with SIGSEGV in g_object_notify()

[Sebastien Bacher]

The bug is old without recent report, closing. Better to open a new
report if there is still a similar issue in recent Ubuntu versions

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

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

Title:
  gnome-control-center crashed with SIGSEGV in g_object_notify()

Status in gnome-control-center package in Ubuntu:
  Invalid

Bug description:
  Crashed when I was trying to set the repetition rate of the keyboard
  keys.

  ProblemType: Crash
  DistroRelease: Ubuntu 13.04
  Package: gnome-control-center 1:3.6.3-0ubuntu18
  ProcVersionSignature: Ubuntu 3.8.0-15.25-generic 3.8.4
  Uname: Linux 3.8.0-15-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.9.2-0ubuntu5
  Architecture: amd64
  Date: Sun Mar 31 11:31:57 2013
  ExecutablePath: /usr/bin/gnome-control-center
  InstallationDate: Installed on 2013-03-28 (2 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Alpha amd64 (20130328)
  MarkForUpload: True
  ProcCmdline: gnome-control-center --overview
  ProcEnviron:
   LANGUAGE=pt_BR:pt:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=pt_BR.UTF-8
   SHELL=/bin/bash
  SegvAnalysis:
   Segfault happened at: 0x7f480f5b1676 :   cmpq   
$0x50,(%rax)
   PC (0x7f480f5b1676) ok
   source "$0x50" ok
   destination "(%rax)" (0x0003) not located in a known VMA region (needed 
writable region)!
  SegvReason: writing NULL VMA
  Signal: 11
  SourcePackage: gnome-control-center
  StacktraceTop:
   g_object_notify () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   g_closure_invoke () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   g_signal_emit_valist () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   g_signal_emit () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
  Title: gnome-control-center crashed with SIGSEGV in g_object_notify()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  usr_lib_gnome-control-center:
   activity-log-manager-control-center 0.9.4-0ubuntu6.1
   deja-dup26.0-0ubuntu1
   gnome-control-center-signon 0.1.5-0ubuntu1
   gnome-control-center-unity  1.2daily13.02.15-0ubuntu1
   indicator-datetime  12.10.3daily13.03.26-0ubuntu1

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

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

[Desktop-packages] [Bug 1112435] Re: [Appearance - Behavior] "Restore Default behaviours" is not work correctly

[Sebastien Bacher]

The option described has been removed since which deprecates the bug

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

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

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

Title:
  [Appearance - Behavior] "Restore Default behaviours" is not work
  correctly

Status in gnome-control-center package in Ubuntu:
  Invalid

Bug description:
  I have tested Edubuntu amd64 (84a74c183faa75e3dfd831b57ec861a9
  *raring-dvd-amd64.iso 20130201), on live-usb-persistent.

  1) On System Settings > Appearance > Behavior I have clicked on "Enable 
workspace" and "Add show desktop icon to the launcher".
  2) I have clicked "Restore Default Behaviours".
  3) "Enable workspaces" is not selected, while "Add show desktop icon to the 
launcher" is selected.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: gnome-control-center 1:3.6.3-0ubuntu12
  ProcVersionSignature: Ubuntu 3.8.0-2.6-generic 3.8.0-rc4
  Uname: Linux 3.8.0-2-generic x86_64
  ApportVersion: 2.8-0ubuntu3
  Architecture: amd64
  CasperVersion: 1.330
  Date: Fri Feb  1 11:50:01 2013
  ExecutablePath: /usr/bin/gnome-control-center
  LiveMediaBuild: Edubuntu 13.04 "Raring Ringtail" - Alpha amd64 (20130201)
  MarkForUpload: True
  ProcEnviron:
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
   PATH=(custom, no user)
   LANG=en_US.UTF-8
  SourcePackage: gnome-control-center
  UpgradeStatus: No upgrade log present (probably fresh install)
  usr_lib_gnome-control-center:
   activity-log-manager-control-center 0.9.4-0ubuntu6.1
   deja-dup25.3-0ubuntu1
   gnome-control-center-signon 0.1.2bzr12.12.05-0ubuntu1
   gnome-control-center-unity  1.2-0ubuntu1
   indicator-datetime  12.10.3daily13.01.25-0ubuntu1

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

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

[Desktop-packages] [Bug 1162611] Re: gnome-control-center crashed with SIGSEGV in xcb_glx_get_string_string_length()

[Sebastien Bacher]

The bug is old without recent report, closing. Better to open a new
report if there is still a similar issue in recent Ubuntu versions

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

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

Title:
  gnome-control-center crashed with SIGSEGV in
  xcb_glx_get_string_string_length()

Status in gnome-control-center package in Ubuntu:
  Invalid

Bug description:
  I just upgraded from Quantal to Raring. I clicked on Details in the
  System-settings window and it crashed.

  ProblemType: Crash
  DistroRelease: Ubuntu 13.04
  Package: gnome-control-center 1:3.6.3-0ubuntu18
  ProcVersionSignature: Ubuntu 3.8.0-15.25-generic 3.8.4
  Uname: Linux 3.8.0-15-generic i686
  ApportVersion: 2.9.2-0ubuntu5
  Architecture: i386
  Date: Mon Apr  1 04:43:07 2013
  ExecutablePath: /usr/bin/gnome-control-center
  InstallationDate: Installed on 2013-03-15 (16 days ago)
  InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release i386 (20121017.2)
  MarkForUpload: True
  ProcCmdline: gnome-control-center background
  ProcEnviron:
   LANGUAGE=en_IN:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_IN
   SHELL=/bin/bash
  SegvAnalysis:
   Segfault happened at: 0xaab4cab4 :   
mov0xc(%eax),%eax
   PC (0xaab4cab4) ok
   source "0xc(%eax)" (0x000c) not located in a known VMA region (needed 
readable region)!
   destination "%eax" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: gnome-control-center
  StacktraceTop:
   xcb_glx_get_string_string_length () from 
/usr/lib/i386-linux-gnu/libxcb-glx.so.0
   __glXGetString () from /usr/lib/i386-linux-gnu/mesa/libGL.so.1
   ?? () from /usr/lib/i386-linux-gnu/mesa/libGL.so.1
   ?? () from /usr/lib/control-center-1/panels/libinfo.so
   g_type_create_instance () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0
  Title: [info]: gnome-control-center crashed with SIGSEGV in 
xcb_glx_get_string_string_length()
  UpgradeStatus: Upgraded to raring on 2013-03-31 (0 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  usr_lib_gnome-control-center:
   activity-log-manager-control-center 0.9.4-0ubuntu6.1
   deja-dup26.0-0ubuntu1
   gnome-control-center-signon 0.1.5-0ubuntu1
   gnome-control-center-unity  1.2daily13.02.15-0ubuntu1
   indicator-datetime  12.10.3daily13.03.26-0ubuntu1

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

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

[Desktop-packages] [Bug 983116] Re: [Component: Keyboard] HUD is not

[Sebastien Bacher]

Ubuntu moved to GNOME and there is no HUD option anymore in gcc

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

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

Title:
  [Component: Keyboard] HUD is  not 

Status in gnome-control-center package in Ubuntu:
  Invalid

Bug description:
  Little confusing description.
  g-c-c -> keyboard -> keyboard shortcuts -> launcher describes HUD as  
shortcut, it should be  or just  as in ccsm -> unity-plugin. 
(screenshots)

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: gnome-control-center 1:3.4.0-0ubuntu7
  ProcVersionSignature: Ubuntu 3.2.0-23.36-generic 3.2.14
  Uname: Linux 3.2.0-23-generic x86_64
  ApportVersion: 2.0.1-0ubuntu3
  Architecture: amd64
  Date: Mon Apr 16 16:23:07 2012
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Alpha amd64 
(20120204)
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-control-center
  UpgradeStatus: No upgrade log present (probably fresh install)
  usr_lib_gnome-control-center:
   activity-log-manager-control-center 0.9.4-0ubuntu3
   gnome-bluetooth 3.2.2-0ubuntu5
   indicator-datetime  0.3.94-0ubuntu1

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

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