[Desktop-packages] [Bug 942856] Re: NetworkManager does not support AES-encrypted private keys for WPA 802.1x authentication

2019-09-26 Thread Mathew Hodson
** Bug watch added: bugzilla.gnome.org/ #670999
   https://bugzilla.gnome.org/show_bug.cgi?id=670999

** Changed in: network-manager
   Importance: Wishlist => Unknown

** Changed in: network-manager
   Status: Confirmed => Unknown

** Changed in: network-manager
 Remote watch: GNOME Bug Tracker #670999 => bugzilla.gnome.org/ #670999

** Bug watch removed: GNOME Bug Tracker #670999
   https://gitlab.gnome.org/670999

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

Title:
  NetworkManager does not support AES-encrypted private keys for WPA
  802.1x authentication

Status in NetworkManager:
  Unknown
Status in network-manager package in Ubuntu:
  Fix Released
Status in network-manager source package in Bionic:
  In Progress

Bug description:
  * Impact

  Selecting AES-{192,256}-CBC keys to connect isn't working

  * Test case

  1. Start with a working (cleartext or DES-3) private key/cert for a network.  
Set up a connection and verify that everything works.
  2. Re-encrypt the key with AES-256 with this command: "openssl rsa -in 
working-key.pem -out aes-key.pem -aes256" (the output should have a line 
starting with "DEK-Info: AES-256-CBC,")
  3. Delete the settings for the test network and attempt to reconnect using 
the new key. 

  That should work

  * Regression potential

  That's new code for an extra type of keys, it shouldn't impact
  existing options

  --

  NetworkManager does not appear to support private keys encrypted with
  AES.  At the very least, it will not validate such a key in nm-util
  when setting up a WPA 802.1x TLS wifi connection.

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

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


[Desktop-packages] [Bug 1638395] Re: Unable to locate remote printer when printing

2019-09-26 Thread allenstif
Very often the users are coming across this common Printing error as
they are not able to locate a Remote Printer at the time of running a
printing process. I have a blog https://printerssupport.co/canon-
printer-not-responding/ along with such Printing solutions which will
help them surely.

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

Title:
  Unable to locate remote printer when printing

Status in cups package in Ubuntu:
  Confirmed

Bug description:
  My printer (EPSON Stylus Photo RX520) is connected to a  Yakkety station 
called "paris" which is the printing server. 
  Printing is fine from the server.

  When i configure another Yakkety station to print via this server, the 
printer is detected OK via dnssd, the driver is installed OK. But i can't 
print. 
  I get the following message "Unable to locate printer "paris.local"."

  I used to work on xenial but the connection was through ipps. I tried
  to configure the connection as in xenial, to no avail ...

  What i did: 
  add "192.168.1.4 paris.local" in /etc/hosts
  remove printer from cups, reinstalled it and i finally was able to print on 
the remote printer!

  Don't know if this problem is related to cups or avahi ...

  Ubuntu 16.10
  cups 2.2.0-2

  What i expected to happen: printing successful
  What happened: client cannot locate remote printer, add to add a line in 
/etc/hosts to make it work

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

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


[Desktop-packages] [Bug 1838177] Re: bluetooth->settings causes gnome-shell assertion failure, then many video-releated msgs

2019-09-26 Thread Launchpad Bug Tracker
[Expired for gnome-shell (Ubuntu) because there has been no activity for
60 days.]

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

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

Title:
  bluetooth->settings causes gnome-shell assertion failure, then many
  video-releated msgs

Status in gnome-shell package in Ubuntu:
  Expired

Bug description:
  Whenever the "bluetooth settings" screen is opened, an assertion
  failure is logged from gnome-shell, followed by many video-related
  lines from gdm-x-session (syslog extract attached). The first part
  looks like this:

  gnome-shell[2872]: g_environ_setenv: assertion 'value != NULL' failed
  /usr/lib/gdm3/gdm-x-session[2251]: (II) modeset(0): EDID vendor "NEC", prod 
id 26342
  ...

  STEPS TO REPRODUCE:
  1. tail -f /var/log/syslog  #in a terminal
  2. In the upper-right top of the screen:
   Speakericon->Bluetoothicon->Gluetooth settings

  RESULTS: BT settings window openens, and many messages logged to syslog
  EXPECTED RESULTS: No assertion errors logged (unclear why anything should be 
logged due to simply opening a window).

  NOTE: Please disregard comments #2 through #5 below, they were
  intended for a differenb bugrep.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: gnome-shell 3.32.1-1ubuntu1~19.04.1
  ProcVersionSignature: Ubuntu 5.0.0-21.22-generic 5.0.15
  Uname: Linux 5.0.0-21-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27.1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Jul 27 22:37:13 2019
  DisplayManager: gdm3
  InstallationDate: Installed on 2018-04-05 (479 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Beta amd64 (20180403.1)
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to disco on 2019-07-26 (2 days ago)

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

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


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

2019-09-26 Thread Bug Watch Updater
** Changed in: ibus
   Status: Fix Released => New

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

Title:
  IBus no longer works in Qt applications after upgrade

Status in ibus:
  New
Status in ibus package in Ubuntu:
  Fix Released
Status in ibus package in Debian:
  Confirmed

Bug description:
  Kubuntu Release 18.04.3 LTS

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

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

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

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

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

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

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

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


[Desktop-packages] [Bug 452073]

2019-09-26 Thread Jérôme
Created attachment 154564
/opt/libreofficedev6.3/program/soffice in version 6.3_6.3.3.0.0

I downloaded the below daily build here :

https://dev-builds.libreoffice.org/daily/libreoffice-6-3/Linux-rpm_deb-
x86_64@86-TDF/2019-09-24_23.33.05/libreoffice-6-3~2019-09-24_23.33.05_LibreOfficeDev_6.3.3.0.0_Linux_x86-64_deb.tar.gz

Into this file, I found the libreofficedev6.3_6.3.3.0.0-1_amd64.deb package 
which has the attached file with the below path :
opt/libreofficedev6.3/program/soffice

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

Title:
  [Upstream] Shouldn't detect configuration at each invocation

Status in LibreOffice:
  Confirmed
Status in OpenOffice:
  New
Status in libreoffice package in Ubuntu:
  Confirmed
Status in openoffice.org package in Ubuntu:
  Won't Fix

Bug description:
  Binary package hint: openoffice.org

  At each invocation of oocalc, oowriter or ooimpress, the
  /usr/lib/openoffice/program/soffice shell script is executed.

  This script will quite always guess the same environment variables.
  Moreover, guessing those values is time consuming at the well known
  critical startup time of openoffice.

  I think we could cache the below environment settings into a 
/var/lib/openoffice/basis3.1/program/environment.sh file:
  -
  FILE_LOCKING=auto
  OPENGL_SUPPORT=no
  SAL_ENABLE_FILE_LOCKING=1
  SAL_NOOPENGL=true
  JITC_PROCESSOR_TYPE=6
  sd_cwd=/usr/lib/openoffice/program
  sd_binary=/usr/lib/openoffice/program/oosplash.bin
  -

  Those environment settings could be calculated again by an apt trigger
  or a daily cron task.

  ProblemType: Bug
  Architecture: i386
  Date: Thu Oct 15 12:46:20 2009
  Dependencies:
   
  DistroRelease: Ubuntu 9.10
  Package: openoffice.org-common 1:3.1.1-4ubuntu1 [modified: 
var/lib/openoffice/basis3.1/share/config/javasettingsunopkginstall.xml]
  PackageArchitecture: all
  ProcEnviron:
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 2.6.31-14.46-generic
  SourcePackage: openoffice.org
  Uname: Linux 2.6.31-14-generic i686

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

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


[Desktop-packages] [Bug 1802208]

2019-09-26 Thread Sbergman
(In reply to Jan-Marek Glogowski from comment #0)
> When OpenJDK tried to enforce stricter class path URL checks without
> previous announcement, things started to break left and right. This included
> failing LibreOffice JUnitTest checks, since the dependency classpath in our
> generated Jars doesn't pass the stricter URL checks and therefore is ignored.

It would have been useful to document exactly what failed.  At least
with java-latest-openjdk-headless-13.0.0.33-1.rolling.fc31.x86_64, the
testurlcheck program in configure.ac reports "false", but (when you
convert the corresponding AC_MSG_ERROR into a AC_MSG_RESULT to not make
configure fail) a full `make check screenshot` works fine for me.

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

Title:
  Reports won't open

Status in LibreOffice:
  Confirmed
Status in libreoffice package in Ubuntu:
  Invalid
Status in libreoffice source package in Xenial:
  Fix Released
Status in libreoffice source package in Bionic:
  Fix Released

Bug description:
  Reports that were working as of June this year (I haven't opened them
  since then) now are failing with the following error:

  Can not activate the factory for
  org.libreoffice.report.pentaho.SOReportJobFactory$_SOReportJobFactory

  I tried creating a fresh report to see if its some kind of out of date file 
format but I get the same error:
1. select "Create Report in Design View..."
2. select "Save"
3. Double click report
4. Same error as above

  Of course I'm expecting the report to open without an error.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: libreoffice-report-builder 1:6.0.6-0ubuntu0.18.04.1
  ProcVersionSignature: Ubuntu 4.15.0-38.41-generic 4.15.18
  Uname: Linux 4.15.0-38-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.4
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Nov  8 12:16:08 2018
  InstallationDate: Installed on 2018-02-17 (263 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
  PackageArchitecture: all
  SourcePackage: libreoffice
  UpgradeStatus: Upgraded to bionic on 2018-05-01 (190 days ago)

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

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


[Desktop-packages] [Bug 1827346] Re: Power: Fail to set delay time when the value is 90 minutes

2019-09-26 Thread Yuan-Chen Cheng
** Changed in: oem-priority/xenial
   Status: Fix Committed => Fix Released

** Changed in: oem-priority/bionic
   Status: Fix Committed => 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/1827346

Title:
  Power: Fail to set delay time when the value is 90 minutes

Status in OEM Priority Project:
  Fix Released
Status in OEM Priority Project bionic series:
  Fix Released
Status in OEM Priority Project xenial series:
  Fix Released
Status in gnome-control-center package in Ubuntu:
  Fix Released
Status in gnome-control-center source package in Xenial:
  Fix Released
Status in gnome-control-center source package in Bionic:
  Fix Released
Status in gnome-control-center source package in Disco:
  Fix Released

Bug description:
  [Impact]

  Fail to set delay time when the value is 90 minutes.

  In cc-power-panel.ui, the value of 90 minutes is 4800 (80*60), not
  5400 (90*60). When setting the delay time to 90 minutes, the UI will
  show "80 minutes" after reopening "All Settings". (Please refer to the
  photo in #1 and #2)

  [Test Case]

  1) Go to [All Settings][Power][Automatic suspend]

  2) Set delay time to 90 minutes (On Battery Power or Plugged in)

  3) Close [All Settings]

  4) Reopen [All Settings][Power][Automatic suspend]

  5) Check if the value is 90 minutes.

  [Regression Potential]

  Low. The value of 90 minutes is wrong. Just correct the value to 5400.

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

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


[Desktop-packages] [Bug 1845286] Re: pdftoraster crashed with SIGSEGV in convert8to16()

2019-09-26 Thread Till Kamppeter
I have fixed the pdftoraster crash upstream. Note also that there is
still a bug in the implicitclass backend which is currently worked on.

** Changed in: cups-filters (Ubuntu)
   Status: Confirmed => In Progress

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

Title:
  pdftoraster crashed with SIGSEGV in convert8to16()

Status in cups-filters package in Ubuntu:
  In Progress

Bug description:
  Tried to print a pdf via an auto configured cups printer - pdftoraster
  crashed nothing was printed.

  ProblemType: Crash
  DistroRelease: Ubuntu 19.10
  Package: cups-filters-core-drivers 1.25.6-0ubuntu1
  ProcVersionSignature: Ubuntu 5.3.0-10.11-generic 5.3.0-rc8
  Uname: Linux 5.3.0-10-generic x86_64
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  Date: Wed Sep 25 06:49:10 2019
  ExecutablePath: /usr/lib/cups/filter/pdftoraster
  InstallationDate: Installed on 2018-09-06 (383 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  Lpstat:
   device for Brother_HL_L2300D_series_MacBook_de_Yasser: ///dev/null
   device for cespu_geral_MacBook_Air_de_Jo_o: ///dev/null
   device for Deskjet_3050A_J611_series_MacBook_Air: ///dev/null
   device for HP-Officejet-Pro-8620: 
dnssd://HP%20Officejet%20Pro%208620%20%5B794B2D%5D._ipp._tcp.local/?uuid=1c852a4d-b800-1f08-abcd-3863bb794b2d
   device for HP_Officejet_Pro_8620_794B2D_: 
implicitclass://HP_Officejet_Pro_8620_794B2D_/
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 04ca:7054 Lite-On Technology Corp. HP HD Camera
   Bus 001 Device 002: ID 8087:0a2b Intel Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: HP HP EliteBook 840 G3
  Papersize: a4
  PpdFiles:
   HP-Officejet-Pro-8620: HP Officejet Pro 8620, driverless, cups-filters 1.25.4
   HP_Officejet_Pro_8620_794B2D_: HP Officejet Pro 8620, driverless, 
cups-filters 1.25.6
  ProcCmdline: implicitclass://HP_Officejet_Pro_8620_794B2D_/ 109 z003te9p 
Lauf\ gegen\ Krebs\ 2019.pdf 1 print-content-optimize=auto\ 
print-rendering-intent=auto\ ColorModel=DeviceGray\ Duplex=DuplexNoTumble\ 
MediaType=Stationery\ number-up=1\ PageSize=A4\ print-scaling=auto\ noCollate\ 
cupsPrintQuality=4\ job-uuid=urn:uuid:1166fa02-95cc-3560-7cd2-f256658917ad\ 
cups-browsed\ job-originating-host-name=localhost\ date-time-at-creation=\ 
date-time-at-processing=\ time-at-creation=1569386949\ 
time-at-processing=1569386949\ print-quality=4\ output-format=apple-raster\ 
Resolution=300dpi\ media-class=pwg\ page-logging=on
  ProcEnviron:
   PATH=(custom, no user)
   LANG=en_US.UTF-8
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-10-generic 
root=UUID=a8dfd19d-7ac8-43b7-bb4d-41c72407226f ro quiet splash vt.handoff=7
  SegvAnalysis:
   Segfault happened at: 0x55e344d74b9b:movzbl (%rdx),%r9d
   PC (0x55e344d74b9b) ok
   source "(%rdx)" (0x55e346c168af) not located in a known VMA region (needed 
readable region)!
   destination "%r9d" ok
  SegvReason: reading unknown VMA
  Signal: 11
  SourcePackage: cups-filters
  StacktraceTop:
   ?? ()
   ?? ()
   ?? ()
   __libc_start_main (main=0x55e344d71b90, argc=6, argv=0x7ffcb779bdc8, 
init=, fini=, rtld_fini=, 
stack_end=0x7ffcb779bdb8) at ../csu/libc-start.c:308
   ?? ()
  Title: pdftoraster crashed with SIGSEGV in __libc_start_main()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  dmi.bios.date: 11/01/2016
  dmi.bios.vendor: HP
  dmi.bios.version: N75 Ver. 01.13
  dmi.board.name: 8079
  dmi.board.vendor: HP
  dmi.board.version: KBC Version 85.74
  dmi.chassis.asset.tag: 5CG7060XN6
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.modalias: 
dmi:bvnHP:bvrN75Ver.01.13:bd11/01/2016:svnHP:pnHPEliteBook840G3:pvr:rvnHP:rn8079:rvrKBCVersion85.74:cvnHP:ct10:cvr:
  dmi.product.family: 103C_5336AN G=N L=BUS B=HP S=ELI
  dmi.product.name: HP EliteBook 840 G3
  dmi.product.sku: W0Q03EC#ABD
  dmi.sys.vendor: HP
  separator:

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

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


[Desktop-packages] [Bug 1845332] Re: Compose key does not create strings

2019-09-26 Thread Gunnar Hjalmarsson
On 2019-09-26 18:51, Oryganum wrote:
>> That wiki page you referred  to was last edited 11 years ago and is
>> obsolete to a large extent.
> 
> Is it possible to contact someone to ask to update this page?

The simple answer to that question is no.

There is a similar page which is somewhat less obsolete, even if also
that one needs to be updated:

https://help.ubuntu.com/community/ComposeKey

But such tutorials are user contributions, and there is no team or
individual who is responsible for maintaining them. So what you can do
is applying to get edit access and try to improve them yourself.

https://help.ubuntu.com/community/WikiGuide#Contributing

I'm inclined to think that  should
be deleted and the other page updated.

> On my Ubuntu 18.04 "Keyboard input method system" gives me options
> IBus, XIM and none.
> 
> Is there any known advantage of choosing IBus there?
> (I am trying to understand why XIM is not a default.)

Given that Ubuntu is now on GNOME, which relies on IBus to a large
extent, IBus will keep being default.

XIM is old, sometimes problematic (see e.g. bug #1573755), and will
probably be dropped completely if/when Ubuntu switches from X to
Wayland.

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

Title:
  Compose key does not create strings

Status in ibus package in Ubuntu:
  Invalid

Bug description:
  According to manual https://wiki.ubuntu.com/ComposeKey it is possible to 
define sequences to type characters and strings with Compose key.
  In Ubuntu 18.04 sequences work for characters but not for strings, line like 
this:
 : "by the way" # Compose b t w
  seems to be ignored.

  $ apt-cache policy ibus
  ibus:
Installed: 1.5.17-3ubuntu5.2
Candidate: 1.5.17-3ubuntu5.2
Version table:
   *** 1.5.17-3ubuntu5.2 500
  500 http://mirror.isoc.org.il/pub/ubuntu bionic-updates/main amd64 
Packages
  500 http://mirror.isoc.org.il/pub/ubuntu bionic-security/main amd64 
Packages
  100 /var/lib/dpkg/status
   1.5.17-3ubuntu4 500
  500 http://mirror.isoc.org.il/pub/ubuntu bionic/main amd64 Packages
  500 http://cz.archive.ubuntu.com/ubuntu bionic/main amd64 Packages

  This problem first reported at Dec 11 '18 and also exists in Kubuntu
  18.04 (see https://askubuntu.com/questions/1099947/how-to-use-
  xcompose-to-produce-snippets).

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

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


[Desktop-packages] [Bug 1845532] Re: power icon does not indicate charging if booted without power connected

2019-09-26 Thread Heather Ellsworth
In 19.10, with the error state, restarting upower fixes the issue. So if
you've booted without power connected, then connect power and don't see
the charging icon, execute `sudo systemctl restart upower` and see the
charging symbol.

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

Title:
  power icon does not indicate charging if booted without power
  connected

Status in upower package in Ubuntu:
  New

Bug description:
  Hardware: Lenovo T590
  OS: 19.10

  When the power is not connected when the laptop boots, and then
  connected, the power icon in the top bar does not change to indicate
  that the laptop is now charging.

  $ upower -d
  Device: /org/freedesktop/UPower/devices/line_power_AC 

 
native-path:  AC

 
power supply: yes   

 
updated:  Thu 26 Sep 2019 08:53:40 AM MDT (2107 seconds ago)
has history:  no
has statistics:   no
line-power
  warning-level:   none
  online:  no
  icon-name:  'ac-adapter-symbolic'

  Device: /org/freedesktop/UPower/devices/battery_BAT0 
native-path:  BAT0
vendor:   SMP
model:02DL012
serial:   1417
power supply: yes
updated:  Thu 26 Sep 2019 09:28:33 AM MDT (14 seconds ago)
has history:  yes
has statistics:   yes
battery
  present: yes
  rechargeable:yes
  state:   discharging
  warning-level:   none
  energy:  55.53 Wh
  energy-empty:0 Wh
  energy-full: 57.21 Wh
  energy-full-design:  57.02 Wh
  energy-rate: 0.319173 W
  voltage: 12.932 V
  time to empty:   7.2 days
  percentage:  97%
  capacity:100%
  technology:  lithium-polymer
  icon-name:  'battery-full-symbolic'

  Device: /org/freedesktop/UPower/devices/DisplayDevice
power supply: yes
updated:  Thu 26 Sep 2019 09:22:33 AM MDT (374 seconds ago)
has history:  no
has statistics:   no
battery
  present: yes
  state:   discharging
  warning-level:   none
  energy:  55.53 Wh
  energy-full: 57.21 Wh
  energy-rate: 0.319173 W
  time to empty:   7.2 days
  percentage:  97%
  icon-name:  'battery-full-symbolic'

  Daemon:
daemon-version:  0.99.11
on-battery:  yes
lid-is-closed:   no
lid-is-present:  yes
critical-action: PowerOff

  $ cat /sys/class/power_supply/BAT0/status 
  Unknown

  However, if the laptop is booted with the power connected, then the
  battery icon in the top bar shows that it's charging and at 100%. If I
  unplug the power, it correctly shows that it is no longer charging but
  it goes back to saying I'm at 97% (the last reported state when booted
  without power).

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: upower 0.99.11-1
  ProcVersionSignature: Ubuntu 5.3.0-10.11-generic 5.3.0-rc8
  Uname: Linux 5.3.0-10-generic x86_64
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Sep 26 10:24:38 2019
  InstallationDate: Installed on 2019-09-13 (12 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: upower
  UpgradeStatus: Upgraded to eoan on 2019-09-19 (7 days ago)

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

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


[Desktop-packages] [Bug 1315349] Re: fonts-linuxlibertine don't have Linux Libertine G (but have Linux libertine O)

2019-09-26 Thread Francois Audirac
This problem already exist in Ubuntu 18.04.
The Linux Biolinum O font is coming with Libreoffice 6, but in Windows package 
Libreoffice comes with the Linux Biolinum G. 
And any document can work without the policy rules.

Can you correct this package and add the G version too ?

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

Title:
  fonts-linuxlibertine don't have Linux Libertine G (but have Linux
  libertine O)

Status in fonts-linuxlibertine package in Ubuntu:
  Confirmed
Status in libreoffice package in Ubuntu:
  Won't Fix

Bug description:
  When you downlaod Linux Libertine you thinks, you have all the fonts:
  * font sans-serif face: Linux Biolinum
  * font sherif : Linux Libertine

  All of theme have two versions: O and G.
  fonts-linuxlibertine give only O version, not the G

  Actual: fonts-linuxlibertine give only O version. The user think with
  LibreOffice (who give the G and O version in its website inside
  LibreOffice for Linux, Windows and Mac OS) that Ubuntu give the two
  versions. But it's not true.

  Expected: fonts-linuxlibertine must give O and G versions.

  Workforme: downlaod from http://numbertext.org/linux/ but it's not
  user friendly (and Ubuntu love to be user friendy).

  
  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: fonts-linuxlibertine 5.1.3-1
  ProcVersionSignature: Ubuntu 3.11.0-20.34~precise1-generic 3.11.10.6
  Uname: Linux 3.11.0-20-generic x86_64
  ApportVersion: 2.0.1-0ubuntu17.6
  Architecture: amd64
  Date: Fri May  2 13:07:38 2014
  Dependencies:

  InstallationMedia: Ubuntu 12.04 "Precise" - Build amd64 LIVE Binary 
20120425-15:28
  MarkForUpload: True
  PackageArchitecture: all
  SourcePackage: fonts-linuxlibertine
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/fonts-linuxlibertine/+bug/1315349/+subscriptions

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


[Desktop-packages] [Bug 1845532] Re: power icon does not indicate charging if booted without power connected

2019-09-26 Thread Heather Ellsworth
I tried this in a 19.04 live boot from a usb stick and the behavior was
correct: if the system was booted without power, the charging symbol was
not there. Then when I connected the power, the charging symbol
appeared.

Also, when booting 19.04 without power connected, there is only the one 
dbus-daemon line in journalctl:
Sep 26 18:55:04 ubuntu dbus-daemon[1097]: [system] Activating via systemd: 
service name='org.freedesktop.UPower' unit='upower.service' requested by 
':1.38' (uid=999 pid=1761 comm="/usr/bin/gnome-shell " label="u
nconfined")

So there is some regression between 19.04 and current 19.10.

19.04 kernel: 5.0.0.-13.14
19.10 kernel: 5.3.0-10.11

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

Title:
  power icon does not indicate charging if booted without power
  connected

Status in upower package in Ubuntu:
  New

Bug description:
  Hardware: Lenovo T590
  OS: 19.10

  When the power is not connected when the laptop boots, and then
  connected, the power icon in the top bar does not change to indicate
  that the laptop is now charging.

  $ upower -d
  Device: /org/freedesktop/UPower/devices/line_power_AC 

 
native-path:  AC

 
power supply: yes   

 
updated:  Thu 26 Sep 2019 08:53:40 AM MDT (2107 seconds ago)
has history:  no
has statistics:   no
line-power
  warning-level:   none
  online:  no
  icon-name:  'ac-adapter-symbolic'

  Device: /org/freedesktop/UPower/devices/battery_BAT0 
native-path:  BAT0
vendor:   SMP
model:02DL012
serial:   1417
power supply: yes
updated:  Thu 26 Sep 2019 09:28:33 AM MDT (14 seconds ago)
has history:  yes
has statistics:   yes
battery
  present: yes
  rechargeable:yes
  state:   discharging
  warning-level:   none
  energy:  55.53 Wh
  energy-empty:0 Wh
  energy-full: 57.21 Wh
  energy-full-design:  57.02 Wh
  energy-rate: 0.319173 W
  voltage: 12.932 V
  time to empty:   7.2 days
  percentage:  97%
  capacity:100%
  technology:  lithium-polymer
  icon-name:  'battery-full-symbolic'

  Device: /org/freedesktop/UPower/devices/DisplayDevice
power supply: yes
updated:  Thu 26 Sep 2019 09:22:33 AM MDT (374 seconds ago)
has history:  no
has statistics:   no
battery
  present: yes
  state:   discharging
  warning-level:   none
  energy:  55.53 Wh
  energy-full: 57.21 Wh
  energy-rate: 0.319173 W
  time to empty:   7.2 days
  percentage:  97%
  icon-name:  'battery-full-symbolic'

  Daemon:
daemon-version:  0.99.11
on-battery:  yes
lid-is-closed:   no
lid-is-present:  yes
critical-action: PowerOff

  $ cat /sys/class/power_supply/BAT0/status 
  Unknown

  However, if the laptop is booted with the power connected, then the
  battery icon in the top bar shows that it's charging and at 100%. If I
  unplug the power, it correctly shows that it is no longer charging but
  it goes back to saying I'm at 97% (the last reported state when booted
  without power).

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: upower 0.99.11-1
  ProcVersionSignature: Ubuntu 5.3.0-10.11-generic 5.3.0-rc8
  Uname: Linux 5.3.0-10-generic x86_64
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Sep 26 10:24:38 2019
  InstallationDate: Installed on 2019-09-13 (12 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: upower
  UpgradeStatus: Upgraded to eoan on 2019-09-19 (7 days ago)

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

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

[Desktop-packages] [Bug 1845548] Stacktrace.txt

2019-09-26 Thread Apport retracing service
** Attachment added: "Stacktrace.txt"
   
https://bugs.launchpad.net/bugs/1845548/+attachment/5291574/+files/Stacktrace.txt

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

Title:
  implicitclass crashed with SIGABRT in __malloc_assert()

Status in cups-filters package in Ubuntu:
  New

Bug description:
  This crashed when attempting to print from firefox

  ProblemType: Crash
  DistroRelease: Ubuntu 19.10
  Package: cups-browsed 1.25.6-0ubuntu1
  ProcVersionSignature: Ubuntu 5.3.0-10.11-generic 5.3.0-rc8
  Uname: Linux 5.3.0-10-generic x86_64
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  Date: Thu Sep 26 14:23:48 2019
  ExecutablePath: /usr/lib/cups/backend/implicitclass
  InstallationDate: Installed on 2019-09-11 (14 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  Lpstat: device for HP_OfficeJet_Pro_8720_BA2C6F_: 
implicitclass://HP_OfficeJet_Pro_8720_BA2C6F_/
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 0bda:c024 Realtek Semiconductor Corp. Bluetooth Radio 
   Bus 001 Device 003: ID 04ca:7070 Lite-On Technology Corp. Integrated Camera
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 4810CT0100
  Papersize: letter
  PpdFiles: HP_OfficeJet_Pro_8720_BA2C6F_: OfficeJet Pro 8720 - IPP Everywhere
  ProcCmdline: implicitclass://HP_OfficeJet_Pro_8720_BA2C6F_/ 2 ken VanDine\ 
Family\ Mail\ -\ Your\ Crucial.com\ Return\ Instructions 1 ColorModel=RGB\ 
cupsPrintQuality=Normal\ MediaType=Stationery\ number-up=1\ noCollate\ 
PageSize=Letter\ Duplex=None\ 
job-uuid=urn:uuid:011f0db5-151a-337b-78c0-2af327efcc22\ cups-browsed\ 
cups-browsed-dest-printer=\\"1\\\ ipps://HP1062E5BA2C6F.local:443/ipp/print\\\ 
raster\\\ 300dpi\\"\ job-originating-host-name=localhost\ 
date-time-at-creation=\ date-time-at-processing=\ time-at-creation=156958\ 
time-at-processing=156958\ print-quality=4
  ProcEnviron:
   PATH=(custom, no user)
   LANG=en_US.UTF-8
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-10-generic 
root=UUID=f9d6b524-56b4-475b-a2a2-97e20145f088 ro quiet splash vt.handoff=7
  Signal: 6
  SourcePackage: cups-filters
  StacktraceTop:
   __malloc_assert (assertion=assertion@entry=0x7f9b1a1512d8 "(old_top == 
initial_top (av) && old_size == 0) || ((unsigned long) (old_size) >= MINSIZE && 
prev_inuse (old_top) && ((unsigned long) old_end & (pagesize - 1)) == 0)", 
file=file@entry=0x7f9b1a14d43f "malloc.c", line=line@entry=2379, 
function=function@entry=0x7f9b1a151a60 <__PRETTY_FUNCTION__.13032> "sysmalloc") 
at malloc.c:298
   sysmalloc (nb=nb@entry=384, av=av@entry=0x7f9b1a180b80 ) at 
malloc.c:2379
   _int_malloc (av=av@entry=0x7f9b1a180b80 , bytes=bytes@entry=375) 
at malloc.c:4141
   __GI___libc_malloc (bytes=bytes@entry=375) at malloc.c:3058
   __GI___strdup (s=0x55ed9340a050 "ColorModel=RGB cupsPrintQuality=Normal 
MediaType=Stationery number-up=1 noCollate PageSize=Letter Duplex=None 
job-uuid=urn:uuid:011f0db5-151a-337b-78c0-2af327efcc22 cups-browsed 
job-originating-host-n"...) at strdup.c:42
  Title: implicitclass crashed with SIGABRT in __malloc_assert()
  UpgradeStatus: Upgraded to eoan on 2019-09-12 (14 days ago)
  UserGroups:
   
  dmi.bios.date: 09/07/2017
  dmi.bios.vendor: LENOVO
  dmi.bios.version: R0RET08L (0.08 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 4810CT0100
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrR0RET08L(0.08):bd09/07/2017:svnLENOVO:pn4810CT0100:pvrThinkPad133rdGen:rvnLENOVO:rn4810CT0100:rvrNotDefined:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad 13 3rd Gen
  dmi.product.name: 4810CT0100
  dmi.product.sku: LENOVO_MT_4810_BU_Think_FM_ThinkPad 13 3rd Gen
  dmi.product.version: ThinkPad 13 3rd Gen
  dmi.sys.vendor: LENOVO
  separator:

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

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


[Desktop-packages] [Bug 1845548] StacktraceSource.txt

2019-09-26 Thread Apport retracing service
** Attachment added: "StacktraceSource.txt"
   
https://bugs.launchpad.net/bugs/1845548/+attachment/5291575/+files/StacktraceSource.txt

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

Title:
  implicitclass crashed with SIGABRT in __malloc_assert()

Status in cups-filters package in Ubuntu:
  New

Bug description:
  This crashed when attempting to print from firefox

  ProblemType: Crash
  DistroRelease: Ubuntu 19.10
  Package: cups-browsed 1.25.6-0ubuntu1
  ProcVersionSignature: Ubuntu 5.3.0-10.11-generic 5.3.0-rc8
  Uname: Linux 5.3.0-10-generic x86_64
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  Date: Thu Sep 26 14:23:48 2019
  ExecutablePath: /usr/lib/cups/backend/implicitclass
  InstallationDate: Installed on 2019-09-11 (14 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  Lpstat: device for HP_OfficeJet_Pro_8720_BA2C6F_: 
implicitclass://HP_OfficeJet_Pro_8720_BA2C6F_/
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 0bda:c024 Realtek Semiconductor Corp. Bluetooth Radio 
   Bus 001 Device 003: ID 04ca:7070 Lite-On Technology Corp. Integrated Camera
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 4810CT0100
  Papersize: letter
  PpdFiles: HP_OfficeJet_Pro_8720_BA2C6F_: OfficeJet Pro 8720 - IPP Everywhere
  ProcCmdline: implicitclass://HP_OfficeJet_Pro_8720_BA2C6F_/ 2 ken VanDine\ 
Family\ Mail\ -\ Your\ Crucial.com\ Return\ Instructions 1 ColorModel=RGB\ 
cupsPrintQuality=Normal\ MediaType=Stationery\ number-up=1\ noCollate\ 
PageSize=Letter\ Duplex=None\ 
job-uuid=urn:uuid:011f0db5-151a-337b-78c0-2af327efcc22\ cups-browsed\ 
cups-browsed-dest-printer=\\"1\\\ ipps://HP1062E5BA2C6F.local:443/ipp/print\\\ 
raster\\\ 300dpi\\"\ job-originating-host-name=localhost\ 
date-time-at-creation=\ date-time-at-processing=\ time-at-creation=156958\ 
time-at-processing=156958\ print-quality=4
  ProcEnviron:
   PATH=(custom, no user)
   LANG=en_US.UTF-8
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-10-generic 
root=UUID=f9d6b524-56b4-475b-a2a2-97e20145f088 ro quiet splash vt.handoff=7
  Signal: 6
  SourcePackage: cups-filters
  StacktraceTop:
   __malloc_assert (assertion=assertion@entry=0x7f9b1a1512d8 "(old_top == 
initial_top (av) && old_size == 0) || ((unsigned long) (old_size) >= MINSIZE && 
prev_inuse (old_top) && ((unsigned long) old_end & (pagesize - 1)) == 0)", 
file=file@entry=0x7f9b1a14d43f "malloc.c", line=line@entry=2379, 
function=function@entry=0x7f9b1a151a60 <__PRETTY_FUNCTION__.13032> "sysmalloc") 
at malloc.c:298
   sysmalloc (nb=nb@entry=384, av=av@entry=0x7f9b1a180b80 ) at 
malloc.c:2379
   _int_malloc (av=av@entry=0x7f9b1a180b80 , bytes=bytes@entry=375) 
at malloc.c:4141
   __GI___libc_malloc (bytes=bytes@entry=375) at malloc.c:3058
   __GI___strdup (s=0x55ed9340a050 "ColorModel=RGB cupsPrintQuality=Normal 
MediaType=Stationery number-up=1 noCollate PageSize=Letter Duplex=None 
job-uuid=urn:uuid:011f0db5-151a-337b-78c0-2af327efcc22 cups-browsed 
job-originating-host-n"...) at strdup.c:42
  Title: implicitclass crashed with SIGABRT in __malloc_assert()
  UpgradeStatus: Upgraded to eoan on 2019-09-12 (14 days ago)
  UserGroups:
   
  dmi.bios.date: 09/07/2017
  dmi.bios.vendor: LENOVO
  dmi.bios.version: R0RET08L (0.08 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 4810CT0100
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrR0RET08L(0.08):bd09/07/2017:svnLENOVO:pn4810CT0100:pvrThinkPad133rdGen:rvnLENOVO:rn4810CT0100:rvrNotDefined:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad 13 3rd Gen
  dmi.product.name: 4810CT0100
  dmi.product.sku: LENOVO_MT_4810_BU_Think_FM_ThinkPad 13 3rd Gen
  dmi.product.version: ThinkPad 13 3rd Gen
  dmi.sys.vendor: LENOVO
  separator:

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

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


[Desktop-packages] [Bug 1845548] ThreadStacktrace.txt

2019-09-26 Thread Apport retracing service
** Attachment added: "ThreadStacktrace.txt"
   
https://bugs.launchpad.net/bugs/1845548/+attachment/5291576/+files/ThreadStacktrace.txt

** Tags added: apport-failed-retrace

** Tags removed: need-amd64-retrace

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

Title:
  implicitclass crashed with SIGABRT in __malloc_assert()

Status in cups-filters package in Ubuntu:
  New

Bug description:
  This crashed when attempting to print from firefox

  ProblemType: Crash
  DistroRelease: Ubuntu 19.10
  Package: cups-browsed 1.25.6-0ubuntu1
  ProcVersionSignature: Ubuntu 5.3.0-10.11-generic 5.3.0-rc8
  Uname: Linux 5.3.0-10-generic x86_64
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  Date: Thu Sep 26 14:23:48 2019
  ExecutablePath: /usr/lib/cups/backend/implicitclass
  InstallationDate: Installed on 2019-09-11 (14 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  Lpstat: device for HP_OfficeJet_Pro_8720_BA2C6F_: 
implicitclass://HP_OfficeJet_Pro_8720_BA2C6F_/
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 0bda:c024 Realtek Semiconductor Corp. Bluetooth Radio 
   Bus 001 Device 003: ID 04ca:7070 Lite-On Technology Corp. Integrated Camera
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 4810CT0100
  Papersize: letter
  PpdFiles: HP_OfficeJet_Pro_8720_BA2C6F_: OfficeJet Pro 8720 - IPP Everywhere
  ProcCmdline: implicitclass://HP_OfficeJet_Pro_8720_BA2C6F_/ 2 ken VanDine\ 
Family\ Mail\ -\ Your\ Crucial.com\ Return\ Instructions 1 ColorModel=RGB\ 
cupsPrintQuality=Normal\ MediaType=Stationery\ number-up=1\ noCollate\ 
PageSize=Letter\ Duplex=None\ 
job-uuid=urn:uuid:011f0db5-151a-337b-78c0-2af327efcc22\ cups-browsed\ 
cups-browsed-dest-printer=\\"1\\\ ipps://HP1062E5BA2C6F.local:443/ipp/print\\\ 
raster\\\ 300dpi\\"\ job-originating-host-name=localhost\ 
date-time-at-creation=\ date-time-at-processing=\ time-at-creation=156958\ 
time-at-processing=156958\ print-quality=4
  ProcEnviron:
   PATH=(custom, no user)
   LANG=en_US.UTF-8
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-10-generic 
root=UUID=f9d6b524-56b4-475b-a2a2-97e20145f088 ro quiet splash vt.handoff=7
  Signal: 6
  SourcePackage: cups-filters
  StacktraceTop:
   __malloc_assert (assertion=assertion@entry=0x7f9b1a1512d8 "(old_top == 
initial_top (av) && old_size == 0) || ((unsigned long) (old_size) >= MINSIZE && 
prev_inuse (old_top) && ((unsigned long) old_end & (pagesize - 1)) == 0)", 
file=file@entry=0x7f9b1a14d43f "malloc.c", line=line@entry=2379, 
function=function@entry=0x7f9b1a151a60 <__PRETTY_FUNCTION__.13032> "sysmalloc") 
at malloc.c:298
   sysmalloc (nb=nb@entry=384, av=av@entry=0x7f9b1a180b80 ) at 
malloc.c:2379
   _int_malloc (av=av@entry=0x7f9b1a180b80 , bytes=bytes@entry=375) 
at malloc.c:4141
   __GI___libc_malloc (bytes=bytes@entry=375) at malloc.c:3058
   __GI___strdup (s=0x55ed9340a050 "ColorModel=RGB cupsPrintQuality=Normal 
MediaType=Stationery number-up=1 noCollate PageSize=Letter Duplex=None 
job-uuid=urn:uuid:011f0db5-151a-337b-78c0-2af327efcc22 cups-browsed 
job-originating-host-n"...) at strdup.c:42
  Title: implicitclass crashed with SIGABRT in __malloc_assert()
  UpgradeStatus: Upgraded to eoan on 2019-09-12 (14 days ago)
  UserGroups:
   
  dmi.bios.date: 09/07/2017
  dmi.bios.vendor: LENOVO
  dmi.bios.version: R0RET08L (0.08 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 4810CT0100
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrR0RET08L(0.08):bd09/07/2017:svnLENOVO:pn4810CT0100:pvrThinkPad133rdGen:rvnLENOVO:rn4810CT0100:rvrNotDefined:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad 13 3rd Gen
  dmi.product.name: 4810CT0100
  dmi.product.sku: LENOVO_MT_4810_BU_Think_FM_ThinkPad 13 3rd Gen
  dmi.product.version: ThinkPad 13 3rd Gen
  dmi.sys.vendor: LENOVO
  separator:

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

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


[Desktop-packages] [Bug 1845548] implicitclass crashed with SIGABRT in __malloc_assert()

2019-09-26 Thread Apport retracing service
StacktraceTop:
 raise () from /tmp/apport_sandbox_wdms9auk/lib/x86_64-linux-gnu/libc.so.6
 abort () from /tmp/apport_sandbox_wdms9auk/lib/x86_64-linux-gnu/libc.so.6
 ?? () from /tmp/apport_sandbox_wdms9auk/lib/x86_64-linux-gnu/libc.so.6
 ?? () from /tmp/apport_sandbox_wdms9auk/lib/x86_64-linux-gnu/libc.so.6
 ?? () from /tmp/apport_sandbox_wdms9auk/lib/x86_64-linux-gnu/libc.so.6

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

Title:
  implicitclass crashed with SIGABRT in __malloc_assert()

Status in cups-filters package in Ubuntu:
  New

Bug description:
  This crashed when attempting to print from firefox

  ProblemType: Crash
  DistroRelease: Ubuntu 19.10
  Package: cups-browsed 1.25.6-0ubuntu1
  ProcVersionSignature: Ubuntu 5.3.0-10.11-generic 5.3.0-rc8
  Uname: Linux 5.3.0-10-generic x86_64
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  Date: Thu Sep 26 14:23:48 2019
  ExecutablePath: /usr/lib/cups/backend/implicitclass
  InstallationDate: Installed on 2019-09-11 (14 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  Lpstat: device for HP_OfficeJet_Pro_8720_BA2C6F_: 
implicitclass://HP_OfficeJet_Pro_8720_BA2C6F_/
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 0bda:c024 Realtek Semiconductor Corp. Bluetooth Radio 
   Bus 001 Device 003: ID 04ca:7070 Lite-On Technology Corp. Integrated Camera
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 4810CT0100
  Papersize: letter
  PpdFiles: HP_OfficeJet_Pro_8720_BA2C6F_: OfficeJet Pro 8720 - IPP Everywhere
  ProcCmdline: implicitclass://HP_OfficeJet_Pro_8720_BA2C6F_/ 2 ken VanDine\ 
Family\ Mail\ -\ Your\ Crucial.com\ Return\ Instructions 1 ColorModel=RGB\ 
cupsPrintQuality=Normal\ MediaType=Stationery\ number-up=1\ noCollate\ 
PageSize=Letter\ Duplex=None\ 
job-uuid=urn:uuid:011f0db5-151a-337b-78c0-2af327efcc22\ cups-browsed\ 
cups-browsed-dest-printer=\\"1\\\ ipps://HP1062E5BA2C6F.local:443/ipp/print\\\ 
raster\\\ 300dpi\\"\ job-originating-host-name=localhost\ 
date-time-at-creation=\ date-time-at-processing=\ time-at-creation=156958\ 
time-at-processing=156958\ print-quality=4
  ProcEnviron:
   PATH=(custom, no user)
   LANG=en_US.UTF-8
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-10-generic 
root=UUID=f9d6b524-56b4-475b-a2a2-97e20145f088 ro quiet splash vt.handoff=7
  Signal: 6
  SourcePackage: cups-filters
  StacktraceTop:
   __malloc_assert (assertion=assertion@entry=0x7f9b1a1512d8 "(old_top == 
initial_top (av) && old_size == 0) || ((unsigned long) (old_size) >= MINSIZE && 
prev_inuse (old_top) && ((unsigned long) old_end & (pagesize - 1)) == 0)", 
file=file@entry=0x7f9b1a14d43f "malloc.c", line=line@entry=2379, 
function=function@entry=0x7f9b1a151a60 <__PRETTY_FUNCTION__.13032> "sysmalloc") 
at malloc.c:298
   sysmalloc (nb=nb@entry=384, av=av@entry=0x7f9b1a180b80 ) at 
malloc.c:2379
   _int_malloc (av=av@entry=0x7f9b1a180b80 , bytes=bytes@entry=375) 
at malloc.c:4141
   __GI___libc_malloc (bytes=bytes@entry=375) at malloc.c:3058
   __GI___strdup (s=0x55ed9340a050 "ColorModel=RGB cupsPrintQuality=Normal 
MediaType=Stationery number-up=1 noCollate PageSize=Letter Duplex=None 
job-uuid=urn:uuid:011f0db5-151a-337b-78c0-2af327efcc22 cups-browsed 
job-originating-host-n"...) at strdup.c:42
  Title: implicitclass crashed with SIGABRT in __malloc_assert()
  UpgradeStatus: Upgraded to eoan on 2019-09-12 (14 days ago)
  UserGroups:
   
  dmi.bios.date: 09/07/2017
  dmi.bios.vendor: LENOVO
  dmi.bios.version: R0RET08L (0.08 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 4810CT0100
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrR0RET08L(0.08):bd09/07/2017:svnLENOVO:pn4810CT0100:pvrThinkPad133rdGen:rvnLENOVO:rn4810CT0100:rvrNotDefined:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad 13 3rd Gen
  dmi.product.name: 4810CT0100
  dmi.product.sku: LENOVO_MT_4810_BU_Think_FM_ThinkPad 13 3rd Gen
  dmi.product.version: ThinkPad 13 3rd Gen
  dmi.sys.vendor: LENOVO
  separator:

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

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


[Desktop-packages] [Bug 1845548] [NEW] implicitclass crashed with SIGABRT in __malloc_assert()

2019-09-26 Thread Ken VanDine
Public bug reported:

This crashed when attempting to print from firefox

ProblemType: Crash
DistroRelease: Ubuntu 19.10
Package: cups-browsed 1.25.6-0ubuntu1
ProcVersionSignature: Ubuntu 5.3.0-10.11-generic 5.3.0-rc8
Uname: Linux 5.3.0-10-generic x86_64
ApportVersion: 2.20.11-0ubuntu7
Architecture: amd64
Date: Thu Sep 26 14:23:48 2019
ExecutablePath: /usr/lib/cups/backend/implicitclass
InstallationDate: Installed on 2019-09-11 (14 days ago)
InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
Lpstat: device for HP_OfficeJet_Pro_8720_BA2C6F_: 
implicitclass://HP_OfficeJet_Pro_8720_BA2C6F_/
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 004: ID 0bda:c024 Realtek Semiconductor Corp. Bluetooth Radio 
 Bus 001 Device 003: ID 04ca:7070 Lite-On Technology Corp. Integrated Camera
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: LENOVO 4810CT0100
Papersize: letter
PpdFiles: HP_OfficeJet_Pro_8720_BA2C6F_: OfficeJet Pro 8720 - IPP Everywhere
ProcCmdline: implicitclass://HP_OfficeJet_Pro_8720_BA2C6F_/ 2 ken VanDine\ 
Family\ Mail\ -\ Your\ Crucial.com\ Return\ Instructions 1 ColorModel=RGB\ 
cupsPrintQuality=Normal\ MediaType=Stationery\ number-up=1\ noCollate\ 
PageSize=Letter\ Duplex=None\ 
job-uuid=urn:uuid:011f0db5-151a-337b-78c0-2af327efcc22\ cups-browsed\ 
cups-browsed-dest-printer=\\"1\\\ ipps://HP1062E5BA2C6F.local:443/ipp/print\\\ 
raster\\\ 300dpi\\"\ job-originating-host-name=localhost\ 
date-time-at-creation=\ date-time-at-processing=\ time-at-creation=156958\ 
time-at-processing=156958\ print-quality=4
ProcEnviron:
 PATH=(custom, no user)
 LANG=en_US.UTF-8
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-10-generic 
root=UUID=f9d6b524-56b4-475b-a2a2-97e20145f088 ro quiet splash vt.handoff=7
Signal: 6
SourcePackage: cups-filters
StacktraceTop:
 __malloc_assert (assertion=assertion@entry=0x7f9b1a1512d8 "(old_top == 
initial_top (av) && old_size == 0) || ((unsigned long) (old_size) >= MINSIZE && 
prev_inuse (old_top) && ((unsigned long) old_end & (pagesize - 1)) == 0)", 
file=file@entry=0x7f9b1a14d43f "malloc.c", line=line@entry=2379, 
function=function@entry=0x7f9b1a151a60 <__PRETTY_FUNCTION__.13032> "sysmalloc") 
at malloc.c:298
 sysmalloc (nb=nb@entry=384, av=av@entry=0x7f9b1a180b80 ) at 
malloc.c:2379
 _int_malloc (av=av@entry=0x7f9b1a180b80 , bytes=bytes@entry=375) 
at malloc.c:4141
 __GI___libc_malloc (bytes=bytes@entry=375) at malloc.c:3058
 __GI___strdup (s=0x55ed9340a050 "ColorModel=RGB cupsPrintQuality=Normal 
MediaType=Stationery number-up=1 noCollate PageSize=Letter Duplex=None 
job-uuid=urn:uuid:011f0db5-151a-337b-78c0-2af327efcc22 cups-browsed 
job-originating-host-n"...) at strdup.c:42
Title: implicitclass crashed with SIGABRT in __malloc_assert()
UpgradeStatus: Upgraded to eoan on 2019-09-12 (14 days ago)
UserGroups:
 
dmi.bios.date: 09/07/2017
dmi.bios.vendor: LENOVO
dmi.bios.version: R0RET08L (0.08 )
dmi.board.asset.tag: Not Available
dmi.board.name: 4810CT0100
dmi.board.vendor: LENOVO
dmi.board.version: Not Defined
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.modalias: 
dmi:bvnLENOVO:bvrR0RET08L(0.08):bd09/07/2017:svnLENOVO:pn4810CT0100:pvrThinkPad133rdGen:rvnLENOVO:rn4810CT0100:rvrNotDefined:cvnLENOVO:ct10:cvrNone:
dmi.product.family: ThinkPad 13 3rd Gen
dmi.product.name: 4810CT0100
dmi.product.sku: LENOVO_MT_4810_BU_Think_FM_ThinkPad 13 3rd Gen
dmi.product.version: ThinkPad 13 3rd Gen
dmi.sys.vendor: LENOVO
separator:

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


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

** Information type changed from Private to Public

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

Title:
  implicitclass crashed with SIGABRT in __malloc_assert()

Status in cups-filters package in Ubuntu:
  New

Bug description:
  This crashed when attempting to print from firefox

  ProblemType: Crash
  DistroRelease: Ubuntu 19.10
  Package: cups-browsed 1.25.6-0ubuntu1
  ProcVersionSignature: Ubuntu 5.3.0-10.11-generic 5.3.0-rc8
  Uname: Linux 5.3.0-10-generic x86_64
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  Date: Thu Sep 26 14:23:48 2019
  ExecutablePath: /usr/lib/cups/backend/implicitclass
  InstallationDate: Installed on 2019-09-11 (14 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  Lpstat: device for HP_OfficeJet_Pro_8720_BA2C6F_: 
implicitclass://HP_OfficeJet_Pro_8720_BA2C6F_/
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 0bda:c024 Realtek Semiconductor Corp. Bluetooth Radio 
   Bus 001 Device 003: ID 04ca:7070 Lite-On Technology Corp. Integrated Camera
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  

[Desktop-packages] [Bug 1845541] [NEW] OS becomes unresponsive when power is plugged in and battery is low

2019-09-26 Thread Jonathan Warner
Public bug reported:

Occasionally when I plug in my laptop at low (close to shut-down levels,
<10%) battery, the OS becomes unresponsive. The GUI doesn't work,
Ctrl+Alt+T doesn't work, nothing works. This makes it difficult to
collect information about the problem, since I basically have to
shutdown with the power button and reboot. It is probably related to
whichever processes monitor the battery and put the computer to sleep
when the battery gets low. Almost like it wants to put the computer to
sleep since the battery is at critical levels, but it just stalls since
the power is plugged in.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xserver-xorg-core 2:1.19.6-1ubuntu4.3
ProcVersionSignature: Ubuntu 4.15.0-62.69-generic 4.15.18
Uname: Linux 4.15.0-62-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.7
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Thu Sep 26 11:41:31 2019
DistUpgraded: Fresh install
DistroCodename: bionic
DistroVariant: ubuntu
DkmsStatus:
 virtualbox, 5.2.32, 4.15.0-58-generic, x86_64: installed
 virtualbox, 5.2.32, 4.15.0-62-generic, x86_64: installed
ExecutablePath: /usr/lib/xorg/Xorg
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 Intel Corporation Skylake GT2 [HD Graphics 520] [8086:1916] (rev 07) (prog-if 
00 [VGA controller])
   Subsystem: Hewlett-Packard Company Skylake GT2 [HD Graphics 520] [103c:81cb]
InstallationDate: Installed on 2019-01-28 (241 days ago)
InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725)
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 003: ID 8087:0a2a Intel Corp. 
 Bus 001 Device 002: ID 1bcf:2c83 Sunplus Innovation Technology Inc. 
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: HP HP ENVY Notebook
MonitorsUser.xml:
 
 
ProcEnviron:
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/usr/bin/fish
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-62-generic 
root=UUID=fcfb9abf-573d-4d5e-bc54-c8a65f678302 ro quiet splash vt.handoff=1
SourcePackage: xorg-server
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 08/17/2016
dmi.bios.vendor: Insyde
dmi.bios.version: F.22
dmi.board.asset.tag: Type2 - Board Asset Tag
dmi.board.name: 81CB
dmi.board.vendor: HP
dmi.board.version: KBC Version 60.26
dmi.chassis.asset.tag: Chassis Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: HP
dmi.chassis.version: Chassis Version
dmi.modalias: 
dmi:bvnInsyde:bvrF.22:bd08/17/2016:svnHP:pnHPENVYNotebook:pvrType1ProductConfigId:rvnHP:rn81CB:rvrKBCVersion60.26:cvnHP:ct10:cvrChassisVersion:
dmi.product.family: 103C_5335KV G=N L=CON B=HP S=ENV
dmi.product.name: HP ENVY Notebook
dmi.product.version: Type1ProductConfigId
dmi.sys.vendor: HP
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.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.3
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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


** Tags: amd64 apport-bug bionic ubuntu

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

Title:
  OS becomes unresponsive when power is plugged in and battery is low

Status in xorg-server package in Ubuntu:
  New

Bug description:
  Occasionally when I plug in my laptop at low (close to shut-down
  levels, <10%) battery, the OS becomes unresponsive. The GUI doesn't
  work, Ctrl+Alt+T doesn't work, nothing works. This makes it difficult
  to collect information about the problem, since I basically have to
  shutdown with the power button and reboot. It is probably related to
  whichever processes monitor the battery and put the computer to sleep
  when the battery gets low. Almost like it wants to put the computer to
  sleep since the battery is at critical levels, but it just stalls
  since the power is plugged in.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xserver-xorg-core 2:1.19.6-1ubuntu4.3
  ProcVersionSignature: Ubuntu 4.15.0-62.69-generic 4.15.18
  Uname: Linux 4.15.0-62-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.7
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  

[Desktop-packages] [Bug 1845385] Re: Touchpad click-drag action broken after close-lid suspend, Lenovo X1C5, Bionic

2019-09-26 Thread David Chalmers
** Description changed:

  Steps to reproduce:
- - observe touchpad click-drag working normally (i.e. can click touchpad and 
drag an icon, or select text in any direction)
+ - observe touchpad click-drag* working normally (i.e. can click touchpad and 
drag an icon, or select text in any direction)
  - close lid to suspend (need to wait some time until red Thinkpad light above 
'i' on lid starts to flash
  - open lid to resume
  - observe touchpad click-drag NOT working. Can click but not drag, or can 
only drag very short distance/awkwardly
+ 
+ *depressing the touchpad surface until it clicks, with one finger (usually 
index) and with the touchpad clicked down, dragging on the touchpad with 
another finger (middle) to move the item selected via the click.
+ typical uses to test: click a window titlebar and move it using drag
+ click a desktop icon and move it using drag
+ click to being select in text area of an app and drag to extend selection
+ 
  
  Also note:
  - sudo moidprobe -r psmouse
  - sudo modprobe psmouse
  restores expected functionaly
  
  Similar symptoms to several related bugs (see below) but reporting 
separately, since:
  - issue still present on later hardware and software than previously reported
  - issue still present despite full firmware updates
  - slightly different experience with workaround (i.e modprobe -r psmouse / 
modprobe psmouse does restore functionality
  
  Related bugs:
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1791427
  https://bugs.launchpad.net/ubuntu/+source/libinput/+bug/1727130
  https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1728778
  
  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xserver-xorg-input-libinput 0.27.1-1
  ProcVersionSignature: Ubuntu 4.15.0-64.73-generic 4.15.18
  Uname: Linux 4.15.0-64-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.9-0ubuntu7.7
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Sep 25 21:29:07 2019
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  InstallationDate: Installed on 2018-11-22 (306 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 138a:0097 Validity Sensors, Inc.
   Bus 001 Device 003: ID 13d3:5682 IMC Networks
   Bus 001 Device 002: ID 8087:0a2b Intel Corp.
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 20HRCTO1WW
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-64-generic 
root=/dev/mapper/system-root ro quiet splash vt.handoff=1
  SourcePackage: xserver-xorg-input-libinput
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/16/2019
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N1MET54W (1.39 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20HRCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40709 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN1MET54W(1.39):bd04/16/2019:svnLENOVO:pn20HRCTO1WW:pvrThinkPadX1Carbon5th:rvnLENOVO:rn20HRCTO1WW:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad X1 Carbon 5th
  dmi.product.name: 20HRCTO1WW
  dmi.product.version: ThinkPad X1 Carbon 5th
  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.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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

Title:
  Touchpad click-drag action broken after close-lid suspend, Lenovo
  X1C5, Bionic

Status in xserver-xorg-input-libinput package in Ubuntu:
  New

Bug description:
  Steps to reproduce:
  - observe touchpad click-drag* working normally (i.e. can click touchpad and 
drag an icon, or select text in any direction)
  - close lid to suspend (need to wait some time until red Thinkpad light above 
'i' on lid starts to flash
  - open lid to resume
  - observe touchpad click-drag NOT working. Can click but not drag, or can 
only drag very short distance/awkwardly

  *depressing the touchpad surface until it 

[Desktop-packages] [Bug 1845532] Re: power icon does not indicate charging if booted without power connected

2019-09-26 Thread Heather Ellsworth
The following is the output of `journalctl | grep -i power` that covers
the duration between the reboot command and login times.

** Attachment added: "journal-power-keyword_no-power-connected-on-boot.out"
   
https://bugs.launchpad.net/ubuntu/+source/upower/+bug/1845532/+attachment/5291524/+files/journal-power-keyword_no-power-connected-on-boot.out

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

Title:
  power icon does not indicate charging if booted without power
  connected

Status in upower package in Ubuntu:
  New

Bug description:
  Hardware: Lenovo T590
  OS: 19.10

  When the power is not connected when the laptop boots, and then
  connected, the power icon in the top bar does not change to indicate
  that the laptop is now charging.

  $ upower -d
  Device: /org/freedesktop/UPower/devices/line_power_AC 

 
native-path:  AC

 
power supply: yes   

 
updated:  Thu 26 Sep 2019 08:53:40 AM MDT (2107 seconds ago)
has history:  no
has statistics:   no
line-power
  warning-level:   none
  online:  no
  icon-name:  'ac-adapter-symbolic'

  Device: /org/freedesktop/UPower/devices/battery_BAT0 
native-path:  BAT0
vendor:   SMP
model:02DL012
serial:   1417
power supply: yes
updated:  Thu 26 Sep 2019 09:28:33 AM MDT (14 seconds ago)
has history:  yes
has statistics:   yes
battery
  present: yes
  rechargeable:yes
  state:   discharging
  warning-level:   none
  energy:  55.53 Wh
  energy-empty:0 Wh
  energy-full: 57.21 Wh
  energy-full-design:  57.02 Wh
  energy-rate: 0.319173 W
  voltage: 12.932 V
  time to empty:   7.2 days
  percentage:  97%
  capacity:100%
  technology:  lithium-polymer
  icon-name:  'battery-full-symbolic'

  Device: /org/freedesktop/UPower/devices/DisplayDevice
power supply: yes
updated:  Thu 26 Sep 2019 09:22:33 AM MDT (374 seconds ago)
has history:  no
has statistics:   no
battery
  present: yes
  state:   discharging
  warning-level:   none
  energy:  55.53 Wh
  energy-full: 57.21 Wh
  energy-rate: 0.319173 W
  time to empty:   7.2 days
  percentage:  97%
  icon-name:  'battery-full-symbolic'

  Daemon:
daemon-version:  0.99.11
on-battery:  yes
lid-is-closed:   no
lid-is-present:  yes
critical-action: PowerOff

  $ cat /sys/class/power_supply/BAT0/status 
  Unknown

  However, if the laptop is booted with the power connected, then the
  battery icon in the top bar shows that it's charging and at 100%. If I
  unplug the power, it correctly shows that it is no longer charging but
  it goes back to saying I'm at 97% (the last reported state when booted
  without power).

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: upower 0.99.11-1
  ProcVersionSignature: Ubuntu 5.3.0-10.11-generic 5.3.0-rc8
  Uname: Linux 5.3.0-10-generic x86_64
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Sep 26 10:24:38 2019
  InstallationDate: Installed on 2019-09-13 (12 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: upower
  UpgradeStatus: Upgraded to eoan on 2019-09-19 (7 days ago)

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

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


[Desktop-packages] [Bug 1845532] Re: power icon does not indicate charging if booted without power connected

2019-09-26 Thread Heather Ellsworth
The only difference in journalctl between when the system boots with
power and without is that when the system boots without power, I see two
journalctl messages:

Sep 26 10:53:27 fenrir dbus-daemon[793]: [system] Activating via systemd: 
service name='org.freedesktop.UPower' unit='upower.service' requested by 
':1.37' (uid=123 pid=1052 comm="/usr/bin/gnome-shell " label="unconfined")
Sep 26 10:54:31 fenrir dbus-daemon[844]: [system] Activating via systemd: 
service name='org.freedesktop.UPower' unit='upower.service' requested by 
':1.38' (uid=123 pid= comm="/usr/bin/gnome-shell " label="unconfined")

When the system boots with power, I see only one similar journalctl message:
Sep 26 11:22:26 fenrir dbus-daemon[835]: [system] Activating via systemd: 
service name='org.freedesktop.UPower' unit='upower.service' requested by 
':1.38' (uid=123 pid=1090 comm="/usr/bin/gnome-shell " label="unconfined")

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

Title:
  power icon does not indicate charging if booted without power
  connected

Status in upower package in Ubuntu:
  New

Bug description:
  Hardware: Lenovo T590
  OS: 19.10

  When the power is not connected when the laptop boots, and then
  connected, the power icon in the top bar does not change to indicate
  that the laptop is now charging.

  $ upower -d
  Device: /org/freedesktop/UPower/devices/line_power_AC 

 
native-path:  AC

 
power supply: yes   

 
updated:  Thu 26 Sep 2019 08:53:40 AM MDT (2107 seconds ago)
has history:  no
has statistics:   no
line-power
  warning-level:   none
  online:  no
  icon-name:  'ac-adapter-symbolic'

  Device: /org/freedesktop/UPower/devices/battery_BAT0 
native-path:  BAT0
vendor:   SMP
model:02DL012
serial:   1417
power supply: yes
updated:  Thu 26 Sep 2019 09:28:33 AM MDT (14 seconds ago)
has history:  yes
has statistics:   yes
battery
  present: yes
  rechargeable:yes
  state:   discharging
  warning-level:   none
  energy:  55.53 Wh
  energy-empty:0 Wh
  energy-full: 57.21 Wh
  energy-full-design:  57.02 Wh
  energy-rate: 0.319173 W
  voltage: 12.932 V
  time to empty:   7.2 days
  percentage:  97%
  capacity:100%
  technology:  lithium-polymer
  icon-name:  'battery-full-symbolic'

  Device: /org/freedesktop/UPower/devices/DisplayDevice
power supply: yes
updated:  Thu 26 Sep 2019 09:22:33 AM MDT (374 seconds ago)
has history:  no
has statistics:   no
battery
  present: yes
  state:   discharging
  warning-level:   none
  energy:  55.53 Wh
  energy-full: 57.21 Wh
  energy-rate: 0.319173 W
  time to empty:   7.2 days
  percentage:  97%
  icon-name:  'battery-full-symbolic'

  Daemon:
daemon-version:  0.99.11
on-battery:  yes
lid-is-closed:   no
lid-is-present:  yes
critical-action: PowerOff

  $ cat /sys/class/power_supply/BAT0/status 
  Unknown

  However, if the laptop is booted with the power connected, then the
  battery icon in the top bar shows that it's charging and at 100%. If I
  unplug the power, it correctly shows that it is no longer charging but
  it goes back to saying I'm at 97% (the last reported state when booted
  without power).

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: upower 0.99.11-1
  ProcVersionSignature: Ubuntu 5.3.0-10.11-generic 5.3.0-rc8
  Uname: Linux 5.3.0-10-generic x86_64
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Sep 26 10:24:38 2019
  InstallationDate: Installed on 2019-09-13 (12 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: upower
  UpgradeStatus: Upgraded to eoan on 2019-09-19 (7 days ago)

To manage notifications about 

[Desktop-packages] [Bug 1845532] Re: power icon does not indicate charging if booted without power connected

2019-09-26 Thread Heather Ellsworth
The following is the output of `journalctl | grep -i power` that covers
the duration between the reboot command and login times.

** Attachment added: "journal-power-keyword_with-power-connected-on-boot.out"
   
https://bugs.launchpad.net/ubuntu/+source/upower/+bug/1845532/+attachment/5291525/+files/journal-power-keyword_with-power-connected-on-boot.out

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

Title:
  power icon does not indicate charging if booted without power
  connected

Status in upower package in Ubuntu:
  New

Bug description:
  Hardware: Lenovo T590
  OS: 19.10

  When the power is not connected when the laptop boots, and then
  connected, the power icon in the top bar does not change to indicate
  that the laptop is now charging.

  $ upower -d
  Device: /org/freedesktop/UPower/devices/line_power_AC 

 
native-path:  AC

 
power supply: yes   

 
updated:  Thu 26 Sep 2019 08:53:40 AM MDT (2107 seconds ago)
has history:  no
has statistics:   no
line-power
  warning-level:   none
  online:  no
  icon-name:  'ac-adapter-symbolic'

  Device: /org/freedesktop/UPower/devices/battery_BAT0 
native-path:  BAT0
vendor:   SMP
model:02DL012
serial:   1417
power supply: yes
updated:  Thu 26 Sep 2019 09:28:33 AM MDT (14 seconds ago)
has history:  yes
has statistics:   yes
battery
  present: yes
  rechargeable:yes
  state:   discharging
  warning-level:   none
  energy:  55.53 Wh
  energy-empty:0 Wh
  energy-full: 57.21 Wh
  energy-full-design:  57.02 Wh
  energy-rate: 0.319173 W
  voltage: 12.932 V
  time to empty:   7.2 days
  percentage:  97%
  capacity:100%
  technology:  lithium-polymer
  icon-name:  'battery-full-symbolic'

  Device: /org/freedesktop/UPower/devices/DisplayDevice
power supply: yes
updated:  Thu 26 Sep 2019 09:22:33 AM MDT (374 seconds ago)
has history:  no
has statistics:   no
battery
  present: yes
  state:   discharging
  warning-level:   none
  energy:  55.53 Wh
  energy-full: 57.21 Wh
  energy-rate: 0.319173 W
  time to empty:   7.2 days
  percentage:  97%
  icon-name:  'battery-full-symbolic'

  Daemon:
daemon-version:  0.99.11
on-battery:  yes
lid-is-closed:   no
lid-is-present:  yes
critical-action: PowerOff

  $ cat /sys/class/power_supply/BAT0/status 
  Unknown

  However, if the laptop is booted with the power connected, then the
  battery icon in the top bar shows that it's charging and at 100%. If I
  unplug the power, it correctly shows that it is no longer charging but
  it goes back to saying I'm at 97% (the last reported state when booted
  without power).

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: upower 0.99.11-1
  ProcVersionSignature: Ubuntu 5.3.0-10.11-generic 5.3.0-rc8
  Uname: Linux 5.3.0-10-generic x86_64
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Sep 26 10:24:38 2019
  InstallationDate: Installed on 2019-09-13 (12 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: upower
  UpgradeStatus: Upgraded to eoan on 2019-09-19 (7 days ago)

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

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


[Desktop-packages] [Bug 1845532] Re: power icon does not indicate charging if booted without power connected

2019-09-26 Thread Heather Ellsworth
This issue is completely reproducible for me. Digging into the
journalctl logs around when the system is rebooting without power
plugged in, here are some lines that stand out and might be useful:

Note that the system was sent to reboot at 10:53:00

...
Sep 26 10:53:37 fenrir systemd[2088]: Started GNOME Power management handling.
Sep 26 10:53:37 fenrir systemd[2088]: Reached target GNOME Power management 
handling.
...
Sep 26 10:54:28 fenrir kernel: ACPI: Power Resource [PUBS] (on)
Sep 26 10:54:28 fenrir kernel: ACPI: Power Resource [USBC] (on)
Sep 26 10:54:28 fenrir kernel: ACPI: Power Resource [PXP] (on)
Sep 26 10:54:28 fenrir kernel: ACPI: Power Resource [PXP] (off)
Sep 26 10:54:28 fenrir kernel: ACPI: Power Resource [V0PR] (on)
Sep 26 10:54:28 fenrir kernel: ACPI: Power Resource [V1PR] (on)
Sep 26 10:54:28 fenrir kernel: ACPI: Power Resource [V2PR] (on)
Sep 26 10:54:28 fenrir kernel: ACPI: Power Resource [WRST] (on)
Sep 26 10:54:28 fenrir kernel: ACPI: Power Resource [PIN] (off)
Sep 26 10:54:28 fenrir kernel: ACPI: Power Resource [PINP] (off)
...
Sep 26 10:54:28 fenrir kernel: usb: port power management may be unreliable
...
Sep 26 10:54:29 fenrir dbus-daemon[844]: dbus[844]: Unknown group "power" in 
message bus configuration file
...
Sep 26 10:54:29 fenrir boltd[842]: journal: opened for 'c003-0082'; size: 0 
bytes
Sep 26 10:54:29 fenrir boltd[842]: [c003-0082-domain?] 
domain: registered (bootacl: 16/16)
Sep 26 10:54:29 fenrir boltd[842]: store: loading devices
Sep 26 10:54:29 fenrir boltd[842]: power: state located at: /run/boltd/power
Sep 26 10:54:29 fenrir systemd[1]: Starting Hold until boot process finishes 
up...
...
Sep 26 10:54:31 fenrir dbus-daemon[844]: [system] Activating via systemd: 
service name='org.freedesktop.UPower' unit='upower.service' requested by 
':1.38' (uid=123 pid= comm="/usr/bin/gnome-shell " label="unconfined")
Sep 26 10:54:31 fenrir systemd[1]: Starting Daemon for power management...
...
Sep 26 10:54:31 fenrir gnome-shell[]: Getting invalid resource scale 
property
Sep 26 10:54:31 fenrir gnome-shell[]: ibus_bus_hello: assertion 
'ibus_bus_is_connected (bus)' failed
Sep 26 10:54:31 fenrir gnome-shell[]: Error while sending AddMatch() 
message: The connection is closed
Sep 26 10:54:31 fenrir gnome-shell[]: ibus_bus_call_async: assertion 
'ibus_bus_is_connected (bus)' failed
Sep 26 10:54:31 fenrir gnome-shell[]: ibus_bus_call_async: assertion 
'ibus_bus_is_connected (bus)' failed
Sep 26 10:54:31 fenrir gnome-shell[]: JS ERROR: Gio.IOErrorEnum: The 
connection is closed
  
_setContext@resource:///org/gnome/shell/misc/inputMethod.js:63:25
Sep 26 10:54:31 fenrir upowerd[1760]: energy_full (57.18) is greater than 
energy_full_design (57.02)
Sep 26 10:54:31 fenrir gnome-shell[]: Error looking up permission: 
GDBus.Error:org.freedesktop.portal.Error.NotFound: No entry for geolocation
Sep 26 10:54:31 fenrir systemd[1062]: Started GNOME XSettings.
Sep 26 10:54:31 fenrir dbus-daemon[844]: [system] Successfully activated 
service 'org.freedesktop.UPower'
Sep 26 10:54:31 fenrir systemd[1]: Started Daemon for power management.
...
Sep 26 10:54:36 fenrir gnome-session-binary[2271]: DEBUG(+): GsmManager: read 
/etc/xdg/autostart/org.gnome.SettingsDaemon.Power.desktop
Sep 26 10:54:36 fenrir gnome-session-binary[2271]: DEBUG(+): GsmManager: not 
adding app: app-id 'org.gnome.SettingsDaemon.Power.desktop' already exists
...
Sep 26 10:54:36 fenrir gnome-session-binary[2271]: DEBUG(+): GsmManager:
ID: /org/gnome/SessionManager/App8
app-id:org.gnome.SettingsDaemon.Power.desktopis-disabled:1
is-conditionally-disabled:0is-delayed:0
...
Sep 26 10:54:36 fenrir systemd[1958]: Started GNOME Power management handling.
Sep 26 10:54:36 fenrir systemd[1958]: Reached target GNOME Power management 
handling.

A full journalctl log is available but it is 46Mb so I didn't attach it
here.

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

Title:
  power icon does not indicate charging if booted without power
  connected

Status in upower package in Ubuntu:
  New

Bug description:
  Hardware: Lenovo T590
  OS: 19.10

  When the power is not connected when the laptop boots, and then
  connected, the power icon in the top bar does not change to indicate
  that the laptop is now charging.

  $ upower -d
  Device: /org/freedesktop/UPower/devices/line_power_AC 

 
native-path:  AC

 
power supply:  

[Desktop-packages] [Bug 1845332] Re: Compose key does not create strings

2019-09-26 Thread Oryganum
Thank you so much for the quick response!

I switched "Keyboard input method system" to "XIM" as you suggested and
now everything works fine.

However, I have a few questions about it.

>> That wiki page you referred  to was last edited 11 years ago and is
obsolete to a large extent.

Is it possible to contact someone to ask to update this page?

>> Today, on an Ubuntu system, it's normally GTK (not IBus, so I'm
closing this bug report) which deals with rules in the ~/.XCompose file.

On my Ubuntu 18.04 "Keyboard input method system" gives me options IBus,
XIM and none.

Is there any known advantage of choosing IBus there? 
(I am trying to understand why XIM is not a default.)

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

Title:
  Compose key does not create strings

Status in ibus package in Ubuntu:
  Invalid

Bug description:
  According to manual https://wiki.ubuntu.com/ComposeKey it is possible to 
define sequences to type characters and strings with Compose key.
  In Ubuntu 18.04 sequences work for characters but not for strings, line like 
this:
 : "by the way" # Compose b t w
  seems to be ignored.

  $ apt-cache policy ibus
  ibus:
Installed: 1.5.17-3ubuntu5.2
Candidate: 1.5.17-3ubuntu5.2
Version table:
   *** 1.5.17-3ubuntu5.2 500
  500 http://mirror.isoc.org.il/pub/ubuntu bionic-updates/main amd64 
Packages
  500 http://mirror.isoc.org.il/pub/ubuntu bionic-security/main amd64 
Packages
  100 /var/lib/dpkg/status
   1.5.17-3ubuntu4 500
  500 http://mirror.isoc.org.il/pub/ubuntu bionic/main amd64 Packages
  500 http://cz.archive.ubuntu.com/ubuntu bionic/main amd64 Packages

  This problem first reported at Dec 11 '18 and also exists in Kubuntu
  18.04 (see https://askubuntu.com/questions/1099947/how-to-use-
  xcompose-to-produce-snippets).

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

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


[Desktop-packages] [Bug 494067]

2019-09-26 Thread Psychonaut
One of the patches introduced as a result of this bug (namely, the one
that forces setting of the browser.preferences.instantApply to "false")
appears to have broken at least one Thunderbird extension, CardBook.  I
have opened an issue for this: Bug 1151186.  It would be great if the
folks responsible for the current issue could have a look at the
CardBook one.

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

Title:
  Provide better Firefox KDE integration

Status in Mozilla Firefox:
  Confirmed
Status in XULRunner:
  Confirmed
Status in firefox package in Ubuntu:
  Fix Released
Status in xulrunner-1.9.1 package in Ubuntu:
  Invalid
Status in Baltix:
  New
Status in openSUSE:
  Fix Released

Bug description:
  Binary package hint: firefox-3.5

  The KDE integration of Firefox is still suboptimal in Ubuntu.

  openSUSE developed a set of patches that improves the situation:
  http://en.opensuse.org/KDE/FirefoxIntegration
  http://gitorious.org/firefox-kde-opensuse/

  These should be integrated into the firefox-3.5 / xulrunner-1.9.1 packages and
  a new package for the helper application kmozillahelper is necessary.

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

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


[Desktop-packages] [Bug 1845532] [NEW] power icon does not indicate charging if booted without power connected

2019-09-26 Thread Heather Ellsworth
Public bug reported:

Hardware: Lenovo T590
OS: 19.10

When the power is not connected when the laptop boots, and then
connected, the power icon in the top bar does not change to indicate
that the laptop is now charging.

$ upower -d
Device: /org/freedesktop/UPower/devices/line_power_AC   

   
  native-path:  AC  

   
  power supply: yes 

   
  updated:  Thu 26 Sep 2019 08:53:40 AM MDT (2107 seconds ago)
  has history:  no
  has statistics:   no
  line-power
warning-level:   none
online:  no
icon-name:  'ac-adapter-symbolic'

Device: /org/freedesktop/UPower/devices/battery_BAT0 
  native-path:  BAT0
  vendor:   SMP
  model:02DL012
  serial:   1417
  power supply: yes
  updated:  Thu 26 Sep 2019 09:28:33 AM MDT (14 seconds ago)
  has history:  yes
  has statistics:   yes
  battery
present: yes
rechargeable:yes
state:   discharging
warning-level:   none
energy:  55.53 Wh
energy-empty:0 Wh
energy-full: 57.21 Wh
energy-full-design:  57.02 Wh
energy-rate: 0.319173 W
voltage: 12.932 V
time to empty:   7.2 days
percentage:  97%
capacity:100%
technology:  lithium-polymer
icon-name:  'battery-full-symbolic'

Device: /org/freedesktop/UPower/devices/DisplayDevice
  power supply: yes
  updated:  Thu 26 Sep 2019 09:22:33 AM MDT (374 seconds ago)
  has history:  no
  has statistics:   no
  battery
present: yes
state:   discharging
warning-level:   none
energy:  55.53 Wh
energy-full: 57.21 Wh
energy-rate: 0.319173 W
time to empty:   7.2 days
percentage:  97%
icon-name:  'battery-full-symbolic'

Daemon:
  daemon-version:  0.99.11
  on-battery:  yes
  lid-is-closed:   no
  lid-is-present:  yes
  critical-action: PowerOff

$ cat /sys/class/power_supply/BAT0/status 
Unknown

However, if the laptop is booted with the power connected, then the
battery icon in the top bar shows that it's charging and at 100%. If I
unplug the power, it correctly shows that it is no longer charging but
it goes back to saying I'm at 97% (the last reported state when booted
without power).

ProblemType: Bug
DistroRelease: Ubuntu 19.10
Package: upower 0.99.11-1
ProcVersionSignature: Ubuntu 5.3.0-10.11-generic 5.3.0-rc8
Uname: Linux 5.3.0-10-generic x86_64
ApportVersion: 2.20.11-0ubuntu7
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Thu Sep 26 10:24:38 2019
InstallationDate: Installed on 2019-09-13 (12 days ago)
InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: upower
UpgradeStatus: Upgraded to eoan on 2019-09-19 (7 days ago)

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


** Tags: amd64 apport-bug eoan

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

Title:
  power icon does not indicate charging if booted without power
  connected

Status in upower package in Ubuntu:
  New

Bug description:
  Hardware: Lenovo T590
  OS: 19.10

  When the power is not connected when the laptop boots, and then
  connected, the power icon in the top bar does not change to indicate
  that the laptop is now charging.

  $ upower -d
  Device: /org/freedesktop/UPower/devices/line_power_AC 

 
native-path:  AC

 
power supply: yes   

 
updated:  Thu 26 Sep 2019 08:53:40 AM MDT (2107 seconds ago)
has history:  no
has 

[Desktop-packages] [Bug 1845286] Re: pdftoraster crashed with SIGSEGV in convert8to16()

2019-09-26 Thread Till Kamppeter
When one uses gstoraster instead of pdftoraster (is used automatically
when Ghostscript is installed) then there does not occur any crash.

** Changed in: cups-filters (Ubuntu)
   Status: Incomplete => Confirmed

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

Title:
  pdftoraster crashed with SIGSEGV in convert8to16()

Status in cups-filters package in Ubuntu:
  Confirmed

Bug description:
  Tried to print a pdf via an auto configured cups printer - pdftoraster
  crashed nothing was printed.

  ProblemType: Crash
  DistroRelease: Ubuntu 19.10
  Package: cups-filters-core-drivers 1.25.6-0ubuntu1
  ProcVersionSignature: Ubuntu 5.3.0-10.11-generic 5.3.0-rc8
  Uname: Linux 5.3.0-10-generic x86_64
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  Date: Wed Sep 25 06:49:10 2019
  ExecutablePath: /usr/lib/cups/filter/pdftoraster
  InstallationDate: Installed on 2018-09-06 (383 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  Lpstat:
   device for Brother_HL_L2300D_series_MacBook_de_Yasser: ///dev/null
   device for cespu_geral_MacBook_Air_de_Jo_o: ///dev/null
   device for Deskjet_3050A_J611_series_MacBook_Air: ///dev/null
   device for HP-Officejet-Pro-8620: 
dnssd://HP%20Officejet%20Pro%208620%20%5B794B2D%5D._ipp._tcp.local/?uuid=1c852a4d-b800-1f08-abcd-3863bb794b2d
   device for HP_Officejet_Pro_8620_794B2D_: 
implicitclass://HP_Officejet_Pro_8620_794B2D_/
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 04ca:7054 Lite-On Technology Corp. HP HD Camera
   Bus 001 Device 002: ID 8087:0a2b Intel Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: HP HP EliteBook 840 G3
  Papersize: a4
  PpdFiles:
   HP-Officejet-Pro-8620: HP Officejet Pro 8620, driverless, cups-filters 1.25.4
   HP_Officejet_Pro_8620_794B2D_: HP Officejet Pro 8620, driverless, 
cups-filters 1.25.6
  ProcCmdline: implicitclass://HP_Officejet_Pro_8620_794B2D_/ 109 z003te9p 
Lauf\ gegen\ Krebs\ 2019.pdf 1 print-content-optimize=auto\ 
print-rendering-intent=auto\ ColorModel=DeviceGray\ Duplex=DuplexNoTumble\ 
MediaType=Stationery\ number-up=1\ PageSize=A4\ print-scaling=auto\ noCollate\ 
cupsPrintQuality=4\ job-uuid=urn:uuid:1166fa02-95cc-3560-7cd2-f256658917ad\ 
cups-browsed\ job-originating-host-name=localhost\ date-time-at-creation=\ 
date-time-at-processing=\ time-at-creation=1569386949\ 
time-at-processing=1569386949\ print-quality=4\ output-format=apple-raster\ 
Resolution=300dpi\ media-class=pwg\ page-logging=on
  ProcEnviron:
   PATH=(custom, no user)
   LANG=en_US.UTF-8
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-10-generic 
root=UUID=a8dfd19d-7ac8-43b7-bb4d-41c72407226f ro quiet splash vt.handoff=7
  SegvAnalysis:
   Segfault happened at: 0x55e344d74b9b:movzbl (%rdx),%r9d
   PC (0x55e344d74b9b) ok
   source "(%rdx)" (0x55e346c168af) not located in a known VMA region (needed 
readable region)!
   destination "%r9d" ok
  SegvReason: reading unknown VMA
  Signal: 11
  SourcePackage: cups-filters
  StacktraceTop:
   ?? ()
   ?? ()
   ?? ()
   __libc_start_main (main=0x55e344d71b90, argc=6, argv=0x7ffcb779bdc8, 
init=, fini=, rtld_fini=, 
stack_end=0x7ffcb779bdb8) at ../csu/libc-start.c:308
   ?? ()
  Title: pdftoraster crashed with SIGSEGV in __libc_start_main()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  dmi.bios.date: 11/01/2016
  dmi.bios.vendor: HP
  dmi.bios.version: N75 Ver. 01.13
  dmi.board.name: 8079
  dmi.board.vendor: HP
  dmi.board.version: KBC Version 85.74
  dmi.chassis.asset.tag: 5CG7060XN6
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.modalias: 
dmi:bvnHP:bvrN75Ver.01.13:bd11/01/2016:svnHP:pnHPEliteBook840G3:pvr:rvnHP:rn8079:rvrKBCVersion85.74:cvnHP:ct10:cvr:
  dmi.product.family: 103C_5336AN G=N L=BUS B=HP S=ELI
  dmi.product.name: HP EliteBook 840 G3
  dmi.product.sku: W0Q03EC#ABD
  dmi.sys.vendor: HP
  separator:

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

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


[Desktop-packages] [Bug 1845286] Re: pdftoraster crashed with SIGSEGV in convert8to16()

2019-09-26 Thread Till Kamppeter
I succeeded to reproduce the crash on the command line. For the tests
shown here I am in the source directory of the current cups-filters,
having run "autogen.sh", "./configure", and "make" already.

After downloading the attached PPD file (comment #11) and the attached
PDF file (comment #7) I have passed the input PDF file through pdftopdf
first, with the following command line:

cat Lauf\ gegen\ Krebs\ 2019.pdf | FINAL_CONTENT_TYPE=application/pdf
PPD=hp_officejet_pro_8620_794b2d_.ppd
DEVICE_URI=implicitclass://hp_officejet_pro_8620_794b2d_/
PRINTER=hp_officejet_pro_8620_794b2d_ ./pdftopdf 1 1 1 1 "print-content-
optimize=auto print-rendering-intent=auto ColorModel=DeviceGray
Duplex=DuplexNoTumble MediaType=Stationery number-up=1 PageSize=A4
print-scaling=auto noCollate cupsPrintQuality=4 job-uuid=urn:uuid
:239f990b-2e91-324e-43dc-529fedd50b88 cups-browsed job-originating-host-
name=localhost date-time-at-creation= date-time-at-processing= time-at-
creation=1569426096 time-at-processing=1569426096 print-quality=4
output-format=apple-raster Resolution=300dpi media-class=pwg page-
logging=on" > out.pdf

I am attaching out.pdf. Note that the duplex setting makes pdftopdf add
a blank page to the beginning of the file.

Now I allow core files to be written with

ulimit -c unlimited

and feed out.pdf through pdftoraster using the following command line:

cat out.pdf | FINAL_CONTENT_TYPE=application/pdf
PPD=hp_officejet_pro_8620_794b2d_.ppd
DEVICE_URI=implicitclass://hp_officejet_pro_8620_794b2d_/
PRINTER=hp_officejet_pro_8620_794b2d_ ./pdftoraster 1 1 1 1 "print-
content-optimize=auto print-rendering-intent=auto ColorModel=DeviceGray
Duplex=DuplexNoTumble MediaType=Stationery number-up=1 PageSize=A4
print-scaling=auto noCollate cupsPrintQuality=4 job-uuid=urn:uuid
:239f990b-2e91-324e-43dc-529fedd50b88 cups-browsed job-originating-host-
name=localhost date-time-at-creation= date-time-at-processing= time-at-
creation=1569426096 time-at-processing=1569426096 print-quality=4
output-format=apple-raster Resolution=300dpi media-class=pwg page-
logging=on" > out.ras

I open the resulting core file with gdb:

gdb -c core .libs/pdftoraster

Running the "bt" command within gdb gives the following backtrace:

#0  0x5585f7910b9b in convert8to16 (
src=0x7f7bb17aba85 , 
dst=0x7ffc890ea660 "", x=, y=)
at filter/pdftoraster.cxx:1012
#1  0x5585f7910eb9 in convertLineChunkedSwap (
src=src@entry=0x7f7bb17aa7c1 , dst=dst@entry=0x5585f955a520 '\377' ..., 
row=row@entry=6859, plane=plane@entry=0, pixels=4805, size=)
at filter/pdftoraster.cxx:1170
#2  0x5585f790f757 in writePageImage (pageNo=2, doc=0x5585f954df10, 
raster=0x5585f954dff0) at filter/pdftoraster.cxx:1626
#3  outPage (raster=, pageNo=, 
doc=) at filter/pdftoraster.cxx:1884
#4  main (argc=, argv=)
at filter/pdftoraster.cxx:2121


** Attachment added: "out.pdf"
   
https://bugs.launchpad.net/ubuntu/+source/cups-filters/+bug/1845286/+attachment/5291517/+files/out.pdf

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

Title:
  pdftoraster crashed with SIGSEGV in convert8to16()

Status in cups-filters package in Ubuntu:
  Confirmed

Bug description:
  Tried to print a pdf via an auto configured cups printer - pdftoraster
  crashed nothing was printed.

  ProblemType: Crash
  DistroRelease: Ubuntu 19.10
  Package: cups-filters-core-drivers 1.25.6-0ubuntu1
  ProcVersionSignature: Ubuntu 5.3.0-10.11-generic 5.3.0-rc8
  Uname: Linux 5.3.0-10-generic x86_64
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  Date: Wed Sep 25 06:49:10 2019
  ExecutablePath: /usr/lib/cups/filter/pdftoraster
  InstallationDate: Installed on 2018-09-06 (383 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  Lpstat:
   device for Brother_HL_L2300D_series_MacBook_de_Yasser: ///dev/null
   device for cespu_geral_MacBook_Air_de_Jo_o: ///dev/null
   device for Deskjet_3050A_J611_series_MacBook_Air: ///dev/null
   device for HP-Officejet-Pro-8620: 
dnssd://HP%20Officejet%20Pro%208620%20%5B794B2D%5D._ipp._tcp.local/?uuid=1c852a4d-b800-1f08-abcd-3863bb794b2d
   device for HP_Officejet_Pro_8620_794B2D_: 
implicitclass://HP_Officejet_Pro_8620_794B2D_/
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 04ca:7054 Lite-On Technology Corp. HP HD Camera
   Bus 001 Device 002: ID 8087:0a2b Intel Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: HP HP EliteBook 840 G3
  Papersize: a4
  PpdFiles:
   HP-Officejet-Pro-8620: HP Officejet Pro 8620, driverless, cups-filters 1.25.4
   HP_Officejet_Pro_8620_794B2D_: HP Officejet Pro 8620, driverless, 
cups-filters 1.25.6
  ProcCmdline: implicitclass://HP_Officejet_Pro_8620_794B2D_/ 109 z003te9p 
Lauf\ gegen\ Krebs\ 2019.pdf 1 print-content-optimize=auto\ 

[Desktop-packages] [Bug 1845501] Re: With NVS-510, screen resolution is locked at 800x600 after switching to intel graphic

2019-09-26 Thread Gavin Lin
** Description changed:

  Currently only see this on a machine with NVS-510.
  Can reproduce with both 430.26 and 430.50 driver.
  Screen resolution was fine before installing nvidia graphic driver.
  But it's locked at 800x600 after installing driver and switching to intel 
graphic.
  
  Steps:
  1. Install 18.04.3 desktop on a machine with Nvidia GK107 [NVS 510] 
[10de:0ffd].
  2. Install nvidia-driver-430 package
  3. Reboot
  4. Switch to intel profile
     $ sudo prime-select intel
  5. Reboot
  
  Expected result:
  Desktop shows up in correct resolution got from edid.
  
  Actual result:
  Desktop shows up in 800x600, and there's no other resolution can be set.
+ 
+ Hardware infomation:
+ Model: Dell Precision Tower 7810
+ GPU: NVIDIA Corporation GK107 [NVS 510] [10de:0ffd] (rev a1)

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

Title:
   With NVS-510, screen resolution is locked at 800x600 after switching
  to intel graphic

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

Bug description:
  Currently only see this on a machine with NVS-510.
  Can reproduce with both 430.26 and 430.50 driver.
  Screen resolution was fine before installing nvidia graphic driver.
  But it's locked at 800x600 after installing driver and switching to intel 
graphic.

  Steps:
  1. Install 18.04.3 desktop on a machine with Nvidia GK107 [NVS 510] 
[10de:0ffd].
  2. Install nvidia-driver-430 package
  3. Reboot
  4. Switch to intel profile
     $ sudo prime-select intel
  5. Reboot

  Expected result:
  Desktop shows up in correct resolution got from edid.

  Actual result:
  Desktop shows up in 800x600, and there's no other resolution can be set.

  Hardware infomation:
  Model: Dell Precision Tower 7810
  GPU: NVIDIA Corporation GK107 [NVS 510] [10de:0ffd] (rev a1)

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

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


[Desktop-packages] [Bug 1845502] Re: With NVS-510, screen stuck at CLI console after switching to intel graphic and switching back to nvidia

2019-09-26 Thread Gavin Lin
** Description changed:

  Currently only see this on a machine with NVS-510.
  Can reproduce with both 430.26 and 430.50 driver.
  Screen stuck at CLI console after switching to intel graphic and switching 
back to nvidia.
  The system still looks running, can access it through ssh or other CLI 
console.
  
  Steps:
  1. Install 18.04.3 desktop on a machine with Nvidia GK107 [NVS 510] 
[10de:0ffd].
  2. Install nvidia-driver-430 package
  3. Reboot
  4. Switch to intel profile
-$ sudo prime-select intel
+    $ sudo prime-select intel
  5. Reboot
  6. Switch to nvidia profile
-$ sudo prime-select nvidia
+    $ sudo prime-select nvidia
  5. Reboot
  
  Expected result:
  System boot into desktop correctly.
  
  Actual result:
  Screen stuck at CLI console.
+ 
+ Hardware infomation:
+ Model: Dell Precision Tower 7810
+ GPU: NVIDIA Corporation GK107 [NVS 510] [10de:0ffd] (rev a1)

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

Title:
  With NVS-510, screen stuck at CLI console after switching to intel
  graphic and switching back to nvidia

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

Bug description:
  Currently only see this on a machine with NVS-510.
  Can reproduce with both 430.26 and 430.50 driver.
  Screen stuck at CLI console after switching to intel graphic and switching 
back to nvidia.
  The system still looks running, can access it through ssh or other CLI 
console.

  Steps:
  1. Install 18.04.3 desktop on a machine with Nvidia GK107 [NVS 510] 
[10de:0ffd].
  2. Install nvidia-driver-430 package
  3. Reboot
  4. Switch to intel profile
     $ sudo prime-select intel
  5. Reboot
  6. Switch to nvidia profile
     $ sudo prime-select nvidia
  5. Reboot

  Expected result:
  System boot into desktop correctly.

  Actual result:
  Screen stuck at CLI console.

  Hardware infomation:
  Model: Dell Precision Tower 7810
  GPU: NVIDIA Corporation GK107 [NVS 510] [10de:0ffd] (rev a1)

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

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


[Desktop-packages] [Bug 1845502] Re: With NVS-510, screen stuck at CLI console after switching to intel graphic and switching back to nvidia

2019-09-26 Thread Gavin Lin
** Attachment added: "20190926_111242.jpg"
   
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-430/+bug/1845502/+attachment/5291479/+files/20190926_111242.jpg

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

Title:
  With NVS-510, screen stuck at CLI console after switching to intel
  graphic and switching back to nvidia

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

Bug description:
  Currently only see this on a machine with NVS-510.
  Can reproduce with both 430.26 and 430.50 driver.
  Screen stuck at CLI console after switching to intel graphic and switching 
back to nvidia.
  The system still looks running, can access it through ssh or other CLI 
console.

  Steps:
  1. Install 18.04.3 desktop on a machine with Nvidia GK107 [NVS 510] 
[10de:0ffd].
  2. Install nvidia-driver-430 package
  3. Reboot
  4. Switch to intel profile
 $ sudo prime-select intel
  5. Reboot
  6. Switch to nvidia profile
 $ sudo prime-select nvidia
  5. Reboot

  Expected result:
  System boot into desktop correctly.

  Actual result:
  Screen stuck at CLI console.

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

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


[Desktop-packages] [Bug 1845502] Re: With NVS-510, screen stuck at CLI console after switching to intel graphic and switching back to nvidia

2019-09-26 Thread Gavin Lin
Please find test report here:
https://drive.google.com/open?id=1DfY6Tt8jUjL2jkBIhxOIB9fsiohXxTJ_fotvGPHpwVg

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

Title:
  With NVS-510, screen stuck at CLI console after switching to intel
  graphic and switching back to nvidia

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

Bug description:
  Currently only see this on a machine with NVS-510.
  Can reproduce with both 430.26 and 430.50 driver.
  Screen stuck at CLI console after switching to intel graphic and switching 
back to nvidia.
  The system still looks running, can access it through ssh or other CLI 
console.

  Steps:
  1. Install 18.04.3 desktop on a machine with Nvidia GK107 [NVS 510] 
[10de:0ffd].
  2. Install nvidia-driver-430 package
  3. Reboot
  4. Switch to intel profile
 $ sudo prime-select intel
  5. Reboot
  6. Switch to nvidia profile
 $ sudo prime-select nvidia
  5. Reboot

  Expected result:
  System boot into desktop correctly.

  Actual result:
  Screen stuck at CLI console.

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

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


[Desktop-packages] [Bug 1845502] [NEW] With NVS-510, screen stuck at CLI console after switching to intel graphic and switching back to nvidia

2019-09-26 Thread Gavin Lin
Public bug reported:

Currently only see this on a machine with NVS-510.
Can reproduce with both 430.26 and 430.50 driver.
Screen stuck at CLI console after switching to intel graphic and switching back 
to nvidia.
The system still looks running, can access it through ssh or other CLI console.

Steps:
1. Install 18.04.3 desktop on a machine with Nvidia GK107 [NVS 510] [10de:0ffd].
2. Install nvidia-driver-430 package
3. Reboot
4. Switch to intel profile
   $ sudo prime-select intel
5. Reboot
6. Switch to nvidia profile
   $ sudo prime-select nvidia
5. Reboot

Expected result:
System boot into desktop correctly.

Actual result:
Screen stuck at CLI console.

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

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

Title:
  With NVS-510, screen stuck at CLI console after switching to intel
  graphic and switching back to nvidia

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

Bug description:
  Currently only see this on a machine with NVS-510.
  Can reproduce with both 430.26 and 430.50 driver.
  Screen stuck at CLI console after switching to intel graphic and switching 
back to nvidia.
  The system still looks running, can access it through ssh or other CLI 
console.

  Steps:
  1. Install 18.04.3 desktop on a machine with Nvidia GK107 [NVS 510] 
[10de:0ffd].
  2. Install nvidia-driver-430 package
  3. Reboot
  4. Switch to intel profile
 $ sudo prime-select intel
  5. Reboot
  6. Switch to nvidia profile
 $ sudo prime-select nvidia
  5. Reboot

  Expected result:
  System boot into desktop correctly.

  Actual result:
  Screen stuck at CLI console.

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

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


[Desktop-packages] [Bug 1845501] Re: With NVS-510, screen resolution is locked at 800x600 after switching to intel graphic

2019-09-26 Thread Gavin Lin
** Attachment added: "20190926_164510.jpg"
   
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-430/+bug/1845501/+attachment/5291478/+files/20190926_164510.jpg

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

Title:
   With NVS-510, screen resolution is locked at 800x600 after switching
  to intel graphic

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

Bug description:
  Currently only see this on a machine with NVS-510.
  Can reproduce with both 430.26 and 430.50 driver.
  Screen resolution was fine before installing nvidia graphic driver.
  But it's locked at 800x600 after installing driver and switching to intel 
graphic.

  Steps:
  1. Install 18.04.3 desktop on a machine with Nvidia GK107 [NVS 510] 
[10de:0ffd].
  2. Install nvidia-driver-430 package
  3. Reboot
  4. Switch to intel profile
     $ sudo prime-select intel
  5. Reboot

  Expected result:
  Desktop shows up in correct resolution got from edid.

  Actual result:
  Desktop shows up in 800x600, and there's no other resolution can be set.

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

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


[Desktop-packages] [Bug 1845501] Re: With NVS-510, screen resolution is locked at 800x600 after switching to intel graphic

2019-09-26 Thread Gavin Lin
Please find test report here:
https://drive.google.com/open?id=1DfY6Tt8jUjL2jkBIhxOIB9fsiohXxTJ_fotvGPHpwVg

** Description changed:

- Currently only see this on a machine with NVS-510 currently.
+ Currently only see this on a machine with NVS-510.
  Can reproduce with both 430.26 and 430.50 driver.
  Screen resolution was fine before installing nvidia graphic driver.
  But it's locked at 800x600 after installing driver and switching to intel 
graphic.
  
  Steps:
  1. Install 18.04.3 desktop on a machine with Nvidia GK107 [NVS 510] 
[10de:0ffd].
  2. Install nvidia-driver-430 package
  3. Reboot
  4. Switch to intel profile
-$ sudo prime-select intel
+    $ sudo prime-select intel
  5. Reboot
  
  Expected result:
  Desktop shows up in correct resolution got from edid.
  
  Actual result:
  Desktop shows up in 800x600, and there's no other resolution can be set.

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

Title:
   With NVS-510, screen resolution is locked at 800x600 after switching
  to intel graphic

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

Bug description:
  Currently only see this on a machine with NVS-510.
  Can reproduce with both 430.26 and 430.50 driver.
  Screen resolution was fine before installing nvidia graphic driver.
  But it's locked at 800x600 after installing driver and switching to intel 
graphic.

  Steps:
  1. Install 18.04.3 desktop on a machine with Nvidia GK107 [NVS 510] 
[10de:0ffd].
  2. Install nvidia-driver-430 package
  3. Reboot
  4. Switch to intel profile
     $ sudo prime-select intel
  5. Reboot

  Expected result:
  Desktop shows up in correct resolution got from edid.

  Actual result:
  Desktop shows up in 800x600, and there's no other resolution can be set.

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

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


[Desktop-packages] [Bug 1845501] [NEW] With NVS-510, screen resolution is locked at 800x600 after switching to intel graphic

2019-09-26 Thread Gavin Lin
Public bug reported:

Currently only see this on a machine with NVS-510.
Can reproduce with both 430.26 and 430.50 driver.
Screen resolution was fine before installing nvidia graphic driver.
But it's locked at 800x600 after installing driver and switching to intel 
graphic.

Steps:
1. Install 18.04.3 desktop on a machine with Nvidia GK107 [NVS 510] [10de:0ffd].
2. Install nvidia-driver-430 package
3. Reboot
4. Switch to intel profile
   $ sudo prime-select intel
5. Reboot

Expected result:
Desktop shows up in correct resolution got from edid.

Actual result:
Desktop shows up in 800x600, and there's no other resolution can be set.

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

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

Title:
   With NVS-510, screen resolution is locked at 800x600 after switching
  to intel graphic

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

Bug description:
  Currently only see this on a machine with NVS-510.
  Can reproduce with both 430.26 and 430.50 driver.
  Screen resolution was fine before installing nvidia graphic driver.
  But it's locked at 800x600 after installing driver and switching to intel 
graphic.

  Steps:
  1. Install 18.04.3 desktop on a machine with Nvidia GK107 [NVS 510] 
[10de:0ffd].
  2. Install nvidia-driver-430 package
  3. Reboot
  4. Switch to intel profile
     $ sudo prime-select intel
  5. Reboot

  Expected result:
  Desktop shows up in correct resolution got from edid.

  Actual result:
  Desktop shows up in 800x600, and there's no other resolution can be set.

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

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


[Desktop-packages] [Bug 1825420] Re: package linux-image-5.0.0-13-generic 5.0.0-13.14 failed to install/upgrade: triggers looping, abandoned

2019-09-26 Thread Brian Murray
I tested an upgrade from Ubuntu 18.10 to Ubuntu 19.04 today with some of
the packages from the DuplicateSignature.txt installed e.g.:

Start-Date: 2019-09-25  17:14:37
Commandline: apt-get install bamfdaemon mime-support
Requested-By: bdmurray (1000)
Install: bamfdaemon:amd64 (0.5.3+18.04.20180207.2-0ubuntu1), libbamf3-2:amd64 
(0.5.3+18.04.20180207.2-0ubuntu1, automatic)
End-Date: 2019-09-25  17:14:38

Start-Date: 2019-09-25  17:15:21
Commandline: apt-get install libvlc-bin gnome-icon-theme hicolor-icon-theme
Requested-By: bdmurray (1000)
Install: gnome-icon-theme:amd64 (3.12.0-3), libvlc5:amd64 (3.0.4-2build1, 
automatic), libvlccore9:amd64 (3.0.4-2build1, automatic), libvlc-bin:amd64 
(3.0.4-2build1), libproxy-tools:amd64 (0.4.15-2, automatic)
End-Date: 2019-09-25  17:15:29

The upgraded proceeded without issue and I did not encounter any issues
with triggers looping.

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

Title:
  package linux-image-5.0.0-13-generic 5.0.0-13.14 failed to
  install/upgrade: triggers looping, abandoned

Status in Ubuntu MATE:
  Invalid
Status in bamf package in Ubuntu:
  Confirmed
Status in dpkg package in Ubuntu:
  Confirmed
Status in initramfs-tools package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed
Status in linux-firmware package in Ubuntu:
  Confirmed
Status in mime-support package in Ubuntu:
  Confirmed

Bug description:
  Steps to reproduce:
  1. Have Ubuntu 18.10 installed
  2. Install all updates to it
  3. Switch to Main server
  4. Launch update-manager
  5. Confirm upgrading to 19.04
  6. Wait for upgrade process to finish

  Expected results:
  * upgrade process ended without errors

  Actual results:
  * upgrade process ended with warning message:

  Could not install 'linux-image-5.0.0-13-generic'
  The upgrade will continue but the 'linux-image-5.0.0-13-generic' package 
may not be in a working state. Please consider submitting a bug report about it.

  triggers looping, abandoned

  Workaround:

Run recommended `dpkg --configure -a` before actual reboot.

  System info: running VirtualBox guest with virtualbox-guest-x11
  (6.0.6-dfsg-1) inside VirtualBox 5.1.38 host.

  ProblemType: Package
  DistroRelease: Ubuntu 19.04
  Package: linux-image-5.0.0-13-generic 5.0.0-13.14
  ProcVersionSignature: Ubuntu 4.18.0-17.18-generic 4.18.20
  Uname: Linux 4.18.0-17-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  mate   1542 F pulseaudio
  Date: Thu Apr 18 22:56:56 2019
  ErrorMessage: triggers looping, abandoned
  InstallationDate: Installed on 2019-02-17 (60 days ago)
  InstallationMedia: Ubuntu-MATE 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.2)
  IwConfig:
   lono wireless extensions.
   
   enp0s3no wireless extensions.
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 002: ID 80ee:0021 VirtualBox USB Tablet
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: innotek GmbH VirtualBox
  ProcFB: 0 vboxdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-17-generic 
root=UUID=01417e27-d554-4ce8-91bc-1dda8392c976 ro quiet splash
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
   No PulseAudio daemon running, or not running as session daemon.
  Python3Details: /usr/bin/python3.7, Python 3.7.3, python3-minimal, 3.7.3-1
  PythonDetails: /usr/bin/python2.7, Python 2.7.16, python-minimal, 2.7.16-1
  RelatedPackageVersions: grub-pc 2.02+dfsg1-12ubuntu2
  RfKill:
   
  SourcePackage: linux
  StagingDrivers: vboxvideo
  Title: package linux-image-5.0.0-13-generic 5.0.0-13.14 failed to 
install/upgrade: triggers looping, abandoned
  UpgradeStatus: Upgraded to disco on 2019-04-18 (0 days ago)
  dmi.bios.date: 12/01/2006
  dmi.bios.vendor: innotek GmbH
  dmi.bios.version: VirtualBox
  dmi.board.name: VirtualBox
  dmi.board.vendor: Oracle Corporation
  dmi.board.version: 1.2
  dmi.chassis.type: 1
  dmi.chassis.vendor: Oracle Corporation
  dmi.modalias: 
dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr:
  dmi.product.family: Virtual Machine
  dmi.product.name: VirtualBox
  dmi.product.version: 1.2
  dmi.sys.vendor: innotek GmbH

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-mate/+bug/1825420/+subscriptions

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


[Desktop-packages] [Bug 1845491] [NEW] CTRL + "Single Click" fails to un-select a selected icon

2019-09-26 Thread Banin Abrar
Public bug reported:

When selecting multiple files using CTRL + click, I noticed that I could
NOT undo a selection by CRTL + clicking on it again.

Inside the Nautilus file browser, however, this issue is NOT present.
>From my testing, the issue is only present on the desktop.


PS: I filed this as a nautilus bug since desktop-icon related bugs are tagged 
as nautilus issues in this link: 
https://wiki.ubuntu.com/Bugs/FindRightPackage#Graphical_Environment

==
SYSTEM INFORMATION
==

lsb_release -rd
===
Description:Ubuntu 19.04
Release:19.04

apt-cache policy nautilus
=
nautilus:
  Installed: 1:3.32.1-0ubuntu0.19.04.0
  Candidate: 1:3.32.1-0ubuntu0.19.04.0
  Version table:
 *** 1:3.32.1-0ubuntu0.19.04.0 500
500 http://ca.archive.ubuntu.com/ubuntu disco-updates/main amd64 
Packages
100 /var/lib/dpkg/status
 1:3.32.0-0ubuntu2 500
500 http://ca.archive.ubuntu.com/ubuntu disco/main amd64 Packages

ProblemType: Bug
DistroRelease: Ubuntu 19.04
Package: nautilus 1:3.32.1-0ubuntu0.19.04.0
ProcVersionSignature: Ubuntu 5.0.0-29.31-generic 5.0.21
Uname: Linux 5.0.0-29-generic x86_64
ApportVersion: 2.20.10-0ubuntu27.1
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Thu Sep 26 17:40:24 2019
GsettingsChanges:
 b'org.gnome.nautilus.icon-view' b'default-zoom-level' b"'standard'"
 b'org.gnome.nautilus.window-state' b'initial-size' b'(768, 789)'
 b'org.gnome.nautilus.list-view' b'default-zoom-level' b"'small'"
InstallationDate: Installed on 2019-06-15 (102 days ago)
InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
ProcEnviron:
 LANGUAGE=en_CA:en
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_CA.UTF-8
 SHELL=/usr/bin/zsh
SourcePackage: nautilus
UpgradeStatus: No upgrade log present (probably fresh install)
usr_lib_nautilus:

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


** Tags: amd64 apport-bug disco nautlius

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

Title:
  CTRL + "Single Click" fails to un-select a selected icon

Status in nautilus package in Ubuntu:
  New

Bug description:
  When selecting multiple files using CTRL + click, I noticed that I
  could NOT undo a selection by CRTL + clicking on it again.

  Inside the Nautilus file browser, however, this issue is NOT present.
  From my testing, the issue is only present on the desktop.

  
  PS: I filed this as a nautilus bug since desktop-icon related bugs are tagged 
as nautilus issues in this link: 
https://wiki.ubuntu.com/Bugs/FindRightPackage#Graphical_Environment

  ==
  SYSTEM INFORMATION
  ==

  lsb_release -rd
  ===
  Description:  Ubuntu 19.04
  Release:  19.04

  apt-cache policy nautilus
  =
  nautilus:
Installed: 1:3.32.1-0ubuntu0.19.04.0
Candidate: 1:3.32.1-0ubuntu0.19.04.0
Version table:
   *** 1:3.32.1-0ubuntu0.19.04.0 500
  500 http://ca.archive.ubuntu.com/ubuntu disco-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   1:3.32.0-0ubuntu2 500
  500 http://ca.archive.ubuntu.com/ubuntu disco/main amd64 Packages

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: nautilus 1:3.32.1-0ubuntu0.19.04.0
  ProcVersionSignature: Ubuntu 5.0.0-29.31-generic 5.0.21
  Uname: Linux 5.0.0-29-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27.1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Sep 26 17:40:24 2019
  GsettingsChanges:
   b'org.gnome.nautilus.icon-view' b'default-zoom-level' b"'standard'"
   b'org.gnome.nautilus.window-state' b'initial-size' b'(768, 789)'
   b'org.gnome.nautilus.list-view' b'default-zoom-level' b"'small'"
  InstallationDate: Installed on 2019-06-15 (102 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  ProcEnviron:
   LANGUAGE=en_CA:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_CA.UTF-8
   SHELL=/usr/bin/zsh
  SourcePackage: nautilus
  UpgradeStatus: No upgrade log present (probably fresh install)
  usr_lib_nautilus:

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

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


[Desktop-packages] [Bug 1842643] Re: [ffe] Update to 1.44.6

2019-09-26 Thread Sebastien Bacher
(re-opening and tagging as blocked by ff for our tracking script)

** Changed in: pango1.0 (Ubuntu)
   Status: Won't Fix => Triaged

** Summary changed:

- [ffe] Update to 1.44.6
+ Don't update to 1.44.6 this cycle

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

Title:
  Don't update to 1.44.6 this cycle

Status in pango1.0 package in Ubuntu:
  Triaged

Bug description:
  There are a lot of changes in pango1.0 since the version we currently
  have in eoan. We held off updating because there was a test failure.
  This has been resolved in the latest release, so we'd like to go for
  the update now.

  Overview of changes in 1.44.6
  =
  - docs: Fix symbol indices
  - Fix Thai line breaking
  - Re-add symbols needed by some bindings
  - Don't insert hyphens for some languages
  - Fix a crash with hyphenation

  Overview of changes in 1.44.5
  =
  - Revert a broken change (causing crashes on OS X)

  Overview of changes in 1.44.4
  =
  - Add an insert-hyphens attribute
  - Reinstate the return type of pango_fc_font_lock_face
  - Fix a problem with ellipses getting the wrong font
  - fc: Improve filtering by font format
  - Re-add PangoFcFont to public headers
  - Install PangoFc and PangoOT introspection files
  - Fix ink rectangles to have positive height
  - Fix mark positioning
  - Switch to using harfbuzz for metrics

  Overview of changes in 1.44.3
  =
  - Install pango-ot headers
  - Make subpixel positioning optional
  - fc: Ignore fonts with unsupported formats

  Overview of changes in 1.44.2
  =
  - Disable ligatures when letterspacing
  - Set design coords on hb_font_t
  - Expose more font options in pango-view
  - OS X: Make 'system-ui' font work
  - Keep deprecated pango-fc apis in headers
  - Make hex boxes work, always
  - introspection: Various build fixes
  - introspection: Add PangoPT, PangoFT2 namespaces
  - layout: Make the new line-spacing opt-in

  Overview of changes in 1.44.1
  =
  - Fix a crash with allow_break attributes
  - Fix Emoji spacing
  - Fix up includes and pkg-config requires
  - Correct some cases for hyphen insertion

  Overview of changes in 1.44.0
  =
  - Use harfbuzz for shaping on all platforms
  - Stop using freetype for font loading; this
  drops support for type1 and bitmap fonts
  - Add a getter for hb_font_t
  - Make PangoCoverage a GObject
  - Add a pango_tailor_break api
  - font metrics: Add line height
  - layout: Support line spacing
  - layout: Draw hyphens for line breaks
  - Add an attribute to suppress line breaking
  - cairo: Don't render hex boxes for space
  - Add an attribute to show invisible characters
  - Stop quantizing glyph positions
  - Add tests for itemization and line breaking
  - Remove language and shape engine remnants
  - Rename meson options: gtk_doc, introspection
  - Require GLib 2.59.2
  - Require Harfbuzz 2.0

  Overview of changes in 1.43.0
  =
  - Drop autotools
  - Drop Visual Studio build
  - Build with meson everywhere
  - Update Emoji tables for Unicode 11
  - Update test data for Unicode 11
  - Fix a crash with Thai breaking
  - Fix a crash with font variations
  - Deprecate bidi apis in favor of fribidi
  - Add a variable font family api
  - Improve font fallback handling on win32

  And see posts from upstream

  https://blogs.gnome.org/mclasen/2019/07/19/pango-updates/
  https://blogs.gnome.org/mclasen/2019/07/27/more-text-rendering-updates/
  https://blogs.gnome.org/mclasen/2019/08/07/pango-1-44-wrap-up/

  for the new features.

  We'd like to update to it, if possible.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pango1.0/+bug/1842643/+subscriptions

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


[Desktop-packages] [Bug 1559245] Re: Pulseaudio selects HSP instead of A2DP and no way to set default action

2019-09-26 Thread Launchpad Bug Tracker
*** This bug is a duplicate of bug 1494230 ***
https://bugs.launchpad.net/bugs/1494230

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

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

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

Title:
  Pulseaudio selects HSP instead of A2DP and no way to set default
  action

Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  I am trying to use a bluetooth headphone with ubuntu 14.04 and system
  defaults to using HSP. The problem is that Once it connects, it should
  use A2DP and become default device because I am using it from KODI and
  it is very inconvenient to set it from command line. Otherwise HSP is
  providing very bad quality audio. There is no way to set a default
  action, and system does not retain the last set setting. Eg. I can go
  and set the headphones to use A2DP but when I connect next time, it
  switches back to HSP. (I believe it could remember the device from the
  device id at least!)

  I asked about this on launchpad answers and somebody closed it and said I 
should report it as a bug. If you think this shouldn't have been reported as a 
bug, blame the person who closed my question at launchpad answers :) Below is 
the link to it and more information and the ugly workaround I implemented in my 
system:
  https://answers.launchpad.net/ubuntu/+question/288799

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

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


[Desktop-packages] [Bug 1686631] Re: [Ubuntu-gnome] if an app is uninstalled and has a snap and deb it displays nothing in the overview

2019-09-26 Thread John Lenton
** Package changed: snapd (Ubuntu) => gnome-software (Ubuntu)

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

Title:
  [Ubuntu-gnome] if an app is uninstalled and has a snap and deb it
  displays nothing in the overview

Status in gnome-software package in Ubuntu:
  New

Bug description:
  STEPS:
  1. Install ubuntu-gnome 17.04
  2. update it
  3. click on Activities
  4. type krita, blender

  EXPECTED:
  I expect to see listed under the gnome-software the option to install one of 
the apps

  ACTUAL:
  I get a message of No Results

  This only happens if both the deb and snap are not installed, under wayland 
snaps are not recognised at all due to the XDG_DATA_DIRS not listing it.
  Wayland:
  
/home/davmor2/.local/share/flatpak/exports/share/:/var/lib/flatpak/exports/share/:/usr/local/share/:/usr/share/

  X11:
  
/usr/share/gnome:/home/davmor2/.local/share/flatpak/exports/share/:/var/lib/flatpak/exports/share/:/usr/local/share/:/usr/share/:/var/lib/snapd/desktop

  WORKAROUND:
  For now both apps appear in gnome-software no problems just not as 
suggestions in the overview.

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

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


[Desktop-packages] [Bug 1686631] [NEW] [Ubuntu-gnome] if an app is uninstalled and has a snap and deb it displays nothing in the overview

2019-09-26 Thread Launchpad Bug Tracker
You have been subscribed to a public bug:

STEPS:
1. Install ubuntu-gnome 17.04
2. update it
3. click on Activities
4. type krita, blender

EXPECTED:
I expect to see listed under the gnome-software the option to install one of 
the apps

ACTUAL:
I get a message of No Results

This only happens if both the deb and snap are not installed, under wayland 
snaps are not recognised at all due to the XDG_DATA_DIRS not listing it.
Wayland:
/home/davmor2/.local/share/flatpak/exports/share/:/var/lib/flatpak/exports/share/:/usr/local/share/:/usr/share/

X11:
/usr/share/gnome:/home/davmor2/.local/share/flatpak/exports/share/:/var/lib/flatpak/exports/share/:/usr/local/share/:/usr/share/:/var/lib/snapd/desktop

WORKAROUND:
For now both apps appear in gnome-software no problems just not as suggestions 
in the overview.

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

-- 
[Ubuntu-gnome] if an app is uninstalled and has a snap and deb it displays 
nothing in the overview
https://bugs.launchpad.net/bugs/1686631
You received this bug notification because you are a member of Desktop 
Packages, which is subscribed to gnome-software in Ubuntu.

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


[Desktop-packages] [Bug 1845422] Re: Firefox don't start

2019-09-26 Thread VinsS
I've tested with my old profile and the safe-mode, same problem.

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

Title:
  Firefox don't start

Status in firefox package in Ubuntu:
  Incomplete

Bug description:
  when I start Firefox nothing append.
  If I restart it, a message appears with says "Firefox is already running but 
not responding. Close the first session if you want open a new one".

  This problem concern the latest update (this morning) of firefox.

  I've also tried in a terminal with the option -g without any reaction.

  
  vincent@djoliba:~$ apt show firefox
  Package: firefox
  Version: 69.0.1+build1-0ubuntu0.18.04.1
  Priority: optional
  Section: web
  Origin: Ubuntu
  Maintainer: Ubuntu Mozilla Team 
  Bugs: https://bugs.launchpad.net/ubuntu/+filebug
  Installed-Size: 189 MB
  Provides: gnome-www-browser, iceweasel, www-browser
  Depends: lsb-release, libatk1.0-0 (>= 1.12.4), libc6 (>= 2.27), 
libcairo-gobject2 (>= 1.10.0), libcairo2 (>= 1.10.0), libdbus-1-3 (>= 1.9.14), 
libdbus-glib-1-2 (>= 0.78), libfontconfig1 (>= 2.12), libfreetype6 (>= 2.3.5), 
libgcc1 (>= 1:4.2), libgdk-pixbuf2.0-0 (>= 2.22.0), libglib2.0-0 (>= 2.31.8), 
libgtk-3-0 (>= 3.4), libpango-1.0-0 (>= 1.22.0), libpangocairo-1.0-0 (>= 
1.14.0), libstartup-notification0 (>= 0.8), libstdc++6 (>= 6), libx11-6, 
libx11-xcb1, libxcb-shm0, libxcb1, libxcomposite1 (>= 1:0.3-1), libxdamage1 (>= 
1:1.1), libxext6, libxfixes3, libxrender1, libxt6
  Recommends: xul-ext-ubufox, libcanberra0, libdbusmenu-glib4, 
libdbusmenu-gtk3-4
  Suggests: fonts-lyx
  Replaces: kubuntu-firefox-installer
  Task: ubuntu-desktop, kubuntu-desktop, kubuntu-full, xubuntu-desktop, 
lubuntu-gtk-desktop, lubuntu-desktop, ubuntustudio-desktop, 
ubuntukylin-desktop, ubuntu-mate-core, ubuntu-mate-desktop
  Xul-Appid: {ec8030f7-c20a-464f-9b0e-13a3a9e97384}
  Supported: 5y
  Download-Size: 50,3 MB
  APT-Manual-Installed: yes
  APT-Sources: http://be.archive.ubuntu.com/ubuntu bionic-updates/main amd64 
Packages
  Description: Le Navigateur Internet simple et sûr de Mozilla ..
  -

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

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


[Desktop-packages] [Bug 1845422] Re: Firefox don't start

2019-09-26 Thread VinsS
Hi, as I say, I've solved the problem with a new profile.

But if I retry firefox -P and choose the profile default I've
immediately the message "Firefox is already running but don't respond".

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

Title:
  Firefox don't start

Status in firefox package in Ubuntu:
  Incomplete

Bug description:
  when I start Firefox nothing append.
  If I restart it, a message appears with says "Firefox is already running but 
not responding. Close the first session if you want open a new one".

  This problem concern the latest update (this morning) of firefox.

  I've also tried in a terminal with the option -g without any reaction.

  
  vincent@djoliba:~$ apt show firefox
  Package: firefox
  Version: 69.0.1+build1-0ubuntu0.18.04.1
  Priority: optional
  Section: web
  Origin: Ubuntu
  Maintainer: Ubuntu Mozilla Team 
  Bugs: https://bugs.launchpad.net/ubuntu/+filebug
  Installed-Size: 189 MB
  Provides: gnome-www-browser, iceweasel, www-browser
  Depends: lsb-release, libatk1.0-0 (>= 1.12.4), libc6 (>= 2.27), 
libcairo-gobject2 (>= 1.10.0), libcairo2 (>= 1.10.0), libdbus-1-3 (>= 1.9.14), 
libdbus-glib-1-2 (>= 0.78), libfontconfig1 (>= 2.12), libfreetype6 (>= 2.3.5), 
libgcc1 (>= 1:4.2), libgdk-pixbuf2.0-0 (>= 2.22.0), libglib2.0-0 (>= 2.31.8), 
libgtk-3-0 (>= 3.4), libpango-1.0-0 (>= 1.22.0), libpangocairo-1.0-0 (>= 
1.14.0), libstartup-notification0 (>= 0.8), libstdc++6 (>= 6), libx11-6, 
libx11-xcb1, libxcb-shm0, libxcb1, libxcomposite1 (>= 1:0.3-1), libxdamage1 (>= 
1:1.1), libxext6, libxfixes3, libxrender1, libxt6
  Recommends: xul-ext-ubufox, libcanberra0, libdbusmenu-glib4, 
libdbusmenu-gtk3-4
  Suggests: fonts-lyx
  Replaces: kubuntu-firefox-installer
  Task: ubuntu-desktop, kubuntu-desktop, kubuntu-full, xubuntu-desktop, 
lubuntu-gtk-desktop, lubuntu-desktop, ubuntustudio-desktop, 
ubuntukylin-desktop, ubuntu-mate-core, ubuntu-mate-desktop
  Xul-Appid: {ec8030f7-c20a-464f-9b0e-13a3a9e97384}
  Supported: 5y
  Download-Size: 50,3 MB
  APT-Manual-Installed: yes
  APT-Sources: http://be.archive.ubuntu.com/ubuntu bionic-updates/main amd64 
Packages
  Description: Le Navigateur Internet simple et sûr de Mozilla ..
  -

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

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


[Desktop-packages] [Bug 1845471] Re: gnome-calendar won't start from Activities Overview

2019-09-26 Thread Ubuntu QA Website
This bug has been reported on the Ubuntu ISO testing tracker.

A list of all reports related to this bug can be found here:
http://iso.qa.ubuntu.com/qatracker/reports/bugs/1845471

** Tags added: iso-testing

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

Title:
  gnome-calendar won't start from Activities Overview

Status in gnome-calendar package in Ubuntu:
  New

Bug description:
  During ISO testing (live-session) I found that I was unable to start
  gnome-calendar.

  Steps to reproduce:
  Display Activities Overview, search for and select "Calendar"

  Expected outcome:
  Application starts

  Actual outcome:
  Application doesn't start

  Workaround:
  Pin application icon to Ubuntu Dock or start from terminal

  Confirmation of issue:
  I can confirm this issue with a permanent installation on another machine.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: gnome-calendar 3.34.0-1
  ProcVersionSignature: Ubuntu 5.3.0-10.11-generic 5.3.0-rc8
  Uname: Linux 5.3.0-10-generic x86_64
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Thu Sep 26 10:36:08 2019
  InstallationDate: Installed on 2019-05-17 (131 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190517)
  SourcePackage: gnome-calendar
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


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

2019-09-26 Thread Paride Legovini
** Also affects: gnome-control-center (Ubuntu Disco)
   Importance: Undecided
   Status: New

** Also affects: gnome-control-center (Ubuntu Eoan)
   Importance: Low
   Status: Confirmed

** Also affects: gnome-control-center (Ubuntu Bionic)
   Importance: Undecided
   Status: New

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

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

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

Title:
  Cannot restore default alert sound (Ubuntu bell)

Status in gnome-control-center package in Ubuntu:
  Confirmed
Status in gnome-control-center source package in Bionic:
  Confirmed
Status in gnome-control-center source package in Disco:
  Confirmed
Status in gnome-control-center source package in Eoan:
  Confirmed

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

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

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

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

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

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

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


[Desktop-packages] [Bug 1845471] [NEW] gnome-calendar won't start from Activities Overview

2019-09-26 Thread Paul White
Public bug reported:

During ISO testing (live-session) I found that I was unable to start
gnome-calendar.

Steps to reproduce:
Display Activities Overview, search for and select "Calendar"

Expected outcome:
Application starts

Actual outcome:
Application doesn't start

Workaround:
Pin application icon to Ubuntu Dock or start from terminal

Confirmation of issue:
I can confirm this issue with a permanent installation on another machine.

ProblemType: Bug
DistroRelease: Ubuntu 19.10
Package: gnome-calendar 3.34.0-1
ProcVersionSignature: Ubuntu 5.3.0-10.11-generic 5.3.0-rc8
Uname: Linux 5.3.0-10-generic x86_64
ApportVersion: 2.20.11-0ubuntu7
Architecture: amd64
CurrentDesktop: GNOME
Date: Thu Sep 26 10:36:08 2019
InstallationDate: Installed on 2019-05-17 (131 days ago)
InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190517)
SourcePackage: gnome-calendar
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug eoan

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

Title:
  gnome-calendar won't start from Activities Overview

Status in gnome-calendar package in Ubuntu:
  New

Bug description:
  During ISO testing (live-session) I found that I was unable to start
  gnome-calendar.

  Steps to reproduce:
  Display Activities Overview, search for and select "Calendar"

  Expected outcome:
  Application starts

  Actual outcome:
  Application doesn't start

  Workaround:
  Pin application icon to Ubuntu Dock or start from terminal

  Confirmation of issue:
  I can confirm this issue with a permanent installation on another machine.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: gnome-calendar 3.34.0-1
  ProcVersionSignature: Ubuntu 5.3.0-10.11-generic 5.3.0-rc8
  Uname: Linux 5.3.0-10-generic x86_64
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Thu Sep 26 10:36:08 2019
  InstallationDate: Installed on 2019-05-17 (131 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190517)
  SourcePackage: gnome-calendar
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1845422] Re: Firefox don't start

2019-09-26 Thread Olivier Tilloy
Thanks for the report VinsS.

Can you reliably reproduce the problem, across reboots ?

Does it start if you run it in safe mode (`firefox -safe-mode`) ?

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

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

Title:
  Firefox don't start

Status in firefox package in Ubuntu:
  Incomplete

Bug description:
  when I start Firefox nothing append.
  If I restart it, a message appears with says "Firefox is already running but 
not responding. Close the first session if you want open a new one".

  This problem concern the latest update (this morning) of firefox.

  I've also tried in a terminal with the option -g without any reaction.

  
  vincent@djoliba:~$ apt show firefox
  Package: firefox
  Version: 69.0.1+build1-0ubuntu0.18.04.1
  Priority: optional
  Section: web
  Origin: Ubuntu
  Maintainer: Ubuntu Mozilla Team 
  Bugs: https://bugs.launchpad.net/ubuntu/+filebug
  Installed-Size: 189 MB
  Provides: gnome-www-browser, iceweasel, www-browser
  Depends: lsb-release, libatk1.0-0 (>= 1.12.4), libc6 (>= 2.27), 
libcairo-gobject2 (>= 1.10.0), libcairo2 (>= 1.10.0), libdbus-1-3 (>= 1.9.14), 
libdbus-glib-1-2 (>= 0.78), libfontconfig1 (>= 2.12), libfreetype6 (>= 2.3.5), 
libgcc1 (>= 1:4.2), libgdk-pixbuf2.0-0 (>= 2.22.0), libglib2.0-0 (>= 2.31.8), 
libgtk-3-0 (>= 3.4), libpango-1.0-0 (>= 1.22.0), libpangocairo-1.0-0 (>= 
1.14.0), libstartup-notification0 (>= 0.8), libstdc++6 (>= 6), libx11-6, 
libx11-xcb1, libxcb-shm0, libxcb1, libxcomposite1 (>= 1:0.3-1), libxdamage1 (>= 
1:1.1), libxext6, libxfixes3, libxrender1, libxt6
  Recommends: xul-ext-ubufox, libcanberra0, libdbusmenu-glib4, 
libdbusmenu-gtk3-4
  Suggests: fonts-lyx
  Replaces: kubuntu-firefox-installer
  Task: ubuntu-desktop, kubuntu-desktop, kubuntu-full, xubuntu-desktop, 
lubuntu-gtk-desktop, lubuntu-desktop, ubuntustudio-desktop, 
ubuntukylin-desktop, ubuntu-mate-core, ubuntu-mate-desktop
  Xul-Appid: {ec8030f7-c20a-464f-9b0e-13a3a9e97384}
  Supported: 5y
  Download-Size: 50,3 MB
  APT-Manual-Installed: yes
  APT-Sources: http://be.archive.ubuntu.com/ubuntu bionic-updates/main amd64 
Packages
  Description: Le Navigateur Internet simple et sûr de Mozilla ..
  -

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

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


[Desktop-packages] [Bug 1845362] Re: gnome-font-viewer crashed with signal 5 in _XEventsQueued()

2019-09-26 Thread Paul White
** Description changed:

- Reproducible crash or freezing of application during ISO testing.
+ Reproducible crash (tested on Ubuntu and Xubuntu) or freezing of
+ application during ISO testing of a live-session.
  
  Application will crash if there is an attempt to close it or scroll
- through fonts. Sometimes fonts are never displayed and application
- freezes. On one occasion my laptop was rendered unusable when Firefox
- was launched while trying to report the crash to Launchpad.
+ through fonts. On one occasion my laptop was rendered unusable when
+ Firefox was launched while trying to report the crash to Launchpad.
+ 
+ After the bug report has been sent gnome-font-viewer will freeze when
+ automatically restarted. No fonts are displayed.
  
  ProblemType: Crash
  DistroRelease: Ubuntu 19.10
  Package: gnome-font-viewer 3.34.0-1
  ProcVersionSignature: Ubuntu 5.3.0-10.11-generic 5.3.0-rc8
  Uname: Linux 5.3.0-10-generic x86_64
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  CasperVersion: 1.416
  CurrentDesktop: XFCE
  Date: Wed Sep 25 17:34:17 2019
  ExecutablePath: /usr/bin/gnome-font-viewer
  LiveMediaBuild: Xubuntu 19.10 "Eoan Ermine" - Beta amd64 (20190925)
  ProcCmdline: gnome-font-viewer
  ProcEnviron:
-  LANGUAGE=en
-  PATH=(custom, no user)
-  XDG_RUNTIME_DIR=
-  LANG=C.UTF-8
-  SHELL=/bin/bash
+  LANGUAGE=en
+  PATH=(custom, no user)
+  XDG_RUNTIME_DIR=
+  LANG=C.UTF-8
+  SHELL=/bin/bash
  Signal: 5
  SourcePackage: gnome-font-viewer
  StacktraceTop:
-  ?? () from /lib/x86_64-linux-gnu/libX11.so.6
-  ?? () from /lib/x86_64-linux-gnu/libX11.so.6
-  _XEventsQueued () from /lib/x86_64-linux-gnu/libX11.so.6
-  XPending () from /lib/x86_64-linux-gnu/libX11.so.6
-  ?? () from /lib/x86_64-linux-gnu/libgdk-3.so.0
+  ?? () from /lib/x86_64-linux-gnu/libX11.so.6
+  ?? () from /lib/x86_64-linux-gnu/libX11.so.6
+  _XEventsQueued () from /lib/x86_64-linux-gnu/libX11.so.6
+  XPending () from /lib/x86_64-linux-gnu/libX11.so.6
+  ?? () from /lib/x86_64-linux-gnu/libgdk-3.so.0
  Title: gnome-font-viewer crashed with signal 5 in _XEventsQueued()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  separator:

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

Title:
  gnome-font-viewer crashed with signal 5 in _XEventsQueued()

Status in gnome-font-viewer package in Ubuntu:
  New

Bug description:
  Reproducible crash (tested on Ubuntu and Xubuntu) or freezing of
  application during ISO testing of a live-session.

  Application will crash if there is an attempt to close it or scroll
  through fonts. On one occasion my laptop was rendered unusable when
  Firefox was launched while trying to report the crash to Launchpad.

  After the bug report has been sent gnome-font-viewer will freeze when
  automatically restarted. No fonts are displayed.

  ProblemType: Crash
  DistroRelease: Ubuntu 19.10
  Package: gnome-font-viewer 3.34.0-1
  ProcVersionSignature: Ubuntu 5.3.0-10.11-generic 5.3.0-rc8
  Uname: Linux 5.3.0-10-generic x86_64
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  CasperVersion: 1.416
  CurrentDesktop: XFCE
  Date: Wed Sep 25 17:34:17 2019
  ExecutablePath: /usr/bin/gnome-font-viewer
  LiveMediaBuild: Xubuntu 19.10 "Eoan Ermine" - Beta amd64 (20190925)
  ProcCmdline: gnome-font-viewer
  ProcEnviron:
   LANGUAGE=en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C.UTF-8
   SHELL=/bin/bash
  Signal: 5
  SourcePackage: gnome-font-viewer
  StacktraceTop:
   ?? () from /lib/x86_64-linux-gnu/libX11.so.6
   ?? () from /lib/x86_64-linux-gnu/libX11.so.6
   _XEventsQueued () from /lib/x86_64-linux-gnu/libX11.so.6
   XPending () from /lib/x86_64-linux-gnu/libX11.so.6
   ?? () from /lib/x86_64-linux-gnu/libgdk-3.so.0
  Title: gnome-font-viewer crashed with signal 5 in _XEventsQueued()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  separator:

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

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


[Desktop-packages] [Bug 1845198] Re: GNOME Shell seemingly locked up at login

2019-09-26 Thread Olivier Tilloy
I tested the package from silo 3814 in an eoan VM where I can observe
the hang very reliably, and the problem appears to be gone (rebooted the
machine a dozen of times or so without an issue).

+1 from me (but as pointed out already the changelog entry needs to be
fixed, it doesn't mention the patch name).

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

Title:
  GNOME Shell seemingly locked up at login

Status in GNOME Shell:
  New
Status in gnome-shell package in Ubuntu:
  In Progress
Status in gnome-shell source package in Eoan:
  In Progress

Bug description:
  In 19.10, and also running the X PPA from
  http://ppa.launchpad.net/canonical-x/x-staging/ubuntu

  When I logged in (after having attached a Bluetooth speaker in order
  to test if it was being reconnected correctly) GNOME Shell isn't
  responding to mouse or keyboard input.

  The clock continues to tell the right time, and the mouse moves around
  the screen and is repainted correctly.

  Most recent output from gdb here:
  https://paste.ubuntu.com/p/pSshP8V2SZ/

  Older output here: https://paste.ubuntu.com/p/rPY2VDj6tX/

  Journal here:  https://paste.ubuntu.com/p/GZcWsQdRhd/

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

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


[Desktop-packages] [Bug 1222602] Re: [regression] [gen3] Mesa 9.2 makes Unity unusable on Atom class hardware and 943/945 graphics controllers

2019-09-26 Thread Bug Watch Updater
** Changed in: mesa
   Status: Unknown => New

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

Title:
  [regression] [gen3] Mesa 9.2 makes Unity unusable on Atom class
  hardware and 943/945 graphics controllers

Status in Mesa:
  New
Status in Nux:
  Fix Released
Status in Release Notes for Ubuntu:
  Invalid
Status in mesa package in Ubuntu:
  Fix Released
Status in nux package in Ubuntu:
  Fix Released
Status in unity package in Ubuntu:
  Invalid

Bug description:
  After the upgrade to Mesa 9.2.0 unity is barely usable.
  Dash, Alt+Tab switcher and Alt+F2 command line shows in more than 1 minute, 
using 100% cpu.

  A downgrade to mesa 9.1.6-2ubuntu2 restores full performance.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: libgl1-mesa-glx 9.2-1ubuntu1
  ProcVersionSignature: Ubuntu 3.11.0-5.11-generic 3.11.0
  Uname: Linux 3.11.0-5-generic i686
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.12.1-0ubuntu3
  Architecture: i386
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Mon Sep  9 01:51:45 2013
  DistUpgraded: 2013-09-08 20:36:47,811 DEBUG enabling apt cron job
  DistroCodename: saucy
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Mobile 945GSE Express Integrated Graphics Controller 
[8086:27ae] (rev 03) (prog-if 00 [VGA controller])
 Subsystem: Micro-Star International Co., Ltd. Device [1462:0110]
 Subsystem: Micro-Star International Co., Ltd. Device [1462:0110]
  InstallationDate: Installed on 2013-09-07 (1 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release i386 (20130424)
  MachineType: MICRO-STAR INTERNATIONAL CO., LTD U90/U100
  MarkForUpload: True
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=it_IT.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-5-generic 
root=UUID=674329c8-d0a6-4954-89c0-72821cfa0ba8 ro quiet splash vt.handoff=7
  SourcePackage: mesa
  UpgradeStatus: Upgraded to saucy on 2013-09-08 (0 days ago)
  dmi.bios.date: 12/01/2009
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 4.6.3
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: U90/U100
  dmi.board.vendor: MICRO-STAR INTERNATIONAL CO., LTD
  dmi.board.version: Ver.001
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 10
  dmi.chassis.vendor: MICRO-STAR INTERNATIONAL CO., LTD
  dmi.chassis.version: Ver.001
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr4.6.3:bd12/01/2009:svnMICRO-STARINTERNATIONALCO.,LTD:pnU90/U100:pvrVer.001:rvnMICRO-STARINTERNATIONALCO.,LTD:rnU90/U100:rvrVer.001:cvnMICRO-STARINTERNATIONALCO.,LTD:ct10:cvrVer.001:
  dmi.product.name: U90/U100
  dmi.product.version: Ver.001
  dmi.sys.vendor: MICRO-STAR INTERNATIONAL CO., LTD
  version.compiz: compiz 1:0.9.10+13.10.20130828.2-0ubuntu1
  version.libdrm2: libdrm2 2.4.46-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 9.2-1ubuntu1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 9.2-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.14.2.901-2ubuntu4
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu3.1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.2.0-0ubuntu6
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.21.14-4ubuntu3
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.9-2ubuntu1
  xserver.bootTime: Mon Sep  9 01:46:55 2013
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id1001 
   vendor HSD
  xserver.version: 2:1.14.2.901-2ubuntu4

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

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


[Desktop-packages] [Bug 1842865] Re: Xubuntu 18.04 sometimes freezes when turned on on logo

2019-09-26 Thread Maxim Smih
@Gunnar Hjalmarsson (gunnarhj) :
 https://bugzilla.kernel.org/show_bug.cgi?id=204779

** Bug watch added: Linux Kernel Bug Tracker #204779
   https://bugzilla.kernel.org/show_bug.cgi?id=204779

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1842865

Title:
  Xubuntu 18.04 sometimes freezes when turned on on logo

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Sometimes, when I turn off the computer, it hangs on the logo. I can
  not turn off the computer using alt + SysRq + REISUO. The light on the
  system unit continues to light, and the fan runs. This is a problem
  with kernel 5.0, 5.3

  Here is the error:
  info: task systemd shutdown:1 blocked for more than 120 seconds
  Not tainted 5.0.0-20-generic #21-Ubuntu
  «echo 0 /proc/sys kernel/hung_task_timeout_secs» disables this message

  https://ibb.co/PcYvDLq
  https://ibb.co/4JMGwvC

  sudo dmesg|grep ACPI|less -  https://pastebin.com/PZxRGNyJ

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Пакет: gvfs 1.36.1-0ubuntu1.3.3
  ProcVersionSign ature: Ubuntu 5.0.0-27. 28 ~ 18,04. 1-generic 5.0.21
  Uname: Linux 5.0.0-27-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.7
  Архитектура: amd64
  CurrentDesktop: XFCE
  Дата: Четверг 5 09:44:35 2019 Дата
  установки: установлено в 2019-08 -09 (26 дней назад)
  InstallationMedia: Xubuntu 18.04.2 LTS «Бионический бобр» - выпуск amd64 
(20190210)
  ProcEnviron:
   LANGUAGE = ru_UA: ru
   PATH = (пользовательский, нет пользователя)
   XDG_RUNTIME_ DIR = 
   LANG = ru_UA.UTF -8
   SHELL = / bin / bash
  SourcePackage: gvfs
  UpgradeStatus: журнал обновления отсутствует (возможно, новая установка)
  ---
  Тип проблемы: ошибка
  ApportVersion: 2.20.9-0ubuntu7.7
  Архитектура: amd64
  AudioDevicesInUse:
   КОМАНДА ДОСТУПА ПОЛЬЗОВАТЕЛЯ PID
   / dev / snd / controlC0: макс. 1055 F  pulseaudio
  CurrentDesktop: XFCE
  DistroRelease: Ubuntu 18.04
  InstallationDate: Установлен 2019-08-09 (37 дней назад)
  InstallationMedia: Xubuntu 18.04.2 LTS "Bionic Beaver" - Выпуск amd64 
(20190210)
  IwConfig:
   enp0s25 без беспроводных расширений.

   enp7s4 нет беспроводных расширений.

   нет никаких беспроводных расширений.
  Тип машины: Hewlett-Packard HP Compaq dc5800 Microtower
  Пакет: Linux (не установлен)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE = / загрузки / vmlinuz- 4.15.0- 62-общий корень 
= UUID = 8c77fe78- d1d9-4452- aca0-eb1f844041 22 ро тихий всплеск vt.handoff = 1
  ProcVersionSign ature: Ubuntu 4.15.0- 62,69-родовое 4.15.18
  RelatedPackageV ersions:
   linux- restricted- modules- 4.15.0- 62-родовое N / A
   linux- backports- modules- 4.15.0 - 62-типовой N / A
   linux-прошивка 1.173.9
  RfKill:

  Теги: bionic
  Uname: Linux 4.15.0-62-generic x86_64
  UpgradeStatus: нет журнала обновления (возможно, новая установка)
  Группы пользователей: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 26.10.2015
  dmi. bios.vendor: Hewlett-Packard
  dmi.bios.version: 786F2 v01.60
  dmi.board. asset.tag: CZC8107S1Y
  dmi.board.name: 2820h
  dmi.board.vendor: Hewlett-Packard
  dmi.chassis. asset.tag: CZC8107S1Y
  dmi.chassis.type: 6
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: dmi: bvnHewlett- Packard: bvr786F2v01. 60: bd10 / 26/2015: 
svnHewlett- Packard:pnHPCompaqdc580 0Microtower: pvr: rvnHewlett- Packard: 
rn2820h: rvr: cvnHewlett- Packard: ct6: cvr:
  dmi.product.family: 103C_53307F
  dmi.product.name: HP Compaq dvtwelet dv00 от компании HP
  :

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

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


[Desktop-packages] [Bug 1609750] Re: Audio not working on Acer Chromebook R11

2019-09-26 Thread daniel primo stuart
Kernel needs this patch for maxim98090 to work on cyan and some baytrail
chromebooks:
https://github.com/torvalds/linux/commit/d5e120422db8808e1c8b1507900ca393a877c58f

As it didn't make to 5.3 on time, would be nice if it were backported by
ubuntu devs

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

Title:
  Audio not working on Acer Chromebook R11

Status in linux:
  Confirmed
Status in linux package in Ubuntu:
  In Progress
Status in pulseaudio package in Ubuntu:
  Invalid

Bug description:
  Audio is not working at all on Acer Chromebook R11 (codename CYAN).
  It's a Intel Braswell platform. snd_hda_intel messages seem normal,
  but Pulseaudio does not detect sound hardware.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: pulseaudio 1:9.0-1.1ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-33.52-generic 4.4.15
  Uname: Linux 4.4.0-33-generic x86_64
  ApportVersion: 2.20.3-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/hwC0D2', '/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', 
'/dev/snd/pcmC0D3p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] 
failed with exit code 1:
  CurrentDesktop: Unity
  Date: Thu Aug  4 14:12:03 2016
  InstallationDate: Installed on 2016-07-22 (13 days ago)
  InstallationMedia:
   
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  SourcePackage: pulseaudio
  Symptom: audio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/20/2016
  dmi.bios.vendor: coreboot
  dmi.chassis.type: 3
  dmi.chassis.vendor: GOOGLE
  dmi.modalias: 
dmi:bvncoreboot:bvr:bd05/20/2016:svnGOOGLE:pnCyan:pvr1.0:cvnGOOGLE:ct3:cvr:
  dmi.product.name: Cyan
  dmi.product.version: 1.0
  dmi.sys.vendor: GOOGLE
  --- 
  ApportVersion: 2.20.3-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/hwC0D2', '/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', 
'/dev/snd/pcmC0D3p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] 
failed with exit code 1:
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.10
  HibernationDevice: RESUME=UUID=53fe7902-c347-4ff8-945d-a3e3de773a08
  InstallationDate: Installed on 2016-07-22 (13 days ago)
  InstallationMedia:
   
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 8087:0a2a Intel Corp. 
   Bus 001 Device 002: ID 0bda:57cf Realtek Semiconductor Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: GOOGLE Cyan
  Package: linux-image-4.4.0-33-generic 4.4.0-33.52
  PackageArchitecture: amd64
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-33-generic 
root=UUID=742e4082-264a-4459-93df-9ec07b41d5e8 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-33.52-generic 4.4.15
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-33-generic N/A
   linux-backports-modules-4.4.0-33-generic  N/A
   linux-firmware1.159
  Tags:  yakkety
  Uname: Linux 4.4.0-33-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 05/20/2016
  dmi.bios.vendor: coreboot
  dmi.chassis.type: 3
  dmi.chassis.vendor: GOOGLE
  dmi.modalias: 
dmi:bvncoreboot:bvr:bd05/20/2016:svnGOOGLE:pnCyan:pvr1.0:cvnGOOGLE:ct3:cvr:
  dmi.product.name: Cyan
  dmi.product.version: 1.0
  dmi.sys.vendor: GOOGLE

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

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


[Desktop-packages] [Bug 1845422] Re: Firefox don't start

2019-09-26 Thread VinsS
After creating a new profile with firefox -P, now I can launch firefox
with this new profile.

Of course without my markups and extensions.

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

Title:
  Firefox don't start

Status in firefox package in Ubuntu:
  New

Bug description:
  when I start Firefox nothing append.
  If I restart it, a message appears with says "Firefox is already running but 
not responding. Close the first session if you want open a new one".

  This problem concern the latest update (this morning) of firefox.

  I've also tried in a terminal with the option -g without any reaction.

  
  vincent@djoliba:~$ apt show firefox
  Package: firefox
  Version: 69.0.1+build1-0ubuntu0.18.04.1
  Priority: optional
  Section: web
  Origin: Ubuntu
  Maintainer: Ubuntu Mozilla Team 
  Bugs: https://bugs.launchpad.net/ubuntu/+filebug
  Installed-Size: 189 MB
  Provides: gnome-www-browser, iceweasel, www-browser
  Depends: lsb-release, libatk1.0-0 (>= 1.12.4), libc6 (>= 2.27), 
libcairo-gobject2 (>= 1.10.0), libcairo2 (>= 1.10.0), libdbus-1-3 (>= 1.9.14), 
libdbus-glib-1-2 (>= 0.78), libfontconfig1 (>= 2.12), libfreetype6 (>= 2.3.5), 
libgcc1 (>= 1:4.2), libgdk-pixbuf2.0-0 (>= 2.22.0), libglib2.0-0 (>= 2.31.8), 
libgtk-3-0 (>= 3.4), libpango-1.0-0 (>= 1.22.0), libpangocairo-1.0-0 (>= 
1.14.0), libstartup-notification0 (>= 0.8), libstdc++6 (>= 6), libx11-6, 
libx11-xcb1, libxcb-shm0, libxcb1, libxcomposite1 (>= 1:0.3-1), libxdamage1 (>= 
1:1.1), libxext6, libxfixes3, libxrender1, libxt6
  Recommends: xul-ext-ubufox, libcanberra0, libdbusmenu-glib4, 
libdbusmenu-gtk3-4
  Suggests: fonts-lyx
  Replaces: kubuntu-firefox-installer
  Task: ubuntu-desktop, kubuntu-desktop, kubuntu-full, xubuntu-desktop, 
lubuntu-gtk-desktop, lubuntu-desktop, ubuntustudio-desktop, 
ubuntukylin-desktop, ubuntu-mate-core, ubuntu-mate-desktop
  Xul-Appid: {ec8030f7-c20a-464f-9b0e-13a3a9e97384}
  Supported: 5y
  Download-Size: 50,3 MB
  APT-Manual-Installed: yes
  APT-Sources: http://be.archive.ubuntu.com/ubuntu bionic-updates/main amd64 
Packages
  Description: Le Navigateur Internet simple et sûr de Mozilla ..
  -

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

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


[Desktop-packages] [Bug 1845427] [NEW] [System Product Name, Realtek ALC887-VD, Green Headphone Out, Front] No sound at all

2019-09-26 Thread ajay khrolia
Public bug reported:

front green jack not working

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: alsa-base 1.0.25+dfsg-0ubuntu5
Uname: Linux 5.3.0-050300-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.9-0ubuntu7.7
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC1:  nascenture   3587 F pulseaudio
 /dev/snd/controlC0:  nascenture   3587 F pulseaudio
 /dev/snd/pcmC0D0p:   nascenture   3587 F...m pulseaudio
 /dev/snd/timer:  nascenture   3587 f pulseaudio
CurrentDesktop: ubuntu:GNOME
Date: Thu Sep 26 11:36:22 2019
InstallationDate: Installed on 2019-08-08 (49 days ago)
InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210)
PackageArchitecture: all
SourcePackage: alsa-driver
Symptom: audio
Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed
Symptom_Card: Built-in Audio - HDA Intel PCH
Symptom_Jack: Green Headphone Out, Front
Symptom_Type: No sound at all
Title: [System Product Name, Realtek ALC887-VD, Green Headphone Out, Front] No 
sound at all
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 09/14/2018
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 0304
dmi.board.asset.tag: Default string
dmi.board.name: PRIME H310M-CS R2.0
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: Rev X.0x
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 3
dmi.chassis.vendor: Default string
dmi.chassis.version: Default string
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0304:bd09/14/2018:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEH310M-CSR2.0:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: System Product Name
dmi.product.sku: SKU
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer
mtime.conffile..etc.modprobe.d.alsa-base.conf: 2019-09-16T18:10:26.699224

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


** Tags: amd64 apport-bug bionic

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

Title:
  [System Product Name, Realtek ALC887-VD, Green Headphone Out, Front]
  No sound at all

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  front green jack not working

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  Uname: Linux 5.3.0-050300-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7.7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  nascenture   3587 F pulseaudio
   /dev/snd/controlC0:  nascenture   3587 F pulseaudio
   /dev/snd/pcmC0D0p:   nascenture   3587 F...m pulseaudio
   /dev/snd/timer:  nascenture   3587 f pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Sep 26 11:36:22 2019
  InstallationDate: Installed on 2019-08-08 (49 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_Jack: Green Headphone Out, Front
  Symptom_Type: No sound at all
  Title: [System Product Name, Realtek ALC887-VD, Green Headphone Out, Front] 
No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/14/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0304
  dmi.board.asset.tag: Default string
  dmi.board.name: PRIME H310M-CS R2.0
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0304:bd09/14/2018:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEH310M-CSR2.0:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.sku: SKU
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer
  mtime.conffile..etc.modprobe.d.alsa-base.conf: 2019-09-16T18:10:26.699224

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

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


[Desktop-packages] [Bug 1794033] Re: i965: Failed to submit batchbuffer: Bad address

2019-09-26 Thread Bug Watch Updater
** Changed in: xserver-xorg-video-intel (Fedora)
   Status: Incomplete => Unknown

** Bug watch added: gitlab.freedesktop.org/mesa/mesa/issues #1680
   https://gitlab.freedesktop.org/mesa/mesa/issues/1680

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

Title:
   i965: Failed to submit batchbuffer: Bad address

Status in mesa package in Ubuntu:
  Confirmed
Status in xserver-xorg-video-intel package in Fedora:
  Unknown

Bug description:
  cpu: Intel® Core™ i5-7500 CPU @ 3.40GHz × 4 
  gpu: Intel® HD Graphics 630 (Kaby Lake GT2)
  00:00.0 Host bridge: Intel Corporation Intel Kaby Lake Host Bridge (rev 05)
  00:02.0 VGA compatible controller: Intel Corporation HD Graphics 630 (rev 04)
  00:08.0 System peripheral: Intel Corporation Skylake Gaussian Mixture Model
  xserver-xorg-video-intel:
Installed: 2:2.99.917+git20171229-1
Candidate: 2:2.99.917+git20171229-1
  ubuntu: 18.04 LTS bionic
  gnome: 3.28.2
  gdm3:
Installed: 3.28.2-0ubuntu1.4
Candidate: 3.28.2-0ubuntu1.4
  os type: 64 bit
  kernel: Linux eva1 4.15.0-30-generic #32-Ubuntu SMP Thu Jul 26 17:42:43 UTC 
2018 x86_64 x86_64 x86_64 GNU/Linux
  mesa-va-drivers:
Installed: 18.0.5-0ubuntu0~18.04.1
Candidate: 18.0.5-0ubuntu0~18.04.1

  from syslog:

  Sep 24 04:08:16 eva /usr/lib/gdm3/gdm-x-session[1170]: i965: Failed to submit 
batchbuffer: Bad address
  Sep 24 04:08:21 eva gnome-terminal-[2597]: gnome-terminal-server: Fatal IO 
error 11 (Resource temporarily unavailable) on X server :0.
  Sep 24 04:08:22 eva [2541]: update-notifier: Fatal IO error 11 (Resource 
temporarily unavailable) on X server :0.
  Sep 24 04:08:22 eva at-spi-bus-launcher[1274]: XIO:  fatal IO error 11 
(Resource temporarily unavailable) on X server ":0" 
   - but 
  (followed by pages upon pages of applications within gnome failing.)

  nothing in kern.log around that time.

  Singular gnome crash, taking down all applications running within it.
  Not yet reproduced. gdm successfully started a new session afterwards.
  Was definitely in a palermoon session on some website or other.

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

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


[Desktop-packages] [Bug 1794033]

2019-09-26 Thread Gitlab-migration
-- GitLab Migration Automatic Message --

This bug has been migrated to freedesktop.org's GitLab instance and has
been closed from further activity.

You can subscribe and participate further through the new bug through
this link to our GitLab instance:
https://gitlab.freedesktop.org/mesa/mesa/issues/1680.

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

Title:
   i965: Failed to submit batchbuffer: Bad address

Status in mesa package in Ubuntu:
  Confirmed
Status in xserver-xorg-video-intel package in Fedora:
  Unknown

Bug description:
  cpu: Intel® Core™ i5-7500 CPU @ 3.40GHz × 4 
  gpu: Intel® HD Graphics 630 (Kaby Lake GT2)
  00:00.0 Host bridge: Intel Corporation Intel Kaby Lake Host Bridge (rev 05)
  00:02.0 VGA compatible controller: Intel Corporation HD Graphics 630 (rev 04)
  00:08.0 System peripheral: Intel Corporation Skylake Gaussian Mixture Model
  xserver-xorg-video-intel:
Installed: 2:2.99.917+git20171229-1
Candidate: 2:2.99.917+git20171229-1
  ubuntu: 18.04 LTS bionic
  gnome: 3.28.2
  gdm3:
Installed: 3.28.2-0ubuntu1.4
Candidate: 3.28.2-0ubuntu1.4
  os type: 64 bit
  kernel: Linux eva1 4.15.0-30-generic #32-Ubuntu SMP Thu Jul 26 17:42:43 UTC 
2018 x86_64 x86_64 x86_64 GNU/Linux
  mesa-va-drivers:
Installed: 18.0.5-0ubuntu0~18.04.1
Candidate: 18.0.5-0ubuntu0~18.04.1

  from syslog:

  Sep 24 04:08:16 eva /usr/lib/gdm3/gdm-x-session[1170]: i965: Failed to submit 
batchbuffer: Bad address
  Sep 24 04:08:21 eva gnome-terminal-[2597]: gnome-terminal-server: Fatal IO 
error 11 (Resource temporarily unavailable) on X server :0.
  Sep 24 04:08:22 eva [2541]: update-notifier: Fatal IO error 11 (Resource 
temporarily unavailable) on X server :0.
  Sep 24 04:08:22 eva at-spi-bus-launcher[1274]: XIO:  fatal IO error 11 
(Resource temporarily unavailable) on X server ":0" 
   - but 
  (followed by pages upon pages of applications within gnome failing.)

  nothing in kern.log around that time.

  Singular gnome crash, taking down all applications running within it.
  Not yet reproduced. gdm successfully started a new session afterwards.
  Was definitely in a palermoon session on some website or other.

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

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