date:20180502

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

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

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

Title:
  i915 driver issue in Ubuntu 18.04

Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  lspci -nnk | grep -iA2 vga
  00:02.0 VGA compatible controller [0300]: Intel Corporation 82945G/GZ 
Integrated Graphics Controller [8086:2772] (rev 02)
  Subsystem: Hewlett-Packard Company 82945G/GZ Integrated Graphics 
Controller [103c:302a]
  Kernel modules: i915, intelfb

  
  and

  xrandr 
  xrandr: Failed to get size of gamma for output default
  Screen 0: minimum 1024 x 768, current 1024 x 768, maximum 1024 x 768
  default connected primary 1024x768+0+0 0mm x 0mm
 1024x768  76.00*

  Output of sudo lshw -c display

  *-display UNCLAIMED   
 description: VGA compatible controller
 product: 82945G/GZ Integrated Graphics Controller
 vendor: Intel Corporation
 physical id: 2
 bus info: pci@:00:02.0
 version: 02
 width: 32 bits
 clock: 33MHz
 capabilities: msi pm vga_controller bus_master cap_list
 configuration: latency=0
 resources: memory:e200-e207 ioport:c000(size=8) 
memory:d000-dfff memory:e208-e20b memory:c-d

  I've tried solution 1 and solution 2 but no success.

  This issue occurred only after installing it, not when I choose 'Try
  without Installing', I don't need to set nomodeset in that case.

  Intel Graphics Update Tool shows:

  Checking if Intel graphics card available...
• checking for i915 module in /sys/module
• i915 module found
  Checking if Intel graphics card available... OK
  Retrieving information from 01.org...
• fetching https://download.01.org/gfx/ilg-config.cfg
• saving to /home/garden/.ilg-config
• fetched 1626 bytes
• fetched 9818 bytes
• fetched 12301 bytes
• looking up [Ubuntu bionic] configuration
  Retrieving information from 01.org... OK
  Checking distribution... Failed

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7
  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
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Tue May  1 17:16:20 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: I just need to know a workaround
  GraphicsCard:
   Intel Corporation 82945G/GZ Integrated Graphics Controller [8086:2772] (rev 
02) (prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company 82945G/GZ Integrated Graphics 
Controller [103c:302a]
  InstallationDate: Installed on 2018-05-01 (0 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  MachineType: Hewlett-Packard HP dx2080 MT(KS826PA)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_IN
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-20-generic 
root=UUID=7ec4f610-9b62-44f3-867d-01abd93de14d ro quiet splash nomodeset 
vt.handoff=1
  Renderer: Software
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  XorgConf:
   Section "Device"
Identifier "Intel Graphics"
Driver "intel"
Option "AccelMethod" "uxa"
   EndSection
  dmi.bios.date: 11/28/2007
  dmi.bios.vendor: Award Software International, Inc.
  dmi.bios.version: V1.03
  dmi.board.name: 0AD8h
  dmi.board.vendor: Board Manufacturer
  dmi.chassis.asset.tag: INA8100LFY
  dmi.chassis.type: 3
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrV1.03:bd11/28/2007:svnHewlett-Packard:pnHPdx2080MT(KS826PA):pvr:rvnBoardManufacturer:rn0AD8h:rvr:cvnHewlett-Packard:ct3:cvr:
  dmi.product.name: HP dx2080 MT(KS826PA)
  dmi.sys.vendor: Hewlett-Packard
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.91+git1804271336.50426f~oibaf~b
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.2~git1804301930.1c5f4f~oibaf~b
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.2~git1804301930.1c5f4f~oibaf~b
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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

-- 
Mailing list: https://launchpad.net/~desktop-packa

[Desktop-packages] [Bug 1721428] Re: Artful (17.10) Session logout after screen turned off

BTW, we have fixed many gnome-shell bugs with these symptoms recently in
Ubuntu 18.04. So please try 18.04 and log a new bug if you have any
problems.

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

Title:
  Artful (17.10) Session logout after screen turned off

Status in GNOME Shell:
  Unknown
Status in gnome-shell package in Ubuntu:
  Invalid
Status in mutter package in Ubuntu:
  Invalid

Bug description:
  Whenever I turn off my screen, the computer (a desktop PC) logs me out
  of my session.

  Here is a discussion thread with users of similar issue:
  
https://ubuntuforums.org/showthread.php?t=2372388&p=13694312&posted=1#post13694312

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

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

[Desktop-packages] [Bug 1721428] Re: Artful (17.10) Session logout after screen turned off

This bug is closed due to no response from the original reporter, so
please don't add further comments.

Everyone else should:

1. If using a release older than 18.04 then apply the workaround from
bug 994921 first.

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


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

Title:
  Artful (17.10) Session logout after screen turned off

Status in GNOME Shell:
  Unknown
Status in gnome-shell package in Ubuntu:
  Invalid
Status in mutter package in Ubuntu:
  Invalid

Bug description:
  Whenever I turn off my screen, the computer (a desktop PC) logs me out
  of my session.

  Here is a discussion thread with users of similar issue:
  
https://ubuntuforums.org/showthread.php?t=2372388&p=13694312&posted=1#post13694312

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

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

[Desktop-packages] [Bug 1720310] Re: unity-gnome-shell-migration.18.08.py crashed with signal 5 in g_object_new_valist() due to gnome-shell-extension-ubuntu-dock not installed

2018-05-02 Thread Didier Roche

** Description changed:

+ [Impact]
+ 
+  * People having this particular setup:
+- removed ubuntu-desktop metapackage from their system
+- upgrading from 16.04 to 18.04 (or previously to 17.10) by manually 
editing /etc/apt/sources.lists without using do-release-upgrade (which 
reinstalls ubuntu-desktop).
+ They end up with:
+ - no ubuntu-dock installed
+ - and consequentely, the settings migration script would trigger an apport 
dialog (crashing) due to lack of gsettings schema.
+  * Even if this is an unsupported case (people shouldn't cowboy sources.list 
and use our upgrader tools), we can easily prevent this crash, ignoring 
settings migration in such a case.
+ 
+ [Test Case]
+ 
+  1. Install 16.04
+  2. Remove ubuntu-desktop metapackage
+  3. Change your sources.list from "xenial" to "bionic"
+  4. apt update && apt full-upgrade
+  5. Reboot and log into a new session once upgrade is done.
+ -> you won't get the ubuntu-dock, but the session migration script shouldn't 
crash.
+ 
+ [Regression Potential]
+ 
+  * The script was crashing (even if there is no settings to migrate, so
+ it was a no-op). We prevents gsettings to segfault by guarding for
+ schema existence in the standard way.
+ 
+ --
+ 
  Upgrade...
  
  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: ubuntu-session 3.26.0-0ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3
  Uname: Linux 4.10.0-35-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Sep 29 08:15:13 2017
  ExecutablePath: 
/usr/share/session-migration/scripts/unity-gnome-shell-migration.18.08.py
  InstallationDate: Installed on 2017-09-25 (3 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  InterpreterPath: /usr/bin/python3.6
  ProcCmdline: /usr/bin/python3 
/usr/share/session-migration/scripts/unity-gnome-shell-migration.18.08.py
  ProcEnviron:
-  LANGUAGE=ru
-  PATH=(custom, user)
-  XDG_RUNTIME_DIR=
-  LANG=ru_RU.UTF-8
-  SHELL=/bin/bash
+  LANGUAGE=ru
+  PATH=(custom, user)
+  XDG_RUNTIME_DIR=
+  LANG=ru_RU.UTF-8
+  SHELL=/bin/bash
  Python3Details: /usr/bin/python3.6, Python 3.6.3rc1, python3-minimal, 
3.6.2-1ubuntu4
  PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 
2.7.14-2ubuntu1
  Signal: 5
  SourcePackage: gnome-session
  StacktraceTop:
-  ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
-  ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
-  g_object_new_valist () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
-  g_object_new () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
-  ffi_call_unix64 () from /usr/lib/x86_64-linux-gnu/libffi.so.6
+  ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
+  ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
+  g_object_new_valist () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
+  g_object_new () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
+  ffi_call_unix64 () from /usr/lib/x86_64-linux-gnu/libffi.so.6
  Title: unity-gnome-shell-migration.18.08.py crashed with signal 5 in 
g_object_new_valist()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

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

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

Title:
  unity-gnome-shell-migration.18.08.py crashed with signal 5 in
  g_object_new_valist() due to gnome-shell-extension-ubuntu-dock not
  installed

Status in gnome-session package in Ubuntu:
  Triaged
Status in gnome-session source package in Bionic:
  Triaged

Bug description:
  [Impact]

   * People having this particular setup:
 - removed ubuntu-desktop metapackage from their system
 - upgrading from 16.04 to 18.04 (or previously to 17.10) by manually 
editing /etc/apt/sources.lists without using do-release-upgrade (which 
reinstalls ubuntu-desktop).
  They end up with:
  - no ubuntu-dock installed
  - and consequentely, the settings migration script would trigger an apport 
dialog (crashing) due to lack of gsettings schema.
   * Even if this is an unsupported case (people shouldn't cowboy sources.list 
and use our upgrader tools), we can easily prevent this crash, ignoring 
settings migration in such a case.

  [Test Case]

   1. Install 16.04
   2. Remove ubuntu-desktop metapackage
   3. Change your sources.list from "xenial" to "bionic"
   4. apt update && apt full-upgrade
   5. Reboot and log into a new session once upgrade is done.
  -> you won't get the ubuntu-dock, but the session migration script shouldn't 
crash.

  [Regression Potential]

   * The script was crashing (even if there is no settings to migrate,
  so it was a no-op). We prevents gsettings to segfault by guarding for
  schema existence in the standard way.

  --

  Upg

[Desktop-packages] [Bug 1720310] Re: unity-gnome-shell-migration.18.08.py crashed with signal 5 in g_object_new_valist() due to gnome-shell-extension-ubuntu-dock not installed

2018-05-02 Thread Didier Roche

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

** Changed in: gnome-session (Ubuntu)
   Status: Confirmed => Triaged

** Changed in: gnome-session (Ubuntu Bionic)
 Assignee: (unassigned) => Didier Roche (didrocks)

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

Title:
  unity-gnome-shell-migration.18.08.py crashed with signal 5 in
  g_object_new_valist() due to gnome-shell-extension-ubuntu-dock not
  installed

Status in gnome-session package in Ubuntu:
  Triaged
Status in gnome-session source package in Bionic:
  Triaged

Bug description:
  [Impact]

   * People having this particular setup:
 - removed ubuntu-desktop metapackage from their system
 - upgrading from 16.04 to 18.04 (or previously to 17.10) by manually 
editing /etc/apt/sources.lists without using do-release-upgrade (which 
reinstalls ubuntu-desktop).
  They end up with:
  - no ubuntu-dock installed
  - and consequentely, the settings migration script would trigger an apport 
dialog (crashing) due to lack of gsettings schema.
   * Even if this is an unsupported case (people shouldn't cowboy sources.list 
and use our upgrader tools), we can easily prevent this crash, ignoring 
settings migration in such a case.

  [Test Case]

   1. Install 16.04
   2. Remove ubuntu-desktop metapackage
   3. Change your sources.list from "xenial" to "bionic"
   4. apt update && apt full-upgrade
   5. Reboot and log into a new session once upgrade is done.
  -> you won't get the ubuntu-dock, but the session migration script shouldn't 
crash.

  [Regression Potential]

   * The script was crashing (even if there is no settings to migrate,
  so it was a no-op). We prevents gsettings to segfault by guarding for
  schema existence in the standard way.

  --

  Upgrade...

  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: ubuntu-session 3.26.0-0ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3
  Uname: Linux 4.10.0-35-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Sep 29 08:15:13 2017
  ExecutablePath: 
/usr/share/session-migration/scripts/unity-gnome-shell-migration.18.08.py
  InstallationDate: Installed on 2017-09-25 (3 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  InterpreterPath: /usr/bin/python3.6
  ProcCmdline: /usr/bin/python3 
/usr/share/session-migration/scripts/unity-gnome-shell-migration.18.08.py
  ProcEnviron:
   LANGUAGE=ru
   PATH=(custom, user)
   XDG_RUNTIME_DIR=
   LANG=ru_RU.UTF-8
   SHELL=/bin/bash
  Python3Details: /usr/bin/python3.6, Python 3.6.3rc1, python3-minimal, 
3.6.2-1ubuntu4
  PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 
2.7.14-2ubuntu1
  Signal: 5
  SourcePackage: gnome-session
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   g_object_new_valist () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   g_object_new () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   ffi_call_unix64 () from /usr/lib/x86_64-linux-gnu/libffi.so.6
  Title: unity-gnome-shell-migration.18.08.py crashed with signal 5 in 
g_object_new_valist()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

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

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

[Desktop-packages] [Bug 1720310] Re: unity-gnome-shell-migration.18.08.py crashed with signal 5 in g_object_new_valist() due to gnome-shell-extension-ubuntu-dock not installed

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

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

Title:
  unity-gnome-shell-migration.18.08.py crashed with signal 5 in
  g_object_new_valist() due to gnome-shell-extension-ubuntu-dock not
  installed

Status in gnome-session package in Ubuntu:
  Triaged
Status in gnome-session source package in Bionic:
  Triaged

Bug description:
  [Impact]

   * People having this particular setup:
 - removed ubuntu-desktop metapackage from their system
 - upgrading from 16.04 to 18.04 (or previously to 17.10) by manually 
editing /etc/apt/sources.lists without using do-release-upgrade (which 
reinstalls ubuntu-desktop).
  They end up with:
  - no ubuntu-dock installed
  - and consequentely, the settings migration script would trigger an apport 
dialog (crashing) due to lack of gsettings schema.
   * Even if this is an unsupported case (people shouldn't cowboy sources.list 
and use our upgrader tools), we can easily prevent this crash, ignoring 
settings migration in such a case.

  [Test Case]

   1. Install 16.04
   2. Remove ubuntu-desktop metapackage
   3. Change your sources.list from "xenial" to "bionic"
   4. apt update && apt full-upgrade
   5. Reboot and log into a new session once upgrade is done.
  -> you won't get the ubuntu-dock, but the session migration script shouldn't 
crash.

  [Regression Potential]

   * The script was crashing (even if there is no settings to migrate,
  so it was a no-op). We prevents gsettings to segfault by guarding for
  schema existence in the standard way.

  --

  Upgrade...

  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: ubuntu-session 3.26.0-0ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3
  Uname: Linux 4.10.0-35-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Sep 29 08:15:13 2017
  ExecutablePath: 
/usr/share/session-migration/scripts/unity-gnome-shell-migration.18.08.py
  InstallationDate: Installed on 2017-09-25 (3 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  InterpreterPath: /usr/bin/python3.6
  ProcCmdline: /usr/bin/python3 
/usr/share/session-migration/scripts/unity-gnome-shell-migration.18.08.py
  ProcEnviron:
   LANGUAGE=ru
   PATH=(custom, user)
   XDG_RUNTIME_DIR=
   LANG=ru_RU.UTF-8
   SHELL=/bin/bash
  Python3Details: /usr/bin/python3.6, Python 3.6.3rc1, python3-minimal, 
3.6.2-1ubuntu4
  PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 
2.7.14-2ubuntu1
  Signal: 5
  SourcePackage: gnome-session
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   g_object_new_valist () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   g_object_new () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   ffi_call_unix64 () from /usr/lib/x86_64-linux-gnu/libffi.so.6
  Title: unity-gnome-shell-migration.18.08.py crashed with signal 5 in 
g_object_new_valist()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

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

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

[Desktop-packages] [Bug 1604036] Re: Upgrade printer-driver-ptouch to support Brother QL-570

** Tags added: bionic

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

Title:
  Upgrade printer-driver-ptouch to support Brother QL-570

Status in hwdata package in Ubuntu:
  Confirmed
Status in ptouch-driver package in Ubuntu:
  Fix Released
Status in usbutils package in Ubuntu:
  Confirmed
Status in hwdata source package in Xenial:
  New
Status in ptouch-driver source package in Xenial:
  Triaged
Status in usbutils source package in Xenial:
  New

Bug description:
  Please, upgrade printer-driver-ptouch to support Brother QL-570
  P-touch Label Printer. See https://bitbucket.org/philpem/printer-
  driver-ptouch/issues/2/negativeprint-and-cutmedia-jobend-doesnt
  (motivate maintainers of printer-driver-ptouch to bump their version
  number and release a version that supports QL-570) and also upgrade
  usbutils to include https://usb-ids.gowdy.us/read/UD/04f9/2028

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

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

[Desktop-packages] [Bug 1635951] Re: Remove libunity9 package dependency for pidgin

** Tags added: bionic

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

Title:
  Remove libunity9 package dependency for pidgin

Status in One Hundred Papercuts:
  Confirmed
Status in pidgin package in Ubuntu:
  Won't Fix

Bug description:
  All alternative flavor of Ubuntu don't use Unity.

  However, they can use Pidgin

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: pidgin 1:2.10.12-0ubuntu5.1
  ProcVersionSignature: Ubuntu 4.4.0-45.66-generic 4.4.21
  Uname: Linux 4.4.0-45-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: LXDE
  Date: Sun Oct 23 13:46:02 2016
  InstallationDate: Installed on 2016-04-02 (203 days ago)
  InstallationMedia: Lubuntu 16.04 LTS "Xenial Xerus" - Beta amd64 (20160323)
  SourcePackage: pidgin
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1670009] Re: Remove libunity9 package dependency for nautilus

** Tags added: 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/1670009

Title:
   Remove libunity9 package dependency for nautilus

Status in One Hundred Papercuts:
  Confirmed
Status in nautilus package in Ubuntu:
  Won't Fix

Bug description:
  Please, drop the dependency from nautilus on libunity9. There is no
  need for it and it unfairly forces non-Unity users to have Unity
  packages installed. If there is a reason for it, create nautilus-unity
  and manage it there. Or downgrade the dependency to recommended or
  suggested.

  See also https://bugs.launchpad.net/ubuntu/+source/pidgin/+bug/1635951
  and https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1669997

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

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

[Desktop-packages] [Bug 1602386] Re: Config directory ~/.purple should be ~/.config/purple

** Tags added: bionic

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

Title:
  Config directory ~/.purple should be ~/.config/purple

Status in One Hundred Papercuts:
  Confirmed
Status in pidgin package in Ubuntu:
  Confirmed

Bug description:
  Personal config directory ~/.purple should be ~/.config/purple

  Please implement this change in such way that for the next x versions
  of this package any old ~/.purple directories are moved or merged or a
  notification is made to the end-user when there is a conflict.

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

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

[Desktop-packages] [Bug 1767993] Re: X11 freezing/low resolution on N3150 intel graphics

2018-05-02 Thread Hadmut Danisch

This is definitely not correct.


a) the problem is not that I can't login. The problem is, the the screen 
remains black and freezes after login when nomodeset is not given. 


b) I had the same problem with the same machine under 17.04 and 17.10, but 
giving nomodeset solved the problem, the x server then came up with high 
resolution. So it is wrong to claim that nomodeset causes the Xserver to remain 
in vesa mode. 

c) logging in via ssh will take some time because I don't have a second
machine here on my desk, I have to get a second computer first. Although
I'm more than willing to blame systemd for any sort of problem, I'm not
sure whether systemd would explain resolution problems.

d) Would be easier if the ubuntu team fixed the recovery mode that's not
working under 18.04.

e) Once upon a time (10-20 years ago) X servers used to have a
-probeonly option to analyze and solve that sort of problem.

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

Title:
  X11 freezing/low resolution on N3150 intel graphics

Status in xorg-server package in Ubuntu:
  Incomplete

Bug description:
  Hi,
  I just installed a fresh 18.04 on an ASRock beebox N3150 machine.

  The regular ubuntu desktop installer hanged after entering X11 mode,
  machine froze.

  I then used Lubuntu alternate installer with the console based
  installation, which worked without any problem.

  But after rebooting the system again hung after the graphical login
  prompt.

  I then changed the boot options in /etc/default/grub to give the
  kernel the options nosplash nomodeset and to leave the system in
  console mode (I had similar experiences with former ubuntu versions on
  that machine where X11 did not start when the mode had been set by
  console.)

  
  Now X11 works, but comes up in vesa mode (1024x768) only.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xserver-xorg-core 2:1.19.6-1ubuntu4
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: LXDE
  Date: Mon Apr 30 12:25:09 2018
  InstallationDate: Installed on 2018-04-30 (0 days ago)
  InstallationMedia: Lubuntu 18.04 LTS "Bionic Beaver" - Release amd64 
(20180426)
  SourcePackage: xorg-server
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1751252] Re: [regression] ubiquity crashed in debconf.py:104 with ValueError: invalid literal for int() with base 10: ''

Possibly relevant to permissions: The uid of this process changed from
'root' in 17.10 (where it works), to 'ubuntu' in 18.04 (where it doesn't
work).

ubuntu4468 17.8  1.2 502716 97352 tty1 Sl+  08:17   0:01
/usr/bin/python3 /usr/lib/ubiquity/bin/ubiquity gtk_ui

In both cases the Xorg process is running as 'ubuntu'.

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

Title:
  [regression] ubiquity crashed in debconf.py:104 with ValueError:
  invalid literal for int() with base 10: ''

Status in OEM Priority Project:
  Triaged
Status in glib2.0 package in Ubuntu:
  Incomplete
Status in ubiquity package in Ubuntu:
  Triaged
Status in glib2.0 source package in Bionic:
  Incomplete
Status in ubiquity source package in Bionic:
  Triaged

Bug description:
  The Ubuntu installer crashes on hiDPI machines (QHD/UHD etc). Although
  it was working some weeks/months ago, so this is a recent regression.

  ---

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

  ---

  WORKAROUND:

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

  ---

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

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

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

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

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

[Desktop-packages] [Bug 1767993] Re: Lubuntu: X11 freezing/low resolution on N3150 intel graphics

** Summary changed:

- X11 freezing/low resolution on N3150 intel graphics
+ Lubuntu: X11 freezing/low resolution on N3150 intel graphics

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

Title:
  Lubuntu: X11 freezing/low resolution on N3150 intel graphics

Status in xorg-server package in Ubuntu:
  Incomplete

Bug description:
  Hi,
  I just installed a fresh 18.04 on an ASRock beebox N3150 machine.

  The regular ubuntu desktop installer hanged after entering X11 mode,
  machine froze.

  I then used Lubuntu alternate installer with the console based
  installation, which worked without any problem.

  But after rebooting the system again hung after the graphical login
  prompt.

  I then changed the boot options in /etc/default/grub to give the
  kernel the options nosplash nomodeset and to leave the system in
  console mode (I had similar experiences with former ubuntu versions on
  that machine where X11 did not start when the mode had been set by
  console.)

  
  Now X11 works, but comes up in vesa mode (1024x768) only.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xserver-xorg-core 2:1.19.6-1ubuntu4
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: LXDE
  Date: Mon Apr 30 12:25:09 2018
  InstallationDate: Installed on 2018-04-30 (0 days ago)
  InstallationMedia: Lubuntu 18.04 LTS "Bionic Beaver" - Release amd64 
(20180426)
  SourcePackage: xorg-server
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1767784] Re: [regression] output device not recognized anymore since update 1:8.0-0ubuntu3.9

2018-05-02 Thread Hui Wang

** Description changed:

- Since the update 1:8.0-0ubuntu3.8 to 1:8.0-0ubuntu3.9 , pulseaudio is
- not showing anymore my soundcard.
+ SRU Document:
+ 
+ [Impact]
+ 
+ The 1:8.0-0ubuntu3.9 introduced a new problem on the machines which do
+ not have internal speaker on them. With the 1:8.0-0ubuntu3.8, even there
+ is no internal speaker and nothing plugged in the audio jack, the
+ profile is still set available, then the active profile is analog-
+ stereo; while with the 1:8.0-0ubuntu3.9, the profile is set to
+ unavailable, and the active profile is off, after users plug sth in the
+ audio jack, the active profile will not switch automatically, need users
+ to switch manually, this change is unfriendly to users.
+ 
+ [Test Case]
+ 
+ On the machines without internal speaker, open sound-setting and check
+ if there is some output devices in the UI, and play sound from the UI.
+ Under 1:8.0-0ubuntu3.9 there is no output device, and can't play sound;
+ under 1:8.0-0ubuntu3.8 there is output device, and can play sound.
+ 
+ [Regression Potential]
+ 
+ This is a revert, after reverting, the content of pulseaudio is exactly
+ same as 1:8.0-0ubuntu3.8
+ 
+ [Other Info]
+ 
+ none
+ 
+ 
+ Since the update 1:8.0-0ubuntu3.8 to 1:8.0-0ubuntu3.9 , pulseaudio is not 
showing anymore my soundcard.
  
  https://launchpad.net/ubuntu/+source/pulseaudio/1:8.0-0ubuntu3.9
  
  The command "pacmd list-sinks" only shows a dummy output
  
  When running on a fresh install of ubuntu 16.04, the sound is ok.
  When updating the install with locking the following files to version 
1:8.0-0ubuntu3 the sound keeps working:
  libpulse0:amd64
  libpulse-mainloop-glib0:amd64
  libpulse-dev:amd64
  pulseaudio-module-x11:amd64
  pulseaudio-module-bluetooth:amd64
  pulseaudio-utils:amd64
  
  When updating to 1:8.0-0ubuntu3.9, I just get a "dummy output".
  
  I tried running the following versions of Ubuntu (live usb), and get the same 
issue (no need to update to get the problem)
  17.04
  17.10
  18.04
  
  I attached the result of command "pactl list"
  I have also generated logs during the boot but I don't know how to attach 
multiple files

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

Title:
  [regression] output device not recognized anymore since update
  1:8.0-0ubuntu3.9

Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  SRU Document:

  [Impact]

  The 1:8.0-0ubuntu3.9 introduced a new problem on the machines which do
  not have internal speaker on them. With the 1:8.0-0ubuntu3.8, even
  there is no internal speaker and nothing plugged in the audio jack,
  the profile is still set available, then the active profile is analog-
  stereo; while with the 1:8.0-0ubuntu3.9, the profile is set to
  unavailable, and the active profile is off, after users plug sth in
  the audio jack, the active profile will not switch automatically, need
  users to switch manually, this change is unfriendly to users.

  [Test Case]

  On the machines without internal speaker, open sound-setting and check
  if there is some output devices in the UI, and play sound from the UI.
  Under 1:8.0-0ubuntu3.9 there is no output device, and can't play
  sound; under 1:8.0-0ubuntu3.8 there is output device, and can play
  sound.

  [Regression Potential]

  This is a revert, after reverting, the content of pulseaudio is
  exactly same as 1:8.0-0ubuntu3.8

  [Other Info]

  none

  
  Since the update 1:8.0-0ubuntu3.8 to 1:8.0-0ubuntu3.9 , pulseaudio is not 
showing anymore my soundcard.

  https://launchpad.net/ubuntu/+source/pulseaudio/1:8.0-0ubuntu3.9

  The command "pacmd list-sinks" only shows a dummy output

  When running on a fresh install of ubuntu 16.04, the sound is ok.
  When updating the install with locking the following files to version 
1:8.0-0ubuntu3 the sound keeps working:
  libpulse0:amd64
  libpulse-mainloop-glib0:amd64
  libpulse-dev:amd64
  pulseaudio-module-x11:amd64
  pulseaudio-module-bluetooth:amd64
  pulseaudio-utils:amd64

  When updating to 1:8.0-0ubuntu3.9, I just get a "dummy output".

  I tried running the following versions of Ubuntu (live usb), and get the same 
issue (no need to update to get the problem)
  17.04
  17.10
  18.04

  I attached the result of command "pactl list"
  I have also generated logs during the boot but I don't know how to attach 
multiple files

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

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

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

2018-05-02 Thread pabro...@gmail.com

Just an update, I was in a different office location today using WPA2 / PEAP 
and wifi connected right away. Same business, NW engineers tell me 
infrastructure is exactly the same in both locations - so mystery - phone 
Android connected perfectly but laptop did not (in other building)!
So pity the assignee as it maybe tricky to replicate.

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

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

Status in network-manager package in Ubuntu:
  Confirmed

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

  Possible gnome-shell integration issue.

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

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

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

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

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

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

  [/code]

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

  Connect to network.

  5)
  Logs (syslog/kernel)

  Core moments:

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

  and ..

[Desktop-packages] [Bug 1756506] Re: snd_hda_intel module rejected by new kernel with retpoline

2018-05-02 Thread Chaim Zax

Please consider my remark above a workaround. It will load your kernel
module, but it also exposes a kernel vulnerability to your system by
allowing a non repoline compiled module to load.

See https://patchwork.kernel.org/patch/10161531/ for more information.

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

Title:
  snd_hda_intel module rejected by new kernel with retpoline

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

Bug description:
  After a routine software update (which updated the kernel) alsa
  recognises no sound card although lspci reports an audio device: Audio
  device: Intel Corporation 8 Series HD Audio Controller (rev 04).

  $ uname -a
  Linux 3.13.0-143-generic #192-Ubuntu SMP Tue Feb 27 10:45:36 UTC 2018 x86_64 
x86_64 x86_64 GNU/Linux

  $ aplay -l
  aplay: device_list:268: no soundcards found...

  $ dmesg | grep snd
  [4.794976] snd_hda_core: version magic '3.13.0-143-generic SMP mod_unload 
modversions ' should be '3.13.0-143-generic SMP mod_unload modversions 
retpoline '

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

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

[Desktop-packages] [Bug 1751252] Re: [regression] ubiquity crashed in debconf.py:104 with ValueError: invalid literal for int() with base 10: ''

Getting closer. It's this failing in the Xorg process:

/* The attach was performed with root privs. We must
 * do manual checking of access rights for the credentials
 * of the client */

if (shm_access(client, &(SHM_PERM(buf)), stuff->readOnly) == -1) {
shmdt(shmdesc->addr);
free(shmdesc);
return BadAccess;
}

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

Title:
  [regression] ubiquity crashed in debconf.py:104 with ValueError:
  invalid literal for int() with base 10: ''

Status in OEM Priority Project:
  Triaged
Status in glib2.0 package in Ubuntu:
  Incomplete
Status in ubiquity package in Ubuntu:
  Triaged
Status in glib2.0 source package in Bionic:
  Incomplete
Status in ubiquity source package in Bionic:
  Triaged

Bug description:
  The Ubuntu installer crashes on hiDPI machines (QHD/UHD etc). Although
  it was working some weeks/months ago, so this is a recent regression.

  ---

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

  ---

  WORKAROUND:

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

  ---

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

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

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

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

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

[Desktop-packages] [Bug 1536158] Re: Upgrade to 1.1.1 that was released in March 2016

If yes, than this bug can be closed.

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

Title:
  Upgrade to 1.1.1 that was released in March 2016

Status in alsa-driver package in Ubuntu:
  Confirmed
Status in alsa-driver-2.6.28-12 package in Ubuntu:
  Confirmed

Bug description:
  Please, upgrade to 1.1.1 that was released in March 2016, see
  http://www.alsa-project.org/main/index.php/Changes_v1.1.0_v1.1.1

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

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

[Desktop-packages] [Bug 1767784] Re: [regression] output device not recognized anymore since update 1:8.0-0ubuntu3.9

2018-05-02 Thread Hui Wang

@Sponsor team,

Please help submit the build request to the queue.

thx.


** Patch added: "pulseaudio_8.0-0ubuntu3.10.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1767784/+attachment/5131910/+files/pulseaudio_8.0-0ubuntu3.10.debdiff

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

Title:
  [regression] output device not recognized anymore since update
  1:8.0-0ubuntu3.9

Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  SRU Document:

  [Impact]

  The 1:8.0-0ubuntu3.9 introduced a new problem on the machines which do
  not have internal speaker on them. With the 1:8.0-0ubuntu3.8, even
  there is no internal speaker and nothing plugged in the audio jack,
  the profile is still set available, then the active profile is analog-
  stereo; while with the 1:8.0-0ubuntu3.9, the profile is set to
  unavailable, and the active profile is off, after users plug sth in
  the audio jack, the active profile will not switch automatically, need
  users to switch manually, this change is unfriendly to users.

  [Test Case]

  On the machines without internal speaker, open sound-setting and check
  if there is some output devices in the UI, and play sound from the UI.
  Under 1:8.0-0ubuntu3.9 there is no output device, and can't play
  sound; under 1:8.0-0ubuntu3.8 there is output device, and can play
  sound.

  [Regression Potential]

  This is a revert, after reverting, the content of pulseaudio is
  exactly same as 1:8.0-0ubuntu3.8

  [Other Info]

  none

  
  Since the update 1:8.0-0ubuntu3.8 to 1:8.0-0ubuntu3.9 , pulseaudio is not 
showing anymore my soundcard.

  https://launchpad.net/ubuntu/+source/pulseaudio/1:8.0-0ubuntu3.9

  The command "pacmd list-sinks" only shows a dummy output

  When running on a fresh install of ubuntu 16.04, the sound is ok.
  When updating the install with locking the following files to version 
1:8.0-0ubuntu3 the sound keeps working:
  libpulse0:amd64
  libpulse-mainloop-glib0:amd64
  libpulse-dev:amd64
  pulseaudio-module-x11:amd64
  pulseaudio-module-bluetooth:amd64
  pulseaudio-utils:amd64

  When updating to 1:8.0-0ubuntu3.9, I just get a "dummy output".

  I tried running the following versions of Ubuntu (live usb), and get the same 
issue (no need to update to get the problem)
  17.04
  17.10
  18.04

  I attached the result of command "pactl list"
  I have also generated logs during the boot but I don't know how to attach 
multiple files

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

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

[Desktop-packages] [Bug 1767784] Re: [regression] output device not recognized anymore since update 1:8.0-0ubuntu3.9

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

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

Title:
  [regression] output device not recognized anymore since update
  1:8.0-0ubuntu3.9

Status in pulseaudio package in Ubuntu:
  In Progress

Bug description:
  SRU Document:

  [Impact]

  The 1:8.0-0ubuntu3.9 introduced a new problem on the machines which do
  not have internal speaker on them. With the 1:8.0-0ubuntu3.8, even
  there is no internal speaker and nothing plugged in the audio jack,
  the profile is still set available, then the active profile is analog-
  stereo; while with the 1:8.0-0ubuntu3.9, the profile is set to
  unavailable, and the active profile is off, after users plug sth in
  the audio jack, the active profile will not switch automatically, need
  users to switch manually, this change is unfriendly to users.

  [Test Case]

  On the machines without internal speaker, open sound-setting and check
  if there is some output devices in the UI, and play sound from the UI.
  Under 1:8.0-0ubuntu3.9 there is no output device, and can't play
  sound; under 1:8.0-0ubuntu3.8 there is output device, and can play
  sound.

  [Regression Potential]

  This is a revert, after reverting, the content of pulseaudio is
  exactly same as 1:8.0-0ubuntu3.8

  [Other Info]

  none

  
  Since the update 1:8.0-0ubuntu3.8 to 1:8.0-0ubuntu3.9 , pulseaudio is not 
showing anymore my soundcard.

  https://launchpad.net/ubuntu/+source/pulseaudio/1:8.0-0ubuntu3.9

  The command "pacmd list-sinks" only shows a dummy output

  When running on a fresh install of ubuntu 16.04, the sound is ok.
  When updating the install with locking the following files to version 
1:8.0-0ubuntu3 the sound keeps working:
  libpulse0:amd64
  libpulse-mainloop-glib0:amd64
  libpulse-dev:amd64
  pulseaudio-module-x11:amd64
  pulseaudio-module-bluetooth:amd64
  pulseaudio-utils:amd64

  When updating to 1:8.0-0ubuntu3.9, I just get a "dummy output".

  I tried running the following versions of Ubuntu (live usb), and get the same 
issue (no need to update to get the problem)
  17.04
  17.10
  18.04

  I attached the result of command "pactl list"
  I have also generated logs during the boot but I don't know how to attach 
multiple files

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

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

[Desktop-packages] [Bug 1751252] Re: [regression] ubiquity crashed in debconf.py:104 with ValueError: invalid literal for int() with base 10: ''

** Changed in: glib2.0 (Ubuntu)
   Status: Incomplete => Invalid

** Changed in: glib2.0 (Ubuntu Bionic)
   Status: Incomplete => Invalid

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

Title:
  [regression] ubiquity crashed in debconf.py:104 with ValueError:
  invalid literal for int() with base 10: ''

Status in OEM Priority Project:
  Triaged
Status in glib2.0 package in Ubuntu:
  Invalid
Status in ubiquity package in Ubuntu:
  Triaged
Status in glib2.0 source package in Bionic:
  Invalid
Status in ubiquity source package in Bionic:
  Triaged

Bug description:
  The Ubuntu installer crashes on hiDPI machines (QHD/UHD etc). Although
  it was working some weeks/months ago, so this is a recent regression.

  ---

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

  ---

  WORKAROUND:

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

  ---

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

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

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

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

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

[Desktop-packages] [Bug 1768232] Re: i915 driver issue in Ubuntu 18.04

2018-05-02 Thread Tarik GRABA

Same thing here with a Dell Latitude E6540 (i5-4210M CPU)

`lspci -v` returns :

00:02.0 VGA compatible controller: Intel Corporation 4th Gen Core Processor 
Integrated Graphics Controller (rev 06) (prog-if 00 [VGA controller])
Subsystem: Dell 4th Gen Core Processor Integrated Graphics Controller
Flags: bus master, fast devsel, latency 0, IRQ 11
Memory at f580 (64-bit, non-prefetchable) [size=4M]
Memory at e000 (64-bit, prefetchable) [size=256M]
I/O ports at f000 [size=64]
[virtual] Expansion ROM at 000c [disabled] [size=128K]
Capabilities: [90] MSI: Enable- Count=1/1 Maskable- 64bit-
Capabilities: [d0] Power Management version 2
Capabilities: [a4] PCI Advanced Features

and sudo lshw -c display ~
  *-display UNCLAIMED
   description: VGA compatible controller
   product: 4th Gen Core Processor Integrated Graphics Controller
   vendor: Intel Corporation
   physical id: 2
   bus info: pci@:00:02.0
   version: 06
   width: 64 bits
   clock: 33MHz
   capabilities: msi pm vga_controller bus_master cap_list
   configuration: latency=0
   resources: memory:f580-f5bf memory:e000-efff 
ioport:f000(size=64) memory:c-d

The xorg intel package is installed:

Package: xserver-xorg-video-intel
Version: 2:2.99.917+git20171229-1

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

Title:
  i915 driver issue in Ubuntu 18.04

Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  lspci -nnk | grep -iA2 vga
  00:02.0 VGA compatible controller [0300]: Intel Corporation 82945G/GZ 
Integrated Graphics Controller [8086:2772] (rev 02)
  Subsystem: Hewlett-Packard Company 82945G/GZ Integrated Graphics 
Controller [103c:302a]
  Kernel modules: i915, intelfb

  
  and

  xrandr 
  xrandr: Failed to get size of gamma for output default
  Screen 0: minimum 1024 x 768, current 1024 x 768, maximum 1024 x 768
  default connected primary 1024x768+0+0 0mm x 0mm
 1024x768  76.00*

  Output of sudo lshw -c display

  *-display UNCLAIMED   
 description: VGA compatible controller
 product: 82945G/GZ Integrated Graphics Controller
 vendor: Intel Corporation
 physical id: 2
 bus info: pci@:00:02.0
 version: 02
 width: 32 bits
 clock: 33MHz
 capabilities: msi pm vga_controller bus_master cap_list
 configuration: latency=0
 resources: memory:e200-e207 ioport:c000(size=8) 
memory:d000-dfff memory:e208-e20b memory:c-d

  I've tried solution 1 and solution 2 but no success.

  This issue occurred only after installing it, not when I choose 'Try
  without Installing', I don't need to set nomodeset in that case.

  Intel Graphics Update Tool shows:

  Checking if Intel graphics card available...
• checking for i915 module in /sys/module
• i915 module found
  Checking if Intel graphics card available... OK
  Retrieving information from 01.org...
• fetching https://download.01.org/gfx/ilg-config.cfg
• saving to /home/garden/.ilg-config
• fetched 1626 bytes
• fetched 9818 bytes
• fetched 12301 bytes
• looking up [Ubuntu bionic] configuration
  Retrieving information from 01.org... OK
  Checking distribution... Failed

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7
  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
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Tue May  1 17:16:20 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: I just need to know a workaround
  GraphicsCard:
   Intel Corporation 82945G/GZ Integrated Graphics Controller [8086:2772] (rev 
02) (prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company 82945G/GZ Integrated Graphics 
Controller [103c:302a]
  InstallationDate: Installed on 2018-05-01 (0 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  MachineType: Hewlett-Packard HP dx2080 MT(KS826PA)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_IN
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-20-generic 
root=UUID=7ec4f610-9b62-44f3-867d-01abd93de14d ro quiet splash nomodeset 
vt.handoff=1
  Renderer: Software
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  XorgConf:
   Section "Device"
Identifier "Intel Graphics"
Driver "intel"
Option "AccelMethod" "uxa"
   EndSection
  dmi.bios.date: 11/28/2007
  dmi.bios.vendor: Award

[Desktop-packages] [Bug 1765390] Re: printer settings: add switch for disable autodetect and add

2018-05-02 Thread AdlerHorst

Sorry for that. I only described the Problem with the Printer
Concept/Workflow that is used in Ubuntu. In my opinion this is one
Issue, I'm not able to get what is working in Background and what is
working how in Background. I'm not familiar with the responsibility in
the deep of your developing. In my opinion I don't have to. I barley
able to manage to report in this strange and absolute not intuitive Web
surface (see also [Bug 1765667] ). I like Ubuntu, but not that much that
I would learn to develop some apps. So please do this for me. I'm
wondering also that you allow accepting Bugs to this package but are not
able to send it further to the correct address. Maybe there is a need of
a Feature Request for a better Work-flow in this reporting tool 😉 .

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

Title:
  printer settings: add switch for disable autodetect and add

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

Bug description:
  First and most important problem: I miss a switch in the printer
  settings to disable automatic detection and adding.

  I have problems on the VM in the company, because after system startup
  masses of printer messages appear and annoy me. I also have the
  problem that I am no longer able to find the printer I would need in
  the whole series of other unwanted printers. It would be easier if I
  only had to use the default printer, but unfortunately this is not the
  case.

  Another problem is adding a printer:
  It is easy to obtain the IP address of the printer. In the Add dialog there 
is a text in the search bar that says that I could insert an IP address. But 
that doesn't work. I need to go to "additional printer settings". Here I can 
add an IP address, but it must be an address starting with "ipp://"? Why do I 
have to do this? IP address is IP address, The program should find the protocol 
that it needs itself!

  Then I have to choose HPLIB and two AppSocket.
  For a printer that wasn't supported, I first had to enter the printer details 
and scroll through a shitty long list of printers and research that a Cannon iR 
is a Cannon Image Runner.
  In the end I had to download a ppd file from canon. (This was an adventure of 
its own, which has nothing to do with Linux). Now I have a printer that works 
and has been renamed with special text to get it to the top of the big list of 
unwanted printers in the system.

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

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

[Desktop-packages] [Bug 1716409] Re: Unable to install flatpakref on Ubuntu artful

2018-05-02 Thread Ads20000

This bug seems to have been re-introduced in Ubuntu 18.04 (GNOME
Software 3.28.1-0ubuntu4), should I file a new bug or re-open this one?

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

Title:
  Unable to install flatpakref on Ubuntu artful

Status in gnome-software package in Ubuntu:
  Fix Released
Status in gnome-software source package in Artful:
  Triaged

Bug description:
  I saw a news article with a link to install a flatpak.

  http://www.omgubuntu.co.uk/2017/09/download-pithos-pandora-app-1-4

  I clicked the link expecting to be able to install the flatpak, but
  the experience appears broken. I'm on an up to date Artful install

  What I did was:-

  Click on http://www.omgubuntu.co.uk/2017/09/download-pithos-pandora-app-1-4
  Click the flathub link:- 
https://flathub.org/repo/appstream/io.github.Pithos.flatpakref
  This downloaded the flatpakref file.
  I clicked the file in my browser, nothing happened

  I then tried finding the file in nautilus and double clicked it.
  GNOME Software launched and presented an error "Don't know how to handle 
'file:///home/alan/Downloads/io.github.Pithos.flatpakref' (see screenshot).

  If I search for pithos in GNOME Software I am able to find the older
  version from the deb repo, but not the newer version from flathub.

  Do we not support flatpak/flathub out of the box? Or is my system
  uniquely hosed?

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

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

[Desktop-packages] [Bug 1768448] Re: Don't use snaps for default system packages

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

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

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

Title:
  Don't use snaps for default system packages

Status in gnome-software package in Ubuntu:
  Opinion

Bug description:
  In a fresh install, standard applications like gnome-calculator and 
gnome-system-monitor are installed as snaps.  This results in a plethora of 
mounted loopback devices for basically nothing.  Never mind the slow 
application startup times (seconds for gnome-system-monitor on a Ryzen 1700 
with 32GB RAM and a Samsung EVO 960 on an M.2 interface).
  Removing the snaps and going back to deb packages, the performance issues go 
away.

  I can understand using snaps for third-party commercial software, but
  for the base system, the default debian package manager has served us
  well.  I consider pushing snaps for default gnome applications a bug,
  and mismanagement of the system.

  This does not happen on an upgraded Ubuntu (from 16.04LTS).  Snap is
  there, with no applications installed.  That's how the default should
  be.

  

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

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

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

[Desktop-packages] [Bug 1767784] Re: [regression] output device not recognized anymore since update 1:8.0-0ubuntu3.9

I've sponsored the update

** Changed in: pulseaudio (Ubuntu)
   Status: In Progress => Fix Committed

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

Title:
  [regression] output device not recognized anymore since update
  1:8.0-0ubuntu3.9

Status in pulseaudio package in Ubuntu:
  Fix Committed
Status in pulseaudio source package in Xenial:
  Fix Committed

Bug description:
  SRU Document:

  [Impact]

  The 1:8.0-0ubuntu3.9 introduced a new problem on the machines which do
  not have internal speaker on them. With the 1:8.0-0ubuntu3.8, even
  there is no internal speaker and nothing plugged in the audio jack,
  the profile is still set available, then the active profile is analog-
  stereo; while with the 1:8.0-0ubuntu3.9, the profile is set to
  unavailable, and the active profile is off, after users plug sth in
  the audio jack, the active profile will not switch automatically, need
  users to switch manually, this change is unfriendly to users.

  [Test Case]

  On the machines without internal speaker, open sound-setting and check
  if there is some output devices in the UI, and play sound from the UI.
  Under 1:8.0-0ubuntu3.9 there is no output device, and can't play
  sound; under 1:8.0-0ubuntu3.8 there is output device, and can play
  sound.

  [Regression Potential]

  This is a revert, after reverting, the content of pulseaudio is
  exactly same as 1:8.0-0ubuntu3.8

  [Other Info]

  none

  
  Since the update 1:8.0-0ubuntu3.8 to 1:8.0-0ubuntu3.9 , pulseaudio is not 
showing anymore my soundcard.

  https://launchpad.net/ubuntu/+source/pulseaudio/1:8.0-0ubuntu3.9

  The command "pacmd list-sinks" only shows a dummy output

  When running on a fresh install of ubuntu 16.04, the sound is ok.
  When updating the install with locking the following files to version 
1:8.0-0ubuntu3 the sound keeps working:
  libpulse0:amd64
  libpulse-mainloop-glib0:amd64
  libpulse-dev:amd64
  pulseaudio-module-x11:amd64
  pulseaudio-module-bluetooth:amd64
  pulseaudio-utils:amd64

  When updating to 1:8.0-0ubuntu3.9, I just get a "dummy output".

  I tried running the following versions of Ubuntu (live usb), and get the same 
issue (no need to update to get the problem)
  17.04
  17.10
  18.04

  I attached the result of command "pactl list"
  I have also generated logs during the boot but I don't know how to attach 
multiple files

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

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

[Desktop-packages] [Bug 1767784] Re: [regression] output device not recognized anymore since update 1:8.0-0ubuntu3.9

2018-05-02 Thread Steve Langasek

Hello Flavien, or anyone else affected,

Accepted pulseaudio into xenial-proposed. The package will build now and
be available at
https://launchpad.net/ubuntu/+source/pulseaudio/1:8.0-0ubuntu3.10 in a
few hours, and then in the -proposed repository.

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

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

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

** Changed in: pulseaudio (Ubuntu Xenial)
   Status: New => Fix Committed

** Tags added: verification-needed verification-needed-xenial

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

Title:
  [regression] output device not recognized anymore since update
  1:8.0-0ubuntu3.9

Status in pulseaudio package in Ubuntu:
  Fix Committed
Status in pulseaudio source package in Xenial:
  Fix Committed

Bug description:
  SRU Document:

  [Impact]

  The 1:8.0-0ubuntu3.9 introduced a new problem on the machines which do
  not have internal speaker on them. With the 1:8.0-0ubuntu3.8, even
  there is no internal speaker and nothing plugged in the audio jack,
  the profile is still set available, then the active profile is analog-
  stereo; while with the 1:8.0-0ubuntu3.9, the profile is set to
  unavailable, and the active profile is off, after users plug sth in
  the audio jack, the active profile will not switch automatically, need
  users to switch manually, this change is unfriendly to users.

  [Test Case]

  On the machines without internal speaker, open sound-setting and check
  if there is some output devices in the UI, and play sound from the UI.
  Under 1:8.0-0ubuntu3.9 there is no output device, and can't play
  sound; under 1:8.0-0ubuntu3.8 there is output device, and can play
  sound.

  [Regression Potential]

  This is a revert, after reverting, the content of pulseaudio is
  exactly same as 1:8.0-0ubuntu3.8

  [Other Info]

  none

  
  Since the update 1:8.0-0ubuntu3.8 to 1:8.0-0ubuntu3.9 , pulseaudio is not 
showing anymore my soundcard.

  https://launchpad.net/ubuntu/+source/pulseaudio/1:8.0-0ubuntu3.9

  The command "pacmd list-sinks" only shows a dummy output

  When running on a fresh install of ubuntu 16.04, the sound is ok.
  When updating the install with locking the following files to version 
1:8.0-0ubuntu3 the sound keeps working:
  libpulse0:amd64
  libpulse-mainloop-glib0:amd64
  libpulse-dev:amd64
  pulseaudio-module-x11:amd64
  pulseaudio-module-bluetooth:amd64
  pulseaudio-utils:amd64

  When updating to 1:8.0-0ubuntu3.9, I just get a "dummy output".

  I tried running the following versions of Ubuntu (live usb), and get the same 
issue (no need to update to get the problem)
  17.04
  17.10
  18.04

  I attached the result of command "pactl list"
  I have also generated logs during the boot but I don't know how to attach 
multiple files

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

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

[Desktop-packages] [Bug 1767096] Re: Random Xorg crashes

2018-05-02 Thread spodin

** Attachment added: "Stacktrace"
   
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1767096/+attachment/5131915/+files/Stacktrace

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

Title:
  Random Xorg crashes

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  Xorg crashes randomly: environment just freezes for a second and I'm
  getting login screen.

  ProblemType: Bug
  DistroRelease: elementary 0.4.1
  Package: xorg 1:7.7+13ubuntu3 [origin: Ubuntu]
  ProcVersionSignature: Ubuntu 4.13.0-39.44~16.04.1-generic 4.13.16
  Uname: Linux 4.13.0-39-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.16
  Architecture: amd64
  CurrentDesktop: Pantheon
  Date: Thu Apr 26 12:57:22 2018
  InstallationDate: Installed on 2018-03-01 (55 days ago)
  InstallationMedia: elementary OS 0.4.1 "Loki" - Stable amd64 (20180214)
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1751252] Re: [regression] ubiquity crashed in debconf.py:104 with ValueError: invalid literal for int() with base 10: ''

Unfortunately I can't tell what in shm_access is failing exactly because
gdb skips straight from shm.c:314 back to the caller. So that suggests
this code path, but I can't verify it:

static int
shm_access(ClientPtr client, SHMPERM_TYPE * perm, int readonly)
{
int uid, gid;
mode_t mask;
int uidset = 0, gidset = 0;
LocalClientCredRec *lcc;

if (GetLocalClientCreds(client, &lcc) != -1) {  // FALSE
...
}
/* Otherwise, check everyone else */
mask = S_IROTH;
if (!readonly) {
mask |= S_IWOTH;
}
return (SHMPERM_MODE(perm) & mask) == mask ? 0 : -1;
}

So Xorg _should_ be returning an error, and it is. The problem seems to
be that the client (python3 gtk_ui process) has a real uid=0 and
effective uid=999. So that allows it to connect to Xorg (normally Xorg
rejects root clients), but doesn't allow Xorg to check the client shm
permissions. So Xorg rejects the client's attempt at XShmAttach.

How any of this relates to scale=200% and why it works at 100%, I'm not
sure. We might need to review comment #15 in more detail.

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

Title:
  [regression] ubiquity crashed in debconf.py:104 with ValueError:
  invalid literal for int() with base 10: ''

Status in OEM Priority Project:
  Triaged
Status in glib2.0 package in Ubuntu:
  Invalid
Status in ubiquity package in Ubuntu:
  Triaged
Status in glib2.0 source package in Bionic:
  Invalid
Status in ubiquity source package in Bionic:
  Triaged

Bug description:
  The Ubuntu installer crashes on hiDPI machines (QHD/UHD etc). Although
  it was working some weeks/months ago, so this is a recent regression.

  ---

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

  ---

  WORKAROUND:

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

  ---

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

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

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

[Desktop-packages] [Bug 1768178] Re: color scheme Solarized Dark is incorrect

2018-05-02 Thread Egmont Koblinger

Submitted https://git.gnome.org/browse/gnome-
terminal/commit/?id=e8ee9f786 to make it more obvious that we indeed
define the Solarized palette correctly.

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

Title:
  color scheme Solarized Dark is incorrect

Status in gnome-terminal package in Ubuntu:
  New

Bug description:
  Original Solarized Dark looks different. Thereis the pull request on
  Github that fixes that - https://github.com/GNOME/gnome-
  terminal/pull/6

  I'm not author of patch and don't checked it, but there is project
  that change color scheme to correct, it described here -
  https://github.com/Anthony25/gnome-terminal-colors-
  solarized/tree/master/colors/dark

  Here is built-in palette collected with gsettings get:
  ['#2E3436', 
  '#CC', 
  '#4E9A06', 
  '#C4A000', 
  '#3465A4', 
  '#75507B', 
  '#06989A', 
  '#D3D7CF', 
  '#555753', 
  '#EF2929', 
  '#8AE234', 
  '#FCE94F', 
  '#729FCF', 
  '#AD7FA8', 
  '#34E2E2', 
  '#EC']

  Here is correct palette:
  ['#070736364242', 
  '#DCDC32322F2F', 
  '#8585', 
  '#B5B58989', 
  '#26268B8BD2D2', 
  '#D3D336368282', 
  '#2A2AA1A19898', 
  '#E8E8D5D5', 
  '#2B2B3636', 
  '#CBCB4B4B1616', 
  '#58586E6E7575', 
  '#65657B7B8383', 
  '#838394949696', 
  '#6C6C7171C4C4', 
  '#9393A1A1A1A1', 
  '#FDFDF6F6E3E3']

  I asked the question about long codes - https://github.com/Anthony25
  /gnome-terminal-colors-solarized/issues/76, but anyway it matches
  original scheme perfectly.

  I created bug at launchpad because Gnome restricted creating bugs for
  non-gnome developers in their guide
  https://wiki.gnome.org/Apps/Terminal/ReportingBugs and point to
  distribution bug tracker.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-terminal 3.28.1-1ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue May  1 07:49:18 2018
  InstallationDate: Installed on 2018-04-29 (1 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=ru_RU.UTF-8
   SHELL=/usr/bin/zsh
  SourcePackage: gnome-terminal
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1767542] Re: Turning off WiFi enables Airplane mode

How is that an important issue? It's a best confusing but whether no
wifi/bluetooth is showed as equivalent to be in airplane mode or not is
just a visual clue being displayed one way or another

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

Title:
  Turning off WiFi enables Airplane mode

Status in gnome-control-center:
  Unknown
Status in gnome-control-center package in Ubuntu:
  Triaged

Bug description:
  Turning off the WiFi from the top right control enables Airplane mode
  (see screenshots). Also after turning off airplane mode, the Wi-Fi is
  not turned back on, rather the Bluetooth is.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-control-center 1:3.28.1-0ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Apr 27 17:46:34 2018
  InstallationDate: Installed on 2018-04-27 (0 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  SourcePackage: gnome-control-center
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1768448] Re: Don't use snaps for default system packages

Thank you for your bug report, that's not really a bug and not one in
gnome-software.

If you want to discuss the use of snaps for those applications
https://community.ubuntu.com/ is a better place.

Snaps have some issues as you pointed but those are being worked on and
are going to be fixed and we believe that providing them as snaps
increases the security and is going to make easier updating them to
newer versions in the futur so it's not likely we revert that decision.

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

Title:
  Don't use snaps for default system packages

Status in gnome-software package in Ubuntu:
  Opinion

Bug description:
  In a fresh install, standard applications like gnome-calculator and 
gnome-system-monitor are installed as snaps.  This results in a plethora of 
mounted loopback devices for basically nothing.  Never mind the slow 
application startup times (seconds for gnome-system-monitor on a Ryzen 1700 
with 32GB RAM and a Samsung EVO 960 on an M.2 interface).
  Removing the snaps and going back to deb packages, the performance issues go 
away.

  I can understand using snaps for third-party commercial software, but
  for the base system, the default debian package manager has served us
  well.  I consider pushing snaps for default gnome applications a bug,
  and mismanagement of the system.

  This does not happen on an upgraded Ubuntu (from 16.04LTS).  Snap is
  there, with no applications installed.  That's how the default should
  be.

  

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

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

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

[Desktop-packages] [Bug 1751252] Re: [regression] ubiquity crashed in debconf.py:104 with ValueError: invalid literal for int() with base 10: ''

Given that XShmAttach can fail (you can google the reasons), I think
maybe we need to handle that in ubiquity/cairo and fall back to an
alternative rendering method.

I'm not so sure we should be treating XShmAttach failure as a bug.

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

Title:
  [regression] ubiquity crashed in debconf.py:104 with ValueError:
  invalid literal for int() with base 10: ''

Status in OEM Priority Project:
  Triaged
Status in glib2.0 package in Ubuntu:
  Invalid
Status in ubiquity package in Ubuntu:
  Triaged
Status in glib2.0 source package in Bionic:
  Invalid
Status in ubiquity source package in Bionic:
  Triaged

Bug description:
  The Ubuntu installer crashes on hiDPI machines (QHD/UHD etc). Although
  it was working some weeks/months ago, so this is a recent regression.

  ---

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

  ---

  WORKAROUND:

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

  ---

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

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

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

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

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

[Desktop-packages] [Bug 1748611] Re: Desktop symbols disappear after changing symbol size in nautilus

Thank you for your bug report, what do you call "symbol"? Could you take
a screenshot showing the issue?

** Package changed: gnome-session (Ubuntu) => nautilus (Ubuntu)

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

Title:
  Desktop symbols disappear after changing symbol size in nautilus

Status in nautilus package in Ubuntu:
  Incomplete

Bug description:
  Problem: When changing the size of folder symbols in the nautilus file
  browser, the symbol size for desktop symbols is also changed. That
  might result in the (temporary) disappearing of desktop symbols.

  How to reproduce the bug: Place some symbols on the right edge of the
  desktop. Open nautilus, increase the size of symbols. The symbol size
  for the desktop and the symbol grid size are also affected by that
  change, symbols placed at the edge will disappear.

  What I expect to happen: Changing the symbol size in nautilus should
  not affect the desktop symbol size/symbol grid size.

  What actually happens: Changing the symbol size in nautilus will
  change the desktop symbol size/ grid size, symbols on the desktop
  might disappear.

  Ubuntu version: 17.10
  ubuntu-session version: 3.26.1-0ubuntu6

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

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

[Desktop-packages] [Bug 1768448] Re: Don't use snaps for default system packages

2018-05-02 Thread Jawtheshark

I see.  Well, then I will have to look for another distribution.

I would strongly suggest that normal packages be managed system wide
with a normal package manager.

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

Title:
  Don't use snaps for default system packages

Status in gnome-software package in Ubuntu:
  Opinion

Bug description:
  In a fresh install, standard applications like gnome-calculator and 
gnome-system-monitor are installed as snaps.  This results in a plethora of 
mounted loopback devices for basically nothing.  Never mind the slow 
application startup times (seconds for gnome-system-monitor on a Ryzen 1700 
with 32GB RAM and a Samsung EVO 960 on an M.2 interface).
  Removing the snaps and going back to deb packages, the performance issues go 
away.

  I can understand using snaps for third-party commercial software, but
  for the base system, the default debian package manager has served us
  well.  I consider pushing snaps for default gnome applications a bug,
  and mismanagement of the system.

  This does not happen on an upgraded Ubuntu (from 16.04LTS).  Snap is
  there, with no applications installed.  That's how the default should
  be.

  

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

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

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

[Desktop-packages] [Bug 1751252] Re: [regression] ubiquity crashed in debconf.py:104 with ValueError: invalid literal for int() with base 10: ''

OK, I can now reproduce the problem at scale=100%. The trick is to slow
down the installer with GDK_SYNCHRONIZE=1. So this is just a race
condition, usually triggered by slower rendering of scale 200%, but can
be triggered other ways.

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

Title:
  [regression] ubiquity crashed in debconf.py:104 with ValueError:
  invalid literal for int() with base 10: ''

Status in OEM Priority Project:
  Triaged
Status in glib2.0 package in Ubuntu:
  Invalid
Status in ubiquity package in Ubuntu:
  Triaged
Status in glib2.0 source package in Bionic:
  Invalid
Status in ubiquity source package in Bionic:
  Triaged

Bug description:
  The Ubuntu installer crashes on hiDPI machines (QHD/UHD etc). Although
  it was working some weeks/months ago, so this is a recent regression.

  ---

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

  ---

  WORKAROUND:

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

  ---

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

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

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

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

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

[Desktop-packages] [Bug 1751252] Re: [regression] ubiquity crashed in debconf.py:104 with ValueError: invalid literal for int() with base 10: ''

So it sounds like a race between Xorg and the ubiquity perms dropping
which then breaks Xorg's ability to authenticate XShmAttach used in
cairo.

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

Title:
  [regression] ubiquity crashed in debconf.py:104 with ValueError:
  invalid literal for int() with base 10: ''

Status in OEM Priority Project:
  Triaged
Status in glib2.0 package in Ubuntu:
  Invalid
Status in ubiquity package in Ubuntu:
  Triaged
Status in glib2.0 source package in Bionic:
  Invalid
Status in ubiquity source package in Bionic:
  Triaged

Bug description:
  The Ubuntu installer crashes on hiDPI machines (QHD/UHD etc). Although
  it was working some weeks/months ago, so this is a recent regression.

  ---

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

  ---

  WORKAROUND:

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

  ---

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

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

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

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

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

[Desktop-packages] [Bug 1767993] Re: Lubuntu: X11 freezing/low resolution on N3150 intel graphics

2018-05-02 Thread Hadmut Danisch

I've found the problem (or at least got some closer):

It's the display port.

I'm using a monitor with 2560x1440 pixels, connected with display port.
The computer has, although tiny, 2xhdmi and 1xdisplay port outputs.

when (without nomodeset) lightdm starts Xorg, it works on the display
port with full resolution, but as soon as the session starts, the screen
remains black.

When I use a HDMI Monitor together with the display port, only console
and mouse pointer work, not even a visible login screen.


but when I use a FullHD HDMI Monitor only, everything works. 


Now, when I use my 2560x1440 monitor over HDMI, the session works, but does 
have  FullHD 1920x1080 only and thus is somewhat blurred. Furthermore, there's 
trouble with the mouse, it behaves crazy as soon as entering an thin area on 
the left side of the screen. 

So now I have a slightly blurred 1920x1080 desktop, a troubled mouse,
and a display-port-monitor connected with an HDMI cable.

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

Title:
  Lubuntu: X11 freezing/low resolution on N3150 intel graphics

Status in xorg-server package in Ubuntu:
  Incomplete

Bug description:
  Hi,
  I just installed a fresh 18.04 on an ASRock beebox N3150 machine.

  The regular ubuntu desktop installer hanged after entering X11 mode,
  machine froze.

  I then used Lubuntu alternate installer with the console based
  installation, which worked without any problem.

  But after rebooting the system again hung after the graphical login
  prompt.

  I then changed the boot options in /etc/default/grub to give the
  kernel the options nosplash nomodeset and to leave the system in
  console mode (I had similar experiences with former ubuntu versions on
  that machine where X11 did not start when the mode had been set by
  console.)

  
  Now X11 works, but comes up in vesa mode (1024x768) only.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xserver-xorg-core 2:1.19.6-1ubuntu4
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: LXDE
  Date: Mon Apr 30 12:25:09 2018
  InstallationDate: Installed on 2018-04-30 (0 days ago)
  InstallationMedia: Lubuntu 18.04 LTS "Bionic Beaver" - Release amd64 
(20180426)
  SourcePackage: xorg-server
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1767415] Re: Emojis in email headers are shown MUCH too large

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

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

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

Title:
  Emojis in email headers are shown MUCH too large

Status in thunderbird package in Ubuntu:
  Confirmed

Bug description:
  See attached picture.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: thunderbird 1:52.7.0+build1-0ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  AddonCompatCheckDisabled: False
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  aschildbach   1621 F pulseaudio
  BuildID: 20180416164209
  Channel: Unavailable
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Apr 27 17:32:00 2018
  EcryptfsInUse: Yes
  ForcedLayersAccel: False
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  IncompatibleExtensions: Thunderbird (default) - 
{972ce4c6-7e08-4474-a285-3208198ce6fd}
  InstallationDate: Installed on 2016-04-21 (735 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  IpRoute:
   default via 192.168.1.1 dev wlp58s0 proto dhcp metric 600 
   169.254.0.0/16 dev wlp58s0 scope link metric 1000 
   192.168.1.0/24 dev wlp58s0 proto kernel scope link src 192.168.1.70 metric 
600
  MostRecentCrashID: bp-dcf7be60-3e00-439e-a39a-52f0d2160327
  PrefSources:
   prefs.js
   /usr/share/xul-ext/enigmail/defaults/preferences/enigmail.js
   /usr/share/xul-ext/enigmail/defaults/preferences/000system.js
  Profiles: Profile0 (Default) - LastVersion=52.7.0/20180416164209 (In use)
  RunningIncompatibleAddons: True
  SourcePackage: thunderbird
  SubmittedCrashIDs:
   bp-dcf7be60-3e00-439e-a39a-52f0d2160327
   bp-47dc2ae5-396d-44a8-a7c0-ecb542160206
   bp-c61df29c-72c2-4a55-ac73-a006c2150907
   bp-a280a2f0-5957-4f04-b28d-0ebe92150820
  UpgradeStatus: Upgraded to bionic on 2018-04-26 (0 days ago)
  dmi.bios.date: 01/16/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.7.0
  dmi.board.name: 07TYC2
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A01
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.7.0:bd01/16/2018:svnDellInc.:pnXPS139350:pvr:rvnDellInc.:rn07TYC2:rvrA01:cvnDellInc.:ct9:cvr:
  dmi.product.family: NULL
  dmi.product.name: XPS 13 9350
  dmi.sys.vendor: Dell Inc.

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

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

[Desktop-packages] [Bug 1748611] Re: Desktop symbols disappear after changing symbol size in nautilus

2018-05-02 Thread Simon P.

I call the stuff I place on the desktop "symbols" - like files, folders
etc. Pictures before and after the changing of the symbol size in
nautilus attached.

** Attachment added: "pictures.zip"

https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1748611/+attachment/5131932/+files/pictures.zip

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

Title:
Desktop symbols disappear after changing symbol size in nautilus

Status in nautilus package in Ubuntu:
Incomplete

Bug description:
Problem: When changing the size of folder symbols in the nautilus file
browser, the symbol size for desktop symbols is also changed. That
might result in the (temporary) disappearing of desktop symbols.

How to reproduce the bug: Place some symbols on the right edge of the
desktop. Open nautilus, increase the size of symbols. The symbol size
for the desktop and the symbol grid size are also affected by that
change, symbols placed at the edge will disappear.

What I expect to happen: Changing the symbol size in nautilus should
not affect the desktop symbol size/symbol grid size.

What actually happens: Changing the symbol size in nautilus will
change the desktop symbol size/ grid size, symbols on the desktop
might disappear.

Ubuntu version: 17.10
ubuntu-session version: 3.26.1-0ubuntu6

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

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

[Desktop-packages] [Bug 1768488] [NEW] dependency problem lightdm -> pam

2018-05-02 Thread Hadmut Danisch

Public bug reported:

Hi,

I've installed Lubuntu 18.04 and found that problem:

the display-manager service complains:

 ● lightdm.service - Light Display Manager
   Loaded: loaded (/lib/systemd/system/lightdm.service; indirect; vendor 
preset: enabled)
   Active: active (running) since Wed 2018-05-02 11:36:27 CEST; 1min 22s ago
 Docs: man:lightdm(1)
  Process: 1717 ExecStartPre=/bin/sh -c [ "$(basename $(cat 
/etc/X11/default-display-manager 2>/dev/null))" = "lightdm" ] (code=exited, 
status=0/SUCCESS)
 Main PID: 1720 (lightdm)
Tasks: 6 (limit: 4915)
   CGroup: /system.slice/lightdm.service
   ├─1720 /usr/sbin/lightdm
   ├─1726 /usr/lib/xorg/Xorg -core :0 -seat seat0 -auth 
/var/run/lightdm/root/:0 -nolisten tcp vt7 -novtswitch
   └─1786 lightdm --session-child 12 19

Mai 02 11:36:29 pcdanisch lightdm[1735]: PAM unable to dlopen(pam_kwallet5.so): 
/lib/security/pam_kwallet5.so: cannot open shared object file: No such file or 
directory
Mai 02 11:36:29 pcdanisch lightdm[1735]: PAM adding faulty module: 
pam_kwallet5.so
Mai 02 11:36:29 pcdanisch lightdm[1735]: pam_unix(lightdm-greeter:session): 
session opened for user lightdm by (uid=0)
Mai 02 11:36:30 pcdanisch lightdm[1786]: PAM unable to 
dlopen(pam_gnome_keyring.so): /lib/security/pam_gnome_keyring.so: cannot open 
shared object file: No such file or directory
Mai 02 11:36:30 pcdanisch lightdm[1786]: PAM adding faulty module: 
pam_gnome_keyring.so
Mai 02 11:36:30 pcdanisch lightdm[1786]: PAM unable to dlopen(pam_kwallet.so): 
/lib/security/pam_kwallet.so: cannot open shared object file: No such file or 
directory
Mai 02 11:36:30 pcdanisch lightdm[1786]: PAM adding faulty module: 
pam_kwallet.so
Mai 02 11:36:30 pcdanisch lightdm[1786]: PAM unable to dlopen(pam_kwallet5.so): 
/lib/security/pam_kwallet5.so: cannot open shared object file: No such file or 
directory
Mai 02 11:36:30 pcdanisch lightdm[1786]: PAM adding faulty module: 
pam_kwallet5.so
Mai 02 11:36:30 pcdanisch lightdm[1786]: pam_succeed_if(lightdm:auth): 
requirement "user ingroup nopasswdlogin" not met by user "danisch"


It's because /etc/pam.d/lightdm and /etc/pam.d/lightdm-greeter try to load pam 
modules which are not installed since there are not dependencies to 
libpam-gnome-keyring  libpam-kwallet4 libpam-kwallet5


If it is not intended to let things run into error message (and possible
further trouble), you should either remove these lines from the config
files or add dependencies to pull in that packages.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: lightdm 1.26.0-0ubuntu1
ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
Uname: Linux 4.15.0-20-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.9-0ubuntu7
Architecture: amd64
CurrentDesktop: LXDE
Date: Wed May  2 12:21:26 2018
InstallationDate: Installed on 2018-04-30 (2 days ago)
InstallationMedia: Lubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
SourcePackage: lightdm
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug bionic

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

Title:
  dependency problem lightdm -> pam

Status in lightdm package in Ubuntu:
  New

Bug description:
  Hi,

  I've installed Lubuntu 18.04 and found that problem:

  the display-manager service complains:

   ● lightdm.service - Light Display Manager
 Loaded: loaded (/lib/systemd/system/lightdm.service; indirect; vendor 
preset: enabled)
 Active: active (running) since Wed 2018-05-02 11:36:27 CEST; 1min 22s ago
   Docs: man:lightdm(1)
Process: 1717 ExecStartPre=/bin/sh -c [ "$(basename $(cat 
/etc/X11/default-display-manager 2>/dev/null))" = "lightdm" ] (code=exited, 
status=0/SUCCESS)
   Main PID: 1720 (lightdm)
  Tasks: 6 (limit: 4915)
 CGroup: /system.slice/lightdm.service
 ├─1720 /usr/sbin/lightdm
 ├─1726 /usr/lib/xorg/Xorg -core :0 -seat seat0 -auth 
/var/run/lightdm/root/:0 -nolisten tcp vt7 -novtswitch
 └─1786 lightdm --session-child 12 19

  Mai 02 11:36:29 pcdanisch lightdm[1735]: PAM unable to 
dlopen(pam_kwallet5.so): /lib/security/pam_kwallet5.so: cannot open shared 
object file: No such file or directory
  Mai 02 11:36:29 pcdanisch lightdm[1735]: PAM adding faulty module: 
pam_kwallet5.so
  Mai 02 11:36:29 pcdanisch lightdm[1735]: pam_unix(lightdm-greeter:session): 
session opened for user lightdm by (uid=0)
  Mai 02 11:36:30 pcdanisch lightdm[1786]: PAM unable to 
dlopen(pam_gnome_keyring.so): /lib/security/pam_gnome_keyring.so: cannot open 
shared object file: No such file or directory
  Mai 02 11:36:30 pcdanisch lightdm[1786]: PAM adding faulty module: 
pam_gnome_keyring.so
  Mai 02 11:36:30 pcdanisch lightdm[1786]: PAM unable to 
dlopen(pam_kwa

[Desktop-packages] [Bug 1756619] Re: nautilus-actions package missing in Ubuntu 18.04 beta

2018-05-02 Thread Norbert

** Also affects: nautilus-actions (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  nautilus-actions package missing in Ubuntu 18.04 beta

Status in gedit package in Ubuntu:
  Confirmed
Status in nautilus-actions package in Ubuntu:
  New

Bug description:
  ***
  Please change this bug from gedit to the correct package.
  ***

  Synaptic no longer offers package nautilus-actions for installation.

  This package is required for right click custom actions in file
  manager and the desktop.

  Please reinstate.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gedit 3.28.0-1ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7
  Uname: Linux 4.15.0-12-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Mar 17 19:39:57 2018
  InstallationDate: Installed on 2018-03-10 (7 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180310)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gedit
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1768499] [NEW] package nvidia-340 (not installed) failed to install/upgrade: trying to overwrite '/lib/udev/rules.d/71-nvidia.rules', which is also in package nvidia-kernel-com

2018-05-02 Thread juliobahar

Public bug reported:

nvidia driver not working after 18.04 upgrade from 16.04 LTS
Had to reinstall an older version 340

ProblemType: Package
DistroRelease: Ubuntu 18.04
Package: nvidia-340 (not installed)
ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
Uname: Linux 4.15.0-20-generic x86_64
ApportVersion: 2.20.9-0ubuntu7
Architecture: amd64
Date: Wed May  2 21:05:09 2018
ErrorMessage: trying to overwrite '/lib/udev/rules.d/71-nvidia.rules', which is 
also in package nvidia-kernel-common-390 390.48-0ubuntu3
InstallationDate: Installed on 2015-10-17 (927 days ago)
InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3
PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
RelatedPackageVersions:
 dpkg 1.19.0.5ubuntu2
 apt  1.6.1
SourcePackage: nvidia-graphics-drivers-340
Title: package nvidia-340 (not installed) failed to install/upgrade: trying to 
overwrite '/lib/udev/rules.d/71-nvidia.rules', which is also in package 
nvidia-kernel-common-390 390.48-0ubuntu3
UpgradeStatus: Upgraded to bionic on 2018-05-02 (0 days ago)

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


** Tags: amd64 apport-package bionic

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

Title:
  package nvidia-340 (not installed) failed to install/upgrade: trying
  to overwrite '/lib/udev/rules.d/71-nvidia.rules', which is also in
  package nvidia-kernel-common-390 390.48-0ubuntu3

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

Bug description:
  nvidia driver not working after 18.04 upgrade from 16.04 LTS
  Had to reinstall an older version 340

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: nvidia-340 (not installed)
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  Date: Wed May  2 21:05:09 2018
  ErrorMessage: trying to overwrite '/lib/udev/rules.d/71-nvidia.rules', which 
is also in package nvidia-kernel-common-390 390.48-0ubuntu3
  InstallationDate: Installed on 2015-10-17 (927 days ago)
  InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
  Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3
  PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu2
   apt  1.6.1
  SourcePackage: nvidia-graphics-drivers-340
  Title: package nvidia-340 (not installed) failed to install/upgrade: trying 
to overwrite '/lib/udev/rules.d/71-nvidia.rules', which is also in package 
nvidia-kernel-common-390 390.48-0ubuntu3
  UpgradeStatus: Upgraded to bionic on 2018-05-02 (0 days ago)

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

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

[Desktop-packages] [Bug 1768501] [NEW] File system problem snapd and others in ubuntu 18.04

2018-05-02 Thread mouad

Public bug reported:

Hi,

The monitor is showing more file then usually (16.04 and lower), and it
very confusing to see snapd's file too.

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

** Attachment added: "Selection_001.png"
   
https://bugs.launchpad.net/bugs/1768501/+attachment/5131968/+files/Selection_001.png

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

Title:
  File system problem snapd and others in ubuntu 18.04

Status in gnome-system-monitor package in Ubuntu:
  New

Bug description:
  Hi,

  The monitor is showing more file then usually (16.04 and lower), and
  it very confusing to see snapd's file too.

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

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

[Desktop-packages] [Bug 1767953] Re: gnome-shell crashed with SIGABRT in __GI_raise() from __GI_abort() from g_assertion_message() from g_assertion_message_expr() from g_hash_table_lookup_node()

2018-05-02 Thread Treviño

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

** This bug has been marked a duplicate of bug 1765686
   gnome-shell crashed with SIGSEGV in g_str_hash() from 
g_hash_table_lookup_node()

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

Title:
  gnome-shell crashed with SIGABRT in __GI_raise() from __GI_abort()
  from g_assertion_message() from g_assertion_message_expr() from
  g_hash_table_lookup_node()

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.28.1-0ubuntu2, the problem page at 
https://errors.ubuntu.com/problem/1bcf7c1c314568cb6da3f8ec7edb13cdb0242a31 
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/1767953/+subscriptions

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

[Desktop-packages] [Bug 1765686] Re: gnome-shell crashed with SIGSEGV in g_str_hash() from g_hash_table_lookup_node()

2018-05-02 Thread Treviño

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

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

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

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

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

Title:
  gnome-shell crashed with SIGSEGV in g_str_hash() from
  g_hash_table_lookup_node()

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

Bug description:
  https://errors.ubuntu.com/problem/87e4666825764619cb47f3837f871d88d65dd606

  ---

  It seems to be reproduceable, if I load a wider filearea with
  different filesystems (ntfs and ext4)

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.28.1-0ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15
  Uname: Linux 4.15.0-15-generic x86_64
  ApportVersion: 2.20.9-0ubuntu5
  Architecture: amd64
  CurrentDesktop: GNOME-Greeter:GNOME
  Date: Fri Apr 20 12:36:08 2018
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  GsettingsChanges:

  InstallationDate: Installed on 2018-03-23 (27 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180321)
  ProcCmdline: /usr/bin/gnome-shell
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/false
  SegvAnalysis:
   Segfault happened at: 0x7fd13cdc0430 :   movsbl (%rdi),%edx
   PC (0x7fd13cdc0430) ok
   source "(%rdi)" (0x00ca) not located in a known VMA region (needed 
readable region)!
   destination "%edx" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: gnome-shell
  StacktraceTop:
   g_str_hash () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_hash_table_lookup () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
   g_main_context_dispatch () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
  Title: gnome-shell crashed with SIGSEGV in g_str_hash()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

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

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

[Desktop-packages] [Bug 1768509] [NEW] [Inspiron 530, Realtek ALC888, Black Line Out, Rear] No sound at all

2018-05-02 Thread Vincenzo

Public bug reported:

I know it was working before with LTS 16.04. Also the sound card is
shown as dummy when I have tried several times to upload the software i
have seen two different sound cards.

Could you help me fix this?

18/04 LTS upgraded fresh, no updates

vincenzo@inspiron530:~$ apt-cache policy pkgname
N: Unable to locate package pkgname
vincenzo@inspiron530:~$ 

i thought it would find the card automatically. it seems not to have the
right card or be misconfigured.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: pulseaudio 1:11.1-1ubuntu7
ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
Uname: Linux 4.15.0-20-generic x86_64
ApportVersion: 2.20.9-0ubuntu7
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  vincenzo949 F pulseaudio
CurrentDesktop: ubuntu:GNOME
Date: Wed May  2 12:33:58 2018
InstallationDate: Installed on 2018-05-02 (0 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_GB.UTF-8
 SHELL=/bin/bash
SourcePackage: pulseaudio
Symptom: audio
Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Intel successful
Symptom_Card: Built-in Audio - HDA Intel
Symptom_DevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  vincenzo949 F pulseaudio
Symptom_Jack: Black Line Out, Rear
Symptom_PulsePlaybackTest: PulseAudio playback test failed
Symptom_Type: No sound at all
Title: [Inspiron 530, Realtek ALC888, Black Line Out, Rear] No sound at all
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 06/20/2008
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.0.15
dmi.board.name: 0K216C
dmi.board.vendor: Dell Inc.
dmi.board.version: ���
dmi.chassis.type: 3
dmi.chassis.vendor: Dell Inc.
dmi.chassis.version: OEM
dmi.modalias: 
dmi:bvnDellInc.:bvr1.0.15:bd06/20/2008:svnDellInc.:pnInspiron530:pvr:rvnDellInc.:rn0K216C:rvr:cvnDellInc.:ct3:cvrOEM:
dmi.product.name: Inspiron 530
dmi.sys.vendor: Dell Inc.

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


** Tags: amd64 apport-bug bionic

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

Title:
  [Inspiron 530, Realtek ALC888, Black Line Out, Rear] No sound at all

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  I know it was working before with LTS 16.04. Also the sound card is
  shown as dummy when I have tried several times to upload the software
  i  have seen two different sound cards.

  Could you help me fix this?

  18/04 LTS upgraded fresh, no updates

  vincenzo@inspiron530:~$ apt-cache policy pkgname
  N: Unable to locate package pkgname
  vincenzo@inspiron530:~$ 

  i thought it would find the card automatically. it seems not to have
  the right card or be misconfigured.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: pulseaudio 1:11.1-1ubuntu7
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  vincenzo949 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Wed May  2 12:33:58 2018
  InstallationDate: Installed on 2018-05-02 (0 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  SourcePackage: pulseaudio
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Intel successful
  Symptom_Card: Built-in Audio - HDA Intel
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  vincenzo949 F pulseaudio
  Symptom_Jack: Black Line Out, Rear
  Symptom_PulsePlaybackTest: PulseAudio playback test failed
  Symptom_Type: No sound at all
  Title: [Inspiron 530, Realtek ALC888, Black Line Out, Rear] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/20/2008
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.0.15
  dmi.board.name: 0K216C
  dmi.board.vendor: Dell Inc.
  dmi.board.version: ���
  dmi.chassis.type: 3
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: OEM
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.0.15:bd06/20/2008:svnDellInc.:pnInspiron530:pvr:rvnDellInc.:rn0K216C:rvr:cvnDellInc.:ct3:cvrOEM:
  dmi.product.name: Inspiron 530
  dmi.sys.vendor: Dell Inc.

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

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

[Desktop-packages] [Bug 1767411] Re: Icons in subject message rendered too big

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

** This bug has been marked a duplicate of bug 1761844
   Thunderbird: emojis is displayed in the email list

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

Title:
  Icons in subject message rendered too big

Status in thunderbird package in Ubuntu:
  New

Bug description:
  When an icon is deplayed inside the Subject field of a message
  Thunderbird renders it too big.

  Example of a UTF8 character being rendered as way too big icon in the
  message source:

  subject: =?utf-8?q?=F0=9F=94=8C?= Het is weer gelukt: veiling was een
  succes!

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: thunderbird 1:52.7.0+build1-0ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  AddonCompatCheckDisabled: False
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  carroarmato0   1641 F pulseaudio
   /dev/snd/controlC0:  carroarmato0   1641 F pulseaudio
  BuildID: 20180416164209
  Channel: Unavailable
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Apr 27 17:17:59 2018
  ExecutablePath: /usr/lib/thunderbird/thunderbird
  Extensions: extensions.sqlite corrupt or missing
  ForcedLayersAccel: False
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  IncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
  InstallationDate: Installed on 2018-04-27 (0 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  IpRoute:
   default via 192.168.20.1 dev wlp3s0 proto dhcp metric 600 
   169.254.0.0/16 dev wlp3s0 scope link metric 1000 
   192.168.20.0/24 dev wlp3s0 proto kernel scope link src 192.168.20.220 metric 
600
  Locales: extensions.sqlite corrupt or missing
  PrefSources: prefs.js
  Prefs:
   extensions.lastAppVersion: "52.7.0" (prefs.js)
   network.cookie.prefsMigrated: true (prefs.js)
   network.predictor.cleaned-up: true (prefs.js)
   places.database.lastMaintenance: 1524839666 (prefs.js)
   places.history.expiration.transient_current_max_pages: 122334 (prefs.js)
  Profiles: Profile0 (Default) - LastVersion=52.7.0/20180416164209 (In use)
  RunningIncompatibleAddons: False
  SourcePackage: thunderbird
  Themes: extensions.sqlite corrupt or missing
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/25/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: JBET60WW (1.24 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20BX004QMB
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40705 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrJBET60WW(1.24):bd05/25/2016:svnLENOVO:pn20BX004QMB:pvrThinkPadT450s:rvnLENOVO:rn20BX004QMB:rvrSDK0J40705WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad T450s
  dmi.product.name: 20BX004QMB
  dmi.product.version: ThinkPad T450s
  dmi.sys.vendor: LENOVO

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

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

[Desktop-packages] [Bug 1759286] Re: Thunderbird shows large overlay emojis over 2/3 of panes

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

** This bug has been marked a duplicate of bug 1761844
   Thunderbird: emojis is displayed in the email list

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

Title:
  Thunderbird shows large overlay emojis over 2/3 of panes

Status in thunderbird package in Ubuntu:
  Triaged

Bug description:
  When launching Thunderbird for the first time after adding a Gmail
  account it begins to download mail. As it does this large emoji's are
  displayed on top of the email list (see screenshot).

  Tested on Bionic daily image 27-03-18.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: thunderbird 1:52.6.0+build1-0ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7
  Uname: Linux 4.15.0-12-generic x86_64
  AddonCompatCheckDisabled: False
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  alex   1410 F pulseaudio
  BuildID: 20180131200234
  Channel: Unavailable
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Mar 27 15:09:18 2018
  Extensions: extensions.sqlite corrupt or missing
  ForcedLayersAccel: False
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  IncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
  InstallationDate: Installed on 2018-03-26 (1 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180325)
  IpRoute:
   default via 10.20.64.1 dev ens33 proto dhcp metric 100 
   10.20.64.0/21 dev ens33 proto kernel scope link src 10.20.67.24 metric 100 
   169.254.0.0/16 dev ens33 scope link metric 1000
  IwConfig:
   ens33 no wireless extensions.
   
   lono wireless extensions.
  Locales: extensions.sqlite corrupt or missing
  PrefSources: prefs.js
  Prefs:
   extensions.lastAppVersion: "52.6.0" (prefs.js)
   network.cookie.prefsMigrated: true (prefs.js)
  Profiles: Profile0 (Default) - LastVersion=52.6.0/20180131200234 (In use)
  RfKill:
   0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
  RunningIncompatibleAddons: False
  SourcePackage: thunderbird
  Themes: extensions.sqlite corrupt or missing
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/02/2015
  dmi.bios.vendor: Phoenix Technologies LTD
  dmi.bios.version: 6.00
  dmi.board.name: 440BX Desktop Reference Platform
  dmi.board.vendor: Intel Corporation
  dmi.board.version: None
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 1
  dmi.chassis.vendor: No Enclosure
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd07/02/2015:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A:
  dmi.product.name: VMware Virtual Platform
  dmi.product.version: None
  dmi.sys.vendor: VMware, Inc.

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

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

[Desktop-packages] [Bug 1768501] Re: File system problem snapd and others in ubuntu 18.04

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

** Changed in: gnome-system-monitor (Ubuntu)
   Importance: Undecided => Low

** This bug has been marked a duplicate of bug 1749007
   Snap mounts should be hidden from System Monitor

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

Title:
  File system problem snapd and others in ubuntu 18.04

Status in gnome-system-monitor package in Ubuntu:
  New

Bug description:
  Hi,

  The monitor is showing more file then usually (16.04 and lower), and
  it very confusing to see snapd's file too.

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

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

[Desktop-packages] [Bug 1761844] Re: Thunderbird: emojis is displayed in the email list

One of the duplicates claims it's fixed in the next tb version from
https://launchpad.net/~mozillateam/+archive/ubuntu/thunderbird-next

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

** Bug watch added: Mozilla Bugzilla #1390015
   https://bugzilla.mozilla.org/show_bug.cgi?id=1390015

** Also affects: thunderbird via
   https://bugzilla.mozilla.org/show_bug.cgi?id=1390015
   Importance: Unknown
   Status: Unknown

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

Title:
  Thunderbird: emojis is displayed in the email list

Status in Mozilla Thunderbird:
  Unknown
Status in thunderbird package in Ubuntu:
  Confirmed

Bug description:
  The list of emails received from Thunderbird shows emojis. This does not 
happen with all accounts.
  It appears to be with the last email address added.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: thunderbird 1:52.6.0+build1-0ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15
  Uname: Linux 4.15.0-15-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  AddonCompatCheckDisabled: False
  ApportVersion: 2.20.9-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   diego  1607 F...m pulseaudio
   /dev/snd/controlC0:  diego  1607 F pulseaudio
   /dev/snd/controlC1:  diego  1607 F pulseaudio
  BuildID: 20180131200234
  Channel: Unavailable
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Apr  6 15:58:17 2018
  Extensions: extensions.sqlite corrupt or missing
  ForcedLayersAccel: False
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  IncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
  InstallationDate: Installed on 2018-04-05 (1 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Beta amd64 (20180404)
  IpRoute:
   default via 181.31.1.1 dev enp2s0 proto dhcp metric 100 
   169.254.0.0/16 dev enp2s0 scope link metric 1000 
   181.31.1.0/24 dev enp2s0 proto kernel scope link src 181.31.1.84 metric 100
  IwConfig:
   lono wireless extensions.
   
   enp2s0no wireless extensions.
  Locales: extensions.sqlite corrupt or missing
  PrefSources: prefs.js
  Profiles: Profile0 (Default) - LastVersion=52.6.0/20180131200234 (In use)
  RfKill:
   
  RunningIncompatibleAddons: False
  SourcePackage: thunderbird
  Themes: extensions.sqlite corrupt or missing
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/14/2012
  dmi.bios.vendor: Award Software International, Inc.
  dmi.bios.version: F4
  dmi.board.name: GA-78LMT-S2
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrF4:bd08/14/2012:svnGigabyteTechnologyCo.,Ltd.:pnGA-78LMT-S2:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-78LMT-S2:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
  dmi.product.name: GA-78LMT-S2
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

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

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

[Desktop-packages] [Bug 1768232] Re: i915 driver issue in Ubuntu 18.04

2018-05-02 Thread Tarik GRABA

I had to use a 4.16 kernel from http://kernel.ubuntu.com/~kernel-
ppa/mainline to have a working machine!

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

Title:
  i915 driver issue in Ubuntu 18.04

Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  lspci -nnk | grep -iA2 vga
  00:02.0 VGA compatible controller [0300]: Intel Corporation 82945G/GZ 
Integrated Graphics Controller [8086:2772] (rev 02)
  Subsystem: Hewlett-Packard Company 82945G/GZ Integrated Graphics 
Controller [103c:302a]
  Kernel modules: i915, intelfb

  
  and

  xrandr 
  xrandr: Failed to get size of gamma for output default
  Screen 0: minimum 1024 x 768, current 1024 x 768, maximum 1024 x 768
  default connected primary 1024x768+0+0 0mm x 0mm
 1024x768  76.00*

  Output of sudo lshw -c display

  *-display UNCLAIMED   
 description: VGA compatible controller
 product: 82945G/GZ Integrated Graphics Controller
 vendor: Intel Corporation
 physical id: 2
 bus info: pci@:00:02.0
 version: 02
 width: 32 bits
 clock: 33MHz
 capabilities: msi pm vga_controller bus_master cap_list
 configuration: latency=0
 resources: memory:e200-e207 ioport:c000(size=8) 
memory:d000-dfff memory:e208-e20b memory:c-d

  I've tried solution 1 and solution 2 but no success.

  This issue occurred only after installing it, not when I choose 'Try
  without Installing', I don't need to set nomodeset in that case.

  Intel Graphics Update Tool shows:

  Checking if Intel graphics card available...
• checking for i915 module in /sys/module
• i915 module found
  Checking if Intel graphics card available... OK
  Retrieving information from 01.org...
• fetching https://download.01.org/gfx/ilg-config.cfg
• saving to /home/garden/.ilg-config
• fetched 1626 bytes
• fetched 9818 bytes
• fetched 12301 bytes
• looking up [Ubuntu bionic] configuration
  Retrieving information from 01.org... OK
  Checking distribution... Failed

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7
  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
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Tue May  1 17:16:20 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: I just need to know a workaround
  GraphicsCard:
   Intel Corporation 82945G/GZ Integrated Graphics Controller [8086:2772] (rev 
02) (prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company 82945G/GZ Integrated Graphics 
Controller [103c:302a]
  InstallationDate: Installed on 2018-05-01 (0 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  MachineType: Hewlett-Packard HP dx2080 MT(KS826PA)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_IN
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-20-generic 
root=UUID=7ec4f610-9b62-44f3-867d-01abd93de14d ro quiet splash nomodeset 
vt.handoff=1
  Renderer: Software
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  XorgConf:
   Section "Device"
Identifier "Intel Graphics"
Driver "intel"
Option "AccelMethod" "uxa"
   EndSection
  dmi.bios.date: 11/28/2007
  dmi.bios.vendor: Award Software International, Inc.
  dmi.bios.version: V1.03
  dmi.board.name: 0AD8h
  dmi.board.vendor: Board Manufacturer
  dmi.chassis.asset.tag: INA8100LFY
  dmi.chassis.type: 3
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrV1.03:bd11/28/2007:svnHewlett-Packard:pnHPdx2080MT(KS826PA):pvr:rvnBoardManufacturer:rn0AD8h:rvr:cvnHewlett-Packard:ct3:cvr:
  dmi.product.name: HP dx2080 MT(KS826PA)
  dmi.sys.vendor: Hewlett-Packard
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.91+git1804271336.50426f~oibaf~b
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.2~git1804301930.1c5f4f~oibaf~b
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.2~git1804301930.1c5f4f~oibaf~b
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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

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

[Desktop-packages] [Bug 1761844] Re: Thunderbird: emojis is displayed in the email list

2018-05-02 Thread Michał Sawicz

Confirmed, emojis are fine in:

$ LANG=C apt policy thunderbird
thunderbird:
  Installed: 1:57.0~b2+build1-0ubuntu0.18.04.1
  Candidate: 1:57.0~b2+build1-0ubuntu0.18.04.1
  Version table:
 *** 1:57.0~b2+build1-0ubuntu0.18.04.1 500
500 http://ppa.launchpad.net/mozillateam/thunderbird-next/ubuntu 
bionic/main amd64 Packages
100 /var/lib/dpkg/status
 1:52.7.0+build1-0ubuntu1 500
500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages

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

Title:
  Thunderbird: emojis is displayed in the email list

Status in Mozilla Thunderbird:
  Unknown
Status in thunderbird package in Ubuntu:
  Confirmed

Bug description:
  The list of emails received from Thunderbird shows emojis. This does not 
happen with all accounts.
  It appears to be with the last email address added.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: thunderbird 1:52.6.0+build1-0ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15
  Uname: Linux 4.15.0-15-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  AddonCompatCheckDisabled: False
  ApportVersion: 2.20.9-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   diego  1607 F...m pulseaudio
   /dev/snd/controlC0:  diego  1607 F pulseaudio
   /dev/snd/controlC1:  diego  1607 F pulseaudio
  BuildID: 20180131200234
  Channel: Unavailable
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Apr  6 15:58:17 2018
  Extensions: extensions.sqlite corrupt or missing
  ForcedLayersAccel: False
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  IncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
  InstallationDate: Installed on 2018-04-05 (1 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Beta amd64 (20180404)
  IpRoute:
   default via 181.31.1.1 dev enp2s0 proto dhcp metric 100 
   169.254.0.0/16 dev enp2s0 scope link metric 1000 
   181.31.1.0/24 dev enp2s0 proto kernel scope link src 181.31.1.84 metric 100
  IwConfig:
   lono wireless extensions.
   
   enp2s0no wireless extensions.
  Locales: extensions.sqlite corrupt or missing
  PrefSources: prefs.js
  Profiles: Profile0 (Default) - LastVersion=52.6.0/20180131200234 (In use)
  RfKill:
   
  RunningIncompatibleAddons: False
  SourcePackage: thunderbird
  Themes: extensions.sqlite corrupt or missing
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/14/2012
  dmi.bios.vendor: Award Software International, Inc.
  dmi.bios.version: F4
  dmi.board.name: GA-78LMT-S2
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrF4:bd08/14/2012:svnGigabyteTechnologyCo.,Ltd.:pnGA-78LMT-S2:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-78LMT-S2:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
  dmi.product.name: GA-78LMT-S2
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

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

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

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

2018-05-02 Thread Willem Holleder

Same problem here with 4 1050TI cards. Installed 18.04, installed 390
driver, system doesn't boot anymore

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

Title:
  nvidia-390 fails to boot graphical display

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

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

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

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

[Desktop-packages] [Bug 1767817] Re: Full text search does not work

2018-05-02 Thread Mordi

Sorry, but the process seems a bit too complex for me.

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

Title:
  Full text search does not work

Status in nautilus package in Ubuntu:
  Confirmed

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

  1.

  Description:  Ubuntu 18.04 LTS
  Release:  18.04

  2.

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

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

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

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

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

[Desktop-packages] [Bug 704504] Re: Run time error in ntfs-config

2018-05-02 Thread dino99

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

** This bug has been marked a duplicate of bug 1768470
   Cannot disable device, please remove from archive

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

Title:
  Run time error in ntfs-config

Status in gnome-terminal package in Ubuntu:
  New

Bug description:
  Terminal shows:-

  frank@ubuntu:~$ gksudo ntfs-config
  Traceback (most recent call last):  File "/usr/bin/ntfs-config", line 102, in 

  main(args, opts)
File "/usr/bin/ntfs-config", line 75, in main
  app = NtfsConfig()
File "/usr/lib/pymodules/python2.6/NtfsConfig/NtfsConfig.py", line 56, in 
__init__
  os.mkdir(HAL_CONFIG_DIR)
  OSError: [Errno 2] No such file or directory: '/etc/hal/fdi/policy'

  I am trying to follow the Ubuntu documentation to make my windows files 
accessible.
  What do I need to do?
  Is there another package that will enable me to do this?
  Thanks in advance

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

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

[Desktop-packages] [Bug 1713581] Re: nautilus crashed with SIGSEGV in g_type_check_instance_is_fundamentally_a()

2018-05-02 Thread Treviño

Yeah, I've noticed it... Mh, I'm a bit out of ideas at this point.
I'll see if I can find a way to reproduce it.

** Changed in: nautilus (Ubuntu)
   Status: Fix Released => Triaged

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

Title:
  nautilus crashed with SIGSEGV in
  g_type_check_instance_is_fundamentally_a()

Status in nautilus package in Ubuntu:
  Triaged

Bug description:
  https://errors.ubuntu.com/problem/ef1ce30f6325c683b207fd96a3be93eda5384054
  Fixed in 
https://gitlab.gnome.org/GNOME/nautilus/commit/b6691821b86460bf9d4caa6391666ae506a743c5

  no idea,sorry

  ProblemType: CrashDistroRelease: Ubuntu 17.10
  Package: nautilus 1:3.25.90-0ubuntu1
  ProcVersionSignature: Ubuntu 4.12.0-11.12-generic 4.12.5
  Uname: Linux 4.12.0-11-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.6-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Aug 29 00:07:44 2017
  EcryptfsInUse: Yes
  ExecutablePath: /usr/bin/nautilus
  InstallationDate: Installed on 2017-08-09 (19 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170807)
  ProcCmdline: /usr/bin/nautilus --gapplication-service
  ProcEnviron:
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
   PATH=(custom, no user)
   LANG=de_DE.UTF-8
  SegvAnalysis:
   Segfault happened at: 0x7f8b19a60d27 
:   mov(%rdi),%rdx
   PC (0x7f8b19a60d27) ok
   source "(%rdi)" (0x0002) not located in a known VMA region (needed 
readable region)!
   destination "%rdx" ok
  SegvReason: reading NULL VMA
  Signal: 11SourcePackage: nautilus
  StacktraceTop:
   g_type_check_instance_is_fundamentally_a () from 
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   g_object_ref () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   g_list_copy_deep () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? ()
   ?? ()
  Title: nautilus crashed with SIGSEGV in 
g_type_check_instance_is_fundamentally_a()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm audio cdrom dip lpadmin netdev plugdev sambashare scanner sudo

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

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

[Desktop-packages] [Bug 1687864] Re: auto-login and "privacy -> auto screen lock -> disable" do not work

2018-05-02 Thread Wolf

The problem persists on "bionic" as well. Keep trying... (-;

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

Title:
  auto-login and "privacy -> auto screen lock -> disable" do not work

Status in gnome-control-center package in Ubuntu:
  Expired

Bug description:
  On my machine, after booting I always have to type in my password,
  allthough I set "settings -> users -> auto login".

  The same happens after resume from suspend, allthough I set "privacy
  -> auto screen lock" to "disabled". In both cases the screen attached
  appears.

  My system:
  ubuntu 16.10
  gnome desktop
  lightdm

  Cheers,
  Wolf

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

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

[Desktop-packages] [Bug 1766137] Re: [regression] Password accepted but login fails (blank purple screen and mouse pointer only)

2018-05-02 Thread Davide

Ads2
The cancel button is not visible (purple screen),
your workaround is for another problem.
I think it's better to remove it from the bug description.

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

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

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

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

  ---

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

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

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

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

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

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

[Desktop-packages] [Bug 1433548] Re: missing words in the English dictionaries

These need to be reported upstream. Please see
http://wordlist.aspell.net/ and https://github.com/en-wl/wordlist

** Changed in: libreoffice-dictionaries (Ubuntu)
   Status: Confirmed => Invalid

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

Title:
  missing words in the English dictionaries

Status in libreoffice-dictionaries package in Ubuntu:
  Invalid

Bug description:
  from  both en_gb and en_us:

  anonymised
  forecastable
  hyperlink
  inconstructive
  mandatorily
  megalomanic
  misconfigured
  oxymoronic
  redistributable
  refactor
  resizable
  unapplied
  unconfirm
  unconfirming
  unobvious
  workflow

  
  only from en_gb:

  constraining
  redistributable

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

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

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

2018-05-02 Thread Beavis

This is a regression, with xubuntu 17.10 prime worked fine.

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

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

Status in nvidia-prime package in Ubuntu:
  Confirmed

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

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

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

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

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

[Desktop-packages] [Bug 1766137] Re: [regression] Password accepted but login fails (blank purple screen and mouse pointer only)

2018-05-02 Thread coolhandlewk

Davide

Ads2000 means to hit cancel before retyping your password.  Hit cancel,
then re-select user, then retype password, all before hitting enter...
and hence the purple screen.  I believe it's the same problem.  This
workaround works for me.

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

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

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

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

  ---

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

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

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

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

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

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

[Desktop-packages] [Bug 1718238] Re: Giant terminal icon is blocking out the Terminal window buttons

2018-05-02 Thread Justin Beitz

Issue remains for me as well 18.04 - 3.28.1

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

Title:
  Giant terminal icon is blocking out the Terminal window buttons

Status in gnome-shell package in Ubuntu:
  Confirmed
Status in mutter package in Ubuntu:
  Confirmed
Status in ubuntu-themes package in Ubuntu:
  Invalid

Bug description:
  Upstream: https://gitlab.gnome.org/GNOME/mutter/issues/23

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: light-themes 16.10+17.10.20170918-0ubuntu1
  ProcVersionSignature: Ubuntu 4.12.0-13.14-generic 4.12.10
  Uname: Linux 4.12.0-13-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Sep 19 12:47:51 2017
  InstallationDate: Installed on 2017-09-19 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170917)
  PackageArchitecture: all
  SourcePackage: ubuntu-themes
  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/1718238/+subscriptions

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

[Desktop-packages] [Bug 1768306] Re: LibreOffice crash

2018-05-02 Thread Olivier Tilloy

> OS: Ubuntu Budgie 18.04 32-bit

That's very likely a duplicate of bug #1699772.

To confirm this, can you run the following command in a terminal:

sed -i '/enabled/c\false<\/enabled>'
~/.config/libreoffice/4/user/config/javasettings_Linux_*.xml

Then execute libreoffice writer and let me know if the crash is still
happening? Thanks!

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

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

Title:
  LibreOffice crash

Status in Ubuntu Budgie:
  New
Status in libreoffice package in Ubuntu:
  Incomplete

Bug description:
  Whenever LibreOffice Writer is launched, it does not load and a crash report 
appears.
  And if it is launched via the command line, it doesn't even show any info or 
error message.

  The LibreOffice base and Calc opens OK though.

  System info:

  OS: Ubuntu Budgie 18.04 32-bit
  PC: Sony Vaio VGN-FE21H

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

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

[Desktop-packages] [Bug 1758689] Re: No microcode option present

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

** Changed in: ubuntu-drivers-common (Ubuntu)
   Status: New => Confirmed

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

Title:
  No microcode option present

Status in ubuntu-drivers-common package in Ubuntu:
  Confirmed

Bug description:
  Appears to have been removed based on 
  "  - Remove the cpu-microcode.py detection plugin (LP: #1738259).
Kernel metapackages are going to have a hard dependency on the
{intel,amd64}-microcode packages to ensure that all bare-metal installs
benefit from microcode updates"
  However that appears to have never occured in bionic for 4.15.x & to have 
been reverted in all other linux-meta packages, ex. xenial - 
  * Miscellaneous upstream changes
  - Revert "UBUNTU: Make kernel image packages depend on cpu microcode 
updates"

   -- Marcelo Henrique Cerri   Fri, 12 Jan
  2018 16:34:13 -0200

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: ubuntu-drivers-common 1:0.5
  ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7
  Uname: Linux 4.15.0-12-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CurrentDesktop: Unity:Unity7:ubuntu
  Date: Sun Mar 25 11:36:27 2018
  SourcePackage: ubuntu-drivers-common
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

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

2018-05-02 Thread Fondfire

Public bug reported:

installation of this package failed, upgrading from 17.10.

ProblemType: Package
DistroRelease: Ubuntu 18.04
Package: libp11-kit-gnome-keyring 3.20.1-1ubuntu1
ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
Uname: Linux 4.15.0-20-generic x86_64
ApportVersion: 2.20.9-0ubuntu7
Architecture: amd64
Date: Wed May  2 01:39:47 2018
Dependencies:
 gcc-8-base 8-20180414-1ubuntu2
 libc6 2.27-3ubuntu1
 libgcc1 1:8-20180414-1ubuntu2
DuplicateSignature:
 package:libp11-kit-gnome-keyring:3.20.1-1ubuntu1
 Unpacking gnome-keyring (3.28.0.2-1ubuntu1) over (3.20.1-1ubuntu1) ...
 dpkg: error processing archive 
/tmp/apt-dpkg-install-PlRQuy/0830-libp11-kit-gnome-keyring_3.28.0.2-1ubuntu1_all.deb
 (--unpack):
  libp11-kit-gnome-keyring:all 3.28.0.2-1ubuntu1 (Multi-Arch: no) is not 
co-installable with libp11-kit-gnome-keyring which has multiple installed 
instances
ErrorMessage: libp11-kit-gnome-keyring:all 3.28.0.2-1ubuntu1 (Multi-Arch: no) 
is not co-installable with libp11-kit-gnome-keyring which has multiple 
installed instances
Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3
PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
RelatedPackageVersions:
 dpkg 1.19.0.5ubuntu2
 apt  1.6.1
SourcePackage: gnome-keyring
Title: package libp11-kit-gnome-keyring 3.20.1-1ubuntu1 failed to 
install/upgrade: libp11-kit-gnome-keyring:all 3.28.0.2-1ubuntu1 (Multi-Arch: 
no) is not co-installable with libp11-kit-gnome-keyring which has multiple 
installed instances
UpgradeStatus: Upgraded to bionic on 2018-05-02 (0 days ago)

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


** Tags: amd64 apport-package bionic

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

Title:
  package libp11-kit-gnome-keyring 3.20.1-1ubuntu1 failed to
  install/upgrade: libp11-kit-gnome-keyring:all 3.28.0.2-1ubuntu1
  (Multi-Arch: no) is not co-installable with libp11-kit-gnome-keyring
  which has multiple installed instances

Status in gnome-keyring package in Ubuntu:
  New

Bug description:
  installation of this package failed, upgrading from 17.10.

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: libp11-kit-gnome-keyring 3.20.1-1ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  Date: Wed May  2 01:39:47 2018
  Dependencies:
   gcc-8-base 8-20180414-1ubuntu2
   libc6 2.27-3ubuntu1
   libgcc1 1:8-20180414-1ubuntu2
  DuplicateSignature:
   package:libp11-kit-gnome-keyring:3.20.1-1ubuntu1
   Unpacking gnome-keyring (3.28.0.2-1ubuntu1) over (3.20.1-1ubuntu1) ...
   dpkg: error processing archive 
/tmp/apt-dpkg-install-PlRQuy/0830-libp11-kit-gnome-keyring_3.28.0.2-1ubuntu1_all.deb
 (--unpack):
libp11-kit-gnome-keyring:all 3.28.0.2-1ubuntu1 (Multi-Arch: no) is not 
co-installable with libp11-kit-gnome-keyring which has multiple installed 
instances
  ErrorMessage: libp11-kit-gnome-keyring:all 3.28.0.2-1ubuntu1 (Multi-Arch: no) 
is not co-installable with libp11-kit-gnome-keyring which has multiple 
installed instances
  Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3
  PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu2
   apt  1.6.1
  SourcePackage: gnome-keyring
  Title: package libp11-kit-gnome-keyring 3.20.1-1ubuntu1 failed to 
install/upgrade: libp11-kit-gnome-keyring:all 3.28.0.2-1ubuntu1 (Multi-Arch: 
no) is not co-installable with libp11-kit-gnome-keyring which has multiple 
installed instances
  UpgradeStatus: Upgraded to bionic on 2018-05-02 (0 days ago)

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

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

[Desktop-packages] [Bug 1768539] [NEW] Conflicts between / and /usr

2018-05-02 Thread Dimitri John Ledkov

Public bug reported:

bin/rm and usr/bin/rm conflict between coreutils and safe-rm

---
Not a conflict, but these just look weird:
neutron-vpnaas ships these in python-neutron-vpnaas
etc/neutron/rootwrap.d/vpnaas.filters
usr/etc/neutron/rootwrap.d/vpnaas.filters

---
pm-utils and molly-guard conflict on:

sbin/pm-hibernate
usr/sbin/pm-hibernate
sbin/pm-suspend
usr/sbin/pm-suspend
sbin/pm-suspend-hybrid
usr/sbin/pm-suspend-hybrid

** Affects: molly-guard (Ubuntu)
 Importance: High
 Status: New

** Affects: neutron-vpnaas (Ubuntu)
 Importance: Wishlist
 Status: New

** Affects: pm-utils (Ubuntu)
 Importance: High
 Status: New

** Affects: safe-rm (Ubuntu)
 Importance: High
 Status: New

** Affects: pm-utils (Debian)
 Importance: Unknown
 Status: Unknown

** Affects: safe-rm (Debian)
 Importance: Unknown
 Status: Unknown

** Also affects: neutron-vpnaas (Ubuntu)
   Importance: Undecided
   Status: New

** Description changed:

  bin/rm and usr/bin/rm conflict between coreutils and safe-rm
+ 
+ 
+ ---
+ Not a conflict, but these just look weird:
+ etc/neutron/rootwrap.d/vpnaas.filters 
universe/python/python-neutron-vpnaas
+ usr/etc/neutron/rootwrap.d/vpnaas.filters 
universe/python/python-neutron-vpnaas

** Description changed:

  bin/rm and usr/bin/rm conflict between coreutils and safe-rm
- 
  
  ---
  Not a conflict, but these just look weird:
- etc/neutron/rootwrap.d/vpnaas.filters 
universe/python/python-neutron-vpnaas
- usr/etc/neutron/rootwrap.d/vpnaas.filters 
universe/python/python-neutron-vpnaas
+ neutron-vpnaas ships these in python-neutron-vpnaas
+ etc/neutron/rootwrap.d/vpnaas.filters
+ usr/etc/neutron/rootwrap.d/vpnaas.filters

** Also affects: pm-utils (Ubuntu)
   Importance: Undecided
   Status: New

** Also affects: molly-guard (Ubuntu)
   Importance: Undecided
   Status: New

** Description changed:

  bin/rm and usr/bin/rm conflict between coreutils and safe-rm
  
  ---
  Not a conflict, but these just look weird:
  neutron-vpnaas ships these in python-neutron-vpnaas
  etc/neutron/rootwrap.d/vpnaas.filters
  usr/etc/neutron/rootwrap.d/vpnaas.filters
+ 
+ ---
+ pm-utils and molly-guard conflict on:
+ 
+ sbin/pm-hibernate
+ usr/sbin/pm-hibernate
+ sbin/pm-suspend
+ usr/sbin/pm-suspend
+ sbin/pm-suspend-hybrid
+ usr/sbin/pm-suspend-hybrid

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

Title:
  Conflicts between / and /usr

Status in molly-guard package in Ubuntu:
  New
Status in neutron-vpnaas package in Ubuntu:
  New
Status in pm-utils package in Ubuntu:
  New
Status in safe-rm package in Ubuntu:
  New
Status in pm-utils package in Debian:
  Unknown
Status in safe-rm package in Debian:
  Unknown

Bug description:
  bin/rm and usr/bin/rm conflict between coreutils and safe-rm

  ---
  Not a conflict, but these just look weird:
  neutron-vpnaas ships these in python-neutron-vpnaas
  etc/neutron/rootwrap.d/vpnaas.filters
  usr/etc/neutron/rootwrap.d/vpnaas.filters

  ---
  pm-utils and molly-guard conflict on:

  sbin/pm-hibernate
  usr/sbin/pm-hibernate
  sbin/pm-suspend
  usr/sbin/pm-suspend
  sbin/pm-suspend-hybrid
  usr/sbin/pm-suspend-hybrid

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

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

[Desktop-packages] [Bug 1718238] Re: Giant terminal icon is blocking out the Terminal window buttons

2018-05-02 Thread Egmont Koblinger

For those who still see this issue in 18.04:

Is the icon really giant (144x144) for you, as attached to this bug; or
is it somewhat smaller (48x48), as attached to bug 1765704?

Does installing/removing gnome-icon-theme, as per comment 8, do anything
for you?

If you execute xprop from gnome-terminal, then click on gnome-terminal's
window, and scroll back, in what size(s) is/are the icon(s) shown there?

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

Title:
  Giant terminal icon is blocking out the Terminal window buttons

Status in gnome-shell package in Ubuntu:
  Confirmed
Status in mutter package in Ubuntu:
  Confirmed
Status in ubuntu-themes package in Ubuntu:
  Invalid

Bug description:
  Upstream: https://gitlab.gnome.org/GNOME/mutter/issues/23

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: light-themes 16.10+17.10.20170918-0ubuntu1
  ProcVersionSignature: Ubuntu 4.12.0-13.14-generic 4.12.10
  Uname: Linux 4.12.0-13-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Sep 19 12:47:51 2017
  InstallationDate: Installed on 2017-09-19 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170917)
  PackageArchitecture: all
  SourcePackage: ubuntu-themes
  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/1718238/+subscriptions

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

[Desktop-packages] [Bug 1768539] Re: Conflicts between / and /usr

2018-05-02 Thread Dimitri John Ledkov

** Bug watch added: Debian Bug tracker #812545
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=812545

** Also affects: pm-utils (Debian) via
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=812545
   Importance: Unknown
   Status: Unknown

** Also affects: safe-rm (Debian) via
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=812545
   Importance: Unknown
   Status: Unknown

** Changed in: neutron-vpnaas (Ubuntu)
   Importance: Undecided => Wishlist

** Changed in: safe-rm (Ubuntu)
   Importance: Undecided => High

** Changed in: pm-utils (Ubuntu)
   Importance: Undecided => High

** Changed in: molly-guard (Ubuntu)
   Importance: Undecided => High

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

Title:
  Conflicts between / and /usr

Status in molly-guard package in Ubuntu:
  New
Status in neutron-vpnaas package in Ubuntu:
  New
Status in pm-utils package in Ubuntu:
  New
Status in safe-rm package in Ubuntu:
  New
Status in pm-utils package in Debian:
  Unknown
Status in safe-rm package in Debian:
  Unknown

Bug description:
  bin/rm and usr/bin/rm conflict between coreutils and safe-rm

  ---
  Not a conflict, but these just look weird:
  neutron-vpnaas ships these in python-neutron-vpnaas
  etc/neutron/rootwrap.d/vpnaas.filters
  usr/etc/neutron/rootwrap.d/vpnaas.filters

  ---
  pm-utils and molly-guard conflict on:

  sbin/pm-hibernate
  usr/sbin/pm-hibernate
  sbin/pm-suspend
  usr/sbin/pm-suspend
  sbin/pm-suspend-hybrid
  usr/sbin/pm-suspend-hybrid

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

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

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

2018-05-02 Thread Apport retracing service

** Tags removed: need-duplicate-check

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

Title:
  package libp11-kit-gnome-keyring 3.20.1-1ubuntu1 failed to
  install/upgrade: libp11-kit-gnome-keyring:all 3.28.0.2-1ubuntu1
  (Multi-Arch: no) is not co-installable with libp11-kit-gnome-keyring
  which has multiple installed instances

Status in gnome-keyring package in Ubuntu:
  New

Bug description:
  installation of this package failed, upgrading from 17.10.

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: libp11-kit-gnome-keyring 3.20.1-1ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  Date: Wed May  2 01:39:47 2018
  Dependencies:
   gcc-8-base 8-20180414-1ubuntu2
   libc6 2.27-3ubuntu1
   libgcc1 1:8-20180414-1ubuntu2
  DuplicateSignature:
   package:libp11-kit-gnome-keyring:3.20.1-1ubuntu1
   Unpacking gnome-keyring (3.28.0.2-1ubuntu1) over (3.20.1-1ubuntu1) ...
   dpkg: error processing archive 
/tmp/apt-dpkg-install-PlRQuy/0830-libp11-kit-gnome-keyring_3.28.0.2-1ubuntu1_all.deb
 (--unpack):
libp11-kit-gnome-keyring:all 3.28.0.2-1ubuntu1 (Multi-Arch: no) is not 
co-installable with libp11-kit-gnome-keyring which has multiple installed 
instances
  ErrorMessage: libp11-kit-gnome-keyring:all 3.28.0.2-1ubuntu1 (Multi-Arch: no) 
is not co-installable with libp11-kit-gnome-keyring which has multiple 
installed instances
  Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3
  PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu2
   apt  1.6.1
  SourcePackage: gnome-keyring
  Title: package libp11-kit-gnome-keyring 3.20.1-1ubuntu1 failed to 
install/upgrade: libp11-kit-gnome-keyring:all 3.28.0.2-1ubuntu1 (Multi-Arch: 
no) is not co-installable with libp11-kit-gnome-keyring which has multiple 
installed instances
  UpgradeStatus: Upgraded to bionic on 2018-05-02 (0 days ago)

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

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

[Desktop-packages] [Bug 1751252] Re: [regression] ubiquity crashed in debconf.py:104 with ValueError: invalid literal for int() with base 10: ''

2018-05-02 Thread PJSingh5000

Ubiquity also crashes inside a virtual machine (VirtualBox) running on a
non-HiDPI host machine.

I have observed corrupted graphics in the "main area" of Ubiquity when
this bug occurs. By "main area", I am referring to the rendered
rectangular area in Ubiquity below the title bar and above the "Copying
files..." progress bar.

The corruption looks like jagged diagonal lines or "snow". I have seen
this on both actual hardware (HiDPI machine scaled at 200%) and in a
virtual machine (non-HiDPI hardware scaled at 100%).

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

Title:
  [regression] ubiquity crashed in debconf.py:104 with ValueError:
  invalid literal for int() with base 10: ''

Status in OEM Priority Project:
  Triaged
Status in glib2.0 package in Ubuntu:
  Invalid
Status in ubiquity package in Ubuntu:
  Triaged
Status in glib2.0 source package in Bionic:
  Invalid
Status in ubiquity source package in Bionic:
  Triaged

Bug description:
  The Ubuntu installer crashes on hiDPI machines (QHD/UHD etc). Although
  it was working some weeks/months ago, so this is a recent regression.

  ---

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

  ---

  WORKAROUND:

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

  ---

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

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

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

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

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

[Desktop-packages] [Bug 1768549] [NEW] Fix typo "location you chose"

Public bug reported:

Impact
==
Ubuntu 18.04 LTS (desktop) features a new Welcome to Ubuntu wizard which shows 
on the first login after installing or upgrading.

There was a typo in the design documents for the "Help improve Ubuntu"
page.

Test Case
=
1. Download the latest bionic daily image. (This is needed because that image 
will include the updated gnome-initial-setup package and represents a preview 
of 18.04.1. Otherwise, the problem is that the first login after a new install 
will not have SRUs applied yet and gnome-initial-setup is already running 
before update-manager will prompt to install updates.)
2. Install Ubuntu from that image.
3. Restart and log in to Ubuntu
4. On the "Help improve Ubuntu" page, it should say "location you chose" 
instead of "location you choose"

5. Do Steps 1-4 with a language other than English

Regression Potential

The biggest concern here is impact on translations.

Proposed mitigation

1. Temporarily bundle Launchpad translations in the package and set 
X-Ubuntu-Use-Langpack to no
2. Manually tweak the translations so that the updated string is still 
associated with the current translations.
3. Once the updated string is available for translation in Launchpad, email the 
ubuntu-translators list to let them know that the verb tense was changed in the 
English source.

Other Info
==
See also
https://github.com/CanonicalLtd/desktop-design/issues/102

You can restart the wizard after completing it by removing
~/.config/gnome-initial-setup-done
It won't show the Livepatch page if that has already been set up, but that's 
not important for this bug.

** Affects: gnome-initial-setup (Ubuntu)
 Importance: Low
 Status: Triaged


** Tags: bionic

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

Title:
  Fix typo "location you chose"

Status in gnome-initial-setup package in Ubuntu:
  Triaged

Bug description:
  Impact
  ==
  Ubuntu 18.04 LTS (desktop) features a new Welcome to Ubuntu wizard which 
shows on the first login after installing or upgrading.

  There was a typo in the design documents for the "Help improve Ubuntu"
  page.

  Test Case
  =
  1. Download the latest bionic daily image. (This is needed because that image 
will include the updated gnome-initial-setup package and represents a preview 
of 18.04.1. Otherwise, the problem is that the first login after a new install 
will not have SRUs applied yet and gnome-initial-setup is already running 
before update-manager will prompt to install updates.)
  2. Install Ubuntu from that image.
  3. Restart and log in to Ubuntu
  4. On the "Help improve Ubuntu" page, it should say "location you chose" 
instead of "location you choose"

  5. Do Steps 1-4 with a language other than English

  Regression Potential
  
  The biggest concern here is impact on translations.

  Proposed mitigation
  
  1. Temporarily bundle Launchpad translations in the package and set 
X-Ubuntu-Use-Langpack to no
  2. Manually tweak the translations so that the updated string is still 
associated with the current translations.
  3. Once the updated string is available for translation in Launchpad, email 
the ubuntu-translators list to let them know that the verb tense was changed in 
the English source.

  Other Info
  ==
  See also
  https://github.com/CanonicalLtd/desktop-design/issues/102

  You can restart the wizard after completing it by removing
  ~/.config/gnome-initial-setup-done
  It won't show the Livepatch page if that has already been set up, but that's 
not important for this bug.

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

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

Re: [Desktop-packages] [Bug 1768306] Re: LibreOffice crash

2018-05-02 Thread Matt

Well it works perfectly after that !
It just outputs "Warning: failed to read path from javaldx" in bash.

Great work :)

2018-05-02 15:31 GMT+02:00 Olivier Tilloy
:

> > OS: Ubuntu Budgie 18.04 32-bit
>
> That's very likely a duplicate of bug #1699772.
>
> To confirm this, can you run the following command in a terminal:
>
> sed -i '/enabled/c\false<\/enabled>'
> ~/.config/libreoffice/4/user/config/javasettings_Linux_*.xml
>
> Then execute libreoffice writer and let me know if the crash is still
> happening? Thanks!
>
> ** Changed in: libreoffice (Ubuntu)
>Status: New => Incomplete
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1768306
>
> Title:
>   LibreOffice crash
>
> Status in Ubuntu Budgie:
>   New
> Status in libreoffice package in Ubuntu:
>   Incomplete
>
> Bug description:
>   Whenever LibreOffice Writer is launched, it does not load and a crash
> report appears.
>   And if it is launched via the command line, it doesn't even show any
> info or error message.
>
>   The LibreOffice base and Calc opens OK though.
>
>   System info:
>
>   OS: Ubuntu Budgie 18.04 32-bit
>   PC: Sony Vaio VGN-FE21H
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntubudgie/+bug/1768306/+subscriptions
>

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

Title:
  LibreOffice crash

Status in Ubuntu Budgie:
  New
Status in libreoffice package in Ubuntu:
  Incomplete

Bug description:
  Whenever LibreOffice Writer is launched, it does not load and a crash report 
appears.
  And if it is launched via the command line, it doesn't even show any info or 
error message.

  The LibreOffice base and Calc opens OK though.

  System info:

  OS: Ubuntu Budgie 18.04 32-bit
  PC: Sony Vaio VGN-FE21H

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

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

[Desktop-packages] [Bug 1705369] Re: Ubuntu 17.10/18.04 boots to black screen when using Nvidia drivers (on a desktop with an Intel GPU)

2018-05-02 Thread Jan Sundman

I'm also affected by this bug on Ubuntu 18.04. This happens both with
nvidia-driver-390 and nvidia-driver-396.

My graphics card model is a Nvidia GM107GLM [Quadro M1200 Mobile] on a
Dell Precision 5520 laptop

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

Title:
  Ubuntu 17.10/18.04 boots to black screen when using Nvidia drivers (on
  a desktop with an Intel GPU)

Status in gdm3 package in Ubuntu:
  Confirmed
Status in gnome-shell package in Ubuntu:
  Invalid
Status in nvidia-graphics-drivers-375 package in Ubuntu:
  Won't Fix
Status in nvidia-graphics-drivers-384 package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu 17.10 boots to black screen when using Nvidia drivers (on a
  desktop with an Intel GPU)

  WORKAROUNDS:

  * Disable integrated graphics/GPU in your BIOS.

  * Add 'nomodeset' to your kernel command line.

  
  ORIGINAL DESCRIPTION:

  This bug is very similar to
  https://bugs.launchpad.net/ubuntu-gnome/+bug/1559576
  which is closed. I have been asked to open a new bug report.

  The issue is on Ubuntu 17.10 with gdm3 fully updated as of July 20,
  2017. I upgraded to 17.10 from a freshly installed Ubuntu 17.04.

  - Lightdm works
  - Nouveau driver works
  - Nvidia driver 375.66 (proprietary) does not work
  - Nvidia driver 384.47 (open source) does not work (from 
https://launchpad.net/~graphics-drivers/+archive/ubuntu/ppa)
  - Nvidia drivers work with Ubuntu Gnome 17.04

  I am using Nvidia GTX 1080 and Intel i7-4790K

  lsb_release -rd:
  Description:  Ubuntu Artful Aardvark (development branch)
  Release:  17.10

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

  uname -s -r -v -p -i -o:
  Linux 4.11.0-11-generic #16-Ubuntu SMP Wed Jul 12 20:40:19 UTC 2017 x86_64 
x86_64 GNU/Linux

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

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

[Desktop-packages] [Bug 1749007] Re: Snap mounts should be hidden from System Monitor

the patch looks fine but it's a bit weird to add the new argument to the
function to the begin of the arguments and not the end, though the API
is not public so it shouldn't really matter. It looks fine to me for a
SRU so I'm going to sponsor it this week

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

Title:
  Snap mounts should be hidden from System Monitor

Status in gnome-system-monitor package in Ubuntu:
  In Progress

Bug description:
  As per https://community.ubuntu.com/t/snaps-in-system-monitor/3961 the
  snap mounts in System Monitor should be hidden just as they're hidden
  from GNOME Disks. Perhaps they should be grouped under a dropdown of /
  (though this would require developing a new feature)?

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

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

[Desktop-packages] [Bug 1767574] Re: number of cores in Resource tab

Thank you for taking the time to report this bug and helping to make
Ubuntu better. The issue you are reporting is an upstream one and it
would be nice if somebody having it could send the bug to the developers
of the software by following the instructions at
https://wiki.ubuntu.com/Bugs/Upstream/GNOME. If you have done so, please
tell us the number of the upstream bug (or the link), so we can add a
bugwatch that will inform us about its status. Thanks in advance.

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

** Summary changed:

- number of cores in Resource tab
+ tweaks to display of number of cores in Resource tab

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

Title:
  tweaks to display of number of cores in Resource tab

Status in gnome-system-monitor package in Ubuntu:
  New

Bug description:
  Not a bug but an enhancement ... I have 6 cores (AMD FX 6300) and the
  resource tab shows 4 cores as the first row and 2 cores in the second.
  It would look nicer to line them up as 3 on 1st row and 3 on 2nd row.
  Also, note the vertical spacing between cpu1 and cpu5; too tight.

  Here's a screenshot: https://imgur.com/a/JUFNWlc

  Thanks.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-system-monitor (not installed)
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Apr 27 22:14:20 2018
  InstallationDate: Installed on 2018-04-27 (1 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no username)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-system-monitor
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1748611] Re: Desktop symbols disappear after changing symbol size in nautilus

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

that seems similar to bug #1537606

** This bug has been marked a duplicate of bug 1537606
   Changing icon sizes causes desktop icon sizes to change too

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

Title:
  Desktop symbols disappear after changing symbol size in nautilus

Status in nautilus package in Ubuntu:
  Incomplete

Bug description:
  Problem: When changing the size of folder symbols in the nautilus file
  browser, the symbol size for desktop symbols is also changed. That
  might result in the (temporary) disappearing of desktop symbols.

  How to reproduce the bug: Place some symbols on the right edge of the
  desktop. Open nautilus, increase the size of symbols. The symbol size
  for the desktop and the symbol grid size are also affected by that
  change, symbols placed at the edge will disappear.

  What I expect to happen: Changing the symbol size in nautilus should
  not affect the desktop symbol size/symbol grid size.

  What actually happens: Changing the symbol size in nautilus will
  change the desktop symbol size/ grid size, symbols on the desktop
  might disappear.

  Ubuntu version: 17.10
  ubuntu-session version: 3.26.1-0ubuntu6

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

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

[Desktop-packages] [Bug 1761844] Re: Thunderbird: emojis is displayed in the email list

2018-05-02 Thread Bug Watch Updater

** Changed in: thunderbird
   Status: Unknown => Invalid

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

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

Title:
  Thunderbird: emojis is displayed in the email list

Status in Mozilla Thunderbird:
  Invalid
Status in thunderbird package in Ubuntu:
  Confirmed

Bug description:
  The list of emails received from Thunderbird shows emojis. This does not 
happen with all accounts.
  It appears to be with the last email address added.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: thunderbird 1:52.6.0+build1-0ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15
  Uname: Linux 4.15.0-15-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  AddonCompatCheckDisabled: False
  ApportVersion: 2.20.9-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   diego  1607 F...m pulseaudio
   /dev/snd/controlC0:  diego  1607 F pulseaudio
   /dev/snd/controlC1:  diego  1607 F pulseaudio
  BuildID: 20180131200234
  Channel: Unavailable
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Apr  6 15:58:17 2018
  Extensions: extensions.sqlite corrupt or missing
  ForcedLayersAccel: False
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  IncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
  InstallationDate: Installed on 2018-04-05 (1 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Beta amd64 (20180404)
  IpRoute:
   default via 181.31.1.1 dev enp2s0 proto dhcp metric 100 
   169.254.0.0/16 dev enp2s0 scope link metric 1000 
   181.31.1.0/24 dev enp2s0 proto kernel scope link src 181.31.1.84 metric 100
  IwConfig:
   lono wireless extensions.
   
   enp2s0no wireless extensions.
  Locales: extensions.sqlite corrupt or missing
  PrefSources: prefs.js
  Profiles: Profile0 (Default) - LastVersion=52.6.0/20180131200234 (In use)
  RfKill:
   
  RunningIncompatibleAddons: False
  SourcePackage: thunderbird
  Themes: extensions.sqlite corrupt or missing
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/14/2012
  dmi.bios.vendor: Award Software International, Inc.
  dmi.bios.version: F4
  dmi.board.name: GA-78LMT-S2
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrF4:bd08/14/2012:svnGigabyteTechnologyCo.,Ltd.:pnGA-78LMT-S2:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-78LMT-S2:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
  dmi.product.name: GA-78LMT-S2
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

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

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

[Desktop-packages] [Bug 1768556] [NEW] Tilde/macron is no longer a dead key on German keyboard

2018-05-02 Thread Michael von Glasow

Public bug reported:

Steps to reproduce:

1. Enable the German keyboard layout.
2. Open a text editor of your choice.
3. Press AltGr and + (second key after P), then press a.
4. Press AltGr + Shift and +, then press a.

Expected behavior:

Key acts as a dead key, the key sequences produce ã and ā, respectively.

Actual behavior:

Key acts as a regular key, the key sequences produce ~a and ¯a,
respectively. This breaks the ability to easily input diacritics for
several languages (including Portuguese, Spanish, Estonian, Latvian,
Lithuanian).

Additional information:

Both keystrokes acted as dead keys in Ubuntu 16.04. I doubt removing the
dead key functionality was intentional: While I do understand that some
people might need the tilde key frequently but hardly ever need a tilde
accent, I cannot think of many situations in which one would require a
bare macron. Plus, for situations in which dead keys are undesirable,
there is also a “nodeadkeys” variant of the German layout, which has
been around for some time.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xkb-data 2.23.1-1ubuntu1
ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
Uname: Linux 4.15.0-20-generic x86_64
ApportVersion: 2.20.9-0ubuntu7
Architecture: amd64
CurrentDesktop: MATE
Date: Wed May  2 16:16:00 2018
Dependencies:
 
DistUpgraded: 2018-05-01 00:48:55,072 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
DistroCodename: bionic
DistroVariant: ubuntu
EcryptfsInUse: Yes
InstallationDate: Installed on 2016-01-29 (824 days ago)
InstallationMedia: Ubuntu-MATE 15.10 "Wily Werewolf" - Release amd64 (20151021)
Lsusb:
 Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet
 Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
MachineType: innotek GmbH VirtualBox
PackageArchitecture: all
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-20-generic 
root=UUID=a1cb66fa-2942-48a4-b7d8-13881405227a ro quiet splash
SourcePackage: xkeyboard-config
UpgradeStatus: Upgraded to bionic on 2018-04-30 (1 days ago)
dmi.bios.date: 12/01/2006
dmi.bios.vendor: innotek GmbH
dmi.bios.version: VirtualBox
dmi.board.name: VirtualBox
dmi.board.vendor: Oracle Corporation
dmi.board.version: 1.2
dmi.chassis.type: 1
dmi.chassis.vendor: Oracle Corporation
dmi.modalias: 
dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr:
dmi.product.family: Virtual Machine
dmi.product.name: VirtualBox
dmi.product.version: 1.2
dmi.sys.vendor: innotek GmbH
version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
version.libdrm2: libdrm2 2.4.91-2
version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1
version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

** Affects: xkeyboard-config (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug bionic ubuntu

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

Title:
  Tilde/macron is no longer a dead key on German keyboard

Status in xkeyboard-config package in Ubuntu:
  New

Bug description:
  Steps to reproduce:

  1. Enable the German keyboard layout.
  2. Open a text editor of your choice.
  3. Press AltGr and + (second key after P), then press a.
  4. Press AltGr + Shift and +, then press a.

  Expected behavior:

  Key acts as a dead key, the key sequences produce ã and ā,
  respectively.

  Actual behavior:

  Key acts as a regular key, the key sequences produce ~a and ¯a,
  respectively. This breaks the ability to easily input diacritics for
  several languages (including Portuguese, Spanish, Estonian, Latvian,
  Lithuanian).

  Additional information:

  Both keystrokes acted as dead keys in Ubuntu 16.04. I doubt removing
  the dead key functionality was intentional: While I do understand that
  some people might need the tilde key frequently but hardly ever need a
  tilde accent, I cannot think of many situations in which one would
  require a bare macron. Plus, for situations in which dead keys are
  undesirable, there is also a “nodeadkeys” variant of the German
  layout, which has been around for some time.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xkb-data 2.23.1-1ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: MATE
  Date: Wed May  2 16:16:00 2018
  Dependencies:
   
  DistUpgraded: 2018-05-01 00:48:55,072 DEBUG Running PostInsta

[Desktop-packages] [Bug 1759625] Re: FFe: Sync gimp 2.10.0~RC2-1 (universe) from Debian experimental (main)

** Also affects: gimp (Ubuntu Bionic)
   Importance: Undecided
   Status: New

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

** Changed in: gimp (Ubuntu Bionic)
   Status: New => Won't Fix

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

Title:
  FFe: Sync gimp 2.10.0~RC2-1 (universe) from Debian experimental (main)

Status in MyPaint:
  New
Status in gimp package in Ubuntu:
  Fix Released
Status in gimp source package in Bionic:
  Won't Fix

Bug description:
  Feature Freeze Justification
  
  gimp's last new stable series, 2.8, was released 6 years ago. The new series 
has years of work porting gimp to use gegl more completely, an integrated crash 
report tool, and many more improvements.

  The Gimp development team is so small that I do not expect there to be
  much support at all for gimp 2.8 any more.

  Future
  ==
  If the final gimp 2.10 is not released before Ubuntu 18.04 LTS is, then we 
should do an SRU to update it then.

  The Gimp developers have announced that they will add features to
  future 2.10 releases so that users won't have to wait several years
  like this again.

  Gimp 3.0 will switch to gtk3 (or gtk4).

  Affected Flavors
  
  Ubuntu Studio is the only flavor to include gimp by default.

  Changes
  ===
  This entire file!
  https://git.gnome.org/browse/gimp/tree/NEWS

  Features are described in several blog posts documenting the 2.9
  development releases at https://www.gimp.org/news/

  Changes in the new Debian version
  =
  Uploaded to experimental on request of the Debian maintainer Ari Pollack.

   gimp (2.10.0~RC1-1) experimental; urgency=medium
   .
     * New upstream release candidate (LP: #1759625)
   - Fixes screenshots in GNOME and KDE on Wayland (Closes: #880186)
     (LP: #1739684)
     * Bump dependencies per configure.ac
     * Add new Build-Depends: gegl, glib-networking, libgexiv2-dev,
   libmypaint-dev, libopenjp2-7-dev (Closes: #827083), libopenexr-dev,
   libwebp-dev, mypaint-brushes, python-cairo-dev
     * Depend on xdg-utils for email feature
     * Update debian/libgimp2.0.symbols
     * Drop all patches (except 01_hurd_ftbfs.patch) since they are obsolete
   with the new release

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

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

[Desktop-packages] [Bug 1768555] [NEW] Update gnome-calendar to 3.28.2

Public bug reported:

placeholder bug. Please fill in.

Impact
--

Test Case
--

Regression Potential


** Affects: gnome-calendar (Ubuntu)
 Importance: Low
 Status: Confirmed

** Affects: gnome-calendar (Ubuntu Bionic)
 Importance: Low
 Status: Confirmed


** Tags: bionic upgrade-software-version

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

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

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

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

Title:
  Update gnome-calendar to 3.28.2

Status in gnome-calendar package in Ubuntu:
  Confirmed
Status in gnome-calendar source package in Bionic:
  Confirmed

Bug description:
  placeholder bug. Please fill in.

  Impact
  --

  Test Case
  --

  Regression Potential
  

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

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

[Desktop-packages] [Bug 1768558] [NEW] At start-up displays only root terminal

2018-05-02 Thread sean markham

Public bug reported:

SORRY I thought I had a duplicate "adwaita-icon-theme" and removed the
small. Now no regular start-up only root. Tried to reinstall thru
package manager while using usb as start-up drive, but still only root
at start-up.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg 1:7.7+13ubuntu3
ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
Uname: Linux 4.4.0-21-generic i686
ApportVersion: 2.20.1-0ubuntu2
Architecture: i386
CasperVersion: 1.376
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
Date: Wed May  2 14:29:14 2018
DistUpgraded: Fresh install
DistroCodename: xenial
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 Intel Corporation Mobile GM965/GL960 Integrated Graphics Controller (primary) 
[8086:2a02] (rev 0c) (prog-if 00 [VGA controller])
   Subsystem: Dell Mobile GM965/GL960 Integrated Graphics Controller (primary) 
[1028:01fe]
   Subsystem: Dell Mobile GM965/GL960 Integrated Graphics Controller 
(secondary) [1028:01fe]
LiveMediaBuild: Lubuntu 16.04 LTS "Xenial Xerus" - Release i386 (20160420.1)
MachineType: Dell Inc. Latitude D830
ProcEnviron:
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: file=/cdrom/preseed/hostname.seed boot=casper 
initrd=/casper/initrd.lz quiet splash ---
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 06/07/2007
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A02
dmi.board.name: 0HN341
dmi.board.vendor: Dell Inc.
dmi.chassis.type: 8
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvrA02:bd06/07/2007:svnDellInc.:pnLatitudeD830:pvr:rvnDellInc.:rn0HN341:rvr:cvnDellInc.:ct8:cvr:
dmi.product.name: Latitude D830
dmi.sys.vendor: Dell Inc.
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.67-1
version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2
version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2

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


** Tags: apport-bug i386 ubuntu xenial

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

Title:
  At start-up displays only root terminal

Status in xorg package in Ubuntu:
  New

Bug description:
  SORRY I thought I had a duplicate "adwaita-icon-theme" and removed the
  small. Now no regular start-up only root. Tried to reinstall thru
  package manager while using usb as start-up drive, but still only root
  at start-up.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic i686
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: i386
  CasperVersion: 1.376
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Wed May  2 14:29:14 2018
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation Mobile GM965/GL960 Integrated Graphics Controller 
(primary) [8086:2a02] (rev 0c) (prog-if 00 [VGA controller])
 Subsystem: Dell Mobile GM965/GL960 Integrated Graphics Controller 
(primary) [1028:01fe]
 Subsystem: Dell Mobile GM965/GL960 Integrated Graphics Controller 
(secondary) [1028:01fe]
  LiveMediaBuild: Lubuntu 16.04 LTS "Xenial Xerus" - Release i386 (20160420.1)
  MachineType: Dell Inc. Latitude D830
  ProcEnviron:
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: file=/cdrom/preseed/hostname.seed boot=casper 
initrd=/casper/initrd.lz quiet splash ---
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/07/2007
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A02
  dmi.board.name: 0HN341
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA02:bd06/07/2007:svnDellInc.:pnLatitudeD830:pvr:rvnDellInc.:rn0HN341:rvr:cvnDellInc.:ct8:cvr:
  dmi.product.name: Latitude D830
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.67-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu

[Desktop-packages] [Bug 1768557] [NEW] Update what's new graphic for Welcome to Ubuntu wizard

Public bug reported:

Impact
==
Ubuntu 18.04 LTS (desktop) features a new Welcome to Ubuntu wizard which shows 
on the first login after installing or upgrading.

This updates the graphic shown on the What's new in Ubuntu screen

"Clock and calendar" has been renamed to "Calendar and notifications"
"Launcher" has been renamed to "Dock"

Test Case
=
1. Download the latest bionic daily image. (This is needed because that image 
will include the updated gnome-initial-setup package and represents a preview 
of 18.04.1. Otherwise, the problem is that the first login after a new install 
will not have SRUs applied yet and gnome-initial-setup is already running 
before update-manager will prompt to install updates.)
2. Install Ubuntu from that image.
3. Restart and log in to Ubuntu
4. Verify that the label changes have been made on the first page of the 
Welcome to Ubuntu wizard

Regression Potential

None; this is just a substitution of a .png.

Other Info
==
See also
https://github.com/CanonicalLtd/desktop-design/issues/101

The graphic is just a .png and is not translatable yet. See LP: #1766277

You can restart the wizard after completing it by removing
~/.config/gnome-initial-setup-done

** Affects: gnome-initial-setup (Ubuntu)
 Importance: Low
 Status: In Progress

** Affects: gnome-initial-setup (Ubuntu Bionic)
 Importance: Low
 Status: Triaged


** Tags: bionic

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

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

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

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

Title:
  Update what's new graphic for Welcome to Ubuntu wizard

Status in gnome-initial-setup package in Ubuntu:
  In Progress
Status in gnome-initial-setup source package in Bionic:
  Triaged

Bug description:
  Impact
  ==
  Ubuntu 18.04 LTS (desktop) features a new Welcome to Ubuntu wizard which 
shows on the first login after installing or upgrading.

  This updates the graphic shown on the What's new in Ubuntu screen

  "Clock and calendar" has been renamed to "Calendar and notifications"
  "Launcher" has been renamed to "Dock"

  Test Case
  =
  1. Download the latest bionic daily image. (This is needed because that image 
will include the updated gnome-initial-setup package and represents a preview 
of 18.04.1. Otherwise, the problem is that the first login after a new install 
will not have SRUs applied yet and gnome-initial-setup is already running 
before update-manager will prompt to install updates.)
  2. Install Ubuntu from that image.
  3. Restart and log in to Ubuntu
  4. Verify that the label changes have been made on the first page of the 
Welcome to Ubuntu wizard

  Regression Potential
  
  None; this is just a substitution of a .png.

  Other Info
  ==
  See also
  https://github.com/CanonicalLtd/desktop-design/issues/101

  The graphic is just a .png and is not translatable yet. See LP:
  #1766277

  You can restart the wizard after completing it by removing
  ~/.config/gnome-initial-setup-done

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

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

[Desktop-packages] [Bug 1768549] Re: Fix typo "location you chose"

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

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

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

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

Title:
  Fix typo "location you chose"

Status in gnome-initial-setup package in Ubuntu:
  Triaged
Status in gnome-initial-setup source package in Bionic:
  Triaged

Bug description:
  Impact
  ==
  Ubuntu 18.04 LTS (desktop) features a new Welcome to Ubuntu wizard which 
shows on the first login after installing or upgrading.

  There was a typo in the design documents for the "Help improve Ubuntu"
  page.

  Test Case
  =
  1. Download the latest bionic daily image. (This is needed because that image 
will include the updated gnome-initial-setup package and represents a preview 
of 18.04.1. Otherwise, the problem is that the first login after a new install 
will not have SRUs applied yet and gnome-initial-setup is already running 
before update-manager will prompt to install updates.)
  2. Install Ubuntu from that image.
  3. Restart and log in to Ubuntu
  4. On the "Help improve Ubuntu" page, it should say "location you chose" 
instead of "location you choose"

  5. Do Steps 1-4 with a language other than English

  Regression Potential
  
  The biggest concern here is impact on translations.

  Proposed mitigation
  
  1. Temporarily bundle Launchpad translations in the package and set 
X-Ubuntu-Use-Langpack to no
  2. Manually tweak the translations so that the updated string is still 
associated with the current translations.
  3. Once the updated string is available for translation in Launchpad, email 
the ubuntu-translators list to let them know that the verb tense was changed in 
the English source.

  Other Info
  ==
  See also
  https://github.com/CanonicalLtd/desktop-design/issues/102

  You can restart the wizard after completing it by removing
  ~/.config/gnome-initial-setup-done
  It won't show the Livepatch page if that has already been set up, but that's 
not important for this bug.

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

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

[Desktop-packages] [Bug 1748611] Re: Desktop symbols disappear after changing symbol size in nautilus

2018-05-02 Thread Simon P.

It is not a duplicate of bug 1537606. The problem I reported is that the
icons disappear on the desktop when they are placed  at the right side
of the desktop and the icon size is increased. I don't see the
correlation of the icon size of nautilus and the desktop as a problem,
the problem is that the icons disappear! That bug first appeared with
the introduction of the Gnome shell in 17.10.

** This bug is no longer a duplicate of bug 1537606
   Changing icon sizes causes desktop icon sizes to change too

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

Title:
  Desktop symbols disappear after changing symbol size in nautilus

Status in nautilus package in Ubuntu:
  Incomplete

Bug description:
  Problem: When changing the size of folder symbols in the nautilus file
  browser, the symbol size for desktop symbols is also changed. That
  might result in the (temporary) disappearing of desktop symbols.

  How to reproduce the bug: Place some symbols on the right edge of the
  desktop. Open nautilus, increase the size of symbols. The symbol size
  for the desktop and the symbol grid size are also affected by that
  change, symbols placed at the edge will disappear.

  What I expect to happen: Changing the symbol size in nautilus should
  not affect the desktop symbol size/symbol grid size.

  What actually happens: Changing the symbol size in nautilus will
  change the desktop symbol size/ grid size, symbols on the desktop
  might disappear.

  Ubuntu version: 17.10
  ubuntu-session version: 3.26.1-0ubuntu6

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

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

[Desktop-packages] [Bug 1766137] Re: [regression] Password accepted but login fails (blank purple screen and mouse pointer only)

2018-05-02 Thread Davide

coolhandlewk
You are right, I misunderstood.
It works for me too, thanks.

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

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

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

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

  ---

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

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

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

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

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

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

[Desktop-packages] [Bug 1768567] [NEW] Mouse not click after clean install ubuntub18.04

2018-05-02 Thread rolivares

Public bug reported:

After upgrade from 17.10 to 18.04 mouse not accept click. Do a clean
install. Firs works well but after update the bug start again. Mouse
work im login screen. I tried in waylan and xorg and is the same. Acer
aspire f15  intel graphics 520. Core I5-6200u

** Affects: gnome-shell (Ubuntu)
 Importance: Undecided
 Status: 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/1768567

Title:
  Mouse not click after clean install ubuntub18.04

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  After upgrade from 17.10 to 18.04 mouse not accept click. Do a clean
  install. Firs works well but after update the bug start again. Mouse
  work im login screen. I tried in waylan and xorg and is the same. Acer
  aspire f15  intel graphics 520. Core I5-6200u

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

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

[Desktop-packages] [Bug 1768556] Re: Tilde/macron is no longer a dead key on German keyboard

2018-05-02 Thread Gunnar Hjalmarsson

Thanks for your report.

It seems to be an intentional upstream change of the basic German
layout:

https://cgit.freedesktop.org/xkeyboard-
config/commit/symbols/de?id=49129c63

So it's not a bug.

The good news is that the "German (dead tilde)" layout variant provides
the behavior you prefer.

** Changed in: xkeyboard-config (Ubuntu)
   Status: New => Invalid

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

Title:
  Tilde/macron is no longer a dead key on German keyboard

Status in xkeyboard-config package in Ubuntu:
  Invalid

Bug description:
  Steps to reproduce:

  1. Enable the German keyboard layout.
  2. Open a text editor of your choice.
  3. Press AltGr and + (second key after P), then press a.
  4. Press AltGr + Shift and +, then press a.

  Expected behavior:

  Key acts as a dead key, the key sequences produce ã and ā,
  respectively.

  Actual behavior:

  Key acts as a regular key, the key sequences produce ~a and ¯a,
  respectively. This breaks the ability to easily input diacritics for
  several languages (including Portuguese, Spanish, Estonian, Latvian,
  Lithuanian).

  Additional information:

  Both keystrokes acted as dead keys in Ubuntu 16.04. I doubt removing
  the dead key functionality was intentional: While I do understand that
  some people might need the tilde key frequently but hardly ever need a
  tilde accent, I cannot think of many situations in which one would
  require a bare macron. Plus, for situations in which dead keys are
  undesirable, there is also a “nodeadkeys” variant of the German
  layout, which has been around for some time.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xkb-data 2.23.1-1ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: MATE
  Date: Wed May  2 16:16:00 2018
  Dependencies:
   
  DistUpgraded: 2018-05-01 00:48:55,072 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: bionic
  DistroVariant: ubuntu
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2016-01-29 (824 days ago)
  InstallationMedia: Ubuntu-MATE 15.10 "Wily Werewolf" - Release amd64 
(20151021)
  Lsusb:
   Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet
   Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: innotek GmbH VirtualBox
  PackageArchitecture: all
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-20-generic 
root=UUID=a1cb66fa-2942-48a4-b7d8-13881405227a ro quiet splash
  SourcePackage: xkeyboard-config
  UpgradeStatus: Upgraded to bionic on 2018-04-30 (1 days ago)
  dmi.bios.date: 12/01/2006
  dmi.bios.vendor: innotek GmbH
  dmi.bios.version: VirtualBox
  dmi.board.name: VirtualBox
  dmi.board.vendor: Oracle Corporation
  dmi.board.version: 1.2
  dmi.chassis.type: 1
  dmi.chassis.vendor: Oracle Corporation
  dmi.modalias: 
dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr:
  dmi.product.family: Virtual Machine
  dmi.product.name: VirtualBox
  dmi.product.version: 1.2
  dmi.sys.vendor: innotek GmbH
  version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
  version.libdrm2: libdrm2 2.4.91-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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

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

[Desktop-packages] [Bug 1767096] Re: Random Xorg crashes

2018-05-02 Thread spodin

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

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

Title:
  Random Xorg crashes

Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  Xorg crashes randomly: environment just freezes for a second and I'm
  getting login screen.

  ProblemType: Bug
  DistroRelease: elementary 0.4.1
  Package: xorg 1:7.7+13ubuntu3 [origin: Ubuntu]
  ProcVersionSignature: Ubuntu 4.13.0-39.44~16.04.1-generic 4.13.16
  Uname: Linux 4.13.0-39-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.16
  Architecture: amd64
  CurrentDesktop: Pantheon
  Date: Thu Apr 26 12:57:22 2018
  InstallationDate: Installed on 2018-03-01 (55 days ago)
  InstallationMedia: elementary OS 0.4.1 "Loki" - Stable amd64 (20180214)
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1568056] Re: Official Package-Names Not Shown in Gnome-Software

2018-05-02 Thread Lonnie Lee Best

** Tags added: bionic

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

Title:
  Official Package-Names Not Shown in Gnome-Software

Status in gnome-software package in Ubuntu:
  Confirmed

Bug description:
  The names of a packages (as you would type them when installing via a
  command prompt) are not indicated in gnome-software.

  Even when I use gnome-software to locate a package, I still want to
  know the package's official Ubuntu name, because I usually want to add
  that package-name to an command install list (sudo apt-get install
  package1 package2 package3), so that I can install all my packages at
  once the next time I do a fresh install.

  That fact that gnome-software can locate packages for me is great. The
  fact that it doesn't reveal the official name of the packages is
  lacking (for me).

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: gnome-software 3.20.1~git20160331.78d1aab-0ubuntu2
  ProcVersionSignature: Ubuntu 4.4.0-17.33-generic 4.4.6
  Uname: Linux 4.4.0-17-generic x86_64
  ApportVersion: 2.20.1-0ubuntu1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Apr  8 12:18:43 2016
  InstallationDate: Installed on 2016-03-14 (25 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160307)
  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/1568056/+subscriptions

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

[Desktop-packages] [Bug 1767784] Re: [regression] output device not recognized anymore since update 1:8.0-0ubuntu3.9

2018-05-02 Thread Michael Pardee

1:8.0-0ubuntu3.10 from proposed fixes the problem

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

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

Title:
  [regression] output device not recognized anymore since update
  1:8.0-0ubuntu3.9

Status in pulseaudio package in Ubuntu:
  Fix Committed
Status in pulseaudio source package in Xenial:
  Fix Committed

Bug description:
  SRU Document:

  [Impact]

  The 1:8.0-0ubuntu3.9 introduced a new problem on the machines which do
  not have internal speaker on them. With the 1:8.0-0ubuntu3.8, even
  there is no internal speaker and nothing plugged in the audio jack,
  the profile is still set available, then the active profile is analog-
  stereo; while with the 1:8.0-0ubuntu3.9, the profile is set to
  unavailable, and the active profile is off, after users plug sth in
  the audio jack, the active profile will not switch automatically, need
  users to switch manually, this change is unfriendly to users.

  [Test Case]

  On the machines without internal speaker, open sound-setting and check
  if there is some output devices in the UI, and play sound from the UI.
  Under 1:8.0-0ubuntu3.9 there is no output device, and can't play
  sound; under 1:8.0-0ubuntu3.8 there is output device, and can play
  sound.

  [Regression Potential]

  This is a revert, after reverting, the content of pulseaudio is
  exactly same as 1:8.0-0ubuntu3.8

  [Other Info]

  none

  
  Since the update 1:8.0-0ubuntu3.8 to 1:8.0-0ubuntu3.9 , pulseaudio is not 
showing anymore my soundcard.

  https://launchpad.net/ubuntu/+source/pulseaudio/1:8.0-0ubuntu3.9

  The command "pacmd list-sinks" only shows a dummy output

  When running on a fresh install of ubuntu 16.04, the sound is ok.
  When updating the install with locking the following files to version 
1:8.0-0ubuntu3 the sound keeps working:
  libpulse0:amd64
  libpulse-mainloop-glib0:amd64
  libpulse-dev:amd64
  pulseaudio-module-x11:amd64
  pulseaudio-module-bluetooth:amd64
  pulseaudio-utils:amd64

  When updating to 1:8.0-0ubuntu3.9, I just get a "dummy output".

  I tried running the following versions of Ubuntu (live usb), and get the same 
issue (no need to update to get the problem)
  17.04
  17.10
  18.04

  I attached the result of command "pactl list"
  I have also generated logs during the boot but I don't know how to attach 
multiple files

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

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

[Desktop-packages] [Bug 1741977] Re: SCX-3200, scanning fails after migration to Kubuntu 17.10