date:20190210

I no longer use FF as my main browser (too many bugs like this one).

JFTR, I just revisited this ticket and tried to reproduce it in bionic
with FF 56 and was unable to.

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

Title:
  scrolling full page faulty on handelsblatt.com

Status in firefox package in Ubuntu:
  Expired

Bug description:
  I am not sure if this is a bug in FF or faulty web programming on the
  part of handelsblatt.com but I come across it often enough (and IIRC
  also on other than the mentioned site) that is annoying.

  steps to reproduce:
  1) visit 
http://www.handelsblatt.com/politik/deutschland/krisenstaat/9546944.html
  2) scroll down with PgDn
  3) notice that some lines have scrolled off the screen that were not visible 
neither before and after the scroll

  The scroll is too far, one has to go back up a few lines with the up
  arrow.

  Launchpad sometimes exhibits a similar behaviour were upon entering
  the page and paging down the page ends up at "End", the end of the
  page.

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

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

[Desktop-packages] [Bug 1286537] Re: scrolling full page faulty on handelsblatt.com

It's quite well possible, of course, that it's simply the page that
changed and the underlying problem in FF is still present.  I don't know
and won't investigate any further.

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

Title:
  scrolling full page faulty on handelsblatt.com

Status in firefox package in Ubuntu:
  Expired

Bug description:
  I am not sure if this is a bug in FF or faulty web programming on the
  part of handelsblatt.com but I come across it often enough (and IIRC
  also on other than the mentioned site) that is annoying.

  steps to reproduce:
  1) visit 
http://www.handelsblatt.com/politik/deutschland/krisenstaat/9546944.html
  2) scroll down with PgDn
  3) notice that some lines have scrolled off the screen that were not visible 
neither before and after the scroll

  The scroll is too far, one has to go back up a few lines with the up
  arrow.

  Launchpad sometimes exhibits a similar behaviour were upon entering
  the page and paging down the page ends up at "End", the end of the
  page.

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

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

[Desktop-packages] [Bug 950843] Re: simple scan fails to scan. "unable to start scan" change scan ner gives no options

Pablo, I agree about the sad state of affairs.  The right place to vent
is at the manufacturers, mostly.  To up their Linux support.  Go vote
with your wallet.

Without the requested information, there's nothing we can do here, so
I'm re-closing.

** Changed in: sane-backends (Ubuntu)
   Status: Confirmed => Opinion

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

Title:
  simple scan fails to scan. "unable to start scan" change scan ner
  gives no options

Status in sane-backends package in Ubuntu:
  Opinion

Bug description:
  running 10.10
  epson stylus cx3200
  usb
  reboot of pc and printer/scanner tried.  
  same problem in 'xsane' and 'scanner utility' packages.
  the software used to work before i had to reinstall it.
...
  james@james-XL58laptop:~$ sane-find-scanner

# sane-find-scanner will now attempt to detect your scanner. If the
# result is different from what you expected, first make sure your
# scanner is powered up and properly connected to your computer.

# No SCSI scanners found. If you expected something different, make sure 
that
# you have loaded a kernel SCSI driver for your SCSI adapter.

  found USB scanner (vendor=0x04b8 [EPSON], product=0x0802 [USB MFP]) at 
libusb:006:002
# Your USB scanner was (probably) detected. It may or may not be supported 
by
# SANE. Try scanimage -L and read the backend's manpage.

# Not checking for parallel port scanners.

# Most Scanners connected to the parallel port or other proprietary ports
# can't be detected by this program.

# You may want to run this program as root to find all devices. Once you
# found the scanner devices, be sure to adjust access permissions as
# necessary.
  james@james-XL58laptop:~$ scanimage -L

  No scanners were identified. If you were expecting something different,
  check that the scanner is plugged in, turned on and detected by the
  sane-find-scanner tool (if appropriate). Please read the documentation
  which came with this software (README, FAQ, manpages).
  james@james-XL58laptop:~$ 
  

  ProblemType: Bug
  DistroRelease: Ubuntu 10.10
  Package: simple-scan 2.32.0-0ubuntu4
  ProcVersionSignature: Ubuntu 2.6.35-32.66-generic 2.6.35.14
  Uname: Linux 2.6.35-32-generic i686
  Architecture: i386
  Date: Fri Mar  9 13:25:52 2012
  DriverPackageVersions:
   libsane 1.0.21-2ubuntu2
   libsane-extras N/A
   hplip 3.10.6-1ubuntu10.2
   hpoj N/A
  EcryptfsInUse: Yes
  InstallationMedia: Ubuntu 10.04.4 LTS "Lucid Lynx" - Release i386 (20120214.2)
  MachineType: ASUSTeK Computer Inc. X58L
  PccardctlIdent:
   Socket 0:
 no product info available
  PccardctlStatus:
   Socket 0:
 no card
  ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.35-32-generic 
root=UUID=1adaa652-ac13-4a80-9382-d57361e69748 ro quiet splash
  ProcEnviron:
   LANG=en_GB.utf8
   SHELL=/bin/bash
  SourcePackage: simple-scan
  dmi.bios.date: 09/08/2008
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 201
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: X58L
  dmi.board.vendor: ASUSTeK Computer Inc.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: ATN12345678901234567
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK Computer Inc.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr201:bd09/08/2008:svnASUSTeKComputerInc.:pnX58L:pvr1.0:rvnASUSTeKComputerInc.:rnX58L:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr1.0:
  dmi.product.name: X58L
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK Computer Inc.

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

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

[Desktop-packages] [Bug 1184699] Re: Canon LIDE 110 can only scan once, then I need to replug the usb cable

I agree that this is a pretty serious issue (certainly for those
affected), with it being capable to destroy hardware, etc.

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

Title:
  Canon LIDE 110 can only scan once, then I need to replug the usb cable

Status in sane-backends package in Ubuntu:
  Confirmed

Bug description:
  I have a Canon LIDE 110 scanner which works by default on ubuntu 13.04. 
  The problem is after first scan, I can not scan for second time. I need to 
reconnect the USB cable to use the scanner again.

  # TEST 1 : without reconnecting the usb cable
  francois@pc:~$ scanimage -v > test1.jpg # success
  scanimage: scanning image of size 636x885 pixels at 8 bits/pixel
  scanimage: acquiring gray frame
  scanimage: min/max graylevel value = 0/255
  scanimage: read 562860 bytes in total
  # I don't unplug plug the usb cable.
  francois@pc:~$ scanimage -v > test2.jpg # FAIL
  scanimage: no SANE devices found

  # TEST 2 : reconnect usb cable between scan attempts
  francois@pc:~$ scanimage -v > test1.jpg # success
  scanimage: scanning image of size 636x885 pixels at 8 bits/pixel
  scanimage: acquiring gray frame
  scanimage: min/max graylevel value = 0/255
  scanimage: read 562860 bytes in total
  # I unplug and replug the usb cable.
  francois@pc:~$ scanimage -v > test2.jpg # SUCCESS
  scanimage: scanning image of size 636x885 pixels at 8 bits/pixel
  scanimage: acquiring gray frame
  scanimage: min/max graylevel value = 0/255
  scanimage: read 562860 bytes in total

  francois@pc:~$ dmesg # extract
  [  829.365158] usb 3-1: USB disconnect, device number 2
  [  834.935000] usb 3-1: new high-speed USB device number 4 using xhci_hcd
  [  834.952515] usb 3-1: New USB device found, idVendor=04a9, idProduct=1909
  [  834.952519] usb 3-1: New USB device strings: Mfr=1, Product=2, 
SerialNumber=0
  [  834.952522] usb 3-1: Product: CanoScan
  [  834.952524] usb 3-1: Manufacturer: Canon
  [ 1623.738811] usb 3-1: USB disconnect, device number 4
  [ 1623.739072] xhci_hcd :00:14.0: Slot 3 endpoint 6 not removed from BW 
list!
  [ 1625.528827] usb 3-1: new high-speed USB device number 5 using xhci_hcd
  [ 1625.546327] usb 3-1: New USB device found, idVendor=04a9, idProduct=1909
  [ 1625.546331] usb 3-1: New USB device strings: Mfr=1, Product=2, 
SerialNumber=0
  [ 1625.546334] usb 3-1: Product: CanoScan
  [ 1625.546336] usb 3-1: Manufacturer: Canon

  francois@pc:~$ uname -a && cat /etc/issue
  Linux pc 3.8.0-22-generic #33-Ubuntu SMP Thu May 16 15:17:14 UTC 2013 x86_64 
x86_64 x86_64 GNU/Linux
  Ubuntu 13.04 \n \l

  The problem was reported here by someone else :
  http://askubuntu.com/questions/278473/canon-lide-110-should-reconnect-
  usb-for-each-scan

  Thanks
  François

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

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

[Desktop-packages] [Bug 1184699] Re: Canon LIDE 110 can only scan once, then I need to replug the usb cable

I am truly sorry to have been silent for so long.

At this point, I can't do more than ask you to verify if this is still a
problem with bionic and/or cosmic.  I'm hoping it's fixed in a later
release and then we can hopefully backport a fix.

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

Title:
  Canon LIDE 110 can only scan once, then I need to replug the usb cable

Status in sane-backends package in Ubuntu:
  Confirmed

Bug description:
  I have a Canon LIDE 110 scanner which works by default on ubuntu 13.04. 
  The problem is after first scan, I can not scan for second time. I need to 
reconnect the USB cable to use the scanner again.

  # TEST 1 : without reconnecting the usb cable
  francois@pc:~$ scanimage -v > test1.jpg # success
  scanimage: scanning image of size 636x885 pixels at 8 bits/pixel
  scanimage: acquiring gray frame
  scanimage: min/max graylevel value = 0/255
  scanimage: read 562860 bytes in total
  # I don't unplug plug the usb cable.
  francois@pc:~$ scanimage -v > test2.jpg # FAIL
  scanimage: no SANE devices found

  # TEST 2 : reconnect usb cable between scan attempts
  francois@pc:~$ scanimage -v > test1.jpg # success
  scanimage: scanning image of size 636x885 pixels at 8 bits/pixel
  scanimage: acquiring gray frame
  scanimage: min/max graylevel value = 0/255
  scanimage: read 562860 bytes in total
  # I unplug and replug the usb cable.
  francois@pc:~$ scanimage -v > test2.jpg # SUCCESS
  scanimage: scanning image of size 636x885 pixels at 8 bits/pixel
  scanimage: acquiring gray frame
  scanimage: min/max graylevel value = 0/255
  scanimage: read 562860 bytes in total

  francois@pc:~$ dmesg # extract
  [  829.365158] usb 3-1: USB disconnect, device number 2
  [  834.935000] usb 3-1: new high-speed USB device number 4 using xhci_hcd
  [  834.952515] usb 3-1: New USB device found, idVendor=04a9, idProduct=1909
  [  834.952519] usb 3-1: New USB device strings: Mfr=1, Product=2, 
SerialNumber=0
  [  834.952522] usb 3-1: Product: CanoScan
  [  834.952524] usb 3-1: Manufacturer: Canon
  [ 1623.738811] usb 3-1: USB disconnect, device number 4
  [ 1623.739072] xhci_hcd :00:14.0: Slot 3 endpoint 6 not removed from BW 
list!
  [ 1625.528827] usb 3-1: new high-speed USB device number 5 using xhci_hcd
  [ 1625.546327] usb 3-1: New USB device found, idVendor=04a9, idProduct=1909
  [ 1625.546331] usb 3-1: New USB device strings: Mfr=1, Product=2, 
SerialNumber=0
  [ 1625.546334] usb 3-1: Product: CanoScan
  [ 1625.546336] usb 3-1: Manufacturer: Canon

  francois@pc:~$ uname -a && cat /etc/issue
  Linux pc 3.8.0-22-generic #33-Ubuntu SMP Thu May 16 15:17:14 UTC 2013 x86_64 
x86_64 x86_64 GNU/Linux
  Ubuntu 13.04 \n \l

  The problem was reported here by someone else :
  http://askubuntu.com/questions/278473/canon-lide-110-should-reconnect-
  usb-for-each-scan

  Thanks
  François

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

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

[Desktop-packages] [Bug 1776000] Re: gnome-control-center says "no bluetooth found" even though bluetooth is present and somewhat usable

I was swamped with other stuff and wasn't able to respond in time.  I'll
try catch, post the required information and then reopen.

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

Title:
  gnome-control-center says "no bluetooth found" even though bluetooth
  is present and somewhat usable

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

Bug description:
  I am running bionic and the gnome-control-center on the bluetooth tab
  tells me that "no bluetooth found" and that I should plug in a dongle
  to use bluetooth.  My computer has built-in bluetooth.

  I believe I am seeing what's being discussed at http://gnome-
  apps.13852.n7.nabble.com/No-Bluetooth-Found-Plug-in-a-dongle-to-use-
  Bluetooth-td68467.html especially the message by Bjørn Forsman, dated
  Dec 31 2016.

  $ ll /dev/rfkill
  crw-rw-r--+ 1 root root 10, 62 Mai 29 17:19 /dev/rfkill

  $ bluetoothctl
  [NEW] Controller 3C:77:E6:EC:91:4E work [default]
  [NEW] Device 20:A9:0E:1B:1B:84 alcatel POP 4
  Agent registered
  [bluetooth]# show
  Controller 3C:77:E6:EC:91:4E (public)
  Name: work
  Alias: work
  Class: 0x0010010c
  Powered: yes
  Discoverable: yes
  Pairable: yes
  UUID: Generic Attribute Profile (1801--1000-8000-00805f9b34fb)
  UUID: A/V Remote Control(110e--1000-8000-00805f9b34fb)
  UUID: OBEX File Transfer(1106--1000-8000-00805f9b34fb)
  UUID: Generic Access Profile(1800--1000-8000-00805f9b34fb)
  UUID: OBEX Object Push  (1105--1000-8000-00805f9b34fb)
  UUID: PnP Information   (1200--1000-8000-00805f9b34fb)
  UUID: IrMC Sync (1104--1000-8000-00805f9b34fb)
  UUID: A/V Remote Control Target (110c--1000-8000-00805f9b34fb)
  UUID: Vendor specific   (5005--1000-8000-0002ee01)
  UUID: Message Notification Se.. (1133--1000-8000-00805f9b34fb)
  UUID: Phonebook Access Server   (112f--1000-8000-00805f9b34fb)
  UUID: Message Access Server (1132--1000-8000-00805f9b34fb)
  Modalias: usb:v1D6Bp0246d0530
  Discovering: yes

  $ rfkill list all
  0: tpacpi_bluetooth_sw: Bluetooth
  Soft blocked: no
  Hard blocked: no
  1: tpacpi_wwan_sw: Wireless WAN
  Soft blocked: no
  Hard blocked: no
  2: phy0: Wireless LAN
  Soft blocked: no
  Hard blocked: no
  30: hci0: Bluetooth
  Soft blocked: no
  Hard blocked: no

  This is what I see in /var/log/syslog when trying to send a file from
  a paired phone.

  Jun  9 22:01:24 work obexd[18062]: CONNECT(0x0), (null)(0x)
  Jun  9 22:01:24 work obexd[18062]: CONNECT(0x0), (null)(0x0)
  Jun  9 22:01:24 work obexd[18062]: PUT(0x2), (null)(0x)
  Jun  9 22:01:24 work obexd[18062]: PUT(0x2), FORBIDDEN(0x43)
  Jun  9 22:01:24 work obexd[18062]: DISCONNECT(0x1), (null)(0x)
  Jun  9 22:01:24 work obexd[18062]: DISCONNECT(0x1), SUCCESS(0x20)
  Jun  9 22:01:24 work obexd[18062]: disconnected: Transport got disconnected
  Jun  9 22:01:24 work bluetoothd[17556]: Unable to get io data for Object 
Push: getpeername: Transport endpoint is not connected (107)

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

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

[Desktop-packages] [Bug 1248373] Re: gedit "Save as..." is disabled when file is opened read-only

[Expired for One Hundred Papercuts because there has been no activity
for 60 days.]

** Changed in: hundredpapercuts
   Status: Incomplete => Expired

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

Title:
  gedit "Save as..." is disabled when file is opened read-only

Status in One Hundred Papercuts:
  Expired
Status in gedit package in Ubuntu:
  Incomplete

Bug description:
  To replicate:
  1: Use firefox to download a file of a type that automatically opens 
read-only in gedit
  2: From gedit, try to save the file to another location using "Save as..." 
from the File menu.

  Both "Save" and "Save as..." are greyed out, but the ideal behaviour
  is to disable only "Save", leaving "Save as..." still enabled.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: gedit 3.8.3-0ubuntu3
  ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3
  Uname: Linux 3.11.0-12-generic x86_64
  ApportVersion: 2.12.5-0ubuntu2.1
  Architecture: amd64
  Date: Wed Nov  6 09:19:02 2013
  InstallationDate: Installed on 2013-08-19 (78 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  MarkForUpload: True
  SourcePackage: gedit
  UpgradeStatus: Upgraded to saucy on 2013-10-24 (12 days ago)

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

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

[Desktop-packages] [Bug 1614634] Re: Gnome Control Panel does not detect Bluetooth USB adapter

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

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

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

Title:
  Gnome Control Panel does not detect Bluetooth USB adapter

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

Bug description:
  I plugged in a working Bluetooth USB adpater, and the Bluetooth
  section of the Gnome Control Panel does not detect it. It continues to
  say "Plug in a dongle to use Bluetooth." I've tried other USB ports
  (this computer is new within the last 2 months), but none detect the
  adapter. It's a Sabrent USB adapter, found here:

  
https://www.amazon.com/dp/B00EAAAJWU/ref=pe_385040_30332190_TE_3p_M3T1_ST1_dp_1

  I'm not sure if I need some additional drivers or not.

  Ubuntu 16.04.1 LTS
  Release 16.04

  gnome-control-center:
Installed: 1:3.18.2-1ubuntu6
Candidate: 1:3.18.2-1ubuntu6
Version table:
   *** 1:3.18.2-1ubuntu6 500
  500 http://us.archive.ubuntu.com/ubuntu xenial/universe amd64 Packages
  100 /var/lib/dpkg/status

  I expected the Bluetooth adapter to allow Bluetooth to be turned on
  after it was plugged in. I tried rebooting the machine with the
  adapter plugged in and that didn't work either. Instead, nothing
  happened.

  Here is a similar, if not the same, issue reported on RedHat:

  https://bugzilla.redhat.com/show_bug.cgi?id=1321395

  Additional package information:

  bluez:
Installed: 5.37-0ubuntu5
Candidate: 5.37-0ubuntu5
Version table:
   *** 5.37-0ubuntu5 500
  500 http://us.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
  100 /var/lib/dpkg/status

  gnome-bluetooth:
Installed: 3.18.2-1ubuntu2
Candidate: 3.18.2-1ubuntu2
Version table:
   *** 3.18.2-1ubuntu2 500
  500 http://us.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
  100 /var/lib/dpkg/status

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

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

[Desktop-packages] [Bug 1764064] Re: Bluetooth audio connected but is not present in "sound input" parameter

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

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

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

Title:
  Bluetooth audio connected but is not present in "sound input"
  parameter

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

Bug description:
  In gnome-control-center, i can connect my bluetooth device.
  In ubuntu 17.10, this device was recognized in "sound input" from 
gnome-control-center, but now not in Ubuntu 18.04 beta.
  This is painfull.
  Thanks.

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

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

[Desktop-packages] [Bug 1750134] Re: The display arrangement doesn't persist after reboot

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

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

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

Title:
  The display arrangement doesn't persist after reboot

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

Bug description:
  Description
  ===

  What I expect to happen
  ---

  That the changes I've made in the display arrangement is the same
  after starting the computer as before shutting it down or rebooting.

  What actually happens
  -

  Both the display orientation and primary display option is restored
  after every startup. I've to change the settings at every startup.

  Steps to reproduce
  ==

  1. Start *Display*.
  2. Make any change in the display arrangement.
  3. Reboot or shut the computer down.
  4. Start the computer.
  5. The arrangement of the displays will be the same as before step 2.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-control-center 1:3.26.2-0ubuntu0.2
  ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Feb 17 13:04:32 2018
  InstallationDate: Installed on 2017-11-29 (79 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  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/1750134/+subscriptions

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

[Desktop-packages] [Bug 1787863] Re: gnome-control-center occasionally fails to launch after multiple tries

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

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

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

Title:
  gnome-control-center occasionally fails to launch after multiple tries

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

Bug description:
  Release: Ubuntu 18.04.1 LTS
  Package Version: 1:3.28.2-0ubuntu0.18.04.1
  Expected Behavior: Program should always launch upon request.
  Problematic Behavior: Attempting to launch this program causes the shell to 
display the loading indicator for an unusual amount of time, only to never 
display the program.

  Description: Upon launching this program through a terminal emulator,
  it never opens and never displays any output. Passing the verbose (-v)
  option with the program has the same result. When I launch it through
  the GUI, the shell displays the spinning circle (loading indicator)
  for an absurd amount of time. The program still does not open. This is
  a fresh install, so I restarted my computer. When launched again, the
  program opened and operated normally. However, upon closing the
  program and opening it again, it does not open up. Task management
  tools only show the process for a brief 3-5 seconds after requesting
  it to open and then it disappears. To my knowledge, this bug does not
  affect any other programs.

  Workaround:
  Entering the command
   killall gnome-control-center
  allows it to open again upon next launches.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-control-center 1:3.28.2-0ubuntu0.18.04.1
  ProcVersionSignature: Ubuntu 4.15.0-32.35-generic 4.15.18
  Uname: Linux 4.15.0-32-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  CurrentDesktop: communitheme:ubuntu:GNOME
  Date: Sun Aug 19 18:17:37 2018
  InstallationDate: Installed on 2018-08-19 (0 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  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/1787863/+subscriptions

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

[Desktop-packages] [Bug 1774901] Re: Ubuntu 16.04 atualized, then wifi no more

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

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

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

Title:
  Ubuntu 16.04 atualized, then wifi no more

Status in network-manager package in Ubuntu:
  Expired

Bug description:
  I use Ubuntu 18.04 LTS release 18.04, since its delivery, in dual boot
  with Windows 8.1, and its all ok. In may 28 I made a normal
  atualization so reboot, then wifi device not connected no more. I
  don´t have wired connection, only wifi, so I don´t know what to
  do.(I´m posting this by Windows, and wifi is connected.)

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

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

[Desktop-packages] [Bug 1750136] Re: Can't move displays when changing orientation

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

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

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

Title:
  Can't move displays when changing orientation

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

Bug description:
  Description
  ===

  What I expect to happen
  ---

  When I move the cursor to one of the displays in the display control
  panel and press down the left button I should be able to move the
  display.

  What actually happens
  -

  Now I have to single click on display 2 (don't know if this because
  it's the primary display, or simply because it got number 2 in its
  name) so it moves down before I can move and change display 3's
  orientation. See attached screencast for a demonstration of the
  problem.

  Steps to reproduce
  ==

  1. Start *Display*.
  2. Try to move display 3.
  3. Single click in display 2.
  4. Try to move display 3 again (and succeed).

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-control-center 1:3.26.2-0ubuntu0.2
  ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Feb 17 13:32:03 2018
  ExecutablePath: /usr/bin/gnome-control-center
  InstallationDate: Installed on 2017-11-29 (79 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  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/1750136/+subscriptions

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

[Desktop-packages] [Bug 1776000] Re: gnome-control-center says "no bluetooth found" even though bluetooth is present and somewhat usable

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

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

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

Title:
  gnome-control-center says "no bluetooth found" even though bluetooth
  is present and somewhat usable

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

Bug description:
  I am running bionic and the gnome-control-center on the bluetooth tab
  tells me that "no bluetooth found" and that I should plug in a dongle
  to use bluetooth.  My computer has built-in bluetooth.

  I believe I am seeing what's being discussed at http://gnome-
  apps.13852.n7.nabble.com/No-Bluetooth-Found-Plug-in-a-dongle-to-use-
  Bluetooth-td68467.html especially the message by Bjørn Forsman, dated
  Dec 31 2016.

  $ ll /dev/rfkill
  crw-rw-r--+ 1 root root 10, 62 Mai 29 17:19 /dev/rfkill

  $ bluetoothctl
  [NEW] Controller 3C:77:E6:EC:91:4E work [default]
  [NEW] Device 20:A9:0E:1B:1B:84 alcatel POP 4
  Agent registered
  [bluetooth]# show
  Controller 3C:77:E6:EC:91:4E (public)
  Name: work
  Alias: work
  Class: 0x0010010c
  Powered: yes
  Discoverable: yes
  Pairable: yes
  UUID: Generic Attribute Profile (1801--1000-8000-00805f9b34fb)
  UUID: A/V Remote Control(110e--1000-8000-00805f9b34fb)
  UUID: OBEX File Transfer(1106--1000-8000-00805f9b34fb)
  UUID: Generic Access Profile(1800--1000-8000-00805f9b34fb)
  UUID: OBEX Object Push  (1105--1000-8000-00805f9b34fb)
  UUID: PnP Information   (1200--1000-8000-00805f9b34fb)
  UUID: IrMC Sync (1104--1000-8000-00805f9b34fb)
  UUID: A/V Remote Control Target (110c--1000-8000-00805f9b34fb)
  UUID: Vendor specific   (5005--1000-8000-0002ee01)
  UUID: Message Notification Se.. (1133--1000-8000-00805f9b34fb)
  UUID: Phonebook Access Server   (112f--1000-8000-00805f9b34fb)
  UUID: Message Access Server (1132--1000-8000-00805f9b34fb)
  Modalias: usb:v1D6Bp0246d0530
  Discovering: yes

  $ rfkill list all
  0: tpacpi_bluetooth_sw: Bluetooth
  Soft blocked: no
  Hard blocked: no
  1: tpacpi_wwan_sw: Wireless WAN
  Soft blocked: no
  Hard blocked: no
  2: phy0: Wireless LAN
  Soft blocked: no
  Hard blocked: no
  30: hci0: Bluetooth
  Soft blocked: no
  Hard blocked: no

  This is what I see in /var/log/syslog when trying to send a file from
  a paired phone.

  Jun  9 22:01:24 work obexd[18062]: CONNECT(0x0), (null)(0x)
  Jun  9 22:01:24 work obexd[18062]: CONNECT(0x0), (null)(0x0)
  Jun  9 22:01:24 work obexd[18062]: PUT(0x2), (null)(0x)
  Jun  9 22:01:24 work obexd[18062]: PUT(0x2), FORBIDDEN(0x43)
  Jun  9 22:01:24 work obexd[18062]: DISCONNECT(0x1), (null)(0x)
  Jun  9 22:01:24 work obexd[18062]: DISCONNECT(0x1), SUCCESS(0x20)
  Jun  9 22:01:24 work obexd[18062]: disconnected: Transport got disconnected
  Jun  9 22:01:24 work bluetoothd[17556]: Unable to get io data for Object 
Push: getpeername: Transport endpoint is not connected (107)

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

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

[Desktop-packages] [Bug 1789914] Re: Bluetooth mouse does not function in Ubuntu after pairing in Settings

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

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

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

Title:
  Bluetooth mouse does not function in Ubuntu after pairing in Settings

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

Bug description:
  Bluetooth mouse does not function in Ubuntu after pairing in Settings

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-control-center 1:3.28.2-0ubuntu0.18.04.2
  ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18
  Uname: Linux 4.15.0-33-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Aug 30 10:23:00 2018
  InstallationDate: Installed on 2018-08-17 (13 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-control-center
  UpgradeStatus: 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/1789914/+subscriptions

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

[Desktop-packages] [Bug 1734580] Re: gnome-control-center details user tab loads slowly

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

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

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

Title:
  gnome-control-center details user tab loads slowly

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

Bug description:
  The Users tab to load pretty much instantly but there is a 4s load
  time.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-control-center 1:3.26.1-0ubuntu5
  ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8
  Uname: Linux 4.13.0-17-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.5
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Nov 27 01:09:04 2017
  InstallationDate: Installed on 2017-10-20 (37 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  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/1734580/+subscriptions

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

[Desktop-packages] [Bug 1768754] Re: Applications are muted (silent) but system sounds work

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

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

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

Title:
  Applications are muted (silent) but system sounds work

Status in pulseaudio package in Ubuntu:
  Expired

Bug description:
  How to reproduce this bug:

  * Connect a laptop to a dock, which is connected to a screen with an HDMI / 
DisplayPort cable.
  * Then configure the sound to exit through the cable connecting the screen.
  * Turn off the computer
  * Take it out of the dock
  * Turn on the computer

  Then, the sound automatically switches to the audio output of the
  laptop. System sounds work well, such as the bell of output volume
  slider or the test speaker buttons “front left” or “front right”.
  Unfortunately, no more applications can produce a sound.

  Graphically, applications react normally, we can see their connections
  with pulse audio in the applications tab of the sound settings. But no
  sound comes out of the speakers.

  Workaround :
  * Connect an alternative audio output, such as a Bluetooth headset
  * Select it in the “Choose a device for sound output:” option
  * Switch back to the internal audio speakers
  * Et voilà !

  If it help, my laptop is a “HP Zbook G2” sometime connected to a “HP
  2012 230W Docking Station”

  Thank you for your attention.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-control-center 1:3.28.1-0ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Thu May  3 09:21:01 2018
  EcryptfsInUse: Yes
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-control-center
  UpgradeStatus: Upgraded to bionic on 2018-04-24 (8 days ago)

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

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

[Desktop-packages] [Bug 1797936] Re: Control Center->Disks cannot create ext4 partition on 5 TB external USB drive

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

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

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

Title:
  Control Center->Disks cannot create ext4 partition on 5 TB external
  USB drive

Status in gnome-disk-utility package in Ubuntu:
  Expired

Bug description:
  I deleted the pre-existing NTFS and got a drive with all space
  unallocated. When I tried to create an ext4 partition, I got an error
  about the size of the partition.

  Closed Control Center->Disks and used gParted. No problem creating the
  ext4 partition.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-disk-utility 3.28.3-0ubuntu1~18.04.1
  ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18
  Uname: Linux 4.15.0-36-generic x86_64
  NonfreeKernelModules: ufsd
  ApportVersion: 2.20.9-0ubuntu7.4
  Architecture: amd64
  CurrentDesktop: MATE
  Date: Sat Oct 13 15:40:29 2018
  ExecutablePath: /usr/bin/gnome-disks
  InstallationDate: Installed on 2018-07-06 (99 days ago)
  InstallationMedia: Ubuntu-MATE 18.04 LTS "Bionic Beaver" - Release amd64 
(20180426)
  ProcEnviron:
   XDG_RUNTIME_DIR=
   SHELL=/bin/bash
   LANGUAGE=en_US
   PATH=(custom, no user)
   LANG=en_US.UTF-8
  SourcePackage: gnome-disk-utility
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1799259] Re: Online Accounts imap does not support plain

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

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

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

Title:
  Online Accounts imap does not support plain

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

Bug description:
  When I try to log in with IMAP It does not go and alerts that it does
  not support plain.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-control-center 1:3.28.2-0ubuntu0.18.04.2
  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: Mon Oct 22 09:21:51 2018
  ExecutablePath: /usr/bin/gnome-control-center
  InstallationDate: Installed on 2018-10-18 (4 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  ProcEnviron:
   XDG_RUNTIME_DIR=
   SHELL=/bin/bash
   PATH=(custom, no user)
   LANG=en_US.UTF-8
  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-online-accounts/+bug/1799259/+subscriptions

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

[Desktop-packages] [Bug 1807076] Re: gnome-control-center doesn't start

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

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

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

Title:
  gnome-control-center doesn't start

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

Bug description:
  gnome-control-center doesn't start. There is no crash, core dump, etc.

  This bit in syslog (/var/log/syslog) gives us some information:

  gnome-control-c[2962]: invalid unclassed pointer in cast to 'GtkWindow'
  gnome-control-c[2962]: gtk_window_present_with_time: assertion 'GTK_IS_WINDOW 
(window)' failed

  Actually something similar has been seen already in the past but it
  hasn't been resolved:

  https://bugs.launchpad.net/ubuntu/+source/gnome-control-
  center/+bug/1745846

  I might not be the only person affected:

  https://askubuntu.com/questions/1094442/gnome-control-center-
  disappears-on-ubuntu-18-10-after-repostioning-ubuntu-
  dock/1098815#1098815

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-control-center 1:3.28.2-0ubuntu0.18.04.2
  ProcVersionSignature: Ubuntu 4.15.0-42.45-generic 4.15.18
  Uname: Linux 4.15.0-42-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  CurrentDesktop: GNOME-Flashback:GNOME
  Date: Thu Dec  6 11:08:42 2018
  InstallationDate: Installed on 2018-11-26 (9 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  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/1807076/+subscriptions

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

[Desktop-packages] [Bug 1780790] Re: Menus, tooltips and dropdowns are often misplaced on screen

2019-02-10 Thread Bug Watch Updater

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

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

On 2018-10-16T10:43:47+00:00 Pedro Côrte-Real wrote:

Created attachment 9017453
Screenshot of the first issue

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

Steps to reproduce:

I can reproduce this frequently but not yet on command. What I'm doing
is normal usage:

- Entering data into the location bar which dropdowns the list of options
- Using the right click and mouseover to open tooltips and dropdown menus on
pages

I'm using gnome-shell 3.28.3-0ubuntu0.18.04.2 on Ubuntu 18.04. Firefox
is 62.0.3+build1-0ubuntu0.18.04.1. I've had the issue happen in all
versions of firefox and gnome shell in Ubuntu 18.04 so far. I did a
small test with Unity and couldn't reproduce the issue yet but since it
doesn't happen 100% of the time longer testing would be required to make
sure it's a gnome-shell specific issue.

Actual results:

Two things are happening that may be separate bugs or not:

- When using an external screen placed on top of the internal one with
firefox maximized on the internal screen the URL bar's dropdown would
consistently appear on the external screen, completely outside the
firefox window, instead of the normal location. Screenshot is attached.

- In what appears to be random chance tooltips and menus are often
misplaced on screen. It's common but not fully reproducible. What I see
is right-clicking an element on a page or hovering over a link and
having the menu/tooltip show up somewhere different on the page. Doing
it again immediately after often results in it appearing in the right
place the second time. I haven't gotten a screenshot yet.

Expected results:

- The dropdown appearing right below the URL bar
- The menus and tooltips appearing at the mouse location

Reply at:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1780790/comments/7

On 2018-10-19T12:07:32+00:00 Daniel-aschilean wrote:

I verified this issue on Ubuntu 18.04 with FF 64.0a1 (2018-10-19) (64-bit) and
I cannot reproduce it.
Can you please test this in safe mode? Here is a link that can help you:
https://goo.gl/AR5o9d.
I think it will be a good idea to retest this on the latest Firefox Nightly.
Here is a link form where you can download it: https://nightly.mozilla.org.
If you still have the issue please create a new profile, you have the steps
here:
https://support.mozilla.org/en-US/kb/profile-manager-create-and-remove-firefox-profiles?redirectlocale=en-US=Managing-profiles#w_starting-the-profile-manager

Reply at:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1780790/comments/9

On 2018-10-19T15:19:12+00:00 Pedro Côrte-Real wrote:

It's natural that you can't reproduce this at will. I can't either.
Unfortunately the sequence of steps needed to reproduce this is not yet
clear to me. I've been trying to find out what they are but don't have
any conclusions yet. With that in mind, testing different versions or
profiles is hard to do conclusively.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1780790/comments/10

On 2018-10-21T07:40:30+00:00 Sledru wrote:

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

Reply at:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1780790/comments/11

On 2018-10-21T19:56:41+00:00 Sledru wrote:

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

Reply at:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1780790/comments/12

On 2019-02-10T19:03:03+00:00 Pedro Côrte-Real wrote:

I've reproduced the issue in a new session in Firefox 65.0. I used
Firefox sync to get my stuff over. Testing with a fully empty session is
harder because I need bookmarks and other stuff to be able to use the
browser and this doesn't happen at will.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1780790/comments/13

** Changed in: firefox
Status: Unknown => Confirmed

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

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

Title:
Menus, tooltips and dropdowns are often misplaced on screen

Status in Mozilla Firefox:
Confirmed
Status in

[Desktop-packages] [Bug 1430561] Re: hp-plugin crashes with error: Python gobject/dbus may be not installed

2019-02-10 Thread Pavel Zaikin

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

Linux Min 19.1
HP LJ p1505 

$ hp-plugin -i -g

hp-plugin[1137]: debug: Validating /home/pz/.hplip/hplip-3.19.1-plugin.run with 
/home/pz/.hplip/hplip-3.19.1-plugin.run.asc signature file
Receiving digital keys: /usr/bin/gpg --homedir /home/pz/.hplip/.gnupg 
--no-permission-warning --keyserver pgp.mit.edu --recv-keys 
0x4ABA2F66DBD5A95894910E0673D770CDA59047B9
hp-plugin[1137]: debug: gpg: keyserver receive failed: No data

hp-plugin[1137]: debug: gpg: keyserver receive failed: No data

()
error: Unable to recieve key from keyserver

...

Plugin installation failed
error: Plugin installation failed

Done.
hp-plugin[1137]: debug: Removing ./plugin_tmp cmd = rm -rf ./plugin_tmp 
hp-plugin[1137]: debug: Exception: 4 (Unknown/invalid device-uri field)
hp-plugin[1137]: debug: Exception: 4 (Unknown/invalid device-uri field)
hp-plugin[1137]: debug: Exception: 4 (Unknown/invalid device-uri field)

Done.
hp-plugin[1137]: debug: Unlocking: /var/hp-plugin.lock

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

Title:
  hp-plugin crashes with error: Python gobject/dbus may be not installed

Status in HPLIP:
  Confirmed
Status in One Hundred Papercuts:
  Confirmed
Status in hplip package in Ubuntu:
  Confirmed

Bug description:
  When trying to configure an HP LaserJet P1102w, when running hp-plugin
  I get errors and can not proceed:

  nessita@miro:~$ hp-plugin
  error: Unable to locate models.dat file

  HP Linux Imaging and Printing System (ver. 3.15.2)
  Plugin Download and Install Utility ver. 2.1

  Copyright (c) 2001-15 Hewlett-Packard Development Company, LP
  This software comes with ABSOLUTELY NO WARRANTY.
  This is free software, and you are welcome to distribute it
  under certain conditions. See COPYING file for more details.

  Checking for network connection...
  Downloading plug-in from: 
  Receiving digital keys: /usr/bin/gpg --homedir /home/nessita/.hplip/.gnupg 
--no-permission-warning --keyserver pgp.mit.edu --recv-keys 0xA59047B9
  Creating directory plugin_tmp
  Verifying archive integrity... All good.
  Uncompressing HPLIP 3.15.2 Plugin Self Extracting 
Archive...
  Error importing HPLIP modules.  Is HPLIP installed?
  error: Python gobject/dbus may be not installed
  error: Plug-in install failed.

  Done.
  nessita@miro:~$

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: hplip 3.15.2-0ubuntu3
  ProcVersionSignature: Ubuntu 3.19.0-7.7-generic 3.19.0
  Uname: Linux 3.19.0-7-generic x86_64
  ApportVersion: 2.16.2-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue Mar 10 19:23:41 2015
  InstallationDate: Installed on 2014-11-30 (100 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1)
  Lpstat: device for Laserjet: ipp://NPI2E6620.local:631/printers/Laserjet
  MachineType: LENOVO 3249CTO
  Papersize: letter
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-7-generic 
root=UUID=30425f63-143e-4183-aa37-394415c60a42 ro quiet splash vt.handoff=7
  SourcePackage: hplip
  UpgradeStatus: Upgraded to vivid on 2015-02-09 (29 days ago)
  dmi.bios.date: 10/26/2010
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 6QET61WW (1.31 )
  dmi.board.name: 3249CTO
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Available
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvr6QET61WW(1.31):bd10/26/2010:svnLENOVO:pn3249CTO:pvrThinkPadX201:rvnLENOVO:rn3249CTO:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 3249CTO
  dmi.product.version: ThinkPad X201
  dmi.sys.vendor: LENOVO

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

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

[Desktop-packages] [Bug 220263]

2019-02-10 Thread Pedro Côrte-Real

I hit this bug today by choosing the dark Adwaita theme in Gnome 3.28
and Firefox 65.0. It's amazing that this is an 18 year old bug. I found
it surprising the system theme did anything to webpages and had two
consecutive surprises:

- First setting the system theme to Adwaita-dark changed the Firefox theme. 
That makes sense. What was surprising was that the Firefox theme then changed 
the content of the web pages. My mental model of a browser is that within the 
page view it's a different world and there's no reason for the web to look 
different to match the browser chrome or the system theme.
- Because I didn't actually like the dark version of Firefox I switched it to 
the Light theme manually (webpages are usually light colored and so dark chrome 
in browsers looks weird). And yet even after doing this pages still had dark 
buttons and input areas. That was even stranger. Now Firefox had a light theme 
and yet the webpages were still picking up broken colors from the system theme 
inconsistent with the Firefox chrome theme.

I fixed this after some web searches by setting "widget.content.gtk-
theme-override:Adwaita". That at least sets a light theme for UI
controls and is back to looking reasonable. I found that in bug #1283086
which seems to be a 3 year old duplicate of this 18 year old bug. The
proposal for removal of all native theming in #1411425 makes perfect
sense.

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

Title:
  Bad Firefox integration with dark themes

Status in Mozilla Firefox:
  Fix Released
Status in XULRunner:
  Confirmed
Status in firefox package in Ubuntu:
  Triaged

Bug description:
  I'm using Mozilla Firefox 3 Beta 5 on Ubuntu 8.04 with a dark theme.
  Now I see all the input boxes and buttons filled with grey colour.
  This happened even with Firefox 2, but I solved that problem with a
  quick guide under the comment "firefox fix" by Proton at the bottom of
  this page: http://www.gnome-
  look.org/content/show.php/Grey+Neu?content=60824

  In Firefox 3 I can't correct this problem.

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

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

[Desktop-packages] [Bug 1815284] Re: Middle click down opens file

2019-02-10 Thread Cody Skinner

Not sure if this is a bug or expected behavior for Nautilus now.
Can confirm that the middle-mouse button does open a file with a single click. 
Both the left or middle mouse buttons can drag and drop a file by moving the 
file, not copying the file. No option appears to select which method to use.

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

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

Title:
  Middle click down opens file

Status in nautilus package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu 18.08 here.

  In Ubuntu 16.04 I could middle click on a file in Nautilus then drag
  and drop it to another folder. After that a small dialog appeared if I
  want to copy or move the file.

  Now when I press middle click on a file, the file opens immediately
  and although I can move it to another folder, there's no choice if I
  want to copy or move the file.

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

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

[Desktop-packages] [Bug 1815395] [NEW] GVFS-SMB write problems to SMB2 shares

2019-02-10 Thread Scott A. Wozny

Public bug reported:

Summary:

I believe there’s a bug in GVFS-SMB (or its implementation in Nautilus)
that manifests when writing to SMB2 shares.  It occurs inconsistently
(but enough to be annoying) in everyday use, but it can be replicated
consistently with a simple echo command redirected to a file on the
share.  This doesn’t happen when using the ‘mount’ command to connect to
SMB2 shares.  It also doesn’t happen when making an SMB1 connection
through Nautilus OR mount.  I’ve also tested this against 2 different
SMB servers (a Synology DS216J and a share on a Win7 Pro system) and the
results are consistent so I don’t believe it’s a server side issue.

I don’t know enough about this part of the system to identify where the
issue is or fix it, but I’ve included data below to show the basis for
my assertions above.  The workaround is either going back to SMB1 or
mounting my shares with the mount command, but I was hoping someone
could take this on and fix it long-term.  As Microsoft progressively
phases out SMB1, I think this will eventually become a wider scale
problem so now would be an opportune time to address it.  If there’s any
further data I can provide, please let me know.

Also, I’m sorry this bug report is so long, but I’m erring on the side
of too much detail rather than too little.

Detail:

On my Ubuntu 18.04 system, when I attempt to echo a string into a file
on a GVFS mounted share (left hand nav of Nautilus + Other Locations)
and that share is configured to SMB1 (client side left to negotiate,
server side locked to SMB1) this works as expected.  I tested against
SMB shares on both a Synology Diskstation DS216J NAS and a Windows 7
Professional workstation. When I was on Ubuntu 16.04 that was SMB1 only
out of the box I didn’t know this problem even existed.  Now that I’m on
Ubuntu 18.04 and my share was willing to make connection at SMB2 I
started to have weird, inconsistent disk problems.  Much troubleshooting
and analysis later, I can recreate this issue consistently with a simple
echo command to a file on the share.

To the SMB share on a Synology Diskstation NAS set to SMB1:

echo "This is a test." > /run/user/1000/gvfs/smb-
share\:server\=diskstation\,share\=fileshare/Test-File-SMB1-GVFS-NAS.txt

The command executes with no feedback (other than the return of the
prompt awaiting the next command) and the file of the name specified
with the contents specified appears at the root of the NAS file share.

To the SMB share on a Windows 7 Professional workstation set to SMB1:

echo "This is a test." > /run/user/1000/gvfs/smb-
share\:server\=hp_laptop\,share\=videos/Test-File-SMB1-GVFS-Win7.txt

The command also executes with no feedback (other than the return of the
prompt awaiting the next command) and the file of the name specified
with the contents specified appears at the root of the “videos” file
share on the Win7 workstation.

I also took PCAPs of this occurring (attached).  What they show is about
what I would expect for this operation.  Client SMB pings the server in
packet 1 who responds in packet 2, queries info on the folder in packet
4 and gets some basic info back in packet 5, queries the filename (to
make sure it doesn’t already exist) several times (not sure why), each
time getting a name not found reply in packets 6 through 17, then
creates the file in packet 18, gets back a success message in packet 19,
queries info on the new file in packet 20, gets a success response in
packet 21, writes the contents in packet 22, gets a good response in
packet 23, queries the file one more time (presumably to make sure the
new size is good) in packet 24, gets a response with the info in packet
25, requests the handle be closed in packet 26, and gets an OK to that
in packet 27.

This is all wonderful.  Perhaps slightly inefficient, but I don’t know
what’s going on under the hood, so who am I to judge?  When I switch to
SMB2 on the server side and reconnect via GVFS using Nautilus, things
fall apart.

To the SMB share on a Synology Diskstation NAS set to SMB2:

echo "This is a test." > /run/user/1000/gvfs/smb-
share\:server\=diskstation\,share\=fileshare/Test-File-SMB2-GVFS-NAS.txt

returns

bash: /run/user/1000/gvfs/smb-share:server=diskstation,share=fileshare
/Test-File-SMB2-GVFS-NAS.txt: Invalid argument

The file is where I expected it, but it is 0 bytes.

To the SMB share on a Windows 7 Professional workstation set to SMB2:

echo "This is a test." > /run/user/1000/gvfs/smb-
share\:server\=hp_laptop\,share\=videos/Test-File-SMB2-GVFS-Win7.txt

returns

bash: /run/user/1000/gvfs/smb-share:server=hp_laptop,share=videos/Test-
File-SMB2-GVFS-Win7.txt: Invalid argument

Again, the file is there in the right location, but it is 0 bytes.

Going to take a look at the PCAPs, it’s pretty clear what’s happened,
but less clear why.  The PCAPs were consistent between the NAS and the
Win7 Pro workstation.  So the client requests a file with no name
(presumably as shortcut for pwd) be opened in

[Desktop-packages] [Bug 1815391] Re: simple-scan crashed with SIGSEGV in g_closure_invoke()

2019-02-10 Thread Apport retracing service

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

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

** Attachment removed: "CoreDump.gz"
   
https://bugs.launchpad.net/bugs/1815391/+attachment/5237536/+files/CoreDump.gz

** Attachment removed: "Disassembly.txt"
   
https://bugs.launchpad.net/bugs/1815391/+attachment/5237539/+files/Disassembly.txt

** Attachment removed: "ProcMaps.txt"
   
https://bugs.launchpad.net/bugs/1815391/+attachment/5237547/+files/ProcMaps.txt

** Attachment removed: "ProcStatus.txt"
   
https://bugs.launchpad.net/bugs/1815391/+attachment/5237549/+files/ProcStatus.txt

** Attachment removed: "Registers.txt"
   
https://bugs.launchpad.net/bugs/1815391/+attachment/5237550/+files/Registers.txt

** Attachment removed: "Stacktrace.txt"
   
https://bugs.launchpad.net/bugs/1815391/+attachment/5237551/+files/Stacktrace.txt

** Attachment removed: "ThreadStacktrace.txt"
   
https://bugs.launchpad.net/bugs/1815391/+attachment/5237552/+files/ThreadStacktrace.txt

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

** Information type changed from Private to Public

** Tags removed: need-amd64-retrace

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

Title:
  simple-scan crashed with SIGSEGV in g_closure_invoke()

Status in simple-scan package in Ubuntu:
  New

Bug description:
  Open app, wait to find scanner: HP 8740, app closes, and does not find
  HP 8740 scanner.

  ProblemType: Crash
  DistroRelease: Ubuntu 19.04
  Package: simple-scan 3.31.90-0ubuntu2
  ProcVersionSignature: Ubuntu 4.19.0-12.13-generic 4.19.18
  Uname: Linux 4.19.0-12-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.10-0ubuntu20
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Feb 10 18:04:03 2019
  ExecutablePath: /usr/bin/simple-scan
  InstallationDate: Installed on 2019-02-10 (0 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190210)
  MachineType: HP HP Pavilion Notebook
  ProcCmdline: simple-scan
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.19.0-12-generic 
root=UUID=f32dac26-880e-4c7a-bd3b-8008302bccc8 ro quiet splash vt.handoff=1
  SegvAnalysis:
   Segfault happened at: 0x55696844c844:mov0x18(%rbp),%rcx
   PC (0x55696844c844) ok
   source "0x18(%rbp)" (0x0018) not located in a known VMA region (needed 
readable region)!
   destination "%rcx" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SimpleScanLog:
   
  SourcePackage: simple-scan
  StacktraceTop:
   ?? ()
   ?? ()
   ?? ()
   g_closure_invoke () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0
   ?? () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0
  Title: simple-scan crashed with SIGSEGV in g_closure_invoke()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  dmi.bios.date: 06/22/2018
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.48
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 8217
  dmi.board.vendor: HP
  dmi.board.version: 83.72
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.48:bd06/22/2018:svnHP:pnHPPavilionNotebook:pvrType1ProductConfigId:rvnHP:rn8217:rvr83.72:cvnHP:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV HP Pavilion
  dmi.product.name: HP Pavilion Notebook
  dmi.product.sku: Z7Y92UA#ABA
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: HP

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/simple-scan/+bug/1815391/+subscriptions

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

[Desktop-packages] [Bug 1430339] Re: fc-match Ryumin should return Mincho(serif) font in ja locale

I am on bionic now and FWIW, the sample supplied by Shibata-San still
looks more like his "before fixed" screenshot, at least in the browser
(I am using Vivaldi).  Is this really fixed?  Or is this just a browser-
specific bug?

** Attachment added: "screenshot from Vivaldi"
   
https://bugs.launchpad.net/ubuntu/+source/fonts-takao/+bug/1430339/+attachment/5237554/+files/vivaldi-ryumin.png

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

Title:
  fc-match Ryumin should return Mincho(serif) font in ja locale

Status in Ubuntu Translations:
  Fix Released
Status in fonts-takao package in Ubuntu:
  Fix Released

Bug description:
  Ryumin and Gothic-BBB are generic font names for serif/sans-serif like
  Arial/Times new roman. fonts-takao-mincho has a rule[1] to offer
  substitute for Ryumin, however `fc-match Ryumin` does not return
  fonts-takao-mincho(serif), it returns fonts-takao-gothic(sans-serif)
  instead.

  Expected result:
  $ fc-match Ryumin
  fonts-japanese-mincho.ttf: "TakaoPMincho" "Regular"

  Actual result:
  $ fc-match Ryumin
  fonts-japanese-gothic.ttf: "Takao Pゴシック" "Regular"

  
  [1]
  /etc/fonts/conf.d/65-fonts-takao-mincho.conf
   21 
   22 
   23 Ryumin
   24 
   25 
   26 Takao P明朝
   27 
   28 

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: fonts-takao-mincho 003.02.01-9ubuntu2
  ProcVersionSignature: Ubuntu 3.19.0-7.7-generic 3.19.0
  Uname: Linux 3.19.0-7-generic x86_64
  ApportVersion: 2.16.2-0ubuntu1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue Mar 10 22:41:44 2015
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2015-02-28 (9 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Alpha amd64 (20150228)
  PackageArchitecture: all
  SourcePackage: fonts-takao
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1430339] Re: fc-match Ryumin should return Mincho(serif) font in ja locale

** Attachment added: "screenshot from evince"
   
https://bugs.launchpad.net/ubuntu/+source/fonts-takao/+bug/1430339/+attachment/5237555/+files/evince-ryumin.png

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

Title:
  fc-match Ryumin should return Mincho(serif) font in ja locale

Status in Ubuntu Translations:
  Fix Released
Status in fonts-takao package in Ubuntu:
  Fix Released

Bug description:
  Ryumin and Gothic-BBB are generic font names for serif/sans-serif like
  Arial/Times new roman. fonts-takao-mincho has a rule[1] to offer
  substitute for Ryumin, however `fc-match Ryumin` does not return
  fonts-takao-mincho(serif), it returns fonts-takao-gothic(sans-serif)
  instead.

  Expected result:
  $ fc-match Ryumin
  fonts-japanese-mincho.ttf: "TakaoPMincho" "Regular"

  Actual result:
  $ fc-match Ryumin
  fonts-japanese-gothic.ttf: "Takao Pゴシック" "Regular"

  
  [1]
  /etc/fonts/conf.d/65-fonts-takao-mincho.conf
   21 
   22 
   23 Ryumin
   24 
   25 
   26 Takao P明朝
   27 
   28 

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: fonts-takao-mincho 003.02.01-9ubuntu2
  ProcVersionSignature: Ubuntu 3.19.0-7.7-generic 3.19.0
  Uname: Linux 3.19.0-7-generic x86_64
  ApportVersion: 2.16.2-0ubuntu1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue Mar 10 22:41:44 2015
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2015-02-28 (9 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Alpha amd64 (20150228)
  PackageArchitecture: all
  SourcePackage: fonts-takao
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1767817] Re: Full text search does not work

2019-02-10 Thread Balazs Pere

Does anybody know what to change in the source code to made FTS work? I
can compile and install it...at my own risk.

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

Title:
  Full text search does not work

Status in nautilus package in Ubuntu:
  Confirmed

Bug description:
  Background: I have installed Tracker. It has finished indexing. I can
  also use Tracker's command line interface to search by content.

  1.

  Description:  Ubuntu 18.04 LTS
  Release:  18.04

  2.

  nautilus:
Installed: 1:3.26.3-0ubuntu4
Candidate: 1:3.26.3-0ubuntu4
Version table:
   *** 1:3.26.3-0ubuntu4 500
  500 http://fi.archive.ubuntu.com/ubuntu bionic/main amd64 Packages
  100 /var/lib/dpkg/status

  3. I expect to be able to search files by content from Nautilus,
  because this feature worked in 17.10.

  4. I get no results from full text search unless the search matches
  file names.

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

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

Re: [Desktop-packages] [Bug 1181666] Re: gnome-shell randomly blocks mouse clicks from working in app windows

2019-02-10 Thread Scott Palmer

The solution until this is solved is to use something other than gnome
shell as far as I know.  Mint Cinnamon and Elementary are both popular
alternatives.

On Sun, Feb 10, 2019, 1:29 PM Adrian <1181...@bugs.launchpad.net wrote:

> I am facing the same issue in Ubuntu 18.10. The super key randomly stops
> working and I loose control of all windows except for the active window,
> which in some cases also stops working and cannot even do clicks there.
> The workaround I found is to close all windows, lock the screen and the
> problem solves for 5-10 min or so. But this is clearly impractical and I
> can't really go on like this any further. I re-installed the OS but it
> didn't solve the issue. I have a Lenovo T430s if that helps. Does anyone
> found a solution to this yet? I'd appreciate it very much!
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1181666
>
> Title:
>   gnome-shell randomly blocks mouse clicks from working in app windows
>
> Status in GNOME Shell:
>   Confirmed
> Status in Ubuntu GNOME:
>   Confirmed
> Status in gnome-shell package in Ubuntu:
>   Confirmed
> Status in mutter package in Ubuntu:
>   Confirmed
>
> Bug description:
>   Under GNOME 3, the use of the mouse-click stops occasionally, though I
>   can still move the mouse around and can still click on items in the
>   Activities screen and the top-bar.
>
>   I can use alt-tab to cycle windows and can still type into already-
>   active textboxes in windows, but I cannot click within the windows,
>   and the mouse is not picked up at all by the windows.
>
>   I can open the alt-f2 "run command" dialogue, but cannot type into it.
>
>   The workaround I'm using is to open terminal (ctrl-alt-T) and run
>   "gnome-shell -r", and restarting that command every time I have the
>   problem again.
>
>   Please ask if there's anything I forgot to mention.
>
>   ADDITIONAL: The error tends to happen randomly, but it seems to happen
>   upon opening a new window, changing windows, closing windows, or
>   opening the activities pane (whether a change of window is thus
>   instigated or not)
>
>   ADDITIONAL 2: (sorry, it's early) The other workaround is to log out
>   and to log in again, but that is also less than ideal
>
>   ProblemType: Bug
>   DistroRelease: Ubuntu 13.04
>   Package: gnome-shell 3.6.3.1-0ubuntu6
>   ProcVersionSignature: Ubuntu 3.8.0-22.33-generic 3.8.11
>   Uname: Linux 3.8.0-22-generic x86_64
>   ApportVersion: 2.9.2-0ubuntu8
>   Architecture: amd64
>   Date: Sun May 19 07:02:18 2013
>   DisplayManager: gdm
>   GsettingsChanges:
>b'org.gnome.desktop.interface' b'clock-show-date' b'true'
>b'org.gnome.desktop.interface' b'clock-show-seconds' b'true'
>b'org.gnome.desktop.interface' b'document-font-name' b"'Sans 10'"
>b'org.gnome.desktop.interface' b'font-name' b"'Cantarell 10'"
>b'org.gnome.desktop.interface' b'monospace-font-name' b"'Ubuntu Mono
> 12'"
>   InstallationDate: Installed on 2013-05-04 (14 days ago)
>   InstallationMedia: Ubuntu-GNOME 13.04 "Raring Ringtail" - Release amd64
> (20130424)
>   MarkForUpload: True
>   ProcEnviron:
>LANGUAGE=en_GB:en
>PATH=(custom, no user)
>XDG_RUNTIME_DIR=
>LANG=en_GB.UTF-8
>SHELL=/bin/bash
>   SourcePackage: gnome-shell
>   UpgradeStatus: No upgrade log present (probably fresh install)
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/gnome-shell/+bug/1181666/+subscriptions
>

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

Title:
  gnome-shell randomly blocks mouse clicks from working in app windows

Status in GNOME Shell:
  Confirmed
Status in Ubuntu GNOME:
  Confirmed
Status in gnome-shell package in Ubuntu:
  Confirmed
Status in mutter package in Ubuntu:
  Confirmed

Bug description:
  Under GNOME 3, the use of the mouse-click stops occasionally, though I
  can still move the mouse around and can still click on items in the
  Activities screen and the top-bar.

  I can use alt-tab to cycle windows and can still type into already-
  active textboxes in windows, but I cannot click within the windows,
  and the mouse is not picked up at all by the windows.

  I can open the alt-f2 "run command" dialogue, but cannot type into it.

  The workaround I'm using is to open terminal (ctrl-alt-T) and run
  "gnome-shell -r", and restarting that command every time I have the
  problem again.

  Please ask if there's anything I forgot to mention.

  ADDITIONAL: The error tends to happen randomly, but it seems to happen
  upon opening a new window, changing windows, closing windows, or
  opening the activities pane (whether a change of window is thus
  instigated or not)

  ADDITIONAL 2: (sorry, it's early) The other workaround is to log out
  and to log in again, but that is also less than ideal

  ProblemType: Bug

[Desktop-packages] [Bug 107854] Re: [upstream] Impress shows black underline in Slide Show despite colored underline

2019-02-10 Thread Christopher M. Penalver

Upstream fix commits in 6.2 are confirmed to resolve this:
Version: 6.2.0.3 (x64)
Build ID: 98c6a8a1c6c7b144ce3cc729e34964b47ce25d62

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

Title:
  [upstream] Impress shows black underline in Slide Show despite colored
  underline

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

Bug description:
  Binary package hint: openoffice.org-impress

  1) lsb_release -rd
  Description:  Ubuntu 11.04
  Release:  11.04

  2) apt-cache policy libreoffice-impress
  libreoffice-impress:
Installed: 1:3.3.2-1ubuntu5
Candidate: 1:3.3.2-1ubuntu5
Version table:
   *** 1:3.3.2-1ubuntu5 0
  500 http://us.archive.ubuntu.com/ubuntu/ natty-updates/main i386 
Packages
  100 /var/lib/dpkg/status
   1:3.3.2-1ubuntu4 0
  500 http://us.archive.ubuntu.com/ubuntu/ natty/main i386 Packages

  OOo 2.x Impress (19.04.07)

  3) What is expected to happen in LibreOffice Impress via the Terminal:

  cd ~/Desktop && wget
  
https://bugs.launchpad.net/ubuntu/+source/openoffice.org/+bug/107854/+attachment/2143745/+files/underline.odp
  && loimpress -nologo underline.odp

  the text with colored underlines should remain colored in Slide Show.

  4) What happens instead is the underlines are black in Slide Show.

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

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

[Desktop-packages] [Bug 1814388] Re: After switching users, I can see the passwords in /dev/tty1

2019-02-10 Thread Feu

** Description changed:

  Basically I installed ubuntu 18.04.1 LTS on an old machine (on a blank
  SSD), and when I just when had finished the configuration installing
  just a few apps, I thought I had seen the admin's user password during
  Power Off (in the boot text screen that blinks) - as it's an old
  computer I could see this text blinking.
  
  I didn't even use this machine.
  
  After some tests, I found out that after performing these steps:
   - turning the machine on, logging into admin user
   - logging off the admin user
   - logging in a non admin user
   - logging off the non admin user
   - logging in back to the admin user
  
  By running `sudo cat /dev/tty1` I could see everything which was typed
  in the login screen. And that is the content that appears during the
  power off text screen.
  
  For more info, please see https://askubuntu.com/questions/1114802
  
  The steps I can remember while setting up this machine were:
   - changing region to Portuguese (brazil) and configuring keyboard
   - installing Gweled, Pitivi, VLC, Spotify and SuperTuxKart through 'Ubuntu 
Software'
   - installing Google Chrome and Skype by downloading their deb packages from 
the official websites
   - uninstalled Thunderbird
   - updated everything
  
  As you can see in the AskUbuntu question, I tried to simulate this by
  repeating these steps in a virtual machine, but was not able to
  reproduce it. One difference is that this is a HP Pavilion old laptop
  with all sorts of things on it, so many drivers may be needed which will
  not be present in the VM. I booted with 4.15.0-29-generic and it behaved
  the same. However, during the session booting with the 4.15.0.29
  recovery mode, I could not detect that sympton!
  
- I'll keep this machine for a few days, but then I'll reinstall
- everything, if it persists, I'll update here.
+ Running:
+ 
+ sudo lsof /dev/tty1
+ 
+ prints two processes, systemd-l and gdm-wayla.
+ 
+ I installed again the same OS on a different machine and got all the
+ updates installed - no external app installed this time. And I was able
+ to reproduce the issue. I don't know why it doesn't happen in the VM,
+ but it did happen on two different machines (on blank SSDs).
  
  ```
  uname -a
  Linux spider 4.15.0-45-generic #48-Ubuntu SMP Tue Jan 29 16:28:13 UTC 2019 
x86_64 x86_64 x86_64 GNU/Linux
  ```
  
  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-screensaver (not installed)
  ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18
  Uname: Linux 4.15.0-45-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Feb  2 13:38:45 2019
  InstallationDate: Installed on 2019-01-30 (2 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  SourcePackage: gnome-screensaver
  Symptom: security
  Title: Screen locking issue
  UpgradeStatus: No upgrade log present (probably fresh install)

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

Title:
  After switching users, I can see the passwords in /dev/tty1

Status in gnome-screensaver package in Ubuntu:
  New

Bug description:
  Basically I installed ubuntu 18.04.1 LTS on an old machine (on a blank
  SSD), and when I just when had finished the configuration installing
  just a few apps, I thought I had seen the admin's user password during
  Power Off (in the boot text screen that blinks) - as it's an old
  computer I could see this text blinking.

  I didn't even use this machine.

  After some tests, I found out that after performing these steps:
   - turning the machine on, logging into admin user
   - logging off the admin user
   - logging in a non admin user
   - logging off the non admin user
   - logging in back to the admin user

  By running `sudo cat /dev/tty1` I could see everything which was typed
  in the login screen. And that is the content that appears during the
  power off text screen.

  For more info, please see https://askubuntu.com/questions/1114802

  The steps I can remember while setting up this machine were:
   - changing region to Portuguese (brazil) and configuring keyboard
   - installing Gweled, Pitivi, VLC, Spotify and SuperTuxKart through 'Ubuntu 
Software'
   - installing Google Chrome and Skype by downloading their deb packages from 
the official websites
   - uninstalled Thunderbird
   - updated everything

  As you can see in the AskUbuntu question, I tried to simulate this by
  repeating these steps in a virtual machine, but was not able to
  reproduce it. One difference is that this is a HP Pavilion old laptop
  with all sorts of things on it, so many drivers may be needed which
  will not be present in the VM. I booted with 4.15.0-29-generic and it
  behaved the same. However, during the session booting with the
  4.15.0.29 recovery mode, I could

[Desktop-packages] [Bug 1181666] Re: gnome-shell randomly blocks mouse clicks from working in app windows

2019-02-10 Thread Adrian

I am facing the same issue in Ubuntu 18.10. The super key randomly stops
working and I loose control of all windows except for the active window,
which in some cases also stops working and cannot even do clicks there.
The workaround I found is to close all windows, lock the screen and the
problem solves for 5-10 min or so. But this is clearly impractical and I
can't really go on like this any further. I re-installed the OS but it
didn't solve the issue. I have a Lenovo T430s if that helps. Does anyone
found a solution to this yet? I'd appreciate it very much!

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

Title:
  gnome-shell randomly blocks mouse clicks from working in app windows

Status in GNOME Shell:
  Confirmed
Status in Ubuntu GNOME:
  Confirmed
Status in gnome-shell package in Ubuntu:
  Confirmed
Status in mutter package in Ubuntu:
  Confirmed

Bug description:
  Under GNOME 3, the use of the mouse-click stops occasionally, though I
  can still move the mouse around and can still click on items in the
  Activities screen and the top-bar.

  I can use alt-tab to cycle windows and can still type into already-
  active textboxes in windows, but I cannot click within the windows,
  and the mouse is not picked up at all by the windows.

  I can open the alt-f2 "run command" dialogue, but cannot type into it.

  The workaround I'm using is to open terminal (ctrl-alt-T) and run
  "gnome-shell -r", and restarting that command every time I have the
  problem again.

  Please ask if there's anything I forgot to mention.

  ADDITIONAL: The error tends to happen randomly, but it seems to happen
  upon opening a new window, changing windows, closing windows, or
  opening the activities pane (whether a change of window is thus
  instigated or not)

  ADDITIONAL 2: (sorry, it's early) The other workaround is to log out
  and to log in again, but that is also less than ideal

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: gnome-shell 3.6.3.1-0ubuntu6
  ProcVersionSignature: Ubuntu 3.8.0-22.33-generic 3.8.11
  Uname: Linux 3.8.0-22-generic x86_64
  ApportVersion: 2.9.2-0ubuntu8
  Architecture: amd64
  Date: Sun May 19 07:02:18 2013
  DisplayManager: gdm
  GsettingsChanges:
   b'org.gnome.desktop.interface' b'clock-show-date' b'true'
   b'org.gnome.desktop.interface' b'clock-show-seconds' b'true'
   b'org.gnome.desktop.interface' b'document-font-name' b"'Sans 10'"
   b'org.gnome.desktop.interface' b'font-name' b"'Cantarell 10'"
   b'org.gnome.desktop.interface' b'monospace-font-name' b"'Ubuntu Mono 12'"
  InstallationDate: Installed on 2013-05-04 (14 days ago)
  InstallationMedia: Ubuntu-GNOME 13.04 "Raring Ringtail" - Release amd64 
(20130424)
  MarkForUpload: True
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1815384] [NEW] [Latitude 7490, Realtek ALC3246, Black Headphone Out, Front] Playback problem

2019-02-10 Thread Catalin Gabriel Stan

Public bug reported:

lsb_release -rd
Description:Ubuntu 18.04.1 LTS
Release:18.04


I am not sure how to describe the problem.

If i turn off my laptop with my headphones in, when it boots up (without 
removing the headphones at any times), then no sound is playing on any exits. 
Not on the laptop's speaker, neither on the headphones.
  
I am a developer, and I think the issue it's that the hardware is trying to 
play the sound on the headphones (because you restrict playing on both the 
speakers and the headphones at once, without extra custom configurations), 
because playing on headphones is what the hardware remembers, but ubuntu 
forgets that between reboots and it's telling the hardware to play on speakers, 
which the hardware won't do. 

To fix the problem, i have to unplug my headphones and plug them back
in. And sometimes that is annoying because some sounds may be too loud
and i am in a meeting :) .

Maybe in ubuntu, the audio port is being initialized with speakers at
boot time, and it is not verifying the aux outputs for listeners, to
initialize with that.

Maybe this should be a new feature.

The feature would be to scan the audio ports at boot time, to see if any
auxiliary ports are found. Not sure if multiple can be found. Initialize
with whatever state would be if those auxiliary ports where plugged in
one at a time, and not found like this. The initial state should not
always be the default audio port.

Thank you for understanding, and please let me know if you what i mean.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: alsa-base 1.0.25+dfsg-0ubuntu5
ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18
Uname: Linux 4.15.0-45-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.5
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  catalinstan   2906 F pulseaudio
CurrentDesktop: ubuntu:GNOME
Date: Sun Feb 10 23:02:24 2019
InstallationDate: Installed on 2018-06-25 (230 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
PackageArchitecture: all
SourcePackage: alsa-driver
Symptom: audio
Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful
Symptom_Card: Built-in Audio - HDA Intel PCH
Symptom_Jack: Black Headphone Out, Front
Symptom_PulsePlaybackTest: PulseAudio playback test successful
Symptom_Type: None of the above
Title: [Latitude 7490, Realtek ALC3246, Black Headphone Out, Front] Playback 
problem
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 11/26/2018
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.7.2
dmi.board.name: 0KP0FT
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 10
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvr1.7.2:bd11/26/2018:svnDellInc.:pnLatitude7490:pvr:rvnDellInc.:rn0KP0FT:rvrA00:cvnDellInc.:ct10:cvr:
dmi.product.family: Latitude
dmi.product.name: Latitude 7490
dmi.sys.vendor: Dell Inc.

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

Title:
  [Latitude 7490, Realtek ALC3246, Black Headphone Out, Front] Playback
  problem

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  lsb_release -rd
  Description:  Ubuntu 18.04.1 LTS
  Release:  18.04

  
  I am not sure how to describe the problem.

  If i turn off my laptop with my headphones in, when it boots up (without 
removing the headphones at any times), then no sound is playing on any exits. 
Not on the laptop's speaker, neither on the headphones.

  I am a developer, and I think the issue it's that the hardware is trying to 
play the sound on the headphones (because you restrict playing on both the 
speakers and the headphones at once, without extra custom configurations), 
because playing on headphones is what the hardware remembers, but ubuntu 
forgets that between reboots and it's telling the hardware to play on speakers, 
which the hardware won't do. 

  To fix the problem, i have to unplug my headphones and plug them back
  in. And sometimes that is annoying because some sounds may be too loud
  and i am in a meeting :) .

  Maybe in ubuntu, the audio port is being initialized with speakers at
  boot time, and it is not verifying the aux outputs for listeners, to
  initialize with that.

  Maybe this should be a new feature.

  The feature would be to scan the audio ports at boot time, to see if
  any auxiliary ports are found. Not sure if multiple can be found.
  Initialize with whatever state would be if those auxiliary ports where
  plugged in one at a time, and not found like this. The initial state
  should not always be the default audio port.

  Thank you for understanding, and please let me know if you what i
  mean.

  ProblemType: Bug
  DistroRelease:

[Desktop-packages] [Bug 1815378] [NEW] gvfs spins up sleeping HDD even if all partitions unmounted

2019-02-10 Thread Emile D

Public bug reported:

Hi,

On my laptop I use :
 * a SSD for boot and all tasks
 * a HDD for storing big files

The HDD is spun down at startup and the corresponding filesystem is
unmounted. I succeed in disabling all services making the HDD
periodically wake up.

The only problem is that this HDD spins up when I launch thunar for the
first time. If I close thunar, spin down the disk, then launch thunar
again, the disk stays in sleep mode...

I found this thread without answer talking about the same issue :
https://forum.xfce.org/viewtopic.php?id=11270

Is there a way to disable thunar first access to umounted partition ?

---

I first reported this bug here :

https://bugzilla.xfce.org/show_bug.cgi?id=14998

I investigated with help from thunar developers and it appears that this
bug is coming from gvfs, because it desapear when I remove gvfs and use
thunar without gvfs extension, and it exists also for nautilus (other
soft using gvfs).

Thank you for your help.

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

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

Title:
  gvfs spins up sleeping HDD even if all partitions unmounted

Status in gvfs package in Ubuntu:
  New

Bug description:
  Hi,

  On my laptop I use :
   * a SSD for boot and all tasks
   * a HDD for storing big files

  The HDD is spun down at startup and the corresponding filesystem is
  unmounted. I succeed in disabling all services making the HDD
  periodically wake up.

  The only problem is that this HDD spins up when I launch thunar for
  the first time. If I close thunar, spin down the disk, then launch
  thunar again, the disk stays in sleep mode...

  I found this thread without answer talking about the same issue :
  https://forum.xfce.org/viewtopic.php?id=11270

  Is there a way to disable thunar first access to umounted partition ?

  ---

  I first reported this bug here :

  https://bugzilla.xfce.org/show_bug.cgi?id=14998

  I investigated with help from thunar developers and it appears that
  this bug is coming from gvfs, because it desapear when I remove gvfs
  and use thunar without gvfs extension, and it exists also for nautilus
  (other soft using gvfs).

  Thank you for your help.

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

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

Re: [Desktop-packages] [Bug 1774443] Re: wireless hardblocked and wireless enable button not functional

2019-02-10 Thread Nicholas Wright

Yes, the issue still persists in 4.19.20 and 5.0-rc5

On Fri, Feb 8, 2019, 9:55 AM Kai-Heng Feng 
wrote:

> Does this still happen on latest mainline kernel?
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1774443
>
> Title:
>   wireless hardblocked and wireless enable button not functional
>
> Status in linux package in Ubuntu:
>   Confirmed
> Status in network-manager package in Ubuntu:
>   New
>
> Bug description:
>   Laptop is an HP Pavilion dm4-3170se. Dual booting Windows 7 and
>   ubuntu. In Windows, system boots with wireless disabled and then
>   pressing the wireless enable button twice enables WiFi.
>
>   In ubuntu, system boots with wireless disabled and wireless enable
>   button has no functionality either directly or in combination with the
>   fn-key.
>
>   Module hp_wmi may be the culprit? But disabling this has no effect on
>   hardblock.
>
>   reference forum post for more detailed info:
>
> https://ubuntuforums.org/showthread.php?t=2392934=13772159#post13772159
>
>   ProblemType: Bug
>   DistroRelease: Ubuntu 16.04
>   Package: network-manager 1.2.6-0ubuntu0.16.04.2
>   ProcVersionSignature: Ubuntu 4.13.0-43.48~16.04.1-generic 4.13.16
>   Uname: Linux 4.13.0-43-generic x86_64
>   ApportVersion: 2.20.1-0ubuntu2.17
>   Architecture: amd64
>   CurrentDesktop: Unity
>   Date: Thu May 31 10:32:38 2018
>   IfupdownConfig:
># interfaces(5) file used by ifup(8) and ifdown(8)
>auto lo
>iface lo inet loopback
>   InstallationDate: Installed on 2018-05-19 (11 days ago)
>   InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64
> (20180228)
>   IpRoute:
>default via 172.16.96.1 dev eno1  proto static  metric 100
>169.254.0.0/16 dev eno1  scope link  metric 1000
>172.16.96.0/19 dev eno1  proto kernel  scope link  src 172.16.119.109
> metric 100
>192.17.90.180 via 172.16.96.1 dev eno1  proto dhcp  metric 100
>   NetworkManager.state:
>[main]
>NetworkingEnabled=true
>WirelessEnabled=true
>WWANEnabled=true
>   ProcEnviron:
>LANGUAGE=en_US
>PATH=(custom, no user)
>XDG_RUNTIME_DIR=
>LANG=en_US.UTF-8
>SHELL=/bin/bash
>   RfKill:
>0: phy0: Wireless LAN
> Soft blocked: no
> Hard blocked: yes
>   SourcePackage: network-manager
>   UpgradeStatus: No upgrade log present (probably fresh install)
>   nmcli-con:
>NAMEUUID  TYPE
>   TIMESTAMP   TIMESTAMP-REAL   AUTOCONNECT
> AUTOCONNECT-PRIORITY  READONLY  DBUS-PATH
>  ACTIVE  DEVICE  STATE  ACTIVE-PATH
>
>Wired connection 1  0357c159-f43c-38f9-8b6f-91bb641d1712
> 802-3-ethernet  1527780471  Thu 31 May 2018 10:27:51 AM CDT  yes
> 4294966297no/org/freedesktop/NetworkManager/Settings/0
> yes eno1activated
> /org/freedesktop/NetworkManager/ActiveConnection/1
>   nmcli-dev:
>DEVICE  TYPE  STATEDBUS-PATH
>   CONNECTION  CON-UUID  CON-PATH
>
>eno1ethernet  connected
> /org/freedesktop/NetworkManager/Devices/2  Wired connection 1
> 0357c159-f43c-38f9-8b6f-91bb641d1712
> /org/freedesktop/NetworkManager/ActiveConnection/1
>wlp8s0  wifi  unavailable
> /org/freedesktop/NetworkManager/Devices/1  --  --
>   --
>
>lo  loopback  unmanaged
> /org/freedesktop/NetworkManager/Devices/0  --  --
>   --
>   nmcli-nm:
>RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING
> WIFI-HW  WIFI  WWAN-HW  WWAN
>running  1.2.6connected  started  full  enabled
>  enabled  disabled  enabled  enabled
>   ---
>   ApportVersion: 2.20.1-0ubuntu2.18
>   Architecture: amd64
>   AudioDevicesInUse:
>USERPID ACCESS COMMAND
>/dev/snd/controlC0:  naww   1928 F pulseaudio
>   CurrentDesktop: Unity
>   DistroRelease: Ubuntu 16.04
>   HibernationDevice: RESUME=UUID=96f5e2e6-1a22-453e-84c5-21cb7094a381
>   IfupdownConfig:
># interfaces(5) file used by ifup(8) and ifdown(8)
>auto lo
>iface lo inet loopback
>   InstallationDate: Installed on 2018-05-19 (32 days ago)
>   InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64
> (20180228)
>   IpRoute:
>default via 192.168.42.129 dev enp0s20u3  proto static  metric 100
>169.254.0.0/16 dev enp0s20u3  scope link  metric 1000
>192.168.42.0/24 dev enp0s20u3  proto kernel  scope link  src
> 192.168.42.168  metric 100
>   MachineType: Hewlett-Packard HP Pavilion dm4 Notebook PC
>   NetworkManager.state:
>[main]
>NetworkingEnabled=true
>WirelessEnabled=true
>WWANEnabled=true
>   Package: network-manager 1.2.6-0ubuntu0.16.04.2
>   PackageArchitecture: amd64
>   ProcFB: 0 inteldrmfb
>   ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-43-generic
> root=UUID=753230c7-6c88-415a-93f2-c133b9a161b1 ro quiet splash vt.handoff=7
>

[Desktop-packages] [Bug 1815339] Re: Printer stopped printing paper size 4"x6" after update ghostscript to 9.26

2019-02-10 Thread Fedik

here is a captured print job

** Attachment added: "appout.pdf"
   
https://bugs.launchpad.net/ubuntu/+source/ghostscript/+bug/1815339/+attachment/5237521/+files/appout.pdf

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

Title:
  Printer stopped printing paper size 4"x6" after update ghostscript to
  9.26

Status in ghostscript package in Ubuntu:
  New

Bug description:
  
  I have an issue with Ghostscript and printing.
  I use Gutenprint for my Canon MG5440, and I cannot print a photo 4"x6" (or 
6"x4"), it does not print anything, however I still able to print A4 paper size.
  I use Ubuntu 18.04 and Gutenprint 5.3.1.

  The printing fail with message:
  
  [Job 143] Start rendering...
  [Job 143] Processing page 1...
  [Job 143]  Unable to open the initial device, quitting.
  [Job 143] Rendering completed
  ...
  [Job 143] PID 24869 (/usr/lib/cups/filter/gstoraster) stopped with status 1.
  ...
  [Job 143] printer-state-message="Filter failed"
  [Job 143] printer-state-reasons=none

  The message "Unable to open the initial device, quitting" comes from
  Ghostscript.

  
  When I downgrade Ghostscript to 9.22, 
  I am again able to print 4"x6" paper size.

  To downgrade: apt install ghostscript=9.22~dfsg+1-0ubuntu1
  libgs9=9.22~dfsg+1-0ubuntu1 libgs9-common=9.22~dfsg+1-0ubuntu1

  I found similar issue for HP printer at Debian https://bugs.debian.org
  /cgi-bin/bugreport.cgi?bug=908205

  
  System info:
  Description:  Ubuntu 18.04.1 LTS
  Release:  18.04

  ghostscript:
Installed: 9.26~dfsg+0-0ubuntu0.18.04.4
Candidate: 9.26~dfsg+0-0ubuntu0.18.04.4
Versions:
   *** 9.26~dfsg+0-0ubuntu0.18.04.4 500
  500 http://ua.archive.ubuntu.com/ubuntu bionic-updates/main amd64 
Packages
  500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 
Packages
  100 /var/lib/dpkg/status
   9.22~dfsg+1-0ubuntu1 500
  500 http://ua.archive.ubuntu.com/ubuntu bionic/main amd64 Packages

  cups:
Installed: 2.2.7-1ubuntu2.3
Candidate: 2.2.7-1ubuntu2.3
Versions:
   *** 2.2.7-1ubuntu2.3 500
  500 http://ua.archive.ubuntu.com/ubuntu bionic-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   2.2.7-1ubuntu2.2 500
  500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 
Packages
   2.2.7-1ubuntu2 500
  500 http://ua.archive.ubuntu.com/ubuntu bionic/main amd64 Packages

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

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

[Desktop-packages] [Bug 1815375] [NEW] Firefox hangs/slows/does-not-respond upon downloading a file

2019-02-10 Thread Trevor Zenk

Public bug reported:

I am using Ubuntu Disco Dingo 19.04 and the current version of Firefox
as of 2/7/2019 (version 65.0).

OS Version: Disco Dingo 19.04
Firefox Version: 65.0
Expected: I can download a file and click save in a reasonable amount of time.
Actual: Downloading a file causes Firefox to crash or freeze or take many many 
minutes! 


Write-up:
When downloading files of any size, the dialogue that asks weather to save or 
open a file appears.  This window, as well as any other Firefox window becomes 
unresponsive.  Occasionally I can wait minutes and it will respond again; 
sometimes the application will crash however.  I believe crashes and longer 
waits occur with larger downloads.  Using Firefox Nightly builds has resolved 
my issue, but this is a temporary fix for me.  I believe it is this 
https://bugzilla.mozilla.org/show_bug.cgi?id=1517101 on the upstream.  <3 thank 
you for the free software; even if there are rough patches occasionally!  
Cheers from Wisconsin.

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

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

Title:
  Firefox hangs/slows/does-not-respond upon downloading a file

Status in firefox package in Ubuntu:
  New

Bug description:
  I am using Ubuntu Disco Dingo 19.04 and the current version of Firefox
  as of 2/7/2019 (version 65.0).

  OS Version: Disco Dingo 19.04
  Firefox Version: 65.0
  Expected: I can download a file and click save in a reasonable amount of time.
  Actual: Downloading a file causes Firefox to crash or freeze or take many 
many minutes! 

  
  Write-up:
  When downloading files of any size, the dialogue that asks weather to save or 
open a file appears.  This window, as well as any other Firefox window becomes 
unresponsive.  Occasionally I can wait minutes and it will respond again; 
sometimes the application will crash however.  I believe crashes and longer 
waits occur with larger downloads.  Using Firefox Nightly builds has resolved 
my issue, but this is a temporary fix for me.  I believe it is this 
https://bugzilla.mozilla.org/show_bug.cgi?id=1517101 on the upstream.  <3 thank 
you for the free software; even if there are rough patches occasionally!  
Cheers from Wisconsin.

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

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

[Desktop-packages] [Bug 1815374] [NEW] Please adjust dependencies so that policykit-1-gnome can be demoted to universe

2019-02-10 Thread Jeremy Bicha

Public bug reported:

The Ubuntu Desktop Team would like to get policykit-1-gnome demoted to
universe since it is no longer used in the default install. (See its
package description.)

I believe screen-resolution-extra is the last thing holding that package
in main.

gnome-shell provides polkit-1-auth-agent. You can see provides and reverse 
depends for a virtual package by running
$ apt-cache showpkg polkit-1-auth-agent

In my experience with demoting xterm to universe, it looked to me like
Ubuntu's germinate doesn't handle virtual packages and alternate
dependencies very well. I ended up having to put gnome-terminal as the
first dependency in the list of alternates.

Suggestion 1

Change screen-resolution-extra's dependency to:
gnome-shell | policykit-1-gnome | polkit-1-auth-agent

Suggestion 2

Change nvidia-settings to Suggest instead of Depend on screen-resolution-extra. 
From the package's description, it sounds like screen-resolution-extra is not 
useful for a default Ubuntu install? If so, we can demote both 
screen-resolution-extra and policykit-1-gnome to universe.

** Affects: screen-resolution-extra (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: disco

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

Title:
  Please adjust dependencies so that policykit-1-gnome can be demoted to
  universe

Status in screen-resolution-extra package in Ubuntu:
  New

Bug description:
  The Ubuntu Desktop Team would like to get policykit-1-gnome demoted to
  universe since it is no longer used in the default install. (See its
  package description.)

  I believe screen-resolution-extra is the last thing holding that
  package in main.

  gnome-shell provides polkit-1-auth-agent. You can see provides and reverse 
depends for a virtual package by running
  $ apt-cache showpkg polkit-1-auth-agent

  In my experience with demoting xterm to universe, it looked to me like
  Ubuntu's germinate doesn't handle virtual packages and alternate
  dependencies very well. I ended up having to put gnome-terminal as the
  first dependency in the list of alternates.

  Suggestion 1
  
  Change screen-resolution-extra's dependency to:
  gnome-shell | policykit-1-gnome | polkit-1-auth-agent

  Suggestion 2
  
  Change nvidia-settings to Suggest instead of Depend on 
screen-resolution-extra. From the package's description, it sounds like 
screen-resolution-extra is not useful for a default Ubuntu install? If so, we 
can demote both screen-resolution-extra and policykit-1-gnome to universe.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/screen-resolution-extra/+bug/1815374/+subscriptions

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

[Desktop-packages] [Bug 1764417] Re: Unrecoverable failure in required component org.gnome.SettingsDaemon.Color.desktop

2019-02-10 Thread cmcint01

I'm seeing similar issue using nvidia card with latest NVIDIA driver update 
410.  
---
error log: 

gnome-session-b

Unrecoverable failure in required component org.gnome.Shell.desktop

Priority: 3

-
Not much else detailed except on ubuntu 18.04 with latest updates.  

after last update started seeing the above errors. Also keyboard
intermittently freezes.  Thanks.

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

Title:
  Unrecoverable failure in required component
  org.gnome.SettingsDaemon.Color.desktop

Status in gnome-settings-daemon package in Ubuntu:
  Confirmed

Bug description:
  I've had this happen a couple of times now since upgrading to 18.04:
  soon (perhaps within a minute) after logging in, Gnome session ends
  abruptly and I'm thrown back to the login screen. IIRC, in both
  instances this occurred on the first login after boot, so it does not
  reoccur on the subsequent re-login, and not on every login (very
  rarely in fact), and for now I have no better steps to reproduce this
  other than "boot, log in".

  Bug #1663839 (reported against 17.04) seems similar, as does bug
  #1731428 (reported against 17.10).

  journalctl output during the issue:

  Apr 16 07:00:30 saegusa gnome-session[4342]: gnome-session-binary[4342]: 
WARNING: Application 'org.gnome.SettingsDaemon.Color.desktop' failed to 
register before timeout
  Apr 16 07:00:30 saegusa gnome-session-binary[4342]: WARNING: Application 
'org.gnome.SettingsDaemon.Color.desktop' failed to register before timeout
  Apr 16 07:00:30 saegusa gnome-session-binary[4342]: Unrecoverable failure in 
required component org.gnome.SettingsDaemon.Color.desktop
  Apr 16 07:00:30 saegusa gnome-session[4342]: gnome-session-binary[4342]: 
CRITICAL: We failed, but the fail whale is dead. Sorry
  Apr 16 07:00:30 saegusa gnome-session-binary[4342]: CRITICAL: We failed, but 
the fail whale is dead. Sorry

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-settings-daemon 3.28.1-0ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15
  Uname: Linux 4.15.0-15-generic x86_64
  ApportVersion: 2.20.9-0ubuntu4
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Apr 16 17:07:14 2018
  InstallationDate: Installed on 2016-10-13 (550 days ago)
  InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fi_FI.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-settings-daemon
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1815348] Re: package libappindicator0.1-cil 12.10.1+16.04.20170215-0ubuntu1 failed to install/upgrade: subprocess installed post-installation script returned error exit status

2019-02-10 Thread Ubuntu Foundations Team Bug Bot

Thank you for taking the time to report this bug and helping to make
Ubuntu better.  Reviewing your dmesg attachment in this bug report it
seems that there is a problem with your hardware.  I recommend
performing a back up and then investigating the situation.  Measures you
might take include checking cable connections and using software tools
to investigate the health of your hardware.  In the event that is is not
in fact an error with your hardware please set the bug's status back to
New.  Thanks and good luck!

[This is an automated message.  I apologize if it reached you
inappropriately; please just reply to this message indicating so.]

** Tags added: hardware-error

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

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

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

Title:
  package libappindicator0.1-cil 12.10.1+16.04.20170215-0ubuntu1 failed
  to install/upgrade: subprocess installed post-installation script
  returned error exit status 134

Status in libappindicator package in Ubuntu:
  Invalid

Bug description:
  l'errore compare all'avvio di ubuntu

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libappindicator0.1-cil 12.10.1+16.04.20170215-0ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-116.140-generic 4.4.98
  Uname: Linux 4.4.0-116-generic i686
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: i386
  Date: Sun Jan 20 19:33:19 2019
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 134
  InstallationDate: Installed on 2013-11-03 (1925 days ago)
  InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release i386 (20110427.1)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.4
   apt  1.2.29
  SourcePackage: libappindicator
  Title: package libappindicator0.1-cil 12.10.1+16.04.20170215-0ubuntu1 failed 
to install/upgrade: subprocess installed post-installation script returned 
error exit status 134
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1815326] Re: Totem does not work on Ubuntu 19.04

2019-02-10 Thread Edson José dos Santos

** Summary changed:

- Totem crashed on Ubuntu disk 19.04
+ Totem does not work on Ubuntu 19.04

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

Title:
  Totem does not work on Ubuntu 19.04

Status in totem package in Ubuntu:
  New

Bug description:
  Hi guys

  Totem crashed and informs you that you need to install plugin, but it
  does not tell you which plugin to install as attached image. If the
  totem knows that a plugin is missing because it does not tell you
  which one needs to be installed?

  The totem stopped working after updating Cheese 3.31.90-1. Cheese also
  stopped working.

  follows the error message by opening the totem through the terminal:

  edson@edson-p6540br:~$ totem

  (totem:4996): Clutter-WARNING **: 01:11:27.077: Whoever translated
  default:LTR did so wrongly.

  (totem:4996): GLib-GObject-CRITICAL **: 01:11:27.181: g_object_set:
  assertion 'G_IS_OBJECT (object)' failed

  (totem:4996): GStreamer-CRITICAL **: 01:11:27.181: gst_bin_add:
  assertion 'GST_IS_ELEMENT (element)' failed

  (totem:4996): GStreamer-CRITICAL **: 01:11:27.181:
  gst_element_get_static_pad: assertion 'GST_IS_ELEMENT (element)'
  failed

  (totem:4996): GStreamer-CRITICAL **: 01:11:27.182: gst_object_unref:
  assertion 'object != NULL' failed

  (totem:4996): GStreamer-CRITICAL **: 01:11:27.186: gst_bin_add_many:
  assertion 'GST_IS_ELEMENT (element_1)' failed

  (totem:4996): GStreamer-CRITICAL **: 01:11:27.186:
  gst_element_link_many: assertion 'GST_IS_ELEMENT (element_1)' failed

  (totem:4996): GStreamer-CRITICAL **: 01:11:27.186:
  gst_element_get_static_pad: assertion 'GST_IS_ELEMENT (element)'
  failed

  (totem:4996): GStreamer-CRITICAL **: 01:11:27.186: gst_ghost_pad_new:
  assertion 'GST_IS_PAD (target)' failed

  (totem:4996): GStreamer-CRITICAL **: 01:11:27.186:
  gst_element_add_pad: assertion 'GST_IS_PAD (pad)' failed

  (totem:4996): GStreamer-CRITICAL **: 01:11:27.186: gst_object_unref: 
assertion 'object != NULL' failed
  GnomeDesktop-Message: 01:11:28.581: got a preview thumbnail

  (totem:4996): GLib-GObject-CRITICAL **: 01:11:28.581: g_object_ref:
  assertion 'G_IS_OBJECT (object)' failed

  ** (totem:4996): WARNING **: 01:17:05.422: can't find typefind
  element, decodebin will not work

  (totem:4996): Totem-WARNING **: 01:17:09.284: Failed to reset the
  playback rate to 1.0

  
  See attached image

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

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

[Desktop-packages] [Bug 1815339] Re: Printer stopped printing paper size 4"x6" after update ghostscript to 9.26

2019-02-10 Thread Robert Krawitz

Reference https://sourceforge.net/p/gimp-print/bugs/719/

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

Title:
  Printer stopped printing paper size 4"x6" after update ghostscript to
  9.26

Status in ghostscript package in Ubuntu:
  New

Bug description:
  
  I have an issue with Ghostscript and printing.
  I use Gutenprint for my Canon MG5440, and I cannot print a photo 4"x6" (or 
6"x4"), it does not print anything, however I still able to print A4 paper size.
  I use Ubuntu 18.04 and Gutenprint 5.3.1.

  The printing fail with message:
  
  [Job 143] Start rendering...
  [Job 143] Processing page 1...
  [Job 143]  Unable to open the initial device, quitting.
  [Job 143] Rendering completed
  ...
  [Job 143] PID 24869 (/usr/lib/cups/filter/gstoraster) stopped with status 1.
  ...
  [Job 143] printer-state-message="Filter failed"
  [Job 143] printer-state-reasons=none

  The message "Unable to open the initial device, quitting" comes from
  Ghostscript.

  
  When I downgrade Ghostscript to 9.22, 
  I am again able to print 4"x6" paper size.

  To downgrade: apt install ghostscript=9.22~dfsg+1-0ubuntu1
  libgs9=9.22~dfsg+1-0ubuntu1 libgs9-common=9.22~dfsg+1-0ubuntu1

  I found similar issue for HP printer at Debian https://bugs.debian.org
  /cgi-bin/bugreport.cgi?bug=908205

  
  System info:
  Description:  Ubuntu 18.04.1 LTS
  Release:  18.04

  ghostscript:
Installed: 9.26~dfsg+0-0ubuntu0.18.04.4
Candidate: 9.26~dfsg+0-0ubuntu0.18.04.4
Versions:
   *** 9.26~dfsg+0-0ubuntu0.18.04.4 500
  500 http://ua.archive.ubuntu.com/ubuntu bionic-updates/main amd64 
Packages
  500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 
Packages
  100 /var/lib/dpkg/status
   9.22~dfsg+1-0ubuntu1 500
  500 http://ua.archive.ubuntu.com/ubuntu bionic/main amd64 Packages

  cups:
Installed: 2.2.7-1ubuntu2.3
Candidate: 2.2.7-1ubuntu2.3
Versions:
   *** 2.2.7-1ubuntu2.3 500
  500 http://ua.archive.ubuntu.com/ubuntu bionic-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   2.2.7-1ubuntu2.2 500
  500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 
Packages
   2.2.7-1ubuntu2 500
  500 http://ua.archive.ubuntu.com/ubuntu bionic/main amd64 Packages

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

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

[Desktop-packages] [Bug 1719192] Re: Some Top Icons Disappear After Screen Locks - 17.10

2019-02-10 Thread Pavel Kokoshnikov

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

Same issue Ubuntu 18.04

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

Title:
  Some Top Icons Disappear After Screen Locks - 17.10

Status in gnome-shell-extension-appindicator package in Ubuntu:
  Confirmed

Bug description:
  Hi friends. I'm testing Ubuntu 17.10 with Gnome 3.26. I noticed some
  top bar icons disappear after my screen locks and I go back in to my
  active session. As an example, I currently have Quassel, Telegram, and
  Nextcloud sync client in the upper right corner displaying their task
  tray icons. If I lock my screen and re-authenticate back in to my
  active session, Quassel remains, but Telegram and Nextcloud are gone.
  The only way to get them back is by closing the application the
  missing icon belongs to and re-launching it.

  Thanks for all of your hard work!

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome (not installed)
  ProcVersionSignature: Ubuntu 4.13.0-11.12-generic 4.13.1
  Uname: Linux 4.13.0-11-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Sep 24 10:57:24 2017
  InstallationDate: Installed on 2017-09-01 (23 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170830)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: meta-gnome3
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1653351]

2019-02-10 Thread Mkmelin+mozilla

Comment on attachment 9029379
noSelectAfterDelete.patch

Review of attachment 9029379:
-

(In reply to alta88 from comment #65)
> The patch does not intend to change existing behavior at all when a message
> is selected, for either message window actions or the imap delete model or
> anything else. 

Well it does. I agree a pref for something like this is not the way to go.
Sorry for the delay, but this bug is very confusing. Fine tuning the behaviour 
is fine by me, but I think you need to do it separately for each case. The 
current patch changes behaviours that shouldn't change.

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

Title:
  Have option to not automatically open next email

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

Bug description:
  I have found that with Thunderbird if I open an email and then press a
  button such as the "Junk" or "Delete" button, it will automatically
  move on and open the next email. Now as I get a lot of spam on this
  email in the inbox with the spam filter not properly configured yet,
  it would be very useful if there were an option to disable this
  automatically opening the next email feature. So that it would just go
  to the blank screen in the email display section. Quite a few people I
  know for similar reasons say they would like an option like this so
  that malicious emails don't accidentally get opened.

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

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

[Desktop-packages] [Bug 1815354] Re: BCM 43142 driver not installed - no WiFi

2019-02-10 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/1815354

** Tags added: iso-testing

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

Title:
  BCM 43142 driver not installed - no WiFi

Status in network-manager package in Ubuntu:
  New

Bug description:
  Disco daily Lubuntu 09.02.2019 and Disco daily Kubuntu 10.02.2019

  BCM 43142 drivers not installed resulting in no WiFi during and after
  installation.

  I was able to attach ethernet cable and use the command line "ubuntu-
  drivers" command to install the drivers and all worked well after
  that.

  Of course if running a machine with no ethernet then this is a huge
  problem for the user.

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

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

[Desktop-packages] [Bug 1814481] Re: bluetooth keyboard not working

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

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

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

Title:
  bluetooth keyboard not working

Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  I recently got a nice mechanical bluetooth keyboard to use on my
  thinkpad. It works fine with Android, Windows 10 and Xubuntu 19.04
  live, but on my installed xubuntu 18.04, 18.04 live and 18.10 live it
  only works after calling `sudo evtest /dev/input/eventN`.

  Xorg.0.log shows it is detected fine, and I can't see anything there
  after temporarily getting it to work using the evtest trick.

  18.515] (II) config/udev: Adding input device Keychron K1 
(/dev/input/event23)
  [18.515] (**) Keychron K1: Applying InputClass "libinput keyboard 
catchall"
  [18.515] (II) Using input driver 'libinput' for 'Keychron K1'
  [18.515] (**) Keychron K1: always reports core events
  [18.515] (**) Option "Device" "/dev/input/event23"
  [18.515] (**) Option "_source" "server/udev"
  [18.516] (II) event23 - Keychron K1: is tagged by udev as: Keyboard
  [18.516] (II) event23 - Keychron K1: device is a keyboard
  [18.516] (II) event23 - Keychron K1: device removed
  [18.524] (II) libinput: Keychron K1: needs a virtual subdevice
  [18.524] (**) Option "config_info" 
"udev:/sys/devices/pci:00/:00:14.0/usb1/1-7/1-7:1.0/bluetooth/hci0/hci0:256/0005:05AC:0255.0007/input/input24/event23"
  [18.524] (II) XINPUT: Adding extended input device "Keychron K1" (type: 
MOUSE, id 20)
  [18.524] (**) Option "AccelerationScheme" "none"
  [18.524] (**) Keychron K1: (accel) selected scheme none/0
  [18.524] (**) Keychron K1: (accel) acceleration factor: 2.000
  [18.524] (**) Keychron K1: (accel) acceleration threshold: 4
  [18.524] (II) event23 - Keychron K1: is tagged by udev as: Keyboard
  [18.524] (II) event23 - Keychron K1: device is a keyboard
  [18.524] (**) Keychron K1: Applying InputClass "libinput keyboard 
catchall"
  [18.524] (II) Using input driver 'libinput' for 'Keychron K1'
  [18.524] (**) Keychron K1: always reports core events
  [18.524] (**) Option "Device" "/dev/input/event23"
  [18.524] (**) Option "_source" "_driver/libinput"
  [18.524] (II) libinput: Keychron K1: is a virtual subdevice
  [18.524] (**) Option "config_info" 
"udev:/sys/devices/pci:00/:00:14.0/usb1/1-7/1-7:1.0/bluetooth/hci0/hci0:256/0005:05AC:0255.0007/input/input24/event23"
  [18.524] (II) XINPUT: Adding extended input device "Keychron K1" (type: 
KEYBOARD, id 21)
  [18.524] (**) Option "xkb_model" "pc105"
  [18.524] (**) Option "xkb_layout" "us"
  [18.524] (**) Option "xkb_variant" "altgr-intl"
  [18.524] (WW) Option "xkb_options" requires a string value

  I've also tried using the latest 4.20.6 from mainline-ppa and the
  latest bluetooth/bluz ppa without success.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-45.48-lowlatency 4.15.18
  Uname: Linux 4.15.0-45-lowlatency x86_64
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: XFCE
  Date: Sun Feb  3 23:51:29 2019
  DistUpgraded: 2019-02-03 21:49:33,752 DEBUG /openCache(), new cache size 92675
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus: virtualbox, 5.2.18, 4.15.0-45-lowlatency, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA 
controller])
 Subsystem: Lenovo HD Graphics 620 [17aa:224b]
  InstallationDate: Installed on 2017-07-24 (559 days ago)
  InstallationMedia: Xubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215)
  MachineType: LENOVO 20HFCTO1WW
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-45-lowlatency 
root=UUID=8f8366ae-4d29-44cf-9b85-f83f1771eab1 ro quiet splash vt.handoff=1
  SourcePackage: xorg
  UpgradeStatus: Upgraded to bionic on 2019-02-03 (0 days ago)
  dmi.bios.date: 09/14/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N1WET51W (1.30 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20HFCTO1WW
  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:bvrN1WET51W(1.30):bd09/14/2018:svnLENOVO:pn20HFCTO1WW:pvrThinkPadT470s:rvnLENOVO:rn20HFCTO1WW:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad T470s
  dmi.product.name: 20HFCTO1WW
  dmi.product.version: ThinkPad T470s
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A

[Desktop-packages] [Bug 1815354] [NEW] BCM 43142 driver not installed - no WiFi

2019-02-10 Thread Leó Kolbeinsson

Public bug reported:

Disco daily Lubuntu 09.02.2019 and Disco daily Kubuntu 10.02.2019

BCM 43142 drivers not installed resulting in no WiFi during and after
installation.

I was able to attach ethernet cable and use the command line "ubuntu-
drivers" command to install the drivers and all worked well after that.

Of course if running a machine with no ethernet then this is a huge
problem for the user.

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

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

Title:
  BCM 43142 driver not installed - no WiFi

Status in network-manager package in Ubuntu:
  New

Bug description:
  Disco daily Lubuntu 09.02.2019 and Disco daily Kubuntu 10.02.2019

  BCM 43142 drivers not installed resulting in no WiFi during and after
  installation.

  I was able to attach ethernet cable and use the command line "ubuntu-
  drivers" command to install the drivers and all worked well after
  that.

  Of course if running a machine with no ethernet then this is a huge
  problem for the user.

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

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

[Desktop-packages] [Bug 1603430] Re: Firefox dropdowns in wrong location

2019-02-10 Thread Robert Foss

This issue is still apparent on Ubuntu 18.10

Package: firefox
Architecture: amd64
Version: 63.0+build1-0ubuntu1

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

Title:
  Firefox dropdowns in wrong location

Status in Linux Mint:
  New
Status in cinnamon-desktop-environment package in Ubuntu:
  Confirmed
Status in firefox package in Ubuntu:
  Confirmed

Bug description:
  On Mint 17.3 Cinnamon 64bit.

  Steps to reproduce:
   * Do a fresh install.
   * Run mintupdate and update all packages.
   * Run firefox. 
   * Start right clicking on the page to open the context menu. Resize the 
window and perhaps move it around the screen a couple of times. Right click 
some more. 
   * Observer that, eventually, the context menu will start to appear in 
incorrect locations on the screen. The same also happens with the search bar, 
text fields and any other dropdown box.

  In the worst embodiment of the bug, the menu opens underneath the
  pointer and treats the release of the mouse button as a click, and so
  does things the user does not want to do.

  I believe the root cause is the following bug in GTK+ 3.10.8. Firefox
  switched over to using GTK+3 in version 46 which is when this bug
  appeared and has been there ever since.

  https://bugzilla.gnome.org/show_bug.cgi?id=758609
  https://bugzilla.mozilla.org/show_bug.cgi?id=1022241

  Mozilla aren't going to fix it because it's a GTK bug. GTK have
  already fixed it. But Mint 17.3 remains on GTK+ 3.10.8 which does not
  have the patch.

  Please roll out the patch for us 17.3 users who cannot upgrade. I can
  confirm that the problem is solved in Mint 18.

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

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

[Desktop-packages] [Bug 1803021] Re: No tutorials

2019-02-10 Thread anatoly techtonik

I see that translations is the primary concern even though the spurious
error message in English is much worse than friendly explanation in
English.

But I just wonder what is your C++-fu? Don't get me wrong - I am unable
to write the patch myself, because my C++ skills are poor, and I am not
saying that package maintainer of C++ project should have C++ skills.
But if Inkscape was in Python, placing an exception handler into menu
action handle doesn't seem like a lot of codepaths.

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

Title:
  No tutorials

Status in inkscape package in Ubuntu:
  Won't Fix

Bug description:
  When selecting `Help -> Tutorials` the error message is shown and no
  tutorial is loaded.

  Failed to load the requested file /usr/share/inkscape/tutorials
  /tutorial-basic.svg

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: inkscape 0.92.3-4
  ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12
  Uname: Linux 4.18.0-10-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13.1
  Architecture: amd64
  CurrentDesktop: i3
  Date: Tue Nov 13 05:18:54 2018
  InstallationDate: Installed on 2018-11-01 (11 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  SourcePackage: inkscape
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1815348] [NEW] package libappindicator0.1-cil 12.10.1+16.04.20170215-0ubuntu1 failed to install/upgrade: subprocess installed post-installation script returned error exit statu

2019-02-10 Thread cirus

Public bug reported:

l'errore compare all'avvio di ubuntu

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: libappindicator0.1-cil 12.10.1+16.04.20170215-0ubuntu1
ProcVersionSignature: Ubuntu 4.4.0-116.140-generic 4.4.98
Uname: Linux 4.4.0-116-generic i686
ApportVersion: 2.20.1-0ubuntu2.15
Architecture: i386
Date: Sun Jan 20 19:33:19 2019
ErrorMessage: subprocess installed post-installation script returned error exit 
status 134
InstallationDate: Installed on 2013-11-03 (1925 days ago)
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release i386 (20110427.1)
PackageArchitecture: all
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.4
 apt  1.2.29
SourcePackage: libappindicator
Title: package libappindicator0.1-cil 12.10.1+16.04.20170215-0ubuntu1 failed to 
install/upgrade: subprocess installed post-installation script returned error 
exit status 134
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: apport-package i386 xenial

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

Title:
  package libappindicator0.1-cil 12.10.1+16.04.20170215-0ubuntu1 failed
  to install/upgrade: subprocess installed post-installation script
  returned error exit status 134

Status in libappindicator package in Ubuntu:
  New

Bug description:
  l'errore compare all'avvio di ubuntu

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libappindicator0.1-cil 12.10.1+16.04.20170215-0ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-116.140-generic 4.4.98
  Uname: Linux 4.4.0-116-generic i686
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: i386
  Date: Sun Jan 20 19:33:19 2019
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 134
  InstallationDate: Installed on 2013-11-03 (1925 days ago)
  InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release i386 (20110427.1)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.4
   apt  1.2.29
  SourcePackage: libappindicator
  Title: package libappindicator0.1-cil 12.10.1+16.04.20170215-0ubuntu1 failed 
to install/upgrade: subprocess installed post-installation script returned 
error exit status 134
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 241937]

2019-02-10 Thread Gijskruitbosch+bugs

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

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

Title:
  Handle tabs like other gnome apps

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

Bug description:
  Binary package hint: firefox-3.0

  I have noticed that dragging tabs in Firefox does not work like in
  other gnome apps.

  Basically, you can drag tabs along the tab bar to change their order,
  like in so many gnome apps. But you can also drag them up and down: if
  you accidentally drag them up and drop them on the bookmark bar, you
  add a bookmark for it. and if you accidentally drag it down to the
  browser area, you load that page again.

  As you can see in the attached screenshot, the "good" area is quite
  small compared to the "bad" areas, so it's actually very easy to miss
  and drop the tab on a wrong place, and perform an action you didn't
  want. I propose that tabs in Firefox should behave just like gnome
  apps, and be able to move only left or right.

  If you don't agree because you like being able to easily adding a
  bookmark or loading a page, think that the same exact effect can be
  achieved by dragging the favicon instead of the tab.

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

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

[Desktop-packages] [Bug 241937]

Comment on attachment 8902388
Bug 450915 - Increase the drag space of the TabsToolbar by 15px on the bottom 
to improve the tab reordering experience.

Review request updated; see interdiff:
https://reviewboard.mozilla.org/r/173956/diff/2-3/

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

Title:
  Handle tabs like other gnome apps

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

Bug description:
  Binary package hint: firefox-3.0

  I have noticed that dragging tabs in Firefox does not work like in
  other gnome apps.

  Basically, you can drag tabs along the tab bar to change their order,
  like in so many gnome apps. But you can also drag them up and down: if
  you accidentally drag them up and drop them on the bookmark bar, you
  add a bookmark for it. and if you accidentally drag it down to the
  browser area, you load that page again.

  As you can see in the attached screenshot, the "good" area is quite
  small compared to the "bad" areas, so it's actually very easy to miss
  and drop the tab on a wrong place, and perform an action you didn't
  want. I propose that tabs in Firefox should behave just like gnome
  apps, and be able to move only left or right.

  If you don't agree because you like being able to easily adding a
  bookmark or loading a page, think that the same exact effect can be
  achieved by dragging the favicon instead of the tab.

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

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

[Desktop-packages] [Bug 241937]

Created attachment 8902388
Bug 450915 - Increase the drag space of the TabsToolbar by 15px on the bottom 
to improve the tab reordering experience.

Review commit: https://reviewboard.mozilla.org/r/173956/diff/#index_header
See other reviews: https://reviewboard.mozilla.org/r/173956/

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

Title:
  Handle tabs like other gnome apps

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

Bug description:
  Binary package hint: firefox-3.0

  I have noticed that dragging tabs in Firefox does not work like in
  other gnome apps.

  Basically, you can drag tabs along the tab bar to change their order,
  like in so many gnome apps. But you can also drag them up and down: if
  you accidentally drag them up and drop them on the bookmark bar, you
  add a bookmark for it. and if you accidentally drag it down to the
  browser area, you load that page again.

  As you can see in the attached screenshot, the "good" area is quite
  small compared to the "bad" areas, so it's actually very easy to miss
  and drop the tab on a wrong place, and perform an action you didn't
  want. I propose that tabs in Firefox should behave just like gnome
  apps, and be able to move only left or right.

  If you don't agree because you like being able to easily adding a
  bookmark or loading a page, think that the same exact effect can be
  achieved by dragging the favicon instead of the tab.

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

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

[Desktop-packages] [Bug 241937]

Comment on attachment 8902388
Bug 450915 - Increase the drag space of the TabsToolbar by 15px on the bottom 
to improve the tab reordering experience.

https://reviewboard.mozilla.org/r/173956/#review182352

::: browser/base/content/browser.css:184
(Diff revision 2)
>  .tabbrowser-tabs[movingtab] > .tabbrowser-tab[fadein]:not([selected]) {
>transition: transform 200ms var(--animation-easing-function);
>  }
>  
> +#TabsToolbar[movingtab] > .tabbrowser-tabs {
> +  padding-bottom: 20px;

The more we increase this the harder it is to tear off a tab without
making a large mouse movement. We're trying to balance ease of
reordering tabs and tearing off tabs.

Chrome looks to tear off at about 15 pixes from their tab bar, even
though their navbar measures about 35px tall.

Edge tears off around 8-10px, but their implementation treats reordering
and tearing off pretty much as one-in-the-same.

Doing this for the top and the menubar isn't as straightforward due to
the visibility of the menubar etc and didn't seem worth the extra
complexity for a "nice-to-have".

I'll lower our amount to be closer to Chrome since we don't have a
metric that says what is the *best* value here, and we don't want to
make tearing tabs off too much harder.

::: browser/themes/shared/tabs.inc.css:29
(Diff revision 2)
>  :root:-moz-lwtheme {
>--tab-line-color: var(--lwt-accent-color);
>  }
>  
>  #tabbrowser-tabs,
> +#tabbrowser-tabs > .tabbrowser-arrowscrollbox,

This was answered in comment 14. Because of how -moz-box-align:stretch;
is applying the space, the tabs shrink in size from 33px to 29px (on
Windows default density) with the increased padding-bottom.

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

Title:
  Handle tabs like other gnome apps

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

Bug description:
  Binary package hint: firefox-3.0

  I have noticed that dragging tabs in Firefox does not work like in
  other gnome apps.

  Basically, you can drag tabs along the tab bar to change their order,
  like in so many gnome apps. But you can also drag them up and down: if
  you accidentally drag them up and drop them on the bookmark bar, you
  add a bookmark for it. and if you accidentally drag it down to the
  browser area, you load that page again.

  As you can see in the attached screenshot, the "good" area is quite
  small compared to the "bad" areas, so it's actually very easy to miss
  and drop the tab on a wrong place, and perform an action you didn't
  want. I propose that tabs in Firefox should behave just like gnome
  apps, and be able to move only left or right.

  If you don't agree because you like being able to easily adding a
  bookmark or loading a page, think that the same exact effect can be
  achieved by dragging the favicon instead of the tab.

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

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

[Desktop-packages] [Bug 241937]

2019-02-10 Thread yfdyh000

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

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

Title:
  Handle tabs like other gnome apps

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

Bug description:
  Binary package hint: firefox-3.0

  I have noticed that dragging tabs in Firefox does not work like in
  other gnome apps.

  Basically, you can drag tabs along the tab bar to change their order,
  like in so many gnome apps. But you can also drag them up and down: if
  you accidentally drag them up and drop them on the bookmark bar, you
  add a bookmark for it. and if you accidentally drag it down to the
  browser area, you load that page again.

  As you can see in the attached screenshot, the "good" area is quite
  small compared to the "bad" areas, so it's actually very easy to miss
  and drop the tab on a wrong place, and perform an action you didn't
  want. I propose that tabs in Firefox should behave just like gnome
  apps, and be able to move only left or right.

  If you don't agree because you like being able to easily adding a
  bookmark or loading a page, think that the same exact effect can be
  achieved by dragging the favicon instead of the tab.

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

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

[Desktop-packages] [Bug 241937]

2019-02-10 Thread Aryx-bugmail

https://hg.mozilla.org/mozilla-central/rev/481d7cc2f6f0

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

Title:
  Handle tabs like other gnome apps

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

Bug description:
  Binary package hint: firefox-3.0

  I have noticed that dragging tabs in Firefox does not work like in
  other gnome apps.

  Basically, you can drag tabs along the tab bar to change their order,
  like in so many gnome apps. But you can also drag them up and down: if
  you accidentally drag them up and drop them on the bookmark bar, you
  add a bookmark for it. and if you accidentally drag it down to the
  browser area, you load that page again.

  As you can see in the attached screenshot, the "good" area is quite
  small compared to the "bad" areas, so it's actually very easy to miss
  and drop the tab on a wrong place, and perform an action you didn't
  want. I propose that tabs in Firefox should behave just like gnome
  apps, and be able to move only left or right.

  If you don't agree because you like being able to easily adding a
  bookmark or loading a page, think that the same exact effect can be
  achieved by dragging the favicon instead of the tab.

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

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

[Desktop-packages] [Bug 241937]

Comment on attachment 8902388
Bug 450915 - Increase the drag space of the TabsToolbar by 15px on the bottom 
to improve the tab reordering experience.

Review request updated; see interdiff:
https://reviewboard.mozilla.org/r/173956/diff/1-2/

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

Title:
  Handle tabs like other gnome apps

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

Bug description:
  Binary package hint: firefox-3.0

  I have noticed that dragging tabs in Firefox does not work like in
  other gnome apps.

  Basically, you can drag tabs along the tab bar to change their order,
  like in so many gnome apps. But you can also drag them up and down: if
  you accidentally drag them up and drop them on the bookmark bar, you
  add a bookmark for it. and if you accidentally drag it down to the
  browser area, you load that page again.

  As you can see in the attached screenshot, the "good" area is quite
  small compared to the "bad" areas, so it's actually very easy to miss
  and drop the tab on a wrong place, and perform an action you didn't
  want. I propose that tabs in Firefox should behave just like gnome
  apps, and be able to move only left or right.

  If you don't agree because you like being able to easily adding a
  bookmark or loading a page, think that the same exact effect can be
  achieved by dragging the favicon instead of the tab.

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

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

[Desktop-packages] [Bug 241937]

2019-02-10 Thread Pulsebot

Pushed by jw...@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/481d7cc2f6f0
Increase the drag space of the TabsToolbar by 15px on the bottom to improve the 
tab reordering experience. r=Gijs

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

Title:
  Handle tabs like other gnome apps

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

Bug description:
  Binary package hint: firefox-3.0

  I have noticed that dragging tabs in Firefox does not work like in
  other gnome apps.

  Basically, you can drag tabs along the tab bar to change their order,
  like in so many gnome apps. But you can also drag them up and down: if
  you accidentally drag them up and drop them on the bookmark bar, you
  add a bookmark for it. and if you accidentally drag it down to the
  browser area, you load that page again.

  As you can see in the attached screenshot, the "good" area is quite
  small compared to the "bad" areas, so it's actually very easy to miss
  and drop the tab on a wrong place, and perform an action you didn't
  want. I propose that tabs in Firefox should behave just like gnome
  apps, and be able to move only left or right.

  If you don't agree because you like being able to easily adding a
  bookmark or loading a page, think that the same exact effect can be
  achieved by dragging the favicon instead of the tab.

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

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

[Desktop-packages] [Bug 241937]

2019-02-10 Thread Dao+bmo

Comment on attachment 8902388
Bug 450915 - Increase the drag space of the TabsToolbar by 15px on the bottom 
to improve the tab reordering experience.

https://reviewboard.mozilla.org/r/173956/#review179384

::: browser/base/content/browser.css:189
(Diff revision 1)
> +  padding-bottom: 20px;
> +}
> +
> +#TabsToolbar[movingtab] + #nav-bar {
> +  margin-top: -20px;
> +  pointer-events: none;

This breaks dropping tabs on the bookmarks menu button

::: browser/themes/shared/tabs.inc.css:29
(Diff revision 1)
>  :root:-moz-lwtheme {
>--tab-line-color: var(--lwt-accent-color);
>  }
>  
>  #tabbrowser-tabs,
> +#tabbrowser-tabs > .tabbrowser-arrowscrollbox,

Why is this needed?

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

Title:
  Handle tabs like other gnome apps

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

Bug description:
  Binary package hint: firefox-3.0

  I have noticed that dragging tabs in Firefox does not work like in
  other gnome apps.

  Basically, you can drag tabs along the tab bar to change their order,
  like in so many gnome apps. But you can also drag them up and down: if
  you accidentally drag them up and drop them on the bookmark bar, you
  add a bookmark for it. and if you accidentally drag it down to the
  browser area, you load that page again.

  As you can see in the attached screenshot, the "good" area is quite
  small compared to the "bad" areas, so it's actually very easy to miss
  and drop the tab on a wrong place, and perform an action you didn't
  want. I propose that tabs in Firefox should behave just like gnome
  apps, and be able to move only left or right.

  If you don't agree because you like being able to easily adding a
  bookmark or loading a page, think that the same exact effect can be
  achieved by dragging the favicon instead of the tab.

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

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

[Desktop-packages] [Bug 241937]

Comment on attachment 8902388
Bug 450915 - Increase the drag space of the TabsToolbar by 15px on the bottom 
to improve the tab reordering experience.

Review request updated; see interdiff:
https://reviewboard.mozilla.org/r/173956/diff/3-4/

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

Title:
  Handle tabs like other gnome apps

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

Bug description:
  Binary package hint: firefox-3.0

  I have noticed that dragging tabs in Firefox does not work like in
  other gnome apps.

  Basically, you can drag tabs along the tab bar to change their order,
  like in so many gnome apps. But you can also drag them up and down: if
  you accidentally drag them up and drop them on the bookmark bar, you
  add a bookmark for it. and if you accidentally drag it down to the
  browser area, you load that page again.

  As you can see in the attached screenshot, the "good" area is quite
  small compared to the "bad" areas, so it's actually very easy to miss
  and drop the tab on a wrong place, and perform an action you didn't
  want. I propose that tabs in Firefox should behave just like gnome
  apps, and be able to move only left or right.

  If you don't agree because you like being able to easily adding a
  bookmark or loading a page, think that the same exact effect can be
  achieved by dragging the favicon instead of the tab.

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

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

[Desktop-packages] [Bug 241937]

2019-02-10 Thread Gijskruitbosch+bugs

Comment on attachment 8902388
Bug 450915 - Increase the drag space of the TabsToolbar by 15px on the bottom 
to improve the tab reordering experience.

https://reviewboard.mozilla.org/r/173956/#review182276

r+ with the downloads and home button included. We can followup making
the 20px match the navbar height more exactly, and/or dealing with the
menubar.

::: browser/base/content/browser.css:184
(Diff revision 2)
>  .tabbrowser-tabs[movingtab] > .tabbrowser-tab[fadein]:not([selected]) {
>transition: transform 200ms var(--animation-easing-function);
>  }
>  
> +#TabsToolbar[movingtab] > .tabbrowser-tabs {
> +  padding-bottom: 20px;

Clever. Two questions:

- the 20px feels kind of arbitrary. I guess this should basically be the navbar 
height, right? Is there some way we can more closely approximate this?
- should we also do the same for the top and the menubar, if the menubar is 
permanently visible (so on non-osx) ?

::: browser/base/content/browser.css:193
(Diff revision 2)
> +  margin-top: -20px;
> +  pointer-events: none;
> +}
> +
> +/* Allow dropping a tab on the bookmarks-menu-button to create a bookmark. */
> +#TabsToolbar[movingtab] + #nav-bar > #nav-bar-customization-target > 
> #bookmarks-menu-button {

We should do the same for the downloads and the home button, which both
also do reasonable things if dropping tabs on them.

::: browser/themes/shared/tabs.inc.css:29
(Diff revision 2)
>  :root:-moz-lwtheme {
>--tab-line-color: var(--lwt-accent-color);
>  }
>  
>  #tabbrowser-tabs,
> +#tabbrowser-tabs > .tabbrowser-arrowscrollbox,

Just for my (& future) understanding, why was this necessary?

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

Title:
  Handle tabs like other gnome apps

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

Bug description:
  Binary package hint: firefox-3.0

  I have noticed that dragging tabs in Firefox does not work like in
  other gnome apps.

  Basically, you can drag tabs along the tab bar to change their order,
  like in so many gnome apps. But you can also drag them up and down: if
  you accidentally drag them up and drop them on the bookmark bar, you
  add a bookmark for it. and if you accidentally drag it down to the
  browser area, you load that page again.

  As you can see in the attached screenshot, the "good" area is quite
  small compared to the "bad" areas, so it's actually very easy to miss
  and drop the tab on a wrong place, and perform an action you didn't
  want. I propose that tabs in Firefox should behave just like gnome
  apps, and be able to move only left or right.

  If you don't agree because you like being able to easily adding a
  bookmark or loading a page, think that the same exact effect can be
  achieved by dragging the favicon instead of the tab.

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

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

[Desktop-packages] [Bug 241937]

Comment on attachment 8902388
Bug 450915 - Increase the drag space of the TabsToolbar by 15px on the bottom 
to improve the tab reordering experience.

Redirecting to Gijs who can hopefully get to this sooner.

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

Title:
  Handle tabs like other gnome apps

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

Bug description:
  Binary package hint: firefox-3.0

  I have noticed that dragging tabs in Firefox does not work like in
  other gnome apps.

  Basically, you can drag tabs along the tab bar to change their order,
  like in so many gnome apps. But you can also drag them up and down: if
  you accidentally drag them up and drop them on the bookmark bar, you
  add a bookmark for it. and if you accidentally drag it down to the
  browser area, you load that page again.

  As you can see in the attached screenshot, the "good" area is quite
  small compared to the "bad" areas, so it's actually very easy to miss
  and drop the tab on a wrong place, and perform an action you didn't
  want. I propose that tabs in Firefox should behave just like gnome
  apps, and be able to move only left or right.

  If you don't agree because you like being able to easily adding a
  bookmark or loading a page, think that the same exact effect can be
  achieved by dragging the favicon instead of the tab.

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

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

[Desktop-packages] [Bug 241937]

2019-02-10 Thread Stefan-georgiev

Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:57.0) Gecko/20100101
Firefox/57.0 (20170915100121)

This issue is verified as fixed with the latest Nightly build on
9/15/2017.

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

Title:
  Handle tabs like other gnome apps

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

Bug description:
  Binary package hint: firefox-3.0

  I have noticed that dragging tabs in Firefox does not work like in
  other gnome apps.

  Basically, you can drag tabs along the tab bar to change their order,
  like in so many gnome apps. But you can also drag them up and down: if
  you accidentally drag them up and drop them on the bookmark bar, you
  add a bookmark for it. and if you accidentally drag it down to the
  browser area, you load that page again.

  As you can see in the attached screenshot, the "good" area is quite
  small compared to the "bad" areas, so it's actually very easy to miss
  and drop the tab on a wrong place, and perform an action you didn't
  want. I propose that tabs in Firefox should behave just like gnome
  apps, and be able to move only left or right.

  If you don't agree because you like being able to easily adding a
  bookmark or loading a page, think that the same exact effect can be
  achieved by dragging the favicon instead of the tab.

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

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

[Desktop-packages] [Bug 241937]

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

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

Title:
  Handle tabs like other gnome apps

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

Bug description:
  Binary package hint: firefox-3.0

  I have noticed that dragging tabs in Firefox does not work like in
  other gnome apps.

  Basically, you can drag tabs along the tab bar to change their order,
  like in so many gnome apps. But you can also drag them up and down: if
  you accidentally drag them up and drop them on the bookmark bar, you
  add a bookmark for it. and if you accidentally drag it down to the
  browser area, you load that page again.

  As you can see in the attached screenshot, the "good" area is quite
  small compared to the "bad" areas, so it's actually very easy to miss
  and drop the tab on a wrong place, and perform an action you didn't
  want. I propose that tabs in Firefox should behave just like gnome
  apps, and be able to move only left or right.

  If you don't agree because you like being able to easily adding a
  bookmark or loading a page, think that the same exact effect can be
  achieved by dragging the favicon instead of the tab.

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

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

[Desktop-packages] [Bug 241937]

Comment on attachment 8902388
Bug 450915 - Increase the drag space of the TabsToolbar by 15px on the bottom 
to improve the tab reordering experience.

https://reviewboard.mozilla.org/r/173956/#review179384

> Why is this needed?

Without this, the tabs shrink in size from 33px to 29px (on Windows)
with the increased padding-bottom.

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

Title:
  Handle tabs like other gnome apps

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

Bug description:
  Binary package hint: firefox-3.0

  I have noticed that dragging tabs in Firefox does not work like in
  other gnome apps.

  Basically, you can drag tabs along the tab bar to change their order,
  like in so many gnome apps. But you can also drag them up and down: if
  you accidentally drag them up and drop them on the bookmark bar, you
  add a bookmark for it. and if you accidentally drag it down to the
  browser area, you load that page again.

  As you can see in the attached screenshot, the "good" area is quite
  small compared to the "bad" areas, so it's actually very easy to miss
  and drop the tab on a wrong place, and perform an action you didn't
  want. I propose that tabs in Firefox should behave just like gnome
  apps, and be able to move only left or right.

  If you don't agree because you like being able to easily adding a
  bookmark or loading a page, think that the same exact effect can be
  achieved by dragging the favicon instead of the tab.

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

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

[Desktop-packages] [Bug 241937]

2019-02-10 Thread yfdyh000

It should have a graphical identity (e.g. "+") for creating a new
window, and a perf to disable the behavior or adjust its threshold.

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

Title:
  Handle tabs like other gnome apps

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

Bug description:
  Binary package hint: firefox-3.0

  I have noticed that dragging tabs in Firefox does not work like in
  other gnome apps.

  Basically, you can drag tabs along the tab bar to change their order,
  like in so many gnome apps. But you can also drag them up and down: if
  you accidentally drag them up and drop them on the bookmark bar, you
  add a bookmark for it. and if you accidentally drag it down to the
  browser area, you load that page again.

  As you can see in the attached screenshot, the "good" area is quite
  small compared to the "bad" areas, so it's actually very easy to miss
  and drop the tab on a wrong place, and perform an action you didn't
  want. I propose that tabs in Firefox should behave just like gnome
  apps, and be able to move only left or right.

  If you don't agree because you like being able to easily adding a
  bookmark or loading a page, think that the same exact effect can be
  achieved by dragging the favicon instead of the tab.

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

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

[Desktop-packages] [Bug 1689825] Re: gnome-keyring not unlocked on xenial when dbus-user-session is installed

Could this be an incompatibility between i386 and amd64 packages?  I
have trouble adding my keys via ssh-add and after reading some comments
here and elsewhere gave removing dbus-user-session a try.  My computer
is amd64 with i386 foreign arch.  dbus-user-session was replaced with
dbus-user-session:i386 and a few other :386 packages.  After the
installation, the situation was much worse, with ssh-add completely
hanging now.

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

Title:
  gnome-keyring not unlocked on xenial when dbus-user-session is
  installed

Status in chromium-browser package in Ubuntu:
  Invalid
Status in dbus package in Ubuntu:
  Triaged
Status in flatpak package in Ubuntu:
  Fix Released

Bug description:
  1) Release: 16.04.2
  2) gnome-keyring: 3.18.3-0ubuntu2
  3) Login. gnome-keyring unlocks "login" features including for google chrome
  4) gnome-keyring is not unlocked, chrome takes 2 minutes to open and with no 
secure password features(sync) functioning.

  For the past couple days, chrome on Ubuntu 16.04 takes a REALLY long
  time (maybe 2 minutes) to start. Once chrome is started, I am not able
  to sync and any secure password features are broken. I found out this
  is due to gnome-keyring not being unlocked at login. There's also no
  way to unlock the "login" portion of the keyring from the running
  daemon by default. I have to kill the gnome-keyring process and start
  without "--login" as a parameter. Then the "login" section shows up
  which I'm able to unlock. From there chrome starts up instantly but
  asks the following:

  Enter password to unlock your login keyring
  The login keyring did not get unlocked when you logged into your computer

  After that, all of it's sync and secure features are functional.

  Starting google-chrome-stable from a command line at boot without
  running the above workaround shows the following error messages:

  Gkr-Message: secret service operation failed: Did not receive a reply. 
Possible causes include: the remote application did not send a reply, the 
message bus security policy blocked the reply, the reply timeout expired, or 
the network connection was broken.
  Gkr-Message: secret service operation failed: Did not receive a reply. 
Possible causes include: the remote application did not send a reply, the 
message bus security policy blocked the reply, the reply timeout expired, or 
the network connection was broken.
  [4364:4393:0510/100407.740292:ERROR:token_service_table.cc(130)] Failed to 
decrypt token for service AccountId-108842767310111573264
  [4364:4445:0510/100407.740292:ERROR:gcm_store_impl.cc(929)] Failed to restore 
security token.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: gnome-keyring 3.18.3-0ubuntu2
  ProcVersionSignature: Ubuntu 4.8.0-52.55~16.04.1-generic 4.8.17
  Uname: Linux 4.8.0-52-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  CurrentDesktop: GNOME-Flashback:Unity
  Date: Wed May 10 09:43:37 2017
  SourcePackage: gnome-keyring
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1803021] Re: No tutorials

2019-02-10 Thread Mattia Rizzolo

That's not easy to do.  Let me quote from my first reply:

> and it wouldn't even be trivial, since it's shared by many other
> codepaths and it would also cause bad translations since nobody woul
> be localizing that changed string).

i.e. that's a generic string used by many other functions, including the
regular "open file".

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

Title:
  No tutorials

Status in inkscape package in Ubuntu:
  Won't Fix

Bug description:
  When selecting `Help -> Tutorials` the error message is shown and no
  tutorial is loaded.

  Failed to load the requested file /usr/share/inkscape/tutorials
  /tutorial-basic.svg

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: inkscape 0.92.3-4
  ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12
  Uname: Linux 4.18.0-10-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13.1
  Architecture: amd64
  CurrentDesktop: i3
  Date: Tue Nov 13 05:18:54 2018
  InstallationDate: Installed on 2018-11-01 (11 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  SourcePackage: inkscape
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1803021] Re: No tutorials

2019-02-10 Thread anatoly techtonik

Thanks! That's much better. =) As a minimal workaround, can you replace the text

Failed to load the requested file /usr/share/inkscape/tutorials
/tutorial-basic.svg

with check for file presence and the following text if check failed

Inkscape Tutorials are shipped as a separate package, which
saves 50Mb of Inkscape package size. Install `inkscape-tutorials`
from Software Center or use `apt` from terminal:

   sudo apt install inkscape-tutorials


https://packages.ubuntu.com/cosmic/graphics/inkscape-tutorials

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

Title:
  No tutorials

Status in inkscape package in Ubuntu:
  Won't Fix

Bug description:
  When selecting `Help -> Tutorials` the error message is shown and no
  tutorial is loaded.

  Failed to load the requested file /usr/share/inkscape/tutorials
  /tutorial-basic.svg

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: inkscape 0.92.3-4
  ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12
  Uname: Linux 4.18.0-10-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13.1
  Architecture: amd64
  CurrentDesktop: i3
  Date: Tue Nov 13 05:18:54 2018
  InstallationDate: Installed on 2018-11-01 (11 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  SourcePackage: inkscape
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1815339] Re: Printer stopped printing paper size 4"x6" after update ghostscript to 9.26

2019-02-10 Thread Fedik

Additional, if I run a raw GS command, Ghostscript does not crashes.

gs -dQUIET -dPARANOIDSAFER -dNOPAUSE -dBATCH -dNOINTERPOLATE
-dNOMEDIAATTRS -dShowAcroForm -sOutputFile=foo.bar -sDEVICE=cups
-sMediaClass=Cassette -sMediaType=PhotopaperMatte -r600x600
-dDEVICEWIDTHPOINTS=288 -dDEVICEHEIGHTPOINTS=432 -dcupsBitsPerColor=8
-dcupsColorOrder=0 -dcupsColorSpace=6 -dcupsCompression=7
-dcupsRowFeed=2 -scupsPageSizeName=w288h432 -I/usr/share/cups/fonts -c
'<>setpagedevice' -f samplec.ps

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

Title:
  Printer stopped printing paper size 4"x6" after update ghostscript to
  9.26

Status in ghostscript package in Ubuntu:
  New

Bug description:
  
  I have an issue with Ghostscript and printing.
  I use Gutenprint for my Canon MG5440, and I cannot print a photo 4"x6" (or 
6"x4"), it does not print anything, however I still able to print A4 paper size.
  I use Ubuntu 18.04 and Gutenprint 5.3.1.

  The printing fail with message:
  
  [Job 143] Start rendering...
  [Job 143] Processing page 1...
  [Job 143]  Unable to open the initial device, quitting.
  [Job 143] Rendering completed
  ...
  [Job 143] PID 24869 (/usr/lib/cups/filter/gstoraster) stopped with status 1.
  ...
  [Job 143] printer-state-message="Filter failed"
  [Job 143] printer-state-reasons=none

  The message "Unable to open the initial device, quitting" comes from
  Ghostscript.

  
  When I downgrade Ghostscript to 9.22, 
  I am again able to print 4"x6" paper size.

  To downgrade: apt install ghostscript=9.22~dfsg+1-0ubuntu1
  libgs9=9.22~dfsg+1-0ubuntu1 libgs9-common=9.22~dfsg+1-0ubuntu1

  I found similar issue for HP printer at Debian https://bugs.debian.org
  /cgi-bin/bugreport.cgi?bug=908205

  
  System info:
  Description:  Ubuntu 18.04.1 LTS
  Release:  18.04

  ghostscript:
Installed: 9.26~dfsg+0-0ubuntu0.18.04.4
Candidate: 9.26~dfsg+0-0ubuntu0.18.04.4
Versions:
   *** 9.26~dfsg+0-0ubuntu0.18.04.4 500
  500 http://ua.archive.ubuntu.com/ubuntu bionic-updates/main amd64 
Packages
  500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 
Packages
  100 /var/lib/dpkg/status
   9.22~dfsg+1-0ubuntu1 500
  500 http://ua.archive.ubuntu.com/ubuntu bionic/main amd64 Packages

  cups:
Installed: 2.2.7-1ubuntu2.3
Candidate: 2.2.7-1ubuntu2.3
Versions:
   *** 2.2.7-1ubuntu2.3 500
  500 http://ua.archive.ubuntu.com/ubuntu bionic-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   2.2.7-1ubuntu2.2 500
  500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 
Packages
   2.2.7-1ubuntu2 500
  500 http://ua.archive.ubuntu.com/ubuntu bionic/main amd64 Packages

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

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

[Desktop-packages] [Bug 1815339] [NEW] Printer stopped printing paper size 4"x6" after update ghostscript to 9.26

2019-02-10 Thread Fedik

Public bug reported:


I have an issue with Ghostscript and printing.
I use Gutenprint for my Canon MG5440, and I cannot print a photo 4"x6" (or 
6"x4"), it does not print anything, however I still able to print A4 paper size.
I use Ubuntu 18.04 and Gutenprint 5.3.1.

The printing fail with message:

[Job 143] Start rendering...
[Job 143] Processing page 1...
[Job 143]  Unable to open the initial device, quitting.
[Job 143] Rendering completed
...
[Job 143] PID 24869 (/usr/lib/cups/filter/gstoraster) stopped with status 1.
...
[Job 143] printer-state-message="Filter failed"
[Job 143] printer-state-reasons=none

The message "Unable to open the initial device, quitting" comes from
Ghostscript.


When I downgrade Ghostscript to 9.22, 
I am again able to print 4"x6" paper size.

To downgrade: apt install ghostscript=9.22~dfsg+1-0ubuntu1
libgs9=9.22~dfsg+1-0ubuntu1 libgs9-common=9.22~dfsg+1-0ubuntu1

I found similar issue for HP printer at Debian https://bugs.debian.org
/cgi-bin/bugreport.cgi?bug=908205


System info:
Description:Ubuntu 18.04.1 LTS
Release:18.04

ghostscript:
  Installed: 9.26~dfsg+0-0ubuntu0.18.04.4
  Candidate: 9.26~dfsg+0-0ubuntu0.18.04.4
  Versions:
 *** 9.26~dfsg+0-0ubuntu0.18.04.4 500
500 http://ua.archive.ubuntu.com/ubuntu bionic-updates/main amd64 
Packages
500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 
Packages
100 /var/lib/dpkg/status
 9.22~dfsg+1-0ubuntu1 500
500 http://ua.archive.ubuntu.com/ubuntu bionic/main amd64 Packages

cups:
  Installed: 2.2.7-1ubuntu2.3
  Candidate: 2.2.7-1ubuntu2.3
  Versions:
 *** 2.2.7-1ubuntu2.3 500
500 http://ua.archive.ubuntu.com/ubuntu bionic-updates/main amd64 
Packages
100 /var/lib/dpkg/status
 2.2.7-1ubuntu2.2 500
500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 
Packages
 2.2.7-1ubuntu2 500
500 http://ua.archive.ubuntu.com/ubuntu bionic/main amd64 Packages

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


** Tags: printing

** Attachment added: "cups error log"
   
https://bugs.launchpad.net/bugs/1815339/+attachment/5237401/+files/error_log.zip

** Tags added: printing

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

Title:
  Printer stopped printing paper size 4"x6" after update ghostscript to
  9.26

Status in ghostscript package in Ubuntu:
  New

Bug description:
  
  I have an issue with Ghostscript and printing.
  I use Gutenprint for my Canon MG5440, and I cannot print a photo 4"x6" (or 
6"x4"), it does not print anything, however I still able to print A4 paper size.
  I use Ubuntu 18.04 and Gutenprint 5.3.1.

  The printing fail with message:
  
  [Job 143] Start rendering...
  [Job 143] Processing page 1...
  [Job 143]  Unable to open the initial device, quitting.
  [Job 143] Rendering completed
  ...
  [Job 143] PID 24869 (/usr/lib/cups/filter/gstoraster) stopped with status 1.
  ...
  [Job 143] printer-state-message="Filter failed"
  [Job 143] printer-state-reasons=none

  The message "Unable to open the initial device, quitting" comes from
  Ghostscript.

  
  When I downgrade Ghostscript to 9.22, 
  I am again able to print 4"x6" paper size.

  To downgrade: apt install ghostscript=9.22~dfsg+1-0ubuntu1
  libgs9=9.22~dfsg+1-0ubuntu1 libgs9-common=9.22~dfsg+1-0ubuntu1

  I found similar issue for HP printer at Debian https://bugs.debian.org
  /cgi-bin/bugreport.cgi?bug=908205

  
  System info:
  Description:  Ubuntu 18.04.1 LTS
  Release:  18.04

  ghostscript:
Installed: 9.26~dfsg+0-0ubuntu0.18.04.4
Candidate: 9.26~dfsg+0-0ubuntu0.18.04.4
Versions:
   *** 9.26~dfsg+0-0ubuntu0.18.04.4 500
  500 http://ua.archive.ubuntu.com/ubuntu bionic-updates/main amd64 
Packages
  500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 
Packages
  100 /var/lib/dpkg/status
   9.22~dfsg+1-0ubuntu1 500
  500 http://ua.archive.ubuntu.com/ubuntu bionic/main amd64 Packages

  cups:
Installed: 2.2.7-1ubuntu2.3
Candidate: 2.2.7-1ubuntu2.3
Versions:
   *** 2.2.7-1ubuntu2.3 500
  500 http://ua.archive.ubuntu.com/ubuntu bionic-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   2.2.7-1ubuntu2.2 500
  500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 
Packages
   2.2.7-1ubuntu2 500
  500 http://ua.archive.ubuntu.com/ubuntu bionic/main amd64 Packages

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

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

[Desktop-packages] [Bug 1800727] Re: [Regression] [Dell XPS 15 9575] Airplane mode key cannot deactivate airplane mode after update to xkb-data 2.23.1-1ubuntu1.18.10.1 from -proposed

2019-02-10 Thread Mario Vukelic

** Description changed:

+ Airplane mode works (enable and disable) after the eventual fixes in bug
+ #1740894 and the regression does not occur.
+ 
+ [Original report]
+ 
  Bug #1740894 proposed update to xkb-data 2.23.1-1ubuntu1.18.10.1 in
  order to pass KEY_RFKILL to userspace.
  
  Despite the issue described in bug #1740894, on Dell XPS 15 9575 the
  airplane mode key actually  worked flawlessly out-of-the-box after
  installing Cosmic at beginning of September, using xkb-data 2.23.
  
  Updating to the proposed xkb-data 2.23.1-1ubuntu1.18.10.1 however leads to 
the following issue:
  1. Press airplane mode key Fn+Pos1
  -> Works. Pop-up says "Airplane mode enabled", airplane icon appears in 
panel, Wifi and BT are off.
  2. Press Fn+Pos1 again
  -> Broken. Pop-up briefly says "Airplane mode disabled", then immediately 
changes to "... enabled", airplane icon remains in panel, Wifi and BT remain 
OFF.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: xkb-data 2.23.1-1ubuntu1.18.10.1
  ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12
  Uname: Linux 4.18.0-11-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Oct 30 22:13:45 2018
  Dependencies:
-  
+ 
  DistUpgraded: Fresh install
  DistroCodename: cosmic
  DistroVariant: ubuntu
  InstallationDate: Installed on 2018-09-13 (47 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Alpha amd64 (20180912)
  Lsusb:
-  Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
-  Bus 001 Device 003: ID 0489:e0a2 Foxconn / Hon Hai 
-  Bus 001 Device 004: ID 27c6:5395  
-  Bus 001 Device 002: ID 0bda:58f4 Realtek Semiconductor Corp. 
-  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
+  Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
+  Bus 001 Device 003: ID 0489:e0a2 Foxconn / Hon Hai
+  Bus 001 Device 004: ID 27c6:5395
+  Bus 001 Device 002: ID 0bda:58f4 Realtek Semiconductor Corp.
+  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. XPS 15 9575
  PackageArchitecture: all
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-11-generic 
root=UUID=26ff4c95-5f68-4121-b7d0-989fa705fcc8 ro quiet splash
  SourcePackage: xkeyboard-config
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/08/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.1.9
  dmi.board.name: 0C32VW
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.1.9:bd08/08/2018:svnDellInc.:pnXPS159575:pvr:rvnDellInc.:rn0C32VW:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 15 9575
  dmi.product.sku: 080D
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.95-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.2-0ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.2-0ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.1-3ubuntu2.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-3

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

Title:
  [Regression] [Dell XPS 15 9575]  Airplane mode key cannot deactivate
  airplane mode after update to xkb-data 2.23.1-1ubuntu1.18.10.1 from
  -proposed

Status in xkeyboard-config package in Ubuntu:
  Fix Released

Bug description:
  Airplane mode works (enable and disable) after the eventual fixes in
  bug #1740894 and the regression does not occur.

  [Original report]

  Bug #1740894 proposed update to xkb-data 2.23.1-1ubuntu1.18.10.1 in
  order to pass KEY_RFKILL to userspace.

  Despite the issue described in bug #1740894, on Dell XPS 15 9575 the
  airplane mode key actually  worked flawlessly out-of-the-box after
  installing Cosmic at beginning of September, using xkb-data 2.23.

  Updating to the proposed xkb-data 2.23.1-1ubuntu1.18.10.1 however leads to 
the following issue:
  1. Press airplane mode key Fn+Pos1
  -> Works. Pop-up says "Airplane mode enabled", airplane icon appears in 
panel, Wifi and BT are off.
  2. Press Fn+Pos1 again
  -> Broken. Pop-up briefly says "Airplane mode disabled", then immediately 
changes to "... enabled", airplane icon remains in panel, Wifi and BT remain 
OFF.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: xkb-data 2.23.1-1ubuntu1.18.10.1
  ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12
  Uname: Linux 4.18.0-11-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13
  Architecture: amd64

[Desktop-packages] [Bug 437288] Re: Nautilus uses a lot of heap memory coping large amounts of data

2019-02-10 Thread Rex de Jong

Re-reading my answer, I doubt it is clear what I meant. What I mean is:

No, the issue is not occurring anymore. I have been using Nautilus in
the form of GNOME Files, and have copied large amounts of data
frequently. Noted that I use Debian Stable, so I guess it is save to say
it will not occur in Ubuntu.

Hope that is a bit more clear ;)

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

Title:
  Nautilus uses a lot of heap memory coping large amounts of data

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

Bug description:
  Binary package hint: nautilus

  While copying a lot of data (>250GB), Nautilus uses up a lot of
  memory. This memory is not given back to the system at any time.
  Depending on the amount of copying Nautilus uses from 800MB up to 3GB.

  Now using Ubuntu alpha 6 with Gnome 2.28, but this problemed also
  showed on my old install (Arch Linux Gnome 2.26)

  I attached a printscreen of the memory in the .png. Memory in use that
  time: 2.4GB. Amount of data copied (not cutted) was about 750GB.

  ProblemType: Bug
  Architecture: amd64
  Date: Sat Sep 26 19:20:11 2009
  DistroRelease: Ubuntu 9.10
  NonfreeKernelModules: nvidia
  Package: nautilus 1:2.28.0-0ubuntu2
  ProcEnviron:
   LANG=nl_NL.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 2.6.31-11.36-generic
  SourcePackage: nautilus
  Uname: Linux 2.6.31-11-generic x86_64

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

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

[Desktop-packages] [Bug 1740894] Re: KEY_RFKILL is not passed to userspace

2019-02-10 Thread Mario Vukelic

And I can confirm that it is fixed on Disco as well

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

Title:
  KEY_RFKILL is not passed to userspace

Status in libxkbcommon package in Ubuntu:
  Fix Released
Status in xkeyboard-config package in Ubuntu:
  Fix Released
Status in xorgproto package in Ubuntu:
  Fix Released
Status in xkeyboard-config source package in Bionic:
  Fix Committed
Status in xkeyboard-config source package in Cosmic:
  Fix Committed
Status in xkeyboard-config source package in Disco:
  Fix Released

Bug description:
  * Impact
  the airplane mode key doesn't work in GNOME

  * Test case
  Use a laptop with a key to activate airplane mode, it should toggle the 
corresponding mode on/off when used

  * Regression potential
  The change adds a new key definition but doesn't touch any existing one, 
nothing specific to test out of the new key working

  -

  There are a couple things going on, that could be fixed by a Debian or
  Ubuntu maintainer:

  - libxkbdcommon needs to be updated from 0.7.1 to 0.7.2. This
  introduces the RFKill key: https://lists.freedesktop.org/archives
  /wayland-devel/2017-August/034721.html

  - x11-proto needs a new release. This commit added RFKill, but it is
  not in a release:
  
https://cgit.freedesktop.org/xorg/proto/xproto/commit/?id=98a32d328e7195e12c38baa877917335bceffbaf

  - Likely other X11 packages need to be rebuilt.

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

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

[Desktop-packages] [Bug 1815338] [NEW] Pressing Alt+ accelerators do not bring up the menu

2019-02-10 Thread Dan Dascalescu

Public bug reported:

If I press and hold Alt, the accelerators for the menu bar (F,
E, S, T, Tab, H) become underlined, but pressing
the F/E/S/T/b/H key does not bring up the pull-down menu.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: gnome-terminal 3.28.2-1ubuntu1~18.04.1
ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18
Uname: Linux 4.15.0-45-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.5
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Sun Feb 10 01:22:49 2019
ExecutablePath: /usr/lib/gnome-terminal/gnome-terminal-server
InstallationDate: Installed on 2018-12-31 (41 days ago)
InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725)
ProcEnviron:
 LANG=en_US.UTF-8
 PATH=(custom, no user)
 SHELL=/bin/bash
 XDG_RUNTIME_DIR=
SourcePackage: gnome-terminal
UpgradeStatus: No upgrade log present (probably fresh install)

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

Title:
  Pressing Alt+ accelerators do not bring up the menu

Status in gnome-terminal package in Ubuntu:
  New

Bug description:
  If I press and hold Alt, the accelerators for the menu bar (F,
  E, S, T, Tab, H) become underlined, but
  pressing the F/E/S/T/b/H key does not bring up the pull-down menu.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-terminal 3.28.2-1ubuntu1~18.04.1
  ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18
  Uname: Linux 4.15.0-45-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Feb 10 01:22:49 2019
  ExecutablePath: /usr/lib/gnome-terminal/gnome-terminal-server
  InstallationDate: Installed on 2018-12-31 (41 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  SourcePackage: gnome-terminal
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 437288] Re: Nautilus uses a lot of heap memory coping large amounts of data

2019-02-10 Thread Rex de Jong

Hi,

No, I do not have the issue anymore. Have been using Debian Stable for
the last couple of years.

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

Title:
  Nautilus uses a lot of heap memory coping large amounts of data

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

Bug description:
  Binary package hint: nautilus

  While copying a lot of data (>250GB), Nautilus uses up a lot of
  memory. This memory is not given back to the system at any time.
  Depending on the amount of copying Nautilus uses from 800MB up to 3GB.

  Now using Ubuntu alpha 6 with Gnome 2.28, but this problemed also
  showed on my old install (Arch Linux Gnome 2.26)

  I attached a printscreen of the memory in the .png. Memory in use that
  time: 2.4GB. Amount of data copied (not cutted) was about 750GB.

  ProblemType: Bug
  Architecture: amd64
  Date: Sat Sep 26 19:20:11 2009
  DistroRelease: Ubuntu 9.10
  NonfreeKernelModules: nvidia
  Package: nautilus 1:2.28.0-0ubuntu2
  ProcEnviron:
   LANG=nl_NL.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 2.6.31-11.36-generic
  SourcePackage: nautilus
  Uname: Linux 2.6.31-11-generic x86_64

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

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

[Desktop-packages] [Bug 1560452] Re: DUALi mtp-probe causes loop