[Desktop-packages] [Bug 1961508] Re: Dock displaying over window after resuming from blank screen

[Edward]

@popov895 Your extension seems to work. I bought you a "coffee". :)

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

Title:
  Dock displaying over window after resuming from blank screen

Status in Dash to dock:
  Unknown
Status in Mutter:
  New
Status in gnome-shell package in Ubuntu:
  Confirmed
Status in gnome-shell-extension-ubuntu-dock package in Ubuntu:
  Won't Fix
Status in mutter package in Ubuntu:
  In Progress
Status in gnome-desktop package in Fedora:
  Confirmed

Bug description:
  I have Blank Screen set to happen after 2 minutes of inactivity.

  When resuming from a Blank Screen (by moving the mouse or touching the
  keyboard), the Dock is displayed over the top of the current program.

  To get it back to normal I need to click "Restore Down" on the current
  programs window and then "Maximize" so that the Dock no longer
  overlaps it.

  (Note: I have Auto-hide dock turned off.)

  This only happens sometimes. I can't reproduce the bug it every time.

  -

  1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> 
About Ubuntu
  - Ubuntu 21.10

  2) The version of the package you are using, via 'apt-cache policy pkgname' 
or by checking in Software Center
  - Not sure (I guess the Dock is part of the Gnome interface?)

  3) What you expected to happen
  - Dock should not overlap the current program on resume from screen blank.

  4) What happened instead
  - The Dock overlaps the current program on resume from screen blank.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu71
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 21.10
  InstallationDate: Installed on 2022-02-18 (24 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  Package: gnome-shell-extension-ubuntu-dock
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.13.0-35.40-generic 5.13.19
  RelatedPackageVersions: mutter-common 40.5-1ubuntu3~21.10.1
  Tags:  wayland-session impish
  Uname: Linux 5.13.0-35-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  --- 
  ProblemType: Bug
  ApportVersion: 2.23.1-0ubuntu3
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 22.10
  InstallationDate: Installed on 2022-02-18 (328 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  Package: mutter
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.19.0-28.29-generic 5.19.17
  RebootRequiredPkgs: Error: path contained symlinks.
  RelatedPackageVersions: mutter-common 43.0-1ubuntu4
  Tags: wayland-session third-party-packages kinetic
  Uname: Linux 5.19.0-28-generic x86_64
  UpgradeStatus: Upgraded to kinetic on 2022-10-25 (79 days ago)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/dash-to-dock/+bug/1961508/+subscriptions


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

[Desktop-packages] [Bug 1961508] Re: Dock displaying over window after resuming from blank screen

[Edward]

The problem persists. Ubuntu 23.10 / Gnome 45. I'm so used to just re-
maximizing every window now.

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

Title:
  Dock displaying over window after resuming from blank screen

Status in Dash to dock:
  Unknown
Status in Mutter:
  New
Status in gnome-shell package in Ubuntu:
  Confirmed
Status in gnome-shell-extension-ubuntu-dock package in Ubuntu:
  Won't Fix
Status in mutter package in Ubuntu:
  In Progress
Status in gnome-desktop package in Fedora:
  Confirmed

Bug description:
  I have Blank Screen set to happen after 2 minutes of inactivity.

  When resuming from a Blank Screen (by moving the mouse or touching the
  keyboard), the Dock is displayed over the top of the current program.

  To get it back to normal I need to click "Restore Down" on the current
  programs window and then "Maximize" so that the Dock no longer
  overlaps it.

  (Note: I have Auto-hide dock turned off.)

  This only happens sometimes. I can't reproduce the bug it every time.

  -

  1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> 
About Ubuntu
  - Ubuntu 21.10

  2) The version of the package you are using, via 'apt-cache policy pkgname' 
or by checking in Software Center
  - Not sure (I guess the Dock is part of the Gnome interface?)

  3) What you expected to happen
  - Dock should not overlap the current program on resume from screen blank.

  4) What happened instead
  - The Dock overlaps the current program on resume from screen blank.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu71
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 21.10
  InstallationDate: Installed on 2022-02-18 (24 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  Package: gnome-shell-extension-ubuntu-dock
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.13.0-35.40-generic 5.13.19
  RelatedPackageVersions: mutter-common 40.5-1ubuntu3~21.10.1
  Tags:  wayland-session impish
  Uname: Linux 5.13.0-35-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  --- 
  ProblemType: Bug
  ApportVersion: 2.23.1-0ubuntu3
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 22.10
  InstallationDate: Installed on 2022-02-18 (328 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  Package: mutter
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.19.0-28.29-generic 5.19.17
  RebootRequiredPkgs: Error: path contained symlinks.
  RelatedPackageVersions: mutter-common 43.0-1ubuntu4
  Tags: wayland-session third-party-packages kinetic
  Uname: Linux 5.19.0-28-generic x86_64
  UpgradeStatus: Upgraded to kinetic on 2022-10-25 (79 days ago)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/dash-to-dock/+bug/1961508/+subscriptions


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

[Desktop-packages] [Bug 2009005] Re: snap version 110.0.5481.177 cant open meets and calendar seems broken

[Edward Hope-Morley]

https://answers.launchpad.net/ubuntu/+question/705683

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

Title:
  snap version 110.0.5481.177 cant open meets and calendar seems broken

Status in chromium-browser package in Ubuntu:
  New

Bug description:
  With the latest version of chromium snap 110.0.5481.177 installed
  yesterday I am no longer able to use google meet or view my google
  calendar.

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


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

[Desktop-packages] [Bug 2009005] [NEW] snap version 110.0.5481.177 cant open meets and calendar seems broken

[Edward Hope-Morley]

Public bug reported:

With the latest version of chromium snap 110.0.5481.177 installed
yesterday I am no longer able to use google meet or view my google
calendar.

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

Title:
  snap version 110.0.5481.177 cant open meets and calendar seems broken

Status in chromium-browser package in Ubuntu:
  New

Bug description:
  With the latest version of chromium snap 110.0.5481.177 installed
  yesterday I am no longer able to use google meet or view my google
  calendar.

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


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

[Desktop-packages] [Bug 1970459] Re: import of ca-certificate in browser does not work

[Edward Karavakis]

How is this not a bug? A crippled version of firefox is being offered by
default without the xdg-desktop-portal-gnome package... I too had to
install in a fresh ubuntu 22.04 installation my institute's Root
Certification Authority Certificate (CERN) and my grid certificate.

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

Title:
  import of ca-certificate in browser does not work

Status in chromium-browser package in Ubuntu:
  Invalid
Status in firefox package in Ubuntu:
  Invalid

Bug description:
  I tried to import a CA root certificate into both Firefox and Chrome.
  In Firefox, the import button just didn't do anything, in Chrome
  pressing "import" hangs up the browser. This means I can't reach the
  intranet of the company I work for.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: ca-certificates 20211016
  ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30
  Uname: Linux 5.15.0-27-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Apr 26 19:16:12 2022
  InstallationDate: Installed on 2022-04-23 (3 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  PackageArchitecture: all
  SourcePackage: ca-certificates
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Desktop-packages] [Bug 1981025] Re: Firefox SNAP update removes icon from desktop

[Edward]

Command doesn't work.

:~$ apport-collect 1981025
The authorization page:
 
(https://launchpad.net/+authorize-token?oauth_token=Kh3CwRWMrWJkRKVgw3MJ_permission=DESKTOP_INTEGRATION)
should be opening in your browser. Use your browser to authorize
this program to access Launchpad on your behalf.
Waiting to hear from Launchpad about your decision...
/usr/bin/xdg-open: 882: firefox: not found
/usr/bin/xdg-open: 882: firefox: not found
xdg-open: no method available for opening 
'https://launchpad.net/+authorize-token?oauth_token=Kh3CwRWMrWJkRKVgw3MJ_permission=DESKTOP_INTEGRATION'

Then when CTRL-C is pressed to end this:

^CTraceback (most recent call last):
  File "/usr/bin/apport-cli", line 387, in 
if not app.run_argv():
  File "/usr/lib/python3/dist-packages/apport/ui.py", line 719, in run_argv
return self.run_update_report()
  File "/usr/lib/python3/dist-packages/apport/ui.py", line 566, in 
run_update_report
if not self.crashdb.can_update(self.options.update_report):
  File "/usr/lib/python3/dist-packages/apport/crashdb_impl/launchpad.py", line 
529, in can_update
bug = self.launchpad.bugs[id]
  File "/usr/lib/python3/dist-packages/apport/crashdb_impl/launchpad.py", line 
155, in launchpad
self.__launchpad = Launchpad.login_with('apport-collect',
  File "/usr/lib/python3/dist-packages/launchpadlib/launchpad.py", line 700, in 
login_with
return cls._authorize_token_and_login(
  File "/usr/lib/python3/dist-packages/launchpadlib/launchpad.py", line 451, in 
_authorize_token_and_login
credentials = authorization_engine(credentials, credential_store)
  File "/usr/lib/python3/dist-packages/launchpadlib/credentials.py", line 627, 
in __call__
self.make_end_user_authorize_token(credentials, request_token_string)
  File "/usr/lib/python3/dist-packages/launchpadlib/credentials.py", line 718, 
in make_end_user_authorize_token
self.wait_for_end_user_authorization(credentials)
  File "/usr/lib/python3/dist-packages/launchpadlib/credentials.py", line 813, 
in wait_for_end_user_authorization
if self.check_end_user_authorization(credentials):
  File "/usr/lib/python3/dist-packages/launchpadlib/credentials.py", line 693, 
in check_end_user_authorization
credentials.exchange_request_token_for_access_token(self.web_root)
  File "/usr/lib/python3/dist-packages/launchpadlib/credentials.py", line 240, 
in exchange_request_token_for_access_token
response, content = _http_post(url, headers, params)
  File "/usr/lib/python3/dist-packages/launchpadlib/credentials.py", line 106, 
in _http_post
response, content = httplib2.Http(
  File "/usr/lib/python3/dist-packages/httplib2/__init__.py", line 1725, in 
request
(response, content) = self._request(
  File "/usr/lib/python3/dist-packages/httplib2/__init__.py", line 1441, in 
_request
(response, content) = self._conn_request(conn, request_uri, method, body, 
headers)
  File "/usr/lib/python3/dist-packages/httplib2/__init__.py", line 1393, in 
_conn_request
response = conn.getresponse()
  File "/usr/lib/python3.10/http/client.py", line 1374, in getresponse
response.begin()
  File "/usr/lib/python3.10/http/client.py", line 318, in begin
version, status, reason = self._read_status()
  File "/usr/lib/python3.10/http/client.py", line 279, in _read_status
line = str(self.fp.readline(_MAXLINE + 1), "iso-8859-1")
  File "/usr/lib/python3.10/socket.py", line 705, in readinto
return self._sock.recv_into(b)
  File "/usr/lib/python3.10/ssl.py", line 1273, in recv_into
return self.read(nbytes, buffer)
  File "/usr/lib/python3.10/ssl.py", line 1129, in read
return self._sslobj.read(len, buffer)
KeyboardInterrupt

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

Title:
  Firefox SNAP update removes icon from desktop

Status in firefox package in Ubuntu:
  New

Bug description:
  Firefox SNAP updated from 102.0 to 102.0.1 today, resulting in the
  desktop icon disappearing, because the firefox_firefox.desktop file
  "icon=" line then points to a now non-existent directory.

  https://discourse.lubuntu.me/t/firefox-snap-updated-firefox-desktop-
  icon-disappeared-after-update/3445

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


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

[Desktop-packages] [Bug 1981025] Re: Firefox SNAP update removes icon from desktop

[Edward]

Attempted again, same thing:

:~$ apport-collect 1981025
The authorization page:
 
(https://launchpad.net/+authorize-token?oauth_token=HQrBgSXhd3p8m5mt8jP3_permission=DESKTOP_INTEGRATION)
should be opening in your browser. Use your browser to authorize
this program to access Launchpad on your behalf.
Waiting to hear from Launchpad about your decision...
/usr/bin/xdg-open: 882: firefox: not found
/usr/bin/xdg-open: 882: firefox: not found
xdg-open: no method available for opening 
'https://launchpad.net/+authorize-token?oauth_token=HQrBgSXhd3p8m5mt8jP3_permission=DESKTOP_INTEGRATION'

^CTraceback (most recent call last):
  File "/usr/bin/apport-cli", line 387, in 
if not app.run_argv():
  File "/usr/lib/python3/dist-packages/apport/ui.py", line 719, in run_argv
return self.run_update_report()
  File "/usr/lib/python3/dist-packages/apport/ui.py", line 566, in 
run_update_report
if not self.crashdb.can_update(self.options.update_report):
  File "/usr/lib/python3/dist-packages/apport/crashdb_impl/launchpad.py", line 
529, in can_update
bug = self.launchpad.bugs[id]
  File "/usr/lib/python3/dist-packages/apport/crashdb_impl/launchpad.py", line 
155, in launchpad
self.__launchpad = Launchpad.login_with('apport-collect',
  File "/usr/lib/python3/dist-packages/launchpadlib/launchpad.py", line 700, in 
login_with
return cls._authorize_token_and_login(
  File "/usr/lib/python3/dist-packages/launchpadlib/launchpad.py", line 451, in 
_authorize_token_and_login
credentials = authorization_engine(credentials, credential_store)
  File "/usr/lib/python3/dist-packages/launchpadlib/credentials.py", line 627, 
in __call__
self.make_end_user_authorize_token(credentials, request_token_string)
  File "/usr/lib/python3/dist-packages/launchpadlib/credentials.py", line 718, 
in make_end_user_authorize_token
self.wait_for_end_user_authorization(credentials)
  File "/usr/lib/python3/dist-packages/launchpadlib/credentials.py", line 811, 
in wait_for_end_user_authorization
time.sleep(access_token_poll_time)
KeyboardInterrupt

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

Title:
  Firefox SNAP update removes icon from desktop

Status in firefox package in Ubuntu:
  New

Bug description:
  Firefox SNAP updated from 102.0 to 102.0.1 today, resulting in the
  desktop icon disappearing, because the firefox_firefox.desktop file
  "icon=" line then points to a now non-existent directory.

  https://discourse.lubuntu.me/t/firefox-snap-updated-firefox-desktop-
  icon-disappeared-after-update/3445

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


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

[Desktop-packages] [Bug 1981025] [NEW] Firefox SNAP update removes icon from desktop

[Edward]

Public bug reported:

Firefox SNAP updated from 102.0 to 102.0.1 today, resulting in the
desktop icon disappearing, because the firefox_firefox.desktop file
"icon=" line then points to a now non-existent directory.

https://discourse.lubuntu.me/t/firefox-snap-updated-firefox-desktop-
icon-disappeared-after-update/3445

** Affects: firefox (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/1981025

Title:
  Firefox SNAP update removes icon from desktop

Status in firefox package in Ubuntu:
  New

Bug description:
  Firefox SNAP updated from 102.0 to 102.0.1 today, resulting in the
  desktop icon disappearing, because the firefox_firefox.desktop file
  "icon=" line then points to a now non-existent directory.

  https://discourse.lubuntu.me/t/firefox-snap-updated-firefox-desktop-
  icon-disappeared-after-update/3445

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


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

[Desktop-packages] [Bug 1951210] Re: libreoffice help doesn't open in firefox (404 error on file:///tmp/lu417531j7po.tmp/NewHelp0.html)

[Edward]

Installed the Firefox snap package, while leaving the Lubuntu
21.10-provided Firefox .deb package installed.

Launched LibreOffice Writer to see what the Help function did.

*It launched a Thunderbird compose window.*

Firefox snap package was then removed. The Thunderbird installation is
the snap package.

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

Title:
  libreoffice help doesn't open in firefox (404 error on
  file:///tmp/lu417531j7po.tmp/NewHelp0.html)

Status in libreoffice package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu jammy live QA-test on
  - dell [optiplex] 780 (c2q-q9400, 8gb, amd/ati cedar radeon hd 
5000/6000/7350/8350)

  Opened LibreOffice Writer as random apps in QA-test.
  Hit F1 to call help, and all I get is an error

  URL:  file:///tmp/lu417531j7po.tmp/NewHelp0.html

  ---
  File not found

  Firefox can’t find the file at /tmp/lu417531j7po.tmp/NewHelp0.html.

  Check the file name for capitalization or other typing errors.
  Check to see if the file was moved, renamed or deleted.
  ---

  Firefox opens as a snap; but it isn't accessing the data from
  LibreOffice.

  Reported first at https://forum.snapcraft.io/t/firefox-snap-breaks-
  libreoffice-deb/27537

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: libreoffice-writer 1:7.2.2-0ubuntu0.21.10.1
  ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14
  Uname: Linux 5.13.0-19-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu73
  Architecture: amd64
  CasperMD5CheckResult: pass
  CasperVersion: 1.465+canary3.3
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Nov 17 04:46:33 2021
  LiveMediaBuild: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (2026)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C.UTF-8
   SHELL=/bin/bash
  SourcePackage: libreoffice
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Desktop-packages] [Bug 1951210] Re: libreoffice help doesn't open in firefox (404 error on file:///tmp/lu417531j7po.tmp/NewHelp0.html)

[Edward]

Issue also occurs in 21.10 release, using Lubuntu.

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

Title:
  libreoffice help doesn't open in firefox (404 error on
  file:///tmp/lu417531j7po.tmp/NewHelp0.html)

Status in libreoffice package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu jammy live QA-test on
  - dell [optiplex] 780 (c2q-q9400, 8gb, amd/ati cedar radeon hd 
5000/6000/7350/8350)

  Opened LibreOffice Writer as random apps in QA-test.
  Hit F1 to call help, and all I get is an error

  URL:  file:///tmp/lu417531j7po.tmp/NewHelp0.html

  ---
  File not found

  Firefox can’t find the file at /tmp/lu417531j7po.tmp/NewHelp0.html.

  Check the file name for capitalization or other typing errors.
  Check to see if the file was moved, renamed or deleted.
  ---

  Firefox opens as a snap; but it isn't accessing the data from
  LibreOffice.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: libreoffice-writer 1:7.2.2-0ubuntu0.21.10.1
  ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14
  Uname: Linux 5.13.0-19-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu73
  Architecture: amd64
  CasperMD5CheckResult: pass
  CasperVersion: 1.465+canary3.3
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Nov 17 04:46:33 2021
  LiveMediaBuild: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (2026)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C.UTF-8
   SHELL=/bin/bash
  SourcePackage: libreoffice
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Desktop-packages] [Bug 1890365] Re: [snap] Web Serial fails to access local device

[edward sternin]

Confirm resolved, after a system update, under snapd 2.49.1, the default
acees is "rwk" and WebUSB device access works.

Thanks, Olivier!

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

Title:
  [snap] Web Serial fails to access local device

Status in chromium-browser package in Ubuntu:
  Fix Released

Bug description:
  A javascript-based web page works fine when accessed through Chrome,
  fails to recognize that any devices exist when accessed from Chromium
  on the same Unubtu 20.04 platform.

  The code includes the following snippet:

  const requestOptions = {
  filters: [{ usbVendorId: 0x1881 }]
};
port = await navigator.serial.requestPort(requestOptions);
await port.open({ baudrate: 9600 });
writer = port.writable.getWriter();
reader = port.readable.getReader();

  Under Chrome 84.0.4147.105 (Official Build) (64-bit), ttyACM0 device
  is listed in the pop-up, is selectable, and can communicate.  Under
  Chromium 84.0.4147.105 (Official Build) snap (64-bit), the pop-up
  contains only "No compatible devices found" message.

  Experimental Web Features flag is enabled in both browsers.

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

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

[Desktop-packages] [Bug 1890365] Re: [snap] Web Serial fails to access local device

[edward sternin]

Adding
  @{PROC}/tty/drivers r,
to /var/lib/snapd/apparmor/profiles/snap.chromium.chromium did the trick.

The file actually had rwk permissions set to TTY*, and ACM* (mine is one
of those), according to the comments in the file.

There was no output in journalctl.

This can be considered a fix, and a return to normal operation for
chromium. It should probably be changed for the distribution, not sure
who can do that.

Thanks.

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

Title:
  [snap] Web Serial fails to access local device

Status in chromium-browser package in Ubuntu:
  New

Bug description:
  A javascript-based web page works fine when accessed through Chrome,
  fails to recognize that any devices exist when accessed from Chromium
  on the same Unubtu 20.04 platform.

  The code includes the following snippet:

  const requestOptions = {
  filters: [{ usbVendorId: 0x1881 }]
};
port = await navigator.serial.requestPort(requestOptions);
await port.open({ baudrate: 9600 });
writer = port.writable.getWriter();
reader = port.readable.getReader();

  Under Chrome 84.0.4147.105 (Official Build) (64-bit), ttyACM0 device
  is listed in the pop-up, is selectable, and can communicate.  Under
  Chromium 84.0.4147.105 (Official Build) snap (64-bit), the pop-up
  contains only "No compatible devices found" message.

  Experimental Web Features flag is enabled in both browsers.

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

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

[Desktop-packages] [Bug 1890365] Re: [snap] Web Serial fails to access local device

[edward sternin]

'''
$ snap connections chromium | grep usb
raw-usb   chromium:raw-usb   :raw-usb manual
$ journalctl -f | grep chromium
Nov 05 18:41:42 XX audit[80101]: AVC apparmor="DENIED" operation="open" 
profile="snap.chromium.chromium" name="/proc/tty/drivers" pid=80101 
comm="ThreadPoolForeg" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0

... repeated several times 

Nov 05 18:42:05 XX polkitd(authority=local)[1133]: Operator of 
unix-session:c2 successfully authenticated as unix-user:X to gain TEMPORARY 
authorization for action io.snapcraft.snapd.manage-interfaces for 
unix-process:80462:133089573 [snap connect chromium:raw-usb] (owned by 
unix-user:X)
'''

The alert dialog reports "No compatible devices found"

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

Title:
  [snap] Web Serial fails to access local device

Status in chromium-browser package in Ubuntu:
  New

Bug description:
  A javascript-based web page works fine when accessed through Chrome,
  fails to recognize that any devices exist when accessed from Chromium
  on the same Unubtu 20.04 platform.

  The code includes the following snippet:

  const requestOptions = {
  filters: [{ usbVendorId: 0x1881 }]
};
port = await navigator.serial.requestPort(requestOptions);
await port.open({ baudrate: 9600 });
writer = port.writable.getWriter();
reader = port.readable.getReader();

  Under Chrome 84.0.4147.105 (Official Build) (64-bit), ttyACM0 device
  is listed in the pop-up, is selectable, and can communicate.  Under
  Chromium 84.0.4147.105 (Official Build) snap (64-bit), the pop-up
  contains only "No compatible devices found" message.

  Experimental Web Features flag is enabled in both browsers.

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

-- 
Mailing list: https://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 1890365] Re: [snap] Web Serial fails to access local device

[edward sternin]

I do not understand your comment, perhaps because I do not understand
snap.

/etc/udev/rules.d for this device configure it to be 666, and it works 
fine under other browsers, so you are not talking about actual device 
access, you are talking about the mapping of this real device onto some 
virtual "raw-usb" device of the snap's sandbox ?

I did what you suggested, tried from the command line before and after 
launching chromium.  I had previously also turned off apparmor for 
chromium altogether (comment #4). None of these affected the outcome.

So, please explain how I "ensure that said interface is connected" for 
the purposes of the snap sandbox.

I can use chromium successfully for accessing the device under RedHat, 
so this is specifically a Ubuntu/Chromium bug/misfeature.

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

Title:
  [snap] Web Serial fails to access local device

Status in chromium-browser package in Ubuntu:
  New

Bug description:
  A javascript-based web page works fine when accessed through Chrome,
  fails to recognize that any devices exist when accessed from Chromium
  on the same Unubtu 20.04 platform.

  The code includes the following snippet:

  const requestOptions = {
  filters: [{ usbVendorId: 0x1881 }]
};
port = await navigator.serial.requestPort(requestOptions);
await port.open({ baudrate: 9600 });
writer = port.writable.getWriter();
reader = port.readable.getReader();

  Under Chrome 84.0.4147.105 (Official Build) (64-bit), ttyACM0 device
  is listed in the pop-up, is selectable, and can communicate.  Under
  Chromium 84.0.4147.105 (Official Build) snap (64-bit), the pop-up
  contains only "No compatible devices found" message.

  Experimental Web Features flag is enabled in both browsers.

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

-- 
Mailing list: https://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 1890365] Re: [snap] Web Serial fails to access local device

[edward sternin]

Made no difference.  Tried before or after launching the browser.

By the way, this bug is not there in edge.  Only Chromium.

On 10/30/20 12:27 PM, Olivier Tilloy wrote:
> Does the following help?
>
>  sudo snap connect chromium:raw-usb
>
> ** Changed in: chromium-browser (Ubuntu)
> Status: Expired => New
>
-- 
-----
Edward Sternin, Physics Department, Brock U, St.Catharines, Ontario, L2S 3A1
   http://www.physics.brocku.ca/People/Faculty/Sternin/
voice: (905)688-5550x3414  FAX:(905)984-4857  email: edward.ster...@brocku.ca

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

Title:
  [snap] Web Serial fails to access local device

Status in chromium-browser package in Ubuntu:
  New

Bug description:
  A javascript-based web page works fine when accessed through Chrome,
  fails to recognize that any devices exist when accessed from Chromium
  on the same Unubtu 20.04 platform.

  The code includes the following snippet:

  const requestOptions = {
  filters: [{ usbVendorId: 0x1881 }]
};
port = await navigator.serial.requestPort(requestOptions);
await port.open({ baudrate: 9600 });
writer = port.writable.getWriter();
reader = port.readable.getReader();

  Under Chrome 84.0.4147.105 (Official Build) (64-bit), ttyACM0 device
  is listed in the pop-up, is selectable, and can communicate.  Under
  Chromium 84.0.4147.105 (Official Build) snap (64-bit), the pop-up
  contains only "No compatible devices found" message.

  Experimental Web Features flag is enabled in both browsers.

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

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

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

[Edward Meador]

Public bug reported:

Unpacking nvidia-340 (340.108-0ubuntu2) ...
dpkg: error processing archive /var/cache/apt/archives/nvidia
-340_340.108-0ubuntu2_amd64.deb (--unpack):
 trying to overwrite '/lib/udev/rules.d/71-nvidia.rules', whi
ch is also in package nvidia-kernel-common-440 440.100-0ubunt
u0.20.04.1
dpkg-deb: error: paste subprocess was killed by signal (Broke
n pipe)
Errors were encountered while processing:
 /var/cache/apt/archives/nvidia-340_340.108-0ubuntu2_amd64.de
b
E: Sub-process /usr/bin/dpkg returned an error code (1)


I'm in ubuntu 20.04.

ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: nvidia-340 (not installed)
ProcVersionSignature: Ubuntu 5.4.0-47.51-generic 5.4.55
Uname: Linux 5.4.0-47-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.6
Architecture: amd64
CasperMD5CheckResult: skip
Date: Thu Sep 17 14:14:06 2020
DuplicateSignature:
 package:nvidia-340:(not installed)
 Unpacking nvidia-340 (340.108-0ubuntu2) ...
 dpkg: error processing archive 
/var/cache/apt/archives/nvidia-340_340.108-0ubuntu2_amd64.deb (--unpack):
  trying to overwrite '/lib/udev/rules.d/71-nvidia.rules', which is also in 
package nvidia-kernel-common-440 440.100-0ubuntu0.20.04.1
ErrorMessage: trying to overwrite '/lib/udev/rules.d/71-nvidia.rules', which is 
also in package nvidia-kernel-common-440 440.100-0ubuntu0.20.04.1
InstallationDate: Installed on 2020-07-18 (61 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 
3.8.2-0ubuntu2
PythonDetails: N/A
RelatedPackageVersions:
 dpkg 1.19.7ubuntu3
 apt  2.0.2ubuntu0.1
SourcePackage: nvidia-graphics-drivers-340
Title: package nvidia-340 (not installed) failed to install/upgrade: trying to 
overwrite '/lib/udev/rules.d/71-nvidia.rules', which is also in package 
nvidia-kernel-common-440 440.100-0ubuntu0.20.04.1
UpgradeStatus: No upgrade log present (probably fresh install)

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


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

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

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

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

Bug description:
  Unpacking nvidia-340 (340.108-0ubuntu2) ...
  dpkg: error processing archive /var/cache/apt/archives/nvidia
  -340_340.108-0ubuntu2_amd64.deb (--unpack):
   trying to overwrite '/lib/udev/rules.d/71-nvidia.rules', whi
  ch is also in package nvidia-kernel-common-440 440.100-0ubunt
  u0.20.04.1
  dpkg-deb: error: paste subprocess was killed by signal (Broke
  n pipe)
  Errors were encountered while processing:
   /var/cache/apt/archives/nvidia-340_340.108-0ubuntu2_amd64.de
  b
  E: Sub-process /usr/bin/dpkg returned an error code (1)

  
  I'm in ubuntu 20.04.

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: nvidia-340 (not installed)
  ProcVersionSignature: Ubuntu 5.4.0-47.51-generic 5.4.55
  Uname: Linux 5.4.0-47-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.6
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Thu Sep 17 14:14:06 2020
  DuplicateSignature:
   package:nvidia-340:(not installed)
   Unpacking nvidia-340 (340.108-0ubuntu2) ...
   dpkg: error processing archive 
/var/cache/apt/archives/nvidia-340_340.108-0ubuntu2_amd64.deb (--unpack):
trying to overwrite '/lib/udev/rules.d/71-nvidia.rules', which is also in 
package nvidia-kernel-common-440 440.100-0ubuntu0.20.04.1
  ErrorMessage: trying to overwrite '/lib/udev/rules.d/71-nvidia.rules', which 
is also in package nvidia-kernel-common-440 440.100-0ubuntu0.20.04.1
  InstallationDate: Installed on 2020-07-18 (61 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 
3.8.2-0ubuntu2
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.19.7ubuntu3
   apt  2.0.2ubuntu0.1
  SourcePackage: nvidia-graphics-drivers-340
  Title: package nvidia-340 (not installed) failed to install/upgrade: trying 
to overwrite '/lib/udev/rules.d/71-nvidia.rules', which is also in package 
nvidia-kernel-common-440 440.100-0ubuntu0.20.04.1
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1845801] Re: [nvidia] Automatic login fails and then all subsequent logins fail. Killing gnome-session-binary fixes it, or just not using automatic login.

[Edward Savage]

Chris,

With the following packages installed and the workaround removed the
issue no longer occurs for me when enabling Automatic Login via
Settings.  I have tested rebooting and starting from off several times
and it worked as expected each time.  Previously the issue occurred on
every boot.

gdm3 (3.36.3-0ubuntu0.20.04.1)
libgdm1 (3.36.3-0ubuntu0.20.04.1)
gir1.2-gdm-1.0:amd64 (3.36.3-0ubuntu0.20.04.1)
nvidia-driver-450 (450.66-0ubuntu0.20.04.1)

/etc/default/grub
```
GRUB_CMDLINE_LINUX_DEFAULT="quiet splash"
```

Of note, when the desktop loaded I was greeted with the Ubuntu new user
"Connect Your Online Accounts" setup screen and what appeared to be a
fresh users settings.  If this happens to anyone here there's a helpful
README.txt in ~/ reminding you that you encrypted your home directory,
and to run ecryptfs-mount-private to gain access.  Oh yeah...

You can also expect to be prompted to unlock your login keyring at some
random moment a few minutes after the desktop loads.

Anyway, wonderful work, and thanks to everyone who helped fix this, at
least for me. :)

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

Title:
  [nvidia] Automatic login fails and then all subsequent logins fail.
  Killing gnome-session-binary fixes it, or just not using automatic
  login.

Status in OEM Priority Project:
  In Progress
Status in gdm3 package in Ubuntu:
  Fix Released
Status in gnome-session package in Ubuntu:
  Invalid
Status in grub2 package in Ubuntu:
  Invalid
Status in nvidia-graphics-drivers-390 package in Ubuntu:
  Invalid
Status in nvidia-graphics-drivers-430 package in Ubuntu:
  Invalid
Status in nvidia-graphics-drivers-435 package in Ubuntu:
  Invalid
Status in nvidia-graphics-drivers-440 package in Ubuntu:
  Invalid
Status in gdm3 source package in Focal:
  Fix Committed
Status in gnome-session source package in Focal:
  Invalid
Status in grub2 source package in Focal:
  Invalid
Status in nvidia-graphics-drivers-390 source package in Focal:
  Invalid
Status in nvidia-graphics-drivers-430 source package in Focal:
  Invalid
Status in nvidia-graphics-drivers-435 source package in Focal:
  Invalid
Status in nvidia-graphics-drivers-440 source package in Focal:
  Invalid

Bug description:
  [ Impact ]
  In some platforms with specific Nvidia cards (with nvidia-driver-440), enable 
auto-login (either during installation or after installation) will fail (either 
stuck in gdm login screen and not able to login even typing correct password).

  [ Test Case ]
  Here are two scenario of auto login with groovy (20.10) daily build[1]:

  1) Checked "Install third-party software" (e.g. nvidia-driver) with
  enabling "Login automatically" during installation.

  2) Install groovy daily build with default options, after installation 
completed:
  2.1) Install nvidia-driver-440 (450.66-0ubuntu1) from ubuntu-archive.
  2.2) Enable "Login automatically" from system settings.

  Then reboot.

  [Expected result]
  System will boot into desktop environment without the login page.

  [Actual result]
  System boots to login page, and can't login to desktop environment with the 
correct password.

  [ Regression potential ]
  Medium, the patch comes from upstream[2] to use /dev/tty1 (instead of tty0) 
to prevent the auto-login user gets tty1. I did verified gdm3 from my PPA[3] 
and it works good. It passed the 30 times reboot stress test by using 
stress/reboot_30 from checkbox.

  [1] sha256sum: 
bf4359114660504ad3f6fbde5e0c3edbc67a4101e4480f576d3cbd4f59acf822
  [2] https://gitlab.gnome.org/GNOME/gdm/-/commit/f843233ad4 
https://gitlab.gnome.org/GNOME/gdm/-/commit/690b3c01
  [3] https://launchpad.net/~os369510/+archive/ubuntu/gdm3-1845801

  ---

  I just updated to the Ubuntu 19.10 beta. After boot, I'm shown the GDM
  login screen (which I shouldn't; I have auto login enabled), and
  logging in just takes me back to the same user selection screen even
  though the password is correct.

  If I switch to a TTY and run `sudo pkill gnome-session-binary`,
  logging in through GDM starts working again.

  I should add that the do-release-upgrade was rocky; I did it in a
  terminal from within gnome, went away for a while, and when I
  returned, I just saw an Ubuntu 19.10 in a TTY. I was able to do `sudo
  dpkg --configure -a` and complete the upgrade, but I don't know if
  something's still messed up due to that.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: xorg 1:7.7+19ubuntu12
  ProcVersionSignature: Ubuntu 5.3.0-13.14-generic 5.3.0
  Uname: Linux 5.3.0-13-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.suspend: suspend hibernate resume
  .proc.driver.nvidia.suspend_depth: default modeset uvm
  

[Desktop-packages] [Bug 1890365] Re: [snap] Web Serial fails to access local device

[edward sternin]

Disabling apparmor for chromium

$ sudo ln -s /etc/apparmor.d/usr.bin.chromium-browser  /etc/apparmor.d/disable/
$ sudo apparmor_parser -R /etc/apparmor.d/disable/usr.bin.chromium-browser

had no effect.

Adding "/dev/tty* rw"  right below the line for "/dev/null rw" in
/etc/apparmor.d/disable/usr.bin.chromium-browser and removing/re-adding
the profile had no effect.

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

Title:
  [snap] Web Serial fails to access local device

Status in chromium-browser package in Ubuntu:
  Incomplete

Bug description:
  A javascript-based web page works fine when accessed through Chrome,
  fails to recognize that any devices exist when accessed from Chromium
  on the same Unubtu 20.04 platform.

  The code includes the following snippet:

  const requestOptions = {
  filters: [{ usbVendorId: 0x1881 }]
};
port = await navigator.serial.requestPort(requestOptions);
await port.open({ baudrate: 9600 });
writer = port.writable.getWriter();
reader = port.readable.getReader();

  Under Chrome 84.0.4147.105 (Official Build) (64-bit), ttyACM0 device
  is listed in the pop-up, is selectable, and can communicate.  Under
  Chromium 84.0.4147.105 (Official Build) snap (64-bit), the pop-up
  contains only "No compatible devices found" message.

  Experimental Web Features flag is enabled in both browsers.

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

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

[Desktop-packages] [Bug 1890365] Re: [snap] Web Serial fails to access local device

[edward sternin]

Also: it is chroME that is installed as a snap package, chroMIUM is
installed through apt-get, and it works just fine:

$ journalctl -f | grep chrome
Aug 05 15:26:57 slon dbus-daemon[782]: [system] Activating via systemd: service 
name='org.bluez' unit='dbus-org.bluez.service' requested by ':1.80' (uid=1000 
pid=3623 comm="/home/opt/google/chrome/chrome " label="unconfined")

and no additional messages as the "connect" button is clicked and the
serial device accessed.

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

Title:
  [snap] Web Serial fails to access local device

Status in chromium-browser package in Ubuntu:
  Incomplete

Bug description:
  A javascript-based web page works fine when accessed through Chrome,
  fails to recognize that any devices exist when accessed from Chromium
  on the same Unubtu 20.04 platform.

  The code includes the following snippet:

  const requestOptions = {
  filters: [{ usbVendorId: 0x1881 }]
};
port = await navigator.serial.requestPort(requestOptions);
await port.open({ baudrate: 9600 });
writer = port.writable.getWriter();
reader = port.readable.getReader();

  Under Chrome 84.0.4147.105 (Official Build) (64-bit), ttyACM0 device
  is listed in the pop-up, is selectable, and can communicate.  Under
  Chromium 84.0.4147.105 (Official Build) snap (64-bit), the pop-up
  contains only "No compatible devices found" message.

  Experimental Web Features flag is enabled in both browsers.

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

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

[Desktop-packages] [Bug 1890365] Re: [snap] Web Serial fails to access local device

[edward sternin]

The output is shown.  Please note that no additional lines show up when
I load the page that has that javascript code, or on clicking the button
that causes the connect attempt.  All of that output is already there.

$ journalctl -f | grep chromium
Aug 05 15:21:33 slon dbus-daemon[1410]: apparmor="DENIED" 
operation="dbus_method_call"  bus="session" 
path="/org/freedesktop/PowerManagement/Inhibit" 
interface="org.freedesktop.PowerManagement.Inhibit" member="Inhibit" 
mask="send" name="org.freedesktop.PowerManagement" pid=2802 
label="snap.chromium.chromium" peer_pid=2397 peer_label="unconfined"
Aug 05 15:21:34 slon dbus-daemon[1410]: apparmor="DENIED" 
operation="dbus_method_call"  bus="session" 
path="/org/freedesktop/PowerManagement/Inhibit" 
interface="org.freedesktop.PowerManagement.Inhibit" member="Inhibit" 
mask="send" name="org.freedesktop.PowerManagement" pid=2802 
label="snap.chromium.chromium" peer_pid=2397 peer_label="unconfined"
Aug 05 15:21:38 slon dbus-daemon[1410]: apparmor="DENIED" 
operation="dbus_method_call"  bus="session" 
path="/org/freedesktop/PowerManagement/Inhibit" 
interface="org.freedesktop.PowerManagement.Inhibit" member="Inhibit" 
mask="send" name="org.freedesktop.PowerManagement" pid=2802 
label="snap.chromium.chromium" peer_pid=2397 peer_label="unconfined"
Aug 05 15:21:43 slon dbus-daemon[1410]: apparmor="DENIED" 
operation="dbus_method_call"  bus="session" 
path="/org/freedesktop/PowerManagement/Inhibit" 
interface="org.freedesktop.PowerManagement.Inhibit" member="Inhibit" 
mask="send" name="org.freedesktop.PowerManagement" pid=2802 
label="snap.chromium.chromium" peer_pid=2397 peer_label="unconfined"
Aug 05 15:21:44 slon dbus-daemon[1410]: apparmor="DENIED" 
operation="dbus_method_call"  bus="session" 
path="/org/freedesktop/PowerManagement/Inhibit" 
interface="org.freedesktop.PowerManagement.Inhibit" member="Inhibit" 
mask="send" name="org.freedesktop.PowerManagement" pid=2802 
label="snap.chromium.chromium" peer_pid=2397 peer_label="unconfined"
Aug 05 15:21:44 slon dbus-daemon[1410]: apparmor="DENIED" 
operation="dbus_method_call"  bus="session" 
path="/org/freedesktop/PowerManagement/Inhibit" 
interface="org.freedesktop.PowerManagement.Inhibit" member="Inhibit" 
mask="send" name="org.freedesktop.PowerManagement" pid=2802 
label="snap.chromium.chromium" peer_pid=2397 peer_label="unconfined"
Aug 05 15:21:44 slon dbus-daemon[1410]: apparmor="DENIED" 
operation="dbus_method_call"  bus="session" 
path="/org/freedesktop/PowerManagement/Inhibit" 
interface="org.freedesktop.PowerManagement.Inhibit" member="Inhibit" 
mask="send" name="org.freedesktop.PowerManagement" pid=2802 
label="snap.chromium.chromium" peer_pid=2397 peer_label="unconfined"
Aug 05 15:21:46 slon dbus-daemon[1410]: apparmor="DENIED" 
operation="dbus_method_call"  bus="session" 
path="/org/freedesktop/PowerManagement/Inhibit" 
interface="org.freedesktop.PowerManagement.Inhibit" member="Inhibit" 
mask="send" name="org.freedesktop.PowerManagement" pid=2802 
label="snap.chromium.chromium" peer_pid=2397 peer_label="unconfined"
Aug 05 15:21:46 slon dbus-daemon[1410]: apparmor="DENIED" 
operation="dbus_method_call"  bus="session" 
path="/org/freedesktop/PowerManagement/Inhibit" 
interface="org.freedesktop.PowerManagement.Inhibit" member="Inhibit" 
mask="send" name="org.freedesktop.PowerManagement" pid=2802 
label="snap.chromium.chromium" peer_pid=2397 peer_label="unconfined"
Aug 05 15:21:46 slon dbus-daemon[1410]: apparmor="DENIED" 
operation="dbus_method_call"  bus="session" 
path="/org/freedesktop/PowerManagement/Inhibit" 
interface="org.freedesktop.PowerManagement.Inhibit" member="Inhibit" 
mask="send" name="org.freedesktop.PowerManagement" pid=2802 
label="snap.chromium.chromium" peer_pid=2397 peer_label="unconfined"
Aug 05 15:22:22 slon audit[2802]: AVC apparmor="DENIED" operation="open" 
profile="snap.chromium.chromium" name="/run/udev/data/c166:0" pid=2802 
comm="ThreadPoolForeg" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0
Aug 05 15:22:22 slon kernel: audit: type=1400 audit(1596655342.601:44): 
apparmor="DENIED" operation="open" profile="snap.chromium.chromium" 
name="/run/udev/data/c166:0" pid=2802 comm="ThreadPoolForeg" requested_mask="r" 
denied_mask="r" fsuid=1000 ouid=0
Aug 05 15:22:45 slon audit[782]: USER_AVC pid=782 uid=103 auid=4294967295 
ses=4294967295 msg='apparmor="DENIED" operation="dbus_method_call"  
bus="system" path="/" interface="org.freedesktop.DBus.ObjectManager" 
member="GetManagedObjects" mask="send" name="org.bluez" pid=3305 
label="snap.chromium.chromium"
Aug 05 15:22:45 slon kernel: audit: type=1107 audit(1596655365.450:45): pid=782 
uid=103 auid=4294967295 ses=4294967295 msg='apparmor="DENIED" 
operation="dbus_method_call"  bus="system" path="/" 
interface="org.freedesktop.DBus.ObjectManager" member="GetManagedObjects" 
mask="send" name="org.bluez" pid=3305 label="snap.chromium.chromium"

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

[Desktop-packages] [Bug 1890365] [NEW] Web Serial fails to access local device

[edward sternin]

Public bug reported:

A javascript-based web page works fine when accessed through Chrome,
fails to recognize that any devices exist when accessed from Chromium on
the same Unubtu 20.04 platform.

The code includes the following snippet:

const requestOptions = {
filters: [{ usbVendorId: 0x1881 }]
  };
  port = await navigator.serial.requestPort(requestOptions);
  await port.open({ baudrate: 9600 });
  writer = port.writable.getWriter();
  reader = port.readable.getReader();

Under Chrome 84.0.4147.105 (Official Build) (64-bit), ttyACM0 device is
listed in the pop-up, is selectable, and can communicate.  Under
Chromium 84.0.4147.105 (Official Build) snap (64-bit), the pop-up
contains only "No compatible devices found" message.

Experimental Web Features flag is enabled in both browsers.

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

Title:
  Web Serial fails to access local device

Status in chromium-browser package in Ubuntu:
  New

Bug description:
  A javascript-based web page works fine when accessed through Chrome,
  fails to recognize that any devices exist when accessed from Chromium
  on the same Unubtu 20.04 platform.

  The code includes the following snippet:

  const requestOptions = {
  filters: [{ usbVendorId: 0x1881 }]
};
port = await navigator.serial.requestPort(requestOptions);
await port.open({ baudrate: 9600 });
writer = port.writable.getWriter();
reader = port.readable.getReader();

  Under Chrome 84.0.4147.105 (Official Build) (64-bit), ttyACM0 device
  is listed in the pop-up, is selectable, and can communicate.  Under
  Chromium 84.0.4147.105 (Official Build) snap (64-bit), the pop-up
  contains only "No compatible devices found" message.

  Experimental Web Features flag is enabled in both browsers.

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

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

[Desktop-packages] [Bug 1859308] Re: software-properties-gtk erroneously reports that certain Intel wireless adapter cards are not working

[Edward Gibbs]

I have the same issue with 8260 on 20.04.  Without backports installed
the wi-fi worked but there was often a very long delay when connecting
to or loading a site.  Ran speed test (google speed test) and there was
a 15 - 20-second delay connecting to the server, but then good speed
(around 40 MBPS) was reported.  This was repeatable.  Installed
backports and selected it as the driver and the delay disappeared.  Now
connects instantly and reports the same good speed.

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

Title:
  software-properties-gtk erroneously reports that certain Intel
  wireless adapter cards are not working

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

Bug description:
  On Ubuntu 20.04 (development branch), as of today, Additional Drivers
  (software-properties-gtk 0.98.6) reports that the device "Intel
  Corporation: Wireless-AC 9260" is not working, and suggests using a
  manually installed driver (cf. screenshot).

  However the device is working correctly:

    * lsmod | grep iwlwifi, lspci -v, lshw, dmesg | grep iwlwifi all show
  that its driver iwlwifi is in use
    * ls /lib/firmware/*9260* show that the appropriate firmware files
  are present

  And I am indeed writing this bug report connected to an ac (5 GHz)
  wifi network, where I can verify a ~130-160 Mbps download speed, so
  software-properties-gtk shouldn't report the device as not working and
  suggest manually installing a driver. Not sure why it says so?

  EDIT: bug confirmed as affecting the following Intel wireless adapter
  cards, and assumedly more to come:

Intel Wi-Fi 6 AX200
Intel Dual Band Wireless-AC 3165
Intel Dual Band Wireless-AC 7260
Intel Dual Band Wireless-AC 8260
Intel Wireless-AC 9260

  Also for reference here are the specs of Intel adapter cards:

ark.intel.com/content/www/us/en/ark.html#@WirelessNetworking

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: software-properties-gtk 0.98.6
  ProcVersionSignature: Ubuntu 5.4.0-9.12-generic 5.4.3
  Uname: Linux 5.4.0-9-generic x86_64
  ApportVersion: 2.20.11-0ubuntu15
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Jan 12 00:53:43 2020
  ExecutablePath: /usr/bin/software-properties-gtk
  InstallationDate: Installed on 2019-12-29 (13 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20191226)
  InterpreterPath: /usr/bin/python3.7
  PackageArchitecture: all
  Python3Details: /usr/bin/python3.7, Python 3.7.6, python3-minimal, 
3.7.5-1ubuntu1
  PythonDetails: /usr/bin/python2.7, Python 2.7.17, python-minimal, 2.7.17-1
  SourcePackage: software-properties
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1873510] Re: Blank screen when hotplugging monitors connected through DisplayPort dock

[Edward Schwartz]

** Attachment added: "Logs while the screens are blank"
   
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1873510/+attachment/5356278/+files/nvidia-bug-report-blank.log.gz

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

Title:
  Blank screen when hotplugging monitors connected through DisplayPort
  dock

Status in xorg package in Ubuntu:
  New

Bug description:
  Hi,

  I run Ubuntu 18.04 on a Dell Precision 7540.  Most of the time I use
  this through a Dell WD19DC dock.  The dock is connected to a Trendnet
  TK-240DP KVM Switch.

  If I have the laptop clamshell closed, like I normally do, and switch
  my KVM to the other computer, and then switch back, my monitors stay
  enter power saving mode.  Most of the time, I am able to recover the
  screens by pressing Control-Alt-F3, waiting a few seconds, and then
  pressing Control-Alt-F2.  The problem does not happen if the clamshell
  is left open.  Part of the problem is that this is a cheaper KVM, and
  from the laptop's perspective the screens are disconnected when the
  computer is switched.

  Changing a few small things makes the problem not occur:

  * Opening the clamshell when switching the KVM.  Interestingly, if the 
clamshell is open during either the switch away OR the switch back, the screen 
recovers.
  * Manually removing the displays one at a time does not reliably trigger the 
problem.  Though I have witnessed the problem occur once or twice when removing 
a single display.

  I am attaching three nvidia bug report logs:

  1. nvidia-bug-report-before.log.gz is after a clean boot when I have not used 
the KVM.  
  2. nvidia-bug-report-blank.log.gz is after switching the KVM to the other 
computer and back.  During this time, both screens are black.  The log was 
taken over ssh.
  3. nvidia-bug-report-workaround.log.gz is after I have recovered the screen 
after using Ctrl-Alt-F3 followed by Ctrl-Alt-F2.

  This problem happens when prime-select is set to intel or nvidia.
  These logs are when it was set to intel.

  Any advice would be greatly appreciated.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  Uname: Linux 5.5.0-050500rc6-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.9-0ubuntu7.14
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: Unity:Unity7:ubuntu
  Date: Fri Apr 17 13:57:43 2020
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus:
   nvidia, 440.82, 4.15.0-1079-oem, x86_64: installed
   nvidia, 440.82, 5.0.0-1047-oem-osp1, x86_64: installed
   nvidia, 440.82, 5.5.0-050500rc6-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Intel Corporation Device [8086:3e9b] (rev 02) (prog-if 00 [VGA controller])
 Subsystem: Dell Device [1028:0926]
   NVIDIA Corporation Device [10de:1f36] (rev a1) (prog-if 00 [VGA controller])
 Subsystem: Dell Device [1028:0926]
  InstallationDate: Installed on 2020-01-03 (104 days ago)
  InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 
(20190805)
  MachineType: Dell Inc. Precision 7540
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.5.0-050500rc6-generic 
root=UUID=7f01cb01-e7df-4259-9d7a-ae37a19f363b ro quiet splash dis_ucode_ldr 
vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/12/2020
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.8.2
  dmi.board.name: 0499T7
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.8.2:bd03/12/2020:svnDellInc.:pnPrecision7540:pvr:rvnDellInc.:rn0499T7:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Precision
  dmi.product.name: Precision 7540
  dmi.product.sku: 0926
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
  version.libdrm2: libdrm2 2.4.99-1ubuntu1~18.04.2
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.8-0ubuntu0~18.04.3
  version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.8-0ubuntu0~18.04.3
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A

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

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

[Desktop-packages] [Bug 1873510] Re: Blank screen when hotplugging monitors connected through DisplayPort dock

[Edward Schwartz]

** Attachment added: "Logs after recovering the screen by switching virtual 
consoles"
   
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1873510/+attachment/5356279/+files/nvidia-bug-report-workaround.log.gz

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

Title:
  Blank screen when hotplugging monitors connected through DisplayPort
  dock

Status in xorg package in Ubuntu:
  New

Bug description:
  Hi,

  I run Ubuntu 18.04 on a Dell Precision 7540.  Most of the time I use
  this through a Dell WD19DC dock.  The dock is connected to a Trendnet
  TK-240DP KVM Switch.

  If I have the laptop clamshell closed, like I normally do, and switch
  my KVM to the other computer, and then switch back, my monitors stay
  enter power saving mode.  Most of the time, I am able to recover the
  screens by pressing Control-Alt-F3, waiting a few seconds, and then
  pressing Control-Alt-F2.  The problem does not happen if the clamshell
  is left open.  Part of the problem is that this is a cheaper KVM, and
  from the laptop's perspective the screens are disconnected when the
  computer is switched.

  Changing a few small things makes the problem not occur:

  * Opening the clamshell when switching the KVM.  Interestingly, if the 
clamshell is open during either the switch away OR the switch back, the screen 
recovers.
  * Manually removing the displays one at a time does not reliably trigger the 
problem.  Though I have witnessed the problem occur once or twice when removing 
a single display.

  I am attaching three nvidia bug report logs:

  1. nvidia-bug-report-before.log.gz is after a clean boot when I have not used 
the KVM.  
  2. nvidia-bug-report-blank.log.gz is after switching the KVM to the other 
computer and back.  During this time, both screens are black.  The log was 
taken over ssh.
  3. nvidia-bug-report-workaround.log.gz is after I have recovered the screen 
after using Ctrl-Alt-F3 followed by Ctrl-Alt-F2.

  This problem happens when prime-select is set to intel or nvidia.
  These logs are when it was set to intel.

  Any advice would be greatly appreciated.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  Uname: Linux 5.5.0-050500rc6-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.9-0ubuntu7.14
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: Unity:Unity7:ubuntu
  Date: Fri Apr 17 13:57:43 2020
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus:
   nvidia, 440.82, 4.15.0-1079-oem, x86_64: installed
   nvidia, 440.82, 5.0.0-1047-oem-osp1, x86_64: installed
   nvidia, 440.82, 5.5.0-050500rc6-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Intel Corporation Device [8086:3e9b] (rev 02) (prog-if 00 [VGA controller])
 Subsystem: Dell Device [1028:0926]
   NVIDIA Corporation Device [10de:1f36] (rev a1) (prog-if 00 [VGA controller])
 Subsystem: Dell Device [1028:0926]
  InstallationDate: Installed on 2020-01-03 (104 days ago)
  InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 
(20190805)
  MachineType: Dell Inc. Precision 7540
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.5.0-050500rc6-generic 
root=UUID=7f01cb01-e7df-4259-9d7a-ae37a19f363b ro quiet splash dis_ucode_ldr 
vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/12/2020
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.8.2
  dmi.board.name: 0499T7
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.8.2:bd03/12/2020:svnDellInc.:pnPrecision7540:pvr:rvnDellInc.:rn0499T7:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Precision
  dmi.product.name: Precision 7540
  dmi.product.sku: 0926
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
  version.libdrm2: libdrm2 2.4.99-1ubuntu1~18.04.2
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.8-0ubuntu0~18.04.3
  version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.8-0ubuntu0~18.04.3
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A

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

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

[Desktop-packages] [Bug 1873510] [NEW] Blank screen when hotplugging monitors connected through DisplayPort dock

[Edward Schwartz]

Public bug reported:

Hi,

I run Ubuntu 18.04 on a Dell Precision 7540.  Most of the time I use
this through a Dell WD19DC dock.  The dock is connected to a Trendnet
TK-240DP KVM Switch.

If I have the laptop clamshell closed, like I normally do, and switch my
KVM to the other computer, and then switch back, my monitors stay enter
power saving mode.  Most of the time, I am able to recover the screens
by pressing Control-Alt-F3, waiting a few seconds, and then pressing
Control-Alt-F2.  The problem does not happen if the clamshell is left
open.  Part of the problem is that this is a cheaper KVM, and from the
laptop's perspective the screens are disconnected when the computer is
switched.

Changing a few small things makes the problem not occur:

* Opening the clamshell when switching the KVM.  Interestingly, if the 
clamshell is open during either the switch away OR the switch back, the screen 
recovers.
* Manually removing the displays one at a time does not reliably trigger the 
problem.  Though I have witnessed the problem occur once or twice when removing 
a single display.

I am attaching three nvidia bug report logs:

1. nvidia-bug-report-before.log.gz is after a clean boot when I have not used 
the KVM.  
2. nvidia-bug-report-blank.log.gz is after switching the KVM to the other 
computer and back.  During this time, both screens are black.  The log was 
taken over ssh.
3. nvidia-bug-report-workaround.log.gz is after I have recovered the screen 
after using Ctrl-Alt-F3 followed by Ctrl-Alt-F2.

This problem happens when prime-select is set to intel or nvidia.  These
logs are when it was set to intel.

Any advice would be greatly appreciated.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xorg 1:7.7+19ubuntu7.1
Uname: Linux 5.5.0-050500rc6-generic x86_64
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.9-0ubuntu7.14
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
CurrentDesktop: Unity:Unity7:ubuntu
Date: Fri Apr 17 13:57:43 2020
DistUpgraded: Fresh install
DistroCodename: bionic
DistroVariant: ubuntu
DkmsStatus:
 nvidia, 440.82, 4.15.0-1079-oem, x86_64: installed
 nvidia, 440.82, 5.0.0-1047-oem-osp1, x86_64: installed
 nvidia, 440.82, 5.5.0-050500rc6-generic, x86_64: installed
ExtraDebuggingInterest: Yes, including running git bisection searches
GraphicsCard:
 Intel Corporation Device [8086:3e9b] (rev 02) (prog-if 00 [VGA controller])
   Subsystem: Dell Device [1028:0926]
 NVIDIA Corporation Device [10de:1f36] (rev a1) (prog-if 00 [VGA controller])
   Subsystem: Dell Device [1028:0926]
InstallationDate: Installed on 2020-01-03 (104 days ago)
InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805)
MachineType: Dell Inc. Precision 7540
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.5.0-050500rc6-generic 
root=UUID=7f01cb01-e7df-4259-9d7a-ae37a19f363b ro quiet splash dis_ucode_ldr 
vt.handoff=1
SourcePackage: xorg
Symptom: display
Title: Xorg freeze
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 03/12/2020
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.8.2
dmi.board.name: 0499T7
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 10
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvr1.8.2:bd03/12/2020:svnDellInc.:pnPrecision7540:pvr:rvnDellInc.:rn0499T7:rvrA00:cvnDellInc.:ct10:cvr:
dmi.product.family: Precision
dmi.product.name: Precision 7540
dmi.product.sku: 0926
dmi.sys.vendor: Dell Inc.
version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
version.libdrm2: libdrm2 2.4.99-1ubuntu1~18.04.2
version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.8-0ubuntu0~18.04.3
version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.8-0ubuntu0~18.04.3
version.xserver-xorg-core: xserver-xorg-core N/A
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A

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


** Tags: amd64 apport-bug bionic false-gpu-hang freeze third-party-packages 
ubuntu

** Attachment added: "Logs before the problem"
   
https://bugs.launchpad.net/bugs/1873510/+attachment/5356261/+files/nvidia-bug-report-before.log.gz

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

Title:
  Blank screen when hotplugging monitors connected through DisplayPort
  dock

Status in xorg package in Ubuntu:
  New

Bug description:
  Hi,

  I run Ubuntu 18.04 on a Dell Precision 7540.  Most of the time I use
  this through a Dell WD19DC dock.  The dock is connected to a Trendnet
  TK-240DP KVM Switch.

  If I have the laptop clamshell closed, like I normally do, and switch
  

[Desktop-packages] [Bug 1869769] Re: gnome-terminal regularly becomes corrupted

[Edward Schwartz]

I wrote about this more here: https://edmcman.github.io/blog/2020-04-01
--the-rabbit-hole-of-multi-line-ur-ls/

But yes, this is not a gnome-terminal bug.

** Changed in: gnome-terminal (Ubuntu)
   Status: New => Invalid

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

Title:
  gnome-terminal regularly becomes corrupted

Status in gnome-terminal package in Ubuntu:
  Invalid

Bug description:
  I regularly run weechat inside gnome-terminal, and it routinely
  becomes corrupted.  It's hard to say whether this is a gnome-terminal
  bug, but I've seen it on different machines.

  The problem is perhaps best shown through a screenshot (attached).
  You can see the statusbar in the second to last row incorrectly
  contains the words "I would" that were displayed elsewhere in the
  terminal but weechat at some point.

  Normal usage of weechat results in tabs that have corruption in other
  rows, but I wasn't readily able to find an example with non-sensitive
  information.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-terminal 3.28.2-1ubuntu1~18.04.1
  Uname: Linux 5.5.0-050500rc6-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.12
  Architecture: amd64
  CurrentDesktop: Unity:Unity7:ubuntu
  Date: Mon Mar 30 13:25:03 2020
  InstallationDate: Installed on 2020-01-03 (86 days ago)
  InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 
(20190805)
  SourcePackage: gnome-terminal
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1869769] Re: gnome-terminal regularly becomes corrupted

[Edward Schwartz]

I managed to track this down to a particular option in weechat,
eat_newline_glitch.  The problem occurs when there are lines that are
_exactly_ as long as the terminal width.  Here is the script:

https://gist.github.com/edmcman/8fa071e68af14c288bf1801ffc142f61

At this point, I believe it unlikely to be a gnome-terminal bug.  But
I'll dig in a little more.

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

Title:
  gnome-terminal regularly becomes corrupted

Status in gnome-terminal package in Ubuntu:
  New

Bug description:
  I regularly run weechat inside gnome-terminal, and it routinely
  becomes corrupted.  It's hard to say whether this is a gnome-terminal
  bug, but I've seen it on different machines.

  The problem is perhaps best shown through a screenshot (attached).
  You can see the statusbar in the second to last row incorrectly
  contains the words "I would" that were displayed elsewhere in the
  terminal but weechat at some point.

  Normal usage of weechat results in tabs that have corruption in other
  rows, but I wasn't readily able to find an example with non-sensitive
  information.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-terminal 3.28.2-1ubuntu1~18.04.1
  Uname: Linux 5.5.0-050500rc6-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.12
  Architecture: amd64
  CurrentDesktop: Unity:Unity7:ubuntu
  Date: Mon Mar 30 13:25:03 2020
  InstallationDate: Installed on 2020-01-03 (86 days ago)
  InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 
(20190805)
  SourcePackage: gnome-terminal
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1869769] [NEW] gnome-terminal regularly becomes corrupted

[Edward Schwartz]

Public bug reported:

I regularly run weechat inside gnome-terminal, and it routinely becomes
corrupted.  It's hard to say whether this is a gnome-terminal bug, but
I've seen it on different machines.

The problem is perhaps best shown through a screenshot (attached).  You
can see the statusbar in the second to last row incorrectly contains the
words "I would" that were displayed elsewhere in the terminal but
weechat at some point.

Normal usage of weechat results in tabs that have corruption in other
rows, but I wasn't readily able to find an example with non-sensitive
information.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: gnome-terminal 3.28.2-1ubuntu1~18.04.1
Uname: Linux 5.5.0-050500rc6-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.12
Architecture: amd64
CurrentDesktop: Unity:Unity7:ubuntu
Date: Mon Mar 30 13:25:03 2020
InstallationDate: Installed on 2020-01-03 (86 days ago)
InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805)
SourcePackage: gnome-terminal
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug bionic third-party-packages

** Attachment added: "Example of corruption"
   
https://bugs.launchpad.net/bugs/1869769/+attachment/5343464/+files/weechat-bug.png

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

Title:
  gnome-terminal regularly becomes corrupted

Status in gnome-terminal package in Ubuntu:
  New

Bug description:
  I regularly run weechat inside gnome-terminal, and it routinely
  becomes corrupted.  It's hard to say whether this is a gnome-terminal
  bug, but I've seen it on different machines.

  The problem is perhaps best shown through a screenshot (attached).
  You can see the statusbar in the second to last row incorrectly
  contains the words "I would" that were displayed elsewhere in the
  terminal but weechat at some point.

  Normal usage of weechat results in tabs that have corruption in other
  rows, but I wasn't readily able to find an example with non-sensitive
  information.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-terminal 3.28.2-1ubuntu1~18.04.1
  Uname: Linux 5.5.0-050500rc6-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.12
  Architecture: amd64
  CurrentDesktop: Unity:Unity7:ubuntu
  Date: Mon Mar 30 13:25:03 2020
  InstallationDate: Installed on 2020-01-03 (86 days ago)
  InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 
(20190805)
  SourcePackage: gnome-terminal
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1695876] Re: German Documentation file displays incorrect CUPS version

[Edward Hope-Morley]

** Tags removed: sts-sru-needed

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

Title:
  German Documentation file displays incorrect CUPS version

Status in CUPS:
  Fix Released
Status in cups package in Ubuntu:
  Fix Released
Status in cups source package in Xenial:
  In Progress

Bug description:
  The /doc/de/index.html.in file in the package source has an incorrect
  version number written into a header instead of using '@CUPS_VERSION@'
  to populate this file as in the other languages' version of the same
  file, seemingly resulting in /usr/share/cups/doc-root/de/index.html
  having the wrong version once CUPS is installed:

  ...
  

  CUPS 2.0.2
  ...

  instead of:

  ...
  

  CUPS @CUPS_VERSION@
  ...

  resulting in 'CUPS 2.0.2' instead of 2.1.3 being shown.

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

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

[Desktop-packages] [Bug 1831413] Re: alsa has to be reloaded afterlogin or else I don't get any sound

[Edward]

OK yeah that's all it needed.

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

Title:
  alsa has to be reloaded afterlogin or else I don't get any sound

Status in alsa-driver package in Ubuntu:
  Incomplete

Bug description:
  If I open Firefox or Chrome or any other app to play anything with
  sound, I get no sound, unless I run ~$ sudo alsa force-reload first.

  Before upgrading from Bionic to Disco I didn't have to do this.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.0.0-15.16-lowlatency 5.0.6
  Uname: Linux 5.0.0-15-lowlatency x86_64
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  timidity   2006 F timidity
   /dev/snd/pcmC0D0p:   timidity   2006 F...m timidity
   /dev/snd/seq:timidity   2006 F timidity
   /dev/snd/timer:  timidity   2006 f timidity
  Date: Sun Jun  2 20:12:03 2019
  InstallationDate: Installed on 2016-12-19 (895 days ago)
  InstallationMedia: Ubuntu-Studio 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  PackageArchitecture: all
  ProcEnviron:
   LANGUAGE=en_US
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
   No PulseAudio daemon running, or not running as session daemon.
  SourcePackage: alsa-driver
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/16/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: B219P027
  dmi.board.asset.tag: N/A
  dmi.board.name: ZBOX-CI320NANO series
  dmi.board.vendor: ZOTAC
  dmi.board.version: Rev.00
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrB219P027:bd07/16/2015:svnMotherboardbyZOTAC:pnZBOX-CI320NANOseries:pvrRev.00:rvnZOTAC:rnZBOX-CI320NANOseries:rvrRev.00:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: N/A
  dmi.product.name: ZBOX-CI320NANO series
  dmi.product.sku: N/A
  dmi.product.version: Rev.00
  dmi.sys.vendor: Motherboard by ZOTAC

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

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

[Desktop-packages] [Bug 1831413] Re: alsa has to be reloaded afterlogin or else I don't get any sound

[Edward]

Wait trying again, forgot something

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

Title:
  alsa has to be reloaded afterlogin or else I don't get any sound

Status in alsa-driver package in Ubuntu:
  Incomplete

Bug description:
  If I open Firefox or Chrome or any other app to play anything with
  sound, I get no sound, unless I run ~$ sudo alsa force-reload first.

  Before upgrading from Bionic to Disco I didn't have to do this.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.0.0-15.16-lowlatency 5.0.6
  Uname: Linux 5.0.0-15-lowlatency x86_64
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  timidity   2006 F timidity
   /dev/snd/pcmC0D0p:   timidity   2006 F...m timidity
   /dev/snd/seq:timidity   2006 F timidity
   /dev/snd/timer:  timidity   2006 f timidity
  Date: Sun Jun  2 20:12:03 2019
  InstallationDate: Installed on 2016-12-19 (895 days ago)
  InstallationMedia: Ubuntu-Studio 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  PackageArchitecture: all
  ProcEnviron:
   LANGUAGE=en_US
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
   No PulseAudio daemon running, or not running as session daemon.
  SourcePackage: alsa-driver
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/16/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: B219P027
  dmi.board.asset.tag: N/A
  dmi.board.name: ZBOX-CI320NANO series
  dmi.board.vendor: ZOTAC
  dmi.board.version: Rev.00
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrB219P027:bd07/16/2015:svnMotherboardbyZOTAC:pnZBOX-CI320NANOseries:pvrRev.00:rvnZOTAC:rnZBOX-CI320NANOseries:rvrRev.00:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: N/A
  dmi.product.name: ZBOX-CI320NANO series
  dmi.product.sku: N/A
  dmi.product.version: Rev.00
  dmi.sys.vendor: Motherboard by ZOTAC

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

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

[Desktop-packages] [Bug 1831413] Re: alsa has to be reloaded afterlogin or else I don't get any sound

[Edward]

I tried that just now, uninstalled timidity, did an apt update and dist-
upgrade and even reboot after that.  Still the same.

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

Title:
  alsa has to be reloaded afterlogin or else I don't get any sound

Status in alsa-driver package in Ubuntu:
  Incomplete

Bug description:
  If I open Firefox or Chrome or any other app to play anything with
  sound, I get no sound, unless I run ~$ sudo alsa force-reload first.

  Before upgrading from Bionic to Disco I didn't have to do this.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.0.0-15.16-lowlatency 5.0.6
  Uname: Linux 5.0.0-15-lowlatency x86_64
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  timidity   2006 F timidity
   /dev/snd/pcmC0D0p:   timidity   2006 F...m timidity
   /dev/snd/seq:timidity   2006 F timidity
   /dev/snd/timer:  timidity   2006 f timidity
  Date: Sun Jun  2 20:12:03 2019
  InstallationDate: Installed on 2016-12-19 (895 days ago)
  InstallationMedia: Ubuntu-Studio 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  PackageArchitecture: all
  ProcEnviron:
   LANGUAGE=en_US
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
   No PulseAudio daemon running, or not running as session daemon.
  SourcePackage: alsa-driver
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/16/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: B219P027
  dmi.board.asset.tag: N/A
  dmi.board.name: ZBOX-CI320NANO series
  dmi.board.vendor: ZOTAC
  dmi.board.version: Rev.00
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrB219P027:bd07/16/2015:svnMotherboardbyZOTAC:pnZBOX-CI320NANOseries:pvrRev.00:rvnZOTAC:rnZBOX-CI320NANOseries:rvrRev.00:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: N/A
  dmi.product.name: ZBOX-CI320NANO series
  dmi.product.sku: N/A
  dmi.product.version: Rev.00
  dmi.sys.vendor: Motherboard by ZOTAC

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

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

[Desktop-packages] [Bug 1831413] Re: alsa has to be reloaded afterlogin or else I don't get any sound

[Edward]

I tried that just now, uninstalled timidity, did an apt update and dist-
upgrade and even reboot after that.  Still the same.

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

Title:
  alsa has to be reloaded afterlogin or else I don't get any sound

Status in alsa-driver package in Ubuntu:
  Incomplete

Bug description:
  If I open Firefox or Chrome or any other app to play anything with
  sound, I get no sound, unless I run ~$ sudo alsa force-reload first.

  Before upgrading from Bionic to Disco I didn't have to do this.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.0.0-15.16-lowlatency 5.0.6
  Uname: Linux 5.0.0-15-lowlatency x86_64
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  timidity   2006 F timidity
   /dev/snd/pcmC0D0p:   timidity   2006 F...m timidity
   /dev/snd/seq:timidity   2006 F timidity
   /dev/snd/timer:  timidity   2006 f timidity
  Date: Sun Jun  2 20:12:03 2019
  InstallationDate: Installed on 2016-12-19 (895 days ago)
  InstallationMedia: Ubuntu-Studio 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  PackageArchitecture: all
  ProcEnviron:
   LANGUAGE=en_US
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
   No PulseAudio daemon running, or not running as session daemon.
  SourcePackage: alsa-driver
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/16/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: B219P027
  dmi.board.asset.tag: N/A
  dmi.board.name: ZBOX-CI320NANO series
  dmi.board.vendor: ZOTAC
  dmi.board.version: Rev.00
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrB219P027:bd07/16/2015:svnMotherboardbyZOTAC:pnZBOX-CI320NANOseries:pvrRev.00:rvnZOTAC:rnZBOX-CI320NANOseries:rvrRev.00:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: N/A
  dmi.product.name: ZBOX-CI320NANO series
  dmi.product.sku: N/A
  dmi.product.version: Rev.00
  dmi.sys.vendor: Motherboard by ZOTAC

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

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

[Desktop-packages] [Bug 1831413] [NEW] alsa has to be reloaded afterlogin or else I don't get any sound

[Edward]

Public bug reported:

If I open Firefox or Chrome or any other app to play anything with
sound, I get no sound, unless I run ~$ sudo alsa force-reload first.

Before upgrading from Bionic to Disco I didn't have to do this.

ProblemType: Bug
DistroRelease: Ubuntu 19.04
Package: alsa-base 1.0.25+dfsg-0ubuntu5
ProcVersionSignature: Ubuntu 5.0.0-15.16-lowlatency 5.0.6
Uname: Linux 5.0.0-15-lowlatency x86_64
ApportVersion: 2.20.10-0ubuntu27
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  timidity   2006 F timidity
 /dev/snd/pcmC0D0p:   timidity   2006 F...m timidity
 /dev/snd/seq:timidity   2006 F timidity
 /dev/snd/timer:  timidity   2006 f timidity
Date: Sun Jun  2 20:12:03 2019
InstallationDate: Installed on 2016-12-19 (895 days ago)
InstallationMedia: Ubuntu-Studio 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
PackageArchitecture: all
ProcEnviron:
 LANGUAGE=en_US
 TERM=xterm-256color
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
PulseList:
 Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
 No PulseAudio daemon running, or not running as session daemon.
SourcePackage: alsa-driver
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 07/16/2015
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: B219P027
dmi.board.asset.tag: N/A
dmi.board.name: ZBOX-CI320NANO series
dmi.board.vendor: ZOTAC
dmi.board.version: Rev.00
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: To Be Filled By O.E.M.
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrB219P027:bd07/16/2015:svnMotherboardbyZOTAC:pnZBOX-CI320NANOseries:pvrRev.00:rvnZOTAC:rnZBOX-CI320NANOseries:rvrRev.00:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
dmi.product.family: N/A
dmi.product.name: ZBOX-CI320NANO series
dmi.product.sku: N/A
dmi.product.version: Rev.00
dmi.sys.vendor: Motherboard by ZOTAC

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


** Tags: amd64 apport-bug disco

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

Title:
  alsa has to be reloaded afterlogin or else I don't get any sound

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  If I open Firefox or Chrome or any other app to play anything with
  sound, I get no sound, unless I run ~$ sudo alsa force-reload first.

  Before upgrading from Bionic to Disco I didn't have to do this.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.0.0-15.16-lowlatency 5.0.6
  Uname: Linux 5.0.0-15-lowlatency x86_64
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  timidity   2006 F timidity
   /dev/snd/pcmC0D0p:   timidity   2006 F...m timidity
   /dev/snd/seq:timidity   2006 F timidity
   /dev/snd/timer:  timidity   2006 f timidity
  Date: Sun Jun  2 20:12:03 2019
  InstallationDate: Installed on 2016-12-19 (895 days ago)
  InstallationMedia: Ubuntu-Studio 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  PackageArchitecture: all
  ProcEnviron:
   LANGUAGE=en_US
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
   No PulseAudio daemon running, or not running as session daemon.
  SourcePackage: alsa-driver
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/16/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: B219P027
  dmi.board.asset.tag: N/A
  dmi.board.name: ZBOX-CI320NANO series
  dmi.board.vendor: ZOTAC
  dmi.board.version: Rev.00
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrB219P027:bd07/16/2015:svnMotherboardbyZOTAC:pnZBOX-CI320NANOseries:pvrRev.00:rvnZOTAC:rnZBOX-CI320NANOseries:rvrRev.00:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: N/A
  dmi.product.name: ZBOX-CI320NANO series
  dmi.product.sku: N/A
  dmi.product.version: Rev.00
  dmi.sys.vendor: Motherboard by ZOTAC

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

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

[Desktop-packages] [Bug 1827219] [NEW] package upower 0.99.4-2ubuntu0.3 failed to install/upgrade: subprocess installed post-installation script returned error exit status 134

[Edward Matthew Bailey]

Public bug reported:

Upgrading from 14.04 to 16.04 got the error at install time and then
after restart

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: upower 0.99.4-2ubuntu0.3
ProcVersionSignature: Ubuntu 4.4.0-147.173-generic 4.4.177
Uname: Linux 4.4.0-147-generic i686
ApportVersion: 2.20.1-0ubuntu2.18
Architecture: i386
Date: Wed May  1 13:22:28 2019
ErrorMessage: subprocess installed post-installation script returned error exit 
status 134
InstallationDate: Installed on 2019-04-29 (2 days ago)
InstallationMedia: Ubuntu 14.04.6 LTS "Trusty Tahr" - Release i386 (20190304.5)
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.5
 apt  1.2.31
SourcePackage: upower
Title: package upower 0.99.4-2ubuntu0.3 failed to install/upgrade: subprocess 
installed post-installation script returned error exit status 134
UpgradeStatus: Upgraded to xenial on 2019-05-01 (0 days ago)

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


** Tags: apport-package i386 xenial

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

Title:
  package upower 0.99.4-2ubuntu0.3 failed to install/upgrade: subprocess
  installed post-installation script returned error exit status 134

Status in upower package in Ubuntu:
  New

Bug description:
  Upgrading from 14.04 to 16.04 got the error at install time and then
  after restart

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: upower 0.99.4-2ubuntu0.3
  ProcVersionSignature: Ubuntu 4.4.0-147.173-generic 4.4.177
  Uname: Linux 4.4.0-147-generic i686
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: i386
  Date: Wed May  1 13:22:28 2019
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 134
  InstallationDate: Installed on 2019-04-29 (2 days ago)
  InstallationMedia: Ubuntu 14.04.6 LTS "Trusty Tahr" - Release i386 
(20190304.5)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.5
   apt  1.2.31
  SourcePackage: upower
  Title: package upower 0.99.4-2ubuntu0.3 failed to install/upgrade: subprocess 
installed post-installation script returned error exit status 134
  UpgradeStatus: Upgraded to xenial on 2019-05-01 (0 days ago)

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

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

[Desktop-packages] [Bug 1771185] Re: Secondary monitor not connecting in 18.04 LTS

[edward]

Hi guys,

i think, i have the very same problem... but i use AMD video. I'd like
to find out if it is the same issue or a different bug. However i cannot
use my second monitor...

Any suggests?

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

Title:
  Secondary monitor not connecting in 18.04 LTS

Status in libxrandr package in Ubuntu:
  Confirmed

Bug description:
  I have an Acer Aspire V Nitro VN7-592G-709V with Nvidia Geforce 960M
  (nvidia driver v390) and a Benq W1070 projector.

  I have upgraded from Ubuntu 16.04 to 18.04 and my projector connects
  for a split second and then gets disconnected. In Ubuntu 16.04
  projector was working fine as a mirror display and extended desktop.
  Here's what I already tried:

  - enable the nouveau driver instead of the nvidia driver -> no result
  - enable the on-board intel board with sudo prime-select intel -> no result
  - apt purge nvidia* & reinstall nvidia driver 390 (stable) or 396 (beta) -> 
no result
  - disable nouveau driver, disable nvidia driver from the repository and 
install nvidia driver from nvidia website (both 390 and 396) -> no result
  - installed CCSM (CompizConfig Settings Manager) and disabled display 
auto-detection -> no result
  - played around with the refresh rate (some forums say that the two outputs 
have to be in sync -> no result
  - deleted the whole Ubuntu 18.04 upgrade and installed a fresh 18.04 -> still 
the same issue
  - tried to manually enable the output with xrandr --output HDMI-1-2 --mode 
1920x1920 -> nothing
  - under settings -> devices -> displays I don't see a secondary display (just 
the main one)

  I have the latest libxrandr2, 2:1.5.1-1 under Ubuntu 18.04 (updated to
  day)

  Here is the output of xrandr the very second when I connect the
  projector (then HDMI-1-2 goes disconnected and no modes are
  displayed):

  ~$ xrandr
  Screen 0: minimum 8 x 8, current 1920 x 1080, maximum 16384 x 16384
  eDP-1-1 connected primary 1920x1080+0+0 (normal left inverted right x 
axis y axis) 345mm x 194mm
     1920x1080 60.02*+  60.0159.9759.9659.93
     1680x1050 59.9559.88
     1600x1024 60.17
     1400x1050 59.98
     1600x900  59.9959.9459.9559.82
     1280x1024 60.02
     1440x900  59.89
     1400x900  59.9659.88
     1280x960  60.00
     1440x810  60.0059.97
     1368x768  59.8859.85
     1360x768  59.8059.96
     1280x800  59.9959.9759.8159.91
     1152x864  60.00
     1280x720  60.0059.9959.8659.74
     1024x768  60.0460.00
     960x720   60.00
     928x696   60.05
     896x672   60.01
     1024x576  59.9559.9659.9059.82
     960x600   59.9360.00
     960x540   59.9659.9959.6359.82
     800x600   60.0060.3256.25
     840x525   60.0159.88
     864x486   59.9259.57
     800x512   60.17
     700x525   59.98
     800x450   59.9559.82
     640x512   60.02
     720x450   59.89
     700x450   59.9659.88
     640x480   60.0059.94
     720x405   59.5158.99
     684x384   59.8859.85
     680x384   59.8059.96
     640x400   59.8859.98
     576x432   60.06
     640x360   59.8659.8359.8459.32
     512x384   60.00
     512x288   60.0059.92
     480x270   59.6359.82
     400x300   60.3256.34
     432x243   59.9259.57
     320x240   60.05
     360x202   59.5159.13
     320x180   59.8459.32
  DP-1-1 disconnected (normal left inverted right x axis y axis)
  HDMI-1-1 disconnected (normal left inverted right x axis y axis)
  DP-1-2 disconnected (normal left inverted right x axis y axis)
  HDMI-1-2 disconnected (normal left inverted right x axis y axis)
    1920x1080 (0x258) 148.500MHz +HSync +VSync
  h: width  1920 start 2008 end 2052 total 2200 skew0 clock  
67.50KHz
  v: height 1080 start 1084 end 1089 total 1125   clock  
60.00Hz
    1920x1080 (0x259) 148.500MHz +HSync +VSync
  h: width  1920 start 2448 end 2492 total 2640 skew0 clock  
56.25KHz
  v: height 1080 start 1084 end 1089 total 1125   clock  
50.00Hz
    1920x1080 (0x25a) 148.352MHz +HSync +VSync
  h: width  1920 start 2008 end 2052 total 2200 skew0 clock  
67.43KHz
  v: height 1080 start 1084 end 1089 total 1125   clock  
59.94Hz
    1920x1080i (0x25b) 74.250MHz +HSync +VSync Interlace
  h: width  1920 start 2008 end 2052 total 2200 skew0 clock  

[Desktop-packages] [Bug 785977] Re: Character set submenus do not appear

[Edward Cherlin]

The Text Encoding submenu is in the View menu, but it does not open in
Firefox 61.0.1 in Ubuntu 18.04.

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

Title:
  Character set submenus do not appear

Status in firefox package in Ubuntu:
  Incomplete

Bug description:
  Binary package hint: firefox

  Ubuntu Natty Narwhal 11.04
  Unity 2D
  Firefox 4.0.1+build1+nobinonly-0ubuntu0.11.04.2

  When I click on View-->Character Sets, most of the submenus fail to
  appear, including Autodetect,  each of the regional submenus under
  More, and Unicode. The result is that I cannot select any character
  set to view the page in. This makes it harder to diagnose pages with
  improper coding.

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

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

[Desktop-packages] [Bug 1763978] Re: nvidia-prime-boot.service: Main process exited, code=exited, status=2/INVALIDARGUMENT

[Edward]

Hi,
I also seem to have this problem:
Ubuntu 18.04
nvidia-prime 0.8.8

output of `journalctl -u nvidia-prime-boot.service`

```
-- Logs begin at Tue 2018-05-15 21:22:38 BST, end at Sun 2018-05-20 15:49:46 
BST. --
May 16 20:50:32 erebus systemd[1]: Starting dGPU off during boot...
May 16 20:50:32 erebus sh[1273]: /bin/sh: 1: cannot create 
/sys/kernel/debug/vgaswitcheroo/switch: Directory nonexistent
May 16 20:50:32 erebus systemd[1]: nvidia-prime-boot.service: Main process 
exited, code=exited, status=2/INVALIDARGUMENT
May 16 20:50:32 erebus systemd[1]: nvidia-prime-boot.service: Failed with 
result 'exit-code'.
May 16 20:50:32 erebus systemd[1]: Failed to start dGPU off during boot.

```

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

Title:
  nvidia-prime-boot.service: Main process exited, code=exited,
  status=2/INVALIDARGUMENT

Status in nvidia-prime package in Ubuntu:
  Confirmed

Bug description:
  Since this week (i believe April 9th) Nvidia-prime isn't working for
  me.

  Running:
  Distributor ID:   Ubuntu
  Description:  Ubuntu Bionic Beaver (development branch)
  Release:  18.04
  Codename: bionic

  Nvidia-prime version:

  Nvidia-prime version:
Installed: 0.8.7
Candidate: 0.8.7
Version table:
   *** 0.8.7 500

  Error code:
  apr 14 11:56:33 Precision-7510 systemd[1]: nvidia-prime-boot.service: Main 
process exited, code=exited, status=2/INVALIDARGUMENT

  apr 14 11:56:33 Precision-7510 systemd[1]: nvidia-prime-boot.service:
  Failed with result 'exit-code'.

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

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

[Desktop-packages] [Bug 1759621] Re: gnome-shell crashed with SIGSEGV in g_type_check_instance_cast() from st_label_set_text() from ffi_call_unix64()

[Edward Pedemonte]

For me, it happens every few times I attach an SD card. Haven't tested
with other media.

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

Title:
  gnome-shell crashed with SIGSEGV in g_type_check_instance_cast() from
  st_label_set_text() from ffi_call_unix64()

Status in gnome-shell package in Ubuntu:
  Confirmed

Bug description:
  https://errors.ubuntu.com/problem/811164cadd3e9e891f9e2d439bda59925f91a62c

  ---

  trying to get vpn up and running

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.28.0-0ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  Uname: Linux 4.15.0-13-generic x86_64
  ApportVersion: 2.20.9-0ubuntu1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Mar 28 18:00:19 2018
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  GsettingsChanges:
   b'org.gnome.shell' b'enabled-extensions' 
b"['vpn-indica...@howdoicomputer.fastmail.com']"
   b'org.gnome.shell' b'app-picker-view' b'uint32 1'
   b'org.gnome.shell' b'favorite-apps' b"['firefox.desktop', 
'rhythmbox.desktop', 'org.gnome.Nautilus.desktop', 
'org.gnome.Software.desktop', 'yelp.desktop', 'org.gnome.Terminal.desktop', 
'cisco-anyconnect.desktop']"
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
  InstallationDate: Installed on 2018-03-23 (4 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
  ProcCmdline: /usr/bin/gnome-shell
  SegvAnalysis:
   Segfault happened at: 0x7fd17cf23d3d :
movzbl 0x16(%rax),%edx
   PC (0x7fd17cf23d3d) ok
   source "0x16(%rax)" (0x00024562) not located in a known VMA region (needed 
readable region)!
   destination "%edx" ok
  SegvReason: reading unknown VMA
  Signal: 11
  SourcePackage: gnome-shell
  StacktraceTop:
   g_type_check_instance_cast () at 
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   st_label_set_text () at /usr/lib/gnome-shell/libst-1.0.so
   ffi_call_unix64 () at /usr/lib/x86_64-linux-gnu/libffi.so.6
   ffi_call () at /usr/lib/x86_64-linux-gnu/libffi.so.6
   () at /usr/lib/libgjs.so.0
  Title: gnome-shell crashed with SIGSEGV in g_type_check_instance_cast()
  UpgradeStatus: Upgraded to bionic on 2018-03-24 (4 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

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

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

[Desktop-packages] [Bug 1744587] Re: hplip under Ubuntu 17.10 for HP OfficeJet Pro 8720

[Edward Flanigan]

I was having all kinds of problems installing hplip from source.
I upgrade my distribution using sudo do-release-upgrade -d

Now I get this:
apt-cache policy hplip
hplip:
  Installed: 3.17.10+repack0-2
  Candidate: 3.17.10+repack0-2
  Version table:
 *** 3.17.10+repack0-2 500
500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages
100 /var/lib/dpkg/status


And I can print again.

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

Title:
  hplip under Ubuntu 17.10 for HP OfficeJet Pro 8720

Status in HPLIP:
  In Progress
Status in hplip package in Ubuntu:
  New

Bug description:
  https://askubuntu.com/questions/990970/how-to-install-hplip-3-17-11
  -under-ubuntu-17-10-for-hp-officejet-pro-8720

  I'm using Ubuntu 17.10

  According to the release notes https://developers.hp.com/hp-linux-
  imaging-and-printing/release_notes I need hplip 3.17.11.


  When I install hplip from using apt-get I get the following error when
  I execute hp-check:

  The error is the following (distro not supported) File
  "/usr/share/hplip/installer/core_install.py", line 475, in init
  self.distro_name = self.distros_index[self.distro]




  I've tried installing from the shell installer with the following:

  error: Configure failed with error: libnetsnmp not found

  When I do the following:

  sudo apt-get install libsnmp-dev

  I get

  libsnmp-dev is already the newest version (5.7.3+dfsg-1.7ubuntu1)

  And apt is an older version

  apt-cache policy hplip
  hplip:
    Installed: 3.17.7+repack0-3
    Candidate: 3.17.7+repack0-3
    Version table:
   *** 3.17.7+repack0-3 500
    500 http://us.archive.ubuntu.com/ubuntu artful/main amd64 Packages
    100 /var/lib/dpkg/status

  Anyone have any ideas on how I can install and/or debug this?

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

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

[Desktop-packages] [Bug 1744587] Re: hplip under Ubuntu 17.10 for HP OfficeJet Pro 8720

[Edward Flanigan]

Feel free to close this.

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

Title:
  hplip under Ubuntu 17.10 for HP OfficeJet Pro 8720

Status in HPLIP:
  In Progress
Status in hplip package in Ubuntu:
  New

Bug description:
  https://askubuntu.com/questions/990970/how-to-install-hplip-3-17-11
  -under-ubuntu-17-10-for-hp-officejet-pro-8720

  I'm using Ubuntu 17.10

  According to the release notes https://developers.hp.com/hp-linux-
  imaging-and-printing/release_notes I need hplip 3.17.11.


  When I install hplip from using apt-get I get the following error when
  I execute hp-check:

  The error is the following (distro not supported) File
  "/usr/share/hplip/installer/core_install.py", line 475, in init
  self.distro_name = self.distros_index[self.distro]




  I've tried installing from the shell installer with the following:

  error: Configure failed with error: libnetsnmp not found

  When I do the following:

  sudo apt-get install libsnmp-dev

  I get

  libsnmp-dev is already the newest version (5.7.3+dfsg-1.7ubuntu1)

  And apt is an older version

  apt-cache policy hplip
  hplip:
    Installed: 3.17.7+repack0-3
    Candidate: 3.17.7+repack0-3
    Version table:
   *** 3.17.7+repack0-3 500
    500 http://us.archive.ubuntu.com/ubuntu artful/main amd64 Packages
    100 /var/lib/dpkg/status

  Anyone have any ideas on how I can install and/or debug this?

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

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

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

[Edward]

Public bug reported:

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

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

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

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

/Edward

** Affects: speech-dispatcher (Ubuntu)
 Importance: Undecided
 Status: New

** Description changed:

- So, a brand new computer running Ubuntu 16.04 LTS.
+ So, a brand new computer running Ubuntu 16.04.3 LTS.
  In hardinfo summary, my audio adapters are
  • HDA-Intel - HDA Intel HDMI
  • HDA-Intel - HDA Intel PCH
  • HDA-Intel - HDA NVidia
  In full detail: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor HD 
Audio Controller (rev 06)
  Memory 16kb (non-prefetchable), snd_hda_intel
  
  As soon as I load a website in Firefox that utilizes speech-dispatcher
  (fimfiction.net) all sounds get distorted, whether I click a paragraph
  for TTS reading or not. The problem seems to go away if I don't use the
  site after a while. When I close down Firefox the problem still lingers
  a bit, but maybe not as long. One thing I did which seemed faster was
  close down everything, then load what I wanted to listen to (Skype,
  Discord), and if it still persisted I would go into "Sound Settings" and
  after a few blinks in that window the sound is normal again.
  
  While the site is open, according to "Sound Settings" (from the speaker
  icon menu) and Pulse Audio Volume Controller (pavu) there are 4 copies
  of this package. Muting them did not help the problem, but moving one of
  them, and a very specific one, from the "Built-in Audio Analog Stereo"
  to something else like HDA NVidia (HDMI 3) seems to be a workaround.
  
  Just so you know, I do not use the HDMI cable for sound, but instead use
  the "headphones" jack. If you need any more details, I'll try to provide
  them.
  
  /Edward

** Description changed:

  So, a brand new computer running Ubuntu 16.04.3 LTS.
  In hardinfo summary, my audio adapters are
  • HDA-Intel - HDA Intel HDMI
  • HDA-Intel - HDA Intel PCH
  • HDA-Intel - HDA NVidia
- In full detail: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor HD 
Audio Controller (rev 06)
+ In detail: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor HD Audio 
Controller (rev 06)
  Memory 16kb (non-prefetchable), snd_hda_intel
  
  As soon as I load a website in Firefox that utilizes speech-dispatcher
  (fimfiction.net) all sounds get distorted, whether I click a paragraph
  for TTS reading or not. The problem seems to go away if I don't use the
  site after a while. When I close down Firefox the problem still lingers
  a bit, but maybe not as long. One thing I did which seemed faster was
  close down everything, then load what I wanted to listen to (Skype,
  Discord), and if it still persisted I would go into "Sound Settings" and
  after a few blinks in that window the sound is normal again.
  
  While the site is open, according to "Sound Settings" (from the speaker
  icon menu) and Pulse Audio Volume Controller (pavu) there are 4 copies
  of this package. Muting them did not help the problem, but moving one of
  them, and a very specific one, from the "Built-in Audio Analog Stereo"
  to something else like HDA NVidia (HDMI 3) seems to be a workaround.
  
  Just so you know, I do not use the HDMI cable for sound, but instead use
  the "headphones" jack. If you need any more details, I'll try to provide
  them.
  
  /Edward

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

Title:
  speech-dispatcher distorts all sound

Stat

[Desktop-packages] [Bug 1705369] Re: Ubuntu 17.10 boots to black screen when using Nvidia drivers (on a desktop with an Intel GPU)

[Edward Boyle]

I have read this entire thread and am wondering if we have some type of
active clear solution. I was under the impression that  Ubuntu had
matured and this kind of nightmare was almost unheaded of anymore.

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

Title:
  Ubuntu 17.10 boots to black screen when using Nvidia drivers (on a
  desktop with an Intel GPU)

Status in gdm3 package in Ubuntu:
  Confirmed
Status in gnome-shell package in Ubuntu:
  Invalid
Status in nvidia-graphics-drivers-375 package in Ubuntu:
  Won't Fix
Status in nvidia-graphics-drivers-384 package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu 17.10 boots to black screen when using Nvidia drivers (on a
  desktop with an Intel GPU)

  WORKAROUNDS:

  * Disable integrated graphics/GPU in your BIOS.

  * Add 'nomodeset' to your kernel command line.

  
  ORIGINAL DESCRIPTION:

  This bug is very similar to
  https://bugs.launchpad.net/ubuntu-gnome/+bug/1559576
  which is closed. I have been asked to open a new bug report.

  The issue is on Ubuntu 17.10 with gdm3 fully updated as of July 20,
  2017. I upgraded to 17.10 from a freshly installed Ubuntu 17.04.

  - Lightdm works
  - Nouveau driver works
  - Nvidia driver 375.66 (proprietary) does not work
  - Nvidia driver 384.47 (open source) does not work (from 
https://launchpad.net/~graphics-drivers/+archive/ubuntu/ppa)
  - Nvidia drivers work with Ubuntu Gnome 17.04

  I am using Nvidia GTX 1080 and Intel i7-4790K

  lsb_release -rd:
  Description:  Ubuntu Artful Aardvark (development branch)
  Release:  17.10

  apt-cache policy gnome-shell:
  gnome-shell:
    Installed: 3.24.2-0ubuntu7
    Candidate: 3.24.2-0ubuntu7
    Version table:
   *** 3.24.2-0ubuntu7 500
  500 http://sa.archive.ubuntu.com/ubuntu artful/main amd64 Packages
  100 /var/lib/dpkg/status

  uname -s -r -v -p -i -o:
  Linux 4.11.0-11-generic #16-Ubuntu SMP Wed Jul 12 20:40:19 UTC 2017 x86_64 
x86_64 GNU/Linux

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

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

[Desktop-packages] [Bug 1705369] Re: Ubuntu 17.10 boots to black screen when using Nvidia drivers (on a desktop with an Intel GPU)

[Edward Boyle]

#60 confirmed as the solution to this?

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

Title:
  Ubuntu 17.10 boots to black screen when using Nvidia drivers (on a
  desktop with an Intel GPU)

Status in gdm3 package in Ubuntu:
  Confirmed
Status in gnome-shell package in Ubuntu:
  Invalid
Status in nvidia-graphics-drivers-375 package in Ubuntu:
  Won't Fix
Status in nvidia-graphics-drivers-384 package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu 17.10 boots to black screen when using Nvidia drivers (on a
  desktop with an Intel GPU)

  WORKAROUNDS:

  * Disable integrated graphics/GPU in your BIOS.

  * Add 'nomodeset' to your kernel command line.

  
  ORIGINAL DESCRIPTION:

  This bug is very similar to
  https://bugs.launchpad.net/ubuntu-gnome/+bug/1559576
  which is closed. I have been asked to open a new bug report.

  The issue is on Ubuntu 17.10 with gdm3 fully updated as of July 20,
  2017. I upgraded to 17.10 from a freshly installed Ubuntu 17.04.

  - Lightdm works
  - Nouveau driver works
  - Nvidia driver 375.66 (proprietary) does not work
  - Nvidia driver 384.47 (open source) does not work (from 
https://launchpad.net/~graphics-drivers/+archive/ubuntu/ppa)
  - Nvidia drivers work with Ubuntu Gnome 17.04

  I am using Nvidia GTX 1080 and Intel i7-4790K

  lsb_release -rd:
  Description:  Ubuntu Artful Aardvark (development branch)
  Release:  17.10

  apt-cache policy gnome-shell:
  gnome-shell:
    Installed: 3.24.2-0ubuntu7
    Candidate: 3.24.2-0ubuntu7
    Version table:
   *** 3.24.2-0ubuntu7 500
  500 http://sa.archive.ubuntu.com/ubuntu artful/main amd64 Packages
  100 /var/lib/dpkg/status

  uname -s -r -v -p -i -o:
  Linux 4.11.0-11-generic #16-Ubuntu SMP Wed Jul 12 20:40:19 UTC 2017 x86_64 
x86_64 GNU/Linux

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

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

[Desktop-packages] [Bug 1408963] Re: [Xbuntu 14.04, 14.10 and 15.04] Network manager stops working: iwl3945 0000:03:00.0: BSM uCode verification failed at addr ...; wlan0: deauthenticating from... by

[Edward Z. Yang]

If you are wondering how to disable power saving, please look at
https://askubuntu.com/a/860754/35182

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

Title:
  [Xbuntu 14.04, 14.10 and 15.04] Network manager stops working: iwl3945
  :03:00.0: BSM uCode verification failed at addr ...; wlan0:
  deauthenticating from... by local choice (Reason: 3=DEAUTH_LEAVING),

Status in network-manager package in Ubuntu:
  Incomplete

Bug description:
  From time to time, the system loses all wireles networks and kubuntu
  network manager applet goes blank - not even one network is shown. All
  wifi connections are broken. Rebooting fixes the issue, switching to
  WICD on-the-fly enables to continue browsing without rebooting, so it
  seems to be no hardware issue or iwl3945 issue.

  What to expect: stable connections and flawless network managing.
  What happens: so above.

  Further informations about the system, the network configuration, the
  package version can be found in the attachment, also parts of rsyslog
  and dmesg.

  Interesting, according to some helpers, are the following lines:
  dmesg:   wlan0: deauthenticating from 02:26:4d:ac:8f:45 by local choice 
(Reason: 3=DEAUTH_LEAVING)

  lsb_release -a
  No LSB modules are available.
  Distributor ID: Ubuntu
  Description:Ubuntu 14.10
  Release:14.10
  Codename:   utopic

  apt-cache policy network-manager
  network-manager:
    Installiert:   0.9.8.8-0ubuntu28
    Installationskandidat: 0.9.8.8-0ubuntu28
    Versionstabelle:
   *** 0.9.8.8-0ubuntu28 0
  500 http://de.archive.ubuntu.com/ubuntu/ utopic/main amd64 Packages
  100 /var/lib/dpkg/status

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

-- 
Mailing list: https://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 1664397] Re: Mouse trails and distorted cursor on 2nd monitor

[Edward Gibbs]

ersion.libgl1-mesa-dri: libgl1-mesa-dri 12.0.6-0ubuntu0.16.04.1
>   version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
>   version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.6-0ubuntu0.16.04.1
>   version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.2
>   version.xserver-xorg-input-evdev: xserver-xorg-input-evdev
> 1:2.10.1-1ubuntu2
>   version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
>   version.xserver-xorg-video-intel: xserver-xorg-video-intel
> 2:2.99.917+git20160325-1ubuntu1.2
>   version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau
> 1:1.0.12-1build2
>   xserver.bootTime: Mon Feb 13 18:15:02 2017
>   xserver.configfile: default
>   xserver.logfile: /var/log/Xorg.0.log
>   xserver.version: 2:1.18.4-0ubuntu0.2
>   xserver.video_driver: modeset
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1664397/+subscriptions
>
-- 
Edward Gibbs
gibbs.edw...@gmail.com

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

Title:
  Mouse trails and distorted cursor on 2nd monitor

Status in xorg package in Ubuntu:
  Invalid

Bug description:
  Lenovo Thinkpad P50, Xeon, Nvidia M2000m 4GB, 16 GB RAM

  2nd monitor (ASUS) connected via either DP or HDMI, when using Hybrid
  Graphics the cursor on the second display is distorted and leaves
  mouse trails that persist for several seconds.  Switching to Nvidia
  graphics cures but Nvidia has other problems (built in display is dim
  and brightness cannot be adjusted).  Interestingly, just opening
  Display settings also cures the problem for as long as the Display
  Setting dialog is open.  Under Windows (10 Pro) Hybrid Graphics does
  not exhibit this problem.

  Ubuntu release is 16.04.2 LTS.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  Uname: Linux 4.9.0-040900-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  BootLog: /dev/nvme0n1p2: clean, 297436/7282688 files, 2849132/29101568 blocks
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Mon Feb 13 18:15:25 2017
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  DkmsStatus:
   bbswitch, 0.8, 4.4.0-62-generic, x86_64: installed
   bbswitch, 0.8, 4.9.0-040900-generic, x86_64: installed
  EcryptfsInUse: Yes
  GraphicsCard:
   NVIDIA Corporation GM107GLM [Quadro M2000M] [10de:13b0] (rev a2) (prog-if 00 
[VGA controller])
 Subsystem: Lenovo GM107GLM [Quadro M2000M] [17aa:2230]
  InstallationDate: Installed on 2017-01-07 (37 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  MachineType: LENOVO 20EN001SUS
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.9.0-040900-generic 
root=UUID=81b27291-6609-488b-8477-b2eb41ab17f2 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/08/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N1EET64W (1.37 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20EN001SUS
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40705 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN1EET64W(1.37):bd12/08/2016:svnLENOVO:pn20EN001SUS:pvrThinkPadP50:rvnLENOVO:rn20EN001SUS:rvrSDK0J40705WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.name: 20EN001SUS
  dmi.product.version: ThinkPad P50
  dmi.sys.vendor: LENOVO
  version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.70-1~ubuntu16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.6-0ubuntu0.16.04.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.6-0ubuntu0.16.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1.2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Mon Feb 13 18:15:02 2017
  xserver.configfile: default
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.18.4-0ubuntu0.2
  xserver.video_driver: modeset

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

-- 
Mailing list: https://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 1664397] Re: Mouse trails and distorted cursor on 2nd monitor

[Edward Gibbs]

nput-evdev
> 1:2.10.1-1ubuntu2
>   version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
>   version.xserver-xorg-video-intel: xserver-xorg-video-intel
> 2:2.99.917+git20160325-1ubuntu1.2
>   version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau
> 1:1.0.12-1build2
>   xserver.bootTime: Mon Feb 13 18:15:02 2017
>   xserver.configfile: default
>   xserver.logfile: /var/log/Xorg.0.log
>   xserver.version: 2:1.18.4-0ubuntu0.2
>   xserver.video_driver: modeset
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1664397/+subscriptions
>
-- 
Edward Gibbs
gibbs.edw...@gmail.com

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

Title:
  Mouse trails and distorted cursor on 2nd monitor

Status in xorg package in Ubuntu:
  Invalid

Bug description:
  Lenovo Thinkpad P50, Xeon, Nvidia M2000m 4GB, 16 GB RAM

  2nd monitor (ASUS) connected via either DP or HDMI, when using Hybrid
  Graphics the cursor on the second display is distorted and leaves
  mouse trails that persist for several seconds.  Switching to Nvidia
  graphics cures but Nvidia has other problems (built in display is dim
  and brightness cannot be adjusted).  Interestingly, just opening
  Display settings also cures the problem for as long as the Display
  Setting dialog is open.  Under Windows (10 Pro) Hybrid Graphics does
  not exhibit this problem.

  Ubuntu release is 16.04.2 LTS.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  Uname: Linux 4.9.0-040900-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  BootLog: /dev/nvme0n1p2: clean, 297436/7282688 files, 2849132/29101568 blocks
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Mon Feb 13 18:15:25 2017
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  DkmsStatus:
   bbswitch, 0.8, 4.4.0-62-generic, x86_64: installed
   bbswitch, 0.8, 4.9.0-040900-generic, x86_64: installed
  EcryptfsInUse: Yes
  GraphicsCard:
   NVIDIA Corporation GM107GLM [Quadro M2000M] [10de:13b0] (rev a2) (prog-if 00 
[VGA controller])
 Subsystem: Lenovo GM107GLM [Quadro M2000M] [17aa:2230]
  InstallationDate: Installed on 2017-01-07 (37 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  MachineType: LENOVO 20EN001SUS
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.9.0-040900-generic 
root=UUID=81b27291-6609-488b-8477-b2eb41ab17f2 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/08/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N1EET64W (1.37 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20EN001SUS
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40705 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN1EET64W(1.37):bd12/08/2016:svnLENOVO:pn20EN001SUS:pvrThinkPadP50:rvnLENOVO:rn20EN001SUS:rvrSDK0J40705WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.name: 20EN001SUS
  dmi.product.version: ThinkPad P50
  dmi.sys.vendor: LENOVO
  version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.70-1~ubuntu16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.6-0ubuntu0.16.04.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.6-0ubuntu0.16.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1.2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Mon Feb 13 18:15:02 2017
  xserver.configfile: default
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.18.4-0ubuntu0.2
  xserver.video_driver: modeset

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

-- 
Mailing list: https://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 1664397] Re: Mouse trails and distorted cursor on 2nd monitor

[Edward Gibbs]

I have the same pre-install of Windows with Lenovo bloatware. I boot it up
every once in a while and let it download whatever Windows and Lenovo
updates it thinks it needs, including video and BIOS, but I don't think
that was what fixed it.  On the Linux side I am running 17.04 now with
community nvidia drivers and have no issues.  I haven't tried Qubes in a
while, but I don't recall noticing the issue last time I was in it.  But my
setup has changed quite a bit too - I am now using dual Lenovo FHD monitors
(one on HDMI, one on DP plus the internal screen, and it seems to work
fine.  I also have Fedora 25 installed and that works too.  What version of
Ubuntu are you running?

Ed Gibbs

On Wed, May 17, 2017 at 4:42 AM maarten <1664...@bugs.launchpad.net>
wrote:

> Updating firmware from Windows doesn't do it for me, but that might be
> because I've got a preinstalled Windows with a Lenovo-supplied version
> of the Intel driver. Windows works fine with it and I would like to keep
> it running fine ofcourse. gibbs-edward: Did you install the latest Intel
> P530 driver instead?
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1664397
>
> Title:
>   Mouse trails and distorted cursor on 2nd monitor
>
> Status in xorg package in Ubuntu:
>   Invalid
>
> Bug description:
>   Lenovo Thinkpad P50, Xeon, Nvidia M2000m 4GB, 16 GB RAM
>
>   2nd monitor (ASUS) connected via either DP or HDMI, when using Hybrid
>   Graphics the cursor on the second display is distorted and leaves
>   mouse trails that persist for several seconds.  Switching to Nvidia
>   graphics cures but Nvidia has other problems (built in display is dim
>   and brightness cannot be adjusted).  Interestingly, just opening
>   Display settings also cures the problem for as long as the Display
>   Setting dialog is open.  Under Windows (10 Pro) Hybrid Graphics does
>   not exhibit this problem.
>
>   Ubuntu release is 16.04.2 LTS.
>
>   ProblemType: Bug
>   DistroRelease: Ubuntu 16.04
>   Package: xorg 1:7.7+13ubuntu3
>   Uname: Linux 4.9.0-040900-generic x86_64
>   .tmp.unity_support_test.0:
>
>   ApportVersion: 2.20.1-0ubuntu2.5
>   Architecture: amd64
>   BootLog: /dev/nvme0n1p2: clean, 297436/7282688 files, 2849132/29101568
> blocks
>   CompizPlugins: No value set for
> `/apps/compiz-1/general/screen0/options/active_plugins'
>   CompositorRunning: compiz
>   CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
>   CompositorUnredirectFSW: true
>   CurrentDesktop: Unity
>   Date: Mon Feb 13 18:15:25 2017
>   DistUpgraded: Fresh install
>   DistroCodename: xenial
>   DistroVariant: ubuntu
>   DkmsStatus:
>bbswitch, 0.8, 4.4.0-62-generic, x86_64: installed
>bbswitch, 0.8, 4.9.0-040900-generic, x86_64: installed
>   EcryptfsInUse: Yes
>   GraphicsCard:
>NVIDIA Corporation GM107GLM [Quadro M2000M] [10de:13b0] (rev a2)
> (prog-if 00 [VGA controller])
>  Subsystem: Lenovo GM107GLM [Quadro M2000M] [17aa:2230]
>   InstallationDate: Installed on 2017-01-07 (37 days ago)
>   InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64
> (20160719)
>   MachineType: LENOVO 20EN001SUS
>   ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.9.0-040900-generic
> root=UUID=81b27291-6609-488b-8477-b2eb41ab17f2 ro quiet splash vt.handoff=7
>   SourcePackage: xorg
>   UpgradeStatus: No upgrade log present (probably fresh install)
>   dmi.bios.date: 12/08/2016
>   dmi.bios.vendor: LENOVO
>   dmi.bios.version: N1EET64W (1.37 )
>   dmi.board.asset.tag: Not Available
>   dmi.board.name: 20EN001SUS
>   dmi.board.vendor: LENOVO
>   dmi.board.version: SDK0J40705 WIN
>   dmi.chassis.asset.tag: No Asset Information
>   dmi.chassis.type: 10
>   dmi.chassis.vendor: LENOVO
>   dmi.chassis.version: None
>   dmi.modalias:
> dmi:bvnLENOVO:bvrN1EET64W(1.37):bd12/08/2016:svnLENOVO:pn20EN001SUS:pvrThinkPadP50:rvnLENOVO:rn20EN001SUS:rvrSDK0J40705WIN:cvnLENOVO:ct10:cvrNone:
>   dmi.product.name: 20EN001SUS
>   dmi.product.version: ThinkPad P50
>   dmi.sys.vendor: LENOVO
>   version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
>   version.ia32-libs: ia32-libs N/A
>   version.libdrm2: libdrm2 2.4.70-1~ubuntu16.04.1
>   version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.6-0ubuntu0.16.04.1
>   version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
>   version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.6-0ubuntu0.16.04.1
>   version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.2
>   version.xserver-xorg-input-evdev: xserver-xorg-input-evdev
> 1:2.10.1-1ubuntu2
>   version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
>   version.xserver-xorg-video-intel: xserver-x

[Desktop-packages] [Bug 1584300] Re: X can't be started without login manager

[Edward Betts]

It seems like this is by design, the workaround is to install xserver-
xorg-legacy.

See https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=802544
And 
http://sources.debian.net/src/xorg-server/2:1.19.3-1/debian/xserver-xorg-core.NEWS/?hl=15#L15

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

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

Title:
  X can't be started without login manager

Status in xorg package in Ubuntu:
  New

Bug description:
  On Ubuntu 16.04 LTS

  X runs fine from the login manager, but if I remove the login manager
  (apt-get remove sddm), X can't be run from the text login: running
  startx don't even change to graphic mode and causes errors (log
  attached).

  This used to work at least up to 15.04

  This happens on various VM vith different video card emulation (vmware, 
cirrus, qemu vga) and on both ubuntu and kubuntu. Log changes slightly, but it 
still seems a permission-related problem: depending by the (emulated) video HW, 
it can complain about 
  xf86EnableIOPorts: failed to set IOPL for I/O (Operation not permitted)
  or can segfault in libpciaccess.

  This happens both on system updated from older version (15.04) and on
  a new clean install from scratch.

  While the installed-from-scratch system obviously has the default,
  untouched, kernel, on the machine I updated from 15.04 I kept my
  custom kernel, that is the same that worked before update to 16.04, so
  it's probably not due to anything related to the kernel). Never tested
  outside a VM on real HW.

  On the system I updated from 15.04, I also tried to run startx as
  root, and it seems to make the difference, because in this way the
  graphic is initialized correctly. (I see some windows with errors, and
  I can't reach the desktop, but this is probably another unrelated
  problem, possibly due to my local configuration).

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  Uname: Linux 4.5.2 x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  Date: Sat May 21 11:01:12 2016
  InstallationDate: Installed on 2012-03-02 (1540 days ago)
  InstallationMedia: Kubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
  ProcEnviron:
   TERM=linux
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: xorg
  UpgradeStatus: Upgraded to xenial on 2016-05-16 (4 days ago)

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

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

[Desktop-packages] [Bug 1683080] [NEW] package libcuda1-352 361.45.11-0ubuntu0.16.04.1 failed to install/upgrade: there is no script in the new version of the package - giving up

[Edward G Prentice]

Public bug reported:

failed during 'sudo aptitude dist-upgrade'

ProblemType: Package
DistroRelease: Ubuntu 17.04
Package: libcuda1-352 361.45.11-0ubuntu0.16.04.1
ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8
Uname: Linux 4.10.0-19-generic x86_64
ApportVersion: 2.20.4-0ubuntu4
Architecture: amd64
Date: Sat Apr 15 15:37:45 2017
ErrorMessage: there is no script in the new version of the package - giving up
InstallationDate: Installed on 2015-03-23 (754 days ago)
InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1)
RelatedPackageVersions:
 dpkg 1.18.10ubuntu2
 apt  1.4
SourcePackage: nvidia-graphics-drivers-361
Title: package libcuda1-352 361.45.11-0ubuntu0.16.04.1 failed to 
install/upgrade: there is no script in the new version of the package - giving 
up
UpgradeStatus: Upgraded to zesty on 2017-04-15 (0 days ago)

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


** Tags: amd64 apport-package need-duplicate-check third-party-packages zesty

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

Title:
  package libcuda1-352 361.45.11-0ubuntu0.16.04.1 failed to
  install/upgrade: there is no script in the new version of the package
  - giving up

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

Bug description:
  failed during 'sudo aptitude dist-upgrade'

  ProblemType: Package
  DistroRelease: Ubuntu 17.04
  Package: libcuda1-352 361.45.11-0ubuntu0.16.04.1
  ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8
  Uname: Linux 4.10.0-19-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  Date: Sat Apr 15 15:37:45 2017
  ErrorMessage: there is no script in the new version of the package - giving up
  InstallationDate: Installed on 2015-03-23 (754 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1)
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu2
   apt  1.4
  SourcePackage: nvidia-graphics-drivers-361
  Title: package libcuda1-352 361.45.11-0ubuntu0.16.04.1 failed to 
install/upgrade: there is no script in the new version of the package - giving 
up
  UpgradeStatus: Upgraded to zesty on 2017-04-15 (0 days ago)

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

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

[Desktop-packages] [Bug 1683081] [NEW] package nvidia-opencl-icd-352 361.45.11-0ubuntu0.16.04.1 failed to install/upgrade: there is no script in the new version of the package - giving up

[Edward G Prentice]

Public bug reported:

failed during 'sudo aptitude dist-upgrade'

ProblemType: Package
DistroRelease: Ubuntu 17.04
Package: nvidia-opencl-icd-352 361.45.11-0ubuntu0.16.04.1
ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8
Uname: Linux 4.10.0-19-generic x86_64
ApportVersion: 2.20.4-0ubuntu4
Architecture: amd64
Date: Sat Apr 15 15:37:50 2017
ErrorMessage: there is no script in the new version of the package - giving up
InstallationDate: Installed on 2015-03-23 (754 days ago)
InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1)
RelatedPackageVersions:
 dpkg 1.18.10ubuntu2
 apt  1.4
SourcePackage: nvidia-graphics-drivers-361
Title: package nvidia-opencl-icd-352 361.45.11-0ubuntu0.16.04.1 failed to 
install/upgrade: there is no script in the new version of the package - giving 
up
UpgradeStatus: Upgraded to zesty on 2017-04-15 (0 days ago)

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


** Tags: amd64 apport-package need-duplicate-check third-party-packages zesty

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

Title:
  package nvidia-opencl-icd-352 361.45.11-0ubuntu0.16.04.1 failed to
  install/upgrade: there is no script in the new version of the package
  - giving up

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

Bug description:
  failed during 'sudo aptitude dist-upgrade'

  ProblemType: Package
  DistroRelease: Ubuntu 17.04
  Package: nvidia-opencl-icd-352 361.45.11-0ubuntu0.16.04.1
  ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8
  Uname: Linux 4.10.0-19-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  Date: Sat Apr 15 15:37:50 2017
  ErrorMessage: there is no script in the new version of the package - giving up
  InstallationDate: Installed on 2015-03-23 (754 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1)
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu2
   apt  1.4
  SourcePackage: nvidia-graphics-drivers-361
  Title: package nvidia-opencl-icd-352 361.45.11-0ubuntu0.16.04.1 failed to 
install/upgrade: there is no script in the new version of the package - giving 
up
  UpgradeStatus: Upgraded to zesty on 2017-04-15 (0 days ago)

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

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

[Desktop-packages] [Bug 1664397] Re: Mouse trails and distorted cursor on 2nd monitor

[Edward Gibbs]

Well, it was not a firmware update that fixed it.  I'm on Qubes 4.2
right now and it still has the problem,  Qubes is using Xfce 4.12 as
it's desktop manager, which I believe is Ubuntu based.  Some update to
Ubuntu must have fixed the problem and it hasn't been rolled into the
Xfce version Qubes is using.

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

Title:
  Mouse trails and distorted cursor on 2nd monitor

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  Lenovo Thinkpad P50, Xeon, Nvidia M2000m 4GB, 16 GB RAM

  2nd monitor (ASUS) connected via either DP or HDMI, when using Hybrid
  Graphics the cursor on the second display is distorted and leaves
  mouse trails that persist for several seconds.  Switching to Nvidia
  graphics cures but Nvidia has other problems (built in display is dim
  and brightness cannot be adjusted).  Interestingly, just opening
  Display settings also cures the problem for as long as the Display
  Setting dialog is open.  Under Windows (10 Pro) Hybrid Graphics does
  not exhibit this problem.

  Ubuntu release is 16.04.2 LTS.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  Uname: Linux 4.9.0-040900-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  BootLog: /dev/nvme0n1p2: clean, 297436/7282688 files, 2849132/29101568 blocks
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Mon Feb 13 18:15:25 2017
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  DkmsStatus:
   bbswitch, 0.8, 4.4.0-62-generic, x86_64: installed
   bbswitch, 0.8, 4.9.0-040900-generic, x86_64: installed
  EcryptfsInUse: Yes
  GraphicsCard:
   NVIDIA Corporation GM107GLM [Quadro M2000M] [10de:13b0] (rev a2) (prog-if 00 
[VGA controller])
 Subsystem: Lenovo GM107GLM [Quadro M2000M] [17aa:2230]
  InstallationDate: Installed on 2017-01-07 (37 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  MachineType: LENOVO 20EN001SUS
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.9.0-040900-generic 
root=UUID=81b27291-6609-488b-8477-b2eb41ab17f2 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/08/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N1EET64W (1.37 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20EN001SUS
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40705 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN1EET64W(1.37):bd12/08/2016:svnLENOVO:pn20EN001SUS:pvrThinkPadP50:rvnLENOVO:rn20EN001SUS:rvrSDK0J40705WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.name: 20EN001SUS
  dmi.product.version: ThinkPad P50
  dmi.sys.vendor: LENOVO
  version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.70-1~ubuntu16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.6-0ubuntu0.16.04.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.6-0ubuntu0.16.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1.2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Mon Feb 13 18:15:02 2017
  xserver.configfile: default
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.18.4-0ubuntu0.2
  xserver.video_driver: modeset

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

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

[Desktop-packages] [Bug 1664397] Re: Mouse trails and distorted cursor on 2nd monitor

[Edward Gibbs]

As requested I downloaded the latest build and ran it from USB.  After
selecting hybrid graphics in BIOS I booted up and was delighted to see
no mouse trails on the 2nd monitor!

I then rebooted back into 16.04 leaving hybrid graphics selected - no
mouse trails!

I think there was an Intel firmware update a week or two ago that I got
on Windows, maybe it updated the Intel graphics firmware?  Whatever
happened I am happy to say that I cannot now duplicate the problem and
hybrid graphics seems to be working properly in both 16.04 and 17.10.

Thanks for your help.

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

Title:
  Mouse trails and distorted cursor on 2nd monitor

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  Lenovo Thinkpad P50, Xeon, Nvidia M2000m 4GB, 16 GB RAM

  2nd monitor (ASUS) connected via either DP or HDMI, when using Hybrid
  Graphics the cursor on the second display is distorted and leaves
  mouse trails that persist for several seconds.  Switching to Nvidia
  graphics cures but Nvidia has other problems (built in display is dim
  and brightness cannot be adjusted).  Interestingly, just opening
  Display settings also cures the problem for as long as the Display
  Setting dialog is open.  Under Windows (10 Pro) Hybrid Graphics does
  not exhibit this problem.

  Ubuntu release is 16.04.2 LTS.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  Uname: Linux 4.9.0-040900-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  BootLog: /dev/nvme0n1p2: clean, 297436/7282688 files, 2849132/29101568 blocks
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Mon Feb 13 18:15:25 2017
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  DkmsStatus:
   bbswitch, 0.8, 4.4.0-62-generic, x86_64: installed
   bbswitch, 0.8, 4.9.0-040900-generic, x86_64: installed
  EcryptfsInUse: Yes
  GraphicsCard:
   NVIDIA Corporation GM107GLM [Quadro M2000M] [10de:13b0] (rev a2) (prog-if 00 
[VGA controller])
 Subsystem: Lenovo GM107GLM [Quadro M2000M] [17aa:2230]
  InstallationDate: Installed on 2017-01-07 (37 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  MachineType: LENOVO 20EN001SUS
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.9.0-040900-generic 
root=UUID=81b27291-6609-488b-8477-b2eb41ab17f2 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/08/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N1EET64W (1.37 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20EN001SUS
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40705 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN1EET64W(1.37):bd12/08/2016:svnLENOVO:pn20EN001SUS:pvrThinkPadP50:rvnLENOVO:rn20EN001SUS:rvrSDK0J40705WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.name: 20EN001SUS
  dmi.product.version: ThinkPad P50
  dmi.sys.vendor: LENOVO
  version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.70-1~ubuntu16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.6-0ubuntu0.16.04.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.6-0ubuntu0.16.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1.2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Mon Feb 13 18:15:02 2017
  xserver.configfile: default
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.18.4-0ubuntu0.2
  xserver.video_driver: modeset

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

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

[Desktop-packages] [Bug 1664397] [NEW] Mouse trails and distorted cursor on 2nd monitor

[Edward Gibbs]

Public bug reported:

Lenovo Thinkpad P50, Xeon, Nvidia M2000m 4GB, 16 GB RAM

2nd monitor (ASUS) connected via either DP or HDMI, when using Hybrid
Graphics the cursor on the second display is distorted and leaves mouse
trails that persist for several seconds.  Switching to Nvidia graphics
cures but Nvidia has other problems (built in display is dim and
brightness cannot be adjusted).  Interestingly, just opening Display
settings also cures the problem for as long as the Display Setting
dialog is open.  Under Windows (10 Pro) Hybrid Graphics does not exhibit
this problem.

Ubuntu release is 16.04.2 LTS.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg 1:7.7+13ubuntu3
Uname: Linux 4.9.0-040900-generic x86_64
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.1-0ubuntu2.5
Architecture: amd64
BootLog: /dev/nvme0n1p2: clean, 297436/7282688 files, 2849132/29101568 blocks
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
CurrentDesktop: Unity
Date: Mon Feb 13 18:15:25 2017
DistUpgraded: Fresh install
DistroCodename: xenial
DistroVariant: ubuntu
DkmsStatus:
 bbswitch, 0.8, 4.4.0-62-generic, x86_64: installed
 bbswitch, 0.8, 4.9.0-040900-generic, x86_64: installed
EcryptfsInUse: Yes
GraphicsCard:
 NVIDIA Corporation GM107GLM [Quadro M2000M] [10de:13b0] (rev a2) (prog-if 00 
[VGA controller])
   Subsystem: Lenovo GM107GLM [Quadro M2000M] [17aa:2230]
InstallationDate: Installed on 2017-01-07 (37 days ago)
InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719)
MachineType: LENOVO 20EN001SUS
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.9.0-040900-generic 
root=UUID=81b27291-6609-488b-8477-b2eb41ab17f2 ro quiet splash vt.handoff=7
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 12/08/2016
dmi.bios.vendor: LENOVO
dmi.bios.version: N1EET64W (1.37 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20EN001SUS
dmi.board.vendor: LENOVO
dmi.board.version: SDK0J40705 WIN
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.modalias: 
dmi:bvnLENOVO:bvrN1EET64W(1.37):bd12/08/2016:svnLENOVO:pn20EN001SUS:pvrThinkPadP50:rvnLENOVO:rn20EN001SUS:rvrSDK0J40705WIN:cvnLENOVO:ct10:cvrNone:
dmi.product.name: 20EN001SUS
dmi.product.version: ThinkPad P50
dmi.sys.vendor: LENOVO
version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.70-1~ubuntu16.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.6-0ubuntu0.16.04.1
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.6-0ubuntu0.16.04.1
version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1.2
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2
xserver.bootTime: Mon Feb 13 18:15:02 2017
xserver.configfile: default
xserver.logfile: /var/log/Xorg.0.log
xserver.version: 2:1.18.4-0ubuntu0.2
xserver.video_driver: modeset

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


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

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

Title:
  Mouse trails and distorted cursor on 2nd monitor

Status in xorg package in Ubuntu:
  New

Bug description:
  Lenovo Thinkpad P50, Xeon, Nvidia M2000m 4GB, 16 GB RAM

  2nd monitor (ASUS) connected via either DP or HDMI, when using Hybrid
  Graphics the cursor on the second display is distorted and leaves
  mouse trails that persist for several seconds.  Switching to Nvidia
  graphics cures but Nvidia has other problems (built in display is dim
  and brightness cannot be adjusted).  Interestingly, just opening
  Display settings also cures the problem for as long as the Display
  Setting dialog is open.  Under Windows (10 Pro) Hybrid Graphics does
  not exhibit this problem.

  Ubuntu release is 16.04.2 LTS.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  Uname: Linux 4.9.0-040900-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  BootLog: /dev/nvme0n1p2: clean, 297436/7282688 files, 2849132/29101568 blocks
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Mon Feb 13 18:15:25 2017
  

[Desktop-packages] [Bug 1569876] Re: Mouse trails disappear only on window refresh

[Edward Gibbs]

I am having a nearly identical problem with my P50 and an ASUS external
monitor.

In my case the trails last for a second or two then go away until I move
the mouse again.  I have the same distorted cursor problem.

I've tried connecting with DP and HDMI, using proprietary or community
drivers, purging nvidia drivers and reloading, etc.  By accident I have
discovered that opening the System Settings and going to the Display
settings (just going to them, not doing anything there) fixes it for as
long as the Display settings are open.  As soon as I close Display
settings it comes right back.

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

Title:
  Mouse trails disappear only on window refresh

Status in xserver-xorg-video-nouveau package in Ubuntu:
  Triaged

Bug description:
  While using nouveau, when I move the mouse it leaves trails that
  disappear when I move the mouse over them or when I refresh the
  screen. The mouse cursor is distorted when moving it slowly which
  makes it harder to click on small buttons (e.g., resizing a window) as
  it's hard to tell where exactly the mouse is located.

  WORKAROUND: Use nivida 367.18.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-18.34-generic 4.4.6
  Uname: Linux 4.4.0-18-generic x86_64
  .tmp.unity.support.test.0:

  ApportVersion: 2.20.1-0ubuntu1
  Architecture: amd64
  BootLog: /dev/sda6: clean, 789425/48300032 files, 33613548/193179136 blocks
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: KDE
  Date: Wed Apr 13 15:29:36 2016
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: kubuntu
  DkmsStatus:
   bbswitch, 0.8, 4.4.0-17-generic, x86_64: installed
   bbswitch, 0.8, 4.4.0-18-generic, x86_64: installed
  ExtraDebuggingInterest: No
  GraphicsCard:
   Intel Corporation Skylake Integrated Graphics [8086:191b] (rev 06) (prog-if 
00 [VGA controller])
     Subsystem: Lenovo Skylake Integrated Graphics [17aa:222e]
   NVIDIA Corporation GM107GLM [Quadro M1000M] [10de:13b1] (rev a2) (prog-if 00 
[VGA controller])
     Subsystem: Lenovo GM107GLM [Quadro M1000M] [17aa:222e]
  InstallationDate: Installed on 2016-04-01 (12 days ago)
  InstallationMedia: Kubuntu 16.04 LTS "Xenial Xerus" - Beta amd64 (20160331)
  MachineType: LENOVO 20EN0013US
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-18-generic 
root=UUID=8e0207fc-0fb8-42e7-9dfc-a301c74d2146 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/08/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N1EET47W (1.21 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20EN0013US
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40705 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN1EET47W(1.21):bd03/08/2016:svnLENOVO:pn20EN0013US:pvrThinkPadP50:rvnLENOVO:rn20EN0013US:rvrSDK0J40705WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.name: 20EN0013US
  dmi.product.version: ThinkPad P50
  dmi.sys.vendor: LENOVO
  version.compiz: compiz 1:0.9.12.2+16.04.20160331-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.67-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Wed Apr 13 07:51:19 2016
  xserver.configfile: default
  xserver.errors:
   Failed to load module "nvidia" (module does not exist, 0)
   Failed to load module "nvidia" (module does not exist, 0)
   Unknown chipset: NV117
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.18.3-1ubuntu2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-nouveau/+bug/1569876/+subscriptions

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

[Desktop-packages] [Bug 1580692] Re: Dell latitude e6520 display freezes must reboot

[Edward Cherlin]

I have seen several remedies proposed for this bug, each of which seems
to work for some people and not others.

I am running Ubuntu 16.10. I had the mouse problem recurring every few
minutes, with the cursor moving normally but unable to click on
anything. Sometimes I could click in one window and not another.
Sometimes I could not click in any window, but the toolbar menu worked.

I also have Windows installed on this computer. The bug never occurs in
Windows.

Upgrade BIOS to A05: No effect on the bug on my computer.

Remove deprecated video driver: No effect on the bug on my computer.

Install most recent version of non-free Nvidia driver, 367.57 0ubuntu3:
Fixes bug on my computer almost completely.

Workarounds:

Switch console ctrl-alt-f1 and back ctrl-alt-f7. Mouse usually resumes
normal action.

Switch to Guest account and back using toolbar menu. Mouse usually
resumes normal action.

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

Title:
  Dell latitude e6520 display freezes must reboot

Status in firefox package in Ubuntu:
  New

Bug description:
  This is a fresh install of Ubuntu 16.04LTS 64 on a Dell Latitude E6520
  laptop with an Intel core i7-2720QM (4 core) CPU, 8GB RAM and an
  NVIDIA N12P-NS2 video controller. The display freezes at random (I had
  this 10 times today with completely different apps running). The mouse
  still moves but the system does not react to clicks or keypresses (not
  even Ctrl-Alt-Del etc. and I can't access terminals at Ctrl+Alt+F1
  etc.) It does not shut down gracefully when the power button is
  pressed. The system is however still active and can be accessed
  externally through SSH. The mouse and screen seems slightly less
  responsive than usual a few seconds before the freeze so that I can
  "feel it coming". However, it is hardly noticeable.

  I noticed that the underside of the laptop is sometimes very hot when
  the display freezes, but it is not systematic, sometimes the freeze
  happens after the laptop had time to cool before booting and hasn't
  got hot yet.

  Until recently this laptop was running windows 7 64 pro without any
  problem. I have performed a full hardware test of the laptop (via
  setup) only a couple of days ago, there was no issue.

  I attached the output of dmesg and the Xorg.0.log file.

  This is not a critical system to me but I thought I'd report the bug
  for all intents and purposes, and I'd rather not reinstall windows on
  it if it can be helped ;-)

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

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

[Desktop-packages] [Bug 1654912] [NEW] Bluetooth sound card not detected - MMOVE Bluetooth Headphones

[Edward]

Public bug reported:

TRNDlabs MMOVE Bluetooth Headphones (earbuds) pair just fine using
blueman, but no sound, and not detected by PulseAudio Volume Control.

Earphones Parameters:
Support Profiles: HFP, HSP, AVRCP, AZDP
Audio Profile: APTX
Bluetooth Version: 4.0
Troubleshooting Tried Already:
-Adjusted Volume
-Looked for any kind of controls for volume in PulseAudio Volume Control and 
Alsa Mixer and QAS Mixer.
-Looked in Synaptic Package Manager for packages that might solve the issue 
(search words, bluetooth, audio, pulse)
-found intone, but it's support is A2DP headsets, which this product 
does not mention.
-tried installing this package, program locks up and won't play 
the music files I try (but that's a separate issue)
-tried installing xfce4-pulseaudio-plugin, couldn't figure out 
how to run it after install, didn't try just running in terminal yet
-treid installing pulseaudio-module-bluetooth, this most likely 
will work...no it didn't

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: alsa-base 1.0.25+dfsg-0ubuntu5
ProcVersionSignature: Ubuntu 4.4.0-57.78-lowlatency 4.4.35
Uname: Linux 4.4.0-57-lowlatency x86_64
ApportVersion: 2.20.1-0ubuntu2.4
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/pcmC0D0p:   Edward-admin   1741 F...m pulseaudio
 /dev/snd/controlC0:  Edward-admin   1741 F pulseaudio
CurrentDesktop: XFCE
Date: Sun Jan  8 17:41:16 2017
InstallationDate: Installed on 2016-12-19 (20 days ago)
InstallationMedia: Ubuntu-Studio 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
JournalErrors:
 Error: command ['journalctl', '-b', '--priority=warning', '--lines=1000'] 
failed with exit code 1: Hint: You are currently not seeing messages from other 
users and the system.
   Users in the 'systemd-journal' group can see all messages. Pass -q to
   turn off this notice.
 No journal files were opened due to insufficient permissions.
PackageArchitecture: all
SourcePackage: alsa-driver
Symptom: audio
Title: Bluetooth sound card not detected
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 07/16/2015
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: B219P027
dmi.board.asset.tag: N/A
dmi.board.name: ZBOX-CI320NANO series
dmi.board.vendor: ZOTAC
dmi.board.version: Rev.00
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: To Be Filled By O.E.M.
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrB219P027:bd07/16/2015:svnMotherboardbyZOTAC:pnZBOX-CI320NANOseries:pvrRev.00:rvnZOTAC:rnZBOX-CI320NANOseries:rvrRev.00:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
dmi.product.name: ZBOX-CI320NANO series
dmi.product.version: Rev.00
dmi.sys.vendor: Motherboard by ZOTAC

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


** Tags: amd64 apport-bug xenial

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

Title:
  Bluetooth sound card not detected - MMOVE Bluetooth Headphones

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  TRNDlabs MMOVE Bluetooth Headphones (earbuds) pair just fine using
  blueman, but no sound, and not detected by PulseAudio Volume Control.

  Earphones Parameters:
  Support Profiles: HFP, HSP, AVRCP, AZDP
  Audio Profile: APTX
  Bluetooth Version: 4.0
  Troubleshooting Tried Already:
  -Adjusted Volume
  -Looked for any kind of controls for volume in PulseAudio Volume Control and 
Alsa Mixer and QAS Mixer.
  -Looked in Synaptic Package Manager for packages that might solve the issue 
(search words, bluetooth, audio, pulse)
-found intone, but it's support is A2DP headsets, which this product 
does not mention.
-tried installing this package, program locks up and won't play 
the music files I try (but that's a separate issue)
-tried installing xfce4-pulseaudio-plugin, couldn't figure out 
how to run it after install, didn't try just running in terminal yet
-treid installing pulseaudio-module-bluetooth, this most likely 
will work...no it didn't

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.4.0-57.78-lowlatency 4.4.35
  Uname: Linux 4.4.0-57-lowlatency x86_64
  ApportVersion: 2.20.1-0ubuntu2.4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   Edward-admin   1741 F...m pulseaudio
   /dev/snd/controlC0:  Edward-admin   1741 F pulseaudio
  CurrentDesktop: XFCE
  Date: Sun Jan  8 17:41:16 2017
  InstallationDate: Installed on 2016-12-19 (20 days ago)
  InstallationMedia: Ubuntu-Studio 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  JournalErrors:
   Error: command ['journalctl', '-b',

[Desktop-packages] [Bug 1442050] Re: (colord:832): Cd-WARNING **: failed to get session [pid 690]: Unknown error -2

[Edward Donovan]

This is happening on a machine I just upgraded to 16.10.  AFAICT, from
looking back at the logs, it only started happening, regularly, after
this upgrade.   :)

Only comes about every three hours here.  Just wanted to confirm it
seems to exist in the latest release.  Thanks.

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

Title:
  (colord:832): Cd-WARNING **: failed to get session [pid 690]: Unknown
  error -2

Status in colord package in Ubuntu:
  Confirmed

Bug description:
  Get that error logged into journalctl

  (colord:832): Cd-WARNING **: failed to get session [pid 690]: Unknown
  error -2

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: systemd 219-6ubuntu3
  ProcVersionSignature: Ubuntu 3.19.0-12.12-generic 3.19.3
  Uname: Linux 3.19.0-12-generic i686
  NonfreeKernelModules: nvidia
  ApportVersion: 2.17-0ubuntu1
  Architecture: i386
  CurrentDesktop: GNOME
  Date: Thu Apr  9 11:57:02 2015
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 003 Device 002: ID 046d:c50e Logitech, Inc. Cordless Mouse Receiver
   Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: ASUSTEK COMPUTER INC P5W DH Deluxe
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-12-generic 
root=UUID=7b1f4a51-558f-468f-85e0-f815d2f791e1 ro
  SourcePackage: systemd
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/22/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 3002
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: P5W DH Deluxe
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr3002:bd07/22/2010:svnASUSTEKCOMPUTERINC:pnP5WDHDeluxe:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5WDHDeluxe:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: P5W DH Deluxe
  dmi.product.version: System Version
  dmi.sys.vendor: ASUSTEK COMPUTER INC

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

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

[Desktop-packages] [Bug 1610769] [NEW] evince takes long time to load PDF if opened from recent files

[Edward Z. Yang]

Public bug reported:

Steps to reproduce:
1. Download this PDF http://web.mit.edu/~ezyang/Public/indiana.pdf
2. Open the PDF using the command "evince indiana.pdf"
3. Close evince, now open evince and attempt to open indiana.pdf from the 
recently used selection

Expected result: It opens as quickly as in (2)
Actual result: It doesn't open until substantially later.

Workaround: Open the PDF directly from command line

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: evince 3.18.2-1ubuntu4
ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
Uname: Linux 4.4.0-31-generic x86_64
NonfreeKernelModules: openafs
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
Date: Sun Aug  7 18:50:35 2016
EcryptfsInUse: Yes
InstallationDate: Installed on 2013-11-21 (991 days ago)
InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1)
SourcePackage: evince
UpgradeStatus: Upgraded to xenial on 2016-07-19 (19 days ago)

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


** Tags: amd64 apport-bug third-party-packages xenial

** Description changed:

  Steps to reproduce:
  1. Download this PDF http://web.mit.edu/~ezyang/Public/indiana.pdf
  2. Open the PDF using the command "evince indiana.pdf"
  3. Close evince, now open evince and attempt to open indiana.pdf from the 
recently used selection
  
  Expected result: It opens as quickly as in (2)
  Actual result: It doesn't open until substantially later.
+ 
+ Workaround: Open the PDF directly from command line
  
  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: evince 3.18.2-1ubuntu4
  ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
  Uname: Linux 4.4.0-31-generic x86_64
  NonfreeKernelModules: openafs
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  Date: Sun Aug  7 18:50:35 2016
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2013-11-21 (991 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  SourcePackage: evince
  UpgradeStatus: Upgraded to xenial on 2016-07-19 (19 days ago)

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

Title:
  evince takes long time to load PDF if opened from recent files

Status in evince package in Ubuntu:
  New

Bug description:
  Steps to reproduce:
  1. Download this PDF http://web.mit.edu/~ezyang/Public/indiana.pdf
  2. Open the PDF using the command "evince indiana.pdf"
  3. Close evince, now open evince and attempt to open indiana.pdf from the 
recently used selection

  Expected result: It opens as quickly as in (2)
  Actual result: It doesn't open until substantially later.

  Workaround: Open the PDF directly from command line

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: evince 3.18.2-1ubuntu4
  ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
  Uname: Linux 4.4.0-31-generic x86_64
  NonfreeKernelModules: openafs
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  Date: Sun Aug  7 18:50:35 2016
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2013-11-21 (991 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  SourcePackage: evince
  UpgradeStatus: Upgraded to xenial on 2016-07-19 (19 days ago)

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

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

[Desktop-packages] [Bug 1604563] [NEW] Install interrupted

[Edward Evans]

Public bug reported:

Goes to automatic report as soon as I try to install it.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg 1:7.7+13ubuntu3
ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
Uname: Linux 4.4.0-31-generic x86_64
NonfreeKernelModules: wl
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
Date: Tue Jul 19 14:50:39 2016
DistUpgraded: Fresh install
DistroCodename: xenial
DistroVariant: ubuntu
DkmsStatus:
 bcmwl, 6.30.223.248+bdcom, 4.4.0-21-generic, x86_64: installed
 bcmwl, 6.30.223.248+bdcom, 4.4.0-28-generic, x86_64: installed
 bcmwl, 6.30.223.248+bdcom, 4.4.0-31-generic, x86_64: installed
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 Advanced Micro Devices, Inc. [AMD/ATI] RV630/M76 [Mobility Radeon HD 2600 
XT/2700] [1002:9583] (prog-if 00 [VGA controller])
   Subsystem: Apple Inc. iMac 7,1 [106b:0083]
InstallationDate: Installed on 2016-07-12 (7 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
MachineType: Apple Inc. iMac7,1
ProcEnviron:
 LANGUAGE=en_US
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-31-generic.efi.signed 
root=UUID=defcb969-2ba0-4ba2-b311-3118142048bc ro quiet splash vt.handoff=7
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 03/05/08
dmi.bios.vendor: Apple Inc.
dmi.bios.version: IM71.88Z.007A.B03.0803051705
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: Mac-F42386C8
dmi.board.vendor: Apple Inc.
dmi.board.version: PVT
dmi.chassis.asset.tag: Asset Tag#
dmi.chassis.type: 13
dmi.chassis.vendor: Apple Inc.
dmi.chassis.version: Mac-F42386C8
dmi.modalias: 
dmi:bvnAppleInc.:bvrIM71.88Z.007A.B03.0803051705:bd03/05/08:svnAppleInc.:pniMac7,1:pvr1.0:rvnAppleInc.:rnMac-F42386C8:rvrPVT:cvnAppleInc.:ct13:cvrMac-F42386C8:
dmi.product.name: iMac7,1
dmi.product.version: 1.0
dmi.sys.vendor: Apple Inc.
version.compiz: compiz 1:0.9.12.2+16.04.20160714-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2
version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2.2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2
xserver.bootTime: Tue Jul 19 09:59:09 2016
xserver.configfile: default
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.version: 2:1.18.3-1ubuntu2.2
xserver.video_driver: radeon

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


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

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

Title:
  Install interrupted

Status in xorg package in Ubuntu:
  New

Bug description:
  Goes to automatic report as soon as I try to install it.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
  Uname: Linux 4.4.0-31-generic x86_64
  NonfreeKernelModules: wl
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Tue Jul 19 14:50:39 2016
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  DkmsStatus:
   bcmwl, 6.30.223.248+bdcom, 4.4.0-21-generic, x86_64: installed
   bcmwl, 6.30.223.248+bdcom, 4.4.0-28-generic, x86_64: installed
   bcmwl, 6.30.223.248+bdcom, 4.4.0-31-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] RV630/M76 [Mobility Radeon HD 2600 
XT/2700] [1002:9583] (prog-if 00 [VGA controller])
 Subsystem: Apple Inc. iMac 7,1 [106b:0083]
  InstallationDate: Installed on 2016-07-12 (7 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: Apple Inc. iMac7,1
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-31-generic.efi.signed 

Re: [Desktop-packages] [Bug 1587968] Re: evince insentitive to typing in search, page, zoom, ect fields

[M. Edward (Ed) Borasky]

I gave up on that ... took "proposed" repo out. I have a couple of
deadlines to meet and don't have time to troubleshoot a bleeding edge
repository. ;-)

On Mon, Jun 6, 2016 at 11:50 PM Sebastien Bacher 
wrote:

> could you try to figure out what updates creates the issue exactly?
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1587968
>
> Title:
>   evince insentitive to typing in search, page, zoom, ect fields
>
> Status in evince package in Ubuntu:
>   Confirmed
>
> Bug description:
>   Thw way to reproduce:
>   Open an attached example_file.pdf file.
>   Press CTRL+F
>   Try to type something (in my case the field is insensitive, I can only
> paste some string).
>
>   The same problem with page and zoom fields.
>
>   ProblemType: Bug
>   DistroRelease: Ubuntu 16.04
>   Package: evince 3.18.2-1ubuntu4
>   ProcVersionSignature: Ubuntu 4.4.0-23.41-generic 4.4.10
>   Uname: Linux 4.4.0-23-generic x86_64
>   NonfreeKernelModules: openafs
>   ApportVersion: 2.20.1-0ubuntu2.1
>   Architecture: amd64
>   CurrentDesktop: Unity
>   Date: Wed Jun  1 17:48:39 2016
>   InstallationDate: Installed on 2015-04-02 (426 days ago)
>   InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64
> (20141022.1)
>   SourcePackage: evince
>   UpgradeStatus: Upgraded to xenial on 2016-04-26 (36 days ago)
>
> To manage notifications about this bug go to:
>
> https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1587968/+subscriptions
>
-- 
How many people can stand on the shoulders of a giant before the giant
collapses?

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

Title:
  evince insentitive to typing in search, page, zoom, ect fields

Status in evince package in Ubuntu:
  Confirmed

Bug description:
  Thw way to reproduce:
  Open an attached example_file.pdf file.
  Press CTRL+F
  Try to type something (in my case the field is insensitive, I can only paste 
some string).

  The same problem with page and zoom fields.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: evince 3.18.2-1ubuntu4
  ProcVersionSignature: Ubuntu 4.4.0-23.41-generic 4.4.10
  Uname: Linux 4.4.0-23-generic x86_64
  NonfreeKernelModules: openafs
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Wed Jun  1 17:48:39 2016
  InstallationDate: Installed on 2015-04-02 (426 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1)
  SourcePackage: evince
  UpgradeStatus: Upgraded to xenial on 2016-04-26 (36 days ago)

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

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

[Desktop-packages] [Bug 1588197] Re: Can't type anything in search box

[M. Edward (Ed) Borasky]

Same here ... seems like a total lack of response / troubleshooting
assistance from Ubuntu so I've dropped back to "stock" Xenial and am
taking myself off the email list for this bug.

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

Title:
  Can't type anything in search box

Status in evince package in Ubuntu:
  Incomplete

Bug description:
  Since Ubuntu 16.04, I can't search strings in PDF using Evince viewer.
  Clicking search button or CTRL+F shows search box, but I can't type
  anything inside.

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

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

[Desktop-packages] [Bug 1587968] Re: evince insentitive to typing in search, page, zoom, ect fields

[M. Edward (Ed) Borasky]

Verified:

1. I can type in the Search field in Evince with my laptop, which does not have 
"propose" enabled.
2. Evince installed version is evince 3.18.2-1ubuntu4 on said laptop,

Attaching "showpkg" for the record - will do the same for the
workstation with "proposed" when I get back home.

** Attachment added: "non-proposed.showpkg"
   
https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1587968/+attachment/4678419/+files/non-proposed.showpkg

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

Title:
  evince insentitive to typing in search, page, zoom, ect fields

Status in evince package in Ubuntu:
  Confirmed

Bug description:
  Thw way to reproduce:
  Open an attached example_file.pdf file.
  Press CTRL+F
  Try to type something (in my case the field is insensitive, I can only paste 
some string).

  The same problem with page and zoom fields.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: evince 3.18.2-1ubuntu4
  ProcVersionSignature: Ubuntu 4.4.0-23.41-generic 4.4.10
  Uname: Linux 4.4.0-23-generic x86_64
  NonfreeKernelModules: openafs
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Wed Jun  1 17:48:39 2016
  InstallationDate: Installed on 2015-04-02 (426 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1)
  SourcePackage: evince
  UpgradeStatus: Upgraded to xenial on 2016-04-26 (36 days ago)

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

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

[Desktop-packages] [Bug 1587968] Re: evince insentitive to typing in search, page, zoom, ect fields

[M. Edward (Ed) Borasky]

I have two systems, a workstation with "proposed" and a laptop with
straight Xenial. Both have the same version of Evince. So it's probably
an underlying desktop library that recently showed up in "proposed".

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

Title:
  evince insentitive to typing in search, page, zoom, ect fields

Status in evince package in Ubuntu:
  Confirmed

Bug description:
  Thw way to reproduce:
  Open an attached example_file.pdf file.
  Press CTRL+F
  Try to type something (in my case the field is insensitive, I can only paste 
some string).

  The same problem with page and zoom fields.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: evince 3.18.2-1ubuntu4
  ProcVersionSignature: Ubuntu 4.4.0-23.41-generic 4.4.10
  Uname: Linux 4.4.0-23-generic x86_64
  NonfreeKernelModules: openafs
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Wed Jun  1 17:48:39 2016
  InstallationDate: Installed on 2015-04-02 (426 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1)
  SourcePackage: evince
  UpgradeStatus: Upgraded to xenial on 2016-04-26 (36 days ago)

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

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

[Desktop-packages] [Bug 1588197] Re: Can't type anything in search box

[M. Edward (Ed) Borasky]

I think the bug is in one of the underlying libraries, not Evince itself
- when I enabled "Proposed" it updated a few GNOME libraries but I don't
recall a change in Evince itself.

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

Title:
  Can't type anything in search box

Status in evince package in Ubuntu:
  Incomplete

Bug description:
  Since Ubuntu 16.04, I can't search strings in PDF using Evince viewer.
  Clicking search button or CTRL+F shows search box, but I can't type
  anything inside.

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

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

[Desktop-packages] [Bug 1587968] Re: evince insentitive to typing in search, page, zoom, ect fields

[M. Edward (Ed) Borasky]

Hit this too and allowed "xenial proposed" yesterday. The system is
16.04 desktop, installed from live USB yesterday.

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

Title:
  evince insentitive to typing in search, page, zoom, ect fields

Status in evince package in Ubuntu:
  Confirmed

Bug description:
  Thw way to reproduce:
  Open an attached example_file.pdf file.
  Press CTRL+F
  Try to type something (in my case the field is insensitive, I can only paste 
some string).

  The same problem with page and zoom fields.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: evince 3.18.2-1ubuntu4
  ProcVersionSignature: Ubuntu 4.4.0-23.41-generic 4.4.10
  Uname: Linux 4.4.0-23-generic x86_64
  NonfreeKernelModules: openafs
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Wed Jun  1 17:48:39 2016
  InstallationDate: Installed on 2015-04-02 (426 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1)
  SourcePackage: evince
  UpgradeStatus: Upgraded to xenial on 2016-04-26 (36 days ago)

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

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

[Desktop-packages] [Bug 1588197] Re: Can't type anything in search box

[M. Edward (Ed) Borasky]

A little more Google tells me this is probably a duplicate of bug
#1587968. I too just switched to installing from "proposed" - did any of
the others on this bug?

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

Title:
  Can't type anything in search box

Status in evince package in Ubuntu:
  Incomplete

Bug description:
  Since Ubuntu 16.04, I can't search strings in PDF using Evince viewer.
  Clicking search button or CTRL+F shows search box, but I can't type
  anything inside.

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

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

[Desktop-packages] [Bug 1588197] Re: Can't type anything in search box

[M. Edward (Ed) Borasky]

I just noticed this. 16.04, GNOME desktop. I can't remember when the
last time I did a successful search in Evince was but it's something I
do regularly. Maybe two or three days at most since it last worked.

I'm attaching an apt-cache show if it'll help.

** Attachment added: "apt-cache show for evince on my workstation"
   
https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1588197/+attachment/4675480/+files/evince.txt

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

Title:
  Can't type anything in search box

Status in evince package in Ubuntu:
  Incomplete

Bug description:
  Since Ubuntu 16.04, I can't search strings in PDF using Evince viewer.
  Clicking search button or CTRL+F shows search box, but I can't type
  anything inside.

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

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

[Desktop-packages] [Bug 1575000] Re: font glyph corruption on dialog box

[M. Edward (Ed) Borasky]

The workaround is worse than the symptom! I have Ubuntu GNOME 16.04 with
[AMD/ATI] Bonaire XT [Radeon HD 7790/8770 / R7 360 / R9 260/360 OEM].
I'm running the low-latency kernel, if it matters: 4.4.0-21-lowlatency
#37-Ubuntu

I went into the menu as described, restarted LibreOffice Calc and opened
the spreadsheet. Instead of garbled test, the dialog box was completely
blank. Then ... the screen went totally dark and Ctl-Alt-Delete no
longer worked. I ended up doing a hardware reset.

Are there by any chance some log files I can attach, or do you already
know what this is?

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

Title:
   font glyph corruption on dialog box

Status in LibreOffice:
  Unknown
Status in xserver-xorg-driver-ati:
  New
Status in xserver-xorg-video-ati package in Ubuntu:
  Confirmed

Bug description:
  I get a font glyph corruption in various dialog boxes in libreoffice. This 
happens using the following graphic configuration:
*-display   
 description: VGA compatible controller
 product: Bonaire [FirePro W5100]
 vendor: Advanced Micro Devices, Inc. [AMD/ATI]
 physical id: 0
 bus info: pci@:03:00.0
 version: 00
 width: 64 bits
 clock: 33MHz
 capabilities: vga_controller bus_master cap_list rom
 configuration: driver=radeon latency=0

  I don't see this in other graphics (NVIDIA, INTEL).

  Steps to reproduce:

  1. Open for instance LibreOffice Writer
  2. Copy some text to the clipboard
  3. Open the Paste Special dialog with CTRL-SHIFT-V 

  I attach a screenshot of the corrupted font.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xserver-xorg-video-radeon 1:7.7.0-1
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Tue Apr 26 09:23:41 2016
  DistUpgraded: 2016-03-11 12:35:09,412 DEBUG enabling apt cron job
  DistroCodename: xenial
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox, 5.0.18, 4.4.0-18-generic, x86_64: installed
   virtualbox, 5.0.18, 4.4.0-21-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Bonaire [FirePro W5100] [1002:6649] 
(prog-if 00 [VGA controller])
 Subsystem: Dell Bonaire [FirePro W5100] [1028:230c]
  InstallationDate: Installed on 2015-10-17 (191 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  MachineType: Dell Inc. Precision Tower 7810
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-21-generic 
root=UUID=63c3c29d-24d9-4ecb-8511-3f2291792bc5 ro quiet splash vt.handoff=7
  SourcePackage: xserver-xorg-video-ati
  UpgradeStatus: Upgraded to xenial on 2016-03-11 (45 days ago)
  dmi.bios.date: 04/14/2015
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A07
  dmi.board.name: 0GWHMW
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 7
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA07:bd04/14/2015:svnDellInc.:pnPrecisionTower7810:pvr01:rvnDellInc.:rn0GWHMW:rvrA00:cvnDellInc.:ct7:cvr:
  dmi.product.name: Precision Tower 7810
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.12.2+16.04.20160415-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.67-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Mon Apr 25 08:20:34 2016
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.18.3-1ubuntu2
  xserver.video_driver: radeon

To manage notifications about this bug go to:
https://bugs.launchpad.net/df-libreoffice/+bug/1575000/+subscriptions

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

[Desktop-packages] [Bug 1569566] [NEW] Missing / garbled fonts in LibreOffice Calc

[M. Edward (Ed) Borasky]

Public bug reported:

Ubuntu 16.04 beta, GNOME desktop. To reproduce, open LibreOffice Calc
and paste a tab-separated file into it. You'll get a dialog that looks
like the attached screenshot. Note the garbled fonts in the upper left
corner.

$ localc --help
LibreOffice 5.1.2.2 10m0(Build:2)

$ lsb_release -rd
Description:Ubuntu Xenial Xerus (development branch)
Release:16.04

$ apt-cache policy libreoffice-calc 
libreoffice-calc:
  Installed: 1:5.1.2-0ubuntu1
  Candidate: 1:5.1.2-0ubuntu1
  Version table:
 *** 1:5.1.2-0ubuntu1 500
500 http://mirror.htnshost.com/ubuntu xenial/main amd64 Packages
100 /var/lib/dpkg/status

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

** Attachment added: "screenshot of dialog with garbled fonts"
   
https://bugs.launchpad.net/bugs/1569566/+attachment/4634757/+files/Screenshot%20from%202016-04-12%2013-49-22.png

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

Title:
  Missing / garbled fonts in LibreOffice Calc

Status in libreoffice package in Ubuntu:
  New

Bug description:
  Ubuntu 16.04 beta, GNOME desktop. To reproduce, open LibreOffice Calc
  and paste a tab-separated file into it. You'll get a dialog that looks
  like the attached screenshot. Note the garbled fonts in the upper left
  corner.

  $ localc --help
  LibreOffice 5.1.2.2 10m0(Build:2)

  $ lsb_release -rd
  Description:  Ubuntu Xenial Xerus (development branch)
  Release:  16.04

  $ apt-cache policy libreoffice-calc 
  libreoffice-calc:
Installed: 1:5.1.2-0ubuntu1
Candidate: 1:5.1.2-0ubuntu1
Version table:
   *** 1:5.1.2-0ubuntu1 500
  500 http://mirror.htnshost.com/ubuntu xenial/main amd64 Packages
  100 /var/lib/dpkg/status

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

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

[Desktop-packages] [Bug 1569566] Re: Missing / garbled fonts in LibreOffice Calc

[M. Edward (Ed) Borasky]

More garbled fonts - this one shows up when I open a spreadsheet that
wants to update external links.

** Attachment added: "Screenshot from 2016-04-12 13-58-50.png"
   
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1569566/+attachment/4634758/+files/Screenshot%20from%202016-04-12%2013-58-50.png

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

Title:
  Missing / garbled fonts in LibreOffice Calc

Status in libreoffice package in Ubuntu:
  New

Bug description:
  Ubuntu 16.04 beta, GNOME desktop. To reproduce, open LibreOffice Calc
  and paste a tab-separated file into it. You'll get a dialog that looks
  like the attached screenshot. Note the garbled fonts in the upper left
  corner.

  $ localc --help
  LibreOffice 5.1.2.2 10m0(Build:2)

  $ lsb_release -rd
  Description:  Ubuntu Xenial Xerus (development branch)
  Release:  16.04

  $ apt-cache policy libreoffice-calc 
  libreoffice-calc:
Installed: 1:5.1.2-0ubuntu1
Candidate: 1:5.1.2-0ubuntu1
Version table:
   *** 1:5.1.2-0ubuntu1 500
  500 http://mirror.htnshost.com/ubuntu xenial/main amd64 Packages
  100 /var/lib/dpkg/status

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

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

[Desktop-packages] [Bug 1566050] [NEW] soffice.bin crashed with SIGSEGV in Menu::~Menu()

[M. Edward (Ed) Borasky]

Public bug reported:

I'm not sure what happened - I've been downloading CSV files in Firefox
and opening them in LibreOffice. I wasn't actively interacting with
LibreOffice when it crashed.

ProblemType: Crash
DistroRelease: Ubuntu 16.04
Package: libreoffice-core 1:5.1.1-0ubuntu3
ProcVersionSignature: Ubuntu 4.4.0-16.32-generic 4.4.6
Uname: Linux 4.4.0-16-generic x86_64
ApportVersion: 2.20.1-0ubuntu1
Architecture: amd64
CurrentDesktop: GNOME
Date: Mon Apr  4 15:57:52 2016
ExecutablePath: /usr/lib/libreoffice/program/soffice.bin
InstallationDate: Installed on 2016-04-03 (1 days ago)
InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Beta amd64 
(20160323.1)
ProcCmdline: /usr/lib/libreoffice/program/soffice.bin --calc 
file:///tmp/mozilla_znmeb0/DKSalaries-1.csv --splash-pipe=5
ProcEnviron:
 PATH=(custom, user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
 LD_LIBRARY_PATH=
SegvAnalysis:
 Segfault happened at: 0x299c100:   push   %rax
 PC (0x0299c100) in non-executable VMA region: 0x016e7000-0x02c4d000 rw-p [heap]
 source "%rax" ok
 destination "(%rsp)" (0x7fffed7e99f0) ok
SegvReason: executing writable VMA [heap]
Signal: 11
SourcePackage: libreoffice
StacktraceTop:
 ?? ()
 ?? () from /usr/lib/libreoffice/program/libmergedlo.so
 ?? () from /usr/lib/libreoffice/program/libmergedlo.so
 Menu::~Menu() () from /usr/lib/libreoffice/program/libmergedlo.so
 ScCsvGrid::~ScCsvGrid() () from 
/usr/lib/libreoffice/program/../program/libsclo.so
Title: soffice.bin crashed with SIGSEGV in Menu::~Menu()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip docker libvirtd lpadmin plugdev sambashare sudo

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


** Tags: amd64 apport-crash need-amd64-retrace xenial

** Information type changed from Private to Public

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

Title:
  soffice.bin crashed with SIGSEGV in Menu::~Menu()

Status in libreoffice package in Ubuntu:
  New

Bug description:
  I'm not sure what happened - I've been downloading CSV files in
  Firefox and opening them in LibreOffice. I wasn't actively interacting
  with LibreOffice when it crashed.

  ProblemType: Crash
  DistroRelease: Ubuntu 16.04
  Package: libreoffice-core 1:5.1.1-0ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-16.32-generic 4.4.6
  Uname: Linux 4.4.0-16-generic x86_64
  ApportVersion: 2.20.1-0ubuntu1
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Mon Apr  4 15:57:52 2016
  ExecutablePath: /usr/lib/libreoffice/program/soffice.bin
  InstallationDate: Installed on 2016-04-03 (1 days ago)
  InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Beta amd64 
(20160323.1)
  ProcCmdline: /usr/lib/libreoffice/program/soffice.bin --calc 
file:///tmp/mozilla_znmeb0/DKSalaries-1.csv --splash-pipe=5
  ProcEnviron:
   PATH=(custom, user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
   LD_LIBRARY_PATH=
  SegvAnalysis:
   Segfault happened at: 0x299c100: push   %rax
   PC (0x0299c100) in non-executable VMA region: 0x016e7000-0x02c4d000 rw-p 
[heap]
   source "%rax" ok
   destination "(%rsp)" (0x7fffed7e99f0) ok
  SegvReason: executing writable VMA [heap]
  Signal: 11
  SourcePackage: libreoffice
  StacktraceTop:
   ?? ()
   ?? () from /usr/lib/libreoffice/program/libmergedlo.so
   ?? () from /usr/lib/libreoffice/program/libmergedlo.so
   Menu::~Menu() () from /usr/lib/libreoffice/program/libmergedlo.so
   ScCsvGrid::~ScCsvGrid() () from 
/usr/lib/libreoffice/program/../program/libsclo.so
  Title: soffice.bin crashed with SIGSEGV in Menu::~Menu()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip docker libvirtd lpadmin plugdev sambashare sudo

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

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

[Desktop-packages] [Bug 1551212] [NEW] gvfs google integration

[Edward Starscream]

Public bug reported:

I need to do "gvfs-mount google-drive://addr...@gmail.com/", not
currently part of the package.

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


** Tags: xenial

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

Title:
  gvfs google integration

Status in gvfs package in Ubuntu:
  New

Bug description:
  I need to do "gvfs-mount google-drive://addr...@gmail.com/", not
  currently part of the package.

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

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

[Desktop-packages] [Bug 1521136] Re: NetworkManager segfaults on connect

[Edward Z. Yang]

Confirmed downgrading fixes the problem.

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

Title:
  NetworkManager segfaults on connect

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  Upon connecting, NetworkManager from -updates is segfaulting:

  [  139.520739] NetworkManager[15884]: segfault at 0 ip
  00497ad7 sp 7fff77195d00 error 4 in
  NetworkManager[40+1bf000]

  
  Nov 30 10:31:23 arbella NetworkManager[16259]:   keyfile: add 
connection in-memory (c4b6e184-67e3-4a12-8dd3-79ec7ef650e0,"enx803f5d087a34")
  Nov 30 10:31:23 arbella NetworkManager[16259]:   (enx803f5d087a34): 
device state change: unmanaged -> unavailable (reason 'connection-assumed') [10 
20 41]
  Nov 30 10:31:23 arbella NetworkManager[16259]:   (enx803f5d087a34): 
device state change: unavailable -> disconnected (reason 'connection-assumed') 
[20 30 41]
  Nov 30 10:31:23 arbella NetworkManager[16259]:   (enx803f5d087a34): 
Activation: starting connection 'enx803f5d087a34' 
(c4b6e184-67e3-4a12-8dd3-79ec7ef650e0)
  Nov 30 10:31:23 arbella NetworkManager[16259]: nm_device_get_device_type: 
assertion 'NM_IS_DEVICE (self)' failed
  Nov 30 10:31:23 arbella NetworkManager[16259]:   (lo): link connected
  Nov 30 10:31:23 arbella NetworkManager[16259]:   (lo): new Generic 
device (carrier: ON, driver: 'unknown', ifindex: 1)
  Nov 30 10:31:23 arbella NetworkManager[16259]:   (wlp2s0): using 
nl80211 for WiFi device control
  Nov 30 10:31:23 arbella NetworkManager[16259]:   (wlp2s0): driver 
supports Access Point (AP) mode
  Nov 30 10:31:23 arbella NetworkManager[16259]:   (wlp2s0): new 802.11 
WiFi device (carrier: UNKNOWN, driver: 'ath10k_pci', ifindex: 3)
  Nov 30 10:31:23 arbella NetworkManager[16259]:   (wlp2s0): device state 
change: unmanaged -> unavailable (reason 'managed') [10 20 2]
  Nov 30 10:31:23 arbella kernel: [  140.168048] IPv6: ADDRCONF(NETDEV_UP): 
wlp2s0: link is not ready
  Nov 30 10:31:23 arbella NetworkManager[16259]:   urfkill disappeared 
from the bus
  Nov 30 10:31:23 arbella NetworkManager[16259]:   use BlueZ version 5
  Nov 30 10:31:23 arbella NetworkManager[16259]:   wpa_supplicant running
  Nov 30 10:31:23 arbella NetworkManager[16259]:   (wlp2s0): supplicant 
interface state: starting -> ready
  Nov 30 10:31:23 arbella NetworkManager[16259]:   (lxcbr0): device state 
change: disconnected -> prepare (reason 'none') [30 40 0]
  Nov 30 10:31:23 arbella NetworkManager[16259]:   (enx803f5d087a34): 
device state change: disconnected -> prepare (reason 'none') [30 40 0]
  Nov 30 10:31:23 arbella NetworkManager[16259]:   Policy set 
'enx803f5d087a34' (enx803f5d087a34) as default for IPv4 routing and DNS.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: Network-Manager 1.0.4-0ubuntu5
  ProcVersionSignature: Ubuntu 4.2.0-18.22-generic 4.2.3
  Uname: Linux 4.2.0-18-generic x86_64
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Mon Nov 30 10:39:36 2015
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2015-11-21 (9 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  IpRoute:
   default via 10.20.64.1 dev wlp2s0  proto static  metric 600 
   10.0.3.0/24 dev lxcbr0  proto kernel  scope link  src 10.0.3.1 
   10.20.64.0/21 dev wlp2s0  proto kernel  scope link  src 10.20.66.104  metric 
600 
   169.254.0.0/16 dev lxcbr0  scope link  metric 1000
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
   WimaxEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-dev:
   DEVICE  TYPE  STATE  DBUS-PATH  
CONNECTION  CON-UUID  CON-PATH  
 
   lxcbr0  bridgeconnected  /org/freedesktop/NetworkManager/Devices/3  
lxcbr0  ac91e68a-905e-4cd2-a937-11b8c5f4bed0  
/org/freedesktop/NetworkManager/ActiveConnection/1 
   wlp2s0  wifi  connected  /org/freedesktop/NetworkManager/Devices/2  
Canonical-2.4GHz-g  4eb6b0d8-a49e-4e11-aff1-18ce3f158523  
/org/freedesktop/NetworkManager/ActiveConnection/2 
   lo  loopback  unmanaged  /org/freedesktop/NetworkManager/Devices/1  --   
   ----
  nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 
2: Error: Object 'nm' is unknown, try 'nmcli help'.

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

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

Re: [Desktop-packages] [Bug 1513168] Re: rythymbox screen goes grey and freezes after connecting IPAD

[edward stavin]

Hi.  I looked at the specific request you made to obtain a backtrace but
the instructions are too complicated to figure out.  Is there some sort of
executable file or one click program to run?

What I can tell you though is that after much a do I figured out that the
problem is most likely caused by the lack of up to date support for apple
IOS products.  IOS 9 requires the current version of
http://www.libimobiledevice.org/downloads/libimobiledevice-1.2.0.tar.bz2 in
ubuntu from www.libimobiledevice.org

Of course this is not the end of it as the above generates dependencies
like usbmuxd and a few others that are also out of date.  I think it said
it needs version 1.0.9 but ubuntu only has 1.0.8

Is there a way to get someone to update this in the near future?  I get a
similar problem with Banshee when I connect the IPAD with IOS9.1 ---
Nothing happens even though the software claims its trying to update the
tablet... so this update would fix both issues I am sure.

Hope I helped

Edward

On Mon, Nov 30, 2015 at 7:39 AM, Sebastien Bacher <seb...@ubuntu.com>
wrote:

> Thank you for taking the time to report this bug and helping to make
> Ubuntu better. Please try to obtain a backtrace following the
> instructions at http://wiki.ubuntu.com/DebuggingProgramCrash and upload
> the backtrace (as an attachment) to the bug report. This will greatly
> help us in tracking down your problem.
>
> ** Changed in: rhythmbox (Ubuntu)
>Importance: Undecided => Low
>
> ** Changed in: rhythmbox (Ubuntu)
>Status: New => Incomplete
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1513168
>
> Title:
>   rythymbox screen goes grey and freezes after connecting IPAD
>
> Status in rhythmbox package in Ubuntu:
>   Incomplete
>
> Bug description:
>   Screen grey and frozen.  Able to stop application from task bar
>   sometimes, other times I have to reboot the system.
>
>   ProblemType: Bug
>   DistroRelease: Ubuntu 14.04
>   Package: rhythmbox 3.0.2-0ubuntu2
>   ProcVersionSignature: Ubuntu 3.19.0-31.36~14.04.1-generic 3.19.8-ckt7
>   Uname: Linux 3.19.0-31-generic i686
>   ApportVersion: 2.14.1-0ubuntu3.18
>   Architecture: i386
>   CurrentDesktop: Unity
>   Date: Wed Nov  4 13:08:32 2015
>   ExecutablePath: /usr/bin/rhythmbox
>   InstallationDate: Installed on 2015-11-04 (0 days ago)
>   InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta i386
> (20150805)
>   ProcEnviron:
>XDG_RUNTIME_DIR=
>SHELL=/bin/bash
>LANGUAGE=en_CA:en
>PATH=(custom, no user)
>LANG=en_CA.UTF-8
>   SourcePackage: rhythmbox
>   UpgradeStatus: No upgrade log present (probably fresh install)
>
> To manage notifications about this bug go to:
>
> https://bugs.launchpad.net/ubuntu/+source/rhythmbox/+bug/1513168/+subscriptions
>

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

Title:
  rythymbox screen goes grey and freezes after connecting IPAD

Status in rhythmbox package in Ubuntu:
  Incomplete

Bug description:
  Screen grey and frozen.  Able to stop application from task bar
  sometimes, other times I have to reboot the system.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: rhythmbox 3.0.2-0ubuntu2
  ProcVersionSignature: Ubuntu 3.19.0-31.36~14.04.1-generic 3.19.8-ckt7
  Uname: Linux 3.19.0-31-generic i686
  ApportVersion: 2.14.1-0ubuntu3.18
  Architecture: i386
  CurrentDesktop: Unity
  Date: Wed Nov  4 13:08:32 2015
  ExecutablePath: /usr/bin/rhythmbox
  InstallationDate: Installed on 2015-11-04 (0 days ago)
  InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta i386 (20150805)
  ProcEnviron:
   XDG_RUNTIME_DIR=
   SHELL=/bin/bash
   LANGUAGE=en_CA:en
   PATH=(custom, no user)
   LANG=en_CA.UTF-8
  SourcePackage: rhythmbox
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 458334] Re: Fails repeatably with "DBus error org.gtk.Private.RemoteVolumeMonitor.NotFound: The given volume was not found"

[Edward Garson]

I experienced a very similar error, but not exactly the same, when
trying to format a 4G USB 2.0 device. Matt's suggested workaround (near
the very top of this report, using dd) worked after a couple of tries. I
was getting "DBus.Python.GLib.Error" when trying to format, with the
same consequences as described in this report.

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

Title:
  Fails repeatably with "DBus error
  org.gtk.Private.RemoteVolumeMonitor.NotFound: The given volume was not
  found"

Status in usb-creator:
  New
Status in nautilus package in Ubuntu:
  Invalid
Status in nautilus package in CentOS:
  Invalid

Bug description:
  Binary package hint: usb-creator

  I'm trying to reformat a 4GB USB stick using usb-creator to put
  karmic-moblin-remix-i386.iso on it.

  1. Run usb-creator-gtk
  2. usb-creator shows /dev/sdb with exclamation mark, /dev/sdb with storage 
icon
  3. I select /dev/sdb and click "Format"
  4. I get a dialog with "Unable to mount 4.0 GB Filesystem" "DBus error 
org.gtk.Private.RemoteVolumeMonitor.NotFound: The given volume was not found"
  5. I dismiss the dialog
  6. I try again to format, instead using /dev/sdb1
  7. I get an identical error
  8. /dev/sdb1 disappears from the list

  ProblemType: Bug
  Architecture: amd64
  Date: Thu Oct 22 17:49:43 2009
  DistroRelease: Ubuntu 9.10
  Package: usb-creator 0.2.11
  PackageArchitecture: all
  ProcEnviron:
   LC_COLLATE=C
   PATH=(custom, user)
   LANG=en_US.UTF-8
   SHELL=/bin/zsh
  ProcVersionSignature: Ubuntu 2.6.31-14.48-generic
  SourcePackage: usb-creator
  Uname: Linux 2.6.31-14-generic x86_64

To manage notifications about this bug go to:
https://bugs.launchpad.net/usb-creator/+bug/458334/+subscriptions

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

[Desktop-packages] [Bug 1382774] Re: Postgresql installation for MAAS fails on locales missing language packs

[Edward Hope-Morley]

** Tags removed: cts
** Tags added: tests

** Tags removed: tests
** Tags added: sts

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

Title:
  Postgresql installation for MAAS fails on locales missing language
  packs

Status in MAAS:
  Triaged
Status in dbconfig-common package in Ubuntu:
  Invalid
Status in maas package in Ubuntu:
  Confirmed
Status in postgresql-common package in Ubuntu:
  Incomplete

Bug description:
  Ubuntu 14.04 with all updates as of time of the writing.

  MAAS - 1.5.4+bzr2294-0ubuntu1.1

  # apt-get install maas
  ...
  Setting up maas-dns (1.5.4+bzr2294-0ubuntu1.1) ...
   * Stopping domain name service... bind9  

   waiting for pid 29580 to 
die


[ OK ]
   * Starting domain name service... bind9  

[ OK ] 
  Setting up maas-region-controller (1.5.4+bzr2294-0ubuntu1.1) ...
  locale: Cannot set LC_ALL to default locale: No such file or directory
  Considering dependency proxy for proxy_http:
  Module proxy already enabled
  Module proxy_http already enabled
  Module expires already enabled
  Module wsgi already enabled
  rsyslog stop/waiting
  rsyslog start/running, process 32763
  squid-deb-proxy stop/waiting
  squid-deb-proxy start/running, process 349
   * Restarting message broker rabbitmq-server  

[ OK ] 
  Creating user "maas_longpoll" ...
  ...done.
  Creating vhost "/maas_longpoll" ...
  ...done.
  Setting permissions for user "maas_longpoll" in vhost "/maas_longpoll" ...
  ...done.
  Creating user "maas_workers" ...
  ...done.
  Creating vhost "/maas_workers" ...
  ...done.
  Setting permissions for user "maas_workers" in vhost "/maas_workers" ...
  ...done.
   * No PostgreSQL clusters exist; see "man pg_createcluster"
  dbconfig-common: writing config to 
/etc/dbconfig-common/maas-region-controller.conf

  Creating config file /etc/dbconfig-common/maas-region-controller.conf with 
new version
  unable to connect to postgresql server.
  error encountered creating user:
  psql: could not connect to server: No such file or directory Is the server 
running locally and accepting connections on Unix domain socket 
"/var/run/postgresql/.s.PGSQL.5432"?
  /usr/bin/locale: Cannot set LC_ALL to default locale: No such file or 
directory

  Here's the environment:
  # export
  declare -x HOME="/root"
  declare -x LANG="en_US.UTF-8"
  declare -x LANGUAGE="en_US:en"
  declare -x LC_ADDRESS="hr_HR.UTF-8"
  declare -x LC_IDENTIFICATION="hr_HR.UTF-8"
  declare -x LC_MEASUREMENT="hr_HR.UTF-8"
  declare -x LC_MONETARY="hr_HR.UTF-8"
  declare -x LC_NAME="hr_HR.UTF-8"
  declare -x LC_NUMERIC="hr_HR.UTF-8"
  declare -x LC_PAPER="hr_HR.UTF-8"
  declare -x LC_TELEPHONE="hr_HR.UTF-8"
  declare -x LC_TIME="hr_HR.UTF-8"
  declare -x LESSCLOSE="/usr/bin/lesspipe %s %s"
  declare -x LESSOPEN="| /usr/bin/lesspipe %s"
  declare -x LOGNAME="root"
  declare -x 
LS_COLORS="rs=0:di=01;34:ln=01;36:mh=00:pi=40;33:so=01;35:do=01;35:bd=40;33;01:cd=40;33;01:or=40;31;01:su=37;41:sg=30;43:ca=30;41:tw=30;42:ow=34;42:st=37;44:ex=01;32:*.tar=01;31:*.tgz=01;31:*.arj=01;31:*.taz=01;31:*.lzh=01;31:*.lzma=01;31:*.tlz=01;31:*.txz=01;31:*.zip=01;31:*.z=01;31:*.Z=01;31:*.dz=01;31:*.gz=01;31:*.lz=01;31:*.xz=01;31:*.bz2=01;31:*.bz=01;31:*.tbz=01;31:*.tbz2=01;31:*.tz=01;31:*.deb=01;31:*.rpm=01;31:*.jar=01;31:*.war=01;31:*.ear=01;31:*.sar=01;31:*.rar=01;31:*.ace=01;31:*.zoo=01;31:*.cpio=01;31:*.7z=01;31:*.rz=01;31:*.jpg=01;35:*.jpeg=01;35:*.gif=01;35:*.bmp=01;35:*.pbm=01;35:*.pgm=01;35:*.ppm=01;35:*.tga=01;35:*.xbm=01;35:*.xpm=01;35:*.tif=01;35:*.tiff=01;35:*.png=01;35:*.svg=01;35:*.svgz=01;35:*.mng=01;35:*.pcx=01;35:*.mov=01;35:*.mpg=01;35:*.mpeg=01;35:*.m2v=01;35:*.mkv=01;35:*.webm=01;35:*.ogm=01;35:*.mp4=01;35:*.m4v=01;35:*.mp4v=01;35:*.vob=01;35:*.qt=01;35:*.nuv=01;35:*.wmv=01;35:*.asf=01;35:*.rm=01;35:*.rmvb=01;35:*.flc=01;35:*.avi=01;35:*.fli=0
 
1;35:*.flv=01;35:*.gl=01;35:*.dl=01;35:*.xcf=01;35:*.xwd=01;35:*.yuv=01;35:*.cgm=01;35:*.emf=01;35:*.axv=01;35:*.anx=01;35:*.ogv=01;35:*.ogx=01;35:*.aac=00;36:*.au=00;36:*.flac=00;36:*.mid=00;36:*.midi=00;36:*.mka=00;36:*.mp3=00;36:*.mpc=00;36:*.ogg=00;36:*.ra=00;36:*.wav=00;36:*.axa=00;36:*.oga=00;36:*.spx=00;36:*.xspf=00;36:"
  declare -x 

[Desktop-packages] [Bug 1513168] Re: rythymbox screen goes grey and freezes after connecting IPAD

[edward stavin]

** Description changed:

- Screen grey and frozen.  Unable to stop application or exit.  ONly
- solution is to reboot system.
+ Screen grey and frozen.  Able to stop application from task bar
+ sometimes, other times I have to reboot the system.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: rhythmbox 3.0.2-0ubuntu2
  ProcVersionSignature: Ubuntu 3.19.0-31.36~14.04.1-generic 3.19.8-ckt7
  Uname: Linux 3.19.0-31-generic i686
  ApportVersion: 2.14.1-0ubuntu3.18
  Architecture: i386
  CurrentDesktop: Unity
  Date: Wed Nov  4 13:08:32 2015
  ExecutablePath: /usr/bin/rhythmbox
  InstallationDate: Installed on 2015-11-04 (0 days ago)
  InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta i386 (20150805)
  ProcEnviron:
-  XDG_RUNTIME_DIR=
-  SHELL=/bin/bash
-  LANGUAGE=en_CA:en
-  PATH=(custom, no user)
-  LANG=en_CA.UTF-8
+  XDG_RUNTIME_DIR=
+  SHELL=/bin/bash
+  LANGUAGE=en_CA:en
+  PATH=(custom, no user)
+  LANG=en_CA.UTF-8
  SourcePackage: rhythmbox
  UpgradeStatus: No upgrade log present (probably fresh install)

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

Title:
  rythymbox screen goes grey and freezes after connecting IPAD

Status in rhythmbox package in Ubuntu:
  New

Bug description:
  Screen grey and frozen.  Able to stop application from task bar
  sometimes, other times I have to reboot the system.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: rhythmbox 3.0.2-0ubuntu2
  ProcVersionSignature: Ubuntu 3.19.0-31.36~14.04.1-generic 3.19.8-ckt7
  Uname: Linux 3.19.0-31-generic i686
  ApportVersion: 2.14.1-0ubuntu3.18
  Architecture: i386
  CurrentDesktop: Unity
  Date: Wed Nov  4 13:08:32 2015
  ExecutablePath: /usr/bin/rhythmbox
  InstallationDate: Installed on 2015-11-04 (0 days ago)
  InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta i386 (20150805)
  ProcEnviron:
   XDG_RUNTIME_DIR=
   SHELL=/bin/bash
   LANGUAGE=en_CA:en
   PATH=(custom, no user)
   LANG=en_CA.UTF-8
  SourcePackage: rhythmbox
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1513168] [NEW] rythymbox screen goes grey and freezes after connecting IPAD

[edward stavin]

Public bug reported:

Screen grey and frozen.  Unable to stop application or exit.  ONly
solution is to reboot system.

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: rhythmbox 3.0.2-0ubuntu2
ProcVersionSignature: Ubuntu 3.19.0-31.36~14.04.1-generic 3.19.8-ckt7
Uname: Linux 3.19.0-31-generic i686
ApportVersion: 2.14.1-0ubuntu3.18
Architecture: i386
CurrentDesktop: Unity
Date: Wed Nov  4 13:08:32 2015
ExecutablePath: /usr/bin/rhythmbox
InstallationDate: Installed on 2015-11-04 (0 days ago)
InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta i386 (20150805)
ProcEnviron:
 XDG_RUNTIME_DIR=
 SHELL=/bin/bash
 LANGUAGE=en_CA:en
 PATH=(custom, no user)
 LANG=en_CA.UTF-8
SourcePackage: rhythmbox
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: apport-bug i386 trusty

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

Title:
  rythymbox screen goes grey and freezes after connecting IPAD

Status in rhythmbox package in Ubuntu:
  New

Bug description:
  Screen grey and frozen.  Unable to stop application or exit.  ONly
  solution is to reboot system.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: rhythmbox 3.0.2-0ubuntu2
  ProcVersionSignature: Ubuntu 3.19.0-31.36~14.04.1-generic 3.19.8-ckt7
  Uname: Linux 3.19.0-31-generic i686
  ApportVersion: 2.14.1-0ubuntu3.18
  Architecture: i386
  CurrentDesktop: Unity
  Date: Wed Nov  4 13:08:32 2015
  ExecutablePath: /usr/bin/rhythmbox
  InstallationDate: Installed on 2015-11-04 (0 days ago)
  InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta i386 (20150805)
  ProcEnviron:
   XDG_RUNTIME_DIR=
   SHELL=/bin/bash
   LANGUAGE=en_CA:en
   PATH=(custom, no user)
   LANG=en_CA.UTF-8
  SourcePackage: rhythmbox
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1029209] Re: tidy doesn't support html5 syntax

[Edward Vielmetti]

There is a new version of Tidy (5.0.0) which has been released and which
is largely backwards compatible with the 2009 Tidy that ships right now.

See https://github.com/htacg/tidy-html5 for the source repository, and
this open issue

https://github.com/htacg/tidy-html5/issues/252

for the packaging issue. There is a desire on the part of the maintainer
to have distributions pick up and offer this current release.

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

Title:
  tidy doesn't  support html5 syntax

Status in tidy package in Ubuntu:
  Confirmed

Bug description:
  Upstream (W3C?) hasn't updated the code in years, so it doesn't
  recognize html5  declaration, and throws warnings or errors
  on valid html5 elements.

  Minor bug, maybe wishlist.

  ProblemType: Bug
  DistroRelease: Ubuntu 10.04
  Package: libtidy-0.99-0 20091223cvs-1
  Uname: Linux 2.6.32-042stab057.1 x86_64
  Architecture: amd64
  Date: Wed Jul 25 21:42:34 2012
  ProcEnviron:
   LANG=en_CA.UTF-8
   SHELL=/bin/bash
  SourcePackage: tidy

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

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

[Desktop-packages] [Bug 589574] Re: libtidy creates invalid tags

[Edward Vielmetti]

This bug is fixed in tidy-html5 v5.0.0, as noted here

https://github.com/htacg/tidy-html5/issues/256

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

Title:
  libtidy creates invalid tags

Status in tidy package in Ubuntu:
  New

Bug description:
  Binary package hint: tidy

  The following HTML causes libtidy to produce invalid tags:

  http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd;>
  
   BC
  

  The result of running this through the tidy command line is:
  $ tidy -w0 t.html

  http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd;>
  http://www.w3.org/1999/xhtml;>
  
  
  
  
  
  B<�>��>C��>
  
  

  The invalid tags change on each run, looking like use after free kind
  of problem.

  This is running on Ubuntu 10.04 LTS, updated recently. 
  Linux 2.6.32-22-generic #35-Ubuntu SMP Tue Jun 1 14:18:25 UTC 2010 x86_64 
GNU/Linux
  /etc/tidy.conf only contains comments.
  there are no other tidy configuration files

  Using LD_PRELOAD I tested the libtidy from earlier distributions;
  only the version from libtidy-0.99-0_20051018-1_amd64.deb does not show this 
effect.

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

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

[Desktop-packages] [Bug 1224732] Re: Custom keyboard shortcuts don't work

[Edward Falk]

I just accepted an auto-update on my Ubuntu 14.04 system and all
application shortcuts stopped working. I can't make them work again.

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

Title:
  Custom keyboard shortcuts don't work

Status in gnome-control-center:
  New
Status in libxfce4ui:
  New
Status in gnome-control-center package in Ubuntu:
  Confirmed
Status in libxkbcommon package in Ubuntu:
  Confirmed

Bug description:
  Just noticed that adding custom keyboard shortcuts does not have any
  effect. If, for example, I add a custom keyboard shortcut for Evince
  and set it to Ctrl+Alt+E, pressing this key combination won't launch
  Evince.

  * What happens *
When I add a custom keyboard shortcut (and bind it to some key 
combination), the shortcut does not run the associated command.

  * What I expect *
After adding the custom shortcut, I expect that the shortcut launches the 
associated command.

  Description:  Ubuntu Saucy Salamander (development branch)
  Release:  13.10

  gnome-control-center:
Installed: 1:3.6.3-0ubuntu36
Candidate: 1:3.6.3-0ubuntu36
Version table:
   *** 1:3.6.3-0ubuntu36 0
  500 http://us.archive.ubuntu.com/ubuntu/ saucy/main i386 Packages
  100 /var/lib/dpkg/status

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: gnome-control-center 1:3.6.3-0ubuntu36
  ProcVersionSignature: Ubuntu 3.11.0-7.13-generic 3.11.0
  Uname: Linux 3.11.0-7-generic i686
  ApportVersion: 2.12.1-0ubuntu4
  Architecture: i386
  Date: Thu Sep 12 19:21:56 2013
  InstallationDate: Installed on 2013-08-31 (12 days ago)
  InstallationMedia: Ubuntu 13.10 Saucy Salamander - Alpha i386 (20130830)
  MarkForUpload: True
  SourcePackage: gnome-control-center
  UpgradeStatus: No upgrade log present (probably fresh install)
  usr_lib_gnome-control-center:
   activity-log-manager  0.9.7-0ubuntu4
   deja-dup  27.3.1-0ubuntu1
   gnome-control-center-datetime 13.10.0+13.10.20130903-0ubuntu1
   gnome-control-center-signon   0.1.7~+13.10.20130724.1-0ubuntu1
   gnome-control-center-unity1.3daily13.06.14.1-0ubuntu1

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

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

[Desktop-packages] [Bug 1482938] [NEW] im-config gcin qt5

[Edward Liu]

Public bug reported:

missing

QT_IM_MODULE=gcin

in /usr/share/im-config/data/26_gcin.rc

QT5 needs this.

ProblemType: Bug
DistroRelease: Ubuntu 15.04
Package: im-config 0.29-1ubuntu2 [modified: usr/share/im-config/data/26_gcin.rc]
ProcVersionSignature: Ubuntu 3.19.0-25.26-generic 3.19.8-ckt2
Uname: Linux 3.19.0-25-generic x86_64
ApportVersion: 2.17.2-0ubuntu1.1
Architecture: amd64
CurrentDesktop: XFCE
Date: Sun Aug  9 09:01:10 2015
InstallationDate: Installed on 2015-04-26 (104 days ago)
InstallationMedia: Ubuntu 15.04 Vivid Vervet - Release amd64 (20150422)
PackageArchitecture: all
SourcePackage: im-config
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: im-config (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug vivid

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

Title:
  im-config gcin qt5

Status in im-config package in Ubuntu:
  New

Bug description:
  missing

  QT_IM_MODULE=gcin

  in /usr/share/im-config/data/26_gcin.rc

  QT5 needs this.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: im-config 0.29-1ubuntu2 [modified: 
usr/share/im-config/data/26_gcin.rc]
  ProcVersionSignature: Ubuntu 3.19.0-25.26-generic 3.19.8-ckt2
  Uname: Linux 3.19.0-25-generic x86_64
  ApportVersion: 2.17.2-0ubuntu1.1
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Sun Aug  9 09:01:10 2015
  InstallationDate: Installed on 2015-04-26 (104 days ago)
  InstallationMedia: Ubuntu 15.04 Vivid Vervet - Release amd64 (20150422)
  PackageArchitecture: all
  SourcePackage: im-config
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/im-config/+bug/1482938/+subscriptions

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

[Desktop-packages] [Bug 1475802] [NEW] system-config-printer unusably slow

[Edward Z. Yang]

Public bug reported:

When I try to load system-config-printer, it takes tens of seconds to
load. Any interactions take many more seconds, to the point that this
utility is unusable.

When I strace initial loading, here is what I get:

socket(PF_INET6, SOCK_STREAM, IPPROTO_IP) = 16
setsockopt(16, SOL_SOCKET, SO_REUSEADDR, [1], 4) = 0
setsockopt(16, SOL_SOCKET, SO_REUSEPORT, [1], 4) = 0
setsockopt(16, SOL_TCP, TCP_NODELAY, [1], 4) = 0
fcntl(16, F_SETFD, FD_CLOEXEC)  = 0
fcntl(16, F_GETFL)  = 0x2 (flags O_RDWR)
fcntl(16, F_SETFL, O_RDWR|O_NONBLOCK)   = 0
connect(16, {sa_family=AF_INET6, sin6_port=htons(631), inet_pton(AF_INET6, 
::1, sin6_addr), sin6_flowinfo=0, sin6_scope_id=0}, 28) = -1 EINPROGRESS 
(Operation now in progress)
fcntl(16, F_SETFL, O_RDWR)  = 0
poll([{fd=16, events=POLLIN|POLLOUT}], 1, 250) = 0 (Timeout)
poll([{fd=16, events=POLLIN|POLLOUT}], 1, 250) = 0 (Timeout)
poll([{fd=16, events=POLLIN|POLLOUT}], 1, 250) = 0 (Timeout)
poll([{fd=16, events=POLLIN|POLLOUT}], 1, 250) = 0 (Timeout)
...

IPv6 is disabled on my system:

ezyang@sabre:~$ cat /proc/sys/net/ipv6/conf/all/disable_ipv6
1

This pattern seems to repeat whenever the interface hangs.

ProblemType: Bug
DistroRelease: Ubuntu 15.04
Package: system-config-printer-gnome 1.5.6+20150318-0ubuntu2.1
ProcVersionSignature: Ubuntu 3.19.0-21.21-generic 3.19.8
Uname: Linux 3.19.0-21-generic x86_64
ApportVersion: 2.17.2-0ubuntu1.1
Architecture: amd64
Date: Fri Jul 17 15:05:17 2015
EcryptfsInUse: Yes
InstallationDate: Installed on 2013-11-21 (603 days ago)
InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 (20131016.1)
MachineType: LENOVO 7762K3U
PackageArchitecture: all
Papersize: letter
PccardctlIdent:
 Socket 0:
   no product info available
PccardctlStatus:
 Socket 0:
   no card
PpdFiles:
 Error: command ['fgrep', '-H', '*NickName', 
'/etc/cups/ppd/mitprint-color.ppd', '/etc/cups/ppd/mitprint.ppd'] failed with 
exit code 2: grep: /etc/cups/ppd/mitprint-color.ppd: Permission denied
 grep: /etc/cups/ppd/mitprint.ppd: Permission denied
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.19.0-21-generic 
root=/dev/mapper/hostname-root ro quiet splash vt.handoff=7
SourcePackage: system-config-printer
UpgradeStatus: Upgraded to vivid on 2015-05-29 (49 days ago)
dmi.bios.date: 03/22/2011
dmi.bios.vendor: LENOVO
dmi.bios.version: 7SET39WW (1.25 )
dmi.board.name: 7762K3U
dmi.board.vendor: LENOVO
dmi.board.version: Not Available
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Not Available
dmi.modalias: 
dmi:bvnLENOVO:bvr7SET39WW(1.25):bd03/22/2011:svnLENOVO:pn7762K3U:pvrThinkPadX61Tablet:rvnLENOVO:rn7762K3U:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
dmi.product.name: 7762K3U
dmi.product.version: ThinkPad X61 Tablet
dmi.sys.vendor: LENOVO

** Affects: system-config-printer (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug vivid

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

Title:
  system-config-printer unusably slow

Status in system-config-printer package in Ubuntu:
  New

Bug description:
  When I try to load system-config-printer, it takes tens of seconds to
  load. Any interactions take many more seconds, to the point that this
  utility is unusable.

  When I strace initial loading, here is what I get:

  socket(PF_INET6, SOCK_STREAM, IPPROTO_IP) = 16
  setsockopt(16, SOL_SOCKET, SO_REUSEADDR, [1], 4) = 0
  setsockopt(16, SOL_SOCKET, SO_REUSEPORT, [1], 4) = 0
  setsockopt(16, SOL_TCP, TCP_NODELAY, [1], 4) = 0
  fcntl(16, F_SETFD, FD_CLOEXEC)  = 0
  fcntl(16, F_GETFL)  = 0x2 (flags O_RDWR)
  fcntl(16, F_SETFL, O_RDWR|O_NONBLOCK)   = 0
  connect(16, {sa_family=AF_INET6, sin6_port=htons(631), inet_pton(AF_INET6, 
::1, sin6_addr), sin6_flowinfo=0, sin6_scope_id=0}, 28) = -1 EINPROGRESS 
(Operation now in progress)
  fcntl(16, F_SETFL, O_RDWR)  = 0
  poll([{fd=16, events=POLLIN|POLLOUT}], 1, 250) = 0 (Timeout)
  poll([{fd=16, events=POLLIN|POLLOUT}], 1, 250) = 0 (Timeout)
  poll([{fd=16, events=POLLIN|POLLOUT}], 1, 250) = 0 (Timeout)
  poll([{fd=16, events=POLLIN|POLLOUT}], 1, 250) = 0 (Timeout)
  ...

  IPv6 is disabled on my system:

  ezyang@sabre:~$ cat /proc/sys/net/ipv6/conf/all/disable_ipv6
  1

  This pattern seems to repeat whenever the interface hangs.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: system-config-printer-gnome 1.5.6+20150318-0ubuntu2.1
  ProcVersionSignature: Ubuntu 3.19.0-21.21-generic 3.19.8
  Uname: Linux 3.19.0-21-generic x86_64
  ApportVersion: 2.17.2-0ubuntu1.1
  Architecture: amd64
  Date: Fri Jul 17 15:05:17 2015
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2013-11-21 (603 days ago)
  InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 
(20131016.1)
  MachineType: 

[Desktop-packages] [Bug 936840] Re: ctrl key now known as primary which breaks keyboard shortcuts

[Edward Falk]

Still being stored as Primary in my Ubuntu/xfce4 14.04 system.

Seriously, what motivated some software engineer to rename ctrl as
Primary? What problem did this solve that couldn't be solved some
other way?

This is what should be done now: Track down all software that writes
Primary to any config file and change it to write ctrl (or
ctrl_L or ctrl_R if you need). Also make sure that all the software
understands Primary and converts it to ctrl when it reads a config
file.

Nonsense like this is why Linux is having so much trouble being adopted
for the general desktop. Every single damn release breaks things. I
can't stand upgrading because I know I need to fix fifty things when I
do.

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

Title:
  ctrl key now known as primary which breaks keyboard shortcuts

Status in Compiz:
  Fix Released
Status in Compiz 0.9.8 series:
  Won't Fix
Status in Compiz Configuration Library:
  Fix Committed
Status in Unity Distro Priority:
  Fix Committed
Status in compiz package in Ubuntu:
  Fix Released
Status in libcompizconfig package in Ubuntu:
  Confirmed

Bug description:
  Previously we used to call the control key Control but this has now
  been changed in GNOME so when the control key is pressed primary is
  returned. In compiz we set keyboard shortcuts as (for example)
  ControlAltLeft.

  When changing settings in gnome-control-center (for example) we will
  set primary  but in compiz we're looking for control which breaks
  keyboard actions.

  This also affects CCSM for setting keyboard shortcuts.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: compiz-core 1:0.9.7.0~bzr2995-0ubuntu4
  ProcVersionSignature: Ubuntu 3.2.0-16.25-generic 3.2.6
  Uname: Linux 3.2.0-16-generic x86_64
  .tmp.unity.scope.cities: Error: [Errno 21] Is a directory: 
'/tmp/unity-scope-cities'
  .tmp.unity.support.test.0:
   
  ApportVersion: 1.91-0ubuntu1
  Architecture: amd64
  CompizPlugins: 
[core,composite,opengl,decor,mousepoll,vpswitch,regex,animation,snap,expo,move,compiztoolbox,place,grid,imgpng,gnomecompat,wall,ezoom,workarounds,resize,fade,unitymtgrabhandles,scale,session,unityshell]
  CompositorRunning: compiz
  Date: Mon Feb 20 09:19:51 2012
  DistUpgraded: Fresh install
  DistroCodename: precise
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox, 4.1.8, 3.2.0-15-generic, x86_64: installed
   virtualbox, 4.1.8, 3.2.0-16-generic, x86_64: installed
  EcryptfsInUse: Yes
  GraphicsCard:
   Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0126] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: Lenovo Device [17aa:21da]
  InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Alpha amd64 
(20120203)
  MachineType: LENOVO 4287CTO
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, user)
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-16-generic 
root=UUID=86ea7114-6b69-4161-b91c-44ccb7fcfd67 ro quiet splash vt.handoff=7
  SourcePackage: compiz
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/01/2011
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 8DET56WW (1.26 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 4287CTO
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Available
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvr8DET56WW(1.26):bd12/01/2011:svnLENOVO:pn4287CTO:pvrThinkPadX220:rvnLENOVO:rn4287CTO:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 4287CTO
  dmi.product.version: ThinkPad X220
  dmi.sys.vendor: LENOVO
  version.compiz: compiz 1:0.9.7.0~bzr2995-0ubuntu4
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.30-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 8.0~rc2-0ubuntu5
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 8.0~rc2-0ubuntu5
  version.xserver-xorg-core: xserver-xorg-core 2:1.11.4-0ubuntu3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 
1:2.6.99.901+git20120126-0ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 
1:6.14.99~git20111219.aacbd629-0ubuntu2
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.17.0-1ubuntu4
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:0.0.16+git20111201+b5534a1-1build2

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

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

[Desktop-packages] [Bug 1471040] Re: xserver broken on Toshiba AC100 since 1.15.1-0ubuntu2

[Edward Batraev]

Now I just do not update Xorg.

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

Title:
  xserver broken on Toshiba AC100 since 1.15.1-0ubuntu2

Status in xorg-server package in Ubuntu:
  Confirmed

Bug description:
  xserver is broken on Toshiba AC100 (armhf) since 1.15.1-0ubuntu2
  https://launchpad.net/ubuntu/utopic/armhf/xserver-xorg-core/2:1.15.1-0ubuntu2

  /var/log/Xorg.0.log from xserver-xorg 1.16 attached

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

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

[Desktop-packages] [Bug 1459687] [NEW] package install-info 5.2.0.dfsg.1-2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 255

[Edward Garson]

Public bug reported:

Failed during a vanilla update.

ProblemType: Package
DistroRelease: Ubuntu 14.04
Package: install-info 5.2.0.dfsg.1-2
ProcVersionSignature: Ubuntu 3.16.0-38.52~14.04.1-generic 3.16.7-ckt10
Uname: Linux 3.16.0-38-generic x86_64
ApportVersion: 2.14.1-0ubuntu3.11
Architecture: amd64
Date: Thu May 28 10:04:42 2015
DuplicateSignature: package:install-info:5.2.0.dfsg.1-2:subprocess installed 
post-installation script returned error exit status 255
ErrorMessage: subprocess installed post-installation script returned error exit 
status 255
InstallationDate: Installed on 2015-04-20 (37 days ago)
InstallationMedia: Xubuntu 14.04.2 LTS Trusty Tahr - Release amd64 
(20150218.1)
SourcePackage: texinfo
Title: package install-info 5.2.0.dfsg.1-2 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 255
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-package third-party-packages trusty

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

Title:
  package install-info 5.2.0.dfsg.1-2 failed to install/upgrade:
  subprocess installed post-installation script returned error exit
  status 255

Status in texinfo package in Ubuntu:
  New

Bug description:
  Failed during a vanilla update.

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: install-info 5.2.0.dfsg.1-2
  ProcVersionSignature: Ubuntu 3.16.0-38.52~14.04.1-generic 3.16.7-ckt10
  Uname: Linux 3.16.0-38-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.11
  Architecture: amd64
  Date: Thu May 28 10:04:42 2015
  DuplicateSignature: package:install-info:5.2.0.dfsg.1-2:subprocess installed 
post-installation script returned error exit status 255
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 255
  InstallationDate: Installed on 2015-04-20 (37 days ago)
  InstallationMedia: Xubuntu 14.04.2 LTS Trusty Tahr - Release amd64 
(20150218.1)
  SourcePackage: texinfo
  Title: package install-info 5.2.0.dfsg.1-2 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 255
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1455091] Re: Remeber log in forever keeps forgetting it forever

[edward stavin]

** Bug watch added: GNOME Bug Tracker #750034
   https://bugzilla.gnome.org/show_bug.cgi?id=750034

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

Title:
  Remeber log in forever keeps forgetting it forever

Status in nautilus package in Ubuntu:
  New

Bug description:
  I keep selecting remember my login to my NAS forever, yet every time I
  return to the screen after shutting down my PC it ask me to retype the
  log in details and password.

  My conclusion would be that the remember forever feature does not
  work... it only remembers for the duration of the current session.
  Once I shutdown or reboot the login details vanish and I have to enter
  them all again.

  Hope this helps improve the product.  I can access the NAS by clicking
  on the NAS icon or going through the widows network icons but the
  results are the same both ways.

  Hope this helps improve a great product.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: nautilus 1:3.10.1-0ubuntu9.7
  ProcVersionSignature: Ubuntu 3.13.0-52.86-generic 3.13.11-ckt18
  Uname: Linux 3.13.0-52-generic i686
  ApportVersion: 2.14.1-0ubuntu3.10
  Architecture: i386
  CurrentDesktop: Unity
  Date: Thu May 14 09:15:07 2015
  ExecutablePath: /usr/bin/nautilus
  GsettingsChanges:
   
  InstallationDate: Installed on 2015-02-16 (87 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release i386 
(20140722.2)
  SourcePackage: nautilus
  UpgradeStatus: No upgrade log present (probably fresh install)

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

-- 
Mailing list: https://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 1455091] Re: Remeber log in forever keeps forgetting it forever

[edward stavin]

can you tell me what version of Nautilus this is that is buggy?  I could
then add it to the gnome report you want.

On Thu, May 28, 2015 at 11:44 AM, Edward Stavin edwardsta...@gmail.com
wrote:

 HI.  Not familiar with your processes as I am really a windows user trying
 to convert myself to using linux. Here is the link you wanted.
 https://bugzilla.gnome.org/show_bug.cgi?id=750034
   Hope this helps you fix it up.

 Edward


 On Wed, May 27, 2015 at 10:56 AM, Sebastien Bacher seb...@ubuntu.com
 wrote:

 Thank you for taking the time to report this bug and helping to make
 Ubuntu better. The issue you are reporting is an upstream one and it
 would be nice if somebody having it could send the bug to the developers
 of the software by following the instructions at
 https://wiki.ubuntu.com/Bugs/Upstream/GNOME. If you have done so, please
 tell us the number of the upstream bug (or the link), so we can add a
 bugwatch that will inform us about its status. Thanks in advance.

 ** Changed in: nautilus (Ubuntu)
Importance: Undecided = Low

 --
 You received this bug notification because you are subscribed to the bug
 report.
 https://bugs.launchpad.net/bugs/1455091

 Title:
   Remeber log in forever keeps forgetting it forever

 Status in nautilus package in Ubuntu:
   New

 Bug description:
   I keep selecting remember my login to my NAS forever, yet every time I
   return to the screen after shutting down my PC it ask me to retype the
   log in details and password.

   My conclusion would be that the remember forever feature does not
   work... it only remembers for the duration of the current session.
   Once I shutdown or reboot the login details vanish and I have to enter
   them all again.

   Hope this helps improve the product.  I can access the NAS by clicking
   on the NAS icon or going through the widows network icons but the
   results are the same both ways.

   Hope this helps improve a great product.

   ProblemType: Bug
   DistroRelease: Ubuntu 14.04
   Package: nautilus 1:3.10.1-0ubuntu9.7
   ProcVersionSignature: Ubuntu 3.13.0-52.86-generic 3.13.11-ckt18
   Uname: Linux 3.13.0-52-generic i686
   ApportVersion: 2.14.1-0ubuntu3.10
   Architecture: i386
   CurrentDesktop: Unity
   Date: Thu May 14 09:15:07 2015
   ExecutablePath: /usr/bin/nautilus
   GsettingsChanges:

   InstallationDate: Installed on 2015-02-16 (87 days ago)
   InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release i386
 (20140722.2)
   SourcePackage: nautilus
   UpgradeStatus: No upgrade log present (probably fresh install)

 To manage notifications about this bug go to:

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




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

Title:
  Remeber log in forever keeps forgetting it forever

Status in Nautilus:
  Unknown
Status in nautilus package in Ubuntu:
  Triaged

Bug description:
  I keep selecting remember my login to my NAS forever, yet every time I
  return to the screen after shutting down my PC it ask me to retype the
  log in details and password.

  My conclusion would be that the remember forever feature does not
  work... it only remembers for the duration of the current session.
  Once I shutdown or reboot the login details vanish and I have to enter
  them all again.

  Hope this helps improve the product.  I can access the NAS by clicking
  on the NAS icon or going through the widows network icons but the
  results are the same both ways.

  Hope this helps improve a great product.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: nautilus 1:3.10.1-0ubuntu9.7
  ProcVersionSignature: Ubuntu 3.13.0-52.86-generic 3.13.11-ckt18
  Uname: Linux 3.13.0-52-generic i686
  ApportVersion: 2.14.1-0ubuntu3.10
  Architecture: i386
  CurrentDesktop: Unity
  Date: Thu May 14 09:15:07 2015
  ExecutablePath: /usr/bin/nautilus
  GsettingsChanges:
   
  InstallationDate: Installed on 2015-02-16 (87 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release i386 
(20140722.2)
  SourcePackage: nautilus
  UpgradeStatus: No upgrade log present (probably fresh install)

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

-- 
Mailing list: https://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 1455091] Re: Remeber log in forever keeps forgetting it forever

[edward stavin]

HI.  Not familiar with your processes as I am really a windows user trying
to convert myself to using linux. Here is the link you wanted.
https://bugzilla.gnome.org/show_bug.cgi?id=750034
  Hope this helps you fix it up.

Edward


On Wed, May 27, 2015 at 10:56 AM, Sebastien Bacher seb...@ubuntu.com
wrote:

 Thank you for taking the time to report this bug and helping to make
 Ubuntu better. The issue you are reporting is an upstream one and it
 would be nice if somebody having it could send the bug to the developers
 of the software by following the instructions at
 https://wiki.ubuntu.com/Bugs/Upstream/GNOME. If you have done so, please
 tell us the number of the upstream bug (or the link), so we can add a
 bugwatch that will inform us about its status. Thanks in advance.

 ** Changed in: nautilus (Ubuntu)
Importance: Undecided = Low

 --
 You received this bug notification because you are subscribed to the bug
 report.
 https://bugs.launchpad.net/bugs/1455091

 Title:
   Remeber log in forever keeps forgetting it forever

 Status in nautilus package in Ubuntu:
   New

 Bug description:
   I keep selecting remember my login to my NAS forever, yet every time I
   return to the screen after shutting down my PC it ask me to retype the
   log in details and password.

   My conclusion would be that the remember forever feature does not
   work... it only remembers for the duration of the current session.
   Once I shutdown or reboot the login details vanish and I have to enter
   them all again.

   Hope this helps improve the product.  I can access the NAS by clicking
   on the NAS icon or going through the widows network icons but the
   results are the same both ways.

   Hope this helps improve a great product.

   ProblemType: Bug
   DistroRelease: Ubuntu 14.04
   Package: nautilus 1:3.10.1-0ubuntu9.7
   ProcVersionSignature: Ubuntu 3.13.0-52.86-generic 3.13.11-ckt18
   Uname: Linux 3.13.0-52-generic i686
   ApportVersion: 2.14.1-0ubuntu3.10
   Architecture: i386
   CurrentDesktop: Unity
   Date: Thu May 14 09:15:07 2015
   ExecutablePath: /usr/bin/nautilus
   GsettingsChanges:

   InstallationDate: Installed on 2015-02-16 (87 days ago)
   InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release i386
 (20140722.2)
   SourcePackage: nautilus
   UpgradeStatus: No upgrade log present (probably fresh install)

 To manage notifications about this bug go to:

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


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

Title:
  Remeber log in forever keeps forgetting it forever

Status in nautilus package in Ubuntu:
  New

Bug description:
  I keep selecting remember my login to my NAS forever, yet every time I
  return to the screen after shutting down my PC it ask me to retype the
  log in details and password.

  My conclusion would be that the remember forever feature does not
  work... it only remembers for the duration of the current session.
  Once I shutdown or reboot the login details vanish and I have to enter
  them all again.

  Hope this helps improve the product.  I can access the NAS by clicking
  on the NAS icon or going through the widows network icons but the
  results are the same both ways.

  Hope this helps improve a great product.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: nautilus 1:3.10.1-0ubuntu9.7
  ProcVersionSignature: Ubuntu 3.13.0-52.86-generic 3.13.11-ckt18
  Uname: Linux 3.13.0-52-generic i686
  ApportVersion: 2.14.1-0ubuntu3.10
  Architecture: i386
  CurrentDesktop: Unity
  Date: Thu May 14 09:15:07 2015
  ExecutablePath: /usr/bin/nautilus
  GsettingsChanges:
   
  InstallationDate: Installed on 2015-02-16 (87 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release i386 
(20140722.2)
  SourcePackage: nautilus
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1455091] [NEW] Remeber log in forever keeps forgetting it forever

[edward stavin]

Public bug reported:

I keep selecting remember my login to my NAS forever, yet every time I
return to the screen after shutting down my PC it ask me to retype the
log in details and password.

My conclusion would be that the remember forever feature does not
work... it only remembers for the duration of the current session.  Once
I shutdown or reboot the login details vanish and I have to enter them
all again.

Hope this helps improve the product.  I can access the NAS by clicking
on the NAS icon or going through the widows network icons but the
results are the same both ways.

Hope this helps improve a great product.

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: nautilus 1:3.10.1-0ubuntu9.7
ProcVersionSignature: Ubuntu 3.13.0-52.86-generic 3.13.11-ckt18
Uname: Linux 3.13.0-52-generic i686
ApportVersion: 2.14.1-0ubuntu3.10
Architecture: i386
CurrentDesktop: Unity
Date: Thu May 14 09:15:07 2015
ExecutablePath: /usr/bin/nautilus
GsettingsChanges:
 
InstallationDate: Installed on 2015-02-16 (87 days ago)
InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release i386 (20140722.2)
SourcePackage: nautilus
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: apport-bug i386 trusty

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

Title:
  Remeber log in forever keeps forgetting it forever

Status in nautilus package in Ubuntu:
  New

Bug description:
  I keep selecting remember my login to my NAS forever, yet every time I
  return to the screen after shutting down my PC it ask me to retype the
  log in details and password.

  My conclusion would be that the remember forever feature does not
  work... it only remembers for the duration of the current session.
  Once I shutdown or reboot the login details vanish and I have to enter
  them all again.

  Hope this helps improve the product.  I can access the NAS by clicking
  on the NAS icon or going through the widows network icons but the
  results are the same both ways.

  Hope this helps improve a great product.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: nautilus 1:3.10.1-0ubuntu9.7
  ProcVersionSignature: Ubuntu 3.13.0-52.86-generic 3.13.11-ckt18
  Uname: Linux 3.13.0-52-generic i686
  ApportVersion: 2.14.1-0ubuntu3.10
  Architecture: i386
  CurrentDesktop: Unity
  Date: Thu May 14 09:15:07 2015
  ExecutablePath: /usr/bin/nautilus
  GsettingsChanges:
   
  InstallationDate: Installed on 2015-02-16 (87 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release i386 
(20140722.2)
  SourcePackage: nautilus
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1426547] [NEW] wakes from suspend with ethernet networking disabled

[edward stavin]

Public bug reported:

Power settings are set to SUSPEND when inactive for 5 minutes.

The activity timer suspends the computer either a) while I am working on
it but after it has been up for about 3 hours regardless of activity or
b) alternatively it suspends the computer after 5 minutes of no activity
and in both cases the when the computer wakes from suspend it does not
have an ethernet connection and does not recover automatically.  The
ENABLE Networking button at the top of the screen is UNCHECKED.
Replacing the check mark does not reenable the ethernet networking
service but the check mark shows the networking as enabled incorrectly.

At this point it is not possible to use the TERMINAL window to report
the ubuntu-bug -w as the window reports at the send button that
networking is not active.

Thus I have reboot the computer to get networking working again and then
immediately used the TERMINAL to place this bug report.

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: compiz-core 1:0.9.11.2+14.04.20140714-0ubuntu1
ProcVersionSignature: Ubuntu 3.13.0-46.76-generic 3.13.11-ckt15
Uname: Linux 3.13.0-46-generic i686
.tmp.unity.support.test.0:
 
ApportVersion: 2.14.1-0ubuntu3.7
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
CurrentDesktop: Unity
Date: Fri Feb 27 15:15:31 2015
DistUpgraded: Fresh install
DistroCodename: trusty
DistroVariant: ubuntu
ExecutablePath: /usr/bin/compiz
GraphicsCard:
 Advanced Micro Devices, Inc. [AMD/ATI] RV350 [Radeon 9550] [1002:4153] 
(prog-if 00 [VGA controller])
   Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] Device [1002:0402]
   Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] Device [1002:0403]
InstallationDate: Installed on 2015-02-16 (11 days ago)
InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release i386 (20140722.2)
Lsusb:
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
 Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
 Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
 Bus 002 Device 002: ID 058f:9360 Alcor Micro Corp. 8-in-1 Media Card Reader
 Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
MachineType: HP Pavilion 061 PW793AA-ABA A1012X
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-46-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
SourcePackage: compiz
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 03/09/2005
dmi.bios.vendor: Phoenix Technologies, LTD
dmi.bios.version: 3.10
dmi.board.name: Salmon
dmi.board.vendor: ASUSTek Computer INC.
dmi.board.version: 1.04
dmi.chassis.type: 3
dmi.chassis.vendor: Hewlett-Packard
dmi.chassis.version: 
dmi.modalias: 
dmi:bvnPhoenixTechnologies,LTD:bvr3.10:bd03/09/2005:svnHPPavilion061:pnPW793AA-ABAA1012X:pvr0nB1211RE101SALMO00:rvnASUSTekComputerINC.:rnSalmon:rvr1.04:cvnHewlett-Packard:ct3:cvr:
dmi.product.name: PW793AA-ABA A1012X
dmi.product.version: 0nB1211RE101SALMO00
dmi.sys.vendor: HP Pavilion 061
version.compiz: compiz 1:0.9.11.2+14.04.20140714-0ubuntu1
version.libdrm2: libdrm2 2.4.56-1~ubuntu2
version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.3
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.3
version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2.7
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3.1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1.4
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2
xserver.bootTime: Fri Feb 27 15:13:45 2015
xserver.configfile: default
xserver.devices:
 inputPower Button KEYBOARD, id 6
 inputPower Button KEYBOARD, id 7
 inputSleep Button KEYBOARD, id 8
 inputAT Translated Set 2 keyboard KEYBOARD, id 9
 inputImPS/2 Generic Wheel Mouse MOUSE, id 10
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.version: 2:1.15.1-0ubuntu2.7
xserver.video_driver: radeon

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


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

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

Title:
  wakes from suspend with ethernet networking disabled

Status in compiz package in Ubuntu:
  New

Bug description:
  Power settings are set to SUSPEND when inactive for 5 minutes.

  The activity timer suspends the computer either a) while I am working
  on it but after it has been up for about 3 hours regardless of
  activity or b) alternatively it suspends the computer after 5 minutes
  of no activity 

[Desktop-packages] [Bug 1423309] Re: screen display settings dont show correct resolution

[edward stavin]

Here is what the display screen shows at boot up... two resolution
choices only... neither correct for an old traditional shaped monitor.
only 800x600 and this 1024x768 popup.  I tried clicking on the choices
pull down to show you the two of them but it seems there me a third bug
present.  the PRT SCRN does not work when the pull down is open... so I
cant show you.

** Attachment added: Screenshot from 2015-02-18 14:44:46.png
   
https://bugs.launchpad.net/ubuntu/+source/unity-control-center/+bug/1423309/+attachment/4322096/+files/Screenshot%20from%202015-02-18%2014%3A44%3A46.png

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

Title:
  screen display settings dont show correct resolution

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

Bug description:
  Only two choices appear in screen display window 800x600 and 1024 x
  768 for my monitor.  Window shows unknown monitor about 85% of the day
  when I check it.  Am forced to use one or the other of these
  settings.. neither of which is right for my screen. One has giant
  letters and the other a verticall squashed screen.

  Once in a while (the other 15%) when I click on the system settings
  icon... something happens and the display resets itself to a higher
  resolution and better screen fill than the above two choices.  then
  when I check the screen display window it shows I have a HANSOL 16
  screen.  In this case a 3rd resolution is offered 1280x1024 5:4 and is
  almost correct... call it useable.  However this 3rd setting does not
  survive a reboot and the cycle repeats itself.

  The monitor is actually a 17 Hansol knock off.. MH-170a model E17BL
  if that helps any... Over ten years old.

  Is there someway to make the Ubuntu system offer the 1280x1024 option
  right after system boot.  For some reason only the other two options I
  mentioned in the first sentence show up.  I will attach a picture of
  what I get when the correct setting finally appears.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: unity-control-center 14.04.3+14.04.20140922-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-45.74-generic 3.13.11-ckt13
  Uname: Linux 3.13.0-45-generic i686
  ApportVersion: 2.14.1-0ubuntu3.7
  Architecture: i386
  CurrentDesktop: Unity
  Date: Wed Feb 18 14:08:01 2015
  ExecutablePath: /usr/bin/unity-control-center
  InstallationDate: Installed on 2015-02-16 (2 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release i386 
(20140722.2)
  SourcePackage: unity-control-center
  UpgradeStatus: No upgrade log present (probably fresh install)
  usr_lib_unity-control-center: deja-dup 30.0-0ubuntu4

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

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

[Desktop-packages] [Bug 1423309] [NEW] screen display settings dont show correct resolution

[edward stavin]

Public bug reported:

Only two choices appear in screen display window 800x600 and 1024 x 768
for my monitor.  Window shows unknown monitor about 85% of the day when
I check it.  Am forced to use one or the other of these settings..
neither of which is right for my screen. One has giant letters and the
other a verticall squashed screen.

Once in a while (the other 15%) when I click on the system settings
icon... something happens and the display resets itself to a higher
resolution and better screen fill than the above two choices.  then when
I check the screen display window it shows I have a HANSOL 16 screen.
In this case a 3rd resolution is offered 1280x1024 5:4 and is almost
correct... call it useable.  However this 3rd setting does not survive a
reboot and the cycle repeats itself.

The monitor is actually a 17 Hansol knock off.. MH-170a model E17BL if
that helps any... Over ten years old.

Is there someway to make the Ubuntu system offer the 1280x1024 option
right after system boot.  For some reason only the other two options I
mentioned in the first sentence show up.  I will attach a picture of
what I get when the correct setting finally appears.

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: unity-control-center 14.04.3+14.04.20140922-0ubuntu1
ProcVersionSignature: Ubuntu 3.13.0-45.74-generic 3.13.11-ckt13
Uname: Linux 3.13.0-45-generic i686
ApportVersion: 2.14.1-0ubuntu3.7
Architecture: i386
CurrentDesktop: Unity
Date: Wed Feb 18 14:08:01 2015
ExecutablePath: /usr/bin/unity-control-center
InstallationDate: Installed on 2015-02-16 (2 days ago)
InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release i386 (20140722.2)
SourcePackage: unity-control-center
UpgradeStatus: No upgrade log present (probably fresh install)
usr_lib_unity-control-center: deja-dup 30.0-0ubuntu4

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


** Tags: apport-bug i386 trusty

** Attachment added: screen resolution that needs to appear on boot.
   
https://bugs.launchpad.net/bugs/1423309/+attachment/4322052/+files/Hansol%20Screenshot%20from%202015-02-18%2010%3A34%3A56.png

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

Title:
  screen display settings dont show correct resolution

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

Bug description:
  Only two choices appear in screen display window 800x600 and 1024 x
  768 for my monitor.  Window shows unknown monitor about 85% of the day
  when I check it.  Am forced to use one or the other of these
  settings.. neither of which is right for my screen. One has giant
  letters and the other a verticall squashed screen.

  Once in a while (the other 15%) when I click on the system settings
  icon... something happens and the display resets itself to a higher
  resolution and better screen fill than the above two choices.  then
  when I check the screen display window it shows I have a HANSOL 16
  screen.  In this case a 3rd resolution is offered 1280x1024 5:4 and is
  almost correct... call it useable.  However this 3rd setting does not
  survive a reboot and the cycle repeats itself.

  The monitor is actually a 17 Hansol knock off.. MH-170a model E17BL
  if that helps any... Over ten years old.

  Is there someway to make the Ubuntu system offer the 1280x1024 option
  right after system boot.  For some reason only the other two options I
  mentioned in the first sentence show up.  I will attach a picture of
  what I get when the correct setting finally appears.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: unity-control-center 14.04.3+14.04.20140922-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-45.74-generic 3.13.11-ckt13
  Uname: Linux 3.13.0-45-generic i686
  ApportVersion: 2.14.1-0ubuntu3.7
  Architecture: i386
  CurrentDesktop: Unity
  Date: Wed Feb 18 14:08:01 2015
  ExecutablePath: /usr/bin/unity-control-center
  InstallationDate: Installed on 2015-02-16 (2 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release i386 
(20140722.2)
  SourcePackage: unity-control-center
  UpgradeStatus: No upgrade log present (probably fresh install)
  usr_lib_unity-control-center: deja-dup 30.0-0ubuntu4

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

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

[Desktop-packages] [Bug 1422203] [NEW] ubuntu software centre freezes while installing Ubuntu Restricted Extras

[edward stavin]

Public bug reported:

Trying to install Ubuntu restricted extras to support audacity on a
freshly installed from DVD copy of Ubuntu 14.10

ProblemType: Bug
DistroRelease: Ubuntu 14.10
Package: software-center 13.10-0ubuntu4.1
ProcVersionSignature: Ubuntu 3.16.0-30.40-generic 3.16.7-ckt3
Uname: Linux 3.16.0-30-generic i686
ApportVersion: 2.14.7-0ubuntu8.1
Architecture: i386
CurrentDesktop: Unity
Date: Sun Feb 15 17:46:52 2015
ExecutablePath: /usr/share/software-center/software-center
InstallationDate: Installed on 2015-02-15 (0 days ago)
InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Release i386 (20141022.1)
InterpreterPath: /usr/bin/python2.7
PackageArchitecture: all
ProcEnviron:
 PATH=(custom, no user)
 LANGUAGE=en_CA:en
 XDG_RUNTIME_DIR=set
 LANG=en_CA.UTF-8
 SHELL=/bin/bash
SourcePackage: software-center
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: apport-bug i386 utopic

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

Title:
  ubuntu software centre freezes while installing Ubuntu Restricted
  Extras

Status in software-center package in Ubuntu:
  New

Bug description:
  Trying to install Ubuntu restricted extras to support audacity on a
  freshly installed from DVD copy of Ubuntu 14.10

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: software-center 13.10-0ubuntu4.1
  ProcVersionSignature: Ubuntu 3.16.0-30.40-generic 3.16.7-ckt3
  Uname: Linux 3.16.0-30-generic i686
  ApportVersion: 2.14.7-0ubuntu8.1
  Architecture: i386
  CurrentDesktop: Unity
  Date: Sun Feb 15 17:46:52 2015
  ExecutablePath: /usr/share/software-center/software-center
  InstallationDate: Installed on 2015-02-15 (0 days ago)
  InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Release i386 (20141022.1)
  InterpreterPath: /usr/bin/python2.7
  PackageArchitecture: all
  ProcEnviron:
   PATH=(custom, no user)
   LANGUAGE=en_CA:en
   XDG_RUNTIME_DIR=set
   LANG=en_CA.UTF-8
   SHELL=/bin/bash
  SourcePackage: software-center
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1417850] [NEW] Resume from suspend to black screen with mouse pointer on Thinkpad Helix

[Edward Z. Yang]

Public bug reported:

This is a fresh 13.10 install on a new Thinkpad Helix. The error is
intermittent, maybe one out of every five suspends hangs this way.
Switching to tty works, killing lightdm puts me back to the login
screen.

ProblemType: Bug
DistroRelease: Ubuntu 14.10
Package: xserver-xorg-video-intel 2:2.99.914-1~exp1ubuntu4.1
ProcVersionSignature: Ubuntu 3.16.0-23.31-generic 3.16.4
Uname: Linux 3.16.0-23-generic x86_64
ApportVersion: 2.14.7-0ubuntu8.1
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
Date: Tue Feb  3 18:59:49 2015
DistUpgraded: Fresh install
DistroCodename: utopic
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, including running git bisection searches
GraphicsCard:
 Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 
09) (prog-if 00 [VGA controller])
   Subsystem: Lenovo Device [17aa:2207]
MachineType: LENOVO 36984SU
ProcEnviron:
 TERM=linux
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=set
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-23-generic.efi.signed 
root=UUID=caf95fbd-1395-4761-9ee0-9221edaeab3c ro quiet splash vt.handoff=7
SourcePackage: xserver-xorg-video-intel
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 07/01/2014
dmi.bios.vendor: LENOVO
dmi.bios.version: GFET48WW (1.27 )
dmi.board.asset.tag: Not Available
dmi.board.name: 36984SU
dmi.board.vendor: LENOVO
dmi.board.version: 0B98401 WIN
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Not Available
dmi.modalias: 
dmi:bvnLENOVO:bvrGFET48WW(1.27):bd07/01/2014:svnLENOVO:pn36984SU:pvrThinkPadHelix:rvnLENOVO:rn36984SU:rvr0B98401WIN:cvnLENOVO:ct10:cvrNotAvailable:
dmi.product.name: 36984SU
dmi.product.version: ThinkPad Helix
dmi.sys.vendor: LENOVO
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.2-0ubuntu0.1
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 10.3.2-0ubuntu0.1
version.xserver-xorg-core: xserver-xorg-core 2:1.16.0-1ubuntu1.2
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~exp1ubuntu4.1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu2
xserver.bootTime: Tue Feb  3 08:00:17 2015
xserver.configfile: default
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 product id   12893 
 vendor AUO
xserver.version: 2:1.16.0-1ubuntu1.2

** Affects: xserver-xorg-video-intel (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug ubuntu utopic

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

Title:
  Resume from suspend to black screen with mouse pointer on Thinkpad
  Helix

Status in xserver-xorg-video-intel package in Ubuntu:
  New

Bug description:
  This is a fresh 13.10 install on a new Thinkpad Helix. The error is
  intermittent, maybe one out of every five suspends hangs this way.
  Switching to tty works, killing lightdm puts me back to the login
  screen.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: xserver-xorg-video-intel 2:2.99.914-1~exp1ubuntu4.1
  ProcVersionSignature: Ubuntu 3.16.0-23.31-generic 3.16.4
  Uname: Linux 3.16.0-23-generic x86_64
  ApportVersion: 2.14.7-0ubuntu8.1
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  Date: Tue Feb  3 18:59:49 2015
  DistUpgraded: Fresh install
  DistroCodename: utopic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: Lenovo Device [17aa:2207]
  MachineType: LENOVO 36984SU
  ProcEnviron:
   TERM=linux
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=set
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-23-generic.efi.signed 
root=UUID=caf95fbd-1395-4761-9ee0-9221edaeab3c ro quiet splash vt.handoff=7
  SourcePackage: xserver-xorg-video-intel
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/01/2014
  dmi.bios.vendor: LENOVO
  dmi.bios.version: GFET48WW (1.27 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 36984SU
  dmi.board.vendor: LENOVO
  dmi.board.version: 0B98401 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not 

[Desktop-packages] [Bug 1392887] Re: serial wacom devices gone after upgrade to utopic/14.10

[Edward Z. Yang]

Using the original workaround (not comment #8), I have gotten back Wacom
input, and it is preserved across sleep. So maybe the updated udevs rule
is not right either. I haven't tested it. I had to reboot to put the new
rule into action.

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

Title:
  serial wacom devices gone after upgrade to utopic/14.10

Status in xf86-input-wacom package in Ubuntu:
  Triaged

Bug description:
  Recently I upgraded ubuntu from 14.04 to 14.10 on my HP EliteBook 2760p. 
After that, all serial wacom devices (for the touchscreen) are gone:
     serial wacom stylus
     serial wacom eraser
     serial wacom touch

  xinput -list and xsetwacom --list don't show these devices and the
  Wacom Tablet section of the system setings reports 'no tablet
  detected' rather than showing the usual settings. Booting with the old
  linux 3.13 kernel makes no difference to the new version 3.16.

  To find out what happened I played around on a spare partition with the 
following results:
  1) fresh installation of 14.10 - result is the same like reported above: no 
touch devices
  2) fresh installation of 14.04 - touch works out of the box
  3) upgraded the fresh installation of trusty to utopic: touch devices gone 
again
  4) manually changed repos to utopic after fresh installation of 14.04 and 
updated ONLY the xserver-xorg-input-wacom package: apt pulled some dependencies 
and installed without errors, touch devices gone (so it reproduces the error 
exactly as the full upgrade)

  WORKAROUND: Replace the udev rule 
/lib/udev/rules.d/69-wacom.rules/wacom.rules by the old file from Ubuntu 14.04 
by putting it in /lib/udev/rules.d/ :
  
https://bugs.launchpad.net/ubuntu/+source/xf86-input-wacom/+bug/1392887/+attachment/4264135/+files/69-xserver-xorg-input-wacom.rules

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: xserver-xorg-input-wacom 1:0.25.0-0ubuntu1
  ProcVersionSignature: Ubuntu 3.16.0-24.32-generic 3.16.4
  Uname: Linux 3.16.0-24-generic x86_64
  ApportVersion: 2.14.7-0ubuntu8
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Nov 14 22:51:05 2014
  DistUpgraded: 2014-11-01 04:28:11,674 DEBUG enabling apt cron job
  DistroCodename: utopic
  DistroVariant: ubuntu
  InstallationDate: Installed on 2012-10-16 (759 days ago)
  InstallationMedia: Ubuntu 12.04.1 LTS Precise Pangolin - Release amd64 
(20120823.1)
  MachineType: Hewlett-Packard HP EliteBook 2760p
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-24-generic 
root=UUID=81ff9b66-4d33-49d5-a76f-cf1418c3e354 ro quiet splash vt.handoff=7
  SourcePackage: xf86-input-wacom
  UpgradeStatus: Upgraded to utopic on 2014-11-01 (13 days ago)
  dmi.bios.date: 08/04/2014
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: 68SOU Ver. F.50
  dmi.board.name: 162A
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 05.40
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvr68SOUVer.F.50:bd08/04/2014:svnHewlett-Packard:pnHPEliteBook2760p:pvrA0005F02:rvnHewlett-Packard:rn162A:rvrKBCVersion05.40:cvnHewlett-Packard:ct10:cvr:
  dmi.product.name: HP EliteBook 2760p
  dmi.product.version: A0005F02
  dmi.sys.vendor: Hewlett-Packard
  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-0ubuntu3
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.3.0-0ubuntu3
  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~exp1ubuntu4
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.11-1ubuntu2
  xserver.bootTime: Fri Nov 14 21:19:38 2014
  xserver.configfile: default
  xserver.errors:

  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id   22337
   vendor SEC
  xserver.version: 2:1.16.0-1ubuntu1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xf86-input-wacom/+bug/1392887/+subscriptions

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

[Desktop-packages] [Bug 1235625] Re: fix legacy keygrabber for gnome-ish sessions

[Edward Z. Yang]

Hey guys, it looks like in Utopic the legacy keygrabber has been gutted
entirely. What should we do now if we run an alternate window manager?

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

Title:
  fix legacy keygrabber for gnome-ish sessions

Status in gnome-settings-daemon package in Ubuntu:
  Fix Released
Status in gnome-settings-daemon source package in Saucy:
  Fix Released

Bug description:
  [ Description ]

  In Saucy, media keys in gnome-ish (using gnome-settings-daemon)
  sessions only work when gnome-panel or Unity are in use, as the code
  path checks for their names on the bus. They ought to work for all
  sessions.

  [ Fix ]

  Change the logic so that the keygrabber is started all the time except
  under Shell sessions.

  [ QA ]

  In a session that runs gnome-settings-daemon but neither panel nor
  shell (xfce or Openbox? or a custom xmonad), check that media keys now
  work.

  [ Regression potential ]

  Changes activation criteria for the legacy keygrabber. Check it still
  works in Unity, panel and that the new method works under shell.

  [ Original report ]

  The previous patch to fix the legacy keygrabber was Unity specific and
  breaks on gnome-ish sessions that require it, instead we should load
  the legacy keygrabber for any session that is not gnome-shell

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

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

[Desktop-packages] [Bug 1372157] Re: Unity Greeter does not follow desktop background

[Edward Morbius]

I have this bug too on my 14.04.1 LTS, login does not show my wallpaper
as it should, it shows default Ubuntu wallpaper, lockscreen correctly
shows my wallpaper but login does not, it is a fresh installation and
fully updated.

lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu 14.04.1 LTS
Release:14.04
Codename:   trusty

apt-cache policy unity-greeter
unity-greeter:
  Installed: 14.04.10-0ubuntu1
  Candidate: 14.04.10-0ubuntu1
  Version table:
 *** 14.04.10-0ubuntu1 0
500 http://archive.ubuntu.com/ubuntu/ trusty-updates/main amd64 Packages
100 /var/lib/dpkg/status
 14.04.9-0ubuntu1 0
500 http://archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages

dpkg -l | grep unity-greeter
ii  unity-greeter 14.04.10-0ubuntu1 
  amd64Unity Greeter

dpkg -l | grep lightdm
ii  liblightdm-gobject-1-01.10.1-0ubuntu1   
  amd64LightDM GObject client library
ii  lightdm   1.10.1-0ubuntu1   
  amd64Display Manager

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

Title:
  Unity Greeter does not follow desktop background

Status in “unity-greeter” package in Ubuntu:
  Confirmed

Bug description:
  I will be referencing this bug
  https://bugs.launchpad.net/bugs/844081

  1) lsb_release -rd output:
  Description:  Ubuntu 14.04.1 LTS
  Release:  14.04

  2) apt-cache policy unity-greeter output
  unity-greeter:
    Installed: 14.04.10-0ubuntu1
    Candidate: 14.04.10-0ubuntu1
    Version table:
   *** 14.04.10-0ubuntu1 0
  500 http://us.archive.ubuntu.com/ubuntu/ trusty-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   14.04.9-0ubuntu1 0
  500 http://us.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages

  3)I change my desktop wallpaper to a picture I have imported from my
  mobile phone or from the internet, Unity greeter should show me my
  desktop wallpaper when I select my User account ready to log in.

  4) Instead, Unity Greeter shows me the default Ubuntu wallpaper.

  
  Oh, I wanted to add that Installing another Wallpaper pack sudo apt-get 
install ubuntu-wallpapers-releasename and selecting one of those wallpapers 
still reverts back to the default wallpaper on the login screen.

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

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

[Desktop-packages] [Bug 1261184] Re: nvidia-331-updates should be the dependency of nvidia-current

[Edward Schwartz]

** Summary changed:

- nvidia-331-updates should be the dependence of nvidia-current
+ nvidia-331-updates should be the dependency of nvidia-current

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

Title:
  nvidia-331-updates should be the dependency of nvidia-current

Status in “nvidia-graphics-drivers-304” package in Ubuntu:
  Confirmed

Bug description:
  nvidia-331-updates should be the dependence of nvidia-current.

  Nvidia 304 is a legacy driver (as 173.14, 96.43 and 71.86), and Nvidia
  331 is the latest long lived branch version of the driver, what fits
  best for Trusty.

  See: http://www.nvidia.com/object/unix.html

  PS: I think current means the latest 331 driver, currently nvidia-
  current is a transitional package for nvidia-304, and sometimes it is
  older than nvidia-304-updates, it is a bit confusing.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: nvidia-current 304.116-0ubuntu1
  ProcVersionSignature: Ubuntu 3.12.0-7.15-generic 3.12.4
  Uname: Linux 3.12.0-7-generic x86_64
  ApportVersion: 2.12.7-0ubuntu2
  Architecture: amd64
  CasperVersion: 1.336ubuntu1
  Date: Sun Dec 15 16:24:20 2013
  LiveMediaBuild: Ubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20131215)
  ProcEnviron:
   LANGUAGE=en_US
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: nvidia-graphics-drivers-304
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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