[Desktop-packages] [Bug 1868332] Re: Scrolling jumps after switching windows

[Diego Garcia]

Same with me.

Ubuntu 22.04.3
Kernel 6.2.0-37
Gnome 42.9
Xorg 1:7.7+23ubuntu2

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

Title:
  Scrolling jumps after switching windows

Status in mutter package in Ubuntu:
  Confirmed

Bug description:
  The bug has to do with mouse scrolling and switching windows; I do not
  know which package it is part of.

  The problem arises when I have two windows of two different
  applications open, such as Google Chrome and a text editor. To
  reproduce the error, I have Google Chrome open initially, then I
  switch tabs (using the shortcut Alt-Tab) to the text editor, then
  scroll around on the text editor. When I Alt-Tab back to Google
  Chrome, my first scroll leads to the page jumping by a large amount
  either up or down before resuming regular mouse scrolling. It is only
  this initial scroll after switching tabs that jumps like this. It also
  happens regardless of whether I use a mouse or the touch pad.

  I also notice, given the same scenario, if I scroll up on the text
  editor, the Google Chrome initial scroll jump will be upward. If I
  scroll down on the text editor, the Chrome jump will be downward. If I
  scroll a lot in the text editor, the Chrome jump will be large. If I
  scroll a small amount in the text editor, the Chrome jump will be
  small.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 5.3.0-40.32~18.04.1-generic 5.3.18
  Uname: Linux 5.3.0-40-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.11
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Mar 20 17:17:39 2020
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA 
controller])
 Subsystem: Hewlett-Packard Company UHD Graphics 620 [103c:83b9]
  InstallationDate: Installed on 2020-01-26 (54 days ago)
  InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 
(20190805)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 8087:0a2b Intel Corp. 
   Bus 001 Device 002: ID 04f2:b593 Chicony Electronics Co., Ltd 
   Bus 001 Device 004: ID 046d:c52b Logitech, Inc. Unifying Receiver
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: HP HP Spectre x360 Convertible 13-ae0xx
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-40-generic 
root=UUID=7cfa547e-7b38-4467-9a1c-5f581ce738c1 ro quiet splash vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/07/2019
  dmi.bios.vendor: AMI
  dmi.bios.version: F.24
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 83B9
  dmi.board.vendor: HP
  dmi.board.version: 56.43
  dmi.chassis.type: 31
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAMI:bvrF.24:bd01/07/2019:svnHP:pnHPSpectrex360Convertible13-ae0xx:pvr:rvnHP:rn83B9:rvr56.43:cvnHP:ct31:cvrChassisVersion:
  dmi.product.family: 103C_5335KV HP Spectre
  dmi.product.name: HP Spectre x360 Convertible 13-ae0xx
  dmi.product.sku: 1WU65AV
  dmi.sys.vendor: HP
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.99-1ubuntu1~18.04.2
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.8-0ubuntu0~18.04.3
  version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.8-0ubuntu0~18.04.3
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A

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


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

[Desktop-packages] [Bug 2016308] Re: gnome-shell crashed with signal 6: libmutter:ERROR:../src/core/window.c:1533:meta_window_unmanage: assertion failed: (window->display->focus_window != window)

[Diego A. Elizondo]

I am using NetBeans 12.5 another way to replicate this bug: add two
JFrame and configure a button in one of the JFrame with the following
code:

 new NewJFrame().setVisible(true);
 this.dispose();

Wayland session: the OS freezes and closes the session.
Xorg session : the OS freezes but it does not close the session and keeps the 
program open

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

Title:
  gnome-shell crashed with signal 6:
  libmutter:ERROR:../src/core/window.c:1533:meta_window_unmanage:
  assertion failed: (window->display->focus_window != window)

Status in Mutter:
  Fix Released
Status in mutter package in Ubuntu:
  Fix Committed

Bug description:
  Hello,

  This bug is triggered by Sweethome 3D but the underlying problem seems
  to be a libmutter issue.

  Setup:
  Ubuntu 23.04
  Ryzen 6000
  AMD 680
  Gnome 44
  Sweethome 3D 7.0.2 (from the repositories)

  Whenever I load a file in Sweethome 3D my desktop session is killed
  instantly. I am either thrown back to the desktop login or it stays
  black.

  This seems like a severe problem to me. Under no circumstances should
  an app like Sweethome 3D be able to crash mutter.

  I don't know how to give any logs. But I attach a sample file for
  Sweethome 3D. Actually it crashes with any file.

  Steps to reproduce:
  Start Sweethome 3D
  Draw some walls to make
  Draw a room
  Save to file
  Quit Sweethome 3D
  Start Sweethome 3D
  Load the file
  Crash

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


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

[Desktop-packages] [Bug 2017614] [NEW] Xwayland

[Diego A. Elizondo]

Public bug reported:

I am using the NetBeans 12.5 IDE (Java 11)  for study reasons, I am
having a bug with the OS I recently upgraded from Ubuntu 22.10 to Ubuntu
23.04, every time I run a project and for example: I have a button
configured to show and hide a form when i press the button the OS
freezes and logs me out, this never happened to me on ubuntu 22.10

ProblemType: Bug
DistroRelease: Ubuntu 23.04
Package: xorg 1:7.7+23ubuntu2
ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6
Uname: Linux 6.2.0-20-generic x86_64
ApportVersion: 2.26.1-0ubuntu2
Architecture: amd64
BootLog: Error: [Errno 13] Permiso denegado: '/var/log/boot.log'
CasperMD5CheckResult: pass
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Mon Apr 24 20:36:04 2023
DistUpgraded: Fresh install
DistroCodename: lunar
DistroVariant: ubuntu
DkmsStatus:
 v4l2loopback/0.12.7, 5.19.0-40-generic, x86_64: installed (WARNING! Diff 
between built and installed module!)
 v4l2loopback/0.12.7, 6.2.0-20-generic, x86_64: installed (WARNING! Diff 
between built and installed module!)
GraphicsCard:
 Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0102] (rev 09) (prog-if 00 [VGA controller])
   Subsystem: Hewlett-Packard Company 2nd Generation Core Processor Family 
Integrated Graphics Controller [103c:2ae2]
InstallationDate: Installed on 2021-07-08 (656 days ago)
InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
MachineType: Hewlett-Packard CQ2951LA
ProcEnviron:
 LANG=es_CR.UTF-8
 LANGUAGE=es_CR:es
 PATH=(custom, no user)
 SHELL=/bin/bash
 XDG_RUNTIME_DIR=
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-20-generic 
root=UUID=375418d9-5c30-48db-b088-b27ed63e58dd ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
Title: Xorg crash
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 08/31/2012
dmi.bios.release: 4.6
dmi.bios.vendor: AMI
dmi.bios.version: 8.08
dmi.board.asset.tag: 3CR2390SBN
dmi.board.name: 2AE2
dmi.board.vendor: PEGATRON CORPORATION
dmi.board.version: 1.02
dmi.chassis.asset.tag: 3CR2390SBN
dmi.chassis.type: 3
dmi.chassis.vendor: Hewlett-Packard
dmi.modalias: 
dmi:bvnAMI:bvr8.08:bd08/31/2012:br4.6:svnHewlett-Packard:pnCQ2951LA:pvr1.00:rvnPEGATRONCORPORATION:rn2AE2:rvr1.02:cvnHewlett-Packard:ct3:cvr:skuH3X53AA#ABM:
dmi.product.family: 103C_53316J G=D
dmi.product.name: CQ2951LA
dmi.product.sku: H3X53AA#ABM
dmi.product.version: 1.00
dmi.sys.vendor: Hewlett-Packard
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.114-1
version.libgl1-mesa-dri: libgl1-mesa-dri 23.0.2-1ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx 23.0.2-1ubuntu1
version.xserver-xorg-core: xserver-xorg-core 2:21.1.7-1ubuntu3
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1

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


** Tags: amd64 apport-bug crash lunar ubuntu wayland-session

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

Title:
  Xwayland

Status in xorg package in Ubuntu:
  New

Bug description:
  I am using the NetBeans 12.5 IDE (Java 11)  for study reasons, I am
  having a bug with the OS I recently upgraded from Ubuntu 22.10 to
  Ubuntu 23.04, every time I run a project and for example: I have a
  button configured to show and hide a form when i press the button the
  OS freezes and logs me out, this never happened to me on ubuntu 22.10

  ProblemType: Bug
  DistroRelease: Ubuntu 23.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6
  Uname: Linux 6.2.0-20-generic x86_64
  ApportVersion: 2.26.1-0ubuntu2
  Architecture: amd64
  BootLog: Error: [Errno 13] Permiso denegado: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Apr 24 20:36:04 2023
  DistUpgraded: Fresh install
  DistroCodename: lunar
  DistroVariant: ubuntu
  DkmsStatus:
   v4l2loopback/0.12.7, 5.19.0-40-generic, x86_64: installed (WARNING! Diff 
between built and installed module!)
   v4l2loopback/0.12.7, 6.2.0-20-generic, x86_64: installed (WARNING! Diff 
between built and installed module!)
  GraphicsCard:
   Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0102] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company 2nd Generation Core Processor Family 
Integrated Graphics Controller [103c:2ae2]
  InstallationDate: Installed on 2021-07-08 (656 days ago)
  InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
  MachineType: Hewlett-Packard CQ2951LA
  ProcEnviron:
   LANG=es_CR.UTF-8
   

[Desktop-packages] [Bug 1993878] Re: Dark mode from the drop down menu turning off on it's own

[Diego Zagalia Ferreira]

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

I was just sad because it's been a long time and it still hasn't been
resolved.

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

Title:
  Dark mode from the drop down menu turning off on it's own

Status in gnome-shell package in Ubuntu:
  Confirmed

Bug description:
  tldr; Dark mode from the drop down menu turning off on it's own,
  resulting in mismatched theme across the shell.

  Description:  Ubuntu 22.10
  Release:  22.10

  Gnome 43.

  Expected : Dark mode from the drop down menu matching the one from
  system settings.

  What happens : Dark mode from the drop down menu turning off on it's
  own.

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


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

[Desktop-packages] [Bug 1970148] Re: Brave & Chrome browsers freezes on download and print to pdf

[Diego Garcia]

I can confirm #37.

--
>From chrome://version:

Google Chrome 107.0.5304.121 (Official Build) (64-bit) 
Revision 
f069d69e0559af6ce6208316892bb2e0a9bd2d17-refs/branch-heads/5304_110@{#3}
OS Linux

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

Title:
  Brave & Chrome browsers freezes on download and print to pdf

Status in chromium-browser package in Ubuntu:
  Invalid

Bug description:
  Whenever any file is downloaded, the browser will freeze. Download
  files, from any page does not work. Same issue with Firefox.

  Similarly, the browser will freeze when a page is printed to pdf.

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


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

[Desktop-packages] [Bug 1970148] Re: Brave & Chrome browsers freezes on download and print to pdf

[Diego Garcia]

In the #25 I said the issue was solved after installing "xdg-desktop-
portal-gnome", but no (It was solved partially)

For me, this issue occurs only at the FIRST Chrome launch (after reboot). If I 
close the browser and reopen it, the issue disappears.
The issue also doesn't come back when I do Log Out, only on restart/shutdown.

Below, I test 2 probable fixes commented in this bug thread:

#28: "The problem seems to be related to Chrome apps (Google Chat for example)"
Me: I don't have any Chrome apps and the issue are happening

#29: "Disabling 'Use hardware acceleration when available' from chrome settings 
the problem stop happend."
Me: Nope. Again, still happening. I think reopening the browser falls into the 
behavior presented above.

--
>From chrome://version:

Google Chrome   105.0.5195.102 (Official Build) (64-bit) 
Revision
4c16f5ffcc2da70ee2600d5db77bed423ac03a5a-refs/branch-heads/5195_55@{#4}
OS  Linux

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

Title:
  Brave & Chrome browsers freezes on download and print to pdf

Status in chromium-browser package in Ubuntu:
  Invalid

Bug description:
  Whenever any file is downloaded, the browser will freeze. Download
  files, from any page does not work. Same issue with Firefox.

  Similarly, the browser will freeze when a page is printed to pdf.

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


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

[Desktop-packages] [Bug 1967843] Re: cheese display corrupted under Ubuntu 22.04

[Diego Viola]

Same problem here with a Logitech C505 on Ubuntu 22.04.

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

Title:
  cheese display corrupted under  Ubuntu 22.04

Status in Cheese:
  Unknown
Status in OEM Priority Project:
  Confirmed
Status in cheese package in Ubuntu:
  Invalid
Status in clutter-gst-3.0 package in Ubuntu:
  Fix Released
Status in clutter-gst-3.0 source package in Jammy:
  Fix Committed

Bug description:
  Impact
  ==
  The cheese app is unusable with color bands showing in the main view.

  This bug doesn't affect all webcams. It's unknown what percentage of
  webcams are affected.

  Test Case
  
  On a system that experiences this bug:
  Install the update
  Run the cheese app
  Verify that the main view shows what your webcam can see normally.
  Click the camera button in the bottom toolbar area.
  Check if the photo looks normal. You can find it in ~/Pictures/Webcam

  What Could Go Wrong
  ===
  Only 4 apps in Ubuntu use clutter-gst: empathy, cheese, lyricue, pinpoint

  clutter-gst has been archived by GNOME. (It's recommended for apps to
  use GTK4 instead of GTK3 + Clutter). That means it's not possible for
  this patch to be accepted upstream. Instead, distros like Arch Linux
  are applying this patch.

  This patch removes 2 renderers that don't work (RGBx and BGRx) but
  still keeps ones that do work: RGBA and BRGA.

  Original Bug Report
  ===
  The cheese application produces a corrupted display under Ubuntu 22.04 with a 
Logitech C525 webcam. When started from the command line, cheese produces 
repeated warnings of the form...

  (cheese:4175): cheese-WARNING **: 05:15:48.706: A lot of buffers are being 
dropped.: ../libs/gst/base/gstbasesink.c(3143): gst_base_sink_is_too_late (): 
/GstCameraBin:camerabin/GstViewfinderBin:vf-bin/ClutterGstVideoSink:cluttergstvideosink0:
  There may be a timestamping problem, or this computer is too slow.

  Adding /etc/modprobe.d/uvcvideo.conf

  with 'options uvcvideo nodrop=1' doesn't solve the problem. This issue
  is not seen in either Ubuntu 21.10 or under Fedora-Workstation-
  Live-x86_64-36_Beta-1.4. The problem in Ubuntu 22.04 occurs under both
  Wayland and X11 displays with the Nvidia drivers.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: cheese 41.1-1build1
  ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30
  Uname: Linux 5.15.0-25-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu80
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Apr  5 05:15:35 2022
  ExecutablePath: /usr/bin/cheese
  InstallationDate: Installed on 2022-03-31 (4 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220326)
  MachineType: Gigabyte Technology Co., Ltd. X570 UD
  ProcEnviron:
   SHELL=/bin/bash
   LANG=en_US.UTF-8
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
   PATH=(custom, no user)
  RelatedPackageVersions:
   cheese41.1-1build1
   cheese-common 41.1-1build1
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/18/2021
  dmi.bios.release: 5.17
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F32
  dmi.board.asset.tag: Default string
  dmi.board.name: X570 UD
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF32:bd01/18/2021:br5.17:svnGigabyteTechnologyCo.,Ltd.:pnX570UD:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnX570UD:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring:
  dmi.product.family: X570 MB
  dmi.product.name: X570 UD
  dmi.product.sku: Default string
  dmi.product.version: Default string
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  ---
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu80
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2022-03-31 (4 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220326)
  MachineType: Gigabyte Technology Co., Ltd. X570 UD
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: cheese 41.1-1build1
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30
  RelatedPackageVersions:
   cheese41.1-1build1
   cheese-common 41.1-1build1
  Tags: wayland-session third-party-packages jammy gstreamer-error
  Uname: Linux 5.15.0-25-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev 

[Desktop-packages] [Bug 1969254] Re: wayland session not longer an option after recent update on Ubuntu 22.04

[Diego Lineros]

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

Interestingly, the gear appears only after hibernation. I can choose
Wayland, but, once I log out everything is gone and I'm back to X11

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

Title:
  wayland session not longer an option after recent update on Ubuntu
  22.04

Status in gnome-session package in Ubuntu:
  Confirmed

Bug description:
  After some recent update to Ubuntu 22.04 dev, X11 is selected by
  default and there is no longer the option to select the display
  protocol at login.

  It seems I am not the only affected:
  https://askubuntu.com/questions/1402671/ubuntu-no-gear-for-
  waylaland-x11

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: ubuntu-session 42.0-1ubuntu2
  Uname: Linux 5.17.3-051703-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Apr 15 22:20:35 2022
  InstallationDate: Installed on 2022-02-02 (72 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  PackageArchitecture: all
  SourcePackage: gnome-session
  UpgradeStatus: Upgraded to jammy on 2022-03-18 (28 days ago)

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


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

[Desktop-packages] [Bug 1969853] Re: Bluetooth doesn't work but seems active

[Diego Aparecido de Souza Pereira]

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

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

Title:
  Bluetooth doesn't work but seems active

Status in bluez package in Ubuntu:
  New

Bug description:
  After updating to version 22.04, with kernel 5.15.0-25, Bluettoth
  stopped working via menu. Before I used versions 20.04 and 21.10, the
  latter with kernel 5.13, and Bluetooth was recognized normally. The
  bluetooth status in the terminal is this:

  diego@diego-Inspiron:~$ sudo systemctl status bluetooth.service
  ● bluetooth.service - Bluetooth service
   Loaded: loaded (/lib/systemd/system/bluetooth.service; enabled; vendor 
preset: enabled)
   Active: active (running) since Thu 2022-04-21 18:16:17 -03; 16min ago
 Docs: man:bluetoothd(8)
 Main PID: 1100 (bluetoothd)
   Status: "Running"
Tasks: 1 (limit: 18808)
   Memory: 1.8M
  CPU: 66ms
   CGroup: /system.slice/bluetooth.service
   └─1100 /usr/lib/bluetooth/bluetoothd

  abr 21 18:16:16 diego-Inspiron systemd[1]: Starting Bluetooth service...
  abr 21 18:16:17 diego-Inspiron bluetoothd[1100]: Bluetooth daemon 5.64
  abr 21 18:16:17 diego-Inspiron systemd[1]: Started Bluetooth service.
  abr 21 18:16:17 diego-Inspiron bluetoothd[1100]: Starting SDP server
  abr 21 18:16:17 diego-Inspiron bluetoothd[1100]: Bluetooth management 
interface 1.21 initialized

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


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

[Desktop-packages] [Bug 1950697] [NEW] gray desktop or login loop

[Diego Pedrosa]

Public bug reported:

I'm using Ubuntu 20.04 (all upgrades)

I was using MATE until I decided to go back to budgie since MATE started 
hogging system resources.
after removing MATE and trying to login with budgie I only get a gray screen.
I reinstalled lightdm, budgie desktop, nvidia drivers, etc.
the only desktop environment that I can use is GNOME(Metacity)

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: lightdm 1.30.0-0ubuntu4~20.04.1
ProcVersionSignature: Ubuntu 5.4.0-90.101-generic 5.4.148
Uname: Linux 5.4.0-90-generic x86_64
NonfreeKernelModules: wl nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu27.21
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: GNOME-Flashback:GNOME
Date: Thu Nov 11 15:45:05 2021
InstallationDate: Installed on 2017-08-04 (1560 days ago)
InstallationMedia: Ubuntu-Budgie 17.04 "Zesty Zapus" - Release amd64 (20170412)
LightdmConfig:
 [Seat:*]
 autologin-guest=false
 #autologin-user=diego
 #autologin-user-timeout=0
SourcePackage: lightdm
UpgradeStatus: No upgrade log present (probably fresh install)
modified.conffile..etc.default.apport:
 # set this to 0 to disable apport, or to 1 to enable it
 # you can temporarily override this with
 # sudo service apport start force_start=1
 enabled=0
mtime.conffile..etc.default.apport: 2019-10-31T12:18:08.840234

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


** Tags: amd64 apport-bug focal

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

Title:
  gray desktop or login loop

Status in lightdm package in Ubuntu:
  New

Bug description:
  I'm using Ubuntu 20.04 (all upgrades)

  I was using MATE until I decided to go back to budgie since MATE started 
hogging system resources.
  after removing MATE and trying to login with budgie I only get a gray screen.
  I reinstalled lightdm, budgie desktop, nvidia drivers, etc.
  the only desktop environment that I can use is GNOME(Metacity)

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: lightdm 1.30.0-0ubuntu4~20.04.1
  ProcVersionSignature: Ubuntu 5.4.0-90.101-generic 5.4.148
  Uname: Linux 5.4.0-90-generic x86_64
  NonfreeKernelModules: wl nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: GNOME-Flashback:GNOME
  Date: Thu Nov 11 15:45:05 2021
  InstallationDate: Installed on 2017-08-04 (1560 days ago)
  InstallationMedia: Ubuntu-Budgie 17.04 "Zesty Zapus" - Release amd64 
(20170412)
  LightdmConfig:
   [Seat:*]
   autologin-guest=false
   #autologin-user=diego
   #autologin-user-timeout=0
  SourcePackage: lightdm
  UpgradeStatus: No upgrade log present (probably fresh install)
  modified.conffile..etc.default.apport:
   # set this to 0 to disable apport, or to 1 to enable it
   # you can temporarily override this with
   # sudo service apport start force_start=1
   enabled=0
  mtime.conffile..etc.default.apport: 2019-10-31T12:18:08.840234

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


-- 
Mailing list: https://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 1942655] Re: problem after minimizing windows

[Diego Iboy]

Being all day trying to replicate the bug, with the extensions disabled,
the bug was not replicated at any time, using the PC in a normal way, as at
all times, I attach the extensions that I use, I do not deduce which can
cause the bug .

[image: image.png]

El lun, 6 sept 2021 a las 8:46, Diego Iboy ()
escribió:

> Hello good Morning
> I attach the resulting txt.
>
> I have disabled the extensions, but I have not been able to replicate the
> bug, I have to mention that it happens randomly throughout the day. With
> which I will continue using it in this way until the end of the day to see
> if it can be replicated.
>
> Greetings
>
> El dom, 5 sept 2021 a las 22:10, Daniel van Vugt (<
> 1942...@bugs.launchpad.net>) escribió:
>
>> Also please run:
>>
>>   lspci -kv > lspci.txt
>>
>> and attach the resulting text file here.
>>
>> --
>> You received this bug notification because you are subscribed to the bug
>> report.
>> https://bugs.launchpad.net/bugs/1942655
>>
>> Title:
>>   problem after minimizing windows
>>
>> Status in GNOME Shell:
>>   Unknown
>> Status in gnome-shell package in Ubuntu:
>>   Incomplete
>>
>> Bug description:
>>   Hello, the problem that I am presented with is basic, but quite
>> annoying.
>>   At any time without any type of pattern, when minimizing a window (of
>> any program), these remain as "background", and become part of the
>> wallpaper. You do not interact with it but it remains static on the site.
>>   I attach an example.
>>   The only temporary solution that has worked for me is to log out, but
>> it almost certainly happens again.
>>   I appreciate the help :)
>>   (The theme has nothing to do with it, it happens to me even though it
>> is stock)
>>
>>   ProblemType: Bug
>>   DistroRelease: Ubuntu 21.04
>>   Package: gnome-shell 3.38.4-1ubuntu3~21.04.1
>>   ProcVersionSignature: Ubuntu 5.11.0-31.33-generic 5.11.22
>>   Uname: Linux 5.11.0-31-generic x86_64
>>   ApportVersion: 2.20.11-0ubuntu65.1
>>   Architecture: amd64
>>   CasperMD5CheckResult: unknown
>>   CurrentDesktop: ubuntu:GNOME
>>   Date: Fri Sep  3 17:12:04 2021
>>   DisplayManager: gdm3
>>   InstallationDate: Installed on 2021-08-28 (6 days ago)
>>   InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64
>> (20210209.1)
>>   RelatedPackageVersions: mutter-common 3.38.4-1ubuntu2
>>   SourcePackage: gnome-shell
>>   UpgradeStatus: Upgraded to hirsute on 2021-08-31 (3 days ago)
>>
>> To manage notifications about this bug go to:
>> https://bugs.launchpad.net/gnome-shell/+bug/1942655/+subscriptions
>>
>>


** Attachment added: "image.png"
   https://bugs.launchpad.net/bugs/1942655/+attachment/5523354/+files/image.png

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

Title:
  Minimized windows stay ghosted on the background wallpaper

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

Bug description:
  Hello, the problem that I am presented with is basic, but quite annoying.
  At any time without any type of pattern, when minimizing a window (of any 
program), these remain as "background", and become part of the wallpaper. You 
do not interact with it but it remains static on the site.
  I attach an example.
  The only temporary solution that has worked for me is to log out, but it 
almost certainly happens again.
  I appreciate the help :)
  (The theme has nothing to do with it, it happens to me even though it is 
stock)

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: gnome-shell 3.38.4-1ubuntu3~21.04.1
  ProcVersionSignature: Ubuntu 5.11.0-31.33-generic 5.11.22
  Uname: Linux 5.11.0-31-generic x86_64
  ApportVersion: 2.20.11-0ubuntu65.1
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Sep  3 17:12:04 2021
  DisplayManager: gdm3
  InstallationDate: Installed on 2021-08-28 (6 days ago)
  InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  RelatedPackageVersions: mutter-common 3.38.4-1ubuntu2
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to hirsute on 2021-08-31 (3 days ago)

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


-- 
Mailing list: https://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 1942655] Re: problem after minimizing windows

[Diego Iboy]

Hello good Morning
I attach the resulting txt.

I have disabled the extensions, but I have not been able to replicate the
bug, I have to mention that it happens randomly throughout the day. With
which I will continue using it in this way until the end of the day to see
if it can be replicated.

Greetings

El dom, 5 sept 2021 a las 22:10, Daniel van Vugt (<
1942...@bugs.launchpad.net>) escribió:

> Also please run:
>
>   lspci -kv > lspci.txt
>
> and attach the resulting text file here.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1942655
>
> Title:
>   problem after minimizing windows
>
> Status in GNOME Shell:
>   Unknown
> Status in gnome-shell package in Ubuntu:
>   Incomplete
>
> Bug description:
>   Hello, the problem that I am presented with is basic, but quite annoying.
>   At any time without any type of pattern, when minimizing a window (of
> any program), these remain as "background", and become part of the
> wallpaper. You do not interact with it but it remains static on the site.
>   I attach an example.
>   The only temporary solution that has worked for me is to log out, but it
> almost certainly happens again.
>   I appreciate the help :)
>   (The theme has nothing to do with it, it happens to me even though it is
> stock)
>
>   ProblemType: Bug
>   DistroRelease: Ubuntu 21.04
>   Package: gnome-shell 3.38.4-1ubuntu3~21.04.1
>   ProcVersionSignature: Ubuntu 5.11.0-31.33-generic 5.11.22
>   Uname: Linux 5.11.0-31-generic x86_64
>   ApportVersion: 2.20.11-0ubuntu65.1
>   Architecture: amd64
>   CasperMD5CheckResult: unknown
>   CurrentDesktop: ubuntu:GNOME
>   Date: Fri Sep  3 17:12:04 2021
>   DisplayManager: gdm3
>   InstallationDate: Installed on 2021-08-28 (6 days ago)
>   InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64
> (20210209.1)
>   RelatedPackageVersions: mutter-common 3.38.4-1ubuntu2
>   SourcePackage: gnome-shell
>   UpgradeStatus: Upgraded to hirsute on 2021-08-31 (3 days ago)
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/gnome-shell/+bug/1942655/+subscriptions
>
>


** Attachment added: "lspci.txt"
   https://bugs.launchpad.net/bugs/1942655/+attachment/5523253/+files/lspci.txt

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

Title:
  problem after minimizing windows

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

Bug description:
  Hello, the problem that I am presented with is basic, but quite annoying.
  At any time without any type of pattern, when minimizing a window (of any 
program), these remain as "background", and become part of the wallpaper. You 
do not interact with it but it remains static on the site.
  I attach an example.
  The only temporary solution that has worked for me is to log out, but it 
almost certainly happens again.
  I appreciate the help :)
  (The theme has nothing to do with it, it happens to me even though it is 
stock)

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: gnome-shell 3.38.4-1ubuntu3~21.04.1
  ProcVersionSignature: Ubuntu 5.11.0-31.33-generic 5.11.22
  Uname: Linux 5.11.0-31-generic x86_64
  ApportVersion: 2.20.11-0ubuntu65.1
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Sep  3 17:12:04 2021
  DisplayManager: gdm3
  InstallationDate: Installed on 2021-08-28 (6 days ago)
  InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  RelatedPackageVersions: mutter-common 3.38.4-1ubuntu2
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to hirsute on 2021-08-31 (3 days ago)

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


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

[Desktop-packages] [Bug 1942655] [NEW] problem after minimizing windows

[Diego Iboy]

Public bug reported:

Hello, the problem that I am presented with is basic, but quite annoying.
At any time without any type of pattern, when minimizing a window (of any 
program), these remain as "background", and become part of the wallpaper. You 
do not interact with it but it remains static on the site.
I attach an example.
The only temporary solution that has worked for me is to log out, but it almost 
certainly happens again.
I appreciate the help :)
(The theme has nothing to do with it, it happens to me even though it is stock)

ProblemType: Bug
DistroRelease: Ubuntu 21.04
Package: gnome-shell 3.38.4-1ubuntu3~21.04.1
ProcVersionSignature: Ubuntu 5.11.0-31.33-generic 5.11.22
Uname: Linux 5.11.0-31-generic x86_64
ApportVersion: 2.20.11-0ubuntu65.1
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Fri Sep  3 17:12:04 2021
DisplayManager: gdm3
InstallationDate: Installed on 2021-08-28 (6 days ago)
InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
RelatedPackageVersions: mutter-common 3.38.4-1ubuntu2
SourcePackage: gnome-shell
UpgradeStatus: Upgraded to hirsute on 2021-08-31 (3 days ago)

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


** Tags: amd64 apport-bug hirsute

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

Title:
  problem after minimizing windows

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  Hello, the problem that I am presented with is basic, but quite annoying.
  At any time without any type of pattern, when minimizing a window (of any 
program), these remain as "background", and become part of the wallpaper. You 
do not interact with it but it remains static on the site.
  I attach an example.
  The only temporary solution that has worked for me is to log out, but it 
almost certainly happens again.
  I appreciate the help :)
  (The theme has nothing to do with it, it happens to me even though it is 
stock)

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: gnome-shell 3.38.4-1ubuntu3~21.04.1
  ProcVersionSignature: Ubuntu 5.11.0-31.33-generic 5.11.22
  Uname: Linux 5.11.0-31-generic x86_64
  ApportVersion: 2.20.11-0ubuntu65.1
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Sep  3 17:12:04 2021
  DisplayManager: gdm3
  InstallationDate: Installed on 2021-08-28 (6 days ago)
  InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  RelatedPackageVersions: mutter-common 3.38.4-1ubuntu2
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to hirsute on 2021-08-31 (3 days ago)

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


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

[Desktop-packages] [Bug 1926110] Re: Apps interface flickering

[Diego Garcia]

Update: no flickering in this time period.

Downgrading to an older kernel version (5.0.0-05-generic) solved the 
problem.
Aparently the kernel version 5.8.0-50-generic has some problem between Intel 
Graphics and Xorg.

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

Title:
  Apps interface flickering

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  It has been 1-ish months since this problem appeared.
  The app/system interface randomly starts flickering. This problem doesn't 
occur on the entire system, sometime it occurs in some apps, other times in the 
system, and other times all of these.
  It occurs since installation.

  Some images and videos (Unfortunetly you'll need to download the videos)
  
https://media.discordapp.net/attachments/748527796405403749/836001618255806484/unknown.png
  
https://media.discordapp.net/attachments/748527796405403749/836004993991311400/unknown.png
  
https://media.discordapp.net/attachments/586951783944028179/832728657075372102/unknown.png
  
https://cdn.discordapp.com/attachments/804416273701797909/832780706790375444/20210416_215049_576x324.mp4
  
https://cdn.discordapp.com/attachments/748527796405403749/836048880592355368/simplescreenrecorder-2021-04-25_22.05.52.mp4

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.8.0-50.56~20.04.1-generic 5.8.18
  Uname: Linux 5.8.0-50-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  BootLog: Error: [Errno 13] Permissão negada: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Apr 25 22:23:48 2021
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  DkmsStatus: v4l2loopback, 0.12.3, 5.8.0-50-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: Holco Enterprise Co, Ltd/Shuttle Computer 3rd Gen Core 
processor Graphics Controller [1297:2027]
  InstallationDate: Installed on 2021-04-17 (9 days ago)
  InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  MachineType: Positivo Informatica SA DC8CR01TV
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-50-generic 
root=UUID=e2946f04-ffa3-4934-b119-e6dcc363a2da ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/31/2014
  dmi.bios.release: 4.6
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2.01.U
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: DC8CR01TV
  dmi.board.vendor: Positivo Informatica SA
  dmi.board.version: POSITIVO
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 13
  dmi.chassis.vendor: Positivo Informatica SA
  dmi.chassis.version: POSITIVO
  dmi.ec.firmware.release: 1.22
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2.01.U:bd03/31/2014:br4.6:efr1.22:svnPositivoInformaticaSA:pnDC8CR01TV:pvr2.01.U_POS_TV:rvnPositivoInformaticaSA:rnDC8CR01TV:rvrPOSITIVO:cvnPositivoInformaticaSA:ct13:cvrPOSITIVO:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: DC8CR01TV
  dmi.product.sku: 1700644
  dmi.product.version: 2.01.U_POS_TV
  dmi.sys.vendor: Positivo Informatica SA
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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

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

[Desktop-packages] [Bug 1926110] Re: Apps interface flickering

[Diego Garcia]

Update: so far, the system has not shown any irregularities. I'll wait
for 3 days because this problem does not have a pattern. It seems to
happen when the system is under high load, but I'm not sure.

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

Title:
  Apps interface flickering

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  It has been 1-ish months since this problem appeared.
  The app/system interface randomly starts flickering. This problem doesn't 
occur on the entire system, sometime it occurs in some apps, other times in the 
system, and other times all of these.
  It occurs since installation.

  Some images and videos (Unfortunetly you'll need to download the videos)
  
https://media.discordapp.net/attachments/748527796405403749/836001618255806484/unknown.png
  
https://media.discordapp.net/attachments/748527796405403749/836004993991311400/unknown.png
  
https://media.discordapp.net/attachments/586951783944028179/832728657075372102/unknown.png
  
https://cdn.discordapp.com/attachments/804416273701797909/832780706790375444/20210416_215049_576x324.mp4
  
https://cdn.discordapp.com/attachments/748527796405403749/836048880592355368/simplescreenrecorder-2021-04-25_22.05.52.mp4

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.8.0-50.56~20.04.1-generic 5.8.18
  Uname: Linux 5.8.0-50-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  BootLog: Error: [Errno 13] Permissão negada: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Apr 25 22:23:48 2021
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  DkmsStatus: v4l2loopback, 0.12.3, 5.8.0-50-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: Holco Enterprise Co, Ltd/Shuttle Computer 3rd Gen Core 
processor Graphics Controller [1297:2027]
  InstallationDate: Installed on 2021-04-17 (9 days ago)
  InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  MachineType: Positivo Informatica SA DC8CR01TV
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-50-generic 
root=UUID=e2946f04-ffa3-4934-b119-e6dcc363a2da ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/31/2014
  dmi.bios.release: 4.6
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2.01.U
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: DC8CR01TV
  dmi.board.vendor: Positivo Informatica SA
  dmi.board.version: POSITIVO
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 13
  dmi.chassis.vendor: Positivo Informatica SA
  dmi.chassis.version: POSITIVO
  dmi.ec.firmware.release: 1.22
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2.01.U:bd03/31/2014:br4.6:efr1.22:svnPositivoInformaticaSA:pnDC8CR01TV:pvr2.01.U_POS_TV:rvnPositivoInformaticaSA:rnDC8CR01TV:rvrPOSITIVO:cvnPositivoInformaticaSA:ct13:cvrPOSITIVO:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: DC8CR01TV
  dmi.product.sku: 1700644
  dmi.product.version: 2.01.U_POS_TV
  dmi.sys.vendor: Positivo Informatica SA
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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

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

[Desktop-packages] [Bug 1926110] Re: Apps interface flickering

[Diego Garcia]

I run Ubuntu 20.04.2 LTS GNOME (Xorg)
Processor Intel Core i3-3110M (HD Graphics 4000)
I'll install an older kernel version (5.0) and test it in the next day at 1PM 
(my actual version is 5.8.0-50-generic)
I have already formated my linux, so I don't have the dpkg.log

Here is my lspci:

00:02.0 VGA compatible controller: Intel Corporation 3rd Gen Core processor 
Graphics Controller (rev 09) (prog-if 00 [VGA controller])
DeviceName:  Onboard IGD
Subsystem: Holco Enterprise Co, Ltd/Shuttle Computer 3rd Gen Core 
processor Graphics Controller
Flags: bus master, fast devsel, latency 0, IRQ 33
Memory at f340 (64-bit, non-prefetchable) [size=4M]
Memory at d000 (64-bit, prefetchable) [size=256M]
I/O ports at f000 [size=64]
Expansion ROM at 000c [virtual] [disabled] [size=128K]
Capabilities: [90] MSI: Enable+ Count=1/1 Maskable- 64bit-
Capabilities: [d0] Power Management version 2
Capabilities: [a4] PCI Advanced Features
Kernel driver in use: i915
Kernel modules: i915


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

Title:
  Apps interface flickering

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  It has been 1-ish months since this problem appeared.
  The app/system interface randomly starts flickering. This problem doesn't 
occur on the entire system, sometime it occurs in some apps, other times in the 
system, and other times all of these.
  It occurs since installation.

  Some images and videos (Unfortunetly you'll need to download the videos)
  
https://media.discordapp.net/attachments/748527796405403749/836001618255806484/unknown.png
  
https://media.discordapp.net/attachments/748527796405403749/836004993991311400/unknown.png
  
https://media.discordapp.net/attachments/586951783944028179/832728657075372102/unknown.png
  
https://cdn.discordapp.com/attachments/804416273701797909/832780706790375444/20210416_215049_576x324.mp4
  
https://cdn.discordapp.com/attachments/748527796405403749/836048880592355368/simplescreenrecorder-2021-04-25_22.05.52.mp4

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.8.0-50.56~20.04.1-generic 5.8.18
  Uname: Linux 5.8.0-50-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  BootLog: Error: [Errno 13] Permissão negada: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Apr 25 22:23:48 2021
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  DkmsStatus: v4l2loopback, 0.12.3, 5.8.0-50-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: Holco Enterprise Co, Ltd/Shuttle Computer 3rd Gen Core 
processor Graphics Controller [1297:2027]
  InstallationDate: Installed on 2021-04-17 (9 days ago)
  InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  MachineType: Positivo Informatica SA DC8CR01TV
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-50-generic 
root=UUID=e2946f04-ffa3-4934-b119-e6dcc363a2da ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/31/2014
  dmi.bios.release: 4.6
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2.01.U
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: DC8CR01TV
  dmi.board.vendor: Positivo Informatica SA
  dmi.board.version: POSITIVO
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 13
  dmi.chassis.vendor: Positivo Informatica SA
  dmi.chassis.version: POSITIVO
  dmi.ec.firmware.release: 1.22
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2.01.U:bd03/31/2014:br4.6:efr1.22:svnPositivoInformaticaSA:pnDC8CR01TV:pvr2.01.U_POS_TV:rvnPositivoInformaticaSA:rnDC8CR01TV:rvrPOSITIVO:cvnPositivoInformaticaSA:ct13:cvrPOSITIVO:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: DC8CR01TV
  dmi.product.sku: 1700644
  dmi.product.version: 2.01.U_POS_TV
  dmi.sys.vendor: Positivo Informatica SA
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  

[Desktop-packages] [Bug 1926110] [NEW] Apps interface flickering

[Diego Garcia]

Public bug reported:

It has been 1-ish months since this problem appeared.
The app/system interface randomly starts flickering. This problem doesn't occur 
on the entire system, sometime it occurs in some apps, other times in the 
system, and other times all of these.
It occurs since installation.

Some images and videos (Unfortunetly you'll need to download the videos)
https://media.discordapp.net/attachments/748527796405403749/836001618255806484/unknown.png
https://media.discordapp.net/attachments/748527796405403749/836004993991311400/unknown.png
https://media.discordapp.net/attachments/586951783944028179/832728657075372102/unknown.png
https://cdn.discordapp.com/attachments/804416273701797909/832780706790375444/20210416_215049_576x324.mp4
https://cdn.discordapp.com/attachments/748527796405403749/836048880592355368/simplescreenrecorder-2021-04-25_22.05.52.mp4

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: xorg 1:7.7+19ubuntu14
ProcVersionSignature: Ubuntu 5.8.0-50.56~20.04.1-generic 5.8.18
Uname: Linux 5.8.0-50-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.16
Architecture: amd64
BootLog: Error: [Errno 13] Permissão negada: '/var/log/boot.log'
CasperMD5CheckResult: skip
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Sun Apr 25 22:23:48 2021
DistUpgraded: Fresh install
DistroCodename: focal
DistroVariant: ubuntu
DkmsStatus: v4l2loopback, 0.12.3, 5.8.0-50-generic, x86_64: installed
ExtraDebuggingInterest: Yes, including running git bisection searches
GraphicsCard:
 Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 
09) (prog-if 00 [VGA controller])
   Subsystem: Holco Enterprise Co, Ltd/Shuttle Computer 3rd Gen Core processor 
Graphics Controller [1297:2027]
InstallationDate: Installed on 2021-04-17 (9 days ago)
InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
MachineType: Positivo Informatica SA DC8CR01TV
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-50-generic 
root=UUID=e2946f04-ffa3-4934-b119-e6dcc363a2da ro quiet splash vt.handoff=7
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 03/31/2014
dmi.bios.release: 4.6
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 2.01.U
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: DC8CR01TV
dmi.board.vendor: Positivo Informatica SA
dmi.board.version: POSITIVO
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 13
dmi.chassis.vendor: Positivo Informatica SA
dmi.chassis.version: POSITIVO
dmi.ec.firmware.release: 1.22
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2.01.U:bd03/31/2014:br4.6:efr1.22:svnPositivoInformaticaSA:pnDC8CR01TV:pvr2.01.U_POS_TV:rvnPositivoInformaticaSA:rnDC8CR01TV:rvrPOSITIVO:cvnPositivoInformaticaSA:ct13:cvrPOSITIVO:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: DC8CR01TV
dmi.product.sku: 1700644
dmi.product.version: 2.01.U_POS_TV
dmi.sys.vendor: Positivo Informatica SA
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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


** Tags: amd64 apport-bug focal ubuntu

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

Title:
  Apps interface flickering

Status in xorg package in Ubuntu:
  New

Bug description:
  It has been 1-ish months since this problem appeared.
  The app/system interface randomly starts flickering. This problem doesn't 
occur on the entire system, sometime it occurs in some apps, other times in the 
system, and other times all of these.
  It occurs since installation.

  Some images and videos (Unfortunetly you'll need to download the videos)
  
https://media.discordapp.net/attachments/748527796405403749/836001618255806484/unknown.png
  
https://media.discordapp.net/attachments/748527796405403749/836004993991311400/unknown.png
  
https://media.discordapp.net/attachments/586951783944028179/832728657075372102/unknown.png
  
https://cdn.discordapp.com/attachments/804416273701797909/832780706790375444/20210416_215049_576x324.mp4
  
https://cdn.discordapp.com/attachments/748527796405403749/836048880592355368/simplescreenrecorder-2021-04-25_22.05.52.mp4

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.8.0-50.56~20.04.1-generic 5.8.18
  Uname: Linux 5.8.0-50-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.16
  

[Desktop-packages] [Bug 1916255] Re: Caps Lock initially not detected in GNOME password dialogs if you logged in with it on

[Diego Arias]

I should clarify that this bug occurs only when the xwayland session is
used, in the x11 (xorg) session the caps lock works correctly

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

Title:
  Caps Lock initially not detected in GNOME password dialogs if you
  logged in with it on

Status in gnome-shell package in Ubuntu:
  Triaged

Bug description:
  Caps lock is not properly detected, for example if you log in with a
  password that is in upper case, when entering the desktop without
  deactivating caps lock, when trying to open an encrypted drive whose
  password is in upper case even though the indicator shows that Caps
  lock is active and detects it as if it were not.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: xwayland 2:1.20.9-2ubuntu1.1
  ProcVersionSignature: Ubuntu 5.8.0-43.49-generic 5.8.18
  Uname: Linux 5.8.0-43-generic x86_64
  ApportVersion: 2.20.11-0ubuntu50.5
  Architecture: amd64
  BootLog: Error: [Errno 13] Permiso denegado: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Feb 19 09:03:42 2021
  DistUpgraded: 2020-10-24 20:57:52,724 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (g-exec-error-quark: Falló al ejecutar el proceso 
hijo «./xorg_fix_proprietary.py» (No existe el archivo o el directorio) (8))
  DistroCodename: groovy
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0102] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company 2nd Generation Core Processor Family 
Integrated Graphics Controller [103c:2ae2]
  InstallationDate: Installed on 2020-04-09 (316 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402)
  MachineType: Hewlett-Packard CQ2951LA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-43-generic 
root=UUID=f43448ef-2a06-45ab-8bac-fe9e8907ff57 ro quiet splash vt.handoff=7
  SourcePackage: xorg-server
  UpgradeStatus: Upgraded to groovy on 2020-10-25 (117 days ago)
  dmi.bios.date: 08/31/2012
  dmi.bios.release: 4.6
  dmi.bios.vendor: AMI
  dmi.bios.version: 8.08
  dmi.board.asset.tag: 3CR2390SBN
  dmi.board.name: 2AE2
  dmi.board.vendor: PEGATRON CORPORATION
  dmi.board.version: 1.02
  dmi.chassis.asset.tag: 3CR2390SBN
  dmi.chassis.type: 3
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnAMI:bvr8.08:bd08/31/2012:br4.6:svnHewlett-Packard:pnCQ2951LA:pvr1.00:rvnPEGATRONCORPORATION:rn2AE2:rvr1.02:cvnHewlett-Packard:ct3:cvr:
  dmi.product.family: 103C_53316J G=D
  dmi.product.name: CQ2951LA
  dmi.product.sku: H3X53AA#ABM
  dmi.product.version: 1.00
  dmi.sys.vendor: Hewlett-Packard
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.102-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.10.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 20.2.6-0ubuntu0.20.10.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200714-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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

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

[Desktop-packages] [Bug 1916255] [NEW] Caps Lock not detected properly

[Diego Arias]

Public bug reported:

Caps lock is not properly detected, for example if you log in with a
password that is in upper case, when entering the desktop without
deactivating caps lock, when trying to open an encrypted drive whose
password is in upper case even though the indicator shows that Caps lock
is active and detects it as if it were not.

ProblemType: Bug
DistroRelease: Ubuntu 20.10
Package: xwayland 2:1.20.9-2ubuntu1.1
ProcVersionSignature: Ubuntu 5.8.0-43.49-generic 5.8.18
Uname: Linux 5.8.0-43-generic x86_64
ApportVersion: 2.20.11-0ubuntu50.5
Architecture: amd64
BootLog: Error: [Errno 13] Permiso denegado: '/var/log/boot.log'
CasperMD5CheckResult: skip
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Fri Feb 19 09:03:42 2021
DistUpgraded: 2020-10-24 20:57:52,724 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (g-exec-error-quark: Falló al ejecutar el proceso 
hijo «./xorg_fix_proprietary.py» (No existe el archivo o el directorio) (8))
DistroCodename: groovy
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0102] (rev 09) (prog-if 00 [VGA controller])
   Subsystem: Hewlett-Packard Company 2nd Generation Core Processor Family 
Integrated Graphics Controller [103c:2ae2]
InstallationDate: Installed on 2020-04-09 (316 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402)
MachineType: Hewlett-Packard CQ2951LA
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-43-generic 
root=UUID=f43448ef-2a06-45ab-8bac-fe9e8907ff57 ro quiet splash vt.handoff=7
SourcePackage: xorg-server
UpgradeStatus: Upgraded to groovy on 2020-10-25 (117 days ago)
dmi.bios.date: 08/31/2012
dmi.bios.release: 4.6
dmi.bios.vendor: AMI
dmi.bios.version: 8.08
dmi.board.asset.tag: 3CR2390SBN
dmi.board.name: 2AE2
dmi.board.vendor: PEGATRON CORPORATION
dmi.board.version: 1.02
dmi.chassis.asset.tag: 3CR2390SBN
dmi.chassis.type: 3
dmi.chassis.vendor: Hewlett-Packard
dmi.modalias: 
dmi:bvnAMI:bvr8.08:bd08/31/2012:br4.6:svnHewlett-Packard:pnCQ2951LA:pvr1.00:rvnPEGATRONCORPORATION:rn2AE2:rvr1.02:cvnHewlett-Packard:ct3:cvr:
dmi.product.family: 103C_53316J G=D
dmi.product.name: CQ2951LA
dmi.product.sku: H3X53AA#ABM
dmi.product.version: 1.00
dmi.sys.vendor: Hewlett-Packard
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.102-1ubuntu1
version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.10.1
version.libgl1-mesa-glx: libgl1-mesa-glx 20.2.6-0ubuntu0.20.10.1
version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.1
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1ubuntu1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200714-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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


** Tags: amd64 apport-bug groovy ubuntu wayland-session

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

Title:
  Caps Lock not detected properly

Status in xorg-server package in Ubuntu:
  New

Bug description:
  Caps lock is not properly detected, for example if you log in with a
  password that is in upper case, when entering the desktop without
  deactivating caps lock, when trying to open an encrypted drive whose
  password is in upper case even though the indicator shows that Caps
  lock is active and detects it as if it were not.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: xwayland 2:1.20.9-2ubuntu1.1
  ProcVersionSignature: Ubuntu 5.8.0-43.49-generic 5.8.18
  Uname: Linux 5.8.0-43-generic x86_64
  ApportVersion: 2.20.11-0ubuntu50.5
  Architecture: amd64
  BootLog: Error: [Errno 13] Permiso denegado: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Feb 19 09:03:42 2021
  DistUpgraded: 2020-10-24 20:57:52,724 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (g-exec-error-quark: Falló al ejecutar el proceso 
hijo «./xorg_fix_proprietary.py» (No existe el archivo o el directorio) (8))
  DistroCodename: groovy
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0102] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company 2nd Generation Core Processor Family 
Integrated Graphics Controller [103c:2ae2]
  InstallationDate: Installed on 2020-04-09 (316 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402)
  MachineType: Hewlett-Packard CQ2951LA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-43-generic 
root=UUID=f43448ef-2a06-45ab-8bac-fe9e8907ff57 ro 

[Desktop-packages] [Bug 1913934] Re: Wrong current option in Screen resolution window

[Diego Betto]

Thank you

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

Title:
  Wrong current option in Screen resolution window

Status in gnome-control-center:
  Unknown
Status in gnome-control-center package in Ubuntu:
  Invalid
Status in libhandy-1 package in Ubuntu:
  Fix Committed

Bug description:
  The checkmark is on the wrong option. Current resolution is 1920x1080,
  not 1600x1200

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: gnome-control-center 1:3.38.1-1ubuntu1
  ProcVersionSignature: Ubuntu 5.8.0-41.46-generic 5.8.18
  Uname: Linux 5.8.0-41-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu50.3
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Jan 31 10:41:49 2021
  ExecutablePath: /usr/bin/gnome-control-center
  ProcEnviron:
   PATH=(custom, user)
   XDG_RUNTIME_DIR=
   LANG=it_IT.UTF-8
   SHELL=/usr/bin/zsh
  SourcePackage: gnome-control-center
  UpgradeStatus: Upgraded to groovy on 2020-10-29 (93 days ago)

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

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

[Desktop-packages] [Bug 1913934] Re: Wrong current option in Screen resolution window

[Diego Betto]

** Attachment added: "ubuntu_bug_report_2021-01-31_10-44.png"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1913934/+attachment/5458488/+files/ubuntu_bug_report_2021-01-31_10-44.png

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

Title:
  Wrong current option in Screen resolution window

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

Bug description:
  The checkmark is on the wrong option. Current resolution is 1920x1080,
  not 1600x1200

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: gnome-control-center 1:3.38.1-1ubuntu1
  ProcVersionSignature: Ubuntu 5.8.0-41.46-generic 5.8.18
  Uname: Linux 5.8.0-41-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu50.3
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Jan 31 10:41:49 2021
  ExecutablePath: /usr/bin/gnome-control-center
  ProcEnviron:
   PATH=(custom, user)
   XDG_RUNTIME_DIR=
   LANG=it_IT.UTF-8
   SHELL=/usr/bin/zsh
  SourcePackage: gnome-control-center
  UpgradeStatus: Upgraded to groovy on 2020-10-29 (93 days ago)

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

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

[Desktop-packages] [Bug 1913934] [NEW] Wrong current option in Screen resolution window

[Diego Betto]

Public bug reported:

The checkmark is on the wrong option. Current resolution is 1920x1080,
not 1600x1200

ProblemType: Bug
DistroRelease: Ubuntu 20.10
Package: gnome-control-center 1:3.38.1-1ubuntu1
ProcVersionSignature: Ubuntu 5.8.0-41.46-generic 5.8.18
Uname: Linux 5.8.0-41-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu50.3
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Sun Jan 31 10:41:49 2021
ExecutablePath: /usr/bin/gnome-control-center
ProcEnviron:
 PATH=(custom, user)
 XDG_RUNTIME_DIR=
 LANG=it_IT.UTF-8
 SHELL=/usr/bin/zsh
SourcePackage: gnome-control-center
UpgradeStatus: Upgraded to groovy on 2020-10-29 (93 days ago)

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


** Tags: amd64 apport-bug groovy

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

Title:
  Wrong current option in Screen resolution window

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

Bug description:
  The checkmark is on the wrong option. Current resolution is 1920x1080,
  not 1600x1200

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: gnome-control-center 1:3.38.1-1ubuntu1
  ProcVersionSignature: Ubuntu 5.8.0-41.46-generic 5.8.18
  Uname: Linux 5.8.0-41-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu50.3
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Jan 31 10:41:49 2021
  ExecutablePath: /usr/bin/gnome-control-center
  ProcEnviron:
   PATH=(custom, user)
   XDG_RUNTIME_DIR=
   LANG=it_IT.UTF-8
   SHELL=/usr/bin/zsh
  SourcePackage: gnome-control-center
  UpgradeStatus: Upgraded to groovy on 2020-10-29 (93 days ago)

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

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

[Desktop-packages] [Bug 1832988] Re: Intel 8260 Bluetooth not working

[Diego Lineros]

Hi I am getting  Failed to send firmware data (-38), even after cool boot
diego@lfb-Desktop:~$ dmesg | grep -i bluetooth
[5.985839] Bluetooth: Core ver 2.22
[5.985858] Bluetooth: HCI device and connection manager initialized
[5.985864] Bluetooth: HCI socket layer initialized
[5.985867] Bluetooth: L2CAP socket layer initialized
[5.985872] Bluetooth: SCO socket layer initialized
[6.132508] Bluetooth: hci0: Bootloader revision 0.0 build 2 week 52 2014
[6.138629] Bluetooth: hci0: Device revision is 5
[6.138631] Bluetooth: hci0: Secure boot is enabled
[6.138631] Bluetooth: hci0: OTP lock is enabled
[6.138632] Bluetooth: hci0: API lock is enabled
[6.138632] Bluetooth: hci0: Debug lock is disabled
[6.138633] Bluetooth: hci0: Minimum firmware build 1 week 10 2014
[6.183029] Bluetooth: hci0: Found device firmware: intel/ibt-11-5.sfi
[6.206658] Bluetooth: hci0: Failed to send firmware data (-38)
[6.206731] Bluetooth: hci0: Intel reset sent to retry FW download
[8.736500] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[8.736503] Bluetooth: BNEP filters: protocol multicast
[8.736512] Bluetooth: BNEP socket layer initialized
diego@lfb-Desktop:~$ dpkg --status bluez | grep '^Version:'
Version: 5.53-0ubuntu3
diego@lfb-Desktop:~$ lspci -knn | grep Net -A3;lsusb
02:00.0 Network controller [0280]: Intel Corporation Wireless 8260 [8086:24f3] 
(rev 3a)
Subsystem: Intel Corporation Dual Band Wireless-AC 8260 [8086:1010]
Kernel driver in use: iwlwifi
Kernel modules: iwlwifi
Bus 008 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 003 Device 002: ID 090c:1000 Silicon Motion, Inc. - Taiwan (formerly Feiya 
Technology Corp.) Flash Drive
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 010 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 009 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 007 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 006 Device 002: ID 8087:0a2b Intel Corp. 
Bus 006 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 001 Device 006: ID 05e3:0608 Genesys Logic, Inc. Hub
Bus 001 Device 003: ID 03f0:7d11 HP, Inc Photosmart Premium C309g-m
Bus 001 Device 002: ID 045e:0761 Microsoft Corp. LifeCam VX-2000
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 005 Device 003: ID 046d:c52b Logitech, Inc. Unifying Receiver
Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 004 Device 003: ID 1ea7:0064 SHARKOON Technologies GmbH 2.4G Mouse
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 014 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 013 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 012 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 011 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

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

Title:
  Intel 8260 Bluetooth not working

Status in gnome-bluetooth package in Ubuntu:
  Invalid
Status in gnome-shell package in Ubuntu:
  Invalid
Status in linux package in Ubuntu:
  Fix Released

Bug description:
  Expected behaviour:
  I can enable bluetooth in the system settings, and pair with my other devices.

  Actual behaviour:
  Always displays as 'off' in the settings dialog, and won't turn on. 

  Bluetooth worked on the same machine with previous Ubuntu releases
  (18.10) & no hardware changes.

  "dmesg | grep -i bluetooth" reports the following:
  ```
  [   14.445902] Bluetooth: Core ver 2.22
  [   14.445918] Bluetooth: HCI device and connection manager initialized
  [   14.445921] Bluetooth: HCI socket layer initialized
  [   14.445923] Bluetooth: L2CAP socket layer initialized
  [   14.445929] Bluetooth: SCO socket layer initialized
  [   14.494345] Bluetooth: hci0: Bootloader revision 0.0 build 2 week 52 2014
  [   14.499050] Bluetooth: hci0: Device revision is 5
  [   14.499052] Bluetooth: hci0: Secure boot is enabled
  [   14.499053] Bluetooth: hci0: OTP lock is enabled
  [   14.499053] Bluetooth: hci0: API lock is enabled
  [   14.499054] Bluetooth: hci0: Debug lock is disabled
  [   14.499055] Bluetooth: hci0: Minimum firmware build 1 week 10 2014
  [   14.503899] Bluetooth: hci0: Found device firmware: intel/ibt-11-5.sfi
  [   14.558347] Bluetooth: hci0: Failed to send firmware data (-38)
  [   15.497805] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
  [   15.497806] Bluetooth: BNEP filters: protocol multicast
  [   15.497810] Bluetooth: BNEP socket layer initialized
  ```

  "lsb_release -rd" reports the following:
  ```
  Description:  Ubuntu 19.04
  Release:  19.04
  ```
  "cat /proc/version_signature" reports the following:
  ```
  Ubuntu 5.0.0-16.17-generic 5.0.8
  ```

  "a

[Desktop-packages] [Bug 1870736] Re: [nvidia] Screen scaling 125% gives 200%

[Diego Lineros]

So... Is that it?

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

Title:
  [nvidia] Screen scaling 125% gives 200%

Status in gnome-control-center package in Ubuntu:
  Confirmed
Status in mutter package in Ubuntu:
  Confirmed

Bug description:
  Procedure used:
  1.
  Fully updated system via apt update && apt upgrade

  2.
  Select the screen setup in gnome control center

  3. 
  Click the "Fractional scaling" toggle

  4. 
  Select 125% and click the green "use" button top right (it says "Anvend" in 
dansih)

  5.
  Observe that the window has grown a lot, click the "use new settings" button

  6.
  The window tells me, I am at 200% scaling. The "200%" option is now 
highlighted.

  7.
  Switch back to 100% and file this bug.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: ubuntu-release-upgrader-core 1:20.04.16
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu22
  Architecture: amd64
  CrashDB: ubuntu
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Apr  4 09:42:34 2020
  InstallationDate: Installed on 2018-01-14 (810 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=da_DK.UTF-8
   SHELL=/bin/bash
  SourcePackage: ubuntu-release-upgrader
  Symptom: release-upgrade
  UpgradeStatus: Upgraded to focal on 2020-04-03 (0 days ago)

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

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

[Desktop-packages] [Bug 1765795] Re: gsd-wacom crashed with SIGSEGV in g_type_check_value()

[Juan Diego Pérez Bohórquez]

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

Is there already a solution to this problem?

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

Title:
  gsd-wacom crashed with SIGSEGV in g_type_check_value()

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

Bug description:
  ...

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: gnome-settings-daemon 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
  CrashCounter: 1
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Apr 20 19:11:23 2018
  ExecutablePath: /usr/lib/gnome-settings-daemon/gsd-wacom
  InstallationDate: Installed on 2018-04-07 (13 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180329)
  ProcCmdline: /usr/lib/gnome-settings-daemon/gsd-wacom
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  SegvAnalysis:
   Segfault happened at: 0x7f81f2050454 :   testb  
$0x4,0x16(%rbx)
   PC (0x7f81f2050454) ok
   source "$0x4" ok
   destination "0x16(%rbx)" (0x0016) not located in a known VMA region 
(needed writable region)!
  SegvReason: writing NULL VMA
  Signal: 11
  SourcePackage: gnome-settings-daemon
  StacktraceTop:
   g_type_check_value () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
   gtk_css_provider_load_from_file () from 
/usr/lib/x86_64-linux-gnu/libgtk-3.so.0
  Title: gsd-wacom crashed with SIGSEGV in g_type_check_value()
  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-settings-daemon/+bug/1765795/+subscriptions

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

[Desktop-packages] [Bug 1804359] Re: tutorial doesn't work

[Diego F . Rodríguez]

I'm no longer sure h brings up the tutorial after installing common-non-dfsg.
The first lines displayed  after pressing h in info are:

Next: Help,  Up: Getting Started

1.1 Starting Info on a Small Screen
===

Since your terminal has a relatively small number of lines on its

...

While this book https://tldp.org/LDP/intro-linux/html/sect_02_03.html
says the tutorial starts with:

File: info.info,  Node: Top,  Next: Getting Started,  Up: (dir)

Info: An Introduction
*

   Info is a program, which you are using now, for reading

...

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

Title:
  tutorial doesn't work

Status in texinfo package in Ubuntu:
  Confirmed

Bug description:
  Running `info` and pressing `h` doesn't bring up promised tutorial:

  ---cut---
  File: dir,  Node: Top,  This is the top of the INFO tree.

  This is the Info main menu (aka directory node).
  A few useful Info commands:

'q' quits;
'H' lists all Info commands;
'h' starts the Info tutorial;
'mTexinfo RET' visits the Texinfo manual, etc.

  ---cut---

  The error message displayed is "Cannot find node '(info)Help'"

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: info 6.5.0.dfsg.1-4
  ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12
  Uname: Linux 4.18.0-11-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13.1
  Architecture: amd64
  CurrentDesktop: i3
  Date: Wed Nov 21 07:16:55 2018
  InstallationDate: Installed on 2018-11-01 (19 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  SourcePackage: texinfo
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1804359] Re: tutorial doesn't work

[Diego F . Rodríguez]

Same problem here. Ubuntu 19.10. Info 6.6.0.dfsg.1-2ubuntu2.
Following advice from 
https://unix.stackexchange.com/questions/588026/cannot-start-the-info-tutorial-in-debian-9-stretch
 I installed emacs-common-non-dfsg.
After that pressing h inside info brings up the tutorial but the command info 
info still results in:
info: No menu item 'info-stnd' in node '(dir)Top'

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

Title:
  tutorial doesn't work

Status in texinfo package in Ubuntu:
  Confirmed

Bug description:
  Running `info` and pressing `h` doesn't bring up promised tutorial:

  ---cut---
  File: dir,  Node: Top,  This is the top of the INFO tree.

  This is the Info main menu (aka directory node).
  A few useful Info commands:

'q' quits;
'H' lists all Info commands;
'h' starts the Info tutorial;
'mTexinfo RET' visits the Texinfo manual, etc.

  ---cut---

  The error message displayed is "Cannot find node '(info)Help'"

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: info 6.5.0.dfsg.1-4
  ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12
  Uname: Linux 4.18.0-11-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13.1
  Architecture: amd64
  CurrentDesktop: i3
  Date: Wed Nov 21 07:16:55 2018
  InstallationDate: Installed on 2018-11-01 (19 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  SourcePackage: texinfo
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1870736] Re: [nvidia] Screen scaling 125% gives 200%

[Diego Lineros]

Scaling is working in my Quadro now, but I can't use as I am finding
serious performance issues. Not good.

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

Title:
  [nvidia] Screen scaling 125% gives 200%

Status in gnome-control-center package in Ubuntu:
  Confirmed
Status in mutter package in Ubuntu:
  Confirmed

Bug description:
  Procedure used:
  1.
  Fully updated system via apt update && apt upgrade

  2.
  Select the screen setup in gnome control center

  3. 
  Click the "Fractional scaling" toggle

  4. 
  Select 125% and click the green "use" button top right (it says "Anvend" in 
dansih)

  5.
  Observe that the window has grown a lot, click the "use new settings" button

  6.
  The window tells me, I am at 200% scaling. The "200%" option is now 
highlighted.

  7.
  Switch back to 100% and file this bug.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: ubuntu-release-upgrader-core 1:20.04.16
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu22
  Architecture: amd64
  CrashDB: ubuntu
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Apr  4 09:42:34 2020
  InstallationDate: Installed on 2018-01-14 (810 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=da_DK.UTF-8
   SHELL=/bin/bash
  SourcePackage: ubuntu-release-upgrader
  Symptom: release-upgrade
  UpgradeStatus: Upgraded to focal on 2020-04-03 (0 days ago)

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

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

[Desktop-packages] [Bug 1870736] Re: [nvidia] Screen scaling 125% gives 200%

[Diego Lineros]

Fedora is moving to Wayland, with Nvidia support. Perhaps that's the
solution.

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

Title:
  [nvidia] Screen scaling 125% gives 200%

Status in gnome-control-center package in Ubuntu:
  Confirmed
Status in mutter package in Ubuntu:
  Confirmed

Bug description:
  Procedure used:
  1.
  Fully updated system via apt update && apt upgrade

  2.
  Select the screen setup in gnome control center

  3. 
  Click the "Fractional scaling" toggle

  4. 
  Select 125% and click the green "use" button top right (it says "Anvend" in 
dansih)

  5.
  Observe that the window has grown a lot, click the "use new settings" button

  6.
  The window tells me, I am at 200% scaling. The "200%" option is now 
highlighted.

  7.
  Switch back to 100% and file this bug.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: ubuntu-release-upgrader-core 1:20.04.16
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu22
  Architecture: amd64
  CrashDB: ubuntu
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Apr  4 09:42:34 2020
  InstallationDate: Installed on 2018-01-14 (810 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=da_DK.UTF-8
   SHELL=/bin/bash
  SourcePackage: ubuntu-release-upgrader
  Symptom: release-upgrade
  UpgradeStatus: Upgraded to focal on 2020-04-03 (0 days ago)

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

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

[Desktop-packages] [Bug 1846374] Re: Having a video playing/paused when switched to another user generates gigabytes of error logs

[Diego]

It also happens with driver nvidia-340.108 in elementary OS 5.1.6 Hera.
In my case the error happens with VLC when trying to open the Hikvision rstp 
streaming (H264), the error lines run fast but stop when closing VLC.

I leave some lines of the error.


VLC media player 3.0.11 Vetinari (revision 3.0.11-0-gdc0c5ced72)
[564386f97a00] main libvlc: Ejecutar vlc con la interfaz predeterminada. 
Use «cvlc» para usar vlc sin interfaz.
Qt: Session management error: None of the authentication protocols specified 
are supported
QApplication: invalid style override 'adwaita' passed, ignoring it.
Available styles: Breeze, Windows, Fusion
[564386f8d3c0] main playlist: playlist is empty
[7fc12c04aee0] main decoder error: buffer deadlock prevented
MultiFramedRTPSource::doGetNextFrame1(): The total received frame size exceeds 
the client's buffer size (25).  70154 bytes of trailing data will be 
dropped!
MultiFramedRTPSource::doGetNextFrame1(): The total received frame size exceeds 
the client's buffer size (50).  100677 bytes of trailing data will be 
dropped!
[h264 @ 0x7fc13000a4e0] illegal memory management control operation 13
[7fc1340020b0] egl_x11 gl error: cannot select OpenGL API
[7fc12c04aee0] avcodec decoder: Using NVIDIA VDPAU Driver Shared Library  
340.108  Wed Dec 11 14:31:24 PST 2019 for hardware decoding
[h264 @ 0x7fc13000a4e0] Failed setup for format vdpau: hwaccel initialisation 
returned error.
[7fc12c04aee0] avcodec decoder error: existing hardware acceleration cannot 
be reused
[h264 @ 0x7fc13000a4e0] top block unavailable for requested intra mode -1
[h264 @ 0x7fc13000a4e0] error while decoding MB 2 0, bytestream 668
[h264 @ 0x7fc130026900] Missing reference picture, default is 65530
[h264 @ 0x7fc130026900] Missing reference picture, default is 65530
[h264 @ 0x7fc13002dec0] Missing reference picture, default is 65526
[h264 @ 0x7fc13002dec0] Missing reference picture, default is 65526
[h264 @ 0x7fc13008ab20] Missing reference picture, default is 65528
[h264 @ 0x7fc13008ab20] Missing reference picture, default is 65528
[h264 @ 0x7fc1300a6aa0] cabac_init_idc 3 overflow
[h264 @ 0x7fc1300a6aa0] decode_slice_header error
[h264 @ 0x7fc1300a6aa0] Missing reference picture, default is 65530
[h264 @ 0x7fc1300a6aa0] Missing reference picture, default is 65530
[h264 @ 0x7fc13000a4e0] illegal modification_of_pic_nums_idc 6
[h264 @ 0x7fc13000a4e0] decode_slice_header error
[h264 @ 0x7fc130026900] Missing reference picture, default is 65531
[h264 @ 0x7fc130026900] Missing reference picture, default is 65531
[h264 @ 0x7fc13002dec0] Missing reference picture, default is 65532
[h264 @ 0x7fc13002dec0] Missing reference picture, default is 65532
[h264 @ 0x7fc13008ab20] Missing reference picture, default is 65534
[h264 @ 0x7fc13008ab20] Missing reference picture, default is 65534
[h264 @ 0x7fc1300a6aa0] Missing reference picture, default is 65536
[h264 @ 0x7fc1300a6aa0] Missing reference picture, default is 65536
[h264 @ 0x7fc13000a4e0] cabac_init_idc 3 overflow
[h264 @ 0x7fc13000a4e0] decode_slice_header error
[7fc138078d00] freetype spu text error: LayoutParagraph(): Invalid max width
[7fc138078d00] freetype spu text error: LayoutParagraph(): Invalid max width
[h264 @ 0x7fc13000a4e0] Missing reference picture, default is 65538
[h264 @ 0x7fc13000a4e0] Missing reference picture, default is 65538
[h264 @ 0x7fc130026900] reference count overflow
[h264 @ 0x7fc130026900] decode_slice_header error

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

Title:
  Having a video playing/paused when switched to another user generates
  gigabytes of error logs

Status in nvidia-graphics-drivers-340 package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-418 package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-435 package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-440 package in Ubuntu:
  Confirmed

Bug description:
  To replicate:

  1. Start a video playing, for example in vlc. 'avcodec decoder: Using
  NVIDIA VDPAU Driver Shared Library  418.56  Fri Mar 15 12:31:51 CDT
  2019 for hardware decoding'

  2. Optionally pause it.

  3. Switch to another user.

  The original user's ~/.xsession-errors will rapidly fill up with
  errors along the lines of "vdpau_chroma filter error".

  At the same time, errors are put in /var/log/syslog as well:

  [7f9d604810a0] vdpau_chroma filter error: video mixer features failure: 
An invalid handle value was provided.
  [7f9d604810a0] vdpau_chroma filter error: video mixer attributes failure: 
An invalid handle value was provided.
  [7f9d604810a0] vdpau_chroma filter error: video mixer rendering failure: 
An invalid handle value was provided.
  (repeat ad nauseum)

  At least one of the two will rapidly fill up its partition and
  problems will arise.

  With AMD video 

[Desktop-packages] [Bug 1870736] Re: [nvidia] Screen scaling 125% gives 200%

[Diego Lineros]

Forget about this, this setting it's and will be always broken, a white
sheet will be needed.

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

Title:
  [nvidia] Screen scaling 125% gives 200%

Status in gnome-control-center package in Ubuntu:
  Confirmed
Status in mutter package in Ubuntu:
  Confirmed

Bug description:
  Procedure used:
  1.
  Fully updated system via apt update && apt upgrade

  2.
  Select the screen setup in gnome control center

  3. 
  Click the "Fractional scaling" toggle

  4. 
  Select 125% and click the green "use" button top right (it says "Anvend" in 
dansih)

  5.
  Observe that the window has grown a lot, click the "use new settings" button

  6.
  The window tells me, I am at 200% scaling. The "200%" option is now 
highlighted.

  7.
  Switch back to 100% and file this bug.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: ubuntu-release-upgrader-core 1:20.04.16
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu22
  Architecture: amd64
  CrashDB: ubuntu
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Apr  4 09:42:34 2020
  InstallationDate: Installed on 2018-01-14 (810 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=da_DK.UTF-8
   SHELL=/bin/bash
  SourcePackage: ubuntu-release-upgrader
  Symptom: release-upgrade
  UpgradeStatus: Upgraded to focal on 2020-04-03 (0 days ago)

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

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

[Desktop-packages] [Bug 1884547] [NEW] can't activate the bluethooth headsed with a2dp sound

[Diego]

Public bug reported:

I follow this bug, and still happend

https://bugs.launchpad.net/ubuntu/+source/bluez/+filebug/e91ee546-b48f-
11ea-a86b-68b5996a96c8


dpkg --status bluez | grep '^Version:'
Version: 5.53-0ubuntu3

cat /etc/*-release
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=20.04
DISTRIB_CODENAME=focal
DISTRIB_DESCRIPTION="Ubuntu 20.04 LTS"
NAME="Ubuntu"
VERSION="20.04 LTS (Focal Fossa)"
ID=ubuntu
ID_LIKE=debian
PRETTY_NAME="Ubuntu 20.04 LTS"
VERSION_ID="20.04"
HOME_URL="https://www.ubuntu.com/;
SUPPORT_URL="https://help.ubuntu.com/;
BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/;
PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy;
VERSION_CODENAME=focal
UBUNTU_CODENAME=focal

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: bluez 5.53-0ubuntu3
ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41
Uname: Linux 5.4.0-37-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.3
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Mon Jun 22 10:54:05 2020
InstallationDate: Installed on 2020-05-19 (33 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
InterestingModules: rfcomm bnep btusb bluetooth
MachineType: LENOVO 20NYS04V00
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-37-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
SourcePackage: bluez
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 03/27/2020
dmi.bios.vendor: LENOVO
dmi.bios.version: N2JET87W (1.65 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20NYS04V00
dmi.board.vendor: LENOVO
dmi.board.version: SDK0J40697 WIN
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.modalias: 
dmi:bvnLENOVO:bvrN2JET87W(1.65):bd03/27/2020:svnLENOVO:pn20NYS04V00:pvrThinkPadT490s:rvnLENOVO:rn20NYS04V00:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
dmi.product.family: ThinkPad T490s
dmi.product.name: 20NYS04V00
dmi.product.sku: LENOVO_MT_20NY_BU_Think_FM_ThinkPad T490s
dmi.product.version: ThinkPad T490s
dmi.sys.vendor: LENOVO
hciconfig:
 hci0:  Type: Primary  Bus: USB
BD Address: 04:ED:33:30:BC:12  ACL MTU: 1021:4  SCO MTU: 96:6
UP RUNNING 
RX bytes:2532201 acl:38232 sco:36899 events:9437 errors:0
TX bytes:4236888 acl:2223 sco:36783 commands:6938 errors:0
mtime.conffile..etc.bluetooth.input.conf: 2020-06-10T09:52:46.145873
mtime.conffile..etc.bluetooth.main.conf: 2020-06-04T16:03:04.084396

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


** Tags: a2dp amd64 and apport-bug bluetooth focal mic

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

Title:
  can't activate the bluethooth headsed with a2dp sound

Status in bluez package in Ubuntu:
  New

Bug description:
  I follow this bug, and still happend

  https://bugs.launchpad.net/ubuntu/+source/bluez/+filebug/e91ee546
  -b48f-11ea-a86b-68b5996a96c8

  
  dpkg --status bluez | grep '^Version:'
  Version: 5.53-0ubuntu3

  cat /etc/*-release
  DISTRIB_ID=Ubuntu
  DISTRIB_RELEASE=20.04
  DISTRIB_CODENAME=focal
  DISTRIB_DESCRIPTION="Ubuntu 20.04 LTS"
  NAME="Ubuntu"
  VERSION="20.04 LTS (Focal Fossa)"
  ID=ubuntu
  ID_LIKE=debian
  PRETTY_NAME="Ubuntu 20.04 LTS"
  VERSION_ID="20.04"
  HOME_URL="https://www.ubuntu.com/;
  SUPPORT_URL="https://help.ubuntu.com/;
  BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/;
  
PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy;
  VERSION_CODENAME=focal
  UBUNTU_CODENAME=focal

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: bluez 5.53-0ubuntu3
  ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41
  Uname: Linux 5.4.0-37-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.3
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Jun 22 10:54:05 2020
  InstallationDate: Installed on 2020-05-19 (33 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  InterestingModules: rfcomm bnep btusb bluetooth
  MachineType: LENOVO 20NYS04V00
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-37-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
  SourcePackage: bluez
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/27/2020
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N2JET87W (1.65 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20NYS04V00
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN2JET87W(1.65):bd03/27/2020:svnLENOVO:pn20NYS04V00:pvrThinkPadT490s:rvnLENOVO:rn20NYS04V00:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad T490s
  

[Desktop-packages] [Bug 1870736] Re: [nvidia] Screen scaling 125% gives 200%

[Diego Lineros]

The problem here is no the scaling itself, the problem here is being
able to separate screens configurations, fractional or not. You must be
able to set font sizes, scale, backgrounds, resolutions, etc, per screen
in an independent way.

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

Title:
  [nvidia] Screen scaling 125% gives 200%

Status in gnome-control-center package in Ubuntu:
  Confirmed
Status in mutter package in Ubuntu:
  Confirmed

Bug description:
  Procedure used:
  1.
  Fully updated system via apt update && apt upgrade

  2.
  Select the screen setup in gnome control center

  3. 
  Click the "Fractional scaling" toggle

  4. 
  Select 125% and click the green "use" button top right (it says "Anvend" in 
dansih)

  5.
  Observe that the window has grown a lot, click the "use new settings" button

  6.
  The window tells me, I am at 200% scaling. The "200%" option is now 
highlighted.

  7.
  Switch back to 100% and file this bug.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: ubuntu-release-upgrader-core 1:20.04.16
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu22
  Architecture: amd64
  CrashDB: ubuntu
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Apr  4 09:42:34 2020
  InstallationDate: Installed on 2018-01-14 (810 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=da_DK.UTF-8
   SHELL=/bin/bash
  SourcePackage: ubuntu-release-upgrader
  Symptom: release-upgrade
  UpgradeStatus: Upgraded to focal on 2020-04-03 (0 days ago)

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

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

[Desktop-packages] [Bug 702431] Re: jack sense does not work with emu20k2 chips (Creative X-Fi Titanium cards)

[Diego Jp]

This is still an unresolved issue on a fresh install of Ubuntu 20.04
(preview). Jack sense on my SB0880 is nonexistent whatsoever in ALSA.

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

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

Title:
  jack sense does not work with emu20k2 chips (Creative X-Fi Titanium
  cards)

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  experienced problem:
  When I plug a headphones into the front panel audio connector, sound comes 
from both back panel connected speakers and front panel connected headphones. 
The sound profile remains at 5.1 channels.

  expected behavior:
  The back panel audio should be muted/disabled when plugging and 
unmuted/enabled when unplugging the front panel connector. Also, it would be 
nice, if the audio profile switches to stereo when something is plugged to the 
front panel line-out, and back to the previous profile when unplugged. (I 
didn't find anything about it being implemented to the linux sound stack 
though.)

  what I did try and find out so far:
  - installed https://wiki.ubuntu.com/Audio/InstallingLinuxAlsaDriverModules 
(with kernel 2.6.35-24-generic)
  - "aplay -l" does not list a seperate front panel audio device (output 
included).
  - I wanted to retrieve a codec dump (as in 
https://wiki.ubuntu.com/ALSA/JackSense) but there are no files matching 
/proc/asound/card*/codec*.

  Any ideas where to find more useful debug output? I'm willing to dig a
  little deeper but I didn't find hints on where to look for
  plugging/unplugging events. At least dmesg remains unchanged.

  ProblemType: Bug
  DistroRelease: Ubuntu 10.10
  Package: alsa-base 1.0.23+dfsg-1ubuntu4
  Uname: Linux 2.6.37-custom1 x86_64
  NonfreeKernelModules: nvidia
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.23.
  Architecture: amd64
  ArecordDevices:
    List of CAPTURE Hardware Devices 
   card 0: XFi [Creative X-Fi], device 0: ctxfi [Front/WaveIn]
 Subdevices: 1/1
 Subdevice #0: subdevice #0
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  malte  2378 F pulseaudio
  Card0.Amixer.info:
   Card hw:0 'XFi'/'Creative X-Fi 20K2 SB0880'
 Mixer name : '20K2'
 Components : ''
 Controls  : 29
 Simple ctrls  : 10
  Date: Thu Jan 13 15:35:48 2011
  InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007)
  PackageArchitecture: all
  ProcEnviron:
   LANGUAGE=de_DE:de:en_GB:en_US:en
   LANG=de_DE.utf8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  dmi.bios.date: 12/30/2009
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: V1.12
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: P35 Platinum(MS-7345)
  dmi.board.vendor: MICRO-STAR INTERNATIONAL CO.,LTD
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: MICRO-STAR INTERNATIONAL CO.,LTD
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrV1.12:bd12/30/2009:svnMICRO-STARINTERNATIONALCO.,LTD:pnP35Platinum(MS-7345):pvr1.0:rvnMICRO-STARINTERNATIONALCO.,LTD:rnP35Platinum(MS-7345):rvr1.0:cvnMICRO-STARINTERNATIONALCO.,LTD:ct3:cvr1.0:
  dmi.product.name: P35 Platinum(MS-7345)
  dmi.product.version: 1.0
  dmi.sys.vendor: MICRO-STAR INTERNATIONAL CO.,LTD

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

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

[Desktop-packages] [Bug 1849859] Re: smb printing fails

[Diego]

Tried just now. After reboot "AuthInfoRequired username,password" still
there

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

Title:
  smb printing fails

Status in cups package in Ubuntu:
  Confirmed
Status in samba package in Ubuntu:
  Confirmed
Status in system-config-printer package in Ubuntu:
  Confirmed

Bug description:
  when I connect to smb server (nas) permanently appears

  "Error while getting peer-to-peer dbus connection: Operation was
  cancelled"

  The printer at this NAS doesn't work too.

  "held for authentication KeyError: 'auth-info-required'"

  The same printer at usb port works fine.

  Ubuntu development version 20.04
  system-config-printer version 1.5.11-4ubuntu1
  smbclient version 2:4.10.7+dfsg-0ubuntu3

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

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

[Desktop-packages] [Bug 1849859] Re: smb printing fails

[Diego]

It's correct. You need to stop, modify and start.
If you modify the file while cupsd is running on restart you lose the changes

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

Title:
  smb printing fails

Status in cups package in Ubuntu:
  Confirmed
Status in samba package in Ubuntu:
  Confirmed
Status in system-config-printer package in Ubuntu:
  Confirmed

Bug description:
  when I connect to smb server (nas) permanently appears

  "Error while getting peer-to-peer dbus connection: Operation was
  cancelled"

  The printer at this NAS doesn't work too.

  "held for authentication KeyError: 'auth-info-required'"

  The same printer at usb port works fine.

  Ubuntu development version 20.04
  system-config-printer version 1.5.11-4ubuntu1
  smbclient version 2:4.10.7+dfsg-0ubuntu3

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

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

[Desktop-packages] [Bug 1849859] Re: smb printing fails

[Diego]

Right! I have to try after reboot

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

Title:
  smb printing fails

Status in cups package in Ubuntu:
  Confirmed
Status in samba package in Ubuntu:
  Confirmed
Status in system-config-printer package in Ubuntu:
  Confirmed

Bug description:
  when I connect to smb server (nas) permanently appears

  "Error while getting peer-to-peer dbus connection: Operation was
  cancelled"

  The printer at this NAS doesn't work too.

  "held for authentication KeyError: 'auth-info-required'"

  The same printer at usb port works fine.

  Ubuntu development version 20.04
  system-config-printer version 1.5.11-4ubuntu1
  smbclient version 2:4.10.7+dfsg-0ubuntu3

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

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

[Desktop-packages] [Bug 1849859] Re: smb printing fails

[Diego]

Thank you...It works

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

Title:
  smb printing fails

Status in cups package in Ubuntu:
  Confirmed
Status in samba package in Ubuntu:
  Confirmed
Status in system-config-printer package in Ubuntu:
  Confirmed

Bug description:
  when I connect to smb server (nas) permanently appears

  "Error while getting peer-to-peer dbus connection: Operation was
  cancelled"

  The printer at this NAS doesn't work too.

  "held for authentication KeyError: 'auth-info-required'"

  The same printer at usb port works fine.

  Ubuntu development version 20.04
  system-config-printer version 1.5.11-4ubuntu1
  smbclient version 2:4.10.7+dfsg-0ubuntu3

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

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

[Desktop-packages] [Bug 1849859] Re: smb printing fails

[Diego]

Hi everyone.
Any news about this bug?
I'm trying just now...but it asks me for credentials with no way to insert 
username and password

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

Title:
  smb printing fails

Status in cups package in Ubuntu:
  Confirmed
Status in samba package in Ubuntu:
  Confirmed
Status in system-config-printer package in Ubuntu:
  Confirmed

Bug description:
  when I connect to smb server (nas) permanently appears

  "Error while getting peer-to-peer dbus connection: Operation was
  cancelled"

  The printer at this NAS doesn't work too.

  "held for authentication KeyError: 'auth-info-required'"

  The same printer at usb port works fine.

  Ubuntu development version 20.04
  system-config-printer version 1.5.11-4ubuntu1
  smbclient version 2:4.10.7+dfsg-0ubuntu3

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

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

[Desktop-packages] [Bug 1862006] Re: dock vanishes on primary monitor after locking screen if full screen windows are active on secondary monitor

[Diego Nuevo]

I left the package field blank intentionally because I'm really not sure
if gnome-shell is the appropriate package. This is a problem related
with: window management and placement, GNOME dock and lockscreen.

** Package changed: ubuntu => gnome-shell (Ubuntu)

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

Title:
  dock vanishes on primary monitor after locking screen if full screen
  windows are active on secondary monitor

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  I have a laptop system with an additional secondary monitor. I have
  the Dock configured to show up only on my primary (laptop) screen.

  When locking the screen with Super+L, and logging back in, the windows
  on my primary (laptop) screen get automatically resized to take up the
  full screen and the Dock on the left vanishes.

  This only happens when I have full screen windows displayed on my
  secondary monitor before locking the screen.

  In order to reveal the Dock again on the primary screen, I need to
  hide/show desktop (Super+D twice) or minimize/reactivate the full-
  screen app on my secondary monitor.

  This started happening after upgrading Ubuntu 19.04 to 19.10.

  The gnome-shell version reported by the gnome-shell --version command is 
3.34.1
  The GNOME version reported by the GNOME control center in the "About" section 
is 3.34.2

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

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

[Desktop-packages] [Bug 1853786] Re: Fullscreen stuck in various applications. Ubuntu 18.04 with Unity.

[Diego]

Btw, after install I've made an update and upgrade before rebooting.

Greetings!

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

Title:
  Fullscreen stuck in various applications. Ubuntu 18.04 with Unity.

Status in lightdm package in Ubuntu:
  Fix Released

Bug description:
  Ubuntu Release: Ubuntu 18.04.3 LTS
  Lightdm Version: 1.26.0-0ubuntu1

  In some programs I can't get out of fullscreen.

  I'm using Ubuntu 18.04 Bionic Beaver with Unity. I installed Unity because I 
simply don't like GNOME. The problem is that some programs get stucked in 
fullscreen, freezing the screen, not getting any response of any kind. The 
mouse moves, but that's it. Killing the process does not resolve the issue.
  This problem came with Ubuntu 18.04 or Unity since the release of Bionic 
Beaver. At this point I'm used to it. I get rid of it by going to terminal with 
ctrl+alt+f4 and typing "sudo service lightdm restart" or by rebooting with 
"sudo reboot now". But It's kind of a nuisance having to do this everytime. The 
programs that get stucked are Stellarium, Whatsdesk, SMPlayer and some flash 
players in firefox. Everyday I upgrade Ubuntu and Lightdm hoping this to be 
solved, but nothing happens.
  Weird thing: When I restart lightdm the problem dissapears until I sleep or 
reboot my notebook.

  Attached here is the "cat /var/log/syslog" output when the problem is
  ocurring using Whatdesk (at 19:53:01 I restart lightdm).

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

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

[Desktop-packages] [Bug 1853786] Re: Fullscreen stuck in various applications. Ubuntu 18.04 with Unity.

[Diego]

It turns out that if you installed Ubuntu 18.04 LTS using the .iso images 
released in April 2018, you may kept back with Linux 4.18 and old Xorg display 
server.
I updated kernel 5.0, Xorg, and graphics drivers by opting-in to “hardware 
enablement” (HWE).

In the terminal:

sudo apt install --install-recommends linux-generic-hwe-18.04 xserver-
xorg-hwe-18.04

It solved the problem.

** Changed in: lightdm (Ubuntu)
 Assignee: (unassigned) => Diego (diego-luna-1711)

** Changed in: lightdm (Ubuntu)
   Status: New => Fix Released

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

Title:
  Fullscreen stuck in various applications. Ubuntu 18.04 with Unity.

Status in lightdm package in Ubuntu:
  Fix Released

Bug description:
  Ubuntu Release: Ubuntu 18.04.3 LTS
  Lightdm Version: 1.26.0-0ubuntu1

  In some programs I can't get out of fullscreen.

  I'm using Ubuntu 18.04 Bionic Beaver with Unity. I installed Unity because I 
simply don't like GNOME. The problem is that some programs get stucked in 
fullscreen, freezing the screen, not getting any response of any kind. The 
mouse moves, but that's it. Killing the process does not resolve the issue.
  This problem came with Ubuntu 18.04 or Unity since the release of Bionic 
Beaver. At this point I'm used to it. I get rid of it by going to terminal with 
ctrl+alt+f4 and typing "sudo service lightdm restart" or by rebooting with 
"sudo reboot now". But It's kind of a nuisance having to do this everytime. The 
programs that get stucked are Stellarium, Whatsdesk, SMPlayer and some flash 
players in firefox. Everyday I upgrade Ubuntu and Lightdm hoping this to be 
solved, but nothing happens.
  Weird thing: When I restart lightdm the problem dissapears until I sleep or 
reboot my notebook.

  Attached here is the "cat /var/log/syslog" output when the problem is
  ocurring using Whatdesk (at 19:53:01 I restart lightdm).

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

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

[Desktop-packages] [Bug 1853786] [NEW] Fullscreen stuck in various applications. Ubuntu 18.04 with Unity.

[Diego]

Public bug reported:

Ubuntu Release: Ubuntu 18.04.3 LTS
Lightdm Version: 1.26.0-0ubuntu1

In some programs I can't get out of fullscreen.

I'm using Ubuntu 18.04 Bionic Beaver with Unity. I installed Unity because I 
simply don't like GNOME. The problem is that some programs get stucked in 
fullscreen, freezing the screen, not getting any response of any kind. The 
mouse moves, but that's it. Killing the process does not resolve the issue.
This problem came with Ubuntu 18.04 or Unity since the release of Bionic 
Beaver. At this point I'm used to it. I get rid of it by going to terminal with 
ctrl+alt+f4 and typing "sudo service lightdm restart" or by rebooting with 
"sudo reboot now". But It's kind of a nuisance having to do this everytime. The 
programs that get stucked are Stellarium, Whatsdesk, SMPlayer and some flash 
players in firefox. Everyday I upgrade Ubuntu and Lightdm hoping this to be 
solved, but nothing happens.
Weird thing: When I restart lightdm the problem dissapears until I sleep or 
reboot my notebook.

Attached here is the "cat /var/log/syslog" output when the problem is
ocurring using Whatdesk (at 19:53:01 I restart lightdm).

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


** Tags: 18.04 fullscreen lightdm org.gnome.sessionmanager stuck unity

** Attachment added: "/var/log/syslog when it's happening."
   
https://bugs.launchpad.net/bugs/1853786/+attachment/5307584/+files/LightDM%20Bug%20Report%20To%20Launchpad

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

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

Title:
  Fullscreen stuck in various applications. Ubuntu 18.04 with Unity.

Status in lightdm package in Ubuntu:
  New

Bug description:
  Ubuntu Release: Ubuntu 18.04.3 LTS
  Lightdm Version: 1.26.0-0ubuntu1

  In some programs I can't get out of fullscreen.

  I'm using Ubuntu 18.04 Bionic Beaver with Unity. I installed Unity because I 
simply don't like GNOME. The problem is that some programs get stucked in 
fullscreen, freezing the screen, not getting any response of any kind. The 
mouse moves, but that's it. Killing the process does not resolve the issue.
  This problem came with Ubuntu 18.04 or Unity since the release of Bionic 
Beaver. At this point I'm used to it. I get rid of it by going to terminal with 
ctrl+alt+f4 and typing "sudo service lightdm restart" or by rebooting with 
"sudo reboot now". But It's kind of a nuisance having to do this everytime. The 
programs that get stucked are Stellarium, Whatsdesk, SMPlayer and some flash 
players in firefox. Everyday I upgrade Ubuntu and Lightdm hoping this to be 
solved, but nothing happens.
  Weird thing: When I restart lightdm the problem dissapears until I sleep or 
reboot my notebook.

  Attached here is the "cat /var/log/syslog" output when the problem is
  ocurring using Whatdesk (at 19:53:01 I restart lightdm).

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

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

[Desktop-packages] [Bug 1809407] Re: [nvidia] Corrupted wallpaper after resuming from suspend or hibernation

[Diego]

Hello, Daniel. I've experienced it in 18.04 and 19.04 both with nvidia-390.129 
in a XPS with hybrid intel x nvidia.
I hope had contributed. If you need some thing let me know.

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

Title:
  [nvidia] Corrupted wallpaper after resuming from suspend or
  hibernation

Status in GNOME Shell:
  Fix Released
Status in mutter package in Ubuntu:
  Fix Released
Status in mutter source package in Bionic:
  Invalid
Status in mutter source package in Disco:
  In Progress
Status in mutter source package in Eoan:
  Fix Released

Bug description:
  [Impact]

  The Nvidia (Xorg) driver corrupts the desktop wallpaper (by design
  (1)) upon resuming from suspend. This creates a poor user experience
  and gives the impression of severe memory corruption.

  (1)
  
https://www.khronos.org/registry/OpenGL/extensions/NV/NV_robustness_video_memory_purge.txt

  [Test Case]

  0. Set up an Nvidia-only system using the proprietary Nvidia Xorg driver.
  1. Suspend and resume the machine.
  Expect: The wallpaper still looks like it did before suspending.

  [Regression Potential]

  Low. The exact same patch is in Gnome 3.34 (Ubuntu 19.10) already and
  has been used for a couple of months without issue.

  [Original Report]

  https://trello.com/c/i5hENxSO

  Every other wake from sleep presents a corrupted screen with no unlock
  app.  There's a dock and system menu on a black background with pixel
  garbage.  Some personal information in the dock's large window
  thumbnails.  Bitmap garbage flashes on the screen when interacting
  with anything.  Only workaround is doing another sleep-wake cycle.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: xorg 1:7.7+19ubuntu8
  ProcVersionSignature: Ubuntu 4.18.0-12.13-generic 4.18.17
  Uname: Linux 4.18.0-12-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..4b.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:4b:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  390.87  Tue Aug 21 12:33:05 
PDT 2018
   GCC version:  gcc version 8.2.0 (Ubuntu 8.2.0-7ubuntu1)
  ApportVersion: 2.20.10-0ubuntu13.1
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Dec 20 22:19:29 2018
  DistUpgraded: 2018-12-01 23:07:50,385 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process 
“./xorg_fix_proprietary.py” (No such file or directory) (8))
  DistroCodename: cosmic
  DistroVariant: ubuntu
  DkmsStatus:
   nvidia, 390.87, 4.18.0-11-generic, x86_64: installed
   nvidia, 390.87, 4.18.0-12-generic, x86_64: installed
   virtualbox, 5.2.18, 4.18.0-11-generic, x86_64: installed
   virtualbox, 5.2.18, 4.18.0-12-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   NVIDIA Corporation GP106 [GeForce GTX 1060 3GB] [10de:1c02] (rev a1) 
(prog-if 00 [VGA controller])
     Subsystem: eVga.com. Corp. GP106 [GeForce GTX 1060 3GB] [3842:6162]
  InstallationDate: Installed on 2018-10-28 (54 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: Gigabyte Technology Co., Ltd. Default string
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-12-generic 
root=UUID=a8c839e7-c579-4699-999a-748f804ff9e0 ro quiet splash vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to cosmic on 2018-12-02 (18 days ago)
  dmi.bios.date: 06/08/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F24
  dmi.board.asset.tag: Default string
  dmi.board.name: X99P-SLI-CF
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF24:bd06/08/2017:svnGigabyteTechnologyCo.,Ltd.:pnDefaultstring:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnX99P-SLI-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: Default string
  dmi.product.name: Default string
  dmi.product.sku: Default string
  dmi.product.version: Default string
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.95-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.2-0ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.2-0ubuntu1
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* 

[Desktop-packages] [Bug 1809407] Re: [nvidia] Corrupted wallpaper after resuming from suspend or hibernation

[Diego]

Sorry for inconvenient Daniel, but the version 3.33.4 was rejected in
review?

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

Title:
  [nvidia] Corrupted wallpaper after resuming from suspend or
  hibernation

Status in GNOME Shell:
  Unknown
Status in mutter package in Ubuntu:
  In Progress
Status in mutter source package in Bionic:
  Confirmed
Status in mutter source package in Disco:
  Confirmed
Status in mutter source package in Eoan:
  In Progress

Bug description:
  https://trello.com/c/i5hENxSO

  Every other wake from sleep presents a corrupted screen with no unlock
  app.  There's a dock and system menu on a black background with pixel
  garbage.  Some personal information in the dock's large window
  thumbnails.  Bitmap garbage flashes on the screen when interacting
  with anything.  Only workaround is doing another sleep-wake cycle.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: xorg 1:7.7+19ubuntu8
  ProcVersionSignature: Ubuntu 4.18.0-12.13-generic 4.18.17
  Uname: Linux 4.18.0-12-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..4b.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:4b:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  390.87  Tue Aug 21 12:33:05 
PDT 2018
   GCC version:  gcc version 8.2.0 (Ubuntu 8.2.0-7ubuntu1)
  ApportVersion: 2.20.10-0ubuntu13.1
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Dec 20 22:19:29 2018
  DistUpgraded: 2018-12-01 23:07:50,385 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process 
“./xorg_fix_proprietary.py” (No such file or directory) (8))
  DistroCodename: cosmic
  DistroVariant: ubuntu
  DkmsStatus:
   nvidia, 390.87, 4.18.0-11-generic, x86_64: installed
   nvidia, 390.87, 4.18.0-12-generic, x86_64: installed
   virtualbox, 5.2.18, 4.18.0-11-generic, x86_64: installed
   virtualbox, 5.2.18, 4.18.0-12-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   NVIDIA Corporation GP106 [GeForce GTX 1060 3GB] [10de:1c02] (rev a1) 
(prog-if 00 [VGA controller])
     Subsystem: eVga.com. Corp. GP106 [GeForce GTX 1060 3GB] [3842:6162]
  InstallationDate: Installed on 2018-10-28 (54 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: Gigabyte Technology Co., Ltd. Default string
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-12-generic 
root=UUID=a8c839e7-c579-4699-999a-748f804ff9e0 ro quiet splash vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to cosmic on 2018-12-02 (18 days ago)
  dmi.bios.date: 06/08/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F24
  dmi.board.asset.tag: Default string
  dmi.board.name: X99P-SLI-CF
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF24:bd06/08/2017:svnGigabyteTechnologyCo.,Ltd.:pnDefaultstring:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnX99P-SLI-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: Default string
  dmi.product.name: Default string
  dmi.product.sku: Default string
  dmi.product.version: Default string
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.95-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.2-0ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.2-0ubuntu1
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.1-3ubuntu2.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-3

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

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

[Desktop-packages] [Bug 1760849] Re: Login screen appears on only one monitor and it's not the one I want

[Diego]

In addition, for me, install lightdm solve the problem. Now, I can see
login screen on both monitors :)

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

Title:
  Login screen appears on only one monitor and it's not the one I want

Status in gdm:
  New
Status in gdm3 package in Ubuntu:
  Triaged
Status in gnome-shell package in Ubuntu:
  Confirmed

Bug description:
  Upstream bugs:
  https://gitlab.gnome.org/GNOME/gdm/issues/168
  https://gitlab.gnome.org/GNOME/gdm/issues/183
  https://gitlab.gnome.org/GNOME/gdm/issues/195
  https://gitlab.gnome.org/GNOME/gdm/issues/319
  https://gitlab.gnome.org/GNOME/gdm/issues/372

  The Ubuntu login screen is tiled on all displays, not mirrored, making
  it nearly impossible to login when using an external monitor if the
  laptop screen is not visible.

  There appears to be no available control to alter the display settings
  of the login screen. Prior to bionic, the controls followed the mouse
  onto different displays so you could login by giving the mouse a swipe
  to the right to get the controls to appear.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gdm3 3.28.0-0ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  Uname: Linux 4.15.0-13-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.9-0ubuntu2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Apr  3 22:13:53 2018
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_AU.UTF-8
   SHELL=/bin/bash
  SourcePackage: gdm3
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1760849] Re: Login screen appears on only one monitor and it's not the one I want

[Diego]

Are there some solution for it?

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

Title:
  Login screen appears on only one monitor and it's not the one I want

Status in gdm:
  New
Status in gdm3 package in Ubuntu:
  Triaged
Status in gnome-shell package in Ubuntu:
  Confirmed

Bug description:
  Upstream bugs:
  https://gitlab.gnome.org/GNOME/gdm/issues/168
  https://gitlab.gnome.org/GNOME/gdm/issues/183
  https://gitlab.gnome.org/GNOME/gdm/issues/195
  https://gitlab.gnome.org/GNOME/gdm/issues/319
  https://gitlab.gnome.org/GNOME/gdm/issues/372

  The Ubuntu login screen is tiled on all displays, not mirrored, making
  it nearly impossible to login when using an external monitor if the
  laptop screen is not visible.

  There appears to be no available control to alter the display settings
  of the login screen. Prior to bionic, the controls followed the mouse
  onto different displays so you could login by giving the mouse a swipe
  to the right to get the controls to appear.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gdm3 3.28.0-0ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  Uname: Linux 4.15.0-13-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.9-0ubuntu2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Apr  3 22:13:53 2018
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_AU.UTF-8
   SHELL=/bin/bash
  SourcePackage: gdm3
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1809407] Re: [nvidia] Corrupted wallpaper after resuming from suspend or hibernation

[Diego]

I'm affected for this BUG too. There some patch to try while?


** Attachment added: "Flicker"
   
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1809407/+attachment/5276744/+files/IMG_20190711_221552562.jpg

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

Title:
  [nvidia] Corrupted wallpaper after resuming from suspend or
  hibernation

Status in GNOME Shell:
  New
Status in mutter package in Ubuntu:
  In Progress
Status in mutter source package in Bionic:
  Confirmed
Status in mutter source package in Disco:
  Confirmed
Status in mutter source package in Eoan:
  In Progress

Bug description:
  https://trello.com/c/i5hENxSO

  Every other wake from sleep presents a corrupted screen with no unlock
  app.  There's a dock and system menu on a black background with pixel
  garbage.  Some personal information in the dock's large window
  thumbnails.  Bitmap garbage flashes on the screen when interacting
  with anything.  Only workaround is doing another sleep-wake cycle.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: xorg 1:7.7+19ubuntu8
  ProcVersionSignature: Ubuntu 4.18.0-12.13-generic 4.18.17
  Uname: Linux 4.18.0-12-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..4b.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:4b:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  390.87  Tue Aug 21 12:33:05 
PDT 2018
   GCC version:  gcc version 8.2.0 (Ubuntu 8.2.0-7ubuntu1)
  ApportVersion: 2.20.10-0ubuntu13.1
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Dec 20 22:19:29 2018
  DistUpgraded: 2018-12-01 23:07:50,385 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process 
“./xorg_fix_proprietary.py” (No such file or directory) (8))
  DistroCodename: cosmic
  DistroVariant: ubuntu
  DkmsStatus:
   nvidia, 390.87, 4.18.0-11-generic, x86_64: installed
   nvidia, 390.87, 4.18.0-12-generic, x86_64: installed
   virtualbox, 5.2.18, 4.18.0-11-generic, x86_64: installed
   virtualbox, 5.2.18, 4.18.0-12-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   NVIDIA Corporation GP106 [GeForce GTX 1060 3GB] [10de:1c02] (rev a1) 
(prog-if 00 [VGA controller])
     Subsystem: eVga.com. Corp. GP106 [GeForce GTX 1060 3GB] [3842:6162]
  InstallationDate: Installed on 2018-10-28 (54 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: Gigabyte Technology Co., Ltd. Default string
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-12-generic 
root=UUID=a8c839e7-c579-4699-999a-748f804ff9e0 ro quiet splash vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to cosmic on 2018-12-02 (18 days ago)
  dmi.bios.date: 06/08/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F24
  dmi.board.asset.tag: Default string
  dmi.board.name: X99P-SLI-CF
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF24:bd06/08/2017:svnGigabyteTechnologyCo.,Ltd.:pnDefaultstring:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnX99P-SLI-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: Default string
  dmi.product.name: Default string
  dmi.product.sku: Default string
  dmi.product.version: Default string
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.95-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.2-0ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.2-0ubuntu1
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.1-3ubuntu2.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-3

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

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

[Desktop-packages] [Bug 1829888] [NEW] Al arrancar la pantalla queda nula

[diego muñoz]

Public bug reported:

Arranco el ordenador y no consigo poder funcionar porque la pantalla que
da sin energia. lo apago forzado y al reiniciarlo arranca con la
pantalla de opciones Ubuntu, lo corrige y ya puedo trabajar, pero la
siguiente vez que lo arranco vuelve hacer lo mismo.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xorg 1:7.7+19ubuntu7.1
ProcVersionSignature: Ubuntu 4.15.0-50.54-generic 4.15.18
Uname: Linux 4.15.0-50-generic i686
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.9-0ubuntu7.6
Architecture: i386
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
Date: Tue May 21 17:39:52 2019
DistUpgraded: Fresh install
DistroCodename: bionic
DistroVariant: ubuntu
GraphicsCard:
 Advanced Micro Devices, Inc. [AMD/ATI] Park [Mobility Radeon HD 5430] 
[1002:68e1] (prog-if 00 [VGA controller])
   Subsystem: ASUSTeK Computer Inc. Caicos [Radeon HD 5450] [1043:3000]
InstallationDate: Installed on 2017-06-18 (701 days ago)
InstallationMedia: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release i386 
(20120817.3)
MachineType: ASUSTeK Computer INC. V-P8H67E
ProcEnviron:
 PATH=(custom, no user)
 LANG=es_ES.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-50-generic 
root=UUID=3f37daeb-b04b-4157-aeba-7a8cb4e19e1f ro vesafb.invalid=1
Renderer: Software
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 02/11/2011
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 0702
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: V-P8H67E
dmi.board.vendor: ASUSTeK Computer INC.
dmi.board.version: Rev 1.xx
dmi.chassis.asset.tag: Asset-1234567890
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.version: Chassis Version
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0702:bd02/11/2011:svnASUSTeKComputerINC.:pnV-P8H67E:pvrSystemVersion:rvnASUSTeKComputerINC.:rnV-P8H67E:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: V-P8H67E
dmi.product.version: System Version
dmi.sys.vendor: ASUSTeK Computer INC.
version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
version.libdrm2: libdrm2 2.4.95-1~18.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.8-0ubuntu0~18.04.2
version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.8-0ubuntu0~18.04.2
version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2
xserver.bootTime: Tue May 21 13:41:28 2019
xserver.configfile: default
xserver.logfile: /var/log/Xorg.0.log
xserver.version: 2:1.19.6-1ubuntu4.2

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


** Tags: apport-bug bionic i386 ubuntu

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

Title:
  Al arrancar la pantalla queda nula

Status in xorg package in Ubuntu:
  New

Bug description:
  Arranco el ordenador y no consigo poder funcionar porque la pantalla
  que da sin energia. lo apago forzado y al reiniciarlo arranca con la
  pantalla de opciones Ubuntu, lo corrige y ya puedo trabajar, pero la
  siguiente vez que lo arranco vuelve hacer lo mismo.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-50.54-generic 4.15.18
  Uname: Linux 4.15.0-50-generic i686
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: i386
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Tue May 21 17:39:52 2019
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Park [Mobility Radeon HD 5430] 
[1002:68e1] (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. Caicos [Radeon HD 5450] [1043:3000]
  InstallationDate: Installed on 2017-06-18 (701 days ago)
  InstallationMedia: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release i386 
(20120817.3)
  MachineType: ASUSTeK Computer INC. V-P8H67E
  ProcEnviron:
   PATH=(custom, no user)
   LANG=es_ES.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-50-generic 
root=UUID=3f37daeb-b04b-4157-aeba-7a8cb4e19e1f ro vesafb.invalid=1
  Renderer: Software
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/11/2011
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0702
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: V-P8H67E
  dmi.board.vendor: ASUSTeK Computer INC.
  

[Desktop-packages] [Bug 1815693] Re: Kubuntu 18.10 Xorg severe memory leak

[Diego Droghini]

Hi everyone,
  I encountered the same problem after updating from kubuntu 17.10 to kubuntu 
18.04 (no virtual box).
Infact after the update, checking the xorg virtual size memory with 'ps aux', i 
can see that it keeps growing. Even using the 'free' command the buff/cache 
field continues to grow.
Even when booting directly from a USB stick (before installation) with 
kubuntu18.04 the problem persists.

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

Title:
  Kubuntu 18.10 Xorg severe memory leak

Status in xorg-server package in Ubuntu:
  Confirmed
Status in xserver-xorg-video-vmware package in Ubuntu:
  Confirmed

Bug description:
  Suddenly sometimes during the past two weeks my kubuntu installation
  has started to freeze up. I can't remember what apt upgrade that
  caused it, and I have done several the last few days hoping for it to
  be resolved.

  I didn't know what was causing it as I hadn't made any other changes
  expect for the odd apt upgrade. Before that I had just finished a
  several weeks long session of intense work around the clock without
  having to reboot even once. Suddenly it is now freezing up within
  hours. Even without doing anything, just leaving the computer alone.
  However, yesterday I accidentally discovered that my RAM was filled
  up. More than filled up, even all swap was full. And before I could
  close anything down it froze up again.

  So TLDR; I have today logged the memory consumption while I was
  handling some bills and linked is a log of constantly increasing Xorg
  memory usage. So it goes until it chokes the machine and only a hard
  reboot is possible.

  My installed RAM is 10GB. Swap is 6GB. Please refer to the linked file to see 
how the Xorg usage creeps up.
  https://www.dropbox.com/s/nf1ev2dxdlc6gqw/xorg_leak.log?dl=0

  I should add that this bug seems specific to Kubuntu, and (I guess)
  associated with running under Virtualbox. I have another Ubuntu 18.04
  (i.e. not _K_ubuntu) running on bare metal and it is not having any
  problems.

  Please advise what additional information I should post to have this
  resolved.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: xorg 1:7.7+19ubuntu8
  ProcVersionSignature: Ubuntu 4.18.0-15.16-generic 4.18.20
  Uname: Linux 4.18.0-15-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13.2
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: KDE
  Date: Wed Feb 13 01:00:13 2019
  DistUpgraded: 2019-02-09 11:54:01,040 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process 
“./xorg_fix_proprietary.py” (No such file or directory) (8))
  DistroCodename: cosmic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   VMware SVGA II Adapter [15ad:0405] (prog-if 00 [VGA controller])
     Subsystem: VMware SVGA II Adapter [15ad:0405]
  InstallationDate: Installed on 2015-10-22 (1209 days ago)
  InstallationMedia: Kubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 003: ID 80ee:0021 VirtualBox USB Tablet
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: innotek GmbH VirtualBox
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-15-generic 
root=UUID=8959cd47-b52f-4a6e-97bb-5d509e3c2480 ro quiet splash
  Renderer: Software
  SourcePackage: xorg
  UpgradeStatus: Upgraded to cosmic on 2019-02-09 (3 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 N/A
  version.libdrm2: libdrm2 2.4.95-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.2-0ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.2-0ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.1-3ubuntu2.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-3

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

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

[Desktop-packages] [Bug 1736222] Re: speech-dispatcher distorts all sound

[Diego]

18.04.2 LTS (Bionic Beaver) Gets triggered every time any sound is playing and 
I need any screen reading (like a website in firefox in special reading view)
It feels like the existing previous sound output gets used as input for mixing 
with the screen reader... with the added pronlem that at least 3 screen reader 
processes are created, thus adding 3 echoes that constitute the noise...

`killall speech-dispatcher` stops the noise but  kills the screeen
reading

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

Title:
  speech-dispatcher distorts all sound

Status in speech-dispatcher package in Ubuntu:
  Confirmed

Bug description:
  So, a brand new computer running Ubuntu 16.04.3 LTS.
  In hardinfo summary, my audio adapters are
  • HDA-Intel - HDA Intel HDMI
  • HDA-Intel - HDA Intel PCH
  • HDA-Intel - HDA NVidia
  In detail: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor HD Audio 
Controller (rev 06)
  Memory 16kb (non-prefetchable), snd_hda_intel

  As soon as I load a website in Firefox that utilizes speech-dispatcher
  (fimfiction.net) all sounds get distorted, whether I click a paragraph
  for TTS reading or not. The problem seems to go away if I don't use
  the site after a while. When I close down Firefox the problem still
  lingers a bit, but maybe not as long. One thing I did which seemed
  faster was close down everything, then load what I wanted to listen to
  (Skype, Discord), and if it still persisted I would go into "Sound
  Settings" and after a few blinks in that window the sound is normal
  again.

  While the site is open, according to "Sound Settings" (from the
  speaker icon menu) and Pulse Audio Volume Controller (pavu) there are
  4 copies of this package. Muting them did not help the problem, but
  moving one of them, and a very specific one, from the "Built-in Audio
  Analog Stereo" to something else like HDA NVidia (HDMI 3) seems to be
  a workaround.

  Just so you know, I do not use the HDMI cable for sound, but instead
  use the "headphones" jack. If you need any more details, I'll try to
  provide them.

  /Edward

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

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

[Desktop-packages] [Bug 1816308] Re: gnome-shell crashes with SIGSEGV in meta_window_actor_is_destroyed() when changing workspace after several minutes of work in one workspace

[Diego]

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

Michael Grivas (mgrivas), could you please elaborate on how you solved
your problem? I am facing the same issue.

I tried changing the following entris with dconf:

/org/gnome/mines/use-animations
/org/gnome/desktop/interface/enable-animations
/org/gnome/shell/extensions/dash-to-dock/animation-time
/org/gnome/shell/extensions/dash-to-dock/animate-show-apps

Fiddling with the above entries did not solve the issue.

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

Title:
   gnome-shell crashes with SIGSEGV in meta_window_actor_is_destroyed()
  when changing workspace after several minutes of work in one workspace

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  After some recent update, I face the following issue:
  Working on a workspace for some time (cannot say how much time), with or 
without lots of windows open, the workspace takes 2-3 minutes to recover, shows 
a crash dialog and restarts gnome.

  In fewer cases, after days of not rebooting, the gnome-shell dies
  instead of restarting, killing the session.

  I normally click to submit the bug reports, which should be in:
  
https://errors.ubuntu.com/user/b56fc2894b10f99f5b9629befd4030528cf0fe943fd6d376f53b724791abcc83b582e15ae82346f04a637b2c7be643f2749a1bdec23b9bc4b9d8cd4c4aa1070e

  There are both created the /var/lib/whoopsie/whoopsie-id  and 
/var/crash/_usr_bin_gnome-shell.1000.crash . 
  The ubuntu-bug /var/crash/_usr_bin_gnome-shell.1000.crash does not work. 
Seems like apport-gtk is frozen.

  The next updates did not fix it.

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

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

[Desktop-packages] [Bug 1592550] Re: nm-applet does not appear in notification area

[Diego Foglino]

I have update ubuntu mate from 16.04 at 18.04.
Now icon not appear, but the connection wi-fi work fine

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

Title:
  nm-applet does not appear in notification area

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

Bug description:
  I have to log in to a wifi service via PEAP at my university. After
  doing this, on each successive reboot my nm-applet does not appear in
  my notification area (all my other applets are still there). I can get
  the applet to appear by running "nm-applet" in a terminal. I do get
  two notifications in the terminal as nm-applet loads:

  (nm-applet:3100): Gtk-WARNING **: Theme parsing error: gtk-
  main.css:69:33: Failed to import: Error opening file: No such file or
  directory

  (nm-applet:3100): Gdk-CRITICAL **: gdk_window_thaw_toplevel_updates:
  assertion 'window->update_and_descendants_freeze_count > 0' failed

  I have installed Ubuntu Mate twice on my system, and the applet works fine 
after logging into various networks until I set up the PEAP login. Also, even 
if the applet doesn't appear I am still connected to any saved wifi network 
within range.
  I am running Ubuntu Mate 16.04, with Mate 1.12.1 on a Dell Latitude e6410.
  Thank you.

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

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

[Desktop-packages] [Bug 1774957] Re: Network icons in status menu disappearing

[Diego Foglino]

I have Ubuntu mate 18.04.2. I don't have gnome-shell installed.
There is this bug.

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

Title:
  Network icons in status menu disappearing

Status in gnome-shell package in Ubuntu:
  Fix Released

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

  ---

  Ever since the update to Ubuntu 18.04 I'm having issues with the
  status menu at the top right of the screen.

  Normally you'd have a wired network connection icon displayed at the top 
without opening the menu. In my case it is not displayed half of the time. In 
the menu list no icon nor label is displayed for the wired connection menu item.
  When talking about half of the time it means that I can randomly make it 
display again when removing the USB network adapter and reconnecting it e.g.
  This does not work reliably though.

  When connecting to a VPN, normally you'd get an additional icon at the
  top. This is not the case any more, nor does the switch behind an
  activated VPN turns change to an active state. The result is that you
  can activate a VPN using the switch, but you can verify that it is
  activated, nor can you de-active the VPN through the menu. This does
  change in settings though.

  Wireless settings are no longer displayed in the menu at all. So no
  way to activate it or connect to a specific network.

  I tried reconfiguring (dpkg-reconfigure) gnome-shell as well as
  network-manager-gnome, to no avail.

  Attached you'll find a screenshot illustrating the issue. You'll see
  two icons missing to the left of the volume icon, as well as the
  wireless menu missing completely and no icon and text label for the
  wired connection menu item.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.28.1-0ubuntu2
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  Uname: Linux 4.15.0-22-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.1
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Mon Jun  4 10:47:05 2018
  DisplayManager: gdm3
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2016-10-07 (604 days ago)
  InstallationMedia: Ubuntu-GNOME 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160720)
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to bionic on 2018-05-31 (3 days ago)

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

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

[Desktop-packages] [Bug 1785964] Re: Unable to unlock the desktop session: systemd-logind: got pause for 13:69

[Diego Bersanetti]

I have integrated graphics Intel HD4600 (Haswell) and discrete Nvidia
GTX750M as well, which is managed by the Nvidia binary blob (the nouveau
module is blacklisted) but usually disabled. I also have an external
monitor always plugged in while at home, and nothing elsewhere.
Unfortunately the bug happens in every situation. I have to say, though,
that the frequency has been going down, I haven't experienced it in the
last ~10 days and I am not sure why, as my usage pattern (physical
places, networks, monitors, etc...) is always the same.

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

Title:
  Unable to unlock the desktop session: systemd-logind: got pause for
  13:69

Status in linux package in Ubuntu:
  Incomplete
Status in xorg-server package in Ubuntu:
  Confirmed

Bug description:
  When this issue happens, you won't be able to unlock your desktop session (VT 
works fine).
  This happened twice today for me, one is after a suspend, one is just a 
screen lock. Not sure what is the trigger yet.

  Syndrome:
  On the login screen after typing the correct password, you will see a small 
circle keep spinning and that's it. I need to restart my computer to get it 
back to normal.

  
  In the syslog this error message looks fishy:
  Aug  8 10:44:57 Leggiero gnome-shell[2118]: g_array_unref: assertion 'array' 
failed

  
  This is part of the syslog fetching from a VT after a GUI unlock attempt 
(session 24 is the desktop login attempt):

  Aug  8 10:44:42 Leggiero systemd[1]: Started Session 24 of user sam.
  Aug  8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) 
systemd-logind: got resume for 226:0
  Aug  8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) AIGLX: 
Resuming AIGLX clients after VT switch
  Aug  8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) modeset(0): 
EDID vendor "AUO", prod id 4204
  Aug  8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) modeset(0): 
Printing DDC gathered Modelines:
  Aug  8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) modeset(0): 
Modeline "1366x768"x0.0   76.20  1366 1404 1426 1590  768 771 777 798 +hsync 
-vsync (47.9 kHz eP)
  Aug  8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) modeset(0): 
Modeline "1366x768"x0.0   76.20  1366 1404 1426 1988  768 771 777 798 +hsync 
-vsync (38.3 kHz e)
  Aug  8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) 
systemd-logind: got resume for 13:78
  Aug  8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) event14 - 
Dell WMI hotkeys: is tagged by udev as: Keyboard
  Aug  8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) event14 - 
Dell WMI hotkeys: device is a keyboard
  Aug  8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) 
systemd-logind: got resume for 13:66
  Aug  8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) event2  - 
Sleep Button: is tagged by udev as: Keyboard
  Aug  8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) event2  - 
Sleep Button: device is a keyboard
  Aug  8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) 
systemd-logind: got resume for 13:79
  Aug  8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) event15 - 
Integrated_Webcam_HD: Integrate: is tagged by udev as: Keyboard
  Aug  8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) event15 - 
Integrated_Webcam_HD: Integrate: device is a keyboard
  Aug  8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) 
systemd-logind: got resume for 13:68
  Aug  8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) event4  - AT 
Translated Set 2 keyboard: is tagged by udev as: Keyboard
  Aug  8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) event4  - AT 
Translated Set 2 keyboard: device is a keyboard
  Aug  8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) 
systemd-logind: got resume for 13:67
  Aug  8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) event3  - 
Power Button: is tagged by udev as: Keyboard
  Aug  8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) event3  - 
Power Button: device is a keyboard
  Aug  8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) 
systemd-logind: got resume for 13:71
  Aug  8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) event7  - 
AlpsPS/2 ALPS GlidePoint: is tagged by udev as: Touchpad
  Aug  8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) event7  - 
AlpsPS/2 ALPS GlidePoint: device is a touchpad
  Aug  8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) 
systemd-logind: got resume for 13:72
  Aug  8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) event8  - 
DELL Wireless hotkeys: is tagged by udev as: Keyboard
  Aug  8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) event8  - 
DELL Wireless hotkeys: device is a keyboard
  Aug  8 10:44:55 Leggiero 

[Desktop-packages] [Bug 1810574] [NEW] Audio is low pitched/deeper on AMD GPU

[Diego Velasquez]

Public bug reported:

I have a dual screen set up, a Display Port Monitor and a HDMI monitor
on Ubuntu 18.04.1 ALSA driver k4.15.0-43-generic. The display port
monitor has speakers so I used as my main speakers, but, the audio of
any source sounds deeper/slower than it should be. Even videos of any
source last longer. For example, 10 "seconds" of  any video in my
computer are 12.5 seconds in my phone stopwatch. I'm using a radeon r9
280x.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: alsa-base 1.0.25+dfsg-0ubuntu5
ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18
Uname: Linux 4.15.0-43-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.5
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  diego  1586 F pulseaudio
 /dev/snd/pcmC1D3p:   diego  1586 F...m pulseaudio
 /dev/snd/controlC1:  diego  1586 F pulseaudio
CurrentDesktop: ubuntu:GNOME
Date: Fri Jan  4 21:31:30 2019
InstallationDate: Installed on 2019-01-03 (1 days ago)
InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725)
PackageArchitecture: all
SourcePackage: alsa-driver
Symptom: audio
Symptom_AlsaPlaybackTest: ALSA playback test through plughw:HDMI failed
Symptom_Card: Tahiti HDMI Audio [Radeon HD 7870 XT / 7950/7970] - HDA ATI HDMI
Symptom_Jack: Digital Out, HDMI
Symptom_Type: Digital clip or distortion, or "overdriven" sound
Title: [System Product Name, ATI R6xx HDMI, Digital Out, HDMI] Sound is 
distorted
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 02/04/2013
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 0502
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: H61M-E
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: Rev X.0x
dmi.chassis.asset.tag: Asset-1234567890
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.version: Chassis Version
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0502:bd02/04/2013:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnH61M-E:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: System Product Name
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer

** Affects: alsa-driver (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug bionic

** Summary changed:

- Audio is low pitch on AMD GPU
+ Audio is low pitched/deeper on AMD GPU

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

Title:
  Audio is low pitched/deeper on AMD GPU

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  I have a dual screen set up, a Display Port Monitor and a HDMI monitor
  on Ubuntu 18.04.1 ALSA driver k4.15.0-43-generic. The display port
  monitor has speakers so I used as my main speakers, but, the audio of
  any source sounds deeper/slower than it should be. Even videos of any
  source last longer. For example, 10 "seconds" of  any video in my
  computer are 12.5 seconds in my phone stopwatch. I'm using a radeon r9
  280x.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18
  Uname: Linux 4.15.0-43-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  diego  1586 F pulseaudio
   /dev/snd/pcmC1D3p:   diego  1586 F...m pulseaudio
   /dev/snd/controlC1:  diego  1586 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Jan  4 21:31:30 2019
  InstallationDate: Installed on 2019-01-03 (1 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:HDMI failed
  Symptom_Card: Tahiti HDMI Audio [Radeon HD 7870 XT / 7950/7970] - HDA ATI HDMI
  Symptom_Jack: Digital Out, HDMI
  Symptom_Type: Digital clip or distortion, or "overdriven" sound
  Title: [System Product Name, ATI R6xx HDMI, Digital Out, HDMI] Sound is 
distorted
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/04/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0502
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: H61M-E
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0502:bd02/04/2013:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnH61M-E:rvrRevX.0x:cvnCh

[Desktop-packages] [Bug 1785964] Re: Unable to unlock the desktop session: systemd-logind: got pause for 13:69

[Diego Bersanetti]

I have some new information: the bug is still happening as before, today
I resumed my session and the login screen got stuck as usual; I left it
there for a couple of minutes, then I unplugged and replugged the
ethernet cable and, as soon as the network was up again, the session was
unlocked! Maybe this can be helpful to understand the bug...

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

Title:
  Unable to unlock the desktop session: systemd-logind: got pause for
  13:69

Status in linux package in Ubuntu:
  Incomplete
Status in xorg-server package in Ubuntu:
  Confirmed

Bug description:
  When this issue happens, you won't be able to unlock your desktop session (VT 
works fine).
  This happened twice today for me, one is after a suspend, one is just a 
screen lock. Not sure what is the trigger yet.

  Syndrome:
  On the login screen after typing the correct password, you will see a small 
circle keep spinning and that's it. I need to restart my computer to get it 
back to normal.

  
  In the syslog this error message looks fishy:
  Aug  8 10:44:57 Leggiero gnome-shell[2118]: g_array_unref: assertion 'array' 
failed

  
  This is part of the syslog fetching from a VT after a GUI unlock attempt 
(session 24 is the desktop login attempt):

  Aug  8 10:44:42 Leggiero systemd[1]: Started Session 24 of user sam.
  Aug  8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) 
systemd-logind: got resume for 226:0
  Aug  8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) AIGLX: 
Resuming AIGLX clients after VT switch
  Aug  8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) modeset(0): 
EDID vendor "AUO", prod id 4204
  Aug  8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) modeset(0): 
Printing DDC gathered Modelines:
  Aug  8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) modeset(0): 
Modeline "1366x768"x0.0   76.20  1366 1404 1426 1590  768 771 777 798 +hsync 
-vsync (47.9 kHz eP)
  Aug  8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) modeset(0): 
Modeline "1366x768"x0.0   76.20  1366 1404 1426 1988  768 771 777 798 +hsync 
-vsync (38.3 kHz e)
  Aug  8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) 
systemd-logind: got resume for 13:78
  Aug  8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) event14 - 
Dell WMI hotkeys: is tagged by udev as: Keyboard
  Aug  8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) event14 - 
Dell WMI hotkeys: device is a keyboard
  Aug  8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) 
systemd-logind: got resume for 13:66
  Aug  8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) event2  - 
Sleep Button: is tagged by udev as: Keyboard
  Aug  8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) event2  - 
Sleep Button: device is a keyboard
  Aug  8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) 
systemd-logind: got resume for 13:79
  Aug  8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) event15 - 
Integrated_Webcam_HD: Integrate: is tagged by udev as: Keyboard
  Aug  8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) event15 - 
Integrated_Webcam_HD: Integrate: device is a keyboard
  Aug  8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) 
systemd-logind: got resume for 13:68
  Aug  8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) event4  - AT 
Translated Set 2 keyboard: is tagged by udev as: Keyboard
  Aug  8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) event4  - AT 
Translated Set 2 keyboard: device is a keyboard
  Aug  8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) 
systemd-logind: got resume for 13:67
  Aug  8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) event3  - 
Power Button: is tagged by udev as: Keyboard
  Aug  8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) event3  - 
Power Button: device is a keyboard
  Aug  8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) 
systemd-logind: got resume for 13:71
  Aug  8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) event7  - 
AlpsPS/2 ALPS GlidePoint: is tagged by udev as: Touchpad
  Aug  8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) event7  - 
AlpsPS/2 ALPS GlidePoint: device is a touchpad
  Aug  8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) 
systemd-logind: got resume for 13:72
  Aug  8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) event8  - 
DELL Wireless hotkeys: is tagged by udev as: Keyboard
  Aug  8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) event8  - 
DELL Wireless hotkeys: device is a keyboard
  Aug  8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) libinput: 
PixArt Microsoft USB Optical Mouse: SetProperty on 286 called but device is 
disabled.
  Aug  8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: This 

[Desktop-packages] [Bug 1728012] Re: Many 3rd party scanner drivers are broken by a sane change

[Diego Arimany]

Since 2017 until now (2019)

For EPSON's website provides Linux packages for scanners and printers as
(.deb, .rpm, or source) which are simple to install. In two steps (if
you have it on the network).

Step 1.
Go to EPSON Driver and Software Download Center 
(http://download.ebz.epson.net/dsc/search/01/search/)
Download and unpack the scanner driver (Image Scan, currently version 1.3.40)

imagescan-bundle-linuxmint-19-1.3.40.x64.deb.tar.gz

Then, run ./install.sh 
sudo ./install.sh

Step 2. (for a newtork scanner)
Edit the file /etc/sane.d/epson2.conf
Modify the line
net 192.168.xxx.yyy (to match your scanner IP)

That's it.
A full how to is at my website 
http://diegoarimany.com/installing-epson-printers-and-scanners-under-linux-mint/

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

Title:
  Many 3rd party scanner drivers are broken by a sane change

Status in sane-backends package in Ubuntu:
  Confirmed

Bug description:
  Many scanners can no more be used since sane has changed something:
  The 3rd-party plug-in the vendor provides as .deb package will still
  install. But the scanner is no more recognized.

  Scanners that are affected are(besides others):
   - Epson Perfection V10
   - Epson Perfection V1000
   - Epson WorkForce GT-1500
   - Brother MFC-8510DN
   - Epson Perfection V33

  It is to note that the probability that the scanner manufacturers fix
  things others broke is below 100%.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: libsane1 1.0.27-1~experimental2ubuntu2
  Uname: Linux 4.14.0-041400rc5-lowlatency x86_64
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  Date: Fri Oct 27 12:35:52 2017
  EcryptfsInUse: Yes
  SourcePackage: sane-backends
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1798790] Re: Ubuntu login screen never appears when using the Nvidia driver (and setting WaylandEnable=false fixes it)

[Diego Germán Gonzalez]

This is not a problem of Wayland or Ubuntu but of Gnome and the Nvidia driver.
In fact Fedora 29 has the same problem, only it has to come out a month later 
they deactivate the proprietary driver and force to use Noveau.

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

Title:
  Ubuntu login screen never appears when using the Nvidia driver (and
  setting WaylandEnable=false fixes it)

Status in gdm3 package in Ubuntu:
  Confirmed
Status in mutter package in Ubuntu:
  Confirmed

Bug description:
  https://gitlab.gnome.org/GNOME/gdm/issues/435

  ---

  The boot process hangs with the last message being "started bpfilter".
  There is unusual Network activity during that time. The light of the
  WiFi adapter is blinking a lot.

  I am not sure the problem is with the gdm3 package. As a matter of
  fact, I would remove it and let someone more experienced to set it.
  I'm afraid I might break something, though.

  The specific steps or actions you took that caused you to encounter the 
problem: 1. Boot Ubuntu 18.10 with the Nvidia proprietary drivers
  installed.

  The behavior you expected: I expected Ubuntu 18.10 to boot normally.

  The behavior you actually encountered: The computer gets stuck in a
  command-like environment with the last message being "started
  bpfilter". You can't type any commands.

  I have found that uninstalling the Nvidia proprietary drivers by going
  into recovery mode fixes the issue.

  Booting with the earlier kernel doesn't fix the issue. Installing the
  earlier v.340 driver also doesn't fix the issue.

  This (https://askubuntu.com/questions/1032639/ubuntu-18-04-stuck-in-
  boot-after-starting-gnome-display-manager-on-intel-graphic) seems
  relevant. This is where I found the "solution".

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

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

[Desktop-packages] [Bug 1805136] [NEW] package emacs-common 1:25.2+1-11 failed to install/upgrade: unable to create new file '/var/lib/dpkg/info/emacs-common.list-new': Operation not permitted

[Diego Betto]

Public bug reported:

18.04 -> 18.10

ProblemType: Package
DistroRelease: Ubuntu 18.10
Package: emacs-common 1:25.2+1-11
ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12
Uname: Linux 4.18.0-11-generic x86_64
ApportVersion: 2.20.10-0ubuntu13.1
Architecture: amd64
Date: Mon Nov 26 12:52:32 2018
DuplicateSignature:
 package:emacs-common:1:25.2+1-11
 Unpacking emacs-common (1:25.2+1-11) ...
 dpkg: error processing archive 
/tmp/apt-dpkg-install-jFqn2A/01-emacs-common_1%3a25.2+1-11_all.deb (--unpack):
  unable to create new file '/var/lib/dpkg/info/emacs-common.list-new': 
Operation not permitted
ErrorMessage: unable to create new file 
'/var/lib/dpkg/info/emacs-common.list-new': Operation not permitted
PackageArchitecture: all
Python3Details: /usr/bin/python3.6, Python 3.6.7, python3-minimal, 3.6.7-1~18.10
PythonDetails: /usr/bin/python2.7, Python 2.7.15+, python-minimal, 2.7.15-3
RelatedPackageVersions:
 dpkg 1.19.0.5ubuntu5
 apt  1.7.0
SourcePackage: emacs
Title: package emacs-common 1:25.2+1-11 failed to install/upgrade: unable to 
create new file '/var/lib/dpkg/info/emacs-common.list-new': Operation not 
permitted
UpgradeStatus: Upgraded to cosmic on 2018-11-26 (0 days ago)

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


** Tags: amd64 apport-package cosmic

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

Title:
  package emacs-common 1:25.2+1-11 failed to install/upgrade: unable to
  create new file '/var/lib/dpkg/info/emacs-common.list-new': Operation
  not permitted

Status in emacs package in Ubuntu:
  New

Bug description:
  18.04 -> 18.10

  ProblemType: Package
  DistroRelease: Ubuntu 18.10
  Package: emacs-common 1:25.2+1-11
  ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12
  Uname: Linux 4.18.0-11-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13.1
  Architecture: amd64
  Date: Mon Nov 26 12:52:32 2018
  DuplicateSignature:
   package:emacs-common:1:25.2+1-11
   Unpacking emacs-common (1:25.2+1-11) ...
   dpkg: error processing archive 
/tmp/apt-dpkg-install-jFqn2A/01-emacs-common_1%3a25.2+1-11_all.deb (--unpack):
unable to create new file '/var/lib/dpkg/info/emacs-common.list-new': 
Operation not permitted
  ErrorMessage: unable to create new file 
'/var/lib/dpkg/info/emacs-common.list-new': Operation not permitted
  PackageArchitecture: all
  Python3Details: /usr/bin/python3.6, Python 3.6.7, python3-minimal, 
3.6.7-1~18.10
  PythonDetails: /usr/bin/python2.7, Python 2.7.15+, python-minimal, 2.7.15-3
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu5
   apt  1.7.0
  SourcePackage: emacs
  Title: package emacs-common 1:25.2+1-11 failed to install/upgrade: unable to 
create new file '/var/lib/dpkg/info/emacs-common.list-new': Operation not 
permitted
  UpgradeStatus: Upgraded to cosmic on 2018-11-26 (0 days ago)

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

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

[Desktop-packages] [Bug 1805133] [NEW] package adwaita-icon-theme 3.30.0-0ubuntu1 failed to install/upgrade: unable to open '/usr/share/pkgconfig/adwaita-icon-theme.pc.dpkg-new': Operation not permitt

[Diego Betto]

Public bug reported:

crash on login after 18.04 -> 18.10

ProblemType: Package
DistroRelease: Ubuntu 18.10
Package: adwaita-icon-theme 3.30.0-0ubuntu1
ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12
Uname: Linux 4.18.0-11-generic x86_64
ApportVersion: 2.20.10-0ubuntu13.1
Architecture: amd64
Date: Mon Nov 26 12:50:09 2018
DuplicateSignature:
 package:adwaita-icon-theme:3.30.0-0ubuntu1
 Unpacking adwaita-icon-theme (3.30.0-0ubuntu1) over (3.28.0-1ubuntu1) ...
 dpkg: error processing archive 
/tmp/apt-dpkg-install-rbRQG1/72-adwaita-icon-theme_3.30.0-0ubuntu1_all.deb 
(--unpack):
  unable to open '/usr/share/pkgconfig/adwaita-icon-theme.pc.dpkg-new': 
Operation not permitted
ErrorMessage: unable to open 
'/usr/share/pkgconfig/adwaita-icon-theme.pc.dpkg-new': Operation not permitted
PackageArchitecture: all
Python3Details: /usr/bin/python3.6, Python 3.6.7, python3-minimal, 3.6.7-1~18.10
PythonDetails: /usr/bin/python2.7, Python 2.7.15+, python-minimal, 2.7.15-3
RelatedPackageVersions:
 dpkg 1.19.0.5ubuntu5
 apt  1.7.0
SourcePackage: adwaita-icon-theme
Title: package adwaita-icon-theme 3.30.0-0ubuntu1 failed to install/upgrade: 
unable to open '/usr/share/pkgconfig/adwaita-icon-theme.pc.dpkg-new': Operation 
not permitted
UpgradeStatus: Upgraded to cosmic on 2018-11-26 (0 days ago)

** Affects: adwaita-icon-theme (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package cosmic

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

Title:
  package adwaita-icon-theme 3.30.0-0ubuntu1 failed to install/upgrade:
  unable to open '/usr/share/pkgconfig/adwaita-icon-theme.pc.dpkg-new':
  Operation not permitted

Status in adwaita-icon-theme package in Ubuntu:
  New

Bug description:
  crash on login after 18.04 -> 18.10

  ProblemType: Package
  DistroRelease: Ubuntu 18.10
  Package: adwaita-icon-theme 3.30.0-0ubuntu1
  ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12
  Uname: Linux 4.18.0-11-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13.1
  Architecture: amd64
  Date: Mon Nov 26 12:50:09 2018
  DuplicateSignature:
   package:adwaita-icon-theme:3.30.0-0ubuntu1
   Unpacking adwaita-icon-theme (3.30.0-0ubuntu1) over (3.28.0-1ubuntu1) ...
   dpkg: error processing archive 
/tmp/apt-dpkg-install-rbRQG1/72-adwaita-icon-theme_3.30.0-0ubuntu1_all.deb 
(--unpack):
unable to open '/usr/share/pkgconfig/adwaita-icon-theme.pc.dpkg-new': 
Operation not permitted
  ErrorMessage: unable to open 
'/usr/share/pkgconfig/adwaita-icon-theme.pc.dpkg-new': Operation not permitted
  PackageArchitecture: all
  Python3Details: /usr/bin/python3.6, Python 3.6.7, python3-minimal, 
3.6.7-1~18.10
  PythonDetails: /usr/bin/python2.7, Python 2.7.15+, python-minimal, 2.7.15-3
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu5
   apt  1.7.0
  SourcePackage: adwaita-icon-theme
  Title: package adwaita-icon-theme 3.30.0-0ubuntu1 failed to install/upgrade: 
unable to open '/usr/share/pkgconfig/adwaita-icon-theme.pc.dpkg-new': Operation 
not permitted
  UpgradeStatus: Upgraded to cosmic on 2018-11-26 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/adwaita-icon-theme/+bug/1805133/+subscriptions

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

[Desktop-packages] [Bug 1805135] [NEW] package emacs-el 1:25.2+1-11 failed to install/upgrade: unable to create new file '/var/lib/dpkg/info/emacs-el.list-new': Operation not permitted

[Diego Betto]

Public bug reported:

after 18.04 -> 18.10

ProblemType: Package
DistroRelease: Ubuntu 18.10
Package: emacs-el 1:25.2+1-11
ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12
Uname: Linux 4.18.0-11-generic x86_64
ApportVersion: 2.20.10-0ubuntu13.1
Architecture: amd64
Date: Mon Nov 26 12:54:53 2018
DuplicateSignature:
 package:emacs-el:1:25.2+1-11
 Unpacking emacs-el (1:25.2+1-11) ...
 dpkg: error processing archive 
/tmp/apt-dpkg-install-1pjqun/0244-emacs-el_1%3a25.2+1-11_all.deb (--unpack):
  unable to create new file '/var/lib/dpkg/info/emacs-el.list-new': Operation 
not permitted
ErrorMessage: unable to create new file '/var/lib/dpkg/info/emacs-el.list-new': 
Operation not permitted
PackageArchitecture: all
Python3Details: /usr/bin/python3.6, Python 3.6.7, python3-minimal, 3.6.7-1~18.10
PythonDetails: /usr/bin/python2.7, Python 2.7.15+, python-minimal, 2.7.15-3
RelatedPackageVersions:
 dpkg 1.19.0.5ubuntu5
 apt  1.7.0
SourcePackage: emacs
Title: package emacs-el 1:25.2+1-11 failed to install/upgrade: unable to create 
new file '/var/lib/dpkg/info/emacs-el.list-new': Operation not permitted
UpgradeStatus: Upgraded to cosmic on 2018-11-26 (0 days ago)

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


** Tags: amd64 apport-package cosmic

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

Title:
  package emacs-el 1:25.2+1-11 failed to install/upgrade: unable to
  create new file '/var/lib/dpkg/info/emacs-el.list-new': Operation not
  permitted

Status in emacs package in Ubuntu:
  New

Bug description:
  after 18.04 -> 18.10

  ProblemType: Package
  DistroRelease: Ubuntu 18.10
  Package: emacs-el 1:25.2+1-11
  ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12
  Uname: Linux 4.18.0-11-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13.1
  Architecture: amd64
  Date: Mon Nov 26 12:54:53 2018
  DuplicateSignature:
   package:emacs-el:1:25.2+1-11
   Unpacking emacs-el (1:25.2+1-11) ...
   dpkg: error processing archive 
/tmp/apt-dpkg-install-1pjqun/0244-emacs-el_1%3a25.2+1-11_all.deb (--unpack):
unable to create new file '/var/lib/dpkg/info/emacs-el.list-new': Operation 
not permitted
  ErrorMessage: unable to create new file 
'/var/lib/dpkg/info/emacs-el.list-new': Operation not permitted
  PackageArchitecture: all
  Python3Details: /usr/bin/python3.6, Python 3.6.7, python3-minimal, 
3.6.7-1~18.10
  PythonDetails: /usr/bin/python2.7, Python 2.7.15+, python-minimal, 2.7.15-3
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu5
   apt  1.7.0
  SourcePackage: emacs
  Title: package emacs-el 1:25.2+1-11 failed to install/upgrade: unable to 
create new file '/var/lib/dpkg/info/emacs-el.list-new': Operation not permitted
  UpgradeStatus: Upgraded to cosmic on 2018-11-26 (0 days ago)

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

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

[Desktop-packages] [Bug 1639300] Re: Error while loading shared libraries

[Diego Solo]

Hi, I had the same problem and couldn't find the exact solution
anywhere, so I'll post my solution here so anyone in the same situation
can solve the problem too.

Apparently, something was wrong with my Ubuntu (18.04). I installed the
OS and all the programs I use, but Inkscape would insist with the
missing libsigc-2.0.so.0 problem. First I thought it was something in
Inkscape so I let a few months pass as I didn't require Inkscape for
work. But when I check again, after several updates, the problem was
still present, so I started searching.

Long story short, some libraries where actually missing, despite all the
packages containing them where installed (so "apt install
[PACKAGE_NAME]" would say). So, the solution is to reinstall all the
packages with missing files, like libsigc-2.0.so.0 which comes with the
package libsigc++-2.0-0v5.

First, you need to know which libraries are missing. For this you can
use the command:

ldd $(which inkscape) | grep "not found"

Then you have to find out, through an internet search, which packages
that library comes with. Once you found it, you just need to reinstall
the package with the following command:

sudo apt install --reinstall [PACKAGE_NAME]

In my case I had to run the following commands:

sudo apt install --reinstall libsigc++-2.0-0v5
sudo apt install --reinstall libatkmm-1.6-1v5
sudo apt install --reinstall libpangomm-1.4-1v5
sudo apt install --reinstall libcairomm-1.0-1v5

Good luck!

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

Title:
  Error while loading shared libraries

Status in Inkscape:
  New
Status in inkscape package in Ubuntu:
  New

Bug description:
  Hi

  I can't run Inskcape 0.91
  Installation was fine :
  $ apt-cache policy inkscape
  inkscape:
Installed: 0.91-7ubuntu2
Candidate: 0.91-7ubuntu2
Version table:
   *** 0.91-7ubuntu2 500
  500 http://fr.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
  100 /var/lib/dpkg/status

  
  A library seems to be missing when launching: 

  inkscape: error while loading shared libraries: libIlmImf.so.6: cannot
  open shared object file: No such file or directory

  Running Ubuntu 16.04 xenial 
  4.4.0-45-generic #66-Ubuntu SMP Wed Oct 19 14:12:37 UTC 2016 x86_64 x86_64 
x86_64 GNU/Linux

  $ ldd $(which inkscape)
  linux-vdso.so.1 =>  (0x7ffc0e9ba000)
libgtkspell.so.0 => /usr/lib/libgtkspell.so.0 (0x7f801000)
libgtkmm-2.4.so.1 => /usr/lib/x86_64-linux-gnu/libgtkmm-2.4.so.1 
(0x7f801b598000)
libatkmm-1.6.so.1 => /usr/lib/x86_64-linux-gnu/libatkmm-1.6.so.1 
(0x7f801b34d000)
libgdkmm-2.4.so.1 => /usr/lib/x86_64-linux-gnu/libgdkmm-2.4.so.1 
(0x7f801b10)
libpangomm-1.4.so.1 => /usr/lib/x86_64-linux-gnu/libpangomm-1.4.so.1 
(0x7f801aed3000)
libgtk-x11-2.0.so.0 => /usr/lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0 
(0x7f801a887000)
libgdk-x11-2.0.so.0 => /usr/lib/x86_64-linux-gnu/libgdk-x11-2.0.so.0 
(0x7f801a5d2000)
libpangocairo-1.0.so.0 => 
/usr/lib/x86_64-linux-gnu/libpangocairo-1.0.so.0 (0x7f801a3c5000)
libgdk_pixbuf-2.0.so.0 => 
/usr/lib/x86_64-linux-gnu/libgdk_pixbuf-2.0.so.0 (0x7f801a1a2000)
libgc.so.1 => /usr/lib/x86_64-linux-gnu/libgc.so.1 (0x7f8019f31000)
libcairomm-1.0.so.1 => /usr/lib/x86_64-linux-gnu/libcairomm-1.0.so.1 
(0x7f8019d0d000)
libgiomm-2.4.so.1 => /usr/lib/x86_64-linux-gnu/libgiomm-2.4.so.1 
(0x7f8019968000)
libglibmm-2.4.so.1 => /usr/lib/x86_64-linux-gnu/libglibmm-2.4.so.1 
(0x7f80196ef000)
libgsl.so.19 => /usr/lib/x86_64-linux-gnu/libgsl.so.19 
(0x7f80192b)
libgslcblas.so.0 => /usr/lib/x86_64-linux-gnu/libgslcblas.so.0 
(0x7f8019071000)
libpng12.so.0 => /lib/x86_64-linux-gnu/libpng12.so.0 
(0x7f8018e4c000)
libxslt.so.1 => /usr/lib/x86_64-linux-gnu/libxslt.so.1 
(0x7f8018c0f000)
libxml2.so.2 => /usr/lib/x86_64-linux-gnu/libxml2.so.2 
(0x7f8018854000)
libpangoft2-1.0.so.0 => /usr/lib/x86_64-linux-gnu/libpangoft2-1.0.so.0 
(0x7f801863e000)
libpango-1.0.so.0 => /usr/lib/x86_64-linux-gnu/libpango-1.0.so.0 
(0x7f80183f2000)
libfontconfig.so.1 => /usr/lib/x86_64-linux-gnu/libfontconfig.so.1 
(0x7f80181ae000)
libsigc-2.0.so.0 => /usr/lib/x86_64-linux-gnu/libsigc-2.0.so.0 
(0x7f8017fa8000)
libz.so.1 => /lib/x86_64-linux-gnu/libz.so.1 (0x7f8017d8e000)
libgomp.so.1 => /usr/lib/x86_64-linux-gnu/libgomp.so.1 
(0x7f8017b6b000)
libpopt.so.0 => /lib/x86_64-linux-gnu/libpopt.so.0 (0x7f801795f000)
libaspell.so.15 => /usr/lib/x86_64-linux-gnu/libaspell.so.15 
(0x7f80176b5000)
libgnomevfs-2.so.0 => /usr/lib/x86_64-linux-gnu/libgnomevfs-2.so.0 
(0x7f801744b000)
libfreetype.so.6 => 

[Desktop-packages] [Bug 1798790] Re: Ubuntu 18.10 login screen never appears when using the Nvidia driver

[Diego Germán Gonzalez]

Edit the file /etc/gdm3/custom.conf it also worked for me.
If someone had tried installing lighdm you can go back to gdm by doing
sudo service lightdm stop
sudo reboot

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

Title:
  Ubuntu 18.10 login screen never appears when using the Nvidia driver

Status in gdm3 package in Ubuntu:
  Confirmed
Status in mutter package in Ubuntu:
  Confirmed

Bug description:
  https://gitlab.gnome.org/GNOME/gdm/issues/435

  ---

  The boot process hangs with the last message being "started bpfilter".
  There is unusual Network activity during that time. The light of the
  WiFi adapter is blinking a lot.

  I am not sure the problem is with the gdm3 package. As a matter of
  fact, I would remove it and let someone more experienced to set it.
  I'm afraid I might break something, though.

  The specific steps or actions you took that caused you to encounter the 
problem: 1. Boot Ubuntu 18.10 with the Nvidia proprietary drivers
  installed.

  The behavior you expected: I expected Ubuntu 18.10 to boot normally.

  The behavior you actually encountered: The computer gets stuck in a
  command-like environment with the last message being "started
  bpfilter". You can't type any commands.

  I have found that uninstalling the Nvidia proprietary drivers by going
  into recovery mode fixes the issue.

  Booting with the earlier kernel doesn't fix the issue. Installing the
  earlier v.340 driver also doesn't fix the issue.

  This (https://askubuntu.com/questions/1032639/ubuntu-18-04-stuck-in-
  boot-after-starting-gnome-display-manager-on-intel-graphic) seems
  relevant. This is where I found the "solution".

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

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

[Desktop-packages] [Bug 1798827] Re: Gnome Display Manager stop after installing Nvidia driver

[Diego Germán Gonzalez]

A temporary solution is to install lightdm before installing the nvidia driver.
sudo apt install lightdm

** Summary changed:

- Nvidia Persistence Daemon stops Ubuntu 18.10 from booting
+ Gnome Display Manager stop after installing Nvidia driver

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

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

Title:
  Gnome Display Manager stop after installing Nvidia driver

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

Bug description:
  At first boot the system boots normally, but at restart after a
  shutdown or restart the boot is frozen in the Nvidia Persistence
  Daemon message.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: nvidia-driver-390 390.87-0ubuntu1
  ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12
  Uname: Linux 4.18.0-10-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.10-0ubuntu13
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Oct 19 10:39:14 2018
  SourcePackage: nvidia-graphics-drivers-390
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1785964] Re: Unable to unlock the desktop session: systemd-logind: got pause for 13:69

[Diego Bersanetti]

This bug happened to me a number of times as well, on a fresh install of
Ubuntu 18.04.1 on a Clevo W230ST (Intel Haswell, nvidia Optimus); it
never happened after a lock screen but only after a suspend/resume; the
nvidia proprietary drivers 396 are installed but not loaded, as I am
using the Intel integrated graphics; the nouveau module is blacklisted.
I attach the relevant syslog.

** Attachment added: "logfile"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1785964/+attachment/5191335/+files/log.txt

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

Title:
  Unable to unlock the desktop session: systemd-logind: got pause for
  13:69

Status in linux package in Ubuntu:
  Incomplete
Status in xorg-server package in Ubuntu:
  Confirmed

Bug description:
  When this issue happens, you won't be able to unlock your desktop session (VT 
works fine).
  This happened twice today for me, one is after a suspend, one is just a 
screen lock. Not sure what is the trigger yet.

  Syndrome:
  On the login screen after typing the correct password, you will see a small 
circle keep spinning and that's it. I need to restart my computer to get it 
back to normal.

  
  In the syslog this error message looks fishy:
  Aug  8 10:44:57 Leggiero gnome-shell[2118]: g_array_unref: assertion 'array' 
failed

  
  This is part of the syslog fetching from a VT after a GUI unlock attempt 
(session 24 is the desktop login attempt):

  Aug  8 10:44:42 Leggiero systemd[1]: Started Session 24 of user sam.
  Aug  8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) 
systemd-logind: got resume for 226:0
  Aug  8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) AIGLX: 
Resuming AIGLX clients after VT switch
  Aug  8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) modeset(0): 
EDID vendor "AUO", prod id 4204
  Aug  8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) modeset(0): 
Printing DDC gathered Modelines:
  Aug  8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) modeset(0): 
Modeline "1366x768"x0.0   76.20  1366 1404 1426 1590  768 771 777 798 +hsync 
-vsync (47.9 kHz eP)
  Aug  8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) modeset(0): 
Modeline "1366x768"x0.0   76.20  1366 1404 1426 1988  768 771 777 798 +hsync 
-vsync (38.3 kHz e)
  Aug  8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) 
systemd-logind: got resume for 13:78
  Aug  8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) event14 - 
Dell WMI hotkeys: is tagged by udev as: Keyboard
  Aug  8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) event14 - 
Dell WMI hotkeys: device is a keyboard
  Aug  8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) 
systemd-logind: got resume for 13:66
  Aug  8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) event2  - 
Sleep Button: is tagged by udev as: Keyboard
  Aug  8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) event2  - 
Sleep Button: device is a keyboard
  Aug  8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) 
systemd-logind: got resume for 13:79
  Aug  8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) event15 - 
Integrated_Webcam_HD: Integrate: is tagged by udev as: Keyboard
  Aug  8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) event15 - 
Integrated_Webcam_HD: Integrate: device is a keyboard
  Aug  8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) 
systemd-logind: got resume for 13:68
  Aug  8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) event4  - AT 
Translated Set 2 keyboard: is tagged by udev as: Keyboard
  Aug  8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) event4  - AT 
Translated Set 2 keyboard: device is a keyboard
  Aug  8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) 
systemd-logind: got resume for 13:67
  Aug  8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) event3  - 
Power Button: is tagged by udev as: Keyboard
  Aug  8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) event3  - 
Power Button: device is a keyboard
  Aug  8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) 
systemd-logind: got resume for 13:71
  Aug  8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) event7  - 
AlpsPS/2 ALPS GlidePoint: is tagged by udev as: Touchpad
  Aug  8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) event7  - 
AlpsPS/2 ALPS GlidePoint: device is a touchpad
  Aug  8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) 
systemd-logind: got resume for 13:72
  Aug  8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) event8  - 
DELL Wireless hotkeys: is tagged by udev as: Keyboard
  Aug  8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) event8  - 
DELL Wireless hotkeys: device is a keyboard
  Aug  8 10:44:55 Leggiero 

[Desktop-packages] [Bug 1790951] Re: Black vertical line on Right Side of the Screen

[Diego Vega]

** Attachment added: "Here is a picture of how it looks"
   
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1790951/+attachment/5185999/+files/40590806_967724336769508_8188974634431938560_n.jpg

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

Title:
  Black vertical line on Right Side of the Screen

Status in xorg package in Ubuntu:
  New

Bug description:
  The OS appears to not recognize the monitors size and no mater if I
  select the native resolution, the black line still there. I've notice
  also that there are 2 display options, LVDS and VGA, but the problem
  is that the VGA doesn't exist, only the LVDS. I've already done the
  xrandr commands, and added the resolutions witch fitted better to the
  machine, but my guess is that it is not the resolution, it is a
  miscommunication between the OS and the hardware.

  Please help, I'm a linux user with less experience, but I like it a
  lot and I wish to stay in Ubuntu(even with that black line, but it
  would be better to not).

  Thanks for your awesome work

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18
  Uname: Linux 4.15.0-33-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Sep  5 14:57:14 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation 4 Series Chipset Integrated Graphics Controller 
[8086:2e22] (rev 03) (prog-if 00 [VGA controller])
 Subsystem: Sony Corporation 4 Series Chipset Integrated Graphics 
Controller [104d:9044]
 Subsystem: Sony Corporation 4 Series Chipset Integrated Graphics 
Controller [104d:9044]
  InstallationDate: Installed on 2018-08-31 (4 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: Sony Corporation VGC-JS160J
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-33-generic 
root=UUID=d74eae8d-b73a-4fd9-ac75-8f3ea6bed617 ro quiet splash vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/29/2008
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: R0201T4
  dmi.board.asset.tag: N/A
  dmi.board.name: VAIO
  dmi.board.vendor: Sony Corporation
  dmi.board.version: N/A
  dmi.chassis.asset.tag: N/A
  dmi.chassis.type: 13
  dmi.chassis.vendor: Sony Corporation
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrR0201T4:bd08/29/2008:svnSonyCorporation:pnVGC-JS160J:pvrC6U09RL6:rvnSonyCorporation:rnVAIO:rvrN/A:cvnSonyCorporation:ct13:cvrN/A:
  dmi.product.family: N/A
  dmi.product.name: VGC-JS160J
  dmi.product.version: C6U09RL6
  dmi.sys.vendor: Sony Corporation
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.91-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4
  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/1790951/+subscriptions

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

[Diego]

Same problem with Lenovo Legion Y520.
Intel HD 640 / Nvidia GTX 1050 Ti

-- 
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 1714659] Re: HPLIP is not compatible with modern GNOME (No system tray detected on this system. Unable to start, exiting.)

[Diego A . Zapata Häntsch]

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

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

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

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

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

  Expected results:
  hp-systray is compatible with modern GNOME

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

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

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

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

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

[Diego Germán Gonzalez]

** Tags added: images in list mailing

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

Title:
  Very large emojis displayed in subject line and in the email list

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

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

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

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

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

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

[Diego Germán Gonzalez]

** Tags added: emoji thunderbird

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

Title:
  Very large emojis displayed in subject line and in the email list

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

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

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

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

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

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

[Diego Germán Gonzalez]

In my case the problem was using the configuration folder of a later version, 
downloaded from the Thunderbird website in the default version included in 
Ubuntu.
Setting from scratch does not present the problem.
I don't invalidate the bug because there are other reports

-- 
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 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/ubuntu/+source/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 1765336] Re: Problems configuring LivePatch from Gnome Initial Setup

[Diego Germán Gonzalez]

** Changed in: gnome-initial-setup (Ubuntu)
   Status: New => Fix Released

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

Title:
  Problems configuring LivePatch from  Gnome Initial Setup

Status in gnome-initial-setup package in Ubuntu:
  Fix Released

Bug description:
  Entering the user and password in GNOME Initial Setup to configure LivePatch 
closes the window. The wizard does not show any information that the 
configuration was successful or that there is a problem.
  If you do this when you enter the wrong password

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-initial-setup 3.28.0-2ubuntu3
  ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15
  Uname: Linux 4.15.0-15-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu5
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Apr 19 05:26:12 2018
  InstallationDate: Installed on 2018-04-11 (8 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180409)
  SourcePackage: gnome-initial-setup
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1765336] [NEW] Problems configuring LivePatch from Gnome Initial Setup

[Diego Germán Gonzalez]

Public bug reported:

Entering the user and password in GNOME Initial Setup to configure LivePatch 
closes the window. The wizard does not show any information that the 
configuration was successful or that there is a problem.
If you do this when you enter the wrong password

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: gnome-initial-setup 3.28.0-2ubuntu3
ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15
Uname: Linux 4.15.0-15-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.9-0ubuntu5
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Thu Apr 19 05:26:12 2018
InstallationDate: Installed on 2018-04-11 (8 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180409)
SourcePackage: gnome-initial-setup
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: gnome-initial-setup (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 gnome-initial-setup in Ubuntu.
https://bugs.launchpad.net/bugs/1765336

Title:
  Problems configuring LivePatch from  Gnome Initial Setup

Status in gnome-initial-setup package in Ubuntu:
  New

Bug description:
  Entering the user and password in GNOME Initial Setup to configure LivePatch 
closes the window. The wizard does not show any information that the 
configuration was successful or that there is a problem.
  If you do this when you enter the wrong password

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-initial-setup 3.28.0-2ubuntu3
  ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15
  Uname: Linux 4.15.0-15-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu5
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Apr 19 05:26:12 2018
  InstallationDate: Installed on 2018-04-11 (8 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180409)
  SourcePackage: gnome-initial-setup
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1763996] Re: Screen dims when wireless device has low battery

[Diego Leal]

** Summary changed:

- Screen dims when wireless devices have low battery levels
+ Screen dims when wireless device has low battery

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

Title:
  Screen dims when wireless device has low battery

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

Bug description:
  I have noticed this happening on my Thinkpad x230, but I have also
  seen this in other laptops.

  The laptop with adequate (above 40%) battery charge suddenly dims the
  screen after displaying a notification about my logitech performance
  mx having low battery.

  I expect the battery levels on my wireless peripherals having no
  effect over my laptop's power settings.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-settings-daemon 3.28.0-0ubuntu2
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  Uname: Linux 4.15.0-13-generic x86_64
  ApportVersion: 2.20.9-0ubuntu4
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Apr 14 20:15:55 2018
  InstallationDate: Installed on 2018-04-08 (6 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Beta amd64 (20180404)
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-settings-daemon
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1763996] [NEW] Screen dims when wireless devices have low battery levels

[Diego Leal]

Public bug reported:

I have noticed this happening on my Thinkpad x230, but I have also seen
this in other laptops.

The laptop with adequate (above 40%) battery charge suddenly dims the
screen after displaying a notification about my logitech performance mx
having low battery.

I expect the battery levels on my wireless peripherals having no effect
over my laptop's power settings.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: gnome-settings-daemon 3.28.0-0ubuntu2
ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
Uname: Linux 4.15.0-13-generic x86_64
ApportVersion: 2.20.9-0ubuntu4
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Sat Apr 14 20:15:55 2018
InstallationDate: Installed on 2018-04-08 (6 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Beta amd64 (20180404)
ProcEnviron:
 LANGUAGE=en_GB:en
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_GB.UTF-8
 SHELL=/bin/bash
SourcePackage: gnome-settings-daemon
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: gnome-settings-daemon (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 gnome-settings-daemon in Ubuntu.
https://bugs.launchpad.net/bugs/1763996

Title:
  Screen dims when wireless devices have low battery levels

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

Bug description:
  I have noticed this happening on my Thinkpad x230, but I have also
  seen this in other laptops.

  The laptop with adequate (above 40%) battery charge suddenly dims the
  screen after displaying a notification about my logitech performance
  mx having low battery.

  I expect the battery levels on my wireless peripherals having no
  effect over my laptop's power settings.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-settings-daemon 3.28.0-0ubuntu2
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  Uname: Linux 4.15.0-13-generic x86_64
  ApportVersion: 2.20.9-0ubuntu4
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Apr 14 20:15:55 2018
  InstallationDate: Installed on 2018-04-08 (6 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Beta amd64 (20180404)
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-settings-daemon
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Diego Germán Gonzalez]

-- 
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 thunderbird package in Ubuntu:
  New

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/ubuntu/+source/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 1761844] [NEW] Thunderbird: emojis is displayed in the email list

[Diego Germán Gonzalez]

Public bug reported:

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.

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


** Tags: amd64 apport-bug bionic

** Attachment added: "Untitled.png"
   
https://bugs.launchpad.net/bugs/1761844/+attachment/5104553/+files/Untitled.png

-- 
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 thunderbird package in Ubuntu:
  New

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

[Desktop-packages] [Bug 1760721] [NEW] Resolution is stuck at 640x480

[Diego Angel Osuna Carrasco]

Public bug reported:

This is a fresh install of Xubuntu 17.10. The OS is stuck at 640x480 
resolution, this happened since the first boot. I researched and found in 
forums that xdiagnose provides a workaround by deactivating some graphics at 
boot, so I installed it and it worked, however, just as a workaround. I can 
change the resolution now, but the size of apps sometimes takes way more screen 
space than it should, and the screen flickers randomly. By selecting "inform 
errors" in xdiagnose I got a pop up message saying the computer is providing 3D 
by software instead of hardware, I don't know how to fix this, any guidance?
Let me know if you need more information.

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: xorg 1:7.7+19ubuntu3
ProcVersionSignature: Ubuntu 4.13.0-21.24-generic 4.13.13
Uname: Linux 4.13.0-21-generic i686
ApportVersion: 2.20.7-0ubuntu3.7
Architecture: i386
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
Date: Mon Apr  2 16:30:13 2018
DistUpgraded: Fresh install
DistroCodename: artful
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 Silicon Integrated Systems [SiS] 661/741/760 PCI/AGP or 662/761Gx PCIE VGA 
Display Adapter [1039:6330] (prog-if 00 [VGA controller])
   Subsystem: Acer Incorporated [ALI] 661/741/760 PCI/AGP or 662/761Gx PCIE VGA 
Display Adapter [1025:0083]
InstallationDate: Installed on 2018-04-02 (0 days ago)
InstallationMedia: Xubuntu 17.10 "Artful Aardvark" - Release i386 (20180105)
Lsusb:
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
 Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
 Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
MachineType: Acer, inc. Aspire 3000
PccardctlIdent:
 Socket 0:
   no product info available
PccardctlStatus:
 Socket 0:
   no card
ProcEnviron:
 LANGUAGE=es_MX:es
 PATH=(custom, no user)
 LANG=es_MX.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-21-generic 
root=UUID=a37feeb6-1e6a-47c6-b003-a161b5612912 ro quiet splash vt.handoff=7
Renderer: Software
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 02/20/06
dmi.bios.vendor: Acer
dmi.bios.version: 3A32
dmi.board.name: Lugano M
dmi.board.vendor: Acer, Inc.
dmi.board.version: Not Applicable
dmi.chassis.type: 1
dmi.chassis.vendor: , Inc.
dmi.chassis.version: N/A
dmi.modalias: 
dmi:bvnAcer:bvr3A32:bd02/20/06:svnAcer,inc.:pnAspire3000:pvrNotApplicable:rvnAcer,Inc.:rnLuganoM:rvrNotApplicable:cvn,Inc.:ct1:cvrN/A:
dmi.product.name: Aspire 3000
dmi.product.version: Not Applicable
dmi.sys.vendor: Acer, inc.
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.83-1
version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.8-0ubuntu0~17.10.1
version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.8-0ubuntu0~17.10.1
version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20170309-0ubuntu1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2
xserver.bootTime: Mon Apr  2 16:18:06 2018
xserver.configfile: default
xserver.devices:
 inputPower Button KEYBOARD, id 6
 inputPower Button KEYBOARD, id 7
 inputSleep Button KEYBOARD, id 8
 inputAT Translated Set 2 keyboard KEYBOARD, id 9
 inputSynPS/2 Synaptics TouchPad TOUCHPAD, id 10
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 
xserver.version: 2:1.19.5-0ubuntu2

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


** Tags: apport-bug artful i386 ubuntu

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

Title:
  Resolution is stuck at 640x480

Status in xorg package in Ubuntu:
  New

Bug description:
  This is a fresh install of Xubuntu 17.10. The OS is stuck at 640x480 
resolution, this happened since the first boot. I researched and found in 
forums that xdiagnose provides a workaround by deactivating some graphics at 
boot, so I installed it and it worked, however, just as a workaround. I can 
change the resolution now, but the size of apps sometimes takes way more screen 
space than it should, and the screen flickers randomly. By selecting "inform 
errors" in xdiagnose I got a pop up message saying the computer is providing 3D 
by software instead of hardware, I don't know how to fix this, any guidance?
  Let me know if you need more information.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: xorg 1:7.7+19ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-21.24-generic 4.13.13
  Uname: Linux 4.13.0-21-generic i686
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: i386
  CompizPlugins: No value set 

[Desktop-packages] [Bug 1755277] [NEW] Fail start x

[diego ezequiel]

Public bug reported:

No desktop visual start. After sleep partial funcionality with errors.
Sorry.

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: xorg 1:7.7+19ubuntu3
ProcVersionSignature: Ubuntu 4.13.0-36.40-generic 4.13.13
Uname: Linux 4.13.0-36-generic i686
ApportVersion: 2.20.7-0ubuntu3.7
Architecture: i386
CompositorRunning: None
Date: Mon Mar 12 17:01:51 2018
DistUpgraded: Fresh install
DistroCodename: artful
DistroVariant: ubuntu
GraphicsCard:
 Intel Corporation Mobile 945GM/GMS, 943/940GML Express Integrated Graphics 
Controller [8086:27a2] (rev 03) (prog-if 00 [VGA controller])
   Subsystem: Lenovo ThinkPad R60/T60/X60 series [17aa:201a]
   Subsystem: Lenovo ThinkPad R60/T60/X60 series [17aa:201a]
InstallationDate: Installed on 2018-03-11 (0 days ago)
InstallationMedia: Ubuntu-Budgie 17.10 "Artful Aardvark" - Release i386 
(20180106)
MachineType: LENOVO 1952AP6
PccardctlIdent:
 Socket 0:
   no product info available
PccardctlStatus:
 Socket 0:
   no card
ProcEnviron:
 LANGUAGE=es_AR:es
 PATH=(custom, no user)
 LANG=es_AR.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-36-generic 
root=UUID=dc47c574-ff68-42ce-a683-ac420cedf1bd ro quiet splash vt.handoff=7
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 12/22/2006
dmi.bios.vendor: LENOVO
dmi.bios.version: 79ETC9WW (2.09 )
dmi.board.name: 1952AP6
dmi.board.vendor: LENOVO
dmi.board.version: Not Available
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Not Available
dmi.modalias: 
dmi:bvnLENOVO:bvr79ETC9WW(2.09):bd12/22/2006:svnLENOVO:pn1952AP6:pvrThinkPadT60:rvnLENOVO:rn1952AP6:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
dmi.product.family: ThinkPad T60
dmi.product.name: 1952AP6
dmi.product.version: ThinkPad T60
dmi.sys.vendor: LENOVO
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.83-1
version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.8-0ubuntu0~17.10.1
version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.8-0ubuntu0~17.10.1
version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20170309-0ubuntu1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2
xserver.bootTime: Mon Mar 12 16:47:07 2018
xserver.configfile: default
xserver.errors:
 event5  - (EE) SynPS/2 Synaptics TouchPad: (EE) kernel bug: Touch jump 
detected and discarded.
 event5  - (EE) SynPS/2 Synaptics TouchPad: (EE) kernel bug: Touch jump 
detected and discarded.
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 product id   16448 
 vendor LEN
xserver.version: 2:1.19.5-0ubuntu2

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


** Tags: apport-bug artful i386 ubuntu

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

Title:
  Fail start x

Status in xorg package in Ubuntu:
  New

Bug description:
  No desktop visual start. After sleep partial funcionality with errors.
  Sorry.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: xorg 1:7.7+19ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-36.40-generic 4.13.13
  Uname: Linux 4.13.0-36-generic i686
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: i386
  CompositorRunning: None
  Date: Mon Mar 12 17:01:51 2018
  DistUpgraded: Fresh install
  DistroCodename: artful
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation Mobile 945GM/GMS, 943/940GML Express Integrated Graphics 
Controller [8086:27a2] (rev 03) (prog-if 00 [VGA controller])
 Subsystem: Lenovo ThinkPad R60/T60/X60 series [17aa:201a]
 Subsystem: Lenovo ThinkPad R60/T60/X60 series [17aa:201a]
  InstallationDate: Installed on 2018-03-11 (0 days ago)
  InstallationMedia: Ubuntu-Budgie 17.10 "Artful Aardvark" - Release i386 
(20180106)
  MachineType: LENOVO 1952AP6
  PccardctlIdent:
   Socket 0:
 no product info available
  PccardctlStatus:
   Socket 0:
 no card
  ProcEnviron:
   LANGUAGE=es_AR:es
   PATH=(custom, no user)
   LANG=es_AR.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-36-generic 
root=UUID=dc47c574-ff68-42ce-a683-ac420cedf1bd ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/22/2006
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 79ETC9WW (2.09 )
  dmi.board.name: 1952AP6
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Available
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 

[Desktop-packages] [Bug 1568560] Re: nm_device_get_device_type: assertion 'NM_IS_DEVICE (self)' failed

[Diego Diniz L. de Oliveira]

Guys...I got this problem solved by running these commands...

Install WICD to manage the network

sudo apt-get install wicd-gtk

Stop and disable Network-Manager

sudo systemctl stop NetworkManager.service
sudo systemctl disable NetworkManager.service

and uninstall avahi-autoipd and isc-dhcp-client using synaptic

But now I'm having two problems, one, system setting is not working
'cause NetworkManager is disabled, two wicd sets a random ip even it's
configured as static so when I turn on the system or restart it, I have
to disconnect and connect again to wicd recognize the righ ip.

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

Title:
  nm_device_get_device_type: assertion 'NM_IS_DEVICE (self)' failed

Status in NetworkManager:
  New
Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  Hello,
  On Ubuntu 15.10 4.2.0-35, with network-manager 1.0.4-0ubuntu5.3
  My WiFi connection is very unstable and I have to  often restart 
NetworkManager service (~ a dozen times every day...):

  sudo systemctl -l status NetworkManager
  ● NetworkManager.service - Network Manager
 Loaded: loaded (/lib/systemd/system/NetworkManager.service; enabled; 
vendor preset: enabled)
 Active: active (running) since dim. 2016-04-10 18:17:07 CEST; 2min 58s ago
   Main PID: 27832 (NetworkManager)
 Memory: 13.8M
CPU: 1.729s
 CGroup: /system.slice/NetworkManager.service
 ├─ 2703 /usr/sbin/dnsmasq --no-resolv --keep-in-foreground 
--no-hosts --bind-interfaces 
--pid-file=/run/sendsigs.omit.d/network-manager.dnsmasq.pid 
--listen-address=127.0.1.1 --conf-file=/var/run/NetworkManager/dnsmasq.conf 
--cache-size=0 --proxy-dnssec 
--enable-dbus=org.freedesktop.NetworkManager.dnsmasq 
--conf-dir=/etc/NetworkManager/dnsmasq.d
 ├─27832 /usr/sbin/NetworkManager --no-daemon
 └─30448 /sbin/dhclient -d -q -sf 
/usr/lib/NetworkManager/nm-dhcp-helper -pf 
/run/sendsigs.omit.d/network-manager.dhclient-wlan0.pid -lf 
/var/lib/NetworkManager/dhclient-7ec429cb-9dde-4ea4-8eda-f259b66e38a7-wlan0.lease
 -cf /var/lib/NetworkManager/dhclient-wlan0.conf wlan0

  avril 10 18:17:08 samsung-ubuntu NetworkManager[27832]:   keyfile: add 
connection in-memory (068de9b1-513a-46f0-b4be-93462d19f68b,"lxcbr0")
  avril 10 18:17:08 samsung-ubuntu NetworkManager[27832]:   (lxcbr0): 
device state change: unmanaged -> unavailable (reason 'connection-assumed') [10 
20 41]
  avril 10 18:17:08 samsung-ubuntu NetworkManager[27832]:   (lxcbr0): 
device state change: unavailable -> disconnected (reason 'connection-assumed') 
[20 30 41]
  avril 10 18:17:08 samsung-ubuntu NetworkManager[27832]:   (lxcbr0): 
Activation: starting connection 'lxcbr0' (068de9b1-513a-46f0-b4be-93462d19f68b)
  avril 10 18:17:08 samsung-ubuntu NetworkManager[27832]:   (virbr1-nic): 
new Tun device (carrier: OFF, driver: 'tun', ifindex: 34)
  avril 10 18:17:08 samsung-ubuntu NetworkManager[27832]:   (virbr1): 
bridge port virbr1-nic was attached
  avril 10 18:17:08 samsung-ubuntu NetworkManager[27832]:   (virbr1-nic): 
enslaved to virbr1
  avril 10 18:17:08 samsung-ubuntu NetworkManager[27832]:   (virbr0): new 
Bridge device (carrier: OFF, driver: 'bridge', ifindex: 29)
  avril 10 18:17:08 samsung-ubuntu NetworkManager[27832]: 
nm_device_get_device_type: assertion 'NM_IS_DEVICE (self)' failed
  avril 10 18:17:08 samsung-ubuntu NetworkManager[27832]:   failed to 
enumerate oFono devices: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: 
The name org.ofono was not provided by any .service files

  Also, each time I restart my desktop, NetworkManager generates a crash 
report: cf. attached screenshots.
  I have tried an Ubuntu VM with the same packages related to networking and 
the exact same releases (same repositories), the crash never happens; the 
difference appears to be only the type of network connection: WiFi for the 
desktop vs Ethernet for the VM.

  Any suggestion?

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

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

[Desktop-packages] [Bug 1684678] Re: NVIDIA Driver Crashes the System

[Diego Souza]

I have a Dell Vostro 5470 with GeForce GT 740M and driver version
375.66. The bug is applied to me too, in the kernel versions
4.4.0-96-generic and 4.4.0-97-generic.

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

Title:
  NVIDIA Driver Crashes the System

Status in bbswitch package in Ubuntu:
  Confirmed

Bug description:
  When I install the proprietary driver from NVIDIA the system doesn't
  log on.In return it repeatedly shows the error.

  bbswitch:No suitable _dsm call found

  
  Driver shown Additional Drivers Page:

  Using NVIDIA binary driver-version 375.29 from
  nvidia-375(proprietary,tested).

  The NVIDIA Driver was working fine in Ubuntu 16.10 in my laptop. 
  When I upgraded to Ubuntu 17.04 I got this error. So I completely removed 
that and made a clean installation of Ubuntu 17.04 but still I got the error.
   
  My Laptop Specs:

  OS:Ubuntu 17.04

  Processor:i5-5200u

  Graphics: NVIDIA 920M 2GB

  RAM: 8GB

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

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

[Desktop-packages] [Bug 1568560] Re: nm_device_get_device_type: assertion 'NM_IS_DEVICE (self)' failed

[Diego Diniz L. de Oliveira]

$ sudo journalctl -b -p err
-- Logs begin at Sex 2017-09-29 07:50:42 BRT, end at Sex 2017-09-29 07:58:58 
BRT. --
Set 29 07:51:03 DTI05 NetworkManager[907]: nm_device_get_device_type: assertion 
'NM_IS_DEVICE (self)' failed

Same error. My computer has no wireless card connected. I've tried a lot
of things (changed network card for a new one, changed to a different
distribution). Maybe is a hardware (motherboard) problem.

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

Title:
  nm_device_get_device_type: assertion 'NM_IS_DEVICE (self)' failed

Status in NetworkManager:
  New
Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  Hello,
  On Ubuntu 15.10 4.2.0-35, with network-manager 1.0.4-0ubuntu5.3
  My WiFi connection is very unstable and I have to  often restart 
NetworkManager service (~ a dozen times every day...):

  sudo systemctl -l status NetworkManager
  ● NetworkManager.service - Network Manager
 Loaded: loaded (/lib/systemd/system/NetworkManager.service; enabled; 
vendor preset: enabled)
 Active: active (running) since dim. 2016-04-10 18:17:07 CEST; 2min 58s ago
   Main PID: 27832 (NetworkManager)
 Memory: 13.8M
CPU: 1.729s
 CGroup: /system.slice/NetworkManager.service
 ├─ 2703 /usr/sbin/dnsmasq --no-resolv --keep-in-foreground 
--no-hosts --bind-interfaces 
--pid-file=/run/sendsigs.omit.d/network-manager.dnsmasq.pid 
--listen-address=127.0.1.1 --conf-file=/var/run/NetworkManager/dnsmasq.conf 
--cache-size=0 --proxy-dnssec 
--enable-dbus=org.freedesktop.NetworkManager.dnsmasq 
--conf-dir=/etc/NetworkManager/dnsmasq.d
 ├─27832 /usr/sbin/NetworkManager --no-daemon
 └─30448 /sbin/dhclient -d -q -sf 
/usr/lib/NetworkManager/nm-dhcp-helper -pf 
/run/sendsigs.omit.d/network-manager.dhclient-wlan0.pid -lf 
/var/lib/NetworkManager/dhclient-7ec429cb-9dde-4ea4-8eda-f259b66e38a7-wlan0.lease
 -cf /var/lib/NetworkManager/dhclient-wlan0.conf wlan0

  avril 10 18:17:08 samsung-ubuntu NetworkManager[27832]:   keyfile: add 
connection in-memory (068de9b1-513a-46f0-b4be-93462d19f68b,"lxcbr0")
  avril 10 18:17:08 samsung-ubuntu NetworkManager[27832]:   (lxcbr0): 
device state change: unmanaged -> unavailable (reason 'connection-assumed') [10 
20 41]
  avril 10 18:17:08 samsung-ubuntu NetworkManager[27832]:   (lxcbr0): 
device state change: unavailable -> disconnected (reason 'connection-assumed') 
[20 30 41]
  avril 10 18:17:08 samsung-ubuntu NetworkManager[27832]:   (lxcbr0): 
Activation: starting connection 'lxcbr0' (068de9b1-513a-46f0-b4be-93462d19f68b)
  avril 10 18:17:08 samsung-ubuntu NetworkManager[27832]:   (virbr1-nic): 
new Tun device (carrier: OFF, driver: 'tun', ifindex: 34)
  avril 10 18:17:08 samsung-ubuntu NetworkManager[27832]:   (virbr1): 
bridge port virbr1-nic was attached
  avril 10 18:17:08 samsung-ubuntu NetworkManager[27832]:   (virbr1-nic): 
enslaved to virbr1
  avril 10 18:17:08 samsung-ubuntu NetworkManager[27832]:   (virbr0): new 
Bridge device (carrier: OFF, driver: 'bridge', ifindex: 29)
  avril 10 18:17:08 samsung-ubuntu NetworkManager[27832]: 
nm_device_get_device_type: assertion 'NM_IS_DEVICE (self)' failed
  avril 10 18:17:08 samsung-ubuntu NetworkManager[27832]:   failed to 
enumerate oFono devices: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: 
The name org.ofono was not provided by any .service files

  Also, each time I restart my desktop, NetworkManager generates a crash 
report: cf. attached screenshots.
  I have tried an Ubuntu VM with the same packages related to networking and 
the exact same releases (same repositories), the crash never happens; the 
difference appears to be only the type of network connection: WiFi for the 
desktop vs Ethernet for the VM.

  Any suggestion?

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

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

[Desktop-packages] [Bug 1700104] [NEW] package pcscd 1.8.10-1ubuntu1.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

[Diego Laverson Freitas]

Public bug reported:

.

ProblemType: Package
DistroRelease: Ubuntu 14.04
Package: pcscd 1.8.10-1ubuntu1.1
ProcVersionSignature: Ubuntu 4.4.0-81.104~14.04.1-generic 4.4.67
Uname: Linux 4.4.0-81-generic x86_64
ApportVersion: 2.14.1-0ubuntu3.24
AptOrdering:
 pcscd: Install
 pcscd: Configure
Architecture: amd64
Date: Fri Jun 23 12:21:31 2017
DuplicateSignature: package:pcscd:1.8.10-1ubuntu1.1:subprocess installed 
post-installation script returned error exit status 1
ErrorMessage: subprocess installed post-installation script returned error exit 
status 1
InstallationDate: Installed on 2016-12-28 (177 days ago)
InstallationMedia: Ubuntu 14.04.5 LTS "Trusty Tahr" - Release amd64 (20160803)
RelatedPackageVersions:
 dpkg 1.17.5ubuntu5.7
 apt  1.0.1ubuntu2.17
SourcePackage: pcsc-lite
Title: package pcscd 1.8.10-1ubuntu1.1 failed to install/upgrade: subprocess 
installed post-installation script returned error exit status 1
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: pcsc-lite (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package trusty

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

Title:
  package pcscd 1.8.10-1ubuntu1.1 failed to install/upgrade: subprocess
  installed post-installation script returned error exit status 1

Status in pcsc-lite package in Ubuntu:
  New

Bug description:
  .

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: pcscd 1.8.10-1ubuntu1.1
  ProcVersionSignature: Ubuntu 4.4.0-81.104~14.04.1-generic 4.4.67
  Uname: Linux 4.4.0-81-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.24
  AptOrdering:
   pcscd: Install
   pcscd: Configure
  Architecture: amd64
  Date: Fri Jun 23 12:21:31 2017
  DuplicateSignature: package:pcscd:1.8.10-1ubuntu1.1:subprocess installed 
post-installation script returned error exit status 1
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  InstallationDate: Installed on 2016-12-28 (177 days ago)
  InstallationMedia: Ubuntu 14.04.5 LTS "Trusty Tahr" - Release amd64 (20160803)
  RelatedPackageVersions:
   dpkg 1.17.5ubuntu5.7
   apt  1.0.1ubuntu2.17
  SourcePackage: pcsc-lite
  Title: package pcscd 1.8.10-1ubuntu1.1 failed to install/upgrade: subprocess 
installed post-installation script returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1699557] [NEW] Evolution: send inline images as attachments

[Diego Chaparro]

Public bug reported:

Since I upgraded from Ubuntu 16 to Ubuntu 17, evolution has stopped
working when sending HTML messages with inline images, copy/paste an
image inside the body not as attachment. Previous to the update, the
images were sent and received inside the HTML body and displayed
correctly in the email content. Since I upgraded, the images are
received as attachments and they aren't displayed inside the HTML
message content.

The problem seems to be on the HTML sent, because I've tested to receive
the messages in different email clients (Evolution and Outlook) and all
of them receives the email images in the same way, as attachments, not
inside the HTML content.

Ubuntu release: 17.04
Evolution version: 3.22.6-1ubuntu1

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

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

Title:
  Evolution: send inline images as attachments

Status in evolution package in Ubuntu:
  New

Bug description:
  Since I upgraded from Ubuntu 16 to Ubuntu 17, evolution has stopped
  working when sending HTML messages with inline images, copy/paste an
  image inside the body not as attachment. Previous to the update, the
  images were sent and received inside the HTML body and displayed
  correctly in the email content. Since I upgraded, the images are
  received as attachments and they aren't displayed inside the HTML
  message content.

  The problem seems to be on the HTML sent, because I've tested to
  receive the messages in different email clients (Evolution and
  Outlook) and all of them receives the email images in the same way, as
  attachments, not inside the HTML content.

  Ubuntu release: 17.04
  Evolution version: 3.22.6-1ubuntu1

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

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

[Desktop-packages] [Bug 1011446] Re: UML drawing tools' comment fields are too small to be usable

[Diego González]

Same issue also confirmed on Ubuntu 16.04 LTS and 16.10.

The cleaner workaround I've achieved is to create a custom desktop entry with 
different file and app name (Name=Dia-X or whatever) on your 
"~/.local/share/applications/", adding "Exec=env LIBOVERLAY_SCROLLBAR=0 dia %F"
as mobidyc pointed.

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

Title:
  UML drawing tools' comment fields are too small to be usable

Status in dia package in Ubuntu:
  Confirmed

Bug description:
  Start dia, pull up the UML diagram items, create a class. Note that
  the comment on the main class window is a bit short - it's still
  usable, but it's definately short.

  The comment field on the attributes tab is 1-3 pixels tall. Same for
  both comment-fields in the Operations tab.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: dia-gnome 0.97.2-5
  ProcVersionSignature: Ubuntu 3.2.0-24.39-generic 3.2.16
  Uname: Linux 3.2.0-24-generic x86_64
  NonfreeKernelModules: fglrx
  ApportVersion: 2.0.1-0ubuntu8
  Architecture: amd64
  Date: Mon Jun 11 00:55:08 2012
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 
(20120425)
  ProcEnviron:
   LANGUAGE=en_US:en
   TERM=xterm
   PATH=(custom, user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: dia
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1638842] Re: network-manager does not manage ethernet and bluetooth interfaces when Ubuntu 16.10 is installed using chroot/netboot method

[Diego]

Same problem here, as stated in
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1658921

Five computers (2 laptops and 3 desktops), upgraded from 16.04. No
chroot. Comment #6 did the trick.

I can't believe this is tagged as "won't fix"

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

Title:
  network-manager does not manage ethernet and bluetooth interfaces when
  Ubuntu 16.10 is installed using chroot/netboot method

Status in network-manager package in Ubuntu:
  Won't Fix

Bug description:
  Hello,

  I installed Ubuntu 16.10 using a chroot. I use network-manager to
  manage connections. My system is up-to-date (so I use network-manager
  1.2.4-0ubuntu1).

  Wifi works perfectly but I cannot connect to wired networks and using
  my phone's Bluetooth connection. Corresponding devices are said to be
  unmanaged by network-manager. nmcli dev outputs:

  DEVICETYPE  STATE CONNECTION 
  enp1s0ethernet  unmanaged -- 
  wlp2s0wifi  disconnected  --
  6C:9B:02:2C:EE:2C btunmanaged -- 
  hfp/org/bluez/hci0/dev_6C_9B_02_2C_EE_2C  gsm   unmanaged -- 
  loloopback  unmanaged -- 

  The following command has no effect:
  sudo nmcli dev set enp1s0 managed yes

  I can connect to a wired connection by doing:
  ifconfig enp1s0 up
  dhclient enp1s0

  There is nothing in the file /etc/network/interfaces.

  Everything works perfectly if I downgrade network-manager to this
  version: network-manager_1.2.2-0ubuntu0.16.04.3_amd64.deb
  (http://packages.ubuntu.com/xenial-updates/amd64/network-
  manager/download). I had to install libreadline6 and downgrade nplan
  to meet dependencies.

  I don't know what to join to this bug report so please ask in case
  anything is needed.

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

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

[Desktop-packages] [Bug 1658921] Re: NetworkManager does not manage wired connection

[Diego]

Ok, just kept on reading bug report 1638842. There's no need to remove
the file, just create an empty one

sudo touch /etc/NetworkManager/conf.d/10-globally-managed-devices.conf

and restart NetworkManager

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

Title:
  NetworkManager does not manage wired connection

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  NetworkManager does not manage my wired eth0 connection, no matter how
  I set /etc/network/interfaces or
  /etc/NetworkManager/NetworkManager.conf

  Using ubuntu 16.04, /etc/network/interfaces only managed lo, and
  [ifupdown] section of NetworkManager.conf had set managed=false.

  With these same settings, after upgrading to ubuntu 16.10, eth0
  appears as unmanaged in nm-applet.

  If I modify /etc/network/interfaces and add

  auto eth0
  iface eth0 inet dhcp

  And set managed=true in NetworkManager.conf [ifupdown] section, eth0
  is still unmanaged despite it does get an IP from DHCP server.

  This is happening in my five computers (two laptops and three
  desktops).

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

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

[Desktop-packages] [Bug 1658921] Re: NetworkManager does not manage wired connection

[Diego]

After pulling my hair for several days, I found this:

https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1638842

/usr/lib/NetworkManager/conf.d/10-globally-managed-devices.conf has the
following content:

[keyfile]
unmanaged-devices=*,except:type:wifi,except:type:wwan

Removing the file and restarting NetworkManager did the trick.

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

Title:
  NetworkManager does not manage wired connection

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  NetworkManager does not manage my wired eth0 connection, no matter how
  I set /etc/network/interfaces or
  /etc/NetworkManager/NetworkManager.conf

  Using ubuntu 16.04, /etc/network/interfaces only managed lo, and
  [ifupdown] section of NetworkManager.conf had set managed=false.

  With these same settings, after upgrading to ubuntu 16.10, eth0
  appears as unmanaged in nm-applet.

  If I modify /etc/network/interfaces and add

  auto eth0
  iface eth0 inet dhcp

  And set managed=true in NetworkManager.conf [ifupdown] section, eth0
  is still unmanaged despite it does get an IP from DHCP server.

  This is happening in my five computers (two laptops and three
  desktops).

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

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

[Desktop-packages] [Bug 1589401] Re: cannot view wifi networks after re-enabling wifi

[Diego Liedo]

I too have this bug on a Lenovo W520 with Ubuntu 16.04 kernel 4.4.0-62-generic
The only solution that has worked is restarting the network-manager service, 
however if I attach an USB WiFi adapter based on rtl8187, the icon becomes 
normal and I can choose a network for that adapter. The Intel Centrino 
Advanced-N 6205 remains unusable.
Also the interface name is wlp3s0 instead of the usual wlan0 on other 
installations I've made.
If I try $ ifdown wlp3s0 results in Unknown interface wlp3s0
As to comment #133 nm-applet still crashes after hardware switching off/on WiFi 
and resuming from suspend.

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

Title:
  cannot view wifi networks after re-enabling wifi

Status in NetworkManager:
  Unknown
Status in network-manager package in Ubuntu:
  Incomplete

Bug description:
  after re enabling wifi, up-down arrows just like wired network. cannot
  see any wifi ssid.

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

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

[Desktop-packages] [Bug 1658921] Re: NetworkManager does not manage wired connection

[Diego]

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

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

Title:
  NetworkManager does not manage wired connection

Status in network-manager package in Ubuntu:
  New

Bug description:
  NetworkManager does not manage my wired eth0 connection, no matter how
  I set /etc/network/interfaces or
  /etc/NetworkManager/NetworkManager.conf

  Using ubuntu 16.04, /etc/network/interfaces only managed lo, and
  [ifupdown] section of NetworkManager.conf had set managed=false.

  With these same settings, after upgrading to ubuntu 16.10, eth0
  appears as unmanaged in nm-applet.

  If I modify /etc/network/interfaces and add

  auto eth0
  iface eth0 inet dhcp

  And set managed=true in NetworkManager.conf [ifupdown] section, eth0
  is still unmanaged despite it does get an IP from DHCP server.

  This is happening in my five computers (two laptops and three
  desktops).

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

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

[Desktop-packages] [Bug 1658921] Re: NetworkManager does not manage wired connection

[Diego]

And here is NetworkManager.conf

** Attachment added: "NetworkManager.conf"
   
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1658921/+attachment/4809300/+files/NetworkManager.conf

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

Title:
  NetworkManager does not manage wired connection

Status in network-manager package in Ubuntu:
  Incomplete

Bug description:
  NetworkManager does not manage my wired eth0 connection, no matter how
  I set /etc/network/interfaces or
  /etc/NetworkManager/NetworkManager.conf

  Using ubuntu 16.04, /etc/network/interfaces only managed lo, and
  [ifupdown] section of NetworkManager.conf had set managed=false.

  With these same settings, after upgrading to ubuntu 16.10, eth0
  appears as unmanaged in nm-applet.

  If I modify /etc/network/interfaces and add

  auto eth0
  iface eth0 inet dhcp

  And set managed=true in NetworkManager.conf [ifupdown] section, eth0
  is still unmanaged despite it does get an IP from DHCP server.

  This is happening in my five computers (two laptops and three
  desktops).

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

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

[Desktop-packages] [Bug 1658921] Re: NetworkManager does not manage wired connection

[Diego]

My /etc/network/interfaces and /etc/NetworkManager/NetworkManager.conf
are just as you stated.


** Attachment added: "interfaces"
   
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1658921/+attachment/4809299/+files/interfaces

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

Title:
  NetworkManager does not manage wired connection

Status in network-manager package in Ubuntu:
  Incomplete

Bug description:
  NetworkManager does not manage my wired eth0 connection, no matter how
  I set /etc/network/interfaces or
  /etc/NetworkManager/NetworkManager.conf

  Using ubuntu 16.04, /etc/network/interfaces only managed lo, and
  [ifupdown] section of NetworkManager.conf had set managed=false.

  With these same settings, after upgrading to ubuntu 16.10, eth0
  appears as unmanaged in nm-applet.

  If I modify /etc/network/interfaces and add

  auto eth0
  iface eth0 inet dhcp

  And set managed=true in NetworkManager.conf [ifupdown] section, eth0
  is still unmanaged despite it does get an IP from DHCP server.

  This is happening in my five computers (two laptops and three
  desktops).

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

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

[Desktop-packages] [Bug 1658921] [NEW] NetworkManager does not manage wired connection

[Diego]

Public bug reported:

NetworkManager does not manage my wired eth0 connection, no matter how I
set /etc/network/interfaces or /etc/NetworkManager/NetworkManager.conf

Using ubuntu 16.04, /etc/network/interfaces only managed lo, and
[ifupdown] section of NetworkManager.conf had set managed=false.

With these same settings, after upgrading to ubuntu 16.10, eth0 appears
as unmanaged in nm-applet.

If I modify /etc/network/interfaces and add

auto eth0
iface eth0 inet dhcp

And set managed=true in NetworkManager.conf [ifupdown] section, eth0 is
still unmanaged despite it does get an IP from DHCP server.

This is happening in my five computers (two laptops and three desktops).

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

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

Title:
  NetworkManager does not manage wired connection

Status in network-manager package in Ubuntu:
  New

Bug description:
  NetworkManager does not manage my wired eth0 connection, no matter how
  I set /etc/network/interfaces or
  /etc/NetworkManager/NetworkManager.conf

  Using ubuntu 16.04, /etc/network/interfaces only managed lo, and
  [ifupdown] section of NetworkManager.conf had set managed=false.

  With these same settings, after upgrading to ubuntu 16.10, eth0
  appears as unmanaged in nm-applet.

  If I modify /etc/network/interfaces and add

  auto eth0
  iface eth0 inet dhcp

  And set managed=true in NetworkManager.conf [ifupdown] section, eth0
  is still unmanaged despite it does get an IP from DHCP server.

  This is happening in my five computers (two laptops and three
  desktops).

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

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

[Desktop-packages] [Bug 1656360] [NEW] Possible erroneous information in software description

[Diego Germán Gonzalez]

Public bug reported:

In the description of Krita (snap package) reads this message "...and
due to a bug in Ubuntu, this snap doesn't work with proprietary video
drivers, e.g. for NVidia." I'm using NVIDIA 367.57 and works without
problems

ProblemType: Bug
DistroRelease: Ubuntu 16.10
Package: gnome-software 3.20.1+git20161013.0.d77d6cf-0ubuntu2
ProcVersionSignature: Ubuntu 4.8.0-34.36-generic 4.8.11
Uname: Linux 4.8.0-34-generic x86_64
NonfreeKernelModules: zfs zunicode zcommon znvpair zavl nvidia_uvm nvidia_drm 
nvidia_modeset nvidia
ApportVersion: 2.20.3-0ubuntu8.2
Architecture: amd64
CurrentDesktop: Unity
Date: Fri Jan 13 13:54:12 2017
InstallationDate: Installed on 2016-11-04 (70 days ago)
InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
SourcePackage: gnome-software
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug yakkety

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

Title:
  Possible erroneous information in software description

Status in gnome-software package in Ubuntu:
  New

Bug description:
  In the description of Krita (snap package) reads this message "...and
  due to a bug in Ubuntu, this snap doesn't work with proprietary video
  drivers, e.g. for NVidia." I'm using NVIDIA 367.57 and works without
  problems

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: gnome-software 3.20.1+git20161013.0.d77d6cf-0ubuntu2
  ProcVersionSignature: Ubuntu 4.8.0-34.36-generic 4.8.11
  Uname: Linux 4.8.0-34-generic x86_64
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl nvidia_uvm nvidia_drm 
nvidia_modeset nvidia
  ApportVersion: 2.20.3-0ubuntu8.2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Jan 13 13:54:12 2017
  InstallationDate: Installed on 2016-11-04 (70 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  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/1656360/+subscriptions

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

[Desktop-packages] [Bug 1229490] Re: Deja-dup backup ignores "folders to ignore" setting

[Diego González]

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

In addition to bug #1313034 (aybe because of it) ignores other folders
marked for example .local/share/zeitgeist .

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

Title:
  Deja-dup backup ignores "folders to ignore" setting

Status in deja-dup package in Ubuntu:
  Confirmed

Bug description:
  Every day deja-dup shows a popup message saying it failed to backup 2
  files. The folders containing these files are already in the list of
  folders to ignore, so deja-dup shouldn't even be trying to back them
  up. I'm attaching a screenshot to illustrate.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: deja-dup 26.0-0ubuntu1
  ProcVersionSignature: Ubuntu 3.8.0-30.44-generic 3.8.13.6
  Uname: Linux 3.8.0-30-generic x86_64
  ApportVersion: 2.9.2-0ubuntu8.3
  Architecture: amd64
  Date: Tue Sep 24 09:34:32 2013
  ExecutablePath: /usr/bin/deja-dup
  InstallationDate: Installed on 2013-08-19 (35 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  MarkForUpload: True
  SourcePackage: deja-dup
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1266492] Re: ld:i386 crashes with -static -fPIE -pie

[Diego]

** Changed in: binutils (Ubuntu Trusty)
 Assignee: (unassigned) => Diego (dmggears3)

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

Title:
  ld:i386 crashes with -static -fPIE -pie

Status in GLibC:
  Incomplete
Status in binutils package in Ubuntu:
  Confirmed
Status in eglibc package in Ubuntu:
  Fix Released
Status in evolution-data-server package in Ubuntu:
  Fix Released
Status in xorg-server package in Ubuntu:
  Fix Released
Status in binutils source package in Trusty:
  Confirmed
Status in eglibc source package in Trusty:
  Fix Released
Status in evolution-data-server source package in Trusty:
  Triaged
Status in xorg-server source package in Trusty:
  Fix Released
Status in eglibc package in Debian:
  Fix Released

Bug description:
  Making a simple file conftest.c with the following contents:

  int main() { return 0; }

  And then compiling it on i386 with gcc -fPIE -pie -static conftest.c
  returns:

  *** Error in `/usr/bin/ld': corrupted double-linked list: 0x08dddb38
  ***

  This breaks compilation xorg-server on i386. I believe that -static
  -fPIE -pie is probably invalid, and it fails on amd64 too.

  $ gcc -fPIE -pie -static conftest.c 
  /usr/bin/ld: /usr/lib/gcc/x86_64-linux-gnu/4.8/crtbeginT.o: relocation 
R_X86_64_32 against `__TMC_END__' can not be used when making a shared object; 
recompile with -fPIC
  /usr/lib/gcc/x86_64-linux-gnu/4.8/crtbeginT.o: error adding symbols: Bad value
  collect2: error: ld returned 1 exit status

  But autoconf hangs on the corrupted double-linked list, which times
  out the xorg-server build.

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

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

[Desktop-packages] [Bug 1517884] Re: libxp6 not available in xenial

[Diego Remolina]

Well not a fix, but a workaround for those of you struggling, simply add
the trusty repository, install libxp6, then remove it...

create:

/etc/apt/sources.list.d/libxp-source.list

as:

# Used to install libxp6 for chemkin and ansys to work
deb http://us.archive.ubuntu.com/ubuntu trusty main universe

apt-get update
apt-get install libxp6

Then comment out the repository line and

apt-get clean all

No updates, etc, but you get the library you need for now.

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

Title:
  libxp6 not available in xenial

Status in libxp package in Ubuntu:
  Confirmed

Bug description:
  libxp6:i386 is not available in 15.10/Wily but is needed.

  Citrix Icaclient depends on it and will not work without it.

  It would be nice to have it in the repos again.

  lsb_release -rd
  Description:  Ubuntu 15.10
  Release:  15.10

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

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

[Desktop-packages] [Bug 1616943] Re: Can't auth against U1 in g-s

[Diego Germán Gonzalez]

I do not know if it's the same problem, but this happens only in the version 
published to correct this bug

** Attachment added: "Captura de pantalla de 2016-10-20 16-00-58.png"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1616943/+attachment/4764532/+files/Captura%20de%20pantalla%20de%202016-10-20%2016-00-58.png

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

Title:
  Can't auth against U1 in g-s

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

Bug description:
  [Impact]
  Authentication using Ubuntu One credentials to install/remove snaps always  
fails. This is due to a behaviour change in snapd (no longer accepts login 
requests from non-root users). Existing credentials continue to work.

  [Test Case]
  1. Delete any existing credentials by deleting passwords marked 
"com.ubuntu.UbuntuOne.GnomeSoftware" using Seahorse.
  2. Start GNOME Software
  3. Search for a snap (e.g. "moon-buggy")
  4. Install Snap
  5. Enter Ubuntu One credentials when prompted

  Observed result:
  Dialog says "Incorrect email or password".

  Expected result:
  Authentication completes and the snap is installed.

  [Regression Potential]
  The solution is to use a new D-Bus service (snapd-login-service) and new 
library (snapd-glib) to get the Macaroon from snapd. This has some risk of 
introducing new bugs. The change is minimised (other snapd code paths 
unchanged) and the alternative is login to be impossible.

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

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

[Desktop-packages] [Bug 1616943] Re: Can't auth against U1 in g-s

[Diego Germán Gonzalez]

Sorry, there would be easier to make snap have a proper graphical installer?
For years they lived together in Ubuntu an installer programs and Synaptic. And 
both did the same.

All the more reason to have two different installers for different
package formats.

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

Title:
  Can't auth against U1 in g-s

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

Bug description:
  [Impact]
  Authentication using Ubuntu One credentials to install/remove snaps always  
fails. This is due to a behaviour change in snapd (no longer accepts login 
requests from non-root users). Existing credentials continue to work.

  [Test Case]
  1. Delete any existing credentials by deleting passwords marked 
"com.ubuntu.UbuntuOne.GnomeSoftware" using Seahorse.
  2. Start GNOME Software
  3. Search for a snap (e.g. "moon-buggy")
  4. Install Snap
  5. Enter Ubuntu One credentials when prompted

  Observed result:
  Dialog says "Incorrect email or password".

  Expected result:
  Authentication completes and the snap is installed.

  [Regression Potential]
  The solution is to use a new D-Bus service (snapd-login-service) and new 
library (snapd-glib) to get the Macaroon from snapd. This has some risk of 
introducing new bugs. The change is minimised (other snapd code paths 
unchanged) and the alternative is login to be impossible.

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

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