date:20190909

I referring to the variant with the TCL dispatcher in the first PPA. You
described this version in #4 as "dispatcher-c-rewrite.patch disabled" so
this is why I call it like this.

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

Title:
  usb-modeswitch can't apply Configuration=0 to Snapdragon X12 LTE

Status in usb-modeswitch package in Ubuntu:
  In Progress

Bug description:
  Please refer to post of usb-modeswitch developer
  http://www.draisberghof.de/usb_modeswitch/bb/viewtopic.php?f=4&t=2827
  for complete issue description.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/usb-modeswitch/+bug/1800794/+subscriptions

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

[Desktop-packages] [Bug 1840874] Re: Mono Runtime error because of bug in LargeArrayBuilder in Mono 5.18

2019-09-09 Thread Timotheus Pokorra

the patch has now been used in Debian Unstable:
https://tracker.debian.org/news/1063115/accepted-mono-5180240dfsg-4-source-all-amd64-into-unstable/

Any chance to get this still into Ubuntu 19.10?
Is there anything I can help?

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

Title:
  Mono Runtime error because of bug in LargeArrayBuilder in Mono 5.18

Status in mono package in Ubuntu:
  New

Bug description:
  This bug happens in Mono 5.18, in Ubuntu Disco (19.04).
  I am using the package 5.18.0.240+dfsg-2ubuntu2.

  You can reproduce the bug with the attached test program.
  It has been fixed upstream in Mono 5.20, with quite a simple patch.

  I got the patch merged into the Debian Mono package:
  https://salsa.debian.org/dotnet-team/mono/merge_requests/3

  Is there any chance, this patch could be applied to the next Ubuntu
  release (19.10), or even Ubuntu Disco (19.04)?

  See for more details:
  https://bugzilla.redhat.com/show_bug.cgi?id=1704847
  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=919194

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

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

[Desktop-packages] [Bug 1714881] Re: no gdm3 greeter with nvidia quadro and modeset=1, discrete nvidia (not optimus)

** Changed in: gdm3 (Ubuntu)
   Status: Fix Released => Triaged

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

Title:
  no gdm3 greeter with nvidia quadro and modeset=1, discrete nvidia (not
  optimus)

Status in gdm:
  Expired
Status in gdm3 package in Ubuntu:
  Triaged

Bug description:
  This is to track 
  https://bugzilla.gnome.org/show_bug.cgi?id=787207 " gdm & nvidia with 
modeset=1 causes loop, does not launch greeter "

  I don't know if this is an nvidia bug or a gdm3 bug but it requires
  both to reproduce.

  
  [reply] [−] Description t...@tim-richardson.net [reporter] 2017-09-03 
10:46:21 UTC
  Created attachment 359016 [details]
  syslog

  reproduced on two Thinkpad laptops with bios set to Discrete graphics.
  In this mode, the integrated Intel graphics is bypassed by a hardware
  mux and the machines appears to have only Nvidia graphics.

  Environment is Ubuntu 17.10 development version, pre-release packages
  One laptop has Quadro 1000M, the other Quadro M1000M. Both cards are 
supported by the latest Nvidia drivers. 

  Nvidia driver 375 or 384 (as packaged by Ubuntu)
  /etc/modprobe.d/zz-nvidia.conf has
  options nvidia_384_drm modeset=1

  and after that setting 
  sudo update-initramfs -u

  This problem does not occur when 
  lightdm is used in instead of gdm3
  or
  modeset=1 
  is not deployed.

  The session attempted to launch is either gnome or the new "ubuntu"
  desktop session, which is gnome

  The boot process fails.Sometimes there is just black screen (and high
  CPU activity driving the fans) and sometimes there is a message about
  NVIDIA persistence daemon starting and stopping, as well as gdm
  messages.

  I mounted the filesystem after a crash, and I attach syslog.

  In the attached syslog, search for persistenced to see messages like
  this

  Sep  2 12:42:15 tim-ThinkPad-W520 org.gnome.Shell.desktop[1206]: Window 
manager warning: Failed to create renderer: Failed
   to initialize renderer: Missing extension for GBM renderer: 
EGL_KHR_platform_gbm, Failed to find matching EGLDeviceEXT
   Sep  2 12:42:15 tim-ThinkPad-W520 gnome-shell[1206]: Failed to create 
backend: Failed to create MetaRenderer
   Sep  2 12:42:15 tim-ThinkPad-W520 systemd[1]: Starting NVIDIA Persistence 
Daemon...
   Sep  2 12:42:15 tim-ThinkPad-W520 nvidia-persistenced: Verbose syslog 
connection opened
   Sep  2 12:42:15 tim-ThinkPad-W520 nvidia-persistenced: Now running with user 
ID 123 and group ID 131
   Sep  2 12:42:15 tim-ThinkPad-W520 systemd[1]: Started NVIDIA Persistence 
Daemon.
   Sep  2 12:42:15 tim-ThinkPad-W520 nvidia-persistenced: Started (1237)
   Sep  2 12:42:15 tim-ThinkPad-W520 gnome-session[1196]: 
gnome-session-binary[1196]: WARNING: App 'org.gnome.Shell.desktop'
   exited with code 1
   Sep  2 12:42:15 tim-ThinkPad-W520 gnome-session-binary[1196]: WARNING: App 
'org.gnome.Shell.desktop' exited with code 1
   Sep  2 12:42:15 tim-ThinkPad-W520 gnome-session-binary[1196]: Unrecoverable 
failure in required component org.gnome.Shell.
   desktop
   Sep  2 12:42:15 tim-ThinkPad-W520 systemd-networkd-wait-online[536]: 
ignoring: lo
   Sep  2 12:42:15 tim-ThinkPad-W520 systemd[1]: Stopping NVIDIA Persistence 
Daemon...
   Sep  2 12:42:15 tim-ThinkPad-W520 nvidia-persistenced: Received signal 15
   Sep  2 12:42:15 tim-ThinkPad-W520 nvidia-persistenced: PID file unlocked.
   Sep  2 12:42:15 tim-ThinkPad-W520 nvidia-persistenced: PID file closed.
   Sep  2 12:42:15 tim-ThinkPad-W520 nvidia-persistenced: The daemon no longer 
has permission to remove its runtime data
   directory /var/run/nvidia-persistenced
   Sep  2 12:42:15 tim-ThinkPad-W520 nvidia-persistenced: Shutdown (1237)

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

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

[Desktop-packages] [Bug 1835956] Re: Deleting "Input Sources" not in use, affects the ones in use.

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

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

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

Title:
  Deleting "Input Sources" not in use, affects the ones in use.

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

Bug description:
  I have a notebook, with an english keyboard layout, so "English (Us,
  intl, with dead keys) was my only option in "Region & Language / Input
  Sources".

  Now I want to use an external keyboard, which has a spanish
  distribution, so I tried adding "Spanish" (Let's call it "es1") to my
  "Input Sources" list. This is not quite my distribution, so I added a
  few more to try: "Spanish (with Sun Dead keys)" (es2), "Spanish (Latin
  American, with Sun dead keys)" (es3) and "Spanish (Win keys)" (es4).

  So after trying all this 4 options in spanish layouts, I decided that
  I want to use the (es4) option, because it fits my keyboard exactly,
  and I won't be needing any of the others spanish options. Just want to
  keep one for english and one for spanish.

  Now comes the strange behaviour: while "es4" is still my layout option
  in use, I go to "Input Sources" configuration and delete the input
  sources I won't be using (es1, es2 and es3). After deleting, I only
  have two options, one for english and one for spanish. The available
  keyboard layout for spanish is the same one I chose before, "Spanish
  (Win keys), but after deleting the other ones, this layout doesn't fit
  my keyboard any more. Some keys don't give me the same characters as
  they did when I was trying all the options and had the others layouts
  installed, but not in use.

  I've also noticed that installing a keyboard layout behaves different
  depending on whether there are other layouts installed or not.  For
  example, if I install and use "Spanish" layout, when there is only
  "English" I don't get the same results if I install and use it when
  there are other "Spanish input sources" already installed.

  
  Cheers

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-control-center 1:3.28.2-0ubuntu0.18.04.4
  ProcVersionSignature: Ubuntu 4.15.0-54.58-generic 4.15.18
  Uname: Linux 4.15.0-54-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.7
  Architecture: amd64
  CurrentDesktop: communitheme:ubuntu:GNOME
  Date: Tue Jul  9 16:37:29 2019
  ExecutablePath: /usr/bin/gnome-control-center
  InstallationDate: Installed on 2018-07-05 (369 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  SourcePackage: gnome-control-center
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1825499] Re: Touchpad vertical sensitivity is much higher than horizontal sensitivity [HP Pavilion g6]

** Project changed: libinput => systemd

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

Title:
  Touchpad vertical sensitivity is much higher than horizontal
  sensitivity [HP Pavilion g6]

Status in systemd:
  Fix Released
Status in libinput package in Ubuntu:
  Invalid
Status in linux package in Ubuntu:
  Invalid
Status in systemd package in Ubuntu:
  New

Bug description:
  After installing Kubuntu 19.04, I found that vertical sensitivity is much 
higher than horizontal sensitivity.
  Installing xserver-xorg-input-synaptics improved the situation a bit and 
enabled KDE touchpad setting that were disabled.

  It's very annoying.

  Laptop: HP Pavilion g6.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: xserver-xorg-input-synaptics 1.9.1-1ubuntu1
  ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6
  Uname: Linux 5.0.0-13-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CurrentDesktop: KDE
  Date: Fri Apr 19 12:00:02 2019
  DistUpgraded: Fresh install
  DistroCodename: disco
  DistroVariant: ubuntu
  MachineType: Hewlett-Packard HP Pavilion g6 Notebook PC
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.0.0-13-generic 
root=UUID=e1903286-a666-49b1-8177-cf31dc5c8e9f ro quiet splash vt.handoff=1
  SourcePackage: xserver-xorg-input-synaptics
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/29/2013
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.25
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 183E
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 56.32
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.25:bd05/29/2013:svnHewlett-Packard:pnHPPaviliong6NotebookPC:pvr088512005D160:rvnHewlett-Packard:rn183E:rvr56.32:cvnHewlett-Packard:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV G=N L=CON B=HP S=PAV X=Null
  dmi.product.name: HP Pavilion g6 Notebook PC
  dmi.product.sku: D4Z91EA#ABV
  dmi.product.version: 088512005D160
  dmi.sys.vendor: Hewlett-Packard
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.97-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.2-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-0ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20180925-2
  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/systemd/+bug/1825499/+subscriptions

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

[Desktop-packages] [Bug 1842898] Re: Scroll bar in the focussed Terminal window is almost invisible

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

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

Title:
  Scroll bar in the focussed Terminal window is almost invisible

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

Bug description:
  Scroll bar in the focussed Terminal window is almost invisible.

  Strangely it's quite visible for all the other (unfocussed) Terminal
  windows.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: yaru-theme-gtk 19.10.1
  ProcVersionSignature: Ubuntu 5.2.0-15.16-generic 5.2.9
  Uname: Linux 5.2.0-15-generic x86_64
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  Date: Thu Sep  5 17:50:51 2019
  InstallationDate: Installed on 2019-05-02 (126 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan EANIMAL" - Alpha amd64 (20190501)
  PackageArchitecture: all
  SourcePackage: yaru-theme
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1779432] Re: [upstream] Libre Writer doesn't do duplex printing

Launchpad has imported 43 comments from the remote bug at
https://bugs.documentfoundation.org/show_bug.cgi?id=60428.

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

On 2013-02-07T16:36:26+00:00 klinge wrote:

Problem description: it's not possible to print duplex from LO. it works
from all other software. I tried all kind of different settings with no
luck.

Steps to reproduce:
1. print
2. change settings to duplex

Current behavior: prints still single paged

Expected behavior: should print douplex

Reply at:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1779432/comments/0

On 2013-05-30T20:37:48+00:00 julien2412 wrote:

*** Bug 65007 has been marked as a duplicate of this bug. ***

Reply at:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1779432/comments/1

On 2013-05-30T21:09:42+00:00 julien2412 wrote:

rosgnilk: I put it at New since there's a duplicate (considering "See
also", I think there are more than 1)

Michael: it seems the Duplex printing option are present in several bugtrackers.
Do you know who may help about this?

Reply at:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1779432/comments/2

On 2013-09-07T09:14:06+00:00 I4U wrote:

Same problem with LO 4.0.2.2 and a HP OJ8600+ on Ubuntu 13.04 (64bits)
and HP LPIP 3.13.8. The duplex printing works fine with Adobe reader
(for instance), but can't be set with LO 4.0.2.2.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1779432/comments/3

On 2013-10-29T17:11:59+00:00 Qubit wrote:

Whiteboard: NeedsDuplexPrinter

Reply at:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1779432/comments/4

On 2014-07-19T14:18:27+00:00 D0m1n1k wrote:

*** Bug 70824 has been marked as a duplicate of this bug. ***

Reply at:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1779432/comments/5

On 2014-07-19T14:27:56+00:00 D0m1n1k wrote:

added 60428 as see also, as he has the inverted problem. (default
settings: duplex, LO set to single paged)

therefore i conclude that the duplex setting is just ignored.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1779432/comments/6

On 2014-09-04T17:59:36+00:00 Herman-viaene wrote:

*** Bug 82999 has been marked as a duplicate of this bug. ***

Reply at:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1779432/comments/7

On 2014-09-05T07:42:38+00:00 Qubit wrote:

Remove comma from whiteboard

Reply at:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1779432/comments/8

On 2014-10-19T13:34:03+00:00 mmalmeida wrote:

I confirm this with HP Officejet 8610 with the following software/OS
pairs:

- Ubuntu 12.04 + LO 4.2.6.3
- Windows 8.1 + 4.1.04

Duplex printing is ignored:
- On Ubuntu it prints one page only
- On Windows it doesn't print at all

Reply at:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1779432/comments/9

On 2014-10-31T05:56:44+00:00 Barta-c wrote:

*** Bug 80841 has been marked as a duplicate of this bug. ***

Reply at:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1779432/comments/10

On 2014-11-29T13:44:21+00:00 X-hnfo-t wrote:

Can confirm this for HP Officejet Pro 8100 on Debian 7 Wheezy, too.

Libreoffice 4.2.6.3 does not change settings for duplex and page
flipping.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1779432/comments/11

On 2014-11-29T13:56:17+00:00 Qubit wrote:

(In reply to GwenDragon from comment #11)
> Can confirm this for HP Officejet Pro 8100 on Debian 7 Wheezy, too.
> 
> Libreoffice 4.2.6.3 does not change settings for duplex and page flipping.

Thanks for the repro! This has been a tricky bug, as it requires some
specific hardware.

Gwen/Miguel: Could one of you try bibisecting to see when this problem first 
appeared in LibreOffice?
https://wiki.documentfoundation.org/Bibisect

Even checking with a LibreOffice 3.5 bu

[Desktop-packages] [Bug 1141034]

2019-09-09 Thread Thomas-lendo

The insert column commands are titled "before" and "after" and the
insert rows commands are titled "above" and "below".

If used in RTL cells, the behavior also is false like the text in the
'Insert...' dialog. If something will be changed here also the
'Delete...' dialog and the above mentioned column/row commands must be
taken into account.

I doubt this is technically possible? What with only partially RTL
columns/rows? How could LibreOffice decide if it's LTR, RTL, whatever?

But to come to this bug report: As columns and rows commands were
renamed, also the 'Delete...' and 'Insert...' dialog must be changed:

* Insert... > Shift cells right > Shift cells after
* Delete... > Shift cells left  > Shift cells before

This isn't what the bug opener wants but it would be at least the same
naming than in other commands.

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

Title:
  RTL Spreadsheet Insert Cells

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

Bug description:
  When using a right-to-left spreadsheet, right clicking and selected
  "insert cells" shows the normal LTR option to shift cells right,
  although when used it actually shifts cells left.

  I believe that shifting cells left is the correct behaviour in this
  case, but the text of the option should be changed to read "shift
  cells left". This was first noticed when using the Hebrew language
  user interface, but the problem is present when using English UI too.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: libreoffice-calc 1:3.5.7-0ubuntu4
  ProcVersionSignature: Ubuntu 3.2.0-38.61-generic 3.2.37
  Uname: Linux 3.2.0-38-generic i686
  ApportVersion: 2.0.1-0ubuntu17.1
  Architecture: i386
  CheckboxSubmission: ad9a15703e19217cb3448f881e125f6a
  CheckboxSystem: abc83e3988b72e7c3a9b3aa684cb92fd
  Date: Sun Mar  3 00:47:21 2013
  MarkForUpload: True
  SourcePackage: libreoffice
  UpgradeStatus: Upgraded to precise on 2012-05-01 (305 days ago)

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

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

[Desktop-packages] [Bug 1843362] [NEW] /usr/bin/gnome-shell:5:_g_log_abort:g_log_writer_default:g_log_structured_array:g_log_structured_standard:gtk_style_context_init

2019-09-09 Thread errors.ubuntu.com bug bridge

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

Public bug reported:

The Ubuntu Error Tracker has been receiving reports about a problem regarding 
gnome-shell.  This problem was most recently seen with package version 
3.33.91-1ubuntu1, the problem page at 
https://errors.ubuntu.com/problem/24c4376abbd8ae5c839eacc23bb86d3be4454b6f 
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/.

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


** Tags: cosmic disco eoan

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

Title:
  /usr/bin/gnome-
  
shell:5:_g_log_abort:g_log_writer_default:g_log_structured_array:g_log_structured_standard:gtk_style_context_init

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.33.91-1ubuntu1, the problem page at 
https://errors.ubuntu.com/problem/24c4376abbd8ae5c839eacc23bb86d3be4454b6f 
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/1843362/+subscriptions

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

[Desktop-packages] [Bug 1843362] Re: /usr/bin/gnome-shell:5:_g_log_abort:g_log_writer_default:g_log_structured_array:g_log_structured_standard:gtk_style_context_init

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

** This bug has been marked a duplicate of private bug 1843346

** This bug is no longer a duplicate of private bug 1843346
** This bug has been marked a duplicate of private bug 1841716

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

Title:
  /usr/bin/gnome-
  
shell:5:_g_log_abort:g_log_writer_default:g_log_structured_array:g_log_structured_standard:gtk_style_context_init

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.33.91-1ubuntu1, the problem page at 
https://errors.ubuntu.com/problem/24c4376abbd8ae5c839eacc23bb86d3be4454b6f 
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/1843362/+subscriptions

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

[Desktop-packages] [Bug 1843201] Re: Unity in Wayland prompts for keyboard focus on each run of ssh-askpass-gnome

** Package changed: wayland (Ubuntu) => unity (Ubuntu)

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

Title:
  Unity in Wayland prompts for keyboard focus on each run of ssh-
  askpass-gnome

Status in gnome-desktop package in Ubuntu:
  New
Status in openssh package in Ubuntu:
  Incomplete
Status in unity package in Ubuntu:
  New

Bug description:
  When using a Wayland-based Unity session on Ubuntu 19.04:

  1. Have ssh-askpass-gnome as your askpass program.
  2. ssh-add -c 
  3. `ssh` to a host

  Each time, before the ssh-askpass prompt is shown, Unity shows this
  dialog:

  +-+
  | |
  | ssh-askpass wants to inhibit shortcuts  |
  | |
  | You can restore Shortcuts by pressing   |
  | Super+Escape.   |
  | |
  |_|
  |   Deny | Allow  |
  +-+

  This is mildly distracting, and it means that you need to hit ,
  answer, , instead of just answer .

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: ssh-askpass-gnome 1:7.9p1-10
  ProcVersionSignature: Ubuntu 5.0.0-27.28-generic 5.0.21
  Uname: Linux 5.0.0-27-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27.1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Sep  8 15:04:25 2019
  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   
canonical-oem-somerville-bionic-amd64-20180608-47+tunnels-mlk+X55+tunnels-mlk+X55.1
  InstallationDate: Installed on 2019-08-27 (12 days ago)
  InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 
20180608-09:38
  SourcePackage: openssh
  UpgradeStatus: Upgraded to disco on 2019-08-31 (8 days ago)

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

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

[Desktop-packages] [Bug 1843295] Re: Desktop icons missing when join displays

Reassigning to Nautilus since that provides the desktop and icons.

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

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

Title:
  Desktop icons missing when join displays

Status in nautilus package in Ubuntu:
  New

Bug description:
  In general there isn't any problems. But when I connect my computer to a 
second monitor. Use display mode "Join Displays". Then disappears all my 
desktop icons . 
  If I switch theDisplay mode to "Mirror" or "Single Display" then will all the 
icons come back.

  I have tryied to change ressolution, background, log out and then in
  again, restart, waited in a periode two weeks, updated etc.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 5.0.0-27.28~18.04.1-generic 5.0.21
  Uname: Linux 5.0.0-27-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..02.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:02:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  390.116  Sun Jan 27 07:21:36 
PST 2019
   GCC version:  gcc version 7.4.0 (Ubuntu 7.4.0-1ubuntu1~18.04.1)
  ApportVersion: 2.20.9-0ubuntu7.7
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Sep  9 19:43:41 2019
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus:
   nvidia, 390.116, 5.0.0-25-generic, x86_64: installed
   nvidia, 390.116, 5.0.0-27-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Intel Corporation Device [8086:591b] (rev 04) (prog-if 00 [VGA controller])
 Subsystem: Lenovo Device [17aa:505e]
 Subsystem: Lenovo GM108M [GeForce 940MX] [17aa:505e]
  InstallationDate: Installed on 2019-08-09 (31 days ago)
  InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 
(20190805)
  MachineType: LENOVO 20J60018MD
  ProcEnviron:
   LANGUAGE=en_US:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.0.0-27-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/16/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: R0FET46W (1.26 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20J60018MD
  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:bvrR0FET46W(1.26):bd10/16/2018:svnLENOVO:pn20J60018MD:pvrThinkPadT470p:rvnLENOVO:rn20J60018MD:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad T470p
  dmi.product.name: 20J60018MD
  dmi.product.sku: LENOVO_MT_20J6_BU_Think_FM_ThinkPad T470p
  dmi.product.version: ThinkPad T470p
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.97-1ubuntu1~18.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.8-0ubuntu0~18.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.8-0ubuntu0~18.04.1
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  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/nautilus/+bug/1843295/+subscriptions

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

[Desktop-packages] [Bug 1825499] Re: Touchpad vertical sensitivity is much higher than horizontal sensitivity [HP Pavilion g6]

** Bug watch added: github.com/systemd/systemd/issues #13116
   https://github.com/systemd/systemd/issues/13116

** Also affects: libinput via
   https://github.com/systemd/systemd/issues/13116
   Importance: Unknown
   Status: Unknown

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

Title:
  Touchpad vertical sensitivity is much higher than horizontal
  sensitivity [HP Pavilion g6]

Status in libinput:
  Unknown
Status in libinput package in Ubuntu:
  Invalid
Status in linux package in Ubuntu:
  Invalid
Status in systemd package in Ubuntu:
  New

Bug description:
  After installing Kubuntu 19.04, I found that vertical sensitivity is much 
higher than horizontal sensitivity.
  Installing xserver-xorg-input-synaptics improved the situation a bit and 
enabled KDE touchpad setting that were disabled.

  It's very annoying.

  Laptop: HP Pavilion g6.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: xserver-xorg-input-synaptics 1.9.1-1ubuntu1
  ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6
  Uname: Linux 5.0.0-13-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CurrentDesktop: KDE
  Date: Fri Apr 19 12:00:02 2019
  DistUpgraded: Fresh install
  DistroCodename: disco
  DistroVariant: ubuntu
  MachineType: Hewlett-Packard HP Pavilion g6 Notebook PC
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.0.0-13-generic 
root=UUID=e1903286-a666-49b1-8177-cf31dc5c8e9f ro quiet splash vt.handoff=1
  SourcePackage: xserver-xorg-input-synaptics
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/29/2013
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.25
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 183E
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 56.32
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.25:bd05/29/2013:svnHewlett-Packard:pnHPPaviliong6NotebookPC:pvr088512005D160:rvnHewlett-Packard:rn183E:rvr56.32:cvnHewlett-Packard:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV G=N L=CON B=HP S=PAV X=Null
  dmi.product.name: HP Pavilion g6 Notebook PC
  dmi.product.sku: D4Z91EA#ABV
  dmi.product.version: 088512005D160
  dmi.sys.vendor: Hewlett-Packard
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.97-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.2-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-0ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20180925-2
  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/libinput/+bug/1825499/+subscriptions

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

[Desktop-packages] [Bug 1842882] Re: gnome-control-center no longer shows all the xrandr resolutions

2019-09-09 Thread Rocko

After resuming from suspend, the extra resolutions have disappeared from
g-c-c (but are still available via xrandr), so something is still
triggering the bug.

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

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

Title:
  gnome-control-center no longer shows all the xrandr resolutions

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

Bug description:
  Very recently gnome-control-center started only showing a subset of
  the available screen resolutions. I'll attach a screenshot and also
  the xrandr dump to show what I mean, eg you can see that the 2048x1152
  (16:9) resolution is now missing.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: gnome-control-center 1:3.33.90-1ubuntu2
  ProcVersionSignature: Ubuntu 5.2.0-15.16-generic 5.2.9
  Uname: Linux 5.2.0-15-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Sep  5 15:56:47 2019
  InstallationDate: Installed on 2019-07-01 (65 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190606)
  SourcePackage: gnome-control-center
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1767312] Re: [radeon] Totem with gstreamer1.0-vaapi and Xorg: wrong color on H264 videos

Sounds like we have a semi-permanent workaround now:

gstreamer-vaapi (1.16.0-3ubuntu2) eoan; urgency=medium

  * debian/patches/git_no_amd.patch:
- backport an upstream change to disable vaapi with the amd drivers,
  the current experience is buggy and it's better to just not enable it
  see the discussions on this mailing list and the referenced bug
  https://mail.gnome.org/archives/distributor-list/2019-September

 -- Sebastien Bacher   Mon, 09 Sep 2019 17:09:08
+0200

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

Title:
  [radeon] Totem with gstreamer1.0-vaapi and Xorg: wrong color on H264
  videos

Status in gstreamer-vaapi package in Ubuntu:
  Confirmed
Status in mesa package in Ubuntu:
  Confirmed

Bug description:
  Ii've found a bug on Ubuntu 18.04 (other distros, as fedora 27, debian 
stable, debian testing) aren't affected).
  When i try to reproduce a video that use h264 codec, i've wrong colors.
  I've a notebook with APU AMD A10 8700p, and integrated gpu radeon r6

  WORKAROUND:
  sudo apt remove gstreamer1.0-vaapi
  or
  sudo apt remove mesa-va-drivers

  See also bug 1720820.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gstreamer-vaapi/+bug/1767312/+subscriptions

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

[Desktop-packages] [Bug 1720820] Re: [radeon] Totem with gstreamer1.0-vaapi and Wayland is just a black screen, then crashes.

Sounds like we have a semi-permanent workaround now:

gstreamer-vaapi (1.16.0-3ubuntu2) eoan; urgency=medium

  * debian/patches/git_no_amd.patch:
- backport an upstream change to disable vaapi with the amd drivers,
  the current experience is buggy and it's better to just not enable it
  see the discussions on this mailing list and the referenced bug
  https://mail.gnome.org/archives/distributor-list/2019-September

 -- Sebastien Bacher   Mon, 09 Sep 2019 17:09:08
+0200

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

Title:
  [radeon] Totem with gstreamer1.0-vaapi and Wayland is just a black
  screen, then crashes.

Status in gstreamer-vaapi package in Ubuntu:
  Confirmed
Status in mesa package in Ubuntu:
  Confirmed

Bug description:
  WORKAROUNDS

  Just for totem:  sudo apt remove gstreamer1.0-vaapi

  Or to workaround in all players:  sudo apt remove mesa-va-drivers

  
  ORIGINAL DESCRIPTION

  Totem with gstreamer1.0-vaapi and Wayland crashes on my machine with
  AMD Fury graphics card and open source drivers. Video output is just a
  black frame and crash happens within just a few seconds after video
  playback starts.

  Could not reproduce bug on two older Intel laptops with iGPU's where
  hardware acceleration seemed to work fine under Wayland.

  Issue is only present on Wayland, not x.

  I can get hardware accelerated video playback working on Wayland with
  'mpv --hwdec=vaapi-copy --opengl-backend=wayland' but this is the only
  way I have found so far. Even in mpv, no other option than vaapi-copy
  works.

  gst-play-1.0 outputs the following error:
  ERROR Internal error: could not render surface for file:///***
  ERROR debug information: ../../../gst/vaapi/gstvaapisink.c(1483): 
gst_vaapisink_show_frame_unlocked (): 
/GstPlayBin:playbin/GstPlaySink:playsink/GstBin:vbin/GstVaapiSink:vaapisink0

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

  totem   3.25.90.1-0ubuntu3
  gstreamer1.0-vaapi:amd641.12.3-1ubuntu1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gstreamer-vaapi/+bug/1720820/+subscriptions

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

[Desktop-packages] [Bug 1841897] Re: Cursor missing from slider

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

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

Title:
  Cursor missing from slider

Status in gnome-control-center:
  Fix Released
Status in gnome-control-center package in Ubuntu:
  In Progress
Status in gnome-control-center source package in Eoan:
  In Progress

Bug description:
  There is no cursor on the slider in gnome-control-center (cf
  screenshot)

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: gnome-control-center 1:3.33.90-1ubuntu2
  ProcVersionSignature: Ubuntu 5.2.0-13.14-generic 5.2.8
  Uname: Linux 5.2.0-13-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Aug 29 09:59:11 2019
  InstallationDate: Installed on 2014-07-15 (1870 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20140520)
  SourcePackage: gnome-control-center
  UpgradeStatus: Upgraded to eoan on 2018-03-24 (522 days ago)

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

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

[Desktop-packages] [Bug 1691678] Re: Scrollbars escape the bottom and right side of the Terminal window by 1px

** Changed in: gnome-terminal
   Status: Unknown => Fix Released

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

Title:
  Scrollbars escape the bottom and right side of the Terminal window by
  1px

Status in GNOME Terminal:
  Fix Released
Status in gnome-terminal package in Ubuntu:
  Confirmed
Status in gtk+3.0 package in Ubuntu:
  Confirmed
Status in ubuntu-themes package in Ubuntu:
  Confirmed
Status in yaru-theme package in Ubuntu:
  Fix Released

Bug description:
  Ubuntu's orange overlay scrollbars escape the bottom of the window
  during resizing.

  To reproduce try gnome-shell on artful using the Ambiance theme. Open
  a Terminal window and resize it vertically, quickly. Notice the bottom
  of the overlay scrollbar overruns the bottom of the window.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.24.2-0ubuntu3
  ProcVersionSignature: Ubuntu 4.10.0-20.22-generic 4.10.8
  Uname: Linux 4.10.0-20-generic x86_64
  ApportVersion: 2.20.5-0ubuntu3
  Architecture: amd64
  Date: Thu May 18 15:28:33 2017
  DisplayManager: lightdm
  GsettingsChanges:
   b'org.gnome.shell' b'app-picker-view' b'uint32 1'
   b'org.gnome.shell' b'favorite-apps' b"['firefox.desktop', 
'org.gnome.Terminal.desktop', 'rhythmbox.desktop', 
'org.gnome.Nautilus.desktop', 'org.gnome.Software.desktop', 'yelp.desktop']"
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
   b'org.gnome.desktop.interface' b'scaling-factor' b'uint32 1'
  InstallationDate: Installed on 2017-05-03 (15 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170502)
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1843201] Re: Unity in Wayland prompts for keyboard focus on each run of ssh-askpass-gnome

2019-09-09 Thread Luke Faraone

Thanks for looking into this, and the pointer.

I guess, another option would be to not request shortcut inhibition,
unless I'm misunderstanding its value? Unless there's a worry that some
other application will be able to steal your password this way — it
doesn't seem obviously warranted to me.

For example, `ssh-askpass-fullscreen` does not generate this prompt. It
isn't clear to me that the fullscreen-ness of this implementation
materially changes the risk profile, so either shortcut inhibition isn't
useful, or I should file a bug against `ssh-askpass-fullscreen` to
either request this privilege or document the gap.

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

Title:
  Unity in Wayland prompts for keyboard focus on each run of ssh-
  askpass-gnome

Status in gnome-desktop package in Ubuntu:
  New
Status in openssh package in Ubuntu:
  Incomplete
Status in wayland package in Ubuntu:
  New

Bug description:
  When using a Wayland-based Unity session on Ubuntu 19.04:

  1. Have ssh-askpass-gnome as your askpass program.
  2. ssh-add -c 
  3. `ssh` to a host

  Each time, before the ssh-askpass prompt is shown, Unity shows this
  dialog:

  +-+
  | |
  | ssh-askpass wants to inhibit shortcuts  |
  | |
  | You can restore Shortcuts by pressing   |
  | Super+Escape.   |
  | |
  |_|
  |   Deny | Allow  |
  +-+

  This is mildly distracting, and it means that you need to hit ,
  answer, , instead of just answer .

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: ssh-askpass-gnome 1:7.9p1-10
  ProcVersionSignature: Ubuntu 5.0.0-27.28-generic 5.0.21
  Uname: Linux 5.0.0-27-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27.1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Sep  8 15:04:25 2019
  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   
canonical-oem-somerville-bionic-amd64-20180608-47+tunnels-mlk+X55+tunnels-mlk+X55.1
  InstallationDate: Installed on 2019-08-27 (12 days ago)
  InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 
20180608-09:38
  SourcePackage: openssh
  UpgradeStatus: Upgraded to disco on 2019-08-31 (8 days ago)

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

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

[Desktop-packages] [Bug 1800794] Re: usb-modeswitch can't apply Configuration=0 to Snapdragon X12 LTE

2019-09-09 Thread Gunnar Hjalmarsson

Thanks! I'll leave it to Mathieu to ask possible follow-up questions.

However, there is one thing I wonder ATM: When you say "with disabled
dispatcher-c-rewrite.patch" above, are you then talking about not using
a dispatcher at all, or are you referring to the variant with the TCL
dispatcher in the first PPA, i.e.
?

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

Title:
  usb-modeswitch can't apply Configuration=0 to Snapdragon X12 LTE

Status in usb-modeswitch package in Ubuntu:
  In Progress

Bug description:
  Please refer to post of usb-modeswitch developer
  http://www.draisberghof.de/usb_modeswitch/bb/viewtopic.php?f=4&t=2827
  for complete issue description.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/usb-modeswitch/+bug/1800794/+subscriptions

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

Re: [Desktop-packages] [Bug 1843164] Re: gnome-terminal starts, but shows no window

2019-09-09 Thread Stefan Reich

I think the lesson here might be to leave Ubuntu 19...

Thanks

On Mon, 9 Sep 2019 at 05:35, Daniel van Vugt 
wrote:

> I think gnome-terminal has other odd dependencies like it needs to
> receive information about the login session and bus before it is willing
> to display. For this reason I would recommend 'xterm' instead if you
> need a working shell via ssh.
>
> ** Changed in: gnome-terminal (Ubuntu)
>Status: New => Confirmed
>
> ** Changed in: gnome-terminal (Ubuntu)
>Importance: Undecided => Medium
>
> ** Summary changed:
>
> - gnome-terminal starts, but shows no window
> + gnome-terminal starts, but shows no window when launched from SSH
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1843164
>
> Title:
>   gnome-terminal starts, but shows no window when launched from SSH
>
> Status in gnome-terminal package in Ubuntu:
>   Confirmed
>
> Bug description:
>   I am starting gnome-terminal on the command line (SSH). It displays
>   nothing and does not show the terminal window. This is a v-server
>   using VNC and Ubuntu 19.
>
>   ProblemType: Bug
>   DistroRelease: Ubuntu 19.04
>   Package: gnome-terminal 3.32.1-1ubuntu1
>   ProcVersionSignature: Ubuntu 5.0.0-25.26-generic 5.0.18
>   Uname: Linux 5.0.0-25-generic x86_64
>   ApportVersion: 2.20.10-0ubuntu27.1
>   Architecture: amd64
>   Date: Sun Sep  8 11:42:23 2019
>   SourcePackage: gnome-terminal
>   UpgradeStatus: No upgrade log present (probably fresh install)
>
> To manage notifications about this bug go to:
>
> https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1843164/+subscriptions
>


-- 
Stefan Reich
BotCompany.de // Java-based operating systems

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

Title:
  gnome-terminal starts, but shows no window when launched from SSH

Status in gnome-terminal package in Ubuntu:
  Confirmed

Bug description:
  I am starting gnome-terminal on the command line (SSH). It displays
  nothing and does not show the terminal window. This is a v-server
  using VNC and Ubuntu 19.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: gnome-terminal 3.32.1-1ubuntu1
  ProcVersionSignature: Ubuntu 5.0.0-25.26-generic 5.0.18
  Uname: Linux 5.0.0-25-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27.1
  Architecture: amd64
  Date: Sun Sep  8 11:42:23 2019
  SourcePackage: gnome-terminal
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1843295] [NEW] Desktop icons missing when join displays

2019-09-09 Thread Jonas Storm Nikolajsen

Public bug reported:

In general there isn't any problems. But when I connect my computer to a second 
monitor. Use display mode "Join Displays". Then disappears all my desktop icons 
. 
If I switch theDisplay mode to "Mirror" or "Single Display" then will all the 
icons come back.

I have tryied to change ressolution, background, log out and then in
again, restart, waited in a periode two weeks, updated etc.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xorg 1:7.7+19ubuntu7.1
ProcVersionSignature: Ubuntu 5.0.0-27.28~18.04.1-generic 5.0.21
Uname: Linux 5.0.0-27-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
.proc.driver.nvidia.gpus..02.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:02:00.0'
.proc.driver.nvidia.registry: Binary: ""
.proc.driver.nvidia.version:
 NVRM version: NVIDIA UNIX x86_64 Kernel Module  390.116  Sun Jan 27 07:21:36 
PST 2019
 GCC version:  gcc version 7.4.0 (Ubuntu 7.4.0-1ubuntu1~18.04.1)
ApportVersion: 2.20.9-0ubuntu7.7
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Mon Sep  9 19:43:41 2019
DistUpgraded: Fresh install
DistroCodename: bionic
DistroVariant: ubuntu
DkmsStatus:
 nvidia, 390.116, 5.0.0-25-generic, x86_64: installed
 nvidia, 390.116, 5.0.0-27-generic, x86_64: installed
ExtraDebuggingInterest: Yes, including running git bisection searches
GraphicsCard:
 Intel Corporation Device [8086:591b] (rev 04) (prog-if 00 [VGA controller])
   Subsystem: Lenovo Device [17aa:505e]
   Subsystem: Lenovo GM108M [GeForce 940MX] [17aa:505e]
InstallationDate: Installed on 2019-08-09 (31 days ago)
InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805)
MachineType: LENOVO 20J60018MD
ProcEnviron:
 LANGUAGE=en_US:en
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.0.0-27-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 10/16/2018
dmi.bios.vendor: LENOVO
dmi.bios.version: R0FET46W (1.26 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20J60018MD
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:bvrR0FET46W(1.26):bd10/16/2018:svnLENOVO:pn20J60018MD:pvrThinkPadT470p:rvnLENOVO:rn20J60018MD:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
dmi.product.family: ThinkPad T470p
dmi.product.name: 20J60018MD
dmi.product.sku: LENOVO_MT_20J6_BU_Think_FM_ThinkPad T470p
dmi.product.version: ThinkPad T470p
dmi.sys.vendor: LENOVO
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.97-1ubuntu1~18.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.8-0ubuntu0~18.04.1
version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.8-0ubuntu0~18.04.1
version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
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 third-party-packages 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/1843295

Title:
  Desktop icons missing when join displays

Status in xorg package in Ubuntu:
  New

Bug description:
  In general there isn't any problems. But when I connect my computer to a 
second monitor. Use display mode "Join Displays". Then disappears all my 
desktop icons . 
  If I switch theDisplay mode to "Mirror" or "Single Display" then will all the 
icons come back.

  I have tryied to change ressolution, background, log out and then in
  again, restart, waited in a periode two weeks, updated etc.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 5.0.0-27.28~18.04.1-generic 5.0.21
  Uname: Linux 5.0.0-27-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..02.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:02:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  390.116  Sun Jan 27 07:21:36 
PST 2019
   GCC version:  gcc version 7.4.0 (Ubuntu 7.4.0-1ubuntu1~18.04.1)
  ApportVersion: 2.20.9-0ubuntu7.7
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Sep  9 19:43:41 2019
  DistUpgraded: Fresh instal

[Desktop-packages] [Bug 1841269] Re: dvbv5-scan Segmentation fault

This bug was fixed in the package v4l-utils - 1.16.7-1

---
v4l-utils (1.16.7-1) unstable; urgency=medium

  * Import latest 1.16.7 upstream release. LP: #1841269

 -- Gregor Jasny   Sun, 01 Sep 2019 14:59:49
+0200

** Changed in: v4l-utils (Ubuntu)
   Status: In Progress => Fix Released

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

Title:
  dvbv5-scan Segmentation fault

Status in v4l-utils package in Ubuntu:
  Fix Released

Bug description:
  LANG=en_US.UTF-8 gdb -ex=r --args dvbv5-scan -l UNIVERSAL -S0 -v -o 
Turksat.conf ./Turksat-42.0E 
  [Thread debugging using libthread_db enabled]
  Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
  Using LNBf UNIVERSAL
Universal, Europe
Freqs : 10800 to 11800 MHz, LO: 9750 MHz
Freqs : 11600 to 12700 MHz, LO: 10600 MHz
  using demux 'dvb0.demux0'
  Device Montage Technology DS3000/TS2020 (/dev/dvb/adapter0/frontend0) 
capabilities:
   CAN_2G_MODULATION
   CAN_FEC_1_2
   CAN_FEC_2_3
   CAN_FEC_3_4
   CAN_FEC_4_5
   CAN_FEC_5_6
   CAN_FEC_6_7
   CAN_FEC_7_8
   CAN_FEC_AUTO
   CAN_INVERSION_AUTO
   CAN_QPSK
   CAN_RECOVER
  DVB API Version 5.11, Current v5 delivery system: DVBS
  Supported delivery systems: 
  [DVBS]
   DVBS2
  Failed to guess country from the current locale setting.

  ERRORcommand BANDWIDTH_HZ (5) not found during retrieve
  Cannot calc frequency shift. Either bandwidth/symbol-rate is unavailable 
(yet).
  Scanning frequency #1 12346000
  frequency: 12346,00 MHz, high_band: 1
  SEC: set voltage to 18V
  DiSEqC TONE: OFF
  DiSEqC command: e0 10 38 f3 
  DiSEqC BURST: SEC_MINI_A
  DiSEqC TONE: ON
  L-Band frequency: 1746,00 MHz (offset = 10600,00 MHz)
  FREQUENCY = 12346000
  INVERSION = AUTO
  SYMBOL_RATE = 960
  INNER_FEC = 3/4
  POLARIZATION = HORIZONTAL
  DELIVERY_SYSTEM = DVBS
  Got parameters for DVBS:
  FREQUENCY = 12346000
  INVERSION = AUTO
  SYMBOL_RATE = 960
  INNER_FEC = 3/4
  POLARIZATION = HORIZONTAL
  DELIVERY_SYSTEM = DVBS
  Lock   (0x1f) Signal= 37,86% C/N= 47,97% UCB= 31440 postBER= 0
  dvb_read_sections: waiting for table ID 0x00, program ID 0x00
  dvb_parse_section: received table 0x00, extension ID 0xa414, section 0/0
  dvb_parse_section: table 0x00, extension ID 0xa414: done
  PAT
  | table_id 0x00
  | section_length  25
  | one 3
  | zero0
  | syntax  1
  | transport_stream_id 42004
  | current_next1
  | version 14
  | one23
  | section_number  0
  | last_section_number 0
  |\ 4 program pids
  |  pid 0x0010: service 0x
  |  pid 0x0065: service 0x3264
  |  pid 0x012d: service 0x3265
  |  pid 0x0066: service 0x3269
  Program #0 is network PID: 0x0010
  Program #1 ID 0x0065, service ID 0x3264
  dvb_read_sections: waiting for table ID 0x02, program ID 0x65
  dvb_parse_section: received table 0x02, extension ID 0x3264, section 0/0
  dvb_parse_section: table 0x02, extension ID 0x3264: done
  PMT
  | table_id 0x02
  | section_length  112
  | one 3
  | zero0
  | syntax  1
  | transport_stream_id 12900
  | current_next1
  | version 7
  | one23
  | section_number  0
  | last_section_number 0
  |- pcr_pid  0b54
  |  reserved2   7
  |  descriptor length   11
  |  zero3   0
  |  reserved3  15
  |0x0c: multiplex_buffer_utilization_descriptor
  |   80 b4 81 68...h
  |0x0e: maximum_bitrate_descriptor
  |   c0 3e a4   .>.
  |\
  |- stream 0x0b54: Video ISO/IEC 13818-2 (2)
  |descriptor length   16
  |0x52: stream_identifier_descriptor
  |   01 .
  |0x02: video_stream_descriptor
  |   1a 48 5f   .H_
  |0x06: ds_alignment_descriptor
  |   02 .
  |0x0e: maximum_bitrate_descriptor
  |   c0 39 4e   .9N
  |- stream 0x0bb8: Audio ISO/IEC 13818-3 (4)
  |descriptor length   17
  |0x52: stream_identifier_descriptor
  |   02 .
  |0x0a: iso639_language_descriptor
  |   lang: tur (type: 0)
  |0x03: audio_stream_descriptor
  |   67 g
  |0x0e: maximum_bitrate_descriptor
  |   c0 02 90   ...
  |- stream 0x0c1c: Audio ISO/IEC 13818-3 (4)
  |descriptor length   17
  |0x52: stream_identifier_descriptor
  |

[Desktop-packages] [Bug 263505] Re: Wishlist: add "use input as a search term" to "address not found" page

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

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

Title:
  Wishlist: add "use input as a search term" to "address not found" page

Status in Mozilla Firefox:
  Confirmed
Status in firefox package in Ubuntu:
  Incomplete

Bug description:
  Binary package hint: firefox

  Altogether too often when I get the "Address Not Found" page, it is
  because I expected too much from the Wonderful Bar or whatever it's
  called.  It would be a useful addition if the "Address Not Found" page
  could offer the option to use the stuff you typed into the location
  bar as input for your designated search engine, and/or perform history
  search on those terms.  (For me, the former is the more useful, but I
  expect both would be handy, and the effort to offer both is probably
  marginal if you decide to do one or the other.)

  All to often, what you typed in is no longer visible in the location
  bar, because http:// gets prepended and sometimes a .com appended to
  what is displayed in the location bar at the point you get the
  "Address Not Found" error.

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

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

[Desktop-packages] [Bug 263505]

2019-09-09 Thread Mak77

Thank you for the update!

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

Title:
  Wishlist: add "use input as a search term" to "address not found" page

Status in Mozilla Firefox:
  Confirmed
Status in firefox package in Ubuntu:
  Incomplete

Bug description:
  Binary package hint: firefox

  Altogether too often when I get the "Address Not Found" page, it is
  because I expected too much from the Wonderful Bar or whatever it's
  called.  It would be a useful addition if the "Address Not Found" page
  could offer the option to use the stuff you typed into the location
  bar as input for your designated search engine, and/or perform history
  search on those terms.  (For me, the former is the more useful, but I
  expect both would be handy, and the effort to offer both is probably
  marginal if you decide to do one or the other.)

  All to often, what you typed in is no longer visible in the location
  bar, because http:// gets prepended and sometimes a .com appended to
  what is displayed in the location bar at the point you get the
  "Address Not Found" error.

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

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

[Desktop-packages] [Bug 263505]

2019-09-09 Thread 7-mathieu

> Mathieu, what's the status of the underlying networking feature?

As you could figure, the feature on the product side is done. I created this 
meta bug https://bugzilla.mozilla.org/show_bug.cgi?id=1579856 , I hope that 
helps!
The remaining bits should be done in the following days.

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

Title:
  Wishlist: add "use input as a search term" to "address not found" page

Status in Mozilla Firefox:
  Confirmed
Status in firefox package in Ubuntu:
  Incomplete

Bug description:
  Binary package hint: firefox

  Altogether too often when I get the "Address Not Found" page, it is
  because I expected too much from the Wonderful Bar or whatever it's
  called.  It would be a useful addition if the "Address Not Found" page
  could offer the option to use the stuff you typed into the location
  bar as input for your designated search engine, and/or perform history
  search on those terms.  (For me, the former is the more useful, but I
  expect both would be handy, and the effort to offer both is probably
  marginal if you decide to do one or the other.)

  All to often, what you typed in is no longer visible in the location
  bar, because http:// gets prepended and sometimes a .com appended to
  what is displayed in the location bar at the point you get the
  "Address Not Found" error.

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

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

[Desktop-packages] [Bug 1675197] Re: Chromium Locks up and uses lots of cpu, but no memory....

2019-09-09 Thread Paul White

Thanks calexil, closing as fixed.

** Changed in: chromium-browser (Ubuntu)
   Status: Incomplete => Fix 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/1675197

Title:
  Chromium Locks up and uses lots of cpu, but no memory

Status in chromium-browser package in Ubuntu:
  Fix Released

Bug description:
  GDB

  http://dpaste.com/3V319B0

  I can cause the lockup everytime by going to: https://paypal.com/vt

  and entering incorrect information and hitting the submit button.

  gdb stops reporting anything and cpu usage spikes to 170-200%

  chromium must be force quit from taskmanager, as closing it does not
  actually kill the processes.

  whether or not extensions are enabled chromium locks up(tabs are still
  rendered but browser cannot create new tabs, or navigate in existing
  ones) and the main process begins using 200-270% of my three cores,
  chrome task manager shows that no tab is using any memory and when
  chromium is exited the main thread does not quit and must be killed.

  I have reinstalled, disabled extensions/plugins, etc... nothing seems
  to remedy this issue.

  I memtested my memory and it was fine.

  It started happening october 2016
  --- 
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  CrashDB: ubuntu
  CurrentDesktop: MATE
  DRM.card0-HDMI-A-1:
   enabled: enabled
   dpms: On
   status: connected
   edid-base64: 
AP///wAi8A4mACANAQOAIht46gyVolZMliUaUFSt74CBgAEBAQEBAQEBAQEBAQEBMCoAmFEAKkAwcBMAUg4RAAAe/QA4TB5TDgAKICAgICAg/ABocCBMMTczMAogICAg/wBDTlAzMzJTMFJICiAgALo=
   modes: 1280x1024 1280x1024 1152x864 1024x768 1024x768 1024x768 832x624 
800x600 800x600 800x600 640x480 640x480 640x480 720x400
  DRM.card0-VGA-1:
   enabled: enabled
   dpms: On
   status: connected
   edid-base64: 
AP///wA6kwcAAQoRAQMIKxt4CrU0pVZKmiUQUFSvzwCBgIGPlQCVDwEBAQEBAQEBHDmQMGIaJ0BosDYAsQ8RAAAY/gAKICAgICAgICAgICAg/ABNQVctU0VSSUFMCiAg/wAKICAgICAgICAgICAgAHk=
   modes: 1680x1050 1280x1024 1280x1024 1440x900 1440x900 1024x768 1024x768 
1024x768 800x600 800x600 800x600 800x600 640x480 640x480 640x480 720x400
  Desktop-Session:
   'mate'
   '/etc/xdg/xdg-mate:/etc/xdg'
   '/usr/share/mate:/usr/local/share/:/usr/share/:/usr/share/mdm/'
  DetectedPlugins:
   
  DistroRelease: Linux 18.1
  Env:
   'None'
   'None'
  InstallationDate: Installed on 2016-07-13 (252 days ago)
  InstallationMedia: Linux Mint 18 "Sarah" - Release amd64 20160628
  Load-Avg-1min: 0.88
  Load-Processes-Running-Percent:   0.2%
  MachineType: MSI MS-7786
  Package: chromium-browser 57.0.2987.98-0ubuntu0.16.04.1276 [origin: 
LP-PPA-canonical-chromium-builds-stage]
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-42-generic 
root=UUID=5c8e46d1-e26c-4bba-b87b-f092a8a3d7ad ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.8.0-42.45~16.04.1-generic 4.8.17
  Tags: serena third-party-packages
  ThirdParty: True
  Uname: Linux 4.8.0-42-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm audio cdrom dialout dip fax floppy lpadmin netdev plugdev 
sambashare scanner sudo tape video
  _MarkForUpload: True
  dmi.bios.date: 02/04/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: V2.0
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: A55M-P33 (MS-7786)
  dmi.board.vendor: MSI
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: MSI
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrV2.0:bd02/04/2013:svnMSI:pnMS-7786:pvr1.0:rvnMSI:rnA55M-P33(MS-7786):rvr1.0:cvnMSI:ct3:cvr1.0:
  dmi.product.name: MS-7786
  dmi.product.version: 1.0
  dmi.sys.vendor: MSI
  etcconfigcpepperflashpluginnonfree:
   flashso="/usr/lib/pepperflashplugin-nonfree/libpepflashplayer.so"
   flashversion=`strings $flashso 2> /dev/null | grep LNX | cut -d ' ' -f 2 | 
sed -e "s/,/./g"`
   CHROMIUM_FLAGS="$CHROMIUM_FLAGS --ppapi-flash-path=$flashso 
--ppapi-flash-version=$flashversion"
  modified.conffile..etc.default.chromium-browser: [deleted]
  mtime.conffile..etc.chromium-browser.default: 2017-03-16T14:53:53.556952

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

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

[Desktop-packages] [Bug 1842902] Re: FFe: create zfs dataset for each user automatically

This bug was fixed in the package zsys - 0.2

---
zsys (0.2) eoan; urgency=medium

  * Add userdata hidden subcommand for creating and renaming user datasets.
(LP: #1842902)
  * Build-dep on grub2-common to not produce s390x build for now until
we support an alternative bootloader.

 -- Didier Roche   Mon, 09 Sep 2019 15:13:26 +0200

** Changed in: zsys (Ubuntu)
   Status: Triaged => 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/1842902

Title:
  FFe: create zfs dataset for each user automatically

Status in shadow package in Ubuntu:
  Triaged
Status in zsys package in Ubuntu:
  Fix Released

Bug description:
  Part of the zsys spec is creating/associating one user dataset for
  each HOME user.

  As zsys is an official experimentation for 19.10, we would like to
  include this feature in a safe way, and reachable for any tool
  creating users (adduser, gnome-control-center, ubiquity…). Those are
  using useradd under the scene.

  For this, the proposed implementation:
  - patch useradd trying to execute "zsys useradd create USER HOMEDIR". If zsys 
isn't present or zsys returns a status code != 0 (which will be the case if the 
running system isn't a zsys one: pure zfs or non zfs like / on ext4), it will 
fallback to mkdir. Then the code does the usual chmod()
  - patch usermod, trying as well to execute "zsys useradd rename-home OLDHOME 
NEWHOME". Same failing reason (not a zsys system, not installed, OLDHOME isn't 
a zsys handled datasets) and fallback to rename(). Then the code does the usual 
chmod().

  Tested with and without zsys installed, the code does what we expect.

  I'm attaching the shadow (useradd/usermod) patches, as you can see it's very 
minimal.
  A new ZSYS release will be needed (https://github.com/ubuntu/zsys). As you 
can see, there are quite some commits since the last release, but it's all 
baked (as usual) by a huge suite of tests (in ZFS and machine layers) with 
corner cases tested and such. I'm confident on that change.

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

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

[Desktop-packages] [Bug 1675197] Re: Chromium Locks up and uses lots of cpu, but no memory....

2019-09-09 Thread calexil

no longer happening

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

Title:
  Chromium Locks up and uses lots of cpu, but no memory

Status in chromium-browser package in Ubuntu:
  Incomplete

Bug description:
  GDB

  http://dpaste.com/3V319B0

  I can cause the lockup everytime by going to: https://paypal.com/vt

  and entering incorrect information and hitting the submit button.

  gdb stops reporting anything and cpu usage spikes to 170-200%

  chromium must be force quit from taskmanager, as closing it does not
  actually kill the processes.

  whether or not extensions are enabled chromium locks up(tabs are still
  rendered but browser cannot create new tabs, or navigate in existing
  ones) and the main process begins using 200-270% of my three cores,
  chrome task manager shows that no tab is using any memory and when
  chromium is exited the main thread does not quit and must be killed.

  I have reinstalled, disabled extensions/plugins, etc... nothing seems
  to remedy this issue.

  I memtested my memory and it was fine.

  It started happening october 2016
  --- 
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  CrashDB: ubuntu
  CurrentDesktop: MATE
  DRM.card0-HDMI-A-1:
   enabled: enabled
   dpms: On
   status: connected
   edid-base64: 
AP///wAi8A4mACANAQOAIht46gyVolZMliUaUFSt74CBgAEBAQEBAQEBAQEBAQEBMCoAmFEAKkAwcBMAUg4RAAAe/QA4TB5TDgAKICAgICAg/ABocCBMMTczMAogICAg/wBDTlAzMzJTMFJICiAgALo=
   modes: 1280x1024 1280x1024 1152x864 1024x768 1024x768 1024x768 832x624 
800x600 800x600 800x600 640x480 640x480 640x480 720x400
  DRM.card0-VGA-1:
   enabled: enabled
   dpms: On
   status: connected
   edid-base64: 
AP///wA6kwcAAQoRAQMIKxt4CrU0pVZKmiUQUFSvzwCBgIGPlQCVDwEBAQEBAQEBHDmQMGIaJ0BosDYAsQ8RAAAY/gAKICAgICAgICAgICAg/ABNQVctU0VSSUFMCiAg/wAKICAgICAgICAgICAgAHk=
   modes: 1680x1050 1280x1024 1280x1024 1440x900 1440x900 1024x768 1024x768 
1024x768 800x600 800x600 800x600 800x600 640x480 640x480 640x480 720x400
  Desktop-Session:
   'mate'
   '/etc/xdg/xdg-mate:/etc/xdg'
   '/usr/share/mate:/usr/local/share/:/usr/share/:/usr/share/mdm/'
  DetectedPlugins:
   
  DistroRelease: Linux 18.1
  Env:
   'None'
   'None'
  InstallationDate: Installed on 2016-07-13 (252 days ago)
  InstallationMedia: Linux Mint 18 "Sarah" - Release amd64 20160628
  Load-Avg-1min: 0.88
  Load-Processes-Running-Percent:   0.2%
  MachineType: MSI MS-7786
  Package: chromium-browser 57.0.2987.98-0ubuntu0.16.04.1276 [origin: 
LP-PPA-canonical-chromium-builds-stage]
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-42-generic 
root=UUID=5c8e46d1-e26c-4bba-b87b-f092a8a3d7ad ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.8.0-42.45~16.04.1-generic 4.8.17
  Tags: serena third-party-packages
  ThirdParty: True
  Uname: Linux 4.8.0-42-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm audio cdrom dialout dip fax floppy lpadmin netdev plugdev 
sambashare scanner sudo tape video
  _MarkForUpload: True
  dmi.bios.date: 02/04/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: V2.0
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: A55M-P33 (MS-7786)
  dmi.board.vendor: MSI
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: MSI
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrV2.0:bd02/04/2013:svnMSI:pnMS-7786:pvr1.0:rvnMSI:rnA55M-P33(MS-7786):rvr1.0:cvnMSI:ct3:cvr1.0:
  dmi.product.name: MS-7786
  dmi.product.version: 1.0
  dmi.sys.vendor: MSI
  etcconfigcpepperflashpluginnonfree:
   flashso="/usr/lib/pepperflashplugin-nonfree/libpepflashplayer.so"
   flashversion=`strings $flashso 2> /dev/null | grep LNX | cut -d ' ' -f 2 | 
sed -e "s/,/./g"`
   CHROMIUM_FLAGS="$CHROMIUM_FLAGS --ppapi-flash-path=$flashso 
--ppapi-flash-version=$flashversion"
  modified.conffile..etc.default.chromium-browser: [deleted]
  mtime.conffile..etc.chromium-browser.default: 2017-03-16T14:53:53.556952

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

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

[Desktop-packages] [Bug 1800794] Re: usb-modeswitch can't apply Configuration=0 to Snapdragon X12 LTE

Log of usb-modeswitch 2.5.2+repack0-2ubuntu2~mtrudel1 and with
/usr/share/usb_modeswitch/03f0:0857 (Configuration=3)

** Attachment added: "usb_modeswitch.log"
   
https://bugs.launchpad.net/ubuntu/+source/usb-modeswitch/+bug/1800794/+attachment/5287517/+files/usb_modeswitch.log

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

Title:
  usb-modeswitch can't apply Configuration=0 to Snapdragon X12 LTE

Status in usb-modeswitch package in Ubuntu:
  In Progress

Bug description:
  Please refer to post of usb-modeswitch developer
  http://www.draisberghof.de/usb_modeswitch/bb/viewtopic.php?f=4&t=2827
  for complete issue description.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/usb-modeswitch/+bug/1800794/+subscriptions

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

[Desktop-packages] [Bug 1800794] Re: usb-modeswitch can't apply Configuration=0 to Snapdragon X12 LTE

Log of usb-modeswitch 2.5.2+repack0-2ubuntu2~mtrudel1 and without
/usr/share/usb_modeswitch/03f0:0857

** Attachment added: "usb_modeswitch.log"
   
https://bugs.launchpad.net/ubuntu/+source/usb-modeswitch/+bug/1800794/+attachment/5287516/+files/usb_modeswitch.log

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

Title:
  usb-modeswitch can't apply Configuration=0 to Snapdragon X12 LTE

Status in usb-modeswitch package in Ubuntu:
  In Progress

Bug description:
  Please refer to post of usb-modeswitch developer
  http://www.draisberghof.de/usb_modeswitch/bb/viewtopic.php?f=4&t=2827
  for complete issue description.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/usb-modeswitch/+bug/1800794/+subscriptions

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

[Desktop-packages] [Bug 1800794] Re: usb-modeswitch can't apply Configuration=0 to Snapdragon X12 LTE

Log of usb-modeswitch 2.5.2+repack0-2ubuntu1 from Ubuntu eoan repository
and with /usr/share/usb_modeswitch/03f0:0857 (Configuration=3)

** Attachment added: "usb_modeswitch.log"
   
https://bugs.launchpad.net/ubuntu/+source/usb-modeswitch/+bug/1800794/+attachment/5287518/+files/usb_modeswitch.log

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

Title:
  usb-modeswitch can't apply Configuration=0 to Snapdragon X12 LTE

Status in usb-modeswitch package in Ubuntu:
  In Progress

Bug description:
  Please refer to post of usb-modeswitch developer
  http://www.draisberghof.de/usb_modeswitch/bb/viewtopic.php?f=4&t=2827
  for complete issue description.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/usb-modeswitch/+bug/1800794/+subscriptions

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

[Desktop-packages] [Bug 1800794] Re: usb-modeswitch can't apply Configuration=0 to Snapdragon X12 LTE

Shortly, 2.5.2+repack0-2ubuntu2~mtrudel1 version does not work with or
without /usr/share/usb_modeswitch/03f0:0857

I created /usr/share/usb_modeswitch/03f0:0857 with Configuration=3
specifically to check if 2.5.2+repack0-2ubuntu2~mtrudel1 can behave at
least like usb-modeswitch 2.5.2+repack0-2ubuntu1.

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

Title:
  usb-modeswitch can't apply Configuration=0 to Snapdragon X12 LTE

Status in usb-modeswitch package in Ubuntu:
  In Progress

Bug description:
  Please refer to post of usb-modeswitch developer
  http://www.draisberghof.de/usb_modeswitch/bb/viewtopic.php?f=4&t=2827
  for complete issue description.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/usb-modeswitch/+bug/1800794/+subscriptions

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

[Desktop-packages] [Bug 1800794] Re: usb-modeswitch can't apply Configuration=0 to Snapdragon X12 LTE

Just in case I want to clarify that I did mistake in #19 and #22 - I
totally forgot that besides configuration file I also added couple of
lines with modem id's to /lib/udev/rules.d/40-usb_modeswitch.rules:

# HP lt4210
ATTR{idVendor}=="03f0", ATTR{idProduct}=="0857", RUN+="usb_modeswitch '/%k'"

Obviously, without this two lines even usb-modeswitch with disabled
dispatcher-c-rewrite.patch will not able to switch modem mode
automatically, as nothing will run usb_modeswitch against device path.

So, I wrote this message to clarify that all usb_modeswitch runs above
and below happened with modified
/lib/udev/rules.d/40-usb_modeswitch.rules

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

Title:
  usb-modeswitch can't apply Configuration=0 to Snapdragon X12 LTE

Status in usb-modeswitch package in Ubuntu:
  In Progress

Bug description:
  Please refer to post of usb-modeswitch developer
  http://www.draisberghof.de/usb_modeswitch/bb/viewtopic.php?f=4&t=2827
  for complete issue description.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/usb-modeswitch/+bug/1800794/+subscriptions

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

[Desktop-packages] [Bug 1832913] Re: Cannot access vdagent virtio channel /dev/virtio-ports/com.redhat.spice.0

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

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

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

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

Title:
  Cannot access vdagent virtio channel /dev/virtio-
  ports/com.redhat.spice.0

Status in gnome-session package in Ubuntu:
  Confirmed

Bug description:
  I am getting this error in my log, Ubuntu 18.04:

  Cannot access vdagent virtio channel /dev/virtio-
  ports/com.redhat.spice.0

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

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

[Desktop-packages] [Bug 1843280] [NEW] Update to 3.11.0 next cycle

Public bug reported:

The new version is in Debian/experimental and has a soname change

** Affects: liblouis (Ubuntu)
 Importance: Wishlist
 Status: Triaged


** Tags: upgrade-software-version version-blocked-ff

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

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

Title:
  Update to 3.11.0 next cycle

Status in liblouis package in Ubuntu:
  Triaged

Bug description:
  The new version is in Debian/experimental and has a soname change

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

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

[Desktop-packages] [Bug 1843277] [NEW] CHOLMOD slows down in parallel

2019-09-09 Thread patrick

Public bug reported:

If I run a simple CHOLMOD C++ program, I noticed that it takes more time
running in parallel than single threaded. For the attached program file
I did

g++ -o main main.cpp /usr/lib/x86_64-linux-gnu/libcholmod.so

time ./main
-> real 2m21,367s user  11m30,913s sys  5m11,448s

(now I force it to be single threaded)
time OPENBLAS_NUM_THREADS=1 OMP_THREAD_LIMIT=1  ./main
-> real 0m49,684s user  0m48,922s sys   0m0,760s

Notice the huge "sys" time consumption in parallel run.

I have a 4 core / 8 thread Intel CPU running Ubuntu 18.04, everything 
up-to-date.
In my research project with a more complex matrix, the slow-down is the factor 
8.

Further info: It is not machine-dependent. It is also confirmed in
Debian 10 on several different machines.

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

** Attachment added: "simple C++ program"
   https://bugs.launchpad.net/bugs/1843277/+attachment/5287505/+files/main.cpp

** Description changed:

  If I run a simple CHOLMOD C++ program, I noticed that it takes more time
  running in parallel than single threaded. For the attached program file
  I did
  
  g++ -o main main.cpp /usr/lib/x86_64-linux-gnu/libcholmod.so
  
  time ./main
  -> real   2m21,367s user  11m30,913s sys  5m11,448s
  
- 
  (now I force it to be single threaded)
  time OPENBLAS_NUM_THREADS=1 OMP_THREAD_LIMIT=1  ./main
  -> real   0m49,684s user  0m48,922s sys   0m0,760s
  
  Notice the huge "sys" time consumption in parallel run.
  
- I have a 4 core / 8 thread Intel CPU.
+ I have a 4 core / 8 thread Intel CPU running Ubuntu 18.04, everything 
up-to-date.
  In my research project with a more complex matrix, the slow-down is the 
factor 8.

** Description changed:

  If I run a simple CHOLMOD C++ program, I noticed that it takes more time
  running in parallel than single threaded. For the attached program file
  I did
  
  g++ -o main main.cpp /usr/lib/x86_64-linux-gnu/libcholmod.so
  
  time ./main
  -> real   2m21,367s user  11m30,913s sys  5m11,448s
  
  (now I force it to be single threaded)
  time OPENBLAS_NUM_THREADS=1 OMP_THREAD_LIMIT=1  ./main
  -> real   0m49,684s user  0m48,922s sys   0m0,760s
  
  Notice the huge "sys" time consumption in parallel run.
  
  I have a 4 core / 8 thread Intel CPU running Ubuntu 18.04, everything 
up-to-date.
  In my research project with a more complex matrix, the slow-down is the 
factor 8.
+ 
+ Further info: It is not machine-dependent. It is also confirmed in
+ Debian 10 on several different machines.

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

Title:
  CHOLMOD slows down in parallel

Status in suitesparse package in Ubuntu:
  New

Bug description:
  If I run a simple CHOLMOD C++ program, I noticed that it takes more
  time running in parallel than single threaded. For the attached
  program file I did

  g++ -o main main.cpp /usr/lib/x86_64-linux-gnu/libcholmod.so

  time ./main
  -> real   2m21,367s user  11m30,913s sys  5m11,448s

  (now I force it to be single threaded)
  time OPENBLAS_NUM_THREADS=1 OMP_THREAD_LIMIT=1  ./main
  -> real   0m49,684s user  0m48,922s sys   0m0,760s

  Notice the huge "sys" time consumption in parallel run.

  I have a 4 core / 8 thread Intel CPU running Ubuntu 18.04, everything 
up-to-date.
  In my research project with a more complex matrix, the slow-down is the 
factor 8.

  Further info: It is not machine-dependent. It is also confirmed in
  Debian 10 on several different machines.

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

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

[Desktop-packages] [Bug 1843044] Re: firefox crashes on a FIPS enabled machine

2019-09-09 Thread Vineetha Kamath

** Description changed:

  [IMPACT]
- firefox is not a FIPS certified library. firefox uses bundled nss and on a 
machine running FIPS enabled kernel, nss by default goes into FIPS mode if 
/proc/sys/crypto/fips_enabled=1. This is an untested configuration and since 
firefox with bundles nss is not a certified library we propose disabling 
reading the 'fips_enabled' flag and therefore switching the library 
automatically into FIPS mode. A FIPS customer reported firefox crash on a FIPS 
enabled system and strace showed it was repeatedly trying to read the 
fips_enabled flag from the bundled nss before crashing.
+ firefox is not a FIPS certified library. firefox uses bundled nss and on a 
machine running FIPS enabled kernel, nss by default goes into FIPS mode if 
/proc/sys/crypto/fips_enabled=1. This is an untested configuration and since 
firefox with bundled nss is not a certified library we propose disabling 
reading the 'fips_enabled' flag and therefore switching the library 
automatically into FIPS mode. A FIPS customer reported firefox crash on a FIPS 
enabled system and strace showed it was repeatedly trying to read the 
fips_enabled flag from the bundled nss before crashing.
  
  The proposed patch disables reading the /proc/sys/crypto/fips_enabled
  flag. The users of the library however can force nss into FIPS mode via
  an environment variable. We plan to leave it as is so as not to regress
  existing users who may be using it.
  
  The issue impacts firefox versions in eoan, disco, bionic and xenial.
  
  lsb_release -rd
  Description:  Ubuntu Eoan Ermine (development branch)
  Release: 19.10
  
  Version: 2:3.45-1ubuntu1
  
  lsb_release -rd
  Description: Ubuntu Disco Dingo
  Release: 19.04
  
  Version: 2:3.42-1ubuntu2
  
  lsb_release -rd
  Description:  Ubuntu Bionic Beaver
  Release:  18.04
  
  Version: 2:3.35-2ubuntu2.3
  
  lsb_release -rd
  Description:  Ubuntu 16.04.3 LTS
  Release:  16.04
  
  Version: 2:3.28.4-0ubuntu0.16.04
  
  [FIX]
  This fix proposes to disable bundled nss in firefox reading 
proc/sys/crypto/fips_enabled. We only want fips certified modules reading this 
file and running in fips mode. firefox is not one of our fips certified 
modules, so should not be reading this along with our fips certified modules to 
determine whether to run in fips mode.
  
  Users who do want to run the library in FIPS mode can do so by using the
  environment variable "NSS_FIPS". We propose to leave it as is so as not
  to regress anyone using this. The user who is using this option should
  be doing so with the awareness.
  
  [TEST]
  Tested on a xenial and bionic desktop ISO running FIPS enabled kernel and in 
FIPS mode. With the patch fix no crashes were observed when launching firefox 
browser.
  Without the patch fix, firefox crashes.
  
  Tested on a xenial and bionic desktop ISO running non-FIPS generic
  kernel. With the patch fix, firefox worked as expected and no changes
  were observed.
  
  [REGRESSION POTENTIAL]
  The regression potential for this is small. A FIPS kernel is required to
  create /proc/sys/crypto/fips_enabled and it is not available in the standard 
Ubuntu archive. For users forcing FIPS through environment variable, nothing 
has changed.

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

Title:
  firefox crashes on a FIPS enabled machine

Status in firefox package in Ubuntu:
  New

Bug description:
  [IMPACT]
  firefox is not a FIPS certified library. firefox uses bundled nss and on a 
machine running FIPS enabled kernel, nss by default goes into FIPS mode if 
/proc/sys/crypto/fips_enabled=1. This is an untested configuration and since 
firefox with bundled nss is not a certified library we propose disabling 
reading the 'fips_enabled' flag and therefore switching the library 
automatically into FIPS mode. A FIPS customer reported firefox crash on a FIPS 
enabled system and strace showed it was repeatedly trying to read the 
fips_enabled flag from the bundled nss before crashing.

  The proposed patch disables reading the /proc/sys/crypto/fips_enabled
  flag. The users of the library however can force nss into FIPS mode
  via an environment variable. We plan to leave it as is so as not to
  regress existing users who may be using it.

  The issue impacts firefox versions in eoan, disco, bionic and xenial.

  lsb_release -rd
  Description:  Ubuntu Eoan Ermine (development branch)
  Release: 19.10

  Version: 2:3.45-1ubuntu1

  lsb_release -rd
  Description: Ubuntu Disco Dingo
  Release: 19.04

  Version: 2:3.42-1ubuntu2

  lsb_release -rd
  Description:  Ubuntu Bionic Beaver
  Release:  18.04

  Version: 2:3.35-2ubuntu2.3

  lsb_release -rd
  Description:  Ubuntu 16.04.3 LTS
  Release:  16.04

  Version: 2:3.28.4-0ubuntu0.16.04

  [FIX]
  This fix proposes to disable bundled nss in firefox reading 
proc/sys/crypto/fips_enabled.

[Desktop-packages] [Bug 1800794] Re: usb-modeswitch can't apply Configuration=0 to Snapdragon X12 LTE

2019-09-09 Thread Gunnar Hjalmarsson

@RussianNeuroMancer: With your log files as guidance, Mathieu has made
several modifications of dispatcher-c-rewrite.patch, which I put in the
second PPA:

https://launchpad.net/~gunnarhj/+archive/ubuntu/usb-modeswitch2

Any chance you can try that too?

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

Title:
  usb-modeswitch can't apply Configuration=0 to Snapdragon X12 LTE

Status in usb-modeswitch package in Ubuntu:
  In Progress

Bug description:
  Please refer to post of usb-modeswitch developer
  http://www.draisberghof.de/usb_modeswitch/bb/viewtopic.php?f=4&t=2827
  for complete issue description.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/usb-modeswitch/+bug/1800794/+subscriptions

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

[Desktop-packages] [Bug 1826878] Re: Right Click Menu Stuck

2019-09-09 Thread Jason Stephenson

It has not happened since I reported it. I have been rebooting a little
more frequently, which I think helps.

I tried that apport command but thanks to systemd-resolved, it failed to
connect to Launchpad after I authorized the token. It couldn't resolve
launchpad.net. That's another, more frequent annoyance, that I've been
putting up with since upgrading to 19.04.

I'm just going to make this bug Invalid, unless some objects.

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

Title:
Right Click Menu Stuck

Status in gnome-shell-extension-ubuntu-dock package in Ubuntu:
Incomplete

Bug description:
This is one of those things that happens apparently randomly from my
(the user's) point of view. Occasionally, when I right click on a
dock icon to bring up the menu, the menu doesn't really respond to
clicking on the commands, and then stays on my screen even after the
dock auto-hides itself.

I can try clicking on the various commands in the menu, but nothing
happens. The menu remains on screen even when I switch applications or
virtual desktops.

I'm using whatever the latest packages are for Gnome and the Dock
extension that come with Ubuntu 19.04.

The only way I've found to resolve this has been to log out of my
Gnome session and log back in. I've been searching for a way to kill
the Dock and restart it, but haven't found anything in my web
searches.

See attached screenshot.

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

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

[Desktop-packages] [Bug 1842927] Re: mozjs60 ftbfs on arm64

2019-09-09 Thread Iain Lane

this is hopefully fixed by https://salsa.debian.org/gnome-
team/mozjs60/commit/74e62fe29e97e5a9d3ae4115f8fe44fbbecee11a, going to
upload to a PPA to test that and then maybe upload to debian / sync

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

Title:
  mozjs60 ftbfs on arm64

Status in mozjs60 package in Ubuntu:
  Confirmed

Bug description:
  mozjs60 ftbfs on arm64

  https://launchpad.net/ubuntu/+source/mozjs60/60.2.3-4build1/+build/17523444

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

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

[Desktop-packages] [Bug 1785629] Re: [MIR] gupnp-av

** Changed in: gupnp-av (Ubuntu)
   Status: Expired => New

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

Title:
  [MIR] gupnp-av

Status in gupnp-av package in Ubuntu:
  New

Bug description:
  * Availability

  Builds on all supported architectures in Ubuntu and on sync from
  Debian

  * Rationale

  We would like to enable dlna sharing of media files, which is a GNOME
  upstream feature and relying on rygel which depends on the gupnp
  libraries, including the gupnp-dlna one

  * Security

  No CVE/known security issue

  * Quality assurance

  - the desktop-packages team is subscribed to the package
  - the bug lists in upstream, the Debian PTS and launchpad are empty
  - upstream has a testsuit which is not being used during build, we are going 
to look at changing that

  * Dependendies

  The package uses standard desktop libraries that are already in main
  (gstreamer, glib)

  * Standards compliance

  the package is using standard packaging (dh10), the standards-version
  is 3.9.8, the package is in sync from Debian

  * Maintainance

  Upstream is active and the desktop team is going to look after the
  package in ubuntu

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gupnp-av/+bug/1785629/+subscriptions

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

[Desktop-packages] [Bug 1843201] Re: Unity in Wayland prompts for keyboard focus on each run of ssh-askpass-gnome

2019-09-09 Thread Christian Ehrhardt 

Hi Luke,
thanks for the bug report and your help to make Ubuntu better.
I'm unsure what ssh could/should do differently in this case.

For similar issues there was a gnome PR [1] that went into gnome that should 
allow a "yes and remember" kind of use-case. Not sure if that is missing in the 
gnome in 19.04, just not yet released or not applying here for another case.
I added gnome/wayland tasks to the bug to get the right experts attention on 
this bug.

[1]: https://gitlab.gnome.org/GNOME/gnome-shell/merge_requests/382

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

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

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

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

Title:
  Unity in Wayland prompts for keyboard focus on each run of ssh-
  askpass-gnome

Status in gnome-desktop package in Ubuntu:
  New
Status in openssh package in Ubuntu:
  Incomplete
Status in wayland package in Ubuntu:
  New

Bug description:
  When using a Wayland-based Unity session on Ubuntu 19.04:

  1. Have ssh-askpass-gnome as your askpass program.
  2. ssh-add -c 
  3. `ssh` to a host

  Each time, before the ssh-askpass prompt is shown, Unity shows this
  dialog:

  +-+
  | |
  | ssh-askpass wants to inhibit shortcuts  |
  | |
  | You can restore Shortcuts by pressing   |
  | Super+Escape.   |
  | |
  |_|
  |   Deny | Allow  |
  +-+

  This is mildly distracting, and it means that you need to hit ,
  answer, , instead of just answer .

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: ssh-askpass-gnome 1:7.9p1-10
  ProcVersionSignature: Ubuntu 5.0.0-27.28-generic 5.0.21
  Uname: Linux 5.0.0-27-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27.1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Sep  8 15:04:25 2019
  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   
canonical-oem-somerville-bionic-amd64-20180608-47+tunnels-mlk+X55+tunnels-mlk+X55.1
  InstallationDate: Installed on 2019-08-27 (12 days ago)
  InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 
20180608-09:38
  SourcePackage: openssh
  UpgradeStatus: Upgraded to disco on 2019-08-31 (8 days ago)

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

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

[Desktop-packages] [Bug 1684123]

2019-09-09 Thread Mike

This is concerning that after all this time (2,5 year) this issue is
still here.

I have the same issue shown in journalctl. I believe it wasn't there from the 
start but showed a while ago. I don't see any problems on the frontend site, 
however.
I have a hybrid GPUs and currently use optimus-manager to switch between GPUs. 
Nouevau is making the switch (successfully).

Here is the bug:

nouveau :01:00.0: bus: MMIO read of  FAULT at 022554 [ IBUS
]

My laptop is:

System:Host: alienware-PC Kernel: 5.2.13-1-MANJARO x86_64 bits: 64 
compiler: gcc v: 9.1.0 Desktop: KDE Plasma 5.16.5 
   tk: Qt 5.13.0 wm: kwin_x11 dm: SDDM Distro: Manjaro Linux 
Machine:   Type: Laptop System: Alienware product: Alienware 17 R3 v: 1.7.0 
serial:  Chassis: type: 10 
   serial:  
   Mobo: Alienware model: 0GH72M v: A00 serial:  UEFI: 
Alienware v: 1.7.0 date: 01/18/2019 
Battery:   ID-1: BAT1 charge: 95.8 Wh condition: 95.8/96.0 Wh (100%) volts: 
17.3/15.0 model: COMPAL PABAS0241231 
   serial:  status: Full 
CPU:   Topology: Quad Core model: Intel Core i7-6700HQ bits: 64 type: MT 
MCP arch: Skylake-S rev: 3 L2 cache: 6144 KiB 
   flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx 
bogomips: 41488 
   Speed: 933 MHz min/max: 800/3500 MHz Core speeds (MHz): 1: 900 2: 
900 3: 900 4: 900 5: 900 6: 900 7: 900 8: 900 
Graphics:  Device-1: Intel HD Graphics 530 vendor: Dell driver: i915 v: kernel 
bus ID: 00:02.0 chip ID: 8086:191b 
   Device-2: NVIDIA GM204M [GeForce GTX 970M] vendor: Dell driver: 
nouveau v: kernel bus ID: 01:00.0 
   chip ID: 10de:13d8 
   Display: x11 server: X.Org 1.20.5 driver: modesetting compositor: 
kwin_x11 tty: N/A 
   OpenGL: renderer: Mesa DRI Intel HD Graphics 530 (Skylake GT2) v: 
4.5 Mesa 19.1.6 compat-v: 3.0 direct render: Yes 
Audio: Device-1: Intel 100 Series/C230 Series Family HD Audio vendor: Dell 
driver: snd_hda_intel v: kernel bus ID: 00:1f.3 
   chip ID: 8086:a170 
   Sound Server: ALSA v: k5.2.13-1-MANJARO 
Network:   Device-1: Qualcomm Atheros Killer E2400 Gigabit Ethernet driver: alx 
v: kernel port: d000 bus ID: 3b:00.0 
   chip ID: 1969:e0a1 
   IF: enp59s0 state: down mac:  
   Device-2: Qualcomm Atheros QCA6174 802.11ac Wireless Network Adapter 
vendor: Bigfoot Networks driver: ath10k_pci 
   v: kernel port: d000 bus ID: 3c:00.0 chip ID: 168c:003e 
   IF: wlp60s0 state: up mac:  
   Device-3: Qualcomm Atheros type: USB driver: btusb bus ID: 1-5:4 
chip ID: 0cf3:e300 
Drives:Local Storage: total: 1.02 TiB used: 730.08 GiB (70.0%) 
   ID-1: /dev/sda vendor: Kingston model: SM2280S3G2120G size: 111.79 
GiB speed: 6.0 Gb/s serial:  
   ID-2: /dev/sdb vendor: HGST (Hitachi) model: HTS721010A9E630 size: 
931.51 GiB speed: 6.0 Gb/s serial:  
RAID:  Hardware-1: Intel 82801 Mobile SATA Controller [RAID mode] driver: 
ahci v: 3.0 bus ID: 00:17.0 chip ID: 8086.282a 
Partition: ID-1: / size: 38.32 GiB used: 30.85 GiB (80.5%) fs: ext4 dev: 
/dev/sda4 
   ID-2: /home size: 71.26 GiB used: 57.85 GiB (81.2%) fs: ext4 dev: 
/dev/sda2 
Sensors:   System Temperatures: cpu: 54.5 C mobo: N/A gpu: nouveau temp: 54 C 
   Fan Speeds (RPM): N/A 
Info:  Processes: 262 Uptime: 5m Memory: 7.66 GiB used: 2.53 GiB (33.0%) 
Init: systemd v: 243 Compilers: gcc: 9.1.0 
   clang: 8.0.1 Shell: bash v: 5.0.11 running in: konsole inxi: 3.0.36

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

Title:
  bus: MMIO read of  FAULT at 3e6684 [ IBUS ]

Status in Nouveau Xorg driver:
  Confirmed
Status in xserver-xorg-video-nouveau package in Ubuntu:
  Confirmed

Bug description:
  This is the error i get when running xdiagnose:

  nouveau :06:00.0: bus: MMIO read of  FAULT at 3e6684 [
  IBUS ]

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: xserver-xorg-video-nouveau 1:1.0.14-0ubuntu1
  ProcVersionSignature: Ubuntu 4.11.0-0.3-generic 4.11.0-rc6
  Uname: Linux 4.11.0-0-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: GNOME
  Date: Wed Apr 19 15:21:16 2017
  DistUpgraded: Fresh install
  DistroCodename: zesty
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox, 5.1.18, 4.10.0-19-generic, x86_64: installed
   virtualbox, 5.1.18, 4.11.0-0-generic, x86_64: installed
  GraphicsCard:
   NVIDIA Corporation GM107 [GeForce GTX 750] [10de:1381] (rev a2) (prog-if 00 
[VGA controller])
 Subsystem: Gigabyte Technology Co., Ltd GM107 [GeForce GTX 750] [1458:362e]
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 003 Device 001:

[Desktop-packages] [Bug 1731459] Re: genesys_gl847 scanners produce a black band in scanned images on Ubuntu 17.10+, 18.04 LTS and 18.10 Cosmic cuttlefish

This bug was fixed in the package sane-backends - 1.0.27-3.2ubuntu1.1

---
sane-backends (1.0.27-3.2ubuntu1.1) disco; urgency=medium

  * debian/patches/git-fix-discolored-bar-issue.patch:
- Upstream commit to fix issue with discolored bar on Genesys GL847
  scanners (LP: #1731459).

 -- Gunnar Hjalmarsson   Thu, 08 Aug 2019 21:21:00
+0200

** Changed in: sane-backends (Ubuntu Disco)
   Status: Fix Committed => Fix Released

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

Title:
  genesys_gl847 scanners produce a black band in scanned images on
  Ubuntu 17.10+,  18.04 LTS and 18.10 Cosmic cuttlefish

Status in sane-backends:
  Fix Released
Status in sane-backends package in Ubuntu:
  Fix Released
Status in sane-backends source package in Bionic:
  Fix Committed
Status in sane-backends source package in Disco:
  Fix Released
Status in sane-backends package in Debian:
  Confirmed

Bug description:
  [Impact]

  When using a Genesys GL847 scanner, the documents get disfigured by a
  discolored bar. The proposed uploads should fix the issue. They are
  available in this PPA:

  https://launchpad.net/~gunnarhj/+archive/ubuntu/sane-backends

  [Test case]

  1. Install the libsane (libsane1 in bionic), libsane-common
 and sane-utils packages from {bionic,disco]-proposed.

  2. Use an affected device to scan, and find that the issue is
 no longer present.

  [Regression risk]

  Upstream commit, focused bug fix => low regression risk

  [Original description]

  On Windows it works but on my Ubuntu 17.10, 18.04 and 18.10 I see a
  black band on scanned image. The scanner is Canon CanoScan LIDE100.
  Libsane version is 1.0.27-1~experimental2ubuntu1

To manage notifications about this bug go to:
https://bugs.launchpad.net/sane-backends/+bug/1731459/+subscriptions

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

[Desktop-packages] [Bug 1731459] Update Released

2019-09-09 Thread Łukasz Zemczak

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

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

Title:
  genesys_gl847 scanners produce a black band in scanned images on
  Ubuntu 17.10+,  18.04 LTS and 18.10 Cosmic cuttlefish

Status in sane-backends:
  Fix Released
Status in sane-backends package in Ubuntu:
  Fix Released
Status in sane-backends source package in Bionic:
  Fix Committed
Status in sane-backends source package in Disco:
  Fix Released
Status in sane-backends package in Debian:
  Confirmed

Bug description:
  [Impact]

  When using a Genesys GL847 scanner, the documents get disfigured by a
  discolored bar. The proposed uploads should fix the issue. They are
  available in this PPA:

  https://launchpad.net/~gunnarhj/+archive/ubuntu/sane-backends

  [Test case]

  1. Install the libsane (libsane1 in bionic), libsane-common
 and sane-utils packages from {bionic,disco]-proposed.

  2. Use an affected device to scan, and find that the issue is
 no longer present.

  [Regression risk]

  Upstream commit, focused bug fix => low regression risk

  [Original description]

  On Windows it works but on my Ubuntu 17.10, 18.04 and 18.10 I see a
  black band on scanned image. The scanner is Canon CanoScan LIDE100.
  Libsane version is 1.0.27-1~experimental2ubuntu1

To manage notifications about this bug go to:
https://bugs.launchpad.net/sane-backends/+bug/1731459/+subscriptions

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

[Desktop-packages] [Bug 1841818] Re: Populate featured snaps from ubuntu-firstrun category

This bug was fixed in the package gnome-initial-setup -
3.28.0-2ubuntu6.16.04.6

---
gnome-initial-setup (3.28.0-2ubuntu6.16.04.6) bionic; urgency=medium

  * debian/patches/0001-Add-Ubuntu-mode-with-special-pages.patch:
- Fix patch being corrupted in previous release

gnome-initial-setup (3.28.0-2ubuntu6.16.04.5) bionic; urgency=medium

  * debian/patches/0001-Add-Ubuntu-mode-with-special-pages.patch:
- Populate featured snaps from ubuntu-firstrun category (LP: #1841818)

 -- Robert Ancell   Wed, 28 Aug 2019
20:48:27 +0300

** Changed in: gnome-initial-setup (Ubuntu Bionic)
   Status: Fix Committed => Fix Released

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

Title:
  Populate featured snaps from ubuntu-firstrun category

Status in gnome-initial-setup package in Ubuntu:
  Fix Released
Status in gnome-initial-setup source package in Bionic:
  Fix Released

Bug description:
  [Impact]
  There is a hidden category in the snap store called "ubuntu-firstrun" which 
shows appropriate snaps to show the user. This category was created after 
gnome-initial-setup had Snap support added to it and used the "featured" 
category.

  [Test Case]
  1. Open GNOME Initial Setup
  2. Go to final page

  Expected result:
  Snaps are shown from the "ubuntu-firstrun" category.

  Observed result:
  Snaps are shown from the "featured" category.

  [Regression Potential]
  Very low. Just the name of the category is changed and has been in use since 
cosmic.

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

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

[Desktop-packages] [Bug 833520] Re: nautilus script variables not set in search results window

** Changed in: nautilus (Ubuntu)
   Status: Fix Committed => 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/833520

Title:
  nautilus script variables not set in search results window

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

Bug description:
  I can use nautilus scripts in any folder but I just realized I can't use them 
(at least to act a single selected file) in the "search results" folder.
  I think that the problem is that the following variable is not set for some 
reason in the "search results" folder:
  $NAUTILUS_SCRIPT_SELECTED_FILE_PATHS

  I want to make a simple script to copy the location of that file. The 
following script works fine except in that folder:
  echo "`dirname "$NAUTILUS_SCRIPT_SELECTED_FILE_PATHS"`" | perl -pe 's/\n//' | 
parcellite

  This behavior was confirmed by another user. See the following thread:
  http://ubuntuforums.org/showthread.php?t=1830402

  I am using 11.04 with Unity, 64-bit, Nautilus version Installed:
  1:2.32.2.1-0ubuntu13

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

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

[Desktop-packages] [Bug 1440253] Re: leading space in manual path specification is interpreted as current directory

** Changed in: nautilus (Ubuntu)
   Status: Fix Committed => 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/1440253

Title:
  leading space in manual path specification is interpreted as current
  directory

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

Bug description:
  * Impact:
  Leading space in locations lead to error

  * Test case
  - enter ' /usr/share/' as a location in the top bar, it should opening the 
directory and not error out

  * Regression potential
  the code change is around the text parsing done in the location bar, enter a 
few different locations and check those work as expected

  --

  For example, if one enters `  /path/to/directory` the input (including
  the leading space) resolves to `/path/to/current/directory
  /path/to/directory` which is never a valid input. The leading space
  should thus be removed before changing the directory.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: nautilus 1:3.14.2-0ubuntu8
  ProcVersionSignature: Ubuntu 3.19.0-11.11-generic 3.19.3
  Uname: Linux 3.19.0-11-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.17-0ubuntu1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sat Apr  4 01:21:29 2015
  EcryptfsInUse: Yes
  GsettingsChanges: b'org.gnome.nautilus.list-view' b'default-column-order' 
b"['name', 'size', 'type', 'date_modified', 'date_accessed', 'owner', 'group', 
'permissions', 'mime_type', 'where']"
  InstallationDate: Installed on 2015-04-02 (1 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Beta amd64 (20150326)
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  SourcePackage: nautilus
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1825167] Re: It does not correctly display the hard drive icon

** Package changed: nautilus (Ubuntu) => gtk+3.0 (Ubuntu)

** Changed in: gtk+3.0 (Ubuntu)
   Status: Incomplete => Triaged

** Bug watch added: gitlab.gnome.org/GNOME/gtk/issues #2104
   https://gitlab.gnome.org/GNOME/gtk/issues/2104

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

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

Title:
  It does not correctly display the hard drive icon

Status in Nautilus:
  Unknown
Status in gtk+3.0 package in Ubuntu:
  Triaged

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

  ---

  The icon of my hard drive is SSD (Attach image).

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: nautilus 1:3.32.0-0ubuntu2
  Uname: Linux 5.0.8-050008-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  Date: Wed Apr 17 08:52:05 2019
  InstallationDate: Installed on 2018-12-02 (135 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  ProcEnviron:
   LANGUAGE=es_CL:es
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=es_CL.UTF-8
   SHELL=/bin/bash
  SourcePackage: nautilus
  UpgradeStatus: Upgraded to disco on 2018-12-02 (135 days ago)
  usr_lib_nautilus:

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

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

[Desktop-packages] [Bug 1842971] Re: Regression: GNOME-Shell & Budgie Desktop application focus is back-to-front

2019-09-09 Thread Iain Lane

Cheers for the report.

I've staged those fixes in git for the next upload (either 3.34.0 or
maybe an earlier one if we get another fix we're waiting for).

https://salsa.debian.org/gnome-
team/mutter/commit/c4f302539f3bea1655e9b431056f878fabc86a3d

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

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

** Changed in: mutter (Ubuntu Eoan)
 Assignee: (unassigned) => Iain Lane (laney)

** Tags removed: 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/1842971

Title:
  Regression: GNOME-Shell & Budgie Desktop application focus is back-to-
  front

Status in Mutter:
  New
Status in mutter package in Ubuntu:
  Fix Committed
Status in mutter source package in Eoan:
  Fix Committed

Bug description:
  Under GNOME-Shell and Budgie Desktop - using third party docks such as
  Plank, the application focus is wrong - it shows the previous
  application window as having the current focus

  i.e. open a terminal, then open nautilus - the active focus window is
  actually still reported as the terminal.

  This makes using a dock impossible.  Under budgie desktop is makes
  navigating windows really difficult.

  I've been working with upstream mutter devs and this has been
  resolved.

  https://gitlab.gnome.org/GNOME/mutter/issues/751

  The merge request is
  https://gitlab.gnome.org/GNOME/mutter/merge_requests/776

  I have manually taken both commits from the merge request and applied
  it to v3.33.92 and the focus issues have been resolved.

  The merge request is due to be merged in 3.34.1.

  Please can the two commits be backported?

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: libmutter-5-0 3.33.91-1ubuntu1
  ProcVersionSignature: Ubuntu 5.2.0-15.16-generic 5.2.9
  Uname: Linux 5.2.0-15-generic x86_64
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  CurrentDesktop: Budgie:GNOME
  Date: Thu Sep  5 21:09:15 2019
  InstallationDate: Installed on 2019-08-29 (7 days ago)
  InstallationMedia: Ubuntu-Budgie 19.10 "Eoan Ermine" - Alpha amd64 (20190829)
  SourcePackage: mutter
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1841718] Re: [radeon] Rendering of combo boxes and tooltips is broken

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

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

Title:
  [radeon] Rendering of combo boxes and tooltips is broken

Status in Mutter:
  New
Status in gtk+3.0 package in Ubuntu:
  Invalid
Status in mesa package in Ubuntu:
  Triaged
Status in mutter package in Ubuntu:
  Invalid
Status in gtk+3.0 source package in Eoan:
  Invalid
Status in mesa source package in Eoan:
  Triaged
Status in mutter source package in Eoan:
  Invalid

Bug description:
  Combo boxes are broken (cf screenshot) Tested in gnome-control-center
  and gtk3-demo.

  Tooltips are also garbage.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: gnome-shell 3.33.91-1ubuntu1
  ProcVersionSignature: Ubuntu 5.2.0-13.14-generic 5.2.8
  Uname: Linux 5.2.0-13-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Aug 28 07:08:33 2019
  DisplayManager: gdm3
  InstallationDate: Installed on 2014-07-15 (1869 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20140520)
  RelatedPackageVersions: mutter-common 3.33.91-1ubuntu1
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to eoan on 2018-03-24 (521 days ago)

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

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

[Desktop-packages] [Bug 1691678] Re: Scrollbars escape the bottom and right side of the Terminal window by 1px

FYI, there's a workaround hacked into Yaru:

https://github.com/ubuntu/yaru/blob/master/gtk/src/light/gtk-3.20/_apps.scss#L174

** Also affects: yaru-theme (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: yaru-theme (Ubuntu)
   Status: New => Fix Released

** Changed in: yaru-theme (Ubuntu)
   Importance: Undecided => Low

** Also affects: ubuntu-themes (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: ubuntu-themes (Ubuntu)
   Importance: Undecided => Low

** Changed in: ubuntu-themes (Ubuntu)
   Status: New => Confirmed

** Also affects: gnome-terminal via
   https://gitlab.gnome.org/GNOME/gnome-terminal/issues/132
   Importance: Unknown
   Status: Unknown

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

Title:
  Scrollbars escape the bottom and right side of the Terminal window by
  1px

Status in GNOME Terminal:
  Unknown
Status in gnome-terminal package in Ubuntu:
  Confirmed
Status in gtk+3.0 package in Ubuntu:
  Confirmed
Status in ubuntu-themes package in Ubuntu:
  Confirmed
Status in yaru-theme package in Ubuntu:
  Fix Released

Bug description:
  Ubuntu's orange overlay scrollbars escape the bottom of the window
  during resizing.

  To reproduce try gnome-shell on artful using the Ambiance theme. Open
  a Terminal window and resize it vertically, quickly. Notice the bottom
  of the overlay scrollbar overruns the bottom of the window.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.24.2-0ubuntu3
  ProcVersionSignature: Ubuntu 4.10.0-20.22-generic 4.10.8
  Uname: Linux 4.10.0-20-generic x86_64
  ApportVersion: 2.20.5-0ubuntu3
  Architecture: amd64
  Date: Thu May 18 15:28:33 2017
  DisplayManager: lightdm
  GsettingsChanges:
   b'org.gnome.shell' b'app-picker-view' b'uint32 1'
   b'org.gnome.shell' b'favorite-apps' b"['firefox.desktop', 
'org.gnome.Terminal.desktop', 'rhythmbox.desktop', 
'org.gnome.Nautilus.desktop', 'org.gnome.Software.desktop', 'yelp.desktop']"
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
   b'org.gnome.desktop.interface' b'scaling-factor' b'uint32 1'
  InstallationDate: Installed on 2017-05-03 (15 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170502)
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1841718] Re: [radeon] Rendering of combo boxes and tooltips is broken