[Desktop-packages] [Bug 2060266] Re: gnome-session.service [unity-session] uses deprecated --builtin parameter

[Haw Loeung]

Confirmed the latest gnome-session fixes this.

| [hloeung@dharkan tmp]$ apt-cache policy unity-session gnome-session-bin
| unity-session:
|   Installed: 46.0-1ubuntu3
|   Candidate: 46.0-1ubuntu3
|   Version table:
|  *** 46.0-1ubuntu3 500
| 500 http://haw-test.archive.ubuntu.com/ubuntu noble/universe amd64 
Packages
| 100 /var/lib/dpkg/status
| gnome-session-bin:
|   Installed: 46.0-1ubuntu3
|   Candidate: 46.0-1ubuntu3
|   Version table:
|  *** 46.0-1ubuntu3 500
| 500 http://haw-test.archive.ubuntu.com/ubuntu noble/main amd64 
Packages
| 100 /var/lib/dpkg/status

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

Title:
  gnome-session.service [unity-session] uses deprecated --builtin
  parameter

Status in gnome-session package in Ubuntu:
  Fix Released

Bug description:
  Hi,

  `gnome-session.service` has the following:

  | [Service]
  | ExecStart=/bin/sh -exc '[ "$DESKTOP_SESSION" != "gnome-classic" ] || export 
| GNOME_SHELL_SESSION_MODE=classic; \
  | export GNOME_SESSION_XDG_SESSION_PATH=${XDG_SESSION_PATH}; \
  | [ "$DESKTOP_SESSION" = gnome-flashback-metacity ] && \
  | exec gnome-session --builtin --session=$DESKTOP_SESSION 
--disable-acceleration-check || \
  | exec gnome-session --builtin --session=$DESKTOP_SESSION'

  Unfortunately, the latest `gnome-session` no longer supports
  `--builtin`. This causes login failures, in particular for me, using
  Unity, I get logged back out from the unity greeter.

  | $ apt-cache policy gnome-session-bin
  | gnome-session-bin:
  |   Installed: 46.0-1ubuntu2
  |   Candidate: 46.0-1ubuntu2
  |   Version table:
  |  *** 46.0-1ubuntu2 500
  | 500 http://haw-test.archive.ubuntu.com/ubuntu noble/main amd64 
Packages
  | 100 /var/lib/dpkg/status
  |  45.0-1ubuntu1 500
  | 500 http://haw-test.archive.ubuntu.com/ubuntu noble-updates/main 
amd64 Packages

  | $ gnome-session --builtin
  |
  | ** (gnome-session-binary:5602): WARNING **: 15:35:22.156: Unknown option 
--builtin

  Removing `--builtin` from `/usr/lib/systemd/user/gnome-
  session.service` let's me log in.

  With that though, I was not able to input text in chromium (installed
  via the snap).

  Downgrading `gnome-session-bin`, `gnome-session-common`, and `unity-
  session` back to 45.0-1ubuntu1 restores things for me:

  | [hloeung@dharkan tmp]$ apt-cache policy gnome-session-bin
  | gnome-session-bin:
  |   Installed: 45.0-1ubuntu1
  |   Candidate: 46.0-1ubuntu2
  |   Version table:
  |  46.0-1ubuntu2 500
  | 500 http://haw-test.archive.ubuntu.com/ubuntu noble/main amd64 
Packages
  |  *** 45.0-1ubuntu1 500
  | 500 http://haw-test.archive.ubuntu.com/ubuntu noble-updates/main 
amd64 Packages
  | 100 /var/lib/dpkg/status
  | [hloeung@dharkan tmp]$ apt-cache policy gnome-session-common
  | gnome-session-common:
  |   Installed: 45.0-1ubuntu1
  |   Candidate: 46.0-1ubuntu2
  |   Version table:
  |  46.0-1ubuntu2 500
  | 500 http://haw-test.archive.ubuntu.com/ubuntu noble/main amd64 
Packages
  |  *** 45.0-1ubuntu1 500
  | 500 http://haw-test.archive.ubuntu.com/ubuntu noble-updates/main 
amd64 Packages
  | 100 /var/lib/dpkg/status
  | [hloeung@dharkan tmp]$ apt-cache policy unity-session
  | unity-session:
  |   Installed: 45.0-1ubuntu1
  |   Candidate: 46.0-1ubuntu2
  |   Version table:
  |  46.0-1ubuntu2 500
  | 500 http://haw-test.archive.ubuntu.com/ubuntu noble/universe amd64 
Packages
  |  *** 45.0-1ubuntu1 500
  | 500 http://haw-test.archive.ubuntu.com/ubuntu 
noble-updates/universe amd64 Packages
  | 100 /var/lib/dpkg/status

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


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

[Desktop-packages] [Bug 2060266] Re: gnome-session no longer supports --builtin

[Haw Loeung]

@vanvugt, it's `unity-session` shipping out
`/usr/lib/systemd/user/gnome-session.service` which is part of `gnome-
session`:

| $ dpkg-query -S /usr/lib/systemd/user/gnome-session.service
| unity-session: /usr/lib/systemd/user/gnome-session.service


$ chdist apt-get noble source unity-session
Reading package lists... Done
Picking 'gnome-session' as source package instead of 'unity-session'
NOTICE: 'gnome-session' packaging is maintained in the 'Git' version control 
system at:
https://salsa.debian.org/gnome-team/gnome-session.git -b ubuntu/master
Please use:
git clone https://salsa.debian.org/gnome-team/gnome-session.git -b ubuntu/master
to retrieve the latest (possibly unreleased) updates to the package.
Need to get 572 kB of source archives.
Get:1 http://azure.archive.ubuntu.com/ubuntu noble/main gnome-session 
46.0-1ubuntu2 (dsc) [3,067 B]
Get:2 http://azure.archive.ubuntu.com/ubuntu noble/main gnome-session 
46.0-1ubuntu2 (tar) [484 kB]
Get:3 http://azure.archive.ubuntu.com/ubuntu noble/main gnome-session 
46.0-1ubuntu2 (diff) [85.0 kB]
Fetched 572 kB in 3s (225 kB/s)
dpkg-source: info: extracting gnome-session in gnome-session-46.0
dpkg-source: info: unpacking gnome-session_46.0.orig.tar.xz
dpkg-source: info: unpacking gnome-session_46.0-1ubuntu2.debian.tar.xz
dpkg-source: info: using patch list from debian/patches/series
dpkg-source: info: applying 
debian/Revert-main-Remove-GNOME_DESKTOP_SESSION_ID-envvar.patch
dpkg-source: info: applying ubuntu/support_autostart_delay.patch
dpkg-source: info: applying ubuntu/ubuntu-sessions.patch
dpkg-source: info: applying ubuntu/remove_session_saving_from_gui.patch
dpkg-source: info: applying ubuntu/add_sessionmigration.patch
dpkg-source: info: applying ubuntu/dbus_request_shutdown.patch
dpkg-source: info: applying ubuntu/ignore_gsettings_region.patch
dpkg-source: info: applying revert_remove_gnome_session_properties.patch


[hloeung@dharkan gnome-session-46.0]$ grep builtin . -r --exclude-dir po
./debian/changelog:- Pass --builtin to gnome-session to fix broken login 
for Unity
./debian/changelog:+ debian/55gnome-session_gnomerc: Use shell builtins 
instead of external
./debian/data/gnome-session.service:exec gnome-session --builtin 
--session=$DESKTOP_SESSION --disable-acceleration-check || \
./debian/data/gnome-session.service:exec gnome-session --builtin 
--session=$DESKTOP_SESSION'

** Changed in: ubuntu
   Status: Incomplete => New

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

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

Title:
  gnome-session no longer supports --builtin

Status in gnome-session package in Ubuntu:
  New

Bug description:
  Hi,

  `gnome-session.service` has the following:

  | [Service]
  | ExecStart=/bin/sh -exc '[ "$DESKTOP_SESSION" != "gnome-classic" ] || export 
| GNOME_SHELL_SESSION_MODE=classic; \
  | export GNOME_SESSION_XDG_SESSION_PATH=${XDG_SESSION_PATH}; \
  | [ "$DESKTOP_SESSION" = gnome-flashback-metacity ] && \
  | exec gnome-session --builtin --session=$DESKTOP_SESSION 
--disable-acceleration-check || \
  | exec gnome-session --builtin --session=$DESKTOP_SESSION'

  Unfortunately, the latest `gnome-session` no longer supports
  `--builtin`. This causes login failures, in particular for me, using
  Unity, I get logged back out from the unity greeter.

  | $ apt-cache policy gnome-session-bin
  | gnome-session-bin:
  |   Installed: 46.0-1ubuntu2
  |   Candidate: 46.0-1ubuntu2
  |   Version table:
  |  *** 46.0-1ubuntu2 500
  | 500 http://haw-test.archive.ubuntu.com/ubuntu noble/main amd64 
Packages
  | 100 /var/lib/dpkg/status
  |  45.0-1ubuntu1 500
  | 500 http://haw-test.archive.ubuntu.com/ubuntu noble-updates/main 
amd64 Packages

  | $ gnome-session --builtin
  |
  | ** (gnome-session-binary:5602): WARNING **: 15:35:22.156: Unknown option 
--builtin

  Removing `--builtin` from `/usr/lib/systemd/user/gnome-
  session.service` let's me log in.

  With that though, I was not able to input text in chromium (installed
  via the snap).

  Downgrading `gnome-session-bin`, `gnome-session-common`, and `unity-
  session` back to 45.0-1ubuntu1 restores things for me:

  | [hloeung@dharkan tmp]$ apt-cache policy gnome-session-bin
  | gnome-session-bin:
  |   Installed: 45.0-1ubuntu1
  |   Candidate: 46.0-1ubuntu2
  |   Version table:
  |  46.0-1ubuntu2 500
  | 500 http://haw-test.archive.ubuntu.com/ubuntu noble/main amd64 
Packages
  |  *** 45.0-1ubuntu1 500
  | 500 http://haw-test.archive.ubuntu.com/ubuntu noble-updates/main 
amd64 Packages
  | 100 /var/lib/dpkg/status
  | [hloeung@dharkan tmp]$ apt-cache policy gnome-session-common
  | gnome-session-common:
  |   Installed: 45.0-1ubuntu1
  |   Candidate: 46.0-1ubuntu2
  |   Version table:
  |  46.0-1ubuntu2 500
  | 500 

[Desktop-packages] [Bug 2060266] [NEW] gnome-session no longer supports --builtin

[Haw Loeung]

Public bug reported:

Hi,

`gnome-session.service` has the following:

| [Service]
| ExecStart=/bin/sh -exc '[ "$DESKTOP_SESSION" != "gnome-classic" ] || export | 
GNOME_SHELL_SESSION_MODE=classic; \
| export GNOME_SESSION_XDG_SESSION_PATH=${XDG_SESSION_PATH}; \
| [ "$DESKTOP_SESSION" = gnome-flashback-metacity ] && \
| exec gnome-session --builtin --session=$DESKTOP_SESSION 
--disable-acceleration-check || \
| exec gnome-session --builtin --session=$DESKTOP_SESSION'

Unfortunately, the latest `gnome-session` no longer supports
`--builtin`. This causes login failures, in particular for me, using
Unity, I get logged back out from the unity greeter.

| $ apt-cache policy gnome-session-bin
| gnome-session-bin:
|   Installed: 46.0-1ubuntu2
|   Candidate: 46.0-1ubuntu2
|   Version table:
|  *** 46.0-1ubuntu2 500
| 500 http://haw-test.archive.ubuntu.com/ubuntu noble/main amd64 
Packages
| 100 /var/lib/dpkg/status
|  45.0-1ubuntu1 500
| 500 http://haw-test.archive.ubuntu.com/ubuntu noble-updates/main 
amd64 Packages

| $ gnome-session --builtin
|
| ** (gnome-session-binary:5602): WARNING **: 15:35:22.156: Unknown option 
--builtin

Removing `--builtin` from `/usr/lib/systemd/user/gnome-session.service`
let's me log in.

With that though, I was not able to input text in chromium (installed
via the snap).

Downgrading `gnome-session-bin`, `gnome-session-common`, and `unity-
session` back to 45.0-1ubuntu1 restores things for me:

| [hloeung@dharkan tmp]$ apt-cache policy gnome-session-bin
| gnome-session-bin:
|   Installed: 45.0-1ubuntu1
|   Candidate: 46.0-1ubuntu2
|   Version table:
|  46.0-1ubuntu2 500
| 500 http://haw-test.archive.ubuntu.com/ubuntu noble/main amd64 
Packages
|  *** 45.0-1ubuntu1 500
| 500 http://haw-test.archive.ubuntu.com/ubuntu noble-updates/main 
amd64 Packages
| 100 /var/lib/dpkg/status
| [hloeung@dharkan tmp]$ apt-cache policy gnome-session-common
| gnome-session-common:
|   Installed: 45.0-1ubuntu1
|   Candidate: 46.0-1ubuntu2
|   Version table:
|  46.0-1ubuntu2 500
| 500 http://haw-test.archive.ubuntu.com/ubuntu noble/main amd64 
Packages
|  *** 45.0-1ubuntu1 500
| 500 http://haw-test.archive.ubuntu.com/ubuntu noble-updates/main 
amd64 Packages
| 100 /var/lib/dpkg/status
| [hloeung@dharkan tmp]$ apt-cache policy unity-session
| unity-session:
|   Installed: 45.0-1ubuntu1
|   Candidate: 46.0-1ubuntu2
|   Version table:
|  46.0-1ubuntu2 500
| 500 http://haw-test.archive.ubuntu.com/ubuntu noble/universe amd64 
Packages
|  *** 45.0-1ubuntu1 500
| 500 http://haw-test.archive.ubuntu.com/ubuntu noble-updates/universe 
amd64 Packages
| 100 /var/lib/dpkg/status

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

** Description changed:

  Hi,
  
  `gnome-session.service` has the following:
  
  | [Service]
  | ExecStart=/bin/sh -exc '[ "$DESKTOP_SESSION" != "gnome-classic" ] || export 
| GNOME_SHELL_SESSION_MODE=classic; \
  | export GNOME_SESSION_XDG_SESSION_PATH=${XDG_SESSION_PATH}; \
  | [ "$DESKTOP_SESSION" = gnome-flashback-metacity ] && \
  | exec gnome-session --builtin --session=$DESKTOP_SESSION 
--disable-acceleration-check || \
  | exec gnome-session --builtin --session=$DESKTOP_SESSION'
  
  Unfortunately, the latest `gnome-session` no longer supports
  `--builtin`. This causes login failures, in particular for me, using
  Unity, I get logged back out from the unity greeter.
  
  | $ apt-cache policy gnome-session-bin
  | gnome-session-bin:
  |   Installed: 46.0-1ubuntu2
  |   Candidate: 46.0-1ubuntu2
  |   Version table:
  |  *** 46.0-1ubuntu2 500
  | 500 http://haw-test.archive.ubuntu.com/ubuntu noble/main amd64 
Packages
  | 100 /var/lib/dpkg/status
  |  45.0-1ubuntu1 500
  | 500 http://haw-test.archive.ubuntu.com/ubuntu noble-updates/main 
amd64 Packages
  
  | $ gnome-session --builtin
  |
  | ** (gnome-session-binary:5602): WARNING **: 15:35:22.156: Unknown option 
--builtin
+ 
+ Removing `--builtin` from `/usr/lib/systemd/user/gnome-session.service`
+ let's me log in.

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

Title:
  gnome-session no longer supports --builtin

Status in gnome-session package in Ubuntu:
  New

Bug description:
  Hi,

  `gnome-session.service` has the following:

  | [Service]
  | ExecStart=/bin/sh -exc '[ "$DESKTOP_SESSION" != "gnome-classic" ] || export 
| GNOME_SHELL_SESSION_MODE=classic; \
  | export GNOME_SESSION_XDG_SESSION_PATH=${XDG_SESSION_PATH}; \
  | [ "$DESKTOP_SESSION" = gnome-flashback-metacity ] && \
  | exec gnome-session --builtin --session=$DESKTOP_SESSION 
--disable-acceleration-check || \
  | exec gnome-session --builtin --session=$DESKTOP_SESSION'

  Unfortunately, the 

[Desktop-packages] [Bug 2060266] Re: gnome-session no longer supports --builtin

[Haw Loeung]

** Tags added: noble

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

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

Title:
  gnome-session no longer supports --builtin

Status in gnome-session package in Ubuntu:
  New
Status in gnome-session source package in Noble:
  New

Bug description:
  Hi,

  `gnome-session.service` has the following:

  | [Service]
  | ExecStart=/bin/sh -exc '[ "$DESKTOP_SESSION" != "gnome-classic" ] || export 
| GNOME_SHELL_SESSION_MODE=classic; \
  | export GNOME_SESSION_XDG_SESSION_PATH=${XDG_SESSION_PATH}; \
  | [ "$DESKTOP_SESSION" = gnome-flashback-metacity ] && \
  | exec gnome-session --builtin --session=$DESKTOP_SESSION 
--disable-acceleration-check || \
  | exec gnome-session --builtin --session=$DESKTOP_SESSION'

  Unfortunately, the latest `gnome-session` no longer supports
  `--builtin`. This causes login failures, in particular for me, using
  Unity, I get logged back out from the unity greeter.

  | $ apt-cache policy gnome-session-bin
  | gnome-session-bin:
  |   Installed: 46.0-1ubuntu2
  |   Candidate: 46.0-1ubuntu2
  |   Version table:
  |  *** 46.0-1ubuntu2 500
  | 500 http://haw-test.archive.ubuntu.com/ubuntu noble/main amd64 
Packages
  | 100 /var/lib/dpkg/status
  |  45.0-1ubuntu1 500
  | 500 http://haw-test.archive.ubuntu.com/ubuntu noble-updates/main 
amd64 Packages

  | $ gnome-session --builtin
  |
  | ** (gnome-session-binary:5602): WARNING **: 15:35:22.156: Unknown option 
--builtin

  Removing `--builtin` from `/usr/lib/systemd/user/gnome-
  session.service` let's me log in.

  With that though, I was not able to input text in chromium (installed
  via the snap).

  Downgrading `gnome-session-bin`, `gnome-session-common`, and `unity-
  session` back to 45.0-1ubuntu1 restores things for me:

  | [hloeung@dharkan tmp]$ apt-cache policy gnome-session-bin
  | gnome-session-bin:
  |   Installed: 45.0-1ubuntu1
  |   Candidate: 46.0-1ubuntu2
  |   Version table:
  |  46.0-1ubuntu2 500
  | 500 http://haw-test.archive.ubuntu.com/ubuntu noble/main amd64 
Packages
  |  *** 45.0-1ubuntu1 500
  | 500 http://haw-test.archive.ubuntu.com/ubuntu noble-updates/main 
amd64 Packages
  | 100 /var/lib/dpkg/status
  | [hloeung@dharkan tmp]$ apt-cache policy gnome-session-common
  | gnome-session-common:
  |   Installed: 45.0-1ubuntu1
  |   Candidate: 46.0-1ubuntu2
  |   Version table:
  |  46.0-1ubuntu2 500
  | 500 http://haw-test.archive.ubuntu.com/ubuntu noble/main amd64 
Packages
  |  *** 45.0-1ubuntu1 500
  | 500 http://haw-test.archive.ubuntu.com/ubuntu noble-updates/main 
amd64 Packages
  | 100 /var/lib/dpkg/status
  | [hloeung@dharkan tmp]$ apt-cache policy unity-session
  | unity-session:
  |   Installed: 45.0-1ubuntu1
  |   Candidate: 46.0-1ubuntu2
  |   Version table:
  |  46.0-1ubuntu2 500
  | 500 http://haw-test.archive.ubuntu.com/ubuntu noble/universe amd64 
Packages
  |  *** 45.0-1ubuntu1 500
  | 500 http://haw-test.archive.ubuntu.com/ubuntu 
noble-updates/universe amd64 Packages
  | 100 /var/lib/dpkg/status

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


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

[Desktop-packages] [Bug 2060266] Re: gnome-session no longer supports --builtin

[Haw Loeung]

** Description changed:

  Hi,
  
  `gnome-session.service` has the following:
  
  | [Service]
  | ExecStart=/bin/sh -exc '[ "$DESKTOP_SESSION" != "gnome-classic" ] || export 
| GNOME_SHELL_SESSION_MODE=classic; \
  | export GNOME_SESSION_XDG_SESSION_PATH=${XDG_SESSION_PATH}; \
  | [ "$DESKTOP_SESSION" = gnome-flashback-metacity ] && \
  | exec gnome-session --builtin --session=$DESKTOP_SESSION 
--disable-acceleration-check || \
  | exec gnome-session --builtin --session=$DESKTOP_SESSION'
  
  Unfortunately, the latest `gnome-session` no longer supports
  `--builtin`. This causes login failures, in particular for me, using
  Unity, I get logged back out from the unity greeter.
  
  | $ apt-cache policy gnome-session-bin
  | gnome-session-bin:
  |   Installed: 46.0-1ubuntu2
  |   Candidate: 46.0-1ubuntu2
  |   Version table:
  |  *** 46.0-1ubuntu2 500
  | 500 http://haw-test.archive.ubuntu.com/ubuntu noble/main amd64 
Packages
  | 100 /var/lib/dpkg/status
  |  45.0-1ubuntu1 500
  | 500 http://haw-test.archive.ubuntu.com/ubuntu noble-updates/main 
amd64 Packages
  
  | $ gnome-session --builtin
  |
  | ** (gnome-session-binary:5602): WARNING **: 15:35:22.156: Unknown option 
--builtin
  
  Removing `--builtin` from `/usr/lib/systemd/user/gnome-session.service`
  let's me log in.
+ 
+ With that though, I was not able to input text in chromium (installed
+ via the snap).
+ 
+ Downgrading `gnome-session-bin`, `gnome-session-common`, and `unity-
+ session` back to 45.0-1ubuntu1 restores things for me:
+ 
+ | [hloeung@dharkan tmp]$ apt-cache policy gnome-session-bin
+ | gnome-session-bin:
+ |   Installed: 45.0-1ubuntu1
+ |   Candidate: 46.0-1ubuntu2
+ |   Version table:
+ |  46.0-1ubuntu2 500
+ | 500 http://haw-test.archive.ubuntu.com/ubuntu noble/main amd64 
Packages
+ |  *** 45.0-1ubuntu1 500
+ | 500 http://haw-test.archive.ubuntu.com/ubuntu noble-updates/main 
amd64 Packages
+ | 100 /var/lib/dpkg/status
+ | [hloeung@dharkan tmp]$ apt-cache policy gnome-session-common
+ | gnome-session-common:
+ |   Installed: 45.0-1ubuntu1
+ |   Candidate: 46.0-1ubuntu2
+ |   Version table:
+ |  46.0-1ubuntu2 500
+ | 500 http://haw-test.archive.ubuntu.com/ubuntu noble/main amd64 
Packages
+ |  *** 45.0-1ubuntu1 500
+ | 500 http://haw-test.archive.ubuntu.com/ubuntu noble-updates/main 
amd64 Packages
+ | 100 /var/lib/dpkg/status
+ | [hloeung@dharkan tmp]$ apt-cache policy unity-session
+ | unity-session:
+ |   Installed: 45.0-1ubuntu1
+ |   Candidate: 46.0-1ubuntu2
+ |   Version table:
+ |  46.0-1ubuntu2 500
+ | 500 http://haw-test.archive.ubuntu.com/ubuntu noble/universe amd64 
Packages
+ |  *** 45.0-1ubuntu1 500
+ | 500 http://haw-test.archive.ubuntu.com/ubuntu 
noble-updates/universe amd64 Packages
+ | 100 /var/lib/dpkg/status

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

Title:
  gnome-session no longer supports --builtin

Status in gnome-session package in Ubuntu:
  New

Bug description:
  Hi,

  `gnome-session.service` has the following:

  | [Service]
  | ExecStart=/bin/sh -exc '[ "$DESKTOP_SESSION" != "gnome-classic" ] || export 
| GNOME_SHELL_SESSION_MODE=classic; \
  | export GNOME_SESSION_XDG_SESSION_PATH=${XDG_SESSION_PATH}; \
  | [ "$DESKTOP_SESSION" = gnome-flashback-metacity ] && \
  | exec gnome-session --builtin --session=$DESKTOP_SESSION 
--disable-acceleration-check || \
  | exec gnome-session --builtin --session=$DESKTOP_SESSION'

  Unfortunately, the latest `gnome-session` no longer supports
  `--builtin`. This causes login failures, in particular for me, using
  Unity, I get logged back out from the unity greeter.

  | $ apt-cache policy gnome-session-bin
  | gnome-session-bin:
  |   Installed: 46.0-1ubuntu2
  |   Candidate: 46.0-1ubuntu2
  |   Version table:
  |  *** 46.0-1ubuntu2 500
  | 500 http://haw-test.archive.ubuntu.com/ubuntu noble/main amd64 
Packages
  | 100 /var/lib/dpkg/status
  |  45.0-1ubuntu1 500
  | 500 http://haw-test.archive.ubuntu.com/ubuntu noble-updates/main 
amd64 Packages

  | $ gnome-session --builtin
  |
  | ** (gnome-session-binary:5602): WARNING **: 15:35:22.156: Unknown option 
--builtin

  Removing `--builtin` from `/usr/lib/systemd/user/gnome-
  session.service` let's me log in.

  With that though, I was not able to input text in chromium (installed
  via the snap).

  Downgrading `gnome-session-bin`, `gnome-session-common`, and `unity-
  session` back to 45.0-1ubuntu1 restores things for me:

  | [hloeung@dharkan tmp]$ apt-cache policy gnome-session-bin
  | gnome-session-bin:
  |   Installed: 45.0-1ubuntu1
  |   Candidate: 46.0-1ubuntu2
  |   Version table:
  |  46.0-1ubuntu2 500
  | 500 http://haw-test.archive.ubuntu.com/ubuntu noble/main amd64 

[Desktop-packages] [Bug 2058881] Re: [snap] Allow chromium snap to access Pressure Stall Information (PSI)

[Haw Loeung]

I've not observed any problems or hindrance as a result of these
denials, no.

Just more noise and thought maybe Chromium was going to use the pressure
stall information for something useful like for the selection of which
tabs/process to kill off when the system is experiencing pressure in
either CPU, I/O, and/or memory.

But all good if it does not and it does not plan to.

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

Title:
  [snap] Allow chromium snap to access Pressure Stall Information (PSI)

Status in chromium-browser package in Ubuntu:
  Confirmed

Bug description:
  Hi,

  Currently seeing this:

  | Mar 25 16:12:23 dharkan.local kernel: audit: type=1400 
audit(1711343543.539:657): apparmor="DENIED" operation="open" class="file" 
profile="snap.chromium.chromium" name="/proc/pressure/cpu" pid=63335 
comm="ThreadPoolForeg" requested_mask="r" denied_mask="r" fsuid=3134 ouid=0
  | Mar 25 16:12:23 dharkan.local kernel: audit: type=1400 
audit(1711343543.539:658): apparmor="DENIED" operation="open" class="file" 
profile="snap.chromium.chromium" name="/proc/pressure/io" pid=63335 
comm="ThreadPoolForeg" requested_mask="r" denied_mask="r" fsuid=3134 ouid=0
  | Mar 25 16:12:23 dharkan.local kernel: audit: type=1400 
audit(1711343543.539:659): apparmor="DENIED" operation="open" class="file" 
profile="snap.chromium.chromium" name="/proc/pressure/memory" pid=63335 
comm="ThreadPoolForeg" requested_mask="r" denied_mask="r" fsuid=3134 ouid>

  It seems the AppAmor profile should be updated to allow Chromium
  access to the pressure stall information for it to monitor and manage
  it's processes?

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


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

[Desktop-packages] [Bug 2058881] Re: [snap] Allow chromium snap to access Pressure Stall Information (PSI)

[Haw Loeung]

It's used here:

|
https://github.com/chromium/chromium/blob/123.0.6312.58/chrome/browser/metrics/pressure/pressure_metrics_reporter.cc#L19

>From this commit:

|
https://github.com/chromium/chromium/commit/dace5562b1d56bf2d2e5b2de6f4518c44844be9f

References this bug:

| https://issues.chromium.org/issues/40256157

** Bug watch added: issues.chromium.org/issues #40256157
   https://issues.chromium.org/issues/40256157

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

Title:
  [snap] Allow chromium snap to access Pressure Stall Information (PSI)

Status in chromium-browser package in Ubuntu:
  Confirmed

Bug description:
  Hi,

  Currently seeing this:

  | Mar 25 16:12:23 dharkan.local kernel: audit: type=1400 
audit(1711343543.539:657): apparmor="DENIED" operation="open" class="file" 
profile="snap.chromium.chromium" name="/proc/pressure/cpu" pid=63335 
comm="ThreadPoolForeg" requested_mask="r" denied_mask="r" fsuid=3134 ouid=0
  | Mar 25 16:12:23 dharkan.local kernel: audit: type=1400 
audit(1711343543.539:658): apparmor="DENIED" operation="open" class="file" 
profile="snap.chromium.chromium" name="/proc/pressure/io" pid=63335 
comm="ThreadPoolForeg" requested_mask="r" denied_mask="r" fsuid=3134 ouid=0
  | Mar 25 16:12:23 dharkan.local kernel: audit: type=1400 
audit(1711343543.539:659): apparmor="DENIED" operation="open" class="file" 
profile="snap.chromium.chromium" name="/proc/pressure/memory" pid=63335 
comm="ThreadPoolForeg" requested_mask="r" denied_mask="r" fsuid=3134 ouid>

  It seems the AppAmor profile should be updated to allow Chromium
  access to the pressure stall information for it to monitor and manage
  it's processes?

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


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

[Desktop-packages] [Bug 2058881] Re: [snap] Allow chromium snap to access Pressure Stall Information (PSI)

[Haw Loeung]

Sorry, I should have mentioned the version. I'm using the chromium from
the candidate channel:

| $ snap info chromium | grep installed
| installed:  123.0.6312.58 (2795) 168MB -

Seems to be happening every 10 mins.

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

Title:
  [snap] Allow chromium snap to access Pressure Stall Information (PSI)

Status in chromium-browser package in Ubuntu:
  Confirmed

Bug description:
  Hi,

  Currently seeing this:

  | Mar 25 16:12:23 dharkan.local kernel: audit: type=1400 
audit(1711343543.539:657): apparmor="DENIED" operation="open" class="file" 
profile="snap.chromium.chromium" name="/proc/pressure/cpu" pid=63335 
comm="ThreadPoolForeg" requested_mask="r" denied_mask="r" fsuid=3134 ouid=0
  | Mar 25 16:12:23 dharkan.local kernel: audit: type=1400 
audit(1711343543.539:658): apparmor="DENIED" operation="open" class="file" 
profile="snap.chromium.chromium" name="/proc/pressure/io" pid=63335 
comm="ThreadPoolForeg" requested_mask="r" denied_mask="r" fsuid=3134 ouid=0
  | Mar 25 16:12:23 dharkan.local kernel: audit: type=1400 
audit(1711343543.539:659): apparmor="DENIED" operation="open" class="file" 
profile="snap.chromium.chromium" name="/proc/pressure/memory" pid=63335 
comm="ThreadPoolForeg" requested_mask="r" denied_mask="r" fsuid=3134 ouid>

  It seems the AppAmor profile should be updated to allow Chromium
  access to the pressure stall information for it to monitor and manage
  it's processes?

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


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

[Desktop-packages] [Bug 2058881] [NEW] [snap] Allow chromium snap to access Pressure Stall Information (PSI)

[Haw Loeung]

Public bug reported:

Hi,

Currently seeing this:

| Mar 25 16:12:23 dharkan.local kernel: audit: type=1400 
audit(1711343543.539:657): apparmor="DENIED" operation="open" class="file" 
profile="snap.chromium.chromium" name="/proc/pressure/cpu" pid=63335 
comm="ThreadPoolForeg" requested_mask="r" denied_mask="r" fsuid=3134 ouid=0
| Mar 25 16:12:23 dharkan.local kernel: audit: type=1400 
audit(1711343543.539:658): apparmor="DENIED" operation="open" class="file" 
profile="snap.chromium.chromium" name="/proc/pressure/io" pid=63335 
comm="ThreadPoolForeg" requested_mask="r" denied_mask="r" fsuid=3134 ouid=0
| Mar 25 16:12:23 dharkan.local kernel: audit: type=1400 
audit(1711343543.539:659): apparmor="DENIED" operation="open" class="file" 
profile="snap.chromium.chromium" name="/proc/pressure/memory" pid=63335 
comm="ThreadPoolForeg" requested_mask="r" denied_mask="r" fsuid=3134 ouid>

It seems the AppAmor profile should be updated to allow Chromium access
to the pressure stall information for it to monitor and manage it's
processes?

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

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

Title:
  [snap] Allow chromium snap to access Pressure Stall Information (PSI)

Status in chromium-browser package in Ubuntu:
  New

Bug description:
  Hi,

  Currently seeing this:

  | Mar 25 16:12:23 dharkan.local kernel: audit: type=1400 
audit(1711343543.539:657): apparmor="DENIED" operation="open" class="file" 
profile="snap.chromium.chromium" name="/proc/pressure/cpu" pid=63335 
comm="ThreadPoolForeg" requested_mask="r" denied_mask="r" fsuid=3134 ouid=0
  | Mar 25 16:12:23 dharkan.local kernel: audit: type=1400 
audit(1711343543.539:658): apparmor="DENIED" operation="open" class="file" 
profile="snap.chromium.chromium" name="/proc/pressure/io" pid=63335 
comm="ThreadPoolForeg" requested_mask="r" denied_mask="r" fsuid=3134 ouid=0
  | Mar 25 16:12:23 dharkan.local kernel: audit: type=1400 
audit(1711343543.539:659): apparmor="DENIED" operation="open" class="file" 
profile="snap.chromium.chromium" name="/proc/pressure/memory" pid=63335 
comm="ThreadPoolForeg" requested_mask="r" denied_mask="r" fsuid=3134 ouid>

  It seems the AppAmor profile should be updated to allow Chromium
  access to the pressure stall information for it to monitor and manage
  it's processes?

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


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

[Desktop-packages] [Bug 2054924] Re: color emoji are broken with fontconfig 2.15

[Haw Loeung]

** Changed in: fontconfig (Ubuntu)
   Status: Triaged => Confirmed

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

Title:
  color emoji are broken with fontconfig 2.15

Status in Fontconfig:
  Fix Released
Status in fontconfig package in Ubuntu:
  Confirmed
Status in fonts-noto-color-emoji package in Ubuntu:
  Triaged
Status in fontconfig package in Debian:
  Confirmed

Bug description:
  The Noto Color Emoji font is no longer used to show emoji. Many emoji
  no longer show and the few that do are not in color.

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


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

[Desktop-packages] [Bug 2054924] Re: color emoji are broken with fontconfig 2.15

[Haw Loeung]

The workaround detailed upstream works for me - removing
/etc/fonts/conf.d/70-no-bitmaps.conf and re-generating your fonts cache.

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

Title:
  color emoji are broken with fontconfig 2.15

Status in Fontconfig:
  Fix Released
Status in fontconfig package in Ubuntu:
  Triaged
Status in fonts-noto-color-emoji package in Ubuntu:
  Triaged
Status in fontconfig package in Debian:
  New

Bug description:
  The Noto Color Emoji font is no longer used to show emoji. Many emoji
  no longer show and the few that do are not in color.

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


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

[Desktop-packages] [Bug 1831483] Re: metrics on pushed routes not applied

[Haw Loeung]

Any updates on this? We're still getting reports of issues from users
where we have two VPN endpoints each pushing routes with different
metrics for preferred routes / path.

We've had to work around this with smaller prefixes.

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

Title:
  metrics on pushed routes not applied

Status in NetworkManager-OpenVPN:
  Expired
Status in network-manager-openvpn package in Ubuntu:
  Triaged

Bug description:
  We have a couple of VPN endpoints located in different places.  These
  each provide access to a bunch of things located in both places.  We
  decided that it would be a good idea to let people connect to both
  endpoints so that by adjusting the metrics on the pushed routes (we
  used 500 and 1000) our users would always use the shortest available
  path.

  This works great with vanilla openvpn, but when using network-manager-
  openvpn, the metrics are lost and instead "50" is used, which means
  that only one gateway is used.  Ideally network-manager-openvpn would
  use the supplied metrics so that traffic is routed as intended.

  This seems to affect network-manager-openvpn in releases of Ubuntu up
  to 18.04 LTS, and possibly beyond.

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


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

[Desktop-packages] [Bug 583994] Re: Consider replacing ntpdate calls by 'ntpd -g'

[Haw Loeung]

** Changed in: ntp (Debian)
   Importance: Unknown => Low

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

Title:
  Consider replacing ntpdate calls by 'ntpd -g'

Status in NTP:
  Invalid
Status in ntp package in Ubuntu:
  Invalid
Status in ubuntu-meta package in Ubuntu:
  Fix Released
Status in ntp package in Debian:
  New

Bug description:
  Binary package hint: ntp

  Given that 'ntpdate' is being obsoleted upstream [1], we should
  replace 'ntpdate' usage by:

   * ntpd -qg (if we really want to set the time and exit), or
   * ntpd-g (if we want to keep ntpd running)

  the '-q' option will set the clock once, and exit; the 'g' allows for
  large corrections to the clock, like what is done by 'ntpdate'.

  
  [1] http://www.eecis.udel.edu/~mills/ntp/html/ntpdate.html

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

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

[Desktop-packages] [Bug 1222602] Re: [regression] [gen3] Mesa 9.2 makes Unity unusable on Atom class hardware and 943/945 graphics controllers

[Haw Loeung]

** Changed in: mesa
   Importance: Unknown => Undecided

** Changed in: mesa
 Remote watch: gitlab.freedesktop.org/mesa/mesa/issues #727 => None

** Changed in: mesa
   Status: New => Won't Fix

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

Title:
  [regression] [gen3] Mesa 9.2 makes Unity unusable on Atom class
  hardware and 943/945 graphics controllers

Status in Mesa:
  Won't Fix
Status in Nux:
  Fix Released
Status in Release Notes for Ubuntu:
  Invalid
Status in mesa package in Ubuntu:
  Fix Released
Status in nux package in Ubuntu:
  Fix Released
Status in unity package in Ubuntu:
  Invalid

Bug description:
  After the upgrade to Mesa 9.2.0 unity is barely usable.
  Dash, Alt+Tab switcher and Alt+F2 command line shows in more than 1 minute, 
using 100% cpu.

  A downgrade to mesa 9.1.6-2ubuntu2 restores full performance.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: libgl1-mesa-glx 9.2-1ubuntu1
  ProcVersionSignature: Ubuntu 3.11.0-5.11-generic 3.11.0
  Uname: Linux 3.11.0-5-generic i686
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.12.1-0ubuntu3
  Architecture: i386
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Mon Sep  9 01:51:45 2013
  DistUpgraded: 2013-09-08 20:36:47,811 DEBUG enabling apt cron job
  DistroCodename: saucy
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Mobile 945GSE Express Integrated Graphics Controller 
[8086:27ae] (rev 03) (prog-if 00 [VGA controller])
 Subsystem: Micro-Star International Co., Ltd. Device [1462:0110]
 Subsystem: Micro-Star International Co., Ltd. Device [1462:0110]
  InstallationDate: Installed on 2013-09-07 (1 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release i386 (20130424)
  MachineType: MICRO-STAR INTERNATIONAL CO., LTD U90/U100
  MarkForUpload: True
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=it_IT.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-5-generic 
root=UUID=674329c8-d0a6-4954-89c0-72821cfa0ba8 ro quiet splash vt.handoff=7
  SourcePackage: mesa
  UpgradeStatus: Upgraded to saucy on 2013-09-08 (0 days ago)
  dmi.bios.date: 12/01/2009
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 4.6.3
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: U90/U100
  dmi.board.vendor: MICRO-STAR INTERNATIONAL CO., LTD
  dmi.board.version: Ver.001
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 10
  dmi.chassis.vendor: MICRO-STAR INTERNATIONAL CO., LTD
  dmi.chassis.version: Ver.001
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr4.6.3:bd12/01/2009:svnMICRO-STARINTERNATIONALCO.,LTD:pnU90/U100:pvrVer.001:rvnMICRO-STARINTERNATIONALCO.,LTD:rnU90/U100:rvrVer.001:cvnMICRO-STARINTERNATIONALCO.,LTD:ct10:cvrVer.001:
  dmi.product.name: U90/U100
  dmi.product.version: Ver.001
  dmi.sys.vendor: MICRO-STAR INTERNATIONAL CO., LTD
  version.compiz: compiz 1:0.9.10+13.10.20130828.2-0ubuntu1
  version.libdrm2: libdrm2 2.4.46-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 9.2-1ubuntu1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 9.2-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.14.2.901-2ubuntu4
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu3.1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.2.0-0ubuntu6
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.21.14-4ubuntu3
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.9-2ubuntu1
  xserver.bootTime: Mon Sep  9 01:46:55 2013
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id1001 
   vendor HSD
  xserver.version: 2:1.14.2.901-2ubuntu4

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

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

[Desktop-packages] [Bug 1300215] Re: Failed to open VDPAU backend libvdpau_i965.so: cannot open shared object file: No such file or directory

[Haw Loeung]

** Changed in: libvdpau (Debian)
   Importance: Unknown => Undecided

** Changed in: libvdpau (Debian)
 Remote watch: Debian Bug tracker #617940 => None

** Changed in: libvdpau (Debian)
   Importance: Undecided => Medium

** Changed in: libvdpau (Debian)
   Status: New => Confirmed

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

Title:
  Failed to open VDPAU backend libvdpau_i965.so: cannot open shared
  object file: No such file or directory

Status in libvdpau package in Ubuntu:
  Triaged
Status in libvdpau-va-gl package in Ubuntu:
  Confirmed
Status in libvdpau package in Debian:
  Confirmed

Bug description:
  This has been bothering me at least since precise (although there the
  missing link went to libvdpau_nvidia.so which was all the more
  mysterious since I do not own NVIDIA hardware).  In numerous cases do
  I get a warning that libvdpau_i965.so is being tried to be accessed
  but it fails.  I also can't find that file anywhere on my system or in
  the Ubuntu repository.  I tried poking around with ldd to find out
  where the call to that lib comes from but so far unsuccessful.

  $ vdpauinfo
  display: :0   screen: 0
  Failed to open VDPAU backend libvdpau_i965.so: cannot open shared object 
file: No such file or directory
  Error creating VDPAU device: 1

  libvdpau1:i386 is version 0.7-1 and vdpauinfo is 0.1-1

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

-- 
Mailing list: https://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 1616650] Re: snap refresh while command is running may cause issues

[Haw Loeung]

On Mon, Apr 06, 2020 at 06:04:27PM -, Steve Langasek wrote:
> On Mon, Apr 06, 2020 at 04:11:03PM -, Olivier Tilloy wrote:
> > > Why is the chromium snap using per-version state directories? I think
> > > fixing that would be much more important in terms of usability.
>
> > That's because the file format for the profile directory can change with
> > new versions, and is not guaranteed to be backward-compatible. Reverting
> > to an old revision shouldn't leave users with an unusable profile
> > directory.
>
> As a user, that is far less important to me than the fact that *every single
> time* there is a snap refresh, Google Meet stops working, I have to restart
> Chromium, it reports that Chromium did not shut down cleanly, and part of my
> session state has been lost with no chance to preserve it.
>
> I think the state should all be moved to the common dir until you have a way
> to handle the rollback case without making the *upgrade* case terrible.

+1 to having the state moved into a common directory.

Does the file format for the profile directory change between minor
releases? Even if so, it isn't any different to users using the .deb
and reverting or downgrading. Google Chrome users download in either
.deb or .rpm.

Thinking more about it, experimental.refresh-app-awareness, if
configurable, will likely just force users to disable automatatic
refreshes completely. Which means no updates for other snaps
installed.

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

Title:
  snap refresh while command is running may cause issues

Status in snapd:
  In Progress
Status in chromium-browser package in Ubuntu:
  Confirmed

Bug description:
  In testing a desktop snap that saves state in $HOME on close, I
  noticed that if I snap refresh the snap while the command is running
  that it will try to save its state to the previous snap version's data
  directory. For the snap I was testing (a browser), this resulted in a
  very poor user experience (the browser on restart complained about an
  improper shutdown).

  What is happening is that:
  1. on launch the snap's HOME is set to SNAP_USER_DATA, which is something 
like /home/user/snap/foo/x1. The security policy correctly allows writes to 
SNAP_USER_DATA
  2. on snap refresh to 'x2', the security policy for the snap is updated for 
the running process such that /home/user/snap/foo/x1 is readonly and 
/home/user/snap/foo/x2 is read/write
  3. the command in '1's environment is not changed and HOME (as well as 
SNAP_USER_DATA and SNAP_DATA) are all still using 'x1' in the path
  4. the command tries to shutdown gracefully and save state to the 'x1' HOME 
and security policy blocks it

  Snappy's design for rollbacks relies on the previous SNAP_DATA and
  SNAP_USER_DATA directories not being writable and IMHO we should not
  change the policy to make other snap version's data dirs writable.

  The design of the snappy state engine ensures (among other things)
  that there is only ever one security policy in place for the snap. In
  snappy 15.04 this problem was (intentionally) avoided because we used
  snap security policy that was versioned such that the new policy would
  not apply until the next app invocation.

  Gustavo and Zygmunt, you both advocated strongly for only one version
  of the policy on disk and loaded in the kernel and I recall bringing
  up this type of bug as a counter-argument, and if IIRC for daemons we
  said that snapd could simply restart them (makes perfect sense). Have
  you thought of the mechanism for restarting non-daemons?

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

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

[Desktop-packages] [Bug 1616650] Re: snap refresh while command is running may cause issues

[Haw Loeung]

Some options:

- add option to disable automated snap refreshes.

- allow configuring the forced refresh of 7 days.

- have a channel for chromium that updates less frequently.

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

Title:
  snap refresh while command is running may cause issues

Status in snapd:
  In Progress
Status in chromium-browser package in Ubuntu:
  New

Bug description:
  In testing a desktop snap that saves state in $HOME on close, I
  noticed that if I snap refresh the snap while the command is running
  that it will try to save its state to the previous snap version's data
  directory. For the snap I was testing (a browser), this resulted in a
  very poor user experience (the browser on restart complained about an
  improper shutdown).

  What is happening is that:
  1. on launch the snap's HOME is set to SNAP_USER_DATA, which is something 
like /home/user/snap/foo/x1. The security policy correctly allows writes to 
SNAP_USER_DATA
  2. on snap refresh to 'x2', the security policy for the snap is updated for 
the running process such that /home/user/snap/foo/x1 is readonly and 
/home/user/snap/foo/x2 is read/write
  3. the command in '1's environment is not changed and HOME (as well as 
SNAP_USER_DATA and SNAP_DATA) are all still using 'x1' in the path
  4. the command tries to shutdown gracefully and save state to the 'x1' HOME 
and security policy blocks it

  Snappy's design for rollbacks relies on the previous SNAP_DATA and
  SNAP_USER_DATA directories not being writable and IMHO we should not
  change the policy to make other snap version's data dirs writable.

  The design of the snappy state engine ensures (among other things)
  that there is only ever one security policy in place for the snap. In
  snappy 15.04 this problem was (intentionally) avoided because we used
  snap security policy that was versioned such that the new policy would
  not apply until the next app invocation.

  Gustavo and Zygmunt, you both advocated strongly for only one version
  of the policy on disk and loaded in the kernel and I recall bringing
  up this type of bug as a counter-argument, and if IIRC for daemons we
  said that snapd could simply restart them (makes perfect sense). Have
  you thought of the mechanism for restarting non-daemons?

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

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

[Desktop-packages] [Bug 1862865] Re: i915 0000:00:02.0: Resetting rcs0 for stuck wait on rcs0

[Haw Loeung]

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

Duplicate of LP:1861395

Per LP:1861395 both 5.4.0-17 (from the Kernel Team's Unstable PPA) and
5.4.0-18 (from -proposed) seems to fixes it for me.

** This bug has been marked a duplicate of bug 1861395
   system hang: i915 Resetting rcs0 for hang on rcs0

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

Title:
  i915 :00:02.0: Resetting rcs0 for stuck wait on rcs0

Status in linux package in Ubuntu:
  Confirmed
Status in mesa package in Ubuntu:
  Invalid
Status in linux source package in Focal:
  Confirmed
Status in mesa source package in Focal:
  Invalid

Bug description:
  Hi,

  Every now and again, my session locks up with the following logged:

  | i915 :00:02.0: Resetting rcs0 for hang on rcs0

  Most of the time, it recovers on it's own but sometimes locks up
  completely requring a reboot. When that happens this is logged:

  | Feb  2 10:37:23 dharkan kernel: [71018.593184] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:37:23 dharkan kernel: [71018.593993] [drm:gen8_reset_engines 
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL: 
0001}
  | Feb  2 10:37:23 dharkan kernel: [71018.594130] i915 :00:02.0: Resetting 
chip for hang on rcs0
  | Feb  2 10:37:23 dharkan kernel: [71018.595937] [drm:gen8_reset_engines 
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL: 
0001}
  | Feb  2 10:37:23 dharkan kernel: [71018.596728] [drm:gen8_reset_engines 
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL: 
0001}
  | Feb  2 10:37:28 dharkan kernel: [71022.816232] Asynchronous wait on fence 
i915:compiz[1495]:105ece timed out (hint:intel_atomic_commit_ready+0x0/0x54 
[i915])
  | Feb  2 10:37:31 dharkan kernel: [71026.593149] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:37:31 dharkan kernel: [71026.593958] [drm:gen8_reset_engines 
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL: 
0001}
  | Feb  2 10:37:31 dharkan kernel: [71026.596916] i915 :00:02.0: Resetting 
chip for hang on rcs0
  | Feb  2 10:37:31 dharkan kernel: [71026.598661] [drm:gen8_reset_engines 
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL: 
0001}
  | Feb  2 10:37:31 dharkan kernel: [71026.599391] [drm:gen8_reset_engines 
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL: 
0001}
  | Feb  2 10:37:35 dharkan kernel: [71030.592141] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:37:39 dharkan kernel: [71034.323140] GpuWatchdog[1860]: segfault 
at 0 ip 55689a4eb33d sp 7f69b674d700 error 6 in 
chrome[5568968fd000+6abe000]
  | Feb  2 10:37:39 dharkan kernel: [71034.323157] Code: 00 79 09 48 8b 7d a0 
e8 31 2c 72 fc 41 8b 85 00 01 00 00 85 c0 0f 84 ab 00 00 00 49 8b 45 00 4c 89 
ef be 01 00 00 00 ff 50 58  04 25 00 00 00 00 37 13 00 00 c6 05 61 3c 59 03 
01 80 bd 7f ff
  | Feb  2 10:37:43 dharkan kernel: [71038.592101] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:37:45 dharkan kernel: [71040.576093] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:37:47 dharkan kernel: [71042.592066] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:37:49 dharkan kernel: [71044.576075] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:37:51 dharkan kernel: [71046.592045] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:37:53 dharkan kernel: [71048.576098] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:37:55 dharkan kernel: [71050.592029] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:37:57 dharkan kernel: [71052.576037] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:37:59 dharkan kernel: [71054.592034] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:38:01 dharkan kernel: [71056.576021] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:38:03 dharkan kernel: [71058.592006] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:38:04 dharkan kernel: [71059.461584] GpuWatchdog[43507]: segfault 
at 0 ip 55ac6731833d sp 7fe71901e700 error 6 in 
chrome[55ac6372a000+6abe000]
  | Feb  2 10:38:04 dharkan kernel: [71059.461600] Code: 00 79 09 48 8b 7d a0 
e8 31 2c 72 fc 41 8b 85 00 01 00 00 85 c0 0f 84 ab 00 00 00 49 8b 45 00 4c 89 
ef be 01 00 00 00 ff 50 58  04 25 00 00 00 00 37 13 00 00 c6 05 61 3c 59 03 
01 80 bd 7f ff
  | Feb  2 10:38:05 dharkan kernel: [71060.575986] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:38:07 dharkan kernel: [71062.591982] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:38:09 dharkan kernel: [71064.575976] i915 :00:02.0: Resetting 
rcs0 for hang on 

[Desktop-packages] [Bug 1862865] Re: i915 0000:00:02.0: Resetting rcs0 for stuck wait on rcs0

[Haw Loeung]

Also, I even tried disabling the power saving feature
(i915.enable_psr=0) but it still seems to lock up or hang.

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

Title:
  i915 :00:02.0: Resetting rcs0 for stuck wait on rcs0

Status in linux package in Ubuntu:
  Confirmed
Status in mesa package in Ubuntu:
  Invalid
Status in linux source package in Focal:
  Confirmed
Status in mesa source package in Focal:
  Invalid

Bug description:
  Hi,

  Every now and again, my session locks up with the following logged:

  | i915 :00:02.0: Resetting rcs0 for hang on rcs0

  Most of the time, it recovers on it's own but sometimes locks up
  completely requring a reboot. When that happens this is logged:

  | Feb  2 10:37:23 dharkan kernel: [71018.593184] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:37:23 dharkan kernel: [71018.593993] [drm:gen8_reset_engines 
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL: 
0001}
  | Feb  2 10:37:23 dharkan kernel: [71018.594130] i915 :00:02.0: Resetting 
chip for hang on rcs0
  | Feb  2 10:37:23 dharkan kernel: [71018.595937] [drm:gen8_reset_engines 
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL: 
0001}
  | Feb  2 10:37:23 dharkan kernel: [71018.596728] [drm:gen8_reset_engines 
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL: 
0001}
  | Feb  2 10:37:28 dharkan kernel: [71022.816232] Asynchronous wait on fence 
i915:compiz[1495]:105ece timed out (hint:intel_atomic_commit_ready+0x0/0x54 
[i915])
  | Feb  2 10:37:31 dharkan kernel: [71026.593149] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:37:31 dharkan kernel: [71026.593958] [drm:gen8_reset_engines 
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL: 
0001}
  | Feb  2 10:37:31 dharkan kernel: [71026.596916] i915 :00:02.0: Resetting 
chip for hang on rcs0
  | Feb  2 10:37:31 dharkan kernel: [71026.598661] [drm:gen8_reset_engines 
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL: 
0001}
  | Feb  2 10:37:31 dharkan kernel: [71026.599391] [drm:gen8_reset_engines 
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL: 
0001}
  | Feb  2 10:37:35 dharkan kernel: [71030.592141] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:37:39 dharkan kernel: [71034.323140] GpuWatchdog[1860]: segfault 
at 0 ip 55689a4eb33d sp 7f69b674d700 error 6 in 
chrome[5568968fd000+6abe000]
  | Feb  2 10:37:39 dharkan kernel: [71034.323157] Code: 00 79 09 48 8b 7d a0 
e8 31 2c 72 fc 41 8b 85 00 01 00 00 85 c0 0f 84 ab 00 00 00 49 8b 45 00 4c 89 
ef be 01 00 00 00 ff 50 58  04 25 00 00 00 00 37 13 00 00 c6 05 61 3c 59 03 
01 80 bd 7f ff
  | Feb  2 10:37:43 dharkan kernel: [71038.592101] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:37:45 dharkan kernel: [71040.576093] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:37:47 dharkan kernel: [71042.592066] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:37:49 dharkan kernel: [71044.576075] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:37:51 dharkan kernel: [71046.592045] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:37:53 dharkan kernel: [71048.576098] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:37:55 dharkan kernel: [71050.592029] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:37:57 dharkan kernel: [71052.576037] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:37:59 dharkan kernel: [71054.592034] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:38:01 dharkan kernel: [71056.576021] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:38:03 dharkan kernel: [71058.592006] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:38:04 dharkan kernel: [71059.461584] GpuWatchdog[43507]: segfault 
at 0 ip 55ac6731833d sp 7fe71901e700 error 6 in 
chrome[55ac6372a000+6abe000]
  | Feb  2 10:38:04 dharkan kernel: [71059.461600] Code: 00 79 09 48 8b 7d a0 
e8 31 2c 72 fc 41 8b 85 00 01 00 00 85 c0 0f 84 ab 00 00 00 49 8b 45 00 4c 89 
ef be 01 00 00 00 ff 50 58  04 25 00 00 00 00 37 13 00 00 c6 05 61 3c 59 03 
01 80 bd 7f ff
  | Feb  2 10:38:05 dharkan kernel: [71060.575986] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:38:07 dharkan kernel: [71062.591982] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:38:09 dharkan kernel: [71064.575976] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:38:11 dharkan kernel: [71066.591956] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:38:13 dharkan kernel: [71068.575937] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:38:15 dharkan 

[Desktop-packages] [Bug 1862865] WifiSyslog.txt

[Haw Loeung]

apport information

** Attachment added: "WifiSyslog.txt"
   
https://bugs.launchpad.net/bugs/1862865/+attachment/5328142/+files/WifiSyslog.txt

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

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

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

Title:
  i915 :00:02.0: Resetting rcs0 for stuck wait on rcs0

Status in linux package in Ubuntu:
  Confirmed
Status in mesa package in Ubuntu:
  Invalid
Status in linux source package in Focal:
  Confirmed
Status in mesa source package in Focal:
  Invalid

Bug description:
  Hi,

  Every now and again, my session locks up with the following logged:

  | i915 :00:02.0: Resetting rcs0 for hang on rcs0

  Most of the time, it recovers on it's own but sometimes locks up
  completely requring a reboot. When that happens this is logged:

  | Feb  2 10:37:23 dharkan kernel: [71018.593184] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:37:23 dharkan kernel: [71018.593993] [drm:gen8_reset_engines 
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL: 
0001}
  | Feb  2 10:37:23 dharkan kernel: [71018.594130] i915 :00:02.0: Resetting 
chip for hang on rcs0
  | Feb  2 10:37:23 dharkan kernel: [71018.595937] [drm:gen8_reset_engines 
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL: 
0001}
  | Feb  2 10:37:23 dharkan kernel: [71018.596728] [drm:gen8_reset_engines 
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL: 
0001}
  | Feb  2 10:37:28 dharkan kernel: [71022.816232] Asynchronous wait on fence 
i915:compiz[1495]:105ece timed out (hint:intel_atomic_commit_ready+0x0/0x54 
[i915])
  | Feb  2 10:37:31 dharkan kernel: [71026.593149] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:37:31 dharkan kernel: [71026.593958] [drm:gen8_reset_engines 
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL: 
0001}
  | Feb  2 10:37:31 dharkan kernel: [71026.596916] i915 :00:02.0: Resetting 
chip for hang on rcs0
  | Feb  2 10:37:31 dharkan kernel: [71026.598661] [drm:gen8_reset_engines 
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL: 
0001}
  | Feb  2 10:37:31 dharkan kernel: [71026.599391] [drm:gen8_reset_engines 
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL: 
0001}
  | Feb  2 10:37:35 dharkan kernel: [71030.592141] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:37:39 dharkan kernel: [71034.323140] GpuWatchdog[1860]: segfault 
at 0 ip 55689a4eb33d sp 7f69b674d700 error 6 in 
chrome[5568968fd000+6abe000]
  | Feb  2 10:37:39 dharkan kernel: [71034.323157] Code: 00 79 09 48 8b 7d a0 
e8 31 2c 72 fc 41 8b 85 00 01 00 00 85 c0 0f 84 ab 00 00 00 49 8b 45 00 4c 89 
ef be 01 00 00 00 ff 50 58  04 25 00 00 00 00 37 13 00 00 c6 05 61 3c 59 03 
01 80 bd 7f ff
  | Feb  2 10:37:43 dharkan kernel: [71038.592101] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:37:45 dharkan kernel: [71040.576093] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:37:47 dharkan kernel: [71042.592066] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:37:49 dharkan kernel: [71044.576075] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:37:51 dharkan kernel: [71046.592045] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:37:53 dharkan kernel: [71048.576098] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:37:55 dharkan kernel: [71050.592029] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:37:57 dharkan kernel: [71052.576037] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:37:59 dharkan kernel: [71054.592034] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:38:01 dharkan kernel: [71056.576021] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:38:03 dharkan kernel: [71058.592006] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:38:04 dharkan kernel: [71059.461584] GpuWatchdog[43507]: segfault 
at 0 ip 55ac6731833d sp 7fe71901e700 error 6 in 
chrome[55ac6372a000+6abe000]
  | Feb  2 10:38:04 dharkan kernel: [71059.461600] Code: 00 79 09 48 8b 7d a0 
e8 31 2c 72 fc 41 8b 85 00 01 00 00 85 c0 0f 84 ab 00 00 00 49 8b 45 00 4c 89 
ef be 01 00 00 00 ff 50 58  04 25 00 00 00 00 37 13 00 00 c6 05 61 3c 59 03 
01 80 bd 7f ff
  | Feb  2 10:38:05 dharkan kernel: [71060.575986] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:38:07 dharkan kernel: [71062.591982] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:38:09 dharkan kernel: [71064.575976] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:38:11 dharkan kernel: [71066.591956] i915 

[Desktop-packages] [Bug 1862865] UdevDb.txt

[Haw Loeung]

apport information

** Attachment added: "UdevDb.txt"
   https://bugs.launchpad.net/bugs/1862865/+attachment/5328141/+files/UdevDb.txt

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

Title:
  i915 :00:02.0: Resetting rcs0 for stuck wait on rcs0

Status in linux package in Ubuntu:
  Confirmed
Status in mesa package in Ubuntu:
  Invalid
Status in linux source package in Focal:
  Confirmed
Status in mesa source package in Focal:
  Invalid

Bug description:
  Hi,

  Every now and again, my session locks up with the following logged:

  | i915 :00:02.0: Resetting rcs0 for hang on rcs0

  Most of the time, it recovers on it's own but sometimes locks up
  completely requring a reboot. When that happens this is logged:

  | Feb  2 10:37:23 dharkan kernel: [71018.593184] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:37:23 dharkan kernel: [71018.593993] [drm:gen8_reset_engines 
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL: 
0001}
  | Feb  2 10:37:23 dharkan kernel: [71018.594130] i915 :00:02.0: Resetting 
chip for hang on rcs0
  | Feb  2 10:37:23 dharkan kernel: [71018.595937] [drm:gen8_reset_engines 
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL: 
0001}
  | Feb  2 10:37:23 dharkan kernel: [71018.596728] [drm:gen8_reset_engines 
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL: 
0001}
  | Feb  2 10:37:28 dharkan kernel: [71022.816232] Asynchronous wait on fence 
i915:compiz[1495]:105ece timed out (hint:intel_atomic_commit_ready+0x0/0x54 
[i915])
  | Feb  2 10:37:31 dharkan kernel: [71026.593149] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:37:31 dharkan kernel: [71026.593958] [drm:gen8_reset_engines 
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL: 
0001}
  | Feb  2 10:37:31 dharkan kernel: [71026.596916] i915 :00:02.0: Resetting 
chip for hang on rcs0
  | Feb  2 10:37:31 dharkan kernel: [71026.598661] [drm:gen8_reset_engines 
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL: 
0001}
  | Feb  2 10:37:31 dharkan kernel: [71026.599391] [drm:gen8_reset_engines 
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL: 
0001}
  | Feb  2 10:37:35 dharkan kernel: [71030.592141] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:37:39 dharkan kernel: [71034.323140] GpuWatchdog[1860]: segfault 
at 0 ip 55689a4eb33d sp 7f69b674d700 error 6 in 
chrome[5568968fd000+6abe000]
  | Feb  2 10:37:39 dharkan kernel: [71034.323157] Code: 00 79 09 48 8b 7d a0 
e8 31 2c 72 fc 41 8b 85 00 01 00 00 85 c0 0f 84 ab 00 00 00 49 8b 45 00 4c 89 
ef be 01 00 00 00 ff 50 58  04 25 00 00 00 00 37 13 00 00 c6 05 61 3c 59 03 
01 80 bd 7f ff
  | Feb  2 10:37:43 dharkan kernel: [71038.592101] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:37:45 dharkan kernel: [71040.576093] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:37:47 dharkan kernel: [71042.592066] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:37:49 dharkan kernel: [71044.576075] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:37:51 dharkan kernel: [71046.592045] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:37:53 dharkan kernel: [71048.576098] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:37:55 dharkan kernel: [71050.592029] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:37:57 dharkan kernel: [71052.576037] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:37:59 dharkan kernel: [71054.592034] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:38:01 dharkan kernel: [71056.576021] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:38:03 dharkan kernel: [71058.592006] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:38:04 dharkan kernel: [71059.461584] GpuWatchdog[43507]: segfault 
at 0 ip 55ac6731833d sp 7fe71901e700 error 6 in 
chrome[55ac6372a000+6abe000]
  | Feb  2 10:38:04 dharkan kernel: [71059.461600] Code: 00 79 09 48 8b 7d a0 
e8 31 2c 72 fc 41 8b 85 00 01 00 00 85 c0 0f 84 ab 00 00 00 49 8b 45 00 4c 89 
ef be 01 00 00 00 ff 50 58  04 25 00 00 00 00 37 13 00 00 c6 05 61 3c 59 03 
01 80 bd 7f ff
  | Feb  2 10:38:05 dharkan kernel: [71060.575986] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:38:07 dharkan kernel: [71062.591982] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:38:09 dharkan kernel: [71064.575976] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:38:11 dharkan kernel: [71066.591956] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:38:13 dharkan kernel: [71068.575937] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | 

[Desktop-packages] [Bug 1862865] Re: i915 0000:00:02.0: Resetting rcs0 for stuck wait on rcs0

[Haw Loeung]

| [Fri Feb 14 18:55:37 2020] i915 :00:02.0: GPU HANG: ecode 9:1:0x, 
hang on rcs0
| [Fri Feb 14 18:55:37 2020] GPU hangs can indicate a bug anywhere in the 
entire gfx stack, including userspace.
| [Fri Feb 14 18:55:37 2020] Please file a _new_ bug report on 
bugs.freedesktop.org against DRI -> DRM/Intel
| [Fri Feb 14 18:55:37 2020] drm/i915 developers can then reassign to the right 
component if it's not a kernel issue.
| [Fri Feb 14 18:55:37 2020] The GPU crash dump is required to analyze GPU 
hangs, so please always attach it.
| [Fri Feb 14 18:55:37 2020] GPU crash dump saved to /sys/class/drm/card0/error
| [Fri Feb 14 18:55:37 2020] i915 :00:02.0: Resetting rcs0 for hang on rcs0
| [Fri Feb 14 18:55:45 2020] i915 :00:02.0: Resetting rcs0 for hang on rcs0

So included saved crash dump from /sys/class/drm/card0/error.


** Attachment added: "/sys/class/drm/card0/error"
   
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1862865/+attachment/5328143/+files/drm-error.txt

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

Title:
  i915 :00:02.0: Resetting rcs0 for stuck wait on rcs0

Status in linux package in Ubuntu:
  Confirmed
Status in mesa package in Ubuntu:
  Invalid
Status in linux source package in Focal:
  Confirmed
Status in mesa source package in Focal:
  Invalid

Bug description:
  Hi,

  Every now and again, my session locks up with the following logged:

  | i915 :00:02.0: Resetting rcs0 for hang on rcs0

  Most of the time, it recovers on it's own but sometimes locks up
  completely requring a reboot. When that happens this is logged:

  | Feb  2 10:37:23 dharkan kernel: [71018.593184] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:37:23 dharkan kernel: [71018.593993] [drm:gen8_reset_engines 
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL: 
0001}
  | Feb  2 10:37:23 dharkan kernel: [71018.594130] i915 :00:02.0: Resetting 
chip for hang on rcs0
  | Feb  2 10:37:23 dharkan kernel: [71018.595937] [drm:gen8_reset_engines 
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL: 
0001}
  | Feb  2 10:37:23 dharkan kernel: [71018.596728] [drm:gen8_reset_engines 
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL: 
0001}
  | Feb  2 10:37:28 dharkan kernel: [71022.816232] Asynchronous wait on fence 
i915:compiz[1495]:105ece timed out (hint:intel_atomic_commit_ready+0x0/0x54 
[i915])
  | Feb  2 10:37:31 dharkan kernel: [71026.593149] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:37:31 dharkan kernel: [71026.593958] [drm:gen8_reset_engines 
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL: 
0001}
  | Feb  2 10:37:31 dharkan kernel: [71026.596916] i915 :00:02.0: Resetting 
chip for hang on rcs0
  | Feb  2 10:37:31 dharkan kernel: [71026.598661] [drm:gen8_reset_engines 
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL: 
0001}
  | Feb  2 10:37:31 dharkan kernel: [71026.599391] [drm:gen8_reset_engines 
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL: 
0001}
  | Feb  2 10:37:35 dharkan kernel: [71030.592141] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:37:39 dharkan kernel: [71034.323140] GpuWatchdog[1860]: segfault 
at 0 ip 55689a4eb33d sp 7f69b674d700 error 6 in 
chrome[5568968fd000+6abe000]
  | Feb  2 10:37:39 dharkan kernel: [71034.323157] Code: 00 79 09 48 8b 7d a0 
e8 31 2c 72 fc 41 8b 85 00 01 00 00 85 c0 0f 84 ab 00 00 00 49 8b 45 00 4c 89 
ef be 01 00 00 00 ff 50 58  04 25 00 00 00 00 37 13 00 00 c6 05 61 3c 59 03 
01 80 bd 7f ff
  | Feb  2 10:37:43 dharkan kernel: [71038.592101] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:37:45 dharkan kernel: [71040.576093] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:37:47 dharkan kernel: [71042.592066] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:37:49 dharkan kernel: [71044.576075] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:37:51 dharkan kernel: [71046.592045] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:37:53 dharkan kernel: [71048.576098] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:37:55 dharkan kernel: [71050.592029] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:37:57 dharkan kernel: [71052.576037] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:37:59 dharkan kernel: [71054.592034] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:38:01 dharkan kernel: [71056.576021] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:38:03 dharkan kernel: [71058.592006] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:38:04 dharkan kernel: [71059.461584] 

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

[Haw Loeung]

apport information

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

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

Title:
  i915 :00:02.0: Resetting rcs0 for stuck wait on rcs0

Status in linux package in Ubuntu:
  Confirmed
Status in mesa package in Ubuntu:
  Invalid
Status in linux source package in Focal:
  Confirmed
Status in mesa source package in Focal:
  Invalid

Bug description:
  Hi,

  Every now and again, my session locks up with the following logged:

  | i915 :00:02.0: Resetting rcs0 for hang on rcs0

  Most of the time, it recovers on it's own but sometimes locks up
  completely requring a reboot. When that happens this is logged:

  | Feb  2 10:37:23 dharkan kernel: [71018.593184] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:37:23 dharkan kernel: [71018.593993] [drm:gen8_reset_engines 
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL: 
0001}
  | Feb  2 10:37:23 dharkan kernel: [71018.594130] i915 :00:02.0: Resetting 
chip for hang on rcs0
  | Feb  2 10:37:23 dharkan kernel: [71018.595937] [drm:gen8_reset_engines 
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL: 
0001}
  | Feb  2 10:37:23 dharkan kernel: [71018.596728] [drm:gen8_reset_engines 
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL: 
0001}
  | Feb  2 10:37:28 dharkan kernel: [71022.816232] Asynchronous wait on fence 
i915:compiz[1495]:105ece timed out (hint:intel_atomic_commit_ready+0x0/0x54 
[i915])
  | Feb  2 10:37:31 dharkan kernel: [71026.593149] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:37:31 dharkan kernel: [71026.593958] [drm:gen8_reset_engines 
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL: 
0001}
  | Feb  2 10:37:31 dharkan kernel: [71026.596916] i915 :00:02.0: Resetting 
chip for hang on rcs0
  | Feb  2 10:37:31 dharkan kernel: [71026.598661] [drm:gen8_reset_engines 
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL: 
0001}
  | Feb  2 10:37:31 dharkan kernel: [71026.599391] [drm:gen8_reset_engines 
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL: 
0001}
  | Feb  2 10:37:35 dharkan kernel: [71030.592141] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:37:39 dharkan kernel: [71034.323140] GpuWatchdog[1860]: segfault 
at 0 ip 55689a4eb33d sp 7f69b674d700 error 6 in 
chrome[5568968fd000+6abe000]
  | Feb  2 10:37:39 dharkan kernel: [71034.323157] Code: 00 79 09 48 8b 7d a0 
e8 31 2c 72 fc 41 8b 85 00 01 00 00 85 c0 0f 84 ab 00 00 00 49 8b 45 00 4c 89 
ef be 01 00 00 00 ff 50 58  04 25 00 00 00 00 37 13 00 00 c6 05 61 3c 59 03 
01 80 bd 7f ff
  | Feb  2 10:37:43 dharkan kernel: [71038.592101] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:37:45 dharkan kernel: [71040.576093] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:37:47 dharkan kernel: [71042.592066] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:37:49 dharkan kernel: [71044.576075] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:37:51 dharkan kernel: [71046.592045] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:37:53 dharkan kernel: [71048.576098] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:37:55 dharkan kernel: [71050.592029] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:37:57 dharkan kernel: [71052.576037] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:37:59 dharkan kernel: [71054.592034] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:38:01 dharkan kernel: [71056.576021] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:38:03 dharkan kernel: [71058.592006] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:38:04 dharkan kernel: [71059.461584] GpuWatchdog[43507]: segfault 
at 0 ip 55ac6731833d sp 7fe71901e700 error 6 in 
chrome[55ac6372a000+6abe000]
  | Feb  2 10:38:04 dharkan kernel: [71059.461600] Code: 00 79 09 48 8b 7d a0 
e8 31 2c 72 fc 41 8b 85 00 01 00 00 85 c0 0f 84 ab 00 00 00 49 8b 45 00 4c 89 
ef be 01 00 00 00 ff 50 58  04 25 00 00 00 00 37 13 00 00 c6 05 61 3c 59 03 
01 80 bd 7f ff
  | Feb  2 10:38:05 dharkan kernel: [71060.575986] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:38:07 dharkan kernel: [71062.591982] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:38:09 dharkan kernel: [71064.575976] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:38:11 dharkan kernel: [71066.591956] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:38:13 dharkan kernel: [71068.575937] i915 :00:02.0: Resetting 
rcs0 for hang on 

[Desktop-packages] [Bug 1862865] PulseList.txt

[Haw Loeung]

apport information

** Attachment added: "PulseList.txt"
   
https://bugs.launchpad.net/bugs/1862865/+attachment/5328140/+files/PulseList.txt

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

Title:
  i915 :00:02.0: Resetting rcs0 for stuck wait on rcs0

Status in linux package in Ubuntu:
  Confirmed
Status in mesa package in Ubuntu:
  Invalid
Status in linux source package in Focal:
  Confirmed
Status in mesa source package in Focal:
  Invalid

Bug description:
  Hi,

  Every now and again, my session locks up with the following logged:

  | i915 :00:02.0: Resetting rcs0 for hang on rcs0

  Most of the time, it recovers on it's own but sometimes locks up
  completely requring a reboot. When that happens this is logged:

  | Feb  2 10:37:23 dharkan kernel: [71018.593184] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:37:23 dharkan kernel: [71018.593993] [drm:gen8_reset_engines 
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL: 
0001}
  | Feb  2 10:37:23 dharkan kernel: [71018.594130] i915 :00:02.0: Resetting 
chip for hang on rcs0
  | Feb  2 10:37:23 dharkan kernel: [71018.595937] [drm:gen8_reset_engines 
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL: 
0001}
  | Feb  2 10:37:23 dharkan kernel: [71018.596728] [drm:gen8_reset_engines 
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL: 
0001}
  | Feb  2 10:37:28 dharkan kernel: [71022.816232] Asynchronous wait on fence 
i915:compiz[1495]:105ece timed out (hint:intel_atomic_commit_ready+0x0/0x54 
[i915])
  | Feb  2 10:37:31 dharkan kernel: [71026.593149] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:37:31 dharkan kernel: [71026.593958] [drm:gen8_reset_engines 
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL: 
0001}
  | Feb  2 10:37:31 dharkan kernel: [71026.596916] i915 :00:02.0: Resetting 
chip for hang on rcs0
  | Feb  2 10:37:31 dharkan kernel: [71026.598661] [drm:gen8_reset_engines 
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL: 
0001}
  | Feb  2 10:37:31 dharkan kernel: [71026.599391] [drm:gen8_reset_engines 
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL: 
0001}
  | Feb  2 10:37:35 dharkan kernel: [71030.592141] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:37:39 dharkan kernel: [71034.323140] GpuWatchdog[1860]: segfault 
at 0 ip 55689a4eb33d sp 7f69b674d700 error 6 in 
chrome[5568968fd000+6abe000]
  | Feb  2 10:37:39 dharkan kernel: [71034.323157] Code: 00 79 09 48 8b 7d a0 
e8 31 2c 72 fc 41 8b 85 00 01 00 00 85 c0 0f 84 ab 00 00 00 49 8b 45 00 4c 89 
ef be 01 00 00 00 ff 50 58  04 25 00 00 00 00 37 13 00 00 c6 05 61 3c 59 03 
01 80 bd 7f ff
  | Feb  2 10:37:43 dharkan kernel: [71038.592101] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:37:45 dharkan kernel: [71040.576093] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:37:47 dharkan kernel: [71042.592066] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:37:49 dharkan kernel: [71044.576075] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:37:51 dharkan kernel: [71046.592045] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:37:53 dharkan kernel: [71048.576098] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:37:55 dharkan kernel: [71050.592029] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:37:57 dharkan kernel: [71052.576037] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:37:59 dharkan kernel: [71054.592034] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:38:01 dharkan kernel: [71056.576021] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:38:03 dharkan kernel: [71058.592006] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:38:04 dharkan kernel: [71059.461584] GpuWatchdog[43507]: segfault 
at 0 ip 55ac6731833d sp 7fe71901e700 error 6 in 
chrome[55ac6372a000+6abe000]
  | Feb  2 10:38:04 dharkan kernel: [71059.461600] Code: 00 79 09 48 8b 7d a0 
e8 31 2c 72 fc 41 8b 85 00 01 00 00 85 c0 0f 84 ab 00 00 00 49 8b 45 00 4c 89 
ef be 01 00 00 00 ff 50 58  04 25 00 00 00 00 37 13 00 00 c6 05 61 3c 59 03 
01 80 bd 7f ff
  | Feb  2 10:38:05 dharkan kernel: [71060.575986] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:38:07 dharkan kernel: [71062.591982] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:38:09 dharkan kernel: [71064.575976] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:38:11 dharkan kernel: [71066.591956] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:38:13 dharkan kernel: [71068.575937] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0

[Desktop-packages] [Bug 1862865] ProcModules.txt

[Haw Loeung]

apport information

** Attachment added: "ProcModules.txt"
   
https://bugs.launchpad.net/bugs/1862865/+attachment/5328139/+files/ProcModules.txt

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

Title:
  i915 :00:02.0: Resetting rcs0 for stuck wait on rcs0

Status in linux package in Ubuntu:
  Confirmed
Status in mesa package in Ubuntu:
  Invalid
Status in linux source package in Focal:
  Confirmed
Status in mesa source package in Focal:
  Invalid

Bug description:
  Hi,

  Every now and again, my session locks up with the following logged:

  | i915 :00:02.0: Resetting rcs0 for hang on rcs0

  Most of the time, it recovers on it's own but sometimes locks up
  completely requring a reboot. When that happens this is logged:

  | Feb  2 10:37:23 dharkan kernel: [71018.593184] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:37:23 dharkan kernel: [71018.593993] [drm:gen8_reset_engines 
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL: 
0001}
  | Feb  2 10:37:23 dharkan kernel: [71018.594130] i915 :00:02.0: Resetting 
chip for hang on rcs0
  | Feb  2 10:37:23 dharkan kernel: [71018.595937] [drm:gen8_reset_engines 
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL: 
0001}
  | Feb  2 10:37:23 dharkan kernel: [71018.596728] [drm:gen8_reset_engines 
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL: 
0001}
  | Feb  2 10:37:28 dharkan kernel: [71022.816232] Asynchronous wait on fence 
i915:compiz[1495]:105ece timed out (hint:intel_atomic_commit_ready+0x0/0x54 
[i915])
  | Feb  2 10:37:31 dharkan kernel: [71026.593149] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:37:31 dharkan kernel: [71026.593958] [drm:gen8_reset_engines 
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL: 
0001}
  | Feb  2 10:37:31 dharkan kernel: [71026.596916] i915 :00:02.0: Resetting 
chip for hang on rcs0
  | Feb  2 10:37:31 dharkan kernel: [71026.598661] [drm:gen8_reset_engines 
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL: 
0001}
  | Feb  2 10:37:31 dharkan kernel: [71026.599391] [drm:gen8_reset_engines 
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL: 
0001}
  | Feb  2 10:37:35 dharkan kernel: [71030.592141] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:37:39 dharkan kernel: [71034.323140] GpuWatchdog[1860]: segfault 
at 0 ip 55689a4eb33d sp 7f69b674d700 error 6 in 
chrome[5568968fd000+6abe000]
  | Feb  2 10:37:39 dharkan kernel: [71034.323157] Code: 00 79 09 48 8b 7d a0 
e8 31 2c 72 fc 41 8b 85 00 01 00 00 85 c0 0f 84 ab 00 00 00 49 8b 45 00 4c 89 
ef be 01 00 00 00 ff 50 58  04 25 00 00 00 00 37 13 00 00 c6 05 61 3c 59 03 
01 80 bd 7f ff
  | Feb  2 10:37:43 dharkan kernel: [71038.592101] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:37:45 dharkan kernel: [71040.576093] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:37:47 dharkan kernel: [71042.592066] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:37:49 dharkan kernel: [71044.576075] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:37:51 dharkan kernel: [71046.592045] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:37:53 dharkan kernel: [71048.576098] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:37:55 dharkan kernel: [71050.592029] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:37:57 dharkan kernel: [71052.576037] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:37:59 dharkan kernel: [71054.592034] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:38:01 dharkan kernel: [71056.576021] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:38:03 dharkan kernel: [71058.592006] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:38:04 dharkan kernel: [71059.461584] GpuWatchdog[43507]: segfault 
at 0 ip 55ac6731833d sp 7fe71901e700 error 6 in 
chrome[55ac6372a000+6abe000]
  | Feb  2 10:38:04 dharkan kernel: [71059.461600] Code: 00 79 09 48 8b 7d a0 
e8 31 2c 72 fc 41 8b 85 00 01 00 00 85 c0 0f 84 ab 00 00 00 49 8b 45 00 4c 89 
ef be 01 00 00 00 ff 50 58  04 25 00 00 00 00 37 13 00 00 c6 05 61 3c 59 03 
01 80 bd 7f ff
  | Feb  2 10:38:05 dharkan kernel: [71060.575986] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:38:07 dharkan kernel: [71062.591982] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:38:09 dharkan kernel: [71064.575976] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:38:11 dharkan kernel: [71066.591956] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:38:13 dharkan kernel: [71068.575937] i915 :00:02.0: Resetting 
rcs0 for hang on 

[Desktop-packages] [Bug 1862865] ProcInterrupts.txt

[Haw Loeung]

apport information

** Attachment added: "ProcInterrupts.txt"
   
https://bugs.launchpad.net/bugs/1862865/+attachment/5328138/+files/ProcInterrupts.txt

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

Title:
  i915 :00:02.0: Resetting rcs0 for stuck wait on rcs0

Status in linux package in Ubuntu:
  Confirmed
Status in mesa package in Ubuntu:
  Invalid
Status in linux source package in Focal:
  Confirmed
Status in mesa source package in Focal:
  Invalid

Bug description:
  Hi,

  Every now and again, my session locks up with the following logged:

  | i915 :00:02.0: Resetting rcs0 for hang on rcs0

  Most of the time, it recovers on it's own but sometimes locks up
  completely requring a reboot. When that happens this is logged:

  | Feb  2 10:37:23 dharkan kernel: [71018.593184] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:37:23 dharkan kernel: [71018.593993] [drm:gen8_reset_engines 
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL: 
0001}
  | Feb  2 10:37:23 dharkan kernel: [71018.594130] i915 :00:02.0: Resetting 
chip for hang on rcs0
  | Feb  2 10:37:23 dharkan kernel: [71018.595937] [drm:gen8_reset_engines 
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL: 
0001}
  | Feb  2 10:37:23 dharkan kernel: [71018.596728] [drm:gen8_reset_engines 
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL: 
0001}
  | Feb  2 10:37:28 dharkan kernel: [71022.816232] Asynchronous wait on fence 
i915:compiz[1495]:105ece timed out (hint:intel_atomic_commit_ready+0x0/0x54 
[i915])
  | Feb  2 10:37:31 dharkan kernel: [71026.593149] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:37:31 dharkan kernel: [71026.593958] [drm:gen8_reset_engines 
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL: 
0001}
  | Feb  2 10:37:31 dharkan kernel: [71026.596916] i915 :00:02.0: Resetting 
chip for hang on rcs0
  | Feb  2 10:37:31 dharkan kernel: [71026.598661] [drm:gen8_reset_engines 
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL: 
0001}
  | Feb  2 10:37:31 dharkan kernel: [71026.599391] [drm:gen8_reset_engines 
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL: 
0001}
  | Feb  2 10:37:35 dharkan kernel: [71030.592141] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:37:39 dharkan kernel: [71034.323140] GpuWatchdog[1860]: segfault 
at 0 ip 55689a4eb33d sp 7f69b674d700 error 6 in 
chrome[5568968fd000+6abe000]
  | Feb  2 10:37:39 dharkan kernel: [71034.323157] Code: 00 79 09 48 8b 7d a0 
e8 31 2c 72 fc 41 8b 85 00 01 00 00 85 c0 0f 84 ab 00 00 00 49 8b 45 00 4c 89 
ef be 01 00 00 00 ff 50 58  04 25 00 00 00 00 37 13 00 00 c6 05 61 3c 59 03 
01 80 bd 7f ff
  | Feb  2 10:37:43 dharkan kernel: [71038.592101] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:37:45 dharkan kernel: [71040.576093] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:37:47 dharkan kernel: [71042.592066] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:37:49 dharkan kernel: [71044.576075] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:37:51 dharkan kernel: [71046.592045] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:37:53 dharkan kernel: [71048.576098] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:37:55 dharkan kernel: [71050.592029] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:37:57 dharkan kernel: [71052.576037] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:37:59 dharkan kernel: [71054.592034] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:38:01 dharkan kernel: [71056.576021] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:38:03 dharkan kernel: [71058.592006] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:38:04 dharkan kernel: [71059.461584] GpuWatchdog[43507]: segfault 
at 0 ip 55ac6731833d sp 7fe71901e700 error 6 in 
chrome[55ac6372a000+6abe000]
  | Feb  2 10:38:04 dharkan kernel: [71059.461600] Code: 00 79 09 48 8b 7d a0 
e8 31 2c 72 fc 41 8b 85 00 01 00 00 85 c0 0f 84 ab 00 00 00 49 8b 45 00 4c 89 
ef be 01 00 00 00 ff 50 58  04 25 00 00 00 00 37 13 00 00 c6 05 61 3c 59 03 
01 80 bd 7f ff
  | Feb  2 10:38:05 dharkan kernel: [71060.575986] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:38:07 dharkan kernel: [71062.591982] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:38:09 dharkan kernel: [71064.575976] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:38:11 dharkan kernel: [71066.591956] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:38:13 dharkan kernel: [71068.575937] i915 :00:02.0: Resetting 
rcs0 for 

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

[Haw Loeung]

apport information

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

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

Title:
  i915 :00:02.0: Resetting rcs0 for stuck wait on rcs0

Status in linux package in Ubuntu:
  Confirmed
Status in mesa package in Ubuntu:
  Invalid
Status in linux source package in Focal:
  Confirmed
Status in mesa source package in Focal:
  Invalid

Bug description:
  Hi,

  Every now and again, my session locks up with the following logged:

  | i915 :00:02.0: Resetting rcs0 for hang on rcs0

  Most of the time, it recovers on it's own but sometimes locks up
  completely requring a reboot. When that happens this is logged:

  | Feb  2 10:37:23 dharkan kernel: [71018.593184] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:37:23 dharkan kernel: [71018.593993] [drm:gen8_reset_engines 
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL: 
0001}
  | Feb  2 10:37:23 dharkan kernel: [71018.594130] i915 :00:02.0: Resetting 
chip for hang on rcs0
  | Feb  2 10:37:23 dharkan kernel: [71018.595937] [drm:gen8_reset_engines 
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL: 
0001}
  | Feb  2 10:37:23 dharkan kernel: [71018.596728] [drm:gen8_reset_engines 
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL: 
0001}
  | Feb  2 10:37:28 dharkan kernel: [71022.816232] Asynchronous wait on fence 
i915:compiz[1495]:105ece timed out (hint:intel_atomic_commit_ready+0x0/0x54 
[i915])
  | Feb  2 10:37:31 dharkan kernel: [71026.593149] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:37:31 dharkan kernel: [71026.593958] [drm:gen8_reset_engines 
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL: 
0001}
  | Feb  2 10:37:31 dharkan kernel: [71026.596916] i915 :00:02.0: Resetting 
chip for hang on rcs0
  | Feb  2 10:37:31 dharkan kernel: [71026.598661] [drm:gen8_reset_engines 
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL: 
0001}
  | Feb  2 10:37:31 dharkan kernel: [71026.599391] [drm:gen8_reset_engines 
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL: 
0001}
  | Feb  2 10:37:35 dharkan kernel: [71030.592141] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:37:39 dharkan kernel: [71034.323140] GpuWatchdog[1860]: segfault 
at 0 ip 55689a4eb33d sp 7f69b674d700 error 6 in 
chrome[5568968fd000+6abe000]
  | Feb  2 10:37:39 dharkan kernel: [71034.323157] Code: 00 79 09 48 8b 7d a0 
e8 31 2c 72 fc 41 8b 85 00 01 00 00 85 c0 0f 84 ab 00 00 00 49 8b 45 00 4c 89 
ef be 01 00 00 00 ff 50 58  04 25 00 00 00 00 37 13 00 00 c6 05 61 3c 59 03 
01 80 bd 7f ff
  | Feb  2 10:37:43 dharkan kernel: [71038.592101] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:37:45 dharkan kernel: [71040.576093] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:37:47 dharkan kernel: [71042.592066] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:37:49 dharkan kernel: [71044.576075] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:37:51 dharkan kernel: [71046.592045] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:37:53 dharkan kernel: [71048.576098] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:37:55 dharkan kernel: [71050.592029] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:37:57 dharkan kernel: [71052.576037] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:37:59 dharkan kernel: [71054.592034] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:38:01 dharkan kernel: [71056.576021] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:38:03 dharkan kernel: [71058.592006] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:38:04 dharkan kernel: [71059.461584] GpuWatchdog[43507]: segfault 
at 0 ip 55ac6731833d sp 7fe71901e700 error 6 in 
chrome[55ac6372a000+6abe000]
  | Feb  2 10:38:04 dharkan kernel: [71059.461600] Code: 00 79 09 48 8b 7d a0 
e8 31 2c 72 fc 41 8b 85 00 01 00 00 85 c0 0f 84 ab 00 00 00 49 8b 45 00 4c 89 
ef be 01 00 00 00 ff 50 58  04 25 00 00 00 00 37 13 00 00 c6 05 61 3c 59 03 
01 80 bd 7f ff
  | Feb  2 10:38:05 dharkan kernel: [71060.575986] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:38:07 dharkan kernel: [71062.591982] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:38:09 dharkan kernel: [71064.575976] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:38:11 dharkan kernel: [71066.591956] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:38:13 dharkan kernel: [71068.575937] i915 :00:02.0: Resetting 

[Desktop-packages] [Bug 1862865] PciMultimedia.txt

[Haw Loeung]

apport information

** Attachment added: "PciMultimedia.txt"
   
https://bugs.launchpad.net/bugs/1862865/+attachment/5328134/+files/PciMultimedia.txt

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

Title:
  i915 :00:02.0: Resetting rcs0 for stuck wait on rcs0

Status in linux package in Ubuntu:
  Confirmed
Status in mesa package in Ubuntu:
  Invalid
Status in linux source package in Focal:
  Confirmed
Status in mesa source package in Focal:
  Invalid

Bug description:
  Hi,

  Every now and again, my session locks up with the following logged:

  | i915 :00:02.0: Resetting rcs0 for hang on rcs0

  Most of the time, it recovers on it's own but sometimes locks up
  completely requring a reboot. When that happens this is logged:

  | Feb  2 10:37:23 dharkan kernel: [71018.593184] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:37:23 dharkan kernel: [71018.593993] [drm:gen8_reset_engines 
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL: 
0001}
  | Feb  2 10:37:23 dharkan kernel: [71018.594130] i915 :00:02.0: Resetting 
chip for hang on rcs0
  | Feb  2 10:37:23 dharkan kernel: [71018.595937] [drm:gen8_reset_engines 
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL: 
0001}
  | Feb  2 10:37:23 dharkan kernel: [71018.596728] [drm:gen8_reset_engines 
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL: 
0001}
  | Feb  2 10:37:28 dharkan kernel: [71022.816232] Asynchronous wait on fence 
i915:compiz[1495]:105ece timed out (hint:intel_atomic_commit_ready+0x0/0x54 
[i915])
  | Feb  2 10:37:31 dharkan kernel: [71026.593149] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:37:31 dharkan kernel: [71026.593958] [drm:gen8_reset_engines 
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL: 
0001}
  | Feb  2 10:37:31 dharkan kernel: [71026.596916] i915 :00:02.0: Resetting 
chip for hang on rcs0
  | Feb  2 10:37:31 dharkan kernel: [71026.598661] [drm:gen8_reset_engines 
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL: 
0001}
  | Feb  2 10:37:31 dharkan kernel: [71026.599391] [drm:gen8_reset_engines 
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL: 
0001}
  | Feb  2 10:37:35 dharkan kernel: [71030.592141] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:37:39 dharkan kernel: [71034.323140] GpuWatchdog[1860]: segfault 
at 0 ip 55689a4eb33d sp 7f69b674d700 error 6 in 
chrome[5568968fd000+6abe000]
  | Feb  2 10:37:39 dharkan kernel: [71034.323157] Code: 00 79 09 48 8b 7d a0 
e8 31 2c 72 fc 41 8b 85 00 01 00 00 85 c0 0f 84 ab 00 00 00 49 8b 45 00 4c 89 
ef be 01 00 00 00 ff 50 58  04 25 00 00 00 00 37 13 00 00 c6 05 61 3c 59 03 
01 80 bd 7f ff
  | Feb  2 10:37:43 dharkan kernel: [71038.592101] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:37:45 dharkan kernel: [71040.576093] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:37:47 dharkan kernel: [71042.592066] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:37:49 dharkan kernel: [71044.576075] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:37:51 dharkan kernel: [71046.592045] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:37:53 dharkan kernel: [71048.576098] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:37:55 dharkan kernel: [71050.592029] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:37:57 dharkan kernel: [71052.576037] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:37:59 dharkan kernel: [71054.592034] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:38:01 dharkan kernel: [71056.576021] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:38:03 dharkan kernel: [71058.592006] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:38:04 dharkan kernel: [71059.461584] GpuWatchdog[43507]: segfault 
at 0 ip 55ac6731833d sp 7fe71901e700 error 6 in 
chrome[55ac6372a000+6abe000]
  | Feb  2 10:38:04 dharkan kernel: [71059.461600] Code: 00 79 09 48 8b 7d a0 
e8 31 2c 72 fc 41 8b 85 00 01 00 00 85 c0 0f 84 ab 00 00 00 49 8b 45 00 4c 89 
ef be 01 00 00 00 ff 50 58  04 25 00 00 00 00 37 13 00 00 c6 05 61 3c 59 03 
01 80 bd 7f ff
  | Feb  2 10:38:05 dharkan kernel: [71060.575986] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:38:07 dharkan kernel: [71062.591982] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:38:09 dharkan kernel: [71064.575976] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:38:11 dharkan kernel: [71066.591956] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:38:13 dharkan kernel: [71068.575937] i915 :00:02.0: Resetting 
rcs0 for hang 

[Desktop-packages] [Bug 1862865] Card0.Codecs.codec.2.txt

[Haw Loeung]

apport information

** Attachment added: "Card0.Codecs.codec.2.txt"
   
https://bugs.launchpad.net/bugs/1862865/+attachment/5328129/+files/Card0.Codecs.codec.2.txt

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

Title:
  i915 :00:02.0: Resetting rcs0 for stuck wait on rcs0

Status in linux package in Ubuntu:
  Confirmed
Status in mesa package in Ubuntu:
  Invalid
Status in linux source package in Focal:
  Confirmed
Status in mesa source package in Focal:
  Invalid

Bug description:
  Hi,

  Every now and again, my session locks up with the following logged:

  | i915 :00:02.0: Resetting rcs0 for hang on rcs0

  Most of the time, it recovers on it's own but sometimes locks up
  completely requring a reboot. When that happens this is logged:

  | Feb  2 10:37:23 dharkan kernel: [71018.593184] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:37:23 dharkan kernel: [71018.593993] [drm:gen8_reset_engines 
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL: 
0001}
  | Feb  2 10:37:23 dharkan kernel: [71018.594130] i915 :00:02.0: Resetting 
chip for hang on rcs0
  | Feb  2 10:37:23 dharkan kernel: [71018.595937] [drm:gen8_reset_engines 
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL: 
0001}
  | Feb  2 10:37:23 dharkan kernel: [71018.596728] [drm:gen8_reset_engines 
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL: 
0001}
  | Feb  2 10:37:28 dharkan kernel: [71022.816232] Asynchronous wait on fence 
i915:compiz[1495]:105ece timed out (hint:intel_atomic_commit_ready+0x0/0x54 
[i915])
  | Feb  2 10:37:31 dharkan kernel: [71026.593149] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:37:31 dharkan kernel: [71026.593958] [drm:gen8_reset_engines 
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL: 
0001}
  | Feb  2 10:37:31 dharkan kernel: [71026.596916] i915 :00:02.0: Resetting 
chip for hang on rcs0
  | Feb  2 10:37:31 dharkan kernel: [71026.598661] [drm:gen8_reset_engines 
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL: 
0001}
  | Feb  2 10:37:31 dharkan kernel: [71026.599391] [drm:gen8_reset_engines 
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL: 
0001}
  | Feb  2 10:37:35 dharkan kernel: [71030.592141] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:37:39 dharkan kernel: [71034.323140] GpuWatchdog[1860]: segfault 
at 0 ip 55689a4eb33d sp 7f69b674d700 error 6 in 
chrome[5568968fd000+6abe000]
  | Feb  2 10:37:39 dharkan kernel: [71034.323157] Code: 00 79 09 48 8b 7d a0 
e8 31 2c 72 fc 41 8b 85 00 01 00 00 85 c0 0f 84 ab 00 00 00 49 8b 45 00 4c 89 
ef be 01 00 00 00 ff 50 58  04 25 00 00 00 00 37 13 00 00 c6 05 61 3c 59 03 
01 80 bd 7f ff
  | Feb  2 10:37:43 dharkan kernel: [71038.592101] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:37:45 dharkan kernel: [71040.576093] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:37:47 dharkan kernel: [71042.592066] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:37:49 dharkan kernel: [71044.576075] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:37:51 dharkan kernel: [71046.592045] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:37:53 dharkan kernel: [71048.576098] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:37:55 dharkan kernel: [71050.592029] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:37:57 dharkan kernel: [71052.576037] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:37:59 dharkan kernel: [71054.592034] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:38:01 dharkan kernel: [71056.576021] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:38:03 dharkan kernel: [71058.592006] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:38:04 dharkan kernel: [71059.461584] GpuWatchdog[43507]: segfault 
at 0 ip 55ac6731833d sp 7fe71901e700 error 6 in 
chrome[55ac6372a000+6abe000]
  | Feb  2 10:38:04 dharkan kernel: [71059.461600] Code: 00 79 09 48 8b 7d a0 
e8 31 2c 72 fc 41 8b 85 00 01 00 00 85 c0 0f 84 ab 00 00 00 49 8b 45 00 4c 89 
ef be 01 00 00 00 ff 50 58  04 25 00 00 00 00 37 13 00 00 c6 05 61 3c 59 03 
01 80 bd 7f ff
  | Feb  2 10:38:05 dharkan kernel: [71060.575986] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:38:07 dharkan kernel: [71062.591982] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:38:09 dharkan kernel: [71064.575976] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:38:11 dharkan kernel: [71066.591956] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:38:13 dharkan kernel: [71068.575937] i915 :00:02.0: Resetting 

[Desktop-packages] [Bug 1862865] Lspci.txt

[Haw Loeung]

apport information

** Attachment added: "Lspci.txt"
   https://bugs.launchpad.net/bugs/1862865/+attachment/5328132/+files/Lspci.txt

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

Title:
  i915 :00:02.0: Resetting rcs0 for stuck wait on rcs0

Status in linux package in Ubuntu:
  Confirmed
Status in mesa package in Ubuntu:
  Invalid
Status in linux source package in Focal:
  Confirmed
Status in mesa source package in Focal:
  Invalid

Bug description:
  Hi,

  Every now and again, my session locks up with the following logged:

  | i915 :00:02.0: Resetting rcs0 for hang on rcs0

  Most of the time, it recovers on it's own but sometimes locks up
  completely requring a reboot. When that happens this is logged:

  | Feb  2 10:37:23 dharkan kernel: [71018.593184] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:37:23 dharkan kernel: [71018.593993] [drm:gen8_reset_engines 
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL: 
0001}
  | Feb  2 10:37:23 dharkan kernel: [71018.594130] i915 :00:02.0: Resetting 
chip for hang on rcs0
  | Feb  2 10:37:23 dharkan kernel: [71018.595937] [drm:gen8_reset_engines 
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL: 
0001}
  | Feb  2 10:37:23 dharkan kernel: [71018.596728] [drm:gen8_reset_engines 
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL: 
0001}
  | Feb  2 10:37:28 dharkan kernel: [71022.816232] Asynchronous wait on fence 
i915:compiz[1495]:105ece timed out (hint:intel_atomic_commit_ready+0x0/0x54 
[i915])
  | Feb  2 10:37:31 dharkan kernel: [71026.593149] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:37:31 dharkan kernel: [71026.593958] [drm:gen8_reset_engines 
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL: 
0001}
  | Feb  2 10:37:31 dharkan kernel: [71026.596916] i915 :00:02.0: Resetting 
chip for hang on rcs0
  | Feb  2 10:37:31 dharkan kernel: [71026.598661] [drm:gen8_reset_engines 
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL: 
0001}
  | Feb  2 10:37:31 dharkan kernel: [71026.599391] [drm:gen8_reset_engines 
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL: 
0001}
  | Feb  2 10:37:35 dharkan kernel: [71030.592141] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:37:39 dharkan kernel: [71034.323140] GpuWatchdog[1860]: segfault 
at 0 ip 55689a4eb33d sp 7f69b674d700 error 6 in 
chrome[5568968fd000+6abe000]
  | Feb  2 10:37:39 dharkan kernel: [71034.323157] Code: 00 79 09 48 8b 7d a0 
e8 31 2c 72 fc 41 8b 85 00 01 00 00 85 c0 0f 84 ab 00 00 00 49 8b 45 00 4c 89 
ef be 01 00 00 00 ff 50 58  04 25 00 00 00 00 37 13 00 00 c6 05 61 3c 59 03 
01 80 bd 7f ff
  | Feb  2 10:37:43 dharkan kernel: [71038.592101] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:37:45 dharkan kernel: [71040.576093] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:37:47 dharkan kernel: [71042.592066] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:37:49 dharkan kernel: [71044.576075] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:37:51 dharkan kernel: [71046.592045] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:37:53 dharkan kernel: [71048.576098] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:37:55 dharkan kernel: [71050.592029] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:37:57 dharkan kernel: [71052.576037] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:37:59 dharkan kernel: [71054.592034] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:38:01 dharkan kernel: [71056.576021] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:38:03 dharkan kernel: [71058.592006] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:38:04 dharkan kernel: [71059.461584] GpuWatchdog[43507]: segfault 
at 0 ip 55ac6731833d sp 7fe71901e700 error 6 in 
chrome[55ac6372a000+6abe000]
  | Feb  2 10:38:04 dharkan kernel: [71059.461600] Code: 00 79 09 48 8b 7d a0 
e8 31 2c 72 fc 41 8b 85 00 01 00 00 85 c0 0f 84 ab 00 00 00 49 8b 45 00 4c 89 
ef be 01 00 00 00 ff 50 58  04 25 00 00 00 00 37 13 00 00 c6 05 61 3c 59 03 
01 80 bd 7f ff
  | Feb  2 10:38:05 dharkan kernel: [71060.575986] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:38:07 dharkan kernel: [71062.591982] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:38:09 dharkan kernel: [71064.575976] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:38:11 dharkan kernel: [71066.591956] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:38:13 dharkan kernel: [71068.575937] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  

[Desktop-packages] [Bug 1862865] IwConfig.txt

[Haw Loeung]

apport information

** Attachment added: "IwConfig.txt"
   
https://bugs.launchpad.net/bugs/1862865/+attachment/5328131/+files/IwConfig.txt

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

Title:
  i915 :00:02.0: Resetting rcs0 for stuck wait on rcs0

Status in linux package in Ubuntu:
  Confirmed
Status in mesa package in Ubuntu:
  Invalid
Status in linux source package in Focal:
  Confirmed
Status in mesa source package in Focal:
  Invalid

Bug description:
  Hi,

  Every now and again, my session locks up with the following logged:

  | i915 :00:02.0: Resetting rcs0 for hang on rcs0

  Most of the time, it recovers on it's own but sometimes locks up
  completely requring a reboot. When that happens this is logged:

  | Feb  2 10:37:23 dharkan kernel: [71018.593184] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:37:23 dharkan kernel: [71018.593993] [drm:gen8_reset_engines 
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL: 
0001}
  | Feb  2 10:37:23 dharkan kernel: [71018.594130] i915 :00:02.0: Resetting 
chip for hang on rcs0
  | Feb  2 10:37:23 dharkan kernel: [71018.595937] [drm:gen8_reset_engines 
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL: 
0001}
  | Feb  2 10:37:23 dharkan kernel: [71018.596728] [drm:gen8_reset_engines 
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL: 
0001}
  | Feb  2 10:37:28 dharkan kernel: [71022.816232] Asynchronous wait on fence 
i915:compiz[1495]:105ece timed out (hint:intel_atomic_commit_ready+0x0/0x54 
[i915])
  | Feb  2 10:37:31 dharkan kernel: [71026.593149] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:37:31 dharkan kernel: [71026.593958] [drm:gen8_reset_engines 
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL: 
0001}
  | Feb  2 10:37:31 dharkan kernel: [71026.596916] i915 :00:02.0: Resetting 
chip for hang on rcs0
  | Feb  2 10:37:31 dharkan kernel: [71026.598661] [drm:gen8_reset_engines 
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL: 
0001}
  | Feb  2 10:37:31 dharkan kernel: [71026.599391] [drm:gen8_reset_engines 
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL: 
0001}
  | Feb  2 10:37:35 dharkan kernel: [71030.592141] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:37:39 dharkan kernel: [71034.323140] GpuWatchdog[1860]: segfault 
at 0 ip 55689a4eb33d sp 7f69b674d700 error 6 in 
chrome[5568968fd000+6abe000]
  | Feb  2 10:37:39 dharkan kernel: [71034.323157] Code: 00 79 09 48 8b 7d a0 
e8 31 2c 72 fc 41 8b 85 00 01 00 00 85 c0 0f 84 ab 00 00 00 49 8b 45 00 4c 89 
ef be 01 00 00 00 ff 50 58  04 25 00 00 00 00 37 13 00 00 c6 05 61 3c 59 03 
01 80 bd 7f ff
  | Feb  2 10:37:43 dharkan kernel: [71038.592101] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:37:45 dharkan kernel: [71040.576093] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:37:47 dharkan kernel: [71042.592066] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:37:49 dharkan kernel: [71044.576075] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:37:51 dharkan kernel: [71046.592045] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:37:53 dharkan kernel: [71048.576098] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:37:55 dharkan kernel: [71050.592029] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:37:57 dharkan kernel: [71052.576037] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:37:59 dharkan kernel: [71054.592034] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:38:01 dharkan kernel: [71056.576021] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:38:03 dharkan kernel: [71058.592006] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:38:04 dharkan kernel: [71059.461584] GpuWatchdog[43507]: segfault 
at 0 ip 55ac6731833d sp 7fe71901e700 error 6 in 
chrome[55ac6372a000+6abe000]
  | Feb  2 10:38:04 dharkan kernel: [71059.461600] Code: 00 79 09 48 8b 7d a0 
e8 31 2c 72 fc 41 8b 85 00 01 00 00 85 c0 0f 84 ab 00 00 00 49 8b 45 00 4c 89 
ef be 01 00 00 00 ff 50 58  04 25 00 00 00 00 37 13 00 00 c6 05 61 3c 59 03 
01 80 bd 7f ff
  | Feb  2 10:38:05 dharkan kernel: [71060.575986] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:38:07 dharkan kernel: [71062.591982] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:38:09 dharkan kernel: [71064.575976] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:38:11 dharkan kernel: [71066.591956] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:38:13 dharkan kernel: [71068.575937] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  

[Desktop-packages] [Bug 1862865] CurrentDmesg.txt

[Haw Loeung]

apport information

** Attachment added: "CurrentDmesg.txt"
   
https://bugs.launchpad.net/bugs/1862865/+attachment/5328130/+files/CurrentDmesg.txt

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

Title:
  i915 :00:02.0: Resetting rcs0 for stuck wait on rcs0

Status in linux package in Ubuntu:
  Confirmed
Status in mesa package in Ubuntu:
  Invalid
Status in linux source package in Focal:
  Confirmed
Status in mesa source package in Focal:
  Invalid

Bug description:
  Hi,

  Every now and again, my session locks up with the following logged:

  | i915 :00:02.0: Resetting rcs0 for hang on rcs0

  Most of the time, it recovers on it's own but sometimes locks up
  completely requring a reboot. When that happens this is logged:

  | Feb  2 10:37:23 dharkan kernel: [71018.593184] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:37:23 dharkan kernel: [71018.593993] [drm:gen8_reset_engines 
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL: 
0001}
  | Feb  2 10:37:23 dharkan kernel: [71018.594130] i915 :00:02.0: Resetting 
chip for hang on rcs0
  | Feb  2 10:37:23 dharkan kernel: [71018.595937] [drm:gen8_reset_engines 
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL: 
0001}
  | Feb  2 10:37:23 dharkan kernel: [71018.596728] [drm:gen8_reset_engines 
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL: 
0001}
  | Feb  2 10:37:28 dharkan kernel: [71022.816232] Asynchronous wait on fence 
i915:compiz[1495]:105ece timed out (hint:intel_atomic_commit_ready+0x0/0x54 
[i915])
  | Feb  2 10:37:31 dharkan kernel: [71026.593149] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:37:31 dharkan kernel: [71026.593958] [drm:gen8_reset_engines 
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL: 
0001}
  | Feb  2 10:37:31 dharkan kernel: [71026.596916] i915 :00:02.0: Resetting 
chip for hang on rcs0
  | Feb  2 10:37:31 dharkan kernel: [71026.598661] [drm:gen8_reset_engines 
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL: 
0001}
  | Feb  2 10:37:31 dharkan kernel: [71026.599391] [drm:gen8_reset_engines 
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL: 
0001}
  | Feb  2 10:37:35 dharkan kernel: [71030.592141] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:37:39 dharkan kernel: [71034.323140] GpuWatchdog[1860]: segfault 
at 0 ip 55689a4eb33d sp 7f69b674d700 error 6 in 
chrome[5568968fd000+6abe000]
  | Feb  2 10:37:39 dharkan kernel: [71034.323157] Code: 00 79 09 48 8b 7d a0 
e8 31 2c 72 fc 41 8b 85 00 01 00 00 85 c0 0f 84 ab 00 00 00 49 8b 45 00 4c 89 
ef be 01 00 00 00 ff 50 58  04 25 00 00 00 00 37 13 00 00 c6 05 61 3c 59 03 
01 80 bd 7f ff
  | Feb  2 10:37:43 dharkan kernel: [71038.592101] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:37:45 dharkan kernel: [71040.576093] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:37:47 dharkan kernel: [71042.592066] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:37:49 dharkan kernel: [71044.576075] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:37:51 dharkan kernel: [71046.592045] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:37:53 dharkan kernel: [71048.576098] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:37:55 dharkan kernel: [71050.592029] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:37:57 dharkan kernel: [71052.576037] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:37:59 dharkan kernel: [71054.592034] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:38:01 dharkan kernel: [71056.576021] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:38:03 dharkan kernel: [71058.592006] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:38:04 dharkan kernel: [71059.461584] GpuWatchdog[43507]: segfault 
at 0 ip 55ac6731833d sp 7fe71901e700 error 6 in 
chrome[55ac6372a000+6abe000]
  | Feb  2 10:38:04 dharkan kernel: [71059.461600] Code: 00 79 09 48 8b 7d a0 
e8 31 2c 72 fc 41 8b 85 00 01 00 00 85 c0 0f 84 ab 00 00 00 49 8b 45 00 4c 89 
ef be 01 00 00 00 ff 50 58  04 25 00 00 00 00 37 13 00 00 c6 05 61 3c 59 03 
01 80 bd 7f ff
  | Feb  2 10:38:05 dharkan kernel: [71060.575986] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:38:07 dharkan kernel: [71062.591982] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:38:09 dharkan kernel: [71064.575976] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:38:11 dharkan kernel: [71066.591956] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:38:13 dharkan kernel: [71068.575937] i915 :00:02.0: Resetting 
rcs0 for hang 

[Desktop-packages] [Bug 1862865] Card0.Codecs.codec.0.txt

[Haw Loeung]

apport information

** Attachment added: "Card0.Codecs.codec.0.txt"
   
https://bugs.launchpad.net/bugs/1862865/+attachment/5328128/+files/Card0.Codecs.codec.0.txt

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

Title:
  i915 :00:02.0: Resetting rcs0 for stuck wait on rcs0

Status in linux package in Ubuntu:
  Confirmed
Status in mesa package in Ubuntu:
  Invalid
Status in linux source package in Focal:
  Confirmed
Status in mesa source package in Focal:
  Invalid

Bug description:
  Hi,

  Every now and again, my session locks up with the following logged:

  | i915 :00:02.0: Resetting rcs0 for hang on rcs0

  Most of the time, it recovers on it's own but sometimes locks up
  completely requring a reboot. When that happens this is logged:

  | Feb  2 10:37:23 dharkan kernel: [71018.593184] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:37:23 dharkan kernel: [71018.593993] [drm:gen8_reset_engines 
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL: 
0001}
  | Feb  2 10:37:23 dharkan kernel: [71018.594130] i915 :00:02.0: Resetting 
chip for hang on rcs0
  | Feb  2 10:37:23 dharkan kernel: [71018.595937] [drm:gen8_reset_engines 
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL: 
0001}
  | Feb  2 10:37:23 dharkan kernel: [71018.596728] [drm:gen8_reset_engines 
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL: 
0001}
  | Feb  2 10:37:28 dharkan kernel: [71022.816232] Asynchronous wait on fence 
i915:compiz[1495]:105ece timed out (hint:intel_atomic_commit_ready+0x0/0x54 
[i915])
  | Feb  2 10:37:31 dharkan kernel: [71026.593149] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:37:31 dharkan kernel: [71026.593958] [drm:gen8_reset_engines 
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL: 
0001}
  | Feb  2 10:37:31 dharkan kernel: [71026.596916] i915 :00:02.0: Resetting 
chip for hang on rcs0
  | Feb  2 10:37:31 dharkan kernel: [71026.598661] [drm:gen8_reset_engines 
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL: 
0001}
  | Feb  2 10:37:31 dharkan kernel: [71026.599391] [drm:gen8_reset_engines 
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL: 
0001}
  | Feb  2 10:37:35 dharkan kernel: [71030.592141] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:37:39 dharkan kernel: [71034.323140] GpuWatchdog[1860]: segfault 
at 0 ip 55689a4eb33d sp 7f69b674d700 error 6 in 
chrome[5568968fd000+6abe000]
  | Feb  2 10:37:39 dharkan kernel: [71034.323157] Code: 00 79 09 48 8b 7d a0 
e8 31 2c 72 fc 41 8b 85 00 01 00 00 85 c0 0f 84 ab 00 00 00 49 8b 45 00 4c 89 
ef be 01 00 00 00 ff 50 58  04 25 00 00 00 00 37 13 00 00 c6 05 61 3c 59 03 
01 80 bd 7f ff
  | Feb  2 10:37:43 dharkan kernel: [71038.592101] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:37:45 dharkan kernel: [71040.576093] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:37:47 dharkan kernel: [71042.592066] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:37:49 dharkan kernel: [71044.576075] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:37:51 dharkan kernel: [71046.592045] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:37:53 dharkan kernel: [71048.576098] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:37:55 dharkan kernel: [71050.592029] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:37:57 dharkan kernel: [71052.576037] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:37:59 dharkan kernel: [71054.592034] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:38:01 dharkan kernel: [71056.576021] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:38:03 dharkan kernel: [71058.592006] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:38:04 dharkan kernel: [71059.461584] GpuWatchdog[43507]: segfault 
at 0 ip 55ac6731833d sp 7fe71901e700 error 6 in 
chrome[55ac6372a000+6abe000]
  | Feb  2 10:38:04 dharkan kernel: [71059.461600] Code: 00 79 09 48 8b 7d a0 
e8 31 2c 72 fc 41 8b 85 00 01 00 00 85 c0 0f 84 ab 00 00 00 49 8b 45 00 4c 89 
ef be 01 00 00 00 ff 50 58  04 25 00 00 00 00 37 13 00 00 c6 05 61 3c 59 03 
01 80 bd 7f ff
  | Feb  2 10:38:05 dharkan kernel: [71060.575986] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:38:07 dharkan kernel: [71062.591982] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:38:09 dharkan kernel: [71064.575976] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:38:11 dharkan kernel: [71066.591956] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:38:13 dharkan kernel: [71068.575937] i915 :00:02.0: Resetting 

[Desktop-packages] [Bug 1862865] Lsusb-v.txt

[Haw Loeung]

apport information

** Attachment added: "Lsusb-v.txt"
   
https://bugs.launchpad.net/bugs/1862865/+attachment/5328133/+files/Lsusb-v.txt

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

Title:
  i915 :00:02.0: Resetting rcs0 for stuck wait on rcs0

Status in linux package in Ubuntu:
  Confirmed
Status in mesa package in Ubuntu:
  Invalid
Status in linux source package in Focal:
  Confirmed
Status in mesa source package in Focal:
  Invalid

Bug description:
  Hi,

  Every now and again, my session locks up with the following logged:

  | i915 :00:02.0: Resetting rcs0 for hang on rcs0

  Most of the time, it recovers on it's own but sometimes locks up
  completely requring a reboot. When that happens this is logged:

  | Feb  2 10:37:23 dharkan kernel: [71018.593184] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:37:23 dharkan kernel: [71018.593993] [drm:gen8_reset_engines 
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL: 
0001}
  | Feb  2 10:37:23 dharkan kernel: [71018.594130] i915 :00:02.0: Resetting 
chip for hang on rcs0
  | Feb  2 10:37:23 dharkan kernel: [71018.595937] [drm:gen8_reset_engines 
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL: 
0001}
  | Feb  2 10:37:23 dharkan kernel: [71018.596728] [drm:gen8_reset_engines 
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL: 
0001}
  | Feb  2 10:37:28 dharkan kernel: [71022.816232] Asynchronous wait on fence 
i915:compiz[1495]:105ece timed out (hint:intel_atomic_commit_ready+0x0/0x54 
[i915])
  | Feb  2 10:37:31 dharkan kernel: [71026.593149] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:37:31 dharkan kernel: [71026.593958] [drm:gen8_reset_engines 
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL: 
0001}
  | Feb  2 10:37:31 dharkan kernel: [71026.596916] i915 :00:02.0: Resetting 
chip for hang on rcs0
  | Feb  2 10:37:31 dharkan kernel: [71026.598661] [drm:gen8_reset_engines 
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL: 
0001}
  | Feb  2 10:37:31 dharkan kernel: [71026.599391] [drm:gen8_reset_engines 
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL: 
0001}
  | Feb  2 10:37:35 dharkan kernel: [71030.592141] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:37:39 dharkan kernel: [71034.323140] GpuWatchdog[1860]: segfault 
at 0 ip 55689a4eb33d sp 7f69b674d700 error 6 in 
chrome[5568968fd000+6abe000]
  | Feb  2 10:37:39 dharkan kernel: [71034.323157] Code: 00 79 09 48 8b 7d a0 
e8 31 2c 72 fc 41 8b 85 00 01 00 00 85 c0 0f 84 ab 00 00 00 49 8b 45 00 4c 89 
ef be 01 00 00 00 ff 50 58  04 25 00 00 00 00 37 13 00 00 c6 05 61 3c 59 03 
01 80 bd 7f ff
  | Feb  2 10:37:43 dharkan kernel: [71038.592101] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:37:45 dharkan kernel: [71040.576093] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:37:47 dharkan kernel: [71042.592066] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:37:49 dharkan kernel: [71044.576075] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:37:51 dharkan kernel: [71046.592045] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:37:53 dharkan kernel: [71048.576098] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:37:55 dharkan kernel: [71050.592029] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:37:57 dharkan kernel: [71052.576037] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:37:59 dharkan kernel: [71054.592034] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:38:01 dharkan kernel: [71056.576021] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:38:03 dharkan kernel: [71058.592006] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:38:04 dharkan kernel: [71059.461584] GpuWatchdog[43507]: segfault 
at 0 ip 55ac6731833d sp 7fe71901e700 error 6 in 
chrome[55ac6372a000+6abe000]
  | Feb  2 10:38:04 dharkan kernel: [71059.461600] Code: 00 79 09 48 8b 7d a0 
e8 31 2c 72 fc 41 8b 85 00 01 00 00 85 c0 0f 84 ab 00 00 00 49 8b 45 00 4c 89 
ef be 01 00 00 00 ff 50 58  04 25 00 00 00 00 37 13 00 00 c6 05 61 3c 59 03 
01 80 bd 7f ff
  | Feb  2 10:38:05 dharkan kernel: [71060.575986] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:38:07 dharkan kernel: [71062.591982] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:38:09 dharkan kernel: [71064.575976] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:38:11 dharkan kernel: [71066.591956] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:38:13 dharkan kernel: [71068.575937] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | 

[Desktop-packages] [Bug 1862865] ProcCpuinfo.txt

[Haw Loeung]

apport information

** Attachment added: "ProcCpuinfo.txt"
   
https://bugs.launchpad.net/bugs/1862865/+attachment/5328135/+files/ProcCpuinfo.txt

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

Title:
  i915 :00:02.0: Resetting rcs0 for stuck wait on rcs0

Status in linux package in Ubuntu:
  Confirmed
Status in mesa package in Ubuntu:
  Invalid
Status in linux source package in Focal:
  Confirmed
Status in mesa source package in Focal:
  Invalid

Bug description:
  Hi,

  Every now and again, my session locks up with the following logged:

  | i915 :00:02.0: Resetting rcs0 for hang on rcs0

  Most of the time, it recovers on it's own but sometimes locks up
  completely requring a reboot. When that happens this is logged:

  | Feb  2 10:37:23 dharkan kernel: [71018.593184] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:37:23 dharkan kernel: [71018.593993] [drm:gen8_reset_engines 
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL: 
0001}
  | Feb  2 10:37:23 dharkan kernel: [71018.594130] i915 :00:02.0: Resetting 
chip for hang on rcs0
  | Feb  2 10:37:23 dharkan kernel: [71018.595937] [drm:gen8_reset_engines 
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL: 
0001}
  | Feb  2 10:37:23 dharkan kernel: [71018.596728] [drm:gen8_reset_engines 
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL: 
0001}
  | Feb  2 10:37:28 dharkan kernel: [71022.816232] Asynchronous wait on fence 
i915:compiz[1495]:105ece timed out (hint:intel_atomic_commit_ready+0x0/0x54 
[i915])
  | Feb  2 10:37:31 dharkan kernel: [71026.593149] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:37:31 dharkan kernel: [71026.593958] [drm:gen8_reset_engines 
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL: 
0001}
  | Feb  2 10:37:31 dharkan kernel: [71026.596916] i915 :00:02.0: Resetting 
chip for hang on rcs0
  | Feb  2 10:37:31 dharkan kernel: [71026.598661] [drm:gen8_reset_engines 
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL: 
0001}
  | Feb  2 10:37:31 dharkan kernel: [71026.599391] [drm:gen8_reset_engines 
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL: 
0001}
  | Feb  2 10:37:35 dharkan kernel: [71030.592141] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:37:39 dharkan kernel: [71034.323140] GpuWatchdog[1860]: segfault 
at 0 ip 55689a4eb33d sp 7f69b674d700 error 6 in 
chrome[5568968fd000+6abe000]
  | Feb  2 10:37:39 dharkan kernel: [71034.323157] Code: 00 79 09 48 8b 7d a0 
e8 31 2c 72 fc 41 8b 85 00 01 00 00 85 c0 0f 84 ab 00 00 00 49 8b 45 00 4c 89 
ef be 01 00 00 00 ff 50 58  04 25 00 00 00 00 37 13 00 00 c6 05 61 3c 59 03 
01 80 bd 7f ff
  | Feb  2 10:37:43 dharkan kernel: [71038.592101] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:37:45 dharkan kernel: [71040.576093] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:37:47 dharkan kernel: [71042.592066] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:37:49 dharkan kernel: [71044.576075] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:37:51 dharkan kernel: [71046.592045] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:37:53 dharkan kernel: [71048.576098] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:37:55 dharkan kernel: [71050.592029] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:37:57 dharkan kernel: [71052.576037] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:37:59 dharkan kernel: [71054.592034] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:38:01 dharkan kernel: [71056.576021] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:38:03 dharkan kernel: [71058.592006] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:38:04 dharkan kernel: [71059.461584] GpuWatchdog[43507]: segfault 
at 0 ip 55ac6731833d sp 7fe71901e700 error 6 in 
chrome[55ac6372a000+6abe000]
  | Feb  2 10:38:04 dharkan kernel: [71059.461600] Code: 00 79 09 48 8b 7d a0 
e8 31 2c 72 fc 41 8b 85 00 01 00 00 85 c0 0f 84 ab 00 00 00 49 8b 45 00 4c 89 
ef be 01 00 00 00 ff 50 58  04 25 00 00 00 00 37 13 00 00 c6 05 61 3c 59 03 
01 80 bd 7f ff
  | Feb  2 10:38:05 dharkan kernel: [71060.575986] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:38:07 dharkan kernel: [71062.591982] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:38:09 dharkan kernel: [71064.575976] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:38:11 dharkan kernel: [71066.591956] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:38:13 dharkan kernel: [71068.575937] i915 :00:02.0: Resetting 
rcs0 for hang on 

[Desktop-packages] [Bug 1862865] CRDA.txt

[Haw Loeung]

apport information

** Attachment added: "CRDA.txt"
   https://bugs.launchpad.net/bugs/1862865/+attachment/5328127/+files/CRDA.txt

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

Title:
  i915 :00:02.0: Resetting rcs0 for stuck wait on rcs0

Status in linux package in Ubuntu:
  Confirmed
Status in mesa package in Ubuntu:
  Invalid
Status in linux source package in Focal:
  Confirmed
Status in mesa source package in Focal:
  Invalid

Bug description:
  Hi,

  Every now and again, my session locks up with the following logged:

  | i915 :00:02.0: Resetting rcs0 for hang on rcs0

  Most of the time, it recovers on it's own but sometimes locks up
  completely requring a reboot. When that happens this is logged:

  | Feb  2 10:37:23 dharkan kernel: [71018.593184] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:37:23 dharkan kernel: [71018.593993] [drm:gen8_reset_engines 
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL: 
0001}
  | Feb  2 10:37:23 dharkan kernel: [71018.594130] i915 :00:02.0: Resetting 
chip for hang on rcs0
  | Feb  2 10:37:23 dharkan kernel: [71018.595937] [drm:gen8_reset_engines 
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL: 
0001}
  | Feb  2 10:37:23 dharkan kernel: [71018.596728] [drm:gen8_reset_engines 
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL: 
0001}
  | Feb  2 10:37:28 dharkan kernel: [71022.816232] Asynchronous wait on fence 
i915:compiz[1495]:105ece timed out (hint:intel_atomic_commit_ready+0x0/0x54 
[i915])
  | Feb  2 10:37:31 dharkan kernel: [71026.593149] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:37:31 dharkan kernel: [71026.593958] [drm:gen8_reset_engines 
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL: 
0001}
  | Feb  2 10:37:31 dharkan kernel: [71026.596916] i915 :00:02.0: Resetting 
chip for hang on rcs0
  | Feb  2 10:37:31 dharkan kernel: [71026.598661] [drm:gen8_reset_engines 
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL: 
0001}
  | Feb  2 10:37:31 dharkan kernel: [71026.599391] [drm:gen8_reset_engines 
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL: 
0001}
  | Feb  2 10:37:35 dharkan kernel: [71030.592141] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:37:39 dharkan kernel: [71034.323140] GpuWatchdog[1860]: segfault 
at 0 ip 55689a4eb33d sp 7f69b674d700 error 6 in 
chrome[5568968fd000+6abe000]
  | Feb  2 10:37:39 dharkan kernel: [71034.323157] Code: 00 79 09 48 8b 7d a0 
e8 31 2c 72 fc 41 8b 85 00 01 00 00 85 c0 0f 84 ab 00 00 00 49 8b 45 00 4c 89 
ef be 01 00 00 00 ff 50 58  04 25 00 00 00 00 37 13 00 00 c6 05 61 3c 59 03 
01 80 bd 7f ff
  | Feb  2 10:37:43 dharkan kernel: [71038.592101] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:37:45 dharkan kernel: [71040.576093] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:37:47 dharkan kernel: [71042.592066] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:37:49 dharkan kernel: [71044.576075] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:37:51 dharkan kernel: [71046.592045] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:37:53 dharkan kernel: [71048.576098] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:37:55 dharkan kernel: [71050.592029] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:37:57 dharkan kernel: [71052.576037] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:37:59 dharkan kernel: [71054.592034] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:38:01 dharkan kernel: [71056.576021] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:38:03 dharkan kernel: [71058.592006] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:38:04 dharkan kernel: [71059.461584] GpuWatchdog[43507]: segfault 
at 0 ip 55ac6731833d sp 7fe71901e700 error 6 in 
chrome[55ac6372a000+6abe000]
  | Feb  2 10:38:04 dharkan kernel: [71059.461600] Code: 00 79 09 48 8b 7d a0 
e8 31 2c 72 fc 41 8b 85 00 01 00 00 85 c0 0f 84 ab 00 00 00 49 8b 45 00 4c 89 
ef be 01 00 00 00 ff 50 58  04 25 00 00 00 00 37 13 00 00 c6 05 61 3c 59 03 
01 80 bd 7f ff
  | Feb  2 10:38:05 dharkan kernel: [71060.575986] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:38:07 dharkan kernel: [71062.591982] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:38:09 dharkan kernel: [71064.575976] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:38:11 dharkan kernel: [71066.591956] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:38:13 dharkan kernel: [71068.575937] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 

[Desktop-packages] [Bug 1862865] Re: i915 0000:00:02.0: Resetting rcs0 for stuck wait on rcs0

[Haw Loeung]

apport information

** Tags added: apport-collected focal

** Description changed:

  Hi,
  
  Every now and again, my session locks up with the following logged:
  
  | i915 :00:02.0: Resetting rcs0 for hang on rcs0
  
  Most of the time, it recovers on it's own but sometimes locks up
  completely requring a reboot. When that happens this is logged:
  
  | Feb  2 10:37:23 dharkan kernel: [71018.593184] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:37:23 dharkan kernel: [71018.593993] [drm:gen8_reset_engines 
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL: 
0001}
  | Feb  2 10:37:23 dharkan kernel: [71018.594130] i915 :00:02.0: Resetting 
chip for hang on rcs0
  | Feb  2 10:37:23 dharkan kernel: [71018.595937] [drm:gen8_reset_engines 
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL: 
0001}
  | Feb  2 10:37:23 dharkan kernel: [71018.596728] [drm:gen8_reset_engines 
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL: 
0001}
  | Feb  2 10:37:28 dharkan kernel: [71022.816232] Asynchronous wait on fence 
i915:compiz[1495]:105ece timed out (hint:intel_atomic_commit_ready+0x0/0x54 
[i915])
  | Feb  2 10:37:31 dharkan kernel: [71026.593149] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:37:31 dharkan kernel: [71026.593958] [drm:gen8_reset_engines 
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL: 
0001}
  | Feb  2 10:37:31 dharkan kernel: [71026.596916] i915 :00:02.0: Resetting 
chip for hang on rcs0
  | Feb  2 10:37:31 dharkan kernel: [71026.598661] [drm:gen8_reset_engines 
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL: 
0001}
  | Feb  2 10:37:31 dharkan kernel: [71026.599391] [drm:gen8_reset_engines 
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL: 
0001}
  | Feb  2 10:37:35 dharkan kernel: [71030.592141] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:37:39 dharkan kernel: [71034.323140] GpuWatchdog[1860]: segfault 
at 0 ip 55689a4eb33d sp 7f69b674d700 error 6 in 
chrome[5568968fd000+6abe000]
  | Feb  2 10:37:39 dharkan kernel: [71034.323157] Code: 00 79 09 48 8b 7d a0 
e8 31 2c 72 fc 41 8b 85 00 01 00 00 85 c0 0f 84 ab 00 00 00 49 8b 45 00 4c 89 
ef be 01 00 00 00 ff 50 58  04 25 00 00 00 00 37 13 00 00 c6 05 61 3c 59 03 
01 80 bd 7f ff
  | Feb  2 10:37:43 dharkan kernel: [71038.592101] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:37:45 dharkan kernel: [71040.576093] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:37:47 dharkan kernel: [71042.592066] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:37:49 dharkan kernel: [71044.576075] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:37:51 dharkan kernel: [71046.592045] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:37:53 dharkan kernel: [71048.576098] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:37:55 dharkan kernel: [71050.592029] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:37:57 dharkan kernel: [71052.576037] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:37:59 dharkan kernel: [71054.592034] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:38:01 dharkan kernel: [71056.576021] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:38:03 dharkan kernel: [71058.592006] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:38:04 dharkan kernel: [71059.461584] GpuWatchdog[43507]: segfault 
at 0 ip 55ac6731833d sp 7fe71901e700 error 6 in 
chrome[55ac6372a000+6abe000]
  | Feb  2 10:38:04 dharkan kernel: [71059.461600] Code: 00 79 09 48 8b 7d a0 
e8 31 2c 72 fc 41 8b 85 00 01 00 00 85 c0 0f 84 ab 00 00 00 49 8b 45 00 4c 89 
ef be 01 00 00 00 ff 50 58  04 25 00 00 00 00 37 13 00 00 c6 05 61 3c 59 03 
01 80 bd 7f ff
  | Feb  2 10:38:05 dharkan kernel: [71060.575986] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:38:07 dharkan kernel: [71062.591982] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:38:09 dharkan kernel: [71064.575976] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:38:11 dharkan kernel: [71066.591956] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:38:13 dharkan kernel: [71068.575937] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:38:15 dharkan kernel: [71070.591932] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:38:17 dharkan kernel: [71072.575930] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:38:19 dharkan kernel: [71074.591922] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:38:21 dharkan kernel: [71076.575911] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:38:23 dharkan kernel: [71078.591901] i915 :00:02.0: Resetting 

[Desktop-packages] [Bug 1862865] Re: i915 0000:00:02.0: Resetting rcs0 for stuck wait on rcs0

[Haw Loeung]

| 00:02.0 VGA compatible controller: Intel Corporation HD Graphics 620 (rev 02) 
(prog-if 00 [VGA controller])
| Subsystem: Lenovo ThinkPad X1 Carbon 5th Gen

Linux 5.4.0-9.12


** Also affects: linux-meta-5.4 (Ubuntu)
   Importance: Undecided
   Status: New

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

** Also affects: mesa (Ubuntu Focal)
   Importance: Undecided
   Status: Invalid

** Also affects: linux-meta-5.4 (Ubuntu Focal)
   Importance: Undecided
   Status: New

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

Title:
  i915 :00:02.0: Resetting rcs0 for stuck wait on rcs0

Status in linux-meta-5.4 package in Ubuntu:
  New
Status in mesa package in Ubuntu:
  Invalid
Status in linux-meta-5.4 source package in Focal:
  New
Status in mesa source package in Focal:
  Invalid

Bug description:
  Hi,

  Every now and again, my session locks up with the following logged:

  | i915 :00:02.0: Resetting rcs0 for hang on rcs0

  Most of the time, it recovers on it's own but sometimes locks up
  completely requring a reboot. When that happens this is logged:

  | Feb  2 10:37:23 dharkan kernel: [71018.593184] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:37:23 dharkan kernel: [71018.593993] [drm:gen8_reset_engines 
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL: 
0001}
  | Feb  2 10:37:23 dharkan kernel: [71018.594130] i915 :00:02.0: Resetting 
chip for hang on rcs0
  | Feb  2 10:37:23 dharkan kernel: [71018.595937] [drm:gen8_reset_engines 
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL: 
0001}
  | Feb  2 10:37:23 dharkan kernel: [71018.596728] [drm:gen8_reset_engines 
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL: 
0001}
  | Feb  2 10:37:28 dharkan kernel: [71022.816232] Asynchronous wait on fence 
i915:compiz[1495]:105ece timed out (hint:intel_atomic_commit_ready+0x0/0x54 
[i915])
  | Feb  2 10:37:31 dharkan kernel: [71026.593149] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:37:31 dharkan kernel: [71026.593958] [drm:gen8_reset_engines 
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL: 
0001}
  | Feb  2 10:37:31 dharkan kernel: [71026.596916] i915 :00:02.0: Resetting 
chip for hang on rcs0
  | Feb  2 10:37:31 dharkan kernel: [71026.598661] [drm:gen8_reset_engines 
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL: 
0001}
  | Feb  2 10:37:31 dharkan kernel: [71026.599391] [drm:gen8_reset_engines 
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL: 
0001}
  | Feb  2 10:37:35 dharkan kernel: [71030.592141] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:37:39 dharkan kernel: [71034.323140] GpuWatchdog[1860]: segfault 
at 0 ip 55689a4eb33d sp 7f69b674d700 error 6 in 
chrome[5568968fd000+6abe000]
  | Feb  2 10:37:39 dharkan kernel: [71034.323157] Code: 00 79 09 48 8b 7d a0 
e8 31 2c 72 fc 41 8b 85 00 01 00 00 85 c0 0f 84 ab 00 00 00 49 8b 45 00 4c 89 
ef be 01 00 00 00 ff 50 58  04 25 00 00 00 00 37 13 00 00 c6 05 61 3c 59 03 
01 80 bd 7f ff
  | Feb  2 10:37:43 dharkan kernel: [71038.592101] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:37:45 dharkan kernel: [71040.576093] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:37:47 dharkan kernel: [71042.592066] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:37:49 dharkan kernel: [71044.576075] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:37:51 dharkan kernel: [71046.592045] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:37:53 dharkan kernel: [71048.576098] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:37:55 dharkan kernel: [71050.592029] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:37:57 dharkan kernel: [71052.576037] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:37:59 dharkan kernel: [71054.592034] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:38:01 dharkan kernel: [71056.576021] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:38:03 dharkan kernel: [71058.592006] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:38:04 dharkan kernel: [71059.461584] GpuWatchdog[43507]: segfault 
at 0 ip 55ac6731833d sp 7fe71901e700 error 6 in 
chrome[55ac6372a000+6abe000]
  | Feb  2 10:38:04 dharkan kernel: [71059.461600] Code: 00 79 09 48 8b 7d a0 
e8 31 2c 72 fc 41 8b 85 00 01 00 00 85 c0 0f 84 ab 00 00 00 49 8b 45 00 4c 89 
ef be 01 00 00 00 ff 50 58  04 25 00 00 00 00 37 13 00 00 c6 05 61 3c 59 03 
01 80 bd 7f ff
  | Feb  2 10:38:05 dharkan kernel: [71060.575986] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:38:07 dharkan kernel: 

[Desktop-packages] [Bug 1862865] [NEW] i915 0000:00:02.0: Resetting rcs0 for stuck wait on rcs0

[Haw Loeung]

Public bug reported:

Hi,

Every now and again, my session locks up with the following logged:

| i915 :00:02.0: Resetting rcs0 for hang on rcs0

Most of the time, it recovers on it's own but sometimes locks up
completely requring a reboot. When that happens this is logged:

| Feb  2 10:37:23 dharkan kernel: [71018.593184] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
| Feb  2 10:37:23 dharkan kernel: [71018.593993] [drm:gen8_reset_engines 
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL: 
0001}
| Feb  2 10:37:23 dharkan kernel: [71018.594130] i915 :00:02.0: Resetting 
chip for hang on rcs0
| Feb  2 10:37:23 dharkan kernel: [71018.595937] [drm:gen8_reset_engines 
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL: 
0001}
| Feb  2 10:37:23 dharkan kernel: [71018.596728] [drm:gen8_reset_engines 
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL: 
0001}
| Feb  2 10:37:28 dharkan kernel: [71022.816232] Asynchronous wait on fence 
i915:compiz[1495]:105ece timed out (hint:intel_atomic_commit_ready+0x0/0x54 
[i915])
| Feb  2 10:37:31 dharkan kernel: [71026.593149] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
| Feb  2 10:37:31 dharkan kernel: [71026.593958] [drm:gen8_reset_engines 
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL: 
0001}
| Feb  2 10:37:31 dharkan kernel: [71026.596916] i915 :00:02.0: Resetting 
chip for hang on rcs0
| Feb  2 10:37:31 dharkan kernel: [71026.598661] [drm:gen8_reset_engines 
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL: 
0001}
| Feb  2 10:37:31 dharkan kernel: [71026.599391] [drm:gen8_reset_engines 
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL: 
0001}
| Feb  2 10:37:35 dharkan kernel: [71030.592141] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
| Feb  2 10:37:39 dharkan kernel: [71034.323140] GpuWatchdog[1860]: segfault at 
0 ip 55689a4eb33d sp 7f69b674d700 error 6 in 
chrome[5568968fd000+6abe000]
| Feb  2 10:37:39 dharkan kernel: [71034.323157] Code: 00 79 09 48 8b 7d a0 e8 
31 2c 72 fc 41 8b 85 00 01 00 00 85 c0 0f 84 ab 00 00 00 49 8b 45 00 4c 89 ef 
be 01 00 00 00 ff 50 58  04 25 00 00 00 00 37 13 00 00 c6 05 61 3c 59 03 01 
80 bd 7f ff
| Feb  2 10:37:43 dharkan kernel: [71038.592101] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
| Feb  2 10:37:45 dharkan kernel: [71040.576093] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
| Feb  2 10:37:47 dharkan kernel: [71042.592066] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
| Feb  2 10:37:49 dharkan kernel: [71044.576075] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
| Feb  2 10:37:51 dharkan kernel: [71046.592045] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
| Feb  2 10:37:53 dharkan kernel: [71048.576098] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
| Feb  2 10:37:55 dharkan kernel: [71050.592029] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
| Feb  2 10:37:57 dharkan kernel: [71052.576037] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
| Feb  2 10:37:59 dharkan kernel: [71054.592034] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
| Feb  2 10:38:01 dharkan kernel: [71056.576021] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
| Feb  2 10:38:03 dharkan kernel: [71058.592006] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
| Feb  2 10:38:04 dharkan kernel: [71059.461584] GpuWatchdog[43507]: segfault 
at 0 ip 55ac6731833d sp 7fe71901e700 error 6 in 
chrome[55ac6372a000+6abe000]
| Feb  2 10:38:04 dharkan kernel: [71059.461600] Code: 00 79 09 48 8b 7d a0 e8 
31 2c 72 fc 41 8b 85 00 01 00 00 85 c0 0f 84 ab 00 00 00 49 8b 45 00 4c 89 ef 
be 01 00 00 00 ff 50 58  04 25 00 00 00 00 37 13 00 00 c6 05 61 3c 59 03 01 
80 bd 7f ff
| Feb  2 10:38:05 dharkan kernel: [71060.575986] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
| Feb  2 10:38:07 dharkan kernel: [71062.591982] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
| Feb  2 10:38:09 dharkan kernel: [71064.575976] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
| Feb  2 10:38:11 dharkan kernel: [71066.591956] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
| Feb  2 10:38:13 dharkan kernel: [71068.575937] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
| Feb  2 10:38:15 dharkan kernel: [71070.591932] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
| Feb  2 10:38:17 dharkan kernel: [71072.575930] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
| Feb  2 10:38:19 dharkan kernel: [71074.591922] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
| Feb  2 10:38:21 dharkan kernel: [71076.575911] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
| Feb  2 10:38:23 dharkan kernel: [71078.591901] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
| Feb  2 10:38:25 dharkan kernel: [71080.575883] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
| Feb  2 10:38:27 dharkan 

[Desktop-packages] [Bug 1862062] [NEW] [snap] Missing canberra-gtk-module?

[Haw Loeung]

Public bug reported:

Hi,

Using the chromium snap, when starting up, it complains about missing
canberra-gtk-module:

| Gtk-Message: 07:22:05.092: Failed to load module "canberra-gtk-module"
| Gtk-Message: 07:22:05.094: Failed to load module "canberra-gtk-module"

Should this be bundled with the snap?

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


** Tags: snap

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

Title:
  [snap] Missing canberra-gtk-module?

Status in chromium-browser package in Ubuntu:
  New

Bug description:
  Hi,

  Using the chromium snap, when starting up, it complains about missing
  canberra-gtk-module:

  | Gtk-Message: 07:22:05.092: Failed to load module "canberra-gtk-module"
  | Gtk-Message: 07:22:05.094: Failed to load module "canberra-gtk-module"

  Should this be bundled with the snap?

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

-- 
Mailing list: https://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 1861045] [NEW] Snap refresh causes various apparmor DENIED and weirdness

[Haw Loeung]

Also lose any changes such as new tabs/sites opened or closed.

Maybe .config needs to move to ~/snap/chromium/common instead of being
copied around between snap updates.

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

Title:
  Snap refresh causes various apparmor DENIED and weirdness

Status in chromium-browser package in Ubuntu:
  New

Bug description:
  Hi,

  chromium installed from the snap refreshed earlier this morning:

  | refresh-date: today at 08:47 AEDT
  | channels:
  |   stable:79.0.3945.130 2020-01-27 (1005) 159MB -
  | installed:   79.0.3945.130(1005) 159MB -

  Unfortunately, when it refreshed, it caused various weirdness -
  default blank tab not showing commonly visited sites, etc.

  Looking into it, it seems to be related to a bunch of apparmor DENIED.
  Two of the important ones, I think which is causing what I was seeing
  is below:

  | [180760.541231] audit: type=1400 audit(1580167457.220:12680): 
apparmor="DENIED" operation="open" profile="snap.chromium.chromium" 
name="/home/hloeung/snap/chromium/986/.config/chromium/Default/Cookies-journal" 
pid=12308 comm="ThreadPoolForeg" requested_mask="wc" denied_mask="wc" 
fsuid=3134 ouid=3134
  | [180765.220924] audit: type=1400 audit(1580167461.900:12706): 
apparmor="DENIED" operation="truncate" profile="snap.chromium.chromium" 
name="/home/hloeung/snap/chromium/986/.config/chromium/Default/History-journal" 
pid=12278 comm="Chrome_HistoryT" requested_mask="w" denied_mask="w" fsuid=3134 
ouid=3134

  Where 986 was the previous snap release version and now 1005.
  Restarting chromium fixed this but it would be nice to not have to
  restart during my working day and being logged out of various places
  (cookie policy set to clear on quit).

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

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

[Desktop-packages] [Bug 1861045] [NEW] Snap refresh causes various apparmor DENIED and weirdness

[Haw Loeung]

Public bug reported:

Hi,

chromium installed from the snap refreshed earlier this morning:

| refresh-date: today at 08:47 AEDT
| channels:
|   stable:79.0.3945.130 2020-01-27 (1005) 159MB -
| installed:   79.0.3945.130(1005) 159MB -

Unfortunately, when it refreshed, it caused various weirdness - default
blank tab not showing commonly visited sites, etc.

Looking into it, it seems to be related to a bunch of apparmor DENIED.
Two of the important ones, I think which is causing what I was seeing is
below:

| [180760.541231] audit: type=1400 audit(1580167457.220:12680): 
apparmor="DENIED" operation="open" profile="snap.chromium.chromium" 
name="/home/hloeung/snap/chromium/986/.config/chromium/Default/Cookies-journal" 
pid=12308 comm="ThreadPoolForeg" requested_mask="wc" denied_mask="wc" 
fsuid=3134 ouid=3134
| [180765.220924] audit: type=1400 audit(1580167461.900:12706): 
apparmor="DENIED" operation="truncate" profile="snap.chromium.chromium" 
name="/home/hloeung/snap/chromium/986/.config/chromium/Default/History-journal" 
pid=12278 comm="Chrome_HistoryT" requested_mask="w" denied_mask="w" fsuid=3134 
ouid=3134

Where 986 was the previous snap release version and now 1005. Restarting
chromium fixed this but it would be nice to not have to restart during
my working day and being logged out of various places (cookie policy set
to clear on quit).

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

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

Title:
  Snap refresh causes various apparmor DENIED and weirdness

Status in chromium-browser package in Ubuntu:
  New

Bug description:
  Hi,

  chromium installed from the snap refreshed earlier this morning:

  | refresh-date: today at 08:47 AEDT
  | channels:
  |   stable:79.0.3945.130 2020-01-27 (1005) 159MB -
  | installed:   79.0.3945.130(1005) 159MB -

  Unfortunately, when it refreshed, it caused various weirdness -
  default blank tab not showing commonly visited sites, etc.

  Looking into it, it seems to be related to a bunch of apparmor DENIED.
  Two of the important ones, I think which is causing what I was seeing
  is below:

  | [180760.541231] audit: type=1400 audit(1580167457.220:12680): 
apparmor="DENIED" operation="open" profile="snap.chromium.chromium" 
name="/home/hloeung/snap/chromium/986/.config/chromium/Default/Cookies-journal" 
pid=12308 comm="ThreadPoolForeg" requested_mask="wc" denied_mask="wc" 
fsuid=3134 ouid=3134
  | [180765.220924] audit: type=1400 audit(1580167461.900:12706): 
apparmor="DENIED" operation="truncate" profile="snap.chromium.chromium" 
name="/home/hloeung/snap/chromium/986/.config/chromium/Default/History-journal" 
pid=12278 comm="Chrome_HistoryT" requested_mask="w" denied_mask="w" fsuid=3134 
ouid=3134

  Where 986 was the previous snap release version and now 1005.
  Restarting chromium fixed this but it would be nice to not have to
  restart during my working day and being logged out of various places
  (cookie policy set to clear on quit).

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

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

[Desktop-packages] [Bug 1641380] Re: chromium-browser: ERR_CERTIFICATE_TRANSPARENCY_REQUIRED for Symantec certs

[Haw Loeung]

@Alberto, the link above has packages for Chromium 53 build with said
fixes.

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

Title:
  chromium-browser: ERR_CERTIFICATE_TRANSPARENCY_REQUIRED for Symantec
  certs

Status in chromium-browser package in Ubuntu:
  Fix Released

Bug description:
  Chromium browser in xenial no longer trusts Symantec issued
  certificates. See [1].

  1. https://bugs.chromium.org/p/chromium/issues/detail?id=664177

  Ubuntu release: 16.04
  chromium-browser: 53.0.2785.143-0ubuntu0.16.04.1.1254

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

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

[Desktop-packages] [Bug 1641380] Re: chromium-browser: ERR_CERTIFICATE_TRANSPARENCY_REQUIRED for Symantec certs

[Haw Loeung]

https://launchpad.net/~canonical-chromium-
builds/+archive/ubuntu/stage/+sourcepub/7137607/+listing-archive-extra

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

Title:
  chromium-browser: ERR_CERTIFICATE_TRANSPARENCY_REQUIRED for Symantec
  certs

Status in chromium-browser package in Ubuntu:
  Fix Released

Bug description:
  Chromium browser in xenial no longer trusts Symantec issued
  certificates. See [1].

  1. https://bugs.chromium.org/p/chromium/issues/detail?id=664177

  Ubuntu release: 16.04
  chromium-browser: 53.0.2785.143-0ubuntu0.16.04.1.1254

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

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

[Desktop-packages] [Bug 1641380] Re: chromium-browser: ERR_CERTIFICATE_TRANSPARENCY_REQUIRED for Symantec certs

[Haw Loeung]

@Oliver, it's actually https://codereview.chromium.org/2511583002.
Mostly this:

"In particular, certificates issued by Symantec fail to work if it's
more than 10 weeks after the build date"

There's a build in the ~canonical-chromium-builds PPA that has the fix:

Changelog

chromium-browser (53.0.2785.143-0ubuntu2.16.10.1323) yakkety-security;
urgency=medium

  * debian/patches/defang-ct-timebomb: backport TLS cert invalidity based
on build-time.  (LP: #1641380)

 -- Chad MILLER   Mon, 14 Nov 2016 10:06:44
-0500

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

Title:
  chromium-browser: ERR_CERTIFICATE_TRANSPARENCY_REQUIRED for Symantec
  certs

Status in chromium-browser package in Ubuntu:
  Fix Released

Bug description:
  Chromium browser in xenial no longer trusts Symantec issued
  certificates. See [1].

  1. https://bugs.chromium.org/p/chromium/issues/detail?id=664177

  Ubuntu release: 16.04
  chromium-browser: 53.0.2785.143-0ubuntu0.16.04.1.1254

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

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

[Desktop-packages] [Bug 1608359] Re: Power "When the lid is closed" setting does nothing

[Haw Loeung]

Who: NetworkManager (UID 0/root, PID 18098/NetworkManager)
What: sleep
 Why: NetworkManager needs to turn off networks
Mode: delay

 Who: hloeung (UID 3134/hloeung, PID 2995/unity-settings-)
What: handle-power-key:handle-suspend-key:handle-hibernate-key
 Why: GNOME handling keypresses
Mode: block

 Who: hloeung (UID 3134/hloeung, PID 2995/unity-settings-)
What: sleep
 Why: GNOME needs to lock the screen
Mode: delay

 Who: hloeung (UID 3134/hloeung, PID 2995/unity-settings-)
What: handle-lid-switch
 Why: Multiple displays attached
Mode: block

 Who: Unity (UID 3134/hloeung, PID 3062/compiz)
What: sleep
 Why: Unity needs to lock the screen
Mode: delay

5 inhibitors listed.

** Changed in: unity-control-center (Ubuntu)
   Status: Incomplete => New

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

Title:
  Power "When the lid is closed" setting does nothing

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

Bug description:
  Hi,

  Probably the opposite of LP: #1574120, after upgrading from Xenial to
  Yakkety (alpha 2), it seems my laptop automatically goes into suspend
  when the lid is closed even though I have "When the lid is closed"
  setting set to "Do nothing".

  I'm not sure what's changed, has the HandleLidSwitch default in logind
  changed? Also, any chance of fixing the "Power" setting so it
  correctly handles updating logind?

  I had to update /etc/systemd/logind.conf and add
  "HandleLidSwitch=ignore".

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

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

[Desktop-packages] [Bug 1608359] [NEW] Power "When the lid is closed" setting does nothing

[Haw Loeung]

Public bug reported:

Hi,

Probably the opposite of LP: #1574120, after upgrading from Xenial to
Yakkety (alpha 2), it seems my laptop automatically goes into suspend
when the lid is closed even though I have "When the lid is closed"
setting set to "Do nothing".

I'm not sure what's changed, has the HandleLidSwitch default in logind
changed? Also, any chance of fixing the "Power" setting so it correctly
handles updating logind?

I had to update /etc/systemd/logind.conf and add
"HandleLidSwitch=ignore".

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


** Tags: yakkety

** Tags added: yakkety

** Description changed:

  Hi,
  
- Probably the opposite of LP#1574120, after upgrading from Xenial to
+ Probably the opposite of LP: #1574120, after upgrading from Xenial to
  Yakkety (alpha 2), it seems my laptop automatically goes into suspend
  when the lid is closed even though I have "When the lid is closed"
  setting set to "Do nothing".
  
  I'm not sure what's changed, has the HandleLidSwitch default in logind
  changed?
  
  I had to update /etc/systemd/logind.conf and add
  "HandleLidSwitch=ignore".

** Description changed:

  Hi,
  
  Probably the opposite of LP: #1574120, after upgrading from Xenial to
  Yakkety (alpha 2), it seems my laptop automatically goes into suspend
  when the lid is closed even though I have "When the lid is closed"
  setting set to "Do nothing".
  
  I'm not sure what's changed, has the HandleLidSwitch default in logind
- changed?
+ changed? Also, any chance of fixing the "Power" setting so it correctly
+ handles updating logind?
  
  I had to update /etc/systemd/logind.conf and add
  "HandleLidSwitch=ignore".

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

Title:
  Power "When the lid is closed" setting does nothing

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

Bug description:
  Hi,

  Probably the opposite of LP: #1574120, after upgrading from Xenial to
  Yakkety (alpha 2), it seems my laptop automatically goes into suspend
  when the lid is closed even though I have "When the lid is closed"
  setting set to "Do nothing".

  I'm not sure what's changed, has the HandleLidSwitch default in logind
  changed? Also, any chance of fixing the "Power" setting so it
  correctly handles updating logind?

  I had to update /etc/systemd/logind.conf and add
  "HandleLidSwitch=ignore".

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

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

[Desktop-packages] [Bug 1556357] IpRoute.txt

[Haw Loeung]

apport information

** Attachment added: "IpRoute.txt"
   
https://bugs.launchpad.net/bugs/1556357/+attachment/4596799/+files/IpRoute.txt

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

Title:
  WiFi fails to resume after suspend; Race with wpasupplicant / wpa_cli
  resume?

Status in network-manager package in Ubuntu:
  New
Status in wpasupplicant package in Ubuntu:
  New

Bug description:
  Hi,

  I'm constantly having issues where my WiFi connection doesn't re-
  establish after resuming from suspend. I think it may be a race where
  the interface isn't ready yet and systemd-sleep calls /lib/systemd
  /system-sleep/wpasupplicant (which is a wrapper to wpa_cli).

  I normally restart NetworkManager but then found that calling 'wpa_cli
  resume' works also.

  Here's the logs:

  | Mar 12 13:53:06 ragnar.local kernel: psmouse serio1: synaptics: quirked 
min/max coordinates: x [1024..5112], y [2024..4832]
  | Mar 12 13:53:06 ragnar.local kernel: PM: resume of devices complete after 
562.709 msecs
  | Mar 12 13:53:06 ragnar.local kernel: PM: Finishing wakeup.
  | Mar 12 13:53:06 ragnar.local systemd[1]: Time has been changed
  | Mar 12 13:53:06 ragnar.local systemd[1066]: Time has been changed
  | Mar 12 13:53:06 ragnar.local kernel: Restarting tasks ... done.
  | Mar 12 13:53:06 ragnar.local systemd-sleep[29174]: System resumed.
  | Mar 12 13:53:06 ragnar.local systemd-sleep[29174]: Failed to connect to 
non-global ctrl_ifname: (nil)  error: No such file or directory
  | Mar 12 13:53:06 ragnar.local systemd-sleep[29227]: 
/lib/systemd/system-sleep/wpasupplicant failed with error code 255.
  | Mar 12 13:53:06 ragnar.local systemd[1]: Started Suspend.
  | Mar 12 13:53:06 ragnar.local systemd[1]: sleep.target: Unit not needed 
anymore. Stopping.
  | Mar 12 13:53:06 ragnar.local systemd[1]: Stopped target Sleep.
  | Mar 12 13:53:06 ragnar.local systemd[1]: Reached target Suspend.
  | Mar 12 13:53:06 ragnar.local systemd[1]: suspend.target: Unit is bound to 
inactive unit systemd-suspend.service. Stopping, too.
  | Mar 12 13:53:06 ragnar.local NetworkManager[23292]:   wake requested 
(sleeping: yes  enabled: yes)
  | Mar 12 13:53:06 ragnar.local systemd[1]: Stopped target Suspend.
  | Mar 12 13:53:06 ragnar.local NetworkManager[23292]:   waking up...
  | Mar 12 13:53:06 ragnar.local systemd-logind[662]: Operation 'sleep' 
finished.
  | Mar 12 13:53:06 ragnar.local kernel: IPv6: ADDRCONF(NETDEV_UP): wlp3s0: 
link is not ready
  | Mar 12 13:53:06 ragnar.local kernel: iwlwifi :03:00.0: L1 Enabled - LTR 
Enabled
  | Mar 12 13:53:06 ragnar.local NetworkManager[23292]:   (wlp3s0): 
device state change: unmanaged -> unavailable (reason 'managed') [10 20 2]
  | Mar 12 13:53:06 ragnar.local kernel: iwlwifi :03:00.0: L1 Enabled - LTR 
Enabled
  | Mar 12 13:53:07 ragnar.local kernel: iwlwifi :03:00.0: L1 Enabled - LTR 
Enabled
  | Mar 12 13:53:07 ragnar.local kernel: iwlwifi :03:00.0: L1 Enabled - LTR 
Enabled
  | Mar 12 13:53:07 ragnar.local NetworkManager[23292]:   NetworkManager 
state is now DISCONNECTED
  | Mar 12 13:53:07 ragnar.local kernel: IPv6: ADDRCONF(NETDEV_UP): wlp3s0: 
link is not ready
  | Mar 12 13:53:07 ragnar.local wpa_supplicant[23157]: dbus: 
wpa_dbus_get_object_properties: failed to get object properties: (none) none
  | Mar 12 13:53:07 ragnar.local wpa_supplicant[23157]: dbus: Failed to 
construct signal
  | Mar 12 13:53:07 ragnar.local wpa_supplicant[23157]: Could not read 
interface p2p-dev-wlp3s0 flags: No such device
  | Mar 12 13:53:07 ragnar.local NetworkManager[23292]:   (wlp3s0): 
supplicant interface state: starting -> ready
  | Mar 12 13:53:07 ragnar.local NetworkManager[23292]:   (wlp3s0): 
device state change: unavailable -> disconnected (reason 
'supplicant-available') [20 30 42]
  | Mar 12 13:53:07 ragnar.local NetworkManager[23292]:   Device 'wlp3s0' 
has no connection; scheduling activate_check in 0 seconds.
  | Mar 12 13:53:07 ragnar.local kernel: IPv6: ADDRCONF(NETDEV_UP): wlp3s0: 
link is not ready


  Thanks,

  Haw
  --- 
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.04
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2014-04-24 (687 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  Package: wpasupplicant
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.4.0-11.26-generic 4.4.4
  RfKill: Error: [Errno 2] No such file or directory
  Tags:  xenial
  Uname: Linux 4.4.0-11-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dialout dip lpadmin plugdev sudo users
  _MarkForUpload: True
  modified.conffile..etc.NetworkManager.NetworkManager.conf: [modified]
  

[Desktop-packages] [Bug 1556357] CRDA.txt

[Haw Loeung]

apport information

** Attachment added: "CRDA.txt"
   https://bugs.launchpad.net/bugs/1556357/+attachment/4596796/+files/CRDA.txt

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

Title:
  WiFi fails to resume after suspend; Race with wpasupplicant / wpa_cli
  resume?

Status in network-manager package in Ubuntu:
  New
Status in wpasupplicant package in Ubuntu:
  New

Bug description:
  Hi,

  I'm constantly having issues where my WiFi connection doesn't re-
  establish after resuming from suspend. I think it may be a race where
  the interface isn't ready yet and systemd-sleep calls /lib/systemd
  /system-sleep/wpasupplicant (which is a wrapper to wpa_cli).

  I normally restart NetworkManager but then found that calling 'wpa_cli
  resume' works also.

  Here's the logs:

  | Mar 12 13:53:06 ragnar.local kernel: psmouse serio1: synaptics: quirked 
min/max coordinates: x [1024..5112], y [2024..4832]
  | Mar 12 13:53:06 ragnar.local kernel: PM: resume of devices complete after 
562.709 msecs
  | Mar 12 13:53:06 ragnar.local kernel: PM: Finishing wakeup.
  | Mar 12 13:53:06 ragnar.local systemd[1]: Time has been changed
  | Mar 12 13:53:06 ragnar.local systemd[1066]: Time has been changed
  | Mar 12 13:53:06 ragnar.local kernel: Restarting tasks ... done.
  | Mar 12 13:53:06 ragnar.local systemd-sleep[29174]: System resumed.
  | Mar 12 13:53:06 ragnar.local systemd-sleep[29174]: Failed to connect to 
non-global ctrl_ifname: (nil)  error: No such file or directory
  | Mar 12 13:53:06 ragnar.local systemd-sleep[29227]: 
/lib/systemd/system-sleep/wpasupplicant failed with error code 255.
  | Mar 12 13:53:06 ragnar.local systemd[1]: Started Suspend.
  | Mar 12 13:53:06 ragnar.local systemd[1]: sleep.target: Unit not needed 
anymore. Stopping.
  | Mar 12 13:53:06 ragnar.local systemd[1]: Stopped target Sleep.
  | Mar 12 13:53:06 ragnar.local systemd[1]: Reached target Suspend.
  | Mar 12 13:53:06 ragnar.local systemd[1]: suspend.target: Unit is bound to 
inactive unit systemd-suspend.service. Stopping, too.
  | Mar 12 13:53:06 ragnar.local NetworkManager[23292]:   wake requested 
(sleeping: yes  enabled: yes)
  | Mar 12 13:53:06 ragnar.local systemd[1]: Stopped target Suspend.
  | Mar 12 13:53:06 ragnar.local NetworkManager[23292]:   waking up...
  | Mar 12 13:53:06 ragnar.local systemd-logind[662]: Operation 'sleep' 
finished.
  | Mar 12 13:53:06 ragnar.local kernel: IPv6: ADDRCONF(NETDEV_UP): wlp3s0: 
link is not ready
  | Mar 12 13:53:06 ragnar.local kernel: iwlwifi :03:00.0: L1 Enabled - LTR 
Enabled
  | Mar 12 13:53:06 ragnar.local NetworkManager[23292]:   (wlp3s0): 
device state change: unmanaged -> unavailable (reason 'managed') [10 20 2]
  | Mar 12 13:53:06 ragnar.local kernel: iwlwifi :03:00.0: L1 Enabled - LTR 
Enabled
  | Mar 12 13:53:07 ragnar.local kernel: iwlwifi :03:00.0: L1 Enabled - LTR 
Enabled
  | Mar 12 13:53:07 ragnar.local kernel: iwlwifi :03:00.0: L1 Enabled - LTR 
Enabled
  | Mar 12 13:53:07 ragnar.local NetworkManager[23292]:   NetworkManager 
state is now DISCONNECTED
  | Mar 12 13:53:07 ragnar.local kernel: IPv6: ADDRCONF(NETDEV_UP): wlp3s0: 
link is not ready
  | Mar 12 13:53:07 ragnar.local wpa_supplicant[23157]: dbus: 
wpa_dbus_get_object_properties: failed to get object properties: (none) none
  | Mar 12 13:53:07 ragnar.local wpa_supplicant[23157]: dbus: Failed to 
construct signal
  | Mar 12 13:53:07 ragnar.local wpa_supplicant[23157]: Could not read 
interface p2p-dev-wlp3s0 flags: No such device
  | Mar 12 13:53:07 ragnar.local NetworkManager[23292]:   (wlp3s0): 
supplicant interface state: starting -> ready
  | Mar 12 13:53:07 ragnar.local NetworkManager[23292]:   (wlp3s0): 
device state change: unavailable -> disconnected (reason 
'supplicant-available') [20 30 42]
  | Mar 12 13:53:07 ragnar.local NetworkManager[23292]:   Device 'wlp3s0' 
has no connection; scheduling activate_check in 0 seconds.
  | Mar 12 13:53:07 ragnar.local kernel: IPv6: ADDRCONF(NETDEV_UP): wlp3s0: 
link is not ready


  Thanks,

  Haw
  --- 
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.04
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2014-04-24 (687 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  Package: wpasupplicant
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.4.0-11.26-generic 4.4.4
  RfKill: Error: [Errno 2] No such file or directory
  Tags:  xenial
  Uname: Linux 4.4.0-11-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dialout dip lpadmin plugdev sudo users
  _MarkForUpload: True
  modified.conffile..etc.NetworkManager.NetworkManager.conf: [modified]
  

[Desktop-packages] [Bug 1556357] IwConfig.txt

[Haw Loeung]

apport information

** Attachment added: "IwConfig.txt"
   
https://bugs.launchpad.net/bugs/1556357/+attachment/4596800/+files/IwConfig.txt

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

Title:
  WiFi fails to resume after suspend; Race with wpasupplicant / wpa_cli
  resume?

Status in network-manager package in Ubuntu:
  New
Status in wpasupplicant package in Ubuntu:
  New

Bug description:
  Hi,

  I'm constantly having issues where my WiFi connection doesn't re-
  establish after resuming from suspend. I think it may be a race where
  the interface isn't ready yet and systemd-sleep calls /lib/systemd
  /system-sleep/wpasupplicant (which is a wrapper to wpa_cli).

  I normally restart NetworkManager but then found that calling 'wpa_cli
  resume' works also.

  Here's the logs:

  | Mar 12 13:53:06 ragnar.local kernel: psmouse serio1: synaptics: quirked 
min/max coordinates: x [1024..5112], y [2024..4832]
  | Mar 12 13:53:06 ragnar.local kernel: PM: resume of devices complete after 
562.709 msecs
  | Mar 12 13:53:06 ragnar.local kernel: PM: Finishing wakeup.
  | Mar 12 13:53:06 ragnar.local systemd[1]: Time has been changed
  | Mar 12 13:53:06 ragnar.local systemd[1066]: Time has been changed
  | Mar 12 13:53:06 ragnar.local kernel: Restarting tasks ... done.
  | Mar 12 13:53:06 ragnar.local systemd-sleep[29174]: System resumed.
  | Mar 12 13:53:06 ragnar.local systemd-sleep[29174]: Failed to connect to 
non-global ctrl_ifname: (nil)  error: No such file or directory
  | Mar 12 13:53:06 ragnar.local systemd-sleep[29227]: 
/lib/systemd/system-sleep/wpasupplicant failed with error code 255.
  | Mar 12 13:53:06 ragnar.local systemd[1]: Started Suspend.
  | Mar 12 13:53:06 ragnar.local systemd[1]: sleep.target: Unit not needed 
anymore. Stopping.
  | Mar 12 13:53:06 ragnar.local systemd[1]: Stopped target Sleep.
  | Mar 12 13:53:06 ragnar.local systemd[1]: Reached target Suspend.
  | Mar 12 13:53:06 ragnar.local systemd[1]: suspend.target: Unit is bound to 
inactive unit systemd-suspend.service. Stopping, too.
  | Mar 12 13:53:06 ragnar.local NetworkManager[23292]:   wake requested 
(sleeping: yes  enabled: yes)
  | Mar 12 13:53:06 ragnar.local systemd[1]: Stopped target Suspend.
  | Mar 12 13:53:06 ragnar.local NetworkManager[23292]:   waking up...
  | Mar 12 13:53:06 ragnar.local systemd-logind[662]: Operation 'sleep' 
finished.
  | Mar 12 13:53:06 ragnar.local kernel: IPv6: ADDRCONF(NETDEV_UP): wlp3s0: 
link is not ready
  | Mar 12 13:53:06 ragnar.local kernel: iwlwifi :03:00.0: L1 Enabled - LTR 
Enabled
  | Mar 12 13:53:06 ragnar.local NetworkManager[23292]:   (wlp3s0): 
device state change: unmanaged -> unavailable (reason 'managed') [10 20 2]
  | Mar 12 13:53:06 ragnar.local kernel: iwlwifi :03:00.0: L1 Enabled - LTR 
Enabled
  | Mar 12 13:53:07 ragnar.local kernel: iwlwifi :03:00.0: L1 Enabled - LTR 
Enabled
  | Mar 12 13:53:07 ragnar.local kernel: iwlwifi :03:00.0: L1 Enabled - LTR 
Enabled
  | Mar 12 13:53:07 ragnar.local NetworkManager[23292]:   NetworkManager 
state is now DISCONNECTED
  | Mar 12 13:53:07 ragnar.local kernel: IPv6: ADDRCONF(NETDEV_UP): wlp3s0: 
link is not ready
  | Mar 12 13:53:07 ragnar.local wpa_supplicant[23157]: dbus: 
wpa_dbus_get_object_properties: failed to get object properties: (none) none
  | Mar 12 13:53:07 ragnar.local wpa_supplicant[23157]: dbus: Failed to 
construct signal
  | Mar 12 13:53:07 ragnar.local wpa_supplicant[23157]: Could not read 
interface p2p-dev-wlp3s0 flags: No such device
  | Mar 12 13:53:07 ragnar.local NetworkManager[23292]:   (wlp3s0): 
supplicant interface state: starting -> ready
  | Mar 12 13:53:07 ragnar.local NetworkManager[23292]:   (wlp3s0): 
device state change: unavailable -> disconnected (reason 
'supplicant-available') [20 30 42]
  | Mar 12 13:53:07 ragnar.local NetworkManager[23292]:   Device 'wlp3s0' 
has no connection; scheduling activate_check in 0 seconds.
  | Mar 12 13:53:07 ragnar.local kernel: IPv6: ADDRCONF(NETDEV_UP): wlp3s0: 
link is not ready


  Thanks,

  Haw
  --- 
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.04
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2014-04-24 (687 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  Package: wpasupplicant
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.4.0-11.26-generic 4.4.4
  RfKill: Error: [Errno 2] No such file or directory
  Tags:  xenial
  Uname: Linux 4.4.0-11-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dialout dip lpadmin plugdev sudo users
  _MarkForUpload: True
  modified.conffile..etc.NetworkManager.NetworkManager.conf: [modified]
  

[Desktop-packages] [Bug 1556357] IpAddr.txt

[Haw Loeung]

apport information

** Attachment added: "IpAddr.txt"
   https://bugs.launchpad.net/bugs/1556357/+attachment/4596798/+files/IpAddr.txt

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

Title:
  WiFi fails to resume after suspend; Race with wpasupplicant / wpa_cli
  resume?

Status in network-manager package in Ubuntu:
  New
Status in wpasupplicant package in Ubuntu:
  New

Bug description:
  Hi,

  I'm constantly having issues where my WiFi connection doesn't re-
  establish after resuming from suspend. I think it may be a race where
  the interface isn't ready yet and systemd-sleep calls /lib/systemd
  /system-sleep/wpasupplicant (which is a wrapper to wpa_cli).

  I normally restart NetworkManager but then found that calling 'wpa_cli
  resume' works also.

  Here's the logs:

  | Mar 12 13:53:06 ragnar.local kernel: psmouse serio1: synaptics: quirked 
min/max coordinates: x [1024..5112], y [2024..4832]
  | Mar 12 13:53:06 ragnar.local kernel: PM: resume of devices complete after 
562.709 msecs
  | Mar 12 13:53:06 ragnar.local kernel: PM: Finishing wakeup.
  | Mar 12 13:53:06 ragnar.local systemd[1]: Time has been changed
  | Mar 12 13:53:06 ragnar.local systemd[1066]: Time has been changed
  | Mar 12 13:53:06 ragnar.local kernel: Restarting tasks ... done.
  | Mar 12 13:53:06 ragnar.local systemd-sleep[29174]: System resumed.
  | Mar 12 13:53:06 ragnar.local systemd-sleep[29174]: Failed to connect to 
non-global ctrl_ifname: (nil)  error: No such file or directory
  | Mar 12 13:53:06 ragnar.local systemd-sleep[29227]: 
/lib/systemd/system-sleep/wpasupplicant failed with error code 255.
  | Mar 12 13:53:06 ragnar.local systemd[1]: Started Suspend.
  | Mar 12 13:53:06 ragnar.local systemd[1]: sleep.target: Unit not needed 
anymore. Stopping.
  | Mar 12 13:53:06 ragnar.local systemd[1]: Stopped target Sleep.
  | Mar 12 13:53:06 ragnar.local systemd[1]: Reached target Suspend.
  | Mar 12 13:53:06 ragnar.local systemd[1]: suspend.target: Unit is bound to 
inactive unit systemd-suspend.service. Stopping, too.
  | Mar 12 13:53:06 ragnar.local NetworkManager[23292]:   wake requested 
(sleeping: yes  enabled: yes)
  | Mar 12 13:53:06 ragnar.local systemd[1]: Stopped target Suspend.
  | Mar 12 13:53:06 ragnar.local NetworkManager[23292]:   waking up...
  | Mar 12 13:53:06 ragnar.local systemd-logind[662]: Operation 'sleep' 
finished.
  | Mar 12 13:53:06 ragnar.local kernel: IPv6: ADDRCONF(NETDEV_UP): wlp3s0: 
link is not ready
  | Mar 12 13:53:06 ragnar.local kernel: iwlwifi :03:00.0: L1 Enabled - LTR 
Enabled
  | Mar 12 13:53:06 ragnar.local NetworkManager[23292]:   (wlp3s0): 
device state change: unmanaged -> unavailable (reason 'managed') [10 20 2]
  | Mar 12 13:53:06 ragnar.local kernel: iwlwifi :03:00.0: L1 Enabled - LTR 
Enabled
  | Mar 12 13:53:07 ragnar.local kernel: iwlwifi :03:00.0: L1 Enabled - LTR 
Enabled
  | Mar 12 13:53:07 ragnar.local kernel: iwlwifi :03:00.0: L1 Enabled - LTR 
Enabled
  | Mar 12 13:53:07 ragnar.local NetworkManager[23292]:   NetworkManager 
state is now DISCONNECTED
  | Mar 12 13:53:07 ragnar.local kernel: IPv6: ADDRCONF(NETDEV_UP): wlp3s0: 
link is not ready
  | Mar 12 13:53:07 ragnar.local wpa_supplicant[23157]: dbus: 
wpa_dbus_get_object_properties: failed to get object properties: (none) none
  | Mar 12 13:53:07 ragnar.local wpa_supplicant[23157]: dbus: Failed to 
construct signal
  | Mar 12 13:53:07 ragnar.local wpa_supplicant[23157]: Could not read 
interface p2p-dev-wlp3s0 flags: No such device
  | Mar 12 13:53:07 ragnar.local NetworkManager[23292]:   (wlp3s0): 
supplicant interface state: starting -> ready
  | Mar 12 13:53:07 ragnar.local NetworkManager[23292]:   (wlp3s0): 
device state change: unavailable -> disconnected (reason 
'supplicant-available') [20 30 42]
  | Mar 12 13:53:07 ragnar.local NetworkManager[23292]:   Device 'wlp3s0' 
has no connection; scheduling activate_check in 0 seconds.
  | Mar 12 13:53:07 ragnar.local kernel: IPv6: ADDRCONF(NETDEV_UP): wlp3s0: 
link is not ready


  Thanks,

  Haw
  --- 
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.04
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2014-04-24 (687 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  Package: wpasupplicant
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.4.0-11.26-generic 4.4.4
  RfKill: Error: [Errno 2] No such file or directory
  Tags:  xenial
  Uname: Linux 4.4.0-11-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dialout dip lpadmin plugdev sudo users
  _MarkForUpload: True
  modified.conffile..etc.NetworkManager.NetworkManager.conf: [modified]
  

[Desktop-packages] [Bug 1556357] Dependencies.txt

[Haw Loeung]

apport information

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

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

Title:
  WiFi fails to resume after suspend; Race with wpasupplicant / wpa_cli
  resume?

Status in network-manager package in Ubuntu:
  New
Status in wpasupplicant package in Ubuntu:
  New

Bug description:
  Hi,

  I'm constantly having issues where my WiFi connection doesn't re-
  establish after resuming from suspend. I think it may be a race where
  the interface isn't ready yet and systemd-sleep calls /lib/systemd
  /system-sleep/wpasupplicant (which is a wrapper to wpa_cli).

  I normally restart NetworkManager but then found that calling 'wpa_cli
  resume' works also.

  Here's the logs:

  | Mar 12 13:53:06 ragnar.local kernel: psmouse serio1: synaptics: quirked 
min/max coordinates: x [1024..5112], y [2024..4832]
  | Mar 12 13:53:06 ragnar.local kernel: PM: resume of devices complete after 
562.709 msecs
  | Mar 12 13:53:06 ragnar.local kernel: PM: Finishing wakeup.
  | Mar 12 13:53:06 ragnar.local systemd[1]: Time has been changed
  | Mar 12 13:53:06 ragnar.local systemd[1066]: Time has been changed
  | Mar 12 13:53:06 ragnar.local kernel: Restarting tasks ... done.
  | Mar 12 13:53:06 ragnar.local systemd-sleep[29174]: System resumed.
  | Mar 12 13:53:06 ragnar.local systemd-sleep[29174]: Failed to connect to 
non-global ctrl_ifname: (nil)  error: No such file or directory
  | Mar 12 13:53:06 ragnar.local systemd-sleep[29227]: 
/lib/systemd/system-sleep/wpasupplicant failed with error code 255.
  | Mar 12 13:53:06 ragnar.local systemd[1]: Started Suspend.
  | Mar 12 13:53:06 ragnar.local systemd[1]: sleep.target: Unit not needed 
anymore. Stopping.
  | Mar 12 13:53:06 ragnar.local systemd[1]: Stopped target Sleep.
  | Mar 12 13:53:06 ragnar.local systemd[1]: Reached target Suspend.
  | Mar 12 13:53:06 ragnar.local systemd[1]: suspend.target: Unit is bound to 
inactive unit systemd-suspend.service. Stopping, too.
  | Mar 12 13:53:06 ragnar.local NetworkManager[23292]:   wake requested 
(sleeping: yes  enabled: yes)
  | Mar 12 13:53:06 ragnar.local systemd[1]: Stopped target Suspend.
  | Mar 12 13:53:06 ragnar.local NetworkManager[23292]:   waking up...
  | Mar 12 13:53:06 ragnar.local systemd-logind[662]: Operation 'sleep' 
finished.
  | Mar 12 13:53:06 ragnar.local kernel: IPv6: ADDRCONF(NETDEV_UP): wlp3s0: 
link is not ready
  | Mar 12 13:53:06 ragnar.local kernel: iwlwifi :03:00.0: L1 Enabled - LTR 
Enabled
  | Mar 12 13:53:06 ragnar.local NetworkManager[23292]:   (wlp3s0): 
device state change: unmanaged -> unavailable (reason 'managed') [10 20 2]
  | Mar 12 13:53:06 ragnar.local kernel: iwlwifi :03:00.0: L1 Enabled - LTR 
Enabled
  | Mar 12 13:53:07 ragnar.local kernel: iwlwifi :03:00.0: L1 Enabled - LTR 
Enabled
  | Mar 12 13:53:07 ragnar.local kernel: iwlwifi :03:00.0: L1 Enabled - LTR 
Enabled
  | Mar 12 13:53:07 ragnar.local NetworkManager[23292]:   NetworkManager 
state is now DISCONNECTED
  | Mar 12 13:53:07 ragnar.local kernel: IPv6: ADDRCONF(NETDEV_UP): wlp3s0: 
link is not ready
  | Mar 12 13:53:07 ragnar.local wpa_supplicant[23157]: dbus: 
wpa_dbus_get_object_properties: failed to get object properties: (none) none
  | Mar 12 13:53:07 ragnar.local wpa_supplicant[23157]: dbus: Failed to 
construct signal
  | Mar 12 13:53:07 ragnar.local wpa_supplicant[23157]: Could not read 
interface p2p-dev-wlp3s0 flags: No such device
  | Mar 12 13:53:07 ragnar.local NetworkManager[23292]:   (wlp3s0): 
supplicant interface state: starting -> ready
  | Mar 12 13:53:07 ragnar.local NetworkManager[23292]:   (wlp3s0): 
device state change: unavailable -> disconnected (reason 
'supplicant-available') [20 30 42]
  | Mar 12 13:53:07 ragnar.local NetworkManager[23292]:   Device 'wlp3s0' 
has no connection; scheduling activate_check in 0 seconds.
  | Mar 12 13:53:07 ragnar.local kernel: IPv6: ADDRCONF(NETDEV_UP): wlp3s0: 
link is not ready


  Thanks,

  Haw
  --- 
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.04
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2014-04-24 (687 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  Package: wpasupplicant
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.4.0-11.26-generic 4.4.4
  RfKill: Error: [Errno 2] No such file or directory
  Tags:  xenial
  Uname: Linux 4.4.0-11-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dialout dip lpadmin plugdev sudo users
  _MarkForUpload: True
  modified.conffile..etc.NetworkManager.NetworkManager.conf: [modified]
  

[Desktop-packages] [Bug 1556357] Re: WiFi fails to resume after suspend; Race with wpasupplicant / wpa_cli resume?

[Haw Loeung]

@Martin, it's Xenial.

| Mar 12 17:35:25 ragnar NetworkManager[23292]:   sleep requested 
(sleeping: no  enabled: yes)
| Mar 12 17:35:25 ragnar NetworkManager[23292]:   sleeping...
| Mar 12 17:35:25 ragnar NetworkManager[23292]:   (wlp3s0): device state 
change: activated -> unmanaged (reason 'sleeping') [100 10 37]
| Mar 12 17:35:26 ragnar NetworkManager[23292]:   (wlp3s0): canceled DHCP 
transaction, DHCP client pid 8279
| Mar 12 17:35:26 ragnar NetworkManager[23292]:   (wlp3s0): DHCPv4 state 
changed bound -> done
| Mar 12 17:35:26 ragnar kernel: [143996.969825] wlp3s0: deauthenticating from 
24:a4:3c:99:31:37 by local choice (Reason: 3=DEAUTH_LEAVING)
| Mar 12 17:35:26 ragnar wpa_supplicant[23157]: wlp3s0: CTRL-EVENT-DISCONNECTED 
bssid=24:a4:3c:99:31:37 reason=3 locally_generated=1
| Mar 12 17:35:26 ragnar NetworkManager[23292]:   NetworkManager state is 
now ASLEEP
| Mar 12 17:35:26 ragnar wpa_supplicant[23157]: p2p-dev-wlp3s0: 
CTRL-EVENT-REGDOM-CHANGE init=CORE type=WORLD
| Mar 12 17:35:26 ragnar kernel: [143996.986106] cfg80211: World regulatory 
domain updated:
| Mar 12 17:35:26 ragnar kernel: [143996.986111] cfg80211:  DFS Master region: 
unset
| Mar 12 17:35:26 ragnar kernel: [143996.986113] cfg80211:   (start_freq - 
end_freq @ bandwidth), (max_antenna_gain, max_eirp), (dfs_cac_time)
| Mar 12 17:35:26 ragnar kernel: [143996.986117] cfg80211:   (2402000 KHz - 
2472000 KHz @ 4 KHz), (N/A, 2000 mBm), (N/A)
| Mar 12 17:35:26 ragnar kernel: [143996.986120] cfg80211:   (2457000 KHz - 
2482000 KHz @ 4 KHz), (N/A, 2000 mBm), (N/A)
| Mar 12 17:35:26 ragnar kernel: [143996.986122] cfg80211:   (2474000 KHz - 
2494000 KHz @ 2 KHz), (N/A, 2000 mBm), (N/A)
| Mar 12 17:35:26 ragnar kernel: [143996.986125] cfg80211:   (517 KHz - 
525 KHz @ 8 KHz, 16 KHz AUTO), (N/A, 2000 mBm), (N/A)
| Mar 12 17:35:26 ragnar kernel: [143996.986129] cfg80211:   (525 KHz - 
533 KHz @ 8 KHz, 16 KHz AUTO), (N/A, 2000 mBm), (0 s)
| Mar 12 17:35:26 ragnar kernel: [143996.986133] cfg80211:   (549 KHz - 
573 KHz @ 16 KHz), (N/A, 2000 mBm), (0 s)
| Mar 12 17:35:26 ragnar kernel: [143996.986136] cfg80211:   (5735000 KHz - 
5835000 KHz @ 8 KHz), (N/A, 2000 mBm), (N/A)
| Mar 12 17:35:26 ragnar kernel: [143996.986139] cfg80211:   (5724 KHz - 
6372 KHz @ 216 KHz), (N/A, 0 mBm), (N/A)
| Mar 12 17:35:26 ragnar wpa_supplicant[23157]: p2p-dev-wlp3s0: 
CTRL-EVENT-REGDOM-CHANGE init=USER type=COUNTRY alpha2=AU
| Mar 12 17:35:26 ragnar kernel: [143996.990173] cfg80211: Regulatory domain 
changed to country: AU
| Mar 12 17:35:26 ragnar kernel: [143996.990177] cfg80211:  DFS Master region: 
ETSI
| Mar 12 17:35:26 ragnar kernel: [143996.990179] cfg80211:   (start_freq - 
end_freq @ bandwidth), (max_antenna_gain, max_eirp), (dfs_cac_time)
| Mar 12 17:35:26 ragnar kernel: [143996.990183] cfg80211:   (2402000 KHz - 
2482000 KHz @ 4 KHz), (N/A, 2000 mBm), (N/A)
| Mar 12 17:35:26 ragnar kernel: [143996.990186] cfg80211:   (517 KHz - 
525 KHz @ 8 KHz, 16 KHz AUTO), (N/A, 1700 mBm), (N/A)
| Mar 12 17:35:26 ragnar kernel: [143996.990189] cfg80211:   (525 KHz - 
533 KHz @ 8 KHz, 16 KHz AUTO), (N/A, 2400 mBm), (0 s)
| Mar 12 17:35:26 ragnar kernel: [143996.990191] cfg80211:   (549 KHz - 
571 KHz @ 16 KHz), (N/A, 2400 mBm), (0 s)
| Mar 12 17:35:26 ragnar kernel: [143996.990193] cfg80211:   (5735000 KHz - 
5835000 KHz @ 8 KHz), (N/A, 3000 mBm), (N/A)
| Mar 12 17:35:26 ragnar wpa_supplicant[23157]: nl80211: deinit 
ifname=p2p-dev-wlp3s0 disabled_11b_rates=0
| Mar 12 17:35:26 ragnar NetworkManager[23292]:   Failed to 
GDBus.Error:fi.w1.wpa_supplicant1.NotConnected: This interface is not 
connected: disconnect.
| Mar 12 17:35:26 ragnar dbus[629]: [system] Activating via systemd: service 
name='org.freedesktop.nm_dispatcher' 
unit='dbus-org.freedesktop.nm-dispatcher.service'
| Mar 12 17:35:26 ragnar systemd[1]: Starting Network Manager Script Dispatcher 
Service...
| Mar 12 17:35:26 ragnar dbus[629]: [system] Successfully activated service 
'org.freedesktop.nm_dispatcher'
| Mar 12 17:35:26 ragnar systemd[1]: Started Network Manager Script Dispatcher 
Service.
  
| Mar 12 17:35:26 ragnar nm-dispatcher: Dispatching action 'down' for wlp3s0


   
| Mar 12 17:35:26 ragnar wpa_supplicant[23157]: nl80211: deinit ifname=wlp3s0 
disabled_11b_rates=0

 
| Mar 12 17:35:27 ragnar systemd[1]: Reached target Sleep.  
  

[Desktop-packages] [Bug 1556357] Re: WiFi fails to resume after suspend; Race with wpasupplicant / wpa_cli resume?

[Haw Loeung]

| [hloeung@ragnar tmp]$ apt-cache policy systemd wpasupplicant
| systemd:
|   Installed: 229-2ubuntu1
|   Candidate: 229-2ubuntu1
|   Version table:
|  *** 229-2ubuntu1 500
| 500 http://archive.ubuntu.com/ubuntu xenial/main amd64 Packages
| 100 /var/lib/dpkg/status
| wpasupplicant:
|   Installed: 2.4-0ubuntu6
|   Candidate: 2.4-0ubuntu6
|   Version table:
|  *** 2.4-0ubuntu6 500
| 500 http://archive.ubuntu.com/ubuntu xenial/main amd64 Packages
| 100 /var/lib/dpkg/status


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

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

Title:
  WiFi fails to resume after suspend; Race with wpasupplicant / wpa_cli
  resume?

Status in systemd package in Ubuntu:
  New
Status in wpasupplicant package in Ubuntu:
  New

Bug description:
  Hi,

  I'm constantly having issues where my WiFi connection doesn't re-
  establish after resuming from suspend. I think it may be a race where
  the interface isn't ready yet and systemd-sleep calls /lib/systemd
  /system-sleep/wpasupplicant (which is a wrapper to wpa_cli).

  I normally restart NetworkManager but then found that calling 'wpa_cli
  resume' works also.

  Here's the logs:

  | Mar 12 13:53:06 ragnar.local kernel: psmouse serio1: synaptics: quirked 
min/max coordinates: x [1024..5112], y [2024..4832]
  | Mar 12 13:53:06 ragnar.local kernel: PM: resume of devices complete after 
562.709 msecs
  | Mar 12 13:53:06 ragnar.local kernel: PM: Finishing wakeup.
  | Mar 12 13:53:06 ragnar.local systemd[1]: Time has been changed
  | Mar 12 13:53:06 ragnar.local systemd[1066]: Time has been changed
  | Mar 12 13:53:06 ragnar.local kernel: Restarting tasks ... done.
  | Mar 12 13:53:06 ragnar.local systemd-sleep[29174]: System resumed.
  | Mar 12 13:53:06 ragnar.local systemd-sleep[29174]: Failed to connect to 
non-global ctrl_ifname: (nil)  error: No such file or directory
  | Mar 12 13:53:06 ragnar.local systemd-sleep[29227]: 
/lib/systemd/system-sleep/wpasupplicant failed with error code 255.
  | Mar 12 13:53:06 ragnar.local systemd[1]: Started Suspend.
  | Mar 12 13:53:06 ragnar.local systemd[1]: sleep.target: Unit not needed 
anymore. Stopping.
  | Mar 12 13:53:06 ragnar.local systemd[1]: Stopped target Sleep.
  | Mar 12 13:53:06 ragnar.local systemd[1]: Reached target Suspend.
  | Mar 12 13:53:06 ragnar.local systemd[1]: suspend.target: Unit is bound to 
inactive unit systemd-suspend.service. Stopping, too.
  | Mar 12 13:53:06 ragnar.local NetworkManager[23292]:   wake requested 
(sleeping: yes  enabled: yes)
  | Mar 12 13:53:06 ragnar.local systemd[1]: Stopped target Suspend.
  | Mar 12 13:53:06 ragnar.local NetworkManager[23292]:   waking up...
  | Mar 12 13:53:06 ragnar.local systemd-logind[662]: Operation 'sleep' 
finished.
  | Mar 12 13:53:06 ragnar.local kernel: IPv6: ADDRCONF(NETDEV_UP): wlp3s0: 
link is not ready
  | Mar 12 13:53:06 ragnar.local kernel: iwlwifi :03:00.0: L1 Enabled - LTR 
Enabled
  | Mar 12 13:53:06 ragnar.local NetworkManager[23292]:   (wlp3s0): 
device state change: unmanaged -> unavailable (reason 'managed') [10 20 2]
  | Mar 12 13:53:06 ragnar.local kernel: iwlwifi :03:00.0: L1 Enabled - LTR 
Enabled
  | Mar 12 13:53:07 ragnar.local kernel: iwlwifi :03:00.0: L1 Enabled - LTR 
Enabled
  | Mar 12 13:53:07 ragnar.local kernel: iwlwifi :03:00.0: L1 Enabled - LTR 
Enabled
  | Mar 12 13:53:07 ragnar.local NetworkManager[23292]:   NetworkManager 
state is now DISCONNECTED
  | Mar 12 13:53:07 ragnar.local kernel: IPv6: ADDRCONF(NETDEV_UP): wlp3s0: 
link is not ready
  | Mar 12 13:53:07 ragnar.local wpa_supplicant[23157]: dbus: 
wpa_dbus_get_object_properties: failed to get object properties: (none) none
  | Mar 12 13:53:07 ragnar.local wpa_supplicant[23157]: dbus: Failed to 
construct signal
  | Mar 12 13:53:07 ragnar.local wpa_supplicant[23157]: Could not read 
interface p2p-dev-wlp3s0 flags: No such device
  | Mar 12 13:53:07 ragnar.local NetworkManager[23292]:   (wlp3s0): 
supplicant interface state: starting -> ready
  | Mar 12 13:53:07 ragnar.local NetworkManager[23292]:   (wlp3s0): 
device state change: unavailable -> disconnected (reason 
'supplicant-available') [20 30 42]
  | Mar 12 13:53:07 ragnar.local NetworkManager[23292]:   Device 'wlp3s0' 
has no connection; scheduling activate_check in 0 seconds.
  | Mar 12 13:53:07 ragnar.local kernel: IPv6: ADDRCONF(NETDEV_UP): wlp3s0: 
link is not ready


  Thanks,

  Haw

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

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

[Desktop-packages] [Bug 1483205] [NEW] unity-control-center needs bluetooth packages

[Haw Loeung]

Public bug reported:

Hi,

unity-control-center seems to require indicator-bluetooth which then
pulls in a bunch of bluetooth packages. Any chance of updating it so
bluetooth is optional? I don't have bluetooth enabled, and would prefer
not to have bluetooth packages installed (indicator-bluetooth, bluez,
indicator-bluetooth, gir1.2-gnomebluetooth-1.0, libbluetooth3, etc.)

Thanks in advance.

** Affects: unity-control-center (Ubuntu)
 Importance: Wishlist
 Status: New

** Changed in: unity-control-center (Ubuntu)
   Importance: Undecided = Wishlist

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

Title:
  unity-control-center needs bluetooth packages

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

Bug description:
  Hi,

  unity-control-center seems to require indicator-bluetooth which then
  pulls in a bunch of bluetooth packages. Any chance of updating it so
  bluetooth is optional? I don't have bluetooth enabled, and would
  prefer not to have bluetooth packages installed (indicator-bluetooth,
  bluez, indicator-bluetooth, gir1.2-gnomebluetooth-1.0, libbluetooth3,
  etc.)

  Thanks in advance.

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

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

[Desktop-packages] [Bug 1465014] Re: after update still vulnerable against LOGJAM

[Haw Loeung]

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

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

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

Title:
  after update still vulnerable against LOGJAM

Status in Network Security Services (NSS):
  Unknown
Status in firefox package in Ubuntu:
  Triaged
Status in nss package in Ubuntu:
  Triaged

Bug description:
  Hint: http://www.ubuntu.com/usn/usn-2639-1/

   As a security improvement, this update also modifies OpenSSL
  behaviour to reject DH key sizes below 768 bits, preventing a possible
  downgrade attack. 

  I installed the update but the test site says, i'm still vulnerable (see 
attachted screen shot).
  Site: https://weakdh.org/

  - Xubuntu 15.04  --  up-to-date

  - openSSL 1.0.1f-1ubuntu11.4  --  up-to-date

  - Firefox 38.0+build3-0ubuntu0.15.04.1  --   up-to-date (even there are the 
versions 38.0.5 and 38.0.6 on the mozilla server available)
  - Chromium 43.0.2357.81-0ubuntu0.15.04.1.1170  --  up-to-date

  


  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: openssl 1.0.1f-1ubuntu11.4
  ProcVersionSignature: Ubuntu 3.19.0-20.20-generic 3.19.8
  Uname: Linux 3.19.0-20-generic x86_64
  ApportVersion: 2.17.2-0ubuntu1.1
  Architecture: amd64
  Date: Sun Jun 14 15:34:46 2015
  InstallationDate: Installed on 2015-05-28 (16 days ago)
  InstallationMedia: Xubuntu 15.04 Vivid Vervet - Release amd64 (20150422.1)
  SourcePackage: openssl
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1465014] Re: after update still vulnerable against LOGJAM

[Haw Loeung]

3.19.2 was just released[1] with:


Notable Changes in NSS 3.19.2
Bug 1172128 - In NSS 3.19.1, the minimum key sizes that the freebl 
cryptographic implementation (part of the softoken cryptographic module used by 
default by NSS) was willing to generate or use was increased - for RSA keys, to 
512 bits, and for DH keys, 1023 bits. This was done as part of a security fix 
for Bug 1138554 / CVE-2015-4000. Applications that requested or attempted to 
use keys smaller then the minimum size would fail. However, this change in 
behaviour unintentionally broke existing NSS applications that need to generate 
or use such keys, via APIs such as SECKEY_CreateRSAPrivateKey or 
SECKEY_CreateDHPrivateKey.

In NSS 3.19.2, this change in freebl behaviour has been reverted. The
fix for Bug 1138554 has been moved to libssl, and will now only affect
the minimum keystrengths used in SSL/TLS.

Note: Future versions of NSS may increase the minimum keysizes required by the 
freebl module. Consumers of NSS are strongly encouraged to migrate to stronger 
cryptographic strengths as soon as possible.



[1]https://developer.mozilla.org/en-US/docs/Mozilla/Projects/NSS/NSS_3.19.2_release_notes

** CVE added: http://www.cve.mitre.org/cgi-
bin/cvename.cgi?name=2015-4000

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

Title:
  after update still vulnerable against LOGJAM

Status in firefox package in Ubuntu:
  Confirmed
Status in nss package in Ubuntu:
  Confirmed

Bug description:
  Hint: http://www.ubuntu.com/usn/usn-2639-1/

   As a security improvement, this update also modifies OpenSSL
  behaviour to reject DH key sizes below 768 bits, preventing a possible
  downgrade attack. 

  I installed the update but the test site says, i'm still vulnerable (see 
attachted screen shot).
  Site: https://weakdh.org/

  - Xubuntu 15.04  --  up-to-date

  - openSSL 1.0.1f-1ubuntu11.4  --  up-to-date

  - Firefox 38.0+build3-0ubuntu0.15.04.1  --   up-to-date (even there are the 
versions 38.0.5 and 38.0.6 on the mozilla server available)
  - Chromium 43.0.2357.81-0ubuntu0.15.04.1.1170  --  up-to-date

  


  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: openssl 1.0.1f-1ubuntu11.4
  ProcVersionSignature: Ubuntu 3.19.0-20.20-generic 3.19.8
  Uname: Linux 3.19.0-20-generic x86_64
  ApportVersion: 2.17.2-0ubuntu1.1
  Architecture: amd64
  Date: Sun Jun 14 15:34:46 2015
  InstallationDate: Installed on 2015-05-28 (16 days ago)
  InstallationMedia: Xubuntu 15.04 Vivid Vervet - Release amd64 (20150422.1)
  SourcePackage: openssl
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1465014] Re: after update still vulnerable against LOGJAM

[Haw Loeung]

Chrome and Firefox both uses NSS. NSS 3.19.1 contains fixes to mitigate
logjam by increasing the minimum modulus size for Diffie-Hellman keys to
1023 bits[1].

Maybe we can look into backporting that.

[1]https://developer.mozilla.org/en-
US/docs/Mozilla/Projects/NSS/NSS_3.19.1_release_notes

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

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

Title:
  after update still vulnerable against LOGJAM

Status in firefox package in Ubuntu:
  New
Status in nss package in Ubuntu:
  New

Bug description:
  Hint: http://www.ubuntu.com/usn/usn-2639-1/

   As a security improvement, this update also modifies OpenSSL
  behaviour to reject DH key sizes below 768 bits, preventing a possible
  downgrade attack. 

  I installed the update but the test site says, i'm still vulnerable (see 
attachted screen shot).
  Site: https://weakdh.org/

  - Xubuntu 15.04  --  up-to-date

  - openSSL 1.0.1f-1ubuntu11.4  --  up-to-date

  - Firefox 38.0+build3-0ubuntu0.15.04.1  --   up-to-date (even there are the 
versions 38.0.5 and 38.0.6 on the mozilla server available)
  - Chromium 43.0.2357.81-0ubuntu0.15.04.1.1170  --  up-to-date

  


  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: openssl 1.0.1f-1ubuntu11.4
  ProcVersionSignature: Ubuntu 3.19.0-20.20-generic 3.19.8
  Uname: Linux 3.19.0-20-generic x86_64
  ApportVersion: 2.17.2-0ubuntu1.1
  Architecture: amd64
  Date: Sun Jun 14 15:34:46 2015
  InstallationDate: Installed on 2015-05-28 (16 days ago)
  InstallationMedia: Xubuntu 15.04 Vivid Vervet - Release amd64 (20150422.1)
  SourcePackage: openssl
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1465014] Re: after update still vulnerable against LOGJAM

[Haw Loeung]

https://hg.mozilla.org/projects/nss/rev/ae72d76f8d24

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

Title:
  after update still vulnerable against LOGJAM

Status in firefox package in Ubuntu:
  New
Status in nss package in Ubuntu:
  New

Bug description:
  Hint: http://www.ubuntu.com/usn/usn-2639-1/

   As a security improvement, this update also modifies OpenSSL
  behaviour to reject DH key sizes below 768 bits, preventing a possible
  downgrade attack. 

  I installed the update but the test site says, i'm still vulnerable (see 
attachted screen shot).
  Site: https://weakdh.org/

  - Xubuntu 15.04  --  up-to-date

  - openSSL 1.0.1f-1ubuntu11.4  --  up-to-date

  - Firefox 38.0+build3-0ubuntu0.15.04.1  --   up-to-date (even there are the 
versions 38.0.5 and 38.0.6 on the mozilla server available)
  - Chromium 43.0.2357.81-0ubuntu0.15.04.1.1170  --  up-to-date

  


  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: openssl 1.0.1f-1ubuntu11.4
  ProcVersionSignature: Ubuntu 3.19.0-20.20-generic 3.19.8
  Uname: Linux 3.19.0-20-generic x86_64
  ApportVersion: 2.17.2-0ubuntu1.1
  Architecture: amd64
  Date: Sun Jun 14 15:34:46 2015
  InstallationDate: Installed on 2015-05-28 (16 days ago)
  InstallationMedia: Xubuntu 15.04 Vivid Vervet - Release amd64 (20150422.1)
  SourcePackage: openssl
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1377220] Re: Google Chrome crash with mesa 10.3 on Intel GPU

[Haw Loeung]

I've been running with --disable-gpu-sandbox since the 14th and so far
haven't experienced any more issues with crashes and lock ups.

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

Title:
  Google Chrome crash with mesa 10.3 on Intel GPU

Status in “mesa” package in Ubuntu:
  Confirmed

Bug description:
  When I start google-chrome on my Ubuntu 14.10 system the process it
  uses to test for a working GPU crashes and then Chrome falls back to
  software rendering.

  In chrome://gpu/ I get:

  Graphics Feature Status
  Canvas: Software only, hardware acceleration unavailable
  Flash: Software only, hardware acceleration unavailable
  Flash Stage3D: Software only, hardware acceleration unavailable
  Flash Stage3D Baseline profile: Software only, hardware acceleration 
unavailable
  Compositing: Software only, hardware acceleration unavailable
  Multiple Raster Threads: Unavailable
  Rasterization: Software only, hardware acceleration unavailable
  Threaded Rasterization: Unavailable
  Video Decode: Software only, hardware acceleration unavailable
  Video Encode: Software only, hardware acceleration unavailable
  WebGL: Unavailable

  Driver Bug Workarounds
  clear_uniforms_before_first_program_use
  count_all_in_varyings_packing
  disable_ext_occlusion_query
  disable_post_sub_buffers_for_onscreen_surfaces
  scalarize_vec_and_mat_constructor_args

  Problems Detected
  GPU process was unable to boot: GPU access is disabled in chrome://settings.
  Disabled Features: all
  [...]

  In Ubuntu 14.04 (and also previous versions), on the same laptop, the
  exact same Google Chrome used to work perfectly with GPU acceleration.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: libgl1-mesa-dri 10.3.0-0ubuntu2
  ProcVersionSignature: Ubuntu 3.16.0-20.27-generic 3.16.3
  Uname: Linux 3.16.0-20-generic x86_64
  .tmp.unity.support.test.0:

  ApportVersion: 2.14.7-0ubuntu2
  Architecture: amd64
  BootLog:
   Scanning for Btrfs filesystems
    * Setting sensors limits   
  [ OK ]
    * Setting up X socket directories...   
  [ OK ]
  CompizPlugins: 
[core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,staticswitcher,workarounds,scale,expo,ezoom,dbus]
  CompositorRunning: kwin
  CurrentDesktop: KDE
  Date: Fri Oct  3 17:48:09 2014
  DistUpgraded: Fresh install
  DistroCodename: utopic
  DistroVariant: kubuntu
  EcryptfsInUse: Yes
  ExtraDebuggingInterest: No
  GraphicsCard:
   Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0126] (rev 09) (prog-if 00 [VGA controller])
     Subsystem: Dell Device [1028:0494]
  MachineType: Dell Inc. Latitude E6520
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-20-generic 
root=UUID=749a9901-bdd3-4b5f-b80e-69414667e058 ro quiet splash vt.handoff=7
  SourcePackage: mesa
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/14/2013
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A19
  dmi.board.name: 0NVF5K
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A01
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA19:bd11/14/2013:svnDellInc.:pnLatitudeE6520:pvr01:rvnDellInc.:rn0NVF5K:rvrA01:cvnDellInc.:ct9:cvr:
  dmi.product.name: Latitude E6520
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.12+14.10.20140918-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.56-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.3.0-0ubuntu2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.3.0-0ubuntu2
  version.xserver-xorg-core: xserver-xorg-core 2:1.16.0-1ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.4.0-2ubuntu2
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.914-1~exp1ubuntu3
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.11-1ubuntu2
  xserver.bootTime: Thu Oct  2 13:54:36 2014
  xserver.configfile: default
  xserver.errors:

  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id8685
   vendor AUO
  xserver.version: 2:1.16.0-1ubuntu1

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

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

[Desktop-packages] [Bug 1380278] Re: unity-settings-daemon crashed with SIGSEGV in _gdk_device_xi2_reset_scroll_valuators()

[Haw Loeung]

** Information type changed from Private to Public

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

Title:
  unity-settings-daemon crashed with SIGSEGV in
  _gdk_device_xi2_reset_scroll_valuators()

Status in “unity-settings-daemon” package in Ubuntu:
  Confirmed

Bug description:
  I don't know

  ProblemType: Crash
  DistroRelease: Ubuntu 14.10
  Package: unity-settings-daemon 14.04.0+14.10.20141010-0ubuntu1
  ProcVersionSignature: Ubuntu 3.16.0-22.29-generic 3.16.4
  Uname: Linux 3.16.0-22-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.14.7-0ubuntu5
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sun Oct 12 16:07:07 2014
  ExecutablePath: /usr/lib/unity-settings-daemon/unity-settings-daemon
  InstallationDate: Installed on 2014-09-21 (21 days ago)
  InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Alpha amd64 (20140921)
  ProcCmdline: /usr/lib/unity-settings-daemon/unity-settings-daemon
  SegvAnalysis:
   Segfault happened at: 0x7f4aed57b3a4:mov0x8(%rax),%edx
   PC (0x7f4aed57b3a4) ok
   source 0x8(%rax) (0x0008) not located in a known VMA region (needed 
readable region)!
   destination %edx ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: unity-settings-daemon
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/libgdk-3.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgdk-3.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgdk-3.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgdk-3.so.0
   gdk_display_get_event () from /usr/lib/x86_64-linux-gnu/libgdk-3.so.0
  Title: unity-settings-daemon crashed with SIGSEGV in gdk_display_get_event()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirtd lpadmin plugdev sambashare sudo

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

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

[Desktop-packages] [Bug 1236346] Re: at-spi2-registryd.conf upstart script missing closing ']'

[Haw Loeung]

Hi,

at-spi2-core_2.10.1-0ubuntu0.1 fixes this for me.


Thanks,

Haw

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

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

Title:
  at-spi2-registryd.conf upstart script missing closing ']'

Status in “at-spi2-core” package in Ubuntu:
  Fix Released
Status in “at-spi2-core” source package in Saucy:
  Fix Committed

Bug description:
  Impact
  At-spi2 does run, but the missing closing bracket in the upstart config file 
may be causing the gsettings check to fail. In addition, the following is shown 
in the user's local upstart logs for at-spi2-registryd:

  /proc/self/fd/9: 2: [: missing ]

  Regression potential:
  Little to none at all given that this was a typo.

  Test case:
  1. Install the new at-spi2-core package from saucy-proposed.
  2. Remove the at-spi2-core upstart log from ~/.cache/upstart.
  3. Log out and back in.
  4. The below error should not be present in the at-spi2-core upstart log.

  Hi,

  I'm seeing a bunch of missing ']' errors in ~/.cache/upstart/at-
  spi2-registryd.log. It seems this is because the 'pre-start' stanza is
  missing a closing ']' as shown below:

  pre-start script
  [ $(gsettings get org.gnome.desktop.interface toolkit-accessibility) \
   = true || exit 0
  end script

  It seems like an easy fix but I can't seem to find which LP branch to
  create a merge proposal against.

  Regards,

  Haw
  --- 
  ApportVersion: 2.12.5-0ubuntu1
  Architecture: amd64
  DistroRelease: Ubuntu 13.10
  MarkForUpload: True
  Package: at-spi2-core 2.10.0-0ubuntu2 [modified: 
usr/share/upstart/sessions/at-spi2-registryd.conf]
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 3.11.0-11.17-generic 3.11.3
  Tags:  saucy
  Uname: Linux 3.11.0-11-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm admin audio cdrom dialout libvirtd lpadmin netdev plugdev 
sambashare users video
  modified.conffile..etc.xdg.autostart.at.spi.dbus.bus.desktop: [modified]
  mtime.conffile..etc.xdg.autostart.at.spi.dbus.bus.desktop: 
2013-07-24T01:24:45.829666

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/at-spi2-core/+bug/1236346/+subscriptions

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

[Desktop-packages] [Bug 1236346] Dependencies.txt

[Haw Loeung]

apport information

** Attachment added: Dependencies.txt
   
https://bugs.launchpad.net/bugs/1236346/+attachment/3864206/+files/Dependencies.txt

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

Title:
  at-spi2-registryd.conf upstart script missing closing ']'

Status in “at-spi2-core” package in Ubuntu:
  New

Bug description:
  Hi,

  I'm seeing a bunch of missing ']' errors in ~/.cache/upstart/at-
  spi2-registryd.log. It seems this is because the 'pre-start' stanza is
  missing a closing ']' as shown below:

  pre-start script
  [ $(gsettings get org.gnome.desktop.interface toolkit-accessibility) \
   = true || exit 0
  end script

  It seems like an easy fix but I can't seem to find which LP branch to
  create a merge proposal against.

  Regards,

  Haw
  --- 
  ApportVersion: 2.12.5-0ubuntu1
  Architecture: amd64
  DistroRelease: Ubuntu 13.10
  MarkForUpload: True
  Package: at-spi2-core 2.10.0-0ubuntu2 [modified: 
usr/share/upstart/sessions/at-spi2-registryd.conf]
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 3.11.0-11.17-generic 3.11.3
  Tags:  saucy
  Uname: Linux 3.11.0-11-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm admin audio cdrom dialout libvirtd lpadmin netdev plugdev 
sambashare users video
  modified.conffile..etc.xdg.autostart.at.spi.dbus.bus.desktop: [modified]
  mtime.conffile..etc.xdg.autostart.at.spi.dbus.bus.desktop: 
2013-07-24T01:24:45.829666

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/at-spi2-core/+bug/1236346/+subscriptions

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

[Desktop-packages] [Bug 1236346] [NEW] at-spi2-registryd.conf upstart script missing closing ']'

[Haw Loeung]

Public bug reported:

Hi,

I'm seeing a bunch of missing ']' errors in ~/.cache/upstart/at-
spi2-registryd.log. It seems this is because the 'pre-start' stanza is
missing a closing ']' as shown below:

pre-start script
[ $(gsettings get org.gnome.desktop.interface toolkit-accessibility) \
 = true || exit 0
end script

It seems like an easy fix but I can't seem to find which LP branch to
create a merge proposal against.

Regards,

Haw
--- 
ApportVersion: 2.12.5-0ubuntu1
Architecture: amd64
DistroRelease: Ubuntu 13.10
MarkForUpload: True
Package: at-spi2-core 2.10.0-0ubuntu2 [modified: 
usr/share/upstart/sessions/at-spi2-registryd.conf]
PackageArchitecture: amd64
ProcVersionSignature: Ubuntu 3.11.0-11.17-generic 3.11.3
Tags:  saucy
Uname: Linux 3.11.0-11-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm admin audio cdrom dialout libvirtd lpadmin netdev plugdev 
sambashare users video
modified.conffile..etc.xdg.autostart.at.spi.dbus.bus.desktop: [modified]
mtime.conffile..etc.xdg.autostart.at.spi.dbus.bus.desktop: 
2013-07-24T01:24:45.829666

** Affects: at-spi2-core (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: apport-collected saucy

** Tags added: saucy

** Tags added: apport-collected

** Description changed:

  Hi,
  
  I'm seeing a bunch of missing ']' errors in ~/.cache/upstart/at-
  spi2-registryd.log. It seems this is because the 'pre-start' stanza is
  missing a closing ']' as shown below:
  
  pre-start script
  [ $(gsettings get org.gnome.desktop.interface toolkit-accessibility) \
   = true || exit 0
  end script
  
  It seems like an easy fix but I can't seem to find which LP branch to
  create a merge proposal against.
  
  Regards,
  
  Haw
+ --- 
+ ApportVersion: 2.12.5-0ubuntu1
+ Architecture: amd64
+ DistroRelease: Ubuntu 13.10
+ MarkForUpload: True
+ Package: at-spi2-core 2.10.0-0ubuntu2 [modified: 
usr/share/upstart/sessions/at-spi2-registryd.conf]
+ PackageArchitecture: amd64
+ ProcVersionSignature: Ubuntu 3.11.0-11.17-generic 3.11.3
+ Tags:  saucy
+ Uname: Linux 3.11.0-11-generic x86_64
+ UpgradeStatus: No upgrade log present (probably fresh install)
+ UserGroups: adm admin audio cdrom dialout libvirtd lpadmin netdev plugdev 
sambashare users video
+ modified.conffile..etc.xdg.autostart.at.spi.dbus.bus.desktop: [modified]
+ mtime.conffile..etc.xdg.autostart.at.spi.dbus.bus.desktop: 
2013-07-24T01:24:45.829666

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

Title:
  at-spi2-registryd.conf upstart script missing closing ']'

Status in “at-spi2-core” package in Ubuntu:
  New

Bug description:
  Hi,

  I'm seeing a bunch of missing ']' errors in ~/.cache/upstart/at-
  spi2-registryd.log. It seems this is because the 'pre-start' stanza is
  missing a closing ']' as shown below:

  pre-start script
  [ $(gsettings get org.gnome.desktop.interface toolkit-accessibility) \
   = true || exit 0
  end script

  It seems like an easy fix but I can't seem to find which LP branch to
  create a merge proposal against.

  Regards,

  Haw
  --- 
  ApportVersion: 2.12.5-0ubuntu1
  Architecture: amd64
  DistroRelease: Ubuntu 13.10
  MarkForUpload: True
  Package: at-spi2-core 2.10.0-0ubuntu2 [modified: 
usr/share/upstart/sessions/at-spi2-registryd.conf]
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 3.11.0-11.17-generic 3.11.3
  Tags:  saucy
  Uname: Linux 3.11.0-11-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm admin audio cdrom dialout libvirtd lpadmin netdev plugdev 
sambashare users video
  modified.conffile..etc.xdg.autostart.at.spi.dbus.bus.desktop: [modified]
  mtime.conffile..etc.xdg.autostart.at.spi.dbus.bus.desktop: 
2013-07-24T01:24:45.829666

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/at-spi2-core/+bug/1236346/+subscriptions

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

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

[Haw Loeung]

apport information

** Attachment added: ProcEnviron.txt
   
https://bugs.launchpad.net/bugs/1236346/+attachment/3864207/+files/ProcEnviron.txt

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

Title:
  at-spi2-registryd.conf upstart script missing closing ']'

Status in “at-spi2-core” package in Ubuntu:
  New

Bug description:
  Hi,

  I'm seeing a bunch of missing ']' errors in ~/.cache/upstart/at-
  spi2-registryd.log. It seems this is because the 'pre-start' stanza is
  missing a closing ']' as shown below:

  pre-start script
  [ $(gsettings get org.gnome.desktop.interface toolkit-accessibility) \
   = true || exit 0
  end script

  It seems like an easy fix but I can't seem to find which LP branch to
  create a merge proposal against.

  Regards,

  Haw
  --- 
  ApportVersion: 2.12.5-0ubuntu1
  Architecture: amd64
  DistroRelease: Ubuntu 13.10
  MarkForUpload: True
  Package: at-spi2-core 2.10.0-0ubuntu2 [modified: 
usr/share/upstart/sessions/at-spi2-registryd.conf]
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 3.11.0-11.17-generic 3.11.3
  Tags:  saucy
  Uname: Linux 3.11.0-11-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm admin audio cdrom dialout libvirtd lpadmin netdev plugdev 
sambashare users video
  modified.conffile..etc.xdg.autostart.at.spi.dbus.bus.desktop: [modified]
  mtime.conffile..etc.xdg.autostart.at.spi.dbus.bus.desktop: 
2013-07-24T01:24:45.829666

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/at-spi2-core/+bug/1236346/+subscriptions

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

[Desktop-packages] [Bug 1236346] Re: at-spi2-registryd.conf upstart script missing closing ']'

[Haw Loeung]

https://launchpadlibrarian.net/152758649/at-
spi2-core_2.10.0-0ubuntu2_2.10.0-0ubuntu2~ppa.diff.gz

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

Title:
  at-spi2-registryd.conf upstart script missing closing ']'

Status in “at-spi2-core” package in Ubuntu:
  New

Bug description:
  Hi,

  I'm seeing a bunch of missing ']' errors in ~/.cache/upstart/at-
  spi2-registryd.log. It seems this is because the 'pre-start' stanza is
  missing a closing ']' as shown below:

  pre-start script
  [ $(gsettings get org.gnome.desktop.interface toolkit-accessibility) \
   = true || exit 0
  end script

  It seems like an easy fix but I can't seem to find which LP branch to
  create a merge proposal against.

  Regards,

  Haw
  --- 
  ApportVersion: 2.12.5-0ubuntu1
  Architecture: amd64
  DistroRelease: Ubuntu 13.10
  MarkForUpload: True
  Package: at-spi2-core 2.10.0-0ubuntu2 [modified: 
usr/share/upstart/sessions/at-spi2-registryd.conf]
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 3.11.0-11.17-generic 3.11.3
  Tags:  saucy
  Uname: Linux 3.11.0-11-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm admin audio cdrom dialout libvirtd lpadmin netdev plugdev 
sambashare users video
  modified.conffile..etc.xdg.autostart.at.spi.dbus.bus.desktop: [modified]
  mtime.conffile..etc.xdg.autostart.at.spi.dbus.bus.desktop: 
2013-07-24T01:24:45.829666

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/at-spi2-core/+bug/1236346/+subscriptions

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

[Desktop-packages] [Bug 1203592] Re: Keyboard backlight does not work in Samsung Series 9 NP900X4C

[Haw Loeung]

** Changed in: gnome-settings-daemon (Ubuntu)
   Importance: Undecided = Medium

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

Title:
  Keyboard backlight does not work in Samsung Series 9 NP900X4C

Status in “gnome-settings-daemon” package in Ubuntu:
  Confirmed

Bug description:
  In Ubuntu 13.04, the keyboard backlight does not work in Samsung
  Series 9 NP900X4C.

  Adding the FN key mappings as described in
  https://help.ubuntu.com/community/SamsungSeries9 does show information
  in the notification area when pressing the keyboard backlight's + and
  - buttons, but:

  1) The notification always identifies the backlight as full max
  2) It has no effect on the backlight - it's always off

  When I first installed Ubuntu on this machine (12.10), even though the
  fn keys never worked I did have intermitent backlight functionality -
  the light sensor would sometimes work and I'd see light in the
  keyboard.

  I dual boot in Windows 8 and backlighting works there, so this is not
  a hardware issue.

  More discussion can be found here:
  http://askubuntu.com/questions/233312/how-to-make-keyboard-backlight-
  fn-buttons-work-in-samsung-series-9

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

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

[Desktop-packages] [Bug 1203211] Re: Modprobe doesn't recognize any parameters on 3.10.0-4

[Haw Loeung]

Hi,

FYI, 3.10.0-5 works fine for me. Thanks.

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

Title:
  Modprobe doesn't recognize any parameters on 3.10.0-4

Status in “gdm” package in Ubuntu:
  Invalid
Status in “linux” package in Ubuntu:
  Fix Committed

Bug description:
  After updating today to kernel 3.10.0-4 on Ubuntu GNOME 13.10 (Macbook
  Pro 8,2), I am unable to boot graphically. Recovery mode boot works
  fine. When attempting to boot using integrated graphics, the syslog
  gets spammed with this sequence of errors over and over:

  Jul 19 19:07:09 polarimetric-MacBookPro acpid: 1 client rule loaded
  Jul 19 19:07:09 polarimetric-MacBookPro kernel: [   26.475546] i915: Unknown 
parameter `modeset'
  Jul 19 19:07:09 polarimetric-MacBookPro gdm-simple-slave[1426]: Child process 
1432 was already dead.
  Jul 19 19:07:09 polarimetric-MacBookPro gdm-simple-slave[1426]: GLib-GObject: 
g_object_ref: assertion 'object-ref_count  0' failed
  Jul 19 19:07:09 polarimetric-MacBookPro gdm-simple-slave[1426]: GLib-GObject: 
g_object_unref: assertion 'object-ref_count  0' failed
  Jul 19 19:07:09 polarimetric-MacBookPro gdm[1189]: GdmDisplay: display lasted 
0.096139 seconds
  Jul 19 19:07:09 polarimetric-MacBookPro gdm[1189]: GdmDisplay: display lasted 
0.097622 seconds
  Jul 19 19:07:09 polarimetric-MacBookPro acpid: client 1432[0:0] has 
disconnected

  This error only occurs if modprobe parameters are passed at boot, so
  the problem appears to be with modprobe. All module parameters are
  said to be invalid. After boot, attempting to insert a module results
  in the same error.

  EDIT: Please ignore the version string in the below information; I'm
  reporting this bug from 3.10.0-3 but it only affects 3.10.0-4.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: linux-image-3.10.0-3-generic 3.10.0-3.12
  ProcVersionSignature: Ubuntu 3.10.0-3.12-generic 3.10.1
  Uname: Linux 3.10.0-3-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.11-0ubuntu1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  polarimetric   1862 F pulseaudio
  Date: Fri Jul 19 19:35:57 2013
  HibernationDevice: RESUME=UUID=8b32a68d-d883-4492-8fa1-a2cf30529ec6
  InstallationDate: Installed on 2013-06-06 (43 days ago)
  InstallationMedia: Ubuntu-GNOME 13.04 Raring Ringtail - Release amd64 
(20130424)
  MachineType: Apple Inc. MacBookPro8,2
  MarkForUpload: True
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=set
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB:
   0 EFI VGA
   1 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.10.0-3-generic 
root=UUID=070a2baf-a3a7-4034-aeaf-419e7b9df4f7 ro quiet splash i915.modeset=1 
i915.lvds_channel_mode=2 i915.lvds_use_ssc=0 intel_pstate=enable vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-3.10.0-3-generic N/A
   linux-backports-modules-3.10.0-3-generic  N/A
   linux-firmware1.112
  SourcePackage: linux
  UpgradeStatus: Upgraded to saucy on 2013-06-28 (21 days ago)
  dmi.bios.date: 01/24/12
  dmi.bios.vendor: Apple Inc.
  dmi.bios.version: MBP81.88Z.0047.B27.1201241646
  dmi.board.asset.tag: Base Board Asset Tag#
  dmi.board.name: Mac-94245A3940C91C80
  dmi.board.vendor: Apple Inc.
  dmi.board.version: MacBookPro8,2
  dmi.chassis.type: 10
  dmi.chassis.vendor: Apple Inc.
  dmi.chassis.version: Mac-94245A3940C91C80
  dmi.modalias: 
dmi:bvnAppleInc.:bvrMBP81.88Z.0047.B27.1201241646:bd01/24/12:svnAppleInc.:pnMacBookPro8,2:pvr1.0:rvnAppleInc.:rnMac-94245A3940C91C80:rvrMacBookPro8,2:cvnAppleInc.:ct10:cvrMac-94245A3940C91C80:
  dmi.product.name: MacBookPro8,2
  dmi.product.version: 1.0
  dmi.sys.vendor: Apple Inc.

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

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

[Desktop-packages] [Bug 1193913] Re: gnome-session-properties hits an error if there is no entry to list

[Haw Loeung]

Hi ,

Workaround would be to copy a file from /etc/xdg/autostart/, then edit
it and replace NoDisplay=true to NoDisplay=false.

Hope this helps.

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

Title:
  gnome-session-properties hits an error if there is no entry to list

Status in The GNOME 2 Session Manager:
  New
Status in “gnome-session” package in Ubuntu:
  Confirmed

Bug description:
  Launching gnome-session-properties causes the following error in
  13.10:

  (gnome-session-properties:13462): Gtk-ERROR **: GtkBox child 
GtkScrolledWindow minimum width: -1  0 for height 331
  Trace/breakpoint trap (core dumped)

  ProblemType: Crash
  DistroRelease: Ubuntu 13.10
  Package: gnome-session-bin 3.8.2.1-1ubuntu2
  ProcVersionSignature: Ubuntu 3.9.0-6.14-generic 3.9.6
  Uname: Linux 3.9.0-6-generic x86_64
  ApportVersion: 2.10.2-0ubuntu2
  Architecture: amd64
  Date: Sun Jun 23 22:10:25 2013
  ExecutablePath: /usr/bin/gnome-session-properties
  InstallationDate: Installed on 2013-06-16 (7 days ago)
  InstallationMedia: Ubuntu 13.10 Saucy Salamander - Alpha amd64 (20130615)
  MarkForUpload: True
  ProcCmdline: gnome-session-properties
  Signal: 5
  SourcePackage: gnome-session
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
   g_cclosure_marshal_VOID__BOXEDv () from 
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   g_signal_emit_valist () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   g_signal_emit () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
  Title: gnome-session-properties crashed with signal 5 in 
g_cclosure_marshal_VOID__BOXEDv()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

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

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

[Desktop-packages] [Bug 1018307] Re: SSL renegotiation fails

[Haw Loeung]

** Tags added: canonical-webops

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

Title:
  SSL renegotiation fails

Status in “openssl” package in Ubuntu:
  Confirmed
Status in “postgresql-9.1” package in Ubuntu:
  Confirmed

Bug description:
  With PostgreSQL 9.1, SSL renegotiation is enabled by default. This
  fails under Ubuntu 12.04, most noticeably when using streaming
  replication as the renegotiation limit is hit quickly.

  On the master:

  2012-06-25 16:16:26 PDT LOG:  SSL renegotiation failure
  2012-06-25 16:16:26 PDT LOG:  SSL error: unexpected record
  2012-06-25 16:16:26 PDT LOG:  could not send data to client: Connection reset 
by peer

  On the hot standby:

  2012-06-25 11:12:11 PDT FATAL:  could not receive data from WAL stream: SSL 
error: sslv3 alert unexpected message
  2012-06-25 11:12:11 PDT LOG:  record with zero length at 1C5/95D2FE00

  If our SSL libraries do not support SSL renegotiation, the default
  setting is wrong and perhaps warnings emitted if attempts are made to
  enable it.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: postgresql-9.1 9.1.4-0ubuntu12.04
  ProcVersionSignature: Ubuntu 3.2.0-25.40-generic 3.2.18
  Uname: Linux 3.2.0-25-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.0.1-0ubuntu8
  Architecture: amd64
  Date: Wed Jun 27 16:38:33 2012
  ProcEnviron:
   LANGUAGE=en_AU:en
   TERM=xterm
   PATH=(custom, user)
   LANG=en_AU.UTF-8
   SHELL=/bin/bash
  SourcePackage: postgresql-9.1
  UpgradeStatus: Upgraded to precise on 2012-04-27 (60 days ago)

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

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

[Desktop-packages] [Bug 1143448] [NEW] colord postinst fails with 27: [: which: unexpected operator

[Haw Loeung]

Public bug reported:

Hi,

Just ran a dist-upgrade and noticed that the post-install script for
colord fails:

$ sudo apt-get dist-upgrade 
Reading package lists... Done
Building dependency tree   
Reading state information... Done
Calculating upgrade... Done
The following NEW packages will be installed:
  libcolorhug1
The following packages will be upgraded:
  colord libcolord1 libgusb2 python-logilab-common
4 upgraded, 1 newly installed, 0 to remove and 0 not upgraded.
Need to get 1,143 kB of archives.
After this operation, 620 kB of additional disk space will be used.
Do you want to continue [Y/n]? y
Get:1 http://archive.ubuntu.com/ubuntu/ raring/main libgusb2 amd64 
0.1.5-0ubuntu1 [18.5 kB]
Get:2 http://archive.ubuntu.com/ubuntu/ raring-proposed/main libcolord1 amd64 
0.1.30-0ubuntu2 [85.6 kB]
Get:3 http://archive.ubuntu.com/ubuntu/ raring-proposed/universe libcolorhug1 
amd64 0.1.30-0ubuntu2 [25.4 kB]
Get:4 http://archive.ubuntu.com/ubuntu/ raring-proposed/main colord amd64 
0.1.30-0ubuntu2 [264 kB]
Get:5 http://archive.ubuntu.com/ubuntu/ raring/main python-logilab-common all 
0.58.3-1ubuntu1 [750 kB]
Fetched 1,143 kB in 12s (92.6 kB/s)
(Reading database ... 192532 files and directories currently installed.)
Preparing to replace libgusb2 0.1.3-5 (using 
.../libgusb2_0.1.5-0ubuntu1_amd64.deb) ...
Unpacking replacement libgusb2:amd64 ...
Preparing to replace libcolord1:amd64 0.1.23-0ubuntu3 (using 
.../libcolord1_0.1.30-0ubuntu2_amd64.deb) ...
Unpacking replacement libcolord1:amd64 ...
Selecting previously unselected package libcolorhug1:amd64.
Unpacking libcolorhug1:amd64 (from .../libcolorhug1_0.1.30-0ubuntu2_amd64.deb) 
...
Preparing to replace colord 0.1.23-0ubuntu3 (using 
.../colord_0.1.30-0ubuntu2_amd64.deb) ...
Unpacking replacement colord ...
Preparing to replace python-logilab-common 0.58.0-1ubuntu1 (using 
.../python-logilab-common_0.58.3-1ubuntu1_all.deb) ...
Unpacking replacement python-logilab-common ...
Processing triggers for libglib2.0-0:amd64 ...
Processing triggers for man-db ...
Processing triggers for doc-base ...
Processing 1 changed doc-base file...
Registering documents with scrollkeeper...
Setting up libgusb2:amd64 (0.1.5-0ubuntu1) ...
Setting up libcolord1:amd64 (0.1.30-0ubuntu2) ...
Setting up libcolorhug1:amd64 (0.1.30-0ubuntu2) ...
Setting up colord (0.1.30-0ubuntu2) ...
Installing new version of config file /etc/colord.conf ...
Installing new version of config file 
/etc/bash_completion.d/colormgr-completion.bash ...
/var/lib/dpkg/info/colord.postinst: 27: [: which: unexpected operator
Setting up python-logilab-common (0.58.3-1ubuntu1) ...
Processing triggers for libc-bin ...
ldconfig deferred processing now taking place
localepurge: Disk space freed in /usr/share/locale: 0 KiB
localepurge: Disk space freed in /usr/share/man: 0 KiB
localepurge: Disk space freed in /usr/share/gnome/help: 0 KiB
localepurge: Disk space freed in /usr/share/omf: 0 KiB
localepurge: Disk space freed in /usr/share/doc/kde/HTML: 0 KiB

Total disk space freed by localepurge: 0 KiB

ProblemType: Bug
DistroRelease: Ubuntu 13.04
Package: colord 0.1.30-0ubuntu2
ProcVersionSignature: Ubuntu 3.8.0-9.18-generic 3.8.1
Uname: Linux 3.8.0-9-generic x86_64
ApportVersion: 2.9-0ubuntu2
Architecture: amd64
Date: Mon Mar  4 14:55:57 2013
MarkForUpload: True
ProcEnviron:
 LANGUAGE=
 TERM=xterm
 PATH=(custom, no user)
 LANG=en_AU.UTF-8
 SHELL=/bin/bash
SourcePackage: colord
UpgradeStatus: Upgraded to raring on 2012-12-06 (87 days ago)

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


** Tags: amd64 apport-bug package-from-proposed raring

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

Title:
  colord postinst fails with 27: [: which: unexpected operator

Status in “colord” package in Ubuntu:
  New

Bug description:
  Hi,

  Just ran a dist-upgrade and noticed that the post-install script for
  colord fails:

  $ sudo apt-get dist-upgrade 
  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  Calculating upgrade... Done
  The following NEW packages will be installed:
libcolorhug1
  The following packages will be upgraded:
colord libcolord1 libgusb2 python-logilab-common
  4 upgraded, 1 newly installed, 0 to remove and 0 not upgraded.
  Need to get 1,143 kB of archives.
  After this operation, 620 kB of additional disk space will be used.
  Do you want to continue [Y/n]? y
  Get:1 http://archive.ubuntu.com/ubuntu/ raring/main libgusb2 amd64 
0.1.5-0ubuntu1 [18.5 kB]
  Get:2 http://archive.ubuntu.com/ubuntu/ raring-proposed/main libcolord1 amd64 
0.1.30-0ubuntu2 [85.6 kB]
  Get:3 http://archive.ubuntu.com/ubuntu/ raring-proposed/universe libcolorhug1 
amd64 0.1.30-0ubuntu2 [25.4 kB]
  Get:4 http://archive.ubuntu.com/ubuntu/ raring-proposed/main colord amd64 

[Desktop-packages] [Bug 1143448] Re: colord postinst fails with 27: [: which: unexpected operator

[Haw Loeung]

** Branch linked: lp:~hloeung/ubuntu/raring/colord/fix-postinst

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

Title:
  colord postinst fails with 27: [: which: unexpected operator

Status in “colord” package in Ubuntu:
  New

Bug description:
  Hi,

  Just ran a dist-upgrade and noticed that the post-install script for
  colord fails:

  $ sudo apt-get dist-upgrade 
  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  Calculating upgrade... Done
  The following NEW packages will be installed:
libcolorhug1
  The following packages will be upgraded:
colord libcolord1 libgusb2 python-logilab-common
  4 upgraded, 1 newly installed, 0 to remove and 0 not upgraded.
  Need to get 1,143 kB of archives.
  After this operation, 620 kB of additional disk space will be used.
  Do you want to continue [Y/n]? y
  Get:1 http://archive.ubuntu.com/ubuntu/ raring/main libgusb2 amd64 
0.1.5-0ubuntu1 [18.5 kB]
  Get:2 http://archive.ubuntu.com/ubuntu/ raring-proposed/main libcolord1 amd64 
0.1.30-0ubuntu2 [85.6 kB]
  Get:3 http://archive.ubuntu.com/ubuntu/ raring-proposed/universe libcolorhug1 
amd64 0.1.30-0ubuntu2 [25.4 kB]
  Get:4 http://archive.ubuntu.com/ubuntu/ raring-proposed/main colord amd64 
0.1.30-0ubuntu2 [264 kB]
  Get:5 http://archive.ubuntu.com/ubuntu/ raring/main python-logilab-common all 
0.58.3-1ubuntu1 [750 kB]
  Fetched 1,143 kB in 12s (92.6 kB/s)   
 
  (Reading database ... 192532 files and directories currently installed.)
  Preparing to replace libgusb2 0.1.3-5 (using 
.../libgusb2_0.1.5-0ubuntu1_amd64.deb) ...
  Unpacking replacement libgusb2:amd64 ...
  Preparing to replace libcolord1:amd64 0.1.23-0ubuntu3 (using 
.../libcolord1_0.1.30-0ubuntu2_amd64.deb) ...
  Unpacking replacement libcolord1:amd64 ...
  Selecting previously unselected package libcolorhug1:amd64.
  Unpacking libcolorhug1:amd64 (from 
.../libcolorhug1_0.1.30-0ubuntu2_amd64.deb) ...
  Preparing to replace colord 0.1.23-0ubuntu3 (using 
.../colord_0.1.30-0ubuntu2_amd64.deb) ...
  Unpacking replacement colord ...
  Preparing to replace python-logilab-common 0.58.0-1ubuntu1 (using 
.../python-logilab-common_0.58.3-1ubuntu1_all.deb) ...
  Unpacking replacement python-logilab-common ...
  Processing triggers for libglib2.0-0:amd64 ...
  Processing triggers for man-db ...
  Processing triggers for doc-base ...
  Processing 1 changed doc-base file...
  Registering documents with scrollkeeper...
  Setting up libgusb2:amd64 (0.1.5-0ubuntu1) ...
  Setting up libcolord1:amd64 (0.1.30-0ubuntu2) ...
  Setting up libcolorhug1:amd64 (0.1.30-0ubuntu2) ...
  Setting up colord (0.1.30-0ubuntu2) ...
  Installing new version of config file /etc/colord.conf ...
  Installing new version of config file 
/etc/bash_completion.d/colormgr-completion.bash ...
  /var/lib/dpkg/info/colord.postinst: 27: [: which: unexpected operator
  Setting up python-logilab-common (0.58.3-1ubuntu1) ...
  Processing triggers for libc-bin ...
  ldconfig deferred processing now taking place
  localepurge: Disk space freed in /usr/share/locale: 0 KiB
  localepurge: Disk space freed in /usr/share/man: 0 KiB
  localepurge: Disk space freed in /usr/share/gnome/help: 0 KiB
  localepurge: Disk space freed in /usr/share/omf: 0 KiB
  localepurge: Disk space freed in /usr/share/doc/kde/HTML: 0 KiB

  Total disk space freed by localepurge: 0 KiB

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: colord 0.1.30-0ubuntu2
  ProcVersionSignature: Ubuntu 3.8.0-9.18-generic 3.8.1
  Uname: Linux 3.8.0-9-generic x86_64
  ApportVersion: 2.9-0ubuntu2
  Architecture: amd64
  Date: Mon Mar  4 14:55:57 2013
  MarkForUpload: True
  ProcEnviron:
   LANGUAGE=
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_AU.UTF-8
   SHELL=/bin/bash
  SourcePackage: colord
  UpgradeStatus: Upgraded to raring on 2012-12-06 (87 days ago)

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

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

[Desktop-packages] [Bug 1070512] Re: The launcher in unity won't start konsole

[Haw Loeung]

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

** This bug is no longer a duplicate of bug 1070605
   Konsole fails to launch in 12.10 - Failed to change to directory '$HOME' 
(No such file or directory)
** This bug has been marked a duplicate of bug 1068451
   konsole app is not accessible via Unity

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

Title:
  The launcher in unity won't start konsole

Status in “unity” package in Ubuntu:
  Confirmed

Bug description:
  Launching konsole from the launcher in Quantal doesn't work. Launching
  it from the command line, however, works fine. Launching it from the
  dash doesn't work either.

  STEPS TO REPRODUCE
  1. Install konsole
  2. Try to start it from the dash by typing konsole on it (konsole won't 
launch)
  3. Start it from gnome-terminal and lock it to the launcher
  4. Try to start it from the launcher and it won't launch

  This is on quantal

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

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

[Desktop-packages] [Bug 881959] [NEW] Running friendly, the video capture doesn't work

[Haw Loeung]

Public bug reported:

Just trying to run the friendly Ubuntu System Testing tool, the video
capture doesn't seem to work

ProblemType: Bug
DistroRelease: Ubuntu 11.10
Package: python-gst0.10 0.10.21-2ubuntu1
ProcVersionSignature: Ubuntu 3.0.0-13.21-generic 3.0.6
Uname: Linux 3.0.0-13-generic x86_64
ApportVersion: 1.23-0ubuntu4
Architecture: amd64
CheckboxCommand: camera_test -t video
CheckboxDescription:
 Select Test to capture video to a file and open it in totem.
 Please make sure that both audio and video is captured.
 
 Did you see/hear the capture?
CheckboxTest: camera/video
Date: Wed Oct 26 22:14:07 2011
InstallationMedia: Ubuntu 11.04 Natty Narwhal - Beta amd64 (20110413)
ProcEnviron:
 SHELL=/bin/bash
 PATH=(custom, no user)
 LC_MESSAGES=en_AU.UTF-8
 LANG=en_AU.UTF-8
 LANGUAGE=en_AU:en_GB:en
SourcePackage: gst0.10-python
UpgradeStatus: Upgraded to oneiric on 2011-09-01 (54 days ago)

** Affects: gst0.10-python (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug capture checkbox-bug oneiric running-unity

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

Title:
  Running friendly, the video capture doesn't work

Status in “gst0.10-python” package in Ubuntu:
  New

Bug description:
  Just trying to run the friendly Ubuntu System Testing tool, the
  video capture doesn't seem to work

  ProblemType: Bug
  DistroRelease: Ubuntu 11.10
  Package: python-gst0.10 0.10.21-2ubuntu1
  ProcVersionSignature: Ubuntu 3.0.0-13.21-generic 3.0.6
  Uname: Linux 3.0.0-13-generic x86_64
  ApportVersion: 1.23-0ubuntu4
  Architecture: amd64
  CheckboxCommand: camera_test -t video
  CheckboxDescription:
   Select Test to capture video to a file and open it in totem.
   Please make sure that both audio and video is captured.
   
   Did you see/hear the capture?
  CheckboxTest: camera/video
  Date: Wed Oct 26 22:14:07 2011
  InstallationMedia: Ubuntu 11.04 Natty Narwhal - Beta amd64 (20110413)
  ProcEnviron:
   SHELL=/bin/bash
   PATH=(custom, no user)
   LC_MESSAGES=en_AU.UTF-8
   LANG=en_AU.UTF-8
   LANGUAGE=en_AU:en_GB:en
  SourcePackage: gst0.10-python
  UpgradeStatus: Upgraded to oneiric on 2011-09-01 (54 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gst0.10-python/+bug/881959/+subscriptions

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

[Desktop-packages] [Bug 881959] Re: Running friendly, the video capture doesn't work

[Haw Loeung]

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

Title:
  Running friendly, the video capture doesn't work

Status in “gst0.10-python” package in Ubuntu:
  New

Bug description:
  Just trying to run the friendly Ubuntu System Testing tool, the
  video capture doesn't seem to work

  ProblemType: Bug
  DistroRelease: Ubuntu 11.10
  Package: python-gst0.10 0.10.21-2ubuntu1
  ProcVersionSignature: Ubuntu 3.0.0-13.21-generic 3.0.6
  Uname: Linux 3.0.0-13-generic x86_64
  ApportVersion: 1.23-0ubuntu4
  Architecture: amd64
  CheckboxCommand: camera_test -t video
  CheckboxDescription:
   Select Test to capture video to a file and open it in totem.
   Please make sure that both audio and video is captured.
   
   Did you see/hear the capture?
  CheckboxTest: camera/video
  Date: Wed Oct 26 22:14:07 2011
  InstallationMedia: Ubuntu 11.04 Natty Narwhal - Beta amd64 (20110413)
  ProcEnviron:
   SHELL=/bin/bash
   PATH=(custom, no user)
   LC_MESSAGES=en_AU.UTF-8
   LANG=en_AU.UTF-8
   LANGUAGE=en_AU:en_GB:en
  SourcePackage: gst0.10-python
  UpgradeStatus: Upgraded to oneiric on 2011-09-01 (54 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gst0.10-python/+bug/881959/+subscriptions

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