date:20191029

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

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

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

Title:
  upower is reporting really odd stats for battery charge time

Status in upower package in Ubuntu:
  Confirmed

Bug description:
  I virtually discharged my Lenovo ideapad y580 today, it then sat there
  charging for 5 ish hours.  However upower shows the battery at 86% and
  say 12:47 to complete the charge.  Unplugging the power and then
  plugging back in said :37 but then this has been climbing since and is
  back upto 2:10.

  ogra_ reported seeing similar things on his n7 with the upgrade to
  raring and also on his chromebook.

  If you need any info just let me know what.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: upower 0.9.19-1ubuntu4
  ProcVersionSignature: Ubuntu 3.8.0-8.17-generic 3.8.0
  Uname: Linux 3.8.0-8-generic x86_64
  ApportVersion: 2.8-0ubuntu4
  Architecture: amd64
  Date: Thu Feb 28 19:13:39 2013
  InstallationDate: Installed on 2013-02-13 (14 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Alpha amd64 (20130213)
  MarkForUpload: True
  SourcePackage: upower
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1550779] Re: [drm:intel_cpu_fifo_underrun_irq_handler [i915]] ERROR CPU pipe A FIFO underrun

2019-10-29 Thread vinibali

Whoops. We still have the functionality of rc6, just under a different name
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=fb6db0f5bf1d4d3a4af6242e287fa795221ec5b8

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

Title:
  [drm:intel_cpu_fifo_underrun_irq_handler [i915]] *ERROR* CPU pipe A
  FIFO underrun

Status in linux package in Ubuntu:
  Confirmed
Status in xorg-server package in Ubuntu:
  Incomplete

Bug description:
  Upgraded linux-image-extra-4.2.0-30-generic I see graphic glitches,
  looks like the graphic buffer gets screwed up

  - funny repetition's patterns  (back in time glitches)
  - black screen (<1sec)
  - graphic errors  

  I can influence the severity of the issue with switching windows and
  using certain programs, e.g. Google Maps in chrome causes this issue
  reproducibly

  dmesg  | grep i915
  [2.726864] [drm] Initialized i915 1.6.0 20150522 for :00:02.0 on 
minor 0
  [2.792005] [drm] GMBUS [i915 gmbus dpb] timed out, falling back to bit 
banging on pin 5
  [3.471092] i915 :00:02.0: fb0: inteldrmfb frame buffer device
  [3.471093] i915 :00:02.0: registered panic notifier
  [9.573129] [drm:intel_cpu_fifo_underrun_irq_handler [i915]] *ERROR* CPU 
pipe A FIFO underrun
  [9.574847] [drm:intel_set_pch_fifo_underrun_reporting [i915]] *ERROR* 
uncleared pch fifo underrun on pch transcoder A
  [9.574895] [drm:intel_pch_fifo_underrun_irq_handler [i915]] *ERROR* PCH 
transcoder A FIFO underrun

  linux-image-extra-4.2.0-27-generic works find

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: xorg 1:7.7+7ubuntu4
  ProcVersionSignature: Ubuntu 4.2.0-30.36-generic 4.2.8-ckt3
  Uname: Linux 4.2.0-30-generic x86_64
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  BootLog:
   
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: GNOME
  Date: Sat Feb 27 20:26:07 2016
  DistUpgraded: Fresh install
  DistroCodename: wily
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox, 5.0.14, 4.2.0-27-generic, x86_64: installed
   virtualbox, 5.0.14, 4.2.0-30-generic, x86_64: installed
  EcryptfsInUse: Yes
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0126] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: Lenovo Device [17aa:21da]
  InstallationDate: Installed on 2016-02-11 (15 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  MachineType: LENOVO 42912XG
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.2.0-30-generic 
root=UUID=cb34d7bb-9316-49b3-aa94-4e2a3512168f ro rootflags=subvol=@ noprompt 
quiet
  SourcePackage: xorg
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/18/2013
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 8DET69WW (1.39 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 42912XG
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Available
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvr8DET69WW(1.39):bd07/18/2013:svnLENOVO:pn42912XG:pvrThinkPadX220:rvnLENOVO:rn42912XG:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 42912XG
  dmi.product.version: ThinkPad X220
  dmi.sys.vendor: LENOVO
  version.compiz: compiz 1:0.9.12.2+15.10.20151202-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.64-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.0.2-1ubuntu4
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.0.2-1ubuntu4
  version.xserver-xorg-core: xserver-xorg-core 2:1.17.2-1ubuntu9.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.2-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 
1:7.5.0+git20150819-0ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20150808-0ubuntu4
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.11-1ubuntu3
  xserver.bootTime: Sat Feb 27 20:25:23 2016
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id   12359 
   vendor SEC
  xserver.version: 2:1.17.2-1ubuntu9.1

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

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

[Desktop-packages] [Bug 1550779] Re: [drm:intel_cpu_fifo_underrun_irq_handler [i915]] ERROR CPU pipe A FIFO underrun

2019-10-29 Thread vinibali

Just a small update:
I have been using i915.enable_psr=0 i915.enable_dc=0 i915.enable_fbc=0 
i915.enable_dp_mst=1 parameters for a few days, but except the very first or 
first two days when I unplugged the docking station, it doesn't helped at all.
So I decided to add error_capture=1 (record the GPU state following a hang) and 
a few days later complete it with a manual/udev disable for the i915 rc6. The 
kernel parameter has been removed 
(https://bugzilla.redhat.com/show_bug.cgi?id=1573482), however the function is 
still in the driver (/sys/class/drm/card0/power/rc6_enable:1).

Regards


** Bug watch added: Red Hat Bugzilla #1573482
   https://bugzilla.redhat.com/show_bug.cgi?id=1573482

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

Title:
  [drm:intel_cpu_fifo_underrun_irq_handler [i915]] *ERROR* CPU pipe A
  FIFO underrun

Status in linux package in Ubuntu:
  Confirmed
Status in xorg-server package in Ubuntu:
  Incomplete

Bug description:
  Upgraded linux-image-extra-4.2.0-30-generic I see graphic glitches,
  looks like the graphic buffer gets screwed up

  - funny repetition's patterns  (back in time glitches)
  - black screen (<1sec)
  - graphic errors  

  I can influence the severity of the issue with switching windows and
  using certain programs, e.g. Google Maps in chrome causes this issue
  reproducibly

  dmesg  | grep i915
  [2.726864] [drm] Initialized i915 1.6.0 20150522 for :00:02.0 on 
minor 0
  [2.792005] [drm] GMBUS [i915 gmbus dpb] timed out, falling back to bit 
banging on pin 5
  [3.471092] i915 :00:02.0: fb0: inteldrmfb frame buffer device
  [3.471093] i915 :00:02.0: registered panic notifier
  [9.573129] [drm:intel_cpu_fifo_underrun_irq_handler [i915]] *ERROR* CPU 
pipe A FIFO underrun
  [9.574847] [drm:intel_set_pch_fifo_underrun_reporting [i915]] *ERROR* 
uncleared pch fifo underrun on pch transcoder A
  [9.574895] [drm:intel_pch_fifo_underrun_irq_handler [i915]] *ERROR* PCH 
transcoder A FIFO underrun

  linux-image-extra-4.2.0-27-generic works find

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: xorg 1:7.7+7ubuntu4
  ProcVersionSignature: Ubuntu 4.2.0-30.36-generic 4.2.8-ckt3
  Uname: Linux 4.2.0-30-generic x86_64
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  BootLog:
   
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: GNOME
  Date: Sat Feb 27 20:26:07 2016
  DistUpgraded: Fresh install
  DistroCodename: wily
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox, 5.0.14, 4.2.0-27-generic, x86_64: installed
   virtualbox, 5.0.14, 4.2.0-30-generic, x86_64: installed
  EcryptfsInUse: Yes
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0126] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: Lenovo Device [17aa:21da]
  InstallationDate: Installed on 2016-02-11 (15 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  MachineType: LENOVO 42912XG
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.2.0-30-generic 
root=UUID=cb34d7bb-9316-49b3-aa94-4e2a3512168f ro rootflags=subvol=@ noprompt 
quiet
  SourcePackage: xorg
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/18/2013
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 8DET69WW (1.39 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 42912XG
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Available
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvr8DET69WW(1.39):bd07/18/2013:svnLENOVO:pn42912XG:pvrThinkPadX220:rvnLENOVO:rn42912XG:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 42912XG
  dmi.product.version: ThinkPad X220
  dmi.sys.vendor: LENOVO
  version.compiz: compiz 1:0.9.12.2+15.10.20151202-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.64-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.0.2-1ubuntu4
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.0.2-1ubuntu4
  version.xserver-xorg-core: xserver-xorg-core 2:1.17.2-1ubuntu9.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.2-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 
1:7.5.0+git20150819-0ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20150808-0ubuntu4
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.11-1ubuntu3
  xserver.bootTime: Sat Feb 27 20:25:23 2016

[Desktop-packages] [Bug 1849405] Re: Repeated keypresses from bluetooth keyboard

2019-10-29 Thread Matt Austin

I've now been using an Xorg session rather than Wayland and haven't seen
the repeated keys issue. I do get some very nasty screen tearing when
scrolling (e.g. websites) on Xorg however, so ideally I'd like to
continue using Wayland.

Does that mean that this is likely a mutter bug, rather than bluez?

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

Title:
  Repeated keypresses from bluetooth keyboard

Status in bluez package in Ubuntu:
  Incomplete
Status in mutter package in Ubuntu:
  Incomplete

Bug description:
  I have a Microsoft Surface bluetooth keyboard, and semi-frequently
  (e.g. around every 10-15mins) end up with repeated keypresses being
  made (e.g. apppt get update).

  This seems to happen when the machine is under slight stress, or when
  a new notification pops up in gnome, so it could be related to wayland
  possibly - but even if wayland or other processes are causing stress,
  I should imagine the bluetooth hid driver should not cause repeated
  key presses.

  Please let me know if you require further information about my
  environment, it's difficult to know where to begin with determining
  which process is the root cause of this.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: bluez 5.48-0ubuntu3.2
  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.7
  Architecture: amd64
  Date: Wed Oct 23 09:38:20 2019
  InterestingModules: rfcomm bnep btusb bluetooth
  MachineType: Dell Inc. Latitude 7480
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_AU.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-32-generic 
root=/dev/mapper/sarasota--kf--vg-root ro quiet splash vt.handoff=1
  SourcePackage: bluez
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/04/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.15.1
  dmi.board.name: 00F6D3
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.15.1:bd07/04/2019:svnDellInc.:pnLatitude7480:pvr:rvnDellInc.:rn00F6D3:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Latitude
  dmi.product.name: Latitude 7480
  dmi.product.sku: 07A0
  dmi.sys.vendor: Dell Inc.
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: F8:63:3F:E9:51:8C  ACL MTU: 1021:4  SCO MTU: 96:6
UP RUNNING PSCAN 
RX bytes:1658613 acl:66750 sco:0 events:15708 errors:0
TX bytes:605292 acl:98 sco:0 commands:2484 errors:0

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

-- 
Mailing list: https://launchpad.net/~desktop-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-10-29 Thread Greg Whiteley

Apologies if I've incorrectly duplicated here - I've logged a separate
bug to ensure there is a full AppPort bundle as suggested in the firefox
bug wiki page.

https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1850597

-- 
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
  use

[Desktop-packages] [Bug 1850597] [NEW] Firefox 71.0~b5+build1-0ubuntu0.16.04.1 crashes at startup

2019-10-29 Thread Greg Whiteley

Public bug reported:

Sorry if this duplicates #1850529 but I wanted to be sure that there was
an AppPort upload

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: firefox 71.0~b5+build1-0ubuntu0.16.04.1 [origin: 
LP-PPA-mozillateam-firefox-next]
ProcVersionSignature: Ubuntu 4.15.0-66.75~16.04.1-generic 4.15.18
Uname: Linux 4.15.0-66-generic x86_64
AddonCompatCheckDisabled: False
ApportVersion: 2.20.1-0ubuntu2.19
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/pcmC0D0p:   greg  13968 F...m pulseaudio
 /dev/snd/controlC0:  greg  13968 F pulseaudio
BuildID: 20191028161640
Channel: beta
CurrentDesktop: Unity
Date: Wed Oct 30 16:39:06 2019
DefaultProfileExtensions: extensions.sqlite corrupt or missing
DefaultProfileIncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
DefaultProfileLocales: extensions.sqlite corrupt or missing
DefaultProfilePrefErrors: Unexpected character ',' before close parenthesis @ 
/usr/lib/firefox/omni.ja:greprefs.js:722
DefaultProfilePrefSources:
 /usr/lib/firefox/defaults/pref/vendor-gre.js
 /usr/lib/firefox/defaults/pref/channel-prefs.js
 prefs.js
DefaultProfileThemes: extensions.sqlite corrupt or missing
ForcedLayersAccel: False
IfupdownConfig:
 # interfaces(5) file used by ifup(8) and ifdown(8)
 auto lo
 iface lo inet loopback
InstallationDate: Installed on 2014-05-06 (2002 days ago)
InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
MostRecentCrashID: bp-374760d9-4963-467e-9ff4-761800191030
Profile1Extensions: extensions.sqlite corrupt or missing
Profile1IncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
Profile1Locales: extensions.sqlite corrupt or missing
Profile1PrefErrors: Unexpected character ',' before close parenthesis @ 
/usr/lib/firefox/omni.ja:greprefs.js:722
Profile1PrefSources:
 /usr/lib/firefox/defaults/pref/vendor-gre.js
 /usr/lib/firefox/defaults/pref/channel-prefs.js
 prefs.js
Profile1Themes: extensions.sqlite corrupt or missing
Profile2Extensions: extensions.sqlite corrupt or missing
Profile2IncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
Profile2Locales: extensions.sqlite corrupt or missing
Profile2PrefErrors: Unexpected character ',' before close parenthesis @ 
/usr/lib/firefox/omni.ja:greprefs.js:722
Profile2PrefSources:
 /usr/lib/firefox/defaults/pref/vendor-gre.js
 /usr/lib/firefox/defaults/pref/channel-prefs.js
 prefs.js
Profile2Themes: extensions.sqlite corrupt or missing
Profiles:
 Profile1 - LastVersion=70.0/20191021052918 (Out of date)
 Profile0 (Default) - LastVersion=71.0/20191028161640
 Profile2 - LastVersion=71.0/20191028161640
RunningIncompatibleAddons: False
SourcePackage: firefox
UpgradeStatus: Upgraded to xenial on 2018-10-19 (375 days ago)
dmi.bios.date: 09/18/2018
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: F10
dmi.board.asset.tag: Default string
dmi.board.name: Z370M D3H-CF
dmi.board.vendor: Gigabyte Technology Co., Ltd.
dmi.board.version: Default string
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 3
dmi.chassis.vendor: Default string
dmi.chassis.version: Default string
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF10:bd09/18/2018:svnGigabyteTechnologyCo.,Ltd.:pnZ370MD3H:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnZ370MD3H-CF:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring:
dmi.product.family: Default string
dmi.product.name: Z370M D3H
dmi.product.version: Default string
dmi.sys.vendor: Gigabyte Technology Co., Ltd.

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


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

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

Title:
  Firefox 71.0~b5+build1-0ubuntu0.16.04.1 crashes at startup

Status in firefox package in Ubuntu:
  New

Bug description:
  Sorry if this duplicates #1850529 but I wanted to be sure that there
  was an AppPort upload

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: firefox 71.0~b5+build1-0ubuntu0.16.04.1 [origin: 
LP-PPA-mozillateam-firefox-next]
  ProcVersionSignature: Ubuntu 4.15.0-66.75~16.04.1-generic 4.15.18
  Uname: Linux 4.15.0-66-generic x86_64
  AddonCompatCheckDisabled: False
  ApportVersion: 2.20.1-0ubuntu2.19
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   greg  13968 F...m pulseaudio
   /dev/snd/controlC0:  greg  13968 F pulseaudio
  BuildID: 20191028161640
  Channel: beta
  CurrentDesktop: Unity
  Date: Wed Oct 30 16:39:06 2019
  DefaultProfileExtensions: extensions.sqlite corrupt or missing
  DefaultProfileIncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
  DefaultProfileLocales: extensions.sqlite corrupt or

[Desktop-packages] [Bug 1849615] Re: WebRTC-related crashes

2019-10-29 Thread Olivier Tilloy

** Changed in: firefox (Ubuntu)
   Status: New => Fix Committed

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

Title:
  WebRTC-related crashes

Status in Mozilla Firefox:
  Fix Released
Status in firefox package in Ubuntu:
  Fix Committed

Bug description:
  In Mozilla we've detected a spike of crashes in the Ubuntu-packaged
  version of Firefox 69.0.x. All the crashes are happening in the WebRTC
  code and specifically libc's FD_SET, FD_CLR and FD_ISSET range-
  checking safety is causing an abort. Is it possible that Firefox is
  being built with a FD_SETSIZE value that's different from what's used
  in libc?

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

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

[Desktop-packages] [Bug 1850052] Re: installing zsys breaks desktop login

This bug was fixed in the package zsys - 0.2.4

---
zsys (0.2.4) focal; urgency=medium

  * Skip tests on platform we don't build a binary for
(no grub2-common package available).
Autopkgtests will still try to run it if it ever ran one day
and would fail as it can't install zsys.

zsys (0.2.3) focal; urgency=medium

  * Backward compatibility for org.zsys set on user datasets and transition
to newer com.ubuntu.zsys (LP: #1850052)

 -- Didier Roche   Tue, 29 Oct 2019 07:48:55 +0100

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

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

Title:
  installing zsys breaks desktop login

Status in zsys package in Ubuntu:
  Fix Released
Status in zsys source package in Eoan:
  Triaged

Bug description:
  [Impact] 
  After installing zsys on 19.10, you can't log in in your desktop. Removing it 
won't fix the issue.

  [Test Case]
  Test A: (migrating broken people)
  1. Install 19.10 using experimental ZFS disk partitioning and reboot on 
installed system.
  2. sudo apt install zsys
  3. Reboot
  4. Attempt to login to the desktop
  -> you can't log in.
  5. Go to a tty (ctrl + alt + F3) and log in as your user
  6. Install zsys 0.2.3 from -proposed
  7. Reboot
  -> you can now log in in GDM.

  Test B: (direct installation)
  1. Install 19.10 using experimental ZFS disk partitioning and reboot on 
installed system.
  2. Install zsys from proposed
  3. Reboot
  -> you can log in in GDM.

  [Regression Potential] 
  Due to a missing rename in the installer from "org.zsys" to 
"com.ubuntu.zsys", we added transitional code which can be dropped in 20.04 as 
soon as compatible ubiquity is installed. People in 19.10 up to date (with the 
SRU fix) will have the required compatible tag.
  Note that we only due to transition once, the first time we are able to set 
the current timestamp.
  This doesn't regress any existing tests. Note that as this is due to unsync 
behavior between installer and zsys, zsys is behaving as expecting 
(unfortunately to the user) and the transitional code being removed soon, we 
didn't add a special test which will be removed later on.

  -

  I installed zsys on an up to date 19.10 system and can now no longer login. 
Removing zsys from a tty does not solve the problem.
  The home partition is no longer available - I have "lost" all my files, which 
were there before I installed zsys and rebooted

  Steps to reproduce.

  1. Install 19.10 using experimental ZFS disk partitioning.
  2. Complete the first run wizard
  3. Install all updates
  4. sudo apt install zsys
  5. reboot
  6. Attempt to login to the desktop

  Actual outcome

  * GDM accepts user/password, clears screen, looks like desktop is
  about to start, then I get dropped back to GDM

  Expected outcome

  * Login successful.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: zsys 0.2.2
  ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
  Uname: Linux 5.3.0-19-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu8
  Architecture: amd64
  Date: Sun Oct 27 14:50:10 2019
  InstallationDate: Installed on 2019-10-27 (0 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  SourcePackage: zsys
  UpgradeStatus: No upgrade log present (probably fresh install)

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

-- 
Mailing list: https://launchpad.net/~desktop-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-10-29 Thread Greg Whiteley

Can confirm same issue here - also 16.04 x86_64 - also tried creating a
new (clean) profile, but that does not resolve the issue.

I've reverted off the beta/next ppa back to
"70.0+build2-0ubuntu0.16.04.1", but can't use my old profile as
reverting profiles isn't allowed

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

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

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

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

-- 
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.launchp

[Desktop-packages] [Bug 1848852] Re: Counter-Strike Global Offensive freezes in gnome-shell

2019-10-29 Thread Treviño

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

** This bug has been marked a duplicate of bug 1845302
   cannot click on others opened applications while the "application not 
responding" dialog is opened

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

Title:
  Counter-Strike Global Offensive freezes in gnome-shell

Status in GNOME Shell:
  New
Status in gnome-shell package in Ubuntu:
  Triaged

Bug description:
  After upgrade to ubuntu 19.10, when I launch counter strike global offensive 
from steam the game is frozen. I can alt-tab and close the game. Tried in 
fluxbox window manager where the game works, changed fullscreen to windowed 
fullscreen in the options and tried on gnome again, now the desktop isn't 
responding after launching the game and I had to ctrl-alt-f3 to reboot my 
machine.
  Using a Radeon RX 580 video card.

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

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

[Desktop-packages] [Bug 1841679] Re: [nvidia] Login screen never wakes after sleeping and there is no way to recover

[Expired for gdm3 (Ubuntu) because there has been no activity for 60
days.]

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

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

Title:
  [nvidia] Login screen never wakes after sleeping and there is no way
  to recover

Status in gdm3 package in Ubuntu:
  Expired
Status in gnome-shell package in Ubuntu:
  Expired

Bug description:
  This was recreated on a System76 Serval WS (serw11) on Ubuntu 18.04 with the 
following versions of packages:
  ```cat /etc/os-release 
  NAME="Ubuntu"
  VERSION="18.04.3 LTS (Bionic Beaver)"
  ID=ubuntu
  ID_LIKE=debian
  PRETTY_NAME="Ubuntu 18.04.3 LTS"
  VERSION_ID="18.04"
  HOME_URL="https://www.ubuntu.com/";
  SUPPORT_URL="https://help.ubuntu.com/";
  BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/";
  
PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy";
  VERSION_CODENAME=bionic
  UBUNTU_CODENAME=bionic
  apt policy gdm3
  gdm3:
  Installed: 3.28.3-0ubuntu18.04.5pop1~1551986836~18.04~d21ecd7
  Candidate: 3.28.3-0ubuntu18.04.5pop1~1551986836~18.04~d21ecd7~dev
  Version table:
  *** 3.28.3-0ubuntu18.04.5pop1~1551986836~18.04~d21ecd7 100
  100 /var/lib/dpkg/status
  3.28.3-0ubuntu18.04.5pop1~1551986836~18.04~d21ecd7~dev 1001
  1001 http://ppa.launchpad.net/system76-dev/stable/ubuntu bionic/main amd64 
Packages
  3.28.3-0ubuntu18.04.4 500
  500 http://us.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages
  500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 Packages
  3.28.0-0ubuntu1 500
  500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages
  apt policy gnome-shell
  gnome-shell:
  Installed: 3.28.4-0ubuntu18.04.1
  Candidate: 3.28.4-0ubuntu18.04.1
  Version table:
  *** 3.28.4-0ubuntu18.04.1 500
  500 http://us.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages
  100 /var/lib/dpkg/status
  3.28.3+git20190124-0ubuntu18.04.2 500
  500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 Packages
  3.28.1-0ubuntu2 500
  500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages
  ```
  Here are the steps to recreate the issue:
  The blank screen issue can be recreated very easily:

  Power on system - NOT LIVE DISK.
  It gets to the ubuntu login screen.
  Do NOT login and stay at this screen until the screen goes blank.
  try to wake screen and unable to.
  only course of action here is to hard power off.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: gdm3 3.28.3-0ubuntu18.04.5pop1~1551986836~18.04~d21ecd7~dev [origin: 
LP-PPA-system76-dev-stable]
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.0.0-23.24~18.04.1-generic 5.0.15
  Tags: bionic third-party-packages
  Uname: Linux 5.0.0-23-generic x86_64
  UnreportableReason: This is not an official Ubuntu package. Please remove any 
third party package and try again.
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm sudo
  _MarkForUpload: True

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

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

[Desktop-packages] [Bug 1841679] Re: [nvidia] Login screen never wakes after sleeping and there is no way to recover

[Expired for gnome-shell (Ubuntu) because there has been no activity for
60 days.]

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

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

Title:
  [nvidia] Login screen never wakes after sleeping and there is no way
  to recover

Status in gdm3 package in Ubuntu:
  Expired
Status in gnome-shell package in Ubuntu:
  Expired

Bug description:
  This was recreated on a System76 Serval WS (serw11) on Ubuntu 18.04 with the 
following versions of packages:
  ```cat /etc/os-release 
  NAME="Ubuntu"
  VERSION="18.04.3 LTS (Bionic Beaver)"
  ID=ubuntu
  ID_LIKE=debian
  PRETTY_NAME="Ubuntu 18.04.3 LTS"
  VERSION_ID="18.04"
  HOME_URL="https://www.ubuntu.com/";
  SUPPORT_URL="https://help.ubuntu.com/";
  BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/";
  
PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy";
  VERSION_CODENAME=bionic
  UBUNTU_CODENAME=bionic
  apt policy gdm3
  gdm3:
  Installed: 3.28.3-0ubuntu18.04.5pop1~1551986836~18.04~d21ecd7
  Candidate: 3.28.3-0ubuntu18.04.5pop1~1551986836~18.04~d21ecd7~dev
  Version table:
  *** 3.28.3-0ubuntu18.04.5pop1~1551986836~18.04~d21ecd7 100
  100 /var/lib/dpkg/status
  3.28.3-0ubuntu18.04.5pop1~1551986836~18.04~d21ecd7~dev 1001
  1001 http://ppa.launchpad.net/system76-dev/stable/ubuntu bionic/main amd64 
Packages
  3.28.3-0ubuntu18.04.4 500
  500 http://us.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages
  500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 Packages
  3.28.0-0ubuntu1 500
  500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages
  apt policy gnome-shell
  gnome-shell:
  Installed: 3.28.4-0ubuntu18.04.1
  Candidate: 3.28.4-0ubuntu18.04.1
  Version table:
  *** 3.28.4-0ubuntu18.04.1 500
  500 http://us.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages
  100 /var/lib/dpkg/status
  3.28.3+git20190124-0ubuntu18.04.2 500
  500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 Packages
  3.28.1-0ubuntu2 500
  500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages
  ```
  Here are the steps to recreate the issue:
  The blank screen issue can be recreated very easily:

  Power on system - NOT LIVE DISK.
  It gets to the ubuntu login screen.
  Do NOT login and stay at this screen until the screen goes blank.
  try to wake screen and unable to.
  only course of action here is to hard power off.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: gdm3 3.28.3-0ubuntu18.04.5pop1~1551986836~18.04~d21ecd7~dev [origin: 
LP-PPA-system76-dev-stable]
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.0.0-23.24~18.04.1-generic 5.0.15
  Tags: bionic third-party-packages
  Uname: Linux 5.0.0-23-generic x86_64
  UnreportableReason: This is not an official Ubuntu package. Please remove any 
third party package and try again.
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm sudo
  _MarkForUpload: True

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

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

[Desktop-packages] [Bug 1845046] Re: Bluetooth headphones/speaker default to low quality headset mode and fails to switch to A2DP when selected

2019-10-29 Thread Rob Frohne

I spent 45 minutes playing with this problem this morning.  I restarted
my computer this morning, but nothing helped.  Now, after work, where
the computer was in suspended, but not restarted, and used periodically,
and it works just fine.  I did connect another headset to see if it was
a Sony problem, and now both headsets work as expected.  I do know that
A2DP is deactivated if you select the microphone on the headset, but
this morning I switched that back and forth several times with no
effect.  Fortunately, or unfortunately as it may be, I cannot now
duplicate the results I had this morning, and I can't figure out why.
It may have happened when I connected the headset to bluetooth again to
test this evening.  I cannot remember if I disconnected the headset and
reconnected it this morning.

Rob

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

Title:
  Bluetooth headphones/speaker default to low quality headset mode and
  fails to switch to A2DP when selected

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

Bug description:
  Whenever I turn on my headphones theyll connect to my computer but im
  able to hear the input audio from my microphone and low quality output
  audio. I have to disconnect the headphones in the bluetooth devices
  and reconnect for it to fix the problem.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: pulseaudio 1:11.1-1ubuntu7.2
  ProcVersionSignature: Ubuntu 5.0.0-29.31~18.04.1-generic 5.0.21
  Uname: Linux 5.0.0-29-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7.7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  litleck1398 F pulseaudio
   /dev/snd/controlC0:  litleck1398 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Sep 23 17:07:59 2019
  InstallationDate: Installed on 2019-09-22 (0 days ago)
  InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 
(20190805)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: pulseaudio
  Symptom: audio
  Symptom_Card: WH-1000XM3
  Symptom_Type: High background noise, or volume is too low
  Title: [WH-1000XM3, playback] Background noise or low volume
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/12/2019
  dmi.bios.vendor: Alienware
  dmi.bios.version: 1.0.19
  dmi.board.name: 01NYPT
  dmi.board.vendor: Alienware
  dmi.board.version: A00
  dmi.chassis.type: 3
  dmi.chassis.vendor: Alienware
  dmi.chassis.version: Not Specified
  dmi.modalias: 
dmi:bvnAlienware:bvr1.0.19:bd02/12/2019:svnAlienware:pnAlienwareAuroraR5:pvr1.0.19:rvnAlienware:rn01NYPT:rvrA00:cvnAlienware:ct3:cvrNotSpecified:
  dmi.product.family: Alienware
  dmi.product.name: Alienware Aurora R5
  dmi.product.sku: 0729
  dmi.product.version: 1.0.19
  dmi.sys.vendor: Alienware

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

-- 
Mailing list: https://launchpad.net/~desktop-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

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

-- 
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 Eoan:
  New
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 184510] A patch has been submitted for review

2019-10-29 Thread Mahara Bot

Patch for "master" branch: https://reviews.mahara.org/10510

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

Title:
  Bug 81910

Status in onboard package in Ubuntu:
  Fix Released

Bug description:
  Binary package hint: onboard

  hardy upgrade from wubi 7.04 install

  ProblemType: Crash
  Architecture: i386
  CrashCounter: 1
  Date: Sat Jan 19 22:35:51 2008
  DistroRelease: Ubuntu 8.04
  ExecutablePath: /usr/share/onboard/run-onboard.py
  InterpreterPath: /usr/bin/python2.5
  NonfreeKernelModules: nvidia
  Package: onboard 0.87
  PackageArchitecture: all
  ProcCmdline: /usr/bin/python /usr/share/onboard/run-onboard.py
  ProcCwd: /home/wx3200
  ProcEnviron:
   PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  Signal: 11
  SourcePackage: onboard
  StacktraceTop:
   ?? () from /usr/lib/python2.5/site-packages/virtkey.so
   ?? ()
   ?? () from /usr/lib/python2.5/site-packages/virtkey.so
   ?? ()
   ?? ()
  Title: run-onboard.py crashed with SIGSEGV
  Uname: Linux ubuntu 2.6.24-3-generic #1 SMP Thu Jan 3 23:30:29 UTC 2008 i686 
GNU/Linux
  UserGroups: adm admin audio cdrom dialout dip floppy lpadmin netdev plugdev 
powerdev scanner video

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

-- 
Mailing list: https://launchpad.net/~desktop-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

Fix released in 20.04:

mutter (3.34.1+git20191022-2ubuntu1) focal; urgency=medium


** Tags added: rls-ee-incoming

-- 
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:
  Unknown
Status in mutter package in Ubuntu:
  Fix Released
Status in mutter source package in Eoan:
  New
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 1850535] Re: Ubuntu 19.10 gnome-shell crashes after changing keyboard

Let's assume this is https://gitlab.gnome.org/GNOME/mutter/issues/750
for now, until proven otherwise.

If it's not then you will need to follow these instructions:
https://wiki.ubuntu.com/Bugs/Responses#Missing_a_crash_report_or_having_a_.crash_attachment

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

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

** Tags added: fixed-in-3.34.2 fixed-upstream

** Also affects: mutter (Ubuntu Focal)
   Importance: Undecided
   Status: New

** Also affects: mutter (Ubuntu Eoan)
   Importance: Undecided
   Status: New

** Changed in: mutter (Ubuntu Focal)
   Status: New => Fix Released

-- 
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:
  Unknown
Status in mutter package in Ubuntu:
  Fix Released
Status in mutter source package in Eoan:
  New
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 1850444] Re: Selecting A2DP profile but only get mono

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

Thank you for taking the time to report this bug and helping to make
Ubuntu better. This particular bug has already been reported and is a
duplicate of bug 1845046, so it is being marked as such. Please look at
the other bug report to see if there is any missing information that you
can provide, or to see if there is a workaround for the bug.
Additionally, any further discussion regarding the bug should occur in
the other report. Feel free to continue to report any other bugs you may
find.


** Summary changed:

- Cannot connect headset to A2DP anymore
+ Selecting A2DP profile but only get mono

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

** This bug has been marked a duplicate of bug 1845046
   Bluetooth headphones/speaker default to low quality headset mode and fails 
to switch to A2DP when selected

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

Title:
  Selecting A2DP profile but only get mono

Status in bluez package in Ubuntu:
  New
Status in pulseaudio package in Ubuntu:
  New

Bug description:
  As of October 29, I can no longer connect to my Sony MDR-1000x headphones 
using A2DP.  The gnome sound manager has the setting, but when I select it and 
use the test button, it is only mono.  I tried the gnome extension 
https://extensions.gnome.org/extension/906/sound-output-device-chooser/ and the 
option is always grayed out there. I tried to make A2DP the default using the 
method described here: 
https://medium.com/@overcode/fixing-bluetooth-in-ubuntu-pop-os-18-04-d4b8dbf7ddd6
  I tried to install some tools to try and get a better idea what might be 
going on.  In case it was a recent update, here are the last few days of my 
update log:
  Start-Date: 2019-10-21  08:19:53
  Commandline: aptdaemon role='role-commit-packages' sender=':1.375055'
  Install: linux-image-5.3.0-19-generic:amd64 (5.3.0-19.20, automatic), 
linux-modules-extra-5.3.0-19-generic:amd64 (5.3.0-19.20, automatic), 
linux-headers-5.3.0-19-generic:amd64 (5.3.0-19.20, automatic), 
linux-modules-5.3.0-19-generic:amd64 (5.3.0-19.20, automatic), 
linux-headers-5.3.0-19:amd64 (5.3.0-19.20, automatic)
  Upgrade: linux-headers-generic:amd64 (5.3.0.18.21, 5.3.0.19.22), 
linux-libc-dev:amd64 (5.3.0-18.19, 5.3.0-19.20), linux-image-generic:amd64 
(5.3.0.18.21, 5.3.0.19.22), linux-signed-generic:amd64 (5.3.0.18.21, 
5.3.0.19.22), linux-generic:amd64 (5.3.0.18.21, 5.3.0.19.22)
  End-Date: 2019-10-21  08:21:37

  Start-Date: 2019-10-21  11:42:11
  Commandline: aptdaemon role='role-commit-packages' sender=':1.1749'
  Upgrade: libaspell15:amd64 (0.60.7-3, 0.60.7-3ubuntu0.1), aspell:amd64 
(0.60.7-3, 0.60.7-3ubuntu0.1), libexiv2-14:amd64 (0.25-4ubuntu2, 
0.25-4ubuntu2.1)
  Remove: linux-modules-extra-5.0.0-32-generic:amd64 (5.0.0-32.34), 
linux-modules-5.0.0-32-generic:amd64 (5.0.0-32.34), 
linux-image-5.0.0-32-generic:amd64 (5.0.0-32.34)
  End-Date: 2019-10-21  11:42:26

  Start-Date: 2019-10-22  06:19:40
  Commandline: /usr/bin/unattended-upgrade
  Upgrade: libopenjp2-7:amd64 (2.3.0-2, 2.3.0-2build0.19.10.1)
  End-Date: 2019-10-22  06:19:41

  Start-Date: 2019-10-22  19:12:43
  Commandline: aptdaemon role='role-commit-packages' sender=':1.375112'
  Upgrade: google-chrome-stable:amd64 (77.0.3865.120-1, 78.0.3904.70-1), 
xsltproc:amd64 (1.1.33-0ubuntu1, 1.1.33-0ubuntu1.1), libxslt1.1:amd64 
(1.1.33-0ubuntu1, 1.1.33-0ubuntu1.1), libxslt1.1:i386 (1.1.33-0ubuntu1, 
1.1.33-0ubuntu1.1)
  End-Date: 2019-10-22  19:12:59

  Start-Date: 2019-10-24  07:00:54
  Commandline: aptdaemon role='role-commit-packages' sender=':1.660642'
  Upgrade: firefox-locale-en:amd64 (69.0.3+build1-0ubuntu1, 
70.0+build2-0ubuntu0.19.10.1), firefox:amd64 (69.0.3+build1-0ubuntu1, 
70.0+build2-0ubuntu0.19.10.1), linux-firmware:amd64 (1.183, 1.183.1)
  End-Date: 2019-10-24  07:01:58

  Start-Date: 2019-10-29  06:33:22
  Commandline: /usr/bin/unattended-upgrade
  Upgrade: libwbclient0:amd64 (2:4.10.7+dfsg-0ubuntu2, 
2:4.10.7+dfsg-0ubuntu2.2), samba-libs:amd64 (2:4.10.7+dfsg-0ubuntu2, 
2:4.10.7+dfsg-0ubuntu2.2), libsmbclient:amd64 (2:4.10.7+dfsg-0ubuntu2, 
2:4.10.7+dfsg-0ubuntu2.2)
  End-Date: 2019-10-29  06:33:25

  Start-Date: 2019-10-29  07:22:22
  Commandline: /usr/sbin/synaptic
  Requested-By: frohro (1000)
  Install: bluez-tests:amd64 (5.50-0ubuntu4), bluez-tools:amd64 
(2.0~20170911.0.7cb788c-2build1), bluetooth:amd64 (5.50-0ubuntu4)
  End-Date: 2019-10-29  07:22:28

  Start-Date: 2019-10-29  07:44:42
  Commandline: apt install pulseaudio pulseaudio-utils pavucontrol 
pulseaudio-module-bluetooth
  Requested-By: frohro (1000)
  Install: pavucontrol:amd64 (3.0-4)
  End-Date: 2019-10-29  07:44:48

  Nothing I tried solves the issue.  It was working a few days ago.

  Thanks,

  Rob

  ProblemType: Bug
  DistroRelease: Ubuntu 19.

[Desktop-packages] [Bug 1845046] Re: Bluetooth headphones/speaker default to low quality headset mode instead of high quality A2DP and can't be easily changed in Settings

I wonder if there's something special about Sony...

* This bug was reported against Sony WH-1000XM3
* A duplicate bug was reported against Sony MDR-1000x
* I also encountered the bug once using Sony SRS-XB2 speakers

** Summary changed:

- [WH-1000XM3, playback] Hearing input and output audio until disconnecting and 
reconnecting
+ Bluetooth headphones/speaker default to low quality headset mode instead of 
high quality A2DP and can't be easily changed in Settings

** Summary changed:

- Bluetooth headphones/speaker default to low quality headset mode instead of 
high quality A2DP and can't be easily changed in Settings
+ Bluetooth headphones/speaker default to low quality headset mode and fails to 
switch to A2DP when selected

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

Title:
  Bluetooth headphones/speaker default to low quality headset mode and
  fails to switch to A2DP when selected

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

Bug description:
  Whenever I turn on my headphones theyll connect to my computer but im
  able to hear the input audio from my microphone and low quality output
  audio. I have to disconnect the headphones in the bluetooth devices
  and reconnect for it to fix the problem.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: pulseaudio 1:11.1-1ubuntu7.2
  ProcVersionSignature: Ubuntu 5.0.0-29.31~18.04.1-generic 5.0.21
  Uname: Linux 5.0.0-29-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7.7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  litleck1398 F pulseaudio
   /dev/snd/controlC0:  litleck1398 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Sep 23 17:07:59 2019
  InstallationDate: Installed on 2019-09-22 (0 days ago)
  InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 
(20190805)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: pulseaudio
  Symptom: audio
  Symptom_Card: WH-1000XM3
  Symptom_Type: High background noise, or volume is too low
  Title: [WH-1000XM3, playback] Background noise or low volume
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/12/2019
  dmi.bios.vendor: Alienware
  dmi.bios.version: 1.0.19
  dmi.board.name: 01NYPT
  dmi.board.vendor: Alienware
  dmi.board.version: A00
  dmi.chassis.type: 3
  dmi.chassis.vendor: Alienware
  dmi.chassis.version: Not Specified
  dmi.modalias: 
dmi:bvnAlienware:bvr1.0.19:bd02/12/2019:svnAlienware:pnAlienwareAuroraR5:pvr1.0.19:rvnAlienware:rn01NYPT:rvrA00:cvnAlienware:ct3:cvrNotSpecified:
  dmi.product.family: Alienware
  dmi.product.name: Alienware Aurora R5
  dmi.product.sku: 0729
  dmi.product.version: 1.0.19
  dmi.sys.vendor: Alienware

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

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

[Desktop-packages] [Bug 1849371] Re: [snap] Cannot run chromium as user www-data because home directory is /var/www

2019-10-29 Thread RichardNeill

The snap confinement also seems to create a number of other problems.
I've also observed:

* Webmail - if I receive an attachment of certain types (libreoffice is
broken; pdf is OK), then I get a "please confirm you want to allow
chromium to open this file" dialog every single time.

* password manager (save passwords) is broken - it won't remember
passwords I saved, nor does it remember my preference not to save the
passwords for web-development on localhost, but prompts every time.

* cross site logins are broken (sign into gmail for work, and other
sites that use that gmail auth just fail).

* some extensions break (e.g. the JSONViewer is silently-non-
functional.)

All of these are fixed if I download and unzip the binary from here:
https://download-chromium.appspot.com/  - though it sacrifices the entire point 
of running a distro.

I understand the rationale for saving developer time, but this is really
broken for me and my company. If it would help, we'd happily be invoiced
£500 by the Ubuntu project if you could go back to the deb build - even
if you chose only to ship alternate releases.

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

Title:
  [snap] Cannot run chromium as user www-data because home directory is
  /var/www

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

Bug description:
  Since the move to snap, and upgrade to 19.10, I can no longer use
  headless-chromium to do automated conversions.

  The script, as currently run by Apache (user www-data) as a back-end
  server process is:

  /usr/bin/timeout 60 chromium-browser --no-sandbox --headless
  --disable-gpu --window-size=2048,1448 --screenshot='dummy.pdf'
  'http://localhost/[...]' 2>&1 2>&1

  This returns error 1, with:

  dconf-CRITICAL **: 19:41:17.958: unable to create directory
  '/var/www/.cache/dconf': Permission denied.  dconf will not work
  properly.

  WARNING: cannot create user data directory: cannot create 
"/var/www/snap/chromium/899": 
  mkdir /var/www/snap: permission denied
  Sorry, home directories outside of /home are not currently supported.
  See https://forum.snapcraft.io/t/11209 for details.

  So... how are we supposed to use scripted Chrome for headless work, when the 
snaps don't support it?
  This is a major blocker for me, as it completely destroys my ability to do 
any development work, because the build-toolchain for selftests relies on the 
ability of chrome to operate headless.

  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
  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-HDMI-A-1:
   enabled: enabled
   dpms: On
   status: connected
   edid-base64: 
AP///wBMLToINDAxMCsWAQOANCB4KgHxoldSnycKUFS/74BxT4EAgUCBgJUAlQ+pQLMAKDyAoHCwI0AwIDYABkQhAAAa/QA4Sx5REQAKICAgICAg/ABTTVMyNEE0NTAKICAg/wBINE1DQTEzMzYyCiAgAQkCAQQAAjqA0HI4LUAQLEWABkQhAAAeAR0AclHQHiBuKFUABkQhAAAeAR0AvFLQHiC4KFVABkQhAAAejArQkCBAMSAMQFUABkQhAAAYjArQiiDgLRAQPpYABkQhAAAY0g==
   modes: 1920x1200 1920x1080 1600x1200 1680x1050 1280x1024 1280x1024 1440x900 
1440x900 1280x960 1280x800 1152x864 1280x720 1280x720 1280x720 1024x768 
1024x768 1024x768 832x624 800x600 800x600 800x600 800x600 720x576 720x480 
720x480 640x480 640x480 640x480 640x480 640x480 720x400
  DRM.card0-HDMI-A-2:
   enabled: enabled
   dpms: On
   status: connected
   edid-base64: 
AP///wAlpVNWODYxMB0NAQOBKR//6uWVpVhMlyYeUFS/7wCBgKlAMVlFWWFZgZkBAQEBSD9AMGKwMkAAwAMAmDIRAAAe/QA4VR9cEQAKICAgICAg/wBCSEZGS0I2MzAwMTY4/ABMMjBDTQogICAgICAgAMU=
   modes: 1600x1200 1280x1024 1280x1024 1280x1024 1024x768 1024x768 1024x768 
1024x768 832x624 800x600 800x600 800x600 800x600 800x600 640x480 640x480 
640x480 640x480 640x480 720x400
  DRM.card0-HDMI-A-3:
   enabled: enabled
   dpms: On
   status: connected
   edid-base64: 
AP///wAlpVNWNjIyMB0NAQOBKR//6uWVpVhMlyYeUFS/7wCBgKlAMVlFWWFZgZkBAQEBSD9AMGKwMkAAwAMAmDIRAAAe/QA4VR9cEQAKICAgICAg/wBCSEZGS0I2MzAwMjI2/ABMMjBDTQogICAgICAgAM8=
   modes: 1600x1200 1280x1024 1280x1024 1280x1024 1024x768 1024x768 1024x768 
1024x768 832x624 800x600 800x600 800x600 800x600 800x600 640x480 640x480 
640x480 640x480 640x480 720x400
  Date: Tue Oct 22 19:48:51 2019
  DiskUsage:
   Filesystem Type   Size  Used Avail Use% Mounted on
   /dev/sdb1  ext4   1.8T  491G  1.3T  29% /home
   tmpfs  tmpfs   32G  927M   31G   3% /dev/shm
   /dev/sdb1  ext4   1.8T  491

[Desktop-packages] [Bug 1850432] Re: acrually i wanted the graphics driver for my intel 3000 graphics driver for 2nd gen core i3 processor

As Timo said, you already have the latest graphics driver installed for
Intel. It is called 'modeset'.

If there is a particular problem you are trying to fix then please
update this bug to describe that problem.

** Package changed: xorg (Ubuntu) => xorg-server (Ubuntu)

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

Title:
  acrually i wanted the graphics driver for my intel 3000 graphics
  driver for 2nd gen core i3 processor

Status in xorg-server package in Ubuntu:
  Incomplete

Bug description:
  acrually i wanted the graphics driver for my intel 3000 graphics
  driver for 2nd gen core i3 processor

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 5.0.0-32.34~18.04.2-generic 5.0.21
  Uname: Linux 5.0.0-32-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.7
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Oct 29 20:09:47 2019
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: Dell 2nd Generation Core Processor Family Integrated Graphics 
Controller [1028:0591]
  InstallationDate: Installed on 2019-10-29 (0 days ago)
  InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 
(20190805)
  MachineType: Dell Inc. Inspiron 3421
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-32-generic 
root=UUID=caaedd10-467d-46ef-9bc9-df58fb08f913 ro quiet splash vt.handoff=1
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/14/2015
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A13
  dmi.board.name: 0WF4PW
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A13
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: Not Specified
  dmi.modalias: 
dmi:bvnDellInc.:bvrA13:bd12/14/2015:svnDellInc.:pnInspiron3421:pvrNotSpecified:rvnDellInc.:rn0WF4PW:rvrA13:cvnDellInc.:ct8:cvrNotSpecified:
  dmi.product.name: Inspiron 3421
  dmi.product.sku: Inspiron 3421
  dmi.product.version: Not Specified
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.97-1ubuntu1~18.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.8-0ubuntu0~18.04.3
  version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.8-0ubuntu0~18.04.3
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A

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

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

[Desktop-packages] [Bug 1849484] Re: [X1 Carbon 7, i915, HDMI] Ultra-wide monitor recognized properly when plugged in only intermittently [Xorg only]

Thanks. I still feel the first solution we should be aiming for is
(another) new HDMI cable. If you've tried a few (without any adapters!)
and none work then I would treat this as a proper kernel bug. The
closest existing one I have found is:

https://bugs.freedesktop.org/show_bug.cgi?id=105601

** Bug watch added: freedesktop.org Bugzilla #105601
   https://bugs.freedesktop.org/show_bug.cgi?id=105601

** No longer affects: xorg-server (Ubuntu)

** Also affects: linux via
   https://bugs.freedesktop.org/show_bug.cgi?id=105601
   Importance: Unknown
   Status: Unknown

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

Title:
  [X1 Carbon 7, i915, HDMI] Ultra-wide monitor recognized properly when
  plugged in only intermittently [Xorg only]

Status in Linux:
  Unknown
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I have an LG ultra-wide (2560x1080) monitor.

  Sometimes when I plug it into my laptop, whose screen was working fine
  before I plugged it in, both screens go black but nothing else
  happens. I can still see the mouse cursor and move it between the two
  monitors (sometimes in the correct location configuration I've
  configured, sometimes not), but nothing is rendered on the screens.

  Sometimes when I plug the monitor in, it comes on, but the resolution
  is wrong.

  Sometimes it is actually recognized and configured correctly.

  Frequently I have to unplug the monitor and plug it back in three
  times or more before it is recognized correctly.

  I wish it just worked right the first time. :-/

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: gnome-shell 3.34.1-1ubuntu1
  ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
  Uname: Linux 5.3.0-19-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu8
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Oct 23 08:34:07 2019
  DisplayManager: gdm3
  InstallationDate: Installed on 2019-09-12 (40 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  RelatedPackageVersions: mutter-common 3.34.1-1ubuntu1
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to eoan on 2019-09-20 (32 days ago)
  --- 
  ProblemType: Bug
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.11-0ubuntu8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  jik3196 F pulseaudio
   /dev/snd/pcmC1D0p:   jik3196 F...m pulseaudio
   /dev/snd/controlC0:  jik3196 F pulseaudio
  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
  DistUpgraded: 2019-09-20 10:09:14,777 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: eoan
  DistroRelease: Ubuntu 19.10
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation UHD Graphics 620 (Whiskey Lake) [8086:3ea0] (rev 02) 
(prog-if 00 [VGA controller])
 Subsystem: Lenovo UHD Graphics 620 (Whiskey Lake) [17aa:2292]
  InstallationDate: Installed on 2019-09-12 (45 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  MachineType: LENOVO 20QD001VUS
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  Package: xorg-server (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-19-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-19-generic N/A
   linux-backports-modules-5.3.0-19-generic  N/A
   linux-firmware1.183.1
  Tags:  eoan ubuntu
  Uname: Linux 5.3.0-19-generic x86_64
  UpgradeStatus: Upgraded to eoan on 2019-09-20 (38 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers wireshark
  _MarkForUpload: True
  dmi.bios.date: 07/04/2019
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N2HET30W (1.13 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20QD001VUS
  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:bvrN2HET30W(1.13):bd07/04/2019:svnLENOVO:pn20QD001VUS:pvrThinkPadX1Carbon7th:rvnLENOVO:rn20QD001VUS:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad X1 Carbon 7th
  dmi.product.name: 20QD001VUS
  dmi.product.sku: LENOVO_MT_20QD_BU_Think_FM_ThinkPad X1 Carbon 7th
  dmi.product.version: ThinkPad X1 Carbon 7th
  dmi.sys.vendor: LENOVO
  modified.conffile..etc.apport.crashdb.conf: [modified]
  mtime.conffile..etc.apport.cras

[Desktop-packages] [Bug 1849950] Re: Gnome Shell window shortcuts maximize, windowed and hide (Super + Up / Down / H) don't work if upgrading from Unity

Just clarifying for future-me and others that there is no "fix" to look
for.

** Changed in: gsettings-desktop-schemas (Ubuntu)
   Status: Fix Released => Won't Fix

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

Title:
  Gnome Shell window shortcuts maximize, windowed and hide (Super + Up /
  Down / H) don't work if upgrading from Unity

Status in GNOME Shell:
  Fix Released
Status in gsettings-desktop-schemas package in Ubuntu:
  Won't Fix

Bug description:
  Happens on Ubuntu 19.10, and did also not work on Ubuntu 19.04 (and
  probably also previous versions), if I recall correctly.

  I am not sure, whether this is an upstream bug of GNOME or just Ubuntu
  related.

  Bug report for GNOME: https://gitlab.gnome.org/GNOME/gnome-
  shell/issues/1829

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

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

[Desktop-packages] [Bug 1848852] Re: Counter-Strike Global Offensive freezes in gnome-shell

Please comment in the upstream bug instead for now, since that's where
it will be fixed:

https://gitlab.gnome.org/GNOME/gnome-shell/issues/1673

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

Title:
  Counter-Strike Global Offensive freezes in gnome-shell

Status in GNOME Shell:
  New
Status in gnome-shell package in Ubuntu:
  Triaged

Bug description:
  After upgrade to ubuntu 19.10, when I launch counter strike global offensive 
from steam the game is frozen. I can alt-tab and close the game. Tried in 
fluxbox window manager where the game works, changed fullscreen to windowed 
fullscreen in the options and tried on gnome again, now the desktop isn't 
responding after launching the game and I had to ctrl-alt-f3 to reboot my 
machine.
  Using a Radeon RX 580 video card.

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

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

[Desktop-packages] [Bug 1846940]

2019-10-29 Thread julien2412

Adding traces in some functions of the quoted commit, I noticed this block was 
repeted infinitely:
OverlayObject::getOverlayObjectPrimitive2DSequence
OverlayObject::getOverlayObjectPrimitive2DSequence
ViewObjectContact::getPrimitive2DSequence
ViewObjectContact::getGridOffset
ViewObjectContact::getPrimitive2DSequence
ViewObjectContact::getGridOffset
ViewObjectContact::getPrimitive2DSequence
ViewObjectContact::getGridOffset

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

Title:
  [upstream] Loop in libreoffice-calc when scrolling to top of
  spreadsheet

Status in LibreOffice:
  Confirmed
Status in libreoffice package in Ubuntu:
  Confirmed

Bug description:
  Have a spreadsheet used in many past release of calc that is now
  failing.  When opening this sheet and if not currently at the top of
  the sheet using the mouse wheel to move to the top (top line to the
  top of the window) soffice.bin goes to 100% cpu and stays there.
  Can't use the mouse wheel to move off of the top line.  Can move off
  the top line by using the mouse and scroll bar.  As soon as you are
  off the top line the loop in soffice.bin stops.  This is the only
  sheet I can find that fails but it does fail on this laptop and also
  my desktop which is also running Ubuntu 19.10/libreoffice-
  calc-6.3.2.2.  Adding failing spreadsheet file to this bug report.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: libreoffice-calc 1:6.3.2-0ubuntu2
  ProcVersionSignature: Ubuntu 5.3.0-13.14-generic 5.3.0
  Uname: Linux 5.3.0-13-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset 
nvidia
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Oct  6 06:35:42 2019
  InstallationDate: Installed on 2019-10-03 (2 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Beta amd64 (20191001.2)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: libreoffice
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1849615] Re: WebRTC-related crashes

** Changed in: firefox
   Status: Confirmed => 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/1849615

Title:
  WebRTC-related crashes

Status in Mozilla Firefox:
  Fix Released
Status in firefox package in Ubuntu:
  New

Bug description:
  In Mozilla we've detected a spike of crashes in the Ubuntu-packaged
  version of Firefox 69.0.x. All the crashes are happening in the WebRTC
  code and specifically libc's FD_SET, FD_CLR and FD_ISSET range-
  checking safety is causing an abort. Is it possible that Firefox is
  being built with a FD_SETSIZE value that's different from what's used
  in libc?

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

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

[Desktop-packages] [Bug 1849615]

2019-10-29 Thread Ncsoregi

https://hg.mozilla.org/mozilla-central/rev/59fb6760bb67

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

Title:
  WebRTC-related crashes

Status in Mozilla Firefox:
  Fix Released
Status in firefox package in Ubuntu:
  New

Bug description:
  In Mozilla we've detected a spike of crashes in the Ubuntu-packaged
  version of Firefox 69.0.x. All the crashes are happening in the WebRTC
  code and specifically libc's FD_SET, FD_CLR and FD_ISSET range-
  checking safety is causing an abort. Is it possible that Firefox is
  being built with a FD_SETSIZE value that's different from what's used
  in libc?

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

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

[Desktop-packages] [Bug 1849615]

2019-10-29 Thread Gabriele Svelto

Taking this as I've got a WIP patch. It just needs some good testing.

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

Title:
  WebRTC-related crashes

Status in Mozilla Firefox:
  Fix Released
Status in firefox package in Ubuntu:
  New

Bug description:
  In Mozilla we've detected a spike of crashes in the Ubuntu-packaged
  version of Firefox 69.0.x. All the crashes are happening in the WebRTC
  code and specifically libc's FD_SET, FD_CLR and FD_ISSET range-
  checking safety is causing an abort. Is it possible that Firefox is
  being built with a FD_SETSIZE value that's different from what's used
  in libc?

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

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

[Desktop-packages] [Bug 1849615]

2019-10-29 Thread Pulsebot

Pushed by gsve...@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/59fb6760bb67
Use poll() instead of select() in WebRTC code r=drno

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

Title:
  WebRTC-related crashes

Status in Mozilla Firefox:
  Fix Released
Status in firefox package in Ubuntu:
  New

Bug description:
  In Mozilla we've detected a spike of crashes in the Ubuntu-packaged
  version of Firefox 69.0.x. All the crashes are happening in the WebRTC
  code and specifically libc's FD_SET, FD_CLR and FD_ISSET range-
  checking safety is causing an abort. Is it possible that Firefox is
  being built with a FD_SETSIZE value that's different from what's used
  in libc?

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

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

[Desktop-packages] [Bug 1849615]

2019-10-29 Thread Gabriele Svelto

Created attachment 9104623
Bug 1590984 - Use poll() instead of select() in WebRTC code r=drno

The use of select() was leading to crashes when the file descriptor value was
larger than FD_SETSIZE. Recent versions of glibc have checks in the FD_CLR(),
FD_SET() and FD_ISSET() macros that will abort() the program instead of doing
an out-of-bounds access. poll() doesn't have limitations on the file
descriptor values and provides behavior that is otherwise identical to
select() thus solving the problem.

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

Title:
  WebRTC-related crashes

Status in Mozilla Firefox:
  Fix Released
Status in firefox package in Ubuntu:
  New

Bug description:
  In Mozilla we've detected a spike of crashes in the Ubuntu-packaged
  version of Firefox 69.0.x. All the crashes are happening in the WebRTC
  code and specifically libc's FD_SET, FD_CLR and FD_ISSET range-
  checking safety is causing an abort. Is it possible that Firefox is
  being built with a FD_SETSIZE value that's different from what's used
  in libc?

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

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

[Desktop-packages] [Bug 1834566] Re: Samsung Notebook 9 Pro - Internal Speaker Playback problem - HDA Intel - Realtek ALC298

2019-10-29 Thread Filipe Garrett

Here to also report that this issue persists on a newer Samsung laptop.
The model in question is the Notebook 7 Force NP760XBE(Style S51 Pro on
some countries) running 19.10. In my case, the speakers work fine,
though. The problem only manifests itself through headphones: very faint
and distorted sound.

I've reported it everywhere support-wise and posted it as a question here, on 
Launchpad:
https://answers.launchpad.net/ubuntu/+question/685478

My alsa-info output file could be found here: http://alsa-
project.org/db/?f=f7aa21f8fde284a2b2eb1d08524b6eb67d45bdfb

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

Title:
  Samsung Notebook 9 Pro - Internal Speaker Playback problem - HDA Intel
  - Realtek ALC298

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  Unable to get system speakers working running 19.04.  At max volume,
  sound is barely perceptible through headphones.  Pavucontrol shows
  sounds is present, but no amount of adjustments makes a difference.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.0.0-20.21-generic 5.0.8
  Uname: Linux 5.0.0-20-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  robert 3355 F pulseaudio
  CurrentDesktop: KDE
  Date: Fri Jun 28 00:44:13 2019
  InstallationDate: Installed on 2019-06-05 (22 days ago)
  InstallationMedia: Kubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_Jack: Digital Out, HDMI
  Symptom_Type: None of the above
  Title: [930MBE, Intel Kabylake HDMI, Digital Out, HDMI] Playback problem
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/25/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P02AHK.029.190425.PS
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: NP930MBE-K04US
  dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.board.version: SGL9872A0S-C01-G001-S0001+10.0.17763
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 31
  dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP02AHK.029.190425.PS:bd04/25/2019:svnSAMSUNGELECTRONICSCO.,LTD.:pn930MBE:pvrP02AHK:rvnSAMSUNGELECTRONICSCO.,LTD.:rnNP930MBE-K04US:rvrSGL9872A0S-C01-G001-S0001+10.0.17763:cvnSAMSUNGELECTRONICSCO.,LTD.:ct31:cvrN/A:
  dmi.product.family: Notebook 9 Series
  dmi.product.name: 930MBE
  dmi.product.sku: SCAI-A5A5-A5A5-A5A5-PAHK
  dmi.product.version: P02AHK
  dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.

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

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

[Desktop-packages] [Bug 1850563] Re: Google Search via Microphone says No Internet Connection

2019-10-29 Thread Paul White

Same here.

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

** Summary changed:

- Google Search via Microphone says No Internet Connection
+ [snap] Google Search via Microphone says No Internet Connection

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

Title:
  [snap] Google Search via Microphone says No Internet Connection

Status in chromium-browser package in Ubuntu:
  Confirmed

Bug description:
  In Ubuntu 19.10, I have Chromium installed via this snap package:
  sudo snap install chromium

  With a working internet connect, if I attempt to search google, using
  the microphone-icon (on the right-side of the google search box), it
  says I do not have an internet connection.

  Video: https://youtu.be/pNDKydvUL74

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

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

[Desktop-packages] [Bug 1850563] [NEW] Google Search via Microphone says No Internet Connection

2019-10-29 Thread Lonnie Lee Best

Public bug reported:

In Ubuntu 19.10, I have Chromium installed via this snap package:
sudo snap install chromium

With a working internet connect, if I attempt to search google, using
the microphone-icon (on the right-side of the google search box), it
says I do not have an internet connection.

Video: https://youtu.be/pNDKydvUL74

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


** Tags: 19.10 eoan 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/1850563

Title:
  Google Search via Microphone says No Internet Connection

Status in chromium-browser package in Ubuntu:
  New

Bug description:
  In Ubuntu 19.10, I have Chromium installed via this snap package:
  sudo snap install chromium

  With a working internet connect, if I attempt to search google, using
  the microphone-icon (on the right-side of the google search box), it
  says I do not have an internet connection.

  Video: https://youtu.be/pNDKydvUL74

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

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

[Desktop-packages] [Bug 1726129] Re: nautilus crashed with SIGSEGV in widget_needs_widget_path

2019-10-29 Thread El jinete sin cabeza

** Tags added: focal

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

Title:
  nautilus crashed with SIGSEGV in widget_needs_widget_path

Status in Nautilus:
  New
Status in gtk+3.0 package in Ubuntu:
  New
Status in nautilus package in Ubuntu:
  Triaged

Bug description:
  https://gitlab.gnome.org/GNOME/nautilus/issues/1190

  ---

  https://errors.ubuntu.com/problem/7c06cf06fd970ce31033f0d775b3adf97559e4ea

  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: nautilus 1:3.26.0-0ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: Budgie:GNOME
  Date: Sun Oct 22 15:30:05 2017
  ExecutablePath: /usr/bin/nautilus
  InstallationDate: Installed on 2017-10-19 (3 days ago)
  InstallationMedia: Ubuntu-Budgie 17.10 "Artful Aardvark" - Release amd64 
(20171017.1)
  ProcCmdline: nautilus --new-window
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SegvAnalysis:
   Segfault happened at: 0x7fe0115bd2a4:mov0x380(%rax),%rax
   PC (0x7fe0115bd2a4) ok
   source "0x380(%rax)" (0x0380) not located in a known VMA region (needed 
readable region)!
   destination "%rax" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: nautilus
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
  Title: nautilus crashed with SIGSEGV
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

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

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

[Desktop-packages] [Bug 1849774] Re: [snap] mailto: links don't work in chromium

2019-10-29 Thread Olivier Tilloy

An exception was added for chromium to be allowed to symlink /usr/bin
/xdg-open in the review tools (see https://git.launchpad.net/review-
tools/commit/?id=31c894178a8fd110b9f65f0ee532b7e11384f8b8).

Waiting for this to be released.

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

Title:
  [snap] mailto: links don't work in chromium

Status in chromium-browser package in Ubuntu:
  Fix Committed

Bug description:
  href="mailto:xyz"; links don't work in the chromium snap package
  anymore to open an external email client.

  It used to work fine in the non-snap Chromium deb package, before
  Ubuntu 19.10.

  In settings, if enabling "Allow sites to ask to become default
  handlers for protocols (recommended)", it is possible to set Gmail to
  be the default mailto handler, which works. But there seems to be no
  way to make the chromium snap open Evolution, Thunderbird or other
  external programs.

  Mailtos work fine in Firefox and chromium-based Brave browser (which
  pops up an xdg-open confirmation dialog box when a mailto link is
  clicked).

  Chromium Version 77.0.3865.120 (Official Build) snap (64-bit)
  Ubuntu Budgie 19.10, gnome 3.34.1

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

-- 
Mailing list: https://launchpad.net/~desktop-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

You should be able to install the debs from the newest Ubuntu serie for testing
https://launchpad.net/ubuntu/+source/network-manager-l2tp/1.2.14-1/+build/17969079

The new versions are not only bugfixes so might not comply for SRUing
but we backport a fix

-- 
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 L2TP over IPsec VPN Manager:
  New
Status in NetworkManager:
  New
Status in strongSwan:
  New
Status in gnome-control-center package in Ubuntu:
  Incomplete

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)

[Desktop-packages] [Bug 1849371] Re: [snap] Cannot run chromium as user www-data because home directory is /var/www

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.

I'm marking this as confirmed but I think it's going to be de-duplicated
in another pass. There's already a bug for this.

** Also affects: snapd
   Importance: Undecided
   Status: New

** Changed in: snapd
   Status: New => Confirmed

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

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

Title:
  [snap] Cannot run chromium as user www-data because home directory is
  /var/www

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

Bug description:
  Since the move to snap, and upgrade to 19.10, I can no longer use
  headless-chromium to do automated conversions.

  The script, as currently run by Apache (user www-data) as a back-end
  server process is:

  /usr/bin/timeout 60 chromium-browser --no-sandbox --headless
  --disable-gpu --window-size=2048,1448 --screenshot='dummy.pdf'
  'http://localhost/[...]' 2>&1 2>&1

  This returns error 1, with:

  dconf-CRITICAL **: 19:41:17.958: unable to create directory
  '/var/www/.cache/dconf': Permission denied.  dconf will not work
  properly.

  WARNING: cannot create user data directory: cannot create 
"/var/www/snap/chromium/899": 
  mkdir /var/www/snap: permission denied
  Sorry, home directories outside of /home are not currently supported.
  See https://forum.snapcraft.io/t/11209 for details.

  So... how are we supposed to use scripted Chrome for headless work, when the 
snaps don't support it?
  This is a major blocker for me, as it completely destroys my ability to do 
any development work, because the build-toolchain for selftests relies on the 
ability of chrome to operate headless.

  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
  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-HDMI-A-1:
   enabled: enabled
   dpms: On
   status: connected
   edid-base64: 
AP///wBMLToINDAxMCsWAQOANCB4KgHxoldSnycKUFS/74BxT4EAgUCBgJUAlQ+pQLMAKDyAoHCwI0AwIDYABkQhAAAa/QA4Sx5REQAKICAgICAg/ABTTVMyNEE0NTAKICAg/wBINE1DQTEzMzYyCiAgAQkCAQQAAjqA0HI4LUAQLEWABkQhAAAeAR0AclHQHiBuKFUABkQhAAAeAR0AvFLQHiC4KFVABkQhAAAejArQkCBAMSAMQFUABkQhAAAYjArQiiDgLRAQPpYABkQhAAAY0g==
   modes: 1920x1200 1920x1080 1600x1200 1680x1050 1280x1024 1280x1024 1440x900 
1440x900 1280x960 1280x800 1152x864 1280x720 1280x720 1280x720 1024x768 
1024x768 1024x768 832x624 800x600 800x600 800x600 800x600 720x576 720x480 
720x480 640x480 640x480 640x480 640x480 640x480 720x400
  DRM.card0-HDMI-A-2:
   enabled: enabled
   dpms: On
   status: connected
   edid-base64: 
AP///wAlpVNWODYxMB0NAQOBKR//6uWVpVhMlyYeUFS/7wCBgKlAMVlFWWFZgZkBAQEBSD9AMGKwMkAAwAMAmDIRAAAe/QA4VR9cEQAKICAgICAg/wBCSEZGS0I2MzAwMTY4/ABMMjBDTQogICAgICAgAMU=
   modes: 1600x1200 1280x1024 1280x1024 1280x1024 1024x768 1024x768 1024x768 
1024x768 832x624 800x600 800x600 800x600 800x600 800x600 640x480 640x480 
640x480 640x480 640x480 720x400
  DRM.card0-HDMI-A-3:
   enabled: enabled
   dpms: On
   status: connected
   edid-base64: 
AP///wAlpVNWNjIyMB0NAQOBKR//6uWVpVhMlyYeUFS/7wCBgKlAMVlFWWFZgZkBAQEBSD9AMGKwMkAAwAMAmDIRAAAe/QA4VR9cEQAKICAgICAg/wBCSEZGS0I2MzAwMjI2/ABMMjBDTQogICAgICAgAM8=
   modes: 1600x1200 1280x1024 1280x1024 1280x1024 1024x768 1024x768 1024x768 
1024x768 832x624 800x600 800x600 800x600 800x600 800x600 640x480 640x480 
640x480 640x480 640x480 720x400
  Date: Tue Oct 22 19:48:51 2019
  DiskUsage:
   Filesystem Type   Size  Used Avail Use% Mounted on
   /dev/sdb1  ext4   1.8T  491G  1.3T  29% /home
   tmpfs  tmpfs   32G  927M   31G   3% /dev/shm
   /dev/sdb1  ext4   1.8T  491G  1.3T  29% /home
  InstallationDate: Installed on 2017-02-03 (991 days ago)
  InstallationMedia: Ubuntu-MATE 17.04 "Zesty Zapus" - Alpha amd64 (20170125)
  MachineType: System manufacturer System Product Name
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-19-generic 
root=UUID=6ef42be7-d431-4d0d-bc57-79f7a96980ef ro
  Snap.ChromeDriverVersion:
   ERROR: ld.so: object 'libgtk3-nocsd.so.0' from LD_PRELOAD cannot be 
preloaded (failed to map segment from shared object): ignored.
   ChromeDriver 77.0.3865.120 
(416d6d8013e9adb6dd33b0c12e7614ff403d1a94-refs/branch-heads/3865@{#884})
  Snap.ChromiumVersion:
   ERROR: ld.so: object 'libgtk3-nocsd.so.0' fro

[Desktop-packages] [Bug 1848753] Re: [snap] chromium times out connecting document portal with NFS home

** Changed in: snapd
   Status: New => Triaged

** Changed in: snapd
   Importance: Undecided => Medium

** Changed in: snapd (Ubuntu)
   Status: New => Triaged

** Changed in: snapd (Ubuntu)
   Importance: Undecided => Medium

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

Title:
  [snap] chromium times out connecting document portal with NFS home

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

Bug description:
  I have my /home folder shared via NFS from a local server one floor
  below in my house. The server runs Ubuntu 18.04.

  After starting a snapped version of chromium-browser in my Ubuntu
  19.10 the document portal timeouts like this:

  XXX@koira:~$ chromium-browser
  2019/10/18 18:51:27.986444 cmd_run.go:893: WARNING: cannot start document 
portal: Failed to activate service 'org.freedesktop.portal.Documents': timed 
out (service_start_timeout=12ms)

  After the timeout my chromium cannot seem to remember accounts or
  passwords.

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

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

[Desktop-packages] [Bug 1849774] Re: [snap] mailto: links don't work in chromium

2019-10-29 Thread Olivier Tilloy

Unfortunately the resulting snap fails the store automated review (see
bug #1850553).

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

Title:
  [snap] mailto: links don't work in chromium

Status in chromium-browser package in Ubuntu:
  Fix Committed

Bug description:
  href="mailto:xyz"; links don't work in the chromium snap package
  anymore to open an external email client.

  It used to work fine in the non-snap Chromium deb package, before
  Ubuntu 19.10.

  In settings, if enabling "Allow sites to ask to become default
  handlers for protocols (recommended)", it is possible to set Gmail to
  be the default mailto handler, which works. But there seems to be no
  way to make the chromium snap open Evolution, Thunderbird or other
  external programs.

  Mailtos work fine in Firefox and chromium-based Brave browser (which
  pops up an xdg-open confirmation dialog box when a mailto link is
  clicked).

  Chromium Version 77.0.3865.120 (Official Build) snap (64-bit)
  Ubuntu Budgie 19.10, gnome 3.34.1

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

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

[Desktop-packages] [Bug 1251281] Re: gnome-session-flashback/Unity fails to start without hardware acceleration in cloud/remote environments (Forwarded-X/XRDP/VNC/NX/X2GO/Chromoting)

2019-10-29 Thread Peter Bennett

Xubuntu should be OK. I have no problems with it. Try this -
https://catch22cats.blogspot.com/2018/05/xrdp-blank-screen-with-
ubuntu-1804.html

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

Title:
  gnome-session-flashback/Unity fails to start without hardware
  acceleration in cloud/remote environments
  (Forwarded-X/XRDP/VNC/NX/X2GO/Chromoting)

Status in gnome-session:
  Fix Released
Status in gnome-session package in Ubuntu:
  Fix Released
Status in gnome-session source package in Trusty:
  Fix Released
Status in gnome-session source package in Utopic:
  Fix Released
Status in gnome-flashback source package in Vivid:
  Fix Released
Status in gnome-session source package in Vivid:
  Fix Released
Status in gnome-session package in Debian:
  New

Bug description:
  == Impact ==
  It was impossible to launch a gnome-session-based desktop on a system where 
hardware accelerations is not available (such as old hardware, or when using a 
remote desktop).

  That looks like a quite popular use case — more than a hundred of
  people marked this bug as affecting them.

  == Test Case ==
  The original bug description below contains a test case.

  == Proposed Fix ==
  The fix backports an upstream commit which adds --disable-acceleration-check 
commandline option, and makes Upstart user session pass that flag to 
gnome-session when the session is gnome-fallback (aka 
gnome-flashback-metacity). Of course, that option can be used with other 
sessions as well.

  This was fixed in vivid in version 3.14.0-2ubuntu4.

  == Regression Potential ==
  The option was accepted upstream, and nobody complained so far. So the 
regression potential should be low.

  This bug will cause static grey or black screen instead of opening
  remote session using Forwarded-X/XRDP/VNC/NX/X2GO/Chromoting from
  x2goclient, rdpclient(reminna/vinagre/mstsc), SSH, VNC, NOMACHINE and
  etc.

  == Original Description ==
  1) lsb_release -rd
  Description:  Ubuntu 14.04 LTS
  Release:  14.04

  2) apt-cache policy gnome-session
  gnome-session:
    Installed: 3.9.90-0ubuntu12
    Candidate: 3.9.90-0ubuntu12
    Version table:
   *** 3.9.90-0ubuntu12 0
  500 http://us.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages
  100 /var/lib/dpkg/status

  3) What is expected to happen is when one installs xrdp on the host
  and attempts to use remmina or vinagre on a Ubuntu 14.04 client to RDP
  in, it works.

  4) What happens instead is it shows a gray static screen as per attached 
screenshot. This would appear an issue with gnome-session as per client log:
  cat .xsession-errors.old
  Script for ibus started at run_im.
  Script for auto started at run_im.
  Script for default started at run_im.
  init: indicator-application main process ended, respawning
  init: indicator-application main process ended, respawning
  init: indicator-application respawning too fast, stopped
  Xsession: X session started for  at Sun Jul 20 15:25:59 CDT 2014
  X Error of failed request:  BadValue (integer parameter out of range for 
operation)
    Major opcode of failed request:  109 (X_ChangeHosts)
    Value in failed request:  0x5
    Serial number of failed request:  6
    Current serial number in output stream:  8
  localuser:moniker being added to access control list
  X Error of failed request:  BadValue (integer parameter out of range for 
operation)
    Major opcode of failed request:  109 (X_ChangeHosts)
    Value in failed request:  0x5
    Serial number of failed request:  6
    Current serial number in output stream:  8
  Script for ibus started at run_im.
  Script for auto started at run_im.
  Script for default started at run_im.
  Script for ibus started at run_im.
  Script for auto started at run_im.
  Script for default started at run_im.
  gnome-session-is-accelerated: No composite extension.
  gnome-session-check-accelerated: Helper exited with code 256
  gnome-session-is-accelerated: No composite extension.
  gnome-session-check-accelerated: Helper exited with code 256

  ** (process:2565): WARNING **: software acceleration check failed:
  Child process exited with code 1

  ** (x-session-manager:2565): CRITICAL **: We failed, but the fail
  whale is dead. Sorry

  The following is not a WORKAROUND, create /etc/xorg.conf :
  Section "Device"
     Identifier  "Intel Graphics"
     Driver  "Intel"
     Option  "DRI" "False"
  EndSection

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: gnome-session 3.9.90-0ubuntu12
  ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4
  Uname: Linux 3.13.0-32-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sun Jul 20 15:35:23 2014
  InstallationDate: Installed on 2014-06-22 (28 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  PackageArchitec

[Desktop-packages] [Bug 1844853] Re: IBus no longer works in Qt applications after upgrade

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

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

Title:
  IBus no longer works in Qt applications after upgrade

Status in GLib:
  Fix Released
Status in ibus:
  Fix Released
Status in glib2.0 package in Ubuntu:
  Confirmed
Status in ibus package in Ubuntu:
  Fix Released
Status in ibus package in Debian:
  Confirmed

Bug description:
  Kubuntu Release 18.04.3 LTS

  Expected behavior:
  ibus continues working as before after applying security update 
1.5.17-ubuntu5.1 from version 1.5.17-ubuntu5.

  Observed behavior:
  ibus is not usable anymore in Qt applications.

  After updating ibus and the related packages ibus-gtk, ibus-gtk3, 
libibus-1.0-5 and gir1.2-ibus-1.0 all from version 1.5.17-ubuntu5 to 
1.5.17-ubuntu5.1, I can no longer use ibus in Qt applications. Using 
shift-space no longer changes the selected input method and even when i switch 
to the mozc input method in a gtk application, i can not use it in any Qt 
applications.
  When starting qtconfig in a terminal, I also get the following message:

  Bus::open: Connect ibus failed! 
  IBusInputContext::createInputContext: no connection to ibus-daemon

  This bug was not present in version 1.5.17-3ubuntu5 and I also
  confirmed that downgrading the packages to version 1.5.17-3ubuntu4
  restores ibus functionality in Qt applications.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: ibus 1.5.17-3ubuntu5.1
  ProcVersionSignature: Ubuntu 5.0.0-30.32~18.04.1-generic 5.0.21
  Uname: Linux 5.0.0-30-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7.7
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Sat Sep 21 07:58:56 2019
  InstallationDate: Installed on 2019-06-28 (84 days ago)
  InstallationMedia: Kubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  SourcePackage: ibus
  UpgradeStatus: No upgrade log present (probably fresh install)

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

-- 
Mailing list: https://launchpad.net/~desktop-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-10-29 Thread mark kowski

Also I attach crash report from fiferox/profile/crashes folder (I don't
know if it helps but more info is better).

** Attachment added: "76339522-5628-c2f7-1570-0a30605df90f"
   
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1850529/+attachment/5301239/+files/76339522-5628-c2f7-1570-0a30605df90f

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

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",
  T

[Desktop-packages] [Bug 1661590] Re: GNOME Software only supports running one application from a snap

I just tried to reproduce the bug as outlined in the bug description. I
can confirm it is now fixed and working as expected. I'm marking the
snappy task as fix released.

** Changed in: snappy
   Status: In Progress => Fix Released

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

Title:
  GNOME Software only supports running one application from a snap

Status in GNOME Software:
  Fix Released
Status in Snappy:
  Fix Released
Status in gnome-software package in Ubuntu:
  Fix Released
Status in gnome-software source package in Xenial:
  Fix Released
Status in gnome-software source package in Artful:
  Won't Fix
Status in gnome-software source package in Bionic:
  Fix Released

Bug description:
  HOW TO REPRODUCE:

  1. Install LibreOffice snap ('nonfree' tag) from Ubuntu Software.
  2. Click on the 'Launch' button once you have it installed.

  WHAT IS EXPECTED: 
  It should launch the LibreOffice wizard instead of any of Writer, Calc, etc.

  WHAT ACTUALLY HAPPENS: 
  It launches LibreOffice Database.

  
  WHY THIS HAPPENS?

  Ubuntu Software probably picks the first listed command
  (libreoffice.base), as shown in

  $ snap info libreoffice
  name:  libreoffice
  summary:   "LibreOffice is a powerful office suite including word processing 
and creation of spreadsheets, slideshows and databases"
  publisher: canonical
  description: |
LibreOffice is a powerful office suite – its clean interface and
feature-rich tools help you unleash your creativity and enhance your
productivity. LibreOffice includes several applications that make it the 
most
powerful Free and Open Source office suite on the market: Writer (word
processing), Calc (spreadsheets), Impress (presentations), Draw (vector
graphics and flowcharts), Base (databases), and Math (formula editing).
  commands:
- libreoffice.base
- libreoffice.calc
- libreoffice.draw
- libreoffice.impress
- libreoffice
- libreoffice.math
- libreoffice.writer
  tracking:stable
  installed:   5.3.0.3 (17) 374MB -
  refreshed:   2017-02-01 20:51:51 +0200 EET
  channels: 
stable:5.3.0.3 (17) 374MB -
candidate: 5.3.0.3 (17) 374MB -
beta:  5.3.0.3 (17) 374MB -
edge:  5.3.0.3 (17) 374MB -

  
  The order in snapcraft.yaml is different, so probably Snapcraft is changing 
the order (it might assume that 'libreoffice' is 'libreoffice.libreoffice', so 
it puts it further down.

  Here is snapcraft.yaml: https://git.launchpad.net/~bjoern-michaelsen
  /df-libreoffice/+git/libreoffice-snap-
  playground/tree/snapcraft.yaml?h=xenial

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

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

[Desktop-packages] [Bug 1848753] Re: [snap] chromium times out connecting document portal with NFS home

Ah, forgive me.

I think this bug requires someone to sit down and attempt to reproduce
it in a controlled environment. I cannot commit to do that anytime soon
as we have a number of open bugs, features we promised to deliver and a
handful of people working on the project.

I'd like to keep the bug open for the next pass of bug review that will
be done by another engineer. We are working towards reducing the number
of NEW, INPROGRESS and finally OPEN bugs so that we can devote more
attention to particular cases and work on debugging them properly.

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

Title:
  [snap] chromium times out connecting document portal with NFS home

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

Bug description:
  I have my /home folder shared via NFS from a local server one floor
  below in my house. The server runs Ubuntu 18.04.

  After starting a snapped version of chromium-browser in my Ubuntu
  19.10 the document portal timeouts like this:

  XXX@koira:~$ chromium-browser
  2019/10/18 18:51:27.986444 cmd_run.go:893: WARNING: cannot start document 
portal: Failed to activate service 'org.freedesktop.portal.Documents': timed 
out (service_start_timeout=12ms)

  After the timeout my chromium cannot seem to remember accounts or
  passwords.

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

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

[Desktop-packages] [Bug 1848753] Re: [snap] chromium times out connecting document portal with NFS home

2019-10-29 Thread Juho L

As I tried to decsribe, that was only after I created an empty db with
executing "touch /home/XXX/.local/share/flatpak/db/documents". Please
ignore that.

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

Title:
  [snap] chromium times out connecting document portal with NFS home

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

Bug description:
  I have my /home folder shared via NFS from a local server one floor
  below in my house. The server runs Ubuntu 18.04.

  After starting a snapped version of chromium-browser in my Ubuntu
  19.10 the document portal timeouts like this:

  XXX@koira:~$ chromium-browser
  2019/10/18 18:51:27.986444 cmd_run.go:893: WARNING: cannot start document 
portal: Failed to activate service 'org.freedesktop.portal.Documents': timed 
out (service_start_timeout=12ms)

  After the timeout my chromium cannot seem to remember accounts or
  passwords.

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

-- 
Mailing list: https://launchpad.net/~desktop-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] [NEW] Ubuntu 19.10 gnome-shell crashes after changing keyboard

2019-10-29 Thread Misaka Mikoto

Public bug reported:

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.

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


** Tags: eoan gnome mutter

-- 
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 package in Ubuntu:
  New

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/ubuntu/+source/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 1838008] Re: [snap] cursor theme isn't respected

2019-10-29 Thread Joel Linn

Broken on KDE by default.

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

Title:
  [snap] cursor theme isn't respected

Status in chromium-browser package in Ubuntu:
  Confirmed

Bug description:
  (initially reported at https://discourse.ubuntu.com/t/call-for-
  testing-chromium-browser-deb-to-snap-transition/11179/85)

  When changing the cursor theme with gnome-tweaks, I can observe that
  some themes aren't respected in the chromium snap. This appears to be
  specific to chromium, other snaps like evince or gimp use the correct
  cursors.

  Yaru and Adwaita are fine, but Redglass or Whiteglass aren't.

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

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

[Desktop-packages] [Bug 1850432] Re: acrually i wanted the graphics driver for my intel 3000 graphics driver for 2nd gen core i3 processor

2019-10-29 Thread Timo Aaltonen

Why? The default for your GPU is 'modeset'.

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

Title:
  acrually i wanted the graphics driver for my intel 3000 graphics
  driver for 2nd gen core i3 processor

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  acrually i wanted the graphics driver for my intel 3000 graphics
  driver for 2nd gen core i3 processor

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 5.0.0-32.34~18.04.2-generic 5.0.21
  Uname: Linux 5.0.0-32-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.7
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Oct 29 20:09:47 2019
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: Dell 2nd Generation Core Processor Family Integrated Graphics 
Controller [1028:0591]
  InstallationDate: Installed on 2019-10-29 (0 days ago)
  InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 
(20190805)
  MachineType: Dell Inc. Inspiron 3421
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-32-generic 
root=UUID=caaedd10-467d-46ef-9bc9-df58fb08f913 ro quiet splash vt.handoff=1
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/14/2015
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A13
  dmi.board.name: 0WF4PW
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A13
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: Not Specified
  dmi.modalias: 
dmi:bvnDellInc.:bvrA13:bd12/14/2015:svnDellInc.:pnInspiron3421:pvrNotSpecified:rvnDellInc.:rn0WF4PW:rvrA13:cvnDellInc.:ct8:cvrNotSpecified:
  dmi.product.name: Inspiron 3421
  dmi.product.sku: Inspiron 3421
  dmi.product.version: Not Specified
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.97-1ubuntu1~18.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.8-0ubuntu0~18.04.3
  version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.8-0ubuntu0~18.04.3
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A

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

-- 
Mailing list: https://launchpad.net/~desktop-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] [NEW] Crash after update to 71.0~b5+build1-0ubuntu0.16.04.1

2019-10-29 Thread mark kowski

Public bug reported:

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

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

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

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

Status in firefox package in Ubuntu:
  New

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 sa

[Desktop-packages] [Bug 1849987] Re: empty space when on list view and when back to icon view

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

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

Title:
  empty space when on list view and when back to icon view

Status in Nautilus:
  Fix Released
Status in nautilus package in Ubuntu:
  Invalid

Bug description:
  Description: Ubuntu 19.10
  Release: 19.10

  nautilus:
Installed: 1:3.34.1-1ubuntu1
Candidate: 1:3.34.1-1ubuntu1

  Expected behavior:

  - (1) Open nautilus in list view OR (2) Open Nautilus in icon view and then 
switch to list view
  - List view occupies all the space between the top bar and the bottom.
  - Switch to icon view
  - Icon view occupies all the space between the top bar and the bottom.

  Actual Behavior

  - (1) Open nautilus in list view OR (2) Open Nautilus in icon view and then 
switch to list view
  - List view occupies approximately 55% of the space between the top bar and 
the bottom. Approximately 45% of the space between the top bar and the bottom 
is blank (the upmost part).
  - Switch to icon view
  - Icon view occupies approximately 55% of the space between the top bar and 
the bottom. Approximately 45% of the space between the top bar and the bottom 
is blank (the upmost part).

  Observations:
  - The side bar doesn't seem to affect the bug.
  - By Starting nautilus in icon view the bug doesn't occur. In this case it's 
only triggered when switching to list view.
  - There are only 2 known ways to revert the bug: (1) when on icon view, 
clicking on "Other Locations", and then back to any section. (2) by restarting 
nautilus. There is no known way to revert the bug in list view.

  I am on Ubuntu 19.10 64Bit Using Gnome and Gnome Shell
  3.34.1-1ubuntu1.

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

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

[Desktop-packages] [Bug 1848753] Re: [snap] chromium times out connecting document portal with NFS home

It seems that loka 29 20:02:33 koira xdg-document-portal[16225]: error: Failed 
to load db: invalid gvdb header
 is relevant. I wonder if the database, whatever the format, is somehow corrupt.

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

Title:
  [snap] chromium times out connecting document portal with NFS home

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

Bug description:
  I have my /home folder shared via NFS from a local server one floor
  below in my house. The server runs Ubuntu 18.04.

  After starting a snapped version of chromium-browser in my Ubuntu
  19.10 the document portal timeouts like this:

  XXX@koira:~$ chromium-browser
  2019/10/18 18:51:27.986444 cmd_run.go:893: WARNING: cannot start document 
portal: Failed to activate service 'org.freedesktop.portal.Documents': timed 
out (service_start_timeout=12ms)

  After the timeout my chromium cannot seem to remember accounts or
  passwords.

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

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

[Desktop-packages] [Bug 1647285] Re: SSL trust not system-wide

2019-10-29 Thread Kevin

@dwmw2,

I figured out the issue. Long story short, freeipa (which is our CA),
when we enroll a PC into the realm, it adds the freeIPA cert to
/etc/ssl/certs/ca-certificates.crt like it should, however it also adds
other information that it shouldn't.

This results in p11-kit-trust.so blowing parsing errors.

You can read the entire bug report here if you want.

https://pagure.io/freeipa/issue/8106

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

Title:
  SSL trust not system-wide

Status in ca-certificates package in Ubuntu:
  Confirmed
Status in nss package in Ubuntu:
  Confirmed
Status in p11-kit package in Ubuntu:
  Confirmed
Status in thunderbird package in Ubuntu:
  Confirmed

Bug description:
  When I install a corporate CA trust root with update-ca-certificates,
  it doesn't seem to work everywhere. Various things like Firefox,
  Evolution, Chrome, etc. all fail to trust the newly-installed trusted
  CA.

  This ought to work, and does on other distributions. In p11-kit there
  is a module p11-kit-trust.so which can be used as a drop-in
  replacement for NSS's own libnssckbi.so trust root module, but which
  reads from the system's configured trust setup instead of the hard-
  coded version.

  This allows us to install the corporate CAs just once, and then file a
  bug against any package that *doesn't* then trust them.

  See https://fedoraproject.org/wiki/Features/SharedSystemCertificates
  for some of the historical details from when this feature was first
  implemented, but this is all now supported upstream and not at all
  distribution-specific. There shouldn't be any significant work
  required; it's mostly just a case of configuring and building it to
  make use of this functionality. (With 'alternatives' to let you
  substitute p11-kit-trust.so for the original NSS libnssckbi.so, etc.)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ca-certificates/+bug/1647285/+subscriptions

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

[Desktop-packages] [Bug 1848753] Re: [snap] chromium times out connecting document portal with NFS home

2019-10-29 Thread Juho L

There does not seem to be anything relevant in the server NFS logs. I
can try harder, I can try to add verbose and check that the logs are
actually being produced, if this does not seem to lead us to the problem
source:

With "journalctl -f" only, I can get the following messages. A lot of
them seem to be related to document portal. I checked the file
flatbak/db/documents and it does not seem to exist.

loka 29 19:44:23 koira dbus-daemon[4642]: [session uid=1000 pid=4642] 
Activating via systemd: service name='org.freedesktop.portal.Documents' 
unit='xdg-document-portal.service' requested by ':1.196' (uid=1000 pid=14113 
comm="/snap/bin/chromium " label="unconfined")
loka 29 19:44:23 koira systemd[4622]: Starting flatpak document portal 
service...
loka 29 19:44:23 koira xdg-document-portal[14171]: error: Failed to load db: 
Error opening file /home/XXX/.local/share/flatpak/db/documents: No such file or 
directory
loka 29 19:44:23 koira systemd[4622]: xdg-document-portal.service: Main process 
exited, code=exited, status=2/INVALIDARGUMENT
loka 29 19:44:23 koira systemd[4622]: xdg-document-portal.service: Failed with 
result 'exit-code'.
loka 29 19:44:23 koira systemd[4622]: Failed to start flatpak document portal 
service.
loka 29 19:44:39 koira xdg-desktop-por[4802]: Failed to get application states: 
GDBus.Error:org.freedesktop.portal.Error.Failed: Could not get window list: 
GDBus.Error:org.freedesktop.DBus.Error.AccessDenied: App introspection not 
allowed
loka 29 19:45:39 koira xdg-desktop-por[4802]: Failed to get application states: 
GDBus.Error:org.freedesktop.portal.Error.Failed: Could not get window list: 
GDBus.Error:org.freedesktop.DBus.Error.AccessDenied: App introspection not 
allowed
loka 29 19:46:23 koira dbus-daemon[4642]: [session uid=1000 pid=4642] Failed to 
activate service 'org.freedesktop.portal.Documents': timed out 
(service_start_timeout=12ms)
loka 29 19:46:24 koira audit[1013]: USER_AVC pid=1013 uid=105 auid=4294967295 
ses=4294967295 msg='apparmor="DENIED" operation="dbus_method_call"  
bus="system" path="/" interface="org.freedesktop.DBus.ObjectManager" 
member="GetManagedObjects" mask="send" name="org.bluez" pid=14113 
label="snap.chromium.chromium"
 exe="/usr/bin/dbus-daemon" sauid=105 
hostname=? addr=? terminal=?'
loka 29 19:46:24 koira kernel: audit: type=1107 audit(1572371184.015:58): 
pid=1013 uid=105 auid=4294967295 ses=4294967295 msg='apparmor="DENIED" 
operation="dbus_method_call"  bus="system" path="/" 
interface="org.freedesktop.DBus.ObjectManager" member="GetManagedObjects" 
mask="send" name="org.bluez" pid=14113 label="snap.chromium.chromium"
exe="/usr/bin/dbus-daemon" sauid=105 hostname=? 
addr=? terminal=?'
loka 29 19:46:24 koira audit[14113]: AVC apparmor="DENIED" operation="open" 
profile="snap.chromium.chromium" name="/var/lib/snapd/desktop/icons/" pid=14113 
comm="chrome" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0
loka 29 19:46:24 koira kernel: audit: type=1400 audit(1572371184.832:59): 
apparmor="DENIED" operation="open" profile="snap.chromium.chromium" 
name="/var/lib/snapd/desktop/icons/" pid=14113 comm="chrome" requested_mask="r" 
denied_mask="r" fsuid=1000 ouid=0


I also tried touching the file first, and the error log begins with different 
errors...
loka 29 20:02:33 koira dbus-daemon[4642]: [session uid=1000 pid=4642] 
Activating via systemd: service name='org.freedesktop.portal.Documents' 
unit='xdg-document-portal.service' requested by ':1.216' (uid=1000 pid=16167 
comm="/snap/bin/chromium " label="unconfined")
loka 29 20:02:33 koira systemd[4622]: Starting flatpak document portal 
service...
loka 29 20:02:33 koira xdg-document-portal[16225]: error: Failed to load db: 
invalid gvdb header
loka 29 20:02:33 koira systemd[4622]: xdg-document-portal.service: Main process 
exited, code=exited, status=2/INVALIDARGUMENT
loka 29 20:02:33 koira systemd[4622]: xdg-document-portal.service: Failed with 
result 'exit-code'.
loka 29 20:02:33 koira systemd[4622]: Failed to start flatpak document portal 
service.

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

Title:
  [snap] chromium times out connecting document portal with NFS home

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

Bug description:
  I have my /home folder shared via NFS from a local server one floor
  below in my house. The server runs Ubuntu 18.04.

  After starting a snapped version of chromium-browser in my Ubuntu
  19.10 the document portal timeouts like this:

  XXX@koira:~$ chromium-browser
  2019/10/18 18:51:27.986444 cmd_run.go:893: WARNING: cannot start document 
portal: Failed to activate service 'org.freedesktop.portal.Documents': timed 
out (service_start_timeout=12ms)

  After the timeout my chrom

[Desktop-packages] [Bug 1850085] Re: right-click 'Format' removable drive not opening dialog

2019-10-29 Thread Andrew Vcourt

Yeah that's everything. Ad nothing out of the ordinary from my boot
records from that time.

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

Title:
  right-click 'Format' removable drive not opening dialog

Status in nautilus package in Ubuntu:
  Incomplete

Bug description:
  right clicking on removable media in nautilus, the format option does
  nothing. All other right click options work as expected. Formatting
  the drive via the disks utility works as expected.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: nautilus 1:3.34.1-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-0ubuntu8
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Oct 27 17:59:20 2019
  GsettingsChanges: b'org.gnome.nautilus.window-state' b'initial-size' b'(890, 
548)'
  InstallationDate: Installed on 2019-10-27 (0 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  ProcEnviron:
   LANGUAGE=en_CA:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_CA.UTF-8
   SHELL=/bin/bash
  SourcePackage: nautilus
  UpgradeStatus: No upgrade log present (probably fresh install)
  usr_lib_nautilus:

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

-- 
Mailing list: https://launchpad.net/~desktop-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-10-29 Thread Lonnie Lee Best

The actual programmer of this module says we need to upgrade-software-
version.

1) 
https://gitlab.gnome.org/GNOME/gnome-control-center/issues/746#note_634394
2) 
https://github.com/nm-l2tp/NetworkManager-l2tp/issues/112#issuecomment-547218557


He believes that this issue is fixed in NetworkManager-l2tp 1.2.12 and later.

Who at Ubuntu can accomplish getting this upgraded in 19.10 instead of
having to wait for 20.04?

Ideally, the upgrade should just be provided via the standard Ubuntu Update GUI 
or CLI:
sudo apt update ; sudo apt upgrade

At this point, upstream has already addressed this bug in a later
version, and it is now up to Ubuntu to upgrade the package in the
repositories.

What is the likelihood that this will be upgraded in Upgraded 19.10?

-- 
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 L2TP over IPsec VPN Manager:
  New
Status in NetworkManager:
  New
Status in strongSwan:
  New
Status in gnome-control-center package in Ubuntu:
  Incomplete

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 workstat

[Desktop-packages] [Bug 1835024] Re: Links triggered within most snap apps open in a separate browser session

Given Maciek's comment about reproducing this with classic snaps I'm
marking this as confirmed.

Interested parties can keep track of
https://github.com/snapcore/snapd/pull/7659 where this issue may be
resolved for _some_ snaps but if confirmed, the same cause is affecting
all the strictly confined apps.

Marking as confirmed.

** Changed in: snapd
   Status: New => Confirmed

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

Title:
  Links triggered within most snap apps open in a separate browser
  session

Status in snapd:
  Confirmed
Status in xdg-utils package in Ubuntu:
  New

Bug description:
  Hi,
  I've recently made a clean install of Ubuntu 19.10 (development release) and 
have noticed that whenever I try to open a link from one of the snap apps 
(being it Slack or Skype) the links although opened in the default browser are 
being opened in a separate session of the web browser.

  I am using Firefox and it is installed as a regular deb package
  (default).

  This is wrong and causes issues with history, sessions and settings
  not being shared between these windows. Now I have the default browser
  I use + a separate session for Slack and another one for Skype. Not to
  mention Firefox also acts just like another Slack/Skype window so dash
  displays these as two instances of the same app.

  To reproduce:
  * Install Ubuntu 19.10 (not sure if upgrade from 19.04 would lead to the same 
behaviour).
  * Confirm FFox is installed as a regular deb package.
  * Install I suppose almost any snap app, although I've only reproduced this 
with Slack and Skype and haven't tried to install other apps.

  System monitor also seems to be installed but when trying to open links from 
the about window - translators - individual names, it seems to do nothing.
  On the other hand Gnome calculator which is also installed as a snap package 
opens the link in the about dialog correctly = in my default browser session.

  ```
  :~# which gnome-calculator 
  /snap/bin/gnome-calculator
  ```

  Thank you very much for looking into that.

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

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

[Desktop-packages] [Bug 1850478] Re: package libedataserverui-1.2-1:amd64 3.18.5-1ubuntu1.2 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before atte

2019-10-29 Thread Apport retracing service

** Tags removed: need-duplicate-check

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

Title:
  package libedataserverui-1.2-1:amd64 3.18.5-1ubuntu1.2 failed to
  install/upgrade: package is in a very bad inconsistent state; you
  should  reinstall it before attempting configuration

Status in evolution-data-server package in Ubuntu:
  New

Bug description:
  Install failed

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libedataserverui-1.2-1:amd64 3.18.5-1ubuntu1.2
  ProcVersionSignature: Ubuntu 4.4.0-166.195-generic 4.4.194
  Uname: Linux 4.4.0-166-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.19
  AptOrdering:
   linux-modules-4.4.0-164-generic: Remove
   libedataserverui-1.2-1: Configure
   NULL: ConfigurePending
  Architecture: amd64
  Date: Tue Oct 29 06:15:13 2019
  DpkgTerminalLog:
   Removing linux-modules-4.4.0-164-generic (4.4.0-164.192) ...
   dpkg: error processing package libedataserverui-1.2-1:amd64 (--configure):
package is in a very bad inconsistent state; you should
reinstall it before attempting configuration
  DuplicateSignature:
   package:libedataserverui-1.2-1:amd64:3.18.5-1ubuntu1.2
   Removing linux-modules-4.4.0-164-generic (4.4.0-164.192) ...
   dpkg: error processing package libedataserverui-1.2-1:amd64 (--configure):
package is in a very bad inconsistent state; you should
  ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
  InstallationDate: Installed on 2018-01-06 (660 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.6
   apt  1.2.32
  SourcePackage: evolution-data-server
  Title: package libedataserverui-1.2-1:amd64 3.18.5-1ubuntu1.2 failed to 
install/upgrade: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1835024] Re: Links triggered within most snap apps open in a separate browser session

Recently we noticed that XDG_RUNTIME_DIR is set to a custom value for
both strictly and classically confined snap applications. It may be the
case that adjusting the runtime directory for a test shows that a remote
window is not opened.

I'm not proposing a solution yet but perhaps we can at least understand
the cause.

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

Title:
  Links triggered within most snap apps open in a separate browser
  session

Status in snapd:
  New
Status in xdg-utils package in Ubuntu:
  New

Bug description:
  Hi,
  I've recently made a clean install of Ubuntu 19.10 (development release) and 
have noticed that whenever I try to open a link from one of the snap apps 
(being it Slack or Skype) the links although opened in the default browser are 
being opened in a separate session of the web browser.

  I am using Firefox and it is installed as a regular deb package
  (default).

  This is wrong and causes issues with history, sessions and settings
  not being shared between these windows. Now I have the default browser
  I use + a separate session for Slack and another one for Skype. Not to
  mention Firefox also acts just like another Slack/Skype window so dash
  displays these as two instances of the same app.

  To reproduce:
  * Install Ubuntu 19.10 (not sure if upgrade from 19.04 would lead to the same 
behaviour).
  * Confirm FFox is installed as a regular deb package.
  * Install I suppose almost any snap app, although I've only reproduced this 
with Slack and Skype and haven't tried to install other apps.

  System monitor also seems to be installed but when trying to open links from 
the about window - translators - individual names, it seems to do nothing.
  On the other hand Gnome calculator which is also installed as a snap package 
opens the link in the about dialog correctly = in my default browser session.

  ```
  :~# which gnome-calculator 
  /snap/bin/gnome-calculator
  ```

  Thank you very much for looking into that.

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

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

[Desktop-packages] [Bug 1848753] Re: [snap] chromium times out connecting document portal with NFS home

Hello there.

loka 24 20:56:42 koira audit[12568]: AVC apparmor="DENIED"
operation="file_mmap" profile="/snap/snapd/4992/usr/lib/snapd/snap-
confine" name="/usr/lib/x86_64-linux-gnu/libgtk3-nocsd.so.0" pid=12568
comm="snap-confine" requested_mask="m" denied_mask="m" fsuid=0 ouid=0

I'm very curious how this can happen. I can only suspect an
LD_LIBRARY_PATH or LD_PRELOAD variables is set and snap-confine is
actually honouring it somehow, despite that not normally affecting
AT_SECURE binaries

loka 24 20:56:42 koira audit[1068]: USER_AVC pid=1068 uid=105
auid=4294967295 ses=4294967295 msg='apparmor="DENIED"
operation="dbus_method_call" bus="system" path="/"
interface="org.freedesktop.DBus.ObjectManager"
member="GetManagedObjects" mask="send" name="org.bluez" pid=12568
label="snap.chromium.chromium"

This denial is fro the chromium snap and could probably be resolved by
connecting the "bluez" interface to chromium.

Neither of those explain why NFS is slow in this specific case that you
are trying. I wonder if this is some sort of remote side logging that
fails because of LAN not providing reverse IP mapping information.

Did you perhaps look at the NFS server logs?

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

Title:
  [snap] chromium times out connecting document portal with NFS home

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

Bug description:
  I have my /home folder shared via NFS from a local server one floor
  below in my house. The server runs Ubuntu 18.04.

  After starting a snapped version of chromium-browser in my Ubuntu
  19.10 the document portal timeouts like this:

  XXX@koira:~$ chromium-browser
  2019/10/18 18:51:27.986444 cmd_run.go:893: WARNING: cannot start document 
portal: Failed to activate service 'org.freedesktop.portal.Documents': timed 
out (service_start_timeout=12ms)

  After the timeout my chromium cannot seem to remember accounts or
  passwords.

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

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

[Desktop-packages] [Bug 1850478] [NEW] package libedataserverui-1.2-1:amd64 3.18.5-1ubuntu1.2 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before at

2019-10-29 Thread Robert Brownell

Public bug reported:

Install failed

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: libedataserverui-1.2-1:amd64 3.18.5-1ubuntu1.2
ProcVersionSignature: Ubuntu 4.4.0-166.195-generic 4.4.194
Uname: Linux 4.4.0-166-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.19
AptOrdering:
 linux-modules-4.4.0-164-generic: Remove
 libedataserverui-1.2-1: Configure
 NULL: ConfigurePending
Architecture: amd64
Date: Tue Oct 29 06:15:13 2019
DpkgTerminalLog:
 Removing linux-modules-4.4.0-164-generic (4.4.0-164.192) ...
 dpkg: error processing package libedataserverui-1.2-1:amd64 (--configure):
  package is in a very bad inconsistent state; you should
  reinstall it before attempting configuration
DuplicateSignature:
 package:libedataserverui-1.2-1:amd64:3.18.5-1ubuntu1.2
 Removing linux-modules-4.4.0-164-generic (4.4.0-164.192) ...
 dpkg: error processing package libedataserverui-1.2-1:amd64 (--configure):
  package is in a very bad inconsistent state; you should
ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
InstallationDate: Installed on 2018-01-06 (660 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.6
 apt  1.2.32
SourcePackage: evolution-data-server
Title: package libedataserverui-1.2-1:amd64 3.18.5-1ubuntu1.2 failed to 
install/upgrade: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-package xenial

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

Title:
  package libedataserverui-1.2-1:amd64 3.18.5-1ubuntu1.2 failed to
  install/upgrade: package is in a very bad inconsistent state; you
  should  reinstall it before attempting configuration

Status in evolution-data-server package in Ubuntu:
  New

Bug description:
  Install failed

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libedataserverui-1.2-1:amd64 3.18.5-1ubuntu1.2
  ProcVersionSignature: Ubuntu 4.4.0-166.195-generic 4.4.194
  Uname: Linux 4.4.0-166-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.19
  AptOrdering:
   linux-modules-4.4.0-164-generic: Remove
   libedataserverui-1.2-1: Configure
   NULL: ConfigurePending
  Architecture: amd64
  Date: Tue Oct 29 06:15:13 2019
  DpkgTerminalLog:
   Removing linux-modules-4.4.0-164-generic (4.4.0-164.192) ...
   dpkg: error processing package libedataserverui-1.2-1:amd64 (--configure):
package is in a very bad inconsistent state; you should
reinstall it before attempting configuration
  DuplicateSignature:
   package:libedataserverui-1.2-1:amd64:3.18.5-1ubuntu1.2
   Removing linux-modules-4.4.0-164-generic (4.4.0-164.192) ...
   dpkg: error processing package libedataserverui-1.2-1:amd64 (--configure):
package is in a very bad inconsistent state; you should
  ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
  InstallationDate: Installed on 2018-01-06 (660 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.6
   apt  1.2.32
  SourcePackage: evolution-data-server
  Title: package libedataserverui-1.2-1:amd64 3.18.5-1ubuntu1.2 failed to 
install/upgrade: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
  UpgradeStatus: No upgrade log present (probably fresh install)

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

-- 
Mailing list: https://launchpad.net/~desktop-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-10-29 Thread Lonnie Lee Best

** Tags added: upgrade-software-version

-- 
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 L2TP over IPsec VPN Manager:
  New
Status in NetworkManager:
  New
Status in strongSwan:
  New
Status in gnome-control-center package in Ubuntu:
  Incomplete

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]: could not decrypt payloads
  Oct 26 02:58:48 workstation5 N

[Desktop-packages] [Bug 1829746] Re: [upstream] LibreOffice Impress embed video broken outside slide

** Changed in: df-libreoffice
   Status: In Progress => Confirmed

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

Title:
  [upstream] LibreOffice Impress embed video broken outside slide

Status in LibreOffice:
  Confirmed
Status in libreoffice package in Ubuntu:
  In Progress

Bug description:
  Summary:
  If you insert video in Impress slideshow and the video is bigger than slide 
or is partially out of slide, the libreoffice UI or "slideshow" breaks. See the 
video [1]

  
  This bug is related to "libreoffice-gtk3" and "gstreamer1.0-gtk3". The bug 
does not accrue if using "libreoffice-gtk2" or none (the default LibreOffice 
VCL). Tested on Ubuntu 19.04. Enabled -purposed and upgraded libreoffice to 
"6.1.6"

  So the current situation (upgrading to "6.1.6") is that video plays
  correctly IF the video is fully inside the slide.

  If the video is a bit outside the slide or video is bigger than slide, when 
pressing "play" button in right pane, libreoffice UI totally breaks.
  Only the ~1/8 of window display content other space is white. If resizing the 
window, the content gets even smaller.
  Also when running the slideshow, it's broken.
  I need to close impress and run it again.

  Can someone else confirm similar behavior?

  [1] https://www.youtube.com/watch?v=e6UDDSBg4m8

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

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

[Desktop-packages] [Bug 1849950] Re: Gnome Shell window shortcuts maximize, windowed and hide (Super + Up / Down / H) don't work if upgrading from Unity

2019-10-29 Thread clel

I have not changed the config in Unity manually, either. I want to say
that it was just a suspicion that Upgrading from Unity to GNOME caused
this. I cannot say for sure, but your post sounds like that really is
the reason? Just want to make sure this really causes this.

If that is true, I am ok with the solution.

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

Title:
  Gnome Shell window shortcuts maximize, windowed and hide (Super + Up /
  Down / H) don't work if upgrading from Unity

Status in GNOME Shell:
  Fix Released
Status in gsettings-desktop-schemas package in Ubuntu:
  Fix Released

Bug description:
  Happens on Ubuntu 19.10, and did also not work on Ubuntu 19.04 (and
  probably also previous versions), if I recall correctly.

  I am not sure, whether this is an upstream bug of GNOME or just Ubuntu
  related.

  Bug report for GNOME: https://gitlab.gnome.org/GNOME/gnome-
  shell/issues/1829

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

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

[Desktop-packages] [Bug 1829746]

2019-10-29 Thread Xiscofauli

Dear Caolán McNamara,
This bug has been in ASSIGNED status for more than 3 months without any
activity. Resetting it to NEW.
Please assigned it back to yourself if you're still working on this.

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

Title:
  [upstream] LibreOffice Impress embed video broken outside slide

Status in LibreOffice:
  Confirmed
Status in libreoffice package in Ubuntu:
  In Progress

Bug description:
  Summary:
  If you insert video in Impress slideshow and the video is bigger than slide 
or is partially out of slide, the libreoffice UI or "slideshow" breaks. See the 
video [1]

  
  This bug is related to "libreoffice-gtk3" and "gstreamer1.0-gtk3". The bug 
does not accrue if using "libreoffice-gtk2" or none (the default LibreOffice 
VCL). Tested on Ubuntu 19.04. Enabled -purposed and upgraded libreoffice to 
"6.1.6"

  So the current situation (upgrading to "6.1.6") is that video plays
  correctly IF the video is fully inside the slide.

  If the video is a bit outside the slide or video is bigger than slide, when 
pressing "play" button in right pane, libreoffice UI totally breaks.
  Only the ~1/8 of window display content other space is white. If resizing the 
window, the content gets even smaller.
  Also when running the slideshow, it's broken.
  I need to close impress and run it again.

  Can someone else confirm similar behavior?

  [1] https://www.youtube.com/watch?v=e6UDDSBg4m8

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

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

[Desktop-packages] [Bug 1251281] Re: gnome-session-flashback/Unity fails to start without hardware acceleration in cloud/remote environments (Forwarded-X/XRDP/VNC/NX/X2GO/Chromoting)

2019-10-29 Thread Gustavo A . Díaz

Hi,

Same thing is happening to me in Xubuntu 18.04 with xrdp. Is there any
fix for this? Thanks.

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

Title:
  gnome-session-flashback/Unity fails to start without hardware
  acceleration in cloud/remote environments
  (Forwarded-X/XRDP/VNC/NX/X2GO/Chromoting)

Status in gnome-session:
  Fix Released
Status in gnome-session package in Ubuntu:
  Fix Released
Status in gnome-session source package in Trusty:
  Fix Released
Status in gnome-session source package in Utopic:
  Fix Released
Status in gnome-flashback source package in Vivid:
  Fix Released
Status in gnome-session source package in Vivid:
  Fix Released
Status in gnome-session package in Debian:
  New

Bug description:
  == Impact ==
  It was impossible to launch a gnome-session-based desktop on a system where 
hardware accelerations is not available (such as old hardware, or when using a 
remote desktop).

  That looks like a quite popular use case — more than a hundred of
  people marked this bug as affecting them.

  == Test Case ==
  The original bug description below contains a test case.

  == Proposed Fix ==
  The fix backports an upstream commit which adds --disable-acceleration-check 
commandline option, and makes Upstart user session pass that flag to 
gnome-session when the session is gnome-fallback (aka 
gnome-flashback-metacity). Of course, that option can be used with other 
sessions as well.

  This was fixed in vivid in version 3.14.0-2ubuntu4.

  == Regression Potential ==
  The option was accepted upstream, and nobody complained so far. So the 
regression potential should be low.

  This bug will cause static grey or black screen instead of opening
  remote session using Forwarded-X/XRDP/VNC/NX/X2GO/Chromoting from
  x2goclient, rdpclient(reminna/vinagre/mstsc), SSH, VNC, NOMACHINE and
  etc.

  == Original Description ==
  1) lsb_release -rd
  Description:  Ubuntu 14.04 LTS
  Release:  14.04

  2) apt-cache policy gnome-session
  gnome-session:
    Installed: 3.9.90-0ubuntu12
    Candidate: 3.9.90-0ubuntu12
    Version table:
   *** 3.9.90-0ubuntu12 0
  500 http://us.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages
  100 /var/lib/dpkg/status

  3) What is expected to happen is when one installs xrdp on the host
  and attempts to use remmina or vinagre on a Ubuntu 14.04 client to RDP
  in, it works.

  4) What happens instead is it shows a gray static screen as per attached 
screenshot. This would appear an issue with gnome-session as per client log:
  cat .xsession-errors.old
  Script for ibus started at run_im.
  Script for auto started at run_im.
  Script for default started at run_im.
  init: indicator-application main process ended, respawning
  init: indicator-application main process ended, respawning
  init: indicator-application respawning too fast, stopped
  Xsession: X session started for  at Sun Jul 20 15:25:59 CDT 2014
  X Error of failed request:  BadValue (integer parameter out of range for 
operation)
    Major opcode of failed request:  109 (X_ChangeHosts)
    Value in failed request:  0x5
    Serial number of failed request:  6
    Current serial number in output stream:  8
  localuser:moniker being added to access control list
  X Error of failed request:  BadValue (integer parameter out of range for 
operation)
    Major opcode of failed request:  109 (X_ChangeHosts)
    Value in failed request:  0x5
    Serial number of failed request:  6
    Current serial number in output stream:  8
  Script for ibus started at run_im.
  Script for auto started at run_im.
  Script for default started at run_im.
  Script for ibus started at run_im.
  Script for auto started at run_im.
  Script for default started at run_im.
  gnome-session-is-accelerated: No composite extension.
  gnome-session-check-accelerated: Helper exited with code 256
  gnome-session-is-accelerated: No composite extension.
  gnome-session-check-accelerated: Helper exited with code 256

  ** (process:2565): WARNING **: software acceleration check failed:
  Child process exited with code 1

  ** (x-session-manager:2565): CRITICAL **: We failed, but the fail
  whale is dead. Sorry

  The following is not a WORKAROUND, create /etc/xorg.conf :
  Section "Device"
     Identifier  "Intel Graphics"
     Driver  "Intel"
     Option  "DRI" "False"
  EndSection

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: gnome-session 3.9.90-0ubuntu12
  ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4
  Uname: Linux 3.13.0-32-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sun Jul 20 15:35:23 2014
  InstallationDate: Installed on 2014-06-22 (28 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  PackageArchitecture: all
  SourcePackage: gnome-session
  Up

[Desktop-packages] [Bug 1539964] Re: file information not shown on rollover on tab if window is maximized

2019-10-29 Thread teo1978

This is still an issue in 16.04. Why the fuck was this closed??

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

Title:
  file information not shown on rollover on tab if window is maximized

Status in gedit package in Ubuntu:
  Won't Fix

Bug description:
  Steps to reproduce:
  1. open several files in Gedit
  2. maximize the window
  3. move the cursor over each tab

  Expected behavior: every time you roll over a tab, a black rectangle
  should appear with white text with information about the file (full
  path, mime type...)

  Observed result: for the left-most tabs and while the cursor x
  position is lower than a certain point, the info box is not shown.
  Instead, a strange flickering can be observed on the top left corner
  of the screen (not even in the area where the info box is supposed to
  be shown); sometimes you may see the info box appear for a fraction of
  an instant. If you move the cursor to the right of a certain threshold
  and for subsequent tabs, it works as expected.

  
  Just another pathetic regression in f***ing-unusable 15.10.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: gedit 3.10.4-0ubuntu13
  ProcVersionSignature: Ubuntu 4.2.0-25.30-generic 4.2.6
  Uname: Linux 4.2.0-25-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sat Jan 30 19:09:37 2016
  InstallationDate: Installed on 2013-10-11 (841 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  SourcePackage: gedit
  UpgradeStatus: Upgraded to wily on 2016-01-18 (12 days ago)

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

-- 
Mailing list: https://launchpad.net/~desktop-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-10-29 Thread Kenneth Zadeck

it is nice to know that i am not the only one wrestling with these alligators.
here is your log as requested.

kenny

** Attachment added: "output of journalctl -b 0"
   
https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1849886/+attachment/5301170/+files/log

-- 
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 1850275] Re: English-Europe locale missing

2019-10-29 Thread Gunnar Hjalmarsson

This is indeed a glibc thing, Sebastien.

And it has been discussed upstream a lot, for instance in
. Awaiting the
result of that discussion, we won't implement any Ubuntu only locales in
Ubuntu.

@Luca: As you mentioned, there are ways to achieve approximately what
you want. You mentioned the Irish locale, and there is also the
en_DK.UTF-8 locale which actually was created to serve as a European
English locale.

** Bug watch added: Sourceware.org Bugzilla #22473
   https://sourceware.org/bugzilla/show_bug.cgi?id=22473

** Package changed: language-selector (Ubuntu) => glibc (Ubuntu)

** Changed in: glibc (Ubuntu)
   Importance: Undecided => Wishlist

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

** Also affects: glibc via
   https://sourceware.org/bugzilla/show_bug.cgi?id=22473
   Importance: Unknown
   Status: Unknown

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

Title:
  English-Europe locale missing

Status in GLibC:
  Unknown
Status in glibc package in Ubuntu:
  Confirmed

Bug description:
  Hello. I'm not reporting a 'bug', perhaps a missing feature.
  I try to explain it. I would like to use my system with Italian locale and 
the English language, but it seems not considered. Usually, I choose English 
for language and Ireland for Time/Date/Currency and it works; but I'm wondering 
why it isn't contemplated the use of the English language for Italian users.

  At least, why don't we insert English-Europe locale settings like in
  Windows systems?

  Sorry for bothering and I hope that I explained well what I mean.
  Thanks in advance for the time on it. Cheers.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: locales 2.27-3ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-66.75-generic 4.15.18
  Uname: Linux 4.15.0-66-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Oct 29 10:18:17 2019
  InstallationDate: Installed on 2019-10-24 (4 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  PackageArchitecture: all
  SourcePackage: glibc
  UpgradeStatus: No upgrade log present (probably fresh install)

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

-- 
Mailing list: https://launchpad.net/~desktop-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] [NEW] lightdm does not work on eoan on raspberry pi 4

You have been subscribed to a public bug:

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.

** Affects: lightdm (Ubuntu)
 Importance: Undecided
 Status: Incomplete

-- 
lightdm does not work on eoan on raspberry pi 4
https://bugs.launchpad.net/bugs/1849886
You received this bug notification because you are a member of Desktop 
Packages, which is subscribed to lightdm in Ubuntu.

-- 
Mailing list: https://launchpad.net/~desktop-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.

** Changed in: gnome-session (Ubuntu)
 Assignee: Alberto Milone (albertomilone) => (unassigned)

-- 
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:
  Confirmed
Status in gnome-session package in Ubuntu:
  Confirmed
Status in gnome-shell package in Ubuntu:
  Confirmed
Status in gdm3 source package in Eoan:
  Confirmed
Status in gnome-session source package in Eoan:
  Confirmed
Status in gnome-shell source package in Eoan:
  Confirmed

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 1849886] Re: lightdm does not work on eoan on raspberry pi 4

Could you get the 'journalctl -b 0' log from a failed session?

** Package changed: software-properties (Ubuntu) => lightdm (Ubuntu)

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

-- 
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 1850278] Re: Activities overview hot corner setting does not persist

You just need to install the 'gnome-session' binary and pick 'GNOME' as
session type on the login screen (by clicking the small badge next to
the sign in button)

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

Title:
  Activities overview hot corner setting does not persist

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  Steps to reproduce:
  1. Disable activities overview hot corner in GNOME tweaks
  2. See that the hot corner is indeed disabled
  3. Lock the screen
  4. Unlock the screen
  5. See that hot corner is active again (however GNOME tweaks still shows it 
as disabled)

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: gnome-shell 3.34.1-1ubuntu1
  ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
  Uname: Linux 5.3.0-19-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu8
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Oct 29 09:47:00 2019
  DisplayManager: gdm3
  InstallationDate: Installed on 2018-09-02 (421 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  ProcEnviron:
   LANGUAGE=en_IL:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_IL
   SHELL=/bin/bash
  RelatedPackageVersions: mutter-common 3.34.1-1ubuntu1
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to eoan on 2019-10-27 (1 days ago)

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

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

[Desktop-packages] [Bug 1849773] Re: /usr/bin/evince:11:strstr:TextSelectionPainter::hasGlyphLessFont:TextSelectionPainter::endPage:TextPage::drawSelection:poppler_page_render_selection

While the bug would be good to fix it's a bit too specific to qualify as
a release issue, tagging rls-ff-notfixing

** Tags removed: rls-ff-incoming
** Tags added: rls-ff-notfixing

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

Title:
  
/usr/bin/evince:11:strstr:TextSelectionPainter::hasGlyphLessFont:TextSelectionPainter::endPage:TextPage::drawSelection:poppler_page_render_selection

Status in evince package in Ubuntu:
  Confirmed

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

  Test Case:
  1. Select some text in the document

  Expected result
  Text is selected

  Actual result
  This crash.

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

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

[Desktop-packages] [Bug 1847551] Re: Mutter 3.34.1 broke Night Light, screen color profiles in Wayland sessions

** Changed in: mutter (Ubuntu Eoan)
 Assignee: (unassigned) => Marco Trevisan (Treviño) (3v1n0)

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

Title:
  Mutter 3.34.1 broke Night Light, screen color profiles in Wayland
  sessions

Status in Mutter:
  Fix Released
Status in mutter package in Ubuntu:
  Fix Released
Status in mutter source package in Eoan:
  In Progress
Status in mutter source package in Focal:
  Fix Released

Bug description:
  [ Impact ]

  Upgrading Mutter 3.34.0 to 3.34.1 has broken Night Light and screen color 
profile switching.
  The commit at fault is 104bdde746c9ceccd9e9ab09b22ef228b8f7026e “kms: Predict 
state changes when processing update” (which was intended to fix LP bug 
1847044).

  [ Test case ]

  - From gnome-control-center display panel, enable the Night Light
  - Force it on, and ensure that the display color temperature increases

  [ Regression potential ]

  Display gamma value might be incorrect

  Upstream issue: https://gitlab.gnome.org/GNOME/mutter/issues/851

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

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

[Desktop-packages] [Bug 1647285] Re: SSL trust not system-wide

2019-10-29 Thread dwmw2

@kvasko yes, it works here. Are you sure that's the version of
libnssckbi.so that is being used? There are lots; I've replaced them
all...

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

Title:
  SSL trust not system-wide

Status in ca-certificates package in Ubuntu:
  Confirmed
Status in nss package in Ubuntu:
  Confirmed
Status in p11-kit package in Ubuntu:
  Confirmed
Status in thunderbird package in Ubuntu:
  Confirmed

Bug description:
  When I install a corporate CA trust root with update-ca-certificates,
  it doesn't seem to work everywhere. Various things like Firefox,
  Evolution, Chrome, etc. all fail to trust the newly-installed trusted
  CA.

  This ought to work, and does on other distributions. In p11-kit there
  is a module p11-kit-trust.so which can be used as a drop-in
  replacement for NSS's own libnssckbi.so trust root module, but which
  reads from the system's configured trust setup instead of the hard-
  coded version.

  This allows us to install the corporate CAs just once, and then file a
  bug against any package that *doesn't* then trust them.

  See https://fedoraproject.org/wiki/Features/SharedSystemCertificates
  for some of the historical details from when this feature was first
  implemented, but this is all now supported upstream and not at all
  distribution-specific. There shouldn't be any significant work
  required; it's mostly just a case of configuring and building it to
  make use of this functionality. (With 'alternatives' to let you
  substitute p11-kit-trust.so for the original NSS libnssckbi.so, etc.)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ca-certificates/+bug/1647285/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-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.

** Changed in: gdm3 (Ubuntu)
 Assignee: (unassigned) => Alberto Milone (albertomilone)

** Changed in: gnome-session (Ubuntu)
 Assignee: (unassigned) => Alberto Milone (albertomilone)

** Changed in: gnome-session (Ubuntu Eoan)
 Assignee: (unassigned) => Alberto Milone (albertomilone)

-- 
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:
  Confirmed
Status in gnome-session package in Ubuntu:
  Confirmed
Status in gnome-shell package in Ubuntu:
  Confirmed
Status in gdm3 source package in Eoan:
  Confirmed
Status in gnome-session source package in Eoan:
  Confirmed
Status in gnome-shell source package in Eoan:
  Confirmed

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 1827644] Re: UPower and battery indicator show wrong information on fully charged ASUS Vivobook X510UR laptop

2019-10-29 Thread Yayai

Been trying for days to 'fix' the battery status, 9.7 hours to full?
think ubuntu is on crack

Device: /org/freedesktop/UPower/devices/line_power_AC
  native-path:  AC
  power supply: yes
  updated:  Tue 29 Oct 2019 09:06:08 PM +08 (4275 seconds ago)
  has history:  no
  has statistics:   no
  line-power
warning-level:   none
online:  yes
icon-name:  'ac-adapter-symbolic'

Device: /org/freedesktop/UPower/devices/battery_BAT0
  native-path:  BAT0
  vendor:   Hewlett-Packard
  model:Primary
  serial:   15305 03/10/2016
  power supply: yes
  updated:  Tue 29 Oct 2019 10:16:20 PM +08 (63 seconds ago)
  has history:  yes
  has statistics:   yes
  battery
present: yes
rechargeable:yes
state:   charging
warning-level:   none
energy:  20.9218 Wh
energy-empty:0 Wh
energy-full: 24.3382 Wh
energy-full-design:  17.8996 Wh
energy-rate: 0.3504 W
voltage: 16.004 V
time to full:9.7 hours
percentage:  100%
capacity:100%
technology:  lithium-ion
icon-name:  'battery-full-charging-symbolic'

Device: /org/freedesktop/UPower/devices/DisplayDevice
  power supply: yes
  updated:  Tue 29 Oct 2019 09:44:19 PM +08 (1984 seconds ago)
  has history:  no
  has statistics:   no
  battery
present: yes
state:   charging
warning-level:   none
energy:  20.9218 Wh
energy-full: 24.3382 Wh
energy-rate: 0.3504 W
time to full:9.7 hours
percentage:  100%
icon-name:  'battery-full-charging-symbolic'

Daemon:
  daemon-version:  0.99.7
  on-battery:  no
  lid-is-closed:   no
  lid-is-present:  yes
  critical-action: HybridSleep

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

Title:
  UPower and battery indicator show wrong information on fully charged
  ASUS Vivobook X510UR laptop

Status in upower package in Ubuntu:
  Confirmed

Bug description:
  When the ASUS Vivobook X510UR laptop is completely charged, the
  correct information is displayed on Windows. However, Ubuntu 18.04.2
  LTS is unable to detect the true battery state. The GNOME battery
  indicator usually shows "Estimating..." or "Not charging", when the
  battery is at 100%.

  If you use the upower version 0.99.7-2ubuntu0.18.04.1 command "upower
  -i /org/freedesktop/UPower/devices/battery_BAT0", this is what you
  get:

native-path:  BAT0
vendor:   ASUSTeK
model:ASUS Battery
power supply: yes
updated:  sex 03 mai 2019 14:33:43 -03 (4 seconds ago)
has history:  yes
has statistics:   yes
battery
  present: yes
  rechargeable:yes
  state:   pending-charge
  warning-level:   none
  energy:  39,191 Wh
  energy-empty:0 Wh
  energy-full: 39,26 Wh
  energy-full-design:  42,082 Wh
  energy-rate: 12,453 W
  voltage: 11,52 V
  percentage:  100%
  capacity:93,294%
  technology:  lithium-ion
  icon-name:  'battery-full-charging-symbolic'
History (charge):
  1556904821100,000 discharging
History (rate):
  155690482112,453  discharging
  15569048183,744   discharging

  The "state" should be "fully-charged", but instead it is "pending-
  charge".

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: upower 0.99.7-2ubuntu0.18.04.1
  ProcVersionSignature: Ubuntu 4.18.0-18.19~18.04.1-generic 4.18.20
  Uname: Linux 4.18.0-18-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Fri May  3 14:34:14 2019
  InstallationDate: Installed on 2018-12-11 (142 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  ProcEnviron:
   LANGUAGE=pt_BR:pt:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=pt_BR.UTF-8
   SHELL=/bin/bash
  SourcePackage: upower
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1647285] Re: SSL trust not system-wide

2019-10-29 Thread Timo Aaltonen

should this be marked as something to fix in focal for the next LTS?

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

Title:
  SSL trust not system-wide

Status in ca-certificates package in Ubuntu:
  Confirmed
Status in nss package in Ubuntu:
  Confirmed
Status in p11-kit package in Ubuntu:
  Confirmed
Status in thunderbird package in Ubuntu:
  Confirmed

Bug description:
  When I install a corporate CA trust root with update-ca-certificates,
  it doesn't seem to work everywhere. Various things like Firefox,
  Evolution, Chrome, etc. all fail to trust the newly-installed trusted
  CA.

  This ought to work, and does on other distributions. In p11-kit there
  is a module p11-kit-trust.so which can be used as a drop-in
  replacement for NSS's own libnssckbi.so trust root module, but which
  reads from the system's configured trust setup instead of the hard-
  coded version.

  This allows us to install the corporate CAs just once, and then file a
  bug against any package that *doesn't* then trust them.

  See https://fedoraproject.org/wiki/Features/SharedSystemCertificates
  for some of the historical details from when this feature was first
  implemented, but this is all now supported upstream and not at all
  distribution-specific. There shouldn't be any significant work
  required; it's mostly just a case of configuring and building it to
  make use of this functionality. (With 'alternatives' to let you
  substitute p11-kit-trust.so for the original NSS libnssckbi.so, etc.)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ca-certificates/+bug/1647285/+subscriptions

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

[Desktop-packages] [Bug 1850432] [NEW] acrually i wanted the graphics driver for my intel 3000 graphics driver for 2nd gen core i3 processor

2019-10-29 Thread Ahmmed Sakin Noman

Public bug reported:

acrually i wanted the graphics driver for my intel 3000 graphics driver
for 2nd gen core i3 processor

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xorg 1:7.7+19ubuntu7.1
ProcVersionSignature: Ubuntu 5.0.0-32.34~18.04.2-generic 5.0.21
Uname: Linux 5.0.0-32-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.7
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Tue Oct 29 20:09:47 2019
DistUpgraded: Fresh install
DistroCodename: bionic
DistroVariant: ubuntu
GraphicsCard:
 Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller])
   Subsystem: Dell 2nd Generation Core Processor Family Integrated Graphics 
Controller [1028:0591]
InstallationDate: Installed on 2019-10-29 (0 days ago)
InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805)
MachineType: Dell Inc. Inspiron 3421
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-32-generic 
root=UUID=caaedd10-467d-46ef-9bc9-df58fb08f913 ro quiet splash vt.handoff=1
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 12/14/2015
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A13
dmi.board.name: 0WF4PW
dmi.board.vendor: Dell Inc.
dmi.board.version: A13
dmi.chassis.type: 8
dmi.chassis.vendor: Dell Inc.
dmi.chassis.version: Not Specified
dmi.modalias: 
dmi:bvnDellInc.:bvrA13:bd12/14/2015:svnDellInc.:pnInspiron3421:pvrNotSpecified:rvnDellInc.:rn0WF4PW:rvrA13:cvnDellInc.:ct8:cvrNotSpecified:
dmi.product.name: Inspiron 3421
dmi.product.sku: Inspiron 3421
dmi.product.version: Not Specified
dmi.sys.vendor: Dell Inc.
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.97-1ubuntu1~18.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.8-0ubuntu0~18.04.3
version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.8-0ubuntu0~18.04.3
version.xserver-xorg-core: xserver-xorg-core N/A
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A

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


** Tags: amd64 apport-bug bionic ubuntu

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

Title:
  acrually i wanted the graphics driver for my intel 3000 graphics
  driver for 2nd gen core i3 processor

Status in xorg package in Ubuntu:
  New

Bug description:
  acrually i wanted the graphics driver for my intel 3000 graphics
  driver for 2nd gen core i3 processor

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 5.0.0-32.34~18.04.2-generic 5.0.21
  Uname: Linux 5.0.0-32-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.7
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Oct 29 20:09:47 2019
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: Dell 2nd Generation Core Processor Family Integrated Graphics 
Controller [1028:0591]
  InstallationDate: Installed on 2019-10-29 (0 days ago)
  InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 
(20190805)
  MachineType: Dell Inc. Inspiron 3421
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-32-generic 
root=UUID=caaedd10-467d-46ef-9bc9-df58fb08f913 ro quiet splash vt.handoff=1
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/14/2015
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A13
  dmi.board.name: 0WF4PW
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A13
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: Not Specified
  dmi.modalias: 
dmi:bvnDellInc.:bvrA13:bd12/14/2015:svnDellInc.:pnInspiron3421:pvrNotSpecified:rvnDellInc.:rn0WF4PW:rvrA13:cvnDellInc.:ct8:cvrNotSpecified:
  dmi.product.name: Inspiron 3421
  dmi.product.sku: Inspiron 3421
  dmi.product.version: Not Specified
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.97-1ubuntu1~18.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.8-0ubuntu0~18.04.3
  version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.8-0ubuntu0~18.04.3
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-

[Desktop-packages] [Bug 1849484] Re: [X1 Carbon 7, i915, HDMI] Ultra-wide monitor recognized properly when plugged in only intermittently [Xorg only]

2019-10-29 Thread Jonathan Kamens

[72227.300557] [drm:drm_dp_dual_mode_detect [drm_kms_helper]] *ERROR* 
Unexpected DP dual mode adaptor ID 50
[72228.173908] [drm:drm_dp_dual_mode_detect [drm_kms_helper]] *ERROR* 
Unexpected DP dual mode adaptor ID 50
[72229.956316] [drm:drm_dp_dual_mode_detect [drm_kms_helper]] *ERROR* 
Unexpected DP dual mode adaptor ID 50
[72233.510378] [drm:drm_dp_dual_mode_detect [drm_kms_helper]] *ERROR* 
Unexpected DP dual mode adaptor ID 50
[72236.205870] [drm:drm_dp_dual_mode_detect [drm_kms_helper]] *ERROR* 
Unexpected DP dual mode adaptor ID 50
[72237.999470] [drm:drm_dp_dual_mode_detect [drm_kms_helper]] *ERROR* 
Unexpected DP dual mode adaptor ID 50
[72239.786382] [drm:drm_dp_dual_mode_detect [drm_kms_helper]] *ERROR* 
Unexpected DP dual mode adaptor ID 50
[72242.549836] [drm:drm_dp_dual_mode_detect [drm_kms_helper]] *ERROR* 
Unexpected DP dual mode adaptor ID 50
[72243.442375] [drm:drm_dp_dual_mode_detect [drm_kms_helper]] *ERROR* 
Unexpected DP dual mode adaptor ID 54
[72244.361826] [drm:drm_dp_dual_mode_detect [drm_kms_helper]] *ERROR* 
Unexpected DP dual mode adaptor ID 50
[72250.961559] [drm:drm_dp_dual_mode_detect [drm_kms_helper]] *ERROR* 
Unexpected DP dual mode adaptor ID 50
[72254.547660] [drm:drm_dp_dual_mode_detect [drm_kms_helper]] *ERROR* 
Unexpected DP dual mode adaptor ID 50
[72269.690250] [drm:drm_dp_dual_mode_detect [drm_kms_helper]] *ERROR* 
Unexpected DP dual mode adaptor ID 50
[72273.607350] [drm] EDID has major version 93, instead of 1
[72279.495513] [drm:drm_dp_dual_mode_detect [drm_kms_helper]] *ERROR* 
Unexpected DP dual mode adaptor ID 50
[72290.492743] [drm:drm_dp_dual_mode_detect [drm_kms_helper]] *ERROR* 
Unexpected DP dual mode adaptor ID 54
[72293.153731] [drm:drm_dp_dual_mode_detect [drm_kms_helper]] *ERROR* 
Unexpected DP dual mode adaptor ID 54
[72294.043151] [drm:drm_dp_dual_mode_detect [drm_kms_helper]] *ERROR* 
Unexpected DP dual mode adaptor ID 54
[72295.855213] [drm:drm_dp_dual_mode_detect [drm_kms_helper]] *ERROR* 
Unexpected DP dual mode adaptor ID 50
[72297.632687] [drm:drm_dp_dual_mode_detect [drm_kms_helper]] *ERROR* 
Unexpected DP dual mode adaptor ID 54
[72300.590655] [drm:drm_dp_dual_mode_detect [drm_kms_helper]] *ERROR* 
Unexpected DP dual mode adaptor ID 54
[72301.836996] i2c i2c-3: sendbytes: error -110
[72315.236846] [drm] EDID has major version 93, instead of 1
[72318.454559] [drm:drm_dp_dual_mode_detect [drm_kms_helper]] *ERROR* 
Unexpected DP dual mode adaptor ID 50
[72318.778580] [drm] EDID has major version 93, instead of 1
[72321.074870] [drm:drm_dp_dual_mode_detect [drm_kms_helper]] *ERROR* 
Unexpected DP dual mode adaptor ID 50
[72322.836269] [drm:drm_dp_dual_mode_detect [drm_kms_helper]] *ERROR* 
Unexpected DP dual mode adaptor ID 50
[72324.607377] [drm:drm_dp_dual_mode_detect [drm_kms_helper]] *ERROR* 
Unexpected DP dual mode adaptor ID 54
[72325.489757] [drm:drm_dp_dual_mode_detect [drm_kms_helper]] *ERROR* 
Unexpected DP dual mode adaptor ID 50
[72330.776866] [drm:drm_dp_dual_mode_detect [drm_kms_helper]] *ERROR* 
Unexpected DP dual mode adaptor ID 50
[72332.734125] mce: CPU7: Core temperature above threshold, cpu clock throttled 
(total events = 575)
[72332.734125] mce: CPU3: Core temperature above threshold, cpu clock throttled 
(total events = 575)
[72332.734127] mce: CPU1: Package temperature above threshold, cpu clock 
throttled (total events = 871)
[72332.734127] mce: CPU5: Package temperature above threshold, cpu clock 
throttled (total events = 871)
[72332.734128] mce: CPU6: Package temperature above threshold, cpu clock 
throttled (total events = 871)
[72332.734129] mce: CPU0: Package temperature above threshold, cpu clock 
throttled (total events = 871)
[72332.734130] mce: CPU4: Package temperature above threshold, cpu clock 
throttled (total events = 871)
[72332.734131] mce: CPU2: Package temperature above threshold, cpu clock 
throttled (total events = 871)
[72332.734132] mce: CPU3: Package temperature above threshold, cpu clock 
throttled (total events = 871)
[72332.734133] mce: CPU7: Package temperature above threshold, cpu clock 
throttled (total events = 871)
[72332.766080] mce: CPU3: Core temperature/speed normal
[72332.766080] mce: CPU7: Core temperature/speed normal
[72332.766081] mce: CPU1: Package temperature/speed normal
[72332.766082] mce: CPU5: Package temperature/speed normal
[72332.766083] mce: CPU2: Package temperature/speed normal
[72332.766083] mce: CPU6: Package temperature/speed normal
[72332.766084] mce: CPU4: Package temperature/speed normal
[72332.766085] mce: CPU0: Package temperature/speed normal
[72332.766086] mce: CPU7: Package temperature/speed normal
[72332.766087] mce: CPU3: Package temperature/speed normal
[72334.303794] [drm:drm_dp_dual_mode_detect [drm_kms_helper]] *ERROR* 
Unexpected DP dual mode adaptor ID 50
[72335.184591] [drm:drm_dp_dual_mode_detect [drm_kms_helper]] *ERROR* 
Unexpected DP dual mode adaptor ID 50
[72336.941529] [drm:drm_dp_dual_mode_detect [drm_kms_helper]] *ERROR* 
Unexpected DP dua

[Desktop-packages] [Bug 1850159] Re: gnome-control-center reports Ethernet Connection Failure while Connection success

unsure where the communication is failing, but could you provide a
screenshot showing the issue? or if not at least state that you
can't/don't want and try to explain better what UI is having the
incorrect status?

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

Title:
  gnome-control-center reports Ethernet Connection Failure while
  Connection success

Status in network-manager package in Ubuntu:
  Incomplete

Bug description:
  gnome-control-center reports Ethernet Connection Failure with TLS
  Authentication

  1) Ubuntu 19.10
  2) 1:3.34.1-1ubuntu2
  3) Show Connected for Wired Connection
  4) Show Disconnected for Wired Connection

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: gnome-control-center 1:3.34.1-1ubuntu2
  ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
  Uname: Linux 5.3.0-19-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Oct 28 17:06:43 2019
  InstallationDate: Installed on 2019-08-01 (88 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  SourcePackage: gnome-control-center
  UpgradeStatus: Upgraded to eoan on 2019-10-28 (0 days ago)

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

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

[Desktop-packages] [Bug 1850159] Re: gnome-control-center reports Ethernet Connection Failure while Connection success

2019-10-29 Thread Mikhail

Sorry for wrong package name changed to network-manager

** Package changed: gnome-control-center (Ubuntu) => network-manager
(Ubuntu)

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

Title:
  gnome-control-center reports Ethernet Connection Failure while
  Connection success

Status in network-manager package in Ubuntu:
  Incomplete

Bug description:
  gnome-control-center reports Ethernet Connection Failure with TLS
  Authentication

  1) Ubuntu 19.10
  2) 1:3.34.1-1ubuntu2
  3) Show Connected for Wired Connection
  4) Show Disconnected for Wired Connection

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: gnome-control-center 1:3.34.1-1ubuntu2
  ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
  Uname: Linux 5.3.0-19-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Oct 28 17:06:43 2019
  InstallationDate: Installed on 2019-08-01 (88 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  SourcePackage: gnome-control-center
  UpgradeStatus: Upgraded to eoan on 2019-10-28 (0 days ago)

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

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

[Desktop-packages] [Bug 1850159] Re: gnome-control-center reports Ethernet Connection Failure while Connection success

Sorry but I still don't understand what UI you are talking about, can
you make a screenshot?

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

Title:
  gnome-control-center reports Ethernet Connection Failure while
  Connection success

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

Bug description:
  gnome-control-center reports Ethernet Connection Failure with TLS
  Authentication

  1) Ubuntu 19.10
  2) 1:3.34.1-1ubuntu2
  3) Show Connected for Wired Connection
  4) Show Disconnected for Wired Connection

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: gnome-control-center 1:3.34.1-1ubuntu2
  ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
  Uname: Linux 5.3.0-19-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Oct 28 17:06:43 2019
  InstallationDate: Installed on 2019-08-01 (88 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  SourcePackage: gnome-control-center
  UpgradeStatus: Upgraded to eoan on 2019-10-28 (0 days ago)

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

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

[Desktop-packages] [Bug 1848852] Re: Counter-Strike Global Offensive freezes in gnome-shell

2019-10-29 Thread Emanuele

I have the same problem, I start CS: GO, after a while I see a warning window
that the game is locked, so click "careful" or "force shut", but it is not
clickable and nothing happens. I have to force the game to close.
I attach the logs.

GPU: NVIDIA GTX 750 ti
Driver: nvidia-driver-435 / eoan, now 435.21-0ubuntu2 amd64 [installed]

** Attachment added: "Log"

https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1848852/+attachment/5301130/+files/logcsgo

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

Title:
Counter-Strike Global Offensive freezes in gnome-shell

Status in GNOME Shell:
New
Status in gnome-shell package in Ubuntu:
Triaged

Bug description:
After upgrade to ubuntu 19.10, when I launch counter strike global offensive
from steam the game is frozen. I can alt-tab and close the game. Tried in
fluxbox window manager where the game works, changed fullscreen to windowed
fullscreen in the options and tried on gnome again, now the desktop isn't
responding after launching the game and I had to ctrl-alt-f3 to reboot my
machine.
Using a Radeon RX 580 video card.

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

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

[Desktop-packages] [Bug 1848852] Re: Counter-Strike Global Offensive freezes in gnome-shell

2019-10-29 Thread Emanuele

I noticed right now that in the logs I keep spam:


ott 29 13:16:33 emanuc gnome-shell[2708]: == Stack trace for context 
0x561e054d9590 ==
ott 29 13:16:33 emanuc gnome-shell[2708]: #0   7fff70acb170 b   
resource:///org/gnome/shell/ui/workspace.js:695 (7f659cb72c10 @ 15)
ott 29 13:16:33 emanuc gnome-shell[2708]: #1   7fff70acb220 b   self-hosted:975 
(7f659ca2dee0 @ 392)
ott 29 13:16:33 emanuc gnome-shell[2708]: Object St.Button (0x561e09289ca0), 
has been already deallocated — impossible to get any property from it. This 
might be caused by the object having been destroyed from C code using something 
such as destroy(), dispose(), or remove() vfuncs.
ott 29 13:16:33 emanuc gnome-shell[2708]: == Stack trace for context 
0x561e054d9590 ==
ott 29 13:16:33 emanuc gnome-shell[2708]: #0   7fff70acb170 b   
resource:///org/gnome/shell/ui/workspace.js:695 (7f659cb72c10 @ 15)
ott 29 13:16:33 emanuc gnome-shell[2708]: #1   7fff70acb220 b   self-hosted:975 
(7f659ca2dee0 @ 392)
ott 29 13:16:33 emanuc gnome-shell[2708]: Object St.Button (0x561e0c6b33d0), 
has been already deallocated — impossible to get any property from it. This 
might be caused by the object having been destroyed from C code using something 
such as destroy(), dispose(), or remove() vfuncs.
ott 29 13:16:33 emanuc gnome-shell[2708]: == Stack trace for context 
0x561e054d9590 ==
ott 29 13:16:33 emanuc gnome-shell[2708]: #0   7fff70acb170 b   
resource:///org/gnome/shell/ui/workspace.js:695 (7f659cb72c10 @ 15)
ott 29 13:16:33 emanuc gnome-shell[2708]: #1   7fff70acb220 b   self-hosted:975 
(7f659ca2dee0 @ 392)
ott 29 13:16:34 emanuc gnome-shell[2708]: Object St.Button (0x561e09289ca0), 
has been already deallocated — impossible to get any property from it. This 
might be caused by the object having been destroyed from C code using something 
such as destroy(), dispose(), or remove() vfuncs.
ott 29 13:16:34 emanuc gnome-shell[2708]: == Stack trace for context 
0x561e054d9590 ==
ott 29 13:16:34 emanuc gnome-shell[2708]: #0   7fff70acb170 b   
resource:///org/gnome/shell/ui/workspace.js:695 (7f659cb72c10 @ 15)
ott 29 13:16:34 emanuc gnome-shell[2708]: #1   7fff70acb220 b   self-hosted:975 
(7f659ca2dee0 @ 392)
ott 29 13:16:34 emanuc gnome-shell[2708]: Object St.Button (0x561e0c6b33d0), 
has been already deallocated — impossible to get any property from it. This 
might be caused by the object having been destroyed from C code using something 
such as destroy(), dispose(), or remove() vfuncs.
ott 29 13:16:34 emanuc gnome-shell[2708]: == Stack trace for context 
0x561e054d9590 ==
ott 29 13:16:34 emanuc gnome-shell[2708]: #0   7fff70acb170 b   
resource:///org/gnome/shell/ui/workspace.js:695 (7f659cb72c10 @ 15)
ott 29 13:16:34 emanuc gnome-shell[2708]: #1   7fff70acb220 b   self-hosted:975 
(7f659ca2dee0 @ 392)
ott 29 13:16:34 emanuc gnome-shell[2708]: Object St.Button (0x561e09289ca0), 
has been already deallocated — impossible to get any property from it. This 
might be caused by the object having been destroyed from C code using something 
such as destroy(), dispose(), or remove() vfuncs.
ott 29 13:16:34 emanuc gnome-shell[2708]: == Stack trace for context 
0x561e054d9590 ==
ott 29 13:16:34 emanuc gnome-shell[2708]: #0   7fff70acb170 b   
resource:///org/gnome/shell/ui/workspace.js:695 (7f659cb72c10 @ 15)
ott 29 13:16:34 emanuc gnome-shell[2708]: #1   7fff70acb220 b   self-hosted:975 
(7f659ca2dee0 @ 392)
ott 29 13:16:35 emanuc gnome-shell[2708]: Object St.Button (0x561e0c6b33d0), 
has been already deallocated — impossible to get any property from it. This 
might be caused by the object having been destroyed from C code using something 
such as destroy(), dispose(), or remove() vfuncs.
ott 29 13:16:35 emanuc gnome-shell[2708]: == Stack trace for context 
0x561e054d9590 ==
ott 29 13:16:35 emanuc gnome-shell[2708]: #0   7fff70acb170 b   
resource:///org/gnome/shell/ui/workspace.js:695 (7f659cb72c10 @ 15)
ott 29 13:16:35 emanuc gnome-shell[2708]: #1   7fff70acb220 b   self-hosted:975 
(7f659ca2dee0 @ 392)
ott 29 13:16:35 emanuc gnome-shell[2708]: Object St.Button (0x561e09289ca0), 
has been already deallocated — impossible to get any property from it. This 
might be caused by the object having been destroyed from C code using something 
such as destroy(), dispose(), or remove() vfuncs.
ott 29 13:16:35 emanuc gnome-shell[2708]: == Stack trace for context 
0x561e054d9590 ==
ott 29 13:16:35 emanuc gnome-shell[2708]: #0   7fff70acb170 b   
resource:///org/gnome/shell/ui/workspace.js:695 (7f659cb72c10 @ 15)
ott 29 13:16:35 emanuc gnome-shell[2708]: #1   7fff70acb220 b   self-hosted:975 
(7f659ca2dee0 @ 392)

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

Title:
  Counter-Strike Global Offensive freezes in gnome-shell

Status in GNOME Shell:
  New
Status in gnome-shell package in Ubuntu:
  Triaged

Bug description:
  After upgrade to ubuntu

[Desktop-packages] [Bug 1850278] Re: Activities overview hot corner setting does not persist

2019-10-29 Thread Michael

Is there an easy way to install GNOME upstream without messing up my
system (this is my main workstation that I depend upon)?

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

Title:
  Activities overview hot corner setting does not persist

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  Steps to reproduce:
  1. Disable activities overview hot corner in GNOME tweaks
  2. See that the hot corner is indeed disabled
  3. Lock the screen
  4. Unlock the screen
  5. See that hot corner is active again (however GNOME tweaks still shows it 
as disabled)

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: gnome-shell 3.34.1-1ubuntu1
  ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
  Uname: Linux 5.3.0-19-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu8
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Oct 29 09:47:00 2019
  DisplayManager: gdm3
  InstallationDate: Installed on 2018-09-02 (421 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  ProcEnviron:
   LANGUAGE=en_IL:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_IL
   SHELL=/bin/bash
  RelatedPackageVersions: mutter-common 3.34.1-1ubuntu1
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to eoan on 2019-10-27 (1 days ago)

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

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

[Desktop-packages] [Bug 1850282] Re: Chromium disappears from system on refresh

2019-10-29 Thread Simon Lambourn

(And just to add insult to injury - you can't even report a bug using
ubuntu-bug chromium!  You get an error message saying "this is produced
by Canonical - for help visit .  The url is not
properly clickable, perhaps because Chromium is not working, and you
can't select it and copy it into another browser.)

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

Title:
  Chromium disappears from system on refresh

Status in chromium-browser package in Ubuntu:
  New

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

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

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

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

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

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

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

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

[Desktop-packages] [Bug 1842865] Re: Xubuntu 18.04 sometimes freezes when turned on on logo

2019-10-29 Thread Maxim Smih

Thank you for the article. Now I'll see how the computer works with the
4.18 kernel. Most likely it is a kernel 5.0 problem or systemd

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1842865

Title:
  Xubuntu 18.04 sometimes freezes when turned on on logo

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Sometimes, when I turn off the computer, it hangs on the logo. I can
  not turn off the computer using alt + SysRq + REISUO. The light on the
  system unit continues to light, and the fan runs. This is a problem
  with kernel 5.0, 5.3.

  There is no such problem with the 4.15 kernel. It happens that after
  90 seconds it turns off. And with a new core, he writes that he will
  turn off after 90 seconds, but he will not turn off.

  Here is the error:
  info: task systemd shutdown:1 blocked for more than 120 seconds
  Not tainted 5.0.0-20-generic #21-Ubuntu
  «echo 0 /proc/sys kernel/hung_task_timeout_secs» disables this message

  https://ibb.co/PcYvDLq
  https://ibb.co/4JMGwvC

  sudo dmesg|grep ACPI|less -  https://pastebin.com/PZxRGNyJ

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Пакет: gvfs 1.36.1-0ubuntu1.3.3
  ProcVersionSign ature: Ubuntu 5.0.0-27. 28 ~ 18,04. 1-generic 5.0.21
  Uname: Linux 5.0.0-27-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.7
  Архитектура: amd64
  CurrentDesktop: XFCE
  Дата: Четверг 5 09:44:35 2019 Дата
  установки: установлено в 2019-08 -09 (26 дней назад)
  InstallationMedia: Xubuntu 18.04.2 LTS «Бионический бобр» - выпуск amd64 
(20190210)
  ProcEnviron:
   LANGUAGE = ru_UA: ru
   PATH = (пользовательский, нет пользователя)
   XDG_RUNTIME_ DIR = 
   LANG = ru_UA.UTF -8
   SHELL = / bin / bash
  SourcePackage: gvfs
  UpgradeStatus: журнал обновления отсутствует (возможно, новая установка)
  ---
  Тип проблемы: ошибка
  ApportVersion: 2.20.9-0ubuntu7.7
  Архитектура: amd64
  AudioDevicesInUse:
   КОМАНДА ДОСТУПА ПОЛЬЗОВАТЕЛЯ PID
   / dev / snd / controlC0: макс. 1055 F  pulseaudio
  CurrentDesktop: XFCE
  DistroRelease: Ubuntu 18.04
  InstallationDate: Установлен 2019-08-09 (37 дней назад)
  InstallationMedia: Xubuntu 18.04.2 LTS "Bionic Beaver" - Выпуск amd64 
(20190210)
  IwConfig:
   enp0s25 без беспроводных расширений.

   enp7s4 нет беспроводных расширений.

   нет никаких беспроводных расширений.
  Тип машины: Hewlett-Packard HP Compaq dc5800 Microtower
  Пакет: Linux (не установлен)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE = / загрузки / vmlinuz- 4.15.0- 62-общий корень 
= UUID = 8c77fe78- d1d9-4452- aca0-eb1f844041 22 ро тихий всплеск vt.handoff = 1
  ProcVersionSign ature: Ubuntu 4.15.0- 62,69-родовое 4.15.18
  RelatedPackageV ersions:
   linux- restricted- modules- 4.15.0- 62-родовое N / A
   linux- backports- modules- 4.15.0 - 62-типовой N / A
   linux-прошивка 1.173.9
  RfKill:

  Теги: bionic
  Uname: Linux 4.15.0-62-generic x86_64
  UpgradeStatus: нет журнала обновления (возможно, новая установка)
  Группы пользователей: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 26.10.2015
  dmi. bios.vendor: Hewlett-Packard
  dmi.bios.version: 786F2 v01.60
  dmi.board. asset.tag: CZC8107S1Y
  dmi.board.name: 2820h
  dmi.board.vendor: Hewlett-Packard
  dmi.chassis. asset.tag: CZC8107S1Y
  dmi.chassis.type: 6
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: dmi: bvnHewlett- Packard: bvr786F2v01. 60: bd10 / 26/2015: 
svnHewlett- Packard:pnHPCompaqdc580 0Microtower: pvr: rvnHewlett- Packard: 
rn2820h: rvr: cvnHewlett- Packard: ct6: cvr:
  dmi.product.family: 103C_53307F
  dmi.product.name: HP Compaq dvtwelet dv00 от компании HP
  :

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

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

[Desktop-packages] [Bug 1638395] Re: Unable to locate remote printer when printing

2019-10-29 Thread jolly stark

the remote printing is basically a kind of printing which contains a
distant printer. it is used for business purposes mainly while we are
traveling it is an alternative term of fax.it make things easy like we
don't need to carry papers while we are traveling remote printer make
this problem easy for us. but when we can not find this remote printer
then it's a big issue to sort out this problem read this article and do
step by step as instructed here.

www.facebook.com

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

Title:
  Unable to locate remote printer when printing

Status in cups package in Ubuntu:
  Confirmed

Bug description:
  My printer (EPSON Stylus Photo RX520) is connected to a  Yakkety station 
called "paris" which is the printing server. 
  Printing is fine from the server.

  When i configure another Yakkety station to print via this server, the 
printer is detected OK via dnssd, the driver is installed OK. But i can't 
print. 
  I get the following message "Unable to locate printer "paris.local"."

  I used to work on xenial but the connection was through ipps. I tried
  to configure the connection as in xenial, to no avail ...

  What i did: 
  add "192.168.1.4 paris.local" in /etc/hosts
  remove printer from cups, reinstalled it and i finally was able to print on 
the remote printer!

  Don't know if this problem is related to cups or avahi ...

  Ubuntu 16.10
  cups 2.2.0-2

  What i expected to happen: printing successful
  What happened: client cannot locate remote printer, add to add a line in 
/etc/hosts to make it work

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

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

[Desktop-packages] [Bug 1793410] Re: [Acer Swift SF315-52, Realtek ALC256, Mic, Internal] Internal microphone not working

2019-10-29 Thread serg

the same issue here with
Swift 314-54

just did the support ticket as well

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

Title:
  [Acer Swift SF315-52, Realtek ALC256, Mic, Internal] Internal
  microphone not working

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  Recently bought a new Acer Swift 3 laptop and installed Ubuntu 18.04
  on it. Everything works except the internal microphone. I have also
  tested with an external microphone and this didn't work either.

  I have worked my way through all the suggested solutions I could find,
  including trying to reconfigure the pins using hdajacketask. In
  pavucontrol I have options for Internal Microphone and Microphone
  (unplugged) but the internal mic only captures static noise.

  The latest HD-Audio Codec-Specific Models has configurations for
  alc255-acer and alc256 for some other models, but setting options snd-
  hda-intel model=MODEL in /etc/modprobe.d/alsa-base.conf does not solve
  the issue with any of these.

  Some info -

  lspci | grep -I audio:

  00:1f.3 Multimedia audio controller: Intel Corporation Sunrise Point-
  LP HD Audio (rev 21)

  
  cat /proc/asound/cards:

   0 [PCH ]: HDA-Intel - HDA Intel PCH
HDA Intel PCH at 0xdf1a8000 irq 127

  
  dmesg | grep snd:

  [3.944593] snd_hda_core: loading out-of-tree module taints kernel.
  [3.956337] snd_soc_skl: Unknown symbol snd_hdac_display_power (err 0)
  [3.956422] snd_soc_skl: Unknown symbol snd_hdac_i915_exit (err 0)
  [4.000880] snd_hda_intel :00:1f.3: Probing card using HDA DKMS, 
version 0.201808050301~ubuntu18.04.1
  [4.000895] snd_hda_intel :00:1f.3: enabling device ( -> 0002)
  [4.013061] snd_hda_codec_realtek hdaudioC0D0: autoconfig for ALC256: 
line_outs=1 (0x14/0x0/0x0/0x0/0x0) type:speaker
  [4.013063] snd_hda_codec_realtek hdaudioC0D0:speaker_outs=0 
(0x0/0x0/0x0/0x0/0x0)
  [4.013065] snd_hda_codec_realtek hdaudioC0D0:hp_outs=1 
(0x21/0x0/0x0/0x0/0x0)
  [4.013066] snd_hda_codec_realtek hdaudioC0D0:mono: mono_out=0x0
  [4.013066] snd_hda_codec_realtek hdaudioC0D0:inputs:
  [4.013068] snd_hda_codec_realtek hdaudioC0D0:  Mic=0x18
  [4.013069] snd_hda_codec_realtek hdaudioC0D0:  Internal Mic=0x12

  
  info on node 12 from cat /proc/asound/card*/codec\#*:

  Node 0x12 [Pin Complex] wcaps 0x40040b: Stereo Amp-In
Control: name="Internal Mic Boost Volume", index=0, device=0
  ControlAmp: chs=3, dir=In, idx=0, ofs=0
Amp-In caps: ofs=0x00, nsteps=0x03, stepsize=0x27, mute=0
Amp-In vals:  [0x02 0x02]
Pincap 0x0020: IN
Pin Default 0x4000: [N/A] Line Out at Ext N/A
  Conn = Unknown, Color = Unknown
  DefAssociation = 0x0, Sequence = 0x0
Pin-ctls: 0x20: IN
Power states:  D0 D1 D2 D3 EPSS
Power: setting=D0, actual=D0

  Let me know if you need any other information.

  James

  ---

  Tags:  bionic
  Uname: Linux 4.15.0-34-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  _MarkForUpload: True
  dmi.bios.date: 06/22/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: V1.04
  dmi.board.asset.tag: Default string
  dmi.board.name: Erdinger_KL
  dmi.board.vendor: KBL
  dmi.board.version: V1.04
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: V1.04
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrV1.04:bd06/22/2018:svnAcer:pnSwiftSF315-52:pvrV1.04:rvnKBL:rnErdinger_KL:rvrV1.04:cvnAcer:ct10:cvrV1.04:
  dmi.product.family: Swift 3
  dmi.product.name: Swift SF315-52
  dmi.product.version: V1.04
  dmi.sys.vendor: Acer

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

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

[Desktop-packages] [Bug 1850159] Re: gnome-control-center reports Ethernet Connection Failure while Connection success

2019-10-29 Thread Mikhail

1) Status switched to "Connecting" for 20-30 secs
2) UI asked for private key password
3) Status switched to "Disconnected"

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

Title:
  gnome-control-center reports Ethernet Connection Failure while
  Connection success

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

Bug description:
  gnome-control-center reports Ethernet Connection Failure with TLS
  Authentication

  1) Ubuntu 19.10
  2) 1:3.34.1-1ubuntu2
  3) Show Connected for Wired Connection
  4) Show Disconnected for Wired Connection

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: gnome-control-center 1:3.34.1-1ubuntu2
  ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
  Uname: Linux 5.3.0-19-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Oct 28 17:06:43 2019
  InstallationDate: Installed on 2019-08-01 (88 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  SourcePackage: gnome-control-center
  UpgradeStatus: Upgraded to eoan on 2019-10-28 (0 days ago)

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

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

[Desktop-packages] [Bug 1850282] [NEW] Chromium disappears from system on refresh

2019-10-29 Thread Simon Lambourn

Public bug reported:

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

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

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

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

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

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

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

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

Title:
  Chromium disappears from system on refresh

Status in chromium-browser package in Ubuntu:
  New

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

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

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

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

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

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

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

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

[Desktop-packages] [Bug 1849950] Re: Gnome Shell window shortcuts maximize, windowed and hide (Super + Up / Down / H) don't work if upgrading from Unity

Unity and GNOME used to share their schemas so any config change done in
Unity would impact GNOME session, that was fixed in 19.10 and Unity now
has its own schemas. We can't tell appart old configs from Unity from
users who changed their GNOME config so we can't really reset those on
upgrade. Closing as we can't really handle better the upgrade but 19.10
fixes the issue for new installs

** Changed in: gsettings-desktop-schemas (Ubuntu)
   Status: New => Fix Released

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

Title:
  Gnome Shell window shortcuts maximize, windowed and hide (Super + Up /
  Down / H) don't work if upgrading from Unity

Status in GNOME Shell:
  Fix Released
Status in gsettings-desktop-schemas package in Ubuntu:
  Fix Released

Bug description:
  Happens on Ubuntu 19.10, and did also not work on Ubuntu 19.04 (and
  probably also previous versions), if I recall correctly.

  I am not sure, whether this is an upstream bug of GNOME or just Ubuntu
  related.

  Bug report for GNOME: https://gitlab.gnome.org/GNOME/gnome-
  shell/issues/1829

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

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

[Desktop-packages] [Bug 1850214] Re: gnome-shell crashed with SIGTRAP in g_settings_schema_get_value() from g_settings_schema_get_value() from g_settings_schema_key_init() from g_settings_get_value()

Looking to some of the error reports, some have that in their journal

systemd[1043]: gnome-session-manager@gnome-login.service: Failed with result 
'exit-code'.
gnome-shell[2350]: Settings schema 'org.gnome.desktop.peripherals.keyboard' 
does not contain a key named 'remember-numlock-state'
systemd[1043]: gnome-shell-x11.service: Main process exited, code=dumped, 
status=5/TRAP

where 'gsettings-desktop-schemas 3.34.0-1ubuntu1'

or


gnome-session-binary[2189]: WARNING: Application 
'org.gnome.SettingsDaemon.MediaKeys.desktop' killed by signal 5
gsd-media-keys[2311]: Settings schema 
'org.gnome.settings-daemon.plugins.media-keys.deprecated' is not installed
systemd[1034]: gnome-shell-x11.service: Main process exited, code=dumped, 
status=5/TRAP


It's the old 'gsettings abort when schemas/keys are missing', the e.u.c reports 
don't include a procmaps or enough informations to tell what's going on exactly 
but it's likely that either the schemas cache update failed or is taken over by 
a /usr/local/ version or similar which is outdated/doesn't include the new key

Likely an installation/local problem more than a gnome-shell issue,
unsure if we should close the report?

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

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

Title:
  gnome-shell crashed with SIGTRAP in g_settings_schema_get_value() from
  g_settings_schema_get_value() from g_settings_schema_key_init() from
  g_settings_get_value() from g_settings_get_boolean()

Status in gnome-shell package in Ubuntu:
  New

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

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

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

[Desktop-packages] [Bug 1850278] Re: Activities overview hot corner setting does not persist

Thank you for your bug report, could you try if it happens in a GNOME
upstream session? If so could you report it upstream on
https://gitlab.gnome.org/GNOME/gnome-shell/issues ?

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

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

Title:
  Activities overview hot corner setting does not persist

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  Steps to reproduce:
  1. Disable activities overview hot corner in GNOME tweaks
  2. See that the hot corner is indeed disabled
  3. Lock the screen
  4. Unlock the screen
  5. See that hot corner is active again (however GNOME tweaks still shows it 
as disabled)

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: gnome-shell 3.34.1-1ubuntu1
  ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
  Uname: Linux 5.3.0-19-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu8
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Oct 29 09:47:00 2019
  DisplayManager: gdm3
  InstallationDate: Installed on 2018-09-02 (421 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  ProcEnviron:
   LANGUAGE=en_IL:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_IL
   SHELL=/bin/bash
  RelatedPackageVersions: mutter-common 3.34.1-1ubuntu1
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to eoan on 2019-10-27 (1 days ago)

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

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

[Desktop-packages] [Bug 1834967] Re: Windows in Activities might be partially off screen

** Tags added: desktop-lts-wishlist

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

Title:
  Windows in Activities might be partially off screen

Status in GNOME Shell:
  New
Status in ubuntu-dock:
  New
Status in gnome-shell package in Ubuntu:
  Confirmed
Status in gnome-shell-extension-dashtodock package in Ubuntu:
  Confirmed
Status in gnome-shell-extension-ubuntu-dock package in Ubuntu:
  Confirmed

Bug description:
  Details in my screenshot: https://photos.app.goo.gl/BR6H56eug7JFMGU37

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: gnome-shell 3.32.2-2ubuntu1
  ProcVersionSignature: Ubuntu 5.0.0-17.18-generic 5.0.8
  Uname: Linux 5.0.0-17-generic x86_64
  ApportVersion: 2.20.11-0ubuntu3
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Jul  1 20:38:43 2019
  DisplayManager: gdm3
  InstallationDate: Installed on 2019-07-01 (0 days ago)
  InstallationMedia:
   
  ProcEnviron:
   LANGUAGE=ru_UA:ru
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=ru_UA.UTF-8
   SHELL=/bin/bash
  RelatedPackageVersions: mutter-common 3.32.2+git20190626-1ubuntu1
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1850275] Re: English-Europe locale missing