date:20191107

** Changed in: yaru
   Status: New => Fix Released

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

Title:
  Octave GUI toolbar file icons are all the same in Yaru icon theme

Status in Yaru Theme:
  Fix Released
Status in octave package in Ubuntu:
  Confirmed
Status in yaru-theme package in Ubuntu:
  Confirmed

Bug description:
  In Octave GUI editor tab, the first five toolbar icons (New, Open,
  Save, Save As, and Print) are all the same icon (a page with the
  letter A in the upper right corner).  It is hard to remember which is
  which.

  I'm using:
  Description:  Ubuntu 19.04
  Release:  19.04

  See the attached screenshot.

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

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

[Desktop-packages] [Bug 1772588] Re: Remove obsolete X11 drivers from the archive

2019-11-07 Thread Bryan Quigley

@leosmuller
evdev was already marked invalid so it's not considered for removal as part of 
this bug report. See comment #1.

siliconmotion - If they work for you on 18.04 LTS, you can keep running
that until 2023.  I would be shocked if these are saving you power - and
happy to help with an analysis in specifics if you want.  Please use the
contact this user button on my Launchpad page to discuss further (click
my name). We can bring a conclusion back to this bug report if relevant
- most of that conversation likely wouldn't be relevant.

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

Title:
  Remove obsolete X11 drivers from the archive

Status in xf86-input-mtrack package in Ubuntu:
  Incomplete
Status in xf86-input-xwiimote package in Ubuntu:
  New
Status in xserver-xorg-input-aiptek package in Ubuntu:
  New
Status in xserver-xorg-input-elographics package in Ubuntu:
  New
Status in xserver-xorg-input-evdev package in Ubuntu:
  Invalid
Status in xserver-xorg-input-keyboard package in Ubuntu:
  New
Status in xserver-xorg-input-mouse package in Ubuntu:
  New
Status in xserver-xorg-input-mutouch package in Ubuntu:
  New
Status in xserver-xorg-input-void package in Ubuntu:
  New
Status in xserver-xorg-video-ast package in Ubuntu:
  Triaged
Status in xserver-xorg-video-geode package in Ubuntu:
  New
Status in xserver-xorg-video-mach64 package in Ubuntu:
  New
Status in xserver-xorg-video-neomagic package in Ubuntu:
  New
Status in xserver-xorg-video-r128 package in Ubuntu:
  New
Status in xserver-xorg-video-savage package in Ubuntu:
  New
Status in xserver-xorg-video-siliconmotion package in Ubuntu:
  New
Status in xserver-xorg-video-sisusb package in Ubuntu:
  New
Status in xserver-xorg-video-tdfx package in Ubuntu:
  New
Status in xserver-xorg-video-trident package in Ubuntu:
  New

Bug description:
  xserver-xorg-video-all has not depended on these drivers for quite
  some time now, meaning that installation images didn't have them
  either nor installed them on the system. Now would be the time to drop
  them from the archive before next LTS & HWE-18.04 stack and in
  preparation for xserver 1.20.

  Some rationale in detail for future reference:
  input:
  -aiptek: no upstream release in 7 years
  -elographics: no upstream release in 6 years
  -evdev: replaced by -libinput (not entirely, see comment #1)
  -keyboard: replaced by -libinput
  -mtrack: no upstream release in 3 years, should be replaceable by -libinput 
by now
  -mouse: replaced by -libinput
  -mutouch: no upstream release in 7 years
  -void: xserver can start without an input driver these days
  -xwiimote: no upstream release in 5 years
  video:
  -ast: no upstream release in 3 years, no KMS support
  -geode: i386 only, no kernel support since moving to i586 (or i686?)
  -mach64: no KMS support
  -neomagic: no upstream release in 3 years, no KMS support
  -r128: no KMS support
  -savage: no KMS support
  -siliconmotion: no KMS suppport
  -sisusb: no KMS support
  -tdfx: no KMS support
  -trident: no KMS support

  Fedora dropped drivers without KMS (kernel modesetting) support five years 
ago:
  https://lists.fedoraproject.org/pipermail/devel/2013-August/188429.html

  one exception to this is -openchrome, which we'll keep since it has
  some users and might even get KMS support before next LTS.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xf86-input-mtrack/+bug/1772588/+subscriptions

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

[Desktop-packages] [Bug 1772588] Re: Remove obsolete X11 drivers from the archive

2019-11-07 Thread Leonardo Soares Müller

There are some computers and configurations I manage which rely on some
of these drivers:

evdev: there are some netbooks which have touchscreens that only work
with evdev, being detected by libinput but doing nothing. While this is
a libinput limitation, removing evdev would limit the netbooks'
capabilities: the touchscreen can be greatly beneficial, especially when
used with programs which can be centered on this type of interactivity
(ArduBlock is one example).

siliconmotion: some years ago, thousands of computers were bought with
PCI GPUs that use siliconmotion graphics. While some of these old
computers are unusable today, the GPUs aren't and can be installed and
used on new computers. These new computers have specifications good
enough to allow up to 5 seats for a single computer, greatly reducing
costs associated with keeping a laboratory, both by reduced initial
investment and reduced power usage.

I am worried: abandoning evdev would make some touchscreens stop
working, as libinput does not support those properly. Abandoning
siliconmotion would make certain multiseat configurations stop working,
making, for example, one laboratories with 8 computers for 22 seats
require buying additional 14 computers to replace what is going to stop
working.

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

Title:
  Remove obsolete X11 drivers from the archive

Status in xf86-input-mtrack package in Ubuntu:
  Incomplete
Status in xf86-input-xwiimote package in Ubuntu:
  New
Status in xserver-xorg-input-aiptek package in Ubuntu:
  New
Status in xserver-xorg-input-elographics package in Ubuntu:
  New
Status in xserver-xorg-input-evdev package in Ubuntu:
  Invalid
Status in xserver-xorg-input-keyboard package in Ubuntu:
  New
Status in xserver-xorg-input-mouse package in Ubuntu:
  New
Status in xserver-xorg-input-mutouch package in Ubuntu:
  New
Status in xserver-xorg-input-void package in Ubuntu:
  New
Status in xserver-xorg-video-ast package in Ubuntu:
  Triaged
Status in xserver-xorg-video-geode package in Ubuntu:
  New
Status in xserver-xorg-video-mach64 package in Ubuntu:
  New
Status in xserver-xorg-video-neomagic package in Ubuntu:
  New
Status in xserver-xorg-video-r128 package in Ubuntu:
  New
Status in xserver-xorg-video-savage package in Ubuntu:
  New
Status in xserver-xorg-video-siliconmotion package in Ubuntu:
  New
Status in xserver-xorg-video-sisusb package in Ubuntu:
  New
Status in xserver-xorg-video-tdfx package in Ubuntu:
  New
Status in xserver-xorg-video-trident package in Ubuntu:
  New

Bug description:
  xserver-xorg-video-all has not depended on these drivers for quite
  some time now, meaning that installation images didn't have them
  either nor installed them on the system. Now would be the time to drop
  them from the archive before next LTS & HWE-18.04 stack and in
  preparation for xserver 1.20.

  Some rationale in detail for future reference:
  input:
  -aiptek: no upstream release in 7 years
  -elographics: no upstream release in 6 years
  -evdev: replaced by -libinput (not entirely, see comment #1)
  -keyboard: replaced by -libinput
  -mtrack: no upstream release in 3 years, should be replaceable by -libinput 
by now
  -mouse: replaced by -libinput
  -mutouch: no upstream release in 7 years
  -void: xserver can start without an input driver these days
  -xwiimote: no upstream release in 5 years
  video:
  -ast: no upstream release in 3 years, no KMS support
  -geode: i386 only, no kernel support since moving to i586 (or i686?)
  -mach64: no KMS support
  -neomagic: no upstream release in 3 years, no KMS support
  -r128: no KMS support
  -savage: no KMS support
  -siliconmotion: no KMS suppport
  -sisusb: no KMS support
  -tdfx: no KMS support
  -trident: no KMS support

  Fedora dropped drivers without KMS (kernel modesetting) support five years 
ago:
  https://lists.fedoraproject.org/pipermail/devel/2013-August/188429.html

  one exception to this is -openchrome, which we'll keep since it has
  some users and might even get KMS support before next LTS.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xf86-input-mtrack/+bug/1772588/+subscriptions

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

[Desktop-packages] [Bug 1848489] Re: [SRU] libreoffice 6.2.8 for disco

2019-11-07 Thread Mathew Hodson

** No longer affects: libreoffice-l10n (Ubuntu)

** Changed in: libreoffice (Ubuntu)
   Status: Fix Committed => Fix Released

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

Title:
  [SRU] libreoffice 6.2.8 for disco

Status in libreoffice package in Ubuntu:
  Fix Released
Status in libreoffice source package in Disco:
  Fix Committed
Status in libreoffice-l10n source package in Disco:
  Fix Committed

Bug description:
  [Impact]

   * LibreOffice 6.2.8 is in its eighth bugfix release of the 6.2 line.
     For a list of fixed bugs compared to 6.2.7 see:
   https://wiki.documentfoundation.org/Releases/6.2.8/RC1#List_of_fixed_bugs
   https://wiki.documentfoundation.org/Releases/6.2.8/RC2#List_of_fixed_bugs
     (that's a total of 26 bugs)

   * Given the nature of the project, the complexity of the codebase and
  the high level of quality assurance upstream, it is preferable to SRU
  a minor release rather than cherry-pick selected bug fixes.

  [Test Case]

   * No specific test case, bugs fixed upstream hopefully come with
  unit/regression tests, and the release itself is extensively exercised
  upstream (both in an automated manner and manually) by a community of
  testers. Each minor release normally goes through two release
  candidates.

   * The libreoffice packages include autopkgtests, those should be run
  and verified to pass.

   * General smoke testing of all the applications in the office suite
  should be carried out.

  [Regression Potential]

   * A minor release with a total of 26 bug fixes always carries the
  potential for introducing regressions, even though it is a bugfix-only
  release, meaning that no new features were added, and no existing
  features were removed.

   * A combination of autopkgtests and careful smoke testing as
  described above should provide reasonable confidence that no
  regressions sneaked in.

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

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

[Desktop-packages] [Bug 1851234] Re: [SRU] libreoffice 6.3.3 for eoan

2019-11-07 Thread Mathew Hodson

** Changed in: libreoffice (Ubuntu)
   Status: Fix Committed => Fix Released

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

Title:
  [SRU] libreoffice 6.3.3 for eoan

Status in libreoffice package in Ubuntu:
  Fix Released
Status in libreoffice source package in Eoan:
  Fix Committed

Bug description:
  [Impact]

   * LibreOffice 6.3.3 is in its third bugfix release of the 6.3 line. Version 
6.3.3 is currently in focal.
     For a list of fixed bugs compared to 6.3.2 see the list of bugs fixed in 
the two release candidates:
   https://wiki.documentfoundation.org/Releases/6.3.3/RC1#List_of_fixed_bugs
   https://wiki.documentfoundation.org/Releases/6.3.3/RC2#List_of_fixed_bugs
     (that's a total of 83 bugs)

   * Given the nature of the project, the complexity of the codebase and
  the high level of quality assurance upstream, it is preferable to SRU
  a minor release rather than cherry-pick selected bug fixes.

  [Test Case]

   * No specific test case, bugs fixed upstream hopefully come with
  unit/regression tests, and the release itself is extensively exercised
  upstream (both in an automated manner and manually) by a community of
  testers. Each minor release normally goes through two release
  candidates.

   * The libreoffice packages include autopkgtests, those should be run
  and verified to pass.

   * General smoke testing of all the applications in the office suite
  should be carried out.

  [Regression Potential]

   * A minor release with a total of 83 bug fixes always carries the
  potential for introducing regressions, even though it is a bugfix-only
  release, meaning that no new features were added, and no existing
  features were removed.

   * A combination of autopkgtests and careful smoke testing as
  described above should provide reasonable confidence that no
  regressions sneaked in.

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

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

[Desktop-packages] [Bug 1809737] Re: Onboard crashes the entire desktop (Xorg crashes in _XkbSetMapChecks xkb.c:2387)

2019-11-07 Thread Leonardo Soares Müller

Is there a packaged version available with the fix for this bug? I'll
have one problematic machine for a few days so I can test. However, it
is an Intel Atom netbook, unlikely to be successful building onboard
directly on it.

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

Title:
  Onboard crashes the entire desktop (Xorg crashes in _XkbSetMapChecks
  xkb.c:2387)

Status in Onboard:
  New
Status in X.Org X server:
  New
Status in onboard package in Ubuntu:
  In Progress
Status in xorg-server package in Ubuntu:
  Triaged

Bug description:
  Onboard 1.4.1 crashes the entire Desktop if I selected any alternate
  character from pop-up

  [bishop@fringe ~]$ ls /usr/share/xsessions/
  xfce.desktop

  [bishop@fringe ~]$ echo $XDG_CURRENT_DESKTOP
  XFCE

  [bishop@fringe ~]$ echo $XDG_SESSION_TYPE
  x11

  [bishop@fringe ~]$ cat /etc/*-release
  Fedora release 29 (Twenty Nine)
  NAME=Fedora
  VERSION="29 (Twenty Nine)"
  ID=fedora
  VERSION_ID=29
  VERSION_CODENAME=""
  PLATFORM_ID="platform:f29"
  PRETTY_NAME="Fedora 29 (Twenty Nine)"
  ANSI_COLOR="0;34"
  LOGO=fedora-logo-icon
  CPE_NAME="cpe:/o:fedoraproject:fedora:29"
  HOME_URL="https://fedoraproject.org/;
  
DOCUMENTATION_URL="https://docs.fedoraproject.org/en-US/fedora/f29/system-administrators-guide/;
  SUPPORT_URL="https://fedoraproject.org/wiki/Communicating_and_getting_help;
  BUG_REPORT_URL="https://bugzilla.redhat.com/;
  REDHAT_BUGZILLA_PRODUCT="Fedora"
  REDHAT_BUGZILLA_PRODUCT_VERSION=29
  REDHAT_SUPPORT_PRODUCT="Fedora"
  REDHAT_SUPPORT_PRODUCT_VERSION=29
  PRIVACY_POLICY_URL="https://fedoraproject.org/wiki/Legal:PrivacyPolicy;
  Fedora release 29 (Twenty Nine)
  Fedora release 29 (Twenty Nine)

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

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

[Desktop-packages] [Bug 1845281] Re: gnome-shell crashed with SIGABRT in __GI_raise() from __GI_abort() from g_assertion_message() from g_assertion_message_expr() from meta_window_get_workspaces() [as

** Changed in: mutter
   Status: New => Fix Released

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

Title:
  gnome-shell crashed with SIGABRT in __GI_raise() from __GI_abort()
  from g_assertion_message() from g_assertion_message_expr() from
  meta_window_get_workspaces() [assertion failure "code should not be
  reached"]

Status in Mutter:
  Fix Released
Status in gnome-shell package in Ubuntu:
  Won't Fix
Status in mutter package in Ubuntu:
  In Progress

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
gnome-shell.  This problem was most recently seen with package version 
3.34.0-1ubuntu1, the problem page at 
https://errors.ubuntu.com/problem/85b6b0b07aafeed5ae109ce89a813b77d3721684 
contains more details, including versions of packages affected, stacktrace or 
traceback, and individual crash reports.
  If you do not have access to the Ubuntu Error Tracker and are a software 
developer, you can request it at http://forms.canonical.com/reports/.

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

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

[Desktop-packages] [Bug 1851139] Re: Firefox crashing about every 10-20 minutes

2019-11-07 Thread Seth Arnold

** Information type changed from Private Security to Public Security

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

Title:
  Firefox crashing about every 10-20 minutes

Status in firefox package in Ubuntu:
  New

Bug description:
  Hi,

  no details yet. Since today's ubuntu 18.04 update my firefox is
  crashing completely about every 10-20 minutes while browsing.
  terminates immediately, all windows/tabs gone instantly.

  I'm not absolutely sure, but I'm unter the impression that it always
  happens when visiting pages with commercial ads or having such pages
  in a tab.

  Since I am hosting web sites with ads myself, I am aware that for
  about three weeks several readers complained about malware and page
  redirects, which have been limited to MacOS/iOS/Safari so far, but it
  proves that particular Browsers are under attack through embedded
  commercial ads. Thus, I am also not sure whether it is actually caused
  by today's update or just a conincidence. But it looks as if there's
  something out there which causes firefox to immediately crash and
  terminate. All windows immediately gone, program terminated. Smells
  like some sort of attack or maybe just a regular bug and no
  intentional attack.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: firefox 70.0+build2-0ubuntu0.18.04.1
  ProcVersionSignature: Ubuntu 4.15.0-66.75-generic 4.15.18
  Uname: Linux 4.15.0-66-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  AddonCompatCheckDisabled: False
  ApportVersion: 2.20.9-0ubuntu7.8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  hadmut 5779 F pulseaudio
  BuildID: 20191021054351
  Channel: Unavailable
  CurrentDesktop: XFCE
  Date: Sun Nov  3 16:20:45 2019
  DefaultProfileExtensions: extensions.sqlite corrupt or missing
  DefaultProfileIncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
  DefaultProfileLocales: extensions.sqlite corrupt or missing
  DefaultProfilePrefErrors: Unexpected character ',' before close parenthesis @ 
/usr/lib/firefox/omni.ja:greprefs.js:930
  DefaultProfilePrefSources: prefs.js
  DefaultProfileThemes: extensions.sqlite corrupt or missing
  ForcedLayersAccel: False
  IfupdownConfig:
   # ifupdown has been replaced by netplan(5) on this system.  See
   # /etc/netplan for current configuration.
   # To re-enable ifupdown on this system, you can run:
   #sudo apt install ifupdown
  InstallationDate: Installed on 2018-06-09 (511 days ago)
  InstallationMedia: Lubuntu 18.04 LTS "Bionic Beaver" - Release amd64 
(20180426)
  Profile0Extensions: extensions.sqlite corrupt or missing
  Profile0IncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
  Profile0Locales: extensions.sqlite corrupt or missing
  Profile0PrefErrors: Unexpected character ',' before close parenthesis @ 
/usr/lib/firefox/omni.ja:greprefs.js:930
  Profile0Themes: extensions.sqlite corrupt or missing
  Profile1Extensions: extensions.sqlite corrupt or missing
  Profile1IncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
  Profile1Locales: extensions.sqlite corrupt or missing
  Profile1PrefErrors: Unexpected character ',' before close parenthesis @ 
/usr/lib/firefox/omni.ja:greprefs.js:930
  Profile1Themes: extensions.sqlite corrupt or missing
  Profile3Extensions: extensions.sqlite corrupt or missing
  Profile3IncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
  Profile3Locales: extensions.sqlite corrupt or missing
  Profile3PrefErrors: Unexpected character ',' before close parenthesis @ 
/usr/lib/firefox/omni.ja:greprefs.js:930
  Profile3PrefSources: prefs.js
  Profile3Themes: extensions.sqlite corrupt or missing
  Profiles:
   Profile3 - LastVersion=69.0.2/20191002193559 (Out of date)
   Profile2 (Default) - LastVersion=70.0/20191021054351 (In use)
   Profile1 - LastVersion=None/None (Out of date)
   Profile0 - LastVersion=None/None (Out of date)
  RunningIncompatibleAddons: False
  SourcePackage: firefox
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/12/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: H61TIW08.111
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: H61H2-TI2
  dmi.board.vendor: Medion
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Medion
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrH61TIW08.111:bd10/12/2012:svnMedion:pnG24:pvr1.0:rvnMedion:rnH61H2-TI2:rvr1.0:cvnMedion:ct3:cvr1.0:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: G24
  dmi.product.version: 1.0
  dmi.sys.vendor: Medion

To

[Desktop-packages] [Bug 1791981] Re: X Server session crash for "No space left on device"

** Tags added: desktop-lts-wishlist

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

Title:
  X Server session crash for "No space left on device"

Status in xorg-server package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu Release: Ubuntu 18.04.1 LTS
  Package version: xserver-xorg: 1:7.7+19ubuntu7.1

  When my laptop resumes after suspend, the desktop session crashes and a new 
one is started. So each time I lose all open applications and unsaved data!
  The expected behavior would be obviously to restore the suspended session.

  I had a look through log files and found that Xorg.0.log ends with the
  following error lines:

  [  6004.019] (II) NVIDIA(0): Setting mode "NULL"
  [  6004.026] (EE) modeset(G0): failed to set mode: No space left on device
  [  6004.026] (EE) 
  Fatal server error:
  [  6004.026] (EE) EnterVT failed for gpu screen 0
  [  6004.027] (EE) 
  [  6004.027] (EE) 
  Please consult the The X.Org Foundation support 
 at http://wiki.x.org
   for help. 
  [  6004.027] (EE) Please also check the log file at "/var/log/Xorg.0.log" for 
additional information.
  [  6004.027] (EE) 
  [  6004.065] (EE) Server terminated with error (1). Closing log file.

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

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

[Desktop-packages] [Bug 1847597] Re: gnome-control-center cannot access google account

The GNOME key expired this week, that's bug #1851564. The issue there is
older so it can't be the same issue

** Changed in: gnome-online-accounts
   Importance: Unknown => Undecided

** Changed in: gnome-online-accounts
 Remote watch: gitlab.gnome.org/GNOME/gnome-online-accounts/issues #42 => None

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

Title:
  gnome-control-center cannot access google account

Status in gnome-online-accounts:
  New
Status in gnome-online-accounts package in Ubuntu:
  Confirmed

Bug description:
  Good morning,

  If I run "gnome-control-center online-accounts" from the terminal and
  trying to add a Google account, I get this error: "Sign in with Google
  is temporarily disabled for this app. This app has not been verified
  yet by Google in order to use Google sign in". On the web, Google
  suggests to contact you, so here I am. Can you fix please? I would use
  my drive folders on my ubuntu 16.04. Thanks in advance.

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-online-accounts/+bug/1847597/+subscriptions

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

[Desktop-packages] [Bug 1851674] Re: All deb packages as being listed as "Proprietary" when opened in gnome-software

Thank you for your bug report, could you a 'journalctl -b 0' log from a
session where you noticed the issue?

** Changed in: gnome-software (Ubuntu)
   Importance: Undecided => Low

** Changed in: gnome-software (Ubuntu)
   Status: New => Incomplete

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

Title:
  All deb packages as being listed as "Proprietary" when opened in
  gnome-software

Status in gnome-software package in Ubuntu:
  Incomplete

Bug description:
  It seems all open-source packages, including for example the official
  package for lshw (https://packages.ubuntu.com/disco/lshw) seem to be
  listed as "Proprietary" in gnome-software/Ubuntu Software. This seems
  to happen from Ubuntu 18.04, with official and 3rd party packages
  (like those from virtualbox.org).

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

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

[Desktop-packages] [Bug 1851520] Re: Online Accounts Cannot Add Gmail Account

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

** This bug has been marked a duplicate of bug 1851564
   Daily Limit Exceeded messages for google calendars

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

Title:
  Online Accounts Cannot Add Gmail Account

Status in webkit2gtk package in Ubuntu:
  Confirmed

Bug description:
  I noticed today that I am unable to create a new GMail account through
  "Online Accounts." The flow happens as expected (username, password,
  2FA) but results in an error:

  "Sign in with Google temporarily disabled for this app

  This app has not been verified yet by Google in order to use Google
  Sign In."

  Issue present on: Pop_OS 19.10, Ubuntu Mate 19.10, Ubuntu 19.10 and
  19.04 and 18.04

  Steps to reproduce:

  1.)Go to Settings -> Online Accounts -> Google
  2.)Enter Username
  3.)Enter Password
  4.)Enter 2FA

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

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

[Desktop-packages] [Bug 1847597] Re: gnome-control-center cannot access google account

2019-11-07 Thread Gunnar Hjalmarsson

** Changed in: gnome-online-accounts (Ubuntu)
   Status: Incomplete => Confirmed

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

Title:
  gnome-control-center cannot access google account

Status in gnome-online-accounts:
  New
Status in gnome-online-accounts package in Ubuntu:
  Confirmed

Bug description:
  Good morning,

  If I run "gnome-control-center online-accounts" from the terminal and
  trying to add a Google account, I get this error: "Sign in with Google
  is temporarily disabled for this app. This app has not been verified
  yet by Google in order to use Google sign in". On the web, Google
  suggests to contact you, so here I am. Can you fix please? I would use
  my drive folders on my ubuntu 16.04. Thanks in advance.

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-online-accounts/+bug/1847597/+subscriptions

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

[Desktop-packages] [Bug 1851621] Re: [snap] No KDE file dialogs

** Attachment added: "eoan-snap-gtkdialog.png"
   
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1851621/+attachment/5303612/+files/eoan-snap-gtkdialog.png

** Changed in: chromium-browser (Ubuntu)
   Status: New => Confirmed

** Changed in: chromium-browser (Ubuntu)
 Assignee: (unassigned) => Olivier Tilloy (osomon)

** Changed in: chromium-browser (Ubuntu)
   Importance: Undecided => Medium

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

Title:
  [snap] No KDE file dialogs

Status in chromium-browser package in Ubuntu:
  Confirmed

Bug description:
  I upgraded from kubuntu 19.04 to 19.10 and noticed that chromium does
  not integrate anymore. Plasma integration Fails to connect to the
  native host (suggested google solutions didn't work), Kubuntu mouse
  pointers change to ugly ones (I bellive GTK fallback), no kde file
  dialog when opening/saving files.

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

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

[Desktop-packages] [Bug 1851621] Re: [snap] No KDE file dialogs

** Attachment added: "bionic-deb-kdialog.png"
   
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1851621/+attachment/5303611/+files/bionic-deb-kdialog.png

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

Title:
  [snap] No KDE file dialogs

Status in chromium-browser package in Ubuntu:
  Confirmed

Bug description:
  I upgraded from kubuntu 19.04 to 19.10 and noticed that chromium does
  not integrate anymore. Plasma integration Fails to connect to the
  native host (suggested google solutions didn't work), Kubuntu mouse
  pointers change to ugly ones (I bellive GTK fallback), no kde file
  dialog when opening/saving files.

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

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

[Desktop-packages] [Bug 1851621] Re: [snap] No KDE file dialogs

For reference, I'm attaching screenshots of a file save dialog in:

 - chromium-browser as a deb package in bionic (kdialog as expected)

 - chromium as a snap in eoan (gtk dialog, not correct)

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

Title:
  [snap] No KDE file dialogs

Status in chromium-browser package in Ubuntu:
  Confirmed

Bug description:
  I upgraded from kubuntu 19.04 to 19.10 and noticed that chromium does
  not integrate anymore. Plasma integration Fails to connect to the
  native host (suggested google solutions didn't work), Kubuntu mouse
  pointers change to ugly ones (I bellive GTK fallback), no kde file
  dialog when opening/saving files.

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

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

[Desktop-packages] [Bug 1847597] Re: gnome-control-center cannot access google account

** Changed in: gnome-online-accounts
   Status: Unknown => New

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

Title:
  gnome-control-center cannot access google account

Status in gnome-online-accounts:
  New
Status in gnome-online-accounts package in Ubuntu:
  Incomplete

Bug description:
  Good morning,

  If I run "gnome-control-center online-accounts" from the terminal and
  trying to add a Google account, I get this error: "Sign in with Google
  is temporarily disabled for this app. This app has not been verified
  yet by Google in order to use Google sign in". On the web, Google
  suggests to contact you, so here I am. Can you fix please? I would use
  my drive folders on my ubuntu 16.04. Thanks in advance.

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-online-accounts/+bug/1847597/+subscriptions

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

[Desktop-packages] [Bug 1851725] [NEW] NetworkManager forgets VPN credentials

2019-11-07 Thread Mathieu Tarral

Public bug reported:

Hi,

Since recently, I can't import a VPN connection in NetworkManager and store my 
credentials.
NetworkManager will systematically forget the password, despite a log entry 
confirming that the operation was a success:

nov. 07 22:26:52  NetworkManager[1518]:   [1573162012.8680]
audit: op="connection-update"
uuid="3f985155-4e20-4351-88d7-14d5909a2d03"
name="at-01.protonvpn.com.udp" args="vpn.secrets" pid=6379 uid=1000
result="success"

Please look at the video attached.

Please fix.

ProblemType: Bug
DistroRelease: Ubuntu 19.10
Package: network-manager 1.20.4-2ubuntu2
ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
Uname: Linux 5.3.0-19-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu8.2
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Thu Nov  7 22:22:00 2019
IfupdownConfig:
 # interfaces(5) file used by ifup(8) and ifdown(8)
 auto lo
 iface lo inet loopback
InstallationDate: Installed on 2019-09-26 (42 days ago)
InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
IpRoute:
 default via 192.168.0.1 dev wlo1 proto dhcp metric 600 
 169.254.0.0/16 dev virbr0 scope link metric 1000 linkdown 
 192.168.0.0/24 dev wlo1 proto kernel scope link src 192.168.0.18 metric 600 
 192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1 linkdown
SourcePackage: network-manager
UpgradeStatus: No upgrade log present (probably fresh install)
nmcli-nm:
 RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  WIFI  
   WWAN-HW  WWAN
 running  1.20.4   connected  started  full  enabled enabled  
enabled  enabled  enabled

** Affects: network-manager (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug eoan

** Attachment added: "NetworkManager forget VPN password"
   
https://bugs.launchpad.net/bugs/1851725/+attachment/5303593/+files/network-manager-vpn-credentials.webm

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

Title:
  NetworkManager forgets VPN credentials

Status in network-manager package in Ubuntu:
  New

Bug description:
  Hi,

  Since recently, I can't import a VPN connection in NetworkManager and store 
my credentials.
  NetworkManager will systematically forget the password, despite a log entry 
confirming that the operation was a success:

  nov. 07 22:26:52  NetworkManager[1518]:   [1573162012.8680]
  audit: op="connection-update"
  uuid="3f985155-4e20-4351-88d7-14d5909a2d03"
  name="at-01.protonvpn.com.udp" args="vpn.secrets" pid=6379 uid=1000
  result="success"

  Please look at the video attached.

  Please fix.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: network-manager 1.20.4-2ubuntu2
  ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
  Uname: Linux 5.3.0-19-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Nov  7 22:22:00 2019
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2019-09-26 (42 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  IpRoute:
   default via 192.168.0.1 dev wlo1 proto dhcp metric 600 
   169.254.0.0/16 dev virbr0 scope link metric 1000 linkdown 
   192.168.0.0/24 dev wlo1 proto kernel scope link src 192.168.0.18 metric 600 
   192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1 
linkdown
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.20.4   connected  started  full  enabled enabled  
enabled  enabled  enabled

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

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

[Desktop-packages] [Bug 1851715] [NEW] Screen brightness adjustment delay

2019-11-07 Thread Phillip Prado

Public bug reported:

Every time I adjust my laptop's screen brightness using the dedicated
brightness keys, there is a substantial delay between when I press the
button and the screen adjusts. Sometimes it even "twitches" and
decreasing the brightness by tapping the button two times will quickly
drop the brightness all the way to the lowest setting after the delay
takes place. I've noticed the issue in the default Ubuntu session and in
my current vanilla gnome-session. It also doesn't matter which
extensions I have installed. The keys work flawlessly in Windows so it
isn't a hardware issue. I have been meaning to report this for a while
and have just never gotten around to it until just now.

ProblemType: Bug
DistroRelease: Ubuntu 19.10
Package: xorg 1:7.7+19ubuntu12
ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
Uname: Linux 5.3.0-19-generic x86_64
ApportVersion: 2.20.11-0ubuntu8.2
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CompositorRunning: None
CurrentDesktop: GNOME
Date: Thu Nov  7 14:37:43 2019
DistUpgraded: 2019-10-21 20:16:37,104 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
DistroCodename: eoan
DistroVariant: ubuntu
DkmsStatus: nvidia, 435.21, 5.3.0-19-generic, x86_64: installed
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA 
controller])
   Subsystem: Huawei Technologies Co., Ltd. UHD Graphics 620 [19e5:3e04]
   Subsystem: Huawei Technologies Co., Ltd. GP108M [GeForce MX150] [19e5:3e04]
InstallationDate: Installed on 2019-09-08 (59 days ago)
InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805)
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 003: ID 05c8:03c0 Cheng Uei Precision Industry Co., Ltd 
(Foxlink) HD Camera
 Bus 001 Device 002: ID 8087:0a2b Intel Corp. 
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: HUAWEI MACH-WX9
ProcEnviron:
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-19-generic 
root=UUID=75fe2138-1abd-47b2-a73f-83280ff782ff ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: Upgraded to eoan on 2019-10-22 (16 days ago)
dmi.bios.date: 03/15/2019
dmi.bios.vendor: HUAWEI
dmi.bios.version: 1.28
dmi.board.name: MACH-WX9-PCB
dmi.board.vendor: HUAWEI
dmi.board.version: M14
dmi.chassis.type: 10
dmi.chassis.vendor: HUAWEI
dmi.chassis.version: M14
dmi.modalias: 
dmi:bvnHUAWEI:bvr1.28:bd03/15/2019:svnHUAWEI:pnMACH-WX9:pvrM14:rvnHUAWEI:rnMACH-WX9-PCB:rvrM14:cvnHUAWEI:ct10:cvrM14:
dmi.product.family: MateBook X
dmi.product.name: MACH-WX9
dmi.product.sku: C128
dmi.product.version: M14
dmi.sys.vendor: HUAWEI
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.99-1ubuntu1
version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.1-1ubuntu1
version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20190815-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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


** Tags: amd64 apport-bug eoan ubuntu

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

Title:
  Screen brightness adjustment delay

Status in xorg package in Ubuntu:
  New

Bug description:
  Every time I adjust my laptop's screen brightness using the dedicated
  brightness keys, there is a substantial delay between when I press the
  button and the screen adjusts. Sometimes it even "twitches" and
  decreasing the brightness by tapping the button two times will quickly
  drop the brightness all the way to the lowest setting after the delay
  takes place. I've noticed the issue in the default Ubuntu session and
  in my current vanilla gnome-session. It also doesn't matter which
  extensions I have installed. The keys work flawlessly in Windows so it
  isn't a hardware issue. I have been meaning to report this for a while
  and have just never gotten around to it until just now.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: xorg 1:7.7+19ubuntu12
  ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
  Uname: Linux 5.3.0-19-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: GNOME
  Date: Thu Nov  7 14:37:43 2019
  DistUpgraded: 2019-10-21 20:16:37,104 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: eoan
  DistroVariant:

[Desktop-packages] [Bug 1851349] Re: Xorg freeze

Status changed to 'Confirmed' because the bug affects multiple users.

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

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

Title:
  Xorg freeze

Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  Installed Ubuntu 19.10. A short freeze or lag occurs with the cursor
  now and then. Problem with multitasking.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: xorg 1:7.7+19ubuntu12
  ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
  Uname: Linux 5.3.0-19-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  BootLog: Error: [Errno 13] Åtkomst nekas: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Nov  5 10:29:50 2019
  DistUpgraded: Fresh install
  DistroCodename: eoan
  DistroVariant: ubuntu
  ExtraDebuggingInterest: No
  GraphicsCard:
   Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA 
controller])
 Subsystem: Dell UHD Graphics 620 [1028:0810]
  InstallationDate: Installed on 2019-10-18 (17 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  MachineType: Dell Inc. Inspiron 5570
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=sv_SE.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-19-generic 
root=UUID=234e65b3-5622-44ae-9ba5-5d8a799fd811 ro quiet splash
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/08/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.0.4
  dmi.board.name: 09YTN7
  dmi.board.vendor: Dell Inc.
  dmi.board.version: X07
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.0.4:bd09/08/2017:svnDellInc.:pnInspiron5570:pvr:rvnDellInc.:rn09YTN7:rvrX07:cvnDellInc.:ct10:cvr:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 5570
  dmi.product.sku: 0810
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.99-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20190815-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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

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

[Desktop-packages] [Bug 1850127] Re: Unable to print with Brother printer since upgrade to Ubuntu 19.10

2019-11-07 Thread Rudolf Leitgeb

I could resolve this issue by upgrading the printer firmware to latest
version 1.40. No idea, why Ubuntu 19.04 printed happily with older
printer firmware, but as of Ubuntu 19.10 new printer firmware (can be
installed through printer web interface) is 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/1850127

Title:
  Unable to print with Brother printer since upgrade to Ubuntu 19.10

Status in cups package in Ubuntu:
  New

Bug description:
  I have recently bought a new color laser printer (Brother HL-
  L8260CDW), which is connected through wLAN. It works like a charm
  under Ubuntu 19.04, but refuses to print since the upgrade to stock
  Ubuntu 19.10. I can reach it via ping and through its HTTP config page
  from the same computer.

  During my collection of relevant bug information I discovered the
  following error messages:

  1. Some print filter was unable to grep 
/etc/cups/ppd/Brother_HL_L8260CDW_series.ppd
  This file was rw for user "root" and r for group "lp", but not accessible 
to others.
  I have made it world readable for testing purposes, but I still can't 
print.

  2. I checked /var/log/syslog for app-armour errors but found none which would 
be related
  to cups and/or printing

  3. After fixing the permission issue, the new error message is "File \'\' not 
found" and
  "Unable to add document to print job.", both of which are too cryptic for 
me to dig
  further into this by myself.

  
  Attached to this bug report I send the following pieces of information:
  - output from "/usr/lib/cups/backend/snmp 10.0.0.14" (snmp.txt)
  - output from "lpinfo -v" (lpinfo.txt)
  - output from "avahi-browse -a -v -t -r" and "avahi-browse -a -v -c -r" 
(avahi.txt)

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: cups 2.2.12-2ubuntu1
  ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
  Uname: Linux 5.3.0-19-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu8
  Architecture: amd64
  CupsErrorLog:
   E [28/Oct/2019:10:40:04 +0100] [Job 112] File \'\' not found
   E [28/Oct/2019:10:40:12 +0100] [Job 112] Unable to add document to print job.
   E [28/Oct/2019:10:45:59 +0100] [Job 113] File \'\' not found
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Oct 28 10:50:05 2019
  InstallationDate: Installed on 2015-11-11 (1446 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  Lpstat: device for Brother_HL_L8260CDW_series: 
implicitclass://Brother_HL_L8260CDW_series/
  MachineType: MSI MS-7982
  Papersize: a4
  PpdFiles: Brother_HL_L8260CDW_series: HL-L8260CDW series - IPP Everywhere
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-19-generic 
root=UUID=64458150-bde5-4ffc-8eb1-038fae855347 ro quiet splash
  SourcePackage: cups
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/08/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 3.10
  dmi.board.asset.tag: Default string
  dmi.board.name: B150M PRO-DH (MS-7982)
  dmi.board.vendor: MSI
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: MSI
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr3.10:bd07/08/2015:svnMSI:pnMS-7982:pvr1.0:rvnMSI:rnB150MPRO-DH(MS-7982):rvr1.0:cvnMSI:ct3:cvr1.0:
  dmi.product.family: Default string
  dmi.product.name: MS-7982
  dmi.product.sku: Default string
  dmi.product.version: 1.0
  dmi.sys.vendor: MSI

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

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

[Desktop-packages] [Bug 1847597] Re: gnome-control-center cannot access google account

2019-11-07 Thread Alan Pope  濾

I have tested with a second google account (my canonical one, as opposed
to my personal one) and get the exact same error.

** Bug watch added: gitlab.gnome.org/GNOME/gnome-online-accounts/issues #42
   https://gitlab.gnome.org/GNOME/gnome-online-accounts/issues/42

** Also affects: gnome-online-accounts via
   https://gitlab.gnome.org/GNOME/gnome-online-accounts/issues/42
   Importance: Unknown
   Status: Unknown

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

Title:
  gnome-control-center cannot access google account

Status in gnome-online-accounts:
  Unknown
Status in gnome-online-accounts package in Ubuntu:
  Incomplete

Bug description:
  Good morning,

  If I run "gnome-control-center online-accounts" from the terminal and
  trying to add a Google account, I get this error: "Sign in with Google
  is temporarily disabled for this app. This app has not been verified
  yet by Google in order to use Google sign in". On the web, Google
  suggests to contact you, so here I am. Can you fix please? I would use
  my drive folders on my ubuntu 16.04. Thanks in advance.

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-online-accounts/+bug/1847597/+subscriptions

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

[Desktop-packages] [Bug 1847597] Re: gnome-control-center cannot access google account

2019-11-07 Thread Alan Pope  濾

I'm seeing the same error.

Steps to reproduce:

Open System Settings
Go to Online Accounts
Add a google account
Enter username / password

I then get the same dialog as the reporter of this bug.

I'm on Ubuntu 19.10.

This smacks of our online accounts api key being revoked / rate-limited
or otherwise restricted by Google.

** Attachment added: "Screenshot from 2019-11-07 20-13-19.png"

https://bugs.launchpad.net/ubuntu/+source/gnome-online-accounts/+bug/1847597/+attachment/5303569/+files/Screenshot%20from%202019-11-07%2020-13-19.png

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

Title:
gnome-control-center cannot access google account

Status in gnome-online-accounts:
Unknown
Status in gnome-online-accounts package in Ubuntu:
Incomplete

Bug description:
Good morning,

If I run "gnome-control-center online-accounts" from the terminal and
trying to add a Google account, I get this error: "Sign in with Google
is temporarily disabled for this app. This app has not been verified
yet by Google in order to use Google sign in". On the web, Google
suggests to contact you, so here I am. Can you fix please? I would use
my drive folders on my ubuntu 16.04. Thanks in advance.

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-online-accounts/+bug/1847597/+subscriptions

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

[Desktop-packages] [Bug 1844739] Re: Latest Firefox update freezing my system

2019-11-07 Thread paz

Yes, freeze from time to time and the all system freezing with it.
alt+f+prinscreen (oom killer) or hard reboot are the only options to go back 
from it.
My suspect is multi processes by default but I'm just guessing.

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

Title:
  Latest Firefox update freezing my system

Status in firefox package in Ubuntu:
  Incomplete

Bug description:
  The latest updates of firefox renders my machine useless. I'm sending
  it as is hopefully before it freezes completely.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: firefox 69.0+build2-0ubuntu0.18.04.1
  ProcVersionSignature: Ubuntu 4.15.0-62.69-generic 4.15.18
  Uname: Linux 4.15.0-62-generic i686
  NonfreeKernelModules: nvidia
  ApportVersion: 2.20.9-0ubuntu7.7
  Architecture: i386
  BuildID: 20190828152935
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Sep 20 01:22:17 2019
  DefaultProfileExtensions: extensions.sqlite corrupt or missing
  DefaultProfileIncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
  DefaultProfileLocales: extensions.sqlite corrupt or missing
  DefaultProfilePrefErrors: Unexpected character ',' before close parenthesis @ 
/usr/lib/firefox/omni.ja:greprefs.js:997
  DefaultProfileThemes: extensions.sqlite corrupt or missing
  InstallationDate: Installed on 2018-05-01 (506 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release i386 (20170412)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US
   SHELL=/bin/bash
  Profiles:
   Profile1 (Default) - LastVersion=None/None (Out of date)
   Profile0 - LastVersion=69.0/20190828152935 (In use)
  SourcePackage: firefox
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1851698] [NEW] firefox crash when opened

2019-11-07 Thread Chris

Public bug reported:

i was using "mailspring", and confirming a subscription to tfir by clicking the 
confirm link in the email they sent. upon clicking the confirm link, firefox 
opened. then after clicking the "verify humanity" button and hitting confirm 
(on the page now open in firefox), that is when the crash happened. 
 I then ran "sudo ubuntu-bug firefox"
 i i can provide any more information, please let me know.
dps

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: firefox 70.0+build2-0ubuntu0.18.04.1
ProcVersionSignature: Ubuntu 5.0.0-32.34~18.04.2-generic 5.0.21
Uname: Linux 5.0.0-32-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia wl
ApportVersion: 2.20.9-0ubuntu7.9
Architecture: amd64
BuildID: 20191021054351
Date: Thu Nov  7 13:22:45 2019
DefaultProfileExtensions: extensions.sqlite corrupt or missing
DefaultProfileIncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
DefaultProfileLocales: extensions.sqlite corrupt or missing
DefaultProfilePrefErrors: Unexpected character ',' before close parenthesis @ 
/usr/lib/firefox/omni.ja:greprefs.js:930
DefaultProfileThemes: extensions.sqlite corrupt or missing
InstallationDate: Installed on 2019-10-23 (15 days ago)
InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210)
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
Profiles:
 Profile1 (Default) - LastVersion=None/None (Out of date)
 Profile0 - LastVersion=70.0/20191021054351
SourcePackage: firefox
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug bionic

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

Title:
  firefox crash when opened

Status in firefox package in Ubuntu:
  New

Bug description:
  i was using "mailspring", and confirming a subscription to tfir by clicking 
the confirm link in the email they sent. upon clicking the confirm link, 
firefox opened. then after clicking the "verify humanity" button and hitting 
confirm (on the page now open in firefox), that is when the crash happened. 
   I then ran "sudo ubuntu-bug firefox"
   i i can provide any more information, please let me know.
  dps

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: firefox 70.0+build2-0ubuntu0.18.04.1
  ProcVersionSignature: Ubuntu 5.0.0-32.34~18.04.2-generic 5.0.21
  Uname: Linux 5.0.0-32-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia wl
  ApportVersion: 2.20.9-0ubuntu7.9
  Architecture: amd64
  BuildID: 20191021054351
  Date: Thu Nov  7 13:22:45 2019
  DefaultProfileExtensions: extensions.sqlite corrupt or missing
  DefaultProfileIncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
  DefaultProfileLocales: extensions.sqlite corrupt or missing
  DefaultProfilePrefErrors: Unexpected character ',' before close parenthesis @ 
/usr/lib/firefox/omni.ja:greprefs.js:930
  DefaultProfileThemes: extensions.sqlite corrupt or missing
  InstallationDate: Installed on 2019-10-23 (15 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  Profiles:
   Profile1 (Default) - LastVersion=None/None (Out of date)
   Profile0 - LastVersion=70.0/20191021054351
  SourcePackage: firefox
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1850969] Re: x11 session all mouse or keyboard action ignored

2019-11-07 Thread corrado venturini

Problem disappeared after last upgrade:
Start-Date: 2019-11-07  17:28:08
Commandline: apt upgrade
Requested-By: corrado (1000)
Upgrade: gir1.2-mutter-5:amd64 (3.34.1+git20191022-2ubuntu1, 
3.34.1+git20191107-1ubuntu1), libmutter-5-0:amd64 (3.34.1+git20191022-2ubuntu1, 
3.34.1+git20191107-1ubuntu1), mutter-common:amd64 (3.34.1+git20191022-2ubuntu1, 
3.34.1+git20191107-1ubuntu1), mutter:amd64 (3.34.1+git20191022-2ubuntu1, 
3.34.1+git20191107-1ubuntu1)
End-Date: 2019-11-07  17:28:15

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

Title:
  x11 session all mouse or keyboard action ignored

Status in GNOME Shell:
  Fix Released
Status in gnome-shell package in Ubuntu:
  In Progress

Bug description:
  Starting with x1 session all mouse or keyboard action are ignored. Only mouse 
arrow moves on the desktop.
  was able to exit only with cntrl+alt+f3
  wayland session works fine.
  Also booting from USB live and selecting 'try ubuntu' has the same problem.
  selecting install the install run smoothly but the just installed system has 
the problem.

  same problem with ISO dated 20191030 20191031 20191101 and 20191021
  after update+upgrade

  corrado@corrado-p13-ff-1101:~/Desktop$ inxi -Fx
  System:Host: corrado-p13-ff-1101 Kernel: 5.3.0-18-generic x86_64 bits: 64 
compiler: gcc v: 9.2.1 Desktop: Gnome 3.34.1 
 Distro: Ubuntu 20.04 LTS (Focal Fossa) 
  Machine:   Type: Desktop Mobo: ASRock model: H110M-G/M.2 serial:  UEFI: American Megatrends v: P1.10 
 date: 05/11/2017 
  CPU:   Topology: Dual Core model: Intel Core i3-7100 bits: 64 type: MT 
MCP arch: Kaby Lake rev: 9 L2 cache: 3072 KiB 
 flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx 
bogomips: 31199 
 Speed: 801 MHz min/max: 800/3900 MHz Core speeds (MHz): 1: 800 2: 
800 3: 800 4: 800 
  Graphics:  Device-1: Intel HD Graphics 630 vendor: ASRock driver: i915 v: 
kernel bus ID: 00:02.0 
 Display: wayland server: X.Org 1.20.5 driver: i915 resolution: 
1920x1080~60Hz 
 OpenGL: renderer: Mesa DRI Intel HD Graphics 630 (Kaby Lake GT2) 
v: 4.5 Mesa 19.2.1 direct render: Yes 
  Audio: Device-1: Intel 100 Series/C230 Series Family HD Audio vendor: 
ASRock driver: snd_hda_intel v: kernel 
 bus ID: 00:1f.3 
 Sound Server: ALSA v: k5.3.0-18-generic 
  Network:   Device-1: Intel Ethernet I219-V vendor: ASRock driver: e1000e v: 
3.2.6-k port: f040 bus ID: 00:1f.6 
 IF: enp0s31f6 state: up speed: 100 Mbps duplex: full mac: 
70:85:c2:44:7b:86 
  Drives:Local Storage: total: 931.51 GiB used: 4.87 GiB (0.5%) 
 ID-1: /dev/sda vendor: Toshiba model: DT01ACA100 size: 931.51 GiB 
temp: 34 C 
  Partition: ID-1: / size: 15.62 GiB used: 4.87 GiB (31.2%) fs: ext4 dev: 
/dev/sda13 
 ID-2: swap-1 size: 8.00 GiB used: 0 KiB (0.0%) fs: swap dev: 
/dev/sda2 
  Sensors:   System Temperatures: cpu: 38.5 C mobo: N/A 
 Fan Speeds (RPM): N/A 
  Info:  Processes: 205 Uptime: 16m Memory: 7.49 GiB used: 1.11 GiB (14.8%) 
Init: systemd runlevel: 5 Compilers: 
 gcc: 9.2.1 Shell: bash v: 5.0.3 inxi: 3.0.36 
  corrado@corrado-p13-ff-1101:~/Desktop$

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu12
  ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1
  Uname: Linux 5.3.0-18-generic x86_64
  ApportVersion: 2.20.11-0ubuntu9
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Nov  1 18:13:53 2019
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation HD Graphics 630 [8086:5912] (rev 04) (prog-if 00 [VGA 
controller])
 Subsystem: ASRock Incorporation HD Graphics 630 [1849:5912]
  InstallationDate: Installed on 2019-11-01 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20191101)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 046d:c016 Logitech, Inc. Optical Wheel Mouse
   Bus 001 Device 002: ID 058f:6377 Alcor Micro Corp. AU6375 4-LUN card reader
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-18-generic 
root=UUID=062c7ec4-2948-49df-934f-d054f397e4c4 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/11/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P1.10
  dmi.board.name: H110M-G/M.2
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By

[Desktop-packages] [Bug 1851518] Re: [950SBE/951SBE, Realtek ALC298, Speaker, Internal] No sound on internal speakers, very very quiet on headphones

2019-11-07 Thread Filipe Garrett

I have a very similar issue with another Samsung laptop:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1850702

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

Title:
  [950SBE/951SBE, Realtek ALC298, Speaker, Internal] No sound on
  internal speakers, very very quiet on headphones

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  I've been googling this issue for 10's of hours and tried many things.

  Relase of Ubuntu: 19.10

  Expected outcome: Music plays on the internal speakers and headphones.

  Actual outcome: I can barely hear audio using headphones with volume
  turned up to 150%.  Absolutely nothing comes out of the speakers. (The
  speakers sound great under Windows 10.)

  Complete alsa-info output is attached, but here are some snippets:

  !!DMI Information
  !!---

  Manufacturer:  SAMSUNG ELECTRONICS CO., LTD.
  Product Name:  950SBE/951SBE
  Product Version:   P06RES
  Firmware Version:  P06RES.075.190529.SP
  Board Vendor:  SAMSUNG ELECTRONICS CO., LTD.
  Board Name:NP950SBE-K01US

  
  !!Kernel Information
  !!--

  Kernel release:5.3.0-19-generic
  Operating System:  GNU/Linux
  Architecture:  x86_64
  Processor: x86_64
  SMP Enabled:   Yes


  !!ALSA Version
  !!

  Driver version: k5.3.0-19-generic
  Library version:1.1.9
  Utilities version:  1.1.9

  
  !!Loaded ALSA modules
  !!---

  snd_hda_intel

  
  !!Sound Servers on this system
  !!

  Pulseaudio:
Installed - Yes (/usr/bin/pulseaudio)
Running - Yes

  
  !!Soundcards recognised by ALSA
  !!-

   0 [PCH]: HDA-Intel - HDA Intel PCH
HDA Intel PCH at 0x604b118000 irq 177

  
  !!PCI Soundcards installed in the system
  !!--

  00:1f.3 Multimedia audio controller: Intel Corporation Cannon Point-LP
  High Definition Audio Controller (rev 11)

  
  !!Advanced information - PCI Vendor/Device/Subsystem ID's
  !!---

  00:1f.3 0401: 8086:9dc8 (rev 11)
  DeviceName: Onboard - Sound

  
  !!HDA-Intel Codec information
  !!---
  --startcollapse--

  Codec: Realtek ALC298
  Address: 0
  AFG Function Id: 0x1 (unsol 1)
  Vendor Id: 0x10ec0298
  Subsystem Id: 0x144dc812
  Revision Id: 0x100103
  No Modem Function Group found
  Default PCM:
  rates [0x60]: 44100 48000
  bits [0xe]: 16 20 24
  formats [0x1]: PCM
  Default Amp-In caps: N/A
  Default Amp-Out caps: N/A
  State of AFG node 0x01:
Power states:  D0 D1 D2 D3 D3cold CLKSTOP EPSS
Power: setting=D0, actual=D0
  GPIO: io=8, o=0, i=0, unsolicited=1, wake=0
IO[0]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0
IO[1]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0
IO[2]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0
IO[3]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0
IO[4]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0
IO[5]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0
IO[6]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0
IO[7]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0
  Node 0x02 [Audio Output] wcaps 0x41d: Stereo Amp-Out
Control: name="Headphone Playback Volume", index=0, device=0
  ControlAmp: chs=3, dir=Out, idx=0, ofs=0
Device: name="ALC298 Analog", type="Audio", device=0
Amp-Out caps: ofs=0x7f, nsteps=0x7f, stepsize=0x01, mute=0
Amp-Out vals:  [0x00 0x00]
Converter: stream=1, channel=0
PCM:
  rates [0x60]: 44100 48000
  bits [0xe]: 16 20 24
  formats [0x1]: PCM
Power states:  D0 D1 D2 D3 EPSS
Power: setting=D0, actual=D0
  Node 0x03 [Audio Output] wcaps 0x41d: Stereo Amp-Out
Control: name="Speaker Playback Volume", index=0, device=0
  ControlAmp: chs=3, dir=Out, idx=0, ofs=0
Amp-Out caps: ofs=0x7f, nsteps=0x7f, stepsize=0x01, mute=0
Amp-Out vals:  [0x7f 0x7f]
Converter: stream=1, channel=0

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
  Uname: Linux 5.3.0-19-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  martin 1383 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Nov  6 06:20:08 2019
  InstallationDate: Installed on 2019-11-03 (3 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio

[Desktop-packages] [Bug 1849249] Re: gnome-shell crashed with SIGABRT: mutter:ERROR:../src/core/window.c:4841:set_workspace_state: assertion failed: (workspace == NULL)

2019-11-07 Thread Rocko

I just discovered that on my laptop this bug only applies to X11
sessions, not to Wayland sessions.

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

Title:
  gnome-shell crashed with SIGABRT:
  mutter:ERROR:../src/core/window.c:4841:set_workspace_state: assertion
  failed: (workspace == NULL)

Status in gnome-shell package in Ubuntu:
  Confirmed

Bug description:
  https://errors.ubuntu.com/problem/8317377ffa8b8148baa481d490fd876111eb3c4b

  gnome-shell crashes with this bug every time that:

  * I am editing a file in geany
  * I open the Find window (CTRL-F) and it opens on another monitor
  * I type in some text in the find window and press ENTER (or click the Next 
button)

  Note especially that the find window must be on the other monitor - if
  it's on the same monitor as geany, gnome-shell doesn't crash.

  (Note: I originally thought that if I moved the find window to the
  other window and then searched, gnome-shell crashed, but I think what
  happens is a) I open the window, b) I move it, search for something,
  and it works, c) I close it and re-open it - it then opens on the
  other monitor and searching will crash gnome-shell.)

  gnome-shell restarts, but the crash causes data loss, as most of the
  running applications don't reappear when it restarts.

  In case it's relevant, I have a laptop screen set at 2048x1152 and an
  external monitor configured to be above it at 2560x1440.

  ProblemType: Crash
  DistroRelease: Ubuntu 19.10
  Package: gnome-shell 3.34.1-1ubuntu1
  Uname: Linux 5.4.0-050400rc4-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Oct 22 10:37:36 2019
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  ExecutableTimestamp: 1570619894
  InstallationDate: Installed on 2019-07-01 (112 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190606)
  ProcCmdline: /usr/bin/gnome-shell
  ProcCwd: /home/rocko
  ProcEnviron:
   LANG=en_AU.UTF-8
   LANGUAGE=en_AU:en
   PATH=(custom, no user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  RelatedPackageVersions: mutter-common 3.34.1-1ubuntu1
  Signal: 6
  SourcePackage: gnome-shell
  StacktraceTop:
   () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_assertion_message_expr () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
   () at /lib/x86_64-linux-gnu/libmutter-5.so.0
   () at /lib/x86_64-linux-gnu/libmutter-5.so.0
   () at /lib/x86_64-linux-gnu/libmutter-5.so.0
  Title: gnome-shell crashed with SIGABRT
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: sudo
  separator:

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

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

[Desktop-packages] [Bug 1791981] Re: X Server session crash for "No space left on device"

2019-11-07 Thread Ben Echols

This is happening to me right now (On Ubuntu 19.10, kernel 5.3.0 and
5.3.9, nvidia drivers version 435 and 440)


It only happens when using nvidia GPU. If I prime-select my intel GPU then 
there is no issue.

It seems related to the laptop display being on some internal display
port that gets disconnected when the lid is closed.

If I type 'systemctl suspend' before closing my lid everything works
fine when I open.

I suspect this is actually a bug in nvidia drivers and not in xorg-
server

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

Title:
  X Server session crash for "No space left on device"

Status in xorg-server package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu Release: Ubuntu 18.04.1 LTS
  Package version: xserver-xorg: 1:7.7+19ubuntu7.1

  When my laptop resumes after suspend, the desktop session crashes and a new 
one is started. So each time I lose all open applications and unsaved data!
  The expected behavior would be obviously to restore the suspended session.

  I had a look through log files and found that Xorg.0.log ends with the
  following error lines:

  [  6004.019] (II) NVIDIA(0): Setting mode "NULL"
  [  6004.026] (EE) modeset(G0): failed to set mode: No space left on device
  [  6004.026] (EE) 
  Fatal server error:
  [  6004.026] (EE) EnterVT failed for gpu screen 0
  [  6004.027] (EE) 
  [  6004.027] (EE) 
  Please consult the The X.Org Foundation support 
 at http://wiki.x.org
   for help. 
  [  6004.027] (EE) Please also check the log file at "/var/log/Xorg.0.log" for 
additional information.
  [  6004.027] (EE) 
  [  6004.065] (EE) Server terminated with error (1). Closing log file.

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

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

[Desktop-packages] [Bug 1851674] [NEW] All deb packages as being listed as "Proprietary" when opened in gnome-software

2019-11-07 Thread Hamish McIntyre-Bhatty

Public bug reported:

It seems all open-source packages, including for example the official
package for lshw (https://packages.ubuntu.com/disco/lshw) seem to be
listed as "Proprietary" in gnome-software/Ubuntu Software. This seems to
happen from Ubuntu 18.04, with official and 3rd party packages (like
those from virtualbox.org).

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

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

Title:
  All deb packages as being listed as "Proprietary" when opened in
  gnome-software

Status in gnome-software package in Ubuntu:
  New

Bug description:
  It seems all open-source packages, including for example the official
  package for lshw (https://packages.ubuntu.com/disco/lshw) seem to be
  listed as "Proprietary" in gnome-software/Ubuntu Software. This seems
  to happen from Ubuntu 18.04, with official and 3rd party packages
  (like those from virtualbox.org).

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

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

[Desktop-packages] [Bug 1851672] [NEW] gnome-control-centre does not open, even from terminal - segmentation fault

2019-11-07 Thread Jacob Quibell

Public bug reported:

Ubuntu 19.10

gnome-control-center:
  Installed: 1:3.34.1-1ubuntu2pop1~1571679625~19.10~ef2ab1f
  Candidate: 1:3.34.1-1ubuntu2pop1~1571679625~19.10~ef2ab1f
  Version table:
 *** 1:3.34.1-1ubuntu2pop1~1571679625~19.10~ef2ab1f 500
500 http://ppa.launchpad.net/system76/pop/ubuntu eoan/main amd64 
Packages
100 /var/lib/dpkg/status
 1:3.34.1-1ubuntu2 500
500 http://gb.archive.ubuntu.com/ubuntu eoan/main amd64 Packages


For bug reporting instructions, please see:
.
Find the GDB manual and other documentation resources online at:
.

For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from gnome-control-center...
(No debugging symbols found in gnome-control-center)
(gdb) run
Starting program: /usr/bin/gnome-control-center 
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[New Thread 0x7fffea25c700 (LWP 13902)]
[New Thread 0x7fffe9a5b700 (LWP 13903)]
[New Thread 0x7fffe3fff700 (LWP 13906)]
[New Thread 0x7fffe36c5700 (LWP 13907)]
[New Thread 0x7fffe2ec4700 (LWP 13908)]
[New Thread 0x7fffe266d700 (LWP 13910)]

Thread 1 "gnome-control-c" received signal SIGSEGV, Segmentation fault.
0x776bae1e in gtk_container_add ()
   from /lib/x86_64-linux-gnu/libgtk-3.so.0
(gdb)

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

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

Title:
  gnome-control-centre does not open, even from terminal - segmentation
  fault

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

Bug description:
  Ubuntu 19.10

  gnome-control-center:
Installed: 1:3.34.1-1ubuntu2pop1~1571679625~19.10~ef2ab1f
Candidate: 1:3.34.1-1ubuntu2pop1~1571679625~19.10~ef2ab1f
Version table:
   *** 1:3.34.1-1ubuntu2pop1~1571679625~19.10~ef2ab1f 500
  500 http://ppa.launchpad.net/system76/pop/ubuntu eoan/main amd64 
Packages
  100 /var/lib/dpkg/status
   1:3.34.1-1ubuntu2 500
  500 http://gb.archive.ubuntu.com/ubuntu eoan/main amd64 Packages

  
  For bug reporting instructions, please see:
  .
  Find the GDB manual and other documentation resources online at:
  .

  For help, type "help".
  Type "apropos word" to search for commands related to "word"...
  Reading symbols from gnome-control-center...
  (No debugging symbols found in gnome-control-center)
  (gdb) run
  Starting program: /usr/bin/gnome-control-center 
  [Thread debugging using libthread_db enabled]
  Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
  [New Thread 0x7fffea25c700 (LWP 13902)]
  [New Thread 0x7fffe9a5b700 (LWP 13903)]
  [New Thread 0x7fffe3fff700 (LWP 13906)]
  [New Thread 0x7fffe36c5700 (LWP 13907)]
  [New Thread 0x7fffe2ec4700 (LWP 13908)]
  [New Thread 0x7fffe266d700 (LWP 13910)]

  Thread 1 "gnome-control-c" received signal SIGSEGV, Segmentation fault.
  0x776bae1e in gtk_container_add ()
 from /lib/x86_64-linux-gnu/libgtk-3.so.0
  (gdb)

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

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

[Desktop-packages] [Bug 1851672] Re: gnome-control-centre does not open, even from terminal - segmentation fault

2019-11-07 Thread Jacob Quibell

already tried in terminal with no luck

sudo apt purge gnome-contol-center
sudo apt auotremove
sudo apt install gnome-control-center

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

Title:
  gnome-control-centre does not open, even from terminal - segmentation
  fault

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

Bug description:
  Ubuntu 19.10

  gnome-control-center:
Installed: 1:3.34.1-1ubuntu2pop1~1571679625~19.10~ef2ab1f
Candidate: 1:3.34.1-1ubuntu2pop1~1571679625~19.10~ef2ab1f
Version table:
   *** 1:3.34.1-1ubuntu2pop1~1571679625~19.10~ef2ab1f 500
  500 http://ppa.launchpad.net/system76/pop/ubuntu eoan/main amd64 
Packages
  100 /var/lib/dpkg/status
   1:3.34.1-1ubuntu2 500
  500 http://gb.archive.ubuntu.com/ubuntu eoan/main amd64 Packages

  
  For bug reporting instructions, please see:
  .
  Find the GDB manual and other documentation resources online at:
  .

  For help, type "help".
  Type "apropos word" to search for commands related to "word"...
  Reading symbols from gnome-control-center...
  (No debugging symbols found in gnome-control-center)
  (gdb) run
  Starting program: /usr/bin/gnome-control-center 
  [Thread debugging using libthread_db enabled]
  Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
  [New Thread 0x7fffea25c700 (LWP 13902)]
  [New Thread 0x7fffe9a5b700 (LWP 13903)]
  [New Thread 0x7fffe3fff700 (LWP 13906)]
  [New Thread 0x7fffe36c5700 (LWP 13907)]
  [New Thread 0x7fffe2ec4700 (LWP 13908)]
  [New Thread 0x7fffe266d700 (LWP 13910)]

  Thread 1 "gnome-control-c" received signal SIGSEGV, Segmentation fault.
  0x776bae1e in gtk_container_add ()
 from /lib/x86_64-linux-gnu/libgtk-3.so.0
  (gdb)

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

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

[Desktop-packages] [Bug 1847979] Re: package xserver-xorg-video-nvidia-430 430.26-0ubuntu0.18.04.2 failed to install/upgrade: trying to overwrite '/usr/share/X11/xorg.conf.d/10-nvidia.conf', which is

2019-11-07 Thread Shih-Yuan Lee

** Changed in: oem-priority
   Status: In Progress => Fix Released

** Changed in: oem-priority
 Assignee: Shih-Yuan Lee (fourdollars) => (unassigned)

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

Title:
  package xserver-xorg-video-nvidia-430 430.26-0ubuntu0.18.04.2 failed
  to install/upgrade: trying to overwrite
  '/usr/share/X11/xorg.conf.d/10-nvidia.conf', which is also in package
  xserver-xorg-video-nvidia-418 418.74-0ubuntu0~18.04.1

Status in OEM Priority Project:
  Fix Released
Status in nvidia-graphics-drivers-430 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-435 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-430 source package in Bionic:
  Fix Released
Status in nvidia-graphics-drivers-435 source package in Bionic:
  Fix Released

Bug description:
  There is some problem when upgrading NVIDIA graphics driver from 418
  to 430.

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: xserver-xorg-video-nvidia-430 430.26-0ubuntu0.18.04.2
  ProcVersionSignature: Ubuntu 5.0.0-1024.27-oem-osp1 5.0.21
  Uname: Linux 5.0.0-1024-oem-osp1 x86_64
  ApportVersion: 2.20.9-0ubuntu7.7
  Architecture: amd64
  Date: Mon Oct 14 04:57:53 2019
  Dependencies:
   gcc-8-base 8.3.0-6ubuntu1~18.04.1
   libc6 2.27-3ubuntu1
   libgcc1 1:8.3.0-6ubuntu1~18.04.1
   libnvidia-cfg1-430 430.26-0ubuntu0.18.04.2
  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-bionic-amd64-20190418-59+beaver-osp1-worm+X09
  DuplicateSignature:
   package:xserver-xorg-video-nvidia-430:430.26-0ubuntu0.18.04.2
   Unpacking xserver-xorg-video-nvidia-430 (430.26-0ubuntu0.18.04.2) ...
   dpkg: error processing archive 
/tmp/apt-dpkg-install-WH1Eoi/29-xserver-xorg-video-nvidia-430_430.26-0ubuntu0.18.04.2_amd64.deb
 (--unpack):
trying to overwrite '/usr/share/X11/xorg.conf.d/10-nvidia.conf', which is 
also in package xserver-xorg-video-nvidia-418 418.74-0ubuntu0~18.04.1
  ErrorMessage: trying to overwrite 
'/usr/share/X11/xorg.conf.d/10-nvidia.conf', which is also in package 
xserver-xorg-video-nvidia-418 418.74-0ubuntu0~18.04.1
  InstallationDate: Installed on 2019-10-14 (0 days ago)
  InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 
20190418-12:10
  Python3Details: /usr/bin/python3.6, Python 3.6.8, python3-minimal, 
3.6.7-1~18.04
  PythonDetails: /usr/bin/python2.7, Python 2.7.15+, python-minimal, 
2.7.15~rc1-1
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu2.3
   apt  1.6.12
  SourcePackage: nvidia-graphics-drivers-430
  Title: package xserver-xorg-video-nvidia-430 430.26-0ubuntu0.18.04.2 failed 
to install/upgrade: trying to overwrite 
'/usr/share/X11/xorg.conf.d/10-nvidia.conf', which is also in package 
xserver-xorg-video-nvidia-418 418.74-0ubuntu0~18.04.1
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1847979/+subscriptions

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

[Desktop-packages] [Bug 1851666] [NEW] In Ubuntu 19.10 when I runs dosbox 0.74, left hand side items of unity favourites are visible with a faded shadow.

2019-11-07 Thread Girish Sharma

Public bug reported:

When I runs dosbox 0.74 in fullscreen mode, unity items are visible in a
disabled mode and screen becomes confusing too.

ProblemType: Bug
DistroRelease: Ubuntu 19.10
Package: gnome-terminal 3.34.0-1ubuntu2
ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
Uname: Linux 5.3.0-19-generic x86_64
ApportVersion: 2.20.11-0ubuntu8.2
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Thu Nov  7 20:52:48 2019
ExecutablePath: /usr/libexec/gnome-terminal-server
InstallationDate: Installed on 2017-11-08 (729 days ago)
InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801)
ProcEnviron:
 LANG=en_IN
 LANGUAGE=en_IN:en
 PATH=(custom, user)
 SHELL=/bin/bash
 XDG_RUNTIME_DIR=
SourcePackage: gnome-terminal
UpgradeStatus: Upgraded to eoan on 2019-11-06 (0 days ago)

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


** Tags: amd64 apport-bug eoan

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

Title:
  In Ubuntu 19.10 when I runs dosbox 0.74, left hand side items of unity
  favourites are visible with a faded shadow.

Status in gnome-terminal package in Ubuntu:
  New

Bug description:
  When I runs dosbox 0.74 in fullscreen mode, unity items are visible in
  a disabled mode and screen becomes confusing too.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: gnome-terminal 3.34.0-1ubuntu2
  ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
  Uname: Linux 5.3.0-19-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Nov  7 20:52:48 2019
  ExecutablePath: /usr/libexec/gnome-terminal-server
  InstallationDate: Installed on 2017-11-08 (729 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  ProcEnviron:
   LANG=en_IN
   LANGUAGE=en_IN:en
   PATH=(custom, user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  SourcePackage: gnome-terminal
  UpgradeStatus: Upgraded to eoan on 2019-11-06 (0 days ago)

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

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

[Desktop-packages] [Bug 1850282] Re: snap cannot be run while being upgraded − no user feedback

2019-11-07 Thread Simon Lambourn

Thank you Olivier.   Yes, I forgot that I should have named "chromium-
browser" rather than "chromium" when submitting the bug report.

I agree that there could have been problems when upgrading the old
chromium browser using apt, but when using apt, the upgrade is user-
initiated, and the user is informed that chromium is going to be
upgraded.  What makes the situation worse with the snap, is that as far
as I recall, the upgrade happens without user knowledge or involvement.
I don't recall being prompted to upgrade anything, it just seemed to
happen automatically and invisibly, until I couldn't access my browser.
It's the lack of info to the user that makes this particularly annoying.

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

Title:
  snap cannot be run while being upgraded − no user feedback

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

Bug description:
  I've just upgraded to Ubuntu 19.10 with the new snap version of
  Chromium a week or two ago

  On starting my system today, I found that Chromium had disappeared
  from the launcher and wasn't even in the apps list.   using the
  command 'chromium' didn't work either, giving me the message that
  chromium wasn't installed.   "You can install it using snap install
  chromium".  Then when I try to install it, I get the message "chromium
  is already installed".

  After about 10 minutes of digging around, I discovered that the
  chromium snap was disabled.  I couldn't enable it because it was being
  refreshed.

  Come on!  this is unacceptable behaviour for any tool but especially a
  browser which must be one of the most heavily used applications on
  Ubuntu.  This will really hit the reputation of ubuntu with any user
  who has to take maybe more than 10 minutes to discover the problem, or
  may never discover it - Chromium may just mysteriously reappear some
  time later.

  Desired behaviour:   Never disappear.  Allow refresh to happen under the 
covers, transparently (as it used to with apt).
  Minimally acceptable behaviour: never disappear, but display a message 
"chromium is being refreshed.  Please try later".

  $ snap info chromium
  name:  chromium
  summary:   Chromium web browser, open-source version of Chrome
  publisher: Canonical✓
  contact:   
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bugs?field.tag=snap
  license:   unset
  description: |
An open-source browser project that aims to build a safer, faster, and more
stable way for all Internet users to experience the web.
  commands:
- chromium.chromedriver
- chromium
  snap-id:  XKEcBqPM06H1Z7zGOdG5fbICuf8NWK5R
  tracking: stable
  channels:
stable:78.0.3904.70 2019-10-29 (920) 160MB -
candidate: 78.0.3904.70 2019-10-29 (920) 160MB -
beta:  78.0.3904.70 2019-10-22 (907) 165MB -
edge:  79.0.3941.4  2019-10-21 (905) 159MB -
  installed:   78.0.3904.70(917) 167MB disabled

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

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

[Desktop-packages] [Bug 1850081] Re: Folder pane text overflows

Launchpad has imported 1 comments from the remote bug at
https://bugzilla.mozilla.org/show_bug.cgi?id=1594723.

If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help.launchpad.net/InterBugTracking.


On 2019-11-07T14:28:47+00:00 Rowan-8 wrote:

Created attachment 9107186
Screenshot_20191028_213026.jpeg

User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:72.0) Gecko/20100101
Firefox/72.0

Steps to reproduce:

After upgrading to Kubuntu 19.10 I noticed the text in the folder pane
overflows which hides the unread count, it appears as if the text is
behind the scrollbar. The Ubuntu package maintainers can replicate the
problem in the upstream build.

See attached screenshot and launchpad details here
https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1850081

Reply at:
https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1850081/comments/16


** Changed in: thunderbird
   Status: Unknown => New

** Changed in: thunderbird
   Importance: Unknown => Medium

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

Title:
  Folder pane text overflows

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

Bug description:
  After upgrading to Kubuntu 19.10 I noticed the text in the folder pane 
overflows which hides the unread count, it appears as if the text is behind the 
scrollbar.
  --- 
  ProblemType: Bug
  AddonCompatCheckDisabled: False
  ApportVersion: 2.20.11-0ubuntu8
  Architecture: amd64
  AudioDevicesInUse:
   USER PID ACCESS COMMAND
   /dev/snd/controlC1:  rowan  2237 F pulseaudio
   /dev/snd/controlC0:  rowan  2237 F pulseaudio
  BuildID: 20191010144232
  Channel: Unavailable
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 19.10
  Extensions: extensions.sqlite corrupt or missing
  ForcedLayersAccel: False
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  IncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
  InstallationDate: Installed on 2018-11-19 (343 days ago)
  InstallationMedia: Kubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.2)
  Locales: extensions.sqlite corrupt or missing
  MostRecentCrashID: bp-6abdd954-b5ad-4d9d-a828-9824b0180710
  Package: thunderbird 1:68.1.2+build1-0ubuntu1
  PackageArchitecture: amd64
  Plugins: Shockwave Flash - /usr/lib/flashplugin-installer/libflashplayer.so
  PrefErrors: Unexpected character ',' before close parenthesis @ 
/usr/lib/thunderbird/omni.ja:greprefs.js:1141
  PrefSources: prefs.js
  ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
  Profiles: Profile0 (Default) - LastVersion=68.1.2/20191010144232 (In use)
  RunningIncompatibleAddons: False
  Tags:  eoan
  Themes: extensions.sqlite corrupt or missing
  Uname: Linux 5.3.0-19-generic x86_64
  UpgradeStatus: Upgraded to eoan on 2019-10-27 (1 days ago)
  UserGroups: adm cdrom dip docker libvirt lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 07/22/2019
  dmi.bios.vendor: Apple Inc.
  dmi.bios.version: 187.0.0.0.0
  dmi.board.name: Mac-E43C1C25D4880AD6
  dmi.board.vendor: Apple Inc.
  dmi.board.version: MacBookPro12,1
  dmi.chassis.type: 9
  dmi.chassis.vendor: Apple Inc.
  dmi.chassis.version: Mac-E43C1C25D4880AD6
  dmi.modalias: 
dmi:bvnAppleInc.:bvr187.0.0.0.0:bd07/22/2019:svnAppleInc.:pnMacBookPro12,1:pvr1.0:rvnAppleInc.:rnMac-E43C1C25D4880AD6:rvrMacBookPro12,1:cvnAppleInc.:ct9:cvrMac-E43C1C25D4880AD6:
  dmi.product.family: MacBook Pro
  dmi.product.name: MacBookPro12,1
  dmi.product.version: 1.0
  dmi.sys.vendor: Apple Inc.

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

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

[Desktop-packages] [Bug 1844126] Re: Update NVIDIA the 430 series and introduce the 435 series

This bug was fixed in the package nvidia-graphics-drivers-435 -
435.21-0ubuntu0.18.04.2

---
nvidia-graphics-drivers-435 (435.21-0ubuntu0.18.04.2) bionic; urgency=medium

  * debian/templates/control.in:
- Add Conflicts and Replaces to xserver-xorg-video-nvidia-#FLAVOUR#.
  This makes sure that upgrading from older driver series does not
  fail (LP: #1847979).

nvidia-graphics-drivers-435 (435.21-0ubuntu0.18.04.1) bionic;
urgency=medium

  * Initial release (LP: #1844126).

 -- Alberto Milone   Wed, 23 Oct 2019
15:08:53 +0200

** Changed in: nvidia-graphics-drivers-435 (Ubuntu Bionic)
   Status: In Progress => Fix Released

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

Title:
  Update NVIDIA the 430 series and introduce the 435 series

Status in nvidia-graphics-drivers-430 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-435 package in Ubuntu:
  Fix Released
Status in nvidia-settings package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-430 source package in Bionic:
  Fix Released
Status in nvidia-graphics-drivers-435 source package in Bionic:
  Fix Released
Status in nvidia-settings source package in Bionic:
  In Progress

Bug description:
  Update NVIDIA the 430 series and introduce the 435 series from 19.10.

  [Impact]
  These releases provide both bug fixes and new features, and we would like to
  make sure all of our users have access to these improvements.

  See the changelog entry below for a full list of changes and bugs.

  [Test Case]
  The following development and SRU process was followed:
  https://wiki.ubuntu.com/NVidiaUpdates

  Certification test suite must pass on a range of hardware:
  https://git.launchpad.net/plainbox-provider-sru/tree/units/sru.pxu

  The QA team that executed the tests will be in charge of attaching the
  artifacts and console output of the appropriate run to the bug. nVidia
  maintainers team members will not mark ‘verification-done’ until this
  has happened.

  [Regression Potential]
  In order to mitigate the regression potential, the results of the
  aforementioned system level tests are attached to this bug.

  
  [Discussion]

  430.50:

    * New upstream release (LP: #1844126):
  - Fixed display color range handling on pre-Turing GPUs, such
    that when limited color range is selected through the display
    controls page in nvidia-settings, output pixel values will be
    correctly clamped to Consumer Technology Association (CTA)
    range.

  435.21:

    * New upstream release:
  - Fixed a bug that caused the X server to crash when using
    HardDPMS with an NVIDIA-driven GPU Screen.
  - Fixed a bug which caused the kernel to panic when exiting a
    single X server when multiple X servers were active and in an
    SLI configuration.
  - Fixed a regression introduced in the 430.* series of releases
    that caused a segmentation fault in libnvcuvid.so while using
    Video Codec SDK APIs on certain graphics boards.
  - Added initial experimental support for runtime D3 (RTD3) power
    management on Turing notebook GPUs.
  - Improved nvidia-bug-report.sh to collect runtime D3 (RTD3)
    power management information.
  - Improved nvidia-bug-report.sh to collect ACPI tables when the
    acpidump tool is available.
  - Added Vulkan and OpenGL+GLX support for PRIME render offload.
    Please see the PRIME Render Offload chapter in the README for
    system requirements and configuration details.
  - Added support for changing Digital Vibrance in the display
    controls section of nvidia-settings on Turing hardware.
  - Fixed the cuvidParseVideoData API in the NVCUVID driver to
    correctly propagate errors returned by the
    PFNVIDSEQUENCECALLBACK callback function to the application.
  - Fixed a bug that caused the NVIDIA X driver to behave
    incorrectly or crash when a client queried Xinerama information
    on X servers with a non-NVIDIA X screen as screen 0.
  - Fixed the "Image Settings" options in the "OpenGL Settings"
    page of nvidia-settings for Quadro GPUs.  Previously, OpenGL
    rendering on Quadro would behave as if the "High Quality"
    option were selected regardless of the selection.  Now, the
    setting will default to "High Quality" for Quadro but selecting
    a lower option will affect rendering accordingly. (Other GPUs
    are unchanged: the default remains "Quality", but other options
    can be selected if desired.)
  - Fixed a bug that could cause Vulkan applications to generate
    spurious warning messages about a missing NV-GLX extension.
  - Fixed a bug that prevented nvidia-drm from marking preferred
    modes properly when reporting display information

[Desktop-packages] [Bug 1844126] Re: Update NVIDIA the 430 series and introduce the 435 series

This bug was fixed in the package nvidia-graphics-drivers-430 -
430.50-0ubuntu0.18.04.2

---
nvidia-graphics-drivers-430 (430.50-0ubuntu0.18.04.2) bionic; urgency=medium

  * debian/templates/control.in:
- Add Conflicts and Replaces to xserver-xorg-video-nvidia-#FLAVOUR#.
  This makes sure that upgrading from older driver series does not
  fail (LP: #1847979).

nvidia-graphics-drivers-430 (430.50-0ubuntu0.18.04.1) bionic;
urgency=medium

  * New upstream release (LP: #1844126):
- Fixed display color range handling on pre-Turing GPUs, such
  that when limited color range is selected through the display
  controls page in nvidia-settings, output pixel values will be
  correctly clamped to Consumer Technology Association (CTA)
  range.

 -- Alberto Milone   Wed, 23 Oct 2019
14:42:35 +0200

** Changed in: nvidia-graphics-drivers-430 (Ubuntu Bionic)
   Status: Fix Committed => Fix Released

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

Title:
  Update NVIDIA the 430 series and introduce the 435 series

Status in nvidia-graphics-drivers-430 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-435 package in Ubuntu:
  Fix Released
Status in nvidia-settings package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-430 source package in Bionic:
  Fix Released
Status in nvidia-graphics-drivers-435 source package in Bionic:
  Fix Released
Status in nvidia-settings source package in Bionic:
  In Progress

Bug description:
  Update NVIDIA the 430 series and introduce the 435 series from 19.10.

  [Impact]
  These releases provide both bug fixes and new features, and we would like to
  make sure all of our users have access to these improvements.

  See the changelog entry below for a full list of changes and bugs.

  [Test Case]
  The following development and SRU process was followed:
  https://wiki.ubuntu.com/NVidiaUpdates

  Certification test suite must pass on a range of hardware:
  https://git.launchpad.net/plainbox-provider-sru/tree/units/sru.pxu

  The QA team that executed the tests will be in charge of attaching the
  artifacts and console output of the appropriate run to the bug. nVidia
  maintainers team members will not mark ‘verification-done’ until this
  has happened.

  [Regression Potential]
  In order to mitigate the regression potential, the results of the
  aforementioned system level tests are attached to this bug.

  
  [Discussion]

  430.50:

    * New upstream release (LP: #1844126):
  - Fixed display color range handling on pre-Turing GPUs, such
    that when limited color range is selected through the display
    controls page in nvidia-settings, output pixel values will be
    correctly clamped to Consumer Technology Association (CTA)
    range.

  435.21:

    * New upstream release:
  - Fixed a bug that caused the X server to crash when using
    HardDPMS with an NVIDIA-driven GPU Screen.
  - Fixed a bug which caused the kernel to panic when exiting a
    single X server when multiple X servers were active and in an
    SLI configuration.
  - Fixed a regression introduced in the 430.* series of releases
    that caused a segmentation fault in libnvcuvid.so while using
    Video Codec SDK APIs on certain graphics boards.
  - Added initial experimental support for runtime D3 (RTD3) power
    management on Turing notebook GPUs.
  - Improved nvidia-bug-report.sh to collect runtime D3 (RTD3)
    power management information.
  - Improved nvidia-bug-report.sh to collect ACPI tables when the
    acpidump tool is available.
  - Added Vulkan and OpenGL+GLX support for PRIME render offload.
    Please see the PRIME Render Offload chapter in the README for
    system requirements and configuration details.
  - Added support for changing Digital Vibrance in the display
    controls section of nvidia-settings on Turing hardware.
  - Fixed the cuvidParseVideoData API in the NVCUVID driver to
    correctly propagate errors returned by the
    PFNVIDSEQUENCECALLBACK callback function to the application.
  - Fixed a bug that caused the NVIDIA X driver to behave
    incorrectly or crash when a client queried Xinerama information
    on X servers with a non-NVIDIA X screen as screen 0.
  - Fixed the "Image Settings" options in the "OpenGL Settings"
    page of nvidia-settings for Quadro GPUs.  Previously, OpenGL
    rendering on Quadro would behave as if the "High Quality"
    option were selected regardless of the selection.  Now, the
    setting will default to "High Quality" for Quadro but selecting
    a lower option will affect rendering accordingly. (Other GPUs
    are unchanged: the default remains "Quality", but other options
    can be

[Desktop-packages] [Bug 1844126] Update Released

2019-11-07 Thread Timo Aaltonen

The verification of the Stable Release Update for nvidia-graphics-
drivers-435 has completed successfully and the package is now being
released to -updates.  Subsequently, the Ubuntu Stable Release Updates
Team is being unsubscribed and will not receive messages about this bug
report.  In the event that you encounter a regression using the package
from -updates please report a new bug using ubuntu-bug and tag the bug
report regression-update so we can easily find any regressions.

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

Title:
  Update NVIDIA the 430 series and introduce the 435 series

Status in nvidia-graphics-drivers-430 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-435 package in Ubuntu:
  Fix Released
Status in nvidia-settings package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-430 source package in Bionic:
  Fix Released
Status in nvidia-graphics-drivers-435 source package in Bionic:
  Fix Released
Status in nvidia-settings source package in Bionic:
  In Progress

Bug description:
  Update NVIDIA the 430 series and introduce the 435 series from 19.10.

  [Impact]
  These releases provide both bug fixes and new features, and we would like to
  make sure all of our users have access to these improvements.

  See the changelog entry below for a full list of changes and bugs.

  [Test Case]
  The following development and SRU process was followed:
  https://wiki.ubuntu.com/NVidiaUpdates

  Certification test suite must pass on a range of hardware:
  https://git.launchpad.net/plainbox-provider-sru/tree/units/sru.pxu

  The QA team that executed the tests will be in charge of attaching the
  artifacts and console output of the appropriate run to the bug. nVidia
  maintainers team members will not mark ‘verification-done’ until this
  has happened.

  [Regression Potential]
  In order to mitigate the regression potential, the results of the
  aforementioned system level tests are attached to this bug.

  
  [Discussion]

  430.50:

    * New upstream release (LP: #1844126):
  - Fixed display color range handling on pre-Turing GPUs, such
    that when limited color range is selected through the display
    controls page in nvidia-settings, output pixel values will be
    correctly clamped to Consumer Technology Association (CTA)
    range.

  435.21:

    * New upstream release:
  - Fixed a bug that caused the X server to crash when using
    HardDPMS with an NVIDIA-driven GPU Screen.
  - Fixed a bug which caused the kernel to panic when exiting a
    single X server when multiple X servers were active and in an
    SLI configuration.
  - Fixed a regression introduced in the 430.* series of releases
    that caused a segmentation fault in libnvcuvid.so while using
    Video Codec SDK APIs on certain graphics boards.
  - Added initial experimental support for runtime D3 (RTD3) power
    management on Turing notebook GPUs.
  - Improved nvidia-bug-report.sh to collect runtime D3 (RTD3)
    power management information.
  - Improved nvidia-bug-report.sh to collect ACPI tables when the
    acpidump tool is available.
  - Added Vulkan and OpenGL+GLX support for PRIME render offload.
    Please see the PRIME Render Offload chapter in the README for
    system requirements and configuration details.
  - Added support for changing Digital Vibrance in the display
    controls section of nvidia-settings on Turing hardware.
  - Fixed the cuvidParseVideoData API in the NVCUVID driver to
    correctly propagate errors returned by the
    PFNVIDSEQUENCECALLBACK callback function to the application.
  - Fixed a bug that caused the NVIDIA X driver to behave
    incorrectly or crash when a client queried Xinerama information
    on X servers with a non-NVIDIA X screen as screen 0.
  - Fixed the "Image Settings" options in the "OpenGL Settings"
    page of nvidia-settings for Quadro GPUs.  Previously, OpenGL
    rendering on Quadro would behave as if the "High Quality"
    option were selected regardless of the selection.  Now, the
    setting will default to "High Quality" for Quadro but selecting
    a lower option will affect rendering accordingly. (Other GPUs
    are unchanged: the default remains "Quality", but other options
    can be selected if desired.)
  - Fixed a bug that could cause Vulkan applications to generate
    spurious warning messages about a missing NV-GLX extension.
  - Fixed a bug that prevented nvidia-drm from marking preferred
    modes properly when reporting display information via the DRM-
    KMS API.
  - Fixed the NvEncodeAPI driver to correctly reject the encoding
    of sequences with resolutions smaller than what the NVENC

[Desktop-packages] [Bug 1847979] Re: package xserver-xorg-video-nvidia-430 430.26-0ubuntu0.18.04.2 failed to install/upgrade: trying to overwrite '/usr/share/X11/xorg.conf.d/10-nvidia.conf', which is

This bug was fixed in the package nvidia-graphics-drivers-430 -
430.50-0ubuntu0.18.04.2

---
nvidia-graphics-drivers-430 (430.50-0ubuntu0.18.04.2) bionic; urgency=medium

  * debian/templates/control.in:
- Add Conflicts and Replaces to xserver-xorg-video-nvidia-#FLAVOUR#.
  This makes sure that upgrading from older driver series does not
  fail (LP: #1847979).

nvidia-graphics-drivers-430 (430.50-0ubuntu0.18.04.1) bionic;
urgency=medium

  * New upstream release (LP: #1844126):
- Fixed display color range handling on pre-Turing GPUs, such
  that when limited color range is selected through the display
  controls page in nvidia-settings, output pixel values will be
  correctly clamped to Consumer Technology Association (CTA)
  range.

 -- Alberto Milone   Wed, 23 Oct 2019
14:42:35 +0200

** Changed in: nvidia-graphics-drivers-430 (Ubuntu Bionic)
   Status: Fix Committed => Fix Released

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

Title:
  package xserver-xorg-video-nvidia-430 430.26-0ubuntu0.18.04.2 failed
  to install/upgrade: trying to overwrite
  '/usr/share/X11/xorg.conf.d/10-nvidia.conf', which is also in package
  xserver-xorg-video-nvidia-418 418.74-0ubuntu0~18.04.1

Status in OEM Priority Project:
  In Progress
Status in nvidia-graphics-drivers-430 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-435 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-430 source package in Bionic:
  Fix Released
Status in nvidia-graphics-drivers-435 source package in Bionic:
  Fix Released

Bug description:
  There is some problem when upgrading NVIDIA graphics driver from 418
  to 430.

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: xserver-xorg-video-nvidia-430 430.26-0ubuntu0.18.04.2
  ProcVersionSignature: Ubuntu 5.0.0-1024.27-oem-osp1 5.0.21
  Uname: Linux 5.0.0-1024-oem-osp1 x86_64
  ApportVersion: 2.20.9-0ubuntu7.7
  Architecture: amd64
  Date: Mon Oct 14 04:57:53 2019
  Dependencies:
   gcc-8-base 8.3.0-6ubuntu1~18.04.1
   libc6 2.27-3ubuntu1
   libgcc1 1:8.3.0-6ubuntu1~18.04.1
   libnvidia-cfg1-430 430.26-0ubuntu0.18.04.2
  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-bionic-amd64-20190418-59+beaver-osp1-worm+X09
  DuplicateSignature:
   package:xserver-xorg-video-nvidia-430:430.26-0ubuntu0.18.04.2
   Unpacking xserver-xorg-video-nvidia-430 (430.26-0ubuntu0.18.04.2) ...
   dpkg: error processing archive 
/tmp/apt-dpkg-install-WH1Eoi/29-xserver-xorg-video-nvidia-430_430.26-0ubuntu0.18.04.2_amd64.deb
 (--unpack):
trying to overwrite '/usr/share/X11/xorg.conf.d/10-nvidia.conf', which is 
also in package xserver-xorg-video-nvidia-418 418.74-0ubuntu0~18.04.1
  ErrorMessage: trying to overwrite 
'/usr/share/X11/xorg.conf.d/10-nvidia.conf', which is also in package 
xserver-xorg-video-nvidia-418 418.74-0ubuntu0~18.04.1
  InstallationDate: Installed on 2019-10-14 (0 days ago)
  InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 
20190418-12:10
  Python3Details: /usr/bin/python3.6, Python 3.6.8, python3-minimal, 
3.6.7-1~18.04
  PythonDetails: /usr/bin/python2.7, Python 2.7.15+, python-minimal, 
2.7.15~rc1-1
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu2.3
   apt  1.6.12
  SourcePackage: nvidia-graphics-drivers-430
  Title: package xserver-xorg-video-nvidia-430 430.26-0ubuntu0.18.04.2 failed 
to install/upgrade: trying to overwrite 
'/usr/share/X11/xorg.conf.d/10-nvidia.conf', which is also in package 
xserver-xorg-video-nvidia-418 418.74-0ubuntu0~18.04.1
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1847979/+subscriptions

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

[Desktop-packages] [Bug 1851621] Re: [snap] No KDE file dialogs

2019-11-07 Thread Javier Urien

Thanks for the info on other bugs!

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

Title:
  [snap] No KDE file dialogs

Status in chromium-browser package in Ubuntu:
  New

Bug description:
  I upgraded from kubuntu 19.04 to 19.10 and noticed that chromium does
  not integrate anymore. Plasma integration Fails to connect to the
  native host (suggested google solutions didn't work), Kubuntu mouse
  pointers change to ugly ones (I bellive GTK fallback), no kde file
  dialog when opening/saving files.

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

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

[Desktop-packages] [Bug 1847979] Update Released

2019-11-07 Thread Timo Aaltonen

The verification of the Stable Release Update for nvidia-graphics-
drivers-435 has completed successfully and the package is now being
released to -updates.  Subsequently, the Ubuntu Stable Release Updates
Team is being unsubscribed and will not receive messages about this bug
report.  In the event that you encounter a regression using the package
from -updates please report a new bug using ubuntu-bug and tag the bug
report regression-update so we can easily find any regressions.

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

Title:
  package xserver-xorg-video-nvidia-430 430.26-0ubuntu0.18.04.2 failed
  to install/upgrade: trying to overwrite
  '/usr/share/X11/xorg.conf.d/10-nvidia.conf', which is also in package
  xserver-xorg-video-nvidia-418 418.74-0ubuntu0~18.04.1

Status in OEM Priority Project:
  In Progress
Status in nvidia-graphics-drivers-430 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-435 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-430 source package in Bionic:
  Fix Released
Status in nvidia-graphics-drivers-435 source package in Bionic:
  Fix Released

Bug description:
  There is some problem when upgrading NVIDIA graphics driver from 418
  to 430.

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: xserver-xorg-video-nvidia-430 430.26-0ubuntu0.18.04.2
  ProcVersionSignature: Ubuntu 5.0.0-1024.27-oem-osp1 5.0.21
  Uname: Linux 5.0.0-1024-oem-osp1 x86_64
  ApportVersion: 2.20.9-0ubuntu7.7
  Architecture: amd64
  Date: Mon Oct 14 04:57:53 2019
  Dependencies:
   gcc-8-base 8.3.0-6ubuntu1~18.04.1
   libc6 2.27-3ubuntu1
   libgcc1 1:8.3.0-6ubuntu1~18.04.1
   libnvidia-cfg1-430 430.26-0ubuntu0.18.04.2
  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-bionic-amd64-20190418-59+beaver-osp1-worm+X09
  DuplicateSignature:
   package:xserver-xorg-video-nvidia-430:430.26-0ubuntu0.18.04.2
   Unpacking xserver-xorg-video-nvidia-430 (430.26-0ubuntu0.18.04.2) ...
   dpkg: error processing archive 
/tmp/apt-dpkg-install-WH1Eoi/29-xserver-xorg-video-nvidia-430_430.26-0ubuntu0.18.04.2_amd64.deb
 (--unpack):
trying to overwrite '/usr/share/X11/xorg.conf.d/10-nvidia.conf', which is 
also in package xserver-xorg-video-nvidia-418 418.74-0ubuntu0~18.04.1
  ErrorMessage: trying to overwrite 
'/usr/share/X11/xorg.conf.d/10-nvidia.conf', which is also in package 
xserver-xorg-video-nvidia-418 418.74-0ubuntu0~18.04.1
  InstallationDate: Installed on 2019-10-14 (0 days ago)
  InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 
20190418-12:10
  Python3Details: /usr/bin/python3.6, Python 3.6.8, python3-minimal, 
3.6.7-1~18.04
  PythonDetails: /usr/bin/python2.7, Python 2.7.15+, python-minimal, 
2.7.15~rc1-1
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu2.3
   apt  1.6.12
  SourcePackage: nvidia-graphics-drivers-430
  Title: package xserver-xorg-video-nvidia-430 430.26-0ubuntu0.18.04.2 failed 
to install/upgrade: trying to overwrite 
'/usr/share/X11/xorg.conf.d/10-nvidia.conf', which is also in package 
xserver-xorg-video-nvidia-418 418.74-0ubuntu0~18.04.1
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1847979/+subscriptions

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

[Desktop-packages] [Bug 1850081] Re: Folder pane text overflows

2019-11-07 Thread Rowan Wookey

I've reported upstream and linked the upstream issue here.

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

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

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

Title:
  Folder pane text overflows

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

Bug description:
  After upgrading to Kubuntu 19.10 I noticed the text in the folder pane 
overflows which hides the unread count, it appears as if the text is behind the 
scrollbar.
  --- 
  ProblemType: Bug
  AddonCompatCheckDisabled: False
  ApportVersion: 2.20.11-0ubuntu8
  Architecture: amd64
  AudioDevicesInUse:
   USER PID ACCESS COMMAND
   /dev/snd/controlC1:  rowan  2237 F pulseaudio
   /dev/snd/controlC0:  rowan  2237 F pulseaudio
  BuildID: 20191010144232
  Channel: Unavailable
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 19.10
  Extensions: extensions.sqlite corrupt or missing
  ForcedLayersAccel: False
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  IncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
  InstallationDate: Installed on 2018-11-19 (343 days ago)
  InstallationMedia: Kubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.2)
  Locales: extensions.sqlite corrupt or missing
  MostRecentCrashID: bp-6abdd954-b5ad-4d9d-a828-9824b0180710
  Package: thunderbird 1:68.1.2+build1-0ubuntu1
  PackageArchitecture: amd64
  Plugins: Shockwave Flash - /usr/lib/flashplugin-installer/libflashplayer.so
  PrefErrors: Unexpected character ',' before close parenthesis @ 
/usr/lib/thunderbird/omni.ja:greprefs.js:1141
  PrefSources: prefs.js
  ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
  Profiles: Profile0 (Default) - LastVersion=68.1.2/20191010144232 (In use)
  RunningIncompatibleAddons: False
  Tags:  eoan
  Themes: extensions.sqlite corrupt or missing
  Uname: Linux 5.3.0-19-generic x86_64
  UpgradeStatus: Upgraded to eoan on 2019-10-27 (1 days ago)
  UserGroups: adm cdrom dip docker libvirt lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 07/22/2019
  dmi.bios.vendor: Apple Inc.
  dmi.bios.version: 187.0.0.0.0
  dmi.board.name: Mac-E43C1C25D4880AD6
  dmi.board.vendor: Apple Inc.
  dmi.board.version: MacBookPro12,1
  dmi.chassis.type: 9
  dmi.chassis.vendor: Apple Inc.
  dmi.chassis.version: Mac-E43C1C25D4880AD6
  dmi.modalias: 
dmi:bvnAppleInc.:bvr187.0.0.0.0:bd07/22/2019:svnAppleInc.:pnMacBookPro12,1:pvr1.0:rvnAppleInc.:rnMac-E43C1C25D4880AD6:rvrMacBookPro12,1:cvnAppleInc.:ct9:cvrMac-E43C1C25D4880AD6:
  dmi.product.family: MacBook Pro
  dmi.product.name: MacBookPro12,1
  dmi.product.version: 1.0
  dmi.sys.vendor: Apple Inc.

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

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

[Desktop-packages] [Bug 1847979] Re: package xserver-xorg-video-nvidia-430 430.26-0ubuntu0.18.04.2 failed to install/upgrade: trying to overwrite '/usr/share/X11/xorg.conf.d/10-nvidia.conf', which is

This bug was fixed in the package nvidia-graphics-drivers-435 -
435.21-0ubuntu0.18.04.2

---
nvidia-graphics-drivers-435 (435.21-0ubuntu0.18.04.2) bionic; urgency=medium

  * debian/templates/control.in:
- Add Conflicts and Replaces to xserver-xorg-video-nvidia-#FLAVOUR#.
  This makes sure that upgrading from older driver series does not
  fail (LP: #1847979).

nvidia-graphics-drivers-435 (435.21-0ubuntu0.18.04.1) bionic;
urgency=medium

  * Initial release (LP: #1844126).

 -- Alberto Milone   Wed, 23 Oct 2019
15:08:53 +0200

** Changed in: nvidia-graphics-drivers-435 (Ubuntu Bionic)
   Status: New => Fix Released

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

Title:
  package xserver-xorg-video-nvidia-430 430.26-0ubuntu0.18.04.2 failed
  to install/upgrade: trying to overwrite
  '/usr/share/X11/xorg.conf.d/10-nvidia.conf', which is also in package
  xserver-xorg-video-nvidia-418 418.74-0ubuntu0~18.04.1

Status in OEM Priority Project:
  In Progress
Status in nvidia-graphics-drivers-430 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-435 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-430 source package in Bionic:
  Fix Released
Status in nvidia-graphics-drivers-435 source package in Bionic:
  Fix Released

Bug description:
  There is some problem when upgrading NVIDIA graphics driver from 418
  to 430.

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: xserver-xorg-video-nvidia-430 430.26-0ubuntu0.18.04.2
  ProcVersionSignature: Ubuntu 5.0.0-1024.27-oem-osp1 5.0.21
  Uname: Linux 5.0.0-1024-oem-osp1 x86_64
  ApportVersion: 2.20.9-0ubuntu7.7
  Architecture: amd64
  Date: Mon Oct 14 04:57:53 2019
  Dependencies:
   gcc-8-base 8.3.0-6ubuntu1~18.04.1
   libc6 2.27-3ubuntu1
   libgcc1 1:8.3.0-6ubuntu1~18.04.1
   libnvidia-cfg1-430 430.26-0ubuntu0.18.04.2
  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-bionic-amd64-20190418-59+beaver-osp1-worm+X09
  DuplicateSignature:
   package:xserver-xorg-video-nvidia-430:430.26-0ubuntu0.18.04.2
   Unpacking xserver-xorg-video-nvidia-430 (430.26-0ubuntu0.18.04.2) ...
   dpkg: error processing archive 
/tmp/apt-dpkg-install-WH1Eoi/29-xserver-xorg-video-nvidia-430_430.26-0ubuntu0.18.04.2_amd64.deb
 (--unpack):
trying to overwrite '/usr/share/X11/xorg.conf.d/10-nvidia.conf', which is 
also in package xserver-xorg-video-nvidia-418 418.74-0ubuntu0~18.04.1
  ErrorMessage: trying to overwrite 
'/usr/share/X11/xorg.conf.d/10-nvidia.conf', which is also in package 
xserver-xorg-video-nvidia-418 418.74-0ubuntu0~18.04.1
  InstallationDate: Installed on 2019-10-14 (0 days ago)
  InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 
20190418-12:10
  Python3Details: /usr/bin/python3.6, Python 3.6.8, python3-minimal, 
3.6.7-1~18.04
  PythonDetails: /usr/bin/python2.7, Python 2.7.15+, python-minimal, 
2.7.15~rc1-1
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu2.3
   apt  1.6.12
  SourcePackage: nvidia-graphics-drivers-430
  Title: package xserver-xorg-video-nvidia-430 430.26-0ubuntu0.18.04.2 failed 
to install/upgrade: trying to overwrite 
'/usr/share/X11/xorg.conf.d/10-nvidia.conf', which is also in package 
xserver-xorg-video-nvidia-418 418.74-0ubuntu0~18.04.1
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1847979/+subscriptions

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

[Desktop-packages] [Bug 1844126] Re: Update NVIDIA the 430 series and introduce the 435 series

2019-11-07 Thread Alberto Milone

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

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

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

Title:
  Update NVIDIA the 430 series and introduce the 435 series

Status in nvidia-graphics-drivers-430 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-435 package in Ubuntu:
  Fix Released
Status in nvidia-settings package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-430 source package in Bionic:
  Fix Committed
Status in nvidia-graphics-drivers-435 source package in Bionic:
  In Progress
Status in nvidia-settings source package in Bionic:
  In Progress

Bug description:
  Update NVIDIA the 430 series and introduce the 435 series from 19.10.

  [Impact]
  These releases provide both bug fixes and new features, and we would like to
  make sure all of our users have access to these improvements.

  See the changelog entry below for a full list of changes and bugs.

  [Test Case]
  The following development and SRU process was followed:
  https://wiki.ubuntu.com/NVidiaUpdates

  Certification test suite must pass on a range of hardware:
  https://git.launchpad.net/plainbox-provider-sru/tree/units/sru.pxu

  The QA team that executed the tests will be in charge of attaching the
  artifacts and console output of the appropriate run to the bug. nVidia
  maintainers team members will not mark ‘verification-done’ until this
  has happened.

  [Regression Potential]
  In order to mitigate the regression potential, the results of the
  aforementioned system level tests are attached to this bug.

  
  [Discussion]

  430.50:

    * New upstream release (LP: #1844126):
  - Fixed display color range handling on pre-Turing GPUs, such
    that when limited color range is selected through the display
    controls page in nvidia-settings, output pixel values will be
    correctly clamped to Consumer Technology Association (CTA)
    range.

  435.21:

    * New upstream release:
  - Fixed a bug that caused the X server to crash when using
    HardDPMS with an NVIDIA-driven GPU Screen.
  - Fixed a bug which caused the kernel to panic when exiting a
    single X server when multiple X servers were active and in an
    SLI configuration.
  - Fixed a regression introduced in the 430.* series of releases
    that caused a segmentation fault in libnvcuvid.so while using
    Video Codec SDK APIs on certain graphics boards.
  - Added initial experimental support for runtime D3 (RTD3) power
    management on Turing notebook GPUs.
  - Improved nvidia-bug-report.sh to collect runtime D3 (RTD3)
    power management information.
  - Improved nvidia-bug-report.sh to collect ACPI tables when the
    acpidump tool is available.
  - Added Vulkan and OpenGL+GLX support for PRIME render offload.
    Please see the PRIME Render Offload chapter in the README for
    system requirements and configuration details.
  - Added support for changing Digital Vibrance in the display
    controls section of nvidia-settings on Turing hardware.
  - Fixed the cuvidParseVideoData API in the NVCUVID driver to
    correctly propagate errors returned by the
    PFNVIDSEQUENCECALLBACK callback function to the application.
  - Fixed a bug that caused the NVIDIA X driver to behave
    incorrectly or crash when a client queried Xinerama information
    on X servers with a non-NVIDIA X screen as screen 0.
  - Fixed the "Image Settings" options in the "OpenGL Settings"
    page of nvidia-settings for Quadro GPUs.  Previously, OpenGL
    rendering on Quadro would behave as if the "High Quality"
    option were selected regardless of the selection.  Now, the
    setting will default to "High Quality" for Quadro but selecting
    a lower option will affect rendering accordingly. (Other GPUs
    are unchanged: the default remains "Quality", but other options
    can be selected if desired.)
  - Fixed a bug that could cause Vulkan applications to generate
    spurious warning messages about a missing NV-GLX extension.
  - Fixed a bug that prevented nvidia-drm from marking preferred
    modes properly when reporting display information via the DRM-
    KMS API.
  - Fixed the NvEncodeAPI driver to correctly reject the encoding
    of sequences with resolutions smaller than what the NVENC
    supports.
  - Fixed display color range handling on pre-Turing GPUs, such
    that when limited color range is selected through the display
    controls page in nvidia-settings, output pixel values will be
    correctly clamped to Consumer Technology Association (CTA)
    range.

To manage notifications about

[Desktop-packages] [Bug 1851520] Re: Online Accounts Cannot Add Gmail Account

Status changed to 'Confirmed' because the bug affects multiple users.

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

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

Title:
  Online Accounts Cannot Add Gmail Account

Status in webkit2gtk package in Ubuntu:
  Confirmed

Bug description:
  I noticed today that I am unable to create a new GMail account through
  "Online Accounts." The flow happens as expected (username, password,
  2FA) but results in an error:

  "Sign in with Google temporarily disabled for this app

  This app has not been verified yet by Google in order to use Google
  Sign In."

  Issue present on: Pop_OS 19.10, Ubuntu Mate 19.10, Ubuntu 19.10 and
  19.04 and 18.04

  Steps to reproduce:

  1.)Go to Settings -> Online Accounts -> Google
  2.)Enter Username
  3.)Enter Password
  4.)Enter 2FA

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

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

[Desktop-packages] [Bug 885525] Re: Deleting a Gmail Message Always Sends Item to [Gmail]/Trash

2019-11-07 Thread Philippe Cloutier

If you are experiencing this, start by checking Gmail's Forwarding and
POP/IMAP settings (at the misleading URL
https://mail.google.com/mail/u/0/#settings/fwdandpop ). In the IMAP
access area, check the second preference ("When I mark a message in IMAP
as deleted") and - if that one is set to "Auto-Expunge off" - the
related third preference "When a message is marked as deleted or
expunged from the last visible IMAP folder". I experienced this bug with
Auto-Expunge enabled, which is currently the default.

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

Title:
  Deleting a Gmail Message Always Sends Item to [Gmail]/Trash

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

Bug description:
  Thunderbird 7.0.1, Ubuntu 11.10

  Gmail accounts do not obey the setting in Account Settings -->
  [Account] --> Server Settings --> When I delete a message

  I changed this to move the message to Gmail's "All Mail" folder,
  attempting to imitate the Gmail web interface's "Archive" option.
  However, regardless of setting, the item always moved to Trash. This
  persisted after restart of the client. The settings save, but have no
  effect.

  Caveat: This was tested on two Google Apps for Domains accounts,
  though I suspect this behavior will happen with gmail.com accounts as
  well.

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

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

[Desktop-packages] [Bug 1851649] [NEW] Package bug

2019-11-07 Thread John Doe

Public bug reported:

I couldn't change brightness. Probably this bug is related to the
problem.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xorg 1:7.7+19ubuntu7.1
ProcVersionSignature: Ubuntu 5.0.0-32.34~18.04.2-generic 5.0.21
Uname: Linux 5.0.0-32-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.9
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Thu Nov  7 14:54:15 2019
DistUpgraded: Fresh install
DistroCodename: bionic
DistroVariant: ubuntu
GraphicsCard:
 Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0106] (rev 09) (prog-if 00 [VGA controller])
   Subsystem: Lenovo 2nd Generation Core Processor Family Integrated Graphics 
Controller [17aa:397d]
 NVIDIA Corporation GF119M [GeForce 410M] [10de:1054] (rev a1) (prog-if 00 [VGA 
controller])
   Subsystem: Lenovo GF119M [GeForce 410M] [17aa:397d]
InstallationDate: Installed on 2019-11-06 (0 days ago)
InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805)
MachineType: LENOVO HuronRiver Platform
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-32-generic 
root=UUID=3f6eec95-af31-4261-96ff-7e5695b716cc ro quiet splash vt.handoff=1
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 10/27/2011
dmi.bios.vendor: LENOVO
dmi.bios.version: 44CN43WW
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: Emerald Lake
dmi.board.vendor: LENOVO
dmi.board.version: FAB1
dmi.chassis.asset.tag: Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: 0.1
dmi.modalias: 
dmi:bvnLENOVO:bvr44CN43WW:bd10/27/2011:svnLENOVO:pnHuronRiverPlatform:pvrLenovoB570e:rvnLENOVO:rnEmeraldLake:rvrFAB1:cvnLENOVO:ct10:cvr0.1:
dmi.product.family: HuronRiver System
dmi.product.name: HuronRiver Platform
dmi.product.sku: System SKUNumber
dmi.product.version: Lenovo B570e
dmi.sys.vendor: LENOVO
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.97-1ubuntu1~18.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.8-0ubuntu0~18.04.3
version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.8-0ubuntu0~18.04.3
version.xserver-xorg-core: xserver-xorg-core 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 ubuntu

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

Title:
  Package bug

Status in xorg package in Ubuntu:
  New

Bug description:
  I couldn't change brightness. Probably this bug is related to the
  problem.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 5.0.0-32.34~18.04.2-generic 5.0.21
  Uname: Linux 5.0.0-32-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.9
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Nov  7 14:54:15 2019
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0106] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: Lenovo 2nd Generation Core Processor Family Integrated Graphics 
Controller [17aa:397d]
   NVIDIA Corporation GF119M [GeForce 410M] [10de:1054] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: Lenovo GF119M [GeForce 410M] [17aa:397d]
  InstallationDate: Installed on 2019-11-06 (0 days ago)
  InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 
(20190805)
  MachineType: LENOVO HuronRiver Platform
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-32-generic 
root=UUID=3f6eec95-af31-4261-96ff-7e5695b716cc ro quiet splash vt.handoff=1
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/27/2011
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 44CN43WW
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: Emerald Lake
  dmi.board.vendor: LENOVO
  dmi.board.version: FAB1
  dmi.chassis.asset.tag: Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnLENOVO:bvr44CN43WW:bd10/27/2011:svnLENOVO:pnHuronRiverPlatform:pvrLenovoB570e:rvnLENOVO:rnEmeraldLake:rvrFAB1:cvnLENOVO:ct10:cvr0.1:
  dmi.product.family: HuronRiver System
  dmi.product.name: HuronRiver Platform
  dmi.product.sku: System SKUNumber
  dmi.product.version: Lenovo B570e
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.97-1ubuntu1~18.04.1

[Desktop-packages] [Bug 1851234] Re: [SRU] libreoffice 6.3.3 for eoan

2019-11-07 Thread Marcus Tomlinson

** Changed in: libreoffice (Ubuntu)
   Status: In Progress => Fix Committed

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

Title:
  [SRU] libreoffice 6.3.3 for eoan

Status in libreoffice package in Ubuntu:
  Fix Committed
Status in libreoffice source package in Eoan:
  Fix Committed

Bug description:
  [Impact]

   * LibreOffice 6.3.3 is in its third bugfix release of the 6.3 line. Version 
6.3.3 is currently in focal.
     For a list of fixed bugs compared to 6.3.2 see the list of bugs fixed in 
the two release candidates:
   https://wiki.documentfoundation.org/Releases/6.3.3/RC1#List_of_fixed_bugs
   https://wiki.documentfoundation.org/Releases/6.3.3/RC2#List_of_fixed_bugs
     (that's a total of 83 bugs)

   * Given the nature of the project, the complexity of the codebase and
  the high level of quality assurance upstream, it is preferable to SRU
  a minor release rather than cherry-pick selected bug fixes.

  [Test Case]

   * No specific test case, bugs fixed upstream hopefully come with
  unit/regression tests, and the release itself is extensively exercised
  upstream (both in an automated manner and manually) by a community of
  testers. Each minor release normally goes through two release
  candidates.

   * The libreoffice packages include autopkgtests, those should be run
  and verified to pass.

   * General smoke testing of all the applications in the office suite
  should be carried out.

  [Regression Potential]

   * A minor release with a total of 83 bug fixes always carries the
  potential for introducing regressions, even though it is a bugfix-only
  release, meaning that no new features were added, and no existing
  features were removed.

   * A combination of autopkgtests and careful smoke testing as
  described above should provide reasonable confidence that no
  regressions sneaked in.

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

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

[Desktop-packages] [Bug 1851234] Re: [SRU] libreoffice 6.3.3 for eoan

2019-11-07 Thread Łukasz Zemczak

Hello Marcus, or anyone else affected,

Accepted libreoffice into eoan-proposed. The package will build now and
be available at
https://launchpad.net/ubuntu/+source/libreoffice/1:6.3.3-0ubuntu0.19.10.1
in a few hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.  Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested and change the tag from
verification-needed-eoan to verification-done-eoan. If it does not fix
the bug for you, please add a comment stating that, and change the tag
to verification-failed-eoan. In either case, without details of your
testing we will not be able to proceed.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance for helping!

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

** Changed in: libreoffice (Ubuntu Eoan)
   Status: In Progress => Fix Committed

** Tags added: verification-needed verification-needed-eoan

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

Title:
  [SRU] libreoffice 6.3.3 for eoan

Status in libreoffice package in Ubuntu:
  Fix Committed
Status in libreoffice source package in Eoan:
  Fix Committed

Bug description:
  [Impact]

   * LibreOffice 6.3.3 is in its third bugfix release of the 6.3 line. Version 
6.3.3 is currently in focal.
     For a list of fixed bugs compared to 6.3.2 see the list of bugs fixed in 
the two release candidates:
   https://wiki.documentfoundation.org/Releases/6.3.3/RC1#List_of_fixed_bugs
   https://wiki.documentfoundation.org/Releases/6.3.3/RC2#List_of_fixed_bugs
     (that's a total of 83 bugs)

   * Given the nature of the project, the complexity of the codebase and
  the high level of quality assurance upstream, it is preferable to SRU
  a minor release rather than cherry-pick selected bug fixes.

  [Test Case]

   * No specific test case, bugs fixed upstream hopefully come with
  unit/regression tests, and the release itself is extensively exercised
  upstream (both in an automated manner and manually) by a community of
  testers. Each minor release normally goes through two release
  candidates.

   * The libreoffice packages include autopkgtests, those should be run
  and verified to pass.

   * General smoke testing of all the applications in the office suite
  should be carried out.

  [Regression Potential]

   * A minor release with a total of 83 bug fixes always carries the
  potential for introducing regressions, even though it is a bugfix-only
  release, meaning that no new features were added, and no existing
  features were removed.

   * A combination of autopkgtests and careful smoke testing as
  described above should provide reasonable confidence that no
  regressions sneaked in.

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

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

[Desktop-packages] [Bug 1781428] Re: please enable snap mediation support

2019-11-07 Thread James Henstridge

The xenial backport is non-functional due to a symbol collision between
libjson-c.so (required by libpulse) and libjson-glib.so (required by
snapd-glib).  This doesn't affect the Bionic backport though.

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

Title:
  please enable snap mediation support

Status in pulseaudio package in Ubuntu:
  Fix Released
Status in pulseaudio source package in Xenial:
  Triaged
Status in pulseaudio source package in Bionic:
  Triaged

Bug description:
  [Impact]
  Ubuntu 16.10 added rudimentary snap support to disable audio recording if the 
connecting process was a snap. By Ubuntu 18.04, something changed in the build 
resulting in 'Enable Snappy support: no' with audio recording no longer being 
mediated by pulseaudio (access to the pulseaudio socket continued to be 
mediated by snapd's apparmor policy). This resulted in any application with the 
pulseaudio interface connected to be able to also record. Ubuntu 16.04 never 
had mediation patches and always allowed recording when the pulseaudio 
interface was connected.

  To correct this situation but not regress existing behavior, Ubuntu
  19.04's pulseaudio was updated patch to allow playback to all
  connected clients (snaps or not), record by classic snaps (see bug
  1787324) and record by strict mode snaps if either the pulseaudio or
  new-in-snapd-2.41 audio-record interfaces were connected. With this
  change, snapd is in a position to migrate snaps to the new audio-
  playback and audio-record interfaces and properly mediate audio
  recording (see https://forum.snapcraft.io/t/upcoming-pulseaudio-
  interface-deprecation/13418).

  The patch to pulseaudio consists of adding a module, enabling it in
  default.pa and then when it is enabled, pulseaudio when faced with a
  record operation will, when the connecting process is a snap (ie, its
  security label (ie, apparmor label) starts with 'snap.'), query snapd
  via its control socket to ask if the snap is classic and if not,
  whether the pulseaudio or audio-record interfaces are connected.
  Adjusting pulseaudio in the manner does not require coordination with
  any release of snapd. It does need a newer version of snapd-glib,
  which was recently updated to 1.49 in the last SRU.

  [Test Case]

  IMPORTANT: if updating pulseaudio while the session is running, either
  need to reboot for the test or kill pulseaudio so it can restart with
  the new snap policy

  For unconfined applications:
  $ paplay /usr/share/sounds/alsa/Noise.wav && echo "yes"
  yes

  $ rm -f /tmp/out.wav ; parecord /tmp/out.wav && echo "yes"  # ctrl-c to stop 
recording
  ^Cyes

  $ paplay /tmp/out.wav && echo "yes"
  yes

  For confined, non-snap applications:
  $ sudo apt-get install evince

  $ aa-exec -p /usr/bin/evince -- paplay
  /usr/share/sounds/alsa/Noise.wav && echo yes

  $ rm -f /tmp/out.wav ; aa-exec -p /usr/bin/evince -- parecord /tmp/out.wav && 
echo "yes"  # ctrl-c to stop recording
  ^Cyes

  $ aa-exec -p /usr/bin/evince -- paplay /tmp/out.wav && echo "yes"
  yes

  For classic snaps:
  $ sudo snap install test-snapd-classic-confinement --classic

  $ snap run --shell test-snapd-classic-confinement

  $ cat /proc/self/attr/current   # verify we are classic confined
  snap.test-snapd-classic-confinement.test-snapd-classic-confinement (complain)

  $ paplay /usr/share/sounds/alsa/Noise.wav && echo "yes"
  yes

  $ rm -f /tmp/out.wav ; parecord /tmp/out.wav && echo "yes"  # ctrl-c to stop 
recording
  ^Cyes

  $ paplay /tmp/out.wav && echo "yes"
  yes

  For strict snaps with pulseaudio:
  $ sudo snap install --dangerous ./test-snapd-pulseaudio_1_amd64.snap

  $ snap connections test-snapd-pulseaudio
  Interface   Plug  Slot Notes
  pulseaudio  test-snapd-pulseaudio:pulseaudio  :pulseaudio  -

  $ test-snapd-pulseaudio.play --help  # ensure SNAP dirs are created
  ...

  $ sudo cp /usr/share/sounds/alsa/Noise.wav /var/snap/test-snapd-
  pulseaudio/common/

  $ test-snapd-pulseaudio.play /var/snap/test-snapd-pulseaudio/common/Noise.wav 
&& echo yes
  xcb_connection_has_error() returned true
  yes

  (note, the xcb_connection_has_error() message is due to the x11
  interface not being connecting which is unrelated to mediation. x11 is
  left out to ensure that just audio-playback/audio-record are tested)

  $ test-snapd-pulseaudio.record /tmp/out.wav && echo yes # should pass
  ...
  ^Cyes

  $ test-snapd-pulseaudio.play /tmp/out.wav && echo yes
  ...
  yes

  For strict snaps with audio-playback/audio-record:
  $ sudo snap refresh core --candidate # make sure have 2.41. 'install' on 16.04
  $ sudo snap install --dangerous ./test-snapd-audio-record_1_amd64.snap

  $ snap connections test-snapd-audio-record  # record not connected
  Interface   PlugSlot Notes
  audio-playback

[Desktop-packages] [Bug 1851640] Re: package chromium-browser 77.0.3865.120-0ubuntu1.19.10.1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before att

2019-11-07 Thread Apport retracing service

** Tags removed: need-duplicate-check

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

Title:
  package chromium-browser 77.0.3865.120-0ubuntu1.19.10.1 failed to
  install/upgrade: package is in a very bad inconsistent state; you
  should  reinstall it before attempting a removal

Status in chromium-browser package in Ubuntu:
  New

Bug description:
  Unable to remove chromium since if failed the installation.

  ProblemType: Package
  DistroRelease: Ubuntu 19.10
  Package: chromium-browser 77.0.3865.120-0ubuntu1.19.10.1
  ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
  Uname: Linux 5.3.0-19-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.1
  Architecture: amd64
  Date: Thu Nov  7 19:39:12 2019
  DuplicateSignature:
   package:chromium-browser:77.0.3865.120-0ubuntu1.19.10.1
   Removing chromium-chromedriver (77.0.3865.120-0ubuntu1.19.10.1) ...
   dpkg: error processing package chromium-browser (--remove):
package is in a very bad inconsistent state; you should
  ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting a removal
  InstallationDate: Installed on 2019-11-02 (4 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  Python3Details: /usr/bin/python3.7, Python 3.7.5rc1, python3-minimal, 3.7.5-1
  PythonDetails: /usr/bin/python2.7, Python 2.7.17rc1, python-minimal, 2.7.17-1
  RelatedPackageVersions:
   dpkg 1.19.7ubuntu2
   apt  1.9.4
  Snap.ChromeDriverVersion: Error: command ['snap', 'run', 
'chromium.chromedriver', '--version'] failed with exit code 1: error: cannot 
find current revision for snap chromium: readlink /snap/chromium/current: no 
such file or directory
  Snap.ChromiumVersion: Error: command ['snap', 'run', 'chromium', '--version'] 
failed with exit code 1: error: cannot find current revision for snap chromium: 
readlink /snap/chromium/current: no such file or directory
  Snap.Connections: Error: command ['snap', 'connections', 'chromium'] failed 
with exit code 1: error: cannot communicate with server: Get 
http://localhost/v2/connections?select=all=chromium: dial unix 
/run/snapd.socket: connect: connection refused
  Snap.Info.chromium: Error: command ['snap', 'info', '--abs-time', 'chromium'] 
failed with exit code 1: error: no snap found for "chromium"
  Snap.Info.core: Error: command ['snap', 'info', '--abs-time', 'core'] failed 
with exit code 1: error: no snap found for "core"
  Snap.Info.core18: Error: command ['snap', 'info', '--abs-time', 'core18'] 
failed with exit code 1: error: no snap found for "core18"
  Snap.Info.gtk-common-themes: Error: command ['snap', 'info', '--abs-time', 
'gtk-common-themes'] failed with exit code 1: error: no snap found for 
"gtk-common-themes"
  SourcePackage: chromium-browser
  Title: package chromium-browser 77.0.3865.120-0ubuntu1.19.10.1 failed to 
install/upgrade: package is in a very bad inconsistent state; you should  
reinstall it before attempting a removal
  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/1851640/+subscriptions

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

[Desktop-packages] [Bug 1851640] [NEW] package chromium-browser 77.0.3865.120-0ubuntu1.19.10.1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before a

2019-11-07 Thread Paskinell Rendal

Public bug reported:

Unable to remove chromium since if failed the installation.

ProblemType: Package
DistroRelease: Ubuntu 19.10
Package: chromium-browser 77.0.3865.120-0ubuntu1.19.10.1
ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
Uname: Linux 5.3.0-19-generic x86_64
ApportVersion: 2.20.11-0ubuntu8.1
Architecture: amd64
Date: Thu Nov  7 19:39:12 2019
DuplicateSignature:
 package:chromium-browser:77.0.3865.120-0ubuntu1.19.10.1
 Removing chromium-chromedriver (77.0.3865.120-0ubuntu1.19.10.1) ...
 dpkg: error processing package chromium-browser (--remove):
  package is in a very bad inconsistent state; you should
ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting a removal
InstallationDate: Installed on 2019-11-02 (4 days ago)
InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
Python3Details: /usr/bin/python3.7, Python 3.7.5rc1, python3-minimal, 3.7.5-1
PythonDetails: /usr/bin/python2.7, Python 2.7.17rc1, python-minimal, 2.7.17-1
RelatedPackageVersions:
 dpkg 1.19.7ubuntu2
 apt  1.9.4
Snap.ChromeDriverVersion: Error: command ['snap', 'run', 
'chromium.chromedriver', '--version'] failed with exit code 1: error: cannot 
find current revision for snap chromium: readlink /snap/chromium/current: no 
such file or directory
Snap.ChromiumVersion: Error: command ['snap', 'run', 'chromium', '--version'] 
failed with exit code 1: error: cannot find current revision for snap chromium: 
readlink /snap/chromium/current: no such file or directory
Snap.Connections: Error: command ['snap', 'connections', 'chromium'] failed 
with exit code 1: error: cannot communicate with server: Get 
http://localhost/v2/connections?select=all=chromium: dial unix 
/run/snapd.socket: connect: connection refused
Snap.Info.chromium: Error: command ['snap', 'info', '--abs-time', 'chromium'] 
failed with exit code 1: error: no snap found for "chromium"
Snap.Info.core: Error: command ['snap', 'info', '--abs-time', 'core'] failed 
with exit code 1: error: no snap found for "core"
Snap.Info.core18: Error: command ['snap', 'info', '--abs-time', 'core18'] 
failed with exit code 1: error: no snap found for "core18"
Snap.Info.gtk-common-themes: Error: command ['snap', 'info', '--abs-time', 
'gtk-common-themes'] failed with exit code 1: error: no snap found for 
"gtk-common-themes"
SourcePackage: chromium-browser
Title: package chromium-browser 77.0.3865.120-0ubuntu1.19.10.1 failed to 
install/upgrade: package is in a very bad inconsistent state; you should  
reinstall it before attempting a removal
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-package eoan

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

Title:
  package chromium-browser 77.0.3865.120-0ubuntu1.19.10.1 failed to
  install/upgrade: package is in a very bad inconsistent state; you
  should  reinstall it before attempting a removal

Status in chromium-browser package in Ubuntu:
  New

Bug description:
  Unable to remove chromium since if failed the installation.

  ProblemType: Package
  DistroRelease: Ubuntu 19.10
  Package: chromium-browser 77.0.3865.120-0ubuntu1.19.10.1
  ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
  Uname: Linux 5.3.0-19-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.1
  Architecture: amd64
  Date: Thu Nov  7 19:39:12 2019
  DuplicateSignature:
   package:chromium-browser:77.0.3865.120-0ubuntu1.19.10.1
   Removing chromium-chromedriver (77.0.3865.120-0ubuntu1.19.10.1) ...
   dpkg: error processing package chromium-browser (--remove):
package is in a very bad inconsistent state; you should
  ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting a removal
  InstallationDate: Installed on 2019-11-02 (4 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  Python3Details: /usr/bin/python3.7, Python 3.7.5rc1, python3-minimal, 3.7.5-1
  PythonDetails: /usr/bin/python2.7, Python 2.7.17rc1, python-minimal, 2.7.17-1
  RelatedPackageVersions:
   dpkg 1.19.7ubuntu2
   apt  1.9.4
  Snap.ChromeDriverVersion: Error: command ['snap', 'run', 
'chromium.chromedriver', '--version'] failed with exit code 1: error: cannot 
find current revision for snap chromium: readlink /snap/chromium/current: no 
such file or directory
  Snap.ChromiumVersion: Error: command ['snap', 'run', 'chromium', '--version'] 
failed with exit code 1: error: cannot find current revision for snap chromium: 
readlink /snap/chromium/current: no such file or directory
  Snap.Connections: Error: command ['snap', 'connections', 'chromium'] failed 
with exit code 1: error: cannot communicate with server: Get 
http://localhost/v2/connections?select=all=chromium: dial unix

[Desktop-packages] [Bug 1850827] Re: nvidia-graphics-drivers-430 430.50-0ubuntu3 ADT test failure with linux 5.4.0-3.4

2019-11-07 Thread Alberto Milone

This is fixed in focal-proposed:
https://launchpad.net/ubuntu/+source/nvidia-graphics-drivers-440/440.31-0ubuntu1

The 440 series replaces the 430 series, and it builds correctly with
Linux 5.4

:~# dkms status
nvidia, 440.31, 5.3.0-21-generic, x86_64: installed
nvidia, 440.31, 5.4.0-4-generic, x86_64: installed

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

Title:
  nvidia-graphics-drivers-430 430.50-0ubuntu3 ADT test failure with
  linux 5.4.0-3.4

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

Bug description:
  Testing failed on:
  amd64: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-focal-canonical-kernel-team-unstable/focal/amd64/n/nvidia-graphics-drivers-430/20191030_143532_ead01@/log.gz

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

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

[Desktop-packages] [Bug 1830408] Re: [nouveau][XFCE] Do not see login screen after screen is blanked

2019-11-07 Thread Theo Linkspfeifer

I suggest that you upgrade to 19.10 and replace light-locker with the
new xfce4-screensaver.

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

Title:
  [nouveau][XFCE] Do not see login screen after screen is blanked

Status in lightdm package in Ubuntu:
  New

Bug description:
  I've just upgraded to 18.10 from 18.04. Now when power manager (or
  whoever) puts the screen to blank, I cannot login, because I do not
  see anything. Befeore the upgrade, mouse move or keypress led to login
  screen. Now does not.

  Workaround:
  When I go to terminal on tty1 and then back CTRL+ALT+F7, login screen appears.

  Where is the problem and how to fix it please?

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: xorg 1:7.7+19ubuntu8
  ProcVersionSignature: Ubuntu 4.18.0-20.21-generic 4.18.20
  Uname: Linux 4.18.0-20-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13.3
  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: XFCE
  Date: Fri May 24 17:59:31 2019
  DistUpgraded: 2019-05-24 13:40:45,847 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process 
“./xorg_fix_proprietary.py” (No such file or directory) (8))
  DistroCodename: cosmic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. 2nd Generation Core Processor Family 
Integrated Graphics Controller [1043:1682]
   NVIDIA Corporation GF119M [GeForce GT 520M] [10de:1050] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: ASUSTeK Computer Inc. GF119M [GeForce GT 520M] [1043:1682]
  InstallationDate: Installed on 2018-09-03 (263 days ago)
  InstallationMedia: Xubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: ASUSTeK Computer Inc. U36SD
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.18.0-20-generic 
root=UUID=aa87c0a2-5b06-40fb-82dd-fbccd7c800e6 ro quiet splash vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to cosmic on 2019-05-24 (0 days ago)
  dmi.bios.date: 07/12/2011
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: U36SD.205
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: U36SD
  dmi.board.vendor: ASUSTeK Computer Inc.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK Computer Inc.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrU36SD.205:bd07/12/2011:svnASUSTeKComputerInc.:pnU36SD:pvr1.0:rvnASUSTeKComputerInc.:rnU36SD:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr1.0:
  dmi.product.family: U
  dmi.product.name: U36SD
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK Computer Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.95-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.8-0ubuntu0~18.10.2
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.8-0ubuntu0~18.10.2
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.1-3ubuntu2.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-3

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

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

[Desktop-packages] [Bug 1765363] Re: prime-select intel is not powering off the nvidia card

2019-11-07 Thread Vicente R

Same issue for me. Power consumption ~10W higher than normal on intel
mode since some update around that happened around this past month.
Previously had to use the command echo 'auto' >
'/sys/bus/pci/devices/:01:00.0/power/control' (from powertop's
tunables) to shut down the dGPU but otherwise worked fine.

Ubuntu 18.04.3, sddm
Legion Y530, Nvidia GTX 1050M
Tested on kernel 5.3 and nvidia 430.50 and on a fresh installation with default 
kernel and nvidia drivers

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

Title:
  prime-select intel is not powering off the nvidia card

Status in nvidia-prime package in Ubuntu:
  Confirmed

Bug description:
  Right now, it seems that prime-select intel makes sure the nvidia driver is 
not loaded, as nvidia-settings reports.
  But my power consumption is > 20W.
  cat /proc/acpi/bbswitch reports the card is still on. 

  
  If bbswitch and powertop are reliable, then the nvidia card is still powered.
  This is a thinkpad w520 in Optimus mode.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: nvidia-prime 0.8.7
  ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15
  Uname: Linux 4.15.0-15-generic x86_64
  ApportVersion: 2.20.9-0ubuntu5
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Apr 19 19:56:21 2018
  Dependencies:
   
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2017-12-14 (125 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  PackageArchitecture: all
  SourcePackage: nvidia-prime
  UpgradeStatus: Upgraded to bionic on 2018-03-09 (41 days ago)

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

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

[Desktop-packages] [Bug 1851621] Re: Chromium deb -> Snap broke kubuntu integration

The plasma integration regression is tracked by bug #1741074.

Incorrect mouse pointers is also a known issue: bug #1833611.

Let's repurpose this bug to track the problem with KDE file dialogs.

** Summary changed:

- Chromium deb -> Snap broke kubuntu integration
+ [snap] No KDE file dialogs

** Tags added: snap

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

Title:
  [snap] No KDE file dialogs

Status in chromium-browser package in Ubuntu:
  New

Bug description:
  I upgraded from kubuntu 19.04 to 19.10 and noticed that chromium does
  not integrate anymore. Plasma integration Fails to connect to the
  native host (suggested google solutions didn't work), Kubuntu mouse
  pointers change to ugly ones (I bellive GTK fallback), no kde file
  dialog when opening/saving files.

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

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

[Desktop-packages] [Bug 1849160] Re: after deb->snap transition, chromium no longer sees local password store

2019-11-07 Thread Giovanni Pelosi

Alter Ubuntu 19.04 => 19.10 upgrade

Chromium passwords are still not working

- password not imported
- password not synced with other systems
- password not saved


I've tried:

---

snap connect chromium:password-manager-service

the command:

snap connections chromium | grep password

returns

password-manager-service  chromium:password-manager-service  :password-
manager-service   manual

---

~ snap list chromium
Name  Version   Rev  Tracking  Publisher   Notes
chromium  78.0.3904.70  920  stablecanonical✓  -

~ apt policy chromium-browser
chromium-browser:
  Installed: 77.0.3865.120-0ubuntu1.19.10.1
  Candidate: 77.0.3865.120-0ubuntu1.19.10.1
  Version table:
 *** 77.0.3865.120-0ubuntu1.19.10.1 500
500 http://it.archive.ubuntu.com/ubuntu eoan-updates/universe amd64 
Packages
100 /var/lib/dpkg/status
 77.0.3865.120-0ubuntu1~snap1 500
500 http://it.archive.ubuntu.com/ubuntu eoan/universe amd64 Packages

---

reimporting old config

mv ~/snap/chromium/current/.config ~/snap/chromium/current/.config.000


chromium-browser  

Importing existing chromium profile from /home/xxx/.config/chromium (version 
76.0.3809.100)
Import done in 12.293 s

what i see here:

[8384:8766:1107/113136.480119:ERROR:token_service_table.cc(140)] Failed to 
decrypt token for service AccountId-101040866152128307883
[8384:8766:1107/113136.480171:ERROR:token_service_table.cc(140)] Failed to 
decrypt token for service AccountId-111604898276580333411
[8384:8766:1107/113136.480196:ERROR:token_service_table.cc(140)] Failed to 
decrypt token for service AccountId-117219250637178212384
[8384:8766:1107/113136.480221:ERROR:token_service_table.cc(140)] Failed to 
decrypt token for service AccountId-116924599772170384880
[8384:8766:1107/113136.480242:ERROR:token_service_table.cc(140)] Failed to 
decrypt token for service AccountId-106555677384077017077
[8384:8384:1107/113137.484604:ERROR:account_tracker.cc(241)] AccessTokenFetched 
error: Invalid credentials (credentials missing).
[8384:8384:1107/113137.484926:ERROR:account_info_fetcher.cc(60)] 
OnGetTokenFailure: Invalid credentials (credentials missing).
[8384:8384:1107/113139.303513:ERROR:data_type_manager_impl.cc(38)] Passwords 
cryptographer error was encountered: 
...
[8384:8697:1107/113149.949701:ERROR:gcm_store_impl.cc(936)] Failed to restore 
security token.
...
[8384:8995:1107/113313.221960:ERROR:database.cc(1581)] Passwords sqlite error 
2067, errno 0: UNIQUE constraint failed: logins.origin_url, 
logins.username_element, logins.username_value, logins.password_element, 
logins.signon_realm, sql: INSERT INTO logins (origin_url, action_url, 
username_element, username_value, password_element, password_value, 
submit_element, signon_realm, preferred, date_created, blacklisted_by_user, 
scheme, password_type, times_used, form_data, date_synced, display_name, 
icon_url, federation_url, skip_zero_click, generation_upload_status, 
possible_username_pairs, id, date_last_used) VALUES 
(?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?)
[8384:8384:1107/113315.265525:ERROR:gaia_auth_fetcher.cc(76)] Missing ID token 
on refresh token fetch response.
[8384:8770:1107/113315.689058:ERROR:password_syncable_service.cc(193)] 
Passwords datatype error was encountered: Failed to get passwords from store.


---

i use multiple profiles with *gmail account and private domain google
accounts

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

Title:
  after deb->snap transition, chromium no longer sees local password
  store

Status in chromium-browser package in Ubuntu:
  Fix Released
Status in chromium-browser source package in Eoan:
  Fix Released

Bug description:
  [Impact]

  After upgrading to eoan and accepting the deb->snap transition for
  chromium, the passwords saved in my browser are no longer available to
  the app, despite
  ~/snap/chromium/current/.config/chromium/Default/Login Data being
  present and fully-populated. If I go into settings, I see Saved
  Passwords: Saved passwords will appear here.

  The data doesn't appear to be lost, since I have a copy in ~/snap as
  well as in ~/.config/chromium, but somehow they're inaccessible.

  
  [Test Case]

  Install chromium-browser in disco (19.04), save a few passwords for login 
forms.
  Dist-upgrade to eoan (19.10), launch chromium, and verify that the saved 
passwords are still there. They can be inspected by browsing to 
chrome://settings/passwords.
  As an additional check, the output of `snap connections chromium | grep 
password` should look like this:

  password-manager-service  chromium:password-manager-service
  :password-manager-service   manual

  I.e. the interface should be marked as manually connected, even though
  the user hasn't explicitly connected it.

  
  [Regression Potential]

  Low. The change removes an assumption on upgrade paths

[Desktop-packages] [Bug 1851621] Re: Chromium deb -> Snap broke kubuntu integration

2019-11-07 Thread Chris Guiver

Thank you for taking the time to report this bug and helping to make
Ubuntu better. Please execute the following command only once, as it
will automatically gather debugging information, in a terminal:

apport-collect 1851621

When reporting bugs in the future please use apport by using 'ubuntu-
bug' and the name of the package affected. You can learn more about this
functionality at https://wiki.ubuntu.com/ReportingBugs.

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

Title:
  Chromium deb -> Snap broke kubuntu integration

Status in chromium-browser package in Ubuntu:
  New

Bug description:
  I upgraded from kubuntu 19.04 to 19.10 and noticed that chromium does
  not integrate anymore. Plasma integration Fails to connect to the
  native host (suggested google solutions didn't work), Kubuntu mouse
  pointers change to ugly ones (I bellive GTK fallback), no kde file
  dialog when opening/saving files.

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

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

[Desktop-packages] [Bug 1850969] Re: x11 session all mouse or keyboard action ignored

** Changed in: gnome-shell
   Status: New => Fix Released

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

Title:
  x11 session all mouse or keyboard action ignored

Status in GNOME Shell:
  Fix Released
Status in gnome-shell package in Ubuntu:
  In Progress

Bug description:
  Starting with x1 session all mouse or keyboard action are ignored. Only mouse 
arrow moves on the desktop.
  was able to exit only with cntrl+alt+f3
  wayland session works fine.
  Also booting from USB live and selecting 'try ubuntu' has the same problem.
  selecting install the install run smoothly but the just installed system has 
the problem.

  same problem with ISO dated 20191030 20191031 20191101 and 20191021
  after update+upgrade

  corrado@corrado-p13-ff-1101:~/Desktop$ inxi -Fx
  System:Host: corrado-p13-ff-1101 Kernel: 5.3.0-18-generic x86_64 bits: 64 
compiler: gcc v: 9.2.1 Desktop: Gnome 3.34.1 
 Distro: Ubuntu 20.04 LTS (Focal Fossa) 
  Machine:   Type: Desktop Mobo: ASRock model: H110M-G/M.2 serial:  UEFI: American Megatrends v: P1.10 
 date: 05/11/2017 
  CPU:   Topology: Dual Core model: Intel Core i3-7100 bits: 64 type: MT 
MCP arch: Kaby Lake rev: 9 L2 cache: 3072 KiB 
 flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx 
bogomips: 31199 
 Speed: 801 MHz min/max: 800/3900 MHz Core speeds (MHz): 1: 800 2: 
800 3: 800 4: 800 
  Graphics:  Device-1: Intel HD Graphics 630 vendor: ASRock driver: i915 v: 
kernel bus ID: 00:02.0 
 Display: wayland server: X.Org 1.20.5 driver: i915 resolution: 
1920x1080~60Hz 
 OpenGL: renderer: Mesa DRI Intel HD Graphics 630 (Kaby Lake GT2) 
v: 4.5 Mesa 19.2.1 direct render: Yes 
  Audio: Device-1: Intel 100 Series/C230 Series Family HD Audio vendor: 
ASRock driver: snd_hda_intel v: kernel 
 bus ID: 00:1f.3 
 Sound Server: ALSA v: k5.3.0-18-generic 
  Network:   Device-1: Intel Ethernet I219-V vendor: ASRock driver: e1000e v: 
3.2.6-k port: f040 bus ID: 00:1f.6 
 IF: enp0s31f6 state: up speed: 100 Mbps duplex: full mac: 
70:85:c2:44:7b:86 
  Drives:Local Storage: total: 931.51 GiB used: 4.87 GiB (0.5%) 
 ID-1: /dev/sda vendor: Toshiba model: DT01ACA100 size: 931.51 GiB 
temp: 34 C 
  Partition: ID-1: / size: 15.62 GiB used: 4.87 GiB (31.2%) fs: ext4 dev: 
/dev/sda13 
 ID-2: swap-1 size: 8.00 GiB used: 0 KiB (0.0%) fs: swap dev: 
/dev/sda2 
  Sensors:   System Temperatures: cpu: 38.5 C mobo: N/A 
 Fan Speeds (RPM): N/A 
  Info:  Processes: 205 Uptime: 16m Memory: 7.49 GiB used: 1.11 GiB (14.8%) 
Init: systemd runlevel: 5 Compilers: 
 gcc: 9.2.1 Shell: bash v: 5.0.3 inxi: 3.0.36 
  corrado@corrado-p13-ff-1101:~/Desktop$

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu12
  ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1
  Uname: Linux 5.3.0-18-generic x86_64
  ApportVersion: 2.20.11-0ubuntu9
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Nov  1 18:13:53 2019
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation HD Graphics 630 [8086:5912] (rev 04) (prog-if 00 [VGA 
controller])
 Subsystem: ASRock Incorporation HD Graphics 630 [1849:5912]
  InstallationDate: Installed on 2019-11-01 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20191101)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 046d:c016 Logitech, Inc. Optical Wheel Mouse
   Bus 001 Device 002: ID 058f:6377 Alcor Micro Corp. AU6375 4-LUN card reader
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-18-generic 
root=UUID=062c7ec4-2948-49df-934f-d054f397e4c4 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/11/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P1.10
  dmi.board.name: H110M-G/M.2
  dmi.board.vendor: ASRock
  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.:bvrP1.10:bd05/11/2017:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnH110M-G/M.2:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.sku: To Be Filled By O.E.M.
  dmi.product.version: To Be

[Desktop-packages] [Bug 1850615] Re: gnome-shell hardlocks under load

2019-11-07 Thread Michał Sawicz

Here's a gdb log, it hung again with all extensions disabled, under
heavier IO and load.

** Attachment added: "gdb.txt"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1850615/+attachment/5303423/+files/gdb.txt

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

Title:
  gnome-shell hardlocks under load

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  With the upgrade to eoan, my GNOME and Ubuntu sessions started locking
  up hard when under load (i.e. when I start my session and start a
  bunch of applications).

  I couldn't find anything special in gdb, whether it's stuck or not,
  the stack looks mostly the same:

  (gdb) info threads
Id   Target Id  Frame 
  * 1Thread 0x7f7439f6bcc0 (LWP 26352) "gnome-shell"0x7f743f7f5c2f 
in __GI___poll (fds=0x7ffc1a361ba8, nfds=1, timeout=-1) at 
../sysdeps/unix/sysv/linux/poll.c:29
2Thread 0x7f7439f68700 (LWP 26354) "gmain"  0x7f743f7f5c2f 
in __GI___poll (fds=0x556aeb3369e0, nfds=2, timeout=-1) at 
../sysdeps/unix/sysv/linux/poll.c:29
3Thread 0x7f7433fff700 (LWP 26356) "gdbus"  0x7f743f7f5c2f 
in __GI___poll (fds=0x7f73fc002070, nfds=4, timeout=-1) at 
../sysdeps/unix/sysv/linux/poll.c:29
4Thread 0x7f74337fe700 (LWP 26357) "dconf worker"   0x7f743f7f5c2f 
in __GI___poll (fds=0x556aeb377c50, nfds=1, timeout=-1) at 
../sysdeps/unix/sysv/linux/poll.c:29
5Thread 0x7f7432336700 (LWP 26358) "gnome-s:disk$0" 
futex_wait_cancelable (private=, expected=0, 
futex_word=0x556aeb339d28) at ../sysdeps/unix/sysv/linux/futex-internal.h:80
6Thread 0x7f74311a7700 (LWP 26384) "JS Helper"  
futex_wait_cancelable (private=, expected=0, 
futex_word=0x556aeb334468) at ../sysdeps/unix/sysv/linux/futex-internal.h:80
7Thread 0x7f7430fa6700 (LWP 26385) "JS Helper"  
futex_wait_cancelable (private=, expected=0, 
futex_word=0x556aeb334468) at ../sysdeps/unix/sysv/linux/futex-internal.h:80
8Thread 0x7f7430da5700 (LWP 26386) "JS Helper"  
futex_wait_cancelable (private=, expected=0, 
futex_word=0x556aeb334468) at ../sysdeps/unix/sysv/linux/futex-internal.h:80
9Thread 0x7f7430ba4700 (LWP 26387) "JS Helper"  
futex_wait_cancelable (private=, expected=0, 
futex_word=0x556aeb33446c) at ../sysdeps/unix/sysv/linux/futex-internal.h:80
10   Thread 0x7f74082d4700 (LWP 26696) "threaded-ml"0x7f743f7f5c2f 
in __GI___poll (fds=0x7f73f4002910, nfds=3, timeout=-1) at 
../sysdeps/unix/sysv/linux/poll.c:29
11   Thread 0x7f73d3fff700 (LWP 2290) "threaded-ml" 0x7f743f7f5c2f 
in __GI___poll (fds=0x7f73cc003130, nfds=3, timeout=-1) at 
../sysdeps/unix/sysv/linux/poll.c:29

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: gnome-shell 3.34.1-1ubuntu1
  ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
  Uname: Linux 5.3.0-19-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu8
  Architecture: amd64
  Date: Wed Oct 30 10:46:53 2019
  DisplayManager: gdm3
  RelatedPackageVersions: mutter-common 3.34.1-1ubuntu1
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to eoan on 2019-10-28 (1 days ago)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  CurrentDesktop: GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 19.10
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  Package: gnome-shell 3.34.1-1ubuntu1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
  RelatedPackageVersions: mutter-common 3.34.1-1ubuntu1
  Tags:  eoan
  Uname: Linux 5.3.0-19-generic x86_64
  UpgradeStatus: Upgraded to eoan on 2019-10-28 (9 days ago)
  UserGroups: adm cdrom dialout dip docker kvm libvirt lp lpadmin lxd plugdev 
sambashare sudo vboxusers wireshark
  _MarkForUpload: True

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

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

[Desktop-packages] [Bug 1851621] [NEW] Chromium deb -> Snap broke kubuntu integration

2019-11-07 Thread Javier Urien

Public bug reported:

I upgraded from kubuntu 19.04 to 19.10 and noticed that chromium does
not integrate anymore. Plasma integration Fails to connect to the native
host (suggested google solutions didn't work), Kubuntu mouse pointers
change to ugly ones (I bellive GTK fallback), no kde file dialog when
opening/saving files.

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


** Tags: kde kubuntu

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

Title:
  Chromium deb -> Snap broke kubuntu integration

Status in chromium-browser package in Ubuntu:
  New

Bug description:
  I upgraded from kubuntu 19.04 to 19.10 and noticed that chromium does
  not integrate anymore. Plasma integration Fails to connect to the
  native host (suggested google solutions didn't work), Kubuntu mouse
  pointers change to ugly ones (I bellive GTK fallback), no kde file
  dialog when opening/saving files.

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

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

[Desktop-packages] [Bug 1845285] Re: SRU request: Include xf86-input-wacom - 1:0.36.1-0ubuntu2 in Ubuntu 18.04

2019-11-07 Thread Cyrus Lien

** Changed in: oem-priority
   Status: Confirmed => Invalid

** Changed in: oem-priority/bionic
   Status: Confirmed => Invalid

** Changed in: xf86-input-wacom (Ubuntu)
   Status: New => Invalid

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

Title:
  SRU request: Include xf86-input-wacom - 1:0.36.1-0ubuntu2 in Ubuntu
  18.04

Status in OEM Priority Project:
  Invalid
Status in OEM Priority Project bionic series:
  Invalid
Status in xf86-input-wacom package in Ubuntu:
  Invalid

Bug description:
  SRU Request:

  [Impact]
  xf86-input-wacom version 1:0.36.1-0ubuntu1 shipped 
/usr/share/X11/xorg.conf.d/70-wacom.conf has this:

  Section "InputClass"
  Identifier "Wacom touchscreen class"
  MatchProduct "Wacom|WACOM|PTK-540WL|ISD-V4"
  MatchDevicePath "/dev/input/event*"
  MatchIsTouchscreen "true"
  Driver "wacom"
  EndSection

  Which config let Wacom touchscreen using wacom input driver and makes
  the touchscreen act incorrectly.

  https://bugs.launchpad.net/ubuntu/+source/xf86-input-
  wacom/+bug/1774242 (comment #14)

  [Test Case]
  1) Enable the bionic-proposed repository, and install the xf86-input-wacom 
package

  2) Restart and see if the Wacom touchscreen works correctly. Also
  check /var/log/Xorg.0.log to see if Wacom touchscreen using libinput
  driver instead wacom driver.

  [Regression Potential]
  Low, the package  xf86-input-wacom - 1:0.36.1-0ubuntu2  is already in Eoan 
and Disco.

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1845285/+subscriptions

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

[Desktop-packages] [Bug 1851564] Re: Daily Limit Exceeded messages for google calendars

Thank you for your bug report, it's probably
https://gitlab.gnome.org/GNOME/gnome-online-accounts/issues/42 , GNOME
failing to get their API key re-approved by Google, hopefully they sort
it out soon though

** Bug watch added: gitlab.gnome.org/GNOME/gnome-online-accounts/issues #42
   https://gitlab.gnome.org/GNOME/gnome-online-accounts/issues/42

** Package changed: gnome-calendar (Ubuntu) => gnome-online-accounts
(Ubuntu)

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

** Changed in: gnome-online-accounts (Ubuntu)
   Status: New => Confirmed

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

Title:
  Daily Limit Exceeded messages for google calendars

Status in gnome-online-accounts package in Ubuntu:
  Confirmed

Bug description:
  This seems to coincide with the 19.04 -> 19.10 upgrade, but I only
  have logs going back to mid august.  The message is repeated for each
  calendar at various times.

  Nov 06 13:49:13 dipper gnome-calendar[8681]:
  source_credentials_required_cb: Failed to authenticate 'Kai Groner':
  Daily Limit Exceeded. The quota will be reset at midnight Pacific Time
  (PT). You may monitor your quota usage and adjust limits in the API
  Console:
  
https://console.developers.google.com/apis/api/caldav.googleapis.com/quotas?project=44438659992

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: gnome-calendar 3.34.2-1
  ProcVersionSignature: Ubuntu 5.3.0-19.20+kai1-generic 5.3.1
  Uname: Linux 5.3.0-19-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Nov  6 15:07:56 2019
  InstallationDate: Installed on 2019-06-18 (141 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  ProcEnviron:
   TERM=tmux-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-calendar
  UpgradeStatus: Upgraded to eoan on 2019-10-23 (14 days ago)

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

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

[Desktop-packages] [Bug 540751] Re: Unable to use dead keys with java and ibus

The bug here is old, rather than reopening it please open a new one
using 'ubuntu-bug ibus' with a detailled description of the issue and
how to trigger it

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

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

Title:
  Unable to use dead keys with java and ibus

Status in ibus package in Ubuntu:
  Invalid
Status in openjdk-6 package in Ubuntu:
  Invalid
Status in openjdk-7 package in Ubuntu:
  Invalid

Bug description:
  Using latest Lucid packages, I am unable to use ^ key to generate ê
  french character in every Java programs (jEdit, Netbeans, etc.).

  Typing ^ + e give just the e character.
  Typing ^ + Space and nothing appears.

  I've tried with Sun JDK (6u18, 6u20, 7) and the bug is still present.

  I've tried to remove ibus and everything works again (I've just unset
  XMODIFIERS and GTK_IM_MODULE).

  I don't know if it's an ibus bug or openjdk one.

  ProblemType: Bug
  Architecture: amd64
  Date: Thu Mar 18 09:03:11 2010
  DistroRelease: Ubuntu 10.04
  ExecutablePath: /usr/lib/jvm/java-6-openjdk/jre/bin/java
  InstallationMedia: Error: [Errno 13] Permission non accordée: 
'/var/log/installer/media-info'
  NonfreeKernelModules: nvidia
  Package: openjdk-6-jre-headless 6b18~pre2-1ubuntu1
  ProcEnviron:
   SHELL=/bin/bash
   PATH=(custom, user)
   LANG=fr_FR.utf8
  ProcVersionSignature: Ubuntu 2.6.32-16.25-genUser Name
  SourcePackage: openjdk-6
  Uname: Linux 2.6.32-16-generic x86_64

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

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

[Desktop-packages] [Bug 1753070] Re: Cannot restore default alert sound (Ubuntu bell)

** Tags added: desktop-lts-wishlist

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

Title:
  Cannot restore default alert sound (Ubuntu bell)

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

Bug description:
  After changing the default alert sound in Settings > Sound > Sound
  Effects, I cannot restore the alert sound to the Ubuntu 17.10 default.
  Gnome Control Center version: 1:3.26.2-0ubuntu0.2

  There are five options in the Sound Effects tab: Default, Bark, Drip,
  Glass and Sonar. Selecting Default gives the same sound as Drip, which
  is not the default I had before.

  I think the sound options come from
  /usr/share/sounds/gnome/default/alerts where I found Ogg files for the
  Bark, Drip, Glass and Sonar options (but not for Default). The
  /usr/share/sounds/ubuntu/stereo/bell.ogg seems to have been the
  original default alert sound, to which I cannot restore.

  I am not sure if this is related, but when I opened the Sound Effects
  tab for the first time, the Alert Volume slider was at 0% and grayed
  out. The alert sound was working fine, so I guess that default
  settings from elsewhere were in effect until I started adjusting
  things in this tab and thereby overriding those default settings. I
  cannot restore to that grayed out state either in this tab.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-control-center 1:3.26.2-0ubuntu0.2
  ProcVersionSignature: Ubuntu 4.13.0-36.40-generic 4.13.13
  Uname: Linux 4.13.0-36-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Mar  3 11:17:54 2018
  InstallationDate: Installed on 2018-02-09 (21 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
  SourcePackage: gnome-control-center
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1828107] Re: gvfs can't list shares from smb servers that disabled SMB1

** Tags added: desktop-lts-wishlist

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

Title:
  gvfs can't list shares from smb servers that disabled SMB1

Status in gvfs:
  New
Status in gvfs package in Ubuntu:
  Triaged

Bug description:
  After bug #1778322 is fixed (just needs a gvfs rebuild with newer
  samba), samba machines will start to show up again in the "windows
  network" tab in nautilus. But if a server has disabled the SMB1
  protocol, nautilus will show an error when that server is clicked on,
  instead of showing the shares list.

  Even with SMB1 disabled, it should still be technically possible to
  get a share list, since smbclient can do it:

  andreas@nsnx:~$ nmblookup -A 192.168.122.101
  Looking up status of 192.168.122.101
D-NO-SMB1   <00> - B  
D-NO-SMB1   <03> - B  
D-NO-SMB1   <20> - B  
..__MSBROWSE__. <01> -  B  
WORKGROUP   <00> -  B  
WORKGROUP   <1d> - B  
WORKGROUP   <1e> -  B  

  MAC Address = 00-00-00-00-00-00

  andreas@nsnx:~$ smbclient -L 192.168.122.101 -N
  WARNING: The "syslog" option is deprecated

Sharename   Type  Comment
-     ---
print$  Disk  Printer Drivers
pub_no_smb1 Disk  
IPC$IPC   IPC Service (d-no-smb1 server (Samba, Ubuntu))
  Reconnecting with SMB1 for workgroup listing.
  protocol negotiation failed: NT_STATUS_INVALID_NETWORK_RESPONSE
  Failed to connect with SMB1 -- no workgroup available

  andreas@nsnx:~$ smbclient //192.168.122.101/pub_no_smb1 -U ubuntu%ubuntu -m 
NT1
  WARNING: The "syslog" option is deprecated
  protocol negotiation failed: NT_STATUS_INVALID_NETWORK_RESPONSE

  andreas@nsnx:~$ smbclient //192.168.122.101/pub_no_smb1 -U ubuntu%ubuntu -m 
SMB2
  WARNING: The "syslog" option is deprecated
  Try "help" to get a list of possible commands.
  smb: \> dir
.   D0  Fri May  3 18:16:38 2019
..  D0  Fri May  3 18:15:24 2019
hello.txt   N   21  Fri May  3 18:16:12 2019
hello-from-nsnx.txt A9  Fri May  3 18:16:38 2019

  20509264 blocks of size 1024. 13121800 blocks
  available

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

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

[Desktop-packages] [Bug 1630417] Re: Unity control center chokes on initial number in user name

** Tags added: desktop-lts-wishlist

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

Title:
   Unity control center chokes on initial number in user name

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

Bug description:
  This is a follow-up from bug 1600638.

  Debian's adduser does not allow the initial character of a username to
  be a digit. It would be nice if (unity/gnome)-control-center could
  detect this and disallow it or recommend against it.

  What happens
  
  A popup that says

  Failed to add account 
  running '/usr/sbin/adduser' failed: Child process exited with code 1'

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

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

[Desktop-packages] [Bug 1849787] Re: The dock is shown in front of full screen windows since 19.10