from:"Fernando"

Time that I opened Firefox through the GUI.
mai 30 16:40:37 fernando-Latitude-E5500 systemd[1562]: Started 
snap.firefox.firefox.b2449455-56d8-4537-8f78-5f51a04cd9a5.scope.

First logs after I entered the link at Firefox.
mai 30 16:41:43 fernando-Latitude-E5500 rtkit-daemon[1259]: Supervising 7 
threads of 4 processes of 1 users.
mai 30 16:41:43 fernando-Latitude-E5500 rtkit-daemon[1259]: Supervising 7 
threads of 4 processes of 1 users.
mai 30 16:41:43 fernando-Latitude-E5500 pulseaudio[1575]: X11 I/O error handler 
called
mai 30 16:41:43 fernando-Latitude-E5500 at-spi-bus-launcher[1921]: X connection 
to :0 broken (explicit kill or server shutdown).

16:41:43 is the exact time the session crashed.


** Attachment added: "Logs reproducing the issue."
   
https://bugs.launchpad.net/ubuntu-mate/+bug/1976161/+attachment/5593923/+files/journalctl-after-issue.log

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

Title:
  Session restarts when opening Pluma or GitHub link in browser

Status in Ubuntu MATE:
  New
Status in firefox package in Ubuntu:
  Incomplete
Status in snapd package in Ubuntu:
  Incomplete

Bug description:
  From a fresh install with Ubuntu Mate 22.04, do:

  1. Login into your user with password.
  2. Open Firefox.
  3. Enter "https://github.com/pimlie/ubuntu-mainline-kernel.sh; at URL address.
  4. GUI will reset and go back to login screen like started a new session.

  This also happens when I tried with opening a '.log' with Pluma.

  I've tried a lot of things at other installation to tackle this problem, but 
I couldn't solve the problem.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: MATE
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2022-05-27 (1 days ago)
  InstallationMedia: Ubuntu-MATE 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  ProcVersionSignature: Ubuntu 5.15.0-33.34-generic 5.15.30
  Snap: snapd 2.55.5 (latest/stable)
  Snap.Changes:
   ID   Status  Spawn  Ready  Summary
   3Done2022-05-28T10:43:02-03:00  2022-05-28T10:46:00-03:00  
Auto-refresh snaps "core20", "firefox", "snapd"
  Tags:  jammy
  Uname: Linux 5.15.0-33-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True

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


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

[Desktop-packages] [Bug 1976161] Re: Session restarts when opening Pluma or GitHub link in browser

** Attachment removed: "journalctl-after-issue.log"

https://bugs.launchpad.net/ubuntu-mate/+bug/1976161/+attachment/5593896/+files/journalctl-after-issue.log

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

Title:
Session restarts when opening Pluma or GitHub link in browser

Status in Ubuntu MATE:
New
Status in firefox package in Ubuntu:
Incomplete
Status in snapd package in Ubuntu:
Incomplete

Bug description:
From a fresh install with Ubuntu Mate 22.04, do:

1. Login into your user with password.
2. Open Firefox.
3. Enter "https://github.com/pimlie/ubuntu-mainline-kernel.sh; at URL address.
4. GUI will reset and go back to login screen like started a new session.

This also happens when I tried with opening a '.log' with Pluma.

I've tried a lot of things at other installation to tackle this problem, but
I couldn't solve the problem.
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu82.1
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: MATE
DistroRelease: Ubuntu 22.04
InstallationDate: Installed on 2022-05-27 (1 days ago)
InstallationMedia: Ubuntu-MATE 22.04 LTS "Jammy Jellyfish" - Release amd64
(20220419)
ProcVersionSignature: Ubuntu 5.15.0-33.34-generic 5.15.30
Snap: snapd 2.55.5 (latest/stable)
Snap.Changes:
ID Status Spawn Ready Summary
3Done2022-05-28T10:43:02-03:00 2022-05-28T10:46:00-03:00
Auto-refresh snaps "core20", "firefox", "snapd"
Tags: jammy
Uname: Linux 5.15.0-33-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
_MarkForUpload: True

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

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

[Desktop-packages] [Bug 1976161] Re: Session restarts when opening Pluma or GitHub link in browser

I don't recall which time exactly, sorry! I will delete the previous log
and send a new one with the time it crashed.

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

Title:
  Session restarts when opening Pluma or GitHub link in browser

Status in Ubuntu MATE:
  New
Status in firefox package in Ubuntu:
  Incomplete
Status in snapd package in Ubuntu:
  Incomplete

Bug description:
  From a fresh install with Ubuntu Mate 22.04, do:

  1. Login into your user with password.
  2. Open Firefox.
  3. Enter "https://github.com/pimlie/ubuntu-mainline-kernel.sh; at URL address.
  4. GUI will reset and go back to login screen like started a new session.

  This also happens when I tried with opening a '.log' with Pluma.

  I've tried a lot of things at other installation to tackle this problem, but 
I couldn't solve the problem.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: MATE
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2022-05-27 (1 days ago)
  InstallationMedia: Ubuntu-MATE 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  ProcVersionSignature: Ubuntu 5.15.0-33.34-generic 5.15.30
  Snap: snapd 2.55.5 (latest/stable)
  Snap.Changes:
   ID   Status  Spawn  Ready  Summary
   3Done2022-05-28T10:43:02-03:00  2022-05-28T10:46:00-03:00  
Auto-refresh snaps "core20", "firefox", "snapd"
  Tags:  jammy
  Uname: Linux 5.15.0-33-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True

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


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

[Desktop-packages] [Bug 1976161] Re: Session restarts when opening Pluma or GitHub link in browser

Sebastien, here's the log file from the command after the issue.

** Attachment added: "journalctl-after-issue.log"

https://bugs.launchpad.net/ubuntu-mate/+bug/1976161/+attachment/5593896/+files/journalctl-after-issue.log

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

Title:
Session restarts when opening Pluma or GitHub link in browser

Status in Ubuntu MATE:
New
Status in firefox package in Ubuntu:
Incomplete
Status in snapd package in Ubuntu:
Incomplete

Bug description:
From a fresh install with Ubuntu Mate 22.04, do:

This also happens when I tried with opening a '.log' with Pluma.

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

[Desktop-packages] [Bug 1976161] Re: Session restarts when opening Pluma or GitHub link in browser

Hi Alberto, I used the "echo $XDG_SESSION_TYPE" to check the display
server and it returned "x11", which I assume it's Xorg (don't know
anything about this).

I will attach the new logs for the commands you've asked.

** Attachment added: "Contains the commands asked by Alberto"

https://bugs.launchpad.net/ubuntu-mate/+bug/1976161/+attachment/5593895/+files/xdg-snapdesk.zip

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

Title:
Session restarts when opening Pluma or GitHub link in browser

Status in Ubuntu MATE:
New
Status in firefox package in Ubuntu:
Incomplete
Status in snapd package in Ubuntu:
Incomplete

Bug description:
From a fresh install with Ubuntu Mate 22.04, do:

This also happens when I tried with opening a '.log' with Pluma.

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

[Desktop-packages] [Bug 1976161] Snap.Info.snapd.txt

apport information

** Attachment added: "Snap.Info.snapd.txt"
   
https://bugs.launchpad.net/bugs/1976161/+attachment/5593555/+files/Snap.Info.snapd.txt

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

Title:
  Session restarts when opening Pluma or GitHub link in browser

Status in Ubuntu MATE:
  New
Status in firefox package in Ubuntu:
  New
Status in snapd package in Ubuntu:
  New

Bug description:
  From a fresh install with Ubuntu Mate 22.04, do:

  1. Login into your user with password.
  2. Open Firefox.
  3. Enter "https://github.com/pimlie/ubuntu-mainline-kernel.sh; at URL address.
  4. GUI will reset and go back to login screen like started a new session.

  This also happens when I tried with opening a '.log' with Pluma.

  I've tried a lot of things at other installation to tackle this problem, but 
I couldn't solve the problem.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: MATE
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2022-05-27 (1 days ago)
  InstallationMedia: Ubuntu-MATE 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  ProcVersionSignature: Ubuntu 5.15.0-33.34-generic 5.15.30
  Snap: snapd 2.55.5 (latest/stable)
  Snap.Changes:
   ID   Status  Spawn  Ready  Summary
   3Done2022-05-28T10:43:02-03:00  2022-05-28T10:46:00-03:00  
Auto-refresh snaps "core20", "firefox", "snapd"
  Tags:  jammy
  Uname: Linux 5.15.0-33-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True

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


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

[Desktop-packages] [Bug 1976161] Snap.Connections.txt

apport information

** Attachment added: "Snap.Connections.txt"
   
https://bugs.launchpad.net/bugs/1976161/+attachment/5593554/+files/Snap.Connections.txt

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

Title:
  Session restarts when opening Pluma or GitHub link in browser

Status in Ubuntu MATE:
  New
Status in firefox package in Ubuntu:
  New
Status in snapd package in Ubuntu:
  New

Bug description:
  From a fresh install with Ubuntu Mate 22.04, do:

  1. Login into your user with password.
  2. Open Firefox.
  3. Enter "https://github.com/pimlie/ubuntu-mainline-kernel.sh; at URL address.
  4. GUI will reset and go back to login screen like started a new session.

  This also happens when I tried with opening a '.log' with Pluma.

  I've tried a lot of things at other installation to tackle this problem, but 
I couldn't solve the problem.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: MATE
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2022-05-27 (1 days ago)
  InstallationMedia: Ubuntu-MATE 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  ProcVersionSignature: Ubuntu 5.15.0-33.34-generic 5.15.30
  Snap: snapd 2.55.5 (latest/stable)
  Snap.Changes:
   ID   Status  Spawn  Ready  Summary
   3Done2022-05-28T10:43:02-03:00  2022-05-28T10:46:00-03:00  
Auto-refresh snaps "core20", "firefox", "snapd"
  Tags:  jammy
  Uname: Linux 5.15.0-33-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True

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


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

[Desktop-packages] [Bug 1976161] Re: Session restarts when opening Pluma or GitHub link in browser

apport information

** Tags added: apport-collected

** Description changed:

  From a fresh install with Ubuntu Mate 22.04, do:
  
  1. Login into your user with password.
  2. Open Firefox.
  3. Enter "https://github.com/pimlie/ubuntu-mainline-kernel.sh; at URL address.
  4. GUI will reset and go back to login screen like started a new session.
  
  This also happens when I tried with opening a '.log' with Pluma.
  
- I've tried a lot of things at other installation to tackle this problem,
- but I couldn't solve the problem.
+ I've tried a lot of things at other installation to tackle this problem, but 
I couldn't solve the problem.
+ --- 
+ ProblemType: Bug
+ ApportVersion: 2.20.11-0ubuntu82.1
+ Architecture: amd64
+ CasperMD5CheckResult: pass
+ CurrentDesktop: MATE
+ DistroRelease: Ubuntu 22.04
+ InstallationDate: Installed on 2022-05-27 (1 days ago)
+ InstallationMedia: Ubuntu-MATE 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
+ ProcVersionSignature: Ubuntu 5.15.0-33.34-generic 5.15.30
+ Snap: snapd 2.55.5 (latest/stable)
+ Snap.Changes:
+  ID   Status  Spawn  Ready  Summary
+  3Done2022-05-28T10:43:02-03:00  2022-05-28T10:46:00-03:00  
Auto-refresh snaps "core20", "firefox", "snapd"
+ Tags:  jammy
+ Uname: Linux 5.15.0-33-generic x86_64
+ UpgradeStatus: No upgrade log present (probably fresh install)
+ UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
+ _MarkForUpload: True

** Attachment added: "Dependencies.txt"
   
https://bugs.launchpad.net/bugs/1976161/+attachment/5593551/+files/Dependencies.txt

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

Title:
  Session restarts when opening Pluma or GitHub link in browser

Status in Ubuntu MATE:
  New
Status in firefox package in Ubuntu:
  New
Status in snapd package in Ubuntu:
  New

Bug description:
  From a fresh install with Ubuntu Mate 22.04, do:

  1. Login into your user with password.
  2. Open Firefox.
  3. Enter "https://github.com/pimlie/ubuntu-mainline-kernel.sh; at URL address.
  4. GUI will reset and go back to login screen like started a new session.

  This also happens when I tried with opening a '.log' with Pluma.

  I've tried a lot of things at other installation to tackle this problem, but 
I couldn't solve the problem.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: MATE
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2022-05-27 (1 days ago)
  InstallationMedia: Ubuntu-MATE 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  ProcVersionSignature: Ubuntu 5.15.0-33.34-generic 5.15.30
  Snap: snapd 2.55.5 (latest/stable)
  Snap.Changes:
   ID   Status  Spawn  Ready  Summary
   3Done2022-05-28T10:43:02-03:00  2022-05-28T10:46:00-03:00  
Auto-refresh snaps "core20", "firefox", "snapd"
  Tags:  jammy
  Uname: Linux 5.15.0-33-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True

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


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

[Desktop-packages] [Bug 1976161] ProcEnviron.txt

apport information

** Attachment added: "ProcEnviron.txt"
   
https://bugs.launchpad.net/bugs/1976161/+attachment/5593553/+files/ProcEnviron.txt

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

Title:
  Session restarts when opening Pluma or GitHub link in browser

Status in Ubuntu MATE:
  New
Status in firefox package in Ubuntu:
  New
Status in snapd package in Ubuntu:
  New

Bug description:
  From a fresh install with Ubuntu Mate 22.04, do:

  1. Login into your user with password.
  2. Open Firefox.
  3. Enter "https://github.com/pimlie/ubuntu-mainline-kernel.sh; at URL address.
  4. GUI will reset and go back to login screen like started a new session.

  This also happens when I tried with opening a '.log' with Pluma.

  I've tried a lot of things at other installation to tackle this problem, but 
I couldn't solve the problem.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: MATE
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2022-05-27 (1 days ago)
  InstallationMedia: Ubuntu-MATE 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  ProcVersionSignature: Ubuntu 5.15.0-33.34-generic 5.15.30
  Snap: snapd 2.55.5 (latest/stable)
  Snap.Changes:
   ID   Status  Spawn  Ready  Summary
   3Done2022-05-28T10:43:02-03:00  2022-05-28T10:46:00-03:00  
Auto-refresh snaps "core20", "firefox", "snapd"
  Tags:  jammy
  Uname: Linux 5.15.0-33-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True

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


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

[Desktop-packages] [Bug 1976161] ProcCpuinfoMinimal.txt

apport information

** Attachment added: "ProcCpuinfoMinimal.txt"
   
https://bugs.launchpad.net/bugs/1976161/+attachment/5593552/+files/ProcCpuinfoMinimal.txt

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

Title:
  Session restarts when opening Pluma or GitHub link in browser

Status in Ubuntu MATE:
  New
Status in firefox package in Ubuntu:
  New
Status in snapd package in Ubuntu:
  New

Bug description:
  From a fresh install with Ubuntu Mate 22.04, do:

  1. Login into your user with password.
  2. Open Firefox.
  3. Enter "https://github.com/pimlie/ubuntu-mainline-kernel.sh; at URL address.
  4. GUI will reset and go back to login screen like started a new session.

  This also happens when I tried with opening a '.log' with Pluma.

  I've tried a lot of things at other installation to tackle this problem, but 
I couldn't solve the problem.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: MATE
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2022-05-27 (1 days ago)
  InstallationMedia: Ubuntu-MATE 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  ProcVersionSignature: Ubuntu 5.15.0-33.34-generic 5.15.30
  Snap: snapd 2.55.5 (latest/stable)
  Snap.Changes:
   ID   Status  Spawn  Ready  Summary
   3Done2022-05-28T10:43:02-03:00  2022-05-28T10:46:00-03:00  
Auto-refresh snaps "core20", "firefox", "snapd"
  Tags:  jammy
  Uname: Linux 5.15.0-33-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True

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


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

[Desktop-packages] [Bug 1937126] Re: Multiple docks visible

2021-07-31 Thread Fernando Fernandes Bonadio

Ok agora entendi, desculpe por isso.

** Attachment added: "settings.txt"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1937126/+attachment/5515026/+files/settings.txt

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

Title:
  Multiple docks visible

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  I downloaded version 21.04 of ubuntu, then I realized that when I downloaded 
the gnome shell tweaking tool, I realized that when I changed the theme of the 
dock and added in the top bar the option to show the option of locations on the 
system, it leaves my language after performing some accesses in the application 
menu this behavior appears.
  I also noticed that by accessing the applications menu the dock that I 
modified to appear in the lower corner of the screen is now also displayed on 
the left side of my monitor.
  I apologize for the English, but I live in Brazil and I am not fluent in this 
language.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: xorg 1:7.7+22ubuntu1
  ProcVersionSignature: Ubuntu 5.11.0-22.23-generic 5.11.21
  Uname: Linux 5.11.0-22-generic x86_64
  ApportVersion: 2.20.11-0ubuntu65.1
  Architecture: amd64
  BootLog: Error: [Errno 13] Permissão negada: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Jul 21 16:23:56 2021
  DistUpgraded: Fresh install
  DistroCodename: hirsute
  DistroVariant: ubuntu
  DkmsStatus: virtualbox, 6.1.18, 5.11.0-22-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation WhiskeyLake-U GT2 [UHD Graphics 620] [8086:3ea0] (rev 02) 
(prog-if 00 [VGA controller])
 Subsystem: Lenovo UHD Graphics 620 (Whiskey Lake) [17aa:3f1a]
  InstallationDate: Installed on 2021-07-17 (3 days ago)
  InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 174f:1176 Syntek Integrated Camera
   Bus 001 Device 002: ID :3825   USB OPTICAL MOUSE
   Bus 001 Device 004: ID 8087:0a2a Intel Corp. Bluetooth wireless interface
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 81S9
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-22-generic 
root=UUID=fce98fbf-751a-4700-bbe5-628c5a913425 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/24/2020
  dmi.bios.release: 1.50
  dmi.bios.vendor: LENOVO
  dmi.bios.version: ASCN50WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40679 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo IdeaPad S145-15IWL
  dmi.ec.firmware.release: 1.50
  dmi.modalias: 
dmi:bvnLENOVO:bvrASCN50WW:bd11/24/2020:br1.50:efr1.50:svnLENOVO:pn81S9:pvrLenovoIdeaPadS145-15IWL:rvnLENOVO:rnLNVNB161216:rvrSDK0J40679WIN:cvnLENOVO:ct10:cvrLenovoIdeaPadS145-15IWL:
  dmi.product.family: IdeaPad S145-15IWL
  dmi.product.name: 81S9
  dmi.product.sku: LENOVO_MT_81S9_BU_idea_FM_IdeaPad S145-15IWL
  dmi.product.version: Lenovo IdeaPad S145-15IWL
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.105-3~21.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.1-2
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.11-1ubuntu1.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200714-1ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1

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


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

[Desktop-packages] [Bug 1937126] Re: bug found

2021-07-27 Thread Fernando Fernandes Bonadio

Este é o bug que estava comentando, hoje após a sessão ser bloqueada ao
realizar o login o bug aparece.

** Attachment added: "bug encontrado"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1937126/+attachment/5514110/+files/Captura%20de%20tela%20de%202021-07-27%2014-01-40.png

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

Title:
  bug found

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  I downloaded version 21.04 of ubuntu, then I realized that when I downloaded 
the gnome shell tweaking tool, I realized that when I changed the theme of the 
dock and added in the top bar the option to show the option of locations on the 
system, it leaves my language after performing some accesses in the application 
menu this behavior appears.
  I also noticed that by accessing the applications menu the dock that I 
modified to appear in the lower corner of the screen is now also displayed on 
the left side of my monitor.
  I apologize for the English, but I live in Brazil and I am not fluent in this 
language.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: xorg 1:7.7+22ubuntu1
  ProcVersionSignature: Ubuntu 5.11.0-22.23-generic 5.11.21
  Uname: Linux 5.11.0-22-generic x86_64
  ApportVersion: 2.20.11-0ubuntu65.1
  Architecture: amd64
  BootLog: Error: [Errno 13] Permissão negada: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Jul 21 16:23:56 2021
  DistUpgraded: Fresh install
  DistroCodename: hirsute
  DistroVariant: ubuntu
  DkmsStatus: virtualbox, 6.1.18, 5.11.0-22-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation WhiskeyLake-U GT2 [UHD Graphics 620] [8086:3ea0] (rev 02) 
(prog-if 00 [VGA controller])
 Subsystem: Lenovo UHD Graphics 620 (Whiskey Lake) [17aa:3f1a]
  InstallationDate: Installed on 2021-07-17 (3 days ago)
  InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 174f:1176 Syntek Integrated Camera
   Bus 001 Device 002: ID :3825   USB OPTICAL MOUSE
   Bus 001 Device 004: ID 8087:0a2a Intel Corp. Bluetooth wireless interface
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 81S9
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-22-generic 
root=UUID=fce98fbf-751a-4700-bbe5-628c5a913425 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/24/2020
  dmi.bios.release: 1.50
  dmi.bios.vendor: LENOVO
  dmi.bios.version: ASCN50WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40679 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo IdeaPad S145-15IWL
  dmi.ec.firmware.release: 1.50
  dmi.modalias: 
dmi:bvnLENOVO:bvrASCN50WW:bd11/24/2020:br1.50:efr1.50:svnLENOVO:pn81S9:pvrLenovoIdeaPadS145-15IWL:rvnLENOVO:rnLNVNB161216:rvrSDK0J40679WIN:cvnLENOVO:ct10:cvrLenovoIdeaPadS145-15IWL:
  dmi.product.family: IdeaPad S145-15IWL
  dmi.product.name: 81S9
  dmi.product.sku: LENOVO_MT_81S9_BU_idea_FM_IdeaPad S145-15IWL
  dmi.product.version: Lenovo IdeaPad S145-15IWL
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.105-3~21.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.1-2
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.11-1ubuntu1.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200714-1ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1

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


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

[Desktop-packages] [Bug 1937126] Re: bug found

2021-07-27 Thread Fernando Fernandes Bonadio

Eu n�o consegui executar este comando gsettings list-recursively
org.gnome.shell > settings.txt

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

Title:
  bug found

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  I downloaded version 21.04 of ubuntu, then I realized that when I downloaded 
the gnome shell tweaking tool, I realized that when I changed the theme of the 
dock and added in the top bar the option to show the option of locations on the 
system, it leaves my language after performing some accesses in the application 
menu this behavior appears.
  I also noticed that by accessing the applications menu the dock that I 
modified to appear in the lower corner of the screen is now also displayed on 
the left side of my monitor.
  I apologize for the English, but I live in Brazil and I am not fluent in this 
language.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: xorg 1:7.7+22ubuntu1
  ProcVersionSignature: Ubuntu 5.11.0-22.23-generic 5.11.21
  Uname: Linux 5.11.0-22-generic x86_64
  ApportVersion: 2.20.11-0ubuntu65.1
  Architecture: amd64
  BootLog: Error: [Errno 13] Permissão negada: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Jul 21 16:23:56 2021
  DistUpgraded: Fresh install
  DistroCodename: hirsute
  DistroVariant: ubuntu
  DkmsStatus: virtualbox, 6.1.18, 5.11.0-22-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation WhiskeyLake-U GT2 [UHD Graphics 620] [8086:3ea0] (rev 02) 
(prog-if 00 [VGA controller])
 Subsystem: Lenovo UHD Graphics 620 (Whiskey Lake) [17aa:3f1a]
  InstallationDate: Installed on 2021-07-17 (3 days ago)
  InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 174f:1176 Syntek Integrated Camera
   Bus 001 Device 002: ID :3825   USB OPTICAL MOUSE
   Bus 001 Device 004: ID 8087:0a2a Intel Corp. Bluetooth wireless interface
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 81S9
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-22-generic 
root=UUID=fce98fbf-751a-4700-bbe5-628c5a913425 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/24/2020
  dmi.bios.release: 1.50
  dmi.bios.vendor: LENOVO
  dmi.bios.version: ASCN50WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40679 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo IdeaPad S145-15IWL
  dmi.ec.firmware.release: 1.50
  dmi.modalias: 
dmi:bvnLENOVO:bvrASCN50WW:bd11/24/2020:br1.50:efr1.50:svnLENOVO:pn81S9:pvrLenovoIdeaPadS145-15IWL:rvnLENOVO:rnLNVNB161216:rvrSDK0J40679WIN:cvnLENOVO:ct10:cvrLenovoIdeaPadS145-15IWL:
  dmi.product.family: IdeaPad S145-15IWL
  dmi.product.name: 81S9
  dmi.product.sku: LENOVO_MT_81S9_BU_idea_FM_IdeaPad S145-15IWL
  dmi.product.version: Lenovo IdeaPad S145-15IWL
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.105-3~21.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.1-2
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.11-1ubuntu1.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200714-1ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1

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


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

[Desktop-packages] [Bug 1937126] Re: bug found

2021-07-26 Thread Fernando Fernandes Bonadio

Bom dia!, na verdade o bug em si n�o est� no xorg mas sim na wayland, pe�o 
desculpa pelo erro na escolha no formul�rio.
Basicamente ap�s um per�odo de sess�o logado o painel na barra superior onde 
adicionei uma extens�o para me mostrar os locais em meu computador deixa de 
ficar traduzido para o portugu�s-br e volta para o ingl�s.
Observei tamb�m de que quando isso ocorre acontece um bug na doca o qual tamb�m 
modifiquei por extens�o e a deixei na parte inferior da tela, contudo ao 
acessar o menu de aplicativos ela acaba aparecendo na parte esquerda do meu 
monitor ficando vis�veis duas docas uma abaixo e uma ao lado.

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

Title:
  bug found

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  I downloaded version 21.04 of ubuntu, then I realized that when I downloaded 
the gnome shell tweaking tool, I realized that when I changed the theme of the 
dock and added in the top bar the option to show the option of locations on the 
system, it leaves my language after performing some accesses in the application 
menu this behavior appears.
  I also noticed that by accessing the applications menu the dock that I 
modified to appear in the lower corner of the screen is now also displayed on 
the left side of my monitor.
  I apologize for the English, but I live in Brazil and I am not fluent in this 
language.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: xorg 1:7.7+22ubuntu1
  ProcVersionSignature: Ubuntu 5.11.0-22.23-generic 5.11.21
  Uname: Linux 5.11.0-22-generic x86_64
  ApportVersion: 2.20.11-0ubuntu65.1
  Architecture: amd64
  BootLog: Error: [Errno 13] Permissão negada: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Jul 21 16:23:56 2021
  DistUpgraded: Fresh install
  DistroCodename: hirsute
  DistroVariant: ubuntu
  DkmsStatus: virtualbox, 6.1.18, 5.11.0-22-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation WhiskeyLake-U GT2 [UHD Graphics 620] [8086:3ea0] (rev 02) 
(prog-if 00 [VGA controller])
 Subsystem: Lenovo UHD Graphics 620 (Whiskey Lake) [17aa:3f1a]
  InstallationDate: Installed on 2021-07-17 (3 days ago)
  InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 174f:1176 Syntek Integrated Camera
   Bus 001 Device 002: ID :3825   USB OPTICAL MOUSE
   Bus 001 Device 004: ID 8087:0a2a Intel Corp. Bluetooth wireless interface
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 81S9
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-22-generic 
root=UUID=fce98fbf-751a-4700-bbe5-628c5a913425 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/24/2020
  dmi.bios.release: 1.50
  dmi.bios.vendor: LENOVO
  dmi.bios.version: ASCN50WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40679 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo IdeaPad S145-15IWL
  dmi.ec.firmware.release: 1.50
  dmi.modalias: 
dmi:bvnLENOVO:bvrASCN50WW:bd11/24/2020:br1.50:efr1.50:svnLENOVO:pn81S9:pvrLenovoIdeaPadS145-15IWL:rvnLENOVO:rnLNVNB161216:rvrSDK0J40679WIN:cvnLENOVO:ct10:cvrLenovoIdeaPadS145-15IWL:
  dmi.product.family: IdeaPad S145-15IWL
  dmi.product.name: 81S9
  dmi.product.sku: LENOVO_MT_81S9_BU_idea_FM_IdeaPad S145-15IWL
  dmi.product.version: Lenovo IdeaPad S145-15IWL
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.105-3~21.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.1-2
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.11-1ubuntu1.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200714-1ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1

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


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

[Desktop-packages] [Bug 1937126] [NEW] bug found

2021-07-21 Thread Fernando Fernandes Bonadio

Public bug reported:

I downloaded version 21.04 of ubuntu, then I realized that when I downloaded 
the gnome shell tweaking tool, I realized that when I changed the theme of the 
dock and added in the top bar the option to show the option of locations on the 
system, it leaves my language after performing some accesses in the application 
menu this behavior appears.
I also noticed that by accessing the applications menu the dock that I modified 
to appear in the lower corner of the screen is now also displayed on the left 
side of my monitor.
I apologize for the English, but I live in Brazil and I am not fluent in this 
language.

ProblemType: Bug
DistroRelease: Ubuntu 21.04
Package: xorg 1:7.7+22ubuntu1
ProcVersionSignature: Ubuntu 5.11.0-22.23-generic 5.11.21
Uname: Linux 5.11.0-22-generic x86_64
ApportVersion: 2.20.11-0ubuntu65.1
Architecture: amd64
BootLog: Error: [Errno 13] Permissão negada: '/var/log/boot.log'
CasperMD5CheckResult: pass
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Wed Jul 21 16:23:56 2021
DistUpgraded: Fresh install
DistroCodename: hirsute
DistroVariant: ubuntu
DkmsStatus: virtualbox, 6.1.18, 5.11.0-22-generic, x86_64: installed
ExtraDebuggingInterest: Yes
GraphicsCard:
 Intel Corporation WhiskeyLake-U GT2 [UHD Graphics 620] [8086:3ea0] (rev 02) 
(prog-if 00 [VGA controller])
   Subsystem: Lenovo UHD Graphics 620 (Whiskey Lake) [17aa:3f1a]
InstallationDate: Installed on 2021-07-17 (3 days ago)
InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 003: ID 174f:1176 Syntek Integrated Camera
 Bus 001 Device 002: ID :3825   USB OPTICAL MOUSE
 Bus 001 Device 004: ID 8087:0a2a Intel Corp. Bluetooth wireless interface
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: LENOVO 81S9
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-22-generic 
root=UUID=fce98fbf-751a-4700-bbe5-628c5a913425 ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 11/24/2020
dmi.bios.release: 1.50
dmi.bios.vendor: LENOVO
dmi.bios.version: ASCN50WW
dmi.board.asset.tag: NO Asset Tag
dmi.board.name: LNVNB161216
dmi.board.vendor: LENOVO
dmi.board.version: SDK0J40679 WIN
dmi.chassis.asset.tag: NO Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Lenovo IdeaPad S145-15IWL
dmi.ec.firmware.release: 1.50
dmi.modalias: 
dmi:bvnLENOVO:bvrASCN50WW:bd11/24/2020:br1.50:efr1.50:svnLENOVO:pn81S9:pvrLenovoIdeaPadS145-15IWL:rvnLENOVO:rnLNVNB161216:rvrSDK0J40679WIN:cvnLENOVO:ct10:cvrLenovoIdeaPadS145-15IWL:
dmi.product.family: IdeaPad S145-15IWL
dmi.product.name: 81S9
dmi.product.sku: LENOVO_MT_81S9_BU_idea_FM_IdeaPad S145-15IWL
dmi.product.version: Lenovo IdeaPad S145-15IWL
dmi.sys.vendor: LENOVO
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.105-3~21.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.1-2
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.20.11-1ubuntu1.1
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200714-1ubuntu1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1

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


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

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

Title:
  bug found

Status in xorg package in Ubuntu:
  New

Bug description:
  I downloaded version 21.04 of ubuntu, then I realized that when I downloaded 
the gnome shell tweaking tool, I realized that when I changed the theme of the 
dock and added in the top bar the option to show the option of locations on the 
system, it leaves my language after performing some accesses in the application 
menu this behavior appears.
  I also noticed that by accessing the applications menu the dock that I 
modified to appear in the lower corner of the screen is now also displayed on 
the left side of my monitor.
  I apologize for the English, but I live in Brazil and I am not fluent in this 
language.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: xorg 1:7.7+22ubuntu1
  ProcVersionSignature: Ubuntu 5.11.0-22.23-generic 5.11.21
  Uname: Linux 5.11.0-22-generic x86_64
  ApportVersion: 2.20.11-0ubuntu65.1
  Architecture: amd64
  BootLog: Error: [Errno 13] Permissão negada: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Jul 21 16:23:56 2021
  DistUpgraded: Fresh install
  DistroCodename: hirsute
  DistroVariant: ubuntu
  DkmsStatus: virtualbox, 6.1.18, 5.11.0-22-generic, x86_64: installed

[Desktop-packages] [Bug 1927063] Re: Terminal prompt got strangely replicated when resizing terminal horizontally

2021-05-04 Thread Fernando Vitor Ventilari Neder

I can confirm this. I'm using Ubuntu 20.04.2 LTS and GNOME Terminal has
the same issue.

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

Title:
  Terminal prompt got strangely replicated when resizing terminal
  horizontally

Status in bash package in Ubuntu:
  Confirmed
Status in gnome-terminal package in Ubuntu:
  Confirmed
Status in mate-terminal package in Ubuntu:
  Confirmed
Status in tilix package in Ubuntu:
  Confirmed
Status in vte2.91 package in Ubuntu:
  Confirmed

Bug description:
  Steps to reproduce:
  1. Have Ubuntu installed
  2. Launch MATE Terminal
  3. Navigate to some folder with long name - `cd 
/usr/share/doc/ayatana-indicator-application`
  4. Resize terminal horizontally

  Expected results:
  * terminal shows the same 
"user@host:/usr/share/doc/ayatana-indicator-application$" with single occurrence

  Actual results:
  * terminal shows multiple occurrencies of 
"user@host:/usr/share/doc/ayatana-indicator-application$"

  (see attached screencast)

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: mate-terminal 1.24.1-1
  ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12
  Uname: Linux 5.11.0-16-generic x86_64
  ApportVersion: 2.20.11-0ubuntu65
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: MATE
  Date: Tue May  4 10:54:59 2021
  InstallationDate: Installed on 2021-04-23 (10 days ago)
  InstallationMedia: Ubuntu-MATE 21.04 "Hirsute Hippo" - Release amd64 
(20210420)
  SourcePackage: mate-terminal
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1918227] [NEW] No display after sleep

2021-03-08 Thread Fernando Castro

Public bug reported:

Approximately two weeks ago after leaving the computer alone the display
turned off like normal but did not come back.The system is working in
the background but the display wont show. I've gotten it to work
sometimes by pulling out the display port cable out and putting it back
in but that hasn't been working lately. Any help would be greatly
appreciated.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: xorg 1:7.7+19ubuntu14
ProcVersionSignature: Ubuntu 5.4.0-66.74-generic 5.4.86
Uname: Linux 5.4.0-66-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.16
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: skip
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Mon Mar  8 22:44:08 2021
DistUpgraded: 2020-05-07 22:40:27,977 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process 
“./xorg_fix_proprietary.py” (No such file or directory) (8))
DistroCodename: focal
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GraphicsCard:
 Advanced Micro Devices, Inc. [AMD/ATI] Navi 10 [Radeon RX 5600 OEM/5600 XT / 
5700/5700 XT] [1002:731f] (rev c1) (prog-if 00 [VGA controller])
   Subsystem: ASUSTeK Computer Inc. Navi 10 [Radeon RX 5600 OEM/5600 XT / 
5700/5700 XT] [1043:0577]
InstallationDate: Installed on 2019-10-30 (495 days ago)
InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
MachineType: System manufacturer System Product Name
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-66-generic 
root=UUID=cdbb24bd-9536-4aa2-b059-e849c202173a ro
SourcePackage: xorg
Symptom: display
UpgradeStatus: Upgraded to focal on 2020-05-08 (305 days ago)
dmi.bios.date: 07/01/2020
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 2407
dmi.board.asset.tag: Default string
dmi.board.name: TUF GAMING X570-PLUS (WI-FI)
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: Rev X.0x
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 3
dmi.chassis.vendor: Default string
dmi.chassis.version: Default string
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2407:bd07/01/2020:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnTUFGAMINGX570-PLUS(WI-FI):rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: System Product Name
dmi.product.sku: SKU
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.1
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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


** Tags: amd64 apport-bug focal ubuntu

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

Title:
  No display after sleep

Status in xorg-server package in Ubuntu:
  New

Bug description:
  Approximately two weeks ago after leaving the computer alone the
  display turned off like normal but did not come back.The system is
  working in the background but the display wont show. I've gotten it to
  work sometimes by pulling out the display port cable out and putting
  it back in but that hasn't been working lately. Any help would be
  greatly appreciated.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-66.74-generic 5.4.86
  Uname: Linux 5.4.0-66-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Mar  8 22:44:08 2021
  DistUpgraded: 2020-05-07 22:40:27,977 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process 
“./xorg_fix_proprietary.py” (No such file or directory) (8))
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Navi 10 [Radeon RX 5600 OEM/5600 XT / 
5700/5700 XT] [1002:731f] (rev c1) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. Navi 10 [Radeon RX 5600 OEM/5600 XT / 
5700/5700 XT] [1043:0577]
  InstallationDate: Installed on 2019-10-30 (495 days ago)
  InstallationMedia: Ubuntu 19.10

[Desktop-packages] [Bug 1917974] [NEW] Xorg freeze

2021-03-05 Thread José Fernando Durán Pérez

Public bug reported:

I had been using the recommended nvidia driver (nvidia-driver-460). I
recently changed to xserver-xorg-video-nouveau for the following
reasons:

1) The resolution configuration was not saved. It is, every power off
and power on the resolution restarted to low resolution.

2) The syslog file in /var/log/ constantly was filled with logs (may be
with a rate of 1 GB per hour), then, I was enforced to install busybox-
syslogd to stop the logging and continue with activities.

3) When using xserver-xorg-video-nouveau, in contrast with nvidia-
driver-460, i didn't had to reset the resolution configuration, which
was great, but now the screen is constantly freezing and i had to use
alt+SysRq+REISUB two times in a day

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: xorg 1:7.7+19ubuntu14
ProcVersionSignature: Ubuntu 5.8.0-44.50~20.04.1-generic 5.8.18
Uname: Linux 5.8.0-44-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.16
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: skip
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Fri Mar  5 22:59:16 2021
DistUpgraded: Fresh install
DistroCodename: focal
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GpuHangFrequency: Several times a week
GpuHangReproducibility: Seems to happen randomly
GpuHangStarted: Today
GraphicsCard:
 NVIDIA Corporation GP108 [GeForce GT 1030] [10de:1d01] (rev a1) (prog-if 00 
[VGA controller])
   Subsystem: Gigabyte Technology Co., Ltd GP108 [GeForce GT 1030] [1458:375c]
InstallationDate: Installed on 2021-02-27 (7 days ago)
InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
MachineType: Default string Default string
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-44-generic 
root=UUID=28228923-7b88-4688-b9fd-157d9ebc22df ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
Title: Xorg freeze
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 06/03/2020
dmi.bios.release: 5.11
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 5.11
dmi.board.asset.tag: Default string
dmi.board.name: X99-k9
dmi.board.vendor: MACHINIST
dmi.board.version: V1.0
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 3
dmi.chassis.vendor: Default string
dmi.chassis.version: Default string
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr5.11:bd06/03/2020:br5.11:svnDefaultstring:pnDefaultstring:pvrDefaultstring:rvnMACHINIST:rnX99-k9:rvrV1.0:cvnDefaultstring:ct3:cvrDefaultstring:
dmi.product.family: Default string
dmi.product.name: Default string
dmi.product.sku: Default string
dmi.product.version: Default string
dmi.sys.vendor: Default string
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.1
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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


** Tags: amd64 apport-bug focal freeze ubuntu

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

Title:
  Xorg freeze

Status in xorg package in Ubuntu:
  New

Bug description:
  I had been using the recommended nvidia driver (nvidia-driver-460). I
  recently changed to xserver-xorg-video-nouveau for the following
  reasons:

  1) The resolution configuration was not saved. It is, every power off
  and power on the resolution restarted to low resolution.

  2) The syslog file in /var/log/ constantly was filled with logs (may
  be with a rate of 1 GB per hour), then, I was enforced to install
  busybox-syslogd to stop the logging and continue with activities.

  3) When using xserver-xorg-video-nouveau, in contrast with nvidia-
  driver-460, i didn't had to reset the resolution configuration, which
  was great, but now the screen is constantly freezing and i had to use
  alt+SysRq+REISUB two times in a day

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.8.0-44.50~20.04.1-generic 5.8.18
  Uname: Linux 5.8.0-44-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Mar  5 22:59:16 2021
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GpuHangFrequency: Several times a week
  GpuHangReproducibility: Seems to happen randomly

[Desktop-packages] [Bug 40148] Re: Key (Code 94) does not work anymore

2021-02-23 Thread Fernando

In my system, ubuntu 20. The bug behaves similar. Key works fine in tty
(outside X). In graphical mode what should be less greater, becomes \|

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

Title:
  Key (Code 94) does not work anymore

Status in xorg package in Ubuntu:
  Invalid

Bug description:
  Dapper updated today to the latest packages.

  On my Thinkpad in Gnome I've chosen "generic 101-key pc" as the
  keyboard model and "German Dead acute" as the layout.

  Pressing the key next to the left shift key does not give anything.
  This key has keycode 94 and is described like this "keycode  94 = less
  greater bar" in xmodmap.de.

  This is what xev reports:

  KeyPress event, serial 26, synthetic NO, window 0x301,
  root 0x76, subw 0x302, time 2985393502, (33,29), root:(38,102),
  state 0x0, keycode 94 (keysym 0x0, NoSymbol), same_screen YES,
  XLookupString gives 0 bytes:
  XmbLookupString gives 0 bytes:
  XFilterEvent returns: False

  KeyRelease event, serial 29, synthetic NO, window 0x301,
  root 0x76, subw 0x302, time 2985393573, (33,29), root:(38,102),
  state 0x0, keycode 94 (keysym 0x0, NoSymbol), same_screen YES,
  XLookupString gives 0 bytes:

  It works in a normal TTY though (outside X).

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

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

[Desktop-packages] [Bug 844582] Re: "Invalid argument" when trying to scan

2021-01-31 Thread Fernando

Hello,
I have the same problem:
   gscan2pdf: sane_start: Invalid argument

I run from the command line with the "--log=log" option and create the log.xz 
file that I attach.
My system is:
   * Kubuntu 20.10 (Ubuntu + KDE)
   * Scanner: Brother DCP-J562DW
I've been able to use this scanner in al ubuntu versions (I'm long linux user 
and gscan2pdf too), but I'm not sure if I've used with the previous 20.04 
version (I think that yes).

I have another PC with Windows 10 and the scanner works. So is something
with my system not with the device.


** Attachment added: "Log for gscan2pdf"
   
https://bugs.launchpad.net/ubuntu/+source/gscan2pdf/+bug/844582/+attachment/5458553/+files/log.xz

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

Title:
  "Invalid argument" when trying to scan

Status in gscan2pdf package in Ubuntu:
  Invalid
Status in sane-backends package in Ubuntu:
  Opinion

Bug description:
  I'm using a Fujitsu M3091DCd scanner with SANE. From the command line
  it works more or less well with Ubuntu.

  I can't use it with gscan2pdf v0.9.31, but gscan2pdf works with
  another scanner.

  All I get is a meaningless "Invalid argument" when I hit the scan
  button.

  When I start gscan2pdf from the command line I see these lines
  appearing when I hit the scan button:

  Error running process: Died at (eval 39) line 7.

$device->start;
$shash{$sane_thread}{status} = $Sane::STATUS+0;
if ($Sane::STATUS != SANE_STATUS_GOOD) {
 print "$prog_name: sane_start: $Sane::STATUS\n" if $debug;
 $shash{$sane_thread}{go} = 0;
 die; # quickest way out of the eval block
}

my $path = $shash{$sane_thread}{data};
if (not open($fh, ">", $path)) {
 $device->cancel;
 $shash{$sane_thread}{status} = SANE_STATUS_ACCESS_DENIED;
 $shash{$sane_thread}{go} = 0;
 die; # quickest way out of the eval block
}
scan_page($device, $fh);
$shash{$sane_thread}{status} = $Sane::STATUS+0;
close $fh;
printf "Scanned page %s.", $path if $debug;
printf " (scanner status = %d)\n", $Sane::STATUS if $debug;
$shash{$sane_thread}{status} = $Sane::STATUS+0;
$shash{$sane_thread}{go} = 0;

  ProblemType: Bug
  DistroRelease: Ubuntu 11.04
  Package: gscan2pdf 0.9.31-2
  ProcVersionSignature: Ubuntu 2.6.38-11.48-generic 2.6.38.8
  Uname: Linux 2.6.38-11-generic x86_64
  NonfreeKernelModules: fglrx
  Architecture: amd64
  Date: Thu Sep  8 09:44:25 2011
  PackageArchitecture: all
  ProcEnviron:
   LANGUAGE=
   PATH=(custom, no username)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gscan2pdf
  UpgradeStatus: Upgraded to natty on 2011-06-01 (98 days ago)

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

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

[Desktop-packages] [Bug 1900906] Re: Can't use dead keys or input e.g. Chinese characters in GNOME shell

2021-01-15 Thread Fernando

The bug persists with accented characters if the dead key is the first
character you type. I mean, open the overview, type "á" and you see just
"a". Then type another "á" and it shows correctly. Same if you type
"lá", the accent shows correctly because the dead key wasn't the first
thing you typed.

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

Title:
  Can't use dead keys or input e.g. Chinese characters in GNOME shell

Status in Mutter:
  Unknown
Status in mutter package in Ubuntu:
  Fix Released
Status in mutter source package in Focal:
  Fix Committed
Status in mutter source package in Groovy:
  Fix Released

Bug description:
  I'm running an up-to-date Ubuntu Focal. I have a standard Spanish keyboard. 
Under X, if I try to input an accentuated character, such as á or ü, in places 
like the search field in the overview or when writing a folder name in the app 
grid, nothing appears. Under Wayland, it fails each time on the first input of 
an accentuated character, then it works.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.9
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-05-01 (174 days ago)
  InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 
(20200203.1)
  Package: ibus
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65
  RelatedPackageVersions: mutter-common 3.36.6-1ubuntu0.20.04.2
  Tags:  focal
  Uname: Linux 5.4.0-52-generic x86_64
  UpgradeStatus: Upgraded to focal on 2020-09-29 (22 days ago)
  UserGroups: sudo
  _MarkForUpload: True

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

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

[Desktop-packages] [Bug 1903230] Re: Mutter release 3.36.7

2020-12-14 Thread Fernando

Is there any expected date to ship this update?

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

Title:
  Mutter release 3.36.7

Status in mutter package in Ubuntu:
  Triaged

Bug description:
  We should release mutter 3.36.7 to focal, for bug 1900906, bug 1894596
  and ...?

  [Impact]

  This is the current GNOME 3.36.x stable update, including some fixes
  (especially crashes and memory leaks) and translation updates.

  https://gitlab.gnome.org/GNOME/mutter/-/blob/gnome-3-36/NEWS

  3.36.7
  ==
  * Fix Night Light updates after DPMS [Jonas, Benjamin; #1392]
  * Fix IM handling on X11 [Carlos; #1413]
  * Fix resizing of attached modal dialogs on wayland [Jonas; !1446]
  * Fix jumps when resizing windows using discrete steps [Jonas; #1447]
  * Fixed crashes [Marco; !1371, #1345]
  * Plugged Memory leaks [Ray; !1449, !1451]
  * Misc. bug fixes and cleanups [Jonas, Carlos, Robert; !1218, !1460, !1463]

  Contributors:
  Marco Trevisan (Treviño), Benjamin Berg, Carlos Garnacho, Robert Mader,
  Ray Strode, Jonas Ådahl

  Translators:
  Juliano de Souza Camargo [pt]

  [Test case]

  The update is part of GNOME stable updates.
  https://wiki.ubuntu.com/StableReleaseUpdates/GNOME

  GNOME Shell and its components should continue working well.

  [Regression potential]

  There have been fixes in nightlight mode, IM handling in X11 and
  resizing windows in Wayland. All of those should not regress after the
  update.

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

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

[Desktop-packages] [Bug 1900906] Re: Can't use dead keys or input e.g. Chinese characters in GNOME shell

2020-11-06 Thread Fernando

Wow, thanks!

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

Title:
  Can't use dead keys or input e.g. Chinese characters in GNOME shell

Status in Mutter:
  Unknown
Status in mutter package in Ubuntu:
  Fix Released
Status in mutter source package in Focal:
  Fix Committed
Status in mutter source package in Groovy:
  Fix Released

Bug description:
  I'm running an up-to-date Ubuntu Focal. I have a standard Spanish keyboard. 
Under X, if I try to input an accentuated character, such as á or ü, in places 
like the search field in the overview or when writing a folder name in the app 
grid, nothing appears. Under Wayland, it fails each time on the first input of 
an accentuated character, then it works.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.9
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-05-01 (174 days ago)
  InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 
(20200203.1)
  Package: ibus
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65
  RelatedPackageVersions: mutter-common 3.36.6-1ubuntu0.20.04.2
  Tags:  focal
  Uname: Linux 5.4.0-52-generic x86_64
  UpgradeStatus: Upgraded to focal on 2020-09-29 (22 days ago)
  UserGroups: sudo
  _MarkForUpload: True

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

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

[Desktop-packages] [Bug 1900906] Re: Can't use dead keys or input e.g. Chinese characters in GNOME shell

2020-11-05 Thread Fernando

Thanks, Daniel. Is there any way of encouraging that mutter update in
Focal? Or at least of estimating when it will be shipped?

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

Title:
  Can't use dead keys or input e.g. Chinese characters in GNOME shell

Status in Mutter:
  Unknown
Status in mutter package in Ubuntu:
  Fix Released
Status in mutter source package in Focal:
  Fix Committed
Status in mutter source package in Groovy:
  Fix Released

Bug description:
  I'm running an up-to-date Ubuntu Focal. I have a standard Spanish keyboard. 
Under X, if I try to input an accentuated character, such as á or ü, in places 
like the search field in the overview or when writing a folder name in the app 
grid, nothing appears. Under Wayland, it fails each time on the first input of 
an accentuated character, then it works.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.9
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-05-01 (174 days ago)
  InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 
(20200203.1)
  Package: ibus
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65
  RelatedPackageVersions: mutter-common 3.36.6-1ubuntu0.20.04.2
  Tags:  focal
  Uname: Linux 5.4.0-52-generic x86_64
  UpgradeStatus: Upgraded to focal on 2020-09-29 (22 days ago)
  UserGroups: sudo
  _MarkForUpload: True

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

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

[Desktop-packages] [Bug 1902715] Re: Change alert sound ubuntu not working (Ubuntu 20.04 LTS)

2020-11-03 Thread Luiz Fernando Pinto de Oliveira

Thank you very much @Sebastien for the indication of the similar bug
(bug #1871320). The same problem is happening to me. How do I solve it?

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

Title:
  Change alert sound ubuntu not working (Ubuntu 20.04 LTS)

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

Bug description:
  I installed the Ubuntu version 20.04 LTS. I would like to change the
  alert sound. I followed these steps:

  1.Open the Activities overview and start typing Sound;
  2.Click on Sound to open the panel;
  3.In the Alert Sound section, select an alert sound.

  However, after choosing the preferred sound it does not change!

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

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

[Desktop-packages] [Bug 1902715] Re: Change alert sound ubuntu not working (Ubuntu 20.04 LTS)

2020-11-03 Thread Luiz Fernando Pinto de Oliveira

What desktop environment do you use?
R -> I am using the GNOME version 3.36.3 in Ubuntu 20.04. 

how do you test if it changed?
I use the terminal. I simply open the terminal and press the Tab key. And for 
example, I chose the "Sonar" alert sound, but I always hear the "Drip" sound.

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

Title:
  Change alert sound ubuntu not working (Ubuntu 20.04 LTS)

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

Bug description:
  I installed the Ubuntu version 20.04 LTS. I would like to change the
  alert sound. I followed these steps:

  1.Open the Activities overview and start typing Sound;
  2.Click on Sound to open the panel;
  3.In the Alert Sound section, select an alert sound.

  However, after choosing the preferred sound it does not change!

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

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

[Desktop-packages] [Bug 1895643] Re: Backport Thunderbird 78 to 20.04 LTS and 18.04 LTS

2020-10-26 Thread Fernando

GContactSync, which is the only working extension recommended by
Thunderbird to sync Google contacts (https://support.mozilla.org/en-
US/kb/thunderbird-and-gmail), doesn't work yet in version 78
(https://github.com/jdgeenen/gcontactsync/issues/163). An upgrade to 78
may lead to unexpected breakage for many.

** Bug watch added: github.com/jdgeenen/gcontactsync/issues #163
   https://github.com/jdgeenen/gcontactsync/issues/163

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

Title:
  Backport Thunderbird 78 to 20.04 LTS and 18.04 LTS

Status in thunderbird package in Ubuntu:
  Confirmed

Bug description:
  Upstream Thunderbird version 78.2.2 should be a candidate for
  backporting to stable Ubuntu releases.

  I've successfully built 78.2.1 against both with forcing nodejs
  version (20.04, 18.04) and disabling AV1 support due to too old nasm
  (18.04). Attaching debdiffs here.

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

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

[Desktop-packages] [Bug 1900906] Re: Can't use dead keys or input e.g. Chinese characters in GNOME shell

2020-10-25 Thread Fernando

I'm amazed and very grateful for how fast this has been fixed, thanks!
Will there be an SRU soon shipping this fix?

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

Title:
  Can't use dead keys or input e.g. Chinese characters in GNOME shell

Status in Mutter:
  Unknown
Status in mutter package in Ubuntu:
  Fix Released
Status in mutter source package in Focal:
  Fix Committed
Status in mutter source package in Groovy:
  Fix Released

Bug description:
  I'm running an up-to-date Ubuntu Focal. I have a standard Spanish keyboard. 
Under X, if I try to input an accentuated character, such as á or ü, in places 
like the search field in the overview or when writing a folder name in the app 
grid, nothing appears. Under Wayland, it fails each time on the first input of 
an accentuated character, then it works.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.9
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-05-01 (174 days ago)
  InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 
(20200203.1)
  Package: ibus
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65
  RelatedPackageVersions: mutter-common 3.36.6-1ubuntu0.20.04.2
  Tags:  focal
  Uname: Linux 5.4.0-52-generic x86_64
  UpgradeStatus: Upgraded to focal on 2020-09-29 (22 days ago)
  UserGroups: sudo
  _MarkForUpload: True

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

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

[Desktop-packages] [Bug 1900906] ProcEnviron.txt

apport information

** Attachment added: "ProcEnviron.txt"
   
https://bugs.launchpad.net/bugs/1900906/+attachment/5425395/+files/ProcEnviron.txt

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

Title:
  Can't input accents in GNOME shell

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

Bug description:
  I'm running an up-to-date Ubuntu Focal. I have a standard Spanish keyboard. 
Under X, if I try to input an accentuated character, such as á or ü, in places 
like the search field in the overview or when writing a folder name in the app 
grid, nothing appears. Under Wayland, it fails each time on the first input of 
an accentuated character, then it works.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.9
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-05-01 (174 days ago)
  InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 
(20200203.1)
  Package: ibus
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65
  RelatedPackageVersions: mutter-common 3.36.6-1ubuntu0.20.04.2
  Tags:  focal
  Uname: Linux 5.4.0-52-generic x86_64
  UpgradeStatus: Upgraded to focal on 2020-09-29 (22 days ago)
  UserGroups: sudo
  _MarkForUpload: True

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

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

[Desktop-packages] [Bug 1900906] ShellJournal.txt

apport information

** Attachment added: "ShellJournal.txt"
   
https://bugs.launchpad.net/bugs/1900906/+attachment/5425396/+files/ShellJournal.txt

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

Title:
  Can't input accents in GNOME shell

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

Bug description:
  I'm running an up-to-date Ubuntu Focal. I have a standard Spanish keyboard. 
Under X, if I try to input an accentuated character, such as á or ü, in places 
like the search field in the overview or when writing a folder name in the app 
grid, nothing appears. Under Wayland, it fails each time on the first input of 
an accentuated character, then it works.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.9
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-05-01 (174 days ago)
  InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 
(20200203.1)
  Package: ibus
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65
  RelatedPackageVersions: mutter-common 3.36.6-1ubuntu0.20.04.2
  Tags:  focal
  Uname: Linux 5.4.0-52-generic x86_64
  UpgradeStatus: Upgraded to focal on 2020-09-29 (22 days ago)
  UserGroups: sudo
  _MarkForUpload: True

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

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

[Desktop-packages] [Bug 1900906] monitors.xml.txt

apport information

** Attachment added: "monitors.xml.txt"
   
https://bugs.launchpad.net/bugs/1900906/+attachment/5425397/+files/monitors.xml.txt

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

Title:
  Can't input accents in GNOME shell

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

Bug description:
  I'm running an up-to-date Ubuntu Focal. I have a standard Spanish keyboard. 
Under X, if I try to input an accentuated character, such as á or ü, in places 
like the search field in the overview or when writing a folder name in the app 
grid, nothing appears. Under Wayland, it fails each time on the first input of 
an accentuated character, then it works.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.9
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-05-01 (174 days ago)
  InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 
(20200203.1)
  Package: ibus
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65
  RelatedPackageVersions: mutter-common 3.36.6-1ubuntu0.20.04.2
  Tags:  focal
  Uname: Linux 5.4.0-52-generic x86_64
  UpgradeStatus: Upgraded to focal on 2020-09-29 (22 days ago)
  UserGroups: sudo
  _MarkForUpload: True

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

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

[Desktop-packages] [Bug 1900906] GsettingsChanges.txt

apport information

** Attachment added: "GsettingsChanges.txt"
   
https://bugs.launchpad.net/bugs/1900906/+attachment/5425393/+files/GsettingsChanges.txt

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

Title:
  Can't input accents in GNOME shell

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

Bug description:
  I'm running an up-to-date Ubuntu Focal. I have a standard Spanish keyboard. 
Under X, if I try to input an accentuated character, such as á or ü, in places 
like the search field in the overview or when writing a folder name in the app 
grid, nothing appears. Under Wayland, it fails each time on the first input of 
an accentuated character, then it works.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.9
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-05-01 (174 days ago)
  InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 
(20200203.1)
  Package: ibus
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65
  RelatedPackageVersions: mutter-common 3.36.6-1ubuntu0.20.04.2
  Tags:  focal
  Uname: Linux 5.4.0-52-generic x86_64
  UpgradeStatus: Upgraded to focal on 2020-09-29 (22 days ago)
  UserGroups: sudo
  _MarkForUpload: True

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

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

[Desktop-packages] [Bug 1900906] Re: Can't input accents in GNOME shell

apport information

** Tags added: apport-collected

** Description changed:

- I'm running an up-to-date Ubuntu Focal. I have a standard Spanish
- keyboard. Under X, if I try to input an accentuated character, such as á
- or ü, in places like the search field in the overview or when writing a
- folder name in the app grid, nothing appears. Under Wayland, it fails
- each time on the first input of an accentuated character, then it works.
+ I'm running an up-to-date Ubuntu Focal. I have a standard Spanish keyboard. 
Under X, if I try to input an accentuated character, such as á or ü, in places 
like the search field in the overview or when writing a folder name in the app 
grid, nothing appears. Under Wayland, it fails each time on the first input of 
an accentuated character, then it works.
+ --- 
+ ProblemType: Bug
+ ApportVersion: 2.20.11-0ubuntu27.9
+ Architecture: amd64
+ CasperMD5CheckResult: skip
+ CurrentDesktop: ubuntu:GNOME
+ DisplayManager: gdm3
+ DistroRelease: Ubuntu 20.04
+ InstallationDate: Installed on 2020-05-01 (174 days ago)
+ InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 
(20200203.1)
+ Package: ibus
+ PackageArchitecture: amd64
+ ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65
+ RelatedPackageVersions: mutter-common 3.36.6-1ubuntu0.20.04.2
+ Tags:  focal
+ Uname: Linux 5.4.0-52-generic x86_64
+ UpgradeStatus: Upgraded to focal on 2020-09-29 (22 days ago)
+ UserGroups: sudo
+ _MarkForUpload: True

** Attachment added: "Dependencies.txt"
   
https://bugs.launchpad.net/bugs/1900906/+attachment/5425392/+files/Dependencies.txt

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

Title:
  Can't input accents in GNOME shell

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

Bug description:
  I'm running an up-to-date Ubuntu Focal. I have a standard Spanish keyboard. 
Under X, if I try to input an accentuated character, such as á or ü, in places 
like the search field in the overview or when writing a folder name in the app 
grid, nothing appears. Under Wayland, it fails each time on the first input of 
an accentuated character, then it works.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.9
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-05-01 (174 days ago)
  InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 
(20200203.1)
  Package: ibus
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65
  RelatedPackageVersions: mutter-common 3.36.6-1ubuntu0.20.04.2
  Tags:  focal
  Uname: Linux 5.4.0-52-generic x86_64
  UpgradeStatus: Upgraded to focal on 2020-09-29 (22 days ago)
  UserGroups: sudo
  _MarkForUpload: True

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

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

[Desktop-packages] [Bug 1900906] ProcCpuinfoMinimal.txt

apport information

** Attachment added: "ProcCpuinfoMinimal.txt"
   
https://bugs.launchpad.net/bugs/1900906/+attachment/5425394/+files/ProcCpuinfoMinimal.txt

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

Title:
  Can't input accents in GNOME shell

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

Bug description:
  I'm running an up-to-date Ubuntu Focal. I have a standard Spanish keyboard. 
Under X, if I try to input an accentuated character, such as á or ü, in places 
like the search field in the overview or when writing a folder name in the app 
grid, nothing appears. Under Wayland, it fails each time on the first input of 
an accentuated character, then it works.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.9
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-05-01 (174 days ago)
  InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 
(20200203.1)
  Package: ibus
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65
  RelatedPackageVersions: mutter-common 3.36.6-1ubuntu0.20.04.2
  Tags:  focal
  Uname: Linux 5.4.0-52-generic x86_64
  UpgradeStatus: Upgraded to focal on 2020-09-29 (22 days ago)
  UserGroups: sudo
  _MarkForUpload: True

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

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

[Desktop-packages] [Bug 1900908] Re: Mutter doesn't apply gsettings appropriately to Wacom tablet

** Description changed:

  I have a Wacom Intuos VT M tablet in a setting with two monitors (laptop
  + external). Under an up-to-date Ubuntu Focal running X, if I map the
  tablet to a single monitor it fails to map it more often than not. A
  reliable way of getting failure is first connecting the tablet via
  bluetooth and then via USB. The only way to revert to a correct behavior
  is reseting X (ALT+F2 r). This is necessary even after rebooting.
  
  I've noticed that, when not working well, the problem is that Mutter
  sends the mapping data to the "Wacom Intuos BT M Pad pad" device, while
  it should be sending them to "Wacom Intuos BT M Pad stylus" (this is
  what it does when it works well).
  
  Under Wayland it works well (well, the tablet buttons don't work under
  Wayland but this is unrelated).
+ 
+ PS I reported this bug agains the Wacom X driver but was told it's
+ really related to mutter (https://github.com/linuxwacom/xf86-input-
+ wacom/issues/148).

** Description changed:

  I have a Wacom Intuos VT M tablet in a setting with two monitors (laptop
  + external). Under an up-to-date Ubuntu Focal running X, if I map the
  tablet to a single monitor it fails to map it more often than not. A
  reliable way of getting failure is first connecting the tablet via
  bluetooth and then via USB. The only way to revert to a correct behavior
  is reseting X (ALT+F2 r). This is necessary even after rebooting.
  
  I've noticed that, when not working well, the problem is that Mutter
  sends the mapping data to the "Wacom Intuos BT M Pad pad" device, while
  it should be sending them to "Wacom Intuos BT M Pad stylus" (this is
  what it does when it works well).
  
  Under Wayland it works well (well, the tablet buttons don't work under
  Wayland but this is unrelated).
  
- PS I reported this bug agains the Wacom X driver but was told it's
+ PS I reported this bug against the Wacom X driver but was told it's
  really related to mutter (https://github.com/linuxwacom/xf86-input-
  wacom/issues/148).

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

Title:
  Mutter doesn't apply gsettings appropriately to Wacom tablet

Status in mutter package in Ubuntu:
  New

Bug description:
  I have a Wacom Intuos VT M tablet in a setting with two monitors
  (laptop + external). Under an up-to-date Ubuntu Focal running X, if I
  map the tablet to a single monitor it fails to map it more often than
  not. A reliable way of getting failure is first connecting the tablet
  via bluetooth and then via USB. The only way to revert to a correct
  behavior is reseting X (ALT+F2 r). This is necessary even after
  rebooting.

  I've noticed that, when not working well, the problem is that Mutter
  sends the mapping data to the "Wacom Intuos BT M Pad pad" device,
  while it should be sending them to "Wacom Intuos BT M Pad stylus"
  (this is what it does when it works well).

  Under Wayland it works well (well, the tablet buttons don't work under
  Wayland but this is unrelated).

  PS I reported this bug against the Wacom X driver but was told it's
  really related to mutter (https://github.com/linuxwacom/xf86-input-
  wacom/issues/148).

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

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

[Desktop-packages] [Bug 1900906] Re: Can't input accents in GNOME shell

** Description changed:

- I have a standard Spanish keyboard. If I try to input an accentuated
- character, such as á or ü, in places like the search field in the
- overview or when writing a folder name in the app grid, nothing appears.
+ I'm running an up-to-date Ubuntu Focal. I have a standard Spanish
+ keyboard. Under X, if I try to input an accentuated character, such as á
+ or ü, in places like the search field in the overview or when writing a
+ folder name in the app grid, nothing appears. Under Wayland, it fails
+ each time on the first input of an accentuated character, then it works.

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

Title:
  Can't input accents in GNOME shell

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  I'm running an up-to-date Ubuntu Focal. I have a standard Spanish
  keyboard. Under X, if I try to input an accentuated character, such as
  á or ü, in places like the search field in the overview or when
  writing a folder name in the app grid, nothing appears. Under Wayland,
  it fails each time on the first input of an accentuated character,
  then it works.

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

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

[Desktop-packages] [Bug 1900908] [NEW] Mutter doesn't apply gsettings appropriately to Wacom tablet

Public bug reported:

I have a Wacom Intuos VT M tablet in a setting with two monitors (laptop
+ external). Under an up-to-date Ubuntu Focal running X, if I map the
tablet to a single monitor it fails to map it more often than not. A
reliable way of getting failure is first connecting the tablet via
bluetooth and then via USB. The only way to revert to a correct behavior
is reseting X (ALT+F2 r). This is necessary even after rebooting.

I've noticed that, when not working well, the problem is that Mutter
sends the mapping data to the "Wacom Intuos BT M Pad pad" device, while
it should be sending them to "Wacom Intuos BT M Pad stylus" (this is
what it does when it works well).

Under Wayland it works well (well, the tablet buttons don't work under
Wayland but this is unrelated).

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

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

Title:
  Mutter doesn't apply gsettings appropriately to Wacom tablet

Status in mutter package in Ubuntu:
  New

Bug description:
  I have a Wacom Intuos VT M tablet in a setting with two monitors
  (laptop + external). Under an up-to-date Ubuntu Focal running X, if I
  map the tablet to a single monitor it fails to map it more often than
  not. A reliable way of getting failure is first connecting the tablet
  via bluetooth and then via USB. The only way to revert to a correct
  behavior is reseting X (ALT+F2 r). This is necessary even after
  rebooting.

  I've noticed that, when not working well, the problem is that Mutter
  sends the mapping data to the "Wacom Intuos BT M Pad pad" device,
  while it should be sending them to "Wacom Intuos BT M Pad stylus"
  (this is what it does when it works well).

  Under Wayland it works well (well, the tablet buttons don't work under
  Wayland but this is unrelated).

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

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

[Desktop-packages] [Bug 1900906] [NEW] Can't input accents in GNOME shell

Public bug reported:

I have a standard Spanish keyboard. If I try to input an accentuated
character, such as á or ü, in places like the search field in the
overview or when writing a folder name in the app grid, nothing appears.

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

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

Title:
  Can't input accents in GNOME shell

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  I have a standard Spanish keyboard. If I try to input an accentuated
  character, such as á or ü, in places like the search field in the
  overview or when writing a folder name in the app grid, nothing
  appears.

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

-- 
Mailing list: https://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 1896349] Re: PCI/internal sound card not detected

2020-09-21 Thread Fernando Marcel Tarantino Martins

Mr Wang, the computer now showed the same problem! I don't know what
happens.
w how to
I tried to solve it using your link, but I don't know how to proceed to
make the backup you ask and also don't know how to attach the other files.
I'm kind of new using Linux and sometimes it's difficult to understand what
application and what steps I have to do in order to make things work as it
should.

On Mon, Sep 21, 2020 at 8:02 AM Fernando Marcel 
wrote:

> Hi, Mr. Wang.
>
> I don't know how but in the next day it just worked normally.
>
> Thank you anyways! :)
>
> On Mon, Sep 21, 2020 at 12:30 AM Hui Wang <1896...@bugs.launchpad.net>
> wrote:
>
>> Please test this: https://bugs.launchpad.net/ubuntu/+source/linux-
>> firmware/+bug/1892714/comments/46
>> <https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1892714/comments/46>
>>
>> --
>> You received this bug notification because you are subscribed to the bug
>> report.
>> https://bugs.launchpad.net/bugs/1896349
>>
>> Title:
>>   PCI/internal sound card not detected
>>
>> Status in alsa-driver package in Ubuntu:
>>   New
>>
>> Bug description:
>>   Description:  Ubuntu 20.04.1 LTS
>>   Release:  20.04
>>
>>   I can select my default audio hardware
>>
>>   When I test it, doesn't work.
>>
>>   When watching a Youtube video, for example, audio doesn't work as
>>   well.
>>
>>   Thru the command lspci, this shows up:
>>
>>   00:00.0 Host bridge: Intel Corporation Device 8a12 (rev 03)
>>   00:02.0 VGA compatible controller: Intel Corporation Iris Plus Graphics
>> G7 (rev 07)
>>   00:04.0 Signal processing controller: Intel Corporation Device 8a03
>> (rev 03)
>>   00:0d.0 USB controller: Intel Corporation Ice Lake Thunderbolt 3 USB
>> Controller (rev 03)
>>   00:14.0 USB controller: Intel Corporation Ice Lake-LP USB 3.1 xHCI Host
>> Controller (rev 30)
>>   00:14.2 RAM memory: Intel Corporation Device 34ef (rev 30)
>>   00:14.3 Network controller: Intel Corporation Killer Wi-Fi 6 AX1650i
>> 160MHz Wireless Network Adapter (201NGW) (rev 30)
>>   00:15.0 Serial bus controller [0c80]: Intel Corporation Ice Lake-LP
>> Serial IO I2C Controller #0 (rev 30)
>>   00:15.1 Serial bus controller [0c80]: Intel Corporation Ice Lake-LP
>> Serial IO I2C Controller #1 (rev 30)
>>   00:16.0 Communication controller: Intel Corporation Management Engine
>> Interface (rev 30)
>>   00:17.0 RAID bus controller: Intel Corporation 82801 Mobile SATA
>> Controller [RAID mode] (rev 30)
>>   00:1c.0 PCI bridge: Intel Corporation Ice Lake-LP PCI Express Root Port
>> #5 (rev 30)
>>   00:1d.0 PCI bridge: Intel Corporation Ice Lake-LP PCI Express Root Port
>> #9 (rev 30)
>>   00:1d.4 PCI bridge: Intel Corporation Device 34b4 (rev 30)
>>   00:1d.6 PCI bridge: Intel Corporation Device 34b6 (rev 30)
>>   00:1f.0 ISA bridge: Intel Corporation Ice Lake-LP LPC Controller (rev
>> 30)
>>   00:1f.3 Multimedia audio controller: Intel Corporation Smart Sound
>> Technology Audio Controller (rev 30)
>>   00:1f.4 SMBus: Intel Corporation Ice Lake-LP SMBus Controller (rev 30)
>>   00:1f.5 Serial bus controller [0c80]: Intel Corporation Ice Lake-LP SPI
>> Controller (rev 30)
>>   01:00.0 3D controller: NVIDIA Corporation GP108M [GeForce MX330] (rev
>> a1)
>>   02:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd.
>> RTS522A PCI Express Card Reader (rev 01)
>>   03:00.0 Non-Volatile memory controller: Intel Corporation Device 0975
>> (rev 03)
>>   04:00.0 Non-Volatile memory controller: Intel Corporation Device 0975
>>
>>   ProblemType: Bug
>>   DistroRelease: Ubuntu 20.04
>>   Package: alsa-base 1.0.25+dfsg-0ubuntu5
>>   ProcVersionSignature: Ubuntu 5.4.0-47.51-generic 5.4.55
>>   Uname: Linux 5.4.0-47-generic x86_64
>>   ApportVersion: 2.20.11-0ubuntu27.8
>>   Architecture: amd64
>>   AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq',
>> '/dev/snd/timer'] failed with exit code 1:
>>   CasperMD5CheckResult: skip
>>   CurrentDesktop: ubuntu:GNOME
>>   Date: Sat Sep 19 19:24:38 2020
>>   InstallationDate: Installed on 2020-09-19 (0 days ago)
>>   InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64
>> (20200731)
>>   PackageArchitecture: all
>>   SourcePackage: alsa-driver
>>   Symptom: audio
>>   Title: PCI/internal sound card not detected
>>   UpgradeStatus: No upgrade log present (probably fresh install)
>>   dmi.bios.date: 02/13/2020
>>   dmi.bios.vendor: Insyd

Re: [Desktop-packages] [Bug 1896349] Re: PCI/internal sound card not detected

2020-09-21 Thread Fernando Marcel Tarantino Martins

Hi, Mr. Wang.

I don't know how but in the next day it just worked normally.

Thank you anyways! :)

On Mon, Sep 21, 2020 at 12:30 AM Hui Wang <1896...@bugs.launchpad.net>
wrote:

> Please test this: https://bugs.launchpad.net/ubuntu/+source/linux-
> firmware/+bug/1892714/comments/46
> 
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1896349
>
> Title:
>   PCI/internal sound card not detected
>
> Status in alsa-driver package in Ubuntu:
>   New
>
> Bug description:
>   Description:  Ubuntu 20.04.1 LTS
>   Release:  20.04
>
>   I can select my default audio hardware
>
>   When I test it, doesn't work.
>
>   When watching a Youtube video, for example, audio doesn't work as
>   well.
>
>   Thru the command lspci, this shows up:
>
>   00:00.0 Host bridge: Intel Corporation Device 8a12 (rev 03)
>   00:02.0 VGA compatible controller: Intel Corporation Iris Plus Graphics
> G7 (rev 07)
>   00:04.0 Signal processing controller: Intel Corporation Device 8a03 (rev
> 03)
>   00:0d.0 USB controller: Intel Corporation Ice Lake Thunderbolt 3 USB
> Controller (rev 03)
>   00:14.0 USB controller: Intel Corporation Ice Lake-LP USB 3.1 xHCI Host
> Controller (rev 30)
>   00:14.2 RAM memory: Intel Corporation Device 34ef (rev 30)
>   00:14.3 Network controller: Intel Corporation Killer Wi-Fi 6 AX1650i
> 160MHz Wireless Network Adapter (201NGW) (rev 30)
>   00:15.0 Serial bus controller [0c80]: Intel Corporation Ice Lake-LP
> Serial IO I2C Controller #0 (rev 30)
>   00:15.1 Serial bus controller [0c80]: Intel Corporation Ice Lake-LP
> Serial IO I2C Controller #1 (rev 30)
>   00:16.0 Communication controller: Intel Corporation Management Engine
> Interface (rev 30)
>   00:17.0 RAID bus controller: Intel Corporation 82801 Mobile SATA
> Controller [RAID mode] (rev 30)
>   00:1c.0 PCI bridge: Intel Corporation Ice Lake-LP PCI Express Root Port
> #5 (rev 30)
>   00:1d.0 PCI bridge: Intel Corporation Ice Lake-LP PCI Express Root Port
> #9 (rev 30)
>   00:1d.4 PCI bridge: Intel Corporation Device 34b4 (rev 30)
>   00:1d.6 PCI bridge: Intel Corporation Device 34b6 (rev 30)
>   00:1f.0 ISA bridge: Intel Corporation Ice Lake-LP LPC Controller (rev 30)
>   00:1f.3 Multimedia audio controller: Intel Corporation Smart Sound
> Technology Audio Controller (rev 30)
>   00:1f.4 SMBus: Intel Corporation Ice Lake-LP SMBus Controller (rev 30)
>   00:1f.5 Serial bus controller [0c80]: Intel Corporation Ice Lake-LP SPI
> Controller (rev 30)
>   01:00.0 3D controller: NVIDIA Corporation GP108M [GeForce MX330] (rev a1)
>   02:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. RTS522A
> PCI Express Card Reader (rev 01)
>   03:00.0 Non-Volatile memory controller: Intel Corporation Device 0975
> (rev 03)
>   04:00.0 Non-Volatile memory controller: Intel Corporation Device 0975
>
>   ProblemType: Bug
>   DistroRelease: Ubuntu 20.04
>   Package: alsa-base 1.0.25+dfsg-0ubuntu5
>   ProcVersionSignature: Ubuntu 5.4.0-47.51-generic 5.4.55
>   Uname: Linux 5.4.0-47-generic x86_64
>   ApportVersion: 2.20.11-0ubuntu27.8
>   Architecture: amd64
>   AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq',
> '/dev/snd/timer'] failed with exit code 1:
>   CasperMD5CheckResult: skip
>   CurrentDesktop: ubuntu:GNOME
>   Date: Sat Sep 19 19:24:38 2020
>   InstallationDate: Installed on 2020-09-19 (0 days ago)
>   InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64
> (20200731)
>   PackageArchitecture: all
>   SourcePackage: alsa-driver
>   Symptom: audio
>   Title: PCI/internal sound card not detected
>   UpgradeStatus: No upgrade log present (probably fresh install)
>   dmi.bios.date: 02/13/2020
>   dmi.bios.vendor: Insyde
>   dmi.bios.version: F.04
>   dmi.board.asset.tag: Type2 - Board Asset Tag
>   dmi.board.name: 875C
>   dmi.board.vendor: HP
>   dmi.board.version: 10.23
>   dmi.chassis.asset.tag: Chassis Asset Tag
>   dmi.chassis.type: 10
>   dmi.chassis.vendor: HP
>   dmi.chassis.version: Chassis Version
>   dmi.modalias:
> dmi:bvnInsyde:bvrF.04:bd02/13/2020:svnHP:pnHPENVYLaptop17m-cg0xxx:pvrType1ProductConfigId:rvnHP:rn875C:rvr10.23:cvnHP:ct10:cvrChassisVersion:
>   dmi.product.family: 103C_5335KV HP Envy
>   dmi.product.name: HP ENVY Laptop 17m-cg0xxx
>   dmi.product.sku: 9XM78UA#ABA
>   dmi.product.version: Type1ProductConfigId
>   dmi.sys.vendor: HP
>
> To manage notifications about this bug go to:
>
> https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1896349/+subscriptions
>

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

Title:
  PCI/internal sound card not detected

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  Description:  Ubuntu 20.04.1 LTS
  Release:  20.04

  I can select my default audio

[Desktop-packages] [Bug 1859555] Re: Calculator does not work in GNOME activities search

2020-05-13 Thread Fernando

Is this maybe due to the patches introduced to fix the following bug?

https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1756826

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

Title:
  Calculator does not work in GNOME activities search

Status in gnome-calculator package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu release: 18.04.3
  Package version: (deb) 1:3.28.2-1~ubuntu18.04.3

  
  What was expected to happen: calculation results are displayed in activities 
search.
  What happens instead: no results are displayed.

  The bug started happening after the last update of the package. The
  previous version worked properly.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-calculator 1:3.28.2-1~ubuntu18.04.3
  ProcVersionSignature: Ubuntu 5.0.0-37.40~18.04.1-generic 5.0.21
  Uname: Linux 5.0.0-37-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7.9
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Tue Jan 14 00:58:57 2020
  InstallationDate: Installed on 2019-10-15 (91 days ago)
  InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 
(20190805)
  ProcEnviron:
   LANGUAGE=pt_BR:pt:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=pt_BR.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-calculator
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1876647] Re: Nautilus search in gnome-shell performance regression

2020-05-07 Thread Fernando

This is probably related to the following bug:

https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1874972

File search in overview mode is now always done full-text. I think that
the intended behavior is doing it exclusively by file name in overview
and optionally in nautilus. Please, confirm you're also affected by this
other bug and mark it there to attract attention.

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

Title:
  Nautilus search in gnome-shell performance regression

Status in nautilus package in Ubuntu:
  Confirmed

Bug description:
  Under 19.10, the Nautilus search provider returned near-instant
  results when searching in GNOME shell's activities, for both standard
  top-level folders like "Downloads", but also when returning results
  for files and directories deeper down.

  Under 20.04, it takes ~10 seconds to start showing results, even when
  just searching for Downloads. It's a bit faster for a warm search, but
  not by much. There is no difference if Nautilus is already running in
  the background or not. Performing a type-to-find in a Nautilus window
  proper is as as instantaneous as the shell search was in 19.10.

  This is a substantial usability regression - I use the feature
  constantly.

  The only thing printed in the logs when performing a search is:

  > May 04 12:40:39 blanchefort nautilus[232948]: Source ID 10873 was
  not found when attempting to remove it

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: nautilus 1:3.36.1.1-1ubuntu2
  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: Mon May  4 12:28:30 2020
  InstallationDate: Installed on 2018-08-13 (629 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  SourcePackage: nautilus
  UpgradeStatus: Upgraded to focal on 2020-03-07 (57 days ago)
  usr_lib_nautilus:

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

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

[Desktop-packages] [Bug 1867402] Re: [snap] Icons in file picker are corrupted

2020-05-07 Thread Fernando

Hi, Jora. The output is:

content[icon-themes]  chromium:icon-themes   gtk-common-
themes:icon-themes   -

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

Title:
  [snap] Icons in file picker are corrupted

Status in chromium-browser package in Ubuntu:
  Incomplete

Bug description:
  See the attached picture. This happens in bionic.

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

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

[Desktop-packages] [Bug 1867402] Re: [snap] Icons in file picker are corrupted

2020-05-06 Thread Fernando

Sebastien, no, it really seems to be the right icons but with a lot of
noise, have a look at the screenshot in the first attachment. It happens
whenever you trigger the GTK file picker from the chromium snap in
whatever way.

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

Title:
  [snap] Icons in file picker are corrupted

Status in chromium-browser package in Ubuntu:
  Incomplete

Bug description:
  See the attached picture. This happens in bionic.

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

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

[Desktop-packages] [Bug 1867402] Re: [snap] Icons in file picker are corrupted

Paul, you're right, I checked a while ago that this wasn't reproducible
in Eoan with the Yaru theme. Maybe this has to do with the fact that the
only-snap Chromium came when Yaru was already the default?

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

Title:
  [snap] Icons in file picker are corrupted

Status in chromium-browser package in Ubuntu:
  Incomplete

Bug description:
  See the attached picture. This happens in bionic.

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

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

[Desktop-packages] [Bug 1867402] Re: [snap] Icons in file picker are corrupted

Yes, it's consistently there. I ran the snap for quite a while until I
had to move to Google Chrome because of MS Teams support (you know,
confinement tech). I reckon not many people open the file picker in a
browser, but it's something I constantly do due to my workflow.

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

Title:
  [snap] Icons in file picker are corrupted

Status in chromium-browser package in Ubuntu:
  Incomplete

Bug description:
  See the attached picture. This happens in bionic.

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

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

[Desktop-packages] [Bug 1867402] Re: Icons in file picker don't render well

Let me clarify. I installed the snap, run it and opened a file picker
via "Save page as" in order to check that the distorted icons were
there. Then run apport and obtained the previous message.

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

Title:
  Icons in file picker don't render well

Status in chromium-browser package in Ubuntu:
  Incomplete

Bug description:
  See the attached picture. This happens in bionic.

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

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

[Desktop-packages] [Bug 1867402] Re: Icons in file picker don't render well

Ooops, no luck. What should I do next?

** Attachment added: "Screenshot from 2020-05-05 17-07-36.png"
   
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1867402/+attachment/5366864/+files/Screenshot%20from%202020-05-05%2017-07-36.png

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

Title:
  Icons in file picker don't render well

Status in chromium-browser package in Ubuntu:
  Incomplete

Bug description:
  See the attached picture. This happens in bionic.

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

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

[Desktop-packages] [Bug 1867402] Re: Icons in file picker don't render well

I see. Well, it was the snap in any case. Let me install the snap and
run that command.

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

Title:
  Icons in file picker don't render well

Status in chromium-browser package in Ubuntu:
  Incomplete

Bug description:
  See the attached picture. This happens in bionic.

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

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

[Desktop-packages] [Bug 1867402] Re: Icons in file picker don't render well

Snap, there's no other option, is there? Will apport-collect work for
the snap installed from the store? I moved to proper Chrome because of
other stuff, but I'd have no problem in reinstalling Chromium for
debugging if necessary.

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

Title:
  Icons in file picker don't render well

Status in chromium-browser package in Ubuntu:
  Incomplete

Bug description:
  See the attached picture. This happens in bionic.

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

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

[Desktop-packages] [Bug 1867402] Re: Icons in file picker don't render well

It looks corrupted to me. This is in bionic with everything by default,
no tweaks at all. I haven't changed a theme since I was in my twenties.

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

Title:
  Icons in file picker don't render well

Status in chromium-browser package in Ubuntu:
  New

Bug description:
  See the attached picture. This happens in bionic.

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

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

[Desktop-packages] [Bug 1874972] Re: Nautilus search in file names shows results from full text search

2020-04-30 Thread Fernando

Could this be relate to this other bug?

https://bugs.launchpad.net/ubuntu/+source/tracker/+bug/1861358

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

Title:
  Nautilus search in file names shows results from full text search

Status in nautilus package in Ubuntu:
  Confirmed

Bug description:
  Nautilus full text search works fine. However, a search in file names brings 
the same results as in full text search. The only difference is that, in the 
file name mode, no text is shown beside the file name.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-04-23 (3 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  Package: nautilus 1:3.36.1.1-1ubuntu2
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
  Tags:  focal
  Uname: Linux 5.4.0-26-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  usr_lib_nautilus:

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

-- 
Mailing list: https://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 1870843] Re: ibus-ui-gtk3 crashed with SIGSEGV in ibus_bus_call_sync()

2020-04-05 Thread Fernando Anton

Hi Sebastien and team,

The bug is not reproducible. It always appeared just after login, after
loading the desktop and without having started any application.

El dom., 5 abr. 2020 a las 11:30, 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: ibus (Ubuntu)
>Status: New => Incomplete
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1870843
>
> Title:
>   ibus-ui-gtk3 crashed with SIGSEGV in ibus_bus_call_sync()
>
> Status in ibus package in Ubuntu:
>   Incomplete
>
> Bug description:
>   Description:  Ubuntu Focal Fossa (development branch)
>   Release:  20.04
>
>   ProblemType: Crash
>   DistroRelease: Ubuntu 20.04
>   Package: ibus 1.5.22-2ubuntu2
>   ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24
>   Uname: Linux 5.4.0-18-generic x86_64
>   NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
>   ApportVersion: 2.20.11-0ubuntu22
>   Architecture: amd64
>   CrashCounter: 1
>   CurrentDesktop: ubuntu:GNOME
>   Date: Sat Apr  4 13:03:51 2020
>   ExecutablePath: /usr/libexec/ibus-ui-gtk3
>   ProcCmdline: /usr/libexec/ibus-ui-gtk3
>   ProcEnviron:
>LANGUAGE=es_AR:es
>PATH=(custom, no user)
>XDG_RUNTIME_DIR=
>LANG=es_AR.UTF-8
>SHELL=/bin/bash
>   SegvAnalysis:
>Segfault happened at: 0x7fee4f4e8f5b : orq
> $0x0,(%rsp)
>PC (0x7fee4f4e8f5b) ok
>source "$0x0" ok
>destination "(%rsp)" (0x7ffe02368d40) not located in a known VMA region
> (needed writable region)!
>Stack memory exhausted (SP below stack segment)
>   SegvReason: writing unknown VMA
>   Signal: 11
>   SourcePackage: ibus
>   StacktraceTop:
>?? () from /lib/x86_64-linux-gnu/libibus-1.0.so.5
>ibus_bus_get_engines_by_names () from
> /lib/x86_64-linux-gnu/libibus-1.0.so.5
>?? ()
>?? ()
>g_cclosure_marshal_VOID__STRINGv () from
> /lib/x86_64-linux-gnu/libgobject-2.0.so.0
>   Title: ibus-ui-gtk3 crashed with SIGSEGV in
> ibus_bus_get_engines_by_names()
>   UpgradeStatus: No upgrade log present (probably fresh install)
>   UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
>   separator:
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1870843/+subscriptions
>

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

Title:
  ibus-ui-gtk3 crashed with SIGSEGV in ibus_bus_call_sync()

Status in ibus package in Ubuntu:
  Incomplete

Bug description:
  Description:  Ubuntu Focal Fossa (development branch)
  Release:  20.04

  ProblemType: Crash
  DistroRelease: Ubuntu 20.04
  Package: ibus 1.5.22-2ubuntu2
  ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24
  Uname: Linux 5.4.0-18-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu22
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Apr  4 13:03:51 2020
  ExecutablePath: /usr/libexec/ibus-ui-gtk3
  ProcCmdline: /usr/libexec/ibus-ui-gtk3
  ProcEnviron:
   LANGUAGE=es_AR:es
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=es_AR.UTF-8
   SHELL=/bin/bash
  SegvAnalysis:
   Segfault happened at: 0x7fee4f4e8f5b : orq
$0x0,(%rsp)
   PC (0x7fee4f4e8f5b) ok
   source "$0x0" ok
   destination "(%rsp)" (0x7ffe02368d40) not located in a known VMA region 
(needed writable region)!
   Stack memory exhausted (SP below stack segment)
  SegvReason: writing unknown VMA
  Signal: 11
  SourcePackage: ibus
  StacktraceTop:
   ?? () from /lib/x86_64-linux-gnu/libibus-1.0.so.5
   ibus_bus_get_engines_by_names () from /lib/x86_64-linux-gnu/libibus-1.0.so.5
   ?? ()
   ?? ()
   g_cclosure_marshal_VOID__STRINGv () from 
/lib/x86_64-linux-gnu/libgobject-2.0.so.0
  Title: ibus-ui-gtk3 crashed with SIGSEGV in ibus_bus_get_engines_by_names()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  separator:

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

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

[Desktop-packages] [Bug 1867402] [NEW] Icons in file picker don't render well

2020-03-13 Thread Fernando

Public bug reported:

See the attached picture. This happens in bionic.

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

** Attachment added: "Screenshot from 2020-03-13 23-34-04.png"
   
https://bugs.launchpad.net/bugs/1867402/+attachment/5336703/+files/Screenshot%20from%202020-03-13%2023-34-04.png

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

Title:
  Icons in file picker don't render well

Status in chromium-browser package in Ubuntu:
  New

Bug description:
  See the attached picture. This happens in bionic.

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

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

[Desktop-packages] [Bug 1859376] [NEW] Problems with updates

2020-01-12 Thread Fernando Paguay

Public bug reported:

When you want to install the updates, the manager says that the packages are 
broken and that you try again.
I did it and it didn't work, so I tried to update through the terminal and it 
didn't work either. I would like to receive help with this problem. Thank you

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xorg 1:7.7+19ubuntu7.1
ProcVersionSignature: Ubuntu 4.15.0-66.75-generic 4.15.18
Uname: Linux 4.15.0-66-generic x86_64
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.9-0ubuntu7.9
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
Date: Sun Jan 12 18:55:35 2020
DistroCodename: bionic
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GraphicsCard:
 Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0156] (rev 
09) (prog-if 00 [VGA controller])
   Subsystem: Acer Incorporated [ALI] 3rd Gen Core processor Graphics 
Controller [1025:0742]
InstallationDate: Installed on 2018-07-02 (559 days ago)
InstallationMedia: Ubuntu 12.04.3 LTS "Precise Pangolin" - Release amd64 
(20130820.1)
Lsusb:
 Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
 Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
 Bus 001 Device 003: ID 1bcf:2c17 Sunplus Innovation Technology Inc. 
 Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: Acer V5-131
ProcEnviron:
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-66-generic 
root=UUID=a61bcc7e-d9c3-4e26-9abd-45c28eb06478 ro drm.debug=0xe plymouth:debug
Renderer: Software
SourcePackage: xorg
UpgradeStatus: Upgraded to bionic on 2018-12-13 (395 days ago)
dmi.bios.date: 03/22/2013
dmi.bios.vendor: Acer
dmi.bios.version: V2.17
dmi.board.asset.tag: Type2 - Board Asset Tag
dmi.board.name: Mimic
dmi.board.vendor: Acer
dmi.board.version: Type2 - Board Version
dmi.chassis.type: 10
dmi.chassis.vendor: Acer
dmi.chassis.version: V2.17
dmi.modalias: 
dmi:bvnAcer:bvrV2.17:bd03/22/2013:svnAcer:pnV5-131:pvrV2.17:rvnAcer:rnMimic:rvrType2-BoardVersion:cvnAcer:ct10:cvrV2.17:
dmi.product.family: Type1Family
dmi.product.name: V5-131
dmi.product.version: V2.17
dmi.sys.vendor: Acer
version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
version.libdrm2: libdrm2 2.4.97-1ubuntu1~18.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.8-0ubuntu0~18.04.3
version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.8-0ubuntu0~18.04.3
version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.3
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2
xserver.bootTime: Fri Jan  3 21:00:06 2020
xserver.configfile: default
xserver.logfile: /var/log/Xorg.0.log
xserver.version: 2:1.19.6-1ubuntu4.3

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


** Tags: amd64 apport-bug bionic ubuntu

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

Title:
  Problems with updates

Status in xorg package in Ubuntu:
  New

Bug description:
  When you want to install the updates, the manager says that the packages are 
broken and that you try again.
  I did it and it didn't work, so I tried to update through the terminal and it 
didn't work either. I would like to receive help with this problem. Thank you

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-66.75-generic 4.15.18
  Uname: Linux 4.15.0-66-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.9-0ubuntu7.9
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Sun Jan 12 18:55:35 2020
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0156] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: Acer Incorporated [ALI] 3rd Gen Core processor Graphics 
Controller [1025:0742]
  InstallationDate: Installed on 2018-07-02 (559 days ago)
  InstallationMedia: Ubuntu 12.04.3 LTS "Precise Pangolin" - Release amd64 
(20130820.1)
  Lsusb:
   Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
   Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 001 Device 003: ID 1bcf:2c17 Sunplus Innovation Technology Inc. 
   Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Acer

[Desktop-packages] [Bug 1849081] Re: ZSH shells break Login screen

2019-10-26 Thread Fernando Racca

More updates.
There was an issue with Powerlevel, at least as documented here.
 https://github.com/romkatv/powerlevel10k/issues/280


However, the issue seems to be lower level. An important issue seems to happen 
here:

include this line at the top of .bashrc when using zsh

```
exec zsh
```

It seems this somehow breaks the login shell. I was able to reproduce
this on my other laptop with 18.04.

As long as that line is not there, the latest version of ZSH + oh_my_zsh
+ Powerlevel10k are working fine.


This bug may be closed at your discretion, but it seems that there is benefit 
in somehow find out how to avoid this breaking in such case .

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

Title:
  ZSH shells break Login screen

Status in gnome-keyring package in Ubuntu:
  New

Bug description:
  There's a bug that affects gnome-keyring, and i'll describe the steps i've 
done to reproduce it twice, although i don't have
  full details as to what exactly is causing it.

  Issue can be summarized as follows:

  On Ubuntu 19.10, but not at least 18.04 (another computer i have using
  the older release), there's an issue that prevents the user to login
  to a gnome session

  The issue shows up when checking the session manager:

  ```
  service gdm3 status
  Process: ExecStartPre: /usr/share/gdm/generate-config 
(code=exited,status=0/SUCCESS)
  Process: ExecStartPre: /usr/lib/gdm3/gdm-wait-for-drm 
(code=exited,status=0/SUCCESS)
  ...

  gdm-password: gkr-pam: unable to local control file
  ```

  Relevant components:

* gdm3 3.34.1-1
* gnome-shell 3.34.1-1
* gnome-keyring 3.34.0-1
* zsh 5.77.1-ubuntu2

  This does not occur on a fresh installation of Ubuntu. It only happens
  once some of these tools are installed:

* zsh (ubuntu package https://packages.ubuntu.com/eoan/zsh , manually 
change shell for user) - 
https://askubuntu.com/questions/131823/how-to-make-zsh-the-default-shell
* oh-my-zsh  (brings in lots of plugins, although only git was sourced) 
- https://github.com/robbyrussell/oh-my-zsh/wiki/Installing-ZSH
* powerlevel10k  (shell theme ) - 
https://github.com/romkatv/powerlevel10k

  The tools would appear to work fine, until you reboot the machine, and
  are asked to login, at which point gkr-pam complains that it can't
  locate control file.

  Unfortunately i don't have better details because eventually i broke
  so much my login that i decided to reinstall the system from scratch.

  Upon installation, i started from fresh, with no zsh, and everything
  worked. Once zsh was installed, it will no longer work.

  A fix for this was to revert to bash shell.

  The key change was to no include this line at the top of .bashrc

  ```
  #exec zsh
  ```

  So i can confirm the issue is there, but that's as far as i got after
  several hours of investigations.

  I appreciate that this bug may not be a gnome-keyring specific bug,
  but seems that its the one been affected anyways.

  
  https://gitlab.gnome.org/GNOME/gnome-keyring/issues/28
  https://gitlab.gnome.org/GNOME/gnome-keyring/issues/26

  https://github.com/GNOME/gnome-keyring/blob/master/pam/gkr-pam-module.c#L676
  https://github.com/GNOME/gnome-keyring/blob/master/pam/gkr-pam-module.c#L847

  
https://github.com/GNOME/gnome-keyring/commit/443a821cba105e8f277828a67b3d019b67f1324a
  
https://github.com/GNOME/gnome-keyring/commit/b22d058a055ec3e0f31ae16417f16b42baadb42f

  
  https://bugs.launchpad.net/ubuntu/+source/gnome-keyring/+bug/1817128
  https://bugs.launchpad.net/ubuntu/+source/gnome-keyring/+bug/1818616

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

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

[Desktop-packages] [Bug 1818616] Re: gnome-keyring is not unlocked upon gdm login in disco

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

I've summarized my investigation so far in this new bug report:

It seems a combination of ZSH, Oh-My-Zsh and possibly Powerlevel10k
break the login screen somehow.

https://bugs.launchpad.net/ubuntu/+source/gnome-keyring/+bug/1849081
https://github.com/robbyrussell/oh-my-zsh/issues/8296
https://github.com/romkatv/powerlevel10k/issues/280

** Bug watch added: github.com/robbyrussell/oh-my-zsh/issues #8296
   https://github.com/robbyrussell/oh-my-zsh/issues/8296

** Bug watch added: github.com/romkatv/powerlevel10k/issues #280
   https://github.com/romkatv/powerlevel10k/issues/280

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

Title:
  gnome-keyring is not unlocked upon gdm login in disco

Status in gdm3 package in Ubuntu:
  Confirmed
Status in gnome-keyring package in Ubuntu:
  Confirmed
Status in pam package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  I'm not sure if this is a regression in my gnome-keyring, gdm3, or pam, or 
local configuration.
  As far as I recall, I should be running just "stock" configs.
  I did not install system with disco, but upgraded to disco throughout 
development series.

  Upon booting, and logging in through gdm3, I get a pop-up from gnome-
  keyring instructing me that gnome-keyring was not unlocked upon
  logging, and I have to re-enter the password again.

  The password for the account and the gnome-keyring are the same, and
  the keyring should be auto-unlocked.

  Looking at the journal, there is a red warning from gdm:
  Mar 05 08:15:58 ottawa gdm-password][18338]: gkr-pam: unable to locate daemon 
control file
  Looking at the code, this happens when neither GNOME_KEYRING_CONTROL nor 
XDG_RUNTIME_DIR are set.

  The messages after it are:
  Mar 05 08:15:58 ottawa gdm-password][18338]: gkr-pam: unable to locate daemon 
control file
  Mar 05 08:15:58 ottawa gdm-password][18338]: pam_unix(gdm-password:session): 
session opened for user xnox by (uid=0)
  Mar 05 08:15:58 ottawa systemd[1]: Created slice User Slice of UID 1000.
  Mar 05 08:15:58 ottawa systemd[1]: Starting User Runtime Directory 
/run/user/1000...
  Mar 05 08:15:58 ottawa systemd-logind[1376]: New session 3 of user xnox.
  Mar 05 08:15:58 ottawa systemd[1]: Started User Runtime Directory 
/run/user/1000.
  Mar 05 08:15:58 ottawa systemd[1]: Starting User Manager for UID 1000...
  Mar 05 08:15:58 ottawa systemd[18344]: pam_unix(systemd-user:session): 
session opened for user xnox by (uid=0)
  Mar 05 08:15:58 ottawa systemd[18344]: Listening on Sound System.
  Mar 05 08:15:58 ottawa systemd[18344]: Listening on GnuPG cryptographic agent 
(ssh-agent emulation).
  Mar 05 08:15:58 ottawa systemd[18344]: Started Pending report trigger for 
Ubuntu Report.
  Mar 05 08:15:58 ottawa systemd[18344]: Listening on GnuPG cryptographic agent 
and passphrase cache (restricted).
  Mar 05 08:15:58 ottawa systemd[18344]: Listening on GnuPG cryptographic agent 
and passphrase cache.
  Mar 05 08:15:58 ottawa systemd[18344]: Reached target Paths.
  Mar 05 08:15:58 ottawa systemd[18344]: Listening on GnuPG cryptographic agent 
and passphrase cache (access for web browsers).
  Mar 05 08:15:58 ottawa systemd[18344]: Reached target Timers.
  Mar 05 08:15:58 ottawa systemd[18344]: Listening on GnuPG network certificate 
management daemon.
  Mar 05 08:15:58 ottawa systemd[18344]: Starting D-Bus User Message Bus Socket.
  Mar 05 08:15:58 ottawa systemd[18344]: Listening on D-Bus User Message Bus 
Socket.
  Mar 05 08:15:58 ottawa systemd[18344]: Reached target Sockets.
  Mar 05 08:15:58 ottawa systemd[18344]: Reached target Basic System.
  Mar 05 08:15:58 ottawa systemd[1]: Started User Manager for UID 1000.
  Mar 05 08:15:58 ottawa systemd[18344]: Started Emacs text editor.
  Mar 05 08:15:58 ottawa systemd[18344]: Reached target Default.
  Mar 05 08:15:58 ottawa systemd[18344]: Startup finished in 72ms.
  Mar 05 08:15:58 ottawa systemd[1]: Started Session 3 of user xnox.

  I don't believe GNOME_KEYRING_CONTROL used to be set, however I do see
  that XDG_RUNTIME_DIR to be created and set by logind. From the above
  logs I can see that it happens _after_ gdm-password is done.

  So It seems like something has changed in the stack, and gdm login /
  libpam-gnome-keyring no longer use systemd-logind PAM module to be
  part of the PAM session. But I'm not sure what has changed to cause
  this (gdm, gnome-keyring, pam, systemd).

  Am I the only one with this issue?

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: gnome-keyring 3.31.90-1ubuntu1
  ProcVersionSignature: Ubuntu 4.19.0-13.14-generic 4.19.20
  Uname: Linux 4.19.0-13-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.10-0ubuntu21
  Architecture: amd64

[Desktop-packages] [Bug 1817128] Re: gnome-keyring not automatically unlocked on login

Thanks,
I've raised several issues to try to fix this problem:

https://bugs.launchpad.net/ubuntu/+source/gnome-keyring/+bug/1849081
https://github.com/robbyrussell/oh-my-zsh/issues/8296
https://github.com/romkatv/powerlevel10k/issues/280

** Bug watch added: github.com/robbyrussell/oh-my-zsh/issues #8296
   https://github.com/robbyrussell/oh-my-zsh/issues/8296

** Bug watch added: github.com/romkatv/powerlevel10k/issues #280
   https://github.com/romkatv/powerlevel10k/issues/280

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

Title:
  gnome-keyring not automatically unlocked on login

Status in gnome-keyring package in Ubuntu:
  Fix Released

Bug description:
  Hi

  After initializing and filling the login screen, at the start screen
  prompts for password to unlock the session keyring. Is this normal on
  Ubuntu disk 19.04.02?

  Note: When filling the login screen to start the micro, should it not
  be unlocked automatically?

  Attached the image of the request I fired it.

  Thank you


  **
  Hi

  Após inicialização e preenchimento da tela de login, ao iniciar a tela
  pede senha para desbloqueio do chaveiro de sessão. Isso é normal no
  Ubuntu disco 19.04.02?

  Obs: Quando do preenchimento da tela de login para iniciar o micro o
  desbloqueio não deveria ser automático?

  Em anexo a imagem da solicitação de desboquei-o.

  Obrigado

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

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

[Desktop-packages] [Bug 1849081] Re: ZSH shells break Login screen

I've cross-posted this issue in the related tools since it's unclear
which one causes it, but it's severe enough to make it worth triaging
it.

https://github.com/robbyrussell/oh-my-zsh/issues/8296
https://github.com/romkatv/powerlevel10k/issues/280


** Bug watch added: github.com/robbyrussell/oh-my-zsh/issues #8296
   https://github.com/robbyrussell/oh-my-zsh/issues/8296

** Bug watch added: github.com/romkatv/powerlevel10k/issues #280
   https://github.com/romkatv/powerlevel10k/issues/280

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

Title:
  ZSH shells break Login screen

Status in gnome-keyring package in Ubuntu:
  New

Bug description:
  There's a bug that affects gnome-keyring, and i'll describe the steps i've 
done to reproduce it twice, although i don't have
  full details as to what exactly is causing it.

  Issue can be summarized as follows:

  On Ubuntu 19.10, but not at least 18.04 (another computer i have using
  the older release), there's an issue that prevents the user to login
  to a gnome session

  The issue shows up when checking the session manager:

  ```
  service gdm3 status
  Process: ExecStartPre: /usr/share/gdm/generate-config 
(code=exited,status=0/SUCCESS)
  Process: ExecStartPre: /usr/lib/gdm3/gdm-wait-for-drm 
(code=exited,status=0/SUCCESS)
  ...

  gdm-password: gkr-pam: unable to local control file
  ```

  Relevant components:

* gdm3 3.34.1-1
* gnome-shell 3.34.1-1
* gnome-keyring 3.34.0-1
* zsh 5.77.1-ubuntu2

  This does not occur on a fresh installation of Ubuntu. It only happens
  once some of these tools are installed:

* zsh (ubuntu package https://packages.ubuntu.com/eoan/zsh , manually 
change shell for user) - 
https://askubuntu.com/questions/131823/how-to-make-zsh-the-default-shell
* oh-my-zsh  (brings in lots of plugins, although only git was sourced) 
- https://github.com/robbyrussell/oh-my-zsh/wiki/Installing-ZSH
* powerlevel10k  (shell theme ) - 
https://github.com/romkatv/powerlevel10k

  The tools would appear to work fine, until you reboot the machine, and
  are asked to login, at which point gkr-pam complains that it can't
  locate control file.

  Unfortunately i don't have better details because eventually i broke
  so much my login that i decided to reinstall the system from scratch.

  Upon installation, i started from fresh, with no zsh, and everything
  worked. Once zsh was installed, it will no longer work.

  A fix for this was to revert to bash shell.

  The key change was to no include this line at the top of .bashrc

  ```
  #exec zsh
  ```

  So i can confirm the issue is there, but that's as far as i got after
  several hours of investigations.

  I appreciate that this bug may not be a gnome-keyring specific bug,
  but seems that its the one been affected anyways.

  
  https://gitlab.gnome.org/GNOME/gnome-keyring/issues/28
  https://gitlab.gnome.org/GNOME/gnome-keyring/issues/26

  https://github.com/GNOME/gnome-keyring/blob/master/pam/gkr-pam-module.c#L676
  https://github.com/GNOME/gnome-keyring/blob/master/pam/gkr-pam-module.c#L847

  
https://github.com/GNOME/gnome-keyring/commit/443a821cba105e8f277828a67b3d019b67f1324a
  
https://github.com/GNOME/gnome-keyring/commit/b22d058a055ec3e0f31ae16417f16b42baadb42f

  
  https://bugs.launchpad.net/ubuntu/+source/gnome-keyring/+bug/1817128
  https://bugs.launchpad.net/ubuntu/+source/gnome-keyring/+bug/1818616

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

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

[Desktop-packages] [Bug 1849081] [NEW] ZSH shells break Login screen

Public bug reported:

There's a bug that affects gnome-keyring, and i'll describe the steps i've done 
to reproduce it twice, although i don't have
full details as to what exactly is causing it.

Issue can be summarized as follows:

On Ubuntu 19.10, but not at least 18.04 (another computer i have using
the older release), there's an issue that prevents the user to login to
a gnome session

The issue shows up when checking the session manager:

```
service gdm3 status
Process: ExecStartPre: /usr/share/gdm/generate-config 
(code=exited,status=0/SUCCESS)
Process: ExecStartPre: /usr/lib/gdm3/gdm-wait-for-drm 
(code=exited,status=0/SUCCESS)
...

gdm-password: gkr-pam: unable to local control file
```

Relevant components:

  * gdm3 3.34.1-1
  * gnome-shell 3.34.1-1
  * gnome-keyring 3.34.0-1
  * zsh 5.77.1-ubuntu2

This does not occur on a fresh installation of Ubuntu. It only happens
once some of these tools are installed:

  * zsh (ubuntu package https://packages.ubuntu.com/eoan/zsh , manually change 
shell for user) - 
https://askubuntu.com/questions/131823/how-to-make-zsh-the-default-shell
* oh-my-zsh  (brings in lots of plugins, although only git was sourced) 
- https://github.com/robbyrussell/oh-my-zsh/wiki/Installing-ZSH
* powerlevel10k  (shell theme ) - 
https://github.com/romkatv/powerlevel10k

The tools would appear to work fine, until you reboot the machine, and
are asked to login, at which point gkr-pam complains that it can't
locate control file.

Unfortunately i don't have better details because eventually i broke so
much my login that i decided to reinstall the system from scratch.

Upon installation, i started from fresh, with no zsh, and everything
worked. Once zsh was installed, it will no longer work.

A fix for this was to revert to bash shell.

The key change was to no include this line at the top of .bashrc

```
#exec zsh
```

So i can confirm the issue is there, but that's as far as i got after
several hours of investigations.

I appreciate that this bug may not be a gnome-keyring specific bug, but
seems that its the one been affected anyways.


https://gitlab.gnome.org/GNOME/gnome-keyring/issues/28
https://gitlab.gnome.org/GNOME/gnome-keyring/issues/26

https://github.com/GNOME/gnome-keyring/blob/master/pam/gkr-pam-module.c#L676
https://github.com/GNOME/gnome-keyring/blob/master/pam/gkr-pam-module.c#L847

https://github.com/GNOME/gnome-keyring/commit/443a821cba105e8f277828a67b3d019b67f1324a
https://github.com/GNOME/gnome-keyring/commit/b22d058a055ec3e0f31ae16417f16b42baadb42f


https://bugs.launchpad.net/ubuntu/+source/gnome-keyring/+bug/1817128
https://bugs.launchpad.net/ubuntu/+source/gnome-keyring/+bug/1818616

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


** Tags: eoan

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

Title:
  ZSH shells break Login screen

Status in gnome-keyring package in Ubuntu:
  New

Bug description:
  There's a bug that affects gnome-keyring, and i'll describe the steps i've 
done to reproduce it twice, although i don't have
  full details as to what exactly is causing it.

  Issue can be summarized as follows:

  On Ubuntu 19.10, but not at least 18.04 (another computer i have using
  the older release), there's an issue that prevents the user to login
  to a gnome session

  The issue shows up when checking the session manager:

  ```
  service gdm3 status
  Process: ExecStartPre: /usr/share/gdm/generate-config 
(code=exited,status=0/SUCCESS)
  Process: ExecStartPre: /usr/lib/gdm3/gdm-wait-for-drm 
(code=exited,status=0/SUCCESS)
  ...

  gdm-password: gkr-pam: unable to local control file
  ```

  Relevant components:

* gdm3 3.34.1-1
* gnome-shell 3.34.1-1
* gnome-keyring 3.34.0-1
* zsh 5.77.1-ubuntu2

  This does not occur on a fresh installation of Ubuntu. It only happens
  once some of these tools are installed:

* zsh (ubuntu package https://packages.ubuntu.com/eoan/zsh , manually 
change shell for user) - 
https://askubuntu.com/questions/131823/how-to-make-zsh-the-default-shell
* oh-my-zsh  (brings in lots of plugins, although only git was sourced) 
- https://github.com/robbyrussell/oh-my-zsh/wiki/Installing-ZSH
* powerlevel10k  (shell theme ) - 
https://github.com/romkatv/powerlevel10k

  The tools would appear to work fine, until you reboot the machine, and
  are asked to login, at which point gkr-pam complains that it can't
  locate control file.

  Unfortunately i don't have better details because eventually i broke
  so much my login that i decided to reinstall the system from scratch.

  Upon installation, i started from fresh, with no zsh, and everything
  worked. Once zsh was installed, it will no longer work.

  A fix for this was to revert to bash shell.

  The key change was to no include this line at the top of .bashrc

  ```

[Desktop-packages] [Bug 1817128] Re: gnome-keyring not automatically unlocked on login

Checking service status indicates the failures:

```
service gdm3 status
Process: ExecStartPre: /usr/share/gdm/generate-config 
(code=exited,status=0/SUCCESS)
Process: ExecStartPre: /usr/lib/gdm3/gdm-wait-for-drm 
(code=exited,status=0/SUCCESS)
...

gdm-password: gkr-pam: unable to local control file
```

Relevant components:

  * gdm3 3.34.1-1
  * gnome-shell 3.34.1-1
  * gnome-keyring 3.34.0-1


Also tried:

/etc/gdm/custom.conf

# Enable automatic login for user
[daemon]
AutomaticLogin=username
AutomaticLoginEnable=True

but this lead to a either a black screen with a mouse pointer, or after
resetting the dconf

```
dconf reset -f /
```

it would eventually crash and had to be hard rebooted.

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

Title:
  gnome-keyring not automatically unlocked on login

Status in gnome-keyring package in Ubuntu:
  Fix Released

Bug description:
  Hi

  After initializing and filling the login screen, at the start screen
  prompts for password to unlock the session keyring. Is this normal on
  Ubuntu disk 19.04.02?

  Note: When filling the login screen to start the micro, should it not
  be unlocked automatically?

  Attached the image of the request I fired it.

  Thank you


  **
  Hi

  Após inicialização e preenchimento da tela de login, ao iniciar a tela
  pede senha para desbloqueio do chaveiro de sessão. Isso é normal no
  Ubuntu disco 19.04.02?

  Obs: Quando do preenchimento da tela de login para iniciar o micro o
  desbloqueio não deveria ser automático?

  Em anexo a imagem da solicitação de desboquei-o.

  Obrigado

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

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

[Desktop-packages] [Bug 1818616] Re: gnome-keyring is not unlocked upon gdm login in disco

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

Filed report as well on Gnome:
https://gitlab.gnome.org/GNOME/gnome-keyring/issues/28

Relevant components:

  * gdm3 3.34.1-1
  * gnome-shell 3.34.1-1
  * gnome-keyring 3.34.0-1

So, no lightdm, unlike this similar issue:
https://github.com/canonical/lightdm/issues/70


they also suggested that the dconf may have become corrupted. 

I've tried as well:

```
mv .config/dconf/user ~/.config/dconf/user.bak
```

But didn't work.


** Bug watch added: gitlab.gnome.org/GNOME/gnome-keyring/issues #28
   https://gitlab.gnome.org/GNOME/gnome-keyring/issues/28

** Bug watch added: github.com/canonical/lightdm/issues #70
   https://github.com/canonical/lightdm/issues/70

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

Title:
  gnome-keyring is not unlocked upon gdm login in disco

Status in gdm3 package in Ubuntu:
  Confirmed
Status in gnome-keyring package in Ubuntu:
  Confirmed
Status in pam package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  I'm not sure if this is a regression in my gnome-keyring, gdm3, or pam, or 
local configuration.
  As far as I recall, I should be running just "stock" configs.
  I did not install system with disco, but upgraded to disco throughout 
development series.

  Upon booting, and logging in through gdm3, I get a pop-up from gnome-
  keyring instructing me that gnome-keyring was not unlocked upon
  logging, and I have to re-enter the password again.

  The password for the account and the gnome-keyring are the same, and
  the keyring should be auto-unlocked.

  Looking at the journal, there is a red warning from gdm:
  Mar 05 08:15:58 ottawa gdm-password][18338]: gkr-pam: unable to locate daemon 
control file
  Looking at the code, this happens when neither GNOME_KEYRING_CONTROL nor 
XDG_RUNTIME_DIR are set.

  The messages after it are:
  Mar 05 08:15:58 ottawa gdm-password][18338]: gkr-pam: unable to locate daemon 
control file
  Mar 05 08:15:58 ottawa gdm-password][18338]: pam_unix(gdm-password:session): 
session opened for user xnox by (uid=0)
  Mar 05 08:15:58 ottawa systemd[1]: Created slice User Slice of UID 1000.
  Mar 05 08:15:58 ottawa systemd[1]: Starting User Runtime Directory 
/run/user/1000...
  Mar 05 08:15:58 ottawa systemd-logind[1376]: New session 3 of user xnox.
  Mar 05 08:15:58 ottawa systemd[1]: Started User Runtime Directory 
/run/user/1000.
  Mar 05 08:15:58 ottawa systemd[1]: Starting User Manager for UID 1000...
  Mar 05 08:15:58 ottawa systemd[18344]: pam_unix(systemd-user:session): 
session opened for user xnox by (uid=0)
  Mar 05 08:15:58 ottawa systemd[18344]: Listening on Sound System.
  Mar 05 08:15:58 ottawa systemd[18344]: Listening on GnuPG cryptographic agent 
(ssh-agent emulation).
  Mar 05 08:15:58 ottawa systemd[18344]: Started Pending report trigger for 
Ubuntu Report.
  Mar 05 08:15:58 ottawa systemd[18344]: Listening on GnuPG cryptographic agent 
and passphrase cache (restricted).
  Mar 05 08:15:58 ottawa systemd[18344]: Listening on GnuPG cryptographic agent 
and passphrase cache.
  Mar 05 08:15:58 ottawa systemd[18344]: Reached target Paths.
  Mar 05 08:15:58 ottawa systemd[18344]: Listening on GnuPG cryptographic agent 
and passphrase cache (access for web browsers).
  Mar 05 08:15:58 ottawa systemd[18344]: Reached target Timers.
  Mar 05 08:15:58 ottawa systemd[18344]: Listening on GnuPG network certificate 
management daemon.
  Mar 05 08:15:58 ottawa systemd[18344]: Starting D-Bus User Message Bus Socket.
  Mar 05 08:15:58 ottawa systemd[18344]: Listening on D-Bus User Message Bus 
Socket.
  Mar 05 08:15:58 ottawa systemd[18344]: Reached target Sockets.
  Mar 05 08:15:58 ottawa systemd[18344]: Reached target Basic System.
  Mar 05 08:15:58 ottawa systemd[1]: Started User Manager for UID 1000.
  Mar 05 08:15:58 ottawa systemd[18344]: Started Emacs text editor.
  Mar 05 08:15:58 ottawa systemd[18344]: Reached target Default.
  Mar 05 08:15:58 ottawa systemd[18344]: Startup finished in 72ms.
  Mar 05 08:15:58 ottawa systemd[1]: Started Session 3 of user xnox.

  I don't believe GNOME_KEYRING_CONTROL used to be set, however I do see
  that XDG_RUNTIME_DIR to be created and set by logind. From the above
  logs I can see that it happens _after_ gdm-password is done.

  So It seems like something has changed in the stack, and gdm login /
  libpam-gnome-keyring no longer use systemd-logind PAM module to be
  part of the PAM session. But I'm not sure what has changed to cause
  this (gdm, gnome-keyring, pam, systemd).

  Am I the only one with this issue?

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: gnome-keyring 3.31.90-1ubuntu1
  ProcVersionSignature: Ubuntu 4.19.0-13.14-generic 4.19.20
  Uname: Linux 4.19.0-13-generic x86_64
  NonfreeKernelModules: zfs zunicode

[Desktop-packages] [Bug 1817128] Re: gnome-keyring not automatically unlocked on login

I can see that this problem is still present on eoan-ermine.

I upgraded from a development version to the latest 19.10

After several configurations of my shell, including zsh, oh-my-ssh and
others, after trying to login this morning, the issue appeared. no
system update, but a few small installations.


I'm unable to login via graphical interface, but able to do so on a separate 
terminal (CTRL+ALT+F2) directly to the terminal.

service gdm3 status shows the service active but shows errors:

gdm3: GDMDisplay: Session never registered, failing
gdm-password: gkr-pam: unable to locate daemon control file
gdm-password: pam_unix(gdm-password: session): session opened for user x by 
uid=0

and continues with the same error

How to solve this? at the moment i can only use terminal based login, no
UI

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

Title:
  gnome-keyring not automatically unlocked on login

Status in gnome-keyring package in Ubuntu:
  Fix Released

Bug description:
  Hi

  After initializing and filling the login screen, at the start screen
  prompts for password to unlock the session keyring. Is this normal on
  Ubuntu disk 19.04.02?

  Note: When filling the login screen to start the micro, should it not
  be unlocked automatically?

  Attached the image of the request I fired it.

  Thank you


  **
  Hi

  Após inicialização e preenchimento da tela de login, ao iniciar a tela
  pede senha para desbloqueio do chaveiro de sessão. Isso é normal no
  Ubuntu disco 19.04.02?

  Obs: Quando do preenchimento da tela de login para iniciar o micro o
  desbloqueio não deveria ser automático?

  Em anexo a imagem da solicitação de desboquei-o.

  Obrigado

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

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

[Desktop-packages] [Bug 1818616] Re: gnome-keyring is not unlocked upon gdm login in disco

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

I've reproduced this bug on eoan-ermine. See my comments on the related
bug report #1817128

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

Title:
  gnome-keyring is not unlocked upon gdm login in disco

Status in gdm3 package in Ubuntu:
  Confirmed
Status in gnome-keyring package in Ubuntu:
  Confirmed
Status in pam package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  I'm not sure if this is a regression in my gnome-keyring, gdm3, or pam, or 
local configuration.
  As far as I recall, I should be running just "stock" configs.
  I did not install system with disco, but upgraded to disco throughout 
development series.

  Upon booting, and logging in through gdm3, I get a pop-up from gnome-
  keyring instructing me that gnome-keyring was not unlocked upon
  logging, and I have to re-enter the password again.

  The password for the account and the gnome-keyring are the same, and
  the keyring should be auto-unlocked.

  Looking at the journal, there is a red warning from gdm:
  Mar 05 08:15:58 ottawa gdm-password][18338]: gkr-pam: unable to locate daemon 
control file
  Looking at the code, this happens when neither GNOME_KEYRING_CONTROL nor 
XDG_RUNTIME_DIR are set.

  The messages after it are:
  Mar 05 08:15:58 ottawa gdm-password][18338]: gkr-pam: unable to locate daemon 
control file
  Mar 05 08:15:58 ottawa gdm-password][18338]: pam_unix(gdm-password:session): 
session opened for user xnox by (uid=0)
  Mar 05 08:15:58 ottawa systemd[1]: Created slice User Slice of UID 1000.
  Mar 05 08:15:58 ottawa systemd[1]: Starting User Runtime Directory 
/run/user/1000...
  Mar 05 08:15:58 ottawa systemd-logind[1376]: New session 3 of user xnox.
  Mar 05 08:15:58 ottawa systemd[1]: Started User Runtime Directory 
/run/user/1000.
  Mar 05 08:15:58 ottawa systemd[1]: Starting User Manager for UID 1000...
  Mar 05 08:15:58 ottawa systemd[18344]: pam_unix(systemd-user:session): 
session opened for user xnox by (uid=0)
  Mar 05 08:15:58 ottawa systemd[18344]: Listening on Sound System.
  Mar 05 08:15:58 ottawa systemd[18344]: Listening on GnuPG cryptographic agent 
(ssh-agent emulation).
  Mar 05 08:15:58 ottawa systemd[18344]: Started Pending report trigger for 
Ubuntu Report.
  Mar 05 08:15:58 ottawa systemd[18344]: Listening on GnuPG cryptographic agent 
and passphrase cache (restricted).
  Mar 05 08:15:58 ottawa systemd[18344]: Listening on GnuPG cryptographic agent 
and passphrase cache.
  Mar 05 08:15:58 ottawa systemd[18344]: Reached target Paths.
  Mar 05 08:15:58 ottawa systemd[18344]: Listening on GnuPG cryptographic agent 
and passphrase cache (access for web browsers).
  Mar 05 08:15:58 ottawa systemd[18344]: Reached target Timers.
  Mar 05 08:15:58 ottawa systemd[18344]: Listening on GnuPG network certificate 
management daemon.
  Mar 05 08:15:58 ottawa systemd[18344]: Starting D-Bus User Message Bus Socket.
  Mar 05 08:15:58 ottawa systemd[18344]: Listening on D-Bus User Message Bus 
Socket.
  Mar 05 08:15:58 ottawa systemd[18344]: Reached target Sockets.
  Mar 05 08:15:58 ottawa systemd[18344]: Reached target Basic System.
  Mar 05 08:15:58 ottawa systemd[1]: Started User Manager for UID 1000.
  Mar 05 08:15:58 ottawa systemd[18344]: Started Emacs text editor.
  Mar 05 08:15:58 ottawa systemd[18344]: Reached target Default.
  Mar 05 08:15:58 ottawa systemd[18344]: Startup finished in 72ms.
  Mar 05 08:15:58 ottawa systemd[1]: Started Session 3 of user xnox.

  I don't believe GNOME_KEYRING_CONTROL used to be set, however I do see
  that XDG_RUNTIME_DIR to be created and set by logind. From the above
  logs I can see that it happens _after_ gdm-password is done.

  So It seems like something has changed in the stack, and gdm login /
  libpam-gnome-keyring no longer use systemd-logind PAM module to be
  part of the PAM session. But I'm not sure what has changed to cause
  this (gdm, gnome-keyring, pam, systemd).

  Am I the only one with this issue?

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: gnome-keyring 3.31.90-1ubuntu1
  ProcVersionSignature: Ubuntu 4.19.0-13.14-generic 4.19.20
  Uname: Linux 4.19.0-13-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.10-0ubuntu21
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Mar  5 08:22:01 2019
  InstallationDate: Installed on 2016-01-26 (1134 days ago)
  InstallationMedia: Ubuntu-Server 16.04 LTS "Xenial Xerus" - Alpha amd64 
(20160125)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-keyring
  UpgradeStatus: Upgraded to disco on 2019-01-15 (48 days ago)

To manage notifications about this bug go to:

[Desktop-packages] [Bug 1833197] Re: crashes when creating annotations (Segmentation fault (core dumped))

2019-06-21 Thread Fernando

Hi Sebastien, thanks for your prompt reply. I'm in the latest LTS. I
don't see any trace of the crash. Maybe it was automatically reported? I
think I have it configured that way. I'll try to reproduce it and then
go through the instructions in the link, although, as I say, it's hard
to reproduce. I just happens after creating annotations for a while.

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

Title:
  crashes when creating annotations (Segmentation fault (core dumped))

Status in evince package in Ubuntu:
  Incomplete

Bug description:
  After creating several annotations in a PDF document evince ends up
  crashing with an inespecific segfault terminal output. It happens
  always, but it takes a long time, so it's hard to reproduce, and it
  doesn't always happens in the same place, despite I've tried to hit
  the bug reopening and inserting an annotation in the same place.

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

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

[Desktop-packages] [Bug 1833197] [NEW] crashes when creating annotations (Segmentation fault (core dumped))

2019-06-18 Thread Fernando

Public bug reported:

After creating several annotations in a PDF document evince ends up
crashing with an inespecific segfault terminal output. It happens
always, but it takes a long time, so it's hard to reproduce, and it
doesn't always happens in the same place, despite I've tried to hit the
bug reopening and inserting an annotation in the same place.

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

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

Title:
  crashes when creating annotations (Segmentation fault (core dumped))

Status in evince package in Ubuntu:
  New

Bug description:
  After creating several annotations in a PDF document evince ends up
  crashing with an inespecific segfault terminal output. It happens
  always, but it takes a long time, so it's hard to reproduce, and it
  doesn't always happens in the same place, despite I've tried to hit
  the bug reopening and inserting an annotation in the same place.

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

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

[Desktop-packages] [Bug 1725588] Re: [regression] borders around tabs in preferences are invisible

2019-05-04 Thread Fernando

Still happening in Bionic with the latest 60.6.1, with the default
theme.

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

Title:
  [regression] borders around tabs in preferences are invisible

Status in thunderbird package in Ubuntu:
  Confirmed

Bug description:
  Potentially related with [1].

  Reproducible in TB 1:52.4.0+build1-0ubuntu2 with default theme for
  both TB and Ubuntu.

  Screenshot attached.

  [1] https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1721189

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

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

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

2019-03-20 Thread Fernando

1:3.26.4-0~ubuntu18.04.4 also fixed this bug for me in Bionic, thanks!

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

Title:
  Full text search does not work

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

Bug description:
  * Impact
  The text search feature, which is depending on tracker, is not working even 
when the service is installed

  * Test case
  - install tracker and restart your session
  - echo 'Nautilus is great' > ~/txt
  - open nautilus and type 'great' in the search entry

  -> the file should be listed

  * Regression potential

  That's changing the search provider logic, make sure that searching
  for file without tracker still works (that only look at filenames) and
  there is no extra logging/cpu usage

  ---

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

  1.

  Description:  Ubuntu 18.04 LTS
  Release:  18.04

  2.

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

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

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

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

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

[Desktop-packages] [Bug 1803127] Re: remmina not able to redirect smart card reader

2019-03-11 Thread Fernando

Ubuntu Mate 18.04
1.2.0-rcgit-29 (git rcgit-29)

Package: remmina
Architecture: amd64
Version: 1.2.0-rcgit.29+dfsg-1ubuntu1
Multi-Arch: foreign
Priority: optional
Section: gnome
Origin: Ubuntu
Maintainer: Ubuntu Developers 
Original-Maintainer: Debian Remote Maintainers 
Bugs: https://bugs.launchpad.net/ubuntu/+filebug
Installed-Size: 441
Depends: libappindicator3-1 (>= 0.4.90), libavahi-client3 (>= 0.6.16), 
libavahi-common3 (>= 0.6.16), libavahi-ui-gtk3-0 (>= 0.6.30), libc6 (>= 2.15), 
libcairo2 (>= 1.6.0), libgcrypt20 (>= 1.8.0), libglib2.0-0 (>= 2.41.2), 
libgtk-3-0 (>= 3.21.5), libjson-glib-1.0-0 (>= 1.2.0), libpango-1.0-0 (>= 
1.14.0), libsoup2.4-1 (>= 2.41.90), libssh-4 (>= 0.6.1), libssl1.1 (>= 1.1.0), 
libvte-2.91-0 (>= 0.49.92), remmina-common (= 1.2.0-rcgit.29+dfsg-1ubuntu1), 
default-dbus-session-bus | dbus-session-bus
Recommends: remmina-plugin-rdp, remmina-plugin-vnc, remmina-plugin-secret
Suggests: remmina-plugin-exec, remmina-plugin-nx, remmina-plugin-spice, 
remmina-plugin-telepathy, remmina-plugin-xdmcp
Filename: pool/main/r/remmina/remmina_1.2.0-rcgit.29+dfsg-1ubuntu1_amd64.deb

It happens the same to me too. The smart card is not shared.

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

Title:
  remmina not able to redirect smart card reader

Status in remmina package in Ubuntu:
  Confirmed

Bug description:
  Linux Mint 19
  1.2.0-rcgit-29 (git rcgit-29)
  Cinamon
  Windows 7 Pro
  RDP
  remmina:
Installed: 1.2.0-rcgit.29+dfsg-1ubuntu1
Candidate: 1.2.0-rcgit.29+dfsg-1ubuntu1
Version table:
   *** 1.2.0-rcgit.29+dfsg-1ubuntu1 500
  500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages

  I expect to see working solution for this problem. The same problem is
  and with Ubuntu 18.04 LTS.

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

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

[Desktop-packages] [Bug 1778011] Re: SRU: PRIME Power Saving mode draws too much power

2018-11-09 Thread Fernando Jascovich

@Alberto: Is there any chance that this work-around works without gdm3? 
I'm using ubuntu-server 18.04 and this my laptop configuration:
➜  ~ inxi -G
Graphics:  Card-1: Intel HD Graphics 5500
   Card-2: NVIDIA GK208M [GeForce 920M]
   Display Server: X.Org 1.19.6 driver: intel Resolution: 
1366x768@60.06hz
   OpenGL: renderer: Mesa DRI Intel HD Graphics 5500 (Broadwell GT2) 
version: 4.5 Mesa 18.0.5

I followed the steps and installed required packages as follows:
➜  ~ sudo apt install nvidia-driver-390/bionic-updates 
ubuntu-drivers-common/bionic-proposed nvidia-prime/bionic-proposed 
nvidia-settings/bionic-updates libnvidia-gl-390/bionic-updates 
libnvidia-compute-390/bionic-updates libnvidia-decode-390/bionic-updates 
libnvidia-encode-390/bionic-updates libnvidia-ifr1-390/bionic-updates 
libnvidia-fbc1-390/bionic-updates

Then I executed "sudo prime-select nvidia".
But after rebooting, I have no openGl support and this error is present at 
Xorg's logs:
VGA arbiter: cannot open kernel arbiter, no multi-card support
Nvidia kernel modules are loaded and Xorg seems to register nvidia driver at 
init.

If I try to run glxgears for example, I get the following message:
glxinfo Error: couldn't get an RGB, Double-buffered visual

And using "sudo prime-select intel" also leaves me without GL. I think
this is something related to gpu-manager, because I am not using any
display manager, just running xorg from startx.

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

Title:
  SRU: PRIME Power Saving mode draws too much power

Status in HWE Next:
  New
Status in gdm3 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-390 package in Ubuntu:
  Fix Released
Status in nvidia-prime package in Ubuntu:
  Fix Released
Status in nvidia-settings package in Ubuntu:
  Fix Released
Status in ubuntu-drivers-common package in Ubuntu:
  Fix Released
Status in gdm3 source package in Bionic:
  Fix Released
Status in nvidia-graphics-drivers-390 source package in Bionic:
  Fix Released
Status in nvidia-prime source package in Bionic:
  Fix Released
Status in nvidia-settings source package in Bionic:
  Fix Released
Status in ubuntu-drivers-common source package in Bionic:
  Fix Released

Bug description:
  SRU Request:

  [Impact]
  Relying on the nouveau driver and on the vga switcheroo (to get around a 
change in systemd LP: #1777099) caused increased power consumption, and slowed 
down the switching process.

  Furthermore, if the main X/Xwayland session was started by Gdm when
  the nvidia driver was loaded, the session will keep the nvidia module
  loaded, and prevent the system from switching off the dGPU. Also, the
  nouveau driver will be loaded, if nvidia is not, and this can cause
  problems to unsupported NVIDIA GPUs.

  The solution involves the following changes:

  1) Solving the problem in systemd (LP: #1777099)

  2) Adding code in gpu-manager and in nvidia-prime to unload the nvidia
  modules, and to allow the PCI device to sleep.

  3) Making a slight change to the current patch in Gdm, used to call
  the PRIME scripts before and after a Gdm session (so that gpu-manager
  gets actually called on log out)

  4) Adding code in gpu-manager to kill the main X/Xwayland session on
  log out, if the session is preventing us from unloading the nvidia
  driver. A new X/Xwayland session will be created after unload the
  module.

  5) Removing the systemd service that loads nouveau from the nvidia
  packages.

  [Test Case]
  1) Enable the -proposed repository, and install the new 
"ubuntu-drivers-common", nvidia drivers, nvidia-prime, and gdm3 *

  2) Make sure the nvidia packages are installed, and enable performance mode 
(if it is already enabled, call "sudo prime-select intel" first):
  sudo prime-select nvidia

  3) Restart your computer and attach your /var/log/gpu-manager.log. see
  if the system boots correctly. If unsure, please attach your /var/log
  /gpu-manager.log and /var/log/Xorg.0.log

  4) Select power saving mode:
  sudo prime-select intel

  5) Log out and log back in

  6) Check if the nvidia driver is still loaded:
  lsmod | grep nvidia

  [Regression Potential]
  Low, as hybrid graphics support does not work correctly, and the changes only 
affect this use case.

  _
  * Steps to test the updates:

  1) Enable the bionic-proposed repositories

  2) Create /etc/apt/preferences.d/proposed-updates with the following
  content:

  Package: *
  Pin: release a=bionic-proposed
  Pin-Priority: 400

  3) Update the list of packages:

  sudo apt-get update

  4) Install the packages from -proposed using the following command:

  sudo apt install nvidia-driver-390/bionic-proposed gdm3/bionic-
  proposed ubuntu-drivers-common/bionic-proposed nvidia-prime/bionic-
  proposed nvidia-settings/bionic-proposed

[Desktop-packages] [Bug 1726262] Re: 17.10 - flickering overlay patterns in gnome-terminal

2018-06-24 Thread Fernando Barbosa

I am affected too. And using Ubuntu 18.04 and a NVIDIA card.

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

Title:
  17.10 - flickering overlay patterns in gnome-terminal

Status in gnome-terminal package in Ubuntu:
  Confirmed

Bug description:
  Clean install of Ubuntu 17.10.

  For gnome-terminal select color-scheme "black on light yellow".

  Overlay partly with e.g. Chrome (Browser) or Geany (editor). Then the
  border shadow of the e.g. Geany produces flickering extended shadows
  in the gnome-terminal. Foto with the extended shadows is attached.

  This bug was introduced with 17.10. This flickering didn't appear in
  17.04, 16.10, 16.04...

  Working as a developer with several open terminal windows on the
  desktop, this produces a disturbing desktop environment and mitigated
  by covering not used terminal windows complete with other apps.

  Haven't reproduced with other apps than gnome-terminal.

  Hardware
  Lenovo Thinkpad e330, cpu : Intel(R) Core(TM) i5-3210M CPU @ 2.50GHz
  gpu Builtin : HD 4000

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

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

[Desktop-packages] [Bug 1773844] [NEW] [NH4CU03, Realtek ALC269VB, Speaker, Internal] No sound at all

2018-05-28 Thread Fernando André

Public bug reported:

This issue happens on xubuntu 17.10 and also ubuntu.
It may be related to this bug 
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/802998
802998 , but since I'm using a new version I reported it again.

1)
lsb_release -rd
Description:Ubuntu 17.10
Release:17.10

2)
apt-cache policy alsa-base
alsa-base:
  Instalado: 1.0.25+dfsg-0ubuntu5
  Candidato: 1.0.25+dfsg-0ubuntu5
  Tabela de versão:
 *** 1.0.25+dfsg-0ubuntu5 500
500 http://br.archive.ubuntu.com/ubuntu artful/main amd64 Packages
500 http://br.archive.ubuntu.com/ubuntu artful/main i386 Packages
100 /var/lib/dpkg/status

5)
uname -a
Linux patricia-NH4CU03 4.16.12 #1 SMP Sun May 27 16:56:57 -03 2018 x86_64 
x86_64 x86_64 GNU/Linux
Also happens on normal kernel version of 17.10 xubuntu and ubuntu
3)
I would expect it to play sound.

4)
It doesn't play any sound.

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: alsa-base 1.0.25+dfsg-0ubuntu5
Uname: Linux 4.16.12 x86_64
ApportVersion: 2.20.7-0ubuntu3.7
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  andref 1587 F pulseaudio
CurrentDesktop: XFCE
Date: Mon May 28 16:05:23 2018
InstallationDate: Installed on 2018-01-25 (123 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
PackageArchitecture: all
ProcEnviron:
 LANGUAGE=pt_BR:pt:en
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=pt_BR.UTF-8
 SHELL=/bin/bash
SourcePackage: alsa-driver
Symptom: audio
Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed
Symptom_Card: Áudio interno - HDA Intel PCH
Symptom_DevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  andref 1587 F pulseaudio
Symptom_Jack: Speaker, Internal
Symptom_Type: No sound at all
Title: [NH4CU03, Realtek ALC269VB, Speaker, Internal] No sound at all
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 04/16/2013
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 1.00W
dmi.board.name: NH4CU03
dmi.board.vendor: Digiboard
dmi.board.version: 1.0
dmi.chassis.type: 10
dmi.chassis.vendor: Digibras
dmi.chassis.version: 1.0
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.00W:bd04/16/2013:svnDigibras:pnNH4CU03:pvr1.0:rvnDigiboard:rnNH4CU03:rvr1.0:cvnDigibras:ct10:cvr1.0:
dmi.product.name: NH4CU03
dmi.product.version: 1.0
dmi.sys.vendor: Digibras
mtime.conffile..etc.modprobe.d.alsa-base.conf: 2018-05-26T21:36:27.395468

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


** Tags: amd64 apport-bug artful

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

Title:
  [NH4CU03, Realtek ALC269VB, Speaker, Internal] No sound at all

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  This issue happens on xubuntu 17.10 and also ubuntu.
  It may be related to this bug 
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/802998
  802998 , but since I'm using a new version I reported it again.

  1)
  lsb_release -rd
  Description:  Ubuntu 17.10
  Release:  17.10

  2)
  apt-cache policy alsa-base
  alsa-base:
Instalado: 1.0.25+dfsg-0ubuntu5
Candidato: 1.0.25+dfsg-0ubuntu5
Tabela de versão:
   *** 1.0.25+dfsg-0ubuntu5 500
  500 http://br.archive.ubuntu.com/ubuntu artful/main amd64 Packages
  500 http://br.archive.ubuntu.com/ubuntu artful/main i386 Packages
  100 /var/lib/dpkg/status

  5)
  uname -a
  Linux patricia-NH4CU03 4.16.12 #1 SMP Sun May 27 16:56:57 -03 2018 x86_64 
x86_64 x86_64 GNU/Linux
  Also happens on normal kernel version of 17.10 xubuntu and ubuntu
  3)
  I would expect it to play sound.

  4)
  It doesn't play any sound.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  Uname: Linux 4.16.12 x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  andref 1587 F pulseaudio
  CurrentDesktop: XFCE
  Date: Mon May 28 16:05:23 2018
  InstallationDate: Installed on 2018-01-25 (123 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
  PackageArchitecture: all
  ProcEnviron:
   LANGUAGE=pt_BR:pt:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=pt_BR.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed
  Symptom_Card: Áudio interno - HDA Intel PCH
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  andref 1587 F pulseaudio
  Symptom_Jack: Speaker, Internal
  Symptom_Type: No sound at all
  Title: [NH4CU03, Realtek ALC269VB, Speaker, Internal] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/16/2013

[Desktop-packages] [Bug 1767005] [NEW] package libreoffice-pdfimport 1:5.1.6~rc2-0ubuntu1~xenial3 failed to install/upgrade: problemas de dependência - deixando desconfigurado

2018-04-25 Thread Fernando

Public bug reported:

error appeared when I booted the pc

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: libreoffice-pdfimport 1:5.1.6~rc2-0ubuntu1~xenial3
ProcVersionSignature: Ubuntu 4.4.0-109.132-generic 4.4.98
Uname: Linux 4.4.0-109-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.15
Architecture: amd64
Date: Tue Apr 24 08:47:37 2018
ErrorMessage: problemas de dependência - deixando desconfigurado
InstallationDate: Installed on 2016-09-28 (574 days ago)
InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719)
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.2
 apt  1.2.20
SourcePackage: libreoffice
Title: package libreoffice-pdfimport 1:5.1.6~rc2-0ubuntu1~xenial3 failed to 
install/upgrade: problemas de dependência - deixando desconfigurado
UpgradeStatus: No upgrade log present (probably fresh install)

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

Title:
  package libreoffice-pdfimport 1:5.1.6~rc2-0ubuntu1~xenial3 failed to
  install/upgrade: problemas de dependência - deixando desconfigurado

Status in libreoffice package in Ubuntu:
  New

Bug description:
  error appeared when I booted the pc

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libreoffice-pdfimport 1:5.1.6~rc2-0ubuntu1~xenial3
  ProcVersionSignature: Ubuntu 4.4.0-109.132-generic 4.4.98
  Uname: Linux 4.4.0-109-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  Date: Tue Apr 24 08:47:37 2018
  ErrorMessage: problemas de dependência - deixando desconfigurado
  InstallationDate: Installed on 2016-09-28 (574 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.20
  SourcePackage: libreoffice
  Title: package libreoffice-pdfimport 1:5.1.6~rc2-0ubuntu1~xenial3 failed to 
install/upgrade: problemas de dependência - deixando desconfigurado
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1747911] [NEW] package libsane1 1.0.27-1~experimental2ubuntu2.1 failed to install/upgrade: intentando sobreescribir el compartido `/lib/udev/hwdb.d/20-sane.hwdb', que es distin

2018-02-07 Thread Fernando Pérez

Public bug reported:

It's the first time I use Linux and I don't have a cue of most
things

Hope this helps.

Regards,

Fernando.

ProblemType: Package
DistroRelease: Ubuntu 17.10
Package: libsane1 1.0.27-1~experimental2ubuntu2.1
ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
Uname: Linux 4.13.0-32-generic x86_64
ApportVersion: 2.20.7-0ubuntu3.7
Architecture: amd64
Date: Wed Feb  7 14:19:50 2018
ErrorMessage: intentando sobreescribir el compartido 
`/lib/udev/hwdb.d/20-sane.hwdb', que es distinto de otras instancias del 
paquetes libsane1:i386
Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 
3.6.3-0ubuntu2
PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 
2.7.14-2ubuntu1
RelatedPackageVersions:
 dpkg 1.18.24ubuntu1
 apt  1.5.1
SourcePackage: sane-backends
Title: package libsane1 1.0.27-1~experimental2ubuntu2.1 failed to 
install/upgrade: intentando sobreescribir el compartido 
`/lib/udev/hwdb.d/20-sane.hwdb', que es distinto de otras instancias del 
paquetes libsane1:i386
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-package artful

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

Title:
  package libsane1 1.0.27-1~experimental2ubuntu2.1 failed to
  install/upgrade: intentando sobreescribir el compartido
  `/lib/udev/hwdb.d/20-sane.hwdb', que es distinto de otras instancias
  del paquetes libsane1:i386

Status in sane-backends package in Ubuntu:
  New

Bug description:
  It's the first time I use Linux and I don't have a cue of most
  things

  Hope this helps.

  Regards,

  Fernando.

  ProblemType: Package
  DistroRelease: Ubuntu 17.10
  Package: libsane1 1.0.27-1~experimental2ubuntu2.1
  ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  Date: Wed Feb  7 14:19:50 2018
  ErrorMessage: intentando sobreescribir el compartido 
`/lib/udev/hwdb.d/20-sane.hwdb', que es distinto de otras instancias del 
paquetes libsane1:i386
  Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 
3.6.3-0ubuntu2
  PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 
2.7.14-2ubuntu1
  RelatedPackageVersions:
   dpkg 1.18.24ubuntu1
   apt  1.5.1
  SourcePackage: sane-backends
  Title: package libsane1 1.0.27-1~experimental2ubuntu2.1 failed to 
install/upgrade: intentando sobreescribir el compartido 
`/lib/udev/hwdb.d/20-sane.hwdb', que es distinto de otras instancias del 
paquetes libsane1:i386
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1553685] Re: Lenovo Y700-17ISK subwoofer doesn't work

2018-01-25 Thread Fernando Consigli

Subwoofer doesn't work on Lenovo Y720-15IKB / Ubuntu 17.10 either :(

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

Title:
  Lenovo Y700-17ISK subwoofer doesn't work

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  Lenovo Y700-17ISK (Intel Core i7-6700HQ/RAM 16GB/SSD 512GB/Nvidia GTX960M 4GB)
  Operating system: Ubuntu 16.04 (xenial-desktop-amd64.iso 04-Mar-2016, kernel 
4.4.0-10-generic, nvidia 361.28)

  Problem: Notebook subwoofer doesn't work.

  Judging from alsa-info.sh output, there is no pin declared for the bass 
output by BIOS.
  Please find a zip file attached: 'alsa-info_hdajackretask-unconnected-pins'

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-10-generic 4.4.0-10.25
  ProcVersionSignature: Ubuntu 4.4.0-10.25-generic 4.4.3
  Uname: Linux 4.4.0-10-generic x86_64
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  aljosa 1776 F pulseaudio
  CurrentDesktop: Unity
  Date: Sun Mar  6 11:02:21 2016
  HibernationDevice: RESUME=UUID=ac022671-63df-40ae-bffe-66fff3b35125
  InstallationDate: Installed on 2016-03-05 (0 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160304)
  MachineType: LENOVO 80Q0
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-10-generic.efi.signed 
root=UUID=aa4325c4-4b4c-4372-b8ca-a66c3e5b2aa6 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-10-generic N/A
   linux-backports-modules-4.4.0-10-generic  N/A
   linux-firmware1.156
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/31/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: CDCN30WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: Allsparks 7A
  dmi.board.vendor: LENOVO
  dmi.board.version: NO DPK
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo ideapad Y700-17ISK
  dmi.modalias: 
dmi:bvnLENOVO:bvrCDCN30WW:bd01/31/2016:svnLENOVO:pn80Q0:pvrLenovoideapadY700-17ISK:rvnLENOVO:rnAllsparks7A:rvrNODPK:cvnLENOVO:ct10:cvrLenovoideapadY700-17ISK:
  dmi.product.name: 80Q0
  dmi.product.version: Lenovo ideapad Y700-17ISK
  dmi.sys.vendor: LENOVO

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

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

[Desktop-packages] [Bug 1707666] [NEW] package libsane (not installed) failed to install/upgrade: trying to overwrite '/etc/sane.d/kodakaio.conf', which is also in package libsane-common 1.0.25+git201

2017-07-31 Thread fernando cabral

Public bug reported:

ubuntu 16.04 lts

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: libsane (not installed)
ProcVersionSignature: Ubuntu 4.4.0-87.110-generic 4.4.73
Uname: Linux 4.4.0-87-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.10
Architecture: amd64
Date: Mon Jul 31 16:58:43 2017
DpkgTerminalLog:
 Preparing to unpack .../libsane_1.0.27+git20170729-xenial0_amd64.deb ...
 Unpacking libsane:amd64 (1.0.27+git20170729-xenial0) over 
(1.0.25+git20150528-1ubuntu2.16.04.1) ...
 dpkg: error processing archive 
/var/cache/apt/archives/libsane_1.0.27+git20170729-xenial0_amd64.deb (--unpack):
  trying to overwrite '/etc/sane.d/kodakaio.conf', which is also in package 
libsane-common 1.0.25+git20150528-1ubuntu2.16.04.1
DuplicateSignature:
 package:libsane:(not installed)
 Unpacking libsane:amd64 (1.0.27+git20170729-xenial0) over 
(1.0.25+git20150528-1ubuntu2.16.04.1) ...
 dpkg: error processing archive 
/var/cache/apt/archives/libsane_1.0.27+git20170729-xenial0_amd64.deb (--unpack):
  trying to overwrite '/etc/sane.d/kodakaio.conf', which is also in package 
libsane-common 1.0.25+git20150528-1ubuntu2.16.04.1
ErrorMessage: trying to overwrite '/etc/sane.d/kodakaio.conf', which is also in 
package libsane-common 1.0.25+git20150528-1ubuntu2.16.04.1
InstallationDate: Installed on 2016-04-29 (457 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.2
 apt  1.2.20
SourcePackage: sane-backends
Title: package libsane (not installed) failed to install/upgrade: trying to 
overwrite '/etc/sane.d/kodakaio.conf', which is also in package libsane-common 
1.0.25+git20150528-1ubuntu2.16.04.1
UpgradeStatus: No upgrade log present (probably fresh install)

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


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

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

Title:
  package libsane (not installed) failed to install/upgrade: trying to
  overwrite '/etc/sane.d/kodakaio.conf', which is also in package
  libsane-common 1.0.25+git20150528-1ubuntu2.16.04.1

Status in sane-backends package in Ubuntu:
  New

Bug description:
  ubuntu 16.04 lts

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libsane (not installed)
  ProcVersionSignature: Ubuntu 4.4.0-87.110-generic 4.4.73
  Uname: Linux 4.4.0-87-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  Date: Mon Jul 31 16:58:43 2017
  DpkgTerminalLog:
   Preparing to unpack .../libsane_1.0.27+git20170729-xenial0_amd64.deb ...
   Unpacking libsane:amd64 (1.0.27+git20170729-xenial0) over 
(1.0.25+git20150528-1ubuntu2.16.04.1) ...
   dpkg: error processing archive 
/var/cache/apt/archives/libsane_1.0.27+git20170729-xenial0_amd64.deb (--unpack):
trying to overwrite '/etc/sane.d/kodakaio.conf', which is also in package 
libsane-common 1.0.25+git20150528-1ubuntu2.16.04.1
  DuplicateSignature:
   package:libsane:(not installed)
   Unpacking libsane:amd64 (1.0.27+git20170729-xenial0) over 
(1.0.25+git20150528-1ubuntu2.16.04.1) ...
   dpkg: error processing archive 
/var/cache/apt/archives/libsane_1.0.27+git20170729-xenial0_amd64.deb (--unpack):
trying to overwrite '/etc/sane.d/kodakaio.conf', which is also in package 
libsane-common 1.0.25+git20150528-1ubuntu2.16.04.1
  ErrorMessage: trying to overwrite '/etc/sane.d/kodakaio.conf', which is also 
in package libsane-common 1.0.25+git20150528-1ubuntu2.16.04.1
  InstallationDate: Installed on 2016-04-29 (457 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.20
  SourcePackage: sane-backends
  Title: package libsane (not installed) failed to install/upgrade: trying to 
overwrite '/etc/sane.d/kodakaio.conf', which is also in package libsane-common 
1.0.25+git20150528-1ubuntu2.16.04.1
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1701848] [NEW] package tex-common 6.04 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

2017-07-01 Thread fernando

Public bug reported:

I don't know

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: tex-common 6.04
ProcVersionSignature: Ubuntu 4.4.0-83.106-generic 4.4.70
Uname: Linux 4.4.0-83-generic i686
ApportVersion: 2.20.1-0ubuntu2.6
Architecture: i386
Date: Sat Jul  1 22:31:42 2017
ErrorMessage: subprocess installed post-installation script returned error exit 
status 1
InstallationDate: Installed on 2013-02-16 (1596 days ago)
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release i386 (20120423)
PackageArchitecture: all
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.2
 apt  1.2.20
SourcePackage: tex-common
Title: package tex-common 6.04 failed to install/upgrade: subprocess installed 
post-installation script returned error exit status 1
UpgradeStatus: Upgraded to xenial on 2016-08-11 (324 days ago)

** Affects: tex-common (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: apport-package i386 need-duplicate-check xenial

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

Title:
  package tex-common 6.04 failed to install/upgrade: subprocess
  installed post-installation script returned error exit status 1

Status in tex-common package in Ubuntu:
  New

Bug description:
  I don't know

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: tex-common 6.04
  ProcVersionSignature: Ubuntu 4.4.0-83.106-generic 4.4.70
  Uname: Linux 4.4.0-83-generic i686
  ApportVersion: 2.20.1-0ubuntu2.6
  Architecture: i386
  Date: Sat Jul  1 22:31:42 2017
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  InstallationDate: Installed on 2013-02-16 (1596 days ago)
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release i386 
(20120423)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.20
  SourcePackage: tex-common
  Title: package tex-common 6.04 failed to install/upgrade: subprocess 
installed post-installation script returned error exit status 1
  UpgradeStatus: Upgraded to xenial on 2016-08-11 (324 days ago)

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

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

[Desktop-packages] [Bug 1700043] [NEW] Thunderbird unable to print/preview

2017-06-23 Thread Fernando Fernandez

Public bug reported:

Since the upgrade to 17.04 thunderbird no longer prints. Even preview is
not working. I tried two different printers, txt and html messages. The
preview window comes empty (see attachement) and the printed sheets come
only with header and footer, but no content (html messages produce only
some horizontal lines, but no real content rendering). My printers are
an HP Laserjet and a Samsung CLP laser.

ProblemType: Bug
DistroRelease: Ubuntu 17.04
Package: thunderbird 1:52.1.1+build1-0ubuntu0.17.04.1
ProcVersionSignature: Ubuntu 4.10.0-24.28-generic 4.10.15
Uname: Linux 4.10.0-24-generic x86_64
AddonCompatCheckDisabled: False
ApportVersion: 2.20.4-0ubuntu4.1
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  ferdez 4497 F pulseaudio
BuildID: 20170510140118
Channel: Unavailable
CurrentDesktop: GNOME
Date: Fri Jun 23 10:40:04 2017
Extensions: extensions.sqlite corrupt or missing
ForcedLayersAccel: False
IfupdownConfig:
 # interfaces(5) file used by ifup(8) and ifdown(8)
 auto lo
 iface lo inet loopback
IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini 
or extensions.sqlite)
InstallationDate: Installed on 2016-05-16 (402 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
IpRoute:
 default via 10.10.1.1 dev wlp13s0 proto static metric 600 
 10.10.1.0/24 dev wlp13s0 proto kernel scope link src 10.10.1.6 metric 600 
 169.254.0.0/16 dev docker0 scope link metric 1000 linkdown 
 172.17.0.0/16 dev docker0 proto kernel scope link src 172.17.0.1 linkdown 
 192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1 linkdown
Locales: extensions.sqlite corrupt or missing
MostRecentCrashID: bp-2ed35e03-ea9c-4c52-9e63-2b9872161102
Plugins: Shockwave Flash - /usr/lib/flashplugin-installer/libflashplayer.so
PrefSources:
 prefs.js
 
[Profile]/extensions/{a62ef8ec-5fdc-40c2-873c-223b8a6925cc}/defaults/preferences/preferences.js
 
[Profile]/extensions/{e2fda1a4-762b-4020-b5ad-a41df1933103}/defaults/preferences/lightning.js
Profiles: Profile0 (Default) - LastVersion=52.1.1/20170510140118 (In use)
RunningIncompatibleAddons: False
SourcePackage: thunderbird
Themes: extensions.sqlite corrupt or missing
UpgradeStatus: Upgraded to zesty on 2017-06-04 (18 days ago)
dmi.bios.date: 10/08/2015
dmi.bios.vendor: INSYDE Corp.
dmi.bios.version: 1.20
dmi.board.name: 06F4
dmi.board.vendor: FF50
dmi.board.version: Type2 - Board Version
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: OEM Chassis ManuFacturer
dmi.chassis.version: OEM Chassis Version
dmi.modalias: 
dmi:bvnINSYDECorp.:bvr1.20:bd10/08/2015:svnTOSHIBA:pnSATELLITEP50-C:pvrPSPUEE-00C008EP:rvnFF50:rn06F4:rvrType2-BoardVersion:cvnOEMChassisManuFacturer:ct10:cvrOEMChassisVersion:
dmi.product.name: SATELLITE P50-C
dmi.product.version: PSPUEE-00C008EP
dmi.sys.vendor: TOSHIBA

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


** Tags: amd64 apport-bug zesty

** Attachment added: "Empty preview window"
   
https://bugs.launchpad.net/bugs/1700043/+attachment/4901490/+files/gnome-shell-screenshot-Y6YA2Y.png

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

Title:
  Thunderbird unable to print/preview

Status in thunderbird package in Ubuntu:
  New

Bug description:
  Since the upgrade to 17.04 thunderbird no longer prints. Even preview
  is not working. I tried two different printers, txt and html messages.
  The preview window comes empty (see attachement) and the printed
  sheets come only with header and footer, but no content (html messages
  produce only some horizontal lines, but no real content rendering). My
  printers are an HP Laserjet and a Samsung CLP laser.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: thunderbird 1:52.1.1+build1-0ubuntu0.17.04.1
  ProcVersionSignature: Ubuntu 4.10.0-24.28-generic 4.10.15
  Uname: Linux 4.10.0-24-generic x86_64
  AddonCompatCheckDisabled: False
  ApportVersion: 2.20.4-0ubuntu4.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ferdez 4497 F pulseaudio
  BuildID: 20170510140118
  Channel: Unavailable
  CurrentDesktop: GNOME
  Date: Fri Jun 23 10:40:04 2017
  Extensions: extensions.sqlite corrupt or missing
  ForcedLayersAccel: False
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  IncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
  InstallationDate: Installed on 2016-05-16 (402 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  IpRoute:
   default via 10.10.1.1 dev wlp13s0 proto static metric 600 
   10.10.1.0/24 dev wlp13s0 proto kernel scope link src 10.10.1.6 metric 600 
   169.254.0.0/16

[Desktop-packages] [Bug 1692330] Re: firefox hangs using 100% cpu

Managed to put my finger on the pattern. Had something to do with stored
passwords. Tried to import stored passwords with Chromium and the same
thing happened. It's probably a corrupted  sqlite file. :-(

Moved away the firefox folder in .mozilla and the problem went away.

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

Title:
  firefox hangs using 100% cpu

Status in firefox package in Ubuntu:
  New

Bug description:
  This happens randomly, firefox just starts using 100% cpu and hangs.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: firefox 53.0.2+build1-0ubuntu0.16.10.2
  ProcVersionSignature: Ubuntu 4.8.0-52.55-generic 4.8.17
  Uname: Linux 4.8.0-52-generic x86_64
  AddonCompatCheckDisabled: False
  ApportVersion: 2.20.3-0ubuntu8.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   ferdez 4600 F...m pulseaudio
   /dev/snd/controlC0:  ferdez 4600 F pulseaudio
  BuildID: 20170509205820
  Channel: Unavailable
  CurrentDesktop: Unity
  Date: Sun May 21 16:08:41 2017
  DefaultProfileIncompatibleExtensions:
   Português Portugal Language Pack - langpack-pt...@firefox.mozilla.org
   English (GB) Language Pack - langpack-en...@firefox.mozilla.org
   English (South Africa) Language Pack - langpack-en...@firefox.mozilla.org
   Português Brasileiro Language Pack - langpack-pt...@firefox.mozilla.org
   Default - {972ce4c6-7e08-4474-a285-3208198ce6fd}
  DefaultProfilePlugins: Shockwave Flash - 
/usr/lib/flashplugin-installer/libflashplayer.so
  DefaultProfilePrefSources:
   prefs.js
   user.js
   [Profile]/extensions/inspec...@mozilla.org/defaults/preferences/inspector.js
  ForcedLayersAccel: False
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2016-05-16 (369 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MostRecentCrashID: bp-964d1e04-1a6d-4531-9dc1-65b032150721
  Profile1Extensions: extensions.sqlite corrupt or missing
  Profile1IncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
  Profile1Locales: extensions.sqlite corrupt or missing
  Profile1Plugins: iTunes Application Detector - 
/usr/lib/mozilla/plugins/librhythmbox-itms-detection-plugin.so
  Profile1PrefSources: prefs.js
  Profile1Themes: extensions.sqlite corrupt or missing
  Profiles:
   Profile0 (Default) - LastVersion=53.0.2/20170509205820 (In use)
   Profile1 - LastVersion=40.0.3/20150826185640 (Out of date)
  RunningIncompatibleAddons: True
  SourcePackage: firefox
  UpgradeStatus: Upgraded to yakkety on 2016-10-29 (203 days ago)
  dmi.bios.date: 10/08/2015
  dmi.bios.vendor: INSYDE Corp.
  dmi.bios.version: 1.20
  dmi.board.name: 06F4
  dmi.board.vendor: FF50
  dmi.board.version: Type2 - Board Version
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: OEM Chassis ManuFacturer
  dmi.chassis.version: OEM Chassis Version
  dmi.modalias: 
dmi:bvnINSYDECorp.:bvr1.20:bd10/08/2015:svnTOSHIBA:pnSATELLITEP50-C:pvrPSPUEE-00C008EP:rvnFF50:rn06F4:rvrType2-BoardVersion:cvnOEMChassisManuFacturer:ct10:cvrOEMChassisVersion:
  dmi.product.name: SATELLITE P50-C
  dmi.product.version: PSPUEE-00C008EP
  dmi.sys.vendor: TOSHIBA

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

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

[Desktop-packages] [Bug 1692330] Re: firefox hangs using 100% cpu

Posted this bug before, but this time I caught it really hanging up.
Maybe the report is more useful this time.

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

Title:
  firefox hangs using 100% cpu

Status in firefox package in Ubuntu:
  New

Bug description:
  This happens randomly, firefox just starts using 100% cpu and hangs.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: firefox 53.0.2+build1-0ubuntu0.16.10.2
  ProcVersionSignature: Ubuntu 4.8.0-52.55-generic 4.8.17
  Uname: Linux 4.8.0-52-generic x86_64
  AddonCompatCheckDisabled: False
  ApportVersion: 2.20.3-0ubuntu8.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   ferdez 4600 F...m pulseaudio
   /dev/snd/controlC0:  ferdez 4600 F pulseaudio
  BuildID: 20170509205820
  Channel: Unavailable
  CurrentDesktop: Unity
  Date: Sun May 21 16:08:41 2017
  DefaultProfileIncompatibleExtensions:
   Português Portugal Language Pack - langpack-pt...@firefox.mozilla.org
   English (GB) Language Pack - langpack-en...@firefox.mozilla.org
   English (South Africa) Language Pack - langpack-en...@firefox.mozilla.org
   Português Brasileiro Language Pack - langpack-pt...@firefox.mozilla.org
   Default - {972ce4c6-7e08-4474-a285-3208198ce6fd}
  DefaultProfilePlugins: Shockwave Flash - 
/usr/lib/flashplugin-installer/libflashplayer.so
  DefaultProfilePrefSources:
   prefs.js
   user.js
   [Profile]/extensions/inspec...@mozilla.org/defaults/preferences/inspector.js
  ForcedLayersAccel: False
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2016-05-16 (369 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MostRecentCrashID: bp-964d1e04-1a6d-4531-9dc1-65b032150721
  Profile1Extensions: extensions.sqlite corrupt or missing
  Profile1IncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
  Profile1Locales: extensions.sqlite corrupt or missing
  Profile1Plugins: iTunes Application Detector - 
/usr/lib/mozilla/plugins/librhythmbox-itms-detection-plugin.so
  Profile1PrefSources: prefs.js
  Profile1Themes: extensions.sqlite corrupt or missing
  Profiles:
   Profile0 (Default) - LastVersion=53.0.2/20170509205820 (In use)
   Profile1 - LastVersion=40.0.3/20150826185640 (Out of date)
  RunningIncompatibleAddons: True
  SourcePackage: firefox
  UpgradeStatus: Upgraded to yakkety on 2016-10-29 (203 days ago)
  dmi.bios.date: 10/08/2015
  dmi.bios.vendor: INSYDE Corp.
  dmi.bios.version: 1.20
  dmi.board.name: 06F4
  dmi.board.vendor: FF50
  dmi.board.version: Type2 - Board Version
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: OEM Chassis ManuFacturer
  dmi.chassis.version: OEM Chassis Version
  dmi.modalias: 
dmi:bvnINSYDECorp.:bvr1.20:bd10/08/2015:svnTOSHIBA:pnSATELLITEP50-C:pvrPSPUEE-00C008EP:rvnFF50:rn06F4:rvrType2-BoardVersion:cvnOEMChassisManuFacturer:ct10:cvrOEMChassisVersion:
  dmi.product.name: SATELLITE P50-C
  dmi.product.version: PSPUEE-00C008EP
  dmi.sys.vendor: TOSHIBA

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

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

[Desktop-packages] [Bug 1692330] [NEW] firefox hangs using 100% cpu

Public bug reported:

This happens randomly, firefox just starts using 100% cpu and hangs.

ProblemType: Bug
DistroRelease: Ubuntu 16.10
Package: firefox 53.0.2+build1-0ubuntu0.16.10.2
ProcVersionSignature: Ubuntu 4.8.0-52.55-generic 4.8.17
Uname: Linux 4.8.0-52-generic x86_64
AddonCompatCheckDisabled: False
ApportVersion: 2.20.3-0ubuntu8.2
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/pcmC0D0p:   ferdez 4600 F...m pulseaudio
 /dev/snd/controlC0:  ferdez 4600 F pulseaudio
BuildID: 20170509205820
Channel: Unavailable
CurrentDesktop: Unity
Date: Sun May 21 16:08:41 2017
DefaultProfileIncompatibleExtensions:
 Português Portugal Language Pack - langpack-pt...@firefox.mozilla.org
 English (GB) Language Pack - langpack-en...@firefox.mozilla.org
 English (South Africa) Language Pack - langpack-en...@firefox.mozilla.org
 Português Brasileiro Language Pack - langpack-pt...@firefox.mozilla.org
 Default - {972ce4c6-7e08-4474-a285-3208198ce6fd}
DefaultProfilePlugins: Shockwave Flash - 
/usr/lib/flashplugin-installer/libflashplayer.so
DefaultProfilePrefSources:
 prefs.js
 user.js
 [Profile]/extensions/inspec...@mozilla.org/defaults/preferences/inspector.js
ForcedLayersAccel: False
IfupdownConfig:
 # interfaces(5) file used by ifup(8) and ifdown(8)
 auto lo
 iface lo inet loopback
InstallationDate: Installed on 2016-05-16 (369 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
MostRecentCrashID: bp-964d1e04-1a6d-4531-9dc1-65b032150721
Profile1Extensions: extensions.sqlite corrupt or missing
Profile1IncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
Profile1Locales: extensions.sqlite corrupt or missing
Profile1Plugins: iTunes Application Detector - 
/usr/lib/mozilla/plugins/librhythmbox-itms-detection-plugin.so
Profile1PrefSources: prefs.js
Profile1Themes: extensions.sqlite corrupt or missing
Profiles:
 Profile0 (Default) - LastVersion=53.0.2/20170509205820 (In use)
 Profile1 - LastVersion=40.0.3/20150826185640 (Out of date)
RunningIncompatibleAddons: True
SourcePackage: firefox
UpgradeStatus: Upgraded to yakkety on 2016-10-29 (203 days ago)
dmi.bios.date: 10/08/2015
dmi.bios.vendor: INSYDE Corp.
dmi.bios.version: 1.20
dmi.board.name: 06F4
dmi.board.vendor: FF50
dmi.board.version: Type2 - Board Version
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: OEM Chassis ManuFacturer
dmi.chassis.version: OEM Chassis Version
dmi.modalias: 
dmi:bvnINSYDECorp.:bvr1.20:bd10/08/2015:svnTOSHIBA:pnSATELLITEP50-C:pvrPSPUEE-00C008EP:rvnFF50:rn06F4:rvrType2-BoardVersion:cvnOEMChassisManuFacturer:ct10:cvrOEMChassisVersion:
dmi.product.name: SATELLITE P50-C
dmi.product.version: PSPUEE-00C008EP
dmi.sys.vendor: TOSHIBA

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


** Tags: amd64 apport-bug yakkety

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

Title:
  firefox hangs using 100% cpu

Status in firefox package in Ubuntu:
  New

Bug description:
  This happens randomly, firefox just starts using 100% cpu and hangs.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: firefox 53.0.2+build1-0ubuntu0.16.10.2
  ProcVersionSignature: Ubuntu 4.8.0-52.55-generic 4.8.17
  Uname: Linux 4.8.0-52-generic x86_64
  AddonCompatCheckDisabled: False
  ApportVersion: 2.20.3-0ubuntu8.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   ferdez 4600 F...m pulseaudio
   /dev/snd/controlC0:  ferdez 4600 F pulseaudio
  BuildID: 20170509205820
  Channel: Unavailable
  CurrentDesktop: Unity
  Date: Sun May 21 16:08:41 2017
  DefaultProfileIncompatibleExtensions:
   Português Portugal Language Pack - langpack-pt...@firefox.mozilla.org
   English (GB) Language Pack - langpack-en...@firefox.mozilla.org
   English (South Africa) Language Pack - langpack-en...@firefox.mozilla.org
   Português Brasileiro Language Pack - langpack-pt...@firefox.mozilla.org
   Default - {972ce4c6-7e08-4474-a285-3208198ce6fd}
  DefaultProfilePlugins: Shockwave Flash - 
/usr/lib/flashplugin-installer/libflashplayer.so
  DefaultProfilePrefSources:
   prefs.js
   user.js
   [Profile]/extensions/inspec...@mozilla.org/defaults/preferences/inspector.js
  ForcedLayersAccel: False
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2016-05-16 (369 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MostRecentCrashID: bp-964d1e04-1a6d-4531-9dc1-65b032150721
  Profile1Extensions: extensions.sqlite corrupt or missing
  Profile1IncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
  Profile1Locales: extensions.sqlite corrupt or missing

[Desktop-packages] [Bug 1692298] [NEW] firefox hangs using 100% cpu