[Desktop-packages] [Bug 1851340] [NEW] Ubuntu 19.10 upgrade results in invisible mouse cursor

2019-11-05 Thread John Hartley
Public bug reported:

Following in place upgrade of Ubuntu 19.04 -> 19.10 I no longer have
visible cursor with my Gnone desktop.

I have found the same problem when upgrading 2 machines from Ubuntu
19.04 -> 19.10.

Reproducing problem is easy:

1. Open Ubuntu Update Window
2. Select "Upgrade"
3. On completion of update (after reboot) cursor is no longer visible.
4. This applies to display connected to VGA port on host with USB Keyboard + 
Mouse

While the connected display has no visible cursor and so is usable, I
have always used X11VNC Server to provide network GUI access. On the
remote X11VNC display I see and can use the cursor.

This bug report is being sent via Remote X11VNC window, as I cannot use
the main VGA display window (due to lack of visible cursor)

I have done search online and thought that maybe issue was with my USB
Mighty Mouse, so I also tried with Logitech M100R USB Mouse. Same
result, no visible mouse cursor.

I have done: "grep usb /var/log/syslog" and can see many USB events,
including both Apple and Logitech mouse detection events.

NOTE:

Due to compatibility issue with X11VNC, I have disable Wayland on both
machines by adding the following option to: /etc/gdm3/custom.conf

WaylandEnable=false

Regards,

John Hartley.

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.1
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Tue Nov  5 18:25:23 2019
DistUpgraded: 2019-11-05 15:20:04,402 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: eoan
DistroVariant: ubuntu
GraphicsCard:
 Matrox Electronics Systems Ltd. G200eR2 [102b:0534] (rev 01) (prog-if 00 [VGA 
controller])
   Subsystem: Lenovo G200eR2 [1d49:0a01]
InstallationDate: Installed on 2018-12-17 (322 days ago)
InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3)
MachineType: LENOVO System x3650 M5: -[8871AC1]-
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-19-generic 
root=UUID=3b8f415b-7e78-461c-83df-64f1f1a7826a ro ipv6.disable=1 quiet splash 
iommu=1 intel_iommu=on ipv6.disable=1 vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: Upgraded to eoan on 2019-11-05 (0 days ago)
dmi.bios.date: 06/03/2019
dmi.bios.vendor: LENOVO
dmi.bios.version: -[TCE140H-2.91]-
dmi.board.asset.tag: (none)
dmi.board.name: 01KN179
dmi.board.vendor: LENOVO
dmi.board.version: NULL
dmi.chassis.asset.tag: none
dmi.chassis.type: 23
dmi.chassis.vendor: LENOVO
dmi.chassis.version: none
dmi.modalias: 
dmi:bvnLENOVO:bvr-[TCE140H-2.91]-:bd06/03/2019:svnLENOVO:pnSystemx3650M5-[8871AC1]-:pvr13:rvnLENOVO:rn01KN179:rvrNULL:cvnLENOVO:ct23:cvrnone:
dmi.product.family: System X
dmi.product.name: System x3650 M5: -[8871AC1]-
dmi.product.sku: (none)
dmi.product.version: 13
dmi.sys.vendor: LENOVO
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

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

Title:
  Ubuntu 19.10 upgrade results in invisible mouse cursor

Status in xorg package in Ubuntu:
  New

Bug description:
  Following in place upgrade of Ubuntu 19.04 -> 19.10 I no longer have
  visible cursor with my Gnone desktop.

  I have found the same problem when upgrading 2 machines from Ubuntu
  19.04 -> 19.10.

  Reproducing problem is easy:

  1. Open Ubuntu Update Window
  2. Select "Upgrade"
  3. On completion of update (after reboot) cursor is no longer visible.
  4. This applies to display connected to VGA port on host with USB Keyboard + 
Mouse

  While the connected display has no visible cursor and so is usable, I
  have always used X11VNC Server to provide network GUI access. On the
  remote X11VNC display I see and can use the cursor.

  This bug report is being sent via Remote X11VNC window, as I cannot
  use the main VGA display window (due to lack of visible cursor)

  I have done search online and thought that maybe issue was with my USB
  Mighty Mouse, so I also tried with Logitech M100R USB Mouse. Same
  result, no visibl

[Desktop-packages] [Bug 1786516] Re: Ubuntu taking screenshot at random times, keybaord down arrow maps to "q" and sometimes work fine.

2019-11-05 Thread Sudeep Patel
Seems had issue with particular update. After updating Ubuntu to new
version solved the issue.

Thanks for your reply

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

Title:
  Ubuntu taking screenshot at random times, keybaord down arrow maps to
  "q" and sometimes work fine.

Status in firefox package in Ubuntu:
  Expired

Bug description:
  I am running ubuntu 18.04 and my pc taking screenshots at random and saving 
in Pictures folders.
  also i observer my keyboard down arrow key maps to "q" and sometimes works 
fine. Not sure what is happening here. it is all random.

  Please advise.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: firefox 61.0.1+build1-0ubuntu0.18.04.1
  ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18
  Uname: Linux 4.15.0-29-generic x86_64
  NonfreeKernelModules: kpatch_livepatch_Ubuntu_4_15_0_29_31_generic_41
  AddonCompatCheckDisabled: False
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  sudeep 3883 F pulseaudio
   /dev/snd/controlC0:  sudeep 3883 F pulseaudio
  BuildID: 20180704192850
  Channel: Unavailable
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Aug 10 22:04:53 2018
  ExecutablePath: /usr/lib/firefox/firefox
  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)
  IpRoute:
   default via 192.168.0.1 dev wlp2s0 proto dhcp metric 600 
   192.168.0.0/24 dev wlp2s0 proto kernel scope link src 192.168.0.105 metric 
600 
   192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1 
linkdown
  Locales: extensions.sqlite corrupt or missing
  MostRecentCrashID: bp-101a5869-fe29-4f41-be1d-ba91f1180216
  PrefErrors: Unexpected character ',' whilst parsing int @ 
/usr/lib/firefox/defaults/pref/vendor-gre.js:8
  PrefSources: prefs.js
  ProcEnviron:
   LANGUAGE=en_IN:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_IN
   SHELL=/bin/bash
  Profiles: Profile0 (Default) - LastVersion=61.0.1/20180704192850 (In use)
  RunningIncompatibleAddons: False
  SourcePackage: firefox
  SubmittedCrashIDs: bp-101a5869-fe29-4f41-be1d-ba91f1180216
  Themes: extensions.sqlite corrupt or missing
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/23/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A19
  dmi.board.name: 0TR3VC
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA19:bd01/23/2018:svnDellInc.:pnLatitudeE5550:pvr:rvnDellInc.:rn0TR3VC:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: Latitude E5550
  dmi.sys.vendor: Dell Inc.

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

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


[Desktop-packages] [Bug 1851334] Re: Performance is not good system freeze a lot of time

2019-11-05 Thread Chris Guiver
Thank you for taking the time to report this bug and helping to make
Ubuntu better.

Bug reporting is about finding & fixing problems, thus preventing future
users from hitting the same bug. You seem to need support more than have
issues with a bug (your issue could be hardware related or lots of
things).

In your case I would boot do a memory test of your system, check your
hdd/ssd health (ie. `smartctl`, `gnome-disks` or KDE partition manager)
and if easily done, open your box and do a quick 'cap check' (not easily
done on notebooks!). I would then likely use  a 'live' system (eg.
Ubuntu install media, and selecting 'try ubuntu', but I'd also likely
use a different release or something else) to see if the issue is
resolved (ie. or configuration issue) or continues to occur.  But this
are support issues and not related to bug-reports.

This bug report can be converted to a question (which is aimed at
support). You can also find help with your problem in the support forum
of your local Ubuntu community http://loco.ubuntu.com/ or asking at
https://askubuntu.com or https://ubuntuforums.org, or for more support
options please look at https://discourse.ubuntu.com/t/community-
support/709

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

Title:
  Performance is not good system freeze a lot of time

Status in xorg package in Ubuntu:
  New

Bug description:
  Performance is not good system freeze a lot of time I am new to Ubuntu
  and don't know what to do please help

  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.1
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Nov  5 01:16:25 2019
  DistUpgraded: Fresh install
  DistroCodename: eoan
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA 
controller])
 Subsystem: Hewlett-Packard Company HD Graphics 620 [103c:81ee]
  InstallationDate: Installed on 2019-11-04 (0 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  MachineType: HP HP Notebook
  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=bef4cfb0-ebad-44d4-aad1-914b2839dba4 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/27/2016
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.21
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 81EE
  dmi.board.vendor: HP
  dmi.board.version: 62.36
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.21:bd10/27/2016:svnHP:pnHPNotebook:pvrType1ProductConfigId:rvnHP:rn81EE:rvr62.36:cvnHP:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV G=N L=CON B=HP
  dmi.product.name: HP Notebook
  dmi.product.sku: 1AP08EA#BH5
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: HP
  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/1851334/+subscriptions

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


[Desktop-packages] [Bug 1850529] Re: Crash after update to 71.0~b5+build1-0ubuntu0.16.04.1

2019-11-05 Thread j127
Also, if this version is known to be broken, maybe it should be removed
for 16.04 users so that it doesn't happen to anyone else? My computer
downloaded it six days after it was confirmed to be broken.

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

Title:
  Crash after update to 71.0~b5+build1-0ubuntu0.16.04.1

Status in firefox package in Ubuntu:
  Confirmed

Bug description:
  After update from: 70.0+build2-0ubuntu0.16.04.1 to
  71.0~b5+build1-0ubuntu0.16.04.1 app is not starting. I got constantly
  message that I can Refresh Firefox (crash) or Start in safe mode (also
  crash).

  Tech details:
  Description:  Ubuntu 16.04.6 LTS
  Release:  16.04
  package name:   71.0~b5+build1-0ubuntu0.16.04.1

  Crash log details:
  AdapterDeviceID: 0x1616
  AdapterDriverVendor: mesa/i965
  AdapterDriverVersion: 18.0.5.0
  AdapterVendorID: 0x8086
  BuildID: 20191028161640
  ContentSandboxCapabilities: 119
  ContentSandboxCapable: 1
  ContentSandboxLevel: 4
  CrashTime: 1572373123
  DOMIPCEnabled: 1
  FramePoisonBase: 9223372036600930304
  FramePoisonSize: 4096
  InstallTime: 1572364967
  IsWayland: 0
  IsWaylandDRM: 0
  MozCrashReason: MOZ_RELEASE_ASSERT(len.isValid()) (Substring tuple length is 
invalid)
  Notes: Ubuntu 16.04.6 LTSFP(D00-L1000-W-T000) WR? WR- OMTP? OMTP- 
  ProductID: {ec8030f7-c20a-464f-9b0e-13a3a9e97384}
  ProductName: Firefox
  ReleaseChannel: beta
  SafeMode: 1
  SecondsSinceLastCrash: 816
  StartupCrash: 0
  StartupTime: 1572373025
  TelemetryEnvironment: 
{"build":{"applicationId":"{ec8030f7-c20a-464f-9b0e-13a3a9e97384}","applicationName":"Firefox","architecture":"x86-64","buildId":"20191028161640","version":"71.0","vendor":"Mozilla","displayVersion":"71.0b5","platformVersion":"71.0","xpcomAbi":"x86_64-gcc3","updaterAvailable":false},"partner":{"distributionId":null,"distributionVersion":null,"partnerId":null,"distributor":null,"distributorChannel":null,"partnerNames":[]},"system":{"memoryMB":15965,"virtualMaxMB":null,"cpu":{"count":4,"cores":2,"vendor":"GenuineIntel","family":6,"model":61,"stepping":4,"l2cacheKB":256,"l3cacheKB":3072,"speedMHz":2700,"extensions":["hasMMX","hasSSE","hasSSE2","hasSSE3","hasSSSE3","hasSSE4_1","hasSSE4_2","hasAVX","hasAVX2","hasAES"]},"os":{"name":"Linux","version":"4.15.0-66-generic","locale":"en-US"},"hdd":{"profile":{"model":null,"revision":null,"type":null},"binary":{"model":null,"revision":null,"type":null},"system":{"model":null,"revision":null,"type":null}},"gfx":{"D2DEnabled":null,"DWriteEnabled":null,"ContentBackend":"Skia","Headless":false,"adapters":[{"description":"Mesa
 DRI Intel(R) HD Graphics 5500 (Broadwell GT2) 
","vendorID":"0x8086","deviceID":"0x1616","subsysID":null,"RAM":3072,"driver":null,"driverVendor":"mesa/i965","driverVersion":"18.0.5.0","driverDate":null,"GPUActive":true}],"monitors":[{"screenWidth":1366,"screenHeight":768}],"features":{"compositor":"none","gpuProcess":{"status":"blocked"},"wrQualified":{"status":"blocked-release-channel-intel"},"webrender":{"status":"unavailable-in-safe-mode"}}},"appleModelId":null},"settings":{"blocklistEnabled":true,"e10sEnabled":true,"e10sMultiProcesses":8,"telemetryEnabled":true,"locale":"en-US","intl":{},"update":{"channel":"beta","enabled":true,"autoDownload":false},"userPrefs":{"app.shield.optoutstudies.enabled":false,"browser.cache.disk.capacity":1048576,"browser.newtabpage.enabled":false,"browser.shell.checkDefaultBrowser":true,"browser.search.region":"US","browser.search.suggest.enabled":false,"browser.search.widget.inNavBar":false,"browser.startup.homepage":"","browser.startup.page":3,"browser.urlbar.suggest.searches":false,"devtools.chrome.enabled":false,"devtools.debugger.remote-enabled":false,"extensions.blocklist.url":"https://blocklists.settings.services.mozilla.com/v1/blocklist/3/%20/%20/","extensions.formautofill.addresses.enabled":false,"extensions.formautofill.creditCards.enabled":false,"privacy.donottrackheader.enabled":true},"sandbox":{"effectiveContentProcessLevel":4},"addonCompatibilityCheckEnabled":true,"isDefaultBrowser":null},"profile":{}}
  ThreadIdNameMapping: 7556:"Gecko_IOThread",7557:"JS Watchdog",7558:"JS 
Helper",7559:"JS Helper",7560:"JS Helper",7561:"JS 
Helper",7562:"Timer",7563:"Netlink Monitor",7564:"Socket Thread",7568:"Cache2 
I/O",7569:"Cookie",7570:"StreamTrans #1",7571:"GMPThread",7572:"Worker 
Launcher",7573:"SoftwareVsyncThread",7574:"Compositor",7575:"ImgDecoder 
#1",7576:"ImageIO",7580:"ImageBridgeChild",7581:"IPDL Background",7582:"DOM 
Worker",7584:"QuotaManager 
IO",7587:"StyleThread#0",7589:"StyleThread#2",7588:"StyleThread#1",7593:"DOM 
Worker",7630:"DataStorage",7631:"DNS Resolver #1",7632:"DNS Resolver 
#2",7633:"StreamTrans #7",7646:"IndexedDB #2",7647:"StreamTrans 
#8",7648:"StreamTrans #9",7649:"StreamTrans #10",
  Throttleable: 1
  UptimeTS: 98.30915265
  Vendor: Mozilla
  Version: 71.0
  useragent_locale: en-US

[Desktop-packages] [Bug 1850529] Re: Crash after update to 71.0~b5+build1-0ubuntu0.16.04.1

2019-11-05 Thread j127
This broke Firefox for me on 16.04 tonight. Has anyone found a temporary
fix? (It's my main browser with all of my tabs and extension data.)

If "upstream builds of firefox 71.0 beta 5" might work in the meantime,
does anyone know how to install it?

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

Title:
  Crash after update to 71.0~b5+build1-0ubuntu0.16.04.1

Status in firefox package in Ubuntu:
  Confirmed

Bug description:
  After update from: 70.0+build2-0ubuntu0.16.04.1 to
  71.0~b5+build1-0ubuntu0.16.04.1 app is not starting. I got constantly
  message that I can Refresh Firefox (crash) or Start in safe mode (also
  crash).

  Tech details:
  Description:  Ubuntu 16.04.6 LTS
  Release:  16.04
  package name:   71.0~b5+build1-0ubuntu0.16.04.1

  Crash log details:
  AdapterDeviceID: 0x1616
  AdapterDriverVendor: mesa/i965
  AdapterDriverVersion: 18.0.5.0
  AdapterVendorID: 0x8086
  BuildID: 20191028161640
  ContentSandboxCapabilities: 119
  ContentSandboxCapable: 1
  ContentSandboxLevel: 4
  CrashTime: 1572373123
  DOMIPCEnabled: 1
  FramePoisonBase: 9223372036600930304
  FramePoisonSize: 4096
  InstallTime: 1572364967
  IsWayland: 0
  IsWaylandDRM: 0
  MozCrashReason: MOZ_RELEASE_ASSERT(len.isValid()) (Substring tuple length is 
invalid)
  Notes: Ubuntu 16.04.6 LTSFP(D00-L1000-W-T000) WR? WR- OMTP? OMTP- 
  ProductID: {ec8030f7-c20a-464f-9b0e-13a3a9e97384}
  ProductName: Firefox
  ReleaseChannel: beta
  SafeMode: 1
  SecondsSinceLastCrash: 816
  StartupCrash: 0
  StartupTime: 1572373025
  TelemetryEnvironment: 
{"build":{"applicationId":"{ec8030f7-c20a-464f-9b0e-13a3a9e97384}","applicationName":"Firefox","architecture":"x86-64","buildId":"20191028161640","version":"71.0","vendor":"Mozilla","displayVersion":"71.0b5","platformVersion":"71.0","xpcomAbi":"x86_64-gcc3","updaterAvailable":false},"partner":{"distributionId":null,"distributionVersion":null,"partnerId":null,"distributor":null,"distributorChannel":null,"partnerNames":[]},"system":{"memoryMB":15965,"virtualMaxMB":null,"cpu":{"count":4,"cores":2,"vendor":"GenuineIntel","family":6,"model":61,"stepping":4,"l2cacheKB":256,"l3cacheKB":3072,"speedMHz":2700,"extensions":["hasMMX","hasSSE","hasSSE2","hasSSE3","hasSSSE3","hasSSE4_1","hasSSE4_2","hasAVX","hasAVX2","hasAES"]},"os":{"name":"Linux","version":"4.15.0-66-generic","locale":"en-US"},"hdd":{"profile":{"model":null,"revision":null,"type":null},"binary":{"model":null,"revision":null,"type":null},"system":{"model":null,"revision":null,"type":null}},"gfx":{"D2DEnabled":null,"DWriteEnabled":null,"ContentBackend":"Skia","Headless":false,"adapters":[{"description":"Mesa
 DRI Intel(R) HD Graphics 5500 (Broadwell GT2) 
","vendorID":"0x8086","deviceID":"0x1616","subsysID":null,"RAM":3072,"driver":null,"driverVendor":"mesa/i965","driverVersion":"18.0.5.0","driverDate":null,"GPUActive":true}],"monitors":[{"screenWidth":1366,"screenHeight":768}],"features":{"compositor":"none","gpuProcess":{"status":"blocked"},"wrQualified":{"status":"blocked-release-channel-intel"},"webrender":{"status":"unavailable-in-safe-mode"}}},"appleModelId":null},"settings":{"blocklistEnabled":true,"e10sEnabled":true,"e10sMultiProcesses":8,"telemetryEnabled":true,"locale":"en-US","intl":{},"update":{"channel":"beta","enabled":true,"autoDownload":false},"userPrefs":{"app.shield.optoutstudies.enabled":false,"browser.cache.disk.capacity":1048576,"browser.newtabpage.enabled":false,"browser.shell.checkDefaultBrowser":true,"browser.search.region":"US","browser.search.suggest.enabled":false,"browser.search.widget.inNavBar":false,"browser.startup.homepage":"","browser.startup.page":3,"browser.urlbar.suggest.searches":false,"devtools.chrome.enabled":false,"devtools.debugger.remote-enabled":false,"extensions.blocklist.url":"https://blocklists.settings.services.mozilla.com/v1/blocklist/3/%20/%20/","extensions.formautofill.addresses.enabled":false,"extensions.formautofill.creditCards.enabled":false,"privacy.donottrackheader.enabled":true},"sandbox":{"effectiveContentProcessLevel":4},"addonCompatibilityCheckEnabled":true,"isDefaultBrowser":null},"profile":{}}
  ThreadIdNameMapping: 7556:"Gecko_IOThread",7557:"JS Watchdog",7558:"JS 
Helper",7559:"JS Helper",7560:"JS Helper",7561:"JS 
Helper",7562:"Timer",7563:"Netlink Monitor",7564:"Socket Thread",7568:"Cache2 
I/O",7569:"Cookie",7570:"StreamTrans #1",7571:"GMPThread",7572:"Worker 
Launcher",7573:"SoftwareVsyncThread",7574:"Compositor",7575:"ImgDecoder 
#1",7576:"ImageIO",7580:"ImageBridgeChild",7581:"IPDL Background",7582:"DOM 
Worker",7584:"QuotaManager 
IO",7587:"StyleThread#0",7589:"StyleThread#2",7588:"StyleThread#1",7593:"DOM 
Worker",7630:"DataStorage",7631:"DNS Resolver #1",7632:"DNS Resolver 
#2",7633:"StreamTrans #7",7646:"IndexedDB #2",7647:"StreamTrans 
#8",7648:"StreamTrans #9",7649:"StreamTrans #10",
  Throttleable: 1
  UptimeTS: 98.30915265
  Vendor: Mo

[Desktop-packages] [Bug 1850529] Re: Crash after update to 71.0~b5+build1-0ubuntu0.16.04.1

2019-11-05 Thread Olivier Tilloy
j127: if you're using the firefox-next PPA, you're doing this at your
own risk, without any guarantees from ubuntu developers that this won't
break. The PPA is meant for testing beta builds, not for end users.

If you want a stable version of firefox, you shouldn't be using that
PPA. Packages in the Ubuntu archive are supported.

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

Title:
  Crash after update to 71.0~b5+build1-0ubuntu0.16.04.1

Status in firefox package in Ubuntu:
  Confirmed

Bug description:
  After update from: 70.0+build2-0ubuntu0.16.04.1 to
  71.0~b5+build1-0ubuntu0.16.04.1 app is not starting. I got constantly
  message that I can Refresh Firefox (crash) or Start in safe mode (also
  crash).

  Tech details:
  Description:  Ubuntu 16.04.6 LTS
  Release:  16.04
  package name:   71.0~b5+build1-0ubuntu0.16.04.1

  Crash log details:
  AdapterDeviceID: 0x1616
  AdapterDriverVendor: mesa/i965
  AdapterDriverVersion: 18.0.5.0
  AdapterVendorID: 0x8086
  BuildID: 20191028161640
  ContentSandboxCapabilities: 119
  ContentSandboxCapable: 1
  ContentSandboxLevel: 4
  CrashTime: 1572373123
  DOMIPCEnabled: 1
  FramePoisonBase: 9223372036600930304
  FramePoisonSize: 4096
  InstallTime: 1572364967
  IsWayland: 0
  IsWaylandDRM: 0
  MozCrashReason: MOZ_RELEASE_ASSERT(len.isValid()) (Substring tuple length is 
invalid)
  Notes: Ubuntu 16.04.6 LTSFP(D00-L1000-W-T000) WR? WR- OMTP? OMTP- 
  ProductID: {ec8030f7-c20a-464f-9b0e-13a3a9e97384}
  ProductName: Firefox
  ReleaseChannel: beta
  SafeMode: 1
  SecondsSinceLastCrash: 816
  StartupCrash: 0
  StartupTime: 1572373025
  TelemetryEnvironment: 
{"build":{"applicationId":"{ec8030f7-c20a-464f-9b0e-13a3a9e97384}","applicationName":"Firefox","architecture":"x86-64","buildId":"20191028161640","version":"71.0","vendor":"Mozilla","displayVersion":"71.0b5","platformVersion":"71.0","xpcomAbi":"x86_64-gcc3","updaterAvailable":false},"partner":{"distributionId":null,"distributionVersion":null,"partnerId":null,"distributor":null,"distributorChannel":null,"partnerNames":[]},"system":{"memoryMB":15965,"virtualMaxMB":null,"cpu":{"count":4,"cores":2,"vendor":"GenuineIntel","family":6,"model":61,"stepping":4,"l2cacheKB":256,"l3cacheKB":3072,"speedMHz":2700,"extensions":["hasMMX","hasSSE","hasSSE2","hasSSE3","hasSSSE3","hasSSE4_1","hasSSE4_2","hasAVX","hasAVX2","hasAES"]},"os":{"name":"Linux","version":"4.15.0-66-generic","locale":"en-US"},"hdd":{"profile":{"model":null,"revision":null,"type":null},"binary":{"model":null,"revision":null,"type":null},"system":{"model":null,"revision":null,"type":null}},"gfx":{"D2DEnabled":null,"DWriteEnabled":null,"ContentBackend":"Skia","Headless":false,"adapters":[{"description":"Mesa
 DRI Intel(R) HD Graphics 5500 (Broadwell GT2) 
","vendorID":"0x8086","deviceID":"0x1616","subsysID":null,"RAM":3072,"driver":null,"driverVendor":"mesa/i965","driverVersion":"18.0.5.0","driverDate":null,"GPUActive":true}],"monitors":[{"screenWidth":1366,"screenHeight":768}],"features":{"compositor":"none","gpuProcess":{"status":"blocked"},"wrQualified":{"status":"blocked-release-channel-intel"},"webrender":{"status":"unavailable-in-safe-mode"}}},"appleModelId":null},"settings":{"blocklistEnabled":true,"e10sEnabled":true,"e10sMultiProcesses":8,"telemetryEnabled":true,"locale":"en-US","intl":{},"update":{"channel":"beta","enabled":true,"autoDownload":false},"userPrefs":{"app.shield.optoutstudies.enabled":false,"browser.cache.disk.capacity":1048576,"browser.newtabpage.enabled":false,"browser.shell.checkDefaultBrowser":true,"browser.search.region":"US","browser.search.suggest.enabled":false,"browser.search.widget.inNavBar":false,"browser.startup.homepage":"","browser.startup.page":3,"browser.urlbar.suggest.searches":false,"devtools.chrome.enabled":false,"devtools.debugger.remote-enabled":false,"extensions.blocklist.url":"https://blocklists.settings.services.mozilla.com/v1/blocklist/3/%20/%20/","extensions.formautofill.addresses.enabled":false,"extensions.formautofill.creditCards.enabled":false,"privacy.donottrackheader.enabled":true},"sandbox":{"effectiveContentProcessLevel":4},"addonCompatibilityCheckEnabled":true,"isDefaultBrowser":null},"profile":{}}
  ThreadIdNameMapping: 7556:"Gecko_IOThread",7557:"JS Watchdog",7558:"JS 
Helper",7559:"JS Helper",7560:"JS Helper",7561:"JS 
Helper",7562:"Timer",7563:"Netlink Monitor",7564:"Socket Thread",7568:"Cache2 
I/O",7569:"Cookie",7570:"StreamTrans #1",7571:"GMPThread",7572:"Worker 
Launcher",7573:"SoftwareVsyncThread",7574:"Compositor",7575:"ImgDecoder 
#1",7576:"ImageIO",7580:"ImageBridgeChild",7581:"IPDL Background",7582:"DOM 
Worker",7584:"QuotaManager 
IO",7587:"StyleThread#0",7589:"StyleThread#2",7588:"StyleThread#1",7593:"DOM 
Worker",7630:"DataStorage",7631:"DNS Resolver #1",7632:"DNS Resolver 
#2",7633:"StreamTrans #7",7646:"IndexedDB #2",7647:"StreamTrans 
#8",7648:"StreamTrans #

[Desktop-packages] [Bug 1849888] Re: evince crashes (segmentation fault) when opening file rfc8655.pdf

2019-11-05 Thread Erik Auerswald
The problem seems to lie in the new format for IETF RFCs, i.e., all
official PDF files of RFCs released using the new format result in
evince crashes:

https://www.rfc-editor.org/rfc/rfc8651.pdf
https://www.rfc-editor.org/rfc/rfc8653.pdf
https://www.rfc-editor.org/rfc/rfc8654.pdf
https://www.rfc-editor.org/rfc/rfc8655.pdf

$ ls -a
.  ..
$ wget -nv https://www.rfc-editor.org/rfc/rfc8651.pdf 
https://www.rfc-editor.org/rfc/rfc8653.pdf 
https://www.rfc-editor.org/rfc/rfc8654.pdf 
https://www.rfc-editor.org/rfc/rfc8655.pdf
2019-11-05 09:53:01 URL:https://www.rfc-editor.org/rfc/rfc8651.pdf 
[137041/137041] -> "rfc8651.pdf" [1]
2019-11-05 09:53:02 URL:https://www.rfc-editor.org/rfc/rfc8653.pdf 
[128896/128896] -> "rfc8653.pdf" [1]
2019-11-05 09:53:02 URL:https://www.rfc-editor.org/rfc/rfc8654.pdf 
[102866/102866] -> "rfc8654.pdf" [1]
2019-11-05 09:53:02 URL:https://www.rfc-editor.org/rfc/rfc8655.pdf 
[325847/325847] -> "rfc8655.pdf" [1]
FINISHED --2019-11-05 09:53:02--
Total wall clock time: 2,3s
Downloaded: 4 files, 678K in 1,0s (654 KB/s)
$ evince rfc8651.pdf 
Segmentation fault (core dumped)
$ evince rfc8653.pdf 
Segmentation fault (core dumped)
$ evince rfc8654.pdf 
Segmentation fault (core dumped)
$ evince rfc8655.pdf 
Segmentation fault (core dumped)

Older PDFs work fine, e.g., https://www.rfc-
editor.org/rfc/pdfrfc/rfc8649.txt.pdf .

The built-in PDF viewer of Firefox can display all the above PDF files.
The built-in PDF viewer of Chrome can display all the above PDF files.
The MuPDF PDF viewer can display all the above PDF files.

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

Title:
  evince crashes (segmentation fault) when opening file rfc8655.pdf

Status in evince package in Ubuntu:
  New

Bug description:
  When trying to display the PDF file rfc8655.pdf from
  https://tools.ietf.org/pdf/rfc8655.pdf evince crashes:

  $ evince rfc8655.pdf 
  Segmentation fault (core dumped)

  I would have expected the PDF file to be displayed.  Instead, evince
  crashed and did not display the document.

  The built-in PDF renderer of Firefox 70.0 does display the PDF
  correctly.

  Since the segmentation fault hints at a memory management error
  triggered by external input this may have security implications.  I
  did not investigate this any further.  I do not set the "This bug is a
  security vulnerability" flag because I do not know if it really is (it
  probably is, but I have no proof) and I do not want this bug report to
  be private.

  $ lsb_release -rd
  Description:Ubuntu 18.04.3 LTS
  Release:18.04

  $ apt-cache policy evince
  evince:
Installed: 3.28.4-0ubuntu1.2
Candidate: 3.28.4-0ubuntu1.2
Version table:
   *** 3.28.4-0ubuntu1.2 500
  500 http://de.archive.ubuntu.com/ubuntu bionic-updates/main amd64 
Packages
  500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 
Packages
  100 /var/lib/dpkg/status
   3.28.2-1 500
  500 http://de.archive.ubuntu.com/ubuntu bionic/main amd64 Packages

  $ evince --version
  GNOME Document Viewer 3.28.4

  $ cat /etc/lsb-release 
  DISTRIB_ID=Ubuntu
  DISTRIB_RELEASE=18.04
  DISTRIB_CODENAME=bionic
  DISTRIB_DESCRIPTION="Ubuntu 18.04.3 LTS"

  This is a fresh install of Ubuntu 18.04 LTS on x86-64 (the upgrade
  from 16.04 resulted in a non-booting system).

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

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


[Desktop-packages] [Bug 1850529] Re: Crash after update to 71.0~b5+build1-0ubuntu0.16.04.1

2019-11-05 Thread Olivier Tilloy
Still crashing with 71.0~b7+build1-0ubuntu0.16.04.1, FWIW.

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

Title:
  Crash after update to 71.0~b5+build1-0ubuntu0.16.04.1

Status in firefox package in Ubuntu:
  Confirmed

Bug description:
  After update from: 70.0+build2-0ubuntu0.16.04.1 to
  71.0~b5+build1-0ubuntu0.16.04.1 app is not starting. I got constantly
  message that I can Refresh Firefox (crash) or Start in safe mode (also
  crash).

  Tech details:
  Description:  Ubuntu 16.04.6 LTS
  Release:  16.04
  package name:   71.0~b5+build1-0ubuntu0.16.04.1

  Crash log details:
  AdapterDeviceID: 0x1616
  AdapterDriverVendor: mesa/i965
  AdapterDriverVersion: 18.0.5.0
  AdapterVendorID: 0x8086
  BuildID: 20191028161640
  ContentSandboxCapabilities: 119
  ContentSandboxCapable: 1
  ContentSandboxLevel: 4
  CrashTime: 1572373123
  DOMIPCEnabled: 1
  FramePoisonBase: 9223372036600930304
  FramePoisonSize: 4096
  InstallTime: 1572364967
  IsWayland: 0
  IsWaylandDRM: 0
  MozCrashReason: MOZ_RELEASE_ASSERT(len.isValid()) (Substring tuple length is 
invalid)
  Notes: Ubuntu 16.04.6 LTSFP(D00-L1000-W-T000) WR? WR- OMTP? OMTP- 
  ProductID: {ec8030f7-c20a-464f-9b0e-13a3a9e97384}
  ProductName: Firefox
  ReleaseChannel: beta
  SafeMode: 1
  SecondsSinceLastCrash: 816
  StartupCrash: 0
  StartupTime: 1572373025
  TelemetryEnvironment: 
{"build":{"applicationId":"{ec8030f7-c20a-464f-9b0e-13a3a9e97384}","applicationName":"Firefox","architecture":"x86-64","buildId":"20191028161640","version":"71.0","vendor":"Mozilla","displayVersion":"71.0b5","platformVersion":"71.0","xpcomAbi":"x86_64-gcc3","updaterAvailable":false},"partner":{"distributionId":null,"distributionVersion":null,"partnerId":null,"distributor":null,"distributorChannel":null,"partnerNames":[]},"system":{"memoryMB":15965,"virtualMaxMB":null,"cpu":{"count":4,"cores":2,"vendor":"GenuineIntel","family":6,"model":61,"stepping":4,"l2cacheKB":256,"l3cacheKB":3072,"speedMHz":2700,"extensions":["hasMMX","hasSSE","hasSSE2","hasSSE3","hasSSSE3","hasSSE4_1","hasSSE4_2","hasAVX","hasAVX2","hasAES"]},"os":{"name":"Linux","version":"4.15.0-66-generic","locale":"en-US"},"hdd":{"profile":{"model":null,"revision":null,"type":null},"binary":{"model":null,"revision":null,"type":null},"system":{"model":null,"revision":null,"type":null}},"gfx":{"D2DEnabled":null,"DWriteEnabled":null,"ContentBackend":"Skia","Headless":false,"adapters":[{"description":"Mesa
 DRI Intel(R) HD Graphics 5500 (Broadwell GT2) 
","vendorID":"0x8086","deviceID":"0x1616","subsysID":null,"RAM":3072,"driver":null,"driverVendor":"mesa/i965","driverVersion":"18.0.5.0","driverDate":null,"GPUActive":true}],"monitors":[{"screenWidth":1366,"screenHeight":768}],"features":{"compositor":"none","gpuProcess":{"status":"blocked"},"wrQualified":{"status":"blocked-release-channel-intel"},"webrender":{"status":"unavailable-in-safe-mode"}}},"appleModelId":null},"settings":{"blocklistEnabled":true,"e10sEnabled":true,"e10sMultiProcesses":8,"telemetryEnabled":true,"locale":"en-US","intl":{},"update":{"channel":"beta","enabled":true,"autoDownload":false},"userPrefs":{"app.shield.optoutstudies.enabled":false,"browser.cache.disk.capacity":1048576,"browser.newtabpage.enabled":false,"browser.shell.checkDefaultBrowser":true,"browser.search.region":"US","browser.search.suggest.enabled":false,"browser.search.widget.inNavBar":false,"browser.startup.homepage":"","browser.startup.page":3,"browser.urlbar.suggest.searches":false,"devtools.chrome.enabled":false,"devtools.debugger.remote-enabled":false,"extensions.blocklist.url":"https://blocklists.settings.services.mozilla.com/v1/blocklist/3/%20/%20/","extensions.formautofill.addresses.enabled":false,"extensions.formautofill.creditCards.enabled":false,"privacy.donottrackheader.enabled":true},"sandbox":{"effectiveContentProcessLevel":4},"addonCompatibilityCheckEnabled":true,"isDefaultBrowser":null},"profile":{}}
  ThreadIdNameMapping: 7556:"Gecko_IOThread",7557:"JS Watchdog",7558:"JS 
Helper",7559:"JS Helper",7560:"JS Helper",7561:"JS 
Helper",7562:"Timer",7563:"Netlink Monitor",7564:"Socket Thread",7568:"Cache2 
I/O",7569:"Cookie",7570:"StreamTrans #1",7571:"GMPThread",7572:"Worker 
Launcher",7573:"SoftwareVsyncThread",7574:"Compositor",7575:"ImgDecoder 
#1",7576:"ImageIO",7580:"ImageBridgeChild",7581:"IPDL Background",7582:"DOM 
Worker",7584:"QuotaManager 
IO",7587:"StyleThread#0",7589:"StyleThread#2",7588:"StyleThread#1",7593:"DOM 
Worker",7630:"DataStorage",7631:"DNS Resolver #1",7632:"DNS Resolver 
#2",7633:"StreamTrans #7",7646:"IndexedDB #2",7647:"StreamTrans 
#8",7648:"StreamTrans #9",7649:"StreamTrans #10",
  Throttleable: 1
  UptimeTS: 98.30915265
  Vendor: Mozilla
  Version: 71.0
  useragent_locale: en-US

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

-- 
Mailing list:

[Desktop-packages] [Bug 1798840] Re: Night Light is not functioning

2019-11-05 Thread Timo Aaltonen
still doesn't make it a wayland bug

** Package changed: wayland (Ubuntu) => gnome-shell (Ubuntu)

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

Title:
  Night Light is not functioning

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

Bug description:
  Night Light is not shading/filtering the screen anymore after the update to 
Cosmic (Ubuntu 18.10) from Bionic (Ubuntu 18.04 LTS).
  It still appears as an option and all the settings work, but the feature 
itself isn't filtering out blue light from the screen.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: gnome-control-center 1:3.30.1-1ubuntu2
  ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12
  Uname: Linux 4.18.0-10-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Oct 19 11:03:28 2018
  InstallationDate: Installed on 2018-08-17 (63 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-control-center
  UpgradeStatus: Upgraded to cosmic on 2018-10-19 (0 days ago)

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

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


[Desktop-packages] [Bug 1798840] Re: Night Light is not functioning

2019-11-05 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

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

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

Title:
  Night Light is not functioning

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

Bug description:
  Night Light is not shading/filtering the screen anymore after the update to 
Cosmic (Ubuntu 18.10) from Bionic (Ubuntu 18.04 LTS).
  It still appears as an option and all the settings work, but the feature 
itself isn't filtering out blue light from the screen.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: gnome-control-center 1:3.30.1-1ubuntu2
  ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12
  Uname: Linux 4.18.0-10-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Oct 19 11:03:28 2018
  InstallationDate: Installed on 2018-08-17 (63 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-control-center
  UpgradeStatus: Upgraded to cosmic on 2018-10-19 (0 days ago)

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

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


[Desktop-packages] [Bug 1851322] Re: VPN auto-connect is not working

2019-11-05 Thread Sebastien Bacher
Thank you for your bug report. What VPN type/plugin are you using?
Could you add your 'journalctl -b 0' log after getting the issue?

** No longer affects: network-manager

** Changed in: network-manager (Ubuntu)
   Importance: Undecided => Low

** Changed in: network-manager (Ubuntu)
   Status: New => Incomplete

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

Title:
  VPN auto-connect is not working

Status in network-manager package in Ubuntu:
  Incomplete

Bug description:
  Hi,

  This is a duplicate of bug:
  https://bugs.launchpad.net/network-manager/+bug/1718931

  It is marked as fixed, but the feature is still broken for me.

  I configured my Wifi connection to automatically connect to a VPN, but it 
only works if I manually
  connect to the Wifi via NetworkManager.

  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.1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Nov  5 04:07: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 (39 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  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/1851322/+subscriptions

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


[Desktop-packages] [Bug 1850775] Re: DNS info is not loaded by dhclient

2019-11-05 Thread Pengpeng Sun
Thanks @Dan, I applied the patch 
https://launchpadlibrarian.net/448207988/resolved.patch to my VM, but the issue 
is still reproducing. 
The md5sum line is before creating "$statedir/isc-dhcp-v4-$interface.conf", 
while I can see the isc-dhcp-v4-$interface.conf file is created on my VM.

I think the root cause is not same with bug 1849608

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

Title:
  DNS info is not loaded by dhclient

Status in network-manager package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  New

Bug description:
  Hi Team,

  Could you please help to confirm if this is an issue on Ubuntu19.10
  Desktop?

  1. Update /etc/dhcp/dhclient.conf file to include below 2 new lines.
 supersede domain-name "vmware.com";
 supersede domain-name-servers 10.117.0.1;

  2. Reboot

  3. check DNS info by "systemd-resolve --status", the DNS domain and
  server is not set. But /run/systemd/resolved.conf.d/isc-
  dhcp-v4-ens160.conf contains the new DNS domain and server.

  4. Manually run "systemctl try-reload-or-restart systemd-
  resolved.service" and then DNS is set correctly, "systemd-resolve
  --status" output have the new DNS domain and server.

  
  I tried the same steps on Ubuntu18.04 Desktop, no such issue. DNS updated 
correctly after reboot.

  Thanks,
  Pengpeng

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

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


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

2019-11-05 Thread Pål Bergström
Public bug reported:

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

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


** Tags: amd64 apport-bug eoan false-gpu-hang freeze ubuntu

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

Title:
  Xorg freeze

Status in xorg package in Ubuntu:
  New

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.

[Desktop-packages] [Bug 1724876] Re: libreoffice soffice.bin using 100% cpu

2019-11-05 Thread Marcus Tomlinson
** Also affects: df-libreoffice via
   https://bugs.documentfoundation.org/show_bug.cgi?id=128406
   Importance: Unknown
   Status: Unknown

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

Title:
  libreoffice soffice.bin using 100% cpu

Status in LibreOffice:
  Unknown
Status in libreoffice package in Ubuntu:
  Incomplete

Bug description:
  With literally every action in libreoffice Calc, CPU usage goes to
  100% due to soffice.bin, and stays on 100% for minutes. To the extend
  that libreoffice calc is UNUSABLE for anything that has to do with
  spreadsheets. As far as I am concerned, this is a critical bug because
  it makes the program unusable, and often even the complete computer
  due to the high cpu load.

  - 'Every action' includes typing as much as one single letter in a cell. Or 
opening the file.
  - the file I am working on is only 1.1Mb in size
  - the same file used to open fine in previous versions of libreoffice.

  what I've tried so far - without any improvement in speed:
  - under tools, options, assigned memory 256 Mb for Libreoffice, and 20Mb per 
object (no solution)
  - automatic calculation has been turned off (no solution)
  - libreoffice-gnome and libreoffice-gtk have been removed (no solution)
  - purged and reinstalled libreoffice. (no solution)
  - created new user profile - also no resolve


  System: Ubuntu 16.04 LTS on AMD A8 with 8Gb ram and running on an SSD.
  Libreoffice: 
  Version: 5.1.6.2
  Build ID: 1:5.1.6~rc2-0ubuntu1~xenial2
  CPU Threads: 4; OS Version: Linux 4.4; UI Render: default

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

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


[Desktop-packages] [Bug 1851018] Re: xorg have some bugs.

2019-11-05 Thread Sebastien Bacher
Thank you for taking the time to report this bug and helping to make
Ubuntu better. Unfortunately, we cannot work on this bug because your
description didn't include enough information. You may find it helpful
to read "How to report bugs effectively"
http://www.chiark.greenend.org.uk/~sgtatham/bugs.html. We'd be grateful
if you would then provide a more complete description of the problem.

We have instructions on debugging some types of problems at
http://wiki.ubuntu.com/DebuggingProcedures.

At a minimum, we need:
1. The specific steps or actions you took that caused you to encounter the 
problem.
2. The behavior you expected.
3. The behavior you actually encountered (in as much detail as possible).
Thanks! 

** Changed in: xorg (Ubuntu)
   Importance: Undecided => Low

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

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

Title:
  xorg have some bugs.

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  1.When pasting, often I paste not the newest copied/cut text/image, but the 
previous one. Very annoying! It is the case in all programs (LibreOffice, Kate, 
Firefox etc.).
  2.When a program has problems - e.g. because something takes a long time, and 
it offers to wait or close down, sometimes the whole computer becomes 
unresponsive - I can move the mouse, but not change to other running programs. 
In the end, I have to hard reboot.

  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
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.suspend: suspend hibernate resume
  .proc.driver.nvidia.suspend_depth: default modeset uvm
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  430.50  Thu Sep  5 22:36:31 
CDT 2019
   GCC version:  gcc version 9.2.1 20191008 (Ubuntu 9.2.1-9ubuntu2)
  ApportVersion: 2.20.11-0ubuntu8.1
  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: ubuntu:GNOME
  Date: Sat Nov  2 19:49:35 2019
  DistUpgraded: 2019-10-19 08:58:21,996 DEBUG install of snap core18 succeeded
  DistroCodename: eoan
  DistroVariant: ubuntu
  DkmsStatus:
   mt7601, 3.0.0.4: added
   nvidia, 430.50, 5.3.0-19-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   NVIDIA Corporation GM204 [GeForce GTX 970] [10de:13c2] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: NVIDIA Corporation GM204 [GeForce GTX 970] [10de:1131]
  InstallationDate: Installed on 2019-07-06 (119 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: MSI MS-7850
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-19-generic 
root=UUID=41f99f54-13ee-4bc3-8dcd-bca83277990a ro quiet splash nomodeset 
video=uvesafb:mode_option=1366x7680-24,mtrr=3,scroll=ywrap vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: Upgraded to eoan on 2019-10-19 (14 days ago)
  dmi.bios.date: 02/16/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: V4.11
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: Z97 PC Mate(MS-7850)
  dmi.board.vendor: MSI
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: To be filled by O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: MSI
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrV4.11:bd02/16/2016:svnMSI:pnMS-7850:pvr1.0:rvnMSI:rnZ97PCMate(MS-7850):rvr1.0:cvnMSI:ct3:cvr1.0:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: MS-7850
  dmi.product.sku: To be filled by O.E.M.
  dmi.product.version: 1.0
  dmi.sys.vendor: MSI
  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.nvidia-graphics-drivers: nvidia-graphics-drivers-* 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/1851018/+subscriptions

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

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

2019-11-05 Thread Sebastien Bacher
The issue looks the same as
https://gitlab.gnome.org/GNOME/mutter/issues/896

** Bug watch added: gitlab.gnome.org/GNOME/mutter/issues #896
   https://gitlab.gnome.org/GNOME/mutter/issues/896

** Package changed: xorg (Ubuntu) => gnome-shell (Ubuntu)

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

** Changed in: gnome-shell (Ubuntu)
   Status: Confirmed => In Progress

** Changed in: gnome-shell (Ubuntu)
 Assignee: (unassigned) => Marco Trevisan (Treviño) (3v1n0)

** Also affects: gnome-shell via
   https://gitlab.gnome.org/GNOME/mutter/issues/896
   Importance: Unknown
   Status: Unknown

-- 
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:
  New
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
  dm

[Desktop-packages] [Bug 1850995] Re: gnome-shell: freeze and high CPU usage

2019-11-05 Thread Sebastien Bacher
*** This bug is a duplicate of bug 1850969 ***
https://bugs.launchpad.net/bugs/1850969

** Bug watch added: gitlab.gnome.org/GNOME/mutter/issues #896
   https://gitlab.gnome.org/GNOME/mutter/issues/896

** Also affects: gnome-shell via
   https://gitlab.gnome.org/GNOME/mutter/issues/896
   Importance: Unknown
   Status: Unknown

** Changed in: gnome-shell (Ubuntu)
   Status: New => In Progress

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

** This bug has been marked a duplicate of bug 1850969
   x11 session all mouse or keyboard action ignored

** No longer affects: gnome-shell

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

Title:
  gnome-shell: freeze and high CPU usage

Status in gnome-shell package in Ubuntu:
  In Progress

Bug description:
  It's easy to reproduce: Put files on the desktop, select them, the selection 
remains and the whole shell crashes.
  I switch to a tty2 session and see the gnome-shell process with 100% CPU.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell 3.34.1+git20191024-1ubuntu1
  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-0ubuntu9
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Nov  2 00:32:11 2019
  DisplayManager: gdm3
  InstallationDate: Installed on 2019-02-18 (256 days ago)
  InstallationMedia: Kubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190130)
  ProcEnviron:
   TERM=screen-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=it_IT.UTF-8
   SHELL=/bin/bash
  RelatedPackageVersions: mutter-common 3.34.1+git20191022-2ubuntu1
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1851007] Re: Login option 'GNOME + Remmina' not working

2019-11-05 Thread Sebastien Bacher
Could you add a journalctl log from a session having the issue?

** Package changed: xorg (Ubuntu) => remmina (Ubuntu)

** Changed in: remmina (Ubuntu)
   Importance: Undecided => Low

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

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

Title:
  Login option 'GNOME + Remmina' not working

Status in remmina package in Ubuntu:
  Incomplete

Bug description:
  Selecting Login option 'GNOME + Remmina' I'm just returned to login
  panel with no message.

  corrado@corrado-p13-ff-1101:~$ 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: 800 MHz min/max: 800/3900 MHz Core speeds (MHz): 1: 800 2: 
800 3: 801 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: 5.30 GiB (0.6%) 
 ID-1: /dev/sda vendor: Toshiba model: DT01ACA100 size: 931.51 GiB 
  Partition: ID-1: / size: 15.62 GiB used: 5.30 GiB (33.9%) 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: 37.5 C mobo: N/A 
 Fan Speeds (RPM): N/A 
  Info:  Processes: 197 Uptime: 7m Memory: 7.49 GiB used: 1.00 GiB (13.4%) 
Init: systemd runlevel: 5 Compilers: 
 gcc: 9.2.1 Shell: bash v: 5.0.3 inxi: 3.0.36 
  corrado@corrado-p13-ff-1101:~$

  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: Sat Nov  2 08:17:56 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 Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.
  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.xserv

[Desktop-packages] [Bug 1850775] Re: DNS info is not loaded by dhclient

2019-11-05 Thread Pengpeng Sun
@Dan, The issue is resolved by your fix.

Instead of only changing /etc/dhcp/dhclient-enter-hooks.d/resolved
script, I added your repository "ppa:ddstreet/systemd" and
updated/upgraded systemd, then the issue was NOT reproducing.

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

Title:
  DNS info is not loaded by dhclient

Status in network-manager package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  New

Bug description:
  Hi Team,

  Could you please help to confirm if this is an issue on Ubuntu19.10
  Desktop?

  1. Update /etc/dhcp/dhclient.conf file to include below 2 new lines.
 supersede domain-name "vmware.com";
 supersede domain-name-servers 10.117.0.1;

  2. Reboot

  3. check DNS info by "systemd-resolve --status", the DNS domain and
  server is not set. But /run/systemd/resolved.conf.d/isc-
  dhcp-v4-ens160.conf contains the new DNS domain and server.

  4. Manually run "systemctl try-reload-or-restart systemd-
  resolved.service" and then DNS is set correctly, "systemd-resolve
  --status" output have the new DNS domain and server.

  
  I tried the same steps on Ubuntu18.04 Desktop, no such issue. DNS updated 
correctly after reboot.

  Thanks,
  Pengpeng

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

-- 
Mailing list: https://launchpad.net/~desktop-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-05 Thread Bug Watch Updater
** Changed in: gnome-shell
   Status: Unknown => New

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

Title:
  x11 session all mouse or keyboard action ignored

Status in GNOME Shell:
  New
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 Filled By O.E.M.
  d

[Desktop-packages] [Bug 1850823] Re: plz help mw

2019-11-05 Thread Sebastien Bacher
Thank you for taking the time to report this bug and helping to make
Ubuntu better. Unfortunately, we cannot work on this bug because your
description didn't include enough information. You may find it helpful
to read "How to report bugs effectively"
http://www.chiark.greenend.org.uk/~sgtatham/bugs.html. We'd be grateful
if you would then provide a more complete description of the problem.

We have instructions on debugging some types of problems at
http://wiki.ubuntu.com/DebuggingProcedures.

At a minimum, we need:
1. The specific steps or actions you took that caused you to encounter the 
problem.
2. The behavior you expected.
3. The behavior you actually encountered (in as much detail as possible).
Thanks! 

** Changed in: xorg (Ubuntu)
   Importance: Undecided => Low

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

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

Title:
  plz help mw

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  like big and big issue

  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
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Oct 31 22:38:46 2019
  DistUpgraded: 2019-10-31 07:37:10,130 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: eoan
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation Skylake GT2 [HD Graphics 520] [8086:1916] (rev 07) 
(prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company Skylake GT2 [HD Graphics 520] 
[103c:8329]
 Subsystem: Hewlett-Packard Company Radeon R7 M520 [103c:8329]
  InstallationDate: Installed on 2019-10-29 (2 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 004: ID 05c8:03ac Cheng Uei Precision Industry Co., Ltd 
(Foxlink) HP TrueVision HD Camera
   Bus 001 Device 003: ID 0bda:b009 Realtek Semiconductor Corp. 802.11n WLAN 
Adapter
   Bus 001 Device 005: ID 148f:7601 Ralink Technology, Corp. MT7601U Wireless 
Adapter
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: HP HP Laptop 15-bs0xx
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-19-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: Upgraded to eoan on 2019-10-31 (0 days ago)
  dmi.bios.date: 05/10/2017
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.10
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 8329
  dmi.board.vendor: HP
  dmi.board.version: 23.27
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.10:bd05/10/2017:svnHP:pnHPLaptop15-bs0xx:pvrType1ProductConfigId:rvnHP:rn8329:rvr23.27:cvnHP:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV HP Notebook
  dmi.product.name: HP Laptop 15-bs0xx
  dmi.product.sku: 2EY79PA#ACJ
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: HP
  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

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

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


[Desktop-packages] [Bug 1792085] Re: MTP not working/very slow on Bionic

2019-11-05 Thread David
I just had this problem yesterday with Ubuntu 18.04 with all the updates and 
with a brand new Xiaomi Mi A3.
Copying from the phone (Xiaomi Mi A2) wasn't that bad, I was with speeds around 
20mb/s but copying the data back to the other phone was unreasonably slow. It 
would start at around 5mb/s and then quickly drop to around 60kb/s. 

To me, enabling the USB Debugging didn't make any difference.

To me, Android File Transfer ( https://www.omgubuntu.co.uk/2017/11
/android-file-transfer-app-linux ) worked as worked around, I managed to
copy the files back at about 10mb/s. Not great, but workable.

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

Title:
  MTP not working/very slow on Bionic

Status in libmtp:
  New
Status in gvfs package in Ubuntu:
  Incomplete

Bug description:
  Hi, unfortunately (for me) MTP android devices no more work on Ubuntu
  18.04.

  I have used MTP on 16.04 without problems, but on 18.04 it does not
  work. When I connect my Android devices (Samsung A5 and Samsung J3)
  and I try to list directories with many files (e.g. /DCIM/Camera) the
  window hangs until I disconnect the device. Same issue if I try to
  post the command "ls /var/run/1000/gvfs/".

  I have installed Ubuntu 18.04 on two different machines - an older HP
  laptop and a recent DELL laptop - and the issue is present on the all
  of them.

  I suspect a defect on the "libmtp". I tried many alternative solutions
  suggested by the net (e.g. jmtpfs and so on) but anyone worked.

  That's all!

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gvfs-fuse 1.36.1-0ubuntu1.1
  ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18
  Uname: Linux 4.15.0-29-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  CasperVersion: 1.394
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Sep 12 06:20:07 2018
  LiveMediaBuild: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gvfs
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1841051] Re: gpg password cache is never cleared

2019-11-05 Thread Sebastien Bacher
Thank you for your bug report. Could you give details on what you did
exactly? If you ticked the box to store the auth in the keyring that's
what it did, why would you expect it to do instead?

** Package changed: seahorse (Ubuntu) => gnome-keyring (Ubuntu)

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

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

Title:
  gpg password cache is never cleared

Status in gnome-keyring package in Ubuntu:
  Incomplete

Bug description:
  The gpg password never expires - not even after reboot.

  I tried to set in dconf-editor:

  org.gnome.crypto.cache gpg-cache-method 'idle'
  org.gnome.crypto.cache gpg-cache-ttl 300

  and created the following file:

  ~/.gnupg/gpg-agent.conf

  default-cache-ttl 300

  
  None of these methods help.

  In case this could be helpful I add this (from Amir on
  https://superuser.com/questions/1347956/gnome-keyring-cant-clear-
  passphrase):

  user@machine:~$ gpgconf --list-dirs agent-socket
  /run/user/1000/gnupg/S.gpg-agent

  user@machine:~$ systemctl --user status gpg-agent.socket
  Failed to dump process list, ignoring: No such file or directory
  ● gpg-agent.socket - GnuPG cryptographic agent and passphrase cache
 Loaded: loaded (/usr/lib/systemd/user/gpg-agent.socket; disabled; vendor 
preset: enabled)
 Active: active (running) since Wed 2019-08-21 14:53:28 CEST; 5min ago
   Docs: man:gpg-agent(1)
 Listen: /run/user/1000/gnupg/S.gpg-agent (Stream)
 CGroup: /user.slice/user-1000.slice/user@1000.service/gpg-agent.socket

  Aug 21 14:53:28 machine systemd[1726]: Listening on GnuPG
  cryptographic agent and passphrase cache.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gpg-agent 2.2.4-1ubuntu1.2
  ProcVersionSignature: Ubuntu 4.15.0-58.64-generic 4.15.18
  Uname: Linux 4.15.0-58-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Aug 22 14:14:08 2019
  InstallationDate: Installed on 2018-08-01 (386 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  SourcePackage: gnupg2
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1850806] Re: Ubuntu Software Centre (gnome-software) search function semi-broken

2019-11-05 Thread Sebastien Bacher
Thank you for your bug report. Could you give an example of string
returning no result and add a screenshot showing hte 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/1850806

Title:
  Ubuntu Software Centre (gnome-software) search function semi-broken

Status in gnome-software package in Ubuntu:
  Incomplete

Bug description:
  Ubuntu version:
  Description:  Ubuntu 19.10
  Release:  19.10

  Package version:
  ubuntu-software:
Installed: 3.30.6-2ubuntu10
Candidate: 3.30.6-2ubuntu10
Version table:
   *** 3.30.6-2ubuntu10 500
  500 http://us.archive.ubuntu.com/ubuntu eoan/main amd64 Packages
  500 http://us.archive.ubuntu.com/ubuntu eoan/main i386 Packages
  100 /var/lib/dpkg/status

  Expected behaviour:
  Typing in a search query returns results

  What happened instead:
  Half the time, Ubuntu Software returns "no results"

  Work-around(ish):
  Delete a letter or two out of the search query

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

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


[Desktop-packages] [Bug 1849930] Re: Additional L2TP VPN Breaks First VPN

2019-11-05 Thread Sebastien Bacher
Closing then, it should be fixed in the current serie. The fix can still
be SRUed but the ppa package would need some change to be SRU compliant

THis change
  * Ensure NM configures /etc/resolv.conf, not pppd  (LP: #1778946)
references to a bug that doesn't impact the package nor describe the problem in 
lt2p

The bugs references should also be made SRU compliant (description of
the impact, testcase to be able to verify the problem and the fix,
regression potential section describing things that could go
wrong/potential side effects of the SRU)

** Changed in: gnome-control-center (Ubuntu)
   Status: Incomplete => Invalid

** Changed in: network-manager-l2tp (Ubuntu)
   Status: Confirmed => Fix Released

** Changed in: network-manager-l2tp (Ubuntu)
   Importance: Undecided => Low

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

Title:
  Additional L2TP VPN Breaks First VPN

Status in gnome-control-center:
  New
Status in NetworkManager:
  New
Status in strongSwan:
  New
Status in gnome-control-center package in Ubuntu:
  Invalid
Status in network-manager-l2tp package in Ubuntu:
  Fix Released

Bug description:
  When I add only one L2TP VPN profile to gnome-control-center's Network
  > VPN settings, it works fine.

  However, if I add a 2nd L2TP VPN, the 2nd L2TP VPN, not only doesn't
  work, but it corrupts the first L2TP VPN so that it too stops working.

  Furthermore, if I remove 2nd L2TP VPN profile (that corrupted the
  first L2TP VPN) this does NOT repair the corruption to the first L2TP
  VPN, it remains corrupted.

  Additionally, removing all VPN profiles and re-adding the first one
  back, doesn't repair the corruption. Rebooting and adding them back
  doesn't work either.

  The only thing that works, that I've found, is completely reinstalling
  Ubuntu 19.10. Please advise better workarounds than reinstalling.

  In case it matters, these additional packages were also required for
  my initial VPN setup:

  sudo apt-get install -y network-manager-l2tp network-manager-l2tp-
  gnome strongswan

  Here's what's in the syslog on a failed VPN Connection attempt:

  Oct 26 02:58:35 workstation5 NetworkManager[1241]:   [1572076715.5632] 
audit: op="connection-activate" uuid="1942cf95-93b1-4e74-a44a-947a46bffb5a" 
name="L2TP VPN1" pid=3531 uid=1000 result="success"
  Oct 26 02:58:35 workstation5 NetworkManager[1241]:   [1572076715.5702] 
vpn-connection[0x5642f421c750,1932cf95-91b1-4e85-a44a-498a56befb5a,"L2TP 
VPN1",0]: Started the VPN service, PID 7273
  Oct 26 02:58:35 workstation5 NetworkManager[1241]:   [1572076715.5747] 
vpn-connection[0x5642f421c750,1932cf95-91b1-4e85-a44a-498a56befb5a,"L2TP 
VPN1",0]: Saw the service appear; activating connection
  Oct 26 02:58:35 workstation5 NetworkManager[1241]:   [1572076715.6566] 
vpn-connection[0x5642f421c750,1932cf95-91b1-4e85-a44a-498a56befb5a,"L2TP 
VPN1",0]: VPN connection: (ConnectInteractive) reply received
  Oct 26 02:58:35 workstation5 NetworkManager[1241]: Stopping strongSwan IPsec 
failed: starter is not running
  Oct 26 02:58:37 workstation5 NetworkManager[1241]: Starting strongSwan 5.7.2 
IPsec [starter]...
  Oct 26 02:58:37 workstation5 NetworkManager[1241]: Loading config setup
  Oct 26 02:58:37 workstation5 NetworkManager[1241]: Loading conn 
'1942cf95-93b1-4e74-a44a-947a46bffb5a'
  Oct 26 02:58:37 workstation5 NetworkManager[1241]: found netkey IPsec stack
  Oct 26 02:58:48 workstation5 NetworkManager[1241]: Stopping strongSwan 
IPsec...
  Oct 26 02:58:48 workstation5 NetworkManager[1241]: initiating Main Mode 
IKE_SA 1942cf95-93b1-4e74-a44a-947a46bffb5a[1] to 49.230.24.121
  Oct 26 02:58:48 workstation5 NetworkManager[1241]: generating ID_PROT request 
0 [ SA V V V V V ]
  Oct 26 02:58:48 workstation5 NetworkManager[1241]: sending packet: from 
192.168.1.2[500] to 49.230.24.121[500] (236 bytes)
  Oct 26 02:58:48 workstation5 NetworkManager[1241]: received packet: from 
49.230.24.121[500] to 192.168.1.2[500] (156 bytes)
  Oct 26 02:58:48 workstation5 NetworkManager[1241]: parsed ID_PROT response 0 
[ SA V V V V ]
  Oct 26 02:58:48 workstation5 NetworkManager[1241]: received XAuth vendor ID
  Oct 26 02:58:48 workstation5 NetworkManager[1241]: received DPD vendor ID
  Oct 26 02:58:48 workstation5 NetworkManager[1241]: received FRAGMENTATION 
vendor ID
  Oct 26 02:58:48 workstation5 NetworkManager[1241]: received NAT-T (RFC 3947) 
vendor ID
  Oct 26 02:58:48 workstation5 NetworkManager[1241]: selected proposal: 
IKE:3DES_CBC/HMAC_SHA1_96/PRF_HMAC_SHA1/MODP_1024
  Oct 26 02:58:48 workstation5 NetworkManager[1241]: generating ID_PROT request 
0 [ KE No NAT-D NAT-D ]
  Oct 26 02:58:48 workstation5 NetworkManager[1241]: sending packet: from 
192.168.1.2[500] to 49.230.24.121[500] (244 bytes)
  Oct 26 02:58:48 workstation5 NetworkManager[1241]: received packet: from 
49.230.24.121[500] to 192.168.1.2[500] (2

[Desktop-packages] [Bug 1850977] Re: gnome-software installs software without user having sudo access

2019-11-05 Thread Sebastien Bacher
Thank you for your bug report. The auth dialog should prompt you for the
password of an user which is admin, are you sure it's prompting for
credentials for the current user and not from another admin one?

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

Title:
  gnome-software installs software without user having sudo access

Status in gnome-software package in Ubuntu:
  Incomplete

Bug description:
  $ lsb_release -rd
  Description:  Ubuntu 18.04.2 LTS
  Release:  18.04

  $ apt-cache policy gnome-software
  gnome-software:
Installed: 3.28.1-0ubuntu4.18.04.8
Candidate: 3.28.1-0ubuntu4.18.04.12
Version table:
   3.28.1-0ubuntu4.18.04.12 500
  500 http://us.archive.ubuntu.com/ubuntu bionic-updates/main amd64 
Packages
   *** 3.28.1-0ubuntu4.18.04.8 100
  100 /var/lib/dpkg/status
   3.28.1-0ubuntu4 500
  500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64

  What I expect to happen:
Software is not installed for a user without sudo access.

  What does happen:
  I'm logging in with an LDAP user. This user does not have sudo access.

  When I select software from gnome-software ("Ubuntu Software"), it
  pops up and asks for my users password. I enter this in, and the
  software then installs (tested with blender, libreoffice, opencl
  driver).

  My user does *not* have sudo access on the system.

  $ sudo su -
  [sudo] password for jason: 
  jason is not in the sudoers file.  This incident will be reported.

  It appears these *may* be being installed with Snaps ... which still:

  How, without having root access, can an unprivileged user install
  something onto the system?

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-software 3.28.1-0ubuntu4.18.04.8
  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.5
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Nov  1 13:53:03 2019
  InstallationDate: Installed on 2019-11-01 (0 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  InstalledPlugins:
   gnome-software-plugin-flatpak N/A
   gnome-software-plugin-limba   N/A
   gnome-software-plugin-snap3.28.1-0ubuntu4.18.04.8
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-software
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1833114] Re: print page dialog latency when trying to cancel or to save

2019-11-05 Thread Christopher Barrington-Leigh
Actually, it is not true that this is solved under 19.10.  All that has
happened is that the latency has shortened to 1-2 seconds. It is *still*
the case that during that time, I cannot get the focus in any other
window or do anything else in the operating system.

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

Title:
  print page dialog latency when trying to cancel or to save

Status in chromium-browser package in Ubuntu:
  New
Status in gtk+3.0 package in Ubuntu:
  Confirmed

Bug description:
  Since less than a month ago, using the print page dialog (which for me
  defaults to saving as PDF) is outlandishly slow. Once opened, if I try
  to close it (click cancel / press Esc) or to use it (click Save or
  press Enter), there is no visible response, and my system hangs for 10
  seconds.  After that though, the operation concludes successfully and
  things return to normal.

  This did not used to happen. Closing or submitting the print-to-PDF
  used to result in the pop-up window closing immediately and the
  browser regaining responsiveness.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: chromium-browser 74.0.3729.169-0ubuntu0.19.04.1
  ProcVersionSignature: Ubuntu 5.0.0-16.17-generic 5.0.8
  Uname: Linux 5.0.0-16-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DRM.card0-DP-1:
   enabled: disabled
   dpms: Off
   status: disconnected
   edid-base64: 
   modes:
  DRM.card0-DP-2:
   enabled: disabled
   dpms: Off
   status: disconnected
   edid-base64: 
   modes:
  DRM.card0-DP-5:
   enabled: enabled
   dpms: On
   status: connected
   edid-base64: 
AP///wAEchAEyHEQUQsZAQSlRyh4PiVfqFRNnyUOT1O/74BxT4FAgYCBwIEAlQCzANHATdAAoPBwPoAwIDUAxY8hAAAaBHQAMPJwWoCwWIoAxY8hAAAa/QAdTB+gPAEKICAgICAg/ABCMzI2SEsKICAgICAgAQwCAxzhT5ACAwQFBgcBERITFBUWHyMJBweDAQAAAjqAGHE4LUBYLEUAxY8hAAAeAR2AGHEcFiBYLCUAxY8hAACeAR0AclHQHiBuKFUAxY8hAAAejArQiiDgLRAQPpYAxY8hAAAYVl4AoKCgKVAwIDUAxI8hAAAa
   modes: 3840x2160 3840x2160 2560x1440 1920x1080 1920x1080 1920x1080 1920x1080 
1680x1050 1280x1024 1280x1024 1440x900 1280x960 1280x800 1152x864 1280x720 
1280x720 1280x720 1280x720 1024x768 1024x768 1024x768 832x624 800x600 800x600 
800x600 800x600 720x576 720x576 720x480 720x480 720x480 720x480 720x480 640x480 
640x480 640x480 640x480 640x480 640x480 720x400
  DRM.card0-DP-6:
   enabled: disabled
   dpms: On
   status: connected
   edid-base64: 
AP///wAQrAngTEFNMAkPAQPOKxt46gGVo1dMnCUSUFSlSwCBgHFPAQEBAQEBAQEBAQEBfC6QoGAaHkAwIDYAsg4RAAAa/wBUNjEzMDUzMjBNQUwK/QA4Sx5TDgAKICAgICAg/ABERUxMIDIwMDVGUFcKAAM=
   modes: 1680x1050 1280x1024 1280x1024 1152x864 1024x768 1024x768 800x600 
800x600 640x480 640x480 720x400
  DRM.card0-DP-7:
   enabled: disabled
   dpms: On
   status: disconnected
   edid-base64: 
   modes:
  DRM.card0-HDMI-A-1:
   enabled: disabled
   dpms: Off
   status: disconnected
   edid-base64: 
   modes:
  DRM.card0-HDMI-A-2:
   enabled: disabled
   dpms: Off
   status: disconnected
   edid-base64: 
   modes:
  DRM.card0-eDP-1:
   enabled: enabled
   dpms: On
   status: connected
   edid-base64: 
AP///wAGrz0TACYXAQSVHxF4AoflpFZQniYNUFQBAQEBAQEBAQEBAQEBAQEBFDeAuHA4JEAQED4ANa0QAAAYDwAg/gBBVU8KICAgICAgICAg/gBCMTQwSEFOMDEuMyAKAHo=
   modes: 1920x1080
  Date: Mon Jun 17 14:03:12 2019
  Desktop-Session:
   'ubuntu'
   '/etc/xdg/xdg-ubuntu:/etc/xdg'
   '/usr/share/ubuntu:/usr/local/share:/usr/share:/var/lib/snapd/desktop'
  DetectedPlugins:
   
  EcryptfsInUse: Yes
  Env:
   'None'
   'None'
  InstallationDate: Installed on 2019-01-24 (144 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  InstalledPlugins:
   
  Load-Avg-1min: 3.09
  Load-Processes-Running-Percent:   0.1%
  MachineType: LENOVO 20BXCTO1WW
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-16-generic 
root=UUID=a6081f39-700f-4698-bda4-464e53d9d229 ro quiet splash vt.handoff=1
  SourcePackage: chromium-browser
  UpgradeStatus: Upgraded to disco on 2019-05-29 (19 days ago)
  dmi.bios.date: 09/13/2017
  dmi.bios.vendor: LENOVO
  dmi.bios.version: JBET66WW (1.30 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20BXCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrJBET66WW(1.30):bd09/13/2017:svnLENOVO:pn20BXCTO1WW:pvrThinkPadT450s:rvnLENOVO:rn20BXCTO1WW:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad T450s
  dmi.product.name: 20BXCTO1WW
  dmi.product.sku: LENOVO_MT_20BX_BU_Think_FM_ThinkPad T450s
  dmi.product.version: ThinkPad T450s
  dmi.sys.vendor: LENOVO
  modified.conffile..etc.default.chromium-browser: [deleted]

To manage notifications about this bug

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

2019-11-05 Thread Marcus Tomlinson
** Changed in: libreoffice (Ubuntu)
   Status: New => In Progress

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

-- 
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:
  In Progress
Status in libreoffice source package in Eoan:
  In Progress

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 1847516] Re: Alt+Shift does not change layout

2019-11-05 Thread Sebastien Bacher
** Package changed: gnome-settings-daemon (Ubuntu) => gnome-tweaks
(Ubuntu)

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

Title:
  Alt+Shift does not change layout

Status in gnome-tweaks package in Ubuntu:
  New

Bug description:
  Ubuntu 19.10 Daily 09.10.2019 and older

  After settings in gnome tweaks I expect changing of keyboard layout,
  but it still super+space.

  Also , shortcut's "Set shortcut' ignores Alt+Shift.

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

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


[Desktop-packages] [Bug 810773] Re: Changing font settings are ineffective

2019-11-05 Thread Paul White
Unable to reproduce with Thunderbird 60.9 (bionic) or 68.1.2 (eoan).

With no comments for over 8 years this issue was probably resolved a
long time ago and this bug report can now be closed. Changing status to
"Incomplete" to allow this report to expire in the absence of any
further comments to confirm that the bug still exists.

Paul White
[Ubuntu Bug Squad]

** Changed in: thunderbird (Ubuntu)
   Status: Confirmed => Incomplete

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

Title:
  Changing font settings are ineffective

Status in thunderbird package in Ubuntu:
  Incomplete

Bug description:
  When changing font settings (Preferences -> Display -> Fonts ->
  Advanced) - when I change those settings and select different fonts
  are use the checkboxes, the settings don't stay when I close the
  dialog box. I then go back to the Advanced Fonts dialog and the
  original settings are there and not the ones I selected.

  ProblemType: Bug
  DistroRelease: Ubuntu 11.10
  Package: thunderbird 5.0+build1+nobinonly-0ubuntu5
  ProcVersionSignature: Ubuntu 3.0.0-5.6-generic 3.0.0-rc7
  Uname: Linux 3.0.0-5-generic i686
  Architecture: i386
  Date: Thu Jul 14 15:06:43 2011
  InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Alpha i386 (20110202)
  ProcEnviron:
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: thunderbird
  UpgradeStatus: Upgraded to oneiric on 2011-07-13 (1 days ago)

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

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


[Desktop-packages] [Bug 859315] Re: clicking email address in web browser opens HTML composer, despite default account settings preferring plain text

2019-11-05 Thread Paul White
We are sorry that we do not always have the capacity to review all
reported bugs in a timely manner.

I'm unable to reproduce this issue using Thunderbird 60.9 in Ubuntu
18.04. Presumably this issue was resolved some time ago and this bug
report can now be closed. I'm changing the status to "Incomplete" to
allow this report to expire in the absence of any further comments to
confirm that the bug still exists.

Thank you for helping make Ubuntu better.

Paul White
[Ubuntu Bug Squad]


** Changed in: thunderbird (Ubuntu)
   Status: Confirmed => Incomplete

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

Title:
  clicking email address in web browser opens HTML composer, despite
  default account settings preferring plain text

Status in thunderbird package in Ubuntu:
  Incomplete

Bug description:
  In the account settings for my default (and only) mail account, I have
  elected not to compose messages in HTML format  (screen shot 1).
  Accordingly, when I hit the Write button on the main window I am
  presented with a plain-text composer, as expected (screen shot 2).

  When I click an email address in Firefox however, I am presented with
  an HTML composer (screen shot 3).

  Further, simply selecting "plain text only" in this composer does not
  actually achieve the desired effect of converting the message back to
  plain-text.  Instead, the HTML formatting toolbar is hidden but the
  message remains in HTML format.  This can be verified by saving a test
  message to the Drafts folder and then inspecting its source.  There is
  no way to convert the message back to plain-text short of copying the
  message body into a new composer properly configured for plain text.

  Screen shots will be attached shortly.

  ProblemType: Bug
  DistroRelease: Ubuntu 11.10
  Package: thunderbird 7.0+build1+nobinonly-0ubuntu1
  ProcVersionSignature: Ubuntu 3.0.0-11.18-generic 3.0.4
  Uname: Linux 3.0.0-11-generic x86_64
  AddonCompatCheckDisabled: False
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
  ApportVersion: 1.23-0ubuntu1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  lx 1828 F pulseaudio
  BuildID: 20110925021328
  CRDA: Error: [Errno 2] No such file or directory
  Card0.Amixer.info:
   Card hw:0 'Intel'/'HDA Intel at 0xf870 irq 47'
 Mixer name : 'Realtek ALC268'
 Components : 'HDA:10ec0268,103c30cc,0013 
HDA:10573055,10573055,00100700'
 Controls  : 21
 Simple ctrls  : 13
  Channel: release
  Date: Mon Sep 26 11:49:26 2011
  ForcedLayersAccel: False
  IfupdownConfig:
   auto lo
   iface lo inet loopback
  InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007)
  IpRoute:
   default via 192.168.0.1 dev wlan0  proto static 
   169.254.0.0/16 dev wlan0  scope link  metric 1000 
   192.168.0.0/24 dev wlan0  proto kernel  scope link  src 192.168.0.3
  Prefs:
   places.database.lastMaintenance - 1316911732
   extensions.lastAppVersion - 7.0
   network.cookie.prefsMigrated - true
   places.history.expiration.transient_current_max_pages - 62892
  Profiles: Profile0 (Default) - LastVersion=7.0/20110925021328
  RunningIncompatibleAddons: False
  SourcePackage: thunderbird
  UpgradeStatus: Upgraded to oneiric on 2011-09-12 (13 days ago)
  dmi.bios.date: 04/04/2007
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: F.05
  dmi.board.name: 30CC
  dmi.board.vendor: Quanta
  dmi.board.version: 79.10
  dmi.chassis.type: 10
  dmi.chassis.vendor: Quanta
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrF.05:bd04/04/2007:svnHewlett-Packard:pnHPPaviliondv6500NotebookPC:pvrRev1:rvnQuanta:rn30CC:rvr79.10:cvnQuanta:ct10:cvrN/A:
  dmi.product.name: HP Pavilion dv6500 Notebook PC
  dmi.product.version: Rev 1
  dmi.sys.vendor: Hewlett-Packard

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

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


[Desktop-packages] [Bug 1851370] [NEW] Epson sx420w prints colors unaligned by row in photoprint

2019-11-05 Thread ossikoo
Public bug reported:

Color pattern in A4 paper is as follows (first line printed first):

YY
RR
AA
...
AA
BB
KK

Y=yellow row
R=red row
A=all colors(but displaced image)
B=Blue line
K=Black line

In fact, I can see two images with partial colors. Test image does not show 
this behavior, but
eg. photoprint does. Same problem also with 32bit version.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: cups 2.1.3-4ubuntu0.10
ProcVersionSignature: Ubuntu 4.4.0-142.168-generic 4.4.167
Uname: Linux 4.4.0-142-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.21
Architecture: amd64
CurrentDesktop: MATE
Date: Tue Nov  5 14:19:15 2019
InstallationDate: Installed on 2016-05-02 (1282 days ago)
InstallationMedia: Ubuntu-MATE 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
Lpstat:
 device for clx-2160samsung: 
dnssd://Samsung%20CLX-2160%20Series%20%40%20koti._ipp._tcp.local/cups?uuid=c81b61b8-294e-385f-5842-2eb4094e7020
 device for Epson-Stylus-SX420W: 
usb://EPSON/Stylus%20SX420W?serial=4D4343503032353032&interface=1
MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
Papersize: a4
PpdFiles: Error: command ['fgrep', '-H', '*NickName', 
'/etc/cups/ppd/Epson-Stylus-SX420W.ppd'] failed with exit code 2: grep: 
/etc/cups/ppd/Epson-Stylus-SX420W.ppd: Permission denied
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-142-generic 
root=UUID=eb3964d3-9c22-4ca8-8b43-01f4a52b1768 ro
SourcePackage: cups
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 05/07/2010
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: P1.30
dmi.board.name: A780LM-S
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.30:bd05/07/2010:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnA780LM-S:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
dmi.product.name: To Be Filled By O.E.M.
dmi.product.version: To Be Filled By O.E.M.
dmi.sys.vendor: To Be Filled By O.E.M.

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


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

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

Title:
  Epson sx420w prints colors unaligned by row in photoprint

Status in cups package in Ubuntu:
  New

Bug description:
  Color pattern in A4 paper is as follows (first line printed first):

  YY
  RR
  AA
  ...
  AA
  BB
  KK

  Y=yellow row
  R=red row
  A=all colors(but displaced image)
  B=Blue line
  K=Black line

  In fact, I can see two images with partial colors. Test image does not show 
this behavior, but
  eg. photoprint does. Same problem also with 32bit version.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: cups 2.1.3-4ubuntu0.10
  ProcVersionSignature: Ubuntu 4.4.0-142.168-generic 4.4.167
  Uname: Linux 4.4.0-142-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.21
  Architecture: amd64
  CurrentDesktop: MATE
  Date: Tue Nov  5 14:19:15 2019
  InstallationDate: Installed on 2016-05-02 (1282 days ago)
  InstallationMedia: Ubuntu-MATE 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  Lpstat:
   device for clx-2160samsung: 
dnssd://Samsung%20CLX-2160%20Series%20%40%20koti._ipp._tcp.local/cups?uuid=c81b61b8-294e-385f-5842-2eb4094e7020
   device for Epson-Stylus-SX420W: 
usb://EPSON/Stylus%20SX420W?serial=4D4343503032353032&interface=1
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  Papersize: a4
  PpdFiles: Error: command ['fgrep', '-H', '*NickName', 
'/etc/cups/ppd/Epson-Stylus-SX420W.ppd'] failed with exit code 2: grep: 
/etc/cups/ppd/Epson-Stylus-SX420W.ppd: Permission denied
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-142-generic 
root=UUID=eb3964d3-9c22-4ca8-8b43-01f4a52b1768 ro
  SourcePackage: cups
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/07/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P1.30
  dmi.board.name: A780LM-S
  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.30:bd05/07/2010:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnA780LM-S:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.

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

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

[Desktop-packages] [Bug 1851127] Re: app page shows no install progress

2019-11-05 Thread Sebastien Bacher
Thank you for your bug report. Could you add a 'journalctl -b 0' log
from a session having the issue? I just tried on a fresh install,
clicked on the gnome-software, clicked on the sublime snap, clicked
install, entered my password and the install bar displayed and updated
as expected

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

Title:
  app page shows no install progress

Status in gnome-software package in Ubuntu:
  Incomplete

Bug description:
  I just installed a couple of applications (bomb squad and android
  studio) and while installing, they show no install progress.

  Steps to reproduce

  Launch gnome-software
  Click an application from the front of G-S
  Click Install
  Fill in password

  Expected outcome

  I expect to be shown a progress bar, showing that installation is
  happening

  Actual outcome

  I see no progress, yet running `snap changes` in a terminal shows it is 
installing
  In addition, clicking "Install" again fails due to the install running.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: gnome-software 3.30.6-2ubuntu10
  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.1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Nov  3 11:42:28 2019
  InstallationDate: Installed on 2019-10-27 (6 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  InstalledPlugins:
   gnome-software-plugin-flatpak N/A
   gnome-software-plugin-snap3.30.6-2ubuntu10
  SourcePackage: gnome-software
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1794064] Re: Clicking a hyperlink in a PDF fails to open it if the default browser is a snap

2019-11-05 Thread Sebastien Bacher
** Changed in: evince (Ubuntu)
   Status: New => Confirmed

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

Title:
  Clicking a hyperlink in a PDF fails to open it if the default browser
  is a snap

Status in evince package in Ubuntu:
  Confirmed

Bug description:
  This is related to bug #1792648. After fixing that one (see discussion
  at https://salsa.debian.org/gnome-team/evince/merge_requests/1),
  clicking a hyperlink in a PDF opens it correctly if the default
  browser is a well-known application (such as /usr/bin/firefox), but it
  fails to do so if the default browser is a snap (e.g. the chromium
  snap).

  This is not a recent regression, it's not working on bionic either.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: evince 3.30.0-2
  ProcVersionSignature: Ubuntu 4.18.0-7.8-generic 4.18.5
  Uname: Linux 4.18.0-7-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.10-0ubuntu11
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Sep 24 12:28:06 2018
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2016-07-02 (813 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  SourcePackage: evince
  UpgradeStatus: Upgraded to cosmic on 2018-09-14 (9 days ago)
  modified.conffile..etc.apparmor.d.abstractions.evince: [modified]
  mtime.conffile..etc.apparmor.d.abstractions.evince: 2018-09-24T11:35:41.904158

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

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


[Desktop-packages] [Bug 992981] Re: thunderbird audio and visual notifications don't work

2019-11-05 Thread Paul White
We are sorry that we do not always have the capacity to review all
reported bugs in a timely manner. There have been no comments on this
bug report for some time.

I'm getting both audio and visual notifications when using Thunderbird
60.9 and Ubuntu 18.04. Is this still an issue for anyone? I'm changing
the status to "Incomplete" to allow this report to expire in the absence
of any further comments to confirm that a problem still exists.

Thank you for helping make Ubuntu better.

Paul White
[Ubuntu Bug Squad]


** Changed in: thunderbird (Ubuntu)
   Status: Confirmed => Incomplete

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

Title:
  thunderbird audio and visual notifications don't work

Status in thunderbird package in Ubuntu:
  Incomplete

Bug description:
  I hear no sound when new mail arrives in Thunderbird and only
  occasionally will the new mail envelope change colr when new mail
  arrives.  I have tried both the default audio notification sound as
  well as my own .wav files.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: thunderbird 11.0.1+build1-0ubuntu2
  ProcVersionSignature: Ubuntu 3.2.0-24.37-generic-pae 3.2.14
  Uname: Linux 3.2.0-24-generic-pae i686
  NonfreeKernelModules: nvidia
  AddonCompatCheckDisabled: False
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
  ApportVersion: 2.0.1-0ubuntu7
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  marcw  1795 F pulseaudio
   /dev/snd/controlC1:  marcw  1795 F pulseaudio
  BuildID: 20120411015315
  CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 
not found.
  Card0.Amixer.info:
   Card hw:0 'NVidia'/'HDA NVidia at 0xfc10 irq 21'
 Mixer name : 'Realtek ALC888'
 Components : 'HDA:10ec0888,1458e601,0011'
 Controls  : 49
 Simple ctrls  : 22
  Card1.Amixer.info:
   Card hw:1 'Q9000'/'Logitech, Inc. QuickCam Pro 9000 at usb-:00:02.1-9, 
high speed'
 Mixer name : 'USB Mixer'
 Components : 'USB046d:0990'
 Controls  : 2
 Simple ctrls  : 1
  Card1.Amixer.values:
   Simple mixer control 'Mic',0
 Capabilities: cvolume cvolume-joined cswitch cswitch-joined penum
 Capture channels: Mono
 Limits: Capture 0 - 3072
 Mono: Capture 559 [18%] [20.18dB] [on]
  Channel: release
  Date: Tue May  1 20:55:22 2012
  ForcedLayersAccel: False
  IfupdownConfig:
   auto lo
   iface lo inet loopback
  IncompatibleExtensions:
   EDS Contact Integration - ID=edsintegrat...@mozilla.com, Version=0.3.9, 
minVersion=7.0, maxVersion=11.0a1, Location=app-global, Type=extension, 
Active=Yes
   Google Calendar Tab - ID=googlecalendartab@momo, Version=3.9, 
minVersion=3.1, maxVersion=10.0a1, Location=app-profile, Type=extension, 
Active=Yes
   Google Contacts - ID={BDD92442-0534-4D6F-A966-BAB7D561D781}, Version=0.6.40, 
minVersion=3.1, maxVersion=9.*, Location=app-profile, Type=extension, Active=Yes
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release i386 
(20120423)
  IpRoute:
   default via 192.168.0.1 dev eth0  proto static 
   169.254.0.0/16 dev eth0  scope link  metric 1000 
   192.168.0.0/24 dev eth0  proto kernel  scope link  src 192.168.0.2  metric 1
  IwConfig:
   lono wireless extensions.
   
   eth0  no wireless extensions.
  PciNetwork:
   
  Prefs:
   places.database.lastMaintenance - 1335848162
   extensions.lastAppVersion - 11.0.1
   network.cookie.prefsMigrated - true
   places.history.expiration.transient_current_max_pages - 104858
  ProcEnviron:
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  Profiles: Profile0 (Default) - LastVersion=11.0.1/20120411015315 (Running)
  RfKill:
   
  RunningIncompatibleAddons: True
  SourcePackage: thunderbird
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/26/2009
  dmi.bios.vendor: Award Software International, Inc.
  dmi.bios.version: FHe
  dmi.board.name: M57SLI-S4
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.type: 3
  dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrFHe:bd02/26/2009:svn:pn:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnM57SLI-S4:rvrx.x:cvn:ct3:cvr:

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

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


[Desktop-packages] [Bug 1850977] Re: gnome-software installs software without user having sudo access

2019-11-05 Thread Jason Stover
A dialog box appears. It just shows the Full Name field, and the name
shown is "Jason Stover" (login: jason) for the LDAP account. The Local
Admin account name is "Jason Local" (login: jlocal).

The passwords between the two accounts is also different incase it was
showing the name of the logged in user, but asking for the password of
the local account, the passwords wouldn't have matched up.

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

Title:
  gnome-software installs software without user having sudo access

Status in gnome-software package in Ubuntu:
  Incomplete

Bug description:
  $ lsb_release -rd
  Description:  Ubuntu 18.04.2 LTS
  Release:  18.04

  $ apt-cache policy gnome-software
  gnome-software:
Installed: 3.28.1-0ubuntu4.18.04.8
Candidate: 3.28.1-0ubuntu4.18.04.12
Version table:
   3.28.1-0ubuntu4.18.04.12 500
  500 http://us.archive.ubuntu.com/ubuntu bionic-updates/main amd64 
Packages
   *** 3.28.1-0ubuntu4.18.04.8 100
  100 /var/lib/dpkg/status
   3.28.1-0ubuntu4 500
  500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64

  What I expect to happen:
Software is not installed for a user without sudo access.

  What does happen:
  I'm logging in with an LDAP user. This user does not have sudo access.

  When I select software from gnome-software ("Ubuntu Software"), it
  pops up and asks for my users password. I enter this in, and the
  software then installs (tested with blender, libreoffice, opencl
  driver).

  My user does *not* have sudo access on the system.

  $ sudo su -
  [sudo] password for jason: 
  jason is not in the sudoers file.  This incident will be reported.

  It appears these *may* be being installed with Snaps ... which still:

  How, without having root access, can an unprivileged user install
  something onto the system?

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-software 3.28.1-0ubuntu4.18.04.8
  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.5
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Nov  1 13:53:03 2019
  InstallationDate: Installed on 2019-11-01 (0 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  InstalledPlugins:
   gnome-software-plugin-flatpak N/A
   gnome-software-plugin-limba   N/A
   gnome-software-plugin-snap3.28.1-0ubuntu4.18.04.8
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-software
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1851375] [NEW] gnome-shell stops allowing interactions

2019-11-05 Thread fcole90
Public bug reported:

>From time to time gnome-shell gets unresponsive to inputs. I can move
the cursor, but I cannot interact with the shell in any way, neither
with mouse or keyboard.

When this happens I move to a vt and restart the shell with `killall -3
gnome-shell`. After this the shell does usually resume working (albeit
some application crashes in the process from time to time).

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: gnome-shell 3.34.1+git20191024-1ubuntu1
ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
Uname: Linux 5.3.0-19-generic x86_64
ApportVersion: 2.20.11-0ubuntu9
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Tue Nov  5 15:31:55 2019
DisplayManager: gdm3
InstallationDate: Installed on 2019-02-03 (274 days ago)
InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725)
RelatedPackageVersions: mutter-common 3.34.1+git20191022-2ubuntu1
SourcePackage: gnome-shell
UpgradeStatus: Upgraded to focal on 2019-07-21 (106 days ago)

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


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

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

Title:
  gnome-shell stops allowing interactions

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  From time to time gnome-shell gets unresponsive to inputs. I can move
  the cursor, but I cannot interact with the shell in any way, neither
  with mouse or keyboard.

  When this happens I move to a vt and restart the shell with `killall
  -3 gnome-shell`. After this the shell does usually resume working
  (albeit some application crashes in the process from time to time).

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell 3.34.1+git20191024-1ubuntu1
  ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
  Uname: Linux 5.3.0-19-generic x86_64
  ApportVersion: 2.20.11-0ubuntu9
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Nov  5 15:31:55 2019
  DisplayManager: gdm3
  InstallationDate: Installed on 2019-02-03 (274 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  RelatedPackageVersions: mutter-common 3.34.1+git20191022-2ubuntu1
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to focal on 2019-07-21 (106 days ago)

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

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


[Desktop-packages] [Bug 1849930] Re: Additional L2TP VPN Breaks First VPN

2019-11-05 Thread Bug Watch Updater
** Changed in: gnome-control-center
   Status: New => Fix Released

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

Title:
  Additional L2TP VPN Breaks First VPN

Status in gnome-control-center:
  Fix Released
Status in NetworkManager:
  New
Status in strongSwan:
  New
Status in gnome-control-center package in Ubuntu:
  Invalid
Status in network-manager-l2tp package in Ubuntu:
  Fix Released

Bug description:
  When I add only one L2TP VPN profile to gnome-control-center's Network
  > VPN settings, it works fine.

  However, if I add a 2nd L2TP VPN, the 2nd L2TP VPN, not only doesn't
  work, but it corrupts the first L2TP VPN so that it too stops working.

  Furthermore, if I remove 2nd L2TP VPN profile (that corrupted the
  first L2TP VPN) this does NOT repair the corruption to the first L2TP
  VPN, it remains corrupted.

  Additionally, removing all VPN profiles and re-adding the first one
  back, doesn't repair the corruption. Rebooting and adding them back
  doesn't work either.

  The only thing that works, that I've found, is completely reinstalling
  Ubuntu 19.10. Please advise better workarounds than reinstalling.

  In case it matters, these additional packages were also required for
  my initial VPN setup:

  sudo apt-get install -y network-manager-l2tp network-manager-l2tp-
  gnome strongswan

  Here's what's in the syslog on a failed VPN Connection attempt:

  Oct 26 02:58:35 workstation5 NetworkManager[1241]:   [1572076715.5632] 
audit: op="connection-activate" uuid="1942cf95-93b1-4e74-a44a-947a46bffb5a" 
name="L2TP VPN1" pid=3531 uid=1000 result="success"
  Oct 26 02:58:35 workstation5 NetworkManager[1241]:   [1572076715.5702] 
vpn-connection[0x5642f421c750,1932cf95-91b1-4e85-a44a-498a56befb5a,"L2TP 
VPN1",0]: Started the VPN service, PID 7273
  Oct 26 02:58:35 workstation5 NetworkManager[1241]:   [1572076715.5747] 
vpn-connection[0x5642f421c750,1932cf95-91b1-4e85-a44a-498a56befb5a,"L2TP 
VPN1",0]: Saw the service appear; activating connection
  Oct 26 02:58:35 workstation5 NetworkManager[1241]:   [1572076715.6566] 
vpn-connection[0x5642f421c750,1932cf95-91b1-4e85-a44a-498a56befb5a,"L2TP 
VPN1",0]: VPN connection: (ConnectInteractive) reply received
  Oct 26 02:58:35 workstation5 NetworkManager[1241]: Stopping strongSwan IPsec 
failed: starter is not running
  Oct 26 02:58:37 workstation5 NetworkManager[1241]: Starting strongSwan 5.7.2 
IPsec [starter]...
  Oct 26 02:58:37 workstation5 NetworkManager[1241]: Loading config setup
  Oct 26 02:58:37 workstation5 NetworkManager[1241]: Loading conn 
'1942cf95-93b1-4e74-a44a-947a46bffb5a'
  Oct 26 02:58:37 workstation5 NetworkManager[1241]: found netkey IPsec stack
  Oct 26 02:58:48 workstation5 NetworkManager[1241]: Stopping strongSwan 
IPsec...
  Oct 26 02:58:48 workstation5 NetworkManager[1241]: initiating Main Mode 
IKE_SA 1942cf95-93b1-4e74-a44a-947a46bffb5a[1] to 49.230.24.121
  Oct 26 02:58:48 workstation5 NetworkManager[1241]: generating ID_PROT request 
0 [ SA V V V V V ]
  Oct 26 02:58:48 workstation5 NetworkManager[1241]: sending packet: from 
192.168.1.2[500] to 49.230.24.121[500] (236 bytes)
  Oct 26 02:58:48 workstation5 NetworkManager[1241]: received packet: from 
49.230.24.121[500] to 192.168.1.2[500] (156 bytes)
  Oct 26 02:58:48 workstation5 NetworkManager[1241]: parsed ID_PROT response 0 
[ SA V V V V ]
  Oct 26 02:58:48 workstation5 NetworkManager[1241]: received XAuth vendor ID
  Oct 26 02:58:48 workstation5 NetworkManager[1241]: received DPD vendor ID
  Oct 26 02:58:48 workstation5 NetworkManager[1241]: received FRAGMENTATION 
vendor ID
  Oct 26 02:58:48 workstation5 NetworkManager[1241]: received NAT-T (RFC 3947) 
vendor ID
  Oct 26 02:58:48 workstation5 NetworkManager[1241]: selected proposal: 
IKE:3DES_CBC/HMAC_SHA1_96/PRF_HMAC_SHA1/MODP_1024
  Oct 26 02:58:48 workstation5 NetworkManager[1241]: generating ID_PROT request 
0 [ KE No NAT-D NAT-D ]
  Oct 26 02:58:48 workstation5 NetworkManager[1241]: sending packet: from 
192.168.1.2[500] to 49.230.24.121[500] (244 bytes)
  Oct 26 02:58:48 workstation5 NetworkManager[1241]: received packet: from 
49.230.24.121[500] to 192.168.1.2[500] (244 bytes)
  Oct 26 02:58:48 workstation5 NetworkManager[1241]: parsed ID_PROT response 0 
[ KE No NAT-D NAT-D ]
  Oct 26 02:58:48 workstation5 NetworkManager[1241]: local host is behind NAT, 
sending keep alives
  Oct 26 02:58:48 workstation5 NetworkManager[1241]: generating ID_PROT request 
0 [ ID HASH ]
  Oct 26 02:58:48 workstation5 NetworkManager[1241]: sending packet: from 
192.168.1.2[4500] to 49.230.24.121[4500] (68 bytes)
  Oct 26 02:58:48 workstation5 NetworkManager[1241]: received packet: from 
49.230.24.121[500] to 192.168.1.2[500] (68 bytes)
  Oct 26 02:58:48 workstation5 NetworkManager[1241]: invalid HASH_V1 payload 
length, decryption failed?
  Oct 26 02:58:48 workstation5 NetworkManager[1241]: co

[Desktop-packages] [Bug 1718135] Re: nautilus crashed with SIGSEGV in nautilus_progress_manager_has_viewers()

2019-11-05 Thread Luca Ciavatta
I have experienced this bug in a clean 18.04.3 install.

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

Title:
  nautilus crashed with SIGSEGV in
  nautilus_progress_manager_has_viewers()

Status in Nautilus:
  New
Status in nautilus package in Ubuntu:
  Triaged

Bug description:
  Copying files

  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: nautilus 1:3.26.0-0ubuntu1
  ProcVersionSignature: Ubuntu 4.12.0-13.14-generic 4.12.10
  Uname: Linux 4.12.0-13-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Sep 19 10:25:22 2017
  ExecutablePath: /usr/bin/nautilus
  InstallationDate: Installed on 2015-10-06 (713 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150924)
  ProcCmdline: /usr/bin/nautilus --gapplication-service
  SegvAnalysis:
   Segfault happened at: 0x5573e2a1d902 
:  cmpq   $0x0,0x20(%rdi)
   PC (0x5573e2a1d902) ok
   source "$0x0" ok
   destination "0x20(%rdi)" (0x0020) not located in a known VMA region 
(needed writable region)!
  SegvReason: writing NULL VMA
  Signal: 11
  SourcePackage: nautilus
  StacktraceTop:
   nautilus_progress_manager_has_viewers ()
   ()
   g_closure_invoke () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   g_signal_emit_valist () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
  Title: nautilus crashed with SIGSEGV in 
nautilus_progress_manager_has_viewers()
  UpgradeStatus: Upgraded to artful on 2017-09-14 (4 days ago)
  UserGroups: adm audio cdrom dialout dip fax lpadmin lxd netdev plex plugdev 
sambashare scanner sudo tape vboxusers video
  usr_lib_nautilus: dropbox 2015.10.28

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

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


[Desktop-packages] [Bug 1833114] Re: print page dialog latency when trying to cancel or to save

2019-11-05 Thread Olivier Tilloy
Thanks for the feedback Christopher. I'm not suggesting everyone upgrade to 
19.10 right away, I was just curious whether doing so would somehow fix the 
problem.
This obviously still needs looking into.

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

Title:
  print page dialog latency when trying to cancel or to save

Status in chromium-browser package in Ubuntu:
  New
Status in gtk+3.0 package in Ubuntu:
  Confirmed

Bug description:
  Since less than a month ago, using the print page dialog (which for me
  defaults to saving as PDF) is outlandishly slow. Once opened, if I try
  to close it (click cancel / press Esc) or to use it (click Save or
  press Enter), there is no visible response, and my system hangs for 10
  seconds.  After that though, the operation concludes successfully and
  things return to normal.

  This did not used to happen. Closing or submitting the print-to-PDF
  used to result in the pop-up window closing immediately and the
  browser regaining responsiveness.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: chromium-browser 74.0.3729.169-0ubuntu0.19.04.1
  ProcVersionSignature: Ubuntu 5.0.0-16.17-generic 5.0.8
  Uname: Linux 5.0.0-16-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DRM.card0-DP-1:
   enabled: disabled
   dpms: Off
   status: disconnected
   edid-base64: 
   modes:
  DRM.card0-DP-2:
   enabled: disabled
   dpms: Off
   status: disconnected
   edid-base64: 
   modes:
  DRM.card0-DP-5:
   enabled: enabled
   dpms: On
   status: connected
   edid-base64: 
AP///wAEchAEyHEQUQsZAQSlRyh4PiVfqFRNnyUOT1O/74BxT4FAgYCBwIEAlQCzANHATdAAoPBwPoAwIDUAxY8hAAAaBHQAMPJwWoCwWIoAxY8hAAAa/QAdTB+gPAEKICAgICAg/ABCMzI2SEsKICAgICAgAQwCAxzhT5ACAwQFBgcBERITFBUWHyMJBweDAQAAAjqAGHE4LUBYLEUAxY8hAAAeAR2AGHEcFiBYLCUAxY8hAACeAR0AclHQHiBuKFUAxY8hAAAejArQiiDgLRAQPpYAxY8hAAAYVl4AoKCgKVAwIDUAxI8hAAAa
   modes: 3840x2160 3840x2160 2560x1440 1920x1080 1920x1080 1920x1080 1920x1080 
1680x1050 1280x1024 1280x1024 1440x900 1280x960 1280x800 1152x864 1280x720 
1280x720 1280x720 1280x720 1024x768 1024x768 1024x768 832x624 800x600 800x600 
800x600 800x600 720x576 720x576 720x480 720x480 720x480 720x480 720x480 640x480 
640x480 640x480 640x480 640x480 640x480 720x400
  DRM.card0-DP-6:
   enabled: disabled
   dpms: On
   status: connected
   edid-base64: 
AP///wAQrAngTEFNMAkPAQPOKxt46gGVo1dMnCUSUFSlSwCBgHFPAQEBAQEBAQEBAQEBfC6QoGAaHkAwIDYAsg4RAAAa/wBUNjEzMDUzMjBNQUwK/QA4Sx5TDgAKICAgICAg/ABERUxMIDIwMDVGUFcKAAM=
   modes: 1680x1050 1280x1024 1280x1024 1152x864 1024x768 1024x768 800x600 
800x600 640x480 640x480 720x400
  DRM.card0-DP-7:
   enabled: disabled
   dpms: On
   status: disconnected
   edid-base64: 
   modes:
  DRM.card0-HDMI-A-1:
   enabled: disabled
   dpms: Off
   status: disconnected
   edid-base64: 
   modes:
  DRM.card0-HDMI-A-2:
   enabled: disabled
   dpms: Off
   status: disconnected
   edid-base64: 
   modes:
  DRM.card0-eDP-1:
   enabled: enabled
   dpms: On
   status: connected
   edid-base64: 
AP///wAGrz0TACYXAQSVHxF4AoflpFZQniYNUFQBAQEBAQEBAQEBAQEBAQEBFDeAuHA4JEAQED4ANa0QAAAYDwAg/gBBVU8KICAgICAgICAg/gBCMTQwSEFOMDEuMyAKAHo=
   modes: 1920x1080
  Date: Mon Jun 17 14:03:12 2019
  Desktop-Session:
   'ubuntu'
   '/etc/xdg/xdg-ubuntu:/etc/xdg'
   '/usr/share/ubuntu:/usr/local/share:/usr/share:/var/lib/snapd/desktop'
  DetectedPlugins:
   
  EcryptfsInUse: Yes
  Env:
   'None'
   'None'
  InstallationDate: Installed on 2019-01-24 (144 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  InstalledPlugins:
   
  Load-Avg-1min: 3.09
  Load-Processes-Running-Percent:   0.1%
  MachineType: LENOVO 20BXCTO1WW
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-16-generic 
root=UUID=a6081f39-700f-4698-bda4-464e53d9d229 ro quiet splash vt.handoff=1
  SourcePackage: chromium-browser
  UpgradeStatus: Upgraded to disco on 2019-05-29 (19 days ago)
  dmi.bios.date: 09/13/2017
  dmi.bios.vendor: LENOVO
  dmi.bios.version: JBET66WW (1.30 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20BXCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrJBET66WW(1.30):bd09/13/2017:svnLENOVO:pn20BXCTO1WW:pvrThinkPadT450s:rvnLENOVO:rn20BXCTO1WW:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad T450s
  dmi.product.name: 20BXCTO1WW
  dmi.product.sku: LENOVO_MT_20BX_BU_Think_FM_ThinkPad T450s
  dmi.product.version: ThinkPad T450s
  dmi.sys.vendor: LENOVO
  modified.conffile..etc.default.chromium-browser: [deleted]

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

[Desktop-packages] [Bug 1851127] Re: app page shows no install progress

2019-11-05 Thread Alan Pope 🍺🐧🐱 🦄
The output of journalctl -b 0.

Having difficulty reproducing the issue now :(

** Attachment added: "foo.txt"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1851127/+attachment/5303028/+files/foo.txt

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

Title:
  app page shows no install progress

Status in gnome-software package in Ubuntu:
  Incomplete

Bug description:
  I just installed a couple of applications (bomb squad and android
  studio) and while installing, they show no install progress.

  Steps to reproduce

  Launch gnome-software
  Click an application from the front of G-S
  Click Install
  Fill in password

  Expected outcome

  I expect to be shown a progress bar, showing that installation is
  happening

  Actual outcome

  I see no progress, yet running `snap changes` in a terminal shows it is 
installing
  In addition, clicking "Install" again fails due to the install running.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: gnome-software 3.30.6-2ubuntu10
  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.1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Nov  3 11:42:28 2019
  InstallationDate: Installed on 2019-10-27 (6 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  InstalledPlugins:
   gnome-software-plugin-flatpak N/A
   gnome-software-plugin-snap3.30.6-2ubuntu10
  SourcePackage: gnome-software
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1849257] Re: Firefox audio not playing via bluetooth

2019-11-05 Thread aveem ashfaq
An update to system solved the problem. Don't know which package. You
can close it now.

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

Title:
  Firefox audio not playing via bluetooth

Status in firefox package in Ubuntu:
  New

Bug description:
  When I am playing videos in Youtube, it plays through my laptop
  speakers instead of through the connected bluetooth device. I tried
  that with my USB headset but still audio plays out through my laptop
  speakers. Same for Prime Video. It works fine in Google chrome i.e.
  audio is re-routed through bluetooth speakers.

  I tried switching audio devices and still nothing changes.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: firefox 69.0.3+build1-0ubuntu1
  ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1
  Uname: Linux 5.3.0-18-generic x86_64
  AddonCompatCheckDisabled: False
  ApportVersion: 2.20.11-0ubuntu8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ashfaq 1386 F pulseaudio
   /dev/snd/pcmC0D0c:   ashfaq 1386 F...m pulseaudio
   /dev/snd/pcmC0D0p:   ashfaq 1386 F...m pulseaudio
  BuildID: 20191010103742
  Channel: Unavailable
  Date: Tue Oct 22 10:58:03 2019
  ForcedLayersAccel: False
  InstallationDate: Installed on 2019-10-18 (3 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  IpRoute:
   default via 192.168.1.1 dev wlp1s0 proto dhcp metric 600 
   169.254.0.0/16 dev wlp1s0 scope link metric 1000 
   192.168.1.0/24 dev wlp1s0 proto kernel scope link src 192.168.1.57 metric 600
  NoProfiles: True
  ProcEnviron:
   LANGUAGE=en_IN:en
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_IN
   SHELL=/bin/bash
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RunningIncompatibleAddons: False
  SourcePackage: firefox
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/28/2017
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V1.08
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: Suntory_KL
  dmi.board.vendor: KBL
  dmi.board.version: V1.08
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.08:bd11/28/2017:svnAcer:pnSwiftSF314-52:pvrV1.08:rvnKBL:rnSuntory_KL:rvrV1.08:cvnAcer:ct10:cvrChassisVersion:
  dmi.product.family: Swift 3
  dmi.product.name: Swift SF314-52
  dmi.product.sku: 
  dmi.product.version: V1.08
  dmi.sys.vendor: Acer

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

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


[Desktop-packages] [Bug 1850535] Re: Ubuntu 19.10 gnome-shell crashes after changing keyboard

2019-11-05 Thread Sebastien Bacher
** No longer affects: mutter (Ubuntu Eoan)

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

Title:
  Ubuntu 19.10 gnome-shell crashes after changing keyboard

Status in Mutter:
  Fix Released
Status in mutter package in Ubuntu:
  Fix Released
Status in mutter source package in Focal:
  Fix Released

Bug description:
  Updated to Ubuntu 19.10 Eoan, changing keyboard (from zh-cn to es-es)
  crashes gnome-shell, and displays that logoff is needed, but clicking
  logoff button is useless (won't work). Reboot, log in, and a black
  screen with movable cursur will be displayed. After some time, the
  crash screen will again be displayed.

  Checked journalctl /usr/bin/gnome-shell, a lot of "gnome-shell[1907]:
  _clutter_stage_queue_event: assertion 'CLUTTER_IS_STAGE (stage)'
  failed" was found.

  Use tty3 to login and deleting ~/.config/dconf/user would help logging
  in to desktop environment (gnome won't display dock, and have no
  settings of dock for some reason though), but changing keyboard still
  crashes gnome as before.

  I tried adding disco and focal apt source into sources.list, and use
  aptitude to upgrade, or downgrade gnome to other versions. Things
  won't work either (can't even login).

  After some googling, I found a possibly related PR:
  https://gitlab.gnome.org/GNOME/mutter/merge_requests/764, but this
  commit is on 3.35.1, not 3.34.

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

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


[Desktop-packages] [Bug 1816396] Re: Starting snap from the after-install notification fails

2019-11-05 Thread Sebastien Bacher
** Changed in: gnome-software (Ubuntu Eoan)
 Assignee: (unassigned) => Robert Ancell (robert-ancell)

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

Title:
  Starting snap from the after-install notification fails

Status in gnome-software package in Ubuntu:
  Fix Released
Status in gnome-software source package in Bionic:
  Triaged
Status in gnome-software source package in Cosmic:
  Won't Fix
Status in gnome-software source package in Disco:
  Won't Fix
Status in gnome-software source package in Eoan:
  Triaged

Bug description:
  [Impact]
  The launch button on the notification shown after snaps are installed doesn't 
 work.

  [Test Case]
  1. Open GNOME Software
  2. Select a snap that is not installed
  3. Install that snap
  4. Switch focus to another application (i.e. so GNOME Software doesn't have 
focus)

  Expected result:
  A notification is shown saying the app is installed with a button that 
launches it.

  Observed result:
  A notification is shown but the launch button give an error like "no such 
desktop file: io.snapcraft.vlc-"

  [Regression Potential]
  TBD

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

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


[Desktop-packages] [Bug 1851385] [NEW] ubuntu 19.10 / print bug : requires authentication

2019-11-05 Thread Cdag
Public bug reported:

Hello,

I have 2 computers(one laptop and one desktop) which have a dual boot
Windows / Ubuntu. My printer (Xerox WorkCentre 6015B) is plugged on a
USB port from my modem on which my computers are connected using Wi-Fi.

Since the upgrade of Ubuntu to version 19.10, I cannot print. On both
computers I get the same message : [The printer] requires authentication
/ credentials required in order to print.

With Ubuntu 19.04, I had absolutely no problem. I tried with a live USB
with Ubuntu 19.04, there is no problem, the printer works. With a Ubuntu
live 19.10, it doesn't work.

If I plug the printer directly on a USB port on my computer, I get the
same error message : [The printer] requires authentication / credentials
required in order to print.

It's the same behaviour on both computers, no I guess it must be a bug.
Anyway I don't know which authentication I could do, with which ID and
password ?

Thank you very much

ProblemType: Bug
DistroRelease: Ubuntu 19.10
Package: cups 2.2.12-2ubuntu1
ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1
Uname: Linux 5.3.0-18-generic x86_64
ApportVersion: 2.20.11-0ubuntu8.2
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Tue Nov  5 15:12:07 2019
Lpstat: device for Xerox_WorkCentre_6015B_Wi-Fi: 
smb://FREEBOX_SERVER/Xerox%20WorkCentre%206015B
MachineType: Acer Aspire V5-571
Papersize: a4
PpdFiles: Error: command ['fgrep', '-H', '*NickName', 
'/etc/cups/ppd/Xerox_WorkCentre_6015B_Wi-Fi.ppd'] failed with exit code 2: 
grep: /etc/cups/ppd/Xerox_WorkCentre_6015B_Wi-Fi.ppd: Permission denied
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-18-generic 
root=UUID=fb8ccf3e-9970-4066-bae2-26fe4387c122 ro quiet splash vt.handoff=7
SourcePackage: cups
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 12/21/2012
dmi.bios.vendor: Phoenix Technologies Ltd.
dmi.bios.version: V2.15
dmi.board.asset.tag: No Asset Tag
dmi.board.name: Aspire V5-571
dmi.board.vendor: Acer
dmi.board.version: V2.15
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 9
dmi.chassis.vendor: Acer
dmi.chassis.version: V2.15
dmi.modalias: 
dmi:bvnPhoenixTechnologiesLtd.:bvrV2.15:bd12/21/2012:svnAcer:pnAspireV5-571:pvrV2.15:rvnAcer:rnAspireV5-571:rvrV2.15:cvnAcer:ct9:cvrV2.15:
dmi.product.family: Aspire V5-571
dmi.product.name: Aspire V5-571
dmi.product.sku: Aspire V5-571_072A_2.15
dmi.product.version: V2.15
dmi.sys.vendor: Acer

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

Title:
  ubuntu 19.10 / print bug : requires authentication

Status in cups package in Ubuntu:
  New

Bug description:
  Hello,

  I have 2 computers(one laptop and one desktop) which have a dual boot
  Windows / Ubuntu. My printer (Xerox WorkCentre 6015B) is plugged on a
  USB port from my modem on which my computers are connected using Wi-
  Fi.

  Since the upgrade of Ubuntu to version 19.10, I cannot print. On both
  computers I get the same message : [The printer] requires
  authentication / credentials required in order to print.

  With Ubuntu 19.04, I had absolutely no problem. I tried with a live
  USB with Ubuntu 19.04, there is no problem, the printer works. With a
  Ubuntu live 19.10, it doesn't work.

  If I plug the printer directly on a USB port on my computer, I get the
  same error message : [The printer] requires authentication /
  credentials required in order to print.

  It's the same behaviour on both computers, no I guess it must be a
  bug. Anyway I don't know which authentication I could do, with which
  ID and password ?

  Thank you very much

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: cups 2.2.12-2ubuntu1
  ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1
  Uname: Linux 5.3.0-18-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Nov  5 15:12:07 2019
  Lpstat: device for Xerox_WorkCentre_6015B_Wi-Fi: 
smb://FREEBOX_SERVER/Xerox%20WorkCentre%206015B
  MachineType: Acer Aspire V5-571
  Papersize: a4
  PpdFiles: Error: command ['fgrep', '-H', '*NickName', 
'/etc/cups/ppd/Xerox_WorkCentre_6015B_Wi-Fi.ppd'] failed with exit code 2: 
grep: /etc/cups/ppd/Xerox_WorkCentre_6015B_Wi-Fi.ppd: Permission denied
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-18-generic 
root=UUID=fb8ccf3e-9970-4066-bae2-26fe4387c122 ro quiet splash vt.handoff=7
  SourcePackage: cups
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/21/2012
  dmi.bios.vendor: Phoenix Technologies Ltd.
  dmi.bios.version: V2.15
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: Aspire V5-571
  dmi.board.vendor: Acer
  dmi.board.version: V2.15
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: Acer
  dmi.chassis.version: V2.1

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

2019-11-05 Thread Sebastien Bacher
setting to incomplete until we get testing feedback from the ppa pointed
out in comment #23

** Changed in: gdm3 (Ubuntu)
   Status: Confirmed => Incomplete

** Changed in: gdm3 (Ubuntu Eoan)
   Status: Confirmed => Incomplete

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

** Changed in: gnome-session (Ubuntu Eoan)
   Status: Confirmed => Incomplete

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

** Changed in: gnome-shell (Ubuntu Eoan)
   Status: Confirmed => Incomplete

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

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

Status in gdm3 package in Ubuntu:
  Incomplete
Status in gnome-session package in Ubuntu:
  Incomplete
Status in gnome-shell package in Ubuntu:
  Incomplete
Status in gdm3 source package in Eoan:
  Incomplete
Status in gnome-session source package in Eoan:
  Incomplete
Status in gnome-shell source package in Eoan:
  Incomplete

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

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

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

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: xorg 1:7.7+19ubuntu12
  ProcVersionSignature: Ubuntu 5.3.0-13.14-generic 5.3.0
  Uname: Linux 5.3.0-13-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.suspend: suspend hibernate resume
  .proc.driver.nvidia.suspend_depth: default modeset uvm
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  435.21  Sun Aug 25 08:17:57 
CDT 2019
   GCC version:  gcc version 9.2.1 20190909 (Ubuntu 9.2.1-8ubuntu1)
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Sep 28 19:55:42 2019
  DistUpgraded: 2019-09-28 18:35:15,142 INFO cache.commit()
  DistroCodename: eoan
  DistroVariant: ubuntu
  DkmsStatus: nvidia, 435.21, 5.3.0-13-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   NVIDIA Corporation GP102 [GeForce GTX 1080 Ti] [10de:1b06] (rev a1) (prog-if 
00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. GP102 [GeForce GTX 1080 Ti] [1043:85e4]
  InstallationDate: Installed on 2019-09-14 (13 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  MachineType: MSI MS-7A67
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-13-generic 
root=UUID=04974c80-e732-49b6-8148-c3dce7c02a25 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg crash
  UpgradeStatus: Upgraded to eoan on 2019-09-28 (0 days ago)
  dmi.bios.date: 01/25/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2.60
  dmi.board.asset.tag: Default string
  dmi.board.name: H270I GAMING PRO AC (MS-7A67)
  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.:bvr2.60:bd01/25/2018:svnMSI:pnMS-7A67:pvr1.0:rvnMSI:rnH270IGAMINGPROAC(MS-7A67):rvr1.0:cvnMSI:ct3:cvr1.0:
  dmi.product.family: Default string
  dmi.product.name: MS-7A67
  dmi.product.sku: Default string
  dmi.product.version: 1.0
  dmi.sys.vendor: MSI
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.99-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.1.6-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20190820-0ubuntu3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1
  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/gdm3/+bug/1845801/+

[Desktop-packages] [Bug 1794064] Re: Clicking a hyperlink in a PDF fails to open it if the default browser is a snap

2019-11-05 Thread Jamie Strandboge
** Changed in: evince (Ubuntu)
   Status: Confirmed => Triaged

** Changed in: evince (Ubuntu)
 Assignee: (unassigned) => Jamie Strandboge (jdstrand)

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

Title:
  Clicking a hyperlink in a PDF fails to open it if the default browser
  is a snap

Status in evince package in Ubuntu:
  Triaged

Bug description:
  This is related to bug #1792648. After fixing that one (see discussion
  at https://salsa.debian.org/gnome-team/evince/merge_requests/1),
  clicking a hyperlink in a PDF opens it correctly if the default
  browser is a well-known application (such as /usr/bin/firefox), but it
  fails to do so if the default browser is a snap (e.g. the chromium
  snap).

  This is not a recent regression, it's not working on bionic either.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: evince 3.30.0-2
  ProcVersionSignature: Ubuntu 4.18.0-7.8-generic 4.18.5
  Uname: Linux 4.18.0-7-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.10-0ubuntu11
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Sep 24 12:28:06 2018
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2016-07-02 (813 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  SourcePackage: evince
  UpgradeStatus: Upgraded to cosmic on 2018-09-14 (9 days ago)
  modified.conffile..etc.apparmor.d.abstractions.evince: [modified]
  mtime.conffile..etc.apparmor.d.abstractions.evince: 2018-09-24T11:35:41.904158

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

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


[Desktop-packages] [Bug 1849886] Re: lightdm does not work on eoan on raspberry pi 4

2019-11-05 Thread Kenneth Zadeck
Last week provided the log file as requested.   is it possible to get
this bug moved off the incomplete list?

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

Title:
  lightdm does not work on eoan on raspberry pi 4

Status in lightdm package in Ubuntu:
  Incomplete

Bug description:
  if you follow the directions on
  https://wiki.ubuntu.com/ARM/RaspberryPi

  sudo apt-get install xubuntu-desktop

  about 20% thru the installation it will ask which window manager you want 
(using dpkg-reconfigure).
  if you select lightdm, you will only get a blank greeter screen after you 
reboot.

  using sudo dpkg-reconfigure gdm3

  resets this to gdm3 and after a reboot, everything is fine.

  this was done on a clean armhf eoan install on a 4gb raspberry pi 4B.

  I have done the install several times.   This bug is repeatable.

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

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


[Desktop-packages] [Bug 1849072] Re: [snap] no access to softlinked folders in home directory

2019-11-05 Thread Olivier Tilloy
That might be doable. Can you share a screenshot of the error page you
see with the setup you described?

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

Title:
  [snap] no access to softlinked folders in home directory

Status in chromium-browser package in Ubuntu:
  New

Bug description:
  How my home filesystem works
  -> ~/Downloads is soft linked to a large non-ssd drive zfs mounted as 
/zfs/Downloads
  (mainly as I download quite a bit of crap, and it would fill up the ssd 
eventually.)

  now chromium can't see this, either to view files, or save/open files.

  chromium is my primary browser - regular updates etc.. on ubuntu, no
  google magic in it.

  I'm not sure if this is fixable with the snap transition?

  But it is a bit of a gotcha for users.

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

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


[Desktop-packages] [Bug 1848658] Re: package chromium-browser 77.0.3865.120-0ubuntu1~snap1 failed to install/upgrade: "error: too early for operation, device not yet seeded or device model not acknowl

2019-11-05 Thread Olivier Tilloy
Ian, it looks like the error was transient, so unfortunately I doubt we'll find 
out.
Could it be that the store was unreachable during a short window of time, at 
the very moment Luis attempted to install chromium?

Luis, can you share the output of "snap changes" and "snap known
serial", as requested by Ian?

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

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

Title:
  package chromium-browser 77.0.3865.120-0ubuntu1~snap1 failed to
  install/upgrade: "error: too early for operation, device not yet
  seeded or device model not acknowledged"

Status in chromium-browser package in Ubuntu:
  Invalid
Status in snapd package in Ubuntu:
  Incomplete

Bug description:
  Packet crash apt install chromium-browser

  ProblemType: Package
  DistroRelease: Ubuntu 19.10
  Package: chromium-browser 77.0.3865.120-0ubuntu1~snap1
  ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1
  Uname: Linux 5.3.0-18-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu8
  AptOrdering:
   chromium-browser:amd64: Install
   NULL: ConfigurePending
  Architecture: amd64
  Date: Fri Oct 18 08:58:37 2019
  ErrorMessage: el subproceso nuevo paquete chromium-browser script 
pre-installation devolvió el código de salida de error 10
  InstallationDate: Installed on 2019-10-18 (0 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: N/A
  RelatedPackageVersions:
   dpkg 1.19.7ubuntu2
   apt  1.9.4
  Snap.ChromeDriverVersion: ChromeDriver 77.0.3865.90 
(58c425ba843df2918d9d4b409331972646c393dd-refs/branch-heads/3865@{#830})
  Snap.ChromiumVersion:
   mkdir: cannot create directory '/run/user/0': Permission denied
   Chromium 77.0.3865.90 snap
  SourcePackage: chromium-browser
  Title: package chromium-browser 77.0.3865.120-0ubuntu1~snap1 failed to 
install/upgrade: el subproceso nuevo paquete chromium-browser script 
pre-installation devolvió el código de salida de error 10
  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/1848658/+subscriptions

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


[Desktop-packages] [Bug 1848692] Re: Rygel autostarts on Ubuntu 19.10

2019-11-05 Thread Launchpad Bug Tracker
This bug was fixed in the package rygel - 0.38.1-2ubuntu3.2

---
rygel (0.38.1-2ubuntu3.2) eoan; urgency=medium

  * debian/rygel.postinst:
- disable the systemd unit when upgrading from a buggy version as well,
  the --no-enable is just working for new installations (lp: #1848692)

rygel (0.38.1-2ubuntu3.1) eoan; urgency=medium

  * debian/rules:
- use 'dh_installsystemduser --no-enable' to not risk enabling media
  sharing for users who don't expect it. GNOME defaults to disable
  rygel on login but that's not the case of other desktops, since that
  can be a privacy issue it's better to default to a safe behaviour.
  (lp: #1848692)

 -- Sebastien Bacher   Wed, 30 Oct 2019 11:31:07
+0100

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

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

Title:
  Rygel autostarts on Ubuntu 19.10

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

Bug description:
  [ Impact ]
  The user medias can end up being shared without action/notification

  [ Test Case ]
  Log into a non GNOME/Ubuntu session and look at the rygel systemd user job 
status (or available media on the network)

  [ Regression potential ] 
  Installing the rygal package isn't going to lead to the service to be active 
by default, which is a behaviour change and be the opposite of what some users 
would expect

  

  I just received this question on IRC:

  11:16 <~phako> hi
  11:16 < Fabzgy> I ve upgraded to Ubuntu 19.10 yesterday
  11:16 < Fabzgy> now rygel is automatically started when I reboot my
  system
  11:17 < Fabzgy> My colleague at work just informed me that all my
  pictures & videos are available to the entire company

  That would be _REALLY_ bad

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

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


[Desktop-packages] [Bug 1849886] Re: lightdm does not work on eoan on raspberry pi 4

2019-11-05 Thread Gunnar Hjalmarsson
** Changed in: lightdm (Ubuntu)
   Status: Incomplete => Confirmed

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

Title:
  lightdm does not work on eoan on raspberry pi 4

Status in lightdm package in Ubuntu:
  Confirmed

Bug description:
  if you follow the directions on
  https://wiki.ubuntu.com/ARM/RaspberryPi

  sudo apt-get install xubuntu-desktop

  about 20% thru the installation it will ask which window manager you want 
(using dpkg-reconfigure).
  if you select lightdm, you will only get a blank greeter screen after you 
reboot.

  using sudo dpkg-reconfigure gdm3

  resets this to gdm3 and after a reboot, everything is fine.

  this was done on a clean armhf eoan install on a 4gb raspberry pi 4B.

  I have done the install several times.   This bug is repeatable.

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

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


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

2019-11-05 Thread Olivier Tilloy
Here is the corresponding console output when running thunderbird with
the corrupted message db:

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

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

Title:
  Thunderbird empty after update to 19.10 - corrupted global-messages-
  db.sqlite

Status in thunderbird package in Ubuntu:
  Confirmed

Bug description:
  HELP

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

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

  If I launch TB form terminal I get this:

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

  What can I do ?

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

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

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


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

2019-11-05 Thread Olivier Tilloy
I can reproduce the problem with the corrupted global-messages-db.sqlite.
When using that file, the thunderbird main UI is mostly empty, the burger menu 
doesn't open, and opening application preferences or account settings from a 
"compose new message" window doesn't work either.

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

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

Title:
  Thunderbird empty after update to 19.10 - corrupted global-messages-
  db.sqlite

Status in thunderbird package in Ubuntu:
  Confirmed

Bug description:
  HELP

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

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

  If I launch TB form terminal I get this:

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

  What can I do ?

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

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

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


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

2019-11-05 Thread Olivier Tilloy
Googling reveals that some ArchLinux users apparently experience(d) the
same problem, as this pastebin reveals (https://pastebin.com/R2GESJqV):

  « If  you experience the following output when starting Thunderbird 68 on 
Linux, the solution is to delete the file global-messages-db.sqlite in your 
profile directory.
 
Example output from an effected system running ArchLinux:

  [following is a console output similar to that in the previous
comment] »

I can't find any reference to similar errors upstream, so I assume this
is random database corruption. Not quite a satisfactory conclusion,
let's just keep the bug open for now.

** Summary changed:

- Thunderbird empty after update to 19.10
+ Thunderbird empty after update to 19.10 - corrupted global-messages-db.sqlite

** Changed in: thunderbird (Ubuntu)
   Importance: Undecided => Low

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

Title:
  Thunderbird empty after update to 19.10 - corrupted global-messages-
  db.sqlite

Status in thunderbird package in Ubuntu:
  Confirmed

Bug description:
  HELP

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

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

  If I launch TB form terminal I get this:

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

  What can I do ?

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

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

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


[Desktop-packages] [Bug 1849729] Re: chromium-browser fails to start after upgrade to eoan

2019-11-05 Thread Olivier Tilloy
*** This bug is a duplicate of bug 1849371 ***
https://bugs.launchpad.net/bugs/1849371

In eoan chromium-browser is a transitional package that installs the
chromium snap.

You hit an unsupported home directory setup, apparently: snapd assumes a
home directory mounted under /home.

This is similar to bug #1849371, even though the error message is
slightly different, and it fails at a different stage. I'll mark it a
duplicate bug.

Quoting Zygmunt: « The limitation on HOME is well known and for now has
no workaround other than to bind mount whatever custom home directory to
/home/$LOGNAME. »

** This bug has been marked a duplicate of bug 1849371
   [snap] Cannot run chromium as user www-data because home directory is 
/var/www

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

Title:
  chromium-browser fails to start after upgrade to eoan

Status in chromium-browser package in Ubuntu:
  New

Bug description:
  did a distro upgrade to eoan through upon request of popup app in
  ubuntu today

  restarted the system

  tried starting chromium-browser from the "Run Application" (Alt-F2)

  Chromium should have started, nothing happened.

  Tried again from a shell:

  $ chromium-browser 
  2019/10/24 22:07:56.441694 cmd_run.go:529: WARNING: XAUTHORITY environment 
value is not a clean path: "/misc/home//.Xauthority"
  cannot perform operation: mount --rbind /home /tmp/snap.rootfs_gRwtXn//home: 
Permission denied

  apt-get --purge remove chromium-browser
  apt-get install chromium-browser

  exits successfully, after exclaiming some stuff about some snap, but
  leaves me with

  $ chromium-browser 
  2019/10/24 22:14:53.150401 cmd_run.go:529: WARNING: XAUTHORITY environment 
value is not a clean path: "/misc/home//.Xauthority"
  cannot perform operation: mount --rbind /home /tmp/snap.rootfs_rkOYc1//home: 
Permission denied

  
  Either the upgrade to eoan left my system broken, or chromium-browser is 
broken.


  
  lsb_release -rd
  Description:  Ubuntu 19.10
  Release:  19.10

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

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: chromium-browser 77.0.3865.120-0ubuntu1~snap1
  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
  Architecture: amd64
  CurrentDesktop: MATE
  Date: Thu Oct 24 22:08:43 2019
  InstallationDate: Installed on 2019-04-10 (197 days ago)
  InstallationMedia: Ubuntu-MATE 19.04 "Disco Dingo" - Alpha amd64 (20190326.1)
  Snap.ChromeDriverVersion:
   Error: command ['snap', 'run', 'chromium.chromedriver', '--version'] failed 
with exit code 1: 2019/10/24 22:08:56.371246 cmd_run.go:529: WARNING: 
XAUTHORITY environment value is not a clean path: 
"/misc/home/thorsten/.Xauthority"
   cannot perform operation: mount --rbind /home /tmp/snap.rootfs_6BAwdi//home: 
Permission denied
  Snap.ChromiumVersion:
   Error: command ['snap', 'run', 'chromium', '--version'] failed with exit 
code 1: 2019/10/24 22:08:56.217828 cmd_run.go:529: WARNING: XAUTHORITY 
environment value is not a clean path: "/misc/home/thorsten/.Xauthority"
   cannot perform operation: mount --rbind /home /tmp/snap.rootfs_tHjxkD//home: 
Permission denied
  SourcePackage: chromium-browser
  UpgradeStatus: Upgraded to eoan on 2019-10-24 (0 days ago)

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

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


[Desktop-packages] [Bug 1754671] Re: Full-tunnel VPN DNS leakage regression

2019-11-05 Thread Joe Hohertz
1.10.6-2ubuntu1.2 has cause a regression in functionality.

Anyone using a "split" VPN, where there is no default route, AND wish to
have DNS services supplied by the server to be honoured, via use of the
ipv4.dns-priority parameter, will have this broken. This is a bit of a
sore point considering the hoops one has to jump through to make this
work at all.

Reverting to previous version restores functionality.

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

Title:
  Full-tunnel VPN DNS leakage regression

Status in NetworkManager:
  Confirmed
Status in network-manager package in Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  Fix Released
Status in network-manager source package in Xenial:
  Confirmed
Status in systemd source package in Xenial:
  Invalid
Status in network-manager source package in Bionic:
  Fix Released
Status in systemd source package in Bionic:
  Fix Released
Status in network-manager source package in Cosmic:
  Fix Released
Status in systemd source package in Cosmic:
  Fix Released

Bug description:
  [Impact]
  When using a VPN the DNS requests might still be sent to a DNS server outside 
the VPN when they should not

  [Test case]
  1) Set up a VPN with split tunneling:
a) Configure VPN normally (set up remote host, any ports and options needed 
for the VPN to work)
b) Under the IPv4 tab: enable "Use this connection only for the resources 
on its network".
c) Under the IPv6 tab: enable "Use this connection only for the resources 
on its network".

  2) Connect to the VPN.

  3) Run 'systemd-resolve --status'; note the DNS servers configured:
a) For the VPN; under a separate link (probably tun0), note down the IP of 
the DNS server(s). Also note the name of the interface (link).
b) For the "main" connection; under the link for your ethernet or wireless 
devices (wl*, en*, whatever it may be), note down the IP of the DNS server(s). 
Also note the name of the interface (link).

  4) In a separate terminal, run 'sudo tcpdump -ni 
  port 53'; let it run.

  5) In a separate terminal, run 'sudo tcpdump -ni 
  port 53'; let it run.

  6) In yet another terminal, issue name resolution requests using dig:
a) For a name known to be reachable via the public network:
   'dig www.yahoo.com'
b) For a name known to be reachable only via the VPN:
   'dig '

  7) Check the output of each terminal running tcpdump. When requesting
  the public name, traffic can go through either. When requesting the
  "private" name (behind the VPN), traffic should only be going through
  the interface for the VPN. Additionally, ensure the IP receiving the
  requests for the VPN name is indeed the IP address noted above for the
  VPN's DNS server.

  If you see no traffic showing in tcpdump output when requesting a
  name, it may be because it is cached by systemd-resolved. Use a
  different name you have not tried before.

  
  [Regression potential]
  The code change the handling of DNS servers when using a VPN, we should check 
that name resolution still work whne using a VPN in different configurations

  -

  In 16.04 the NetworkManager package used to carry this patch:
  
http://bazaar.launchpad.net/~network-manager/network-manager/ubuntu/view/head:/debian/patches/Filter-DNS-servers-to-add-to-dnsmasq-based-on-availa.patch

  It fixed the DNS setup so that when I'm on the VPN, I am not sending
  unencrypted DNS queries to the (potentially hostile) local
  nameservers.

  This patch disappeared in an update. I think it was present in
  1.2.2-0ubuntu0.16.04.4 but was dropped some time later.

  This security bug exists upstream too: 
https://bugzilla.gnome.org/show_bug.cgi?id=746422
  It's not a *regression* there though, as they didn't fix it yet 
(unfortunately!)

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

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


[Desktop-packages] [Bug 1849346] Re: [snap] kerberos GSSAPI no longer works after deb->snap transition

2019-11-05 Thread Olivier Tilloy
Thanks for the report.
Can you check for apparmor denials in the system journal when reproducing the 
problem? Run the following command in a terminal before launching chromium:

journalctl -f | grep DEN

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

Title:
  [snap] kerberos GSSAPI no longer works after deb->snap transition

Status in chromium-browser package in Ubuntu:
  Confirmed

Bug description:
  I configure AuthServerWhitelist as documented:

  https://www.chromium.org/developers/design-documents/http-
  authentication

  and can see my whitelisted domains in chrome://policy/

  but websites that used to work with SPNEGO/GSSAPI/kerberos no longer
  work. I'm guessing the snap needs some sort of permission to use the
  kerberos ticket cache (or the plumbing to do so doesn't exist...).

  I can confirm that Chrome has the desired behavior.

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

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


[Desktop-packages] [Bug 1648846] Re: Chromium ignores no_proxy environment variable

2019-11-05 Thread Olivier Tilloy
Yuriy, could you please test whether google chrome, as distributed by Google, 
is also affected?
If so, can you file a bug report at 
https://bugs.chromium.org/p/chromium/issues/list?

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

Title:
  Chromium ignores no_proxy environment variable

Status in chromium-browser package in Ubuntu:
  Invalid

Bug description:
  I need the proxy to be bypassed for a number of sites. These sites are
  listed in the no_proxy environment variable. However, this is ignored
  by Chromium. There does not appear to be any way in Chromium (nor in
  the system proxy settings) to specify sites for which the proxy should
  be bypassed.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: chromium-browser 53.0.2785.143-0ubuntu0.16.04.1.1257
  ProcVersionSignature: Ubuntu 4.4.0-53.74-generic 4.4.30
  Uname: Linux 4.4.0-53-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.2
  Architecture: amd64
  CurrentDesktop: GNOME-Flashback:Unity
  DRM.card0-DP-1:
   edid-base64: 
   dpms: Off
   modes: 
   enabled: disabled
   status: disconnected
  DRM.card0-HDMI-A-1:
   edid-base64: 
   dpms: Off
   modes: 
   enabled: disabled
   status: disconnected
  DRM.card0-LVDS-1:
   edid-base64: 
AP///wAGr54TAAETAQOAJhV4CsSVnldTkiYPUFQBAQEBAQEBAQEBAQEBAQEBHCpAbmGEDDAwIDYAftYQAAAYDwAg/gBBVU8KICAgICAgICAg/gBCMTczUlcwMSBWMyAKACQ=
   dpms: On
   modes: 1600x900
   enabled: enabled
   status: connected
  DRM.card0-VGA-1:
   edid-base64: 
   dpms: Off
   modes: 
   enabled: disabled
   status: disconnected
  Date: Fri Dec  9 17:23:04 2016
  Desktop-Session:
   'gnome-flashback-compiz'
   '/etc/xdg/xdg-gnome-flashback-compiz:/usr/share/upstart/xdg:/etc/xdg'
   
'/usr/share/gnome-flashback-compiz:/usr/local/share/:/usr/share/:/var/lib/snapd/desktop'
  DetectedPlugins:
   
  Env:
   'None'
   'None'
  InstallationDate: Installed on 2014-12-07 (732 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  Load-Avg-1min: 1.11
  Load-Processes-Running-Percent:   0.1%
  MachineType: Hewlett-Packard HP Pavilion dv7 Notebook PC
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-53-generic 
root=UUID=9a82200b-b3aa-44b6-b217-8db2a403850f ro ipv6.disable=1 quiet splash 
vt.handoff=7
  SourcePackage: chromium-browser
  UpgradeStatus: Upgraded to xenial on 2016-04-24 (229 days ago)
  dmi.bios.date: 05/21/2012
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: F.19
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 1803
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 10.59
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrF.19:bd05/21/2012:svnHewlett-Packard:pnHPPaviliondv7NotebookPC:pvr06902120471620100:rvnHewlett-Packard:rn1803:rvr10.59:cvnHewlett-Packard:ct10:cvrChassisVersion:
  dmi.product.name: HP Pavilion dv7 Notebook PC
  dmi.product.version: 06902120471620100
  dmi.sys.vendor: Hewlett-Packard
  etcconfigcpepperflashpluginnonfree:
   flashso="/usr/lib/pepperflashplugin-nonfree/libpepflashplayer.so"
   flashversion=`strings $flashso 2> /dev/null | grep LNX | cut -d ' ' -f 2 | 
sed -e "s/,/./g"`
   CHROMIUM_FLAGS="$CHROMIUM_FLAGS --ppapi-flash-path=$flashso 
--ppapi-flash-version=$flashversion"
  gconf-keys: /desktop/gnome/applications/browser/exec = 
b'firefox\n'/desktop/gnome/url-handlers/https/command = b'sensible-browser 
%s\n'/desktop/gnome/url-handlers/https/enabled = 
b'true\n'/desktop/gnome/url-handlers/http/command = b'sensible-browser 
%s\n'/desktop/gnome/url-handlers/http/enabled = 
b'true\n'/desktop/gnome/session/required_components/windowmanager = 
b''/apps/metacity/general/compositing_manager = 
b''/desktop/gnome/interface/icon_theme = 
b'gnome\n'/desktop/gnome/interface/gtk_theme = b'Clearlooks\n'
  modified.conffile..etc.default.chromium-browser: [deleted]
  mtime.conffile..etc.chromium-browser.default: 2016-04-24T14:29:37.993623

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

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


[Desktop-packages] [Bug 1847069] Re: [snap] Chromium snap starts slowly

2019-11-05 Thread Olivier Tilloy
Lorenz, would you mind sharing your insights on squashfs with LZMA
performance on the snapcraft forums (https://forum.snapcraft.io/) ?

I'm sure the snapd team would be interested in looking at potential
performance improvements.

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

Title:
  [snap] Chromium snap starts slowly

Status in chromium-browser package in Ubuntu:
  Confirmed

Bug description:
  The problem is shown here, https://discourse.ubuntu.com/t/call-for-
  testing-chromium-browser-deb-to-snap-transition/11179/141 more
  graphically.

  Chromium snap takes quite a while to start and doesn't carry the
  system theme, whereas the chromium-browser folder taken off the
  snap/chromium starts practically immediately.

  The libcanberra-gtk3-module is missing inside the snap, and cannot use
  the module in the system.

  The Chromium snap is 607.3 MB, while the standalone Chromium is 237.2
  MB, taken off the snap.

  Conclusion on Chromium snap on Ubuntu Eoan;
  Two bugs and a missing module
  1) Starts slowly,
  2) Cannot carry the system theme,
  3) Doesn't have libcanberra-gtk3-module

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

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


[Desktop-packages] [Bug 1851407] [NEW] NetworkManager 1.10.6-2ubuntu1.2 breaks VPN DNS

2019-11-05 Thread Joe Hohertz
Public bug reported:

NetworkManager as of 1.10.6-2ubuntu1.2 has cause a regression whereby a
VPN connection which sets it's dns-priority to a negative value, which
should cause the DNS server supplied by the DNS connection to be placed
first, instead now refuses to place the DNS server into the resolver
under any circumstance.

Pinning the 1.10.6-2ubuntu1.1 works around the issue.

I suspect the fix-dns-leak-lp1754671.patch has caused this regression.

This patch should be reverted as soon as possible to restore proper
functionality of network manager with respect to VPN servers with DNS
resolvers.

$ lsb_release -rd
Description:Ubuntu 18.04.3 LTS
Release:18.04

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

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

Title:
  NetworkManager 1.10.6-2ubuntu1.2 breaks VPN DNS

Status in network-manager package in Ubuntu:
  New

Bug description:
  NetworkManager as of 1.10.6-2ubuntu1.2 has cause a regression whereby
  a VPN connection which sets it's dns-priority to a negative value,
  which should cause the DNS server supplied by the DNS connection to be
  placed first, instead now refuses to place the DNS server into the
  resolver under any circumstance.

  Pinning the 1.10.6-2ubuntu1.1 works around the issue.

  I suspect the fix-dns-leak-lp1754671.patch has caused this regression.

  This patch should be reverted as soon as possible to restore proper
  functionality of network manager with respect to VPN servers with DNS
  resolvers.

  $ lsb_release -rd
  Description:  Ubuntu 18.04.3 LTS
  Release:  18.04

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

-- 
Mailing list: https://launchpad.net/~desktop-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-05 Thread corrado venturini
The same problem with live session from a recent ISO:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1851058

-- 
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:
  New
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

[Desktop-packages] [Bug 1851058] Re: Live session any mouse or keyboard command is ignored

2019-11-05 Thread corrado venturini
This seems the same problem of 
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1850969
no problem starting apps from the icons on the dock but immediate hang clicking 
an icon on the desktop.
I still see the problem with the ISO: Ubuntu 20.04 LTS "Focal Fossa" - Alpha 
amd64 (20191105)

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

Title:
  Live session any mouse or keyboard command is ignored

Status in xorg package in Ubuntu:
  New

Bug description:
  The problem happens in the live session. Ubiquity starts ok, The default 
desktop is displayed, but any mouse or keyboard command is ignored. If instead 
of "Try Ubuntu" I select "install Ubuntu" the install runs fine but the new 
installed system has the problem described in bug #1850969.
  Same problem with ISO Alpha amd64 (20191101), 20191102, 20191030 and 20191031
  also on a different hardware (HP laptop) and also selecting 'graphic failsafe'
  Now I'm working with Wayland session because X11 does not work.

  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: Sat Nov  2 17:36:01 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 Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.
  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.1.0-1
  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/1851058/+subscriptions

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


[Desktop-packages] [Bug 1851407] Re: NetworkManager 1.10.6-2ubuntu1.2 breaks VPN DNS

2019-11-05 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

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

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

Title:
  NetworkManager 1.10.6-2ubuntu1.2 breaks VPN DNS

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  NetworkManager as of 1.10.6-2ubuntu1.2 has cause a regression whereby
  a VPN connection which sets it's dns-priority to a negative value,
  which should cause the DNS server supplied by the DNS connection to be
  placed first, instead now refuses to place the DNS server into the
  resolver under any circumstance.

  Pinning the 1.10.6-2ubuntu1.1 works around the issue.

  I suspect the fix-dns-leak-lp1754671.patch has caused this regression.

  This patch should be reverted as soon as possible to restore proper
  functionality of network manager with respect to VPN servers with DNS
  resolvers.

  $ lsb_release -rd
  Description:  Ubuntu 18.04.3 LTS
  Release:  18.04

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

-- 
Mailing list: https://launchpad.net/~desktop-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-05 Thread Olivier Tilloy
Thanks for the details Rowan. I can see what you mean now, and I can
observe the same problem. This appears to be a regression indeed.

I can observe the problem even in upstream builds of thunderbird. Would
you mind filing a bug at
https://bugzilla.mozilla.org/enter_bug.cgi#h=dupes%7CThunderbird and
sharing a link to it here?

** Changed in: thunderbird (Ubuntu)
   Status: Incomplete => Confirmed

** Changed in: thunderbird (Ubuntu)
   Importance: Undecided => 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 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/ubuntu/+source/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 1848692] Re: Rygel autostarts on Ubuntu 19.10

2019-11-05 Thread Launchpad Bug Tracker
This bug was fixed in the package rygel - 0.38.2-3ubuntu2

---
rygel (0.38.2-3ubuntu2) focal; urgency=medium

  * debian/rygel-2.6-dev.install:
- install the documentation again, it's shipped correctly with the
  new tarball version

 -- Sebastien Bacher   Tue, 05 Nov 2019 17:01:30
+0100

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

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

Title:
  Rygel autostarts on Ubuntu 19.10

Status in rygel package in Ubuntu:
  Fix Released
Status in rygel source package in Eoan:
  Fix Released

Bug description:
  [ Impact ]
  The user medias can end up being shared without action/notification

  [ Test Case ]
  Log into a non GNOME/Ubuntu session and look at the rygel systemd user job 
status (or available media on the network)

  [ Regression potential ] 
  Installing the rygal package isn't going to lead to the service to be active 
by default, which is a behaviour change and be the opposite of what some users 
would expect

  

  I just received this question on IRC:

  11:16 <~phako> hi
  11:16 < Fabzgy> I ve upgraded to Ubuntu 19.10 yesterday
  11:16 < Fabzgy> now rygel is automatically started when I reboot my
  system
  11:17 < Fabzgy> My colleague at work just informed me that all my
  pictures & videos are available to the entire company

  That would be _REALLY_ bad

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

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


[Desktop-packages] [Bug 1845689] Re: Bluetooth loops when pairing Connecting MPOW T5 headset

2019-11-05 Thread Johnny Ooi
Oh, and it pairs okay under Windows on the same laptop (I dual boot
Windows 8 and Ubuntu)

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

Title:
  Bluetooth loops when pairing Connecting MPOW T5 headset

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  I am running ubuntu Disco, recently upgraded from Beaver.

  Now when I pair my MPOW T5 bluetooth earbuds, they will pair, connect,
  then Bluetooth on the machine will restart. This is visible by the
  Bluetooth applet showing Bluetooth being switched off then on again.
  This will happen a few times, then bluetooth will lock up, rendering
  it and the settings applet frozen. Requiring a restart to fix.

  It is like something in Bluetooth subsystem is crashing out when
  pairing with the T5

  I used to use this MPOW T5 with ubuntu Beaver without issue and am
  tempted just to roll back to my image from then But here's hoping
  someone can help identify why this is happening.

  I am also using this on my Disco installation on my Pixelbook (which
  was a clean install, not an upgrade), so maybe that's something worth
  noting.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.0.0-29.31-generic 5.0.21
  Uname: Linux 5.0.0-29-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.10-0ubuntu27.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  johnny 2201 F pulseaudio
   /dev/snd/controlC0:  johnny 2201 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Sep 27 17:34:49 2019
  InstallationDate: Installed on 2018-12-31 (269 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Title: Bluetooth sound card not detected
  UpgradeStatus: Upgraded to disco on 2019-09-21 (6 days ago)
  dmi.bios.date: 04/08/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 4.6.5
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: W35xSS_370SS
  dmi.board.vendor: Notebook
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: Notebook
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd04/08/2014:svnNotebook:pnW35xSS_370SS:pvrNotApplicable:rvnNotebook:rnW35xSS_370SS:rvrNotApplicable:cvnNotebook:ct9:cvrN/A:
  dmi.product.family: Not Applicable
  dmi.product.name: W35xSS_370SS
  dmi.product.sku: Not Applicable
  dmi.product.version: Not Applicable
  dmi.sys.vendor: Notebook

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

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


[Desktop-packages] [Bug 1845689] Re: Bluetooth loops when pairing Connecting MPOW T5 headset

2019-11-05 Thread Johnny Ooi
As an experiment took the 19.04 Ubuntu live disk, booted up from that
and paired mt MPOW T5. Bluetooth crash looped as well. This eliminates
anything I've installed as cause.

I suspect something in the driver is not liking the bluetooth device on
my machine, since it paired with 19.04 on my Pixelbook okay without
crash looping.

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

Title:
  Bluetooth loops when pairing Connecting MPOW T5 headset

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  I am running ubuntu Disco, recently upgraded from Beaver.

  Now when I pair my MPOW T5 bluetooth earbuds, they will pair, connect,
  then Bluetooth on the machine will restart. This is visible by the
  Bluetooth applet showing Bluetooth being switched off then on again.
  This will happen a few times, then bluetooth will lock up, rendering
  it and the settings applet frozen. Requiring a restart to fix.

  It is like something in Bluetooth subsystem is crashing out when
  pairing with the T5

  I used to use this MPOW T5 with ubuntu Beaver without issue and am
  tempted just to roll back to my image from then But here's hoping
  someone can help identify why this is happening.

  I am also using this on my Disco installation on my Pixelbook (which
  was a clean install, not an upgrade), so maybe that's something worth
  noting.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.0.0-29.31-generic 5.0.21
  Uname: Linux 5.0.0-29-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.10-0ubuntu27.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  johnny 2201 F pulseaudio
   /dev/snd/controlC0:  johnny 2201 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Sep 27 17:34:49 2019
  InstallationDate: Installed on 2018-12-31 (269 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Title: Bluetooth sound card not detected
  UpgradeStatus: Upgraded to disco on 2019-09-21 (6 days ago)
  dmi.bios.date: 04/08/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 4.6.5
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: W35xSS_370SS
  dmi.board.vendor: Notebook
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: Notebook
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd04/08/2014:svnNotebook:pnW35xSS_370SS:pvrNotApplicable:rvnNotebook:rnW35xSS_370SS:rvrNotApplicable:cvnNotebook:ct9:cvrN/A:
  dmi.product.family: Not Applicable
  dmi.product.name: W35xSS_370SS
  dmi.product.sku: Not Applicable
  dmi.product.version: Not Applicable
  dmi.sys.vendor: Notebook

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

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


[Desktop-packages] [Bug 1847566] Re: Unlocking the screen is slower the older the session

2019-11-05 Thread John Heidemann
FWIW, this issue was a problem in Fedora as well, through F30.  It seems
fixed in F31, so maybe it's fixed in gnome-3.34?

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

Title:
  Unlocking the screen is slower the older the session

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  Unlocking the screen takes several seconds after a session is a day old. 
Initially it is fast.
  Closing all programs and locking/login doesn't help.
  Logout/login DOES help.
  It feels as if the time is related to the maximum RAM used.

  Output of journalctl -b around the time of login:

  okt 10 07:23:57 proxim dbus-daemon[1205]: [system] Activating via systemd: 
service name='net.reactivated.Fprint' unit='fprintd.service' requested by 
':1.318' (uid=1000 pid=1966 comm="/usr/bin/gnome-shell " label="unconfined")
  okt 10 07:23:57 proxim systemd[1]: Starting Fingerprint Authentication 
Daemon...
  okt 10 07:23:57 proxim dbus-daemon[1205]: [system] Successfully activated 
service 'net.reactivated.Fprint'
  okt 10 07:23:57 proxim systemd[1]: Started Fingerprint Authentication Daemon.
  okt 10 07:24:00 proxim gdm-password][31867]: pam_ecryptfs: 
pam_sm_authenticate: /home/guus is already mounted
  okt 10 07:24:00 proxim gdm-password][31867]: gkr-pam: unlocked login keyring
  okt 10 07:24:01 proxim NetworkManager[1206]:   [1570685041.6037] 
agent-manager: req[0x5627d239e300, :1.318/org.gnome.Shell.NetworkAgent/1000]: 
agent registered
  okt 10 07:24:01 proxim gnome-shell[1966]: [AppIndicatorSupport-DEBUG] 
Registering StatusNotifierItem 
:1.85/org/ayatana/NotificationItem/software_update_available
  okt 10 07:24:02 proxim gnome-shell[1966]: [AppIndicatorSupport-FATAL] unable 
to update overlay icon
  okt 10 07:24:02 proxim gnome-shell[1966]: [AppIndicatorSupport-FATAL] unable 
to update overlay icon
  okt 10 07:24:02 proxim gnome-shell[1966]: Couldn’t parse steam.desktop as a 
desktop file, will treat it as a regular file.
  okt 10 07:24:02 proxim gnome-shell[1966]: Couldn’t parse ns.nl.desktop as a 
desktop file, will treat it as a regular file.
  okt 10 07:24:02 proxim gnome-shell[1966]: Couldn’t parse Overview.desktop as 
a desktop file, will treat it as a regular file.
  okt 10 07:24:04 proxim org.gnome.Shell.desktop[1966]: Window manager warning: 
Overwriting existing binding of keysym 35 with keysym 35 (keycode e).
  okt 10 07:24:04 proxim org.gnome.Shell.desktop[1966]: Window manager warning: 
Overwriting existing binding of keysym 31 with keysym 31 (keycode a).
  okt 10 07:24:04 proxim org.gnome.Shell.desktop[1966]: Window manager warning: 
Overwriting existing binding of keysym 32 with keysym 32 (keycode b).
  okt 10 07:24:04 proxim org.gnome.Shell.desktop[1966]: Window manager warning: 
Overwriting existing binding of keysym 39 with keysym 39 (keycode 12).
  okt 10 07:24:04 proxim org.gnome.Shell.desktop[1966]: Window manager warning: 
Overwriting existing binding of keysym 38 with keysym 38 (keycode 11).
  okt 10 07:24:04 proxim org.gnome.Shell.desktop[1966]: Window manager warning: 
Overwriting existing binding of keysym 33 with keysym 33 (keycode c).
  okt 10 07:24:04 proxim org.gnome.Shell.desktop[1966]: Window manager warning: 
Overwriting existing binding of keysym 34 with keysym 34 (keycode d).
  okt 10 07:24:04 proxim org.gnome.Shell.desktop[1966]: Window manager warning: 
Overwriting existing binding of keysym 36 with keysym 36 (keycode f).
  okt 10 07:24:04 proxim org.gnome.Shell.desktop[1966]: Window manager warning: 
Overwriting existing binding of keysym 37 with keysym 37 (keycode 10).

  cheers, Guus

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: gnome-shell 3.32.2-2ubuntu1~ubuntu19.04.1
  ProcVersionSignature: Ubuntu 5.0.0-31.33-generic 5.0.21
  Uname: Linux 5.0.0-31-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27.1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Oct 10 07:26:36 2019
  DisplayManager: gdm3
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2019-08-18 (52 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  RelatedPackageVersions: mutter-common 3.32.2+git20190711-2ubuntu1~19.04.1
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1851144] Re: Switching from unity-greeter to lightdm-gtk-greeter prevents lightdm.service from starting

2019-11-05 Thread jean-christophe manciot
No such issue with eaon.

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

Title:
  Switching from unity-greeter to lightdm-gtk-greeter prevents
  lightdm.service from starting

Status in lightdm package in Ubuntu:
  New

Bug description:
  Ubuntu 20.04
  lightdm 1.30.0-0ubuntu2
  lightdm-gtk-greeter 2.0.6-0ubuntu1

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: lightdm 1.30.0-0ubuntu2
  ProcVersionSignature: Ubuntu 5.3.0-21.22-generic 5.3.7
  Uname: Linux 5.3.0-21-generic x86_64
  ApportVersion: 2.20.11-0ubuntu9
  Architecture: amd64
  Date: Sun Nov  3 16:15:54 2019
  InstallationDate: Installed on 2015-04-28 (1650 days ago)
  InstallationMedia: Ubuntu-Server 15.04 "Vivid Vervet" - Release amd64 
(20150422)
  SourcePackage: lightdm
  UpgradeStatus: Upgraded to focal on 2019-11-03 (0 days ago)
  modified.conffile..etc.apport.crashdb.conf: [modified]
  mtime.conffile..etc.apport.crashdb.conf: 2018-10-30T10:37:29

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

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


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

2019-11-05 Thread Martin
I just updated to systemd 243 from that place and enabled auto login. It
had no effect; login fails just like with systemd 242.

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

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

Status in gdm3 package in Ubuntu:
  Incomplete
Status in gnome-session package in Ubuntu:
  Incomplete
Status in gnome-shell package in Ubuntu:
  Incomplete
Status in gdm3 source package in Eoan:
  Incomplete
Status in gnome-session source package in Eoan:
  Incomplete
Status in gnome-shell source package in Eoan:
  Incomplete

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

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

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

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: xorg 1:7.7+19ubuntu12
  ProcVersionSignature: Ubuntu 5.3.0-13.14-generic 5.3.0
  Uname: Linux 5.3.0-13-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.suspend: suspend hibernate resume
  .proc.driver.nvidia.suspend_depth: default modeset uvm
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  435.21  Sun Aug 25 08:17:57 
CDT 2019
   GCC version:  gcc version 9.2.1 20190909 (Ubuntu 9.2.1-8ubuntu1)
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Sep 28 19:55:42 2019
  DistUpgraded: 2019-09-28 18:35:15,142 INFO cache.commit()
  DistroCodename: eoan
  DistroVariant: ubuntu
  DkmsStatus: nvidia, 435.21, 5.3.0-13-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   NVIDIA Corporation GP102 [GeForce GTX 1080 Ti] [10de:1b06] (rev a1) (prog-if 
00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. GP102 [GeForce GTX 1080 Ti] [1043:85e4]
  InstallationDate: Installed on 2019-09-14 (13 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  MachineType: MSI MS-7A67
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-13-generic 
root=UUID=04974c80-e732-49b6-8148-c3dce7c02a25 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg crash
  UpgradeStatus: Upgraded to eoan on 2019-09-28 (0 days ago)
  dmi.bios.date: 01/25/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2.60
  dmi.board.asset.tag: Default string
  dmi.board.name: H270I GAMING PRO AC (MS-7A67)
  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.:bvr2.60:bd01/25/2018:svnMSI:pnMS-7A67:pvr1.0:rvnMSI:rnH270IGAMINGPROAC(MS-7A67):rvr1.0:cvnMSI:ct3:cvr1.0:
  dmi.product.family: Default string
  dmi.product.name: MS-7A67
  dmi.product.sku: Default string
  dmi.product.version: 1.0
  dmi.sys.vendor: MSI
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.99-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.1.6-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20190820-0ubuntu3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1
  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/gdm3/+bug/1845801/+subscriptions

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


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

2019-11-05 Thread Martin
Sorry, I wrote that comment from my phone and it changed "PPA" to
"place" without me noticing.

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

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

Status in gdm3 package in Ubuntu:
  Incomplete
Status in gnome-session package in Ubuntu:
  Incomplete
Status in gnome-shell package in Ubuntu:
  Incomplete
Status in gdm3 source package in Eoan:
  Incomplete
Status in gnome-session source package in Eoan:
  Incomplete
Status in gnome-shell source package in Eoan:
  Incomplete

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

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

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

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: xorg 1:7.7+19ubuntu12
  ProcVersionSignature: Ubuntu 5.3.0-13.14-generic 5.3.0
  Uname: Linux 5.3.0-13-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.suspend: suspend hibernate resume
  .proc.driver.nvidia.suspend_depth: default modeset uvm
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  435.21  Sun Aug 25 08:17:57 
CDT 2019
   GCC version:  gcc version 9.2.1 20190909 (Ubuntu 9.2.1-8ubuntu1)
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Sep 28 19:55:42 2019
  DistUpgraded: 2019-09-28 18:35:15,142 INFO cache.commit()
  DistroCodename: eoan
  DistroVariant: ubuntu
  DkmsStatus: nvidia, 435.21, 5.3.0-13-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   NVIDIA Corporation GP102 [GeForce GTX 1080 Ti] [10de:1b06] (rev a1) (prog-if 
00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. GP102 [GeForce GTX 1080 Ti] [1043:85e4]
  InstallationDate: Installed on 2019-09-14 (13 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  MachineType: MSI MS-7A67
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-13-generic 
root=UUID=04974c80-e732-49b6-8148-c3dce7c02a25 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg crash
  UpgradeStatus: Upgraded to eoan on 2019-09-28 (0 days ago)
  dmi.bios.date: 01/25/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2.60
  dmi.board.asset.tag: Default string
  dmi.board.name: H270I GAMING PRO AC (MS-7A67)
  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.:bvr2.60:bd01/25/2018:svnMSI:pnMS-7A67:pvr1.0:rvnMSI:rnH270IGAMINGPROAC(MS-7A67):rvr1.0:cvnMSI:ct3:cvr1.0:
  dmi.product.family: Default string
  dmi.product.name: MS-7A67
  dmi.product.sku: Default string
  dmi.product.version: 1.0
  dmi.sys.vendor: MSI
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.99-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.1.6-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20190820-0ubuntu3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1
  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/gdm3/+bug/1845801/+subscriptions

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


[Desktop-packages] [Bug 1851420] [NEW] Chromium: plasma integration and Whatsapp web broken after 19.10 update

2019-11-05 Thread sbaragnaus
Public bug reported:

Hi, I've just upgraded Kubuntu from 19.04 to 19.10.

Unfortunately I've three problems with Chromium:

1) Plasma integration doesn't work anymore. It says it can't connect to
native host.

2) Whatsapp web doesn't work. It says I need Google Chrome 49+

3) Mouse cursor is different from the one used in Kde

What's wrong?

My user agent is: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36
(KHTML, like Gecko) snap Chromium/78.0.3904.70 Chrome/78.0.3904.70
Safari/537.36

Please note:

a) I've also installed Google Chrome (not Chromium): Plasma interation
and Whatsapp web works well

b) I've removed Chromium browser with Discover, then install it again:
same problems

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


** Tags: plasma 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/1851420

Title:
  Chromium: plasma integration and Whatsapp web broken after 19.10
  update

Status in chromium-browser package in Ubuntu:
  New

Bug description:
  Hi, I've just upgraded Kubuntu from 19.04 to 19.10.

  Unfortunately I've three problems with Chromium:

  1) Plasma integration doesn't work anymore. It says it can't connect
  to native host.

  2) Whatsapp web doesn't work. It says I need Google Chrome 49+

  3) Mouse cursor is different from the one used in Kde

  What's wrong?

  My user agent is: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36
  (KHTML, like Gecko) snap Chromium/78.0.3904.70 Chrome/78.0.3904.70
  Safari/537.36

  Please note:

  a) I've also installed Google Chrome (not Chromium): Plasma interation
  and Whatsapp web works well

  b) I've removed Chromium browser with Discover, then install it again:
  same problems

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

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


[Desktop-packages] [Bug 1850529] Re: Crash after update to 71.0~b5+build1-0ubuntu0.16.04.1

2019-11-05 Thread mark kowski
Yep - fully agree - beta for testing (or for hardcore daily users ;).
Any chances for fix anytime soon anyway?

@j127 - downgrade to latest stable version, find your profile folder 
(about:profiles), open the folder with your new profile and copy/paste proper 
files from old profile (passwords, database, cookies, history, bookmarks): 
https://support.mozilla.org/en-US/kb/profiles-where-firefox-stores-user-data.
Close browser, run again and you have temporary solution for using part of your 
private data on old version of FF. As mentioned above - you can't use your full 
new profile folder with older version of FF so you need to manually overwrite 
dedicated files.
Hope it helps :)!

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

Title:
  Crash after update to 71.0~b5+build1-0ubuntu0.16.04.1

Status in firefox package in Ubuntu:
  Confirmed

Bug description:
  After update from: 70.0+build2-0ubuntu0.16.04.1 to
  71.0~b5+build1-0ubuntu0.16.04.1 app is not starting. I got constantly
  message that I can Refresh Firefox (crash) or Start in safe mode (also
  crash).

  Tech details:
  Description:  Ubuntu 16.04.6 LTS
  Release:  16.04
  package name:   71.0~b5+build1-0ubuntu0.16.04.1

  Crash log details:
  AdapterDeviceID: 0x1616
  AdapterDriverVendor: mesa/i965
  AdapterDriverVersion: 18.0.5.0
  AdapterVendorID: 0x8086
  BuildID: 20191028161640
  ContentSandboxCapabilities: 119
  ContentSandboxCapable: 1
  ContentSandboxLevel: 4
  CrashTime: 1572373123
  DOMIPCEnabled: 1
  FramePoisonBase: 9223372036600930304
  FramePoisonSize: 4096
  InstallTime: 1572364967
  IsWayland: 0
  IsWaylandDRM: 0
  MozCrashReason: MOZ_RELEASE_ASSERT(len.isValid()) (Substring tuple length is 
invalid)
  Notes: Ubuntu 16.04.6 LTSFP(D00-L1000-W-T000) WR? WR- OMTP? OMTP- 
  ProductID: {ec8030f7-c20a-464f-9b0e-13a3a9e97384}
  ProductName: Firefox
  ReleaseChannel: beta
  SafeMode: 1
  SecondsSinceLastCrash: 816
  StartupCrash: 0
  StartupTime: 1572373025
  TelemetryEnvironment: 
{"build":{"applicationId":"{ec8030f7-c20a-464f-9b0e-13a3a9e97384}","applicationName":"Firefox","architecture":"x86-64","buildId":"20191028161640","version":"71.0","vendor":"Mozilla","displayVersion":"71.0b5","platformVersion":"71.0","xpcomAbi":"x86_64-gcc3","updaterAvailable":false},"partner":{"distributionId":null,"distributionVersion":null,"partnerId":null,"distributor":null,"distributorChannel":null,"partnerNames":[]},"system":{"memoryMB":15965,"virtualMaxMB":null,"cpu":{"count":4,"cores":2,"vendor":"GenuineIntel","family":6,"model":61,"stepping":4,"l2cacheKB":256,"l3cacheKB":3072,"speedMHz":2700,"extensions":["hasMMX","hasSSE","hasSSE2","hasSSE3","hasSSSE3","hasSSE4_1","hasSSE4_2","hasAVX","hasAVX2","hasAES"]},"os":{"name":"Linux","version":"4.15.0-66-generic","locale":"en-US"},"hdd":{"profile":{"model":null,"revision":null,"type":null},"binary":{"model":null,"revision":null,"type":null},"system":{"model":null,"revision":null,"type":null}},"gfx":{"D2DEnabled":null,"DWriteEnabled":null,"ContentBackend":"Skia","Headless":false,"adapters":[{"description":"Mesa
 DRI Intel(R) HD Graphics 5500 (Broadwell GT2) 
","vendorID":"0x8086","deviceID":"0x1616","subsysID":null,"RAM":3072,"driver":null,"driverVendor":"mesa/i965","driverVersion":"18.0.5.0","driverDate":null,"GPUActive":true}],"monitors":[{"screenWidth":1366,"screenHeight":768}],"features":{"compositor":"none","gpuProcess":{"status":"blocked"},"wrQualified":{"status":"blocked-release-channel-intel"},"webrender":{"status":"unavailable-in-safe-mode"}}},"appleModelId":null},"settings":{"blocklistEnabled":true,"e10sEnabled":true,"e10sMultiProcesses":8,"telemetryEnabled":true,"locale":"en-US","intl":{},"update":{"channel":"beta","enabled":true,"autoDownload":false},"userPrefs":{"app.shield.optoutstudies.enabled":false,"browser.cache.disk.capacity":1048576,"browser.newtabpage.enabled":false,"browser.shell.checkDefaultBrowser":true,"browser.search.region":"US","browser.search.suggest.enabled":false,"browser.search.widget.inNavBar":false,"browser.startup.homepage":"","browser.startup.page":3,"browser.urlbar.suggest.searches":false,"devtools.chrome.enabled":false,"devtools.debugger.remote-enabled":false,"extensions.blocklist.url":"https://blocklists.settings.services.mozilla.com/v1/blocklist/3/%20/%20/","extensions.formautofill.addresses.enabled":false,"extensions.formautofill.creditCards.enabled":false,"privacy.donottrackheader.enabled":true},"sandbox":{"effectiveContentProcessLevel":4},"addonCompatibilityCheckEnabled":true,"isDefaultBrowser":null},"profile":{}}
  ThreadIdNameMapping: 7556:"Gecko_IOThread",7557:"JS Watchdog",7558:"JS 
Helper",7559:"JS Helper",7560:"JS Helper",7561:"JS 
Helper",7562:"Timer",7563:"Netlink Monitor",7564:"Socket Thread",7568:"Cache2 
I/O",7569:"Cookie",7570:"StreamTrans #1",7571:"GMPThread",7572:"Worker 
Launcher",7573:"SoftwareVsyncThread",7574:"Compositor"

[Desktop-packages] [Bug 1848185] Re: segfault in __strcasestr

2019-11-05 Thread Sebastien Bacher
No report for the 1.8.10-2ubuntu3 version

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

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

Title:
  segfault in __strcasestr

Status in network-manager-applet package in Ubuntu:
  Fix Released
Status in network-manager-applet source package in Bionic:
  Fix Committed

Bug description:
  * Impact

  The connection editor sometime segfaults

  * Test case

  no specific to trigger the issue but check that error reports stop with the 
new version
  https://errors.ubuntu.com/problem/22f059991e427d58a003539ecedff7be196a7e35

  * Regression potential

  the change is smaller and in newer serie, it should create issues but
  check that the editor keeps working fine without segfaultsb

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

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


[Desktop-packages] [Bug 1851127] Re: app page shows no install progress

2019-11-05 Thread Sebastien Bacher
** Changed in: gnome-software (Ubuntu)
   Status: Incomplete => 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/1851127

Title:
  app page shows no install progress

Status in gnome-software package in Ubuntu:
  New

Bug description:
  I just installed a couple of applications (bomb squad and android
  studio) and while installing, they show no install progress.

  Steps to reproduce

  Launch gnome-software
  Click an application from the front of G-S
  Click Install
  Fill in password

  Expected outcome

  I expect to be shown a progress bar, showing that installation is
  happening

  Actual outcome

  I see no progress, yet running `snap changes` in a terminal shows it is 
installing
  In addition, clicking "Install" again fails due to the install running.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: gnome-software 3.30.6-2ubuntu10
  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.1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Nov  3 11:42:28 2019
  InstallationDate: Installed on 2019-10-27 (6 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  InstalledPlugins:
   gnome-software-plugin-flatpak N/A
   gnome-software-plugin-snap3.30.6-2ubuntu10
  SourcePackage: gnome-software
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1851058] Re: Live session any mouse or keyboard command is ignored

2019-11-05 Thread Sebastien Bacher
*** This bug is a duplicate of bug 1850969 ***
https://bugs.launchpad.net/bugs/1850969

** This bug has been marked a duplicate of bug 1850969
   x11 session all mouse or keyboard action ignored

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

Title:
  Live session any mouse or keyboard command is ignored

Status in xorg package in Ubuntu:
  New

Bug description:
  The problem happens in the live session. Ubiquity starts ok, The default 
desktop is displayed, but any mouse or keyboard command is ignored. If instead 
of "Try Ubuntu" I select "install Ubuntu" the install runs fine but the new 
installed system has the problem described in bug #1850969.
  Same problem with ISO Alpha amd64 (20191101), 20191102, 20191030 and 20191031
  also on a different hardware (HP laptop) and also selecting 'graphic failsafe'
  Now I'm working with Wayland session because X11 does not work.

  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: Sat Nov  2 17:36:01 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 Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.
  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.1.0-1
  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/1851058/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-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-05 Thread Ubuntu QA Website
This bug has been reported on the Ubuntu ISO testing tracker.

A list of all reports related to this bug can be found here:
http://iso.qa.ubuntu.com/qatracker/reports/bugs/1850969

** Tags added: iso-testing

-- 
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:
  New
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 

[Desktop-packages] [Bug 1848741] Re: [amdgpu] Ubuntu 19.10 horizontal graphics corruption on AMD Ryzen 2500u (Raven Ridge)

2019-11-05 Thread elios
I am having this issue with a DELL XPS 13 (Intel HD 620).

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

Title:
  [amdgpu] Ubuntu 19.10 horizontal graphics corruption on AMD Ryzen
  2500u (Raven Ridge)

Status in linux package in Ubuntu:
  Confirmed
Status in xserver-xorg-video-amdgpu package in Ubuntu:
  Confirmed

Bug description:
  I have graphics artefacts: screan tearing, pieces of the previous window 
appear in the newly opened window.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu8
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 19.10
  InstallationDate: Installed on 2019-09-08 (42 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  Package: gnome-shell 3.34.1-1ubuntu1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1
  RelatedPackageVersions: mutter-common 3.34.1-1ubuntu1
  Tags:  eoan
  Uname: Linux 5.3.0-18-generic x86_64
  UpgradeStatus: Upgraded to eoan on 2019-10-17 (3 days ago)
  UserGroups: adm cdrom dip docker input lpadmin plugdev sambashare sudo
  _MarkForUpload: True

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

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


[Desktop-packages] [Bug 1851007] Re: Login option 'GNOME + Remmina' not working

2019-11-05 Thread corrado venturini
adding journalctl

** Attachment added: "journalctl -b"
   
https://bugs.launchpad.net/ubuntu/+source/remmina/+bug/1851007/+attachment/5303107/+files/boo.txt

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

Title:
  Login option 'GNOME + Remmina' not working

Status in remmina package in Ubuntu:
  Incomplete

Bug description:
  Selecting Login option 'GNOME + Remmina' I'm just returned to login
  panel with no message.

  corrado@corrado-p13-ff-1101:~$ 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: 800 MHz min/max: 800/3900 MHz Core speeds (MHz): 1: 800 2: 
800 3: 801 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: 5.30 GiB (0.6%) 
 ID-1: /dev/sda vendor: Toshiba model: DT01ACA100 size: 931.51 GiB 
  Partition: ID-1: / size: 15.62 GiB used: 5.30 GiB (33.9%) 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: 37.5 C mobo: N/A 
 Fan Speeds (RPM): N/A 
  Info:  Processes: 197 Uptime: 7m Memory: 7.49 GiB used: 1.00 GiB (13.4%) 
Init: systemd runlevel: 5 Compilers: 
 gcc: 9.2.1 Shell: bash v: 5.0.3 inxi: 3.0.36 
  corrado@corrado-p13-ff-1101:~$

  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: Sat Nov  2 08:17:56 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 Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.
  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-e

[Desktop-packages] [Bug 1849886] Re: lightdm does not work on eoan on raspberry pi 4

2019-11-05 Thread Kenneth Zadeck
Just for the record, I tried to change the memory size to 2gb and it did
not help.There are other open raspberry pi 4 bugs that are dependent
on having more that 3gb or ram and so i decided to test that possibility
(see https://bugs.launchpad.net/ubuntu/+source/linux-
raspi2/+bug/1848703) especially since the other person who sees this bug
also has a 4gb system.However it does not seem to help.

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

Title:
  lightdm does not work on eoan on raspberry pi 4

Status in lightdm package in Ubuntu:
  Confirmed

Bug description:
  if you follow the directions on
  https://wiki.ubuntu.com/ARM/RaspberryPi

  sudo apt-get install xubuntu-desktop

  about 20% thru the installation it will ask which window manager you want 
(using dpkg-reconfigure).
  if you select lightdm, you will only get a blank greeter screen after you 
reboot.

  using sudo dpkg-reconfigure gdm3

  resets this to gdm3 and after a reboot, everything is fine.

  this was done on a clean armhf eoan install on a 4gb raspberry pi 4B.

  I have done the install several times.   This bug is repeatable.

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

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


Re: [Desktop-packages] [Bug 1841051] Re: gpg password cache is never cleared

2019-11-05 Thread Wolf Pichler
It is no fault.

My original FR concerned gpg-agent because I was unaware of the fact
that

seahorse/gnome-keyring had the password stored.

On 05.11.19 11:26, Sebastien Bacher wrote:
> Thank you for your bug report. Could you give details on what you did
> exactly? If you ticked the box to store the auth in the keyring that's
> what it did, why would you expect it to do instead?
>
> ** Package changed: seahorse (Ubuntu) => gnome-keyring (Ubuntu)
>
> ** Changed in: gnome-keyring (Ubuntu)
> Status: New => Incomplete
>

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

Title:
  gpg password cache is never cleared

Status in gnome-keyring package in Ubuntu:
  Incomplete

Bug description:
  The gpg password never expires - not even after reboot.

  I tried to set in dconf-editor:

  org.gnome.crypto.cache gpg-cache-method 'idle'
  org.gnome.crypto.cache gpg-cache-ttl 300

  and created the following file:

  ~/.gnupg/gpg-agent.conf

  default-cache-ttl 300

  
  None of these methods help.

  In case this could be helpful I add this (from Amir on
  https://superuser.com/questions/1347956/gnome-keyring-cant-clear-
  passphrase):

  user@machine:~$ gpgconf --list-dirs agent-socket
  /run/user/1000/gnupg/S.gpg-agent

  user@machine:~$ systemctl --user status gpg-agent.socket
  Failed to dump process list, ignoring: No such file or directory
  ● gpg-agent.socket - GnuPG cryptographic agent and passphrase cache
 Loaded: loaded (/usr/lib/systemd/user/gpg-agent.socket; disabled; vendor 
preset: enabled)
 Active: active (running) since Wed 2019-08-21 14:53:28 CEST; 5min ago
   Docs: man:gpg-agent(1)
 Listen: /run/user/1000/gnupg/S.gpg-agent (Stream)
 CGroup: /user.slice/user-1000.slice/user@1000.service/gpg-agent.socket

  Aug 21 14:53:28 machine systemd[1726]: Listening on GnuPG
  cryptographic agent and passphrase cache.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gpg-agent 2.2.4-1ubuntu1.2
  ProcVersionSignature: Ubuntu 4.15.0-58.64-generic 4.15.18
  Uname: Linux 4.15.0-58-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Aug 22 14:14:08 2019
  InstallationDate: Installed on 2018-08-01 (386 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  SourcePackage: gnupg2
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1851322] Re: VPN auto-connect is not working

2019-11-05 Thread Mathieu Tarral
Hi Sebastien,

I'm using an the OpenVPN plugin.
I'm imported an .ovpn config file into NetworkManager and filled my credentials.

I found some interesting log messages in journalctl:

nov. 05 21:00:58  gnome-shell[2760]: Invalid connection type: vpn
nov. 05 21:00:58  gnome-shell[2760]: Invalid connection type: vpn
nov. 05 21:00:58  NetworkManager[1485]:  [1572984058.4210] 
vpn-connection[0x55e68ff9c730,50d6326e-03bc-49a9-9f04-40c353cf55b3,"protonvpn.udp.com",0]:
 Failed to request VPN secrets #3: No agents were available for this request.
nov. 05 21:00:58  NetworkManager[1485]:   [1572984058.4212] device 
(wlo1): state change: secondaries -> failed (reason 
'secondary-connection-failed', sys-iface-state: 'managed')


The error seems to be the "agent"
--> Failed to request VPN secrets #3: No agents were available for this request.

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

Title:
  VPN auto-connect is not working

Status in network-manager package in Ubuntu:
  Incomplete

Bug description:
  Hi,

  This is a duplicate of bug:
  https://bugs.launchpad.net/network-manager/+bug/1718931

  It is marked as fixed, but the feature is still broken for me.

  I configured my Wifi connection to automatically connect to a VPN, but it 
only works if I manually
  connect to the Wifi via NetworkManager.

  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.1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Nov  5 04:07: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 (39 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  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/1851322/+subscriptions

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


[Desktop-packages] [Bug 1792085] Re: MTP not working/very slow on Bionic

2019-11-05 Thread Artem Astafyev
As a temporary workaround ADB push/pull can be used. Mine worked with
speed around 20 Mb/s.

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

Title:
  MTP not working/very slow on Bionic

Status in libmtp:
  New
Status in gvfs package in Ubuntu:
  Incomplete

Bug description:
  Hi, unfortunately (for me) MTP android devices no more work on Ubuntu
  18.04.

  I have used MTP on 16.04 without problems, but on 18.04 it does not
  work. When I connect my Android devices (Samsung A5 and Samsung J3)
  and I try to list directories with many files (e.g. /DCIM/Camera) the
  window hangs until I disconnect the device. Same issue if I try to
  post the command "ls /var/run/1000/gvfs/".

  I have installed Ubuntu 18.04 on two different machines - an older HP
  laptop and a recent DELL laptop - and the issue is present on the all
  of them.

  I suspect a defect on the "libmtp". I tried many alternative solutions
  suggested by the net (e.g. jmtpfs and so on) but anyone worked.

  That's all!

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gvfs-fuse 1.36.1-0ubuntu1.1
  ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18
  Uname: Linux 4.15.0-29-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  CasperVersion: 1.394
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Sep 12 06:20:07 2018
  LiveMediaBuild: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gvfs
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1841051] Re: gpg password cache is never cleared

2019-11-05 Thread Sebastien Bacher
thanks, closing then

** Changed in: gnome-keyring (Ubuntu)
   Status: Incomplete => Invalid

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

Title:
  gpg password cache is never cleared

Status in gnome-keyring package in Ubuntu:
  Invalid

Bug description:
  The gpg password never expires - not even after reboot.

  I tried to set in dconf-editor:

  org.gnome.crypto.cache gpg-cache-method 'idle'
  org.gnome.crypto.cache gpg-cache-ttl 300

  and created the following file:

  ~/.gnupg/gpg-agent.conf

  default-cache-ttl 300

  
  None of these methods help.

  In case this could be helpful I add this (from Amir on
  https://superuser.com/questions/1347956/gnome-keyring-cant-clear-
  passphrase):

  user@machine:~$ gpgconf --list-dirs agent-socket
  /run/user/1000/gnupg/S.gpg-agent

  user@machine:~$ systemctl --user status gpg-agent.socket
  Failed to dump process list, ignoring: No such file or directory
  ● gpg-agent.socket - GnuPG cryptographic agent and passphrase cache
 Loaded: loaded (/usr/lib/systemd/user/gpg-agent.socket; disabled; vendor 
preset: enabled)
 Active: active (running) since Wed 2019-08-21 14:53:28 CEST; 5min ago
   Docs: man:gpg-agent(1)
 Listen: /run/user/1000/gnupg/S.gpg-agent (Stream)
 CGroup: /user.slice/user-1000.slice/user@1000.service/gpg-agent.socket

  Aug 21 14:53:28 machine systemd[1726]: Listening on GnuPG
  cryptographic agent and passphrase cache.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gpg-agent 2.2.4-1ubuntu1.2
  ProcVersionSignature: Ubuntu 4.15.0-58.64-generic 4.15.18
  Uname: Linux 4.15.0-58-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Aug 22 14:14:08 2019
  InstallationDate: Installed on 2018-08-01 (386 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  SourcePackage: gnupg2
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1851322] Re: VPN auto-connect is not working

2019-11-05 Thread Sebastien Bacher
The issue seems to be on the gnome-shell side then, which is supposed also to 
be the agent
gnome-shell[2760]: Invalid connection type: vpn

Could you report the issue upstream on https://gitlab.gnome.org/GNOME
/gnome-shell/issues ?

** Package changed: network-manager (Ubuntu) => gnome-shell (Ubuntu)

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

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

Title:
  VPN auto-connect is not working

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  Hi,

  This is a duplicate of bug:
  https://bugs.launchpad.net/network-manager/+bug/1718931

  It is marked as fixed, but the feature is still broken for me.

  I configured my Wifi connection to automatically connect to a VPN, but it 
only works if I manually
  connect to the Wifi via NetworkManager.

  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.1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Nov  5 04:07: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 (39 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  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/gnome-shell/+bug/1851322/+subscriptions

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


[Desktop-packages] [Bug 1851007] Re: Login option 'GNOME + Remmina' not working

2019-11-05 Thread Sebastien Bacher
Thanks for the log, that was informative, the issue is

gnome-session-binary[1634]: WARNING: Unable to find required component 
'org.gnome.SettingsDaemon.Clipboard'
gnome-session-binary[1634]: WARNING: Unable to find required component 
'org.gnome.SettingsDaemon.Mouse'

Those plugins got removed from gnome-settings-daemon but are still listed as 
requiredcomponents
https://gitlab.com/Remmina/Remmina/blob/master/data/desktop/remmina-gnome.session

Editing /usr/share/gnome-session/sessions/remmina-gnome.session to
removed those items should be enough to get past that issue if you want
to try that workaround.

Confirming the bug, that should also probably sent upstream

** Changed in: remmina (Ubuntu)
   Status: Incomplete => Confirmed

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

Title:
  Login option 'GNOME + Remmina' not working

Status in remmina package in Ubuntu:
  Confirmed

Bug description:
  Selecting Login option 'GNOME + Remmina' I'm just returned to login
  panel with no message.

  corrado@corrado-p13-ff-1101:~$ 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: 800 MHz min/max: 800/3900 MHz Core speeds (MHz): 1: 800 2: 
800 3: 801 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: 5.30 GiB (0.6%) 
 ID-1: /dev/sda vendor: Toshiba model: DT01ACA100 size: 931.51 GiB 
  Partition: ID-1: / size: 15.62 GiB used: 5.30 GiB (33.9%) 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: 37.5 C mobo: N/A 
 Fan Speeds (RPM): N/A 
  Info:  Processes: 197 Uptime: 7m Memory: 7.49 GiB used: 1.00 GiB (13.4%) 
Init: systemd runlevel: 5 Compilers: 
 gcc: 9.2.1 Shell: bash v: 5.0.3 inxi: 3.0.36 
  corrado@corrado-p13-ff-1101:~$

  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: Sat Nov  2 08:17:56 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.:pvrToBeFilled

[Desktop-packages] [Bug 1851375] Re: gnome-shell stops allowing interactions

2019-11-05 Thread Sebastien Bacher
*** This bug is a duplicate of bug 1850969 ***
https://bugs.launchpad.net/bugs/1850969

** This bug has been marked a duplicate of bug 1850969
   x11 session all mouse or keyboard action ignored

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

Title:
  gnome-shell stops allowing interactions

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  From time to time gnome-shell gets unresponsive to inputs. I can move
  the cursor, but I cannot interact with the shell in any way, neither
  with mouse or keyboard.

  When this happens I move to a vt and restart the shell with `killall
  -3 gnome-shell`. After this the shell does usually resume working
  (albeit some application crashes in the process from time to time).

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell 3.34.1+git20191024-1ubuntu1
  ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
  Uname: Linux 5.3.0-19-generic x86_64
  ApportVersion: 2.20.11-0ubuntu9
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Nov  5 15:31:55 2019
  DisplayManager: gdm3
  InstallationDate: Installed on 2019-02-03 (274 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  RelatedPackageVersions: mutter-common 3.34.1+git20191022-2ubuntu1
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to focal on 2019-07-21 (106 days ago)

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

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


[Desktop-packages] [Bug 1849257] Re: Firefox audio not playing via bluetooth

2019-11-05 Thread Sebastien Bacher
** Changed in: firefox (Ubuntu)
   Status: New => Fix Released

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

Title:
  Firefox audio not playing via bluetooth

Status in firefox package in Ubuntu:
  Fix Released

Bug description:
  When I am playing videos in Youtube, it plays through my laptop
  speakers instead of through the connected bluetooth device. I tried
  that with my USB headset but still audio plays out through my laptop
  speakers. Same for Prime Video. It works fine in Google chrome i.e.
  audio is re-routed through bluetooth speakers.

  I tried switching audio devices and still nothing changes.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: firefox 69.0.3+build1-0ubuntu1
  ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1
  Uname: Linux 5.3.0-18-generic x86_64
  AddonCompatCheckDisabled: False
  ApportVersion: 2.20.11-0ubuntu8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ashfaq 1386 F pulseaudio
   /dev/snd/pcmC0D0c:   ashfaq 1386 F...m pulseaudio
   /dev/snd/pcmC0D0p:   ashfaq 1386 F...m pulseaudio
  BuildID: 20191010103742
  Channel: Unavailable
  Date: Tue Oct 22 10:58:03 2019
  ForcedLayersAccel: False
  InstallationDate: Installed on 2019-10-18 (3 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  IpRoute:
   default via 192.168.1.1 dev wlp1s0 proto dhcp metric 600 
   169.254.0.0/16 dev wlp1s0 scope link metric 1000 
   192.168.1.0/24 dev wlp1s0 proto kernel scope link src 192.168.1.57 metric 600
  NoProfiles: True
  ProcEnviron:
   LANGUAGE=en_IN:en
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_IN
   SHELL=/bin/bash
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RunningIncompatibleAddons: False
  SourcePackage: firefox
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/28/2017
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V1.08
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: Suntory_KL
  dmi.board.vendor: KBL
  dmi.board.version: V1.08
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.08:bd11/28/2017:svnAcer:pnSwiftSF314-52:pvrV1.08:rvnKBL:rnSuntory_KL:rvrV1.08:cvnAcer:ct10:cvrChassisVersion:
  dmi.product.family: Swift 3
  dmi.product.name: Swift SF314-52
  dmi.product.sku: 
  dmi.product.version: V1.08
  dmi.sys.vendor: Acer

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

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


[Desktop-packages] [Bug 1850977] Re: gnome-software installs software without user having sudo access

2019-11-05 Thread Sebastien Bacher
Could you add a journalctl -b 0 log from a session when you did those
actions? Also what happens if you try to snap install a snap from the
commandline?

** Changed in: gnome-software (Ubuntu)
   Status: Incomplete => 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/1850977

Title:
  gnome-software installs software without user having sudo access

Status in gnome-software package in Ubuntu:
  New

Bug description:
  $ lsb_release -rd
  Description:  Ubuntu 18.04.2 LTS
  Release:  18.04

  $ apt-cache policy gnome-software
  gnome-software:
Installed: 3.28.1-0ubuntu4.18.04.8
Candidate: 3.28.1-0ubuntu4.18.04.12
Version table:
   3.28.1-0ubuntu4.18.04.12 500
  500 http://us.archive.ubuntu.com/ubuntu bionic-updates/main amd64 
Packages
   *** 3.28.1-0ubuntu4.18.04.8 100
  100 /var/lib/dpkg/status
   3.28.1-0ubuntu4 500
  500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64

  What I expect to happen:
Software is not installed for a user without sudo access.

  What does happen:
  I'm logging in with an LDAP user. This user does not have sudo access.

  When I select software from gnome-software ("Ubuntu Software"), it
  pops up and asks for my users password. I enter this in, and the
  software then installs (tested with blender, libreoffice, opencl
  driver).

  My user does *not* have sudo access on the system.

  $ sudo su -
  [sudo] password for jason: 
  jason is not in the sudoers file.  This incident will be reported.

  It appears these *may* be being installed with Snaps ... which still:

  How, without having root access, can an unprivileged user install
  something onto the system?

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-software 3.28.1-0ubuntu4.18.04.8
  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.5
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Nov  1 13:53:03 2019
  InstallationDate: Installed on 2019-11-01 (0 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  InstalledPlugins:
   gnome-software-plugin-flatpak N/A
   gnome-software-plugin-limba   N/A
   gnome-software-plugin-snap3.28.1-0ubuntu4.18.04.8
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-software
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


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

2019-11-05 Thread Sebastien Bacher
Thanks for testing, could you add the journalctl log from that session?

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

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

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

Status in gdm3 package in Ubuntu:
  New
Status in gnome-session package in Ubuntu:
  Incomplete
Status in gnome-shell package in Ubuntu:
  Incomplete
Status in gdm3 source package in Eoan:
  Incomplete
Status in gnome-session source package in Eoan:
  Incomplete
Status in gnome-shell source package in Eoan:
  Incomplete

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

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

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

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: xorg 1:7.7+19ubuntu12
  ProcVersionSignature: Ubuntu 5.3.0-13.14-generic 5.3.0
  Uname: Linux 5.3.0-13-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.suspend: suspend hibernate resume
  .proc.driver.nvidia.suspend_depth: default modeset uvm
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  435.21  Sun Aug 25 08:17:57 
CDT 2019
   GCC version:  gcc version 9.2.1 20190909 (Ubuntu 9.2.1-8ubuntu1)
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Sep 28 19:55:42 2019
  DistUpgraded: 2019-09-28 18:35:15,142 INFO cache.commit()
  DistroCodename: eoan
  DistroVariant: ubuntu
  DkmsStatus: nvidia, 435.21, 5.3.0-13-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   NVIDIA Corporation GP102 [GeForce GTX 1080 Ti] [10de:1b06] (rev a1) (prog-if 
00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. GP102 [GeForce GTX 1080 Ti] [1043:85e4]
  InstallationDate: Installed on 2019-09-14 (13 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  MachineType: MSI MS-7A67
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-13-generic 
root=UUID=04974c80-e732-49b6-8148-c3dce7c02a25 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg crash
  UpgradeStatus: Upgraded to eoan on 2019-09-28 (0 days ago)
  dmi.bios.date: 01/25/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2.60
  dmi.board.asset.tag: Default string
  dmi.board.name: H270I GAMING PRO AC (MS-7A67)
  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.:bvr2.60:bd01/25/2018:svnMSI:pnMS-7A67:pvr1.0:rvnMSI:rnH270IGAMINGPROAC(MS-7A67):rvr1.0:cvnMSI:ct3:cvr1.0:
  dmi.product.family: Default string
  dmi.product.name: MS-7A67
  dmi.product.sku: Default string
  dmi.product.version: 1.0
  dmi.sys.vendor: MSI
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.99-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.1.6-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20190820-0ubuntu3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1
  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/gdm3/+bug/1845801/+subscriptions

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


[Desktop-packages] [Bug 1850977] Re: gnome-software installs software without user having sudo access

2019-11-05 Thread Jason Stover
Here's the lines from journalctl -b 0  The "sudo" was from me doing:
sudo su - ... just prior to the "snap install blender --classic"

--- start cut ---
Nov 05 15:15:39 jms-u18t sudo[18049]: pam_unix(sudo:auth): authentication 
failure; logname= uid=1031 euid=0 tty=/dev/pts/0 ruser=jason rhost=  user=jason
Nov 05 15:15:39 jms-u18t sudo[18049]:jason : user NOT in sudoers ; 
TTY=pts/0 ; PWD=/home/users/jason ; USER=root ; COMMAND=/bin/su -
Nov 05 15:15:43 jms-u18t gnome-shell[16877]: polkitAuthenticationAgent: 
Received 3 identities that can be used for authentication. Only considering one.
Nov 05 15:15:46 jms-u18t polkit-agent-helper-1[18065]: pam_unix(polkit-1:auth): 
authentication failure; logname= uid=1031 euid=0 tty= ruser=jason rhost=  
user=jason
Nov 05 15:15:46 jms-u18t polkitd(authority=local)[881]: Operator of 
unix-session:116 successfully authenticated as unix-user:jason to gain 
TEMPORARY authorization for action io.snapcraft.snapd.manage for 
unix-process:18050:34595600 [snap install blender] (owned by unix-user:jason)
Nov 05 15:15:46 jms-u18t snapd[860]: api.go:952: Installing snap "blender" 
revision unset
Nov 05 15:16:02 jms-u18t gnome-shell[16877]: polkitAuthenticationAgent: 
Received 3 identities that can be used for authentication. Only considering one.
Nov 05 15:16:05 jms-u18t polkit-agent-helper-1[18083]: pam_unix(polkit-1:auth): 
authentication failure; logname= uid=1031 euid=0 tty= ruser=jason rhost=  
user=jason
Nov 05 15:16:05 jms-u18t polkitd(authority=local)[881]: Operator of 
unix-session:116 successfully authenticated as unix-user:jason to gain 
TEMPORARY authorization for action io.snapcraft.snapd.manage for 
unix-process:18068:34597431 [snap install blender --classic] (owned by 
unix-user:jason)
Nov 05 15:16:05 jms-u18t snapd[860]: api.go:952: Installing snap "blender" 
revision unset
Nov 05 15:16:11 jms-u18t systemd[1]: Reloading.
Nov 05 15:16:11 jms-u18t systemd[1]: Mounting Mount unit for blender, revision 
33...
Nov 05 15:16:11 jms-u18t systemd[1]: Mounted Mount unit for blender, revision 
33.
Nov 05 15:16:14 jms-u18t audit[18150]: AVC apparmor="STATUS" 
operation="profile_replace" info="same as current profile, skipping" 
profile="unconfined" name="snap-update-ns.blender" pid=18150 
comm="apparmor_parser"
Nov 05 15:16:14 jms-u18t audit[18151]: AVC apparmor="STATUS" 
operation="profile_replace" info="same as current profile, skipping" 
profile="unconfined" name="snap.blender.blender" pid=18151 
comm="apparmor_parser"
Nov 05 15:16:14 jms-u18t kernel: audit: type=1400 audit(1572988574.599:142): 
apparmor="STATUS" operation="profile_replace" info="same as current profile, 
skipping" profile="unconfined" name="snap-update-ns.blender" pid=18150 
comm="apparmor_parser"
Nov 05 15:16:14 jms-u18t kernel: audit: type=1400 audit(1572988574.599:143): 
apparmor="STATUS" operation="profile_replace" info="same as current profile, 
skipping" profile="unconfined" name="snap.blender.blender" pid=18151 
comm="apparmor_parser"
Nov 05 15:16:15 jms-u18t gnome-shell[16877]: Some code accessed the property 
'refreshPropertyOnProxy' on the module 'util'. That property was defined with 
'let' or 'const' inside the module. This was previously supported, but is not 
correct according to the ES6 standard. Any symbols to be exported from a 
Nov 05 15:16:15 jms-u18t pkexec[18154]: pam_unix(polkit-1:session): session 
opened for user root by (uid=1031)
Nov 05 15:16:15 jms-u18t pkexec[18154]: jason: Executing command [USER=root] 
[TTY=unknown] [CWD=/home/users/jason] 
[COMMAND=/usr/lib/update-notifier/package-system-locked]

--- end cut ---

So, we have here from polkitd:  "successfully authenticated as unix-
user:jason to gain TEMPORARY authorization for action
io.snapcraft.snapd.manage"

So... installing thorough snap, as long as you know the users
password... lets you install something on the system? Without needing
root privileges?

Is this some apparmor policy thing?

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

Title:
  gnome-software installs software without user having sudo access

Status in gnome-software package in Ubuntu:
  New

Bug description:
  $ lsb_release -rd
  Description:  Ubuntu 18.04.2 LTS
  Release:  18.04

  $ apt-cache policy gnome-software
  gnome-software:
Installed: 3.28.1-0ubuntu4.18.04.8
Candidate: 3.28.1-0ubuntu4.18.04.12
Version table:
   3.28.1-0ubuntu4.18.04.12 500
  500 http://us.archive.ubuntu.com/ubuntu bionic-updates/main amd64 
Packages
   *** 3.28.1-0ubuntu4.18.04.8 100
  100 /var/lib/dpkg/status
   3.28.1-0ubuntu4 500
  500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64

  What I expect to happen:
Software is not installed for a user without sudo access.

  What does happen:
  I'm logging in with an LDAP user. This user does not have sudo access.

  When I select softwar

[Desktop-packages] [Bug 1850977] Re: gnome-software installs software without user having sudo access

2019-11-05 Thread Jason Stover
Attached is a screenshot of the VM window where the terminal install was
done.

** Attachment added: "Installation using snap on account without sudo access"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1850977/+attachment/5303117/+files/Screenshot_2019-11-05_15-28-49.png

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

Title:
  gnome-software installs software without user having sudo access

Status in gnome-software package in Ubuntu:
  New

Bug description:
  $ lsb_release -rd
  Description:  Ubuntu 18.04.2 LTS
  Release:  18.04

  $ apt-cache policy gnome-software
  gnome-software:
Installed: 3.28.1-0ubuntu4.18.04.8
Candidate: 3.28.1-0ubuntu4.18.04.12
Version table:
   3.28.1-0ubuntu4.18.04.12 500
  500 http://us.archive.ubuntu.com/ubuntu bionic-updates/main amd64 
Packages
   *** 3.28.1-0ubuntu4.18.04.8 100
  100 /var/lib/dpkg/status
   3.28.1-0ubuntu4 500
  500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64

  What I expect to happen:
Software is not installed for a user without sudo access.

  What does happen:
  I'm logging in with an LDAP user. This user does not have sudo access.

  When I select software from gnome-software ("Ubuntu Software"), it
  pops up and asks for my users password. I enter this in, and the
  software then installs (tested with blender, libreoffice, opencl
  driver).

  My user does *not* have sudo access on the system.

  $ sudo su -
  [sudo] password for jason: 
  jason is not in the sudoers file.  This incident will be reported.

  It appears these *may* be being installed with Snaps ... which still:

  How, without having root access, can an unprivileged user install
  something onto the system?

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-software 3.28.1-0ubuntu4.18.04.8
  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.5
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Nov  1 13:53:03 2019
  InstallationDate: Installed on 2019-11-01 (0 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  InstalledPlugins:
   gnome-software-plugin-flatpak N/A
   gnome-software-plugin-limba   N/A
   gnome-software-plugin-snap3.28.1-0ubuntu4.18.04.8
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-software
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1851420] Re: Chromium: plasma integration and Whatsapp web broken after 19.10 update

2019-11-05 Thread Olivier Tilloy
Thanks for the report.

1) is bug #1741074.
2) web.whatsapp.com does user-agent detection. You'll need to spoof your user 
agent, for example using 
https://chrome.google.com/webstore/detail/user-agent-switcher-for-c/djflhoibgkdhkhhcedjiklpkjnoahfmg
3) is bug #1833611

I'm closing this bug as all the issues reported either have an easy
solution, or are already tracked by separate bug reports.

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

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

Title:
  Chromium: plasma integration and Whatsapp web broken after 19.10
  update

Status in chromium-browser package in Ubuntu:
  Invalid

Bug description:
  Hi, I've just upgraded Kubuntu from 19.04 to 19.10.

  Unfortunately I've three problems with Chromium:

  1) Plasma integration doesn't work anymore. It says it can't connect
  to native host.

  2) Whatsapp web doesn't work. It says I need Google Chrome 49+

  3) Mouse cursor is different from the one used in Kde

  What's wrong?

  My user agent is: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36
  (KHTML, like Gecko) snap Chromium/78.0.3904.70 Chrome/78.0.3904.70
  Safari/537.36

  Please note:

  a) I've also installed Google Chrome (not Chromium): Plasma interation
  and Whatsapp web works well

  b) I've removed Chromium browser with Discover, then install it again:
  same problems

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

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


Re: [Desktop-packages] [Bug 1841051] Re: gpg password cache is never cleared

2019-11-05 Thread Wolf Pichler
Thanks!

On 05.11.19 21:30, Sebastien Bacher wrote:
> thanks, closing then
>
> ** Changed in: gnome-keyring (Ubuntu)
> Status: Incomplete => Invalid
>

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

Title:
  gpg password cache is never cleared

Status in gnome-keyring package in Ubuntu:
  Invalid

Bug description:
  The gpg password never expires - not even after reboot.

  I tried to set in dconf-editor:

  org.gnome.crypto.cache gpg-cache-method 'idle'
  org.gnome.crypto.cache gpg-cache-ttl 300

  and created the following file:

  ~/.gnupg/gpg-agent.conf

  default-cache-ttl 300

  
  None of these methods help.

  In case this could be helpful I add this (from Amir on
  https://superuser.com/questions/1347956/gnome-keyring-cant-clear-
  passphrase):

  user@machine:~$ gpgconf --list-dirs agent-socket
  /run/user/1000/gnupg/S.gpg-agent

  user@machine:~$ systemctl --user status gpg-agent.socket
  Failed to dump process list, ignoring: No such file or directory
  ● gpg-agent.socket - GnuPG cryptographic agent and passphrase cache
 Loaded: loaded (/usr/lib/systemd/user/gpg-agent.socket; disabled; vendor 
preset: enabled)
 Active: active (running) since Wed 2019-08-21 14:53:28 CEST; 5min ago
   Docs: man:gpg-agent(1)
 Listen: /run/user/1000/gnupg/S.gpg-agent (Stream)
 CGroup: /user.slice/user-1000.slice/user@1000.service/gpg-agent.socket

  Aug 21 14:53:28 machine systemd[1726]: Listening on GnuPG
  cryptographic agent and passphrase cache.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gpg-agent 2.2.4-1ubuntu1.2
  ProcVersionSignature: Ubuntu 4.15.0-58.64-generic 4.15.18
  Uname: Linux 4.15.0-58-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Aug 22 14:14:08 2019
  InstallationDate: Installed on 2018-08-01 (386 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  SourcePackage: gnupg2
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1741074] Re: [snap] chrome-gnome-shell extension fails to detect native host connector

2019-11-05 Thread sbaragnaus
This bug is still present in Kubuntu 19.10. Poor Chromium...

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

Title:
  [snap] chrome-gnome-shell extension fails to detect native host
  connector

Status in chromium-browser package in Ubuntu:
  Triaged

Bug description:
  (initially reported at https://forum.snapcraft.io/t/chrome-gnome-
  shell-does-not-work-with-chromium-snap/3377)

  See attached screenshot.

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

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


[Desktop-packages] [Bug 1849346] Re: [snap] kerberos GSSAPI no longer works after deb->snap transition

2019-11-05 Thread st0ve
The /etc/gss/mech.d/ and /etc/krb5.conf.d/ denials may be relevant. Both
directories are empty in my case, but lack of access may be killing some
logic that relies on checking them.

** Attachment added: "AppArmor denials"
   
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1849346/+attachment/5303122/+files/apparmor_denials.txt

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

Title:
  [snap] kerberos GSSAPI no longer works after deb->snap transition

Status in chromium-browser package in Ubuntu:
  Confirmed

Bug description:
  I configure AuthServerWhitelist as documented:

  https://www.chromium.org/developers/design-documents/http-
  authentication

  and can see my whitelisted domains in chrome://policy/

  but websites that used to work with SPNEGO/GSSAPI/kerberos no longer
  work. I'm guessing the snap needs some sort of permission to use the
  kerberos ticket cache (or the plumbing to do so doesn't exist...).

  I can confirm that Chrome has the desired behavior.

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

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


[Desktop-packages] [Bug 1850887] Re: Audio / Sound reverts to HDMI when power event occurs

2019-11-05 Thread BloodyIron
I just upgraded from 19.04 to 19.10 and this happens every reboot, my
default audio switches from my sound card to my HDMI audio output.

This kind of a regression is really going to turn new users off to
Ubuntu/Linux.

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

Title:
  Audio / Sound reverts to HDMI when power event occurs

Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  PulseAudio reverts the sound to HDMI all the time when a HDMI related
  power event occurs. That means, although I have set another USB sound
  device plugged in and set as default under sound settings, when an
  application like Kodi or the system shuts off the HDMI monitor and I
  reactivate the monitor, the sound is set to HDMI output again and
  again.

  That probably has to do with the fix to the reported Bug # 1711101 and
  definitely not happened at Ubuntu 19.04. I switched to Ubuntu 19.10
  two days ago.

  Setting the USB device as default does not help, even when done by
  PulseAudio mixer (gui) and removing HDMI output from the alternatives
  option.

  Expected behavior:
  PulseAudio keeps the sound setting to the selected device

  Actual behavior: 
  PulseAudio changes to HDMI at every HDMI power event

  Annoying manual workaround:
  Setting the desired Audio option on the control panel after every HDMI power 
event again

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Component: pulseaudio
  Version: 1:13.0-1ubuntu1

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

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


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

2019-11-05 Thread Martin
It seems like Ubuntu now freezes when I try to switch to a TTY when
auto-login is enabled and has failed. This also happens with systemd 242
now though, so it must be some unrelated change. I got the log though,
thanks to journalctl saving logs from previous boots, and attached
failedlogin2.txt.

Interestingly, when booting from recovery mode, when just resuming
normal boot from the recovery menu, auto login works perfectly. After
that, I tried messing with grub options, and when I remove "splash" from
the linux cmdline, auto login works perfectly. I assume then that this
issue is related to how the GPU is initialized during early boot to show
the splash screen? (For the record, I tried to set my cmdline to "quiet
splash nomodeset", and it had no effect.)

** Attachment added: "output of journalctl -b  where login failed 
while running systemd 243"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1845801/+attachment/5303124/+files/failedlogin2.txt

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

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

Status in gdm3 package in Ubuntu:
  New
Status in gnome-session package in Ubuntu:
  Incomplete
Status in gnome-shell package in Ubuntu:
  Incomplete
Status in gdm3 source package in Eoan:
  Incomplete
Status in gnome-session source package in Eoan:
  Incomplete
Status in gnome-shell source package in Eoan:
  Incomplete

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

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

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

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: xorg 1:7.7+19ubuntu12
  ProcVersionSignature: Ubuntu 5.3.0-13.14-generic 5.3.0
  Uname: Linux 5.3.0-13-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.suspend: suspend hibernate resume
  .proc.driver.nvidia.suspend_depth: default modeset uvm
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  435.21  Sun Aug 25 08:17:57 
CDT 2019
   GCC version:  gcc version 9.2.1 20190909 (Ubuntu 9.2.1-8ubuntu1)
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Sep 28 19:55:42 2019
  DistUpgraded: 2019-09-28 18:35:15,142 INFO cache.commit()
  DistroCodename: eoan
  DistroVariant: ubuntu
  DkmsStatus: nvidia, 435.21, 5.3.0-13-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   NVIDIA Corporation GP102 [GeForce GTX 1080 Ti] [10de:1b06] (rev a1) (prog-if 
00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. GP102 [GeForce GTX 1080 Ti] [1043:85e4]
  InstallationDate: Installed on 2019-09-14 (13 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  MachineType: MSI MS-7A67
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-13-generic 
root=UUID=04974c80-e732-49b6-8148-c3dce7c02a25 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg crash
  UpgradeStatus: Upgraded to eoan on 2019-09-28 (0 days ago)
  dmi.bios.date: 01/25/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2.60
  dmi.board.asset.tag: Default string
  dmi.board.name: H270I GAMING PRO AC (MS-7A67)
  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.:bvr2.60:bd01/25/2018:svnMSI:pnMS-7A67:pvr1.0:rvnMSI:rnH270IGAMINGPROAC(MS-7A67):rvr1.0:cvnMSI:ct3:cvr1.0:
  dmi.product.family: Default string
  dmi.product.name: MS-7A67
  dmi.product.sku: Default string
  dmi.product.version: 1.0
  dmi.sys.vendor: MSI
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.99-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.1.6-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git2019

[Desktop-packages] [Bug 1851445] [NEW] Update to 70.0.1

2019-11-05 Thread Chris Coulson
Public bug reported:

https://www.mozilla.org/en-US/firefox/70.0.1/releasenotes/

** Affects: firefox (Ubuntu)
 Importance: Undecided
 Status: Fix Released

** Changed in: firefox (Ubuntu)
   Status: New => Fix Released

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

Title:
  Update to 70.0.1

Status in firefox package in Ubuntu:
  Fix Released

Bug description:
  https://www.mozilla.org/en-US/firefox/70.0.1/releasenotes/

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

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


  1   2   >