[Desktop-packages] [Bug 1996946] Re: Memory leak on every frame when reading GIF animations

[Alejandro]

** Changed in: gdk-pixbuf (Ubuntu)
   Status: New => Confirmed

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

Title:
  Memory leak on every frame when reading GIF animations

Status in gdk-pixbuf package in Ubuntu:
  Confirmed

Bug description:
  There is a big memory leak when reading GIF animations.

  The issue was identified and fixed in gdk-pixbuf two (2) years ago,
  but it was released in a version grater that the available in Ubuntu
  20.04.

  At first glance, the leak appears only when a static image is
  requested, but this function is used by pixbuf's upload functions and
  calls this function internally. So the leak happens every time a GIF
  is loaded.

  Here is the commit with the fix released in version 2.41:

  https://gitlab.gnome.org/GNOME/gdk-
  pixbuf/-/commit/dd3aa9ed64a0a370c8150f98e849ffc6e73da827

  A patch is attached to this message.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdk-pixbuf/+bug/1996946/+subscriptions


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

[Desktop-packages] [Bug 1996946] Re: Memory leak on every frame when reading GIF animations

[Alejandro]

** Description changed:

  There is a big memory leak when reading GIF animations.
  
  The issue was identified and fixed in gdk-pixbuf two (2) years ago, but
  it was released in a version grater that the available in Ubuntu 20.04.
  
  At first glance, the leak appears only when a static image is requested,
  but this function is used by pixbuf's upload functions and calls this
  function internally. So the leak happens every time a GIF is loaded.
  
- Here is the commit with the fix releases in version 2.41:
+ Here is the commit with the fix released in version 2.41:
  
  https://gitlab.gnome.org/GNOME/gdk-
  pixbuf/-/commit/dd3aa9ed64a0a370c8150f98e849ffc6e73da827
  
  A patch is attached to this message.

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

Title:
  Memory leak on every frame when reading GIF animations

Status in gdk-pixbuf package in Ubuntu:
  New

Bug description:
  There is a big memory leak when reading GIF animations.

  The issue was identified and fixed in gdk-pixbuf two (2) years ago,
  but it was released in a version grater that the available in Ubuntu
  20.04.

  At first glance, the leak appears only when a static image is
  requested, but this function is used by pixbuf's upload functions and
  calls this function internally. So the leak happens every time a GIF
  is loaded.

  Here is the commit with the fix released in version 2.41:

  https://gitlab.gnome.org/GNOME/gdk-
  pixbuf/-/commit/dd3aa9ed64a0a370c8150f98e849ffc6e73da827

  A patch is attached to this message.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdk-pixbuf/+bug/1996946/+subscriptions


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

[Desktop-packages] [Bug 1996946] [NEW] Memory leak on every frame when reading GIF animations

[Alejandro]

Public bug reported:

There is a big memory leak when reading GIF animations.

The issue was identified and fixed in gdk-pixbuf two (2) years ago, but
it was released in a version grater that the available in Ubuntu 20.04.

At first glance, the leak appears only when a static image is requested,
but this function is used by pixbuf's upload functions and calls this
function internally. So the leak happens every time a GIF is loaded.

Here is the commit with the fix releases in version 2.41:

https://gitlab.gnome.org/GNOME/gdk-
pixbuf/-/commit/dd3aa9ed64a0a370c8150f98e849ffc6e73da827

A patch is attached to this message.

** Affects: gdk-pixbuf (Ubuntu)
 Importance: Undecided
 Status: New

** Patch added: "Fix memory leak"
   
https://bugs.launchpad.net/bugs/1996946/+attachment/5631282/+files/fix-animation-iterator-leak.patch

** Summary changed:

- Memory leak on every frmae when reading GIF animations
+ Memory leak on every frame when reading GIF animations

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

Title:
  Memory leak on every frame when reading GIF animations

Status in gdk-pixbuf package in Ubuntu:
  New

Bug description:
  There is a big memory leak when reading GIF animations.

  The issue was identified and fixed in gdk-pixbuf two (2) years ago,
  but it was released in a version grater that the available in Ubuntu
  20.04.

  At first glance, the leak appears only when a static image is
  requested, but this function is used by pixbuf's upload functions and
  calls this function internally. So the leak happens every time a GIF
  is loaded.

  Here is the commit with the fix releases in version 2.41:

  https://gitlab.gnome.org/GNOME/gdk-
  pixbuf/-/commit/dd3aa9ed64a0a370c8150f98e849ffc6e73da827

  A patch is attached to this message.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdk-pixbuf/+bug/1996946/+subscriptions


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

[Desktop-packages] [Bug 1970921] Re: Drag and drop does not work

[Alejandro]

I have the same problem, drag and drop fails in many forms on Wayland (not on 
X11).
If you repeatedly drag and drop from Nautilus to Chrome (for example), it works 
like 10% of the time.

- sometimes it works
- sometimes it pastes a text path instead of the file
- sometimes it does nothing

When opening a Chrome tab by dropping a file, often I see a wrong path
like this:

file:///home/thisuser/Downloads/some_document.docx-34:-56:63:64

It seems like the random addendum -34:-56:63:64 is causing the fail.

I'm using up to date Ubuntu 22.04, Gnome 42.4 on Wayland.  Drag and drop
is failing for me since Ubuntu 22.04 release, when I switched to
Wayland.

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

Title:
  Drag and drop does not work

Status in Nautilus:
  Fix Released
Status in nautilus package in Ubuntu:
  Triaged

Bug description:
  After upgrading Ubuntu to 22.04 drag and dropping files from nautilus
  to web browser (chromium, google chrome / apps like seafile, etc.) do
  not work. Also drag & drop from nautilus to slack desktop app does not
  work. If making several attempts, it might suddenly work with nth
  attempt.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: nautilus 1:42.0-1ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30
  Uname: Linux 5.15.0-27-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Apr 29 13:32:48 2022
  InstallationDate: Installed on 2016-11-22 (1983 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  SourcePackage: nautilus
  UpgradeStatus: Upgraded to jammy on 2022-04-29 (0 days ago)
  usr_lib_nautilus:
   evince42.1-3
   file-roller   3.42.0-1
   nautilus-extension-gnome-terminal 3.44.0-1ubuntu1
   nautilus-share0.7.3-2ubuntu6

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


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

[Desktop-packages] [Bug 1987737] Re: firefox from snap disabled save button in subfolders

[Alejandro R. Mosteo]

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

I guess this info is no longer needed, but just in case:

Neither of /usr/libexec/xdg-desktop-portal-gtk -rv or journalctl -f
produce any new output while reproducing the bug.

$ LANG=C dpkg -l xdg-desktop-portal*
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name   Version Architecture Description
+++-==-===--
ii  xdg-desktop-portal 1.14.3-0ubuntu2 amd64desktop integration 
portal for Flatpak and Snap
un  xdg-desktop-portal-backend  (no description 
available)
ii  xdg-desktop-portal-gnome   42.0.1-1ubuntu2 amd64GNOME portal 
backend for xdg-desktop-portal
ii  xdg-desktop-portal-gtk 1.14.0-1build1  amd64GTK+/GNOME portal 
backend for xdg-desktop-portal

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

Title:
  firefox from snap disabled save button in subfolders

Status in firefox package in Ubuntu:
  Incomplete

Bug description:
  1) Ubuntu 22.04 fully updated
  2) Firefox snap id 3wdHCAVyZEmYsCMFDE9qt92UV8rC8Wdk
  3) I expect being able to save a file to folders in my home folder or in a 
usb drive
  4) When selecting a plugged-in USB drive or the home folder I can save, once 
I enter a subfolder the "save" button in the save dialog gets greyed out.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: firefox 1:1snap1-0ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39
  Uname: Linux 5.15.0-46-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset 
nvidia
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop:
   
  Date: Fri Aug 26 10:11:37 2022
  InstallationDate: Installed on 2021-07-14 (407 days ago)
  InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  SourcePackage: firefox
  UpgradeStatus: Upgraded to jammy on 2022-08-24 (1 days ago)
  modified.conffile..etc.default.apport: [modified]
  mtime.conffile..etc.default.apport: 2021-07-14T15:11:35.001074

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


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

[Desktop-packages] [Bug 1987737] Re: firefox from snap disabled save button in subfolders

[Alejandro R. Mosteo]

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

> Does it ungrey if you edit the filename? it seems a bit similar to bug
#1971516

Indeed it does. It's a duplicate then, I will mark it as such.

** This bug has been marked a duplicate of bug 1971516
   Entering fileselector subdir disables the save button until filename is 
edited

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

Title:
  firefox from snap disabled save button in subfolders

Status in firefox package in Ubuntu:
  Incomplete

Bug description:
  1) Ubuntu 22.04 fully updated
  2) Firefox snap id 3wdHCAVyZEmYsCMFDE9qt92UV8rC8Wdk
  3) I expect being able to save a file to folders in my home folder or in a 
usb drive
  4) When selecting a plugged-in USB drive or the home folder I can save, once 
I enter a subfolder the "save" button in the save dialog gets greyed out.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: firefox 1:1snap1-0ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39
  Uname: Linux 5.15.0-46-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset 
nvidia
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop:
   
  Date: Fri Aug 26 10:11:37 2022
  InstallationDate: Installed on 2021-07-14 (407 days ago)
  InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  SourcePackage: firefox
  UpgradeStatus: Upgraded to jammy on 2022-08-24 (1 days ago)
  modified.conffile..etc.default.apport: [modified]
  mtime.conffile..etc.default.apport: 2021-07-14T15:11:35.001074

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


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

[Desktop-packages] [Bug 1987737] Re: firefox from snap disabled save button in subfolders

[Alejandro R. Mosteo]

Yes, it happens with any folder under my home folder, including the
'Downloads' one.

I'm using stock Ubuntu with the default Gnome shell.

This is an upgraded system since at least 18.04, via 20.04.

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

Title:
  firefox from snap disabled save button in subfolders

Status in firefox package in Ubuntu:
  Incomplete

Bug description:
  1) Ubuntu 22.04 fully updated
  2) Firefox snap id 3wdHCAVyZEmYsCMFDE9qt92UV8rC8Wdk
  3) I expect being able to save a file to folders in my home folder or in a 
usb drive
  4) When selecting a plugged-in USB drive or the home folder I can save, once 
I enter a subfolder the "save" button in the save dialog gets greyed out.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: firefox 1:1snap1-0ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39
  Uname: Linux 5.15.0-46-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset 
nvidia
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop:
   
  Date: Fri Aug 26 10:11:37 2022
  InstallationDate: Installed on 2021-07-14 (407 days ago)
  InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  SourcePackage: firefox
  UpgradeStatus: Upgraded to jammy on 2022-08-24 (1 days ago)
  modified.conffile..etc.default.apport: [modified]
  mtime.conffile..etc.default.apport: 2021-07-14T15:11:35.001074

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


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

[Desktop-packages] [Bug 1987737] [NEW] firefox from snap disabled save button in subfolders

[Alejandro R. Mosteo]

Public bug reported:

1) Ubuntu 22.04 fully updated
2) Firefox snap id 3wdHCAVyZEmYsCMFDE9qt92UV8rC8Wdk
3) I expect being able to save a file to folders in my home folder or in a usb 
drive
4) When selecting a plugged-in USB drive or the home folder I can save, once I 
enter a subfolder the "save" button in the save dialog gets greyed out.

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: firefox 1:1snap1-0ubuntu2
ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39
Uname: Linux 5.15.0-46-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset 
nvidia
ApportVersion: 2.20.11-0ubuntu82.1
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop:
 
Date: Fri Aug 26 10:11:37 2022
InstallationDate: Installed on 2021-07-14 (407 days ago)
InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
SourcePackage: firefox
UpgradeStatus: Upgraded to jammy on 2022-08-24 (1 days ago)
modified.conffile..etc.default.apport: [modified]
mtime.conffile..etc.default.apport: 2021-07-14T15:11:35.001074

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


** Tags: amd64 apport-bug jammy

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

Title:
  firefox from snap disabled save button in subfolders

Status in firefox package in Ubuntu:
  New

Bug description:
  1) Ubuntu 22.04 fully updated
  2) Firefox snap id 3wdHCAVyZEmYsCMFDE9qt92UV8rC8Wdk
  3) I expect being able to save a file to folders in my home folder or in a 
usb drive
  4) When selecting a plugged-in USB drive or the home folder I can save, once 
I enter a subfolder the "save" button in the save dialog gets greyed out.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: firefox 1:1snap1-0ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39
  Uname: Linux 5.15.0-46-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset 
nvidia
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop:
   
  Date: Fri Aug 26 10:11:37 2022
  InstallationDate: Installed on 2021-07-14 (407 days ago)
  InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  SourcePackage: firefox
  UpgradeStatus: Upgraded to jammy on 2022-08-24 (1 days ago)
  modified.conffile..etc.default.apport: [modified]
  mtime.conffile..etc.default.apport: 2021-07-14T15:11:35.001074

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


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

[Desktop-packages] [Bug 1971916] [NEW] error in the system

[Alejandro Chavez Rodriguez]

Public bug reported:

I get several messages when I start the UBUNTU OS

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg 1:7.7+13ubuntu3.1
ProcVersionSignature: Ubuntu 4.15.0-142.146~16.04.1-generic 4.15.18
Uname: Linux 4.15.0-142-generic i686
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.1-0ubuntu2.30
Architecture: i386
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
Date: Thu May  5 21:42:12 2022
DistUpgraded: Fresh install
DistroCodename: xenial
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, including running git bisection searches
GraphicsCard:
 Advanced Micro Devices, Inc. [AMD/ATI] RV620/M82 [Mobility Radeon HD 
3410/3430] [1002:95c2] (prog-if 00 [VGA controller])
   Subsystem: Hewlett-Packard Company RV620/M82 [Mobility Radeon HD 3410/3430] 
[103c:30e9]
InstallationDate: Installed on 2022-05-02 (3 days ago)
InstallationMedia: Ubuntu 16.04.6 LTS "Xenial Xerus" - Release i386 (20190227.1)
MachineType: Hewlett-Packard HP Compaq 6830s (FR883LA#ABM)
ProcEnviron:
 LANGUAGE=es_MX:es
 PATH=(custom, no user)
 LANG=es_MX.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-142-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 06/24/2009
dmi.bios.vendor: Hewlett-Packard
dmi.bios.version: 68PZD Ver. F.0F
dmi.board.name: 30E9
dmi.board.vendor: Hewlett-Packard
dmi.board.version: KBC Version 95.1D
dmi.chassis.asset.tag: CNU8504GHF
dmi.chassis.type: 10
dmi.chassis.vendor: Hewlett-Packard
dmi.modalias: 
dmi:bvnHewlett-Packard:bvr68PZDVer.F.0F:bd06/24/2009:svnHewlett-Packard:pnHPCompaq6830s(FR883LA#ABM):pvrF.0F:rvnHewlett-Packard:rn30E9:rvrKBCVersion95.1D:cvnHewlett-Packard:ct10:cvr:
dmi.product.family: 103C_5336AN
dmi.product.name: HP Compaq 6830s (FR883LA#ABM)
dmi.product.version: F.0F
dmi.sys.vendor: Hewlett-Packard
version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1
version.libdrm2: libdrm2 2.4.91-2~16.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~16.04.1
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~16.04.1
version.xserver-xorg-core: xserver-xorg-core N/A
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
xserver.bootTime: Thu May  5 21:31:49 2022
xserver.configfile: default
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs: OutputLVDS   VGA-0
xserver.version: 2:1.19.6-1ubuntu4.1~16.04.6
xserver.video_driver: radeon

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


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

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

Title:
  error in the system

Status in xorg package in Ubuntu:
  New

Bug description:
  I get several messages when I start the UBUNTU OS

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3.1
  ProcVersionSignature: Ubuntu 4.15.0-142.146~16.04.1-generic 4.15.18
  Uname: Linux 4.15.0-142-generic i686
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.30
  Architecture: i386
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Thu May  5 21:42:12 2022
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] RV620/M82 [Mobility Radeon HD 
3410/3430] [1002:95c2] (prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company RV620/M82 [Mobility Radeon HD 
3410/3430] [103c:30e9]
  InstallationDate: Installed on 2022-05-02 (3 days ago)
  InstallationMedia: Ubuntu 16.04.6 LTS "Xenial Xerus" - Release i386 
(20190227.1)
  MachineType: Hewlett-Packard HP Compaq 6830s (FR883LA#ABM)
  ProcEnviron:
   LANGUAGE=es_MX:es
   PATH=(custom, no user)
   LANG=es_MX.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-142-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/24/2009
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: 68PZD Ver. F.0F
  dmi.board.name: 30E9
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 95.1D

[Desktop-packages] [Bug 1969959] Re: Weird colors after startup (Ubuntu 22.04)

[Alejandro R. Mosteo]

Same here, trying the first stable live release of 22.04. I get a
weirdly saturated green-lime combo. Picture attached.

VGA: Intel HD Graphics 530
Monitor: HP LE2201w


** Attachment added: "Picture of screen"
   
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1969959/+attachment/5582878/+files/20220423_194416.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/1969959

Title:
  Weird colors after startup (Ubuntu 22.04)

Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  I started Ubuntu 22.04 from a live pen drive. Everything seems fine,
  the usual screen with the options to "Try Ubuntu" or "Install" Ubuntu
  appears. When hitting "Try Ubuntu", the screen turns black for a
  couple of seconds and then re-appears in yellow and brown colors,
  feels like a 4 color display (white, black, yellow and orange) and I
  can hardly see anything - sending this bug report from that live
  system right after starting it up.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30
  Uname: Linux 5.15.0-25-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CasperVersion: 1.470
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Apr 22 15:54:05 2022
  DistUpgraded: Fresh install
  DistroCodename: jammy
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   NVIDIA Corporation TU117 [GeForce GTX 1650] [10de:1f82] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: NVIDIA Corporation TU117 [GeForce GTX 1650] [10de:1f82]
   Advanced Micro Devices, Inc. [AMD/ATI] Renoir [1002:1636] (rev d9) (prog-if 
00 [VGA controller])
 Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] Renoir [1002:1636]
  LiveMediaBuild: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419)
  MachineType: Micro-Star International Co., Ltd. MS-7C56
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz 
file=/cdrom/preseed/username.seed maybe-ubiquity quiet splash ---
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/30/2020
  dmi.bios.release: 5.17
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: A.40
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: B550-A PRO (MS-7C56)
  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.:bvrA.40:bd10/30/2020:br5.17:svnMicro-StarInternationalCo.,Ltd.:pnMS-7C56:pvr1.0:rvnMicro-StarInternationalCo.,Ltd.:rnB550-APRO(MS-7C56):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr1.0:skuTobefilledbyO.E.M.:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: MS-7C56
  dmi.product.sku: To be filled by O.E.M.
  dmi.product.version: 1.0
  dmi.sys.vendor: Micro-Star International Co., Ltd.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.110-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.1-1ubuntu2
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build3
  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

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


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

[Desktop-packages] [Bug 1960647] [NEW] sound problem on Dell Vostro 3405

[Alejandro Arcos]

Public bug reported:

>From install xubuntu not sound on my laptop, i following
https://help.ubuntu.com/community/SoundTroubleshootingProcedure

I found with BIOS nro 146 not show features (microfone for example) and
my system show Dummy outputs devices.

After upgrade BIOS 149 this features appears!! But not sounds... attach
file with info!!!

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: alsa-base 1.0.25+dfsg-0ubuntu5
ProcVersionSignature: Ubuntu 5.4.0-99.112-generic 5.4.162
Uname: Linux 5.4.0-99-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.21
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC1:  melange1188 F pulseaudio
 /dev/snd/controlC0:  melange1188 F pulseaudio
CasperMD5CheckResult: skip
CurrentDesktop: XFCE
Date: Fri Feb 11 12:42:33 2022
InstallationDate: Installed on 2021-11-19 (83 days ago)
InstallationMedia: Xubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
PackageArchitecture: all
SourcePackage: alsa-driver
Symptom: audio
Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Generic_1 failed
Symptom_Card: Family 17h (Models 10h-1fh) HD Audio Controller - HD-Audio Generic
Symptom_DevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC1:  melange1188 F pulseaudio
 /dev/snd/controlC0:  melange1188 F pulseaudio
Symptom_Jack: Speaker, Internal
Symptom_Type: No sound at all
Title: [Vostro 3405, Cirrus Logic Generic, Speaker, Internal] No sound at all
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 10/12/2021
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.4.9
dmi.board.asset.tag: not specified
dmi.board.name: 0Y6PDY
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 10
dmi.chassis.vendor: Dell Inc.
dmi.chassis.version: 1.4.9
dmi.modalias: 
dmi:bvnDellInc.:bvr1.4.9:bd10/12/2021:svnDellInc.:pnVostro3405:pvr1.4.9:rvnDellInc.:rn0Y6PDY:rvrA00:cvnDellInc.:ct10:cvr1.4.9:
dmi.product.family: Vostro
dmi.product.name: Vostro 3405
dmi.product.sku: 0A11
dmi.product.version: 1.4.9
dmi.sys.vendor: Dell Inc.
mtime.conffile..etc.modprobe.d.alsa-base.conf: 2022-02-11T11:47:02.161792

** Affects: alsa-driver (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 alsa-driver in Ubuntu.
https://bugs.launchpad.net/bugs/1960647

Title:
   sound problem on Dell Vostro 3405

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  From install xubuntu not sound on my laptop, i following
  https://help.ubuntu.com/community/SoundTroubleshootingProcedure

  I found with BIOS nro 146 not show features (microfone for example)
  and my system show Dummy outputs devices.

  After upgrade BIOS 149 this features appears!! But not sounds...
  attach file with info!!!

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.4.0-99.112-generic 5.4.162
  Uname: Linux 5.4.0-99-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  melange1188 F pulseaudio
   /dev/snd/controlC0:  melange1188 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: XFCE
  Date: Fri Feb 11 12:42:33 2022
  InstallationDate: Installed on 2021-11-19 (83 days ago)
  InstallationMedia: Xubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 
(20200731)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Generic_1 failed
  Symptom_Card: Family 17h (Models 10h-1fh) HD Audio Controller - HD-Audio 
Generic
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  melange1188 F pulseaudio
   /dev/snd/controlC0:  melange1188 F pulseaudio
  Symptom_Jack: Speaker, Internal
  Symptom_Type: No sound at all
  Title: [Vostro 3405, Cirrus Logic Generic, Speaker, Internal] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/12/2021
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.4.9
  dmi.board.asset.tag: not specified
  dmi.board.name: 0Y6PDY
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: 1.4.9
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.4.9:bd10/12/2021:svnDellInc.:pnVostro3405:pvr1.4.9:rvnDellInc.:rn0Y6PDY:rvrA00:cvnDellInc.:ct10:cvr1.4.9:
  dmi.product.family: Vostro
  dmi.product.name: Vostro 3405
  dmi.product.sku: 0A11
  dmi.product.version: 1.4.9
  dmi.sys.vendor: Dell Inc.
  mtime.conffile..etc.modprobe.d.alsa-base.conf: 2022-02-11T11:47:02.161792

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


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

[Desktop-packages] [Bug 1771880] Re: Seahorse unable to import pkcs12 certificates

[Alejandro]

same problem. LTS Ubuntu 20.04 update today 01-2022, seahorse 3.36-1

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

Title:
  Seahorse unable to import pkcs12 certificates

Status in seahorse:
  New
Status in gnome-keyring package in Ubuntu:
  Triaged
Status in seahorse package in Ubuntu:
  Triaged
Status in gnome-keyring package in Fedora:
  New
Status in seahorse package in Fedora:
  Unknown

Bug description:
  seahorse 3.20.0-5 / gnome-keyring 3.28.0.2-1ubuntu1.18.04.1 / Ubuntu
  18.04 LTS / GNOME 3.28.1

  When trying to import a certificate into seahorse/gnome-keyring on
  Ubuntu 18.04, seahorse GUI application shows the 'import' button
  greyed out, while mouse hovering the "import" button shows the message
  "Cannot import because there are no compatible importers".

  This problem doesn't occur on Ubuntu 16.04 LTS (Seahorse 3.18.0), as
  I've just tested on my wife's laptop, but happens in my Laptop with
  Ubuntu 18.04 LTS (Seahorse 3.20.0-5).

  Because that problem, it's not possible to digitally sign documents
  with LibreOffice.

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


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

[Desktop-packages] [Bug 1890572] Re: USB backend never ends if the printer is not connected

[Alejandro]

Hi Till,

the issue was reported in the Apple repository:

https://github.com/apple/cups/issues/5817

I will check whether this was already fixed in OpenPrinting or not.

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

Title:
  USB backend never ends if the printer is not connected

Status in cups package in Ubuntu:
  Fix Released

Bug description:
  USB backend never ends if the printer is not connected. We have been
  able to identify a infinity loop in print_device function in usb-
  libusb.c file:

  ```
    fprintf(stderr, "DEBUG: Printing on printer with URI: %s\n", uri);
    while ((g.printer = find_device(print_cb, uri)) == NULL)
    {
  _cupsLangPrintFilter(stderr, "INFO",
  _("Waiting for printer to become available."));
  sleep(5);
    }
  ```

  It's also easy to test by invoking the backend by hand:

  ```
  # export DEVICE_URI='usb://Printer/Model?serial=?'
  # /usr/lib/cups/backend/usb 0 root title 1 '' data.file

  DEBUG: Loading USB quirks from "/usr/share/cups/usb".
  DEBUG: Loaded 159 quirks.
  DEBUG: Printing on printer with URI: usb://Printer/Model?serial=?
  DEBUG: libusb_get_device_list=6
  INFO: Waiting for printer to become available.
  DEBUG: libusb_get_device_list=6
  INFO: Waiting for printer to become available.
  DEBUG: libusb_get_device_list=6
  INFO: Waiting for printer to become available.
  DEBUG: libusb_get_device_list=6
  INFO: Waiting for printer to become available.
  DEBUG: libusb_get_device_list=6
  INFO: Waiting for printer to become available.
  ...

  ```

  Setting a job timeout policy or manually stopping work are not options
  for us. We may have jobs that take hours to complete.

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


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

[Desktop-packages] [Bug 1692671] Re: intel driver fails to reenable display

[Alejandro Mery]

it's been more than 4 years. nothing is the same as when this problem
happened

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

Title:
  intel driver fails to reenable display

Status in xorg-server package in Ubuntu:
  Incomplete

Bug description:
  if the display is sent to sleep it won't wake up. If I go to tty1 or
  tty2 I'm pulled back to tty7 (?) within seconds.

  sometimes if I ctrl-alt-del I'm sent back to the login screen and from
  there I can resume the session.

  everything was working fine with my previous (1920x1080) display, but
  since I switched to a 3840x2160 display the only reliable solution to
  get the computer back from blanking is pressing the power button. I
  can then see the shutdown "splash" and after powering it back again
  everything is back to normal. until it blanks the screen again
  obviusly

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-78.99-generic 4.4.62
  Uname: Linux 4.4.0-78-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Mon May 22 19:16:43 2017
  InstallationDate: Installed on 2015-12-27 (512 days ago)
  InstallationMedia: Xubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  SourcePackage: xorg
  UpgradeStatus: Upgraded to xenial on 2016-04-27 (389 days ago)

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


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

[Desktop-packages] [Bug 1890572] Re: USB backend never ends if the printer is not connected

[Alejandro]

Hi Sebastian,

the patch set the job state to backend error.

I don't think openprinting is the right error here. The problem is in
the backend (the USB backend) when it's not possible to communicate with
a USB printer. This usually means that the printer is not connected.

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

Title:
  USB backend never ends if the printer is not connected

Status in cups package in Ubuntu:
  New

Bug description:
  USB backend never ends if the printer is not connected. We have been
  able to identify a infinity loop in print_device function in usb-
  libusb.c file:

  ```
    fprintf(stderr, "DEBUG: Printing on printer with URI: %s\n", uri);
    while ((g.printer = find_device(print_cb, uri)) == NULL)
    {
  _cupsLangPrintFilter(stderr, "INFO",
  _("Waiting for printer to become available."));
  sleep(5);
    }
  ```

  It's also easy to test by invoking the backend by hand:

  ```
  # export DEVICE_URI='usb://Printer/Model?serial=?'
  # /usr/lib/cups/backend/usb 0 root title 1 '' data.file

  DEBUG: Loading USB quirks from "/usr/share/cups/usb".
  DEBUG: Loaded 159 quirks.
  DEBUG: Printing on printer with URI: usb://Printer/Model?serial=?
  DEBUG: libusb_get_device_list=6
  INFO: Waiting for printer to become available.
  DEBUG: libusb_get_device_list=6
  INFO: Waiting for printer to become available.
  DEBUG: libusb_get_device_list=6
  INFO: Waiting for printer to become available.
  DEBUG: libusb_get_device_list=6
  INFO: Waiting for printer to become available.
  DEBUG: libusb_get_device_list=6
  INFO: Waiting for printer to become available.
  ...

  ```

  Setting a job timeout policy or manually stopping work are not options
  for us. We may have jobs that take hours to complete.

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

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

[Desktop-packages] [Bug 1923109] [NEW] Power daemon does not sense when AC adapter is plugged and shuts the machine down

[Alejandro Wills]

Public bug reported:

If any power-related app is open, or if I let the "low battery"
notification go away, the control center does not report the connection
of an AC Adapter and eventually powers the machine down.

uname -a returns:

Linux maelstrom-x509dj-m509dj 5.8.0-48-generic #54-Ubuntu SMP Fri Mar 19
14:25:20 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux

sudo dmesg | tail returns:

[sudo] password for maelstrom: 
[3.835417] ---[ end trace d10ad7cd4552be52 ]---
[4.566546] input: HD-Audio Generic Headphone as 
/devices/pci:00/:00:08.1/:03:00.6/sound/card1/input21
[4.574762] ACPI Warning: \_SB.PCI0.GPP0.VGA._DSM: Argument #4 type mismatch 
- Found [Buffer], ACPI requires [Package] (20200528/nsarguments-59)
[7.687695] IPv6: ADDRCONF(NETDEV_CHANGE): wlp2s0: link becomes ready
[8.797016] rfkill: input handler disabled
[   16.687324] Bluetooth: RFCOMM TTY layer initialized
[   16.687331] Bluetooth: RFCOMM socket layer initialized
[   16.687340] Bluetooth: RFCOMM ver 1.11
[   16.870417] rfkill: input handler enabled
[   20.199148] rfkill: input handler disabled

ProblemType: Bug
DistroRelease: Ubuntu 20.10
Package: gnome-control-center 1:3.38.3-0ubuntu1
ProcVersionSignature: Ubuntu 5.8.0-48.54-generic 5.8.18
Uname: Linux 5.8.0-48-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu50.5
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Thu Apr  8 16:36:51 2021
ExecutablePath: /usr/bin/gnome-control-center
InstallationDate: Installed on 2021-03-02 (37 days ago)
InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
ProcEnviron:
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: gnome-control-center
UpgradeStatus: No upgrade log present (probably fresh install)

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

Title:
  Power daemon does not sense when AC adapter is plugged and shuts the
  machine down

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

Bug description:
  If any power-related app is open, or if I let the "low battery"
  notification go away, the control center does not report the
  connection of an AC Adapter and eventually powers the machine down.

  uname -a returns:

  Linux maelstrom-x509dj-m509dj 5.8.0-48-generic #54-Ubuntu SMP Fri Mar
  19 14:25:20 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux

  sudo dmesg | tail returns:

  [sudo] password for maelstrom: 
  [3.835417] ---[ end trace d10ad7cd4552be52 ]---
  [4.566546] input: HD-Audio Generic Headphone as 
/devices/pci:00/:00:08.1/:03:00.6/sound/card1/input21
  [4.574762] ACPI Warning: \_SB.PCI0.GPP0.VGA._DSM: Argument #4 type 
mismatch - Found [Buffer], ACPI requires [Package] (20200528/nsarguments-59)
  [7.687695] IPv6: ADDRCONF(NETDEV_CHANGE): wlp2s0: link becomes ready
  [8.797016] rfkill: input handler disabled
  [   16.687324] Bluetooth: RFCOMM TTY layer initialized
  [   16.687331] Bluetooth: RFCOMM socket layer initialized
  [   16.687340] Bluetooth: RFCOMM ver 1.11
  [   16.870417] rfkill: input handler enabled
  [   20.199148] rfkill: input handler disabled

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: gnome-control-center 1:3.38.3-0ubuntu1
  ProcVersionSignature: Ubuntu 5.8.0-48.54-generic 5.8.18
  Uname: Linux 5.8.0-48-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu50.5
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Apr  8 16:36:51 2021
  ExecutablePath: /usr/bin/gnome-control-center
  InstallationDate: Installed on 2021-03-02 (37 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-control-center
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1846699] Re: Missing mechanism in Glibmm that prevents the support of some themes (CSS) in Gtkmm

[Alejandro Claro]

Hi @Sebastien,

I don't really understand the last comment. What do you mean by
"However, I am closing it because the bug has been fixed in the latest
development version of Ubuntu."?

The issue is present in the last version of the package for Ubuntu 18.04
LTS. The problem is that we can NOT migrate our systems to Ubuntu 20.04
LTS.

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

Title:
  Missing mechanism in Glibmm that prevents the support of some themes
  (CSS) in Gtkmm

Status in glibmm2.4 package in Ubuntu:
  Fix Committed

Bug description:
  In  GTK+ 3.20 the theming mechanics was heavily changed.

  https://developer.gnome.org/gtk3/stable/ch32s10.html

  One of the major changes was the use of element names much more than
  style classes. For this the function gtk_widget_class_set_css_name()
  was added to t he API and used to assign the element names. However,
  this was not added in GTKmm, making impossible to assign element names
  in custom widget, and no automatically assignment was developed in
  GTKmm's Widget class in order to be able to identify widget classes in
  the theming system (CSS).

  The problem was discussed and tracked up to Glibmm in GNOME bug
  tracking system:

  https://gitlab.gnome.org/GNOME/gtkmm/issues/17
  https://gitlab.gnome.org/GNOME/glibmm/issues/33

  The issues are due to the lack of the mechanism to call
  gtk_widget_class_set_css_name() function in the instance init
  function.

  This was solved in Glibmm2.4 2.60, however Ubuntu is still behind this
  version and it's affecting some of our products.

  We have applied a patch to the current version (2.56) of Glibmm2.4 in
  Ubuntu 18.04 successfully, but I would like to ask you to consider
  upgrading the version of Glibmm in the official repository or apply
  the patch.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glibmm2.4/+bug/1846699/+subscriptions

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

[Desktop-packages] [Bug 1841793] Re: Don't update to 2.65.3

[Alejandro Claro]

Thanks @sebastien!

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

Title:
  Don't update to 2.65.3

Status in glibmm2.4 package in Ubuntu:
  Triaged

Bug description:
  The .news entry starts with

  '2.63.1: (unstable):
  Distro packagers should probably not package this yet.'

  Let's follow upstream's advice there

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glibmm2.4/+bug/1841793/+subscriptions

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

[Desktop-packages] [Bug 1846699] Re: Missing mechanism in Glibmm that prevents the support of some themes (CSS) in Gtkmm

[Alejandro Claro]

HI, can someone please sponsor this patch or the upgrade of the Glibmm
package to at least version 2.60?

We have some products that are affected by this problem, and we can not
upgrade to Ubuntu 20.04 yet.

Thanks.

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

Title:
  Missing mechanism in Glibmm that prevents the support of some themes
  (CSS) in Gtkmm

Status in glibmm2.4 package in Ubuntu:
  New

Bug description:
  In  GTK+ 3.20 the theming mechanics was heavily changed.

  https://developer.gnome.org/gtk3/stable/ch32s10.html

  One of the major changes was the use of element names much more than
  style classes. For this the function gtk_widget_class_set_css_name()
  was added to t he API and used to assign the element names. However,
  this was not added in GTKmm, making impossible to assign element names
  in custom widget, and no automatically assignment was developed in
  GTKmm's Widget class in order to be able to identify widget classes in
  the theming system (CSS).

  The problem was discussed and tracked up to Glibmm in GNOME bug
  tracking system:

  https://gitlab.gnome.org/GNOME/gtkmm/issues/17
  https://gitlab.gnome.org/GNOME/glibmm/issues/33

  The issues are due to the lack of the mechanism to call
  gtk_widget_class_set_css_name() function in the instance init
  function.

  This was solved in Glibmm2.4 2.60, however Ubuntu is still behind this
  version and it's affecting some of our products.

  We have applied a patch to the current version (2.56) of Glibmm2.4 in
  Ubuntu 18.04 successfully, but I would like to ask you to consider
  upgrading the version of Glibmm in the official repository or apply
  the patch.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glibmm2.4/+bug/1846699/+subscriptions

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

[Desktop-packages] [Bug 1841793] Re: Don't update to 2.65.3

[Alejandro Claro]

Please can somebody indicate whether this is still an issue or not?

We have some products that cannot be upgraded to Ubuntu 20.04 yet, and
the version of Glibmm in Ubuntu 1804 (Glibmm 2.56) has some important
compatibility issues after some design changes in glib. The mechanisms
to solve this issue were introduced in Glibmm 2.60:

https://developer.gnome.org/glibmm/2.60/classGlib_1_1ExtraClassInit.html

I would like to ask to please increase the version in Ubuntu 18.04, to
at least Glibmm 2.60 or to include a patch to introduce the solution.
The patch is included in this issue report:

https://bugs.launchpad.net/ubuntu/+source/glibmm2.4/+bug/1846699

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

Title:
  Don't update to 2.65.3

Status in glibmm2.4 package in Ubuntu:
  Triaged

Bug description:
  The .news entry starts with

  '2.63.1: (unstable):
  Distro packagers should probably not package this yet.'

  Let's follow upstream's advice there

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glibmm2.4/+bug/1841793/+subscriptions

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

[Desktop-packages] [Bug 1883798] Re: package libjpeg-turbo8 2.0.3-0ubuntu1 failed to install/upgrade: trying to overwrite shared '/usr/share/doc/libjpeg-turbo8/changelog.Debian.gz', which is different

[Alejandro Jesus Huamantuma Anco]

Hi. I installed packettracer. Is there any solution?

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

Title:
  package libjpeg-turbo8 2.0.3-0ubuntu1 failed to install/upgrade:
  trying to overwrite shared '/usr/share/doc/libjpeg-
  turbo8/changelog.Debian.gz', which is different from other instances
  of package libjpeg-turbo8:amd64

Status in libjpeg-turbo package in Ubuntu:
  Confirmed

Bug description:
  not install file !!! packettracer

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: libjpeg-turbo8 2.0.3-0ubuntu1
  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.2
  AptOrdering:
   libjpeg-turbo8:amd64: Install
   NULL: ConfigurePending
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Wed Jun 17 03:37:01 2020
  DpkgTerminalLog:
   Preparing to unpack .../libjpeg-turbo8_2.0.3-0ubuntu1.20.04.1_amd64.deb ...
   Unpacking libjpeg-turbo8:amd64 (2.0.3-0ubuntu1.20.04.1) over 
(2.0.3-0ubuntu1) ...
   dpkg: error processing archive 
/var/cache/apt/archives/libjpeg-turbo8_2.0.3-0ubuntu1.20.04.1_amd64.deb 
(--unpack):
trying to overwrite shared 
'/usr/share/doc/libjpeg-turbo8/changelog.Debian.gz', which is different from 
other instances of package libjpeg-turbo8:amd64
  ErrorMessage: trying to overwrite shared 
'/usr/share/doc/libjpeg-turbo8/changelog.Debian.gz', which is different from 
other instances of package libjpeg-turbo8:amd64
  InstallationDate: Installed on 2020-06-16 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 
3.8.2-0ubuntu2
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.19.7ubuntu3
   apt  2.0.2ubuntu0.1
  SourcePackage: libjpeg-turbo
  Title: package libjpeg-turbo8 2.0.3-0ubuntu1 failed to install/upgrade: 
trying to overwrite shared '/usr/share/doc/libjpeg-turbo8/changelog.Debian.gz', 
which is different from other instances of package libjpeg-turbo8:amd64
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libjpeg-turbo/+bug/1883798/+subscriptions

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

[Desktop-packages] [Bug 1890572] Re: USB backend never ends if the printer is not connected

[Alejandro Claro]

We have prepared a patch for the package in Ubuntu 18.04 (CUPS 2.2.7).
We would like to request to include a solution like this for at least
Ubuntu 18.04.

We also made a pull request in the official CUPS repository:

https://github.com/apple/cups/issues/5817
https://github.com/apple/cups/pull/5818

However, we don't have plans to upgrade or change the distribution we
use (Ubuntu 18.04), and this issue is affecting us considerably.

** Bug watch added: github.com/apple/cups/issues #5817
   https://github.com/apple/cups/issues/5817

** Patch added: "usb-libusb.c.patch"
   
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1890572/+attachment/5399506/+files/usb-libusb.c.patch

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

Title:
  USB backend never ends if the printer is not connected

Status in cups package in Ubuntu:
  New

Bug description:
  USB backend never ends if the printer is not connected. We have been
  able to identify a infinity loop in print_device function in usb-
  libusb.c file:

  ```
    fprintf(stderr, "DEBUG: Printing on printer with URI: %s\n", uri);
    while ((g.printer = find_device(print_cb, uri)) == NULL)
    {
  _cupsLangPrintFilter(stderr, "INFO",
  _("Waiting for printer to become available."));
  sleep(5);
    }
  ```

  It's also easy to test by invoking the backend by hand:

  ```
  # export DEVICE_URI='usb://Printer/Model?serial=?'
  # /usr/lib/cups/backend/usb 0 root title 1 '' data.file

  DEBUG: Loading USB quirks from "/usr/share/cups/usb".
  DEBUG: Loaded 159 quirks.
  DEBUG: Printing on printer with URI: usb://Printer/Model?serial=?
  DEBUG: libusb_get_device_list=6
  INFO: Waiting for printer to become available.
  DEBUG: libusb_get_device_list=6
  INFO: Waiting for printer to become available.
  DEBUG: libusb_get_device_list=6
  INFO: Waiting for printer to become available.
  DEBUG: libusb_get_device_list=6
  INFO: Waiting for printer to become available.
  DEBUG: libusb_get_device_list=6
  INFO: Waiting for printer to become available.
  ...

  ```

  Setting a job timeout policy or manually stopping work are not options
  for us. We may have jobs that take hours to complete.

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

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

[Desktop-packages] [Bug 1890763] [NEW] I suspect Firefox cause journal problem, doing lags of keyboard and mouse input, or slow apps

[Alejandro Gómez]

Public bug reported:

I have a new installation of Ubuntu 20.04 LTS.

Two weeks ago I experienced several issues:
-slow boot
-disk failures (inodes corrupted, superblock invalid, read-only at start)
-Firefox slower to respond at start, can't get the previous session
-systemd-journald error trying to write on read-only filesystem
-/tmpfs read-only
-/var/log/journal with 1.6 GB
-snap-store process with the highest memory use

Yesterday I have to abandon the use of this Ubuntu 20.04, because the
lack of trust

Today, I trim the max size of journal files (100 MB), change resolution
of display and avoid using Firefox (instead using Chromium); however,
this report invoke Firefox; during 2 hours I been working as smooth and
fine as always.

Finally, I use Ubuntu in a diary basis; in this device I have versions
16.04, 18.04 and 20.04. Only 20.04 give this problems.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: firefox 79.0+build1-0ubuntu0.20.04.1
ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
Uname: Linux 5.4.0-42-generic x86_64
AddonCompatCheckDisabled: False
ApportVersion: 2.20.11-0ubuntu27.6
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC1:  alejandro   2458 F pulseaudio
 /dev/snd/controlC0:  alejandro   2458 F pulseaudio
BuildID: 20200720193547
CasperMD5CheckResult: skip
Channel: Unavailable
CurrentDesktop: ubuntu:GNOME
Date: Thu Aug  6 21:48:33 2020
DefaultProfileExtensions: extensions.sqlite corrupt or missing
DefaultProfileIncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
DefaultProfileLocales: extensions.sqlite corrupt or missing
DefaultProfilePrefErrors: Unexpected character ',' before close parenthesis @ 
/usr/lib/firefox/omni.ja:greprefs.js:725
DefaultProfileThemes: extensions.sqlite corrupt or missing
ForcedLayersAccel: False
InstallationDate: Installed on 2020-05-19 (79 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
IpRoute:
 default via 192.168.1.254 dev wlp2s0 proto dhcp metric 600 
 169.254.0.0/16 dev wlp2s0 scope link metric 1000 
 192.168.1.0/24 dev wlp2s0 proto kernel scope link src 192.168.1.64 metric 600
Profile0Extensions: extensions.sqlite corrupt or missing
Profile0IncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
Profile0Locales: extensions.sqlite corrupt or missing
Profile0PrefErrors: Unexpected character ',' before close parenthesis @ 
/usr/lib/firefox/omni.ja:greprefs.js:725
Profile0PrefSources: prefs.js
Profile0Themes: extensions.sqlite corrupt or missing
Profiles:
 Profile1 (Default) - LastVersion=None/None (Out of date)
 Profile0 - LastVersion=79.0/20200720193547
RunningIncompatibleAddons: False
SourcePackage: firefox
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 08/24/2015
dmi.bios.vendor: LENOVO
dmi.bios.version: A4CN40WW (V 2.09)
dmi.board.asset.tag: No Asset Tag
dmi.board.name: Lancer 5B3
dmi.board.vendor: LENOVO
dmi.board.version: SDK0J40688SDK0J40688 WIN
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Lenovo Z50-75
dmi.modalias: 
dmi:bvnLENOVO:bvrA4CN40WW(V2.09):bd08/24/2015:svnLENOVO:pn80EC:pvrLenovoZ50-75:rvnLENOVO:rnLancer5B3:rvrSDK0J40688SDK0J40688WIN:cvnLENOVO:ct10:cvrLenovoZ50-75:
dmi.product.family: IDEAPAD
dmi.product.name: 80EC
dmi.product.sku: LENOVO_MT_80EC0_BU_idea_FM_Lenovo Z50-75
dmi.product.version: Lenovo Z50-75
dmi.sys.vendor: LENOVO

** Affects: firefox (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 firefox in Ubuntu.
https://bugs.launchpad.net/bugs/1890763

Title:
  I suspect Firefox cause journal problem, doing lags of keyboard and
  mouse input, or slow apps

Status in firefox package in Ubuntu:
  New

Bug description:
  I have a new installation of Ubuntu 20.04 LTS.

  Two weeks ago I experienced several issues:
  -slow boot
  -disk failures (inodes corrupted, superblock invalid, read-only at start)
  -Firefox slower to respond at start, can't get the previous session
  -systemd-journald error trying to write on read-only filesystem
  -/tmpfs read-only
  -/var/log/journal with 1.6 GB
  -snap-store process with the highest memory use

  Yesterday I have to abandon the use of this Ubuntu 20.04, because the
  lack of trust

  Today, I trim the max size of journal files (100 MB), change
  resolution of display and avoid using Firefox (instead using
  Chromium); however, this report invoke Firefox; during 2 hours I been
  working as smooth and fine as always.

  Finally, I use Ubuntu in a diary basis; in this device I have versions
  16.04, 18.04 and 20.04. Only 20.04 give this problems.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: firefox 79.0+build1-0ubuntu

[Desktop-packages] [Bug 1890572] Re: USB backend never ends if the printer is not connected

[Alejandro Claro]

** Description changed:

- USB backend never ends if the printer is not connected. we have been
+ USB backend never ends if the printer is not connected. We have been
  able to identify a infinity loop in print_device function in usb-
  libusb.c file:
  
  ```
-   fprintf(stderr, "DEBUG: Printing on printer with URI: %s\n", uri);
-   while ((g.printer = find_device(print_cb, uri)) == NULL)
-   {
- _cupsLangPrintFilter(stderr, "INFO",
-_("Waiting for printer to become available."));
- sleep(5);
-   }
+   fprintf(stderr, "DEBUG: Printing on printer with URI: %s\n", uri);
+   while ((g.printer = find_device(print_cb, uri)) == NULL)
+   {
+ _cupsLangPrintFilter(stderr, "INFO",
+ _("Waiting for printer to become available."));
+ sleep(5);
+   }
  ```
  
  It's also easy to test by invoking the backend by hand:
- 
  
  ```
  # export DEVICE_URI='usb://Printer/Model?serial=?'
  # /usr/lib/cups/backend/usb 0 root title 1 '' data.file
  
  DEBUG: Loading USB quirks from "/usr/share/cups/usb".
  DEBUG: Loaded 159 quirks.
  DEBUG: Printing on printer with URI: usb://Brother/PJ-773?serial=?
  DEBUG: libusb_get_device_list=6
  INFO: Waiting for printer to become available.
  
  DEBUG: libusb_get_device_list=6
  INFO: Waiting for printer to become available.
  DEBUG: libusb_get_device_list=6
  INFO: Waiting for printer to become available.
  DEBUG: libusb_get_device_list=6
  INFO: Waiting for printer to become available.
  DEBUG: libusb_get_device_list=6
  INFO: Waiting for printer to become available.
  ...
  
  ```
  
- Setting a job timeout policy or stopping the job by hand are not options
- for us. We can have job that take up to an hour to complete.
+ Setting a work timeout policy or manually stopping work are not options
+ for us. We may have jobs that take up to an hour to complete.

** Description changed:

  USB backend never ends if the printer is not connected. We have been
  able to identify a infinity loop in print_device function in usb-
  libusb.c file:
  
  ```
    fprintf(stderr, "DEBUG: Printing on printer with URI: %s\n", uri);
    while ((g.printer = find_device(print_cb, uri)) == NULL)
    {
  _cupsLangPrintFilter(stderr, "INFO",
  _("Waiting for printer to become available."));
  sleep(5);
    }
  ```
  
  It's also easy to test by invoking the backend by hand:
  
  ```
  # export DEVICE_URI='usb://Printer/Model?serial=?'
  # /usr/lib/cups/backend/usb 0 root title 1 '' data.file
  
  DEBUG: Loading USB quirks from "/usr/share/cups/usb".
  DEBUG: Loaded 159 quirks.
- DEBUG: Printing on printer with URI: usb://Brother/PJ-773?serial=?
+ DEBUG: Printing on printer with URI: usb://Printer/Model?serial=?
  DEBUG: libusb_get_device_list=6
  INFO: Waiting for printer to become available.
  
  DEBUG: libusb_get_device_list=6
  INFO: Waiting for printer to become available.
  DEBUG: libusb_get_device_list=6
  INFO: Waiting for printer to become available.
  DEBUG: libusb_get_device_list=6
  INFO: Waiting for printer to become available.
  DEBUG: libusb_get_device_list=6
  INFO: Waiting for printer to become available.
  ...
  
  ```
  
  Setting a work timeout policy or manually stopping work are not options
  for us. We may have jobs that take up to an hour to complete.

** Description changed:

  USB backend never ends if the printer is not connected. We have been
  able to identify a infinity loop in print_device function in usb-
  libusb.c file:
  
  ```
    fprintf(stderr, "DEBUG: Printing on printer with URI: %s\n", uri);
    while ((g.printer = find_device(print_cb, uri)) == NULL)
    {
  _cupsLangPrintFilter(stderr, "INFO",
  _("Waiting for printer to become available."));
  sleep(5);
    }
  ```
  
  It's also easy to test by invoking the backend by hand:
  
  ```
  # export DEVICE_URI='usb://Printer/Model?serial=?'
  # /usr/lib/cups/backend/usb 0 root title 1 '' data.file
  
  DEBUG: Loading USB quirks from "/usr/share/cups/usb".
  DEBUG: Loaded 159 quirks.
  DEBUG: Printing on printer with URI: usb://Printer/Model?serial=?
  DEBUG: libusb_get_device_list=6
  INFO: Waiting for printer to become available.
- 
  DEBUG: libusb_get_device_list=6
  INFO: Waiting for printer to become available.
  DEBUG: libusb_get_device_list=6
  INFO: Waiting for printer to become available.
  DEBUG: libusb_get_device_list=6
  INFO: Waiting for printer to become available.
  DEBUG: libusb_get_device_list=6
  INFO: Waiting for printer to become available.
  ...
  
  ```
  
- Setting a work timeout policy or manually stopping work are not options
+ Setting a job timeout policy or manually stopping work are not options
  for us. We may have jobs that take up to an hour to complete.

** Description changed:

  USB backend never ends if the printer is not connected. We have been
  able to identify a infinity loop in print_device function in usb-
  libusb.c file:
  
  ```
    fprintf(stderr, "DEBUG: Printing on printer with URI: %s\n", uri);
    while ((g.p

[Desktop-packages] [Bug 1890572] [NEW] USB backend never ends if the printer is not connected

[Alejandro Claro]

Public bug reported:

USB backend never ends if the printer is not connected. we have been
able to identify a infinity loop in print_device function in usb-
libusb.c file:

```
  fprintf(stderr, "DEBUG: Printing on printer with URI: %s\n", uri);
  while ((g.printer = find_device(print_cb, uri)) == NULL)
  {
_cupsLangPrintFilter(stderr, "INFO",
 _("Waiting for printer to become available."));
sleep(5);
  }
```

It's also easy to test by invoking the backend by hand:


```
# export DEVICE_URI='usb://Printer/Model?serial=?'
# /usr/lib/cups/backend/usb 0 root title 1 '' data.file

DEBUG: Loading USB quirks from "/usr/share/cups/usb".
DEBUG: Loaded 159 quirks.
DEBUG: Printing on printer with URI: usb://Brother/PJ-773?serial=?
DEBUG: libusb_get_device_list=6
INFO: Waiting for printer to become available.

DEBUG: libusb_get_device_list=6
INFO: Waiting for printer to become available.
DEBUG: libusb_get_device_list=6
INFO: Waiting for printer to become available.
DEBUG: libusb_get_device_list=6
INFO: Waiting for printer to become available.
DEBUG: libusb_get_device_list=6
INFO: Waiting for printer to become available.
...

```

Setting a job timeout policy or stopping the job by hand are not options
for us. We can have job that take up to an hour to complete.

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

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

Title:
  USB backend never ends if the printer is not connected

Status in cups package in Ubuntu:
  New

Bug description:
  USB backend never ends if the printer is not connected. we have been
  able to identify a infinity loop in print_device function in usb-
  libusb.c file:

  ```
fprintf(stderr, "DEBUG: Printing on printer with URI: %s\n", uri);
while ((g.printer = find_device(print_cb, uri)) == NULL)
{
  _cupsLangPrintFilter(stderr, "INFO",
 _("Waiting for printer to become available."));
  sleep(5);
}
  ```

  It's also easy to test by invoking the backend by hand:

  
  ```
  # export DEVICE_URI='usb://Printer/Model?serial=?'
  # /usr/lib/cups/backend/usb 0 root title 1 '' data.file

  DEBUG: Loading USB quirks from "/usr/share/cups/usb".
  DEBUG: Loaded 159 quirks.
  DEBUG: Printing on printer with URI: usb://Brother/PJ-773?serial=?
  DEBUG: libusb_get_device_list=6
  INFO: Waiting for printer to become available.

  DEBUG: libusb_get_device_list=6
  INFO: Waiting for printer to become available.
  DEBUG: libusb_get_device_list=6
  INFO: Waiting for printer to become available.
  DEBUG: libusb_get_device_list=6
  INFO: Waiting for printer to become available.
  DEBUG: libusb_get_device_list=6
  INFO: Waiting for printer to become available.
  ...

  ```

  Setting a job timeout policy or stopping the job by hand are not
  options for us. We can have job that take up to an hour to complete.

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

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

[Desktop-packages] [Bug 1846699] Re: Missing mechanism in Glibmm that prevents the support of some themes (CSS) in Gtkmm

[Alejandro Claro]

Patch for version 2.56 that incorporates a fix related to the theme
management in version 2.60

** Patch added: "Patch for version 2.56 that incorporates a fix related to the 
theme management in version 2.60"
   
https://bugs.launchpad.net/ubuntu/+source/glibmm2.4/+bug/1846699/+attachment/5390142/+files/0001-Object-construction-Add-custom-class-init-and-instan.patch

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

Title:
  Missing mechanism in Glibmm that prevents the support of some themes
  (CSS) in Gtkmm

Status in glibmm2.4 package in Ubuntu:
  New

Bug description:
  In  GTK+ 3.20 the theming mechanics was heavily changed.

  https://developer.gnome.org/gtk3/stable/ch32s10.html

  One of the major changes was the use of element names much more than
  style classes. For this the function gtk_widget_class_set_css_name()
  was added to t he API and used to assign the element names. However,
  this was not added in GTKmm, making impossible to assign element names
  in custom widget, and no automatically assignment was developed in
  GTKmm's Widget class in order to be able to identify widget classes in
  the theming system (CSS).

  The problem was discussed and tracked up to Glibmm in GNOME bug
  tracking system:

  https://gitlab.gnome.org/GNOME/gtkmm/issues/17
  https://gitlab.gnome.org/GNOME/glibmm/issues/33

  The issues are due to the lack of the mechanism to call
  gtk_widget_class_set_css_name() function in the instance init
  function.

  This was solved in Glibmm2.4 2.60, however Ubuntu is still behind this
  version and it's affecting some of our products.

  We have applied a patch to the current version (2.56) of Glibmm2.4 in
  Ubuntu 18.04 successfully, but I would like to ask you to consider
  upgrading the version of Glibmm in the official repository or apply
  the patch.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glibmm2.4/+bug/1846699/+subscriptions

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

[Desktop-packages] [Bug 1846699] Re: Missing mechanism in Glibmm that prevents the support of some themes (CSS) in Gtkmm

[Alejandro Claro]

Can anybody look at this issue?

We have a patch to solve this in the Ubuntu 18.04 package (version
v2.56) and we are also able to compile and use version 2.60. However, we
will like to be included in the official distribution files. This
simplifies our deployment.

If we provide the patch of the upgrade to v2.6x will anybody review it?

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

Title:
  Missing mechanism in Glibmm that prevents the support of some themes
  (CSS) in Gtkmm

Status in glibmm2.4 package in Ubuntu:
  New

Bug description:
  In  GTK+ 3.20 the theming mechanics was heavily changed.

  https://developer.gnome.org/gtk3/stable/ch32s10.html

  One of the major changes was the use of element names much more than
  style classes. For this the function gtk_widget_class_set_css_name()
  was added to t he API and used to assign the element names. However,
  this was not added in GTKmm, making impossible to assign element names
  in custom widget, and no automatically assignment was developed in
  GTKmm's Widget class in order to be able to identify widget classes in
  the theming system (CSS).

  The problem was discussed and tracked up to Glibmm in GNOME bug
  tracking system:

  https://gitlab.gnome.org/GNOME/gtkmm/issues/17
  https://gitlab.gnome.org/GNOME/glibmm/issues/33

  The issues are due to the lack of the mechanism to call
  gtk_widget_class_set_css_name() function in the instance init
  function.

  This was solved in Glibmm2.4 2.60, however Ubuntu is still behind this
  version and it's affecting some of our products.

  We have applied a patch to the current version (2.56) of Glibmm2.4 in
  Ubuntu 18.04 successfully, but I would like to ask you to consider
  upgrading the version of Glibmm in the official repository or apply
  the patch.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glibmm2.4/+bug/1846699/+subscriptions

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

[Desktop-packages] [Bug 1883409] [NEW] package cups-client 2.3.1-9ubuntu1.1 failed to install/upgrade: no se pudieron copiar los datos extraídos de './usr/bin/lpoptions' a '/usr/bin/lpoptions.dpkg-new

[Alejandro]

Public bug reported:

no deja de molesrae

ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: cups-client 2.3.1-9ubuntu1.1
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.2
Architecture: amd64
CasperMD5CheckResult: skip
Date: Sat Jun 13 06:32:25 2020
ErrorMessage: no se pudieron copiar los datos extraídos de 
'./usr/bin/lpoptions' a '/usr/bin/lpoptions.dpkg-new': fin de fichero o de 
flujo inesperado
InstallationDate: Installed on 2020-06-13 (1 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: No 
destinations added.
MachineType: Dell Inc. Latitude E6400
Papersize: letter
ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-5.4.0-37-generic 
root=UUID=1bcab7a8-d4a0-4bae-adfc-3e1e7fa36a9c ro quiet splash vt.handoff=7
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-37-generic 
root=UUID=1bcab7a8-d4a0-4bae-adfc-3e1e7fa36a9c ro quiet splash vt.handoff=7
Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 
3.8.2-0ubuntu2
PythonDetails: N/A
RelatedPackageVersions:
 dpkg 1.19.7ubuntu3
 apt  2.0.2ubuntu0.1
SourcePackage: cups
Title: package cups-client 2.3.1-9ubuntu1.1 failed to install/upgrade: no se 
pudieron copiar los datos extraídos de './usr/bin/lpoptions' a 
'/usr/bin/lpoptions.dpkg-new': fin de fichero o de flujo inesperado
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 06/04/2013
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A34
dmi.board.name: 0G866N
dmi.board.vendor: Dell Inc.
dmi.chassis.type: 8
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvrA34:bd06/04/2013:svnDellInc.:pnLatitudeE6400:pvr:rvnDellInc.:rn0G866N:rvr:cvnDellInc.:ct8:cvr:
dmi.product.name: Latitude E6400
dmi.sys.vendor: Dell Inc.

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


** Tags: amd64 apport-package focal

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

Title:
  package cups-client 2.3.1-9ubuntu1.1 failed to install/upgrade: no se
  pudieron copiar los datos extraídos de './usr/bin/lpoptions' a
  '/usr/bin/lpoptions.dpkg-new': fin de fichero o de flujo inesperado

Status in cups package in Ubuntu:
  New

Bug description:
  no deja de molesrae

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: cups-client 2.3.1-9ubuntu1.1
  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.2
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Sat Jun 13 06:32:25 2020
  ErrorMessage: no se pudieron copiar los datos extraídos de 
'./usr/bin/lpoptions' a '/usr/bin/lpoptions.dpkg-new': fin de fichero o de 
flujo inesperado
  InstallationDate: Installed on 2020-06-13 (1 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: No 
destinations added.
  MachineType: Dell Inc. Latitude E6400
  Papersize: letter
  ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-5.4.0-37-generic 
root=UUID=1bcab7a8-d4a0-4bae-adfc-3e1e7fa36a9c ro quiet splash vt.handoff=7
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-37-generic 
root=UUID=1bcab7a8-d4a0-4bae-adfc-3e1e7fa36a9c ro quiet splash vt.handoff=7
  Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 
3.8.2-0ubuntu2
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.19.7ubuntu3
   apt  2.0.2ubuntu0.1
  SourcePackage: cups
  Title: package cups-client 2.3.1-9ubuntu1.1 failed to install/upgrade: no se 
pudieron copiar los datos extraídos de './usr/bin/lpoptions' a 
'/usr/bin/lpoptions.dpkg-new': fin de fichero o de flujo inesperado
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/04/2013
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A34
  dmi.board.name: 0G866N
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA34:bd06/04/2013:svnDellInc.:pnLatitudeE6400:pvr:rvnDellInc.:rn0G866N:rvr:cvnDellInc.:ct8:cvr:
  dmi.product.name: Latitude E6400
  dmi.sys.vendor: Dell Inc.

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

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

[Desktop-packages] [Bug 1883408] [NEW] package cups-client 2.3.1-9ubuntu1.1 failed to install/upgrade: no se pudieron copiar los datos extraídos de './usr/bin/lpoptions' a '/usr/bin/lpoptions.dpkg-new

[Alejandro]

Public bug reported:

no deja de molesrae

ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: cups-client 2.3.1-9ubuntu1.1
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.2
Architecture: amd64
CasperMD5CheckResult: skip
Date: Sat Jun 13 06:32:25 2020
ErrorMessage: no se pudieron copiar los datos extraídos de 
'./usr/bin/lpoptions' a '/usr/bin/lpoptions.dpkg-new': fin de fichero o de 
flujo inesperado
InstallationDate: Installed on 2020-06-13 (1 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: No 
destinations added.
MachineType: Dell Inc. Latitude E6400
Papersize: letter
ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-5.4.0-37-generic 
root=UUID=1bcab7a8-d4a0-4bae-adfc-3e1e7fa36a9c ro quiet splash vt.handoff=7
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-37-generic 
root=UUID=1bcab7a8-d4a0-4bae-adfc-3e1e7fa36a9c ro quiet splash vt.handoff=7
Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 
3.8.2-0ubuntu2
PythonDetails: N/A
RelatedPackageVersions:
 dpkg 1.19.7ubuntu3
 apt  2.0.2ubuntu0.1
SourcePackage: cups
Title: package cups-client 2.3.1-9ubuntu1.1 failed to install/upgrade: no se 
pudieron copiar los datos extraídos de './usr/bin/lpoptions' a 
'/usr/bin/lpoptions.dpkg-new': fin de fichero o de flujo inesperado
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 06/04/2013
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A34
dmi.board.name: 0G866N
dmi.board.vendor: Dell Inc.
dmi.chassis.type: 8
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvrA34:bd06/04/2013:svnDellInc.:pnLatitudeE6400:pvr:rvnDellInc.:rn0G866N:rvr:cvnDellInc.:ct8:cvr:
dmi.product.name: Latitude E6400
dmi.sys.vendor: Dell Inc.

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


** Tags: amd64 apport-package focal

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

Title:
  package cups-client 2.3.1-9ubuntu1.1 failed to install/upgrade: no se
  pudieron copiar los datos extraídos de './usr/bin/lpoptions' a
  '/usr/bin/lpoptions.dpkg-new': fin de fichero o de flujo inesperado

Status in cups package in Ubuntu:
  New

Bug description:
  no deja de molesrae

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: cups-client 2.3.1-9ubuntu1.1
  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.2
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Sat Jun 13 06:32:25 2020
  ErrorMessage: no se pudieron copiar los datos extraídos de 
'./usr/bin/lpoptions' a '/usr/bin/lpoptions.dpkg-new': fin de fichero o de 
flujo inesperado
  InstallationDate: Installed on 2020-06-13 (1 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: No 
destinations added.
  MachineType: Dell Inc. Latitude E6400
  Papersize: letter
  ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-5.4.0-37-generic 
root=UUID=1bcab7a8-d4a0-4bae-adfc-3e1e7fa36a9c ro quiet splash vt.handoff=7
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-37-generic 
root=UUID=1bcab7a8-d4a0-4bae-adfc-3e1e7fa36a9c ro quiet splash vt.handoff=7
  Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 
3.8.2-0ubuntu2
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.19.7ubuntu3
   apt  2.0.2ubuntu0.1
  SourcePackage: cups
  Title: package cups-client 2.3.1-9ubuntu1.1 failed to install/upgrade: no se 
pudieron copiar los datos extraídos de './usr/bin/lpoptions' a 
'/usr/bin/lpoptions.dpkg-new': fin de fichero o de flujo inesperado
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/04/2013
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A34
  dmi.board.name: 0G866N
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA34:bd06/04/2013:svnDellInc.:pnLatitudeE6400:pvr:rvnDellInc.:rn0G866N:rvr:cvnDellInc.:ct8:cvr:
  dmi.product.name: Latitude E6400
  dmi.sys.vendor: Dell Inc.

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

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

[Desktop-packages] [Bug 1876594] Re: totem doesn't start on Wayland: Error 71 (Error de protocolo) dispatching to Wayland display

[Alejandro]

WAYLAND_DEBUG=1 totem >& totem-wayland-log.txt
asked in #3

** Attachment added: "WAYLAND_DEBUG=1 totem >& totem-wayland-log.txt"
   
https://bugs.launchpad.net/ubuntu/+source/totem/+bug/1876594/+attachment/5366162/+files/totem-wayland-log.txt

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

Title:
  totem doesn't start on Wayland: Error 71 (Error de protocolo)
  dispatching to Wayland display

Status in totem package in Ubuntu:
  Incomplete

Bug description:
  Gdk-Message: 12:33:12.232: Error 71 (Error de protocolo) dispatching
  to Wayland display.

  
  This error is only visible when starting Totem from Terminal.  Otherwise, 
Totem quietly doesn't start.

  vlc is working fine.

  I'm using Ubuntu 20.04 with Gnome (not Gnome on Xorg).

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: totem 3.34.1-2ubuntu2
  ProcVersionSignature: Ubuntu 5.4.0-28.32-generic 5.4.30
  Uname: Linux 5.4.0-28-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: GNOME
  Date: Sun May  3 12:23:48 2020
  InstallationDate: Installed on 2013-07-11 (2487 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  ProcEnviron:
   LANGUAGE=es_AR:es
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=es_AR.UTF-8
   SHELL=/bin/bash
  SourcePackage: totem
  UpgradeStatus: Upgraded to focal on 2020-04-23 (9 days ago)

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

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

[Desktop-packages] [Bug 1876594] [NEW] totem doesn't start on Wayland

[Alejandro]

Public bug reported:

Gdk-Message: 12:33:12.232: Error 71 (Error de protocolo) dispatching to
Wayland display.


This error is only visible when starting Totem from Terminal.  Otherwise, Totem 
quietly doesn't start.

vlc is working fine.

I'm using Ubuntu 20.04 with Gnome (not Gnome on Xorg).

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: totem 3.34.1-2ubuntu2
ProcVersionSignature: Ubuntu 5.4.0-28.32-generic 5.4.30
Uname: Linux 5.4.0-28-generic x86_64
ApportVersion: 2.20.11-0ubuntu27
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: GNOME
Date: Sun May  3 12:23:48 2020
InstallationDate: Installed on 2013-07-11 (2487 days ago)
InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
ProcEnviron:
 LANGUAGE=es_AR:es
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=es_AR.UTF-8
 SHELL=/bin/bash
SourcePackage: totem
UpgradeStatus: Upgraded to focal on 2020-04-23 (9 days ago)

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


** Tags: amd64 apport-bug focal wayland-session

** Summary changed:

- totem don't start on Wayland
+ totem doesn't start on Wayland

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

Title:
  totem doesn't start on Wayland

Status in totem package in Ubuntu:
  New

Bug description:
  Gdk-Message: 12:33:12.232: Error 71 (Error de protocolo) dispatching
  to Wayland display.

  
  This error is only visible when starting Totem from Terminal.  Otherwise, 
Totem quietly doesn't start.

  vlc is working fine.

  I'm using Ubuntu 20.04 with Gnome (not Gnome on Xorg).

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: totem 3.34.1-2ubuntu2
  ProcVersionSignature: Ubuntu 5.4.0-28.32-generic 5.4.30
  Uname: Linux 5.4.0-28-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: GNOME
  Date: Sun May  3 12:23:48 2020
  InstallationDate: Installed on 2013-07-11 (2487 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  ProcEnviron:
   LANGUAGE=es_AR:es
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=es_AR.UTF-8
   SHELL=/bin/bash
  SourcePackage: totem
  UpgradeStatus: Upgraded to focal on 2020-04-23 (9 days ago)

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

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

[Desktop-packages] [Bug 1849542] Re: Thunderbird empty after update to 19.10

[Loïc Alejandro]

I got it. See it attached.

** Attachment added: "faulty file"
   
https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1849542/+attachment/5299645/+files/global-messages-db.sqlite

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

Title:
  Thunderbird empty after update to 19.10

Status in thunderbird package in Ubuntu:
  Incomplete

Bug description:
  HELP

  Just performed an upgrade from Ubuntu 19.04 to 19.10. Launched
  Thunderbird and the interface is empty. No emails, no folders, no
  calendar, I can't even open the "account settings" window.

  This is a complete disaster. I need thunderbird for my work.

  If I launch TB form terminal I get this:

  lalejand@Gedeon:~$ thunderbird 
  JavaScript error: resource:///modules/gloda/gloda.js, line 1922: TypeError: 
aAttrDef.objectNounDef is undefined
  JavaScript error: resource:///modules/gloda/gloda.js, line 1922: TypeError: 
aAttrDef.objectNounDef is undefined
  JavaScript error: resource:///modules/gloda/gloda.js, line 1922: TypeError: 
aAttrDef.objectNounDef is undefined
  JavaScript error: resource:///modules/gloda/gloda.js, line 1922: TypeError: 
aAttrDef.objectNounDef is undefined
  JavaScript error: resource:///modules/gloda/gloda.js, line 1922: TypeError: 
aAttrDef.objectNounDef is undefined
  JavaScript error: resource:///modules/gloda/gloda.js, line 1922: TypeError: 
aAttrDef.objectNounDef is undefined
  TypeError: aAttrDef.objectNounDef is undefined
  -- Exception object --
  *
  -- Stack Trace --
  defineAttribute@resource:///modules/gloda/gloda.js:1922:5
  defineAttributes@resource:///modules/gloda/fundattr.js:71:35
  init@resource:///modules/gloda/fundattr.js:43:12
  @resource:///modules/gloda/everybody.js:13:15
  @resource:///modules/gloda/public.js:8:57
  
nsAutoCompleteGloda@jar:file:///usr/lib/thunderbird/omni.ja!/components/glautocomp.js:516:32
  createInstance@resource://gre/modules/XPCOMUtils.jsm:433:19
  glodaSearch_XBL_Constructor@chrome://messenger/content/search.xml:73:16
  JavaScript error: chrome://messenger/content/messenger.xul, line 1: 
TypeError: QuickFilterBarMuxer is undefined
  JavaScript error: chrome://messenger/content/msgMail3PaneWindow.js, line 470: 
TypeError: TagUtils is undefined
  JavaScript error: resource:///modules/gloda/gloda.js, line 1922: TypeError: 
aAttrDef.objectNounDef is undefined

  What can I do ?

  Release: Ubuntu 19.10
  Package version: 1:68.1.2+build1-0ubuntu

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

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

[Desktop-packages] [Bug 1849542] Re: Thunderbird empty after update to 19.10

[Loïc Alejandro]

Just deleted global-messages-db.sqlite and now it looks like it works
fine. I hopê I didn't loose anything.

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

Title:
  Thunderbird empty after update to 19.10

Status in thunderbird package in Ubuntu:
  New

Bug description:
  HELP

  Just performed an upgrade from Ubuntu 19.04 to 19.10. Launched
  Thunderbird and the interface is empty. No emails, no folders, no
  calendar, I can't even open the "account settings" window.

  This is a complete disaster. I need thunderbird for my work.

  If I launch TB form terminal I get this:

  lalejand@Gedeon:~$ thunderbird 
  JavaScript error: resource:///modules/gloda/gloda.js, line 1922: TypeError: 
aAttrDef.objectNounDef is undefined
  JavaScript error: resource:///modules/gloda/gloda.js, line 1922: TypeError: 
aAttrDef.objectNounDef is undefined
  JavaScript error: resource:///modules/gloda/gloda.js, line 1922: TypeError: 
aAttrDef.objectNounDef is undefined
  JavaScript error: resource:///modules/gloda/gloda.js, line 1922: TypeError: 
aAttrDef.objectNounDef is undefined
  JavaScript error: resource:///modules/gloda/gloda.js, line 1922: TypeError: 
aAttrDef.objectNounDef is undefined
  JavaScript error: resource:///modules/gloda/gloda.js, line 1922: TypeError: 
aAttrDef.objectNounDef is undefined
  TypeError: aAttrDef.objectNounDef is undefined
  -- Exception object --
  *
  -- Stack Trace --
  defineAttribute@resource:///modules/gloda/gloda.js:1922:5
  defineAttributes@resource:///modules/gloda/fundattr.js:71:35
  init@resource:///modules/gloda/fundattr.js:43:12
  @resource:///modules/gloda/everybody.js:13:15
  @resource:///modules/gloda/public.js:8:57
  
nsAutoCompleteGloda@jar:file:///usr/lib/thunderbird/omni.ja!/components/glautocomp.js:516:32
  createInstance@resource://gre/modules/XPCOMUtils.jsm:433:19
  glodaSearch_XBL_Constructor@chrome://messenger/content/search.xml:73:16
  JavaScript error: chrome://messenger/content/messenger.xul, line 1: 
TypeError: QuickFilterBarMuxer is undefined
  JavaScript error: chrome://messenger/content/msgMail3PaneWindow.js, line 470: 
TypeError: TagUtils is undefined
  JavaScript error: resource:///modules/gloda/gloda.js, line 1922: TypeError: 
aAttrDef.objectNounDef is undefined

  What can I do ?

  Release: Ubuntu 19.10
  Package version: 1:68.1.2+build1-0ubuntu

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

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

[Desktop-packages] [Bug 1849542] [NEW] Thunderbird empty after update to 19.10

[Loïc Alejandro]

Public bug reported:

HELP

Just performed an upgrade from Ubuntu 19.04 to 19.10. Launched
Thunderbird and the interface is empty. No emails, no folders, no
calendar, I can't even open the "account settings" window.

This is a complete disaster. I need thunderbird for my work.

If I launch TB form terminal I get this:

lalejand@Gedeon:~$ thunderbird 
JavaScript error: resource:///modules/gloda/gloda.js, line 1922: TypeError: 
aAttrDef.objectNounDef is undefined
JavaScript error: resource:///modules/gloda/gloda.js, line 1922: TypeError: 
aAttrDef.objectNounDef is undefined
JavaScript error: resource:///modules/gloda/gloda.js, line 1922: TypeError: 
aAttrDef.objectNounDef is undefined
JavaScript error: resource:///modules/gloda/gloda.js, line 1922: TypeError: 
aAttrDef.objectNounDef is undefined
JavaScript error: resource:///modules/gloda/gloda.js, line 1922: TypeError: 
aAttrDef.objectNounDef is undefined
JavaScript error: resource:///modules/gloda/gloda.js, line 1922: TypeError: 
aAttrDef.objectNounDef is undefined
TypeError: aAttrDef.objectNounDef is undefined
-- Exception object --
*
-- Stack Trace --
defineAttribute@resource:///modules/gloda/gloda.js:1922:5
defineAttributes@resource:///modules/gloda/fundattr.js:71:35
init@resource:///modules/gloda/fundattr.js:43:12
@resource:///modules/gloda/everybody.js:13:15
@resource:///modules/gloda/public.js:8:57
nsAutoCompleteGloda@jar:file:///usr/lib/thunderbird/omni.ja!/components/glautocomp.js:516:32
createInstance@resource://gre/modules/XPCOMUtils.jsm:433:19
glodaSearch_XBL_Constructor@chrome://messenger/content/search.xml:73:16
JavaScript error: chrome://messenger/content/messenger.xul, line 1: TypeError: 
QuickFilterBarMuxer is undefined
JavaScript error: chrome://messenger/content/msgMail3PaneWindow.js, line 470: 
TypeError: TagUtils is undefined
JavaScript error: resource:///modules/gloda/gloda.js, line 1922: TypeError: 
aAttrDef.objectNounDef is undefined

What can I do ?

Release: Ubuntu 19.10
Package version: 1:68.1.2+build1-0ubuntu

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

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

Title:
  Thunderbird empty after update to 19.10

Status in thunderbird package in Ubuntu:
  New

Bug description:
  HELP

  Just performed an upgrade from Ubuntu 19.04 to 19.10. Launched
  Thunderbird and the interface is empty. No emails, no folders, no
  calendar, I can't even open the "account settings" window.

  This is a complete disaster. I need thunderbird for my work.

  If I launch TB form terminal I get this:

  lalejand@Gedeon:~$ thunderbird 
  JavaScript error: resource:///modules/gloda/gloda.js, line 1922: TypeError: 
aAttrDef.objectNounDef is undefined
  JavaScript error: resource:///modules/gloda/gloda.js, line 1922: TypeError: 
aAttrDef.objectNounDef is undefined
  JavaScript error: resource:///modules/gloda/gloda.js, line 1922: TypeError: 
aAttrDef.objectNounDef is undefined
  JavaScript error: resource:///modules/gloda/gloda.js, line 1922: TypeError: 
aAttrDef.objectNounDef is undefined
  JavaScript error: resource:///modules/gloda/gloda.js, line 1922: TypeError: 
aAttrDef.objectNounDef is undefined
  JavaScript error: resource:///modules/gloda/gloda.js, line 1922: TypeError: 
aAttrDef.objectNounDef is undefined
  TypeError: aAttrDef.objectNounDef is undefined
  -- Exception object --
  *
  -- Stack Trace --
  defineAttribute@resource:///modules/gloda/gloda.js:1922:5
  defineAttributes@resource:///modules/gloda/fundattr.js:71:35
  init@resource:///modules/gloda/fundattr.js:43:12
  @resource:///modules/gloda/everybody.js:13:15
  @resource:///modules/gloda/public.js:8:57
  
nsAutoCompleteGloda@jar:file:///usr/lib/thunderbird/omni.ja!/components/glautocomp.js:516:32
  createInstance@resource://gre/modules/XPCOMUtils.jsm:433:19
  glodaSearch_XBL_Constructor@chrome://messenger/content/search.xml:73:16
  JavaScript error: chrome://messenger/content/messenger.xul, line 1: 
TypeError: QuickFilterBarMuxer is undefined
  JavaScript error: chrome://messenger/content/msgMail3PaneWindow.js, line 470: 
TypeError: TagUtils is undefined
  JavaScript error: resource:///modules/gloda/gloda.js, line 1922: TypeError: 
aAttrDef.objectNounDef is undefined

  What can I do ?

  Release: Ubuntu 19.10
  Package version: 1:68.1.2+build1-0ubuntu

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

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

[Desktop-packages] [Bug 1841793] Re: Don't update to 2.631

[Alejandro Claro]

Thank you for your answer Jeremy. Now it's clear to me.

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

Title:
  Don't update to 2.631

Status in glibmm2.4 package in Ubuntu:
  Triaged

Bug description:
  The .news entry starts with

  '2.63.1: (unstable):
  Distro packagers should probably not package this yet.'

  Let's follow upstream's advice there

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glibmm2.4/+bug/1841793/+subscriptions

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

[Desktop-packages] [Bug 1846699] [NEW] Missing mechanism in Glibmm that prevents the support of some themes (CSS) in Gtkmm

[Alejandro Claro]

Public bug reported:

In  GTK+ 3.20 the theming mechanics was heavily changed.

https://developer.gnome.org/gtk3/stable/ch32s10.html

One of the major changes was the use of element names much more than
style classes. For this the function gtk_widget_class_set_css_name() was
added to t he API and used to assign the element names. However, this
was not added in GTKmm, making impossible to assign element names in
custom widget, and no automatically assignment was developed in GTKmm's
Widget class in order to be able to identify widget classes in the
theming system (CSS).

The problem was discussed and tracked up to Glibmm in GNOME bug tracking
system:

https://gitlab.gnome.org/GNOME/gtkmm/issues/17
https://gitlab.gnome.org/GNOME/glibmm/issues/33

The issues are due to the lack of the mechanism to call
gtk_widget_class_set_css_name() function in the instance init function.

This was solved in Glibmm2.4 2.60, however Ubuntu is still behind this
version and it's affecting some of our products.

We have applied a patch to the current version (2.56) of Glibmm2.4 in
Ubuntu 18.04 successfully, but I would like to ask you to consider
upgrading the version of Glibmm in the official repository or apply the
patch.

** Affects: glibmm2.4 (Ubuntu)
 Importance: Undecided
 Status: New

** Description changed:

  In  GTK+ 3.20 the theming mechanics was heavily changed.
  
  https://developer.gnome.org/gtk3/stable/ch32s10.html
  
  One of the major changes was the use of element names much more than
  style classes. For this the function gtk_widget_class_set_css_name() was
  added to t he API and used to assign the element names. However, this
  was not added in GTKmm, making impossible to assign element names in
  custom widget, and no automatically assignment was developed in GTKmm's
  Widget class in order to be able to identify widget classes in the
  theming system (CSS).
  
  The problem was discussed and tracked up to Glibmm in GNOME bug tracking
  system:
  
  https://gitlab.gnome.org/GNOME/gtkmm/issues/17
  https://gitlab.gnome.org/GNOME/glibmm/issues/33
  
  The issues are due to the lack of the mechanism to call
  gtk_widget_class_set_css_name() function in the instance init function.
  
  This was solved in Glibmm2.4 2.60, however Ubuntu is still behind this
  version and it's affecting some of our products.
  
  We have applied a patch to the current version (2.56) of Glibmm2.4 in
- Ubuntu 18.04 successfully, but I would like to ask considered upgrading
- the version of Glibmm in the official repository or apply the patch.
+ Ubuntu 18.04 successfully, but I would like to ask you to consider
+ upgrading the version of Glibmm in the official repository or apply the
+ patch.

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

Title:
  Missing mechanism in Glibmm that prevents the support of some themes
  (CSS) in Gtkmm

Status in glibmm2.4 package in Ubuntu:
  New

Bug description:
  In  GTK+ 3.20 the theming mechanics was heavily changed.

  https://developer.gnome.org/gtk3/stable/ch32s10.html

  One of the major changes was the use of element names much more than
  style classes. For this the function gtk_widget_class_set_css_name()
  was added to t he API and used to assign the element names. However,
  this was not added in GTKmm, making impossible to assign element names
  in custom widget, and no automatically assignment was developed in
  GTKmm's Widget class in order to be able to identify widget classes in
  the theming system (CSS).

  The problem was discussed and tracked up to Glibmm in GNOME bug
  tracking system:

  https://gitlab.gnome.org/GNOME/gtkmm/issues/17
  https://gitlab.gnome.org/GNOME/glibmm/issues/33

  The issues are due to the lack of the mechanism to call
  gtk_widget_class_set_css_name() function in the instance init
  function.

  This was solved in Glibmm2.4 2.60, however Ubuntu is still behind this
  version and it's affecting some of our products.

  We have applied a patch to the current version (2.56) of Glibmm2.4 in
  Ubuntu 18.04 successfully, but I would like to ask you to consider
  upgrading the version of Glibmm in the official repository or apply
  the patch.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glibmm2.4/+bug/1846699/+subscriptions

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

[Desktop-packages] [Bug 1841793] Re: Don't update to 2.61.1

[Alejandro Claro]

Good morning Sebastien,

can you please describe why is it a problem to upgrade Glibmm?

We are affected by an issue in the current version (2.58). After some
changes in GTK+ theme mechanisms in order to be able to configure the
CSS class names properly it is important to be able to call
gtk_widget_class_set_css_name() in the object instance init function.

However, this was not possible until Glibmm team add the support to this
in version 2.60. Without these change there is no way to solve the
problem. The discussion about this can be found in GNOME issue tracking:

https://gitlab.gnome.org/GNOME/glibmm/issues/33
https://gitlab.gnome.org/GNOME/gtkmm/issues/17


** Bug watch added: gitlab.gnome.org/GNOME/glibmm/issues #33
   https://gitlab.gnome.org/GNOME/glibmm/issues/33

** Bug watch added: gitlab.gnome.org/GNOME/gtkmm/issues #17
   https://gitlab.gnome.org/GNOME/gtkmm/issues/17

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

Title:
  Don't update to 2.61.1

Status in glibmm2.4 package in Ubuntu:
  Triaged

Bug description:
  The .news entry starts with

  '2.61.1: (unstable):
  Distro packagers should probably not package this yet.'

  Let's follow upstream's advice there

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glibmm2.4/+bug/1841793/+subscriptions

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

[Desktop-packages] [Bug 1754702] Re: Delay before you can type after switching input source

[Alejandro]

I have one more update. I could not use ubuntu 18.04 with this bug, so
since then, I have been working on ubuntu 16.04 with unity. Yesterday I
tried ubuntu 19.04 on a live usb and after configure to my usual
setting, the bug was not present. I proceeded to install in on my
computer, and I found the bug again. I tried the same procedure and I
got the same results. Therefore, I am guessing it could be some
configuration file somewhere.  After backing up my files, I did a clean
install and now the bug is nowhere to be found. I could not determine
what it was, but I am thinking it was something in the transition to
gnome was not compatible. I am using 19.04 with no problem now, working
perfectly and very surprised at how much the desktop has evolved in over
a year. Beautiful and fast! kudos to everyone involved. I originally
filed this bug, so I am not sure if it can be marked as not in disco
dingo. Thanks

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

Title:
  Delay before you can type after switching input source

Status in gnome-shell package in Ubuntu:
  Confirmed

Bug description:
  In ubuntu 18.04 I installed different keyboard languages: spanish
  latin american, japanese, japanese-ibus.  To change the input method
  you press the selected key, and an indicator menu appears on-screen to
  indicate which language is selected next.  The menu disapears after
  2~3 seconds and during which time typing is blocked.  If you type
  while the language input method menu is displayed, the menu will not
  disapear and stay as long as you type.

  The language input menu should not block typing, and the disapearance
  of the menu should not be delayed by typing.

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

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

[Desktop-packages] [Bug 1816456] [NEW] sane-backends defect - Canon DR-X10C scanner

[Alejandro Claro]

Public bug reported:

We have detected a defect relate to the support of Canon DR-X10C
scanners. This has been addressed and a merge request is going to be
accepted this week:

https://gitlab.com/sane-project/backends/merge_requests/12

This is important for one of our products and we will like to ask to
include this fix in the Ubuntu 18.04 package if it's possible.

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

** Description changed:

  We have detected a defect relate to the support of Canon DR-X10C
- scanners. This has been address and a merge request is going to be
+ scanners. This has been addressed and a merge request is going to be
  accepted this week:
  
  https://gitlab.com/sane-project/backends/merge_requests/12
  
  This is important for one of our products and we will like to ask to
  include this fix in the Ubuntu 18.04 package if it's possible.

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

Title:
  sane-backends defect - Canon DR-X10C scanner

Status in sane-backends package in Ubuntu:
  New

Bug description:
  We have detected a defect relate to the support of Canon DR-X10C
  scanners. This has been addressed and a merge request is going to be
  accepted this week:

  https://gitlab.com/sane-project/backends/merge_requests/12

  This is important for one of our products and we will like to ask to
  include this fix in the Ubuntu 18.04 package if it's possible.

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

-- 
Mailing list: https://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 1725764] Re: Despues de reiniciar, Ubuntu ha experimentado un error interno

[Alejandro Paredes]

Best regard,

every time I restart the system, this error comes out

Thanks

El mié., 6 feb. 2019 a las 9:55, Sebastien Bacher ()
escribió:

> Thank you for taking the time to report this bug and helping to make
> Ubuntu better. Please answer these questions:
> * Is this reproducible?
> * If so, what specific steps should we take to recreate this bug?
>
> This will help us to find and resolve the problem.
>
> ** Changed in: nautilus (Ubuntu)
>Status: Confirmed => Incomplete
>
> ** Information type changed from Private to Public
>
> --
> You received this bug notification because you are subscribed to a
> duplicate bug report (1729083).
> https://bugs.launchpad.net/bugs/1725764
>
> Title:
>   Despues de reiniciar, Ubuntu ha experimentado un error interno
>
> Status in nautilus package in Ubuntu:
>   Incomplete
>
> Bug description:
>   Instalé Synaptic y reinicié el sistema operativo, UBUNTU EXPERIMENTÓ
>   UN ERROR INTERNO, dijo Ubuntu.
>
>   ProblemType: Crash
>   DistroRelease: Ubuntu 17.10
>   Package: nautilus 1:3.26.0-0ubuntu1
>   ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
>   Uname: Linux 4.13.0-16-generic x86_64
>   ApportVersion: 2.20.7-0ubuntu3
>   Architecture: amd64
>   CurrentDesktop: ubuntu:GNOME
>   Date: Sat Oct 21 14:00:28 2017
>   ExecutablePath: /usr/bin/nautilus-desktop
>   InstallationDate: Installed on 2017-10-21 (0 days ago)
>   InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64
> (20171018)
>   ProcCmdline: nautilus-desktop
>   Signal: 5
>   SourcePackage: nautilus
>   StacktraceTop:
>?? () from /usr/lib/x86_64-linux-gnu/libX11.so.6
>?? () from /usr/lib/x86_64-linux-gnu/libX11.so.6
>_XReply () from /usr/lib/x86_64-linux-gnu/libX11.so.6
>XGetWindowProperty () from /usr/lib/x86_64-linux-gnu/libX11.so.6
>?? () from /usr/lib/x86_64-linux-gnu/libgnome-desktop-3.so.12
>   Title: nautilus-desktop crashed with signal 5 in _XReply()
>   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/nautilus/+bug/1725764/+subscriptions
>


-- 

Cualquier inquietud, sugerencia o duda al respecto, estaremos atentos de
resolverla en la menor brevedad.


Cordialmente,


*Alejandro Paredes*

*Consultor de Seguridad Informática*

Ing. Sistemas - Auditor Kaspersky


La información contenida en este documento es de carácter reservado y solo
puede ser utilizado por las personas autorizadas para su evaluación. El
sello de confidencialidad hace referencia a que esta información no puede
ser reproducida ni revelada a terceros. El carácter reservado de la
información está fundamentado en los artículos 72 y siguientes de la
decisión del acuerdo de Cartagena 344 de 1993, el artículo 308 del código
penal y los artículos 16 y siguientes de la ley 256 de 1996 de la República
de Colombia. Se prohíbe el análisis, divulgación o retransmisión de esta
información sobre cualquier formato o medio, electrónica o mecánicamente
para cualquier finalidad o cualquier otro uso, la reproducción,
publicación, divulgación, reenvió, copia, impresión y cualquier manejo de
los datos incluidos en este mail, así como cualquier otra acción
relacionada con ella sin el expreso consentimiento de mi persona Conforme a
los derechos otorgados para el titular por la ley 1581 de 2012. Cualquier
omisión a esta advertencia, podrá desembocar en sanciones administrativas
ante la superintendencia de industria y comercio, a más de las denuncias
penales respectivas.

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

Title:
  Despues de reiniciar, Ubuntu ha experimentado un error interno

Status in nautilus package in Ubuntu:
  Incomplete

Bug description:
  Instalé Synaptic y reinicié el sistema operativo, UBUNTU EXPERIMENTÓ
  UN ERROR INTERNO, dijo Ubuntu.

  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: nautilus 1:3.26.0-0ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Oct 21 14:00:28 2017
  ExecutablePath: /usr/bin/nautilus-desktop
  InstallationDate: Installed on 2017-10-21 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  ProcCmdline: nautilus-desktop
  Signal: 5
  SourcePackage: nautilus
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/libX11.so.6
   ?? () from /usr/lib/x86_64-linux-gnu/libX11.so.6
   _XReply () from /usr/lib/x86_64-linux-gnu/libX11.so.6
   XGetWindowProperty () from /usr/lib/x86_64-lin

[Desktop-packages] [Bug 1814481] [NEW] bluetooth keyboard not working

[Alejandro Mery]

Public bug reported:

I recently got a nice mechanical bluetooth keyboard to use on my
thinkpad. It works fine with Android, Windows 10 and Xubuntu 19.04 live,
but on my installed xubuntu 18.04, 18.04 live and 18.10 live it only
works after calling `sudo evtest /dev/input/eventN`.

Xorg.0.log shows it is detected fine, and I can't see anything there
after temporarily getting it to work using the evtest trick.

18.515] (II) config/udev: Adding input device Keychron K1 
(/dev/input/event23)
[18.515] (**) Keychron K1: Applying InputClass "libinput keyboard catchall"
[18.515] (II) Using input driver 'libinput' for 'Keychron K1'
[18.515] (**) Keychron K1: always reports core events
[18.515] (**) Option "Device" "/dev/input/event23"
[18.515] (**) Option "_source" "server/udev"
[18.516] (II) event23 - Keychron K1: is tagged by udev as: Keyboard
[18.516] (II) event23 - Keychron K1: device is a keyboard
[18.516] (II) event23 - Keychron K1: device removed
[18.524] (II) libinput: Keychron K1: needs a virtual subdevice
[18.524] (**) Option "config_info" 
"udev:/sys/devices/pci:00/:00:14.0/usb1/1-7/1-7:1.0/bluetooth/hci0/hci0:256/0005:05AC:0255.0007/input/input24/event23"
[18.524] (II) XINPUT: Adding extended input device "Keychron K1" (type: 
MOUSE, id 20)
[18.524] (**) Option "AccelerationScheme" "none"
[18.524] (**) Keychron K1: (accel) selected scheme none/0
[18.524] (**) Keychron K1: (accel) acceleration factor: 2.000
[18.524] (**) Keychron K1: (accel) acceleration threshold: 4
[18.524] (II) event23 - Keychron K1: is tagged by udev as: Keyboard
[18.524] (II) event23 - Keychron K1: device is a keyboard
[18.524] (**) Keychron K1: Applying InputClass "libinput keyboard catchall"
[18.524] (II) Using input driver 'libinput' for 'Keychron K1'
[18.524] (**) Keychron K1: always reports core events
[18.524] (**) Option "Device" "/dev/input/event23"
[18.524] (**) Option "_source" "_driver/libinput"
[18.524] (II) libinput: Keychron K1: is a virtual subdevice
[18.524] (**) Option "config_info" 
"udev:/sys/devices/pci:00/:00:14.0/usb1/1-7/1-7:1.0/bluetooth/hci0/hci0:256/0005:05AC:0255.0007/input/input24/event23"
[18.524] (II) XINPUT: Adding extended input device "Keychron K1" (type: 
KEYBOARD, id 21)
[18.524] (**) Option "xkb_model" "pc105"
[18.524] (**) Option "xkb_layout" "us"
[18.524] (**) Option "xkb_variant" "altgr-intl"
[18.524] (WW) Option "xkb_options" requires a string value

I've also tried using the latest 4.20.6 from mainline-ppa and the latest
bluetooth/bluz ppa without success.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xorg 1:7.7+19ubuntu7.1
ProcVersionSignature: Ubuntu 4.15.0-45.48-lowlatency 4.15.18
Uname: Linux 4.15.0-45-lowlatency x86_64
ApportVersion: 2.20.9-0ubuntu7.5
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
CurrentDesktop: XFCE
Date: Sun Feb  3 23:51:29 2019
DistUpgraded: 2019-02-03 21:49:33,752 DEBUG /openCache(), new cache size 92675
DistroCodename: bionic
DistroVariant: ubuntu
DkmsStatus: virtualbox, 5.2.18, 4.15.0-45-lowlatency, x86_64: installed
ExtraDebuggingInterest: Yes
GraphicsCard:
 Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA 
controller])
   Subsystem: Lenovo HD Graphics 620 [17aa:224b]
InstallationDate: Installed on 2017-07-24 (559 days ago)
InstallationMedia: Xubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215)
MachineType: LENOVO 20HFCTO1WW
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-45-lowlatency 
root=UUID=8f8366ae-4d29-44cf-9b85-f83f1771eab1 ro quiet splash vt.handoff=1
SourcePackage: xorg
UpgradeStatus: Upgraded to bionic on 2019-02-03 (0 days ago)
dmi.bios.date: 09/14/2018
dmi.bios.vendor: LENOVO
dmi.bios.version: N1WET51W (1.30 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20HFCTO1WW
dmi.board.vendor: LENOVO
dmi.board.version: SDK0J40709 WIN
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.modalias: 
dmi:bvnLENOVO:bvrN1WET51W(1.30):bd09/14/2018:svnLENOVO:pn20HFCTO1WW:pvrThinkPadT470s:rvnLENOVO:rn20HFCTO1WW:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrNone:
dmi.product.family: ThinkPad T470s
dmi.product.name: 20HFCTO1WW
dmi.product.version: ThinkPad T470s
dmi.sys.vendor: LENOVO
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.95-1~18.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.2-0ubuntu1~18.04.1
version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.2-0ubuntu1~18.04.1
version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

** Affects: xorg (U

[Desktop-packages] [Bug 1769299] Re: universal access zoom unusable

[Alejandro Fabre]

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

Have the same problem.

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

Title:
  universal access zoom unusable

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

Bug description:
  
  Filed by mark on behalf of low vision user Ken.   Ken is able to read 56 
point type without magnification at normal reading distance and can barely read 
the universal access "large text" from a distance of about 2.5 inches from a 
26inch monitor at 1360x768.   So he really needs magnification and a lot more 
than the 2x default I used here for testing.   We do not live in the same town 
so providing additional details would be slow.

  Turned on zoom from the universal access button on top panel.
  Default settings were used including Zoom = 2.0, screen part = full

  Several areas are corrupted.  These zoom and scroll separately from
  the rest of the screen and in a way that severely impairs use as
  portions may not ever be visible.   Portions of these subwindows
  cannot be used because you have to move the mouse off them to be able
  see them so you can either see or click but not both.

  These areas are:
- The top panel
- The left panel (launcher)  (intermittently)
- pull down menus, particularly the universal access pull down from the top 
panel

  
  Also, the zoom randomly every couple seconds. jumps to a different position 
without the user's consent.   This appeared to be because text was printed by a 
program running in the terminal window (long apt-get install) but continued to 
happen even when that window was minimized and even when that program stopped 
printing.

  These problems persisted with all the other zoom modes.   One mode,
  however, created new bugs.  With "magnifier extends outside of
  screen", you lose the ability to see the top and left panels at all;
  you can pan over where they would be but they are not drawn.   Can't
  open the pulldown menu since there is no icon, so who knows how it
  would be rendered.

  These bugs made it very difficult to get screenshots, especially with
  the defective screenshot program gnome-screenshot which ships with
  system.   Also, the bug-reporting program did not permitted attaching
  additional screenshots once spectacle was installed.

  Ubuntu 18.04, fresh install, only a few added packages (ham radio
  related, chrome).  Not using wayland, though a wayland session runs
  concurrently with X11 even though no one has logged in with wayland.

  Another problem in making the bug report is the irresponsible practice
  of failing to identify the software being used.   The accessability
  man in circle menu does not have a heading to tell you what program is
  run for the accessability menu or any of the functions thus invoked.
  Nor does the settings.  And there is no tooltip, popup, or about menu
  item to convey this information to the user.   And running a diff on
  ps doesn't show any new processes started when zoom is turned on.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sat May  5 00:04:35 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  GraphicsCard:
   NVIDIA Corporation G98 [GeForce 8400 GS Rev. 2] [10de:06e4] (rev a1) 
(prog-if 00 [VGA controller])
 Subsystem: Micro-Star International Co., Ltd. [MSI] G98 [GeForce 8400 GS 
Rev. 2] [1462:1163]
  InstallationDate: Installed on 2018-05-05 (0 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  MachineType: Dell Inc. OptiPlex 760
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-20-generic 
root=UUID=6a7e27f6-5135-461e-9e6b-fea68756ed37 ro quiet splash vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/29/2009
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A03
  dmi.board.name: 0M858N
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A01
  dmi.chassis.type: 6
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA03:bd04/29/2009:svnDellInc.:pnOptiPlex760:pvr:rvnDellInc.:rn0M858N:rvrA01:cvnDellInc.:ct6:cvr:
  dmi.product.name: OptiPlex 760
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.91-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1
  version.libgl1-mesa-glx: lib

[Desktop-packages] [Bug 1188569] Re: Some keyboard shortcuts randomly stop working

[Alejandro A.]

@18
Installing the unity-settings-daemon from mentioned ppa in 18.04 fixed my 
problems completely :)

Thank you very much for your efforts!

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

Title:
  Some keyboard shortcuts randomly stop working

Status in GNOME Shell:
  New
Status in Unity:
  Confirmed
Status in unity package in Ubuntu:
  Invalid
Status in unity-settings-daemon package in Ubuntu:
  Confirmed

Bug description:
  Hi,
  Certain shortcuts randomly stops working in my computer. They are Super+s 
(workspace switcher), Super+Up (switch to workspace above) and Super+Down 
(switch to workspace below). Other shortcuts work fine.

  A few notes that might help:
  1- Reassigning shortcuts make them work again except for Super+s.
  2- Rebooting make shortcuts work.
  3- I have been using these shortcuts with many previous ubuntu versions and 
my preferences are old.
  4- I am not sure of certain steps that produces the problem. The shortcuts 
sometimes stop working but once they stop, they do not work unless I reassign 
them or reboot.

  I am using Ubuntu 13.04.

  Thank you

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: unity 7.0.0daily13.04.18~13.04-0ubuntu1
  ProcVersionSignature: Ubuntu 3.8.0-23.34-generic 3.8.11
  Uname: Linux 3.8.0-23-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.9.2-0ubuntu8.1
  Architecture: amd64
  CompizPlugins: 
[core,composite,opengl,compiztoolbox,decor,regex,grid,mousepoll,place,wall,snap,resize,vpswitch,session,animation,gnomecompat,imgpng,commands,move,workarounds,fade,unitymtgrabhandles,expo,scale,ezoom,unityshell]
  Date: Fri Jun  7 13:40:06 2013
  InstallationDate: Installed on 2013-05-27 (11 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  MarkForUpload: True
  SourcePackage: unity
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1738164] Re: [snap] U2F doesn't work with yubikey

[Alejandro M. Medrano Gil]

Sorry forgot

journalctl -f:
-- Logs begin at Sun 2018-08-12 21:54:04 CEST. --
ago 16 19:20:29 Alex thunderbird.desktop[25941]: [Parent 26418, Gecko_IOThread] 
WARNING: pipe error (113): Conexión reinicializada por la máquina remota: file 
/build/firefox-oscv9o/firefox-61.0.1+build1/ipc/chromium/src/chrome/common/ipc_channel_posix.cc,
 line 353
ago 16 19:37:40 Alex dbus-daemon[18014]: apparmor="DENIED" 
operation="dbus_method_call"  bus="session" path="/org/freedesktop/secrets" 
interface="org.freedesktop.DBus.Properties" member="GetAll" mask="send" 
name="org.freedesktop.secrets" pid=27271 label="snap.chromium.chromium" 
peer_pid=18002 peer_label="unconfined"
ago 16 19:37:40 Alex audit[989]: USER_AVC pid=989 uid=103 auid=4294967295 
ses=4294967295 msg='apparmor="DENIED" operation="dbus_method_call"  
bus="system" path="/" interface="org.freedesktop.DBus.ObjectManager" 
member="GetManagedObjects" mask="send" name="org.bluez" pid=26979 
label="snap.chromium.chromium" peer_pid=985 peer_label="unconfined"
  exe="/usr/bin/dbus-daemon" sauid=103 
hostname=? addr=? terminal=?'
ago 16 19:37:40 Alex kernel: audit: type=1107 audit(1534441060.543:176): 
pid=989 uid=103 auid=4294967295 ses=4294967295 msg='apparmor="DENIED" 
operation="dbus_method_call"  bus="system" path="/" 
interface="org.freedesktop.DBus.ObjectManager" member="GetManagedObjects" 
mask="send" name="org.bluez" pid=26979 label="snap.chromium.chromium" 
peer_pid=985 peer_label="unconfined"
  exe="/usr/bin/dbus-daemon" sauid=103 hostname=? 
addr=? terminal=?'
ago 16 19:37:47 Alex audit[26979]: AVC apparmor="DENIED" operation="open" 
profile="snap.chromium.chromium" name="/run/udev/data/c238:0" pid=26979 
comm="TaskSchedulerFo" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0
ago 16 19:37:47 Alex kernel: audit: type=1400 audit(1534441067.899:177): 
apparmor="DENIED" operation="open" profile="snap.chromium.chromium" 
name="/run/udev/data/c238:0" pid=26979 comm="TaskSchedulerFo" 
requested_mask="r" denied_mask="r" fsuid=1000 ouid=0
ago 16 19:37:47 Alex audit[26979]: AVC apparmor="DENIED" operation="open" 
profile="snap.chromium.chromium" name="/run/udev/data/c239:0" pid=26979 
comm="TaskSchedulerFo" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0
ago 16 19:37:47 Alex audit[26979]: AVC apparmor="DENIED" operation="open" 
profile="snap.chromium.chromium" name="/run/udev/data/c240:0" pid=26979 
comm="TaskSchedulerFo" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0
ago 16 19:37:47 Alex kernel: audit: type=1400 audit(1534441067.927:178): 
apparmor="DENIED" operation="open" profile="snap.chromium.chromium" 
name="/run/udev/data/c239:0" pid=26979 comm="TaskSchedulerFo" 
requested_mask="r" denied_mask="r" fsuid=1000 ouid=0
ago 16 19:37:47 Alex kernel: audit: type=1400 audit(1534441067.927:179): 
apparmor="DENIED" operation="open" profile="snap.chromium.chromium" 
name="/run/udev/data/c240:0" pid=26979 comm="TaskSchedulerFo" 
requested_mask="r" denied_mask="r" fsuid=1000 ouid=0
ago 16 19:38:12 Alex audit[26979]: AVC apparmor="DENIED" operation="open" 
profile="snap.chromium.chromium" name="/run/udev/data/c238:0" pid=26979 
comm="TaskSchedulerFo" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0
ago 16 19:38:12 Alex kernel: audit: type=1400 audit(1534441092.615:180): 
apparmor="DENIED" operation="open" profile="snap.chromium.chromium" 
name="/run/udev/data/c238:0" pid=26979 comm="TaskSchedulerFo" 
requested_mask="r" denied_mask="r" fsuid=1000 ouid=0
ago 16 19:38:12 Alex audit[26979]: AVC apparmor="DENIED" operation="open" 
profile="snap.chromium.chromium" name="/run/udev/data/c239:0" pid=26979 
comm="TaskSchedulerFo" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0
ago 16 19:38:12 Alex audit[26979]: AVC apparmor="DENIED" operation="open" 
profile="snap.chromium.chromium" name="/run/udev/data/c240:0" pid=26979 
comm="TaskSchedulerFo" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0
ago 16 19:38:12 Alex kernel: audit: type=1400 audit(1534441092.643:181): 
apparmor="DENIED" operation="open" profile="snap.chromium.chromium" 
name="/run/udev/data/c239:0" pid=26979 comm="TaskSchedulerFo" 
requested_mask="r" denied_mask="r" fsuid=1000 ouid=0
ago 16 19:38:12 Alex kernel: audit: type=1400 audit(1534441092.643:182): 
apparmor="DENIED" operation="open" profile="snap.chromium.chromium" 
name="/run/udev/data/c240:0" pid=26979 comm="TaskSchedulerFo" 
requested_mask="r" denied_mask="r" fsuid=1000 ouid=0
ago 16 19:38:16 Alex kernel: usb 1-9: new full-speed USB device number 11 using 
xhci_hcd
ago 16 19:38:16 Alex kernel: usb 1-9: New USB device found, idVendor=1050, 
idProduct=0116
ago 16 19:38:16 Alex kernel: usb 1-9: New USB device strings: Mfr=1, Product=2, 
SerialNumber=0
ago 16 19:38:16 Alex kernel: usb 1-9: Product: Yubikey NEO OTP+U2F+CCID
ago 16 19:38:16 Alex kernel: usb 1-9: Manufacturer: Yubico
ago 16 19:38:16 Alex kernel: input: Yubico Yubikey NEO OTP+U2F+CCID as 
/devices/pci:00/00

[Desktop-packages] [Bug 1738164] Re: [snap] U2F doesn't work with yubikey

[Alejandro M. Medrano Gil]

I have the same issue, my Yubikey is the yibikey neo 4 model, it does
support U2F. after installing Ubuntu 18.04.01 I followed yubico's
instructions:
https://support.yubico.com/support/solutions/articles/1506449-using-
your-u2f-yubikey-with-linux

which means I have a udev rule for the device, but dmesg was still
mapping to snap.chromium. At this point the U2F seemed to wait for input
until timeout, whereas the key's LED would flash like if it were in
process of system recognition indefinitelly (as seen from dmesg, it
seems chromium it continously attempting to read the device, but there
are permission restrictions).

dmesg:
[18519.805380] usb 1-9: new full-speed USB device number 9 using xhci_hcd
[18519.954776] usb 1-9: New USB device found, idVendor=1050, idProduct=0116
[18519.954782] usb 1-9: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[18519.954785] usb 1-9: Product: Yubikey NEO OTP+U2F+CCID
[18519.954789] usb 1-9: Manufacturer: Yubico
[18519.956412] input: Yubico Yubikey NEO OTP+U2F+CCID as 
/devices/pci:00/:00:14.0/usb1/1-9/1-9:1.0/0003:1050:0116.0006/input/input20
[18520.014104] hid-generic 0003:1050:0116.0006: input,hidraw1: USB HID v1.10 
Keyboard [Yubico Yubikey NEO OTP+U2F+CCID] on usb-:00:14.0-9/input0
[18520.015266] hid-generic 0003:1050:0116.0007: hiddev0,hidraw2: USB HID v1.10 
Device [Yubico Yubikey NEO OTP+U2F+CCID] on usb-:00:14.0-9/input1
[18551.143579] audit: type=1107 audit(1534439526.751:164): pid=989 uid=103 
auid=4294967295 ses=4294967295 msg='apparmor="DENIED" 
operation="dbus_method_call"  bus="system" path="/" 
interface="org.freedesktop.DBus.ObjectManager" member="GetManagedObjects" 
mask="send" name="org.bluez" pid=25155 label="snap.chromium.chromium" 
peer_pid=985 peer_label="unconfined"
exe="/usr/bin/dbus-daemon" sauid=103 hostname=? addr=? 
terminal=?'
[18553.624016] audit: type=1400 audit(1534439529.231:165): apparmor="DENIED" 
operation="open" profile="snap.chromium.chromium" name="/run/udev/data/c238:0" 
pid=25155 comm="TaskSchedulerFo" requested_mask="r" denied_mask="r" fsuid=1000 
ouid=0
[18553.638835] audit: type=1400 audit(1534439529.247:166): apparmor="DENIED" 
operation="open" profile="snap.chromium.chromium" name="/run/udev/data/c239:0" 
pid=25155 comm="TaskSchedulerFo" requested_mask="r" denied_mask="r" fsuid=1000 
ouid=0
[18553.639389] audit: type=1400 audit(1534439529.247:167): apparmor="DENIED" 
operation="open" profile="snap.chromium.chromium" name="/run/udev/data/c240:1" 
pid=25155 comm="TaskSchedulerFo" requested_mask="r" denied_mask="r" fsuid=1000 
ouid=0
[18553.639450] audit: type=1400 audit(1534439529.247:168): apparmor="DENIED" 
operation="open" profile="snap.chromium.chromium" name="/run/udev/data/c240:2" 
pid=25155 comm="TaskSchedulerFo" requested_mask="r" denied_mask="r" fsuid=1000 
ouid=0
[18553.639491] audit: type=1400 audit(1534439529.247:169): apparmor="DENIED" 
operation="open" profile="snap.chromium.chromium" name="/run/udev/data/c240:0" 
pid=25155 comm="TaskSchedulerFo" requested_mask="r" denied_mask="r" fsuid=1000 
ouid=0
[18863.195707] audit: type=1400 audit(1534439838.807:170): apparmor="DENIED" 
operation="open" profile="snap.chromium.chromium" name="/run/udev/data/c238:0" 
pid=25155 comm="TaskSchedulerFo" requested_mask="r" denied_mask="r" fsuid=1000 
ouid=0
[18863.215818] audit: type=1400 audit(1534439838.827:171): apparmor="DENIED" 
operation="open" profile="snap.chromium.chromium" name="/run/udev/data/c239:0" 
pid=25155 comm="TaskSchedulerFo" requested_mask="r" denied_mask="r" fsuid=1000 
ouid=0
[18863.216503] audit: type=1400 audit(1534439838.827:172): apparmor="DENIED" 
operation="open" profile="snap.chromium.chromium" name="/run/udev/data/c240:1" 
pid=25155 comm="TaskSchedulerFo" requested_mask="r" denied_mask="r" fsuid=1000 
ouid=0
[18863.216561] audit: type=1400 audit(1534439838.827:173): apparmor="DENIED" 
operation="open" profile="snap.chromium.chromium" name="/run/udev/data/c240:2" 
pid=25155 comm="TaskSchedulerFo" requested_mask="r" denied_mask="r" fsuid=1000 
ouid=0
[18863.216616] audit: type=1400 audit(1534439838.827:174): apparmor="DENIED" 
operation="open" profile="snap.chromium.chromium" name="/run/udev/data/c240:0" 
pid=25155 comm="TaskSchedulerFo" requested_mask="r" denied_mask="r" fsuid=1000 
ouid=0


I have attempted as instructed in #9, the results are as described in
#4: the U2F solicitors (github, gmail) will report "somethig whent
wrong" as soon as the key is inserted. Thus it seems the issue got
worse. BTW how do I get back to the default channel?

stderr:
Gtk-Message: Failed to load module "canberra-gtk-module"
Gtk-Message: Failed to load module "canberra-gtk-module"
[24390:24390:0816/191106.760998:WARNING:password_store_factory.cc(250)] Using 
basic (unencrypted) store for password storage. See 
https://chromium.googlesource.com/chromium/src/+/master/docs/linux_password_storage.md
 for more information about password storage options.
[24390:24390:0816/191109.00096

[Desktop-packages] [Bug 1786541] [NEW] package libgphoto2-6:i386 2.5.14-1 failed to install/upgrade: problemas de dependencias - se deja sin configurar

[Alejandro Montejo Galvez]

Public bug reported:

Mi pc no para de tener ese error

ProblemType: Package
DistroRelease: Ubuntu 17.10
Package: libgphoto2-6:i386 2.5.14-1
ProcVersionSignature: Ubuntu 4.13.0-46.51-generic 4.13.16
Uname: Linux 4.13.0-46-generic x86_64
ApportVersion: 2.20.7-0ubuntu3.9
AptOrdering:
 playonlinux:amd64: Install
 NULL: ConfigurePending
Architecture: amd64
Date: Fri Aug 10 17:13:15 2018
ErrorMessage: problemas de dependencias - se deja sin configurar
InstallationDate: Installed on 2018-06-28 (43 days ago)
InstallationMedia: Lubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105)
PackageArchitecture: i386
Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 
3.6.3-0ubuntu3
PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 
2.7.14-2ubuntu1
RelatedPackageVersions:
 dpkg 1.18.24ubuntu1
 apt  1.5.2
SourcePackage: libgphoto2
Title: package libgphoto2-6:i386 2.5.14-1 failed to install/upgrade: problemas 
de dependencias - se deja sin configurar
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: apport-package artful i386

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

Title:
  package libgphoto2-6:i386 2.5.14-1 failed to install/upgrade:
  problemas de dependencias - se deja sin configurar

Status in libgphoto2 package in Ubuntu:
  New

Bug description:
  Mi pc no para de tener ese error

  ProblemType: Package
  DistroRelease: Ubuntu 17.10
  Package: libgphoto2-6:i386 2.5.14-1
  ProcVersionSignature: Ubuntu 4.13.0-46.51-generic 4.13.16
  Uname: Linux 4.13.0-46-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.9
  AptOrdering:
   playonlinux:amd64: Install
   NULL: ConfigurePending
  Architecture: amd64
  Date: Fri Aug 10 17:13:15 2018
  ErrorMessage: problemas de dependencias - se deja sin configurar
  InstallationDate: Installed on 2018-06-28 (43 days ago)
  InstallationMedia: Lubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105)
  PackageArchitecture: i386
  Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 
3.6.3-0ubuntu3
  PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 
2.7.14-2ubuntu1
  RelatedPackageVersions:
   dpkg 1.18.24ubuntu1
   apt  1.5.2
  SourcePackage: libgphoto2
  Title: package libgphoto2-6:i386 2.5.14-1 failed to install/upgrade: 
problemas de dependencias - se deja sin configurar
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1780442] Re: Please backport fix for & in attributes

[Alejandro Guerrero]

I want to make sure it's clear this is a high-impact regression. Right
now I'm unable to use Software at all because of this, Software is empty
and says "no software data found". Software is useless. Manually editing
fwpd.xml or removing it and refreshing appstream restores functionality.
For me personally this ain't such a big deal as I know how to workaround
it, but normal users will be clueless and should not be expected having
to wait weeks for restored functionality because of something as trivial
as a unescaped ampersand.

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

Title:
  Please backport fix for & in attributes

Status in Fwupd:
  New
Status in appstream-glib package in Ubuntu:
  Fix Released
Status in appstream-glib source package in Xenial:
  Fix Committed

Bug description:
  [Impact]

  There are instances of fwupd being unable to run updates on certain
  devices on Ubuntu 16.04. due to a "&" in metadata.

  [Test Case]

   * Try to perform an update on a 8bitdo affected device.

  [Regression Potential]

   * Regressions would occur in metadata processing where the fwupd
  daemon wouldn't be able to process it.

  [Other Info]
   
  This was discussed here:
  https://github.com/hughsie/fwupd/issues/565#issuecomment-402534337

  This has been fixed in appstream-glib to prevent & in the metadata.  This fix 
is already in 18.04 and just needs to be backported to 16.04.
  
https://github.com/hughsie/appstream-glib/commit/6048520484101df5d33f3c852c10640e630d20cf

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

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

[Desktop-packages] [Bug 1780442] Re: Please backport fix for & in attributes

[Alejandro Guerrero]

Sorry it should say "fwupd.xml". Weird that you can't edit recent
comments at Launchpad, maybe Ubuntu should consider switching to GitLab
;)

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

Title:
  Please backport fix for & in attributes

Status in Fwupd:
  New
Status in appstream-glib package in Ubuntu:
  Fix Released
Status in appstream-glib source package in Xenial:
  Fix Committed

Bug description:
  [Impact]

  There are instances of fwupd being unable to run updates on certain
  devices on Ubuntu 16.04. due to a "&" in metadata.

  [Test Case]

   * Try to perform an update on a 8bitdo affected device.

  [Regression Potential]

   * Regressions would occur in metadata processing where the fwupd
  daemon wouldn't be able to process it.

  [Other Info]
   
  This was discussed here:
  https://github.com/hughsie/fwupd/issues/565#issuecomment-402534337

  This has been fixed in appstream-glib to prevent & in the metadata.  This fix 
is already in 18.04 and just needs to be backported to 16.04.
  
https://github.com/hughsie/appstream-glib/commit/6048520484101df5d33f3c852c10640e630d20cf

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

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

[Desktop-packages] [Bug 1769358] [NEW] Thumbnail previews in Files/Nautilus only show when zoom is 150% or more

[Loïc Alejandro]

Public bug reported:

Ubuntu 18.04 LTS
Nautilus package: 1:3.26.3-0ubuntu4

I don't get thumbnail previews in Files (Nautilus) at the default zoom
level when using List view.

If I select 150% in the hamburger menu the thumbnails are displayed, and
they are displayed in Grid view at all sizes. They are also displayed in
the Open File dialog, even though the icon size there is smaller than in
Files!

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

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

Title:
  Thumbnail previews in Files/Nautilus only show when zoom is 150% or
  more

Status in nautilus package in Ubuntu:
  New

Bug description:
  Ubuntu 18.04 LTS
  Nautilus package: 1:3.26.3-0ubuntu4

  I don't get thumbnail previews in Files (Nautilus) at the default zoom
  level when using List view.

  If I select 150% in the hamburger menu the thumbnails are displayed,
  and they are displayed in Grid view at all sizes. They are also
  displayed in the Open File dialog, even though the icon size there is
  smaller than in Files!

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

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

[Desktop-packages] [Bug 1754702] Re: input method on-screen animation prevents typing

[Alejandro]

I also do not know about the code, but I tested ubuntu mate 18.04 and
ibus.  Here a similar menu appears, but there is no delay when typing
and changing input method.  Maybe it could be a hint to fix the bug.

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

Title:
  input method on-screen animation prevents typing

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

Bug description:
  In ubuntu 18.04 I installed different keyboard languages: spanish
  latin american, japanese, japanese-ibus.  To change the input method
  you press the selected key, and an indicator menu appears on-screen to
  indicate which language is selected next.  The menu disapears after
  2~3 seconds and during which time typing is blocked.  If you type
  while the language input method menu is displayed, the menu will not
  disapear and stay as long as you type.

  The language input menu should not block typing, and the disapearance
  of the menu should not be delayed by typing.

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

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

[Desktop-packages] [Bug 1754702] Re: input method on-screen animation prevents typing

[Alejandro]

Hello, Thanks for the information.  I reviewed the information that you
sent me.  It is the same issue as described in the ask ubuntu question.
Therefore it should be the same problem as the bug you mentioned.   I
have been using unity, and for 18.04 thought about moving to gnome, so
this is the first time I experience it.  Should I mark as duplicate of
1244090?  The only new information is that it affects 18.04 too. Thanks
in advance.

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

Title:
  input method on-screen animation prevents typing

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

Bug description:
  In ubuntu 18.04 I installed different keyboard languages: spanish
  latin american, japanese, japanese-ibus.  To change the input method
  you press the selected key, and an indicator menu appears on-screen to
  indicate which language is selected next.  The menu disapears after
  2~3 seconds and during which time typing is blocked.  If you type
  while the language input method menu is displayed, the menu will not
  disapear and stay as long as you type.

  The language input menu should not block typing, and the disapearance
  of the menu should not be delayed by typing.

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

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

[Desktop-packages] [Bug 1754702] [NEW] input method on-screen animation prevents typing

[Alejandro]

Public bug reported:

In ubuntu 18.04 I installed different keyboard languages: spanish latin
american, japanese, japanese-ibus.  To change the input method you press
the selected key, and an indicator menu appears on-screen to indicate
which language is selected next.  The menu disapears after 2~3 seconds
and during which time typing is blocked.  If you type while the language
input method menu is displayed, the menu will not disapear and stay as
long as you type.

The language input menu should not block typing, and the disapearance of
the menu should not be delayed by typing.

** Affects: language-selector (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: ibus input-method

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

Title:
  input method on-screen animation prevents typing

Status in language-selector package in Ubuntu:
  New

Bug description:
  In ubuntu 18.04 I installed different keyboard languages: spanish
  latin american, japanese, japanese-ibus.  To change the input method
  you press the selected key, and an indicator menu appears on-screen to
  indicate which language is selected next.  The menu disapears after
  2~3 seconds and during which time typing is blocked.  If you type
  while the language input method menu is displayed, the menu will not
  disapear and stay as long as you type.

  The language input menu should not block typing, and the disapearance
  of the menu should not be delayed by typing.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/language-selector/+bug/1754702/+subscriptions

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

[Desktop-packages] [Bug 1518473] Re: /sys/class/backlight/acpi_video0/brightness is broken

[Alejandro Palacios]

link-dupont really nailed it! I am having the same issue on an HP
Elitebook 8770w with ONLY an NVIDIA Quadro K3000M, using the proprietary
driver version 387.34 on Fedora 27, Kernel 4.14.3-300

I tried all:

acpi_backlight=video
acpi_backlight=vendor
acpi_backlight=native

to no avail, so removed all of that and installed inotify-tools, I do
have /sys/class/backlight/acpi_video0 so I ended up with the following
script in /home/YOURUSERHERE/Scripts/backlight_inotify.sh

#!/bin/sh

path=/sys/class/backlight/acpi_video0

luminance() {
read -r level < "$path"/actual_brightness
factor=$((100 / max))
printf '%d\n' "$((level * factor))"
}

read -r max < "$path"/max_brightness

nvidia-settings -n -a BacklightBrightness="$(luminance)"

inotifywait -me modify --format '' "$path"/actual_brightness | while read; do
nvidia-settings -n -a BacklightBrightness="$(luminance)"
done


And then created file brightnessfix.desktop under 
/home/YOURUSERHERE/.config/autostart


[Desktop Entry]
Name=Brightness Fix
Exec=/home/YOURUSERHERE/Scripts/backlight_inotify.sh
Terminal=false
Type=Application
Name[en_US]=backlightfix.desktop


It is a very effective workaround, thanks.

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

Title:
  /sys/class/backlight/acpi_video0/brightness is broken

Status in System76:
  Triaged
Status in nvidia-graphics-drivers-352 package in Ubuntu:
  Confirmed

Bug description:
  With nvidia-352 (and for that matter nvidia-346), the
  /sys/class/backlight interface is broken.

  Writing to /sys/class/backlight/acpi_video0/brightness has no effect,
  and reading from it returns a value that does not necessarily reflect
  the current brightness.

  I don't know when exactly this broke in the Nvidia driver, but I do
  know that not that long ago it worked because the system76-driver uses
  this to restore the previous backlight brightness level during boot. I
  believe this still worked with nvidia-343 and perhaps also worked in
  early nvidia-346 versions.

  This problem is somewhat masked because with Ubuntu (Unity), unity-
  settings-daemon has two code paths for setting the brightness:

  1) Using /sys/class/backlight

  2) Using xrandr, which as far as I can tell takes (roughly) the same
  approach as the `xbacklight` command line tool

  However, approach (2) does not work with Ubuntu GNOME because gnome-
  settings-daemon has dropped this code (it dropped gnome-settings-
  daemon/gsd-rr*).

  I've started digging into the dkms module source code, but haven't
  come up with anything yet. Of course, there is a chance the problem is
  in the closed proprietary bits.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: nvidia-352 352.63-0ubuntu0.15.10.1
  ProcVersionSignature: Ubuntu 4.2.0-18.22-generic 4.2.3
  Uname: Linux 4.2.0-18-generic x86_64
  NonfreeKernelModules: nvidia
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  352.63  Sat Nov  7 21:25:42 
PST 2015
   GCC version:  gcc version 5.2.1 20151010 (Ubuntu 5.2.1-22ubuntu2)
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Nov 20 15:01:42 2015
  DistUpgraded: Fresh install
  DistroCodename: wily
  DistroVariant: ubuntu
  DkmsStatus:
   bbswitch, 0.7, 4.2.0-18-generic, x86_64: installed
   fwts-efi-runtime-dkms, 15.09.00, 4.2.0-18-generic, x86_64: installed
   nvidia-352, 352.63, 4.2.0-18-generic, x86_64: installed
  GraphicsCard:
   NVIDIA Corporation GM204M [GeForce GTX 970M] [10de:1618] (rev a1) (prog-if 
00 [VGA controller])
     Subsystem: CLEVO/KAPOK Computer Device [1558:7701]
  MachineType: System76, Inc. Serval WS
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-18-generic.efi.signed 
root=UUID=d68b8062-f67c-495c-8c16-f2e11d9a9916 ro quiet splash
  SourcePackage: nvidia-graphics-drivers-352
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/09/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1.03.03RSY2
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: Serval WS
  dmi.board.vendor: System76, Inc.
  dmi.board.version: serw8-17g
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: System76, Inc.
  dmi.chassis.version: Serval WS
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.03.03RSY2:bd06/09/2015:svnSystem76,Inc.:pnServalWS:pvrserw8-17g:rvnSystem76,Inc.:rnServalWS:rvrserw8-17g:cvnSystem76,Inc.:ct9:cvrServalWS:
  dmi.product.name: Serval WS
  dmi.product.version: serw8-17g
  dmi.sys.vendor: System76, Inc.
  modified.conffile..etc.modprobe.d.nvidia.352.hybrid.conf: [deleted]
  version.compiz: compiz 1:0.9.12.2+15.10.20151015-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.64-1
  versio

[Desktop-packages] [Bug 1731392] [NEW] package inkscape 0.91-7ubuntu2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

[alejandro hurtado chacñama]

Public bug reported:

this problem always appears when starting the operating system

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: inkscape 0.91-7ubuntu2
ProcVersionSignature: Ubuntu 4.10.0-38.42~16.04.1-generic 4.10.17
Uname: Linux 4.10.0-38-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.10
Architecture: amd64
Date: Wed Nov  8 11:06:18 2017
ErrorMessage: subprocess installed post-installation script returned error exit 
status 1
InstallationDate: Installed on 2017-02-17 (265 days ago)
InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.2
 apt  1.2.24
SourcePackage: inkscape
Title: package inkscape 0.91-7ubuntu2 failed to install/upgrade: subprocess 
installed post-installation script returned error exit status 1
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-package xenial

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

Title:
  package inkscape 0.91-7ubuntu2 failed to install/upgrade: subprocess
  installed post-installation script returned error exit status 1

Status in inkscape package in Ubuntu:
  New

Bug description:
  this problem always appears when starting the operating system

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: inkscape 0.91-7ubuntu2
  ProcVersionSignature: Ubuntu 4.10.0-38.42~16.04.1-generic 4.10.17
  Uname: Linux 4.10.0-38-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  Date: Wed Nov  8 11:06:18 2017
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  InstallationDate: Installed on 2017-02-17 (265 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.24
  SourcePackage: inkscape
  Title: package inkscape 0.91-7ubuntu2 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/inkscape/+bug/1731392/+subscriptions

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

[Desktop-packages] [Bug 1682193] Re: Mouse acceleration significantly reduced after upgrade to 17.04

[Alejandro R. Mosteo]

#27, just to add to my previous post a few months ago, removing xserver-
xorg-input-libinput AND installing xserver-xorg-input-evdev fixed it for
me in several machines. What I additionally found is that the latter
package does not come preinstalled and just removing libinput will leave
you mouse/keyboardless in X.

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

Title:
  Mouse acceleration significantly reduced after upgrade to 17.04

Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  My external Logitech USB mouse was behaving nicely under 16.10 but
  after upgrade to 17.04 it has slowed down to a crawl. Settings
  slidebars are set at the maximum acceleration, but it only affects the
  touch pad, the mouse is extremely slow.

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

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

[Desktop-packages] [Bug 1706305] [NEW] package libnl-genl-3-200:amd64 3.2.29-0ubuntu2.1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempti

[Alejandro Martínez ballesteros]

Public bug reported:

I don't know what is the problem. I only have read the notification
telling me I have a problem in ubuntu.

ProblemType: Package
DistroRelease: Ubuntu 17.04
Package: libnl-genl-3-200:amd64 3.2.29-0ubuntu2.1
ProcVersionSignature: Ubuntu 4.10.0-28.32-generic 4.10.17
Uname: Linux 4.10.0-28-generic x86_64
ApportVersion: 2.20.4-0ubuntu4.5
Architecture: amd64
Date: Tue Jul 25 12:18:43 2017
Dependencies:
 gcc-6-base 6.3.0-12ubuntu2
 libc6 2.24-9ubuntu2.2
 libgcc1 1:6.3.0-12ubuntu2
 libnl-3-200 3.2.29-0ubuntu2.1
DuplicateSignature:
 package:libnl-genl-3-200:amd64:3.2.29-0ubuntu2.1
 Setting up mythes-en-au (2.1-5.4) ...
 dpkg: error processing package libnl-genl-3-200:amd64 (--configure):
  package is in a very bad inconsistent state; you should
ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
InstallationDate: Installed on 2017-07-24 (0 days ago)
InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
RelatedPackageVersions:
 dpkg 1.18.10ubuntu2
 apt  1.4
SourcePackage: libnl3
Title: package libnl-genl-3-200:amd64 3.2.29-0ubuntu2.1 failed to 
install/upgrade: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-package zesty

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

Title:
  package libnl-genl-3-200:amd64 3.2.29-0ubuntu2.1 failed to
  install/upgrade: package is in a very bad inconsistent state; you
  should  reinstall it before attempting configuration

Status in libnl3 package in Ubuntu:
  New

Bug description:
  I don't know what is the problem. I only have read the notification
  telling me I have a problem in ubuntu.

  ProblemType: Package
  DistroRelease: Ubuntu 17.04
  Package: libnl-genl-3-200:amd64 3.2.29-0ubuntu2.1
  ProcVersionSignature: Ubuntu 4.10.0-28.32-generic 4.10.17
  Uname: Linux 4.10.0-28-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4.5
  Architecture: amd64
  Date: Tue Jul 25 12:18:43 2017
  Dependencies:
   gcc-6-base 6.3.0-12ubuntu2
   libc6 2.24-9ubuntu2.2
   libgcc1 1:6.3.0-12ubuntu2
   libnl-3-200 3.2.29-0ubuntu2.1
  DuplicateSignature:
   package:libnl-genl-3-200:amd64:3.2.29-0ubuntu2.1
   Setting up mythes-en-au (2.1-5.4) ...
   dpkg: error processing package libnl-genl-3-200:amd64 (--configure):
package is in a very bad inconsistent state; you should
  ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
  InstallationDate: Installed on 2017-07-24 (0 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu2
   apt  1.4
  SourcePackage: libnl3
  Title: package libnl-genl-3-200:amd64 3.2.29-0ubuntu2.1 failed to 
install/upgrade: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1692671] Re: intel driver fails to reenable display

[Alejandro Mery]

** Attachment added: "lspci -v"
   
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1692671/+attachment/4881544/+files/lspci.txt

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

Title:
  intel driver fails to reenable display

Status in xorg package in Ubuntu:
  New

Bug description:
  if the display is sent to sleep it won't wake up. If I go to tty1 or
  tty2 I'm pulled back to tty7 (?) within seconds.

  sometimes if I ctrl-alt-del I'm sent back to the login screen and from
  there I can resume the session.

  everything was working fine with my previous (1920x1080) display, but
  since I switched to a 3840x2160 display the only reliable solution to
  get the computer back from blanking is pressing the power button. I
  can then see the shutdown "splash" and after powering it back again
  everything is back to normal. until it blanks the screen again
  obviusly

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-78.99-generic 4.4.62
  Uname: Linux 4.4.0-78-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Mon May 22 19:16:43 2017
  InstallationDate: Installed on 2015-12-27 (512 days ago)
  InstallationMedia: Xubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  SourcePackage: xorg
  UpgradeStatus: Upgraded to xenial on 2016-04-27 (389 days ago)

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

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

[Desktop-packages] [Bug 1692671] Re: intel driver fails to reenable display

[Alejandro Mery]

** Attachment added: "dmesg"
   
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1692671/+attachment/4881545/+files/dmesg.txt

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

Title:
  intel driver fails to reenable display

Status in xorg package in Ubuntu:
  New

Bug description:
  if the display is sent to sleep it won't wake up. If I go to tty1 or
  tty2 I'm pulled back to tty7 (?) within seconds.

  sometimes if I ctrl-alt-del I'm sent back to the login screen and from
  there I can resume the session.

  everything was working fine with my previous (1920x1080) display, but
  since I switched to a 3840x2160 display the only reliable solution to
  get the computer back from blanking is pressing the power button. I
  can then see the shutdown "splash" and after powering it back again
  everything is back to normal. until it blanks the screen again
  obviusly

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-78.99-generic 4.4.62
  Uname: Linux 4.4.0-78-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Mon May 22 19:16:43 2017
  InstallationDate: Installed on 2015-12-27 (512 days ago)
  InstallationMedia: Xubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  SourcePackage: xorg
  UpgradeStatus: Upgraded to xenial on 2016-04-27 (389 days ago)

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

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

[Desktop-packages] [Bug 1692671] Re: intel driver fails to reenable display

[Alejandro Mery]

** Attachment added: "sudo get-edid | parse-edid"
   
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1692671/+attachment/4881543/+files/edid.txt

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

Title:
  intel driver fails to reenable display

Status in xorg package in Ubuntu:
  New

Bug description:
  if the display is sent to sleep it won't wake up. If I go to tty1 or
  tty2 I'm pulled back to tty7 (?) within seconds.

  sometimes if I ctrl-alt-del I'm sent back to the login screen and from
  there I can resume the session.

  everything was working fine with my previous (1920x1080) display, but
  since I switched to a 3840x2160 display the only reliable solution to
  get the computer back from blanking is pressing the power button. I
  can then see the shutdown "splash" and after powering it back again
  everything is back to normal. until it blanks the screen again
  obviusly

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-78.99-generic 4.4.62
  Uname: Linux 4.4.0-78-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Mon May 22 19:16:43 2017
  InstallationDate: Installed on 2015-12-27 (512 days ago)
  InstallationMedia: Xubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  SourcePackage: xorg
  UpgradeStatus: Upgraded to xenial on 2016-04-27 (389 days ago)

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

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

[Desktop-packages] [Bug 1692671] [NEW] intel driver fails to reenable display

[Alejandro Mery]

Public bug reported:

if the display is sent to sleep it won't wake up. If I go to tty1 or
tty2 I'm pulled back to tty7 (?) within seconds.

sometimes if I ctrl-alt-del I'm sent back to the login screen and from
there I can resume the session.

everything was working fine with my previous (1920x1080) display, but
since I switched to a 3840x2160 display the only reliable solution to
get the computer back from blanking is pressing the power button. I can
then see the shutdown "splash" and after powering it back again
everything is back to normal. until it blanks the screen again obviusly

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg 1:7.7+13ubuntu3
ProcVersionSignature: Ubuntu 4.4.0-78.99-generic 4.4.62
Uname: Linux 4.4.0-78-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.5
Architecture: amd64
CurrentDesktop: XFCE
Date: Mon May 22 19:16:43 2017
InstallationDate: Installed on 2015-12-27 (512 days ago)
InstallationMedia: Xubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
SourcePackage: xorg
UpgradeStatus: Upgraded to xenial on 2016-04-27 (389 days ago)

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


** Tags: amd64 apport-bug xenial

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

Title:
  intel driver fails to reenable display

Status in xorg package in Ubuntu:
  New

Bug description:
  if the display is sent to sleep it won't wake up. If I go to tty1 or
  tty2 I'm pulled back to tty7 (?) within seconds.

  sometimes if I ctrl-alt-del I'm sent back to the login screen and from
  there I can resume the session.

  everything was working fine with my previous (1920x1080) display, but
  since I switched to a 3840x2160 display the only reliable solution to
  get the computer back from blanking is pressing the power button. I
  can then see the shutdown "splash" and after powering it back again
  everything is back to normal. until it blanks the screen again
  obviusly

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-78.99-generic 4.4.62
  Uname: Linux 4.4.0-78-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Mon May 22 19:16:43 2017
  InstallationDate: Installed on 2015-12-27 (512 days ago)
  InstallationMedia: Xubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  SourcePackage: xorg
  UpgradeStatus: Upgraded to xenial on 2016-04-27 (389 days ago)

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

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

[Desktop-packages] [Bug 1682193] Re: Mouse acceleration significantly reduced after upgrade to 17.04

[Alejandro R. Mosteo]

Just to confirm that removing xserver-xorg-input-libinput solved the
issue without [immediately evident] side effects. I had to reconfigure
the mouse speed in the GUI.

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

Title:
  Mouse acceleration significantly reduced after upgrade to 17.04

Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  My external Logitech USB mouse was behaving nicely under 16.10 but
  after upgrade to 17.04 it has slowed down to a crawl. Settings
  slidebars are set at the maximum acceleration, but it only affects the
  touch pad, the mouse is extremely slow.

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

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

[Desktop-packages] [Bug 1682193] Re: Mouse acceleration significantly reduced after upgrade to 17.04

[Alejandro R. Mosteo]

@loplop, surprisingly in my default installation the only mouse option
related to our problem in settings is labeled as "Mouse Speed" (Below
System Settings -> Mouse & Touchpad). Whatever it does behind the scenes
I can't but guess; in my duplicate bug #1683435 I reported seeing "Accel
Speed" in the capabilities listed by xinput. I too am used to being able
to differentiate between acceleration and precision somehow in other
desktops/OSs.

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

Title:
  Mouse acceleration significantly reduced after upgrade to 17.04

Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  My external Logitech USB mouse was behaving nicely under 16.10 but
  after upgrade to 17.04 it has slowed down to a crawl. Settings
  slidebars are set at the maximum acceleration, but it only affects the
  touch pad, the mouse is extremely slow.

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

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

[Desktop-packages] [Bug 1685443] [NEW] package pulseaudio-module-bluetooth 1:9.0-2ubuntu2.1 failed to install/upgrade: il pacchetto si trova in uno stato di inconsistenza critico: è consigliato insta

[Alejandro Figliolia]

Public bug reported:


alejandro@alejandro-HP-Pavilion-15-Notebook-PC:~$ sudo apt-get remove 
pulseaudio-module-bluetooth
[sudo] password di alejandro: 
Lettura elenco dei pacchetti... Fatto
Generazione albero delle dipendenze   
Lettura informazioni sullo stato... Fatto
I seguenti pacchetti saranno RIMOSSI:
  pulseaudio-module-bluetooth
0 aggiornati, 0 installati, 1 da rimuovere e 0 non aggiornati.
1 non completamente installati o rimossi.
Dopo quest'operazione, verranno liberati 285 kB di spazio su disco.
Continuare? [S/n] s
dpkg: errore nell'elaborare il pacchetto pulseaudio-module-bluetooth (--remove):
 il pacchetto si trova in uno stato di inconsistenza grave:
 è necessario installarlo nuovamente prima di rimuoverlo
Si sono verificati degli errori nell'elaborazione:
 pulseaudio-module-bluetooth
E: Sub-process /usr/bin/dpkg returned an error code (1)
alejandro@alejandro-HP-Pavilion-15-Notebook-PC:~$ sudo apt-get install 
pulseaudio-module-bluetooth
Lettura elenco dei pacchetti... Fatto
Generazione albero delle dipendenze   
Lettura informazioni sullo stato... Fatto
pulseaudio-module-bluetooth is already the newest version (1:9.0-2ubuntu2.1).
0 aggiornati, 0 installati, 0 da rimuovere e 0 non aggiornati.
1 non completamente installati o rimossi.
È necessario scaricare 0 B/56,5 kB di archivi.
Dopo quest'operazione, verranno occupati 0 B di spazio su disco.
Continuare? [S/n] s
dpkg: errore nell'elaborare il pacchetto pulseaudio-module-bluetooth 
(--configure):
 il pacchetto si trova in uno stato di inconsistenza critico: è consigliato
 installarlo nuovamente prima di tentare la configurazione.
Si sono verificati degli errori nell'elaborazione:
 pulseaudio-module-bluetooth
E: Sub-process /usr/bin/dpkg returned an error code (1)
alejandro@alejandro-HP-Pavilion-15-Notebook-PC:~$ sudo apt-get purge 
pulseaudio-module-bluetooth
Lettura elenco dei pacchetti... Fatto
Generazione albero delle dipendenze   
Lettura informazioni sullo stato... Fatto
I seguenti pacchetti saranno RIMOSSI:
  pulseaudio-module-bluetooth*
0 aggiornati, 0 installati, 1 da rimuovere e 0 non aggiornati.
1 non completamente installati o rimossi.
Dopo quest'operazione, verranno liberati 285 kB di spazio su disco.
Continuare? [S/n] s
dpkg: errore nell'elaborare il pacchetto pulseaudio-module-bluetooth (--remove):
 il pacchetto si trova in uno stato di inconsistenza grave:
 è necessario installarlo nuovamente prima di rimuoverlo
Si sono verificati degli errori nell'elaborazione:
 pulseaudio-module-bluetooth
E: Sub-process /usr/bin/dpkg returned an error code (1)

ProblemType: Package
DistroRelease: Ubuntu 16.10
Package: pulseaudio-module-bluetooth 1:9.0-2ubuntu2.1
ProcVersionSignature: Ubuntu 4.8.0-46.49-generic 4.8.17
Uname: Linux 4.8.0-46-generic x86_64
ApportVersion: 2.20.3-0ubuntu8.2
AptOrdering: NULL: ConfigurePending
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC1:  alejandro   2009 F.... pulseaudio
 /dev/snd/controlC0:  alejandro   2009 F pulseaudio
Date: Sat Apr 22 08:09:48 2017
DpkgTerminalLog:
 dpkg: errore nell'elaborare il pacchetto pulseaudio-module-bluetooth 
(--configure):
  il pacchetto si trova in uno stato di inconsistenza critico: è consigliato
  installarlo nuovamente prima di tentare la configurazione.
ErrorMessage: il pacchetto si trova in uno stato di inconsistenza critico: è 
consigliato  installarlo nuovamente prima di tentare la configurazione.
InstallationDate: Installed on 2017-04-13 (8 days ago)
InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions:
 dpkg 1.18.10ubuntu1
 apt  1.3.4
SourcePackage: pulseaudio
Title: package pulseaudio-module-bluetooth 1:9.0-2ubuntu2.1 failed to 
install/upgrade: il pacchetto si trova in uno stato di inconsistenza critico: è 
consigliato  installarlo nuovamente prima di tentare la configurazione.
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 11/26/2014
dmi.bios.vendor: Insyde
dmi.bios.version: F.67
dmi.board.asset.tag: Type2 - Board Asset Tag
dmi.board.name: 2166
dmi.board.vendor: Hewlett-Packard
dmi.board.version: 29.42
dmi.chassis.type: 10
dmi.chassis.vendor: Hewlett-Packard
dmi.chassis.version: Chassis Version
dmi.modalias: 
dmi:bvnInsyde:bvrF.67:bd11/26/2014:svnHewlett-Packard:pnHPPavilion15NotebookPC:pvr08961030410620100:rvnHewlett-Packard:rn2166:rvr29.42:cvnHewlett-Packard:ct10:cvrChassisVersion:
dmi.product.name: HP Pavilion 15 Notebook PC
dmi.product.version: 08961030410620100
dmi.sys.vendor: Hewlett-Packard

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


** Tags: amd64 apport-package yakkety

-- 
You received this bug notification because you are a member of Desktop
Packages, whic

[Desktop-packages] [Bug 1683435] [NEW] Mouse speed/acceleration ignored in 17.04

[Alejandro R. Mosteo]

Public bug reported:

After upgrading to 17.04 my mouse (a plain Logitech USB-PS/2 Optical
Mouse) is much slower and nothing I do changes its speed.

Tried through the settings GUI, using xset and using xinput. Nothing
seems to do anything. The only thing that offers some feedback is
xinput, that complaints about a value out of range:

$ xinput --set-prop 8 289 2
X Error of failed request:  BadValue (integer parameter out of range for 
operation)
  Major opcode of failed request:  131 (XInputExtension)
  Minor opcode of failed request:  57 ()
  Value in failed request:  0x121
  Serial number of failed request:  19
  Current serial number in output stream:  20
where 8 is the device id, 289 is the "libinput Accel Speed", and 2 is the 
desired multiplier:

$ xinput --list --short
⎡ Virtual core pointer  id=2[master pointer  (3)]
⎜   ↳ Virtual core XTEST pointerid=4[slave  pointer  (2)]
⎜   ↳ Logitech USB-PS/2 Optical Mouse   id=8[slave  pointer  (2)]
⎣ Virtual core keyboard id=3[master keyboard (2)]
↳ Virtual core XTEST keyboard   id=5[slave  keyboard (3)]
↳ Power Button  id=6[slave  keyboard (3)]
↳ Power Button  id=7[slave  keyboard (3)]
↳ Media Center Ed. eHome Infrared Remote Transceiver (185b:3020)id=9
[slave  keyboard (3)]
↳ LITEON Technology USB Multimedia Keyboard id=10   [slave  keyboard (3)]
↳ Nuvoton w836x7hg Infrared Remote Transceiver  id=11   [slave  
keyboard (3)]

Basically I can set that value in the range 0..1, with no effect
(although it is reported correctly by xinput --list-props), or outside
and getting the error. Likewise, changing values with xset shows them as
changed, but the mouse is oblivious to it.


Finally, I tried in a live USB and at least via the settings GUI there's no 
noticeable difference between either extreme setting of the slider.

ProblemType: Bug
DistroRelease: Ubuntu 17.04
Package: xorg 1:7.7+16ubuntu3
ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8
Uname: Linux 4.10.0-19-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
.proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
.proc.driver.nvidia.registry: Binary: ""
.proc.driver.nvidia.version:
 NVRM version: NVIDIA UNIX x86_64 Kernel Module  375.39  Tue Jan 31 20:47:00 
PST 2017
 GCC version:  gcc version 6.3.0 20170406 (Ubuntu 6.3.0-12ubuntu2)
.proc.driver.nvidia.warnings.fbdev:
 Your system is not currently configured to drive a VGA console
 on the primary VGA device. The NVIDIA Linux graphics driver
 requires the use of a text-mode VGA console. Use of other console
 drivers including, but not limited to, vesafb, may result in
 corruption and stability problems, and is not supported.
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.4-0ubuntu4
Architecture: amd64
BootLog: root: clean, 577548/2097152 files, 6029465/8388608 blocks
CompizPlugins: 
[core,bailer,detection,composite,opengl,decor,compiztoolbox,resize,regex,mousepoll,move,grid,vpswitch,animation,wall,gnomecompat,imgpng,place,snap,expo,unitymtgrabhandles,workarounds,fade,session,ezoom,scale,unityshell]
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
CurrentDesktop:
 
Date: Mon Apr 17 19:06:07 2017
DistUpgraded: 2017-04-17 14:10:56,823 DEBUG icon theme changed, re-reading
DistroCodename: zesty
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 NVIDIA Corporation GK208 [GeForce GT 730] [10de:1287] (rev a1) (prog-if 00 
[VGA controller])
   Subsystem: ASUSTeK Computer Inc. GK208 [GeForce GT 730] [1043:8525]
InstallationDate: Installed on 2014-03-13 (1130 days ago)
InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1)
MachineType: Tranquil PC IXLs
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-19-generic 
root=UUID=bb84f1b8-0976-403f-a1da-0a4d0b7de950 ro quiet splash vt.handoff=7
SourcePackage: xorg
UpgradeStatus: Upgraded to zesty on 2017-04-17 (0 days ago)
dmi.bios.date: 10/07/2011
dmi.bios.vendor: Intel Corp.
dmi.bios.version: BLH6710H.86A.0132.2011.1007.1505
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: DH67CF
dmi.board.vendor: Intel Corporation
dmi.board.version: AAG10215-204
dmi.chassis.type: 3
dmi.chassis.vendor: Tranquil PC
dmi.modalias: 
dmi:bvnIntelCorp.:bvrBLH6710H.86A.0132.2011.1007.1505:bd10/07/2011:svnTranquilPC:pnIXLs:pvr:rvnIntelCorporation:rnDH67CF:rvrAAG10215-204:cvnTranquilPC:ct3:cvr:
dmi.product.name: IXLs
dmi.sys.vendor: Tranquil PC
version.compiz: compiz 1:0.9.13.1+17.04.20170109-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.76-1
version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.3-1ubuntu1
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl

[Desktop-packages] [Bug 1652749] Re: Gnome Shell. Run gksudo from Activities Overview.

[Alejandro G . García]

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

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

Title:
  Gnome Shell. Run gksudo from Activities Overview.

Status in gksu package in Ubuntu:
  Invalid

Bug description:
  OS: Ubuntu 16.04.1 LTS (amd64)
  Package: gnome-shell 3.18.5-0ubuntu0.2
  Package: libgdk-pixbuf2.0-0:amd64 2.32.2-1ubuntu1.2

  When I try to run gksudo from the Activities Overview in Gnome Shell,
  the following exception occur.

  kernel: [ 1590.097250] traps: gksudo[5218] general protection
  ip:7fd4b5a3dbb1 sp:7ffcaa92a710 error:0 in
  libgdk-x11-2.0.so.0.2400.30[7fd4b59cd000+b]

  This only happen if I don't leave the Activities Overview.
  If I leave the Activities Overview just after run the command, not error 
happens. The gksudo window is showed for input the password and the application 
is launched correctly.

  Procedure:
  1. Open the Activities Overview in Gnome Shell.
  2. Press Alt + F2 and type "gksudo {any application}"
  3. Don't leave the Activities Overview and wait about 30 seconds.
  4. Nothing happens. Inspect the system log for gksudo exceptions.

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

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

[Desktop-packages] [Bug 1652749] [NEW] Gnome Shell. Run gksudo from Activities Overview.

[Alejandro G . García]

Public bug reported:

OS: Ubuntu 16.04.1 LTS (amd64)
Package: gnome-shell 3.18.5-0ubuntu0.2
Package: libgdk-pixbuf2.0-0:amd64 2.32.2-1ubuntu1.2

When I try to run gksudo from the Activities Overview in Gnome Shell,
the following exception occur.

kernel: [ 1590.097250] traps: gksudo[5218] general protection
ip:7fd4b5a3dbb1 sp:7ffcaa92a710 error:0 in
libgdk-x11-2.0.so.0.2400.30[7fd4b59cd000+b]

This only happen if I don't leave the Activities Overview.
If I leave the Activities Overview just after run the command, not error 
happens. The gksudo window is showed for input the password and the application 
is launched correctly.

Procedure:
1. Open the Activities Overview in Gnome Shell.
2. Press Alt + F2 and type "gksudo {any application}"
3. Don't leave the Activities Overview and wait about 30 seconds.
4. Nothing happens. Inspect the system log for gksudo exceptions.

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


** Tags: gksudo gnome-shell libgdk

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

Title:
  Gnome Shell. Run gksudo from Activities Overview.

Status in gksu package in Ubuntu:
  New

Bug description:
  OS: Ubuntu 16.04.1 LTS (amd64)
  Package: gnome-shell 3.18.5-0ubuntu0.2
  Package: libgdk-pixbuf2.0-0:amd64 2.32.2-1ubuntu1.2

  When I try to run gksudo from the Activities Overview in Gnome Shell,
  the following exception occur.

  kernel: [ 1590.097250] traps: gksudo[5218] general protection
  ip:7fd4b5a3dbb1 sp:7ffcaa92a710 error:0 in
  libgdk-x11-2.0.so.0.2400.30[7fd4b59cd000+b]

  This only happen if I don't leave the Activities Overview.
  If I leave the Activities Overview just after run the command, not error 
happens. The gksudo window is showed for input the password and the application 
is launched correctly.

  Procedure:
  1. Open the Activities Overview in Gnome Shell.
  2. Press Alt + F2 and type "gksudo {any application}"
  3. Don't leave the Activities Overview and wait about 30 seconds.
  4. Nothing happens. Inspect the system log for gksudo exceptions.

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

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

[Desktop-packages] [Bug 1612334] [NEW] package libglapi-mesa:i386 11.2.0-1ubuntu2.1 failed to install/upgrade: package libglapi-mesa:i386 is already installed and configured

[Alejandro Lemus]

Public bug reported:

mmnb ,mn

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: libglapi-mesa:i386 11.2.0-1ubuntu2.1
ProcVersionSignature: Ubuntu 4.4.0-34.53-generic 4.4.15
Uname: Linux 4.4.0-34-generic x86_64
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.1-0ubuntu2.1
AptdaemonVersion: 1.1.1+bzr982-0ubuntu14
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
Date: Fri Aug  5 00:00:04 2016
Dependencies:
 gcc-6-base 6.0.1-0ubuntu1
 libc6 2.23-0ubuntu3
 libgcc1 1:6.0.1-0ubuntu1
DistUpgraded: Fresh install
DistroCodename: xenial
DistroVariant: ubuntu
DkmsStatus:
 virtualbox, 5.0.24, 3.13.0-91-generic, x86_64: installed
 virtualbox, 5.0.24, 4.4.0-31-generic, x86_64: installed
 virtualbox, 5.0.24, 4.4.0-34-generic, x86_64: installed
DuplicateSignature:
 package:libglapi-mesa:i386:11.2.0-1ubuntu2.1
 Setting up ure (5.1.4-0ubuntu1) ...
 dpkg: error processing package libreoffice-style-breeze (--configure):
  no package named 'libreoffice-style-breeze' is installed, cannot configure
ErrorMessage: package libglapi-mesa:i386 is already installed and configured
GraphicsCard:
 Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller])
   Subsystem: Lenovo 2nd Generation Core Processor Family Integrated Graphics 
Controller [17aa:3975]
InstallationDate: Installed on 2014-04-10 (854 days ago)
InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
MachineType: LENOVO HuronRiver Platform
PackageArchitecture: i386
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-34-generic 
root=UUID=4e98a8b3-1dd5-495c-92ab-fe0cff0ef38c ro quiet splash vt.handoff=7
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.1
 apt  1.2.12~ubuntu16.04.1
SourcePackage: mesa
Title: package libglapi-mesa:i386 11.2.0-1ubuntu2.1 failed to install/upgrade: 
package libglapi-mesa:i386 is already installed and configured
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 10/27/2011
dmi.bios.vendor: LENOVO
dmi.bios.version: 44CN43WW
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: Emerald Lake
dmi.board.vendor: LENOVO
dmi.board.version: FAB1
dmi.chassis.asset.tag: Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: 0.1
dmi.modalias: 
dmi:bvnLENOVO:bvr44CN43WW:bd10/27/2011:svnLENOVO:pnHuronRiverPlatform:pvr0.1:rvnLENOVO:rnEmeraldLake:rvrFAB1:cvnLENOVO:ct10:cvr0.1:
dmi.product.name: HuronRiver Platform
dmi.product.version: 0.1
dmi.sys.vendor: LENOVO
version.compiz: compiz 1:0.9.12.2+16.04.20160714-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2.1
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2.1
version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2.3
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2
xserver.bootTime: Thu Aug 11 12:00:46 2016
xserver.configfile: default
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 product id 732 
 vendor LGD
xserver.version: 2:1.18.3-1ubuntu2.3

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


** Tags: already-installed apport-package compiz-0.9 i386 ubuntu xenial

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

Title:
  package libglapi-mesa:i386 11.2.0-1ubuntu2.1 failed to
  install/upgrade: package libglapi-mesa:i386 is already installed and
  configured

Status in mesa package in Ubuntu:
  New

Bug description:
  mmnb ,mn

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libglapi-mesa:i386 11.2.0-1ubuntu2.1
  ProcVersionSignature: Ubuntu 4.4.0-34.53-generic 4.4.15
  Uname: Linux 4.4.0-34-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.1
  AptdaemonVersion: 1.1.1+bzr982-0ubuntu14
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Fri Aug  5 00:00:04 2016
  Dependencies:
   gcc-6-base 6.0.1-0ubuntu1
   libc6 2.23-0ubuntu3
   libgcc1 1:6.0.1-0ubuntu1
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox, 5.0.24, 

[Desktop-packages] [Bug 1607799] Re: Dash freezes after U1 login

[Alejandro J. Cura]

I can confirm that the silo mentioned in #9 fixes the issue for me
(frieza, rc-proposed r161).

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

Title:
  Dash freezes after U1 login

Status in Canonical System Image:
  In Progress
Status in libsignon-glib package in Ubuntu:
  In Progress
Status in unity-scopes-api package in Ubuntu:
  Incomplete
Status in unity-scopes-shell package in Ubuntu:
  Incomplete
Status in unity8 package in Ubuntu:
  Incomplete

Bug description:
  Test case.
  - Without U1 account, go to Ubuntu Store.
  - Tap on an app.
  - Tap on the install button.
  - Introduce credentials.

  Expected result.
  - After credentials, the app is installed.

  Actual result.
  - Dash is frozen. Cannot go back to the scopes. Launcher and indicators do 
work, though. There is no crash.

  current build number: 389
  device name: arale
  channel: ubuntu-touch/rc-proposed/meizu.en

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1607799/+subscriptions

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

[Desktop-packages] [Bug 1597681] Re: [CTA] Enable WAPI support

[Alejandro J. Cura]

** Changed in: indicator-network (Ubuntu)
   Importance: Undecided => High

** Changed in: indicator-network (Ubuntu)
   Status: New => Confirmed

** Changed in: indicator-network (Ubuntu)
 Assignee: (unassigned) => Pete Woods (pete-woods)

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

Title:
  [CTA] Enable WAPI support

Status in Canonical System Image:
  Confirmed
Status in indicator-network package in Ubuntu:
  Confirmed
Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  The phone does not currently support WAPI [1]

  It should do so. As part of this, support for the SMS4 [2] cipher is
  also required.

  
  [1] 
https://en.wikipedia.org/wiki/WLAN_Authentication_and_Privacy_Infrastructure
  [2]: https://en.wikipedia.org/wiki/SMS4

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1597681/+subscriptions

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

[Desktop-packages] [Bug 1579837] Re: Issue after wizard with policykit

[Alejandro J. Cura]

** Changed in: canonical-devices-system-image
Milestone: 12 => backlog

** Changed in: canonical-devices-system-image
   Importance: High => Medium

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

Title:
  Issue after wizard with policykit

Status in Canonical System Image:
  In Progress
Status in accountsservice package in Ubuntu:
  Fix Released
Status in policykit-unity8 package in Ubuntu:
  Triaged
Status in ubuntu-system-settings package in Ubuntu:
  Incomplete

Bug description:
  STEPS:
  1. Bootstrap flash a fresh image to a device
  2. Run through the wizard selecting pin for authentication
  3. Tap on the get started button
  4. Phone freezes for a while
  5. At some point it unfreezes and you see the dash
  6. Reboot and get password login instead of pin login

  EXPECTED:
  I expect no freeze (possibly due to apport) and pin dialogue on reboot

  ACTUAL:
  I get a long freeze and on reboot instead of getting the pin dialogue to 
unlock the phone I get the password dialogue and full osk.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1579837/+subscriptions

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

[Desktop-packages] [Bug 1586379] Re: Microphone not working on MacBookpro 15 (version 8.2) and Xubuntu 16.04

[Alejandro Comisario]

anyone ?

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

Title:
  Microphone not working on MacBookpro 15 (version 8.2) and Xubuntu
  16.04

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  I have a Macbook pro 15 (version 8.2) with Xubuntu 14.04 the mic
  worked out of the box, with xubuntu 16.04

  * upgraded from 14.04
  * fresh install

  The mic does'nt get any signal, i have tried these:
  
http://askubuntu.com/questions/482626/microphone-not-working-on-ubuntu-14-04-on-macbookpro10-2

  with no luck.

  the output of the command:
  wget -O alsa-info.sh http://www.alsa-project.org/alsa-info.sh && chmod +x 
./alsa-info.sh && ./alsa-info.sh

  is here:
  http://www.alsa-project.org/db/?f=1a18a2a3188be0c68d960ae4e6d8ec2ccacb994d

  if please can anyone help me ? 
  not being able to use the microphone is killing me.

  thank you !

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

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

[Desktop-packages] [Bug 1586379] Re: Microphone not working on MacBookpro 15 (version 8.2) and Xubuntu 16.04

[Alejandro Comisario]

thank god, hope someone take it asap

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

Title:
  Microphone not working on MacBookpro 15 (version 8.2) and Xubuntu
  16.04

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  I have a Macbook pro 15 (version 8.2) with Xubuntu 14.04 the mic
  worked out of the box, with xubuntu 16.04

  * upgraded from 14.04
  * fresh install

  The mic does'nt get any signal, i have tried these:
  
http://askubuntu.com/questions/482626/microphone-not-working-on-ubuntu-14-04-on-macbookpro10-2

  with no luck.

  the output of the command:
  wget -O alsa-info.sh http://www.alsa-project.org/alsa-info.sh && chmod +x 
./alsa-info.sh && ./alsa-info.sh

  is here:
  http://www.alsa-project.org/db/?f=1a18a2a3188be0c68d960ae4e6d8ec2ccacb994d

  if please can anyone help me ? 
  not being able to use the microphone is killing me.

  thank you !

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

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

[Desktop-packages] [Bug 1586379] Re: Microphone not working on MacBookpro 15 (version 8.2) and Xubuntu 16.04

[Alejandro Comisario]

Hi, any help ?

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

Title:
  Microphone not working on MacBookpro 15 (version 8.2) and Xubuntu
  16.04

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  I have a Macbook pro 15 (version 8.2) with Xubuntu 14.04 the mic
  worked out of the box, with xubuntu 16.04

  * upgraded from 14.04
  * fresh install

  The mic does'nt get any signal, i have tried these:
  
http://askubuntu.com/questions/482626/microphone-not-working-on-ubuntu-14-04-on-macbookpro10-2

  with no luck.

  the output of the command:
  wget -O alsa-info.sh http://www.alsa-project.org/alsa-info.sh && chmod +x 
./alsa-info.sh && ./alsa-info.sh

  is here:
  http://www.alsa-project.org/db/?f=1a18a2a3188be0c68d960ae4e6d8ec2ccacb994d

  if please can anyone help me ? 
  not being able to use the microphone is killing me.

  thank you !

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

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

[Desktop-packages] [Bug 1586379] [NEW] Microphone not working on MacBookpro 15 (version 8.2) and Xubuntu 16.04

[Alejandro Comisario]

Public bug reported:

I have a Macbook pro 15 (version 8.2) with Xubuntu 14.04 the mic worked
out of the box, with xubuntu 16.04

* upgraded from 14.04
* fresh install

The mic does'nt get any signal, i have tried these:
http://askubuntu.com/questions/482626/microphone-not-working-on-ubuntu-14-04-on-macbookpro10-2

with no luck.

the output of the command:
wget -O alsa-info.sh http://www.alsa-project.org/alsa-info.sh && chmod +x 
./alsa-info.sh && ./alsa-info.sh

is here:
http://www.alsa-project.org/db/?f=1a18a2a3188be0c68d960ae4e6d8ec2ccacb994d

if please can anyone help me ? 
not being able to use the microphone is killing me.

thank you !

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

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

Title:
  Microphone not working on MacBookpro 15 (version 8.2) and Xubuntu
  16.04

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  I have a Macbook pro 15 (version 8.2) with Xubuntu 14.04 the mic
  worked out of the box, with xubuntu 16.04

  * upgraded from 14.04
  * fresh install

  The mic does'nt get any signal, i have tried these:
  
http://askubuntu.com/questions/482626/microphone-not-working-on-ubuntu-14-04-on-macbookpro10-2

  with no luck.

  the output of the command:
  wget -O alsa-info.sh http://www.alsa-project.org/alsa-info.sh && chmod +x 
./alsa-info.sh && ./alsa-info.sh

  is here:
  http://www.alsa-project.org/db/?f=1a18a2a3188be0c68d960ae4e6d8ec2ccacb994d

  if please can anyone help me ? 
  not being able to use the microphone is killing me.

  thank you !

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

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

[Desktop-packages] [Bug 1317860] Re: the phone should switch itself off before completely draining battery

[Alejandro J. Cura]

** Also affects: livecd-rootfs (Ubuntu)
   Importance: Undecided
   Status: New

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

** Changed in: livecd-rootfs (Ubuntu)
   Status: New => Fix Released

** Changed in: livecd-rootfs (Ubuntu)
 Assignee: (unassigned) => Xavi Garcia (xavi-garcia-mena)

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

Title:
  the phone should switch itself off before completely draining battery

Status in Canonical System Image:
  Fix Committed
Status in Ubuntu UX:
  Fix Committed
Status in indicator-power package in Ubuntu:
  Invalid
Status in livecd-rootfs package in Ubuntu:
  Fix Released
Status in upower package in Ubuntu:
  Invalid

Bug description:
  the phone should switch itself off at around ~5% remaining battery.

  This is to preserve a little battery for use cases such as:

  * turn it back on once or twice for urgent short phone calls
  * prevent the battery from going into a state where it can't be charged any 
more
  * have enough power to turn itself on again and trigger an alarm

  : "The device should hibernate
  (PC) or power off (phone/tablet) if both of these things are true: *
  there is less than 2% battery remaining * there has been more than 3%
  battery remaining at some point since the last time the device
  hibernated or powered off."

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1317860/+subscriptions

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

[Desktop-packages] [Bug 1317860] Re: the phone should switch itself off before completely draining battery

[Alejandro J. Cura]

** Changed in: canonical-devices-system-image
   Status: In Progress => Fix Committed

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

Title:
  the phone should switch itself off before completely draining battery

Status in Canonical System Image:
  Fix Committed
Status in Ubuntu UX:
  Fix Committed
Status in indicator-power package in Ubuntu:
  Invalid
Status in upower package in Ubuntu:
  Confirmed

Bug description:
  the phone should switch itself off at around ~5% remaining battery.

  This is to preserve a little battery for use cases such as:

  * turn it back on once or twice for urgent short phone calls
  * prevent the battery from going into a state where it can't be charged any 
more
  * have enough power to turn itself on again and trigger an alarm

  : "The device should hibernate
  (PC) or power off (phone/tablet) if both of these things are true: *
  there is less than 2% battery remaining * there has been more than 3%
  battery remaining at some point since the last time the device
  hibernated or powered off."

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1317860/+subscriptions

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

[Desktop-packages] [Bug 1567250] Re: ssh signin problem since OTA-10

[Alejandro J. Cura]

** Changed in: gnome-keyring (Ubuntu)
 Assignee: (unassigned) => Pete Woods (pete-woods)

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

** Changed in: indicator-network (Ubuntu)
 Assignee: Antti Kaijanmäki (kaijanmaki) => Pete Woods (pete-woods)

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

Title:
  ssh signin problem since OTA-10

Status in Canonical System Image:
  Confirmed
Status in Ubuntu Terminal App:
  Incomplete
Status in gnome-keyring package in Ubuntu:
  New
Status in indicator-network package in Ubuntu:
  Confirmed
Status in openssh package in Ubuntu:
  Invalid

Bug description:
  Not sure if this is a terminal or image issue, but here goes.

  Since the update last night to OTA-10 I cannot ssh to a server
  anymore. Error message: "Agent Admitted Failure To Sign Using The Key"

  On server side and client side nothing changed to the user settings or
  keys.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1567250/+subscriptions

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

[Desktop-packages] [Bug 1571522] Re: Detect captive WiFi hotspots

[Alejandro J. Cura]

** Changed in: canonical-devices-system-image
Milestone: None => 11

** Changed in: canonical-devices-system-image
Milestone: 11 => backlog

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

Title:
  Detect captive WiFi hotspots

Status in Canonical System Image:
  Confirmed
Status in indicator-network package in Ubuntu:
  Confirmed
Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  Right now it is very annoying that when you connect to a captive wifi
  portal, the device does not detect that. All other devices open the
  log in page automatically, except ubuntu devices. One needs to
  manually open the browser, type a url and get redirected before being
  able to log in and start e.g. telegram messaging over the wifi
  connection.

  My proposed solution to solve this:
  When a WiFi connection is established, indicator-network should do a http GET 
call to ubuntu.com. If the reply turns out to be a redirect, it should open the 
browser with the redirect url.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1571522/+subscriptions

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

[Desktop-packages] [Bug 1342123] Re: evolution-calendar-factory always running with high memory usage

[Alejandro J. Cura]

** Changed in: indicator-datetime (Ubuntu)
 Assignee: Charles Kerr (charlesk) => Renato Araujo Oliveira Filho 
(renatofilho)

** Changed in: canonical-devices-system-image
 Assignee: Alejandro J. Cura (alecu) => Bill Filler (bfiller)

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

Title:
  evolution-calendar-factory always running with high memory usage

Status in Canonical System Image:
  Confirmed
Status in evolution-data-server package in Ubuntu:
  Confirmed
Status in indicator-datetime package in Ubuntu:
  Confirmed

Bug description:
  At boot the process is using over 100MB on my mako (build 129)
  I sync'd a fairly large set of calendar events from google previously

  Does this process need to be running all the time?
  Can we streamline it to not read so much of the data set, which it appears to 
be doing?

  With no calendar entries (i.e. removing 
.local/share/evolution/xxx/calendar.ics) the process still uses over 30MB
  (looking at RSS with  ps aux --sort -rss )

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1342123/+subscriptions

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

[Desktop-packages] [Bug 1317860] Re: the phone should switch itself off before completely draining battery

[Alejandro J. Cura]

** Changed in: canonical-devices-system-image
Milestone: ww08-2016 => 11

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

Title:
  the phone should switch itself off before completely draining battery

Status in Canonical System Image:
  In Progress
Status in Ubuntu UX:
  Fix Committed
Status in indicator-power package in Ubuntu:
  Invalid
Status in upower package in Ubuntu:
  Confirmed

Bug description:
  the phone should switch itself off at around ~5% remaining battery.

  This is to preserve a little battery for use cases such as:

  * turn it back on once or twice for urgent short phone calls
  * prevent the battery from going into a state where it can't be charged any 
more
  * have enough power to turn itself on again and trigger an alarm

  : "The device should hibernate
  (PC) or power off (phone/tablet) if both of these things are true: *
  there is less than 2% battery remaining * there has been more than 3%
  battery remaining at some point since the last time the device
  hibernated or powered off."

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1317860/+subscriptions

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

[Desktop-packages] [Bug 1317860] Re: the phone should switch itself off before completely draining battery

[Alejandro J. Cura]

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

** Changed in: indicator-power (Ubuntu)
   Status: Triaged => Invalid

** Changed in: upower (Ubuntu)
 Assignee: (unassigned) => Xavi Garcia (xavi-garcia-mena)

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

** Changed in: canonical-devices-system-image
   Importance: Critical => High

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

Title:
  the phone should switch itself off before completely draining battery

Status in Canonical System Image:
  In Progress
Status in Ubuntu UX:
  Fix Committed
Status in indicator-power package in Ubuntu:
  Invalid
Status in upower package in Ubuntu:
  New

Bug description:
  the phone should switch itself off at around ~5% remaining battery.

  This is to preserve a little battery for use cases such as:

  * turn it back on once or twice for urgent short phone calls
  * prevent the battery from going into a state where it can't be charged any 
more
  * have enough power to turn itself on again and trigger an alarm

  : "The device should hibernate
  (PC) or power off (phone/tablet) if both of these things are true: *
  there is less than 2% battery remaining * there has been more than 3%
  battery remaining at some point since the last time the device
  hibernated or powered off."

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1317860/+subscriptions

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

[Desktop-packages] [Bug 1539634] Re: network-manager crashes when using libnl-3-200-3.21.1-1ubuntu1

[Claudio Alejandro Sanhueza Lobos]

Fixed after following this:

http://askubuntu.com/questions/727127/last-upgrade-crashes-network-
manager-no-internet-connection-no-applet

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

Title:
  network-manager crashes when using libnl-3-200-3.21.1-1ubuntu1

Status in network-manager package in Ubuntu:
  Fix Released
Status in network-manager source package in Trusty:
  Fix Committed

Bug description:
  [Triage Notes]

  This regression is caused by a libnl proposed update tracked in bug
  1511735. It has not been released as an update, only proposed as an
  update for early testing. If you volunteered to test proposed updates,
  then thank you. Your care and attention will stop this regression from
  hitting ordinary users, and we appreciate your contribution to Ubuntu.

  If you are not aware that you volunteered to test proposed updates,
  then please be aware that your system is configured to do so. In this
  case, you probably should turn this off. I'd appreciate if someone
  could explain how to do this in the comments.

  [Impact]

   * NetworkManager depends on libnl (libnl-3-200 libnl-genl-3-200
     libnl-route-3-200) and when libnl is updated to proposed
     3.2.21-1ubuntu1 NM segfaults due to libnl exposing a bug in NM
     validation packets.

     This affects the 0.98 release of NetworkManager and has already
     been fixed in newer releases.

   * Backporting fixes from upstream release is required to prevent
     NetworkManager from faulting which breaks networking on most
     Desktop releases.

   * All patches applied are already accepted upstream and newer Ubuntu
     releases are not affected.

   * Upgrading NetworkManager to 0.9.8.8-0ubuntu7.3 prior to updating
     libnl-3.2.21-1ubuntu1 is required to prevent NetworkManager crashing.

  [Test Case]

   * Reproduce crash test:
  1. Download 14.04.03 Desktop iso, amd64
  2. Launched in a VM, run from iso
  3. In terminal, enable proposed
  4. sudo apt-get install libnl-3-200 libnl-genl-3-200 libnl-route-3-200
  5. sudo restart network-manager
  #  note the nm-applet disappears as NM has now crashed, no network
     conn.
  6. dmesg to confirm network-manager crash
  7. sudo dpkg --install 
gir1.2-networkmanager-1.0_0.9.8.8-0ubuntu7.3_amd64.deb 
libnm-glib4_0.9.8.8-0ubuntu7.3_amd64.deb 
libnm-glib-vpn1_0.9.8.8-0ubuntu7.3_amd64.deb 
libnm-util2_0.9.8.8-0ubuntu7.3_amd64.deb 
network-manager_0.9.8.8-0ubuntu7.3_amd64.deb
  8. sudo start network-manager
  #  nm-applet reappears, network connectivity restored

   * Successful upgrade test:
     1. Download 14.04.03 Desktop iso, amd64
     2. Launched in a VM, run from iso
     3. In a terminal, sudo dpkg --install 
gir1.2-networkmanager-1.0_0.9.8.8-0ubuntu7.3_amd64.deb 
libnm-glib4_0.9.8.8-0ubuntu7.3_amd64.deb 
libnm-glib-vpn1_0.9.8.8-0ubuntu7.3_amd64.deb 
libnm-util2_0.9.8.8-0ubuntu7.3_amd64.deb 
network-manager_0.9.8.8-0ubuntu7.3_amd64.deb
     4. sudo restart network-manager  # NM still runs, no crash, net up
     5. enable trusty-proposed in /etc/apt/sources.list
     6. sudo apt-get update
     7. sudo apt-get install libnl-3-200 libnl-genl-3-200 libnl-route-3-200
     8. sudo restart network-manager  # NM still runs, no crash, net up.

  [Regression Potential]

   * NetworkManager is a highly visible package, so testing NetworkManager
     functionality is critical.  The patch does address the crash specificly
     introduced by the updated libnl SRU.

   * We need to ensure that users have installed this NetworkManager
     update before installing libnl3 update (special phasing needed).

  [Original Description]
  Testing out proposed libnl-3 package[1] exposed a bug in NM 0.98.

  After installing updated libnl3 and restarting networkmanager, NM
  crashes with:

  /var/log/syslog shows:
  init: network-manager main process (1057) killed by SEGV signal
  init: network-manager main process ended, respawning
  init: network-manager main process (1065) killed by SEGV signal
  init: network-manager respawning too fast, stopped

  The bug has been fixed in upstream 0.98 with these patches:

  
http://cgit.freedesktop.org/NetworkManager/NetworkManager/commit/?id=8e4576b9fdb5c888d20a13aa2cc198df790dba54
  
http://cgit.freedesktop.org/NetworkManager/NetworkManager/commit/?id=65981edb9f562c07e78815c98093da67c50bfdcf

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

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

[Desktop-packages] [Bug 1536195] Re: Can't receive calls and sms while the other SIM is using data

[Alejandro J. Cura]

** Summary changed:

- Can't receive calls and sms while Hotspot is active 
+ Can't receive calls and sms while the other SIM is using data

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

Title:
  Can't receive calls and sms while the other SIM is using data

Status in indicator-network package in Ubuntu:
  Invalid
Status in network-manager package in Ubuntu:
  Invalid
Status in ofono package in Ubuntu:
  Invalid

Bug description:
  Using 2 Sim Cards
  Sim 1 for using telephone calls (Provider: Telering (Austria))
  Sim 2 for using mobile internet (Provider: 3 AT; this Sim is a Data-Only Sim)

  While activating Hotspot (using/sharing the internet using Sim 2) I
  cant receive any calls (number from Sim 1) or SMS. When calling me the
  caller always get a message from tel-provider: "The customer is
  currently not accessible...", it seems like the phone switched of. But
  I can make calls during the phone is in "Hotspot"-mode without
  problems.

  Calls and SMS are related to SIM 1
  Data is related to Sim 2 (is running in 2G/3G mode)

  After ending Hotspot I am not reachable at all. I have to reboot (sometimes 
twice) to be accessible again.
  --

  Using bq Aquarius E4.5 Ubuntu Edition
  with
  Ubuntu 15.04 OTA-8.5 20151210

  Phone is runing as it was delivered, no developer mode
  -

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

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

[Desktop-packages] [Bug 1484589] Re: Spurious volume notification when changing output role with headphones

[Alejandro J. Cura]

** Changed in: canonical-devices-system-image
Milestone: ww46-2015 => ww02-2016

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

Title:
  Spurious volume notification when changing output role with headphones

Status in Canonical System Image:
  Fix Committed
Status in indicator-sound package in Ubuntu:
  Fix Committed
Status in pulseaudio package in Ubuntu:
  New

Bug description:
  Ubuntu 15.04 r90

  1. Install the "Maroon in Trouble" game.
  2. With headphones connected, start a new game.
  3. After a while, disconnect the headphones.

  What happens:
  2. There's a volume notification each time a sound plays.
  3. There are no more volume notifications.

  What should happen:
  2. There are no volume notifications, because neither the sound output nor 
the volume is changing.

  : "When the primary sound
  output changes for any reason except an app request, or when the sound
  volume changes for any reason, a confirmation bubble should appear ...
  There should be no special notification when the active output role
  changes."

  This could be a side-effect of bug 1418210, but probably not, since it
  is idempotent: the notifications keep happening even if you don't
  change the volume in the meantime.

  [Split off bug 1478506.]

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1484589/+subscriptions

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

[Desktop-packages] [Bug 1512307] Re: fglrx and fglrx-updates install crashes system: no screen access possible

[Alejandro Mery]

same problem with AMD E2-1800.
00:01.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] 
Wrestler [Radeon HD 7340]

I can shortly see a kernel panic before it jumps back to graphic mode
and freezes permanently but I haven't been able to capture the text yet.

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

Title:
  fglrx and fglrx-updates install crashes system: no screen access
  possible

Status in fglrx-installer package in Ubuntu:
  Confirmed

Bug description:
  affected version: Ubuntu 15.10 64bit 
  using the Ubuntu "Additional drivers" function it shows:
  AMD/ ATI: Kaveri [Radeon R7 Graphics]

  with options:
  x.org. ...
  fglrx-updates
  fglrx

  choosing fglrx or fglrx-updates initiates the install. No errors
  reported in this stage.

  After a system REBOOT:

  - boot-up process stops at splashscreen
  - no access to terminal possible (CTRL+ALT+...) is not showing any results.
  - display port is inactive (monitor is switching to standby)
  - no LAN / WLAN access (SSH impossible)

  Hardware shutdown:
  - reboot is showing no effect
  - reboot 4sec is exiting as expected

  The fglrx install was repeated 3 times on this machine (followed by fresh 
install)
  also showing same behavior on an AMD E-450

  error was not present in 15.04 or 14.04LTS

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: ubuntu-release-upgrader-core 1:15.10.14
  ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3
  Uname: Linux 4.2.0-16-generic x86_64
  ApportVersion: 2.19.1-0ubuntu4
  Architecture: amd64
  CrashDB: ubuntu
  CurrentDesktop: Unity
  Date: Mon Nov  2 11:39:25 2015
  InstallationDate: Installed on 2015-10-26 (6 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: dist-upgrade
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/fglrx-installer/+bug/1512307/+subscriptions

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

[Desktop-packages] [Bug 1507769] Re: App store does not display images

[Alejandro J. Cura]

** Changed in: indicator-network (Ubuntu)
 Assignee: (unassigned) => Pete Woods (pete-woods)

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

Title:
  App store does not display images

Status in Canonical System Image:
  Confirmed
Status in indicator-network package in Ubuntu:
  New
Status in network-manager package in Ubuntu:
  New
Status in qtbase-opensource-src package in Ubuntu:
  New
Status in unity8 package in Ubuntu:
  Confirmed

Bug description:
  On both mako and arale using latest rc-proposed
  No images are loaded in the app store view
  I noticed free showed less than 100MB available on the mako
  Closing a few apps and refreshing loaded the images, as did  a reboot on the 
arale.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1507769/+subscriptions

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

[Desktop-packages] [Bug 1458046] Re: [touch] NetworkManager needs to inhibit sleep if hotspot is active

[Alejandro J. Cura]

Reassigning since Pete is working on this

** Changed in: indicator-network (Ubuntu)
 Assignee: Alejandro J. Cura (alecu) => Pete Woods (pete-woods)

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

Title:
  [touch] NetworkManager needs to inhibit sleep if hotspot is active

Status in Canonical System Image:
  Confirmed
Status in indicator-network package in Ubuntu:
  New
Status in network-manager package in Ubuntu:
  Confirmed
Status in ubuntu-system-settings package in Ubuntu:
  New
Status in network-manager package in Ubuntu RTM:
  Confirmed

Bug description:
  As Ubuntu touch uses an auto-suspend model, it's possible for the
  system to be suspended while a user has a hotspot active and in use.

  In order to prevent such behavior, we should modify NetworkManager to
  inhibit suspend via powerd's DBus interface when hotspot is active and
  one or more clients are connected to the hotspot.   As a first pass,
  inhibiting suspend when hotspot is active would probably be
  sufficient.   This could probably be implemented via a NM dispatcher
  script, which would run when the hotspot is activated.

  <https://wiki.ubuntu.com/Networking#hotspot-power>:
  "* Whenever at least one person is using your hotspot, the device should not 
sleep automatically.
  * The indicator icon should be different when anyone is connected than when 
no-one is.
  * If a hotspot is set up, there should be a “Hotspot” item in the “Ways to 
reduce battery use” list in “Power” settings."

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1458046/+subscriptions

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

[Desktop-packages] [Bug 1466273] Re: gstreamer fails intermittently

[Alejandro J. Cura]

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

** Package changed: gstreamer (Ubuntu) => gstreamer0.10 (Ubuntu)

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

Title:
  gstreamer fails intermittently

Status in Thumbnail generator for all kinds of files:
  New
Status in gstreamer0.10 package in Ubuntu:
  New

Bug description:
  gstreamer occasionally fails to extract a thumbnail from a video file.
  It's clearly a race condition because, almost all of the time, it
  succeeds. To reproduce:

  Check out the thumbnailer/devel branch at r217 and build it. Then:

  cd build/src/vs-thumb

  ./vs-thumb fd://0 ./x.jpg <../../../tests/media/testvideo.ogg

  Point a browser at the generated x.jpg file and check that the image
  was extracted correctly.

  Now run

  while ./vs-thumb fd://0 ./x.jpg <../../../tests/media/testvideo.ogg ;
  do :; done

  Within maybe a hundred iterations or so, I get:

  Error creating thumbnail: ThumbnailExtractor: change_state(): reading
  async messages: GStreamer error: negotiation problem.

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

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

[Desktop-packages] [Bug 1459235] Re: Google Address book: Unable to open address book

[Alejandro Espinosa]

Same for me.
In the error message details you can see that it tries to redirect to 
https://developers.google.com/accounts/docs/AuthForInstalledApps where you can 
read:

"ClientLogin has been officially deprecated since April 20, 2012 and is
now no longer available. Requests to ClientLogin will fail with a HTTP
404 response. We encourage you to migrate to OAuth 2.0 as soon as
possible."

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

Title:
  Google Address book: Unable to open address book

Status in evolution package in Ubuntu:
  Confirmed

Bug description:
  Since today (2015-05-27) I've been getting this message when trying to
  open my Google address book:

  Unable to open address book

  This address book cannot be opened.  This either means that an
  incorrect URI was entered, or the server is unreachable.

  Detailed error message: Unable to connect to 'Google address book':
  The requested resource was not found:
  https://developers.google.com/accounts/docs/AuthForInstalledApps

  
  Running standard Evolution ( 3.10.4) on Ubuntu 14.04.2 LTS

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

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

[Desktop-packages] [Bug 1268257] Re: nvidia-331-updates 331.38-0ubuntu3: nvidia-331-updates kernel module failed to build, with only error: "objdump: '... .tmp_nv.o': No such file"

[alejandro coca galviz]

** Changed in: nvidia-graphics-drivers-331-updates (Ubuntu)
 Assignee: (unassigned) => alejandro coca galviz (alejandro-coca-galviz)

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

Title:
  nvidia-331-updates 331.38-0ubuntu3: nvidia-331-updates kernel module
  failed to build, with only error: "objdump: '... .tmp_nv.o': No such
  file"

Status in NVIDIA Drivers Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-331 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-331-updates package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-340 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-340-updates package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-346 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-346-updates package in Ubuntu:
  Fix Released

Bug description:
  **WARNING:** This bug has been widely reported and has *many*
  automatic subscribers. Please be considerate.

  **If you need help:** try searching and asking on
  http://discourse.ubuntu.com or http://ubuntuforums.org or contacting a
  nearby user group (see http://loco.ubuntu.com or search for "LUG" in
  your area). Link back to this bug for clarity.

  ---

  This seems to fix it (at least for one version upgrade) for many
  people

  $ sudo dpkg-reconfigure nvidia-331

  after that...

  $ sudo dpkg-reconfigure nvidia-331-uvm

  (some users may be on the versions of these packages suffixed with
  -updates )

  Update 2015-05-23:
  As of the recent kernel update (3.13.0-53), the above two commands followed 
by a reboot may not fix it. Instead:

  $ sudo apt-get install --reinstall nvidia-331 nvidia-331-uvm

  followed by a reboot.

  ---

  **If you want to unsubscribe:** see
  https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-
  drivers-331-updates/+bug/1268257/+subscribe. You can also change your
  settings so you don't get comments but do get notified when the bug is
  solved - see https://askubuntu.com/questions/576523 for details.

  **If you want to comment:** Please consider if you have something
  meaningful to contribute to the 2500+ people who will get an email.

  **If you are an Ubuntu developer:** thanks for looking into this! :D

  

  Nvidia kernel module failed to build on kernel 3.13.0-2
  Yesterday when the new kernel was pushed, the dkms process failed.

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: nvidia-331-updates 331.20-0ubuntu9
  ProcVersionSignature: Ubuntu 3.12.0-7.15-generic 3.12.4
  Uname: Linux 3.12.0-7-generic x86_64
  ApportVersion: 2.13.1-0ubuntu1
  Architecture: amd64
  DKMSKernelVersion: 3.13.0-2-generic
  Date: Sun Jan 12 01:28:35 2014
  InstallationDate: Installed on 2013-11-03 (69 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  PackageVersion: 331.20-0ubuntu9
  SourcePackage: nvidia-graphics-drivers-331-updates
  Title: nvidia-331-updates 331.20-0ubuntu9: nvidia-331-updates kernel module 
failed to build
  UpgradeStatus: Upgraded to trusty on 2013-12-29 (13 days ago)

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

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

[Desktop-packages] [Bug 1449829] [NEW] There was an error playing video from the webcam after taking photo.

[Alejandro Morales Lepe]

Public bug reported:

Cheese fails to capture video from the webcam after taking a photo.
Running Cheese from the terminal prompts the following error:

libv4l2: error setting pixformat: Device or resource busy

(cheese:5170): cheese-WARNING **: Device '/dev/video0' is busy: 
gstv4l2object.c(2838): gst_v4l2_object_set_format (): 
/GstCameraBin:camerabin/GstWrapperCameraBinSrc:camera_source/GstBin:bin18/GstV4l2Src:video_source:
Call to S_FMT failed for YU12 @ 640x480: Device or resource busy


My camera needs the r5u87x firmware from this PPA: 
https://launchpad.net/~r5u87x-loader/+archive/ubuntu/ppa

ProblemType: Bug
DistroRelease: Ubuntu 15.04
Package: cheese 3.14.1-2ubuntu4
ProcVersionSignature: Ubuntu 3.19.0-15.15-generic 3.19.3
Uname: Linux 3.19.0-15-generic i686
ApportVersion: 2.17.2-0ubuntu1
Architecture: i386
CurrentDesktop: Unity
Date: Tue Apr 28 20:20:38 2015
InstallationDate: Installed on 2015-04-28 (0 days ago)
InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release i386 (20150422)
SourcePackage: cheese
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: apport-bug i386 vivid

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

Title:
  There was an error playing video from the webcam after taking photo.

Status in cheese package in Ubuntu:
  New

Bug description:
  Cheese fails to capture video from the webcam after taking a photo.
  Running Cheese from the terminal prompts the following error:

  libv4l2: error setting pixformat: Device or resource busy

  (cheese:5170): cheese-WARNING **: Device '/dev/video0' is busy: 
gstv4l2object.c(2838): gst_v4l2_object_set_format (): 
/GstCameraBin:camerabin/GstWrapperCameraBinSrc:camera_source/GstBin:bin18/GstV4l2Src:video_source:
  Call to S_FMT failed for YU12 @ 640x480: Device or resource busy

  
  My camera needs the r5u87x firmware from this PPA: 
  https://launchpad.net/~r5u87x-loader/+archive/ubuntu/ppa

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: cheese 3.14.1-2ubuntu4
  ProcVersionSignature: Ubuntu 3.19.0-15.15-generic 3.19.3
  Uname: Linux 3.19.0-15-generic i686
  ApportVersion: 2.17.2-0ubuntu1
  Architecture: i386
  CurrentDesktop: Unity
  Date: Tue Apr 28 20:20:38 2015
  InstallationDate: Installed on 2015-04-28 (0 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release i386 (20150422)
  SourcePackage: cheese
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1318815] Re: xinput settings not persistent

[Alejandro Druetta]

I have the same problem with xinput. I resolved it temporarily with a
script, but it isn't such a great solution.

Ubuntu 14.04.2
Unity 7.2.4

** Tags added: xinput

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

Title:
  xinput settings not persistent

Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  When I set some mouse/touchpad settings and log off/on (or reboot) the
  settings are lost.

  As a workaround I tried putting the corresponding xinput lines in
  .xsessionrc (as suggested somewhere) but that does not help either.

  I am not sure who exactly would be responsible for saving the settings
  so in case: I'm using xfce.

  [This is offtopic but I would have loved to report this using ubuntu-
  bug but this crashes itself every time it starts -- which is often.]

  My versions are:
  Ubuntu 14.04
  xserver-xorg 1:7.7+1ubuntu8
  xfce 4.10.1

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

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

[Desktop-packages] [Bug 1316035] Re: matrox g200eR2 is unclaimed in 14.04

[Alejandro Azario]

Me too, same problem with eight HP ProLiant Gen8 DL380p, video card
Matrox Electronics Systems Ltd. MGA G200EH.

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

Title:
  matrox g200eR2 is unclaimed in 14.04

Status in xorg-server package in Ubuntu:
  Confirmed

Bug description:
  On a certified Dell PowerEdge T620 server
  (http://www.ubuntu.com/certification/hardware/201207-11426/)

  The matrox video card is not recognised:
  lspci | grep VGA
  0a:00.0 VGA compatible controller: Matrox Electronics Systems Ltd. G200eR2

  lshw -C display
*-display UNCLAIMED 
 description: VGA compatible controller
 product: G200eR2
 vendor: Matrox Electronics Systems Ltd.
 physical id: 0
 bus info: pci@:0a:00.0
 version: 00
 width: 32 bits
 clock: 33MHz
 capabilities: pm vga_controller bus_master cap_list
 configuration: latency=64 maxlatency=32 mingnt=16
 resources: memory:d800-d8ff memory:deffc000-deff 
memory:de00-de7f

  Thus xserver is not hardver accelerated.

  Also /dev/dri and /dev/dri/card0 is missing.

  kernel module mga is not loaded, although if i manually load by modprobe it 
works fine
  modprobe mga
  lsmod | grep mga
  mga40811  0 
  drm   302817  1 mga

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

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

[Desktop-packages] [Bug 1373968] Re: GUI does not work after update

[Alejandro Dubrovsky]

I had the same issue. Turned out to be that the kernel that was actually
running was not the same as the one that was being installed and,
supposedly, the nvidia driver was compiling against.

Do a 'uname -a' and check to see if you are running what you think you
are running (in my case 3.11.0 vs 3.13.0). Also, an 'lsmod | grep
nvidia' showed nothing on mine.

Installing linux-generic and a reboot solved the issue for me (ie 'sudo
apt-get install linux-generic')

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

Title:
  GUI does not work after update

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

Bug description:
  After logging into PC today and running the software updater, various
  system updates were downloaded. I was promped to restart, which I did.
  At reboot, the system would get as far as displaying the login screen.
  After I entered my password, the system appears to hang, with no disk
  activity. I have a dual monitor system, but only the left monitor is
  active, in that it displays a purple Ubuntu splash screen, without the
  login box. I have tried restarting a number of times, but the result
  is always the same. I can log in by using the advanced options and
  drop into the root console.

  I am using Ubuntu 14.04.1 LTS.
  uname -a reports 3.11.0-20-generic #34-Ubuntu SMP Tue Apr 1 20:40:25 UTC 2014 
x86_64 x86_64 x86_64 GNU/Linux

  Hardware is a Dell Precision T3400

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

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

[Desktop-packages] [Bug 1365695] Re: No longer able to use GUI after update

[Alejandro Dubrovsky]

Some people are reporting the "blank" (background) screen before the login, 
some after. Are they the same bug? 
(I suffer from the after-login variety)

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

Title:
  No longer able to use GUI after update

Status in “nvidia-graphics-drivers-304-updates” package in Ubuntu:
  Confirmed
Status in “nvidia-graphics-drivers-331” package in Ubuntu:
  Confirmed
Status in “nvidia-graphics-drivers-331-updates” package in Ubuntu:
  Confirmed
Status in “ubuntu-drivers-common” package in Ubuntu:
  Fix Released
Status in “xserver-xorg-video-intel” package in Ubuntu:
  Confirmed
Status in “nvidia-graphics-drivers-304-updates” source package in Trusty:
  Confirmed
Status in “nvidia-graphics-drivers-331” source package in Trusty:
  Confirmed
Status in “nvidia-graphics-drivers-331-updates” source package in Trusty:
  Confirmed
Status in “ubuntu-drivers-common” source package in Trusty:
  Triaged
Status in “xserver-xorg-video-intel” source package in Trusty:
  Incomplete

Bug description:
  Until yesterday the 14.04 install on this Thinkpad T530 (nvidia
  Optimus) with nvidia-331 drivers worked just fine, including excellent
  multi-monitor behavior. Yesterday the set of packages below [1] was
  updated. I shut down, booted this morning and found out that I was not
  shown the lightdm login screen: I was stuck at the purple screen that
  precedes it (into which I enter my disk encryption password).

  Now the funny thing is that I could hear the lightdm startup sound and
  could actually login by typing my password (disk activity and started
  processes verify I am actually logged in), but I can't see anything:
  I'm still stuck at the puple screen.

  Uninstalling the nvidia drivers solved the problem: I'm typing this in
  a browser window using the nouveau drivers.

  I atttempted switching to nvidia-304, but that doesn't work either.
  Using those drivers I am shown the lightdm login screen, but after
  logging in I'm stuck with a screen showing only the background image.
  Nothing else is available, no keyboard or mouse trickery will reveal
  any menu, dialog or terminal to gain access.

  Since nouveau doesn't support a multi-monitor setup, it would be great
  if I someone could tell me how to get the nvidia drivers working
  again.

  Some things I noticed:
  - .xsession-errors reported 'Xlib:  extension "GLX" missing on display ":0"'
  - /var/log/Xorg.0.log reported 'setversion 1.4 failed: Permission denied'

  [1] The packages that were updated:

  Start-Date: 2014-09-03  15:07:38
  Upgrade: libsystemd-login0:amd64 (204-5ubuntu20.4, 204-5ubuntu20.5), 
systemd-services:amd64 (204-5ubuntu20.4, 204-5ubuntu20.5), librbd1:amd64 
(0.80.1-0ubuntu1.1, 0.80.5-0ubuntu0.14.04.1), ubuntu-drivers-common:amd64 
(0.2.91.5, 0.2.91.6), libsystemd-daemon0:amd64 (204-5ubuntu20.4, 
204-5ubuntu20.5), libgudev-1.0-0:amd64 (204-5ubuntu20.4, 204-5ubuntu20.5), 
libgudev-1.0-0:i386 (204-5ubuntu20.4, 204-5ubuntu20.5), libpam-systemd:amd64 
(204-5ubuntu20.4, 204-5ubuntu20.5), librados2:amd64 (0.80.1-0ubuntu1.1, 
0.80.5-0ubuntu0.14.04.1), shotwell-common:amd64 (0.18.0-0ubuntu4.1, 
0.18.0-0ubuntu4.2), udev:amd64 (204-5ubuntu20.4, 204-5ubuntu20.5), 
shotwell:amd64 (0.18.0-0ubuntu4.1, 0.18.0-0ubuntu4.2), gir1.2-gudev-1.0:amd64 
(204-5ubuntu20.4, 204-5ubuntu20.5), libudev-dev:amd64 (204-5ubuntu20.4, 
204-5ubuntu20.5), libudev1:amd64 (204-5ubuntu20.4, 204-5ubuntu20.5), 
libudev1:i386 (204-5ubuntu20.4, 204-5ubuntu20.5), 
xserver-xorg-video-intel:amd64 (2.99.910-0ubuntu1, 2.99.910-0ubuntu1.1), 
libsystemd-journal0:amd64 (204-5ubuntu20.4, 204-5ubuntu20.5), rsyslog:amd64 
(7.4.4-1ubuntu2, 7.4.4-1ubuntu2.1)
  End-Date: 2014-09-03  15:08:06

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: nvidia-current-updates (not installed)
  ProcVersionSignature: Ubuntu 3.13.0-35.62-generic 3.13.11.6
  Uname: Linux 3.13.0-35-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.14.1-0ubuntu3.3
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Thu Sep  4 22:07:11 2014
  SourcePackage: nvidia-graphics-drivers-304-updates
  UpgradeStatus: Upgraded to trusty on 2014-06-03 (93 days ago)

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

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

[Desktop-packages] [Bug 1247366] Re: Evolution is missing bogofilter integration

[Alejandro Arcos]

I did not write that use Ubuntu 14.04 and evolution 3.10.4  
I remove bogofilter :-( 
But spamassasin not work perfectly :-( 
I that I can help?

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

Title:
  Evolution is missing bogofilter integration

Status in “evolution” package in Ubuntu:
  Confirmed

Bug description:
  On fresh install and after upgrade to Ubuntu 13.10, Evolution is
  missing bogofilter integration.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: evolution 3.8.4-0ubuntu1
  ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3
  Uname: Linux 3.11.0-12-generic x86_64
  ApportVersion: 2.12.5-0ubuntu2.1
  Architecture: amd64
  Date: Sat Nov  2 05:15:42 2013
  ExecutablePath: /usr/bin/evolution
  InstallationDate: Installed on 2013-10-27 (6 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  MarkForUpload: True
  SourcePackage: evolution
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1247366] Re: Evolution is missing bogofilter integration

[Alejandro Arcos]

I have the same problem. When remove spamassassin:

Error while performing operation.

Failed to spawn SpamAssassin (/usr/bin/sa-learn --spam --no-sync
--local): Failed to execute child process "/usr/bin/sa-learn" (No such
file or directory)

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

Title:
  Evolution is missing bogofilter integration

Status in “evolution” package in Ubuntu:
  Confirmed

Bug description:
  On fresh install and after upgrade to Ubuntu 13.10, Evolution is
  missing bogofilter integration.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: evolution 3.8.4-0ubuntu1
  ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3
  Uname: Linux 3.11.0-12-generic x86_64
  ApportVersion: 2.12.5-0ubuntu2.1
  Architecture: amd64
  Date: Sat Nov  2 05:15:42 2013
  ExecutablePath: /usr/bin/evolution
  InstallationDate: Installed on 2013-10-27 (6 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  MarkForUpload: True
  SourcePackage: evolution
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 619595] Re: texlive-publishers requieres texlive-fonts-recommend

[Oscar Alejandro Amado Sarmiento]

This problem was solved a lot time ago. I had need to install another
latex package, but I don´t remember what was.

** Changed in: texlive-extra (Ubuntu)
   Status: Confirmed => Invalid

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

Title:
  texlive-publishers requieres texlive-fonts-recommend

Status in “texlive-extra” package in Ubuntu:
  Invalid

Bug description:
  I'm using texlive-publishers but when I try to create a document, I
  can't. Is necesary to install  texlive-fonts-recommend to be able to
  create documents like IEEEtran

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/texlive-extra/+bug/619595/+subscriptions

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

[Desktop-packages] [Bug 1284635]

[I Alejandro Fleischer]

I can't stop or modify receiving mails from this bug. Could you please help
me.

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

Title:
  IBus does not support certain keyboard layouts

Status in “ibus” package in Ubuntu:
  Triaged
Status in “ibus” source package in Trusty:
  Triaged

Bug description:
  installed trusty beta1 with keyboard layout set correctly during
  install

  install completes, login to new install - layout as set during install

  once logged in - layout set to US and keyboard layout set during
  install is missing from list

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: keyboard-configuration 1.70ubuntu8
  ProcVersionSignature: Ubuntu 3.13.0-12.32-generic 3.13.4
  Uname: Linux 3.13.0-12-generic i686
  ApportVersion: 2.13.2-0ubuntu5
  Architecture: i386
  CurrentDesktop: XFCE
  Date: Tue Feb 25 12:55:56 2014
  InstallationDate: Installed on 2014-02-25 (0 days ago)
  InstallationMedia: Xubuntu 14.04 LTS "Trusty Tahr" - Alpha i386 (20140225)
  PackageArchitecture: all
  SourcePackage: console-setup
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1307608] Re: failed login for app install, resulted in "install" button

[Alejandro J. Cura]

** Changed in: signon (Ubuntu)
   Status: Incomplete => Invalid

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

Title:
  failed login for app install, resulted in "install" button

Status in “signon” package in Ubuntu:
  Invalid
Status in “ubuntuone-credentials” package in Ubuntu:
  Triaged
Status in “unity-scope-click” package in Ubuntu:
  Invalid

Bug description:
  On devel-proposed 
  Ubuntu 14.04 LTS - armhf (20140414)

  steps to repro:
  1. freshly flashed device
  2. navigate to Apps scope
  3. select an app from "Available"
  4. click "install", which prompts to "go to accounts", click it
  5. settings acct animates fwd presenting accounts list, select ubuntu1
  6. enter user name, then enter wrong password without correcting, return 
to the same app preview
  7. click "install", the app scopes then seems lost...all previews seem to go 
blank

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

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