[Desktop-packages] [Bug 1830444] Re: IPv4 does not provide "Shared to other computers" method

[Dan Kortschak]

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

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

Title:
  IPv4 does not provide "Shared to other computers" method

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

Bug description:
  In previous versions of Ubuntu (16.04 and before), it was possible to
  specify the IPv4 method to use "Shared to other computers" directly
  from the top bar (via the via the nm-connection-editor/nm-applet).

  This ability is no longer available via the preferred network
  configuration panel in the gnome control center, i.e. without invoking
  either nm-connection-editor directly or via the nm-applet (which then
  doubles up the network controls in the top bar).

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-control-center 1:3.28.2-0ubuntu0.18.04.4
  ProcVersionSignature: Ubuntu 4.18.0-20.21~18.04.1-generic 4.18.20
  Uname: Linux 4.18.0-20-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat May 25 09:12:16 2019
  InstallationDate: Installed on 2019-05-22 (2 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  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/1830444/+subscriptions

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

[Desktop-packages] [Bug 1805561] Re: [nvidia] "Ubuntu on Wayland" login option is missing in 19.04 even though nvidia-drm.modeset=1 is set.

[Launchpad Bug Tracker]

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

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

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

Title:
  [nvidia] "Ubuntu on Wayland" login option is missing in 19.04 even
  though nvidia-drm.modeset=1 is set.

Status in gdm3 package in Ubuntu:
  Expired
Status in mutter package in Ubuntu:
  Expired

Bug description:
  No wayland in Beta of 19.04

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: xwayland 2:1.20.3-1ubuntu1
  ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12
  Uname: Linux 4.18.0-11-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  410.78  Sat Nov 10 22:09:04 
CST 2018
   GCC version:  gcc version 8.2.0 (Ubuntu 8.2.0-9ubuntu1)
  ApportVersion: 2.20.10-0ubuntu14
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Nov 27 22:33:12 2018
  DistUpgraded: 2018-11-07 22:10:40,058 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: disco
  DistroVariant: ubuntu
  DkmsStatus: nvidia, 410.78, 4.18.0-11-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA 
controller])
 Subsystem: Huawei Technologies Co., Ltd. UHD Graphics 620 [19e5:3e04]
 Subsystem: Huawei Technologies Co., Ltd. GP108M [GeForce MX150] [19e5:3e04]
  InstallationDate: Installed on 2018-08-01 (119 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 05c8:03c0 Cheng Uei Precision Industry Co., Ltd 
(Foxlink) 
   Bus 001 Device 002: ID 8087:0a2b Intel Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: HUAWEI MACH-WX9
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-11-generic 
root=UUID=b0227ec8-a2f0-4e84-921d-290520742391 ro quiet splash 
nvidia-drm.modeset=1 vt.handoff=1
  SourcePackage: xorg-server
  UpgradeStatus: Upgraded to disco on 2018-11-08 (20 days ago)
  XorgLog:
   
  dmi.bios.date: 06/05/2018
  dmi.bios.vendor: HUAWEI
  dmi.bios.version: 1.12
  dmi.board.name: MACH-WX9
  dmi.board.vendor: HUAWEI
  dmi.board.version: M14
  dmi.chassis.type: 10
  dmi.chassis.vendor: HUAWEI
  dmi.chassis.version: M14
  dmi.modalias: 
dmi:bvnHUAWEI:bvr1.12:bd06/05/2018:svnHUAWEI:pnMACH-WX9:pvrM14:rvnHUAWEI:rnMACH-WX9:rvrM14:cvnHUAWEI:ct10:cvrM14:
  dmi.product.family: HUAWEI MateBook X
  dmi.product.name: MACH-WX9
  dmi.product.sku: C128
  dmi.product.version: M14
  dmi.sys.vendor: HUAWEI
  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.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.3-1ubuntu1
  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+git20180925-2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-3

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

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

[Desktop-packages] [Bug 1805561] Re: [nvidia] "Ubuntu on Wayland" login option is missing in 19.04 even though nvidia-drm.modeset=1 is set.

[Launchpad Bug Tracker]

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

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

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

Title:
  [nvidia] "Ubuntu on Wayland" login option is missing in 19.04 even
  though nvidia-drm.modeset=1 is set.

Status in gdm3 package in Ubuntu:
  Expired
Status in mutter package in Ubuntu:
  Expired

Bug description:
  No wayland in Beta of 19.04

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: xwayland 2:1.20.3-1ubuntu1
  ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12
  Uname: Linux 4.18.0-11-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  410.78  Sat Nov 10 22:09:04 
CST 2018
   GCC version:  gcc version 8.2.0 (Ubuntu 8.2.0-9ubuntu1)
  ApportVersion: 2.20.10-0ubuntu14
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Nov 27 22:33:12 2018
  DistUpgraded: 2018-11-07 22:10:40,058 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: disco
  DistroVariant: ubuntu
  DkmsStatus: nvidia, 410.78, 4.18.0-11-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA 
controller])
 Subsystem: Huawei Technologies Co., Ltd. UHD Graphics 620 [19e5:3e04]
 Subsystem: Huawei Technologies Co., Ltd. GP108M [GeForce MX150] [19e5:3e04]
  InstallationDate: Installed on 2018-08-01 (119 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 05c8:03c0 Cheng Uei Precision Industry Co., Ltd 
(Foxlink) 
   Bus 001 Device 002: ID 8087:0a2b Intel Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: HUAWEI MACH-WX9
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-11-generic 
root=UUID=b0227ec8-a2f0-4e84-921d-290520742391 ro quiet splash 
nvidia-drm.modeset=1 vt.handoff=1
  SourcePackage: xorg-server
  UpgradeStatus: Upgraded to disco on 2018-11-08 (20 days ago)
  XorgLog:
   
  dmi.bios.date: 06/05/2018
  dmi.bios.vendor: HUAWEI
  dmi.bios.version: 1.12
  dmi.board.name: MACH-WX9
  dmi.board.vendor: HUAWEI
  dmi.board.version: M14
  dmi.chassis.type: 10
  dmi.chassis.vendor: HUAWEI
  dmi.chassis.version: M14
  dmi.modalias: 
dmi:bvnHUAWEI:bvr1.12:bd06/05/2018:svnHUAWEI:pnMACH-WX9:pvrM14:rvnHUAWEI:rnMACH-WX9:rvrM14:cvnHUAWEI:ct10:cvrM14:
  dmi.product.family: HUAWEI MateBook X
  dmi.product.name: MACH-WX9
  dmi.product.sku: C128
  dmi.product.version: M14
  dmi.sys.vendor: HUAWEI
  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.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.3-1ubuntu1
  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+git20180925-2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-3

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

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

[Desktop-packages] [Bug 1817658] Re: Netflix Video Player not available

[Launchpad Bug Tracker]

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

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

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

Title:
  Netflix Video Player not available

Status in firefox package in Ubuntu:
  Expired

Bug description:
  Ooops! Qualcosa è andato storto.

  Netflix Video Player non disponibile.

  Stiamo incontrando difficoltà a riprodurre Netflix tramite il tuo
  browser (mozilla firefox quantum 65).

  Assicurati di avere una versione ufficiale di Firefox.

  Codice di errore: F7355

  --
  Translated by Google:

  Ooops! Something went wrong.

  Netflix Video Player not available.

  We are having difficulty playing Netflix through your browser (mozilla
  firefox quantum 65).

  Make sure you have an official version of Firefox.

  Error code: F7355

  --

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: ubuntu-docs 18.04.4
  ProcVersionSignature: Ubuntu 4.18.0-15.16~18.04.1-generic 4.18.20
  Uname: Linux 4.18.0-15-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  CasperVersion: 1.394
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Feb 26 06:01:59 2019
  LiveMediaBuild: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210)
  PackageArchitecture: all
  SourcePackage: ubuntu-docs
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 597825]

[Ge3k0s]

(In reply to :Gijs from comment #84)
> We hide the menubar by default and have lived with this for nearly 20 years.
> I don't think it needs priority right now - we have enough on our plate as
> part of the Photon backlog.

I was thinking more about all the other places in the UI where these
underlined letters still live (as you said for 20 years so clearly for
too long), but I understand that Photon has already a big scope.

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

Title:
  Menu accelerators in Firefox don't follow the GNOME policy.

Status in Mozilla Firefox:
  Confirmed
Status in One Hundred Papercuts:
  Fix Released
Status in firefox package in Ubuntu:
  Fix Released

Bug description:
  Binary package hint: firefox

  The current GNOME default is that menu accelerators are hidden, and
  shown when you press the ALT key.

  Firefox doesn't observe this policy and have their menu accelerators
  displayed all the time.

  Also, pressing ALT alone in GNOME and Firefox doesn't invoke any menu
  command.

  This inconsistent behavior is a usability issue and also makes Ubuntu
  desktop look unprofessional.

  ProblemType: Bug
  DistroRelease: Ubuntu 10.04
  Package: firefox 3.6.3+nobinonly-0ubuntu4
  ProcVersionSignature: Ubuntu 2.6.32-22.36-generic 2.6.32.11+drm33.2
  Uname: Linux 2.6.32-22-generic x86_64
  Architecture: amd64
  Date: Wed Jun 23 21:37:05 2010
  EcryptfsInUse: Yes
  FirefoxPackages:
   firefox 3.6.3+nobinonly-0ubuntu4
   firefox-gnome-support 3.6.3+nobinonly-0ubuntu4
   firefox-branding 3.6.3+nobinonly-0ubuntu4
   abroswer N/A
   abrowser-branding N/A
  ProcEnviron:
   PATH=(custom, user)
   LANG=pl_PL.utf8
   SHELL=/bin/bash
  SourcePackage: firefox

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

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

[Desktop-packages] [Bug 424711]

[Bug-husbandry-bot]

https://bugzilla.mozilla.org/show_bug.cgi?id=1552613

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

Title:
  When menu icons are disabled, users must restart Firefox for the
  change to appear

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

Bug description:
  If a user disables menu icons, most applications reflect the change
  immediately. However, Firefox needs to be restarted before the change
  takes place. This can give the impression that Firefox is not honoring
  the setting.

  This has been confirmed with Firefox 3.7 on Ubuntu 10.04

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

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

[Desktop-packages] [Bug 597825]

[Gijskruitbosch+bugs]

We hide the menubar by default and have lived with this for nearly 20
years. I don't think it needs priority right now - we have enough on our
plate as part of the Photon backlog.

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

Title:
  Menu accelerators in Firefox don't follow the GNOME policy.

Status in Mozilla Firefox:
  Confirmed
Status in One Hundred Papercuts:
  Fix Released
Status in firefox package in Ubuntu:
  Fix Released

Bug description:
  Binary package hint: firefox

  The current GNOME default is that menu accelerators are hidden, and
  shown when you press the ALT key.

  Firefox doesn't observe this policy and have their menu accelerators
  displayed all the time.

  Also, pressing ALT alone in GNOME and Firefox doesn't invoke any menu
  command.

  This inconsistent behavior is a usability issue and also makes Ubuntu
  desktop look unprofessional.

  ProblemType: Bug
  DistroRelease: Ubuntu 10.04
  Package: firefox 3.6.3+nobinonly-0ubuntu4
  ProcVersionSignature: Ubuntu 2.6.32-22.36-generic 2.6.32.11+drm33.2
  Uname: Linux 2.6.32-22-generic x86_64
  Architecture: amd64
  Date: Wed Jun 23 21:37:05 2010
  EcryptfsInUse: Yes
  FirefoxPackages:
   firefox 3.6.3+nobinonly-0ubuntu4
   firefox-gnome-support 3.6.3+nobinonly-0ubuntu4
   firefox-branding 3.6.3+nobinonly-0ubuntu4
   abroswer N/A
   abrowser-branding N/A
  ProcEnviron:
   PATH=(custom, user)
   LANG=pl_PL.utf8
   SHELL=/bin/bash
  SourcePackage: firefox

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

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

[Desktop-packages] [Bug 424711] Re: When menu icons are disabled, users must restart Firefox for the change to appear

[Bug Watch Updater]

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

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

Title:
  When menu icons are disabled, users must restart Firefox for the
  change to appear

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

Bug description:
  If a user disables menu icons, most applications reflect the change
  immediately. However, Firefox needs to be restarted before the change
  takes place. This can give the impression that Firefox is not honoring
  the setting.

  This has been confirmed with Firefox 3.7 on Ubuntu 10.04

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

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

[Desktop-packages] [Bug 597825]

[Ge3k0s]

Could this be considered as part of Photon redesign ?

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

Title:
  Menu accelerators in Firefox don't follow the GNOME policy.

Status in Mozilla Firefox:
  Confirmed
Status in One Hundred Papercuts:
  Fix Released
Status in firefox package in Ubuntu:
  Fix Released

Bug description:
  Binary package hint: firefox

  The current GNOME default is that menu accelerators are hidden, and
  shown when you press the ALT key.

  Firefox doesn't observe this policy and have their menu accelerators
  displayed all the time.

  Also, pressing ALT alone in GNOME and Firefox doesn't invoke any menu
  command.

  This inconsistent behavior is a usability issue and also makes Ubuntu
  desktop look unprofessional.

  ProblemType: Bug
  DistroRelease: Ubuntu 10.04
  Package: firefox 3.6.3+nobinonly-0ubuntu4
  ProcVersionSignature: Ubuntu 2.6.32-22.36-generic 2.6.32.11+drm33.2
  Uname: Linux 2.6.32-22-generic x86_64
  Architecture: amd64
  Date: Wed Jun 23 21:37:05 2010
  EcryptfsInUse: Yes
  FirefoxPackages:
   firefox 3.6.3+nobinonly-0ubuntu4
   firefox-gnome-support 3.6.3+nobinonly-0ubuntu4
   firefox-branding 3.6.3+nobinonly-0ubuntu4
   abroswer N/A
   abrowser-branding N/A
  ProcEnviron:
   PATH=(custom, user)
   LANG=pl_PL.utf8
   SHELL=/bin/bash
  SourcePackage: firefox

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

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

[Desktop-packages] [Bug 1776475] Re: Unlocking existing session often requires several attempts.

[Magesh Dhasayyan]

I had the exact same issue. In my case, I upgraded xubuntu 16.04 to 18.04 and 
this issue started showing up. Pulseaudio was also not working.
>From further investigation, I noticed that chrome-remote-desktop was starting 
>Xsession and this was causing issues. I removed that package and it fixed the 
>issue.

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

Title:
  Unlocking existing session often requires several attempts.

Status in lightdm package in Ubuntu:
  Confirmed

Bug description:
  # Context

  * Computer with several X sessions opened.
  * Users switching from one opened session to another.
  * Lightdm opens new greeter, wait for typing password.
  * User types password.
  * Password is accepted.
  * System closes the current greeter (screen gets black for an instant).

  # Expected

  * User gets back to their already opened session.

  # Observed

  * System immediately opens another greeter.
  * User has to type password again.

  # Reproducible

  * Not always. At times, often, at other times, rare.

  # Additional information

  Users switch session via 
  dm-tool switch-to-user $OTHERUSER
  but I guess bug appears with other means (like menu item like "lock screen", 
etc).

  # Information requested

  lsb_release -rd

  Description:  Ubuntu 18.04 LTS
  Release:  18.04

  
  LC_ALL=C apt-cache policy lightdm

  lightdm:
Installed: 1.26.0-0ubuntu1
Candidate: 1.26.0-0ubuntu1
Version table:
   *** 1.26.0-0ubuntu1 500
  500 http://fr.archive.ubuntu.com/ubuntu bionic/universe amd64 Packages
  100 /var/lib/dpkg/status

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: lightdm 1.26.0-0ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
  Uname: Linux 4.15.0-23-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  Date: Tue Jun 12 14:14:52 2018
  ExecutablePath: /usr/sbin/lightdm
  InstallationDate: Installed on 2018-05-25 (18 days ago)
  InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Release amd64 
(20180426)
  ProcEnviron:
   LANG=fr_FR.UTF-8
   PATH=(custom, no user)
  SourcePackage: lightdm
  UpgradeStatus: No upgrade log present (probably fresh install)
  modified.conffile..etc.logrotate.d.lightdm: [modified]
  mtime.conffile..etc.logrotate.d.lightdm: 2018-05-25T06:19:22.081830

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

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

[Desktop-packages] [Bug 1798790] Re: Ubuntu login screen never appears when using the Nvidia driver (and setting WaylandEnable=false fixes it)

[Bug Watch Updater]

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

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

Title:
  Ubuntu login screen never appears when using the Nvidia driver (and
  setting WaylandEnable=false fixes it)

Status in gdm:
  Fix Released
Status in gdm3 package in Ubuntu:
  Confirmed
Status in mutter package in Ubuntu:
  Confirmed
Status in gdm3 source package in Eoan:
  Confirmed
Status in mutter source package in Eoan:
  Confirmed

Bug description:
  https://gitlab.gnome.org/GNOME/gdm/issues/483
  formerly https://gitlab.gnome.org/GNOME/gdm/issues/435

  ---

  The boot process hangs with the last message being "started bpfilter".
  There is unusual Network activity during that time. The light of the
  WiFi adapter is blinking a lot.

  I am not sure the problem is with the gdm3 package. As a matter of
  fact, I would remove it and let someone more experienced to set it.
  I'm afraid I might break something, though.

  The specific steps or actions you took that caused you to encounter the 
problem: 1. Boot Ubuntu 18.10 with the Nvidia proprietary drivers
  installed.

  The behavior you expected: I expected Ubuntu 18.10 to boot normally.

  The behavior you actually encountered: The computer gets stuck in a
  command-like environment with the last message being "started
  bpfilter". You can't type any commands.

  I have found that uninstalling the Nvidia proprietary drivers by going
  into recovery mode fixes the issue.

  Booting with the earlier kernel doesn't fix the issue. Installing the
  earlier v.340 driver also doesn't fix the issue.

  This (https://askubuntu.com/questions/1032639/ubuntu-18-04-stuck-in-
  boot-after-starting-gnome-display-manager-on-intel-graphic) seems
  relevant. This is where I found the "solution".

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

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

[Desktop-packages] [Bug 1794139] Re: At random times, no warning when closing a file after it's been deleted

[Bug Watch Updater]

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

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

Title:
  At random times, no warning when closing a file after it's been
  deleted

Status in gedit:
  New
Status in gedit package in Ubuntu:
  Triaged

Bug description:
  See https://gitlab.gnome.org/GNOME/gedit/issues/73#note_331812

  Closed upstream because gedit version too old.

  It seem I never get it right. When I report an issue here I get told
  to report it upstream, and viceversa.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: gedit 3.18.3-0ubuntu4
  ProcVersionSignature: Ubuntu 4.4.0-135.161-generic 4.4.140
  Uname: Linux 4.4.0-135-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Mon Sep 24 17:46:45 2018
  InstallationDate: Installed on 2013-10-11 (1808 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  SourcePackage: gedit
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1831356] Re: Settings crashes when I click "Devices"(Enheter in norwegian) tap

[Gunnar Hjalmarsson]

Thanks for your report!

Can you please start it from terminal:

gnome-control-center

and check if any useful error message is printed when you click Devices.

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

Title:
  Settings crashes when I click "Devices"(Enheter in norwegian) tap

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

Bug description:
  Not much to say. It crashes every time, I cleick devices - and then
  continues to crash on every start up. Trying the command:

gsettings reset org.gnome.ControlCenter last-panel

  as a known workaround for a similar problem, will let me access gnome-
  control-center and use it, until I click Devices again.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: gnome-control-center 1:3.32.1-1ubuntu4.1
  ProcVersionSignature: Ubuntu 5.0.0-15.16-generic 5.0.6
  Uname: Linux 5.0.0-15-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  CurrentDesktop: Unity:Unity7:ubuntu
  Date: Sun Jun  2 03:21:58 2019
  InstallationDate: Installed on 2018-12-11 (172 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  SourcePackage: gnome-control-center
  UpgradeStatus: Upgraded to disco on 2019-06-02 (0 days ago)

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

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

[Desktop-packages] [Bug 1831356] [NEW] Settings crashes when I click "Devices"(Enheter in norwegian) tap

[Lars Bahner]

Public bug reported:

Not much to say. It crashes every time, I cleick devices - and then
continues to crash on every start up. Trying the command:

  gsettings reset org.gnome.ControlCenter last-panel

as a known workaround for a similar problem, will let me access gnome-
control-center and use it, until I click Devices again.

ProblemType: Bug
DistroRelease: Ubuntu 19.04
Package: gnome-control-center 1:3.32.1-1ubuntu4.1
ProcVersionSignature: Ubuntu 5.0.0-15.16-generic 5.0.6
Uname: Linux 5.0.0-15-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.10-0ubuntu27
Architecture: amd64
CurrentDesktop: Unity:Unity7:ubuntu
Date: Sun Jun  2 03:21:58 2019
InstallationDate: Installed on 2018-12-11 (172 days ago)
InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725)
SourcePackage: gnome-control-center
UpgradeStatus: Upgraded to disco on 2019-06-02 (0 days ago)

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


** Tags: amd64 apport-bug disco

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

Title:
  Settings crashes when I click "Devices"(Enheter in norwegian) tap

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

Bug description:
  Not much to say. It crashes every time, I cleick devices - and then
  continues to crash on every start up. Trying the command:

gsettings reset org.gnome.ControlCenter last-panel

  as a known workaround for a similar problem, will let me access gnome-
  control-center and use it, until I click Devices again.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: gnome-control-center 1:3.32.1-1ubuntu4.1
  ProcVersionSignature: Ubuntu 5.0.0-15.16-generic 5.0.6
  Uname: Linux 5.0.0-15-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  CurrentDesktop: Unity:Unity7:ubuntu
  Date: Sun Jun  2 03:21:58 2019
  InstallationDate: Installed on 2018-12-11 (172 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  SourcePackage: gnome-control-center
  UpgradeStatus: Upgraded to disco on 2019-06-02 (0 days ago)

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

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

[Desktop-packages] [Bug 1830691] Re: [SRU] libreoffice 6.2.4 for disco

[Mathew Hodson]

** Tags added: upgrade-software-version

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

Title:
  [SRU] libreoffice 6.2.4 for disco

Status in libreoffice package in Ubuntu:
  Fix Released
Status in libreoffice-l10n package in Ubuntu:
  Fix Released
Status in libreoffice source package in Disco:
  Fix Committed
Status in libreoffice-l10n source package in Disco:
  Fix Committed

Bug description:
  [Impact]

   * LibreOffice 6.2.4 is in its fourth bugfix release of the 6.2 line. Version 
6.2.4 is currently in Eoan.
     For a list of fixed bugs compared to 6.2.3 see the list of bugs fixed in 
the two release candidates:
   https://wiki.documentfoundation.org/Releases/6.2.4/RC1#List_of_fixed_bugs
   https://wiki.documentfoundation.org/Releases/6.2.4/RC2#List_of_fixed_bugs
     (that's a total of 115 bugs)

   * Given the nature of the project, the complexity of the codebase and
  the high level of quality assurance upstream, it is preferable to SRU
  a minor release rather than cherry-pick selected bug fixes.

  [Test Case]

   * No specific test case, bugs fixed upstream hopefully come with
  unit/regression tests, and the release itself is extensively exercised
  upstream (both in an automated manner and manually) by a community of
  testers. Each minor release normally goes through two release
  candidates.

   * The libreoffice packages include autopkgtests, those should be run
  and verified to pass.

   * General smoke testing of all the applications in the office suite
  should be carried out.

  [Regression Potential]

   * A minor release with a total of 115 bug fixes always carries the
  potential for introducing regressions, even though it is a bugfix-only
  release, meaning that no new features were added, and no existing
  features were removed.

   * A combination of autopkgtests and careful smoke testing as
  described above should provide reasonable confidence that no
  regressions sneaked in.

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

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

[Desktop-packages] [Bug 1830884] Re: Update to 3.32.2

[Mathew Hodson]

** Changed in: gnome-control-center (Ubuntu Disco)
   Importance: Undecided => Low

** Tags added: upgrade-software-version

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

Title:
  Update to 3.32.2

Status in gnome-control-center package in Ubuntu:
  Fix Released
Status in gnome-control-center source package in Disco:
  Fix Committed

Bug description:
  * Impact
  That's a GNOME bugfix update, the summary of the changes can be seen there
  https://gitlab.gnome.org/GNOME/gnome-control-center/blob/gnome-3-32/NEWS

  * Test case
  No specific test case, play with different settings and ensure they work 
correcly

  The SRU is under the standard rules from
  https://wiki.ubuntu.com/StableReleaseUpdates/GNOME

  * Regression potential

  Based on the fixes in that update
  - Check that the application panel icons looks right
  - Try to change your screen settings and verify it still works
  - Look at the sound panel for UI problems

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

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

[Desktop-packages] [Bug 1824111] Re: Backport packages for 18.04.3 HWE stack

[Mathew Hodson]

** No longer affects: xserver-xorg-video-amdgpu-hwe-18.04 (Ubuntu)

** No longer affects: xserver-xorg-video-ati-hwe-18.04 (Ubuntu)

** No longer affects: xserver-xorg-video-nouveau-hwe-18.04 (Ubuntu)

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

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

Title:
  Backport packages for 18.04.3 HWE stack

Status in OEM Priority Project:
  Confirmed
Status in libclc package in Ubuntu:
  Invalid
Status in libdrm package in Ubuntu:
  Invalid
Status in llvm-toolchain-8 package in Ubuntu:
  Invalid
Status in mesa package in Ubuntu:
  Invalid
Status in libclc source package in Bionic:
  Fix Committed
Status in libdrm source package in Bionic:
  Fix Committed
Status in llvm-toolchain-8 source package in Bionic:
  Fix Committed
Status in mesa source package in Bionic:
  Fix Committed
Status in xorg-server-hwe-18.04 source package in Bionic:
  Fix Committed
Status in xserver-xorg-video-amdgpu-hwe-18.04 source package in Bionic:
  New
Status in xserver-xorg-video-ati-hwe-18.04 source package in Bionic:
  New
Status in xserver-xorg-video-nouveau-hwe-18.04 source package in Bionic:
  New

Bug description:
  [Impact]

  These are needed for 18.04.3 images.

  [Test case]

  Boot a daily image, see that it still has the necessary stack
  installed and working.

  Check upgrade from stock bionic.

  [Regression potential]

  libdrm: very minimal chance for regressions

  llvm-8: a new package, no regression potential on it's own

  libclc: more or less just adds support for new llvm

  mesa: a new major release, but we'll pull the final stable release of
  19.0.x series, so there shouldn't be any regressions left at that
  point

  xserver: a new minor release

  xorg drivers: modest updates, mainly just new ati/amdgpu

  [Other info]

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

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

[Desktop-packages] [Bug 1814373] Re: storage / luks / dmsetup regressed (or got better) on ppc64le

[Mathew Hodson]

** No longer affects: udisks2 (Ubuntu)

** No longer affects: udisks2 (Ubuntu Bionic)

** No longer affects: udisks2 (Ubuntu Cosmic)

** No longer affects: udisks2 (Ubuntu Disco)

** No longer affects: udisks2 (Ubuntu Eoan)

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

Title:
  storage / luks / dmsetup regressed (or got better) on ppc64le

Status in linux package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Fix Committed
Status in linux source package in Bionic:
  New
Status in systemd source package in Bionic:
  Fix Committed
Status in linux source package in Cosmic:
  New
Status in systemd source package in Cosmic:
  Fix Committed
Status in linux source package in Disco:
  New
Status in systemd source package in Disco:
  Fix Committed
Status in linux source package in Eoan:
  Confirmed
Status in systemd source package in Eoan:
  Fix Committed
Status in systemd package in Debian:
  New

Bug description:
  in disco proposed with new systemd and v4.19 kernel it appears that
  dmsetup / cryptsetup storage either got better or worse.

  Devices take very long to activate, and sometimes remain in use during
  test clean up.

  This leads to udisks autopkgtest failing on ppc64le and systemd's
  "storage" autopkgtest is also failing.

  I've tried to make ppc64le test more resilient, but it's still odd
  that it became unstable in disco, and used to be rock solid on
  ppc64le.

  --
  sru template for systemd upload:

  [impact]
  buffer overflow can cause memory corruption; this is seen in failed 
autopkgtests

  [test case]
  see comment 6

  [regression potential]
  the patch is minimal and clearly correct; however the regression potential is 
around invalid/corrupted keys read from the keyring.

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

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

[Desktop-packages] [Bug 1768166] Re: Random crashes

[Gunnar Hjalmarsson]

On 2019-06-02 01:08, Ping-Wu wrote:
> I might be able to personally force one or two Chinese Ubuntu forum
> participants to test your proposed changes. But that's about it for
> now.

That would be helpful. Not to mention your own observations.

Thanks!

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

Title:
  Random crashes

Status in ibus-libpinyin package in Ubuntu:
  Fix Released
Status in libpinyin package in Ubuntu:
  Fix Released
Status in ibus-libpinyin source package in Bionic:
  Fix Committed
Status in libpinyin source package in Bionic:
  Fix Committed
Status in ibus-libpinyin source package in Cosmic:
  Fix Committed
Status in libpinyin source package in Cosmic:
  Fix Committed

Bug description:
  [Impact]

  ibus-libpinyin has proved to crash far too often. One or more files in
  ~/.cache/ibus/libpinyin get corrupted somehow, and emptying that
  directory allows the user to keep using ibus-libpinyin.

  In disco (and eoan) ibus-libpinyin 1.11.0 and libpinyin 2.2.2 are
  present, and the number of crashes has been reduced significantly:

  https://errors.ubuntu.com/?package=ibus-libpinyin=month

  Upstream ChangeLog ibus-libpinyin:
  --
  version 1.11.0
  * fixes keypad decimal
  * fixes emoji candidates
  * support configurable opencc config

  version 1.10.92
  * fixes Enter handling

  version 1.10.91
  * support ime.register_trigger in lua extension
  * support predicted candidates
  * support emoji input

  version 1.10.0
  * bug fixes

  version 1.9.91
  * migrate to use GSettings
  * fixes lyx short cut issue

  version 1.9.3
  * translate input method name in ibus menu

  Upstream ChangeLog libpinyin:
  -
  version 2.2.2
  * minor fixes

  version 2.2.1
  * fixes predicted candidates

  version 2.2.0
  * bug fixes

  The proposal is to backport the disco versions of those packages to
  bionic and cosmic in an attempt to prevent crashes. Proposed uploads
  are available in this PPA:

  https://launchpad.net/~gunnarhj/+archive/ubuntu/ibus-libpinyin

  [Test Case]

  * Install from {bionic,cosmic}-proposed:
    - libpinyin13
    - libpinyin-data
    - ibus-libpinyin

  * Use "Intelligent Pinyin" for typing and confirm that no new issues
    show up when doing so.

  (This is apparently not a confirmation that the upload really fixes
  the bug. To compensate for that, we will await testing of the
  -proposed packages by a few Chinese users before considering the
  uploads verified.)

  Reverse dependencies
  
  Besides ibus-libpinyin, also fcitx-libpinyin and ibus-libzhuyin depend on 
packages belonging to the libpinyin source package. So additional test measures 
are:

  * Install fcitx-libpinyin and ibus-libzhuyin.

  * Use both those tools for typing Chinese, and confirm that you don't
    observe any adverse effects of the libpinyin upgrade.

  [Regression Potential]

  The changes are mostly bug fixes, so the regression risk should be
  limited. Also consider that the starting point is a rather unstable
  functionality.

  NOTE TO SRU TEAM: Please let the SRU age for longer than 7 days to get
  as much testing as possible. There do not seem to be too many risky
  changes carried, but such jumps in upstream versions always carry some
  regression-risk.

  [Original description]

  I have experienced random ibus-libpinyin crashes in bionic.  I cannot
  reproduce it, but it occurred at least a few times, even after the
  official bionic release.  Same crashes were also reported in the
  Ubuntu Chinese forum.

  Currently, the workaround is to delete the ~/.cache/ibus/libpinyin
  folder.

  I talked to Peng Wu, ibus-libpinyin's creator and main maintainer, he
  suggested that we update the version of ibus-libpinyin to 1.10.

  Can we give this update a trial?

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

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

[Desktop-packages] [Bug 1767454] Re: "Other Locations" does not automatically find Samba servers in Ubuntu 18.04

[Mathew Hodson]

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

** This bug has been marked a duplicate of bug 1778322
   gvfs-smb-browse can't browse samba/smb tree

** Project changed: samba => ubuntu

** Changed in: ubuntu
   Importance: Unknown => Undecided

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

** Changed in: ubuntu
 Remote watch: Samba Bugzilla #12876 => None

** No longer affects: ubuntu

** Bug watch removed: Samba Bugzilla #12876
   https://bugzilla.samba.org/show_bug.cgi?id=12876

** Project changed: gvfs => ubuntu

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

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

** Changed in: ubuntu
 Remote watch: GNOME Bug Tracker #780958 => None

** No longer affects: ubuntu

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

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

Title:
  "Other Locations" does not automatically find Samba servers in Ubuntu
  18.04

Status in dolphin:
  Unknown
Status in gvfs package in Ubuntu:
  Fix Released
Status in samba package in Ubuntu:
  Invalid

Bug description:
  Ubuntu: 18.04 clean install
  Nautilus: 1:3.26.3-0ubuntu4

  The actions taken to produce the problem:
  Click on “Other Locations” in Nautilus.

  The expected result of these actions:
  Samba servers to automatically show up under “Networks”. This is the behavior 
in Ubuntu 17.10 using Nautilus 1:3.26.0-0ub. Also, clicking on “”Windows 
Network” immediately shows "Folder is Empty".

  The actual result of these actions:
  The Samba servers never show up under “Networks” and clicking on "Windows 
Network" always immediately comes up with "Folder is Empty".

  Further information:
  This happens on both machines with a clean Ubuntu 18.04 install. My Ubuntu 
17.10 machines still work like expected.

  I can still manually type in the Samba information in "Connect to
  Server" and the 18.04 machines connect just fine.

  
  From syslog:
  Apr 27 13:49:34 david-HP-ProBook-440-G2 dbus-daemon[1333]: [session uid=1000 
pid=1333] Activating service name='org.gnome.Nautilus' requested by ':1.13' 
(uid=1000 pid=1468 comm="/usr/bin/gnome-shell " label="unconfined")
  Apr 27 13:49:34 david-HP-ProBook-440-G2 dbus-daemon[1333]: [session uid=1000 
pid=1333] Successfully activated service 'org.gnome.Nautilus'
  Apr 27 13:49:35 david-HP-ProBook-440-G2 dbus-daemon[754]: [system] Activating 
via systemd: service name='org.freedesktop.hostname1' 
unit='dbus-org.freedesktop.hostname1.service' requested by ':1.131' (uid=1000 
pid=4857 comm="/usr/bin/nautilus --gapplication-service " label="unconfined")
  Apr 27 13:49:35 david-HP-ProBook-440-G2 systemd[1]: Starting Hostname 
Service...
  Apr 27 13:49:35 david-HP-ProBook-440-G2 nautilus[4857]: Called "net usershare 
info" but it failed: Failed to execute child process “net” (No such file or 
directory)
  Apr 27 13:49:35 david-HP-ProBook-440-G2 dbus-daemon[754]: [system] 
Successfully activated service 'org.freedesktop.hostname1'
  Apr 27 13:49:35 david-HP-ProBook-440-G2 systemd[1]: Started Hostname Service.
  Apr 27 13:49:40 david-HP-ProBook-440-G2 gvfsd[1432]: mkdir failed on 
directory /var/cache/samba: Permission denied

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

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

[Desktop-packages] [Bug 1826468]

[Mokurtz]

After further testing, the bug persists.

I had a file on an gvfs-mounted sftp share that was locked. I clicked on
"enable editing," which creates a new file in that directory, and Writer
crashed.

Less severe but the same behavior from a different functionality.

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

Title:
  [upstream] Libreoffice Calc cannot export PDF to a network drive

Status in LibreOffice:
  Fix Released
Status in libreoffice package in Ubuntu:
  Fix Released

Bug description:
  After upgrading from 18.10 to 19.04 I lost possibility to export a
  document to PDF, if a document is on a network drive (it's a DAVS
  network folder in my case). I receive a pop-up windows about general
  I/O error.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: libreoffice (not installed)
  ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6
  Uname: Linux 5.0.0-13-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Thu Apr 25 23:35:20 2019
  InstallationDate: Installed on 2018-05-05 (355 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=pl_PL.UTF-8
   SHELL=/usr/bin/fish
  SourcePackage: libreoffice
  UpgradeStatus: Upgraded to disco on 2019-04-23 (2 days ago)

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

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

[Desktop-packages] [Bug 1778322] Re: gvfs-smb-browse can't browse samba/smb tree

[Mathew Hodson]

** Bug watch added: Samba Bugzilla #12876
   https://bugzilla.samba.org/show_bug.cgi?id=12876

** Also affects: samba via
   https://bugzilla.samba.org/show_bug.cgi?id=12876
   Importance: Unknown
   Status: Unknown

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

Title:
  gvfs-smb-browse can't browse samba/smb tree

Status in gvfs:
  Unknown
Status in samba:
  Unknown
Status in gvfs package in Ubuntu:
  Fix Released
Status in samba package in Ubuntu:
  Fix Released
Status in gvfs source package in Bionic:
  Fix Committed
Status in samba source package in Bionic:
  Fix Released
Status in gvfs source package in Cosmic:
  Fix Committed
Status in samba source package in Cosmic:
  Fix Released

Bug description:
  [Impact]
  The so called "browsing a windows network" made use of an SMB1 protocol 
version feature. Recent versions of samba, including the one released with 
bionic, default to a higher versions of the protocol which lacks this feature. 
As a result, the "other locations -> windows network" tab in Nautilus is empty 
even when there are windows or samba machines in the network.
  Accessing such machines directly, via smb:/// type urls, 
continues to work.

  The fix is two-fold:
  - introduce a new samba API call that can be used to set the protocol version 
to use
  - change applications to make use of this API call to set the protocol versio 
to SMB1/NT1 just for the network browsing

  gvfs was updated to make use of this api call, if detected at build
  time. To complete this SRU, gvfs needs a no-change rebuild *after*
  samba was accepted into proposed.

  [Test case]
  * Launch a bionic desktop vm. You can start with a server one, and then 
install the "ubuntu-desktop" package. In the same command, also install the 
packages we need for this test:
  $ sudo apt update
  $ sudo apt install ubuntu-desktop samba smbclient

  * set a password for the ubuntu user, so you can login at the graphical 
console
  $ sudo passwd ubuntu

  * set the same password for the ubuntu samba user:
  sudo smbpasswd -a ubuntu

  * add a simple [pub] share to samba:
  $ printf "[pub]\n\tpath=/tmp\n\tguest ok = no\n" | sudo tee -a 
/etc/samba/smb.conf

  * reboot
  $ sudo reboot

  * login at the graphical console as the ubuntu user. Go through the
  first-user-setup motions as you want.

  * try to browse the windows network via "other locations -> windows
  network". You will get an empty folder.

  * update the samba and gvfs packages
  * logout and login again on the gui, browse the windows network again. This 
time it will show the "WORKGROUP" folder, and if you click through, you will 
see yourself (your VM) and the [pub] share, among others.

  * click on the "pub" share, select registered user and login with the
  ubuntu credentials you created earlier with smbpasswd.

  * in another terminal, run this command to confirm that the SMB protocol 
version that was used to connect to [pub] was not just NT1/SMB1, but higher:
  $ sudo smbstatus
  ...
  8779ubuntu   ubuntu   192.168.122.94 (ipv4:192.168.122.94:60818) 
SMB3_11   -partial(AES-128-CMAC)

  Note "SMB3_11" above.

  
  [Regression potential]
  The samba update itself just introduces and exposes a new API call. It's up 
to other applications to make use of that. gvfs was patched to detect this call 
at build time and use it if it's detected.
  Packages that are not rebuilt will not see the change, and packages that 
*are* rebuilt will only see the change if they make use of it.

  [Other Info]
  This update introduces a specific runtime dependency between gvfs and 
libsmbclient due to the new API call added to the latter. Any package that is 
rebuilt with libsmbclient and makes use of that API call will get this specific 
dependency. This is handled automatically by dh_mkshlibs.

  To complete this SRU, gvfs will need a no-change rebuild after samba
  was accepted into proposed.

  Disco's gvfs is already using the new call, as can be seen in this build log 
https://launchpadlibrarian.net/415424052/buildlog_ubuntu-disco-amd64.gvfs_1.40.0-1_BUILDING.txt.gz:
  ...
  Dependency smbclient found: YES 0.5.0
  Checking for function "smbc_setOptionProtocols" with dependency smbclient: YES

  The smbc_setOptionProtocols() call is only used when the url is like
  "smb:///", or the server cannot be resolved. The downgrade overrides
  the setting in smb.conf, and is used just for this case: browsing the
  network. When connecting to a machine, the url is like
  "smb:///", and then this function we are adding is not called.

  I updated the test to actually click on the machine that shows up in
  the network browsing, and then check with "smbstatus" which version of
  the protocol was used when connecting to an actual share.

  ---

  Nautilus should show smbtree and host on the smb network.

  When inputing this 

[Desktop-packages] [Bug 1831353] [NEW] can't browse pages

[Polaris]

Public bug reported:

Rebooting doesn't help.

Using:
Firefox: 67.0 64 bit
OS: 16.04.6 Xubuntu
Kernel 4.4.0-148-generic(x86_64)
Desktop XFCE 4

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: firefox 67.0+build2-0ubuntu0.16.04.1
ProcVersionSignature: Ubuntu 4.4.0-148.174-generic 4.4.177
Uname: Linux 4.4.0-148-generic x86_64
AddonCompatCheckDisabled: False
ApportVersion: 2.20.1-0ubuntu2.18
Architecture: amd64
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-id', 
'/dev/snd/pcmC2D0c', '/dev/snd/controlC2', '/dev/snd/by-path', 
'/dev/snd/hwC0D2', '/dev/snd/pcmC0D2c', '/dev/snd/pcmC0D0c', 
'/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/hwC1D0', 
'/dev/snd/pcmC1D3p', '/dev/snd/controlC1', '/dev/snd/seq', '/dev/snd/timer'] 
failed with exit code 1:
BuildID: 20190517141553
Channel: Unavailable
CurrentDesktop: XFCE
Date: Sat Jun  1 16:26:11 2019
Extensions: extensions.sqlite corrupt or missing
ForcedLayersAccel: False
IfupdownConfig:
 # interfaces(5) file used by ifup(8) and ifdown(8)
 auto lo
 iface lo inet loopback
IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini 
or extensions.sqlite)
InstallationDate: Installed on 2015-12-26 (1253 days ago)
InstallationMedia: Xubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
IpRoute:
 default via 192.168.1.1 dev eth0  proto static  metric 100 
 169.254.0.0/16 dev eth0  scope link  metric 1000 
 192.168.1.0/24 dev eth0  proto kernel  scope link  src 192.168.1.199  metric 
100
Locales: extensions.sqlite corrupt or missing
Plugins: Shockwave Flash - /usr/lib/flashplugin-installer/libflashplayer.so
PrefErrors: Unexpected character ',' before close parenthesis @ 
/usr/lib/firefox/omni.ja:greprefs.js:1151
PrefSources: prefs.js
Profiles: Profile0 (Default) - LastVersion=67.0/20190517141553 (In use)
RunningIncompatibleAddons: False
SourcePackage: firefox
Themes: extensions.sqlite corrupt or missing
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 03/27/2007
dmi.bios.vendor: Intel Corp.
dmi.bios.version: CO96510J.86A.5869.2007.0327.0132
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: DQ965GF
dmi.board.vendor: Intel Corporation
dmi.board.version: AAD41676-305
dmi.chassis.type: 3
dmi.modalias: 
dmi:bvnIntelCorp.:bvrCO96510J.86A.5869.2007.0327.0132:bd03/27/2007:svn:pn:pvr:rvnIntelCorporation:rnDQ965GF:rvrAAD41676-305:cvn:ct3:cvr:

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


** Tags: amd64 apport-bug xenial

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

Title:
  can't browse pages

Status in firefox package in Ubuntu:
  New

Bug description:
  Rebooting doesn't help.

  Using:
  Firefox: 67.0 64 bit
  OS: 16.04.6 Xubuntu
  Kernel 4.4.0-148-generic(x86_64)
  Desktop XFCE 4

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: firefox 67.0+build2-0ubuntu0.16.04.1
  ProcVersionSignature: Ubuntu 4.4.0-148.174-generic 4.4.177
  Uname: Linux 4.4.0-148-generic x86_64
  AddonCompatCheckDisabled: False
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-id', 
'/dev/snd/pcmC2D0c', '/dev/snd/controlC2', '/dev/snd/by-path', 
'/dev/snd/hwC0D2', '/dev/snd/pcmC0D2c', '/dev/snd/pcmC0D0c', 
'/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/hwC1D0', 
'/dev/snd/pcmC1D3p', '/dev/snd/controlC1', '/dev/snd/seq', '/dev/snd/timer'] 
failed with exit code 1:
  BuildID: 20190517141553
  Channel: Unavailable
  CurrentDesktop: XFCE
  Date: Sat Jun  1 16:26:11 2019
  Extensions: extensions.sqlite corrupt or missing
  ForcedLayersAccel: False
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  IncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
  InstallationDate: Installed on 2015-12-26 (1253 days ago)
  InstallationMedia: Xubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
  IpRoute:
   default via 192.168.1.1 dev eth0  proto static  metric 100 
   169.254.0.0/16 dev eth0  scope link  metric 1000 
   192.168.1.0/24 dev eth0  proto kernel  scope link  src 192.168.1.199  metric 
100
  Locales: extensions.sqlite corrupt or missing
  Plugins: Shockwave Flash - /usr/lib/flashplugin-installer/libflashplayer.so
  PrefErrors: Unexpected character ',' before close parenthesis @ 
/usr/lib/firefox/omni.ja:greprefs.js:1151
  PrefSources: prefs.js
  Profiles: Profile0 (Default) - LastVersion=67.0/20190517141553 (In use)
  RunningIncompatibleAddons: False
  SourcePackage: firefox
  Themes: extensions.sqlite corrupt or missing
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/27/2007
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: CO96510J.86A.5869.2007.0327.0132
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: DQ965GF
  

[Desktop-packages] [Bug 21753] Re: Epiphany 'Move tab to window' option doesn't work in breezy

[Bug Watch Updater]

** Changed in: firefox
   Status: Confirmed => Won't Fix

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

Title:
  Epiphany 'Move tab to window' option doesn't work in breezy

Status in Mozilla Firefox:
  Won't Fix
Status in firefox package in Ubuntu:
  Won't Fix
Status in xulrunner-1.9 package in Ubuntu:
  Won't Fix

Bug description:
  Using the 'Tabsmenu' extension in epiphany-extensions, the option to move tabs
  between windows no longer works. This feature worked fine in Hoary.

  https://bugzilla.mozilla.org/show_bug.cgi?id=296002:
  https://bugzilla.mozilla.org/show_bug.cgi?id=296002

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

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

[Desktop-packages] [Bug 422511] Re: problem with new scrollbar in Human theme - GtkRange::trough-border set to 2

[Bug Watch Updater]

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

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

Title:
  problem with new scrollbar in Human theme - GtkRange::trough-border
  set to 2

Status in elementary Stylesheet:
  Won't Fix
Status in Mozilla Firefox:
  New
Status in GTK+:
  Expired
Status in human-theme:
  New
Status in LibGTK:
  New
Status in gtk+2.0 package in Ubuntu:
  Triaged
Status in human-theme package in Ubuntu:
  Confirmed
Status in seamonkey package in Ubuntu:
  New

Bug description:
  The new scrollbar in Karmic's Human theme has a usability bug:
  To reproduce, open nautilus, maximize the window, then open a directory with 
enough files to cause the scrollbar to appear (e.g. /lib). Now move your mouse 
to the right edge of the screen, and left click. Instead of grabbing the scroll 
bar, the mouse will behave as if you had clicked the scrollbar background, i.e. 
the bar will jump to that position (in Firefox, nothing happens). The problem 
is that the bar doesn't extend to the right edge, leaving a two pixel margin, 
but because of Fitts' law, it's much easier to click on the screen edge than 
the few pixels to the left of it.

  The cause of this is GtkRange::trough-border being set to 2. Setting
  it to 0 removes the margin around the bar.

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

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

[Desktop-packages] [Bug 422511]

[Bug-husbandry-bot]

https://bugzilla.mozilla.org/show_bug.cgi?id=1552613

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

Title:
  problem with new scrollbar in Human theme - GtkRange::trough-border
  set to 2

Status in elementary Stylesheet:
  Won't Fix
Status in Mozilla Firefox:
  New
Status in GTK+:
  Expired
Status in human-theme:
  New
Status in LibGTK:
  New
Status in gtk+2.0 package in Ubuntu:
  Triaged
Status in human-theme package in Ubuntu:
  Confirmed
Status in seamonkey package in Ubuntu:
  New

Bug description:
  The new scrollbar in Karmic's Human theme has a usability bug:
  To reproduce, open nautilus, maximize the window, then open a directory with 
enough files to cause the scrollbar to appear (e.g. /lib). Now move your mouse 
to the right edge of the screen, and left click. Instead of grabbing the scroll 
bar, the mouse will behave as if you had clicked the scrollbar background, i.e. 
the bar will jump to that position (in Firefox, nothing happens). The problem 
is that the bar doesn't extend to the right edge, leaving a two pixel margin, 
but because of Fitts' law, it's much easier to click on the screen edge than 
the few pixels to the left of it.

  The cause of this is GtkRange::trough-border being set to 2. Setting
  it to 0 removes the margin around the bar.

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

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

[Desktop-packages] [Bug 597476] Re: GeForce 7150M / nForce 630M uses an unusable resolution by default

[Christopher M. Penalver]

André Silva Coelho de Oliveira, it is most helpful if you use the computer the 
problem is reproducible with and file a new report with Ubuntu by first 
ensuring the package xdiagnose is installed, and click the Yes button for 
attaching additional debugging information after running the following from a 
terminal:
ubuntu-bug xorg

Also, please feel free to subscribe me to it.

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

Title:
  GeForce 7150M / nForce 630M uses an unusable resolution by default

Status in xserver-xorg-video-nouveau package in Ubuntu:
  Expired

Bug description:
  Binary package hint: xorg

  Booting Ubuntu Lucid 32-bit Desktop CD on a HP Pavillon dv2500, the
  following card displays a default resolution which is not usable.  The
  screen is offset to the right, there are artifacts and horizontal bars
  on the screen.

  Would it be possible to do two things in this bug:
  1) Create a guide on the wiki explaining another workaround which explains 
how to either change the resolution (or installing the binary drivers from the 
Live CD without restarting). This will assure that people with this issue can 
check a verified document explaining how to get ubuntu installed on this 
hardware.
  2) Get the default resolution for this machine to be 1280x800 instead of 
1024x768 from the 10.04.1 CD

  00:12.0 VGA compatible controller [0300]: nVidia Corporation C67 [GeForce 
7150M / nForce 630M] [10de:0531] (rev a2)
Kernel driver in use: nouveau
Kernel modules: nvidiafb, nouveau

  Workaround: Though the interface is not usable, you can still guide
  your mouse and go to the correct items. Go to System > Preferences >
  Monitors and change the default resolution of 1024x768 to 1280x800.

  ProblemType: Bug
  DistroRelease: Ubuntu 10.04
  Package: xorg 1:7.5+5ubuntu1
  ProcVersionSignature: Ubuntu 2.6.32-21.32-generic 2.6.32.11+drm33.2
  Uname: Linux 2.6.32-21-generic i686
  Architecture: i386
  Date: Tue Jun 22 22:41:55 2010
  DkmsStatus: Error: [Errno 2] No such file or directory
  GdmLog1: Error: command ['gksu', '-D', 'Apport', '--', 'cat', 
'/var/log/gdm/:0.log.1'] failed with exit code 1: cat: /var/log/gdm/:0.log.1: 
No such file or directory
  GdmLog2: Error: command ['gksu', '-D', 'Apport', '--', 'cat', 
'/var/log/gdm/:0.log.2'] failed with exit code 1: cat: /var/log/gdm/:0.log.2: 
No such file or directory
  LiveMediaBuild: Ubuntu 10.04 LTS "Lucid Lynx" - Release i386 (20100429)
  Lsusb:
   Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 001 Device 002: ID 04f2:b016 Chicony Electronics Co., Ltd VGA 30fps UVC 
Webcam
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Hewlett-Packard HP Pavilion dv2700 Notebook PC
  ProcCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/hostname.seed 
boot=casper initrd=/casper/initrd.lz quiet splash -- maybe-ubiquity
  ProcEnviron:
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: xorg
  dmi.bios.date: 01/24/2008
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: F.15
  dmi.board.name: 30D6
  dmi.board.vendor: Wistron
  dmi.board.version: 81.50
  dmi.chassis.type: 10
  dmi.chassis.vendor: Wistron
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrF.15:bd01/24/2008:svnHewlett-Packard:pnHPPaviliondv2700NotebookPC:pvrF.15:rvnWistron:rn30D6:rvr81.50:cvnWistron:ct10:cvrN/A:
  dmi.product.name: HP Pavilion dv2700 Notebook PC
  dmi.product.version: F.15
  dmi.sys.vendor: Hewlett-Packard
  glxinfo: Error: [Errno 2] No such file or directory
  system:
   distro: Ubuntu
   codename:   lucid
   architecture:   i686
   kernel: 2.6.32-21-generic

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-nouveau/+bug/597476/+subscriptions

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

[Desktop-packages] [Bug 21753]

[Stransky]

We're not going to fix that.

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

Title:
  Epiphany 'Move tab to window' option doesn't work in breezy

Status in Mozilla Firefox:
  Won't Fix
Status in firefox package in Ubuntu:
  Won't Fix
Status in xulrunner-1.9 package in Ubuntu:
  Won't Fix

Bug description:
  Using the 'Tabsmenu' extension in epiphany-extensions, the option to move tabs
  between windows no longer works. This feature worked fine in Hoary.

  https://bugzilla.mozilla.org/show_bug.cgi?id=296002:
  https://bugzilla.mozilla.org/show_bug.cgi?id=296002

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

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

[Desktop-packages] [Bug 597476] Re: GeForce 7150M / nForce 630M uses an unusable resolution by default

[André Silva Coelho de Oliveira]

I can confirm that this problem still happens even with the newest
(Ubuntu 19) version. Tryied to install Ubuntu 19 on a HP Pavillion
dv6000 and the same problem persist.

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

Title:
  GeForce 7150M / nForce 630M uses an unusable resolution by default

Status in xserver-xorg-video-nouveau package in Ubuntu:
  Expired

Bug description:
  Binary package hint: xorg

  Booting Ubuntu Lucid 32-bit Desktop CD on a HP Pavillon dv2500, the
  following card displays a default resolution which is not usable.  The
  screen is offset to the right, there are artifacts and horizontal bars
  on the screen.

  Would it be possible to do two things in this bug:
  1) Create a guide on the wiki explaining another workaround which explains 
how to either change the resolution (or installing the binary drivers from the 
Live CD without restarting). This will assure that people with this issue can 
check a verified document explaining how to get ubuntu installed on this 
hardware.
  2) Get the default resolution for this machine to be 1280x800 instead of 
1024x768 from the 10.04.1 CD

  00:12.0 VGA compatible controller [0300]: nVidia Corporation C67 [GeForce 
7150M / nForce 630M] [10de:0531] (rev a2)
Kernel driver in use: nouveau
Kernel modules: nvidiafb, nouveau

  Workaround: Though the interface is not usable, you can still guide
  your mouse and go to the correct items. Go to System > Preferences >
  Monitors and change the default resolution of 1024x768 to 1280x800.

  ProblemType: Bug
  DistroRelease: Ubuntu 10.04
  Package: xorg 1:7.5+5ubuntu1
  ProcVersionSignature: Ubuntu 2.6.32-21.32-generic 2.6.32.11+drm33.2
  Uname: Linux 2.6.32-21-generic i686
  Architecture: i386
  Date: Tue Jun 22 22:41:55 2010
  DkmsStatus: Error: [Errno 2] No such file or directory
  GdmLog1: Error: command ['gksu', '-D', 'Apport', '--', 'cat', 
'/var/log/gdm/:0.log.1'] failed with exit code 1: cat: /var/log/gdm/:0.log.1: 
No such file or directory
  GdmLog2: Error: command ['gksu', '-D', 'Apport', '--', 'cat', 
'/var/log/gdm/:0.log.2'] failed with exit code 1: cat: /var/log/gdm/:0.log.2: 
No such file or directory
  LiveMediaBuild: Ubuntu 10.04 LTS "Lucid Lynx" - Release i386 (20100429)
  Lsusb:
   Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 001 Device 002: ID 04f2:b016 Chicony Electronics Co., Ltd VGA 30fps UVC 
Webcam
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Hewlett-Packard HP Pavilion dv2700 Notebook PC
  ProcCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/hostname.seed 
boot=casper initrd=/casper/initrd.lz quiet splash -- maybe-ubiquity
  ProcEnviron:
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: xorg
  dmi.bios.date: 01/24/2008
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: F.15
  dmi.board.name: 30D6
  dmi.board.vendor: Wistron
  dmi.board.version: 81.50
  dmi.chassis.type: 10
  dmi.chassis.vendor: Wistron
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrF.15:bd01/24/2008:svnHewlett-Packard:pnHPPaviliondv2700NotebookPC:pvrF.15:rvnWistron:rn30D6:rvr81.50:cvnWistron:ct10:cvrN/A:
  dmi.product.name: HP Pavilion dv2700 Notebook PC
  dmi.product.version: F.15
  dmi.sys.vendor: Hewlett-Packard
  glxinfo: Error: [Errno 2] No such file or directory
  system:
   distro: Ubuntu
   codename:   lucid
   architecture:   i686
   kernel: 2.6.32-21-generic

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-nouveau/+bug/597476/+subscriptions

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

[Desktop-packages] [Bug 1778322] Re: gvfs-smb-browse can't browse samba/smb tree

[Mathew Hodson]

** Also affects: gvfs via
   https://bugzilla.gnome.org/show_bug.cgi?id=780958
   Importance: Unknown
   Status: Unknown

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

Title:
  gvfs-smb-browse can't browse samba/smb tree

Status in gvfs:
  Unknown
Status in gvfs package in Ubuntu:
  Fix Released
Status in samba package in Ubuntu:
  Fix Released
Status in gvfs source package in Bionic:
  Fix Committed
Status in samba source package in Bionic:
  Fix Released
Status in gvfs source package in Cosmic:
  Fix Committed
Status in samba source package in Cosmic:
  Fix Released

Bug description:
  [Impact]
  The so called "browsing a windows network" made use of an SMB1 protocol 
version feature. Recent versions of samba, including the one released with 
bionic, default to a higher versions of the protocol which lacks this feature. 
As a result, the "other locations -> windows network" tab in Nautilus is empty 
even when there are windows or samba machines in the network.
  Accessing such machines directly, via smb:/// type urls, 
continues to work.

  The fix is two-fold:
  - introduce a new samba API call that can be used to set the protocol version 
to use
  - change applications to make use of this API call to set the protocol versio 
to SMB1/NT1 just for the network browsing

  gvfs was updated to make use of this api call, if detected at build
  time. To complete this SRU, gvfs needs a no-change rebuild *after*
  samba was accepted into proposed.

  [Test case]
  * Launch a bionic desktop vm. You can start with a server one, and then 
install the "ubuntu-desktop" package. In the same command, also install the 
packages we need for this test:
  $ sudo apt update
  $ sudo apt install ubuntu-desktop samba smbclient

  * set a password for the ubuntu user, so you can login at the graphical 
console
  $ sudo passwd ubuntu

  * set the same password for the ubuntu samba user:
  sudo smbpasswd -a ubuntu

  * add a simple [pub] share to samba:
  $ printf "[pub]\n\tpath=/tmp\n\tguest ok = no\n" | sudo tee -a 
/etc/samba/smb.conf

  * reboot
  $ sudo reboot

  * login at the graphical console as the ubuntu user. Go through the
  first-user-setup motions as you want.

  * try to browse the windows network via "other locations -> windows
  network". You will get an empty folder.

  * update the samba and gvfs packages
  * logout and login again on the gui, browse the windows network again. This 
time it will show the "WORKGROUP" folder, and if you click through, you will 
see yourself (your VM) and the [pub] share, among others.

  * click on the "pub" share, select registered user and login with the
  ubuntu credentials you created earlier with smbpasswd.

  * in another terminal, run this command to confirm that the SMB protocol 
version that was used to connect to [pub] was not just NT1/SMB1, but higher:
  $ sudo smbstatus
  ...
  8779ubuntu   ubuntu   192.168.122.94 (ipv4:192.168.122.94:60818) 
SMB3_11   -partial(AES-128-CMAC)

  Note "SMB3_11" above.

  
  [Regression potential]
  The samba update itself just introduces and exposes a new API call. It's up 
to other applications to make use of that. gvfs was patched to detect this call 
at build time and use it if it's detected.
  Packages that are not rebuilt will not see the change, and packages that 
*are* rebuilt will only see the change if they make use of it.

  [Other Info]
  This update introduces a specific runtime dependency between gvfs and 
libsmbclient due to the new API call added to the latter. Any package that is 
rebuilt with libsmbclient and makes use of that API call will get this specific 
dependency. This is handled automatically by dh_mkshlibs.

  To complete this SRU, gvfs will need a no-change rebuild after samba
  was accepted into proposed.

  Disco's gvfs is already using the new call, as can be seen in this build log 
https://launchpadlibrarian.net/415424052/buildlog_ubuntu-disco-amd64.gvfs_1.40.0-1_BUILDING.txt.gz:
  ...
  Dependency smbclient found: YES 0.5.0
  Checking for function "smbc_setOptionProtocols" with dependency smbclient: YES

  The smbc_setOptionProtocols() call is only used when the url is like
  "smb:///", or the server cannot be resolved. The downgrade overrides
  the setting in smb.conf, and is used just for this case: browsing the
  network. When connecting to a machine, the url is like
  "smb:///", and then this function we are adding is not called.

  I updated the test to actually click on the machine that shows up in
  the network browsing, and then check with "smbstatus" which version of
  the protocol was used when connecting to an actual share.

  ---

  Nautilus should show smbtree and host on the smb network.

  When inputing this command:
  killall gvfsd-smb-browse && GVFS_DEBUG=1 /usr/lib/gvfs/gvfsd-smb-browse

  You can see the error:
  

[Desktop-packages] [Bug 1778322] Re: gvfs-smb-browse can't browse samba/smb tree

[Mathew Hodson]

** Bug watch removed: gitlab.gnome.org/GNOME/gvfs/issues #307
   https://gitlab.gnome.org/GNOME/gvfs/issues/307

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

Title:
  gvfs-smb-browse can't browse samba/smb tree

Status in gvfs:
  Unknown
Status in gvfs package in Ubuntu:
  Fix Released
Status in samba package in Ubuntu:
  Fix Released
Status in gvfs source package in Bionic:
  Fix Committed
Status in samba source package in Bionic:
  Fix Released
Status in gvfs source package in Cosmic:
  Fix Committed
Status in samba source package in Cosmic:
  Fix Released

Bug description:
  [Impact]
  The so called "browsing a windows network" made use of an SMB1 protocol 
version feature. Recent versions of samba, including the one released with 
bionic, default to a higher versions of the protocol which lacks this feature. 
As a result, the "other locations -> windows network" tab in Nautilus is empty 
even when there are windows or samba machines in the network.
  Accessing such machines directly, via smb:/// type urls, 
continues to work.

  The fix is two-fold:
  - introduce a new samba API call that can be used to set the protocol version 
to use
  - change applications to make use of this API call to set the protocol versio 
to SMB1/NT1 just for the network browsing

  gvfs was updated to make use of this api call, if detected at build
  time. To complete this SRU, gvfs needs a no-change rebuild *after*
  samba was accepted into proposed.

  [Test case]
  * Launch a bionic desktop vm. You can start with a server one, and then 
install the "ubuntu-desktop" package. In the same command, also install the 
packages we need for this test:
  $ sudo apt update
  $ sudo apt install ubuntu-desktop samba smbclient

  * set a password for the ubuntu user, so you can login at the graphical 
console
  $ sudo passwd ubuntu

  * set the same password for the ubuntu samba user:
  sudo smbpasswd -a ubuntu

  * add a simple [pub] share to samba:
  $ printf "[pub]\n\tpath=/tmp\n\tguest ok = no\n" | sudo tee -a 
/etc/samba/smb.conf

  * reboot
  $ sudo reboot

  * login at the graphical console as the ubuntu user. Go through the
  first-user-setup motions as you want.

  * try to browse the windows network via "other locations -> windows
  network". You will get an empty folder.

  * update the samba and gvfs packages
  * logout and login again on the gui, browse the windows network again. This 
time it will show the "WORKGROUP" folder, and if you click through, you will 
see yourself (your VM) and the [pub] share, among others.

  * click on the "pub" share, select registered user and login with the
  ubuntu credentials you created earlier with smbpasswd.

  * in another terminal, run this command to confirm that the SMB protocol 
version that was used to connect to [pub] was not just NT1/SMB1, but higher:
  $ sudo smbstatus
  ...
  8779ubuntu   ubuntu   192.168.122.94 (ipv4:192.168.122.94:60818) 
SMB3_11   -partial(AES-128-CMAC)

  Note "SMB3_11" above.

  
  [Regression potential]
  The samba update itself just introduces and exposes a new API call. It's up 
to other applications to make use of that. gvfs was patched to detect this call 
at build time and use it if it's detected.
  Packages that are not rebuilt will not see the change, and packages that 
*are* rebuilt will only see the change if they make use of it.

  [Other Info]
  This update introduces a specific runtime dependency between gvfs and 
libsmbclient due to the new API call added to the latter. Any package that is 
rebuilt with libsmbclient and makes use of that API call will get this specific 
dependency. This is handled automatically by dh_mkshlibs.

  To complete this SRU, gvfs will need a no-change rebuild after samba
  was accepted into proposed.

  Disco's gvfs is already using the new call, as can be seen in this build log 
https://launchpadlibrarian.net/415424052/buildlog_ubuntu-disco-amd64.gvfs_1.40.0-1_BUILDING.txt.gz:
  ...
  Dependency smbclient found: YES 0.5.0
  Checking for function "smbc_setOptionProtocols" with dependency smbclient: YES

  The smbc_setOptionProtocols() call is only used when the url is like
  "smb:///", or the server cannot be resolved. The downgrade overrides
  the setting in smb.conf, and is used just for this case: browsing the
  network. When connecting to a machine, the url is like
  "smb:///", and then this function we are adding is not called.

  I updated the test to actually click on the machine that shows up in
  the network browsing, and then check with "smbstatus" which version of
  the protocol was used when connecting to an actual share.

  ---

  Nautilus should show smbtree and host on the smb network.

  When inputing this command:
  killall gvfsd-smb-browse && GVFS_DEBUG=1 /usr/lib/gvfs/gvfsd-smb-browse

  You can see the error:
  smb-network: Queued new 

Re: [Desktop-packages] [Bug 1768166] Re: Random crashes

[Ping-Wu]

Duly noted.

I am hitting a brick wall in the Chinese Ubuntu forum.  It turns out that
nobody is using the ibus-libpinyin input method.

Would you be interested in using, as part of your daily routine, an input
tool that can suddenly crash and cannot be recovered until you delete all
the vocabulary that you have painstakingly built?  I won't blame them.

Switching to a different Chinese input method is much more involved than
you may think.  Even temporarily.  I might be able to personally force one
or two Chinese Ubuntu forum participants to test your proposed changes.
But that's about it for now.


On Sat, Jun 1, 2019 at 10:30 AM Gunnar Hjalmarsson <
1768...@bugs.launchpad.net> wrote:

> @Ping-Wu: Which tools for inputting Chinese should be available on
> Ubuntu going forward is indeed a valid discussion, but this bug report
> is not a proper place for it. I notice your strong interest in the
> topic, and if you want to start such a discussion, I would suggest that
> you start a thread at .
>
> For Ubuntu 18.04 we have the tools which are in the archive, and ibus-
> libpinyin ("Intelligent Pinyin") is the default method for Simplified
> Chinese. This bug (filed by yourself) is about upgrading the software
> for that method, and only that.
>
> So can we please focus here on testing the proposal to upgrade, and hold
> the wider discussion in e.g. the Ubuntu Community Hub?
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1768166
>
> Title:
>   Random crashes
>
> Status in ibus-libpinyin package in Ubuntu:
>   Fix Released
> Status in libpinyin package in Ubuntu:
>   Fix Released
> Status in ibus-libpinyin source package in Bionic:
>   Fix Committed
> Status in libpinyin source package in Bionic:
>   Fix Committed
> Status in ibus-libpinyin source package in Cosmic:
>   Fix Committed
> Status in libpinyin source package in Cosmic:
>   Fix Committed
>
> Bug description:
>   [Impact]
>
>   ibus-libpinyin has proved to crash far too often. One or more files in
>   ~/.cache/ibus/libpinyin get corrupted somehow, and emptying that
>   directory allows the user to keep using ibus-libpinyin.
>
>   In disco (and eoan) ibus-libpinyin 1.11.0 and libpinyin 2.2.2 are
>   present, and the number of crashes has been reduced significantly:
>
>   https://errors.ubuntu.com/?package=ibus-libpinyin=month
>
>   Upstream ChangeLog ibus-libpinyin:
>   --
>   version 1.11.0
>   * fixes keypad decimal
>   * fixes emoji candidates
>   * support configurable opencc config
>
>   version 1.10.92
>   * fixes Enter handling
>
>   version 1.10.91
>   * support ime.register_trigger in lua extension
>   * support predicted candidates
>   * support emoji input
>
>   version 1.10.0
>   * bug fixes
>
>   version 1.9.91
>   * migrate to use GSettings
>   * fixes lyx short cut issue
>
>   version 1.9.3
>   * translate input method name in ibus menu
>
>   Upstream ChangeLog libpinyin:
>   -
>   version 2.2.2
>   * minor fixes
>
>   version 2.2.1
>   * fixes predicted candidates
>
>   version 2.2.0
>   * bug fixes
>
>   The proposal is to backport the disco versions of those packages to
>   bionic and cosmic in an attempt to prevent crashes. Proposed uploads
>   are available in this PPA:
>
>   https://launchpad.net/~gunnarhj/+archive/ubuntu/ibus-libpinyin
>
>   [Test Case]
>
>   * Install from {bionic,cosmic}-proposed:
> - libpinyin13
> - libpinyin-data
> - ibus-libpinyin
>
>   * Use "Intelligent Pinyin" for typing and confirm that no new issues
> show up when doing so.
>
>   (This is apparently not a confirmation that the upload really fixes
>   the bug. To compensate for that, we will await testing of the
>   -proposed packages by a few Chinese users before considering the
>   uploads verified.)
>
>   Reverse dependencies
>   
>   Besides ibus-libpinyin, also fcitx-libpinyin and ibus-libzhuyin depend
> on packages belonging to the libpinyin source package. So additional test
> measures are:
>
>   * Install fcitx-libpinyin and ibus-libzhuyin.
>
>   * Use both those tools for typing Chinese, and confirm that you don't
> observe any adverse effects of the libpinyin upgrade.
>
>   [Regression Potential]
>
>   The changes are mostly bug fixes, so the regression risk should be
>   limited. Also consider that the starting point is a rather unstable
>   functionality.
>
>   NOTE TO SRU TEAM: Please let the SRU age for longer than 7 days to get
>   as much testing as possible. There do not seem to be too many risky
>   changes carried, but such jumps in upstream versions always carry some
>   regression-risk.
>
>   [Original description]
>
>   I have experienced random ibus-libpinyin crashes in bionic.  I cannot
>   reproduce it, but it occurred at least a few times, even after the
>   official bionic release.  Same crashes were also 

[Desktop-packages] [Bug 1831347] [NEW] Xorg freeze - update

[Peter]

Public bug reported:

Dear Ubuntu,

Thank you for taking the time to read this report. My last report stated
that nvidia-430 driver was the problem. I have since reinstalled ubuntu
18.4 and carefully followed the EGPU setup provided online using
gswitch. I should note that last install I forgot to add "systemctl
enable gswitch". I have noticed far fewer issues. Interestingly, I also
enabled autologin for my account. This appears to have helped the
problem significantly. I did try switching to regular password required
at login and the freezing / hanging did occur during some web browsing
but it was only for about 5 - 10 seconds. I then immediately switched
back to autologins and I have not noticed any freezing or hanging! I
believe the problem with regular password req logins is that it causes
my internal display (laptop screen) to be enabled first during the login
when I enter my password. After I enter my password the internal display
turns off and then I use my external display only as I have that
confiured in the ubuntu device settings. But with autologin, the
computer boots momentarily to internal screen when you see the ubuntu
dots sliding to the right and then into gnome.

So it appears using autologin is more stable when using an EGPU with
external display only! I am using nvidia-430 drivers.

So I think gdm3 needs an update or X11 needs an update so that it can
honor the external display better? Anyways! I will keep you posted.

Thanks for your dedication guys!!

Take care,

Peter

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xorg 1:7.7+19ubuntu7.1
ProcVersionSignature: Ubuntu 4.18.0-20.21~18.04.1-generic 4.18.20
Uname: Linux 4.18.0-20-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
.proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
.proc.driver.nvidia.gpus..07.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:07:00.0'
.proc.driver.nvidia.registry: Binary: ""
.proc.driver.nvidia.suspend: suspend hibernate resume
.proc.driver.nvidia.suspend_depth: default modeset uvm
.proc.driver.nvidia.version:
 NVRM version: NVIDIA UNIX x86_64 Kernel Module  430.14  Wed May  8 01:10:53 
UTC 2019
 GCC version:  gcc version 7.4.0 (Ubuntu 7.4.0-1ubuntu1~18.04)
ApportVersion: 2.20.9-0ubuntu7.6
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Sat Jun  1 16:26:04 2019
DistUpgraded: Fresh install
DistroCodename: bionic
DistroVariant: ubuntu
DkmsStatus: nvidia, 418.67, 4.18.0-20-generic, x86_64: installed
ExtraDebuggingInterest: Yes
GraphicsCard:
 Intel Corporation Device [8086:3e9b] (prog-if 00 [VGA controller])
   Subsystem: Dell Device [1028:087c]
   Subsystem: Dell GP107M [GeForce GTX 1050 Ti Mobile] [1028:087c]
 NVIDIA Corporation GP102 [GeForce GTX 1080 Ti] [10de:1b06] (rev a1) (prog-if 
00 [VGA controller])
   Subsystem: eVga.com. Corp. GP102 [GeForce GTX 1080 Ti] [3842:6696]
InstallationDate: Installed on 2019-06-01 (0 days ago)
InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210)
MachineType: Dell Inc. XPS 15 9570
ProcEnviron:
 LANGUAGE=en_CA:en
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_CA.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-20-generic 
root=UUID=96ec9aa4-d13a-4223-b15b-4284df054c79 ro quiet splash 
nouveau.modeset=0 vt.handoff=1
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 04/26/2019
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.10.1
dmi.board.name: 0D0T05
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 10
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvr1.10.1:bd04/26/2019:svnDellInc.:pnXPS159570:pvr:rvnDellInc.:rn0D0T05:rvrA00:cvnDellInc.:ct10:cvr:
dmi.product.family: XPS
dmi.product.name: XPS 15 9570
dmi.product.sku: 087C
dmi.sys.vendor: Dell Inc.
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.95-1~18.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.8-0ubuntu0~18.04.2
version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.8-0ubuntu0~18.04.2
version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
version.xserver-xorg-core: xserver-xorg-core N/A
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A

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


** Tags: amd64 apport-bug bionic possible-manual-nvidia-install ubuntu

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

Title:
  Xorg freeze - update

Status in xorg package in Ubuntu:
  New

Bug description:
  Dear Ubuntu,

  Thank you for taking the time to 

[Desktop-packages] [Bug 1768166] Re: Random crashes

[Gunnar Hjalmarsson]

@Ping-Wu: Which tools for inputting Chinese should be available on
Ubuntu going forward is indeed a valid discussion, but this bug report
is not a proper place for it. I notice your strong interest in the
topic, and if you want to start such a discussion, I would suggest that
you start a thread at .

For Ubuntu 18.04 we have the tools which are in the archive, and ibus-
libpinyin ("Intelligent Pinyin") is the default method for Simplified
Chinese. This bug (filed by yourself) is about upgrading the software
for that method, and only that.

So can we please focus here on testing the proposal to upgrade, and hold
the wider discussion in e.g. the Ubuntu Community Hub?

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

Title:
  Random crashes

Status in ibus-libpinyin package in Ubuntu:
  Fix Released
Status in libpinyin package in Ubuntu:
  Fix Released
Status in ibus-libpinyin source package in Bionic:
  Fix Committed
Status in libpinyin source package in Bionic:
  Fix Committed
Status in ibus-libpinyin source package in Cosmic:
  Fix Committed
Status in libpinyin source package in Cosmic:
  Fix Committed

Bug description:
  [Impact]

  ibus-libpinyin has proved to crash far too often. One or more files in
  ~/.cache/ibus/libpinyin get corrupted somehow, and emptying that
  directory allows the user to keep using ibus-libpinyin.

  In disco (and eoan) ibus-libpinyin 1.11.0 and libpinyin 2.2.2 are
  present, and the number of crashes has been reduced significantly:

  https://errors.ubuntu.com/?package=ibus-libpinyin=month

  Upstream ChangeLog ibus-libpinyin:
  --
  version 1.11.0
  * fixes keypad decimal
  * fixes emoji candidates
  * support configurable opencc config

  version 1.10.92
  * fixes Enter handling

  version 1.10.91
  * support ime.register_trigger in lua extension
  * support predicted candidates
  * support emoji input

  version 1.10.0
  * bug fixes

  version 1.9.91
  * migrate to use GSettings
  * fixes lyx short cut issue

  version 1.9.3
  * translate input method name in ibus menu

  Upstream ChangeLog libpinyin:
  -
  version 2.2.2
  * minor fixes

  version 2.2.1
  * fixes predicted candidates

  version 2.2.0
  * bug fixes

  The proposal is to backport the disco versions of those packages to
  bionic and cosmic in an attempt to prevent crashes. Proposed uploads
  are available in this PPA:

  https://launchpad.net/~gunnarhj/+archive/ubuntu/ibus-libpinyin

  [Test Case]

  * Install from {bionic,cosmic}-proposed:
    - libpinyin13
    - libpinyin-data
    - ibus-libpinyin

  * Use "Intelligent Pinyin" for typing and confirm that no new issues
    show up when doing so.

  (This is apparently not a confirmation that the upload really fixes
  the bug. To compensate for that, we will await testing of the
  -proposed packages by a few Chinese users before considering the
  uploads verified.)

  Reverse dependencies
  
  Besides ibus-libpinyin, also fcitx-libpinyin and ibus-libzhuyin depend on 
packages belonging to the libpinyin source package. So additional test measures 
are:

  * Install fcitx-libpinyin and ibus-libzhuyin.

  * Use both those tools for typing Chinese, and confirm that you don't
    observe any adverse effects of the libpinyin upgrade.

  [Regression Potential]

  The changes are mostly bug fixes, so the regression risk should be
  limited. Also consider that the starting point is a rather unstable
  functionality.

  NOTE TO SRU TEAM: Please let the SRU age for longer than 7 days to get
  as much testing as possible. There do not seem to be too many risky
  changes carried, but such jumps in upstream versions always carry some
  regression-risk.

  [Original description]

  I have experienced random ibus-libpinyin crashes in bionic.  I cannot
  reproduce it, but it occurred at least a few times, even after the
  official bionic release.  Same crashes were also reported in the
  Ubuntu Chinese forum.

  Currently, the workaround is to delete the ~/.cache/ibus/libpinyin
  folder.

  I talked to Peng Wu, ibus-libpinyin's creator and main maintainer, he
  suggested that we update the version of ibus-libpinyin to 1.10.

  Can we give this update a trial?

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

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

[Desktop-packages] [Bug 1831343] [NEW] [bionic] Full GNOME Session crash shortly after login

[Timothy Burke]

Public bug reported:

>From /var/log/syslog

Jun  1 10:52:50 armadillo gnome-session[1187]: gnome-session-binary[1187]: 
WARNING: Application 'org.gnome.SettingsDaemon.Color.desktop' failed to 
register before timeout
Jun  1 10:52:50 armadillo gnome-session-binary[1187]: WARNING: Application 
'org.gnome.SettingsDaemon.Color.desktop' failed to register before timeout
Jun  1 10:52:50 armadillo gnome-session-binary[1187]: Unrecoverable failure in 
required component org.gnome.SettingsDaemon.Color.desktop
Jun  1 10:52:50 armadillo gnome-session[1187]: gnome-session-binary[1187]: 
CRITICAL: We failed, but the fail whale is dead. Sorry
Jun  1 10:52:50 armadillo gnome-session-binary[1187]: CRITICAL: We failed, but 
the fail whale is dead. Sorry

Version 3.28.1-0ubuntu3

Has happened on multiple different installs on two different PCs (Dell
Latitude e6430 and Thinkpad x131e)

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: gnome-session-bin 3.28.1-0ubuntu3
ProcVersionSignature: Ubuntu 4.18.0-20.21~18.04.1-generic 4.18.20
Uname: Linux 4.18.0-20-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.6
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Sat Jun  1 11:43:05 2019
ExecutablePath: /usr/lib/gnome-session/gnome-session-binary
InstallationDate: Installed on 2019-05-31 (0 days ago)
InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210)
ProcEnviron:
 LANGUAGE=en_CA:en
 PATH=(custom, user)
 XDG_RUNTIME_DIR=
 LANG=en_CA.UTF-8
 SHELL=/bin/bash
SourcePackage: gnome-session
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug bionic

** Description changed:

  From /var/log/syslog
  
  Jun  1 10:52:50 armadillo gnome-session[1187]: gnome-session-binary[1187]: 
WARNING: Application 'org.gnome.SettingsDaemon.Color.desktop' failed to 
register before timeout
  Jun  1 10:52:50 armadillo gnome-session-binary[1187]: WARNING: Application 
'org.gnome.SettingsDaemon.Color.desktop' failed to register before timeout
  Jun  1 10:52:50 armadillo gnome-session-binary[1187]: Unrecoverable failure 
in required component org.gnome.SettingsDaemon.Color.desktop
  Jun  1 10:52:50 armadillo gnome-session[1187]: gnome-session-binary[1187]: 
CRITICAL: We failed, but the fail whale is dead. Sorry
  Jun  1 10:52:50 armadillo gnome-session-binary[1187]: CRITICAL: We failed, 
but the fail whale is dead. Sorry
  
  Version 3.28.1-0ubuntu3
+ 
+ Has happened on multiple different installs on two different PCs (Dell
+ Latitude e6430 and Thinkpad x131e)
  
  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-session-bin 3.28.1-0ubuntu3
  ProcVersionSignature: Ubuntu 4.18.0-20.21~18.04.1-generic 4.18.20
  Uname: Linux 4.18.0-20-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Jun  1 11:43:05 2019
  ExecutablePath: /usr/lib/gnome-session/gnome-session-binary
  InstallationDate: Installed on 2019-05-31 (0 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  ProcEnviron:
-  LANGUAGE=en_CA:en
-  PATH=(custom, user)
-  XDG_RUNTIME_DIR=
-  LANG=en_CA.UTF-8
-  SHELL=/bin/bash
+  LANGUAGE=en_CA:en
+  PATH=(custom, user)
+  XDG_RUNTIME_DIR=
+  LANG=en_CA.UTF-8
+  SHELL=/bin/bash
  SourcePackage: gnome-session
  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-session in Ubuntu.
https://bugs.launchpad.net/bugs/1831343

Title:
  [bionic] Full GNOME Session crash shortly after login

Status in gnome-session package in Ubuntu:
  New

Bug description:
  From /var/log/syslog

  Jun  1 10:52:50 armadillo gnome-session[1187]: gnome-session-binary[1187]: 
WARNING: Application 'org.gnome.SettingsDaemon.Color.desktop' failed to 
register before timeout
  Jun  1 10:52:50 armadillo gnome-session-binary[1187]: WARNING: Application 
'org.gnome.SettingsDaemon.Color.desktop' failed to register before timeout
  Jun  1 10:52:50 armadillo gnome-session-binary[1187]: Unrecoverable failure 
in required component org.gnome.SettingsDaemon.Color.desktop
  Jun  1 10:52:50 armadillo gnome-session[1187]: gnome-session-binary[1187]: 
CRITICAL: We failed, but the fail whale is dead. Sorry
  Jun  1 10:52:50 armadillo gnome-session-binary[1187]: CRITICAL: We failed, 
but the fail whale is dead. Sorry

  Version 3.28.1-0ubuntu3

  Has happened on multiple different installs on two different PCs (Dell
  Latitude e6430 and Thinkpad x131e)

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-session-bin 3.28.1-0ubuntu3
  ProcVersionSignature: Ubuntu 4.18.0-20.21~18.04.1-generic 4.18.20
  Uname: Linux 4.18.0-20-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Jun  1 11:43:05 2019
  ExecutablePath: 

[Desktop-packages] [Bug 1831341] Re: package libreoffice-common 1:5.1.6~rc2-0ubuntu1~xenial6 failed to install/upgrade: unable to stat './usr/share/icons/locolor/32x32/mimetypes/libreoffice-oasis-draw

[Apport retracing service]

** Tags removed: need-duplicate-check

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

Title:
  package libreoffice-common 1:5.1.6~rc2-0ubuntu1~xenial6 failed to
  install/upgrade: unable to stat
  './usr/share/icons/locolor/32x32/mimetypes/libreoffice-oasis-
  drawing.png' (which I was about to install): Input/output error

Status in libreoffice package in Ubuntu:
  New

Bug description:
  Distribution-upgrade was proposed on my BananaPi from Ubuntu 16.04.6
  LTS to 18.04.2 LTS. I agreed, but during the process, the crash
  occured.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libreoffice-common 1:5.1.6~rc2-0ubuntu1~xenial6
  Uname: Linux 3.4.39-BPI-M3-Kernel armv7l
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: armhf
  Date: Sat Jun  1 18:32:16 2019
  DuplicateSignature:
   package:libreoffice-common:1:5.1.6~rc2-0ubuntu1~xenial6
   Unpacking ure (5.1.6~rc2-0ubuntu1~xenial7) over (5.1.6~rc2-0ubuntu1~xenial6) 
...
   dpkg: error processing archive 
/var/cache/apt/archives/ure_5.1.6~rc2-0ubuntu1~xenial7_armhf.deb (--unpack):
unable to stat 
'./usr/share/maven-repo/org/libreoffice/jurt/5.1.6/jurt-5.1.6.jar' (which I was 
about to install): Input/output error
  ErrorMessage: unable to stat 
'./usr/share/icons/locolor/32x32/mimetypes/libreoffice-oasis-drawing.png' 
(which I was about to install): Input/output error
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.5
   apt  1.2.31
  SourcePackage: libreoffice
  Title: package libreoffice-common 1:5.1.6~rc2-0ubuntu1~xenial6 failed to 
install/upgrade: unable to stat 
'./usr/share/icons/locolor/32x32/mimetypes/libreoffice-oasis-drawing.png' 
(which I was about to install): Input/output error
  UpgradeStatus: Upgraded to xenial on 2019-06-01 (0 days ago)

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

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

[Desktop-packages] [Bug 1831341] Re: package libreoffice-common 1:5.1.6~rc2-0ubuntu1~xenial6 failed to install/upgrade: unable to stat './usr/share/icons/locolor/32x32/mimetypes/libreoffice-oasis-draw

[Tilmann Rückauer]

Ah, to be precise: The Upgrade was cancelled due to lacking space on /.
Afterwards, an update was proposed, during which this error occurred.

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

Title:
  package libreoffice-common 1:5.1.6~rc2-0ubuntu1~xenial6 failed to
  install/upgrade: unable to stat
  './usr/share/icons/locolor/32x32/mimetypes/libreoffice-oasis-
  drawing.png' (which I was about to install): Input/output error

Status in libreoffice package in Ubuntu:
  New

Bug description:
  Distribution-upgrade was proposed on my BananaPi from Ubuntu 16.04.6
  LTS to 18.04.2 LTS. I agreed, but during the process, the crash
  occured.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libreoffice-common 1:5.1.6~rc2-0ubuntu1~xenial6
  Uname: Linux 3.4.39-BPI-M3-Kernel armv7l
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: armhf
  Date: Sat Jun  1 18:32:16 2019
  DuplicateSignature:
   package:libreoffice-common:1:5.1.6~rc2-0ubuntu1~xenial6
   Unpacking ure (5.1.6~rc2-0ubuntu1~xenial7) over (5.1.6~rc2-0ubuntu1~xenial6) 
...
   dpkg: error processing archive 
/var/cache/apt/archives/ure_5.1.6~rc2-0ubuntu1~xenial7_armhf.deb (--unpack):
unable to stat 
'./usr/share/maven-repo/org/libreoffice/jurt/5.1.6/jurt-5.1.6.jar' (which I was 
about to install): Input/output error
  ErrorMessage: unable to stat 
'./usr/share/icons/locolor/32x32/mimetypes/libreoffice-oasis-drawing.png' 
(which I was about to install): Input/output error
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.5
   apt  1.2.31
  SourcePackage: libreoffice
  Title: package libreoffice-common 1:5.1.6~rc2-0ubuntu1~xenial6 failed to 
install/upgrade: unable to stat 
'./usr/share/icons/locolor/32x32/mimetypes/libreoffice-oasis-drawing.png' 
(which I was about to install): Input/output error
  UpgradeStatus: Upgraded to xenial on 2019-06-01 (0 days ago)

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

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

[Desktop-packages] [Bug 1831341] [NEW] package libreoffice-common 1:5.1.6~rc2-0ubuntu1~xenial6 failed to install/upgrade: unable to stat './usr/share/icons/locolor/32x32/mimetypes/libreoffice-oasis-dr

[Tilmann Rückauer]

Public bug reported:

Distribution-upgrade was proposed on my BananaPi from Ubuntu 16.04.6 LTS
to 18.04.2 LTS. I agreed, but during the process, the crash occured.

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: libreoffice-common 1:5.1.6~rc2-0ubuntu1~xenial6
Uname: Linux 3.4.39-BPI-M3-Kernel armv7l
ApportVersion: 2.20.1-0ubuntu2.18
Architecture: armhf
Date: Sat Jun  1 18:32:16 2019
DuplicateSignature:
 package:libreoffice-common:1:5.1.6~rc2-0ubuntu1~xenial6
 Unpacking ure (5.1.6~rc2-0ubuntu1~xenial7) over (5.1.6~rc2-0ubuntu1~xenial6) 
...
 dpkg: error processing archive 
/var/cache/apt/archives/ure_5.1.6~rc2-0ubuntu1~xenial7_armhf.deb (--unpack):
  unable to stat 
'./usr/share/maven-repo/org/libreoffice/jurt/5.1.6/jurt-5.1.6.jar' (which I was 
about to install): Input/output error
ErrorMessage: unable to stat 
'./usr/share/icons/locolor/32x32/mimetypes/libreoffice-oasis-drawing.png' 
(which I was about to install): Input/output error
PackageArchitecture: all
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.5
 apt  1.2.31
SourcePackage: libreoffice
Title: package libreoffice-common 1:5.1.6~rc2-0ubuntu1~xenial6 failed to 
install/upgrade: unable to stat 
'./usr/share/icons/locolor/32x32/mimetypes/libreoffice-oasis-drawing.png' 
(which I was about to install): Input/output error
UpgradeStatus: Upgraded to xenial on 2019-06-01 (0 days ago)

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


** Tags: apport-package armhf xenial

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

Title:
  package libreoffice-common 1:5.1.6~rc2-0ubuntu1~xenial6 failed to
  install/upgrade: unable to stat
  './usr/share/icons/locolor/32x32/mimetypes/libreoffice-oasis-
  drawing.png' (which I was about to install): Input/output error

Status in libreoffice package in Ubuntu:
  New

Bug description:
  Distribution-upgrade was proposed on my BananaPi from Ubuntu 16.04.6
  LTS to 18.04.2 LTS. I agreed, but during the process, the crash
  occured.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libreoffice-common 1:5.1.6~rc2-0ubuntu1~xenial6
  Uname: Linux 3.4.39-BPI-M3-Kernel armv7l
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: armhf
  Date: Sat Jun  1 18:32:16 2019
  DuplicateSignature:
   package:libreoffice-common:1:5.1.6~rc2-0ubuntu1~xenial6
   Unpacking ure (5.1.6~rc2-0ubuntu1~xenial7) over (5.1.6~rc2-0ubuntu1~xenial6) 
...
   dpkg: error processing archive 
/var/cache/apt/archives/ure_5.1.6~rc2-0ubuntu1~xenial7_armhf.deb (--unpack):
unable to stat 
'./usr/share/maven-repo/org/libreoffice/jurt/5.1.6/jurt-5.1.6.jar' (which I was 
about to install): Input/output error
  ErrorMessage: unable to stat 
'./usr/share/icons/locolor/32x32/mimetypes/libreoffice-oasis-drawing.png' 
(which I was about to install): Input/output error
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.5
   apt  1.2.31
  SourcePackage: libreoffice
  Title: package libreoffice-common 1:5.1.6~rc2-0ubuntu1~xenial6 failed to 
install/upgrade: unable to stat 
'./usr/share/icons/locolor/32x32/mimetypes/libreoffice-oasis-drawing.png' 
(which I was about to install): Input/output error
  UpgradeStatus: Upgraded to xenial on 2019-06-01 (0 days ago)

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

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

[Desktop-packages] [Bug 1827843] Re: Ubuntu 18.04: App Menu Drawer doesn't show up fully always!

[gmagoon]

Looks like that was it. I removed all my extensions and I don't get that
app display error anymore. I guess I will have to do without the net
speed extension :(

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

Title:
  Ubuntu 18.04: App Menu Drawer doesn't show up fully always!

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  Hi
  I am using Ubuntu 18.04. The App Menu Drawer doesn't show up always fully 
with all the icons. Sometimes one page shows up while the rest of the pages are 
empty. Not sure what caused this Thanks!

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-48.51-generic 4.15.18
  Uname: Linux 4.15.0-48-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Mon May  6 14:07:50 2019
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: No
  GraphicsCard:
   Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA 
controller])
 Subsystem: Dell HD Graphics 5500 [1028:06b0]
  InstallationDate: Installed on 2019-02-10 (85 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: Dell Inc. Inspiron 3558
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-48-generic 
root=UUID=11c430c4-0277-4837-abc2-5daafb4e3cd5 ro quiet splash vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/27/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A17
  dmi.board.name: 0PNFDX
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA17:bd08/27/2018:svnDellInc.:pnInspiron3558:pvr:rvnDellInc.:rn0PNFDX:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: Inspiron 3558
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
  version.libdrm2: libdrm2 2.4.95-1~18.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.8-0ubuntu0~18.04.2
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.8-0ubuntu0~18.04.2
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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

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

[Desktop-packages] [Bug 1831339] [NEW] Backup Unbuntu ERROR undefined

[Louis Peutzen]

Public bug reported:

Backup Unbuntu ERROR undefined

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xorg 1:7.7+19ubuntu7.1
ProcVersionSignature: Ubuntu 4.18.0-20.21~18.04.1-generic 4.18.20
Uname: Linux 4.18.0-20-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.6
Architecture: amd64
CompositorRunning: None
Date: Sat Jun  1 14:59:04 2019
DistUpgraded: Fresh install
DistroCodename: bionic
DistroVariant: ubuntu
DpkgLog:
 
ExtraDebuggingInterest: Yes, including running git bisection searches
GraphicsCard:
 NVIDIA Corporation GF108 [GeForce GT 430] [10de:0de1] (rev a1) (prog-if 00 
[VGA controller])
   Subsystem: eVga.com. Corp. GF108 [GeForce GT 430] [3842:1335]
InstallationDate: Installed on 2019-03-27 (66 days ago)
InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210)
MachineType: System manufacturer System Product Name
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-20-generic 
root=/dev/mapper/ubuntu--vg-root ro drm.debug=0xe plymouth:debug
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 11/18/2009
dmi.bios.vendor: Phoenix Technologies, LTD
dmi.bios.version: ASUS P5N-E SLI ACPI BIOS Revision 1406
dmi.board.name: P5N-E SLI
dmi.board.vendor: ASUSTeK Computer INC.
dmi.board.version: 1.XX
dmi.chassis.asset.tag: 123456789000
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.version: Chassis Version
dmi.modalias: 
dmi:bvnPhoenixTechnologies,LTD:bvrASUSP5N-ESLIACPIBIOSRevision1406:bd11/18/2009:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5N-ESLI:rvr1.XX:cvnChassisManufacture:ct3:cvrChassisVersion:
dmi.product.name: System Product Name
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.95-1~18.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.8-0ubuntu0~18.04.2
version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.8-0ubuntu0~18.04.2
version.xserver-xorg-core: xserver-xorg-core N/A
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
xserver.bootTime: Wed Apr 24 21:29:22 2019

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


** Tags: amd64 apport-bug bionic third-party-packages ubuntu

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

Title:
  Backup Unbuntu ERROR undefined

Status in xorg package in Ubuntu:
  New

Bug description:
  Backup Unbuntu ERROR undefined

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.18.0-20.21~18.04.1-generic 4.18.20
  Uname: Linux 4.18.0-20-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  CompositorRunning: None
  Date: Sat Jun  1 14:59:04 2019
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  DpkgLog:
   
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   NVIDIA Corporation GF108 [GeForce GT 430] [10de:0de1] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: eVga.com. Corp. GF108 [GeForce GT 430] [3842:1335]
  InstallationDate: Installed on 2019-03-27 (66 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  MachineType: System manufacturer System Product Name
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-20-generic 
root=/dev/mapper/ubuntu--vg-root ro drm.debug=0xe plymouth:debug
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/18/2009
  dmi.bios.vendor: Phoenix Technologies, LTD
  dmi.bios.version: ASUS P5N-E SLI ACPI BIOS Revision 1406
  dmi.board.name: P5N-E SLI
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: 1.XX
  dmi.chassis.asset.tag: 123456789000
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnPhoenixTechnologies,LTD:bvrASUSP5N-ESLIACPIBIOSRevision1406:bd11/18/2009:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5N-ESLI:rvr1.XX:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.95-1~18.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.8-0ubuntu0~18.04.2
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.8-0ubuntu0~18.04.2
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  

[Desktop-packages] [Bug 1827948] Re: Use libreoffice-style-breeze as the default icon theme

[Frederik Feichtmeier]

There is one problem with colibre: it doesn't work with dark themes :/

Whereas breeze has a dark and a light variant for yaru and yaru dark

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

Title:
  Use libreoffice-style-breeze as the default icon theme

Status in libreoffice package in Ubuntu:
  New

Bug description:
  The Yaru icon theme uses 1 pixel strokes for its symbolic icon set. 
  So do the breeze icons for libreoffice.

  All in all does the breeze icon set for libre office fit very good to
  the look of the Yaru icons.

  https://i.imgur.com/tgioycv.png

  https://i.imgur.com/WwKvjMh.png

  Thus I would suggest to use it as the default icon set in Ubuntu to
  guarantee a consistent look and feel across the desktop

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

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

[Desktop-packages] [Bug 1794139] Re: At random times, no warning when closing a file after it's been deleted

[C de-Avillez]

** Bug watch added: gitlab.gnome.org/GNOME/gedit/issues #73
   https://gitlab.gnome.org/GNOME/gedit/issues/73

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

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

Title:
  At random times, no warning when closing a file after it's been
  deleted

Status in gedit:
  Unknown
Status in gedit package in Ubuntu:
  Triaged

Bug description:
  See https://gitlab.gnome.org/GNOME/gedit/issues/73#note_331812

  Closed upstream because gedit version too old.

  It seem I never get it right. When I report an issue here I get told
  to report it upstream, and viceversa.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: gedit 3.18.3-0ubuntu4
  ProcVersionSignature: Ubuntu 4.4.0-135.161-generic 4.4.140
  Uname: Linux 4.4.0-135-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Mon Sep 24 17:46:45 2018
  InstallationDate: Installed on 2013-10-11 (1808 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  SourcePackage: gedit
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1827446] Re: Unable to switch back to nvidia after suspend on intel

[Jean-Francois Labonte]

I am planning to test this command :

`echo "1" > /sys/bus/pci/devices/\:01\:00.0/reset`

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

Title:
  Unable to switch back to nvidia after suspend on intel

Status in Nvidia:
  New
Status in NVIDIA-Common:
  New
Status in nvidia-prime package in Ubuntu:
  New

Bug description:
  I am not sure that it is something that an issue caused by nvidia-prime
  or if it is something that is cause in the drivers or if it is a bug with
  the kernel itself, cause it seems to be a problem with Linux PM, so this bug
  could be moved if needed

  *** What's Wrong? ***

  As the title states, I am unable to use the Nvidia GPU when I have
  changed profile for intel then computer on suspend for more than 30
  minutes ( This has to be determined precisely how long until I get the
  issue ) and then set back the profile to nvidia.

  So basically, it seems that the nvidia modules are unable to be loaded, I 
have tried to fix
  the issue using bbswitch. It doesn't work neither, if the 
/sys/bus/pci/devices/\:01\:00.0/power/control is set to auto, I am unable 
to load the kernel modules anymore.

  *** What do I expect ***

  Well, I was hoping that I would be able to keep my laptop on and simply 
switch from one GPU to other
  seamlessly. It is, until I put my laptop on suspend for an extended time 
while I am on powersaving mode

  

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: nvidia-prime 0.8.10
  Uname: 5.0.0-14-generic #15-Ubuntu x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia
  Architecture: amd64
  CurrentDesktop: MATE
  CurrentDM: GDM3
  Date Thursday May 2nd 2019 7:49 PM
  InstallationDate: Installed on  (0 days ago)
  SourcePackage: nvidia-prime
  UpgradeStatus: No upgrade log present (fresh install)

  Description:  Ubuntu 19.04
  Release:  19.04
  nvidia-prime:
    Installed: 0.8.10
    Candidate: 0.8.10
    Version table:
   *** 0.8.10 500
  500 http://ca.archive.ubuntu.com/ubuntu disco/main amd64 Packages
  500 http://ca.archive.ubuntu.com/ubuntu disco/main i386 Packages
  100 /var/lib/dpkg/status

  /var/lib/dpkg/status -> https://paste.ubuntu.com/p/McmJHRgjTH/

  https://paste.ubuntu.com/p/Pxnw7mDmzQ/ -> dmesg before issue

   MORE dmesg will come, need to get fresh data! *

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

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

[Desktop-packages] [Bug 1831328] [NEW] Ubuntu 18.04 LTS boot hangs after 1st update

[Sylvain Vedrenne]

Public bug reported:

I installed Ubuntu 18.04 LTS on my new ASUS UX533F laptop.

The installation seemed successful at first - except for the audio not
working - but then:

- open "Software Updates"
- accept to install all available updates
- reboot
  => The system hangs on the purple screen

If I press the space bar before the ASUS logo at boot, I can access the
GRUB menu and select the Recovery Mode - same problem in Recovery Mode:
the system hangs on the purple screen.

To avoid instability issues with the graphics card NVidia GeForce MX150,
I had added 'nouveau.modeset=0' to /etc/default/grub for the Linux
command line before doing the first software update and reboot.

/etc/default/grub
...
GRUB_CMDLINE_LINUX_DEFAULT="quiet splash nouveau.modeset=0"
...

But it doesn't prevent this boot hanging problem. And it is not the
cause of this boot hanging problem.

Adding dis_ucode_ldr to the Linux command line lets me to go past the
GRUB screen and boot Ubuntu 18.04 again. But this is only a workaround.
We need a proper fix.

** Affects: ubuntu
 Importance: Undecided
 Status: New

** Package changed: gvfs (Ubuntu) => ubuntu

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

Title:
  Ubuntu 18.04 LTS boot hangs after 1st update

Status in Ubuntu:
  New

Bug description:
  I installed Ubuntu 18.04 LTS on my new ASUS UX533F laptop.

  The installation seemed successful at first - except for the audio not
  working - but then:

  - open "Software Updates"
  - accept to install all available updates
  - reboot
=> The system hangs on the purple screen

  If I press the space bar before the ASUS logo at boot, I can access
  the GRUB menu and select the Recovery Mode - same problem in Recovery
  Mode: the system hangs on the purple screen.

  To avoid instability issues with the graphics card NVidia GeForce
  MX150, I had added 'nouveau.modeset=0' to /etc/default/grub for the
  Linux command line before doing the first software update and reboot.

  /etc/default/grub
  ...
  GRUB_CMDLINE_LINUX_DEFAULT="quiet splash nouveau.modeset=0"
  ...

  But it doesn't prevent this boot hanging problem. And it is not the
  cause of this boot hanging problem.

  Adding dis_ucode_ldr to the Linux command line lets me to go past the
  GRUB screen and boot Ubuntu 18.04 again. But this is only a
  workaround. We need a proper fix.

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

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

[Desktop-packages] [Bug 1831322] Re: Installer hangs right after GRUB screen

[Sylvain Vedrenne]

** Package changed: gvfs (Ubuntu) => ubuntu

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

Title:
  Installer hangs right after GRUB screen

Status in Ubuntu:
  New

Bug description:
  I wanted to try Ubuntu 19.04 on my new ASUS UX533 laptop, but it
  miserably failed right after selecting "Try Ubuntu" in the GRUB menu.

  - download the 64-bit PC (AMD64) desktop image and write it on a USB key with 
dd
  - boot the laptop from the USB key
=> the GRUB screen displays Ok
  - select "Try Ubuntu"
=> the GRUB screen disappears Ok
=> blank screen Ok
=> the system hangs there KO

  Same problem when selecting any of the options in the GRUB menu, even
  the "Safe graphics" ones.

  I suspected a problem with the NVidia GeForce MX150 graphics card, so
  I tried adding

nomedeset
  or
nouveau.modeset=0

  to the Linux command line, but it didn't work better.

  I tried (found on the internet) adding
dis_ucode_ldr to the Linux command line
  and this worked!

  But obviously we need a proper fix.

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

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

[Desktop-packages] [Bug 1831322] Re: Installer hangs right after GRUB screen

[Sylvain Vedrenne]

Doesn't affect gvfs.

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

Title:
  Installer hangs right after GRUB screen

Status in gvfs package in Ubuntu:
  New

Bug description:
  I wanted to try Ubuntu 19.04 on my new ASUS UX533 laptop, but it
  miserably failed right after selecting "Try Ubuntu" in the GRUB menu.

  - download the 64-bit PC (AMD64) desktop image and write it on a USB key with 
dd
  - boot the laptop from the USB key
=> the GRUB screen displays Ok
  - select "Try Ubuntu"
=> the GRUB screen disappears Ok
=> blank screen Ok
=> the system hangs there KO

  Same problem when selecting any of the options in the GRUB menu, even
  the "Safe graphics" ones.

  I suspected a problem with the NVidia GeForce MX150 graphics card, so
  I tried adding

nomedeset
  or
nouveau.modeset=0

  to the Linux command line, but it didn't work better.

  I tried (found on the internet) adding
dis_ucode_ldr to the Linux command line
  and this worked!

  But obviously we need a proper fix.

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

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

[Desktop-packages] [Bug 1831322] [NEW] Installer hangs right after GRUB screen

[Sylvain Vedrenne]

Public bug reported:

I wanted to try Ubuntu 19.04 on my new ASUS UX533 laptop, but it
miserably failed right after selecting "Try Ubuntu" in the GRUB menu.

- download the 64-bit PC (AMD64) desktop image and write it on a USB key with dd
- boot the laptop from the USB key
  => the GRUB screen displays Ok
- select "Try Ubuntu"
  => the GRUB screen disappears Ok
  => blank screen Ok
  => the system hangs there KO

Same problem when selecting any of the options in the GRUB menu, even
the "Safe graphics" ones.

I suspected a problem with the NVidia GeForce MX150 graphics card, so I
tried adding

  nomedeset
or
  nouveau.modeset=0

to the Linux command line, but it didn't work better.

I tried (found on the internet) adding
  dis_ucode_ldr to the Linux command line
and this worked!

But obviously we need a proper fix.

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

Title:
  Installer hangs right after GRUB screen

Status in gvfs package in Ubuntu:
  New

Bug description:
  I wanted to try Ubuntu 19.04 on my new ASUS UX533 laptop, but it
  miserably failed right after selecting "Try Ubuntu" in the GRUB menu.

  - download the 64-bit PC (AMD64) desktop image and write it on a USB key with 
dd
  - boot the laptop from the USB key
=> the GRUB screen displays Ok
  - select "Try Ubuntu"
=> the GRUB screen disappears Ok
=> blank screen Ok
=> the system hangs there KO

  Same problem when selecting any of the options in the GRUB menu, even
  the "Safe graphics" ones.

  I suspected a problem with the NVidia GeForce MX150 graphics card, so
  I tried adding

nomedeset
  or
nouveau.modeset=0

  to the Linux command line, but it didn't work better.

  I tried (found on the internet) adding
dis_ucode_ldr to the Linux command line
  and this worked!

  But obviously we need a proper fix.

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

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

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

[Dan Streetman]

> Is this going to be fixed in disco?

speaking for systemd only, the commit needed is 
a97a3b256cd6c56ab1d817440d3b8acb3272ee17:
https://github.com/systemd/systemd/commit/a97a3b256

that's included starting at v240, so is already in disco.

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

Title:
  Full-tunnel VPN DNS leakage regression

Status in NetworkManager:
  Fix Released
Status in network-manager package in Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  Fix Released
Status in network-manager source package in Xenial:
  New
Status in systemd source package in Xenial:
  Invalid
Status in network-manager source package in Bionic:
  In Progress
Status in systemd source package in Bionic:
  Fix Committed
Status in network-manager source package in Cosmic:
  New
Status in systemd source package in Cosmic:
  Fix Committed

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

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

  2) Connect to the VPN.

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

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

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

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

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

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

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

  -

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

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

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

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

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

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

[Desktop-packages] [Bug 1830408] Re: [nouveau][XFCE] Do not see login screen after screen is blanked

[crysman]

Another piece of information:
It seems to be broken only once - at the first time. When I do the workaround 
and let it go blank again, no need to repeat it - just once every fresh boot 
seems to be enough. Weird...

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

Title:
  [nouveau][XFCE] Do not see login screen after screen is blanked

Status in lightdm package in Ubuntu:
  New

Bug description:
  I've just upgraded to 18.10 from 18.04. Now when power manager (or
  whoever) puts the screen to blank, I cannot login, because I do not
  see anything. Befeore the upgrade, mouse move or keypress led to login
  screen. Now does not.

  Workaround:
  When I go to terminal on tty1 and then back CTRL+ALT+F7, login screen appears.

  Where is the problem and how to fix it please?

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: xorg 1:7.7+19ubuntu8
  ProcVersionSignature: Ubuntu 4.18.0-20.21-generic 4.18.20
  Uname: Linux 4.18.0-20-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13.3
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: XFCE
  Date: Fri May 24 17:59:31 2019
  DistUpgraded: 2019-05-24 13:40:45,847 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process 
“./xorg_fix_proprietary.py” (No such file or directory) (8))
  DistroCodename: cosmic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. 2nd Generation Core Processor Family 
Integrated Graphics Controller [1043:1682]
   NVIDIA Corporation GF119M [GeForce GT 520M] [10de:1050] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: ASUSTeK Computer Inc. GF119M [GeForce GT 520M] [1043:1682]
  InstallationDate: Installed on 2018-09-03 (263 days ago)
  InstallationMedia: Xubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: ASUSTeK Computer Inc. U36SD
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.18.0-20-generic 
root=UUID=aa87c0a2-5b06-40fb-82dd-fbccd7c800e6 ro quiet splash vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to cosmic on 2019-05-24 (0 days ago)
  dmi.bios.date: 07/12/2011
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: U36SD.205
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: U36SD
  dmi.board.vendor: ASUSTeK Computer Inc.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK Computer Inc.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrU36SD.205:bd07/12/2011:svnASUSTeKComputerInc.:pnU36SD:pvr1.0:rvnASUSTeKComputerInc.:rnU36SD:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr1.0:
  dmi.product.family: U
  dmi.product.name: U36SD
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK Computer Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.95-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.8-0ubuntu0~18.10.2
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.8-0ubuntu0~18.10.2
  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

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

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

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

[Daniel Risacher]

I see this problem when I am running Calibre and connect a Kindle Fire.
The Fire shows up as a mounted device in Nautilus, but has nothing on it
(which is wrong).  Errors from both dmesg and Calibre imply that the
problem may be related to libusb_claim_interface()

dmesg shows:

[149203.958526] usb 1-1: new high-speed USB device number 6 using xhci_hcd
[149204.107572] usb 1-1: New USB device found, idVendor=1949, idProduct=00f1
[149204.107582] usb 1-1: New USB device strings: Mfr=2, Product=3, 
SerialNumber=4
[149204.107589] usb 1-1: Product: Fire
[149204.107595] usb 1-1: Manufacturer: Amazon
[149204.107601] usb 1-1: SerialNumber: 00DA080750350787
[149205.439654] usb 1-1: usbfs: process 19822 (DeviceManager) did not claim 
interface 0 before use
[149205.567133] usb 1-1: reset high-speed USB device number 6 using xhci_hcd
[149205.715936] usb 1-1: usbfs: process 19822 (DeviceManager) did not claim 
interface 0 before use
[149205.716428] usb 1-1: usbfs: process 19851 (events) did not claim interface 
0 before use
[149205.716462] usb 1-1: usbfs: process 19851 (events) did not claim interface 
0 before use
[149205.716643] usb 1-1: usbfs: process 19851 (events) did not claim interface 
0 before use
[149205.717093] usb 1-1: usbfs: process 19822 (DeviceManager) did not claim 
interface 0 before use

Calibre output:

Device 0 (VID=1949 and PID=00f1) is UNKNOWN in libmtp v1.1.13.
Please report this VID/PID and the device model to the libmtp development team
ignoring libusb_claim_interface() = -6PTP_ERROR_IO: failed to open session, 
trying again after resetting USB interface
LIBMTP libusb: Attempt to reset device
ignoring libusb_claim_interface() = -6LIBMTP PANIC: failed to open session on 
second attempt
Error while trying to open MTPDevice(busnum=1, devnum=5, vendor_id=6473, 
product_id=241, bcd=65535, serial=u'00DA080750350787', manufacturer=u'Amazon', 
product=u'Fire') (Driver: )
Traceback (most recent call last):
  File "/usr/lib/calibre/calibre/gui2/device.py", line 295, in detect_device
dev.open(cd, self.current_library_uuid)
  File "/usr/lib/calibre/calibre/devices/mtp/driver.py", line 126, in open
BASE.open(self, device, library_uuid)
  File "/usr/lib/calibre/calibre/devices/mtp/base.py", line 26, in synchronizer
return func(self, *args, **kwargs)
  File "/usr/lib/calibre/calibre/devices/mtp/unix/driver.py", line 220, in open
connected_device, as_unicode(e)))
OpenFailed: Failed to open MTPDevice(busnum=1, devnum=5, vendor_id=6473, 
product_id=241, bcd=65535, serial=u'00DA080750350787', manufacturer=u'Amazon', 
product=u'Fire'): Error: Unable to open MTP device with busnum=1 and devnum=5, 
tried 1 such devices

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

Title:
  MTP not working/very slow on Bionic

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

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

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

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

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

  That's all!

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

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

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

[Desktop-packages] [Bug 1825717] Re: hplip issue during hp-setup - stuck at plugin install

[Mauro Gaspari]

Additional Feedback.

I did a fresh install of ubuntu-budgie 19.04
1. installed hplip from repos (version 3.19.1)
2. ran hp-setup -i 
3. went through the steps
4. install completed including plugin, can print and scan with no issue

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

Title:
  hplip issue during hp-setup - stuck at plugin install

Status in hplip package in Ubuntu:
  Confirmed

Bug description:
  Fresh install of Kubuntu 19.04 
  Installed hplip from repositories, available version is 3.19.1+dfsg0-1

  When I start setup with hp-setup, this happens:
  1. I am asked connection type. I select network ethernet
  2. My printer is detected. I select it and hit next
  3. I am told about the proprietary plugin to download. I confirm, accept 
download. I enter my user's password. I get a confirmation that the plugin is 
correctly Installed.
  4. On next screen, I get a warning and cannot continue installation. I am 
told this printer needs a proprietary plugin to work correctly. After this I am 
stuck in a loop between points 3 and 4. I also tried to start hp-setup from 
super user on command line. but no way around this issue.

  What I did next, I manually downloaded hplip-3.19.3.run from HP
  website. Removed version of hplip installed from repositories.
  Installed from manually downloaded package, followed the very same
  steps. Everything worked fine and printer is installed successfully.

  I hope this information is useful.

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

-- 
Mailing list: https://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 1768166] Re: Random crashes

[Ping-Wu]

I have been hearing this swan song for several years now that ibus-pinyin
is being or has been deprecated.  Actually it is a miracle that ibus-pinyin
still works in Ubuntu--*and only in Ubuntu*.  For unknown and very strange
reasons, I can never make ibus-pinyin work in Fedora, or even in Debian.
Indeed, this is the main reason that I am sticking with Ubuntu, even though
I was one of the very first supporters of the Fedora Linux when it was
being developed at the University of Hawaii.

Most Linux users in the Chinese Ubuntu forum actually use Sogou pinyin
(搜狗拼音）, this is a proprietary program running on the fcitx input
framework.  Sogou pinyin is definitely better than ibus-libpinyin (very few
people actually use ibus-libpinyin), but is inferior to ibus-pinyin in
terms of speed and stability.  We have a pro bono project in Honolulu
teaching seniors to be proficient in computers. Since many of our students
are of Chinese descent, our program also includes teaching them how to
input Chinese characters.  Ibus-pinyin has been our choice of Chinese input
tool because of its snappiness and being trouble-free.  You would think
that these two characters should also make ibus-pinyin a favorable Chinese
input engine?  But since so few people in China are using Linux desktops,
logic doesn't make sense.  It is the so-called upstream developers (mainly
Peng Wu of Red Hat), or the lack thereof (ibus-pinyin developers), that
prevails.

Based on my interactions with many Chinese Ubuntu forum elders, I am NOT
surprised that the upstream developers do not think highly of ibus-pinyin.
The reasons are three-fold: first, they are not using the right distro
(i.e., not using Ubuntu); second, they did not install a Ubuntu-specific
ibus-pinyin database (i.e., system-wide vocabulary); and third, they have
not used ibus-pinyin long enough (i.e., they do not have their own user
vocabulary).

I think upstream developers do not like ibus-pinyin also because it does
not have many bells and whistles (e.g., inputting emojis which I absolutely
could care less).  But ibus-pinyin also has some of the critical features
that are lacking in ibus-libpinyin.  For example, the latter cannot
conveniently input special symbols (many in the Chinese Ubuntu forum think
this a main reason not to use ibus-libpinyin).  Also, ibus-libpinyin will
treat a decimal point as a Chinese period, such as 19。04 (which should be
19.04）.   But most important AFAIC, ibus-pinyin uses a simple,
straightforward sqlite database structure that is very easy to comprehend.
How the table-lookup database is structured in ibus-libpinyin is
complicated and undocumented.

Many members of the Chinese Ubuntu forum have a very negative attitude
towards ibus-libpinyin partly because of the personality of its principal
developer Peng Wu.  They have always complained about being contemptuously
snobbed when they visited the ibus-libpinyin GitHub forum (many were told
to switch to Fedora).  I myself also could never get a straight answer from
Peng Wu.

I sincerely hope that your effort to make ibus-libpinyin stable ("stable"
in an absolute sense) will help attracting more users--ibus-libpinyin in
specific and Ubuntu in general.  I will definitely use it at least
occasionally to make sure that everything is OK.  Should Ubuntu
powers-that-be make an unfortunate decision and drop ibus-pinyin from its
archive, I will simply freeze my version of Ubuntu at 18.04, which is now
turning out to be exceptionally good.

On Fri, May 31, 2019 at 9:20 PM Gunnar Hjalmarsson <
1768...@bugs.launchpad.net> wrote:

> @Ping-Wu: ibus-pinyin will soon be removed from the archive.
>
> $ zcat /usr/share/doc/ibus-pinyin/NEWS.Debian.gz
> ibus-pinyin (1.5.0-5) unstable; urgency=medium
>
> Package ibus-pinyin is now deprecated; its upstream has stopped
> development
> for years in favour of new ibus-libpinyin. New ibus users should
> install
> ibus-libpinyin instead of this package. This package (ibus-pinyin)
> will be
> removed after Debian Buster (Debian 10) release.
>
>  -- Boyuan Yang   Tue, 18 Sep 2018 16:53:42 -0400
>
> Seems like it won't be present in the Ubuntu 20.04 archive.
>
> So let's focus 100% on ibus-libpinyin at this bug report.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1768166
>
> Title:
>   Random crashes
>
> Status in ibus-libpinyin package in Ubuntu:
>   Fix Released
> Status in libpinyin package in Ubuntu:
>   Fix Released
> Status in ibus-libpinyin source package in Bionic:
>   Fix Committed
> Status in libpinyin source package in Bionic:
>   Fix Committed
> Status in ibus-libpinyin source package in Cosmic:
>   Fix Committed
> Status in libpinyin source package in Cosmic:
>   Fix Committed
>
> Bug description:
>   [Impact]
>
>   ibus-libpinyin has proved to crash far too often. One or more files in
>   ~/.cache/ibus/libpinyin get corrupted somehow, and emptying that
>   directory allows the 

[Desktop-packages] [Bug 1776391] Re: Wifi Icon disappeared after upgrading to 4.15.0-23-generic

[Launchpad Bug Tracker]

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

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

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

Title:
  Wifi Icon disappeared after upgrading to 4.15.0-23-generic

Status in Ubuntu MATE:
  New
Status in linux package in Ubuntu:
  Confirmed
Status in network-manager-applet package in Ubuntu:
  New

Bug description:
  After updating to Ubuntu Mate 4.15.0-23-generic the wifi icon
  disappeared from the task bar. I have no problems connecting to
  networks or anything (by going to Network Connections in Control Panel
  ). I was using the 4.13.something -generic version before.

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

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

[Desktop-packages] [Bug 1660121] Re: LightDM can't use the user background on Mate

[Norbert]

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

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

Title:
  LightDM can't use the user background on Mate

Status in Ubuntu MATE:
  New
Status in lightdm package in Ubuntu:
  New

Bug description:
  Using Ubuntu Mate 16.10 (the issue appears too on 16.04 and 17.04
  alpha 2).

  On Mate, the LightDM Gtk Greeter can't use the user background. It
  works fine on other DEs like Xfce.

  From what I understand, LightDM and/or the Gkt greeter (not sure which
  one handles the background) gets the background path from Gsettings,
  so I assume it can't find the one from Mate, which stores it in
  "org.mate.background picture-filename".

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

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

[Desktop-packages] [Bug 1776391] Re: Wifi Icon disappeared after upgrading to 4.15.0-23-generic

[Ubuntu Kernel Bot]

** Package changed: linux-meta (Ubuntu) => linux (Ubuntu)

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

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

Title:
  Wifi Icon disappeared after upgrading to 4.15.0-23-generic

Status in Ubuntu MATE:
  New
Status in linux package in Ubuntu:
  Confirmed
Status in network-manager-applet package in Ubuntu:
  New

Bug description:
  After updating to Ubuntu Mate 4.15.0-23-generic the wifi icon
  disappeared from the task bar. I have no problems connecting to
  networks or anything (by going to Network Connections in Control Panel
  ). I was using the 4.13.something -generic version before.

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

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

[Desktop-packages] [Bug 1812310] Missing required logs.

[Ubuntu Kernel Bot]

This bug is missing log files that will aid in diagnosing the problem.
While running an Ubuntu kernel (not a mainline or third-party kernel)
please enter the following command in a terminal window:

apport-collect 1812310

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable
to run this command, please add a comment stating that fact and change
the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the
Ubuntu Kernel Team.

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

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

Title:
  No more sound on lenovo R61i booting MATE 16.04

Status in Ubuntu MATE:
  Invalid
Status in linux package in Ubuntu:
  Incomplete
Status in pulseaudio package in Ubuntu:
  New

Bug description:
  When booting MATE 16.04 on my lenovo R61i, I no longer have sound. I
  was able to listen to a YouTube video from the laptop when booting
  Linux Mint, but can no longer hear ANYTHING when booting MATE 16.04

  Thanks for your consideration,
  Abu Billy

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

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

[Desktop-packages] [Bug 1618723] Re: Unable to connect to wifi with Orca

[Norbert]

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

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

Title:
  Unable to connect to wifi with Orca

Status in Ubuntu MATE:
  New
Status in orca package in Ubuntu:
  New

Bug description:
  I don't think this is specifically related to the wifi applet whatever
  it's called, but I've only just got back into using Linux and I'm
  still getting to know what bit does what.

  I cannot find a way to connect to my WIFI with Orca. Logic would
  dictate that I can use CTRL+ALT+ESCAPE to get to the bottom panel, or
  use Orca Flat Review while in the top menu to get to a panel where I
  can tab to the network chooser, but this isn't doable.

  Am I missing something? Or is it impossible?

  Cheers.

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

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

[Desktop-packages] [Bug 1776391] Re: Wifi Icon disappeared after upgrading to 4.15.0-23-generic

[Norbert]

** Also affects: network-manager-applet (Ubuntu)
   Importance: Undecided
   Status: New

** Also affects: linux-meta (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  Wifi Icon disappeared after upgrading to 4.15.0-23-generic

Status in Ubuntu MATE:
  New
Status in linux package in Ubuntu:
  Confirmed
Status in network-manager-applet package in Ubuntu:
  New

Bug description:
  After updating to Ubuntu Mate 4.15.0-23-generic the wifi icon
  disappeared from the task bar. I have no problems connecting to
  networks or anything (by going to Network Connections in Control Panel
  ). I was using the 4.13.something -generic version before.

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

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

[Desktop-packages] [Bug 1797137] Re: HPLIP gui bug

[Norbert]

** Changed in: ubuntu-mate
   Status: New => Invalid

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

Title:
  HPLIP gui bug

Status in Ubuntu MATE:
  Invalid
Status in hplip package in Ubuntu:
  New

Bug description:
  Good afternoon

  After having installed the last version of HPLIP 3.18.9 with Ubuntu
  18.04 Mate, I found a bug concerning the page asking to select the
  printer connection type (WiFi, network or USB). If this page is called
  by using the HP icon and then by selecting add a device, it's
  impossible to reach the next page, by clicking on next. The page is
  coming back again and again.

  If I execute the instruction hp-setup in a terminal, the page asking
  to select the connection type is coming and then, a click on the Next
  button, is leading to the page where I can select the printer.

  So it seem that there is a bug concerning the HPLIP Gui.

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

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

[Desktop-packages] [Bug 1768920] Re: 2 WiFi Icons in the Panel after installation of 18.04

[Norbert]

** Also affects: network-manager-applet (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  2 WiFi Icons in the Panel after installation of 18.04

Status in Ubuntu MATE:
  Confirmed
Status in network-manager-applet package in Ubuntu:
  New

Bug description:
  After installing Ubuntu Mate 18.04, on the First login it shows 2 WiFi icons 
in the top panel.
  It goes away after the reboot though.

  My Laptop: Dell XPS 13 9370 Developer Edition, 16 GB RAM and 1 TB SSD

  Regards,
  Saurabh

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

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

[Desktop-packages] [Bug 1798233] Re: Orca's focus not restored correctly when pressing escape to close the brisk menu or the traditional menus

[Norbert]

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

** Changed in: ubuntu-mate
   Status: New => Invalid

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

Title:
  Orca's focus not restored correctly when pressing escape to close the
  brisk menu or the traditional menus

Status in Ubuntu MATE:
  Invalid
Status in orca package in Ubuntu:
  New

Bug description:
  Steps to Reproduce:
  On the latest daily builds of Ubuntu Mate 18.10, when using the alt+f1 menu, 
or the brisk menu at least in the familiar layout, pressing escape doesn't 
properly restore Orca's focus. The effect is that if you press escape and you 
land in a text field, Orca isn't able to track the text field until you do 
something that causes focus to change again, such as opening up a menu in an 
application and then pressing escape to close the menu again. This worked 
correctly in Ubuntu Mate 18.04.1.

  Steps to reproduce:
  1. On a recent daily build of Ubuntu Mate 18.10, log in to the system and 
press alt+super+s to turn on Orca.
  2. Press control+alt+D to set focus to the Desktop.
  3. Press alt+f1 to open the menu. Orca should say "menu."
  4. Press escape to close the menu.
  Actual result: Orca doesn't announce that you've returned to the desktop, and 
you must press the arrow key to confirm this.
  Expected result: Orca should announce the focus immediately when escape is 
pressed.
  I don't know whether this is a bug in Orca itself or some updates to Ubuntu 
Mate so that's why I'm posting this here.

  Thank you very much for your time and I look forward to any fixes you
  may be able to provide.

  Sincerely,

  Brandon Tyson

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

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

[Desktop-packages] [Bug 1812310] Re: No more sound on lenovo R61i booting MATE 16.04

[Ubuntu Kernel Bot]

** Package changed: linux-meta (Ubuntu) => linux (Ubuntu)

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

Title:
  No more sound on lenovo R61i booting MATE 16.04

Status in Ubuntu MATE:
  Invalid
Status in linux package in Ubuntu:
  New
Status in pulseaudio package in Ubuntu:
  New

Bug description:
  When booting MATE 16.04 on my lenovo R61i, I no longer have sound. I
  was able to listen to a YouTube video from the laptop when booting
  Linux Mint, but can no longer hear ANYTHING when booting MATE 16.04

  Thanks for your consideration,
  Abu Billy

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

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

[Desktop-packages] [Bug 1812310] Re: No more sound on lenovo R61i booting MATE 16.04

[Norbert]

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

** Also affects: linux-meta (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: ubuntu-mate
   Status: New => Invalid

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

Title:
  No more sound on lenovo R61i booting MATE 16.04

Status in Ubuntu MATE:
  Invalid
Status in linux package in Ubuntu:
  New
Status in pulseaudio package in Ubuntu:
  New

Bug description:
  When booting MATE 16.04 on my lenovo R61i, I no longer have sound. I
  was able to listen to a YouTube video from the laptop when booting
  Linux Mint, but can no longer hear ANYTHING when booting MATE 16.04

  Thanks for your consideration,
  Abu Billy

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

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

[Desktop-packages] [Bug 1812909] Re: disks application screws up when manipulating partitions

[Norbert]

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

** Changed in: ubuntu-mate
   Status: New => Invalid

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

Title:
  disks application screws up when manipulating partitions

Status in Ubuntu MATE:
  Invalid
Status in gnome-disk-utility package in Ubuntu:
  New

Bug description:
  Ubuntu MATE 18.04.1, normal installation.

  When I use the disks application to add, delete, resize or otherwise
  manipulate partitions, the graphical display of the disk screws up --
  partitions disappear, sizes are all wrong, it's very weird and
  difficult to explain. Upon reboot, the disk application does correctly
  display partitions again, and the changes have taken effect.

  Will try and take screenshots if nobody can reproduce, just let me
  know.

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

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

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

[Norbert]

** Changed in: ubuntu-mate
   Status: New => Invalid

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

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

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

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

  Expected results:
  * upgrade process ended without errors

  Actual results:
  * upgrade process ended with warning message:

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

  triggers looping, abandoned

  Workaround:

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

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

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

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

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

[Desktop-packages] [Bug 1824281] Re: Printer Won't Work...almost...got closer this time

[Norbert]

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

** Changed in: ubuntu-mate
   Status: New => Invalid

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

Title:
  Printer Won't Work...almost...got closer this time

Status in Ubuntu MATE:
  Invalid
Status in cups package in Ubuntu:
  New

Bug description:
  Page 1 ():
  {'cups_connection_failure': False}
  Page 2 ():
  {'local_server_exporting_printers': False}
  Page 3 ():
  {'cups_dest': ,
   'cups_instance': None,
   'cups_queue': 'Brother-MFC-8860DN',
   'cups_queue_listed': True}
  Page 4 ():
  {'cups_device_uri_scheme': 'usb',
   'cups_printer_dict': {'device-uri': 
'usb://Brother/MFC-8860DN?serial=000C8J645496',
 'printer-info': 'Brother MFC-8860DN',
 'printer-is-shared': True,
 'printer-location': 'ubuntu-mate',
 'printer-make-and-model': 'Brother MFC-8840D for CUPS',
 'printer-state': 3,
 'printer-state-message': '',
 'printer-state-reasons': ['none'],
 'printer-type': 8523796,
 'printer-uri-supported': 
'ipp://localhost/printers/Brother-MFC-8860DN'},
   'cups_printer_remote': False,
   'is_cups_class': False,
   'local_cups_queue_attributes': {'charset-configured': 'utf-8',
   'charset-supported': ['us-ascii', 'utf-8'],
   'color-supported': False,
   'compression-supported': ['none', 'gzip'],
   'copies-default': 1,
   'copies-supported': (1, ),
   'cups-version': '2.2.7',
   'device-uri': 
'usb://Brother/MFC-8860DN?serial=000C8J645496',
   'document-format-default': 
'application/octet-stream',
   'document-format-supported': 
['application/octet-stream',
 
'application/pdf',
 
'application/postscript',
 
'application/vnd.adobe-reader-postscript',
 
'application/vnd.cups-command',
 
'application/vnd.cups-pdf',
 
'application/vnd.cups-pdf-banner',
 
'application/vnd.cups-postscript',
 
'application/vnd.cups-raster',
 
'application/vnd.cups-raw',
 
'application/x-cshell',
 
'application/x-csource',
 
'application/x-perl',
 
'application/x-shell',
 'image/gif',
 'image/jpeg',
 'image/png',
 
'image/pwg-raster',
 'image/tiff',
 'image/urf',
 
'image/x-bitmap',
 
'image/x-photocd',
 
'image/x-portable-anymap',
 
'image/x-portable-bitmap',
 
'image/x-portable-graymap',
 
'image/x-portable-pixmap',
 
'image/x-sgi-rgb',
 
'image/x-sun-raster',
 
'image/x-xbitmap',
 
'image/x-xpixmap',
 
'image/x-xwindowdump',
 'text/css',
  

[Desktop-packages] [Bug 1797718] Re: Disks cannot create ext4 partition on 5 TB external USB drive

[Norbert]

** Changed in: ubuntu-mate
   Status: New => Invalid

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

Title:
  Disks cannot create ext4 partition on 5 TB external USB drive

Status in Ubuntu MATE:
  Invalid
Status in gnome-disk-utility package in Ubuntu:
  New

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-mate/+bug/1797718/+subscriptions

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

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

[Norbert]

** Changed in: ubuntu-mate
   Status: New => Incomplete

** Changed in: ubuntu-mate
   Status: Incomplete => Invalid

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

Title:
  [upstream] Libre Writer doesn't do duplex printing

Status in LibreOffice:
  Unknown
Status in Ubuntu MATE:
  Invalid
Status in libreoffice package in Ubuntu:
  New

Bug description:
  The Libre Writer print settings are set to two side printing, but
  program only prints single side. Is not HP Linux driver because both
  FireFox and Chrome print both sides.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: libreoffice-core 1:6.0.3-0ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
  Uname: Linux 4.15.0-23-generic x86_64
  NonfreeKernelModules: ufsd
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  CurrentDesktop: MATE
  Date: Fri Jun 29 22:17:38 2018
  ExecutablePath: /usr/lib/libreoffice/program/soffice.bin
  InstallationDate: Installed on 2018-06-15 (14 days ago)
  InstallationMedia: Ubuntu-MATE 18.04 LTS "Bionic Beaver" - Release amd64 
(20180426)
  SourcePackage: libreoffice
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1803032] Re: LibreOffice crashes kernel while trying to open 500+ new windows.

[Norbert]

** Changed in: ubuntu-mate
   Status: New => Invalid

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

Title:
  LibreOffice crashes kernel while trying to open 500+ new windows.

Status in Ubuntu MATE:
  Invalid
Status in libreoffice package in Ubuntu:
  New

Bug description:
  I am trying to combine 500+ .tiff files into a single .pdf file. I
  read that LibreOffice could do this. I started LibreOffice and
  selected the .tiff files. LibreOffice immediately tried to open 500+
  new windows. I tried to close LibreOffice but got an error window
  warning that LibreOffice is not responding. When I selected kill any
  way, nothing happened. Eventually the entire screen went black - the
  kernel had crashed. Had to reboot my machine.

  Still need to convert many tiff files to a single pdf file (preferably
  without using ghostscript like tiff2pdf).

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: libreoffice (not installed)
  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: MATE
  Date: Mon Nov 12 22:19:13 2018
  InstallationDate: Installed on 2018-10-25 (19 days ago)
  InstallationMedia: Ubuntu-MATE 18.04 LTS "Bionic Beaver" - Release amd64 
(20180426)
  SourcePackage: libreoffice
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1810551] Re: LibreOffice Writer does not print page numbers.

[Norbert]

** Changed in: ubuntu-mate
   Status: New => Invalid

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

Title:
  LibreOffice Writer does not print page numbers.

Status in Ubuntu MATE:
  Invalid
Status in libreoffice package in Ubuntu:
  Incomplete

Bug description:
  When I select Format->Page I see that the page numbering is set to 1,
  2,... but no page numbers are actually printed.

  (bug reported over 5-years ago and not fixed). LibreOffice Writer
  still does not do duplex printing. Workaround - export to PDF and then
  use any other program to print duplex. They all work except
  LibreOffice Writer.

  Robert Pearson

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: libreoffice (not installed)
  ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17
  Uname: Linux 4.18.0-13-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13.1
  Architecture: amd64
  CurrentDesktop: MATE
  Date: Fri Jan  4 14:21:31 2019
  InstallationDate: Installed on 2018-12-16 (19 days ago)
  InstallationMedia: Ubuntu-MATE 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.2)
  SourcePackage: libreoffice
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1831203] Re: flash overloads cpu, kills performance

[Paul White]

** Package changed: ubuntu => flashplugin-nonfree (Ubuntu)

** Tags added: xenial

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

Title:
  flash overloads cpu, kills performance

Status in flashplugin-nonfree package in Ubuntu:
  New

Bug description:
  Description:  Ubuntu 16.04.6 LTS
  Release:  16.04

  # apt-cache policy flashplugin-installer 
  flashplugin-installer:
Installed: 32.0.0.192ubuntu0.16.04.1
Candidate: 32.0.0.192ubuntu0.16.04.1
Version table:
   *** 32.0.0.192ubuntu0.16.04.1 500
  500 http://us.archive.ubuntu.com/ubuntu xenial-updates/multiverse 
amd64 Packages
  500 http://security.ubuntu.com/ubuntu xenial-security/multiverse 
amd64 Packages
  100 /var/lib/dpkg/status
   11.2.202.616ubuntu1 500
  500 http://us.archive.ubuntu.com/ubuntu xenial/multiverse amd64 
Packages

  System freezes for ten seconds and/or much longer.
  I would say "See attached screenshot"... but that doesn't appear to be an 
option here.

  Note CPU usage by plugin.
  Also please note virtual memory usage by firefox, I don't know if it's 
relevant.  I have 8GB RAM. I frequently have a dozen windows and 50+ tabs open. 
 Some windows have many more tabs than others.

  I have to wonder if this isn't a kernel bug? Or a top bug? How can a
  system use more than 100% of the CPU?  Is it trying to somehow express
  the fact that I have 8 cores and 117% means something?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/flashplugin-nonfree/+bug/1831203/+subscriptions

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

[Desktop-packages] [Bug 1831203] [NEW] flash overloads cpu, kills performance

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

Description:Ubuntu 16.04.6 LTS
Release:16.04

# apt-cache policy flashplugin-installer 
flashplugin-installer:
  Installed: 32.0.0.192ubuntu0.16.04.1
  Candidate: 32.0.0.192ubuntu0.16.04.1
  Version table:
 *** 32.0.0.192ubuntu0.16.04.1 500
500 http://us.archive.ubuntu.com/ubuntu xenial-updates/multiverse amd64 
Packages
500 http://security.ubuntu.com/ubuntu xenial-security/multiverse amd64 
Packages
100 /var/lib/dpkg/status
 11.2.202.616ubuntu1 500
500 http://us.archive.ubuntu.com/ubuntu xenial/multiverse amd64 Packages

System freezes for ten seconds and/or much longer.
I would say "See attached screenshot"... but that doesn't appear to be an 
option here.

Note CPU usage by plugin.
Also please note virtual memory usage by firefox, I don't know if it's 
relevant.  I have 8GB RAM. I frequently have a dozen windows and 50+ tabs open. 
 Some windows have many more tabs than others.

I have to wonder if this isn't a kernel bug? Or a top bug? How can a
system use more than 100% of the CPU?  Is it trying to somehow express
the fact that I have 8 cores and 117% means something?

** Affects: flashplugin-nonfree (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: bot-comment
-- 
flash overloads cpu, kills performance
https://bugs.launchpad.net/bugs/1831203
You received this bug notification because you are a member of Desktop 
Packages, which is subscribed to flashplugin-nonfree in Ubuntu.

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

[Desktop-packages] [Bug 1768166] Re: Random crashes

[Gunnar Hjalmarsson]

@Ping-Wu: ibus-pinyin will soon be removed from the archive.

$ zcat /usr/share/doc/ibus-pinyin/NEWS.Debian.gz
ibus-pinyin (1.5.0-5) unstable; urgency=medium

Package ibus-pinyin is now deprecated; its upstream has stopped development
for years in favour of new ibus-libpinyin. New ibus users should install
ibus-libpinyin instead of this package. This package (ibus-pinyin) will be
removed after Debian Buster (Debian 10) release.

 -- Boyuan Yang   Tue, 18 Sep 2018 16:53:42 -0400

Seems like it won't be present in the Ubuntu 20.04 archive.

So let's focus 100% on ibus-libpinyin at this bug report.

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

Title:
  Random crashes

Status in ibus-libpinyin package in Ubuntu:
  Fix Released
Status in libpinyin package in Ubuntu:
  Fix Released
Status in ibus-libpinyin source package in Bionic:
  Fix Committed
Status in libpinyin source package in Bionic:
  Fix Committed
Status in ibus-libpinyin source package in Cosmic:
  Fix Committed
Status in libpinyin source package in Cosmic:
  Fix Committed

Bug description:
  [Impact]

  ibus-libpinyin has proved to crash far too often. One or more files in
  ~/.cache/ibus/libpinyin get corrupted somehow, and emptying that
  directory allows the user to keep using ibus-libpinyin.

  In disco (and eoan) ibus-libpinyin 1.11.0 and libpinyin 2.2.2 are
  present, and the number of crashes has been reduced significantly:

  https://errors.ubuntu.com/?package=ibus-libpinyin=month

  Upstream ChangeLog ibus-libpinyin:
  --
  version 1.11.0
  * fixes keypad decimal
  * fixes emoji candidates
  * support configurable opencc config

  version 1.10.92
  * fixes Enter handling

  version 1.10.91
  * support ime.register_trigger in lua extension
  * support predicted candidates
  * support emoji input

  version 1.10.0
  * bug fixes

  version 1.9.91
  * migrate to use GSettings
  * fixes lyx short cut issue

  version 1.9.3
  * translate input method name in ibus menu

  Upstream ChangeLog libpinyin:
  -
  version 2.2.2
  * minor fixes

  version 2.2.1
  * fixes predicted candidates

  version 2.2.0
  * bug fixes

  The proposal is to backport the disco versions of those packages to
  bionic and cosmic in an attempt to prevent crashes. Proposed uploads
  are available in this PPA:

  https://launchpad.net/~gunnarhj/+archive/ubuntu/ibus-libpinyin

  [Test Case]

  * Install from {bionic,cosmic}-proposed:
    - libpinyin13
    - libpinyin-data
    - ibus-libpinyin

  * Use "Intelligent Pinyin" for typing and confirm that no new issues
    show up when doing so.

  (This is apparently not a confirmation that the upload really fixes
  the bug. To compensate for that, we will await testing of the
  -proposed packages by a few Chinese users before considering the
  uploads verified.)

  Reverse dependencies
  
  Besides ibus-libpinyin, also fcitx-libpinyin and ibus-libzhuyin depend on 
packages belonging to the libpinyin source package. So additional test measures 
are:

  * Install fcitx-libpinyin and ibus-libzhuyin.

  * Use both those tools for typing Chinese, and confirm that you don't
    observe any adverse effects of the libpinyin upgrade.

  [Regression Potential]

  The changes are mostly bug fixes, so the regression risk should be
  limited. Also consider that the starting point is a rather unstable
  functionality.

  NOTE TO SRU TEAM: Please let the SRU age for longer than 7 days to get
  as much testing as possible. There do not seem to be too many risky
  changes carried, but such jumps in upstream versions always carry some
  regression-risk.

  [Original description]

  I have experienced random ibus-libpinyin crashes in bionic.  I cannot
  reproduce it, but it occurred at least a few times, even after the
  official bionic release.  Same crashes were also reported in the
  Ubuntu Chinese forum.

  Currently, the workaround is to delete the ~/.cache/ibus/libpinyin
  folder.

  I talked to Peng Wu, ibus-libpinyin's creator and main maintainer, he
  suggested that we update the version of ibus-libpinyin to 1.10.

  Can we give this update a trial?

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

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

[Desktop-packages] [Bug 1825717] Re: hplip issue during hp-setup - stuck at plugin install

[Mauro Gaspari]

Additional Feedback.

I did a fresh install of ubuntu-budgie 19.04
1. installed hplip from repos (version 3.19.1)
2. ran hp-setup -i 
3. went through the steps
4. install completed including plugin, can print and scan with no issue

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

Title:
  hplip issue during hp-setup - stuck at plugin install

Status in hplip package in Ubuntu:
  Confirmed

Bug description:
  Fresh install of Kubuntu 19.04 
  Installed hplip from repositories, available version is 3.19.1+dfsg0-1

  When I start setup with hp-setup, this happens:
  1. I am asked connection type. I select network ethernet
  2. My printer is detected. I select it and hit next
  3. I am told about the proprietary plugin to download. I confirm, accept 
download. I enter my user's password. I get a confirmation that the plugin is 
correctly Installed.
  4. On next screen, I get a warning and cannot continue installation. I am 
told this printer needs a proprietary plugin to work correctly. After this I am 
stuck in a loop between points 3 and 4. I also tried to start hp-setup from 
super user on command line. but no way around this issue.

  What I did next, I manually downloaded hplip-3.19.3.run from HP
  website. Removed version of hplip installed from repositories.
  Installed from manually downloaded package, followed the very same
  steps. Everything worked fine and printer is installed successfully.

  I hope this information is useful.

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

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