[Desktop-packages] [Bug 1728988] Re: poppler crashes on this file

2018-11-16 Thread madbiologist
This file no longer crashes evince/poppler on Ubuntu 18.04 "Bionic
Beaver" 64 bit with libcairo2 1.15.10-2

** Changed in: cairo (Ubuntu)
   Status: In Progress => Fix Released

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

Title:
  poppler crashes on this file

Status in cairo package in Ubuntu:
  Fix Released
Status in poppler package in Ubuntu:
  Invalid

Bug description:
  When opening the PDF file available at:
  https://mega.nz/#!QUlxRabb!CkbkbKanfjFCO6OaKCoFq2_yHoIWChV-ruc3PHB87E8

  evince/pdftocairo are core dumping.

  As far as I can tell it's because the underlying lib (cairo/poppler)
  has a bug.

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

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


[Desktop-packages] [Bug 1803807] [NEW] Lock screen doesn't work in 18.10

2018-11-16 Thread Andras Veto
Public bug reported:

Super+l needs to be pressed twice to lock the screen. Pressing the
shortcut only once results in strange behavior. Locking the screen in
general is buggy (e.g. dock is visible when screen is locked, once
screen is unlocked the dock disappears even after pressing activities).
These issues were not present in 18.04. I am on a fresh install of 18.10
with gnome.

See also:
https://askubuntu.com/questions/1082761/automatic-locking-screen-doesnt-work-in-ubuntu-18-10
https://askubuntu.com/questions/1085471/unable-to-login-again-after-screen-lock-also-gnome-hangs-if-able-to-login
https://askubuntu.com/questions/1090091/ubuntu-18-10-screen-lock-options-grayed-out

1)
Description:Ubuntu 18.10
Release:18.10
2)
gdm3:
  Installed: 3.30.1-1ubuntu5
  Candidate: 3.30.1-1ubuntu5
  Version table:
 *** 3.30.1-1ubuntu5 500
500 http://us.archive.ubuntu.com/ubuntu cosmic/main amd64 Packages
100 /var/lib/dpkg/status
gnome-shell:
  Installed: 3.30.1-2ubuntu1
  Candidate: 3.30.1-2ubuntu1
  Version table:
 *** 3.30.1-2ubuntu1 500
500 http://us.archive.ubuntu.com/ubuntu cosmic/main amd64 Packages
100 /var/lib/dpkg/status
3)
The lock screen should maintain the functionality present in 18.04. Pressing 
the shortcut once should lock the screen, no ui elements should remain on the 
locked screen, locking and unlocking the screen should not result in the dock 
disappearing.
4)
The lock screen no longer works. It is possible to view and interact with ui 
elements after pressing the lock shortcut. It is possible to view the dock when 
the screen is locked.

ProblemType: Bug
DistroRelease: Ubuntu 18.10
Package: gdm3 3.30.1-1ubuntu5
ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12
Uname: Linux 4.18.0-11-generic x86_64
ApportVersion: 2.20.10-0ubuntu13.1
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Sat Nov 17 00:41:33 2018
ExecutablePath: /usr/lib/gdm3/gdm-x-session
InstallationDate: Installed on 2018-11-16 (1 days ago)
InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3)
ProcEnviron:
 SHELL=/usr/bin/zsh
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 XDG_RUNTIME_DIR=
SourcePackage: gdm3
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug cosmic

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

Title:
  Lock screen doesn't work in 18.10

Status in gdm3 package in Ubuntu:
  New

Bug description:
  Super+l needs to be pressed twice to lock the screen. Pressing the
  shortcut only once results in strange behavior. Locking the screen in
  general is buggy (e.g. dock is visible when screen is locked, once
  screen is unlocked the dock disappears even after pressing
  activities). These issues were not present in 18.04. I am on a fresh
  install of 18.10 with gnome.

  See also:
  
https://askubuntu.com/questions/1082761/automatic-locking-screen-doesnt-work-in-ubuntu-18-10
  
https://askubuntu.com/questions/1085471/unable-to-login-again-after-screen-lock-also-gnome-hangs-if-able-to-login
  
https://askubuntu.com/questions/1090091/ubuntu-18-10-screen-lock-options-grayed-out

  1)
  Description:  Ubuntu 18.10
  Release:  18.10
  2)
  gdm3:
Installed: 3.30.1-1ubuntu5
Candidate: 3.30.1-1ubuntu5
Version table:
   *** 3.30.1-1ubuntu5 500
  500 http://us.archive.ubuntu.com/ubuntu cosmic/main amd64 Packages
  100 /var/lib/dpkg/status
  gnome-shell:
Installed: 3.30.1-2ubuntu1
Candidate: 3.30.1-2ubuntu1
Version table:
   *** 3.30.1-2ubuntu1 500
  500 http://us.archive.ubuntu.com/ubuntu cosmic/main amd64 Packages
  100 /var/lib/dpkg/status
  3)
  The lock screen should maintain the functionality present in 18.04. Pressing 
the shortcut once should lock the screen, no ui elements should remain on the 
locked screen, locking and unlocking the screen should not result in the dock 
disappearing.
  4)
  The lock screen no longer works. It is possible to view and interact with ui 
elements after pressing the lock shortcut. It is possible to view the dock when 
the screen is locked.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: gdm3 3.30.1-1ubuntu5
  ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12
  Uname: Linux 4.18.0-11-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13.1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Nov 17 00:41:33 2018
  ExecutablePath: /usr/lib/gdm3/gdm-x-session
  InstallationDate: Installed on 2018-11-16 (1 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  ProcEnviron:
   SHELL=/usr/bin/zsh
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   XDG_RUNTIME_DIR=
  SourcePackage: gdm3
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications 

[Desktop-packages] [Bug 1799001] Re: Theming does not work on LXQt

2018-11-16 Thread Chris Guiver
i'm running a QA-test on daily image; the icons or theme on the daily
image appears like that I attached in my last (#7) comment but "base
database" greyed out (no document etc)

** Attachment added: "today's qa-test 'live' image x86 t43"
   
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1799001/+attachment/5213582/+files/libreoffice_main_screen_2018-11-17.jpg

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

Title:
  Theming does not work on LXQt

Status in libreoffice package in Ubuntu:
  Fix Released
Status in libreoffice source package in Cosmic:
  Fix Committed

Bug description:
  [Impact]

  Without this change, LibreOffice does not correctly use the Breeze
  theme, which is needed for consistency with the rest of the Lubuntu,
  LXQt-based desktop. At times, it is even hard to use because of the
  inconsistent theming which can hide buttons at times.

  [Test Case]

  Update to the version of LibreOffice with this patch and open it on a
  Lubuntu 18.10 installation. It should use the Breeze theming rather
  than the stock GTK theming on startup.

  [Regression Potential]

  Little to none. If for some reason the criteria that is used to check
  for the LXQt desktop no longer works, which is unlikely in a stable
  release, this will no longer work.

  [Other Info]

  I submitted these upstream (as my first patches \o/):
  https://gerrit.libreoffice.org/61641
  https://gerrit.libreoffice.org/61751

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

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


[Desktop-packages] [Bug 1784485] Re: [ZenBook S UX391UA, Realtek ALC294, Mic, Internal] No sound at all

2018-11-16 Thread Thusitha Chandrapala
I have the issue as well. I have a dual boot system with following. 
Zenbook UX490UAR
Ubuntu 18.04.1
Windows 10

I think this is due to windows not properly shutting down and holding on
to a hardware device, although not sure how. Managed to resolve by a
full shutdown. i.e. go to shutdown on the windows start menu and hold
shift while pressing restart. A screen will appear where you can select
to shutdown.

After the restart and logging into ubuntu, sound works . 
For the volume control related bug, there was a guide here : 
https://askubuntu.com/questions/906303/volume-control-on-asus-zenbook-3

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

Title:
  [ZenBook S UX391UA, Realtek ALC294, Mic, Internal] No sound at all

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  Internal speaker - not sound at all
  Cable Headphonse - realy quiet disorted sound
  Bluetooth headphones - sound works fine

  On Windows 10 everything works fine.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  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
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  pmichalski   7964 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Jul 30 22:32:10 2018
  InstallationDate: Installed on 2018-07-17 (12 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=pl_PL.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaRecordingTest: ALSA recording test through plughw:PCH failed
  Symptom_Card: Wbudowany dźwięk - HDA Intel PCH
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gdm2988 F pulseaudio
pmichalski   7964 F pulseaudio
  Symptom_Jack: Mic, Internal
  Symptom_Type: No sound at all
  Title: [ZenBook S UX391UA, Realtek ALC294, Mic, Internal] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/18/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX391UA.204
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX391UA
  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.:bvrUX391UA.204:bd05/18/2018:svnASUSTeKCOMPUTERINC.:pnZenBookSUX391UA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX391UA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: ZenBook S
  dmi.product.name: ZenBook S UX391UA
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

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

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


[Desktop-packages] [Bug 1803520] Re: Broken pipe errors on firefox close

2018-11-16 Thread lotuspsychje
@ Oliver #3 no firefox works like a charm on this system
i cannot see breaking or unexpected behaviour GUI
only the syslog errors

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

Title:
  Broken pipe errors on firefox close

Status in firefox package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu desktop 18.04.1 up to date with kernel 4.15.0-39-generic @
  15/11/2018

  every time firefox is closed, syslog spits out gnome-shell broken pipe
  errors like these:

  Nov 15 11:02:01 RooTBooK org.gnome.Shell.desktop[16761]: [Parent 15445, 
Gecko_IOThread] WARNING: pipe error: Gebroken pijp: file 
/build/firefox-4VfQCB/firefox-63.0+build2/ipc/chromium/src/chrome/common/ipc_channel_posix.cc,
 line 729
  Nov 15 11:02:29 RooTBooK org.gnome.Shell.desktop[16761]: [Parent 15445, 
Gecko_IOThread] WARNING: pipe error (101): Verbinding is weggevallen: file 
/build/firefox-4VfQCB/firefox-63.0+build2/ipc/chromium/src/chrome/common/ipc_channel_posix.cc,
 line 356
  Nov 15 11:02:29 RooTBooK org.gnome.Shell.desktop[16761]: [Parent 15445, 
Gecko_IOThread] WARNING: pipe error (58): Verbinding is weggevallen: file 
/build/firefox-4VfQCB/firefox-63.0+build2/ipc/chromium/src/chrome/common/ipc_channel_posix.cc,
 line 356
  Nov 15 11:02:29 RooTBooK org.gnome.Shell.desktop[16761]: IPDL protocol error: 
Handler returned error code!
  Nov 15 11:02:29 RooTBooK org.gnome.Shell.desktop[16761]: ###!!! 
[Parent][DispatchAsyncMessage] Error: PLayerTransaction::Msg_ReleaseLayer 
Processing error: message was deserialized, but the handler returned false 
(indicating failure)
  Nov 15 11:03:09 RooTBooK firefox[1211]: Theme parsing error: :1:34: 
Expected ')' in color definition
  Nov 15 11:03:09 RooTBooK firefox[1211]: Theme parsing error: :1:77: 
Expected ')' in color definition

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: firefox 63.0+build2-0ubuntu0.18.04.2
  ProcVersionSignature: Ubuntu 4.15.0-39.42-generic 4.15.18
  Uname: Linux 4.15.0-39-generic x86_64
  AddonCompatCheckDisabled: False
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  lotuspsychje  16784 F pulseaudio
  BuildID: 20181023214826
  Channel: Unavailable
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Nov 15 11:05:06 2018
  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 2018-08-17 (90 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  IpRoute:
   default via 192.168.1.1 dev wlp2s0 proto dhcp metric 600 
   169.254.0.0/16 dev wlp2s0 scope link metric 1000 
   192.168.1.0/24 dev wlp2s0 proto kernel scope link src 192.168.1.2 metric 600 
   192.168.250.0/24 dev anbox0 proto kernel scope link src 192.168.250.1
  Locales: extensions.sqlite corrupt or missing
  PrefSources: prefs.js
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=nl_BE.UTF-8
   SHELL=/bin/bash
  Profiles: Profile0 (Default) - LastVersion=63.0/20181023214826 (In use)
  RunningIncompatibleAddons: False
  SourcePackage: firefox
  Themes: extensions.sqlite corrupt or missing
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/14/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 7.009
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: N7x0WU
  dmi.board.vendor: Notebook
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: No Enclosure
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr7.009:bd05/14/2018:svnNotebook:pnN7x0WU:pvrNotApplicable:rvnNotebook:rnN7x0WU:rvrNotApplicable:cvnNoEnclosure:ct10:cvrN/A:
  dmi.product.family: Not Applicable
  dmi.product.name: N7x0WU
  dmi.product.version: Not Applicable
  dmi.sys.vendor: Notebook

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

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


[Desktop-packages] [Bug 1792822] Re: Dual monitor not working in 18.04(.1) on a dual-radeon-GPU system

2018-11-16 Thread 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/1792822

Title:
  Dual monitor not working in 18.04(.1) on a dual-radeon-GPU system

Status in mutter package in Ubuntu:
  Expired

Bug description:
  Dual monitor setup works fine in 16.04 LTS. Not anymore in 18.04(.1).
  This renders 18.04 useless. Till this is solved will have to stick
  with 16.04. i.e. this is a pretty critical bug!

  
  After a fresh install from DVD first got a freeze on login screen (live CD 
will run ubuntu though!). This could be solved by switching to lightdm display 
manager. (Boo! for GDM that cannot even show a login screen without freezing 
the system)

  But one issue remains: the dual monitor setup will not work in 18.04.

  I can see the mouse move to the second monitor. I can drag windows
  there (and lose sight of them). I can see the mouse cursor change to
  click a link. But otherwise there is a completely black screen, or
  dots / colored fields, but nothing even resembling a program.

  MB: Gigabyte GA-A75M-UD2H
  Monitor that works fine: ASUS on Radeon HD 6550D
  monitor that only shows mouse cursor: benq on Radeon HD 4870 (onboard on the 
gigabyte motherboard)

  Note: dual monitor setup did not work with other upgrades after 16.04. I 
hoped this would be solved with the next LTS update. Not so, to great 
disappointment!
  Ubuntu really fails if with new major updates it makes systems fall down. 
This kind of thing should work FLAWLESS out of the box! How would anyone move 
to Ubuntu when this kind of thing does not work? Windows is a drama, but at 
least it has the mere basics working!

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3.1
  ProcVersionSignature: Ubuntu 4.4.0-135.161-generic 4.4.140
  Uname: Linux 4.4.0-135-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Sun Sep 16 23:09:31 2018
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox, 5.0.40, 4.4.0-133-generic, x86_64: installed
   virtualbox, 5.0.40, 4.4.0-134-generic, x86_64: installed
   virtualbox, 5.0.40, 4.4.0-135-generic, x86_64: installed
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] BeaverCreek [Radeon HD 6550D] 
[1002:9640] (prog-if 00 [VGA controller])
 Subsystem: Gigabyte Technology Co., Ltd BeaverCreek [Radeon HD 6550D] 
[1458:d000]
   Advanced Micro Devices, Inc. [AMD/ATI] RV770 [Radeon HD 4870] [1002:9440] 
(prog-if 00 [VGA controller])
 Subsystem: PC Partner Limited / Sapphire Technology RV770 [Radeon HD 4870] 
[174b:0851]
  InstallationDate: Installed on 2016-10-02 (714 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  MachineType: Gigabyte Technology Co., Ltd. GA-A75M-UD2H
  ProcEnviron:
   LANGUAGE=nl_NL
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=nl_NL.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-135-generic 
root=UUID=a5b3b47d-aa17-4b49-ba9a-eeaefc2556d6 ro quiet splash
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/17/2011
  dmi.bios.vendor: Award Software International, Inc.
  dmi.bios.version: F6c
  dmi.board.name: GA-A75M-UD2H
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrF6c:bd11/17/2011:svnGigabyteTechnologyCo.,Ltd.:pnGA-A75M-UD2H:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-A75M-UD2H:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
  dmi.product.name: GA-A75M-UD2H
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.91-2~16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~16.04.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~16.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.8
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1.2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: 

[Desktop-packages] [Bug 1778011] Re: SRU: PRIME Power Saving mode draws too much power

2018-11-16 Thread Vitaliy Kraynov
My gpu-manager.log (Intel selected)

** Attachment added: "gpu-manager.log"
   
https://bugs.launchpad.net/ubuntu/+source/nvidia-prime/+bug/1778011/+attachment/5213565/+files/gpu-manager.log

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

Title:
  SRU: PRIME Power Saving mode draws too much power

Status in HWE Next:
  New
Status in gdm3 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-390 package in Ubuntu:
  Fix Released
Status in nvidia-prime package in Ubuntu:
  Fix Released
Status in nvidia-settings package in Ubuntu:
  Fix Released
Status in sddm package in Ubuntu:
  Confirmed
Status in ubuntu-drivers-common package in Ubuntu:
  Fix Released
Status in gdm3 source package in Bionic:
  Fix Released
Status in nvidia-graphics-drivers-390 source package in Bionic:
  Fix Released
Status in nvidia-prime source package in Bionic:
  Fix Released
Status in nvidia-settings source package in Bionic:
  Fix Released
Status in sddm source package in Bionic:
  Confirmed
Status in ubuntu-drivers-common source package in Bionic:
  Fix Released

Bug description:
  SRU Request:

  [Impact]
  Relying on the nouveau driver and on the vga switcheroo (to get around a 
change in systemd LP: #1777099) caused increased power consumption, and slowed 
down the switching process.

  Furthermore, if the main X/Xwayland session was started by Gdm when
  the nvidia driver was loaded, the session will keep the nvidia module
  loaded, and prevent the system from switching off the dGPU. Also, the
  nouveau driver will be loaded, if nvidia is not, and this can cause
  problems to unsupported NVIDIA GPUs.

  The solution involves the following changes:

  1) Solving the problem in systemd (LP: #1777099)

  2) Adding code in gpu-manager and in nvidia-prime to unload the nvidia
  modules, and to allow the PCI device to sleep.

  3) Making a slight change to the current patch in Gdm, used to call
  the PRIME scripts before and after a Gdm session (so that gpu-manager
  gets actually called on log out)

  4) Adding code in gpu-manager to kill the main X/Xwayland session on
  log out, if the session is preventing us from unloading the nvidia
  driver. A new X/Xwayland session will be created after unload the
  module.

  5) Removing the systemd service that loads nouveau from the nvidia
  packages.

  [Test Case]
  1) Enable the -proposed repository, and install the new 
"ubuntu-drivers-common", nvidia drivers, nvidia-prime, and gdm3 *

  2) Make sure the nvidia packages are installed, and enable performance mode 
(if it is already enabled, call "sudo prime-select intel" first):
  sudo prime-select nvidia

  3) Restart your computer and attach your /var/log/gpu-manager.log. see
  if the system boots correctly. If unsure, please attach your /var/log
  /gpu-manager.log and /var/log/Xorg.0.log

  4) Select power saving mode:
  sudo prime-select intel

  5) Log out and log back in

  6) Check if the nvidia driver is still loaded:
  lsmod | grep nvidia

  [Regression Potential]
  Low, as hybrid graphics support does not work correctly, and the changes only 
affect this use case.

  _
  * Steps to test the updates:

  1) Enable the bionic-proposed repositories

  2) Create /etc/apt/preferences.d/proposed-updates with the following
  content:

  Package: *
  Pin: release a=bionic-proposed
  Pin-Priority: 400

  3) Update the list of packages:

  sudo apt-get update

  4) Install the packages from -proposed using the following command:

  sudo apt install nvidia-driver-390/bionic-proposed gdm3/bionic-
  proposed ubuntu-drivers-common/bionic-proposed nvidia-prime/bionic-
  proposed nvidia-settings/bionic-proposed libnvidia-gl-390/bionic-
  proposed libnvidia-compute-390/bionic-proposed libnvidia-decode-390
  /bionic-proposed libnvidia-encode-390/bionic-proposed libnvidia-
  ifr1-390/bionic-proposed libnvidia-fbc1-390/bionic-proposed

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1778011/+subscriptions

-- 
Mailing list: https://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 1797513] Re: package libreoffice-sdbc-firebird 1:5.3.4-0ubuntu0.16.04.1~lo0.1 failed to install/upgrade: new libreoffice-sdbc-firebird package pre-installation script subpr

2018-11-16 Thread ChrisR
Many thanks.

This has fixed the problem.

(I am attempting to extract a lot of reluctant uses from Microsoft and the
last remaining issue not surprisingly is the Access database.)



On Fri, Nov 16, 2018 at 9:50 PM Olivier Tilloy 
wrote:

> It appears you have an old version of libreoffice-sdbc-firebird
> installed (1:5.3.4-0ubuntu0.16.04.1~lo0.1, targetting xenial, from the
> LO fresh PPA).
>
> The relevant error message is:
>
> dpkg-maintscript-helper: error: file
> '/usr/share/doc/libreoffice-sdbc-firebird' not owned by package
> 'libreoffice-sdbc-firebird:amd64'
> dpkg-maintscript-helper: error: directory
> '/usr/share/doc/libreoffice-sdbc-firebird' contains files not owned by
> package libreoffice-sdbc-firebird:amd64, cannot switch to symlink
>
> Can you try the following, and let us know whether that resolves the
> issue?
>
> sudo apt purge libreoffice-sdbc-firebird
> sudo apt install libreoffice-sdbc-firebird
>
> ** Changed in: libreoffice (Ubuntu)
>Status: New => Incomplete
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1797513
>
> Title:
>   package libreoffice-sdbc-firebird 1:5.3.4-0ubuntu0.16.04.1~lo0.1
>   failed to install/upgrade: new libreoffice-sdbc-firebird package pre-
>   installation script subprocess returned error exit status 1
>
> Status in libreoffice package in Ubuntu:
>   Incomplete
>
> Bug description:
>   Keep reoccuring
>
>   ProblemType: Package
>   DistroRelease: Ubuntu 18.04
>   Package: libreoffice-sdbc-firebird 1:5.3.4-0ubuntu0.16.04.1~lo0.1
>   ProcVersionSignature: Ubuntu 4.15.0-38.41-generic 4.15.18
>   Uname: Linux 4.15.0-38-generic x86_64
>   ApportVersion: 2.20.9-0ubuntu7.4
>   Architecture: amd64
>   Date: Fri Oct 12 12:19:48 2018
>   Dependencies:
>
>   ErrorMessage: new libreoffice-sdbc-firebird package pre-installation
> script subprocess returned error exit status 1
>   InstallationDate: Installed on 2015-08-01 (1167 days ago)
>   InstallationMedia: Ubuntu-Server 15.04 "Vivid Vervet" - Release amd64
> (20150422)
>   PackageArchitecture: all
>   Python3Details: /usr/bin/python3.6, Python 3.6.6, python3-minimal,
> 3.6.5-3ubuntu1
>   PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal,
> 2.7.15~rc1-1
>   RelatedPackageVersions:
>dpkg 1.19.0.5ubuntu2
>apt  1.6.5
>   SourcePackage: libreoffice
>   Title: package libreoffice-sdbc-firebird 1:5.3.4-0ubuntu0.16.04.1~lo0.1
> failed to install/upgrade: new libreoffice-sdbc-firebird package
> pre-installation script subprocess returned error exit status 1
>   UpgradeStatus: No upgrade log present (probably fresh install)
>
> To manage notifications about this bug go to:
>
> https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1797513/+subscriptions
>


-- 
Chris Reilly +61-42-828-0001
m...@chrisreilly.net
P.O.Box 1623
North Sydney
AUSTRALIA
+61-2-99 55

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

Title:
  package libreoffice-sdbc-firebird 1:5.3.4-0ubuntu0.16.04.1~lo0.1
  failed to install/upgrade: new libreoffice-sdbc-firebird package pre-
  installation script subprocess returned error exit status 1

Status in libreoffice package in Ubuntu:
  Incomplete

Bug description:
  Keep reoccuring

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: libreoffice-sdbc-firebird 1:5.3.4-0ubuntu0.16.04.1~lo0.1
  ProcVersionSignature: Ubuntu 4.15.0-38.41-generic 4.15.18
  Uname: Linux 4.15.0-38-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.4
  Architecture: amd64
  Date: Fri Oct 12 12:19:48 2018
  Dependencies:
   
  ErrorMessage: new libreoffice-sdbc-firebird package pre-installation script 
subprocess returned error exit status 1
  InstallationDate: Installed on 2015-08-01 (1167 days ago)
  InstallationMedia: Ubuntu-Server 15.04 "Vivid Vervet" - Release amd64 
(20150422)
  PackageArchitecture: all
  Python3Details: /usr/bin/python3.6, Python 3.6.6, python3-minimal, 
3.6.5-3ubuntu1
  PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu2
   apt  1.6.5
  SourcePackage: libreoffice
  Title: package libreoffice-sdbc-firebird 1:5.3.4-0ubuntu0.16.04.1~lo0.1 
failed to install/upgrade: new libreoffice-sdbc-firebird package 
pre-installation script subprocess returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1778011] Re: SRU: PRIME Power Saving mode draws too much power

2018-11-16 Thread Vitaliy Kraynov
My laptop is MSI GE60 0NC
CPU: Intel i5-3210M, GPU: NVIDIA GeForce GTX 660M
Running Kubuntu 18.10

As in comment 
https://bugs.launchpad.net/ubuntu/+source/nvidia-prime/+bug/1778011/comments/13 
my laptop has a led indicating if Nvidia GPU is on and according to it Nvidia 
GPU does not power off when I select Intel GPU.
Also tested on Kubuntu 18.04 (without "proposed" repository), same issue.

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

Title:
  SRU: PRIME Power Saving mode draws too much power

Status in HWE Next:
  New
Status in gdm3 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-390 package in Ubuntu:
  Fix Released
Status in nvidia-prime package in Ubuntu:
  Fix Released
Status in nvidia-settings package in Ubuntu:
  Fix Released
Status in sddm package in Ubuntu:
  Confirmed
Status in ubuntu-drivers-common package in Ubuntu:
  Fix Released
Status in gdm3 source package in Bionic:
  Fix Released
Status in nvidia-graphics-drivers-390 source package in Bionic:
  Fix Released
Status in nvidia-prime source package in Bionic:
  Fix Released
Status in nvidia-settings source package in Bionic:
  Fix Released
Status in sddm source package in Bionic:
  Confirmed
Status in ubuntu-drivers-common source package in Bionic:
  Fix Released

Bug description:
  SRU Request:

  [Impact]
  Relying on the nouveau driver and on the vga switcheroo (to get around a 
change in systemd LP: #1777099) caused increased power consumption, and slowed 
down the switching process.

  Furthermore, if the main X/Xwayland session was started by Gdm when
  the nvidia driver was loaded, the session will keep the nvidia module
  loaded, and prevent the system from switching off the dGPU. Also, the
  nouveau driver will be loaded, if nvidia is not, and this can cause
  problems to unsupported NVIDIA GPUs.

  The solution involves the following changes:

  1) Solving the problem in systemd (LP: #1777099)

  2) Adding code in gpu-manager and in nvidia-prime to unload the nvidia
  modules, and to allow the PCI device to sleep.

  3) Making a slight change to the current patch in Gdm, used to call
  the PRIME scripts before and after a Gdm session (so that gpu-manager
  gets actually called on log out)

  4) Adding code in gpu-manager to kill the main X/Xwayland session on
  log out, if the session is preventing us from unloading the nvidia
  driver. A new X/Xwayland session will be created after unload the
  module.

  5) Removing the systemd service that loads nouveau from the nvidia
  packages.

  [Test Case]
  1) Enable the -proposed repository, and install the new 
"ubuntu-drivers-common", nvidia drivers, nvidia-prime, and gdm3 *

  2) Make sure the nvidia packages are installed, and enable performance mode 
(if it is already enabled, call "sudo prime-select intel" first):
  sudo prime-select nvidia

  3) Restart your computer and attach your /var/log/gpu-manager.log. see
  if the system boots correctly. If unsure, please attach your /var/log
  /gpu-manager.log and /var/log/Xorg.0.log

  4) Select power saving mode:
  sudo prime-select intel

  5) Log out and log back in

  6) Check if the nvidia driver is still loaded:
  lsmod | grep nvidia

  [Regression Potential]
  Low, as hybrid graphics support does not work correctly, and the changes only 
affect this use case.

  _
  * Steps to test the updates:

  1) Enable the bionic-proposed repositories

  2) Create /etc/apt/preferences.d/proposed-updates with the following
  content:

  Package: *
  Pin: release a=bionic-proposed
  Pin-Priority: 400

  3) Update the list of packages:

  sudo apt-get update

  4) Install the packages from -proposed using the following command:

  sudo apt install nvidia-driver-390/bionic-proposed gdm3/bionic-
  proposed ubuntu-drivers-common/bionic-proposed nvidia-prime/bionic-
  proposed nvidia-settings/bionic-proposed libnvidia-gl-390/bionic-
  proposed libnvidia-compute-390/bionic-proposed libnvidia-decode-390
  /bionic-proposed libnvidia-encode-390/bionic-proposed libnvidia-
  ifr1-390/bionic-proposed libnvidia-fbc1-390/bionic-proposed

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1778011/+subscriptions

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


[Desktop-packages] [Bug 1803792] [NEW] Can't pin/keep/lock Quod Libet 4.2 to docks using bamf

2018-11-16 Thread Alexander Browne
Public bug reported:

Since upgrading the music player Quod Libet to the latest version (4.2,
via ppa:lazka/ppa), I there's no option to pin it to the MATE dock
applet. I'm using 18.10, and I also tried Plank. A Quod Libet developer
confirmed the issue as well in Unity on 16.04. AFAICT, these three docks
all use bamf.

Since all earlier versions of Quod Libet work fine, I posted a bug with
them (https://github.com/quodlibet/quodlibet/issues/3029), but there are
no reports of any issue with it from other docks/shells, like GNOME
Shell or Plasma, so maybe it's a bug with bamf?

ProblemType: Bug
DistroRelease: Ubuntu 18.10
Package: bamfdaemon 0.5.3+18.04.20180207.2-0ubuntu1
ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12
Uname: Linux 4.18.0-11-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.20.10-0ubuntu13.1
Architecture: amd64
CurrentDesktop: MATE
Date: Fri Nov 16 17:50:42 2018
InstallationDate: Installed on 2016-11-22 (724 days ago)
InstallationMedia: Ubuntu-MATE 16.10 "Yakkety Yak" - Release amd64 (20161012.1)
SourcePackage: bamf
UpgradeStatus: Upgraded to cosmic on 2018-09-29 (48 days ago)

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


** Tags: amd64 apport-bug cosmic

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

Title:
  Can't pin/keep/lock Quod Libet 4.2 to docks using bamf

Status in bamf package in Ubuntu:
  New

Bug description:
  Since upgrading the music player Quod Libet to the latest version
  (4.2, via ppa:lazka/ppa), I there's no option to pin it to the MATE
  dock applet. I'm using 18.10, and I also tried Plank. A Quod Libet
  developer confirmed the issue as well in Unity on 16.04. AFAICT, these
  three docks all use bamf.

  Since all earlier versions of Quod Libet work fine, I posted a bug
  with them (https://github.com/quodlibet/quodlibet/issues/3029), but
  there are no reports of any issue with it from other docks/shells,
  like GNOME Shell or Plasma, so maybe it's a bug with bamf?

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: bamfdaemon 0.5.3+18.04.20180207.2-0ubuntu1
  ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12
  Uname: Linux 4.18.0-11-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.10-0ubuntu13.1
  Architecture: amd64
  CurrentDesktop: MATE
  Date: Fri Nov 16 17:50:42 2018
  InstallationDate: Installed on 2016-11-22 (724 days ago)
  InstallationMedia: Ubuntu-MATE 16.10 "Yakkety Yak" - Release amd64 
(20161012.1)
  SourcePackage: bamf
  UpgradeStatus: Upgraded to cosmic on 2018-09-29 (48 days ago)

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

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


[Desktop-packages] [Bug 1803604] Re: "Send -> Document as e-mail" in Writer / Calc does not work

2018-11-16 Thread Bug Watch Updater
Launchpad has imported 17 comments from the remote bug at
https://bugs.documentfoundation.org/show_bug.cgi?id=116211.

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


On 2018-03-05T17:13:13+00:00 Bernard Moreton wrote:

Description:
When tools/options/internet/email is set to /usr/bin/claws-mail, send by email 
fails.  If it's unsert, to allow a default of xdg-email, it still fails, and if 
it's explicitly set to /usr/bin/xdg-email it still does not work.  Trying to 
Send now leaves me in limbo, somewhere between LO and my email client (Claws), 
with neither having focus, so alt-tab gets me nowhere until I manually reassert 
focus on one or the other.
Build ID: 1:6.0.2~rc1-0ubuntu0.16.04.1~lo1
on Ubunto 16.04.4 LTS

Help (on tools/options/internet/email) is not at all helpful,
and Browse isn't either - on my system it includes claws-mail.

If I select xdg-email, then I get the same result s for Claws.
xdg-email --attach  works fine for me from the command line.

If AppArmor has to be enforced, then suitable documentation should be
provided for new users.  It seems that security is now a step ahead of
usability?

Steps to Reproduce:
1.Set email cliednt (tools/options) to claws-mail or xdg-email
2.send (current) document as attachment
3.

Actual Results:  
Neither LO nor email client has focus, and nothing happens

Expected Results:
Document should be properly attached to n (draft) email


Reproducible: Always


User Profile Reset: Yes


OpenGL enabled: Yes

Additional Info:
Always worked fine until 6.0


User-Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/538.1 (KHTML, like 
Gecko) QupZilla/1.8.9 Safari/538.1

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


On 2018-03-06T07:32:06+00:00 Olivier Tilloy wrote:

Tested and I can reproduce the issue when claws-mail is the default
e-mail client on the system, even with apparmor profiles disabled (so
unlikely to be an apparmor-related issue).

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


On 2018-03-06T08:14:20+00:00 Dgp-mail wrote:

(In reply to Olivier Tilloy from comment #1)
> Tested and I can reproduce the issue

Olivier, if you can reproduce the issue, you can change status to NEW (I
did it,because of your comment)

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


On 2018-09-17T11:16:48+00:00 Bernard Moreton wrote:

Send by email still fails in 6.1.1.2.
This is disappointing, since 'sending' a document is a basic operation, which 
users would naturally expect.  As noted, this all worked prior to 6.0, so it's 
a regression.

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


On 2018-09-17T13:14:22+00:00 Bernard Moreton wrote:

I see a similar report on Apache OpenOffice, also on the Ubuntu bug reports.
Following a hint from the latter, I deleted the entry "/usr/bin/claws-mail" in 
Tools/Options/Internet/Email and tried again to send a document.  This time no 
error was reported to the GUI, but I'd called soffice from the commandline, and 
there an error had appeared "/usr/lib/libreoffice/program/senddoc: 361: 
/usr/lib/libreoffice/program/senddoc: /usr/bin/claws-mail: Permission denied"

A long listing shows
-rwxr-xr-x 1 root root 3950472 Dec 17  2017 /usr/bin/claws-mail
which looks ok?

I'll restore the setting in Tools/Options, since a visible error message
is better than an invisible one!

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


On 2018-09-18T09:50:33+00:00 Bernard Moreton wrote:

I modified 'senddoc' temporarily, to 'echo' the claws-mail command, and opened 
my testfile again from the commandline.  That showed 
/usr/bin/claws-mail --attach 
/tmp/lu35337hoq3k.tmp/lu35337hoq3n.tmp/errors_090715.odt
(all on one line).

A further edit to 'ls' the attachment file gave
/usr/lib/libreoffice/program/senddoc: 363: 
/usr/lib/libreoffice/program/senddoc: ls: Permission denied

Running the claws-mail command from the commandline (while LO was still
open) gave a similar result: file does not exist, or no permission.

Doing 'ls -l' from the command line shows the file still existing, with
directory permissions restricted to me as the owner.

A permissions problem, then?  But I can't see what it is.

Reply at:

[Desktop-packages] [Bug 1767693] Re: 18.04 GNOME displays at 60fps even if the monitor is set to 144hz

2018-11-16 Thread wayward4now
*** This bug is a duplicate of bug 1763892 ***
https://bugs.launchpad.net/bugs/1763892

Same problem with Xubuntu 18.04.

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

Title:
  18.04 GNOME displays at 60fps even if the monitor is set to 144hz

Status in Mutter:
  Unknown
Status in meta-gnome3 package in Ubuntu:
  Confirmed
Status in mutter package in Ubuntu:
  Confirmed

Bug description:
  Expected behavior : the Ubuntu desktop refreshes at the same rate as
  the monitor's refresh rate

  Current behavior : The mouse cursor moves at 144fps/hz as expected, but GNOME 
only refreshes at 60fps, resulting in very stuttery display(dragging windows, 
menu transitions etc).
  The issue is isolated to GNOME, Ubuntu flavors which do not have GNOME 3 do 
not exhibit the same problem.

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

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


[Desktop-packages] [Bug 1800062]

2018-11-16 Thread Ray Johnston
Hint: Read the documenation. Look for .htm files that contain "halftone".
Ghostscript supports PostScript Level 3 halftones and includes some
tools to do special dithering/halftoning.

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

Title:
  Ghostscript command line: /usr/bin/gs :Unrecoverable error: undefined
  in .putdeviceprops

Status in GS-GPL:
  Fix Released
Status in ghostscript package in Ubuntu:
  Fix Released
Status in ghostscript source package in Trusty:
  Fix Released
Status in ghostscript source package in Xenial:
  Fix Released
Status in ghostscript source package in Bionic:
  Fix Released
Status in ghostscript source package in Cosmic:
  Fix Released

Bug description:
  PDF file data fail to rendering to raster data.

  We were reported a bug from our printer users:
  I print file use papersize A5 (Ubuntu 16.04.1(x64),Ghostscript 9.18) is Okay.

  But, after I update (apt-get upgrade) to Ubuntu 16.04.5(x64),Ghostscript 
9.25, I print the same file with the same driver there is an error reports:
  "Filter Error"

  I figure out that all the papersize with define "LeadingEdge" can't print 
success after update.
  (with "LeadingEdge":A5, Statement, A4(without "LeadingEdge") is print Okay).

  
  I view the "CUPS Error Log",there is an error reports when print job fails:
  "Ghostscript command line: /usr/bin/gs -dQUIET -dPARANOIDSAFER -dNOPAUSE 
-dBATCH -dNOINTERPOLATE -sDEVICE=cups -sstdout=%stderr -sOutputFile=%stdout 
-sMediaType=Plain -sOutputType=Pass=1,Direction=1 -r600x600 -dLeadingEdge=1 
-dMediaPosition=7 -dDEVICEWIDTHPOINTS=420 -dDEVICEHEIGHTPOINTS=595 
-dcupsBitsPerColor=8 -dcupsColorOrder=0 -dcupsColorSpace=1 
-scupsPageSizeName=A5 -I/usr/share/cups/fonts -c \'<>setpagedevice\' -f -_

  Unrecoverable error: undefined in .putdeviceprops"

  Ubuntu 18.04(x64), Ghostscript 9.22 also have the same problem.

  --
  ghostscript had confirm that this a bug of ghostscript 9.22(and the later 
version).

  Below information is the correspondence of ghostscript:
  https://bugs.ghostscript.com/show_bug.cgi?id=700023
  ---

  Our printer driver users(also users of Ubuntu 16.04) can't do their normal 
print jobs. 
  So, we are eagerly hopping that you can offer us a patch(Ubuntu 16.04) to fix 
this bug?

To manage notifications about this bug go to:
https://bugs.launchpad.net/gs-gpl/+bug/1800062/+subscriptions

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


[Desktop-packages] [Bug 1802573] Re: Thinkpad x220 - Unable to use 2560x1440 external display connected via DisplayPort due flashing black screen

2018-11-16 Thread Adam Kessel
I can't even get into the login screen when the DisplayPort device is
attached. But I disconnected that, got to gdm login via the VGA device,
then switched to Ubuntu on Wayland. Ubuntu on Wayland works fine for me
generally, but I get the same behavior when connecting the DisplayPort
device after logging in. I've included a video of the behavior here:
https://photos.app.goo.gl/aJSx5stMMg7QZULH6

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

Title:
  Thinkpad x220 - Unable to use 2560x1440 external display connected via
  DisplayPort due flashing black screen

Status in xorg-server package in Ubuntu:
  Incomplete

Bug description:
  I have a fresh install of 18.10 on an old Thinkpad x220. Everything
  works fine with the internal display or an external Dell G2410
  (1920x1080) connected via VGA. But when I try to switch to an external
  BenQ PD2710QC (2560x1440) I only see the screen for a few seconds at a
  time and then it flashes to black. This happens consistently for
  minutes--it never "settles down".

  I've tried the default configuration as well as copying xorg.conf from
  /usr/share/doc/xserver-xorg-video-intel into /etc/x11. I've tried both
  xorg configurations with nomodeset in the bootloader and without. I
  have not been able to find any configuration that allows this external
  DisplayPort display to work.

  The same hardware combination works fine in Windows 10.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: xorg 1:7.7+19ubuntu8
  ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12
  Uname: Linux 4.18.0-10-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13
  Architecture: amd64
  Date: Fri Nov  9 13:10:59 2018
  DistUpgraded: Fresh install
  DistroCodename: cosmic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0126] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: Lenovo 2nd Generation Core Processor Family Integrated Graphics 
Controller [17aa:21da]
  InstallationDate: Installed on 2018-11-09 (0 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  MachineType: LENOVO 42872WU
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-10-generic 
root=UUID=cd4f21be-48dd-48e7-b289-a59a32bd0be3 ro quiet splash nomodeset 
vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  XorgConf:
   Section "Device"
Identifier "Intel"
Driver "intel"
   #Option "AccelMethod" "uxa"
   EndSection
  dmi.bios.date: 06/21/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 8DET76WW (1.46 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 42872WU
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Available
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvr8DET76WW(1.46):bd06/21/2018:svnLENOVO:pn42872WU:pvrThinkPadX220:rvnLENOVO:rn42872WU:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.family: ThinkPad X220
  dmi.product.name: 42872WU
  dmi.product.version: ThinkPad X220
  dmi.sys.vendor: LENOVO
  version.compiz: compiz 1:0.9.13.1+18.10.20180930-0ubuntu1
  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 N/A
  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/xorg-server/+bug/1802573/+subscriptions

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


[Desktop-packages] [Bug 1799001] Re: Theming does not work on LXQt

2018-11-16 Thread Chris Guiver
Booted same box; dist-upgrade; confirmed LXQt appearance settings were
the same, and then re-ran

Icons on main screen have changed.  I've attached screenshot.

(I didn't find breeze icon set online to compare with sorry)

** Attachment added: "libreoffice_2018-11-17_main_screen.jpg"
   
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1799001/+attachment/5213557/+files/libreoffice_2018-11-17_main_screen.jpg

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

Title:
  Theming does not work on LXQt

Status in libreoffice package in Ubuntu:
  Fix Released
Status in libreoffice source package in Cosmic:
  Fix Committed

Bug description:
  [Impact]

  Without this change, LibreOffice does not correctly use the Breeze
  theme, which is needed for consistency with the rest of the Lubuntu,
  LXQt-based desktop. At times, it is even hard to use because of the
  inconsistent theming which can hide buttons at times.

  [Test Case]

  Update to the version of LibreOffice with this patch and open it on a
  Lubuntu 18.10 installation. It should use the Breeze theming rather
  than the stock GTK theming on startup.

  [Regression Potential]

  Little to none. If for some reason the criteria that is used to check
  for the LXQt desktop no longer works, which is unlikely in a stable
  release, this will no longer work.

  [Other Info]

  I submitted these upstream (as my first patches \o/):
  https://gerrit.libreoffice.org/61641
  https://gerrit.libreoffice.org/61751

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

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


[Desktop-packages] [Bug 150373] Re: creating a 7zip gives error

2018-11-16 Thread Erkin Alp Güney
Still present in cosmic.

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

Title:
  creating a 7zip gives error

Status in File Roller:
  Expired
Status in file-roller package in Ubuntu:
  Invalid
Status in p7zip package in Ubuntu:
  Fix Released

Bug description:
  Binary package hint: file-roller

  In Gutsy Beta, if you create a 7zip archive, it will work, but throw
  an error at the end.

  The error message looks like this:

  7-Zip (A) 4.51 beta  Copyright (c) 1999-2007 Igor Pavlov  2007-07-25
  p7zip Version 4.51 (locale=en_US.UTF-8,Utf16=on,HugeFiles=on,1 CPU)
  Scanning

  Creating archive /home/matt/Desktop/service.7z

  Compressing  lots o' file names 

  Everything is Ok

  7-Zip (A) 4.51 beta  Copyright (c) 1999-2007 Igor Pavlov  2007-07-25
  p7zip Version 4.51 (locale=en_US.UTF-8,Utf16=on,HugeFiles=on,1 CPU)

  Scanning

  Updating archive /home/matt/Desktop/service.7z


  System error:
  E_NOTIMPL

To manage notifications about this bug go to:
https://bugs.launchpad.net/file-roller/+bug/150373/+subscriptions

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


[Desktop-packages] [Bug 1797796] Re: embedding OLE objects in Writer leads to blurred print

2018-11-16 Thread Wolf Rogner
This issue does not happen under 18.04(.1). Only on 18.10.
It happens in the default installation.
Current version is 6.1.2.1 and any embedded file or object gets rendered 
blurred.

Haven't tried snap only AppImage. With AppImage, all embediments are
rendered precisely.

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

Title:
  embedding OLE objects in Writer leads to blurred print

Status in libreoffice package in Ubuntu:
  Incomplete

Bug description:
  Steps to create:

  Open blank Writer document
  Insert OLE object -> Libreoffice Calc
  enter some numbers
  leave OLE object

  -> The object is rendered blurred.

  Enter OLE object (double click)
  -> the content is rendered correctly

  Print document
  -> the content of the OLE object is printed in lower quality than rest of 
document

  Combined documents with text and calculations cannot be printed in unified 
quality.
  -> This type of document is not up to office standards.

  Only on Ubuntu (on Mac this cannot be observed)

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: libreoffice-writer 1:6.0.6-0ubuntu0.18.04.1
  ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18
  Uname: Linux 4.15.0-36-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.4
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Oct 14 20:29:01 2018
  InstallationDate: Installed on 2018-04-30 (167 days ago)
  InstallationMedia: Ubuntu 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/+source/libreoffice/+bug/1797796/+subscriptions

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


[Desktop-packages] [Bug 1790100] ProcCpuinfoMinimal.txt

2018-11-16 Thread giannione
apport information

** Attachment added: "ProcCpuinfoMinimal.txt"
   
https://bugs.launchpad.net/bugs/1790100/+attachment/5213544/+files/ProcCpuinfoMinimal.txt

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

Title:
  unable to write ~ and ^ chars in the terminal

Status in gnome-terminal package in Ubuntu:
  New
Status in vte2.91 package in Ubuntu:
  Fix Released

Bug description:
  Hello,

  I am using Ubuntu 18.10 and since the last update, I am unable to
  write ~ and ^ chars in the terminal, in both gnome-terminal and Geany
  (both using libvte2.91).

  I don't have this issue with other applications (terminator, xterm,
  Firefox, Gedit, etc.). But note that now, when I type ^ for the first
  time in Gedit for example, I see this char but underlined. If I type
  it a second type (or press space), it is transformed in ^ without line
  under it. This is a new behaviour that can cause this bug in libvte.

  Please tell me if I need to join other info!

  Thanks!

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: libvte-2.91-0 0.52.2-1ubuntu1
  ProcVersionSignature: Ubuntu 4.17.0-9.10-generic 4.17.17
  Uname: Linux 4.17.0-9-generic x86_64
  ApportVersion: 2.20.10-0ubuntu9
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Aug 31 11:17:43 2018
  InstallationDate: Installed on 2015-08-10 (1116 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  SourcePackage: vte2.91
  UpgradeStatus: Upgraded to cosmic on 2016-04-29 (854 days ago)

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

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


[Desktop-packages] [Bug 1790100] Re: unable to write ~ and ^ chars in the terminal

2018-11-16 Thread giannione
hello, I run that command
"ubuntu-bug -u 1790100"

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

Title:
  unable to write ~ and ^ chars in the terminal

Status in gnome-terminal package in Ubuntu:
  New
Status in vte2.91 package in Ubuntu:
  Fix Released

Bug description:
  Hello,

  I am using Ubuntu 18.10 and since the last update, I am unable to
  write ~ and ^ chars in the terminal, in both gnome-terminal and Geany
  (both using libvte2.91).

  I don't have this issue with other applications (terminator, xterm,
  Firefox, Gedit, etc.). But note that now, when I type ^ for the first
  time in Gedit for example, I see this char but underlined. If I type
  it a second type (or press space), it is transformed in ^ without line
  under it. This is a new behaviour that can cause this bug in libvte.

  Please tell me if I need to join other info!

  Thanks!

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: libvte-2.91-0 0.52.2-1ubuntu1
  ProcVersionSignature: Ubuntu 4.17.0-9.10-generic 4.17.17
  Uname: Linux 4.17.0-9-generic x86_64
  ApportVersion: 2.20.10-0ubuntu9
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Aug 31 11:17:43 2018
  InstallationDate: Installed on 2015-08-10 (1116 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  SourcePackage: vte2.91
  UpgradeStatus: Upgraded to cosmic on 2016-04-29 (854 days ago)

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

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


[Desktop-packages] [Bug 1790100] ProcEnviron.txt

2018-11-16 Thread giannione
apport information

** Attachment added: "ProcEnviron.txt"
   
https://bugs.launchpad.net/bugs/1790100/+attachment/5213545/+files/ProcEnviron.txt

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

Title:
  unable to write ~ and ^ chars in the terminal

Status in gnome-terminal package in Ubuntu:
  New
Status in vte2.91 package in Ubuntu:
  Fix Released

Bug description:
  Hello,

  I am using Ubuntu 18.10 and since the last update, I am unable to
  write ~ and ^ chars in the terminal, in both gnome-terminal and Geany
  (both using libvte2.91).

  I don't have this issue with other applications (terminator, xterm,
  Firefox, Gedit, etc.). But note that now, when I type ^ for the first
  time in Gedit for example, I see this char but underlined. If I type
  it a second type (or press space), it is transformed in ^ without line
  under it. This is a new behaviour that can cause this bug in libvte.

  Please tell me if I need to join other info!

  Thanks!

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: libvte-2.91-0 0.52.2-1ubuntu1
  ProcVersionSignature: Ubuntu 4.17.0-9.10-generic 4.17.17
  Uname: Linux 4.17.0-9-generic x86_64
  ApportVersion: 2.20.10-0ubuntu9
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Aug 31 11:17:43 2018
  InstallationDate: Installed on 2015-08-10 (1116 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  SourcePackage: vte2.91
  UpgradeStatus: Upgraded to cosmic on 2016-04-29 (854 days ago)

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

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


[Desktop-packages] [Bug 1790100] apport information

2018-11-16 Thread giannione
ProblemType: Bug
ApportVersion: 2.20.9-0ubuntu7.4
Architecture: amd64
CurrentDesktop: GNOME
DistroRelease: Ubuntu 18.04
InstallationDate: Installed on 2017-10-25 (387 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
Package: gnome-terminal 3.28.2-1ubuntu1~18.04.1
PackageArchitecture: amd64
ProcVersionSignature: Ubuntu 4.15.0-38.41-generic 4.15.18
Tags:  bionic wayland-session
Uname: Linux 4.15.0-38-generic x86_64
UpgradeStatus: Upgraded to bionic on 2018-10-13 (34 days ago)
UserGroups: adm cdrom dip libvirt lpadmin plugdev sambashare sudo vboxusers
_MarkForUpload: True

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

Title:
  unable to write ~ and ^ chars in the terminal

Status in gnome-terminal package in Ubuntu:
  New
Status in vte2.91 package in Ubuntu:
  Fix Released

Bug description:
  Hello,

  I am using Ubuntu 18.10 and since the last update, I am unable to
  write ~ and ^ chars in the terminal, in both gnome-terminal and Geany
  (both using libvte2.91).

  I don't have this issue with other applications (terminator, xterm,
  Firefox, Gedit, etc.). But note that now, when I type ^ for the first
  time in Gedit for example, I see this char but underlined. If I type
  it a second type (or press space), it is transformed in ^ without line
  under it. This is a new behaviour that can cause this bug in libvte.

  Please tell me if I need to join other info!

  Thanks!

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: libvte-2.91-0 0.52.2-1ubuntu1
  ProcVersionSignature: Ubuntu 4.17.0-9.10-generic 4.17.17
  Uname: Linux 4.17.0-9-generic x86_64
  ApportVersion: 2.20.10-0ubuntu9
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Aug 31 11:17:43 2018
  InstallationDate: Installed on 2015-08-10 (1116 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  SourcePackage: vte2.91
  UpgradeStatus: Upgraded to cosmic on 2016-04-29 (854 days ago)

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

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


[Desktop-packages] [Bug 1790100] Dependencies.txt

2018-11-16 Thread giannione
apport information

** Attachment added: "Dependencies.txt"
   
https://bugs.launchpad.net/bugs/1790100/+attachment/5213543/+files/Dependencies.txt

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

Title:
  unable to write ~ and ^ chars in the terminal

Status in gnome-terminal package in Ubuntu:
  New
Status in vte2.91 package in Ubuntu:
  Fix Released

Bug description:
  Hello,

  I am using Ubuntu 18.10 and since the last update, I am unable to
  write ~ and ^ chars in the terminal, in both gnome-terminal and Geany
  (both using libvte2.91).

  I don't have this issue with other applications (terminator, xterm,
  Firefox, Gedit, etc.). But note that now, when I type ^ for the first
  time in Gedit for example, I see this char but underlined. If I type
  it a second type (or press space), it is transformed in ^ without line
  under it. This is a new behaviour that can cause this bug in libvte.

  Please tell me if I need to join other info!

  Thanks!

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: libvte-2.91-0 0.52.2-1ubuntu1
  ProcVersionSignature: Ubuntu 4.17.0-9.10-generic 4.17.17
  Uname: Linux 4.17.0-9-generic x86_64
  ApportVersion: 2.20.10-0ubuntu9
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Aug 31 11:17:43 2018
  InstallationDate: Installed on 2015-08-10 (1116 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  SourcePackage: vte2.91
  UpgradeStatus: Upgraded to cosmic on 2016-04-29 (854 days ago)

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

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


[Desktop-packages] [Bug 1790100] Re: unable to write ~ and ^ chars in the terminal

2018-11-16 Thread giannione
ProblemType: Bug
ApportVersion: 2.20.9-0ubuntu7.4
Architecture: amd64
CurrentDesktop: GNOME
DistroRelease: Ubuntu 18.04
InstallationDate: Installed on 2017-10-25 (387 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
Package: gnome-terminal 3.28.2-1ubuntu1~18.04.1
PackageArchitecture: amd64
ProcVersionSignature: Ubuntu 4.15.0-38.41-generic 4.15.18
Tags:  bionic wayland-session
Uname: Linux 4.15.0-38-generic x86_64
UpgradeStatus: Upgraded to bionic on 2018-10-13 (34 days ago)
UserGroups: adm cdrom dip libvirt lpadmin plugdev sambashare sudo vboxusers
_MarkForUpload: True


** Tags added: apport-collected bionic

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

Title:
  unable to write ~ and ^ chars in the terminal

Status in gnome-terminal package in Ubuntu:
  New
Status in vte2.91 package in Ubuntu:
  Fix Released

Bug description:
  Hello,

  I am using Ubuntu 18.10 and since the last update, I am unable to
  write ~ and ^ chars in the terminal, in both gnome-terminal and Geany
  (both using libvte2.91).

  I don't have this issue with other applications (terminator, xterm,
  Firefox, Gedit, etc.). But note that now, when I type ^ for the first
  time in Gedit for example, I see this char but underlined. If I type
  it a second type (or press space), it is transformed in ^ without line
  under it. This is a new behaviour that can cause this bug in libvte.

  Please tell me if I need to join other info!

  Thanks!

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: libvte-2.91-0 0.52.2-1ubuntu1
  ProcVersionSignature: Ubuntu 4.17.0-9.10-generic 4.17.17
  Uname: Linux 4.17.0-9-generic x86_64
  ApportVersion: 2.20.10-0ubuntu9
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Aug 31 11:17:43 2018
  InstallationDate: Installed on 2015-08-10 (1116 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  SourcePackage: vte2.91
  UpgradeStatus: Upgraded to cosmic on 2016-04-29 (854 days ago)

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

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


[Desktop-packages] [Bug 1790100] ProcCpuinfoMinimal.txt

2018-11-16 Thread giannione
apport information

** Attachment added: "ProcCpuinfoMinimal.txt"
   
https://bugs.launchpad.net/bugs/1790100/+attachment/5213547/+files/ProcCpuinfoMinimal.txt

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

Title:
  unable to write ~ and ^ chars in the terminal

Status in gnome-terminal package in Ubuntu:
  New
Status in vte2.91 package in Ubuntu:
  Fix Released

Bug description:
  Hello,

  I am using Ubuntu 18.10 and since the last update, I am unable to
  write ~ and ^ chars in the terminal, in both gnome-terminal and Geany
  (both using libvte2.91).

  I don't have this issue with other applications (terminator, xterm,
  Firefox, Gedit, etc.). But note that now, when I type ^ for the first
  time in Gedit for example, I see this char but underlined. If I type
  it a second type (or press space), it is transformed in ^ without line
  under it. This is a new behaviour that can cause this bug in libvte.

  Please tell me if I need to join other info!

  Thanks!

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: libvte-2.91-0 0.52.2-1ubuntu1
  ProcVersionSignature: Ubuntu 4.17.0-9.10-generic 4.17.17
  Uname: Linux 4.17.0-9-generic x86_64
  ApportVersion: 2.20.10-0ubuntu9
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Aug 31 11:17:43 2018
  InstallationDate: Installed on 2015-08-10 (1116 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  SourcePackage: vte2.91
  UpgradeStatus: Upgraded to cosmic on 2016-04-29 (854 days ago)

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

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


[Desktop-packages] [Bug 1790100] Dependencies.txt

2018-11-16 Thread giannione
apport information

** Attachment added: "Dependencies.txt"
   
https://bugs.launchpad.net/bugs/1790100/+attachment/5213546/+files/Dependencies.txt

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

Title:
  unable to write ~ and ^ chars in the terminal

Status in gnome-terminal package in Ubuntu:
  New
Status in vte2.91 package in Ubuntu:
  Fix Released

Bug description:
  Hello,

  I am using Ubuntu 18.10 and since the last update, I am unable to
  write ~ and ^ chars in the terminal, in both gnome-terminal and Geany
  (both using libvte2.91).

  I don't have this issue with other applications (terminator, xterm,
  Firefox, Gedit, etc.). But note that now, when I type ^ for the first
  time in Gedit for example, I see this char but underlined. If I type
  it a second type (or press space), it is transformed in ^ without line
  under it. This is a new behaviour that can cause this bug in libvte.

  Please tell me if I need to join other info!

  Thanks!

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: libvte-2.91-0 0.52.2-1ubuntu1
  ProcVersionSignature: Ubuntu 4.17.0-9.10-generic 4.17.17
  Uname: Linux 4.17.0-9-generic x86_64
  ApportVersion: 2.20.10-0ubuntu9
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Aug 31 11:17:43 2018
  InstallationDate: Installed on 2015-08-10 (1116 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  SourcePackage: vte2.91
  UpgradeStatus: Upgraded to cosmic on 2016-04-29 (854 days ago)

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

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


[Desktop-packages] [Bug 1728012] Re: Many 3rd party scanner drivers are broken by a sane change

2018-11-16 Thread James C March
@luca.mg Your suggestion in comment #157 worked! I had to install
libsane-extras (and libsane-common) using Synaptic Package Manager. Not
sure why those weren't already part of the install. I also added the
line "brother4" to the file /etc/sane.d/dll.d/libsane-extras. Now my
home wifi networked Brother MFC-J470DW scanner (brscan4) shows up and
works with XSANE and Simple Scan! Thank you!

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

Title:
  Many 3rd party scanner drivers are broken by a sane change

Status in sane-backends package in Ubuntu:
  Confirmed

Bug description:
  Many scanners can no more be used since sane has changed something:
  The 3rd-party plug-in the vendor provides as .deb package will still
  install. But the scanner is no more recognized.

  Scanners that are affected are(besides others):
   - Epson Perfection V10
   - Epson Perfection V1000
   - Epson WorkForce GT-1500
   - Brother MFC-8510DN
   - Epson Perfection V33

  It is to note that the probability that the scanner manufacturers fix
  things others broke is below 100%.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: libsane1 1.0.27-1~experimental2ubuntu2
  Uname: Linux 4.14.0-041400rc5-lowlatency x86_64
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  Date: Fri Oct 27 12:35:52 2017
  EcryptfsInUse: Yes
  SourcePackage: sane-backends
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1788220] Re: [snap] Ubuntu 18.04 LTS includes gnome-calculator as a snap

2018-11-16 Thread Steve Langasek
** Changed in: ubuntu-meta (Ubuntu)
   Status: New => Opinion

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

Title:
  [snap] Ubuntu 18.04 LTS includes gnome-calculator as a snap

Status in gnome-calculator package in Ubuntu:
  Fix Released
Status in ubuntu-meta package in Ubuntu:
  Opinion

Bug description:
  Ubuntu 18.04 includes the calculator as a snap.

  The standard installation of snap, with no custom snap apps installed
  other than what Ubuntu installs by default, takes a whooping 1.6GB of
  hard disk. Calc takes forever to start in a modern machine compared to
  the normal calc installed with APT, creates snap files in the user's
  home dir (with name $HOME/snap). This is ridiculous.

  Snap is immature, there's no sysadmin tool support, and it's not ready
  to make it the default for standard Ubuntu LTS.

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

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


[Desktop-packages] [Bug 1552792] Re: gnome software leaves dependencies installed

2018-11-16 Thread Ken VanDine
I've verified this fixes the issue with the following versions:

packagekit=1.1.9-1ubuntu2.18.04.4
gnome-software=3.28.1-0ubuntu4.18.04.7


** Tags removed: verification-needed-bionic
** Tags added: verification-done-bionic

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

Title:
  gnome software leaves dependencies installed

Status in GNOME Software:
  Invalid
Status in Release Notes for Ubuntu:
  Fix Released
Status in gnome-software package in Ubuntu:
  Fix Released
Status in packagekit package in Ubuntu:
  Fix Released
Status in gnome-software source package in Bionic:
  Fix Committed
Status in packagekit source package in Bionic:
  Fix Committed
Status in gnome-software source package in Cosmic:
  Fix Released
Status in packagekit source package in Cosmic:
  Fix Released

Bug description:
  [Impact]
  Installing an application them removing it leaves dependencies behind.

  [Test Case]
  1. Ensure that GNOME Sudoku is not installed:
  $ sudo apt remove gnome-sudoku libqqwing2v5
  2. Check if you have any packages that need autoremoval:
  $ sudo apt autoremove --no-act
  3. Open GNOME Software.
  4. Search for and install GNOME Sudoku (make sure to install the .deb, not 
the snap).
  5. Uninstall GNOME Sudoku.
  6. Check if you have any packages that need autoremoval:
  $ sudo apt autoremove --no-act

  Expected result:
  The packages in step 6 are the same as in step 2 (which might be none).

  Observed result:
  The packages in step 6 includes libqqwing2v5, which is a dependency of 
gnome-sudoku and not useful without the game installed.

  [Regression Potential]
  This requires a fix to PackageKit which used to autoremove all packages (too 
aggressive), not just the ones related to the current transaction. A bug in the 
code could cause more packages to be removed than is suitable. GNOME Software 
previously didn't use this autoremove functionality, so by enabling it we could 
trigger a problem in either the existing code or the new fix.

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

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


[Desktop-packages] [Bug 1771031] Re: Please remove libgnome from Ubuntu

2018-11-16 Thread Gianfranco Costamagna
Syncd shortly

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

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

Title:
  Please remove libgnome from Ubuntu

Status in gbonds package in Ubuntu:
  New
Status in gjiten package in Ubuntu:
  New
Status in gnome-color-chooser package in Ubuntu:
  New
Status in gnome-commander package in Ubuntu:
  New
Status in gnome-translate package in Ubuntu:
  New
Status in grdesktop package in Ubuntu:
  New
Status in gresolver package in Ubuntu:
  New
Status in libbonobo package in Ubuntu:
  New
Status in libbonoboui package in Ubuntu:
  New
Status in libgnome package in Ubuntu:
  New
Status in libgnomeui package in Ubuntu:
  New
Status in linsmith package in Ubuntu:
  New
Status in p4vasp package in Ubuntu:
  Fix Released
Status in pike7.8 package in Ubuntu:
  Invalid
Status in resapplet package in Ubuntu:
  New
Status in winefish package in Ubuntu:
  New

Bug description:
  libgnome has been removed from Debian Testing and will not be included
  in the Debian 10 "Buster" release. We should do the same. If we do it
  now, maybe some projects will do the needed porting work away from
  libgnome (porting to gtk3 is probably needed) in time for Ubuntu 20.04
  LTS or Debian 10. Users who are hurt by these removals can keep using
  Ubuntu 18.04 LTS for a few years.

  This bug depends on these other removals:
  gnome-python LP: #1739800
  gnome-sharp2 LP: #1771025
  DONE: shutter LP: #1771030

  The libgnome removal in turn blocks these other removals:
  gnome-vfs LP: #1771035
  libgnome-keyring LP: #1771036

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

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


[Desktop-packages] [Bug 1771031] Re: Please remove libgnome from Ubuntu

2018-11-16 Thread Gianfranco Costamagna
Removed from disco

** Changed in: pike7.8 (Ubuntu)
   Status: New => Invalid

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

Title:
  Please remove libgnome from Ubuntu

Status in gbonds package in Ubuntu:
  New
Status in gjiten package in Ubuntu:
  New
Status in gnome-color-chooser package in Ubuntu:
  New
Status in gnome-commander package in Ubuntu:
  New
Status in gnome-translate package in Ubuntu:
  New
Status in grdesktop package in Ubuntu:
  New
Status in gresolver package in Ubuntu:
  New
Status in libbonobo package in Ubuntu:
  New
Status in libbonoboui package in Ubuntu:
  New
Status in libgnome package in Ubuntu:
  New
Status in libgnomeui package in Ubuntu:
  New
Status in linsmith package in Ubuntu:
  New
Status in p4vasp package in Ubuntu:
  Fix Released
Status in pike7.8 package in Ubuntu:
  Invalid
Status in resapplet package in Ubuntu:
  New
Status in winefish package in Ubuntu:
  New

Bug description:
  libgnome has been removed from Debian Testing and will not be included
  in the Debian 10 "Buster" release. We should do the same. If we do it
  now, maybe some projects will do the needed porting work away from
  libgnome (porting to gtk3 is probably needed) in time for Ubuntu 20.04
  LTS or Debian 10. Users who are hurt by these removals can keep using
  Ubuntu 18.04 LTS for a few years.

  This bug depends on these other removals:
  gnome-python LP: #1739800
  gnome-sharp2 LP: #1771025
  DONE: shutter LP: #1771030

  The libgnome removal in turn blocks these other removals:
  gnome-vfs LP: #1771035
  libgnome-keyring LP: #1771036

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

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


[Desktop-packages] [Bug 1802623] Re: gnome-shell crashed with signal 5 in _XIOError()

2018-11-16 Thread Steve Beattie
Thanks for taking the time to report this bug and helping to make Ubuntu
better. We appreciate the difficulties you are facing, but this appears
to be a "regular" (non-security) bug.  I have unmarked it as a security
issue since this bug does not show evidence of allowing attackers to
cross privilege boundaries nor directly cause loss of data/privacy.
Please feel free to report any other bugs you may find.

** Information type changed from Private Security to Public

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

Title:
  gnome-shell crashed with signal 5 in _XIOError()

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  d

  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.26.1-0ubuntu4
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CurrentDesktop: GNOME-Greeter:GNOME
  Date: Sun Sep 30 10:21:48 2018
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  GsettingsChanges:
   
  InstallationDate: Installed on 2018-05-14 (179 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  ProcCmdline: /usr/bin/gnome-shell
  ProcEnviron:
   LANGUAGE=en_IN:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_IN
   SHELL=/bin/false
  Signal: 5
  SourcePackage: gnome-shell
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/libmutter-1.so.0
   _XIOError () from /usr/lib/x86_64-linux-gnu/libX11.so.6
   _XEventsQueued () from /usr/lib/x86_64-linux-gnu/libX11.so.6
   XPending () from /usr/lib/x86_64-linux-gnu/libX11.so.6
   ?? () from /usr/lib/x86_64-linux-gnu/libgdk-3.so.0
  Title: gnome-shell crashed with signal 5 in _XIOError()
  UpgradeStatus: Upgraded to artful on 2018-06-22 (140 days ago)
  UserGroups:

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

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


[Desktop-packages] [Bug 1803059] Re: Nullpointer dereference

2018-11-16 Thread Steve Beattie
** Information type changed from Private Security to Public Security

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

Title:
  Nullpointer dereference

Status in evince package in Ubuntu:
  New

Bug description:
  System Info: Linux zero 4.15.0-38-generic #41-Ubuntu SMP Wed Oct 10
  10:59:38 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux

  Evince version: GNOME Document Viewer 3.28.4

  While fuzzing evince v3.28.4, on linux 4.15.0-38-generic (Ubuntu 18.04
  LTS), a null-pointer dereference was observed, initially this was
  reported to evince but the evince team advised that the issue is in
  poppler, the library used by evince to render PDF, poppler version:
  0.62.0-2ubuntu2.2 is vulnerable to null-pointer dereference, however
  the issue is already fixed in poppler 0.70, but this will still crash
  your evince v3.28.4 in ubuntu if poppler is not updated to v.0.70.

  Fuzzing result showing a very important vulnerability in a package
  currently shipped by a major Linux distribution is still of interest,
  even if that Linux distribution does not package the latest released
  upstream version. I think Ubuntu is still using,

  Source: poppler
  Version: 0.62.0-2ubuntu2.2

  So, most of the systems will be affected to this issue.

  Upstream: https://gitlab.freedesktop.org/poppler/poppler/issues/664

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

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


[Desktop-packages] [Bug 1802754] Re: package nvidia-340 (not installed) failed to install/upgrade: опит за презапис на '/lib/udev/rules.d/71-nvidia.rules', съществуващ вече и в пакета nvidia-kernel-co

2018-11-16 Thread Steve Beattie
Thanks for taking the time to report this bug and helping to make Ubuntu
better. We appreciate the difficulties you are facing, but this appears
to be a "regular" (non-security) bug.  I have unmarked it as a security
issue since this bug does not show evidence of allowing attackers to
cross privilege boundaries nor directly cause loss of data/privacy.
Please feel free to report any other bugs you may find.

** Information type changed from Private Security to Public

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

Title:
  package nvidia-340 (not installed) failed to install/upgrade: опит за
  презапис на '/lib/udev/rules.d/71-nvidia.rules', съществуващ вече и в
  пакета nvidia-kernel-common-390 390.77-0ubuntu0.18.04.1

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

Bug description:
  a

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: nvidia-340 (not installed)
  ProcVersionSignature: Ubuntu 4.15.0-38.41-generic 4.15.18
  Uname: Linux 4.15.0-38-generic x86_64
  NonfreeKernelModules: nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7.4
  Architecture: amd64
  Date: Sun Nov 11 19:49:25 2018
  ErrorMessage: опит за презапис на '/lib/udev/rules.d/71-nvidia.rules', 
съществуващ вече и в пакета nvidia-kernel-common-390 390.77-0ubuntu0.18.04.1
  InstallationDate: Installed on 2018-11-11 (0 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  Python3Details: /usr/bin/python3.6, Python 3.6.6, python3-minimal, 
3.6.5-3ubuntu1
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu2.1
   apt  1.6.6
  SourcePackage: nvidia-graphics-drivers-340
  Title: package nvidia-340 (not installed) failed to install/upgrade: опит за 
презапис на '/lib/udev/rules.d/71-nvidia.rules', съществуващ вече и в пакета 
nvidia-kernel-common-390 390.77-0ubuntu0.18.04.1
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1803527] Re: ubuntu 18.10 fails to restore from suspend if no password

2018-11-16 Thread Steve Beattie
** Package changed: ubuntu => gnome-shell (Ubuntu)

** Information type changed from Private Security to Public

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

Title:
  ubuntu 18.10 fails to restore from suspend if no password

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  my system:
  ubuntu 18.10
  4k monitor with 1 scale and 1.5 font scale
  nvidia 410 and 390 drivers are checked

  when happened:
  lock screen or suspend. return after that.
  if I have user password prompt enabled: everything ok
  if I haven't user password prompt enabled, system started with gnome crashed

  I expect:
  ubuntu to has the same behaviour either I have a password either not.

  What happened:
  in case of no password (I should just 'swipe up' or press 'space' and 
everything should be ready.. but) most of the times I can not return to desktop.
  - freezes on a screen with panels but no desktop
  - freezes on a purple screen that no command is working (as ctrl+alt+t)
  - freezes on a useless gnome panels (dash and topbar) mode

  solution chosen:
  I press ctrl+alt+F1 to change environment, I enter my password... BUT again 
the gnome is too slow, app icon is always on and everything is acting weird 
(some apps' icon that I have opened on the other session is liked pined on dash 
without have the option to unpin it - like I see it but it is not pinned)
  So, I just save what I can through the new session and just restart the pc 
(in new session is available - in the previous is only suspend available)

  frequency: about 80% of the times. If lock-screen showed up normally
  (and I have to press space to unlock) everything works like a charm
  afterwards. If not.. it will be the mess I described above

  hope it helps

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

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


[Desktop-packages] [Bug 1783514] Re: firefox password field not accessible in popup dialog

2018-11-16 Thread Michael Kuster
There's no differens using

GTK_IM_MODULE= firefox

Unfortunatley sunrise.ch changed the login PopUp-window and separated
the password entry field to a separate step. On the attached screenshot
you can see like it should be, after you entered a valid phone number.
You can use following phone nr. (is not mine) just one that works: 076
447 12 12. You are not able to reach the password field. If you are fast
enough you can click to "My Sunrise" and if the dialog appears for some
milliseconds you can try to fill in the password character by
character...

I suggest to install the Firefox AddOn "windscribe" (no need for an
account). If you click to the password field, the PopUp-dialog
disappears like described in the bug #1803631.

this bug dosn't affect ubuntu 18.10

** Attachment added: "password field.png"
   
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1783514/+attachment/5213539/+files/password%20field.png

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

Title:
  firefox password field not accessible in popup dialog

Status in firefox package in Ubuntu:
  Incomplete

Bug description:
  
  if you open the popup dialog "My Sunrise" on this site:
  https://www.sunrise.ch/en/residential/welcome-page.html

  you are not able to access the password field. Not by clicking and not
  with tab-key. on the given expample site you can check the box "Show
  password", the you can enter the password. But if you don't have this
  option, you can't login.

  Another example is the Firefox addon "Windscribe". You have to login
  with popup dialog and it's not possible to enter the password.

  This bug affects only the Linux version of firefox as I now.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: firefox 61.0.1+build1-0ubuntu0.18.04.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
  BuildID: 20180704192850
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Jul 25 10:32:34 2018
  ExecutablePath: /usr/lib/firefox/firefox
  SourcePackage: firefox
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1724876] Re: libreoffice soffice.bin using 100% cpu

2018-11-16 Thread Olivier Tilloy
If this really is an upstream bug in glib
(https://gitlab.gnome.org/GNOME/glib/issues/1128) then it looks like no,
this isn't being actively worked on.

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

Title:
  libreoffice soffice.bin using 100% cpu

Status in libreoffice package in Ubuntu:
  Confirmed

Bug description:
  With literally every action in libreoffice Calc, CPU usage goes to
  100% due to soffice.bin, and stays on 100% for minutes. To the extend
  that libreoffice calc is UNUSABLE for anything that has to do with
  spreadsheets. As far as I am concerned, this is a critical bug because
  it makes the program unusable, and often even the complete computer
  due to the high cpu load.

  - 'Every action' includes typing as much as one single letter in a cell. Or 
opening the file.
  - the file I am working on is only 1.1Mb in size
  - the same file used to open fine in previous versions of libreoffice.

  what I've tried so far - without any improvement in speed:
  - under tools, options, assigned memory 256 Mb for Libreoffice, and 20Mb per 
object (no solution)
  - automatic calculation has been turned off (no solution)
  - libreoffice-gnome and libreoffice-gtk have been removed (no solution)
  - purged and reinstalled libreoffice. (no solution)
  - created new user profile - also no resolve


  System: Ubuntu 16.04 LTS on AMD A8 with 8Gb ram and running on an SSD.
  Libreoffice: 
  Version: 5.1.6.2
  Build ID: 1:5.1.6~rc2-0ubuntu1~xenial2
  CPU Threads: 4; OS Version: Linux 4.4; UI Render: default

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

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


[Desktop-packages] [Bug 1798103] Re: Text highlight mismatch in view-source when layout.css.devPixelsPerPx is >= 1.2

2018-11-16 Thread Olivier Tilloy
I can reliably reproduce the bug with the steps provided.

@Jani: would you mind reporting the bug upstream at
https://bugzilla.mozilla.org/enter_bug.cgi#h=dupes%7CFirefox and sharing
the link to it here?

When I search for upstream bug reports containing
"layout.css.devPixelsPerPx", I find several issues that are probably
related to what you're seeing, but none mention the view-source: view,
so I think a new bug would be useful.

Thanks!

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

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

Title:
  Text highlight mismatch in view-source when layout.css.devPixelsPerPx
  is >= 1.2

Status in firefox package in Ubuntu:
  Confirmed

Bug description:
  == The issue ==
  Search and text selection highlighting visuals get mismatched with the actual 
selection in view-source when the value of `layout.css.devPixelsPerPx` is 1.2 
or larger.

  == Steps to reproduce ==
  * Open `about:config`, find `layout.css.devPixelsPerPx` and change the value 
from default (-1.0) to 1.2.
  * Open a view-source view with long lines: 
`view-source:https://www.youtube.com/user/10asti10`
  * hit Ctrl+f, search for rss
  * using the LMB, try selecting some text, then copy and paste it somewhere

  == What happens ==
  Screenshot 1: the highlighted text on the page is not ”rss”. The highlight 
doesn’t even adhere to letter widths.

  Screenshot 2: the pasted text is not even close to what you’ve
  selected to copy.

  == What I expect to happen ==
  For the search to hightlight an occurence of ”rss”, and for the pasted text 
to correspond to what I’ve selected from the view-source view.

  == Other info ==
  * In my testing, a devPixelsPerPx value of 1.1 seems to not trigger this, 
whereas 1.2 and anything above does.
  * In addition to 18.04 (whence the attached info is from) I’ve reproduced 
this in a VM running up-to-date 18.10.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: firefox 62.0.3+build1-0ubuntu0.18.04.1
  ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18
  Uname: Linux 4.15.0-36-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.9-0ubuntu7.4
  Architecture: amd64
  BuildID: 20181002130007
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Oct 16 16:59:28 2018
  InstallationDate: Installed on 2016-10-13 (733 days ago)
  InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fi_FI.UTF-8
   SHELL=/bin/bash
  SourcePackage: firefox
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1803655] Re: screen flickering and appearing green colour at screen edges

2018-11-16 Thread Steve Beattie
Thanks for taking the time to report this bug and helping to make Ubuntu
better. We appreciate the difficulties you are facing, but this appears
to be a "regular" (non-security) bug.  I have unmarked it as a security
issue since this bug does not show evidence of allowing attackers to
cross privilege boundaries nor directly cause loss of data/privacy.
Please feel free to report any other bugs you may find.

** Information type changed from Private Security to Public

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

Title:
  screen flickering and appearing green colour at screen edges

Status in xorg package in Ubuntu:
  New

Bug description:
  recently ihave installed ubuntu 18.10 version from 16.04 lts but it
  has started screen flickering and screen appearing green at edges of
  the screen before logging the system  the screen flickering is
  appearing and with green color after login the screen flickering
  dissapears .I hope you will find the solution and this problem is
  appearing from 5 days is this a software or hardware problem.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: xorg 1:7.7+19ubuntu8
  ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12
  Uname: Linux 4.18.0-11-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13.1
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Nov 16 09:45:49 2018
  DistUpgraded: Fresh install
  DistroCodename: cosmic
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller 
[8086:0152] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: Lenovo Xeon E3-1200 v2/3rd Gen Core processor Graphics 
Controller [17aa:365e]
  InstallationDate: Installed on 2018-11-15 (0 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  MachineType: LENOVO 10104
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.18.0-11-generic 
root=UUID=72505e1c-0f9f-4860-b3d1-59f626acc7e8 ro quiet splash vt.handoff=1
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/03/2012
  dmi.bios.vendor: LENOVO
  dmi.bios.version: ELKT29AUS
  dmi.board.name: MAHOBAY
  dmi.board.vendor: LENOVO
  dmi.board.version: Win8 STD EM DPK IPG
  dmi.chassis.type: 13
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnLENOVO:bvrELKT29AUS:bd12/03/2012:svnLENOVO:pn10104:pvrLenovoC440:rvnLENOVO:rnMAHOBAY:rvrWin8STDEMDPKIPG:cvnToBeFilledByO.E.M.:ct13:cvrToBeFilledByO.E.M.:
  dmi.product.family: IdeaCentre
  dmi.product.name: 10104
  dmi.product.sku: LENOVO_MT_1010
  dmi.product.version: Lenovo C440
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.95-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.2-0ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.2-0ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.1-3ubuntu2.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-3

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

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


[Desktop-packages] [Bug 1798843] Re: Ubuntu Software (gnome-software package) loads a blank screen

2018-11-16 Thread Olivier Tilloy
Version 3.30.2-0ubuntu8 is now available in cosmic-updates. Are you
still seeing the problem after updating?

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

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

Title:
  Ubuntu Software (gnome-software package) loads a blank screen

Status in gnome-software package in Ubuntu:
  Incomplete

Bug description:
  Ubuntu Software (gnome-software package) loads a blank screen in
  Ubuntu 18.10 'Cosmic' x64 upon launching the app.

  No text, images, or UI elements appear within the window.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: gnome-software 3.30.2-0ubuntu7
  ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12
  Uname: Linux 4.18.0-10-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Oct 19 11:15:37 2018
  InstallationDate: Installed on 2018-08-17 (63 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  InstalledPlugins:
   gnome-software-plugin-flatpak 3.30.2-0ubuntu7
   gnome-software-plugin-limba   N/A
   gnome-software-plugin-snap3.30.2-0ubuntu7
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-software
  UpgradeStatus: Upgraded to cosmic on 2018-10-19 (0 days ago)

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

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


[Desktop-packages] [Bug 1798450] Re: [snap] File dialogs show snap's home directory instead of user's

2018-11-16 Thread Bug Watch Updater
** Changed in: snapcraft
   Status: Unknown => New

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

Title:
  [snap] File dialogs show snap's home directory instead of user's

Status in Snapcraft:
  New
Status in chromium-browser package in Ubuntu:
  Confirmed
Status in libreoffice package in Ubuntu:
  Confirmed

Bug description:
  How to reproduce:

  - Find a web page that has a file chooser (you can just paste `` into an empty HTML page)
  - Click the "Choose File" button
  - Click "Home" if you didn't start here
  - See that Chromium uses `/home/$USER/snap/chromium/500` as the home folder

  Expected behavior:

  The file picker should use the user's home folder, not the snap's,
  because everything else would be confusing for end users.

  Versions:

  snap2.35.4+18.10
  snapd   2.35.4+18.10
  series  16
  ubuntu  18.10
  kernel  4.18.11-surface-linux-surface

  Chromium 70.0.3538.67 snap

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

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


[Desktop-packages] [Bug 1784485] Re: [ZenBook S UX391UA, Realtek ALC294, Mic, Internal] No sound at all

2018-11-16 Thread sojusnik
@Karen Chaltikian

Good news! Although I've tried this on my UX391UA, but without success.

Can you describe your procedure step-by-step?

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

Title:
  [ZenBook S UX391UA, Realtek ALC294, Mic, Internal] No sound at all

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  Internal speaker - not sound at all
  Cable Headphonse - realy quiet disorted sound
  Bluetooth headphones - sound works fine

  On Windows 10 everything works fine.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  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
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  pmichalski   7964 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Jul 30 22:32:10 2018
  InstallationDate: Installed on 2018-07-17 (12 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=pl_PL.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaRecordingTest: ALSA recording test through plughw:PCH failed
  Symptom_Card: Wbudowany dźwięk - HDA Intel PCH
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gdm2988 F pulseaudio
pmichalski   7964 F pulseaudio
  Symptom_Jack: Mic, Internal
  Symptom_Type: No sound at all
  Title: [ZenBook S UX391UA, Realtek ALC294, Mic, Internal] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/18/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX391UA.204
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX391UA
  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.:bvrUX391UA.204:bd05/18/2018:svnASUSTeKCOMPUTERINC.:pnZenBookSUX391UA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX391UA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: ZenBook S
  dmi.product.name: ZenBook S UX391UA
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

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

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


[Desktop-packages] [Bug 1728012] Re: Many 3rd party scanner drivers are broken by a sane change

2018-11-16 Thread Jaime Cruz
Another vote for LouBurnard's method here.  Bionic with Epson Perfection
V33 scanner.

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

Title:
  Many 3rd party scanner drivers are broken by a sane change

Status in sane-backends package in Ubuntu:
  Confirmed

Bug description:
  Many scanners can no more be used since sane has changed something:
  The 3rd-party plug-in the vendor provides as .deb package will still
  install. But the scanner is no more recognized.

  Scanners that are affected are(besides others):
   - Epson Perfection V10
   - Epson Perfection V1000
   - Epson WorkForce GT-1500
   - Brother MFC-8510DN
   - Epson Perfection V33

  It is to note that the probability that the scanner manufacturers fix
  things others broke is below 100%.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: libsane1 1.0.27-1~experimental2ubuntu2
  Uname: Linux 4.14.0-041400rc5-lowlatency x86_64
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  Date: Fri Oct 27 12:35:52 2017
  EcryptfsInUse: Yes
  SourcePackage: sane-backends
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1798450] Re: [snap] File dialogs show snap's home directory instead of user's

2018-11-16 Thread Olivier Tilloy
And I filed https://github.com/ubuntu/snapcraft-desktop-
helpers/issues/167 to track the issue where it belongs.

** Also affects: df-libreoffice via
   https://github.com/ubuntu/snapcraft-desktop-helpers/issues/167
   Importance: Unknown
   Status: Unknown

** Project changed: df-libreoffice => snapcraft

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

Title:
  [snap] File dialogs show snap's home directory instead of user's

Status in Snapcraft:
  Unknown
Status in chromium-browser package in Ubuntu:
  Confirmed
Status in libreoffice package in Ubuntu:
  Confirmed

Bug description:
  How to reproduce:

  - Find a web page that has a file chooser (you can just paste `` into an empty HTML page)
  - Click the "Choose File" button
  - Click "Home" if you didn't start here
  - See that Chromium uses `/home/$USER/snap/chromium/500` as the home folder

  Expected behavior:

  The file picker should use the user's home folder, not the snap's,
  because everything else would be confusing for end users.

  Versions:

  snap2.35.4+18.10
  snapd   2.35.4+18.10
  series  16
  ubuntu  18.10
  kernel  4.18.11-surface-linux-surface

  Chromium 70.0.3538.67 snap

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

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


[Desktop-packages] [Bug 1798450] Re: [snap] File dialogs show snap's home directory instead of user's

2018-11-16 Thread Olivier Tilloy
This also affects the libreoffice snap, and more generally all snaps
using the desktop helpers (and it should be fixed there).

** Tags added: snap

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

** Changed in: chromium-browser (Ubuntu)
   Importance: Undecided => Medium

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

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

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

** Bug watch added: github.com/ubuntu/snapcraft-desktop-helpers/issues #167
   https://github.com/ubuntu/snapcraft-desktop-helpers/issues/167

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

Title:
  [snap] File dialogs show snap's home directory instead of user's

Status in Snapcraft:
  Unknown
Status in chromium-browser package in Ubuntu:
  Confirmed
Status in libreoffice package in Ubuntu:
  Confirmed

Bug description:
  How to reproduce:

  - Find a web page that has a file chooser (you can just paste `` into an empty HTML page)
  - Click the "Choose File" button
  - Click "Home" if you didn't start here
  - See that Chromium uses `/home/$USER/snap/chromium/500` as the home folder

  Expected behavior:

  The file picker should use the user's home folder, not the snap's,
  because everything else would be confusing for end users.

  Versions:

  snap2.35.4+18.10
  snapd   2.35.4+18.10
  series  16
  ubuntu  18.10
  kernel  4.18.11-surface-linux-surface

  Chromium 70.0.3538.67 snap

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

-- 
Mailing list: https://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 1803752] Re: HID inputs (mouse buttons and keyboard) stop responding when plug in DP monitor

2018-11-16 Thread Jonathan Polak
VGA compatible controller: Intel Corporation Skylake GT2 [HD Graphics 520]
(rev 07)
Subsystem: Lenovo Skylake GT2 [HD Graphics 520]
Kernel driver in use: i915
Kernel modules: i915


AND attached Xorg.0.log


On Fri, Nov 16, 2018 at 11:00 AM APolihron  wrote:

> What GPU and video driver are you using?
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1803752
>
> Title:
>   HID inputs (mouse buttons and keyboard) stop responding when plug in
>   DP monitor
>
> Status in ubuntu-mate:
>   New
> Status in mate-common package in Ubuntu:
>   New
> Status in xorg package in Ubuntu:
>   New
>
> Bug description:
>   Ever since upgrading to 18.10 plugging in external monitors has been
>   buggy.
>
>   Device Lenovo T460s. Ubuntu-Mate 18.10.
>
>   Plugging in External monitor using mini-display port causes keyboard
>   to be unresponsive. Mouse buttons as well. though can still move mouse
>   on screen. Plugging in and out using arndr sometimes resolves this.
>   Notwithstanding, no smooth transition to multimonitor mode.
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu-mate/+bug/1803752/+subscriptions
>


** Attachment added: "Xorg.0.log"
   https://bugs.launchpad.net/bugs/1803752/+attachment/5213531/+files/Xorg.0.log

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

Title:
  HID inputs (mouse buttons and keyboard) stop responding when plug in
  DP monitor

Status in ubuntu-mate:
  New
Status in mate-common package in Ubuntu:
  New
Status in xorg package in Ubuntu:
  New

Bug description:
  Ever since upgrading to 18.10 plugging in external monitors has been
  buggy.

  Device Lenovo T460s. Ubuntu-Mate 18.10.

  Plugging in External monitor using mini-display port causes keyboard
  to be unresponsive. Mouse buttons as well. though can still move mouse
  on screen. Plugging in and out using arndr sometimes resolves this.
  Notwithstanding, no smooth transition to multimonitor mode.

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

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


[Desktop-packages] [Bug 1799693] Re: Stable libopus-1.3 released

2018-11-16 Thread Jeremy Bicha
Ubuntu's opus comes directly from Debian.

Therefore, it would be helpful if someone would report this issue to
Debian. There are some instructions available for that at
https://wiki.ubuntu.com/Debian/Bugs

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

Title:
  Stable libopus-1.3 released

Status in opus package in Ubuntu:
  New

Bug description:
  Cosmic is currently shipping libopus-1.3~beta+20180518-1 which is now 
outdated and technically marked as a beta. 
  http://opus-codec.org/release/stable/2018/10/18/libopus-1_3.html

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

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


[Desktop-packages] [Bug 1795169] Re: Focus switches constantly between username and password fields

2018-11-16 Thread Olivier Tilloy
Yet another bug that goes away when unsetting GTK_IM_MODULE. See also
bug #1803631 and bug #1765304.

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

Title:
  Focus switches constantly between username and password fields

Status in firefox package in Ubuntu:
  Invalid
Status in firefox source package in Bionic:
  Confirmed

Bug description:
  https://www.bbva.es/particulares/index.jsp

  If you click on "Entrar"(Log in) the pop-up window that opens allows you to 
enter a username when you click in "usuario"(user) but when you click on "clave 
de acceso"(password) the selection cursor changes continuously between "user" 
and " password ", preventing the introduction of the password.
  Ubuntu 16.04 with firefox 62.0 work fine, when update to ubuntu 18.04.1 LTS 
with firefox 62.0 fail.
  The 18.04 with Chromium 69.0.3497.81, also works well.
  I have the same problem in two computers.

  Description:  Ubuntu 18.04.1 LTS
  Release:  18.04

  firefox:
Instalados: 62.0+build2-0ubuntu0.18.04.5
Candidato:  62.0+build2-0ubuntu0.18.04.5
Tabla de versión:
   *** 62.0+build2-0ubuntu0.18.04.5 500
  500 http://es.archive.ubuntu.com/ubuntu bionic-updates/main amd64 
Packages
  500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 
Packages
  100 /var/lib/dpkg/status
   59.0.2+build1-0ubuntu1 500
  500 http://es.archive.ubuntu.com/ubuntu bionic/main amd64 Packages

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

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


[Desktop-packages] [Bug 1750243] Re: [snap] StartupWMClass missing in .desktop file

2018-11-16 Thread Olivier Tilloy
Note that the fact that "Create shortcut" doesn't work in the snap is a
known issue: bug #1732482.

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

Title:
  [snap] StartupWMClass missing in .desktop file

Status in chromium-browser package in Ubuntu:
  Confirmed

Bug description:
  Chromium Snap Version 64.0.3282.167

  How to reproduce:

  In Gnome:

  Add the Chromium Snap to the left launcher panel. 
  Start the Chromium Snap.

  Actual behavior: 
  The Chromium snap starts and creates a new symbol in the launcher panel.

  Desired behavior:
  The Chromium snap should start using the symbol which is already pinned to 
the launcher panel.

  In Budgie:

  The Chromium Snap cannot be pinned to the panel at all.

  Possible solution:

  Add StartupWMClass= ... to the .desktop launcher of the chromium snap.

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

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


[Desktop-packages] [Bug 1797796] Re: embedding OLE objects in Writer leads to blurred print

2018-11-16 Thread Olivier Tilloy
Thank for the feedback Wolf. Can you try the snap package (sudo snap
install libreoffice; snap run libreoffice.writer) and report whether the
issue exists with it as well?

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

Title:
  embedding OLE objects in Writer leads to blurred print

Status in libreoffice package in Ubuntu:
  Incomplete

Bug description:
  Steps to create:

  Open blank Writer document
  Insert OLE object -> Libreoffice Calc
  enter some numbers
  leave OLE object

  -> The object is rendered blurred.

  Enter OLE object (double click)
  -> the content is rendered correctly

  Print document
  -> the content of the OLE object is printed in lower quality than rest of 
document

  Combined documents with text and calculations cannot be printed in unified 
quality.
  -> This type of document is not up to office standards.

  Only on Ubuntu (on Mac this cannot be observed)

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: libreoffice-writer 1:6.0.6-0ubuntu0.18.04.1
  ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18
  Uname: Linux 4.15.0-36-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.4
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Oct 14 20:29:01 2018
  InstallationDate: Installed on 2018-04-30 (167 days ago)
  InstallationMedia: Ubuntu 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/+source/libreoffice/+bug/1797796/+subscriptions

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


[Desktop-packages] [Bug 1803752] Re: HID inputs (mouse buttons and keyboard) stop responding when plug in DP monitor

2018-11-16 Thread APolihron
What GPU and video driver are you using?

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

Title:
  HID inputs (mouse buttons and keyboard) stop responding when plug in
  DP monitor

Status in ubuntu-mate:
  New
Status in mate-common package in Ubuntu:
  New
Status in xorg package in Ubuntu:
  New

Bug description:
  Ever since upgrading to 18.10 plugging in external monitors has been
  buggy.

  Device Lenovo T460s. Ubuntu-Mate 18.10.

  Plugging in External monitor using mini-display port causes keyboard
  to be unresponsive. Mouse buttons as well. though can still move mouse
  on screen. Plugging in and out using arndr sometimes resolves this.
  Notwithstanding, no smooth transition to multimonitor mode.

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

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


[Desktop-packages] [Bug 1803752] Re: HID inputs (mouse buttons and keyboard) stop responding when plug in DP monitor

2018-11-16 Thread APolihron
I believe that is a kernel problem.

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

Title:
  HID inputs (mouse buttons and keyboard) stop responding when plug in
  DP monitor

Status in ubuntu-mate:
  New
Status in mate-common package in Ubuntu:
  New
Status in xorg package in Ubuntu:
  New

Bug description:
  Ever since upgrading to 18.10 plugging in external monitors has been
  buggy.

  Device Lenovo T460s. Ubuntu-Mate 18.10.

  Plugging in External monitor using mini-display port causes keyboard
  to be unresponsive. Mouse buttons as well. though can still move mouse
  on screen. Plugging in and out using arndr sometimes resolves this.
  Notwithstanding, no smooth transition to multimonitor mode.

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

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


[Desktop-packages] [Bug 1783514] Re: firefox password field not accessible in popup dialog

2018-11-16 Thread Olivier Tilloy
I cannot observe the issue as I don't have a valid customer number to
test with.

Can you try running firefox with the environment variable GTK_IM_MODULE
unset, and let us know if that makes a difference (wondering whether
that's related to bug #1803631) ? You can do that by closing firefox and
then running the following command in a terminal:

GTK_IM_MODULE= firefox

** Summary changed:

- firefox password field not accessable in popup dialog
+ firefox password field not accessible in popup dialog

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

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

Title:
  firefox password field not accessible in popup dialog

Status in firefox package in Ubuntu:
  Incomplete

Bug description:
  
  if you open the popup dialog "My Sunrise" on this site:
  https://www.sunrise.ch/en/residential/welcome-page.html

  you are not able to access the password field. Not by clicking and not
  with tab-key. on the given expample site you can check the box "Show
  password", the you can enter the password. But if you don't have this
  option, you can't login.

  Another example is the Firefox addon "Windscribe". You have to login
  with popup dialog and it's not possible to enter the password.

  This bug affects only the Linux version of firefox as I now.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: firefox 61.0.1+build1-0ubuntu0.18.04.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
  BuildID: 20180704192850
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Jul 25 10:32:34 2018
  ExecutablePath: /usr/lib/firefox/firefox
  SourcePackage: firefox
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1792329] Re: Firefox freezes continuously on Ubuntu 16.04

2018-11-16 Thread Olivier Tilloy
Could it be that your system is running out of memory? Do you have swap
configured?

** Summary changed:

- Firefox freezes continuosly on Ubuntu 16.04
+ Firefox freezes continuously on Ubuntu 16.04

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

Title:
  Firefox freezes continuously on Ubuntu 16.04

Status in firefox package in Ubuntu:
  New

Bug description:
  FireFox 62 freezes continuously. (64 bit Ubuntu 16.04.5)
  Lock mouse and keyboard on Ubuntu, I have to switch off with the On / Off 
button. Minor defect, but appeared simultaneously, I open a second / third 
page, do not load, I go back to the previous one and is no longer loaded, you 
only see the wheel of time. In this case, restart Firefox.

  
  glxinfo | grep "OpenGL version"
  OpenGL version string: 3.0 Mesa 18.0.5

  WM_CLASS(STRING) = "Navigator", "Firefox"

  Description:  Ubuntu 16.04.5 LTS
  Release:  16.04

  Intel® Celeron(R) CPU N2840 @ 2.16GHz × 2

  Intel® Bay Trail
  --- 
  AddonCompatCheckDisabled: False
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   stefano1933 F...m pulseaudio
   /dev/snd/controlC0:  stefano1933 F pulseaudio
  BuildID: 20181023214907
  Channel: Unavailable
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.04
  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 2018-09-12 (59 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  IpRoute:
   default via 192.168.1.1 dev wlp2s0  proto static  metric 600 
   169.254.0.0/16 dev wlp2s0  scope link  metric 1000 
   192.168.1.0/24 dev wlp2s0  proto kernel  scope link  src 192.168.1.3  metric 
600
  Locales: extensions.sqlite corrupt or missing
  Package: firefox 63.0+build2-0ubuntu0.16.04.2
  PackageArchitecture: amd64
  Plugins: Shockwave Flash - /usr/lib/flashplugin-installer/libflashplayer.so
  PrefSources: prefs.js
  ProcVersionSignature: Ubuntu 4.15.0-38.41~16.04.1-generic 4.15.18
  Profiles: Profile0 (Default) - LastVersion=63.0/20181023214907 (In use)
  RunningIncompatibleAddons: False
  Tags:  xenial
  Themes: extensions.sqlite corrupt or missing
  Uname: Linux 4.15.0-38-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 07/18/2014
  dmi.bios.vendor: LENOVO
  dmi.bios.version: A7CN40WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: Lancer 5A6
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0F82993WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo G50-30
  dmi.modalias: 
dmi:bvnLENOVO:bvrA7CN40WW:bd07/18/2014:svnLENOVO:pn80G0:pvrLenovoG50-30:rvnLENOVO:rnLancer5A6:rvrSDK0F82993WIN:cvnLENOVO:ct10:cvrLenovoG50-30:
  dmi.product.family: IDEAPAD
  dmi.product.name: 80G0
  dmi.product.version: Lenovo G50-30
  dmi.sys.vendor: LENOVO

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

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


[Desktop-packages] [Bug 1799293] Re: gnome session: Must ask twice to lock the screen

2018-11-16 Thread Brian Murray
** Tags added: rls-cc-incoming rls-dd-incoming

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

Title:
  gnome session: Must ask twice to lock the screen

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

Bug description:
  1) Ubuntu 18.10 (new install)
  2) gdm3 3.30.1-1ubuntu5

  Preconditions
  The session's user has auto-login enabled (i.e. the system starts and the 
user is not prompted for a password but directly presented with the desktop)

  3) What should happen:
  Unlocked desktop is showing. Lock screen is invoked (via WIN+L or via top 
right corner menu) and the lock screen is engaged (that is, lock screen clock 
shade drops down and screen fades to dark). Pressing ENTER brings back the lock 
screen and the password is prompted.

  4) What happens:
  First Win + L lets the system in a half locked state in which the contents of 
the desktop are seen although no interaction is possible. A second Win + L 
correctly invokes the lock screen.

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

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


[Desktop-packages] [Bug 1803604] Re: "Send -> Document as e-mail" in Writer / Calc does not work

2018-11-16 Thread Olivier Tilloy
** Bug watch added: Document Foundation Bugzilla #116211
   https://bugs.documentfoundation.org/show_bug.cgi?id=116211

** Also affects: df-libreoffice via
   https://bugs.documentfoundation.org/show_bug.cgi?id=116211
   Importance: Unknown
   Status: Unknown

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

Title:
  "Send -> Document as e-mail" in Writer / Calc does not work

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

Bug description:
  Description:  Linux Mint 18.3 Sylvia
  Release:  18.3
  LO: Version: 6.1.3.2
  Build-ID: 1:6.1.3~rc2-0ubuntu0.16.04.1

  In writer I have an open document. If I then want to send it:

  "File - send - document as e-mail"

  **Nothing happens**

  Same with send e-mail as open-document and word document. Only send
  with pdf opens at least the pdf dialogue. But then nothing happens.

  Path to thunderbird: /usr/bin/thunderbird
  Thunderbird opens if I use this path so the path seems correct. No error 
message received.

  Expect: Mail is opened and document attached. (which worked before)

  Update: Just checked in Ubuntu 18.04 and LO 6.06.2
  There it works as expected. Will check my other system again. Maybe it just 
does not work on my other system.

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

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


[Desktop-packages] [Bug 1798053] Re: [SRU] Click on the back icon in gnome-software doesn't work

2018-11-16 Thread Olivier Tilloy
Bug #1800286 is very unlikely to be caused by this SRU.

** Tags removed: verification-failed-cosmic

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

Title:
  [SRU] Click on the back icon in gnome-software doesn't work

Status in gnome-software package in Ubuntu:
  Fix Released
Status in gnome-software source package in Cosmic:
  Fix Released

Bug description:
  [Test Case]

  1. Open gnome-software
  2. Press Ctrl+F and type "firefox" or any string that will return results
  3. Click any result in the list (snap package or deb, already installed or 
not, it doesn't matter)
  4. Observe that a new page is open showing details about the application
  5. Close gnome-software
  6. Open gnome-software again
  7. Observe that the application is open on the last open page (details view 
about the application)
  8. Click the back button (top-left corner)

  Expected result: the application goes back to the list of search
  results (or perhaps to the home screen)

  Current result: nothing happens

  Please note that the upstream fix reverts a new behaviour and as a
  result, when opening again gnome-software at step 6, the application
  opens on the home screen instead of resuming the last open page. This
  is consistent with how gnome-software behaves in bionic. So after
  applying the patch, steps 7 and 8 can be folded into one single step:
  "Observe that the application is open on the home screen".

  
  [Regression Potential]

  Low. This is a cherry-pick of a self-contained trivial upstream commit that 
is already released in gnome-software 3.30.3 
(https://gitlab.gnome.org/GNOME/gnome-software/commit/ca5f8e74b6f9991ae228caa2c698131a54764774).
  As noted above, it does change the behaviour of re-opening the application 
after closing it, but it reverts it to the behaviour it had in bionic, so I 
don't think it should be considered a regression.

  Re-opening the application after closing it in a number of different
  situations should be thoroughly exercised to make sure that this
  doesn't introduce any functional regression.

  
  [Original Description]

  Searched for Chromium, installed Chromium (snap version), clicked Launched 
and used chromium.
  Went back to gnome-software and clicked the back button. Nothing happened. 
Restarted gnome-software and clicked the back button. Nothing happened.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: gnome-software 3.30.2-0ubuntu3 [modified: 
usr/share/gnome-shell/search-providers/org.gnome.Software-search-provider.ini]
  ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12
  Uname: Linux 4.18.0-10-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13
  Architecture: amd64
  CasperVersion: 1.399
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Oct 16 11:22:16 2018
  InstalledPlugins:
   gnome-software-plugin-flatpak N/A
   gnome-software-plugin-limba   N/A
   gnome-software-plugin-snap3.30.2-0ubuntu3
  LiveMediaBuild: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181016)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-software
  UpgradeStatus: No upgrade log present (probably fresh install)
  modified.conffile..etc.xdg.autostart.gnome-software-service.desktop: [deleted]

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

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


[Desktop-packages] [Bug 1800286] Re: Not Showing all aplications that are installled

2018-11-16 Thread Olivier Tilloy
** Tags added: bot-stop-nagging

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

Title:
  Not Showing all aplications that are installled

Status in gnome-software package in Ubuntu:
  New

Bug description:
  Gnome-software, games, and othere are not seen in the gnome-software
  store installed section.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: gnome-software 3.30.2-0ubuntu8
  ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12
  Uname: Linux 4.18.0-11-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Oct 27 07:14:46 2018
  InstallationDate: Installed on 2018-10-10 (16 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  InstalledPlugins:
   gnome-software-plugin-flatpak N/A
   gnome-software-plugin-limba   N/A
   gnome-software-plugin-snap3.30.2-0ubuntu8
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-software
  UpgradeStatus: Upgraded to cosmic on 2018-10-26 (0 days ago)

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

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


[Desktop-packages] [Bug 1803520] Re: Broken pipe errors on firefox close

2018-11-16 Thread Olivier Tilloy
Does this otherwise break any firefox functionality, or impair the
system in any way?

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

Title:
  Broken pipe errors on firefox close

Status in firefox package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu desktop 18.04.1 up to date with kernel 4.15.0-39-generic @
  15/11/2018

  every time firefox is closed, syslog spits out gnome-shell broken pipe
  errors like these:

  Nov 15 11:02:01 RooTBooK org.gnome.Shell.desktop[16761]: [Parent 15445, 
Gecko_IOThread] WARNING: pipe error: Gebroken pijp: file 
/build/firefox-4VfQCB/firefox-63.0+build2/ipc/chromium/src/chrome/common/ipc_channel_posix.cc,
 line 729
  Nov 15 11:02:29 RooTBooK org.gnome.Shell.desktop[16761]: [Parent 15445, 
Gecko_IOThread] WARNING: pipe error (101): Verbinding is weggevallen: file 
/build/firefox-4VfQCB/firefox-63.0+build2/ipc/chromium/src/chrome/common/ipc_channel_posix.cc,
 line 356
  Nov 15 11:02:29 RooTBooK org.gnome.Shell.desktop[16761]: [Parent 15445, 
Gecko_IOThread] WARNING: pipe error (58): Verbinding is weggevallen: file 
/build/firefox-4VfQCB/firefox-63.0+build2/ipc/chromium/src/chrome/common/ipc_channel_posix.cc,
 line 356
  Nov 15 11:02:29 RooTBooK org.gnome.Shell.desktop[16761]: IPDL protocol error: 
Handler returned error code!
  Nov 15 11:02:29 RooTBooK org.gnome.Shell.desktop[16761]: ###!!! 
[Parent][DispatchAsyncMessage] Error: PLayerTransaction::Msg_ReleaseLayer 
Processing error: message was deserialized, but the handler returned false 
(indicating failure)
  Nov 15 11:03:09 RooTBooK firefox[1211]: Theme parsing error: :1:34: 
Expected ')' in color definition
  Nov 15 11:03:09 RooTBooK firefox[1211]: Theme parsing error: :1:77: 
Expected ')' in color definition

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: firefox 63.0+build2-0ubuntu0.18.04.2
  ProcVersionSignature: Ubuntu 4.15.0-39.42-generic 4.15.18
  Uname: Linux 4.15.0-39-generic x86_64
  AddonCompatCheckDisabled: False
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  lotuspsychje  16784 F pulseaudio
  BuildID: 20181023214826
  Channel: Unavailable
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Nov 15 11:05:06 2018
  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 2018-08-17 (90 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  IpRoute:
   default via 192.168.1.1 dev wlp2s0 proto dhcp metric 600 
   169.254.0.0/16 dev wlp2s0 scope link metric 1000 
   192.168.1.0/24 dev wlp2s0 proto kernel scope link src 192.168.1.2 metric 600 
   192.168.250.0/24 dev anbox0 proto kernel scope link src 192.168.250.1
  Locales: extensions.sqlite corrupt or missing
  PrefSources: prefs.js
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=nl_BE.UTF-8
   SHELL=/bin/bash
  Profiles: Profile0 (Default) - LastVersion=63.0/20181023214826 (In use)
  RunningIncompatibleAddons: False
  SourcePackage: firefox
  Themes: extensions.sqlite corrupt or missing
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/14/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 7.009
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: N7x0WU
  dmi.board.vendor: Notebook
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: No Enclosure
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr7.009:bd05/14/2018:svnNotebook:pnN7x0WU:pvrNotApplicable:rvnNotebook:rnN7x0WU:rvrNotApplicable:cvnNoEnclosure:ct10:cvrN/A:
  dmi.product.family: Not Applicable
  dmi.product.name: N7x0WU
  dmi.product.version: Not Applicable
  dmi.sys.vendor: Notebook

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

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


[Desktop-packages] [Bug 1803520] Re: Broken pipe errors on firefox close

2018-11-16 Thread Olivier Tilloy
Not seeing those when testing in a clean 18.04 VM, but it looks like
others are seeing them: https://askubuntu.com/questions/1093181
/shutdown-freeze

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

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

Title:
  Broken pipe errors on firefox close

Status in firefox package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu desktop 18.04.1 up to date with kernel 4.15.0-39-generic @
  15/11/2018

  every time firefox is closed, syslog spits out gnome-shell broken pipe
  errors like these:

  Nov 15 11:02:01 RooTBooK org.gnome.Shell.desktop[16761]: [Parent 15445, 
Gecko_IOThread] WARNING: pipe error: Gebroken pijp: file 
/build/firefox-4VfQCB/firefox-63.0+build2/ipc/chromium/src/chrome/common/ipc_channel_posix.cc,
 line 729
  Nov 15 11:02:29 RooTBooK org.gnome.Shell.desktop[16761]: [Parent 15445, 
Gecko_IOThread] WARNING: pipe error (101): Verbinding is weggevallen: file 
/build/firefox-4VfQCB/firefox-63.0+build2/ipc/chromium/src/chrome/common/ipc_channel_posix.cc,
 line 356
  Nov 15 11:02:29 RooTBooK org.gnome.Shell.desktop[16761]: [Parent 15445, 
Gecko_IOThread] WARNING: pipe error (58): Verbinding is weggevallen: file 
/build/firefox-4VfQCB/firefox-63.0+build2/ipc/chromium/src/chrome/common/ipc_channel_posix.cc,
 line 356
  Nov 15 11:02:29 RooTBooK org.gnome.Shell.desktop[16761]: IPDL protocol error: 
Handler returned error code!
  Nov 15 11:02:29 RooTBooK org.gnome.Shell.desktop[16761]: ###!!! 
[Parent][DispatchAsyncMessage] Error: PLayerTransaction::Msg_ReleaseLayer 
Processing error: message was deserialized, but the handler returned false 
(indicating failure)
  Nov 15 11:03:09 RooTBooK firefox[1211]: Theme parsing error: :1:34: 
Expected ')' in color definition
  Nov 15 11:03:09 RooTBooK firefox[1211]: Theme parsing error: :1:77: 
Expected ')' in color definition

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: firefox 63.0+build2-0ubuntu0.18.04.2
  ProcVersionSignature: Ubuntu 4.15.0-39.42-generic 4.15.18
  Uname: Linux 4.15.0-39-generic x86_64
  AddonCompatCheckDisabled: False
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  lotuspsychje  16784 F pulseaudio
  BuildID: 20181023214826
  Channel: Unavailable
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Nov 15 11:05:06 2018
  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 2018-08-17 (90 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  IpRoute:
   default via 192.168.1.1 dev wlp2s0 proto dhcp metric 600 
   169.254.0.0/16 dev wlp2s0 scope link metric 1000 
   192.168.1.0/24 dev wlp2s0 proto kernel scope link src 192.168.1.2 metric 600 
   192.168.250.0/24 dev anbox0 proto kernel scope link src 192.168.250.1
  Locales: extensions.sqlite corrupt or missing
  PrefSources: prefs.js
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=nl_BE.UTF-8
   SHELL=/bin/bash
  Profiles: Profile0 (Default) - LastVersion=63.0/20181023214826 (In use)
  RunningIncompatibleAddons: False
  SourcePackage: firefox
  Themes: extensions.sqlite corrupt or missing
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/14/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 7.009
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: N7x0WU
  dmi.board.vendor: Notebook
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: No Enclosure
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr7.009:bd05/14/2018:svnNotebook:pnN7x0WU:pvrNotApplicable:rvnNotebook:rnN7x0WU:rvrNotApplicable:cvnNoEnclosure:ct10:cvrN/A:
  dmi.product.family: Not Applicable
  dmi.product.name: N7x0WU
  dmi.product.version: Not Applicable
  dmi.sys.vendor: Notebook

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

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


[Desktop-packages] [Bug 1803631] Re: Clicking an field in a webextension popup will cause popup to close

2018-11-16 Thread Olivier Tilloy
Unsetting the GTK_IM_MODULE environment variable makes the problem go
away.

Possibly related: bug #1765304.

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

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

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

Title:
  Clicking an  field in a webextension popup will
  cause popup to close

Status in firefox package in Ubuntu:
  Confirmed

Bug description:
  This bug is Ubuntu specific, I've tested in Fedora 28 with Firefox
  63.0 and cannot reproduce. I've attached an example extension that
  triggers the bug.

  To reproduce:

  1. Go to about:debugging and load test extension
  2. Open extension popup and click on text field
  3. Try to input text

  Expected behavior:

  My input shows up in text field

  Actual behavior:

  Extension popup closes

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: firefox 63.0+build2-0ubuntu0.18.04.2
  ProcVersionSignature: Ubuntu 4.15.0-39.42-generic 4.15.18
  Uname: Linux 4.15.0-39-generic x86_64
  AddonCompatCheckDisabled: False
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  mymindstorm   1349 F pulseaudio
  BuildID: 20181023214826
  Channel: Unavailable
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Nov 15 18:51:36 2018
  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 2018-11-15 (0 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  IpRoute:
   default via 192.168.122.1 dev ens3 proto dhcp metric 100 
   169.254.0.0/16 dev ens3 scope link metric 1000 
   192.168.122.0/24 dev ens3 proto kernel scope link src 192.168.122.13 metric 
100
  IwConfig:
   lono wireless extensions.
   
   ens3  no wireless extensions.
  Locales: extensions.sqlite corrupt or missing
  PrefSources: prefs.js
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  Profiles: Profile0 (Default) - LastVersion=63.0/20181023214826 (In use)
  RfKill:
   
  RunningIncompatibleAddons: False
  SourcePackage: firefox
  Themes: extensions.sqlite corrupt or missing
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/01/2014
  dmi.bios.vendor: SeaBIOS
  dmi.bios.version: ?-20180531_142017-buildhw-08.phx2.fedoraproject.org-1.fc28
  dmi.chassis.type: 1
  dmi.chassis.vendor: QEMU
  dmi.chassis.version: pc-i440fx-2.11
  dmi.modalias: 
dmi:bvnSeaBIOS:bvr?-20180531_142017-buildhw-08.phx2.fedoraproject.org-1.fc28:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-2.11:cvnQEMU:ct1:cvrpc-i440fx-2.11:
  dmi.product.name: Standard PC (i440FX + PIIX, 1996)
  dmi.product.version: pc-i440fx-2.11
  dmi.sys.vendor: QEMU

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

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


[Desktop-packages] [Bug 1803764] [NEW] opensgmls reports errors on W3C "standard" DTD's

2018-11-16 Thread David A. Cobb
Public bug reported:

RELEASE: Ubuntu 18.04.1 LTS
onsgmls:I: "OpenSP" version "1.5.2"

After several failed attempts to validate a developing XHTML+RDFa
document, I cut and pasted the simplest possible XHTML (encl1) and
atttempted to validate it within emacs+psgml.  The error messages refer,
not to some error in my document, but to errors in the DTD's.  That's
not impossible, but very improbable that it would not have been caught
and passed on to the W3C.

*** onsgmls output: ***
-*- mode: compilation; default-directory: "~/LEARN/RDFa+XHTML/" -*-
Compilation started at Fri Nov 16 11:56:50

onsgmls -s --warning=all  minimal.xhtml
onsgmls:http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd:273:27:E: 
omitted tag minimization parameter can be omitted only if OMITTAG NO is 
specified
onsgmls:http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd:275:8:E: 
character ":" invalid: only "CDATA", "ENTITIES", "ENTITY", "ID", "IDREF", 
"IDREFS", "NAME", "NAMES", "NMTOKEN", "NMTOKENS", "NOTATION", "NUMBER", 
"NUMBERS", "NUTOKEN", "NUTOKENS" and parameter separators allowed
onsgmls:http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd:289:49:E: 
omitted tag minimization parameter can be omitted only if OMITTAG NO is 
specified
onsgmls:http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd:292:8:E: 
character ":" invalid: only "CDATA", "ENTITIES", "ENTITY", "ID", "IDREF", 
"IDREFS", "NAME", "NAMES", "NMTOKEN", "NMTOKENS", "NOTATION", "NUMBER", 
"NUMBERS", "NUTOKEN", "NUTOKENS" and parameter separators allowed
onsgmls:http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd:301:25:E: 
omitted tag minimization parameter can be omitted only if OMITTAG NO is 
specified
onsgmls:http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd:303:8:E: 
character ":" invalid: only "CDATA", "ENTITIES", "ENTITY", "ID", "IDREF", 
"IDREFS", "NAME", "NAMES", "NMTOKEN", "NMTOKENS", "NOTATION", "NUMBER", 
"NUMBERS", "NUTOKEN", "NUTOKENS" and parameter separators allowed
onsgmls:http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd:309:15:E: 
omitted tag minimization parameter can be omitted only if OMITTAG NO is 
specified
onsgmls:http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd:317:15:E: 
omitted tag minimization parameter can be omitted only if OMITTAG NO is 
specified
onsgmls:http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd:319:8:E: 
character ":" invalid: only "CDATA", "ENTITIES", "ENTITY", "ID", "IDREF", 
"IDREFS", "NAME", "NAMES", "NMTOKEN", "NMTOKENS", "NOTATION", "NUMBER", 
"NUMBERS", "NUTOKEN", "NUTOKENS" and parameter separators allowed
*** And more like the above ***

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

** Attachment added: "encl 1:  My very simple document"
   
https://bugs.launchpad.net/bugs/1803764/+attachment/5213530/+files/minimal.xhtml

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

Title:
  opensgmls reports errors on W3C "standard" DTD's

Status in openjade package in Ubuntu:
  New

Bug description:
  RELEASE: Ubuntu 18.04.1 LTS
  onsgmls:I: "OpenSP" version "1.5.2"

  After several failed attempts to validate a developing XHTML+RDFa
  document, I cut and pasted the simplest possible XHTML (encl1) and
  atttempted to validate it within emacs+psgml.  The error messages
  refer, not to some error in my document, but to errors in the DTD's.
  That's not impossible, but very improbable that it would not have been
  caught and passed on to the W3C.

  *** onsgmls output: ***
  -*- mode: compilation; default-directory: "~/LEARN/RDFa+XHTML/" -*-
  Compilation started at Fri Nov 16 11:56:50

  onsgmls -s --warning=all  minimal.xhtml
  
onsgmls:http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd:273:27:E: 
omitted tag minimization parameter can be omitted only if OMITTAG NO is 
specified
  onsgmls:http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd:275:8:E: 
character ":" invalid: only "CDATA", "ENTITIES", "ENTITY", "ID", "IDREF", 
"IDREFS", "NAME", "NAMES", "NMTOKEN", "NMTOKENS", "NOTATION", "NUMBER", 
"NUMBERS", "NUTOKEN", "NUTOKENS" and parameter separators allowed
  
onsgmls:http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd:289:49:E: 
omitted tag minimization parameter can be omitted only if OMITTAG NO is 
specified
  onsgmls:http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd:292:8:E: 
character ":" invalid: only "CDATA", "ENTITIES", "ENTITY", "ID", "IDREF", 
"IDREFS", "NAME", "NAMES", "NMTOKEN", "NMTOKENS", "NOTATION", "NUMBER", 
"NUMBERS", "NUTOKEN", "NUTOKENS" and parameter separators allowed
  
onsgmls:http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd:301:25:E: 
omitted tag minimization parameter can be omitted only if OMITTAG NO is 
specified
  onsgmls:http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd:303:8:E: 
character ":" invalid: only "CDATA", "ENTITIES", "ENTITY", "ID", "IDREF", 
"IDREFS", "NAME", 

[Desktop-packages] [Bug 1803604] Re: "Send -> Document as e-mail" in Writer / Calc does not work

2018-11-16 Thread Olivier Tilloy
I can observe the issue if I set the "Tools > Options > Internet >
E-mail" field to "/usr/bin/thunderbird". But if I unset the field
(blank) then LibreOffice calls xdg-email, which figures out the default
e-mail client as expected (assuming thunderbird is configured as your
default e-mail client).

Calling directly /usr/bin/thunderbird is blocked by the libreoffice-
senddoc apparmor profile.

I'm confirming the bug, but it's unlikely that it will get much
traction, given how easy it is to work around it by simply unsetting the
e-mail client in the options.

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

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

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

Title:
  "Send -> Document as e-mail" in Writer / Calc does not work

Status in libreoffice package in Ubuntu:
  Confirmed

Bug description:
  Description:  Linux Mint 18.3 Sylvia
  Release:  18.3
  LO: Version: 6.1.3.2
  Build-ID: 1:6.1.3~rc2-0ubuntu0.16.04.1

  In writer I have an open document. If I then want to send it:

  "File - send - document as e-mail"

  **Nothing happens**

  Same with send e-mail as open-document and word document. Only send
  with pdf opens at least the pdf dialogue. But then nothing happens.

  Path to thunderbird: /usr/bin/thunderbird
  Thunderbird opens if I use this path so the path seems correct. No error 
message received.

  Expect: Mail is opened and document attached. (which worked before)

  Update: Just checked in Ubuntu 18.04 and LO 6.06.2
  There it works as expected. Will check my other system again. Maybe it just 
does not work on my other system.

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

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


[Desktop-packages] [Bug 1803752] Re: HID inputs (mouse buttons and keyboard) stop responding when plug in DP monitor

2018-11-16 Thread Jonathan Polak
** Attachment added: "dmseg file"
   
https://bugs.launchpad.net/ubuntu-mate/+bug/1803752/+attachment/5213529/+files/dmesg

** Tags added: 18.10 cosmic

** Tags added: hid

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

** Also affects: mate-common (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  HID inputs (mouse buttons and keyboard) stop responding when plug in
  DP monitor

Status in ubuntu-mate:
  New
Status in mate-common package in Ubuntu:
  New
Status in xorg package in Ubuntu:
  New

Bug description:
  Ever since upgrading to 18.10 plugging in external monitors has been
  buggy.

  Device Lenovo T460s. Ubuntu-Mate 18.10.

  Plugging in External monitor using mini-display port causes keyboard
  to be unresponsive. Mouse buttons as well. though can still move mouse
  on screen. Plugging in and out using arndr sometimes resolves this.
  Notwithstanding, no smooth transition to multimonitor mode.

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

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


[Desktop-packages] [Bug 844833] Re: Libreoffice mail sender not set

2018-11-16 Thread Olivier Tilloy
This is no longer valid, that bug was fixed at some point in the past 7 (!) 
years.
The "Tools > Options > Internet > E-mail" field is unset (blank) by default, 
and this makes LibreOffice call xdg-email, which figures out the default e-mail 
client as expected.

** Changed in: libreoffice (Ubuntu)
   Status: Confirmed => Fix Released

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

Title:
  Libreoffice mail sender not set

Status in One Hundred Papercuts:
  Invalid
Status in libreoffice package in Ubuntu:
  Fix Released

Bug description:
  This is a simple bug, a real papercut.

  Actually : In the default Installation of Ubuntu, Libreoffice have an
  integrated button in the toolbar to send current document via e-mail.
  But if you click it, it doesn't work : e-mail software isn't set. We
  have to manually open Libreoffice, go in tools > Options > Internet
  E-mail and set "thunderbird" as e-mail software.

  Should be : On the default Ubuntu installation (since Oneiric),
  Thunderbird is the default mail software. So it should be used like
  that in Libreoffice. The libreoffice default mail software should be
  set to "thunderbird" by default, or even better (but maybe more
  difficult) to the default mail software in the system.

  ProblemType: Bug
  DistroRelease: Ubuntu 11.10
  Package: libreoffice (not installed)
  ProcVersionSignature: Ubuntu 3.0.0-10.16-generic 3.0.4
  Uname: Linux 3.0.0-10-generic x86_64
  Architecture: amd64
  Date: Thu Sep  8 15:56:05 2011
  InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Beta amd64 (20110901)
  ProcEnviron:
   PATH=(custom, no user)
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  SourcePackage: libreoffice
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1784485] Re: [ZenBook S UX391UA, Realtek ALC294, Mic, Internal] No sound at all

2018-11-16 Thread Karen Chaltikian
To add to the above: shutting down the laptop and then starting from
there in Ubuntu, as suggested in one of the workarounds above, actually
made the sound work

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

Title:
  [ZenBook S UX391UA, Realtek ALC294, Mic, Internal] No sound at all

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  Internal speaker - not sound at all
  Cable Headphonse - realy quiet disorted sound
  Bluetooth headphones - sound works fine

  On Windows 10 everything works fine.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  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
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  pmichalski   7964 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Jul 30 22:32:10 2018
  InstallationDate: Installed on 2018-07-17 (12 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=pl_PL.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaRecordingTest: ALSA recording test through plughw:PCH failed
  Symptom_Card: Wbudowany dźwięk - HDA Intel PCH
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gdm2988 F pulseaudio
pmichalski   7964 F pulseaudio
  Symptom_Jack: Mic, Internal
  Symptom_Type: No sound at all
  Title: [ZenBook S UX391UA, Realtek ALC294, Mic, Internal] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/18/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX391UA.204
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX391UA
  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.:bvrUX391UA.204:bd05/18/2018:svnASUSTeKCOMPUTERINC.:pnZenBookSUX391UA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX391UA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: ZenBook S
  dmi.product.name: ZenBook S UX391UA
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

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

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


[Desktop-packages] [Bug 1802208] Re: Reports won't open

2018-11-16 Thread Olivier Tilloy
I rebuilt libreoffice 6.0.7 for bionic with the debian patch that sets
jdk.net.URLClassPath.disableClassPathURLCheck to true, and verified that
this was built against a version of the JDK that has the patch to honour
that flag, but this hasn't fixed the issue.

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

Title:
  Reports won't open

Status in libreoffice package in Ubuntu:
  Invalid
Status in libreoffice source package in Xenial:
  Confirmed
Status in libreoffice source package in Bionic:
  Confirmed

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

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

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

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

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

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

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


[Desktop-packages] [Bug 1803743] [NEW] Иногда пропадает звук. Помогает только перезагрузка.

2018-11-16 Thread Zepem
Public bug reported:

Здравствуйте!
С переходом на 16.04 lts на моем компьютере иногда стал пропадать звук.  
Определить по какой причине так и не получилось. Если звук пропадает то 
помогает только перезагрузка. Обращался на форум, но безрезультатно 
https://forum.ubuntu.ru/index.php?topic=278602.0   Пару раз переустанавливал 
Убунту 16.04 и один раз Убунту 18.04 - но проблема осталась. Востанавливал по 
инструкции https://help.ubuntu.com/community/SoundTroubleshootingProcedure. 
Первых два шага не помогают. Проблема остается и звук появляется только при 
перезагрузке. Третий шаг это задать вопрос здесь, что я собственно и делаю.  В 
третьем шаге предлагается специальный скрипт, который собирает всю необходимую 
информацию о системе и публикует ее на сайте. вот ссылка на отчет о моей 
системе в момент когда звук отсутствует 
http://www.alsa-project.org/db/?f=e3512ce403985434442eb1d4b4905e5bcab76ac8 
Помогите, пожалуйста.

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

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

Title:
  Иногда пропадает звук. Помогает только перезагрузка.

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  Здравствуйте!
  С переходом на 16.04 lts на моем компьютере иногда стал пропадать звук.  
Определить по какой причине так и не получилось. Если звук пропадает то 
помогает только перезагрузка. Обращался на форум, но безрезультатно 
https://forum.ubuntu.ru/index.php?topic=278602.0   Пару раз переустанавливал 
Убунту 16.04 и один раз Убунту 18.04 - но проблема осталась. Востанавливал по 
инструкции https://help.ubuntu.com/community/SoundTroubleshootingProcedure. 
Первых два шага не помогают. Проблема остается и звук появляется только при 
перезагрузке. Третий шаг это задать вопрос здесь, что я собственно и делаю.  В 
третьем шаге предлагается специальный скрипт, который собирает всю необходимую 
информацию о системе и публикует ее на сайте. вот ссылка на отчет о моей 
системе в момент когда звук отсутствует 
http://www.alsa-project.org/db/?f=e3512ce403985434442eb1d4b4905e5bcab76ac8 
  Помогите, пожалуйста.

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

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


[Desktop-packages] [Bug 1799430] Re: Icon dock visible on lock screen

2018-11-16 Thread Dmitry Korzhevin
Created some photos of this issue:

https://photos.app.goo.gl/YeryTjUuLvDE8GxR8

Issue still exist with all updates installed.

Dmitry

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

Title:
  Icon dock visible on lock screen

Status in gnome-shell-extension-dashtodock package in Ubuntu:
  Confirmed
Status in mutter package in Ubuntu:
  Confirmed

Bug description:
  When locking the machine with alt-L the icon dock is still visible.

  After Login, the dock does not get adjusted to the top menu.

  In rare cases, the dock does not respond any more. This requires a
  reboot of the machine

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: mutter 3.30.1-1
  ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12
  Uname: Linux 4.18.0-10-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Oct 23 12:59:27 2018
  InstallationDate: Installed on 2018-04-30 (176 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  SourcePackage: mutter
  UpgradeStatus: Upgraded to cosmic on 2018-10-20 (2 days ago)

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

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


[Desktop-packages] [Bug 1799001] Re: Theming does not work on LXQt

2018-11-16 Thread Olivier Tilloy
@Chris: the output of the dpkg command you provided in #3 suggests not
all the packages were built at the time you tried it (you only installed
the architecture-independent packages from the update), can you try
again and confirm that libreoffice uses the breeze theme by default, on
Lubuntu/LXQt?

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

Title:
  Theming does not work on LXQt

Status in libreoffice package in Ubuntu:
  Fix Released
Status in libreoffice source package in Cosmic:
  Fix Committed

Bug description:
  [Impact]

  Without this change, LibreOffice does not correctly use the Breeze
  theme, which is needed for consistency with the rest of the Lubuntu,
  LXQt-based desktop. At times, it is even hard to use because of the
  inconsistent theming which can hide buttons at times.

  [Test Case]

  Update to the version of LibreOffice with this patch and open it on a
  Lubuntu 18.10 installation. It should use the Breeze theming rather
  than the stock GTK theming on startup.

  [Regression Potential]

  Little to none. If for some reason the criteria that is used to check
  for the LXQt desktop no longer works, which is unlikely in a stable
  release, this will no longer work.

  [Other Info]

  I submitted these upstream (as my first patches \o/):
  https://gerrit.libreoffice.org/61641
  https://gerrit.libreoffice.org/61751

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

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


[Desktop-packages] [Bug 1448778] Re: Evince fails to display some fonts (some font thing failed)

2018-11-16 Thread Antoine Amarilli
I agree that this bug is super confusing: when apparmor prevents evince
from accessing a font (in my case, because of some folders in /usr/share
having been symlinked to a different partition), there is no visible
error message (except "some font thing failed" in the console log) and
the text with the affected font is silently not rendered at all.

I agree that at the very least evince should have a visible warning that
some document content was not rendered.

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

Title:
  Evince fails to display some fonts (some font thing failed)

Status in evince package in Ubuntu:
  Invalid

Bug description:
  Dear experts,

  Since the upgrade to Ubuntu 15.04, evince fails to display some fonts
  of most of my latex pdfs. I attached an example of the pdf rendered by
  evince, and a screenshot of what it's supposed to look like. The
  console is spammed with errors:

  'some font thing failed'

  The pdf display correctly with xpdf and  okular.

  Thanks

  Description:  Ubuntu 15.04
  Release:  15.04
  evince:
Installed: 3.14.2-0ubuntu2
Candidate: 3.14.2-0ubuntu2
Version table:
   *** 3.14.2-0ubuntu2 0
  500 http://ftp.belnet.be/ubuntu.com/ubuntu/ vivid/main amd64 Packages
  100 /var/lib/dpkg/status

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: evince 3.14.2-0ubuntu2
  ProcVersionSignature: Ubuntu 3.19.0-15.15-generic 3.19.3
  Uname: Linux 3.19.0-15-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.17.2-0ubuntu1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sun Apr 26 23:15:02 2015
  SourcePackage: evince
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1803604] Re: "Send -> Document as e-mail" in Writer / Calc does not work

2018-11-16 Thread Peter Ludwig
** Description changed:

  Description:  Linux Mint 18.3 Sylvia
  Release:  18.3
  LO: Version: 6.1.3.2
  Build-ID: 1:6.1.3~rc2-0ubuntu0.16.04.1
  
  In writer I have an open document. If I then want to send it:
  
  "File - send - document as e-mail"
  
  **Nothing happens**
  
  Same with send e-mail as open-document and word document. Only send with
  pdf opens at least the pdf dialogue. But then nothing happens.
  
  Path to thunderbird: /usr/bin/thunderbird
  Thunderbird opens if I use this path so the path seems correct. No error 
message received.
  
  Expect: Mail is opened and document attached. (which worked before)
+ 
+ Update: Just checked in Ubuntu 18.04 and LO 6.06.2
+ There it works as expected. Will check my other system again. Maybe it just 
does not work on my other system.

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

Title:
  "Send -> Document as e-mail" in Writer / Calc does not work

Status in libreoffice package in Ubuntu:
  New

Bug description:
  Description:  Linux Mint 18.3 Sylvia
  Release:  18.3
  LO: Version: 6.1.3.2
  Build-ID: 1:6.1.3~rc2-0ubuntu0.16.04.1

  In writer I have an open document. If I then want to send it:

  "File - send - document as e-mail"

  **Nothing happens**

  Same with send e-mail as open-document and word document. Only send
  with pdf opens at least the pdf dialogue. But then nothing happens.

  Path to thunderbird: /usr/bin/thunderbird
  Thunderbird opens if I use this path so the path seems correct. No error 
message received.

  Expect: Mail is opened and document attached. (which worked before)

  Update: Just checked in Ubuntu 18.04 and LO 6.06.2
  There it works as expected. Will check my other system again. Maybe it just 
does not work on my other system.

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

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


[Desktop-packages] [Bug 1796777] Re: thunderbird download settings are inconsistent

2018-11-16 Thread Paul White
** Also affects: thunderbird via
   https://bugzilla.mozilla.org/show_bug.cgi?id=1507804
   Importance: Unknown
   Status: Unknown

** Summary changed:

- thunderbird download settings are inconsistent
+ Download settings are inconsistent between create and move

** Summary changed:

- Download settings are inconsistent between create and move
+ Download folder settings are inconsistent between create and move

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

Title:
  Download folder settings are inconsistent between create and move

Status in Mozilla Thunderbird:
  Unknown
Status in thunderbird package in Ubuntu:
  Confirmed

Bug description:
  When "message synchronizing" is set to download messages from an IMAP
  account, a newly created folder under the inbox is automatically set
  to download messages as well, but when that folder is then moved
  (using the mouse) under some other folder, the "download" check box on
  the panel "Items for offline use" is cleared.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: thunderbird 1:52.9.1+build3-0ubuntu0.16.04.1
  ProcVersionSignature: Ubuntu 4.15.0-36.39~16.04.1-generic 4.15.18
  Uname: Linux 4.15.0-36-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  AddonCompatCheckDisabled: False
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  humphrey   2434 F pulseaudio
   /dev/snd/controlC1:  humphrey   2434 F pulseaudio
  BuildID: 20180710085647
  Channel: Unavailable
  CurrentDesktop: Unity
  Date: Tue Oct  9 11:41:44 2018
  ExecutablePath: /usr/lib/thunderbird/thunderbird
  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 2017-12-13 (299 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  IpRoute:
   default via 192.168.1.1 dev enp4s0  proto static  metric 100 
   169.254.0.0/16 dev enp4s0  scope link  metric 1000 
   192.168.1.0/24 dev enp4s0  proto kernel  scope link  src 192.168.1.101  
metric 100
  IwConfig:
   lono wireless extensions.
   
   enp4s0no wireless extensions.
  Locales: extensions.sqlite corrupt or missing
  MostRecentCrashID: bp-3f3dab64-e8aa-4350-afd1-b05560180506
  Plugins: Shockwave Flash - /usr/lib/flashplugin-installer/libflashplayer.so
  PrefSources:
   prefs.js
   
[Profile]/extensions/{e2fda1a4-762b-4020-b5ad-a41df1933103}/defaults/preferences/lightning.js
  Profiles: Profile0 (Default) - LastVersion=52.9.1/20180710085647 (In use)
  RfKill:
   
  RunningIncompatibleAddons: False
  SourcePackage: thunderbird
  Themes: extensions.sqlite corrupt or missing
  UpgradeStatus: Upgraded to xenial on 2018-08-28 (41 days ago)
  dmi.bios.date: 06/22/2010
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.3.0
  dmi.board.name: 0N185P
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A02
  dmi.chassis.type: 3
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.3.0:bd06/22/2010:svnDellInc.:pnVostro420Series:pvr:rvnDellInc.:rn0N185P:rvrA02:cvnDellInc.:ct3:cvr:
  dmi.product.name: Vostro 420 Series
  dmi.sys.vendor: Dell Inc.

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

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


[Desktop-packages] [Bug 1796777] Re: thunderbird download settings are inconsistent

2018-11-16 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

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

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

Title:
  Download folder settings are inconsistent between create and move

Status in Mozilla Thunderbird:
  Unknown
Status in thunderbird package in Ubuntu:
  Confirmed

Bug description:
  When "message synchronizing" is set to download messages from an IMAP
  account, a newly created folder under the inbox is automatically set
  to download messages as well, but when that folder is then moved
  (using the mouse) under some other folder, the "download" check box on
  the panel "Items for offline use" is cleared.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: thunderbird 1:52.9.1+build3-0ubuntu0.16.04.1
  ProcVersionSignature: Ubuntu 4.15.0-36.39~16.04.1-generic 4.15.18
  Uname: Linux 4.15.0-36-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  AddonCompatCheckDisabled: False
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  humphrey   2434 F pulseaudio
   /dev/snd/controlC1:  humphrey   2434 F pulseaudio
  BuildID: 20180710085647
  Channel: Unavailable
  CurrentDesktop: Unity
  Date: Tue Oct  9 11:41:44 2018
  ExecutablePath: /usr/lib/thunderbird/thunderbird
  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 2017-12-13 (299 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  IpRoute:
   default via 192.168.1.1 dev enp4s0  proto static  metric 100 
   169.254.0.0/16 dev enp4s0  scope link  metric 1000 
   192.168.1.0/24 dev enp4s0  proto kernel  scope link  src 192.168.1.101  
metric 100
  IwConfig:
   lono wireless extensions.
   
   enp4s0no wireless extensions.
  Locales: extensions.sqlite corrupt or missing
  MostRecentCrashID: bp-3f3dab64-e8aa-4350-afd1-b05560180506
  Plugins: Shockwave Flash - /usr/lib/flashplugin-installer/libflashplayer.so
  PrefSources:
   prefs.js
   
[Profile]/extensions/{e2fda1a4-762b-4020-b5ad-a41df1933103}/defaults/preferences/lightning.js
  Profiles: Profile0 (Default) - LastVersion=52.9.1/20180710085647 (In use)
  RfKill:
   
  RunningIncompatibleAddons: False
  SourcePackage: thunderbird
  Themes: extensions.sqlite corrupt or missing
  UpgradeStatus: Upgraded to xenial on 2018-08-28 (41 days ago)
  dmi.bios.date: 06/22/2010
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.3.0
  dmi.board.name: 0N185P
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A02
  dmi.chassis.type: 3
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.3.0:bd06/22/2010:svnDellInc.:pnVostro420Series:pvr:rvnDellInc.:rn0N185P:rvrA02:cvnDellInc.:ct3:cvr:
  dmi.product.name: Vostro 420 Series
  dmi.sys.vendor: Dell Inc.

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

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


[Desktop-packages] [Bug 1796777] Re: thunderbird download settings are inconsistent

2018-11-16 Thread Paul White
Confirmed using Ubuntu 19.04 (dev) and Thunderbird 60.2.1
Reported Upstream: https://bugzilla.mozilla.org/show_bug.cgi?id=1507804

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

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

Title:
  Download folder settings are inconsistent between create and move

Status in Mozilla Thunderbird:
  Unknown
Status in thunderbird package in Ubuntu:
  Confirmed

Bug description:
  When "message synchronizing" is set to download messages from an IMAP
  account, a newly created folder under the inbox is automatically set
  to download messages as well, but when that folder is then moved
  (using the mouse) under some other folder, the "download" check box on
  the panel "Items for offline use" is cleared.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: thunderbird 1:52.9.1+build3-0ubuntu0.16.04.1
  ProcVersionSignature: Ubuntu 4.15.0-36.39~16.04.1-generic 4.15.18
  Uname: Linux 4.15.0-36-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  AddonCompatCheckDisabled: False
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  humphrey   2434 F pulseaudio
   /dev/snd/controlC1:  humphrey   2434 F pulseaudio
  BuildID: 20180710085647
  Channel: Unavailable
  CurrentDesktop: Unity
  Date: Tue Oct  9 11:41:44 2018
  ExecutablePath: /usr/lib/thunderbird/thunderbird
  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 2017-12-13 (299 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  IpRoute:
   default via 192.168.1.1 dev enp4s0  proto static  metric 100 
   169.254.0.0/16 dev enp4s0  scope link  metric 1000 
   192.168.1.0/24 dev enp4s0  proto kernel  scope link  src 192.168.1.101  
metric 100
  IwConfig:
   lono wireless extensions.
   
   enp4s0no wireless extensions.
  Locales: extensions.sqlite corrupt or missing
  MostRecentCrashID: bp-3f3dab64-e8aa-4350-afd1-b05560180506
  Plugins: Shockwave Flash - /usr/lib/flashplugin-installer/libflashplayer.so
  PrefSources:
   prefs.js
   
[Profile]/extensions/{e2fda1a4-762b-4020-b5ad-a41df1933103}/defaults/preferences/lightning.js
  Profiles: Profile0 (Default) - LastVersion=52.9.1/20180710085647 (In use)
  RfKill:
   
  RunningIncompatibleAddons: False
  SourcePackage: thunderbird
  Themes: extensions.sqlite corrupt or missing
  UpgradeStatus: Upgraded to xenial on 2018-08-28 (41 days ago)
  dmi.bios.date: 06/22/2010
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.3.0
  dmi.board.name: 0N185P
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A02
  dmi.chassis.type: 3
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.3.0:bd06/22/2010:svnDellInc.:pnVostro420Series:pvr:rvnDellInc.:rn0N185P:rvrA02:cvnDellInc.:ct3:cvr:
  dmi.product.name: Vostro 420 Series
  dmi.sys.vendor: Dell Inc.

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

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


[Desktop-packages] [Bug 1799001] Re: Theming does not work on LXQt

2018-11-16 Thread Hans P Möller
I did see a change. Icons are changed from Tango (previous default) to
Breeze (new default).

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

Title:
  Theming does not work on LXQt

Status in libreoffice package in Ubuntu:
  Fix Released
Status in libreoffice source package in Cosmic:
  Fix Committed

Bug description:
  [Impact]

  Without this change, LibreOffice does not correctly use the Breeze
  theme, which is needed for consistency with the rest of the Lubuntu,
  LXQt-based desktop. At times, it is even hard to use because of the
  inconsistent theming which can hide buttons at times.

  [Test Case]

  Update to the version of LibreOffice with this patch and open it on a
  Lubuntu 18.10 installation. It should use the Breeze theming rather
  than the stock GTK theming on startup.

  [Regression Potential]

  Little to none. If for some reason the criteria that is used to check
  for the LXQt desktop no longer works, which is unlikely in a stable
  release, this will no longer work.

  [Other Info]

  I submitted these upstream (as my first patches \o/):
  https://gerrit.libreoffice.org/61641
  https://gerrit.libreoffice.org/61751

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

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


[Desktop-packages] [Bug 1797373] Re: 3D slide transitions don't work at all or tear when played

2018-11-16 Thread Bug Watch Updater
Launchpad has imported 1 comments from the remote bug at
https://bugs.documentfoundation.org/show_bug.cgi?id=121463.

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


On 2018-11-16T12:51:07+00:00 Olivier Tilloy wrote:

Description:
(initially reported on ubuntu: https://launchpad.net/bugs/1797373)

Normal effects *work*: Wipe, Wheel, Uncover, Bars, Checkers, Shape, Box,
Wedge, Venetian, Fade, Cut, Cover, Dissolve, Comb, Push, Split,
Diagonal.

3D-Effects *don’t work*: Tiles, Cube, Circles, Helix, Fall, Turn Around,
Iris, Turn Down, Rochade, 3D Venetian, Static, Fine Dissolve, Vortex,
Ripple, Glitter, Honeycomb, Newsflash.

Normal effects works perfectly, 3D-effects either don't work at all or when 
played with F5, shows a flashing screen.
Tearing is also seen. Hardware acceleration is checked.

Steps to Reproduce:
1. Create a new presentation in impress
2. Apply 3D transitions to slides
3. Start the slideshow with F5

Actual Results:
Some 3D transitions don't work at all (remain black), some flash/tear quite 
visibly.

Expected Results:
3D transitions are rendered smoothly.


Reproducible: Always


User Profile Reset: No


OpenGL enabled: Yes

Additional Info:

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


** Changed in: df-libreoffice
   Status: Unknown => New

** Changed in: df-libreoffice
   Importance: Unknown => Medium

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

Title:
  3D slide transitions don't work at all or tear when played

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

Bug description:
  Normal effects *work*: Wipe, Wheel, Uncover, Bars, Checkers, Shape,
  Box, Wedge, Venetian, Fade, Cut, Cover, Dissolve, Comb, Push, Split,
  Diagonal.

  3D-Effects *don’t work*: Tiles, Cube, Circles, Helix, Fall, Turn
  Around, Iris, Turn Down, Rochade, 3D Venetian, Static, Fine Dissolve,
  Vortex, Ripple, Glitter, Honeycomb, Newsflash.

  Normal effects works perfectly, 3D-effects either don't work at all or when 
played with F5, shows a flashing screen.
  Tearing is also seen. Hardware acceleration is checked.

  
  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: libreoffice 1:6.0.6-0ubuntu0.18.04.1
  ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18
  Uname: Linux 4.15.0-36-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.4
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Oct 11 17:59:04 2018
  InstallationDate: Installed on 2017-10-28 (348 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  ProcEnviron:
   LANGUAGE=en_IN:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_IN
   SHELL=/bin/bash
  SourcePackage: libreoffice
  UpgradeStatus: Upgraded to bionic on 2018-09-27 (14 days ago)

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

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


[Desktop-packages] [Bug 1771880] Re: Seahorse unable to import pkcs12 certificates

2018-11-16 Thread Cieniek
For what I have tested this bug affects also Network Manager - can't set
certificates for WPA(2) Enterprise and/or 802.1X.

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

Title:
  Seahorse unable to import pkcs12 certificates

Status in gnome-keyring package in Ubuntu:
  Confirmed
Status in seahorse package in Ubuntu:
  Confirmed
Status in gnome-keyring package in Fedora:
  New

Bug description:
  seahorse 3.20.0-5 / gnome-keyring 3.28.0.2-1ubuntu1.18.04.1 / Ubuntu
  18.04 LTS / GNOME 3.28.1

  When trying to import a certificate into seahorse/gnome-keyring on
  Ubuntu 18.04, seahorse GUI application shows the 'import' button
  greyed out, while mouse hovering the "import" button shows the message
  "Cannot import because there are no compatible importers".

  This problem doesn't occur on Ubuntu 16.04 LTS (Seahorse 3.18.0), as
  I've just tested on my wife's laptop, but happens in my Laptop with
  Ubuntu 18.04 LTS (Seahorse 3.20.0-5).

  Because that problem, it's not possible to digitally sign documents
  with LibreOffice.

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

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


[Desktop-packages] [Bug 1803696] Re: Status of togglable menu entries is very hard to distinguish with gen VCL plugin

2018-11-16 Thread Bug Watch Updater
Launchpad has imported 1 comments from the remote bug at
https://bugs.documentfoundation.org/show_bug.cgi?id=121461.

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


On 2018-11-16T12:35:57+00:00 Olivier Tilloy wrote:

Description:
(initially reported in Ubuntu: https://launchpad.net/bugs/1803696)

Some menu items like "Snap to Snap Guides" can be toggled, but it's very
hard to understand in which status they are because the outline around
the icon is almost invisible.

Steps to Reproduce:
Run LibreOffice Draw with SAL_USE_VCLPLUGIN=gen, toggle the "View > Snap Guides 
> Snap To Snap Guides" menu item.

Actual Results:
When re-opening the "View > Snap Guides" menu, it is very hard to tell whether 
the "Snap To Snap Guides" entry is checked or not. When it is checked, there is 
a thin, almost invisible outline around the icon.

Expected Results:
When re-opening the "View > Snap Guides" menu, it is obvious whether the "Snap 
To Snap Guides" entry is checked or not.


Reproducible: Always


User Profile Reset: No


Additional Info:

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


** Changed in: df-libreoffice
   Status: Unknown => New

** Changed in: df-libreoffice
   Importance: Unknown => Low

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

Title:
  Status of togglable menu entries is very hard to distinguish with gen
  VCL plugin

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

Bug description:
  Some buttons like "Snap to Snap Guides" can be toggled, but it's very
  hard to understand in which status they are.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: libreoffice (not installed)
  ProcVersionSignature: Ubuntu 4.15.0-39.42-generic 4.15.18
  Uname: Linux 4.15.0-39-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  CurrentDesktop: LXDE
  Date: Fri Nov 16 12:21:50 2018
  InstallationDate: Installed on 2018-10-31 (15 days ago)
  InstallationMedia: Lubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  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/1803696/+subscriptions

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


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

2018-11-16 Thread Ahmet İpkin
** Project changed: linuxmint => firefox (Ubuntu)

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

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

Title:
  Firefox dropdowns in wrong location

Status in Linux Mint:
  New
Status in firefox package in Ubuntu:
  New

Bug description:
  On Mint 17.3 Cinnamon 64bit.

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

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

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

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

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

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

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

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


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

2018-11-16 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

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

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

Title:
  Firefox dropdowns in wrong location

Status in Linux Mint:
  New
Status in firefox package in Ubuntu:
  New

Bug description:
  On Mint 17.3 Cinnamon 64bit.

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

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

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

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

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

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

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

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


[Desktop-packages] [Bug 1800465] Re: Vulkan error when using NVIDIA-Prime

2018-11-16 Thread Jaap Buurman
I have the exact same bug. This one seems to be related:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-
drivers-390/+bug/1769857

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

Title:
  Vulkan error when using NVIDIA-Prime

Status in NVIDIA Drivers Ubuntu:
  New
Status in nvidia-graphics-drivers-390 package in Ubuntu:
  Confirmed
Status in nvidia-prime package in Ubuntu:
  Confirmed

Bug description:
  After installing Ubuntu 18.10 and the Nvidia driver + Vulkan-Utils,
  switching to NVIDIA and then running vulkaninfo or vulkan-cube works
  perfectly.

  But when you reboot and update, then switch to Intel, then back to Nvidia, 
all Vulkan programs give an 
  "Assertion `!err' failed."

  Vulkaninfo:

  ===
  Presentable Surfaces:
  =
  GPU id   : 0 (GeForce GTX 960M)
  Surface type : VK_KHR_xcb_surface
  vulkaninfo: 
/build/vulkan-tools-ZnxIl9/vulkan-tools-1.1.82.0+dfsg1/vulkaninfo/vulkaninfo.c:1253:
 AppDumpSurfaceFormats: Assertion `!err' failed.
  Annullato (core dump creato)

  
  Vulkancube:
  vulkan-cube: 
/build/vulkan-tools-ZnxIl9/vulkan-tools-1.1.82.0+dfsg1/cube/cube.c:3416: 
demo_init_vk_swapchain: Assertion `!err' failed.
  Annullato (core dump creato)

  
  I still have not found a workaround for that, the only way to get it working 
again is to reinstall everything. 

  - Install Ubuntu 18.10
  - Install proprietary 390 NVIDIA drivers
  - Switch NVIDIA-Prime to NVIDIA
  - Testing the vulkan capabilities works
  - Updating the system then switching to intel
  - Reboot
  - Switch to nvida
  - Now all Vulkan programs when using NVIDIA give that error

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

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


[Desktop-packages] [Bug 1803706] [NEW] yaru theme long application menus overflowing

2018-11-16 Thread Sandor
Public bug reported:

Hi I am not a developer, only a user.

In 18.10 Cosmic with new Yaru theme: any application with long menus are 
overflowing and covering the menubar making impossible to slide mouse to the 
next menu. It affects long sub-menus too. It mainly affects LibreOffice as it 
has got quite large menus but it is also present in CherryTree app and I guess 
in any other.
When the menu is not wider than the available vertical area of the screen than 
they show up nicely aligned under the menu toolbar but when it is too large: it 
might even run edge to edge vertically.

(As for Design: probably a slightly different colour at the end of these
long menus would make them more visible where the arrows are.)

Thanks

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

** Attachment added: "Yaru-theme-issue-picture"
   
https://bugs.launchpad.net/bugs/1803706/+attachment/5213483/+files/LibreOffice-YaruTheme-overflow-menus-1.png

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

Title:
  yaru theme long application menus overflowing

Status in yaru-theme package in Ubuntu:
  New

Bug description:
  Hi I am not a developer, only a user.

  In 18.10 Cosmic with new Yaru theme: any application with long menus are 
overflowing and covering the menubar making impossible to slide mouse to the 
next menu. It affects long sub-menus too. It mainly affects LibreOffice as it 
has got quite large menus but it is also present in CherryTree app and I guess 
in any other.
  When the menu is not wider than the available vertical area of the screen 
than they show up nicely aligned under the menu toolbar but when it is too 
large: it might even run edge to edge vertically.

  (As for Design: probably a slightly different colour at the end of
  these long menus would make them more visible where the arrows are.)

  Thanks

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/yaru-theme/+bug/1803706/+subscriptions

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


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

2018-11-16 Thread Launchpad Bug Tracker
You have been subscribed to a public bug:

On Mint 17.3 Cinnamon 64bit.

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

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

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

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

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

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

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

-- 
Firefox dropdowns in wrong location
https://bugs.launchpad.net/bugs/1603430
You received this bug notification because you are a member of Desktop 
Packages, which is subscribed to firefox 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 1797373] Re: 3D slide transitions don't work at all or tear when played

2018-11-16 Thread Olivier Tilloy
I reported the bug upstream:
https://bugs.documentfoundation.org/show_bug.cgi?id=121463

** Summary changed:

- 3D slide transitions don't work at all or when played there is flashing screen
+ 3D slide transitions don't work at all or tear when played

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

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

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

** Bug watch added: Document Foundation Bugzilla #121463
   https://bugs.documentfoundation.org/show_bug.cgi?id=121463

** Also affects: df-libreoffice via
   https://bugs.documentfoundation.org/show_bug.cgi?id=121463
   Importance: Unknown
   Status: Unknown

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

Title:
  3D slide transitions don't work at all or tear when played

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

Bug description:
  Normal effects *work*: Wipe, Wheel, Uncover, Bars, Checkers, Shape,
  Box, Wedge, Venetian, Fade, Cut, Cover, Dissolve, Comb, Push, Split,
  Diagonal.

  3D-Effects *don’t work*: Tiles, Cube, Circles, Helix, Fall, Turn
  Around, Iris, Turn Down, Rochade, 3D Venetian, Static, Fine Dissolve,
  Vortex, Ripple, Glitter, Honeycomb, Newsflash.

  Normal effects works perfectly, 3D-effects either don't work at all or when 
played with F5, shows a flashing screen.
  Tearing is also seen. Hardware acceleration is checked.

  
  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: libreoffice 1:6.0.6-0ubuntu0.18.04.1
  ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18
  Uname: Linux 4.15.0-36-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.4
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Oct 11 17:59:04 2018
  InstallationDate: Installed on 2017-10-28 (348 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  ProcEnviron:
   LANGUAGE=en_IN:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_IN
   SHELL=/bin/bash
  SourcePackage: libreoffice
  UpgradeStatus: Upgraded to bionic on 2018-09-27 (14 days ago)

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

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


[Desktop-packages] [Bug 1188569] Re: Some keyboard shortcuts randomly stop working

2018-11-16 Thread Khurshid Alam
Media keys not working is different issue, patch is only for custom
keyboard shortcuts randomly not working after getting back from lock
screen.

About media keys I have tested 12 different machines, but I can't
reproduce. For me play/pause have always worked even before the patch.

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

Title:
  Some keyboard shortcuts randomly stop working

Status in GNOME Shell:
  New
Status in Unity:
  Confirmed
Status in unity package in Ubuntu:
  Invalid
Status in unity-settings-daemon package in Ubuntu:
  Confirmed

Bug description:
  Hi,
  Certain shortcuts randomly stops working in my computer. They are Super+s 
(workspace switcher), Super+Up (switch to workspace above) and Super+Down 
(switch to workspace below). Other shortcuts work fine.

  A few notes that might help:
  1- Reassigning shortcuts make them work again except for Super+s.
  2- Rebooting make shortcuts work.
  3- I have been using these shortcuts with many previous ubuntu versions and 
my preferences are old.
  4- I am not sure of certain steps that produces the problem. The shortcuts 
sometimes stop working but once they stop, they do not work unless I reassign 
them or reboot.

  I am using Ubuntu 13.04.

  Thank you

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: unity 7.0.0daily13.04.18~13.04-0ubuntu1
  ProcVersionSignature: Ubuntu 3.8.0-23.34-generic 3.8.11
  Uname: Linux 3.8.0-23-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.9.2-0ubuntu8.1
  Architecture: amd64
  CompizPlugins: 
[core,composite,opengl,compiztoolbox,decor,regex,grid,mousepoll,place,wall,snap,resize,vpswitch,session,animation,gnomecompat,imgpng,commands,move,workarounds,fade,unitymtgrabhandles,expo,scale,ezoom,unityshell]
  Date: Fri Jun  7 13:40:06 2013
  InstallationDate: Installed on 2013-05-27 (11 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  MarkForUpload: True
  SourcePackage: unity
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1469163] Re: Missing characters on slide text/title

2018-11-16 Thread Olivier Tilloy
I cannot reproduce the problem here, in a stock Ubuntu 16.04 VM.

** Summary changed:

- Missing charachters on slide text/title
+ Missing characters on slide text/title

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

Title:
  Missing characters on slide text/title

Status in libreoffice package in Ubuntu:
  Confirmed

Bug description:
  Opening an existing document (from a previous version of libreoffice,
  two years old), clicking on the text to edit, after a few milliseconds
  some of the letters disappear. The disappeared letters do not have any
  special formatting. In presentation mode (F5) the letters appear
  correctly.

  See the attached documents (the slides and the snapshot).

  Here on (K)ubuntu 14.04 64bit

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: libreoffice-impress 1:4.2.8-0ubuntu2
  ProcVersionSignature: Ubuntu 3.13.0-55.94-generic 3.13.11-ckt20
  Uname: Linux 3.13.0-55-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.11
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Fri Jun 26 14:32:08 2015
  InstallationDate: Installed on 2013-08-01 (694 days ago)
  InstallationMedia: Kubuntu 12.04.2 LTS "Precise Pangolin" - Release amd64 
(20130214)
  SourcePackage: libreoffice
  UpgradeStatus: Upgraded to trusty on 2014-04-18 (434 days ago)

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

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


[Desktop-packages] [Bug 1803696] Re: Status of togglable menu entries is very hard to distinguish with gen VCL plugin

2018-11-16 Thread Olivier Tilloy
I reported the bug upstream:
https://bugs.documentfoundation.org/show_bug.cgi?id=121461.

** Bug watch added: Document Foundation Bugzilla #121461
   https://bugs.documentfoundation.org/show_bug.cgi?id=121461

** Also affects: df-libreoffice via
   https://bugs.documentfoundation.org/show_bug.cgi?id=121461
   Importance: Unknown
   Status: Unknown

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

Title:
  Status of togglable menu entries is very hard to distinguish with gen
  VCL plugin

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

Bug description:
  Some buttons like "Snap to Snap Guides" can be toggled, but it's very
  hard to understand in which status they are.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: libreoffice (not installed)
  ProcVersionSignature: Ubuntu 4.15.0-39.42-generic 4.15.18
  Uname: Linux 4.15.0-39-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  CurrentDesktop: LXDE
  Date: Fri Nov 16 12:21:50 2018
  InstallationDate: Installed on 2018-10-31 (15 days ago)
  InstallationMedia: Lubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  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/1803696/+subscriptions

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


[Desktop-packages] [Bug 1803696] Re: Togglable buttons status is very hard to see

2018-11-16 Thread Olivier Tilloy
Confirmed, the outline around the icon is almost invisible, making it
really hard to tell whether the option is checked.

This is with the generic VCL plugin. This can be observed on a stock
ubuntu desktop by running:

SAL_USE_VCLPLUGIN=gen libreoffice --draw

** Summary changed:

- Togglable buttons status is very hard to see
+ Status of togglable menu entries is very hard to distinguish with gen VCL 
plugin

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

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

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

Title:
  Status of togglable menu entries is very hard to distinguish with gen
  VCL plugin

Status in libreoffice package in Ubuntu:
  Confirmed

Bug description:
  Some buttons like "Snap to Snap Guides" can be toggled, but it's very
  hard to understand in which status they are.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: libreoffice (not installed)
  ProcVersionSignature: Ubuntu 4.15.0-39.42-generic 4.15.18
  Uname: Linux 4.15.0-39-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  CurrentDesktop: LXDE
  Date: Fri Nov 16 12:21:50 2018
  InstallationDate: Installed on 2018-10-31 (15 days ago)
  InstallationMedia: Lubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  SourcePackage: libreoffice
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1759916] Re: black screen after logon

2018-11-16 Thread Daniel van Vugt
It looks like this bug was reported before the official release of
18.04. Can you please update the system and tell us if the bug still
occurs?


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

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

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

Title:
  black screen after logon

Status in Ubuntu:
  Incomplete

Bug description:
  black screen after logon

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu5
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  Uname: Linux 4.15.0-13-generic x86_64
  ApportVersion: 2.20.9-0ubuntu2
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Thu Mar 29 19:41:21 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA 
controller])
 Subsystem: Lenovo HD Graphics 5500 [17aa:3824]
  InstallationDate: Installed on 2015-12-14 (836 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  MachineType: LENOVO 80K6
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-13-generic 
root=UUID=73fd1edc-d964-40d3-a1dd-b1ca4118cce6 ro quiet splash vt.handoff=1
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/19/2015
  dmi.bios.vendor: LENOVO
  dmi.bios.version: C2CN17WW(V1.03)
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: Lenovo Z51-70
  dmi.board.vendor: LENOVO
  dmi.board.version: No DPK
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo Z51-70
  dmi.modalias: 
dmi:bvnLENOVO:bvrC2CN17WW(V1.03):bd03/19/2015:svnLENOVO:pn80K6:pvrLenovoZ51-70:rvnLENOVO:rnLenovoZ51-70:rvrNoDPK:cvnLENOVO:ct10:cvrLenovoZ51-70:
  dmi.product.family: IDEAPAD
  dmi.product.name: 80K6
  dmi.product.version: Lenovo Z51-70
  dmi.sys.vendor: LENOVO
  version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
  version.libdrm2: libdrm2 2.4.91-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu3
  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
  xserver.bootTime: Thu Mar 29 19:26:30 2018
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.19.6-1ubuntu3
  xserver.video_driver: modeset

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

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


[Desktop-packages] [Bug 1760312] Re: AMD or Intel VGA driver

2018-11-16 Thread Daniel van Vugt
Thank you for reporting this bug to Ubuntu.
Ubuntu 17.10 (artful) reached end-of-life on July 19, 2018.

See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases 

We appreciate that this bug may be old and you might not be interested
in discussing it any more. But if you are then please upgrade to the
latest Ubuntu version and re-test. If you then find the bug is still
present in the newer Ubuntu version, please add a comment here telling
us which new version it is in and change the bug status to Confirmed.

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

** Changed in: ubuntu
   Status: New => Won't Fix

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

Title:
   AMD or Intel VGA driver

Status in Ubuntu:
  Won't Fix

Bug description:
  Can't install AMD or Intel VGA driver

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: xorg 1:7.7+19ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-37.42-generic 4.13.13
  Uname: Linux 4.13.0-37-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Mar 31 21:49:29 2018
  DistUpgraded: Fresh install
  DistroCodename: artful
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company 3rd Gen Core processor Graphics 
Controller [103c:194d]
   Advanced Micro Devices, Inc. [AMD/ATI] Mars [Radeon HD 8670A/8670M/8750M] 
[1002:6600] (rev ff) (prog-if ff)
  InstallationDate: Installed on 2018-03-31 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
  MachineType: Hewlett-Packard HP ProBook 450 G0
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-37-generic.efi.signed 
root=UUID=0e6bda63-55f9-42e5-8061-7f3db5d18136 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/06/2017
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: 68IRF Ver. F.65
  dmi.board.name: 1949
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 90.0F
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvr68IRFVer.F.65:bd04/06/2017:svnHewlett-Packard:pnHPProBook450G0:pvrA2018CD200:rvnHewlett-Packard:rn1949:rvrKBCVersion90.0F:cvnHewlett-Packard:ct10:cvr:
  dmi.product.family: 103C_5336AN G=N L=BUS B=HP S=PRO
  dmi.product.name: HP ProBook 450 G0
  dmi.product.version: A2018CD200
  dmi.sys.vendor: Hewlett-Packard
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.83-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.8-0ubuntu0~17.10.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.8-0ubuntu0~17.10.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20170309-0ubuntu1
  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/+bug/1760312/+subscriptions

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


[Desktop-packages] [Bug 1469163] Re: Missing charachters on slide text/title

2018-11-16 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

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

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

Title:
  Missing charachters on slide text/title

Status in libreoffice package in Ubuntu:
  Confirmed

Bug description:
  Opening an existing document (from a previous version of libreoffice,
  two years old), clicking on the text to edit, after a few milliseconds
  some of the letters disappear. The disappeared letters do not have any
  special formatting. In presentation mode (F5) the letters appear
  correctly.

  See the attached documents (the slides and the snapshot).

  Here on (K)ubuntu 14.04 64bit

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: libreoffice-impress 1:4.2.8-0ubuntu2
  ProcVersionSignature: Ubuntu 3.13.0-55.94-generic 3.13.11-ckt20
  Uname: Linux 3.13.0-55-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.11
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Fri Jun 26 14:32:08 2015
  InstallationDate: Installed on 2013-08-01 (694 days ago)
  InstallationMedia: Kubuntu 12.04.2 LTS "Precise Pangolin" - Release amd64 
(20130214)
  SourcePackage: libreoffice
  UpgradeStatus: Upgraded to trusty on 2014-04-18 (434 days ago)

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

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


[Desktop-packages] [Bug 1469163] Re: Missing charachters on slide text/title

2018-11-16 Thread Martin Kuba
I have the same problem on Linux Mint MATE 18.3 Sylvia (Ubuntu 16.04)
with LibreOffice 1:6.1.3~rc2-0ubuntu0.16.04.1 from PPA.

$ LC_ALL=C apt-cache policy  libreoffice-impress
libreoffice-impress:
  Installed: 1:6.1.3~rc2-0ubuntu0.16.04.1
  Candidate: 1:6.1.3~rc2-0ubuntu0.16.04.1
  Version table:
 *** 1:6.1.3~rc2-0ubuntu0.16.04.1 500
500 http://ppa.launchpad.net/libreoffice/ppa/ubuntu xenial/main amd64 
Packages
100 /var/lib/dpkg/status

It happens also when I downgrade to 1:5.1.6~rc2-0ubuntu1~xenial4 from
xenial-upgrades.

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

Title:
  Missing charachters on slide text/title

Status in libreoffice package in Ubuntu:
  Confirmed

Bug description:
  Opening an existing document (from a previous version of libreoffice,
  two years old), clicking on the text to edit, after a few milliseconds
  some of the letters disappear. The disappeared letters do not have any
  special formatting. In presentation mode (F5) the letters appear
  correctly.

  See the attached documents (the slides and the snapshot).

  Here on (K)ubuntu 14.04 64bit

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: libreoffice-impress 1:4.2.8-0ubuntu2
  ProcVersionSignature: Ubuntu 3.13.0-55.94-generic 3.13.11-ckt20
  Uname: Linux 3.13.0-55-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.11
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Fri Jun 26 14:32:08 2015
  InstallationDate: Installed on 2013-08-01 (694 days ago)
  InstallationMedia: Kubuntu 12.04.2 LTS "Precise Pangolin" - Release amd64 
(20130214)
  SourcePackage: libreoffice
  UpgradeStatus: Upgraded to trusty on 2014-04-18 (434 days ago)

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

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


[Desktop-packages] [Bug 1794282] Re: warning dialog when closing multiple private tabs can become unresponsive

2018-11-16 Thread Olivier Tilloy
I am unable to observe the issue.

I never get a warning when closing a private browsing window, even if it
has several tabs open, and there doesn't seem to be any relevant option
in about:config to control that.

I do get a warning when closing a normal window with several tabs open,
but gnome shell never considers the window to become unresponsive. I
have disabled screen blanking and locking and waited for 10 minutes, and
the firefox window remains responsive and the warning dialog can be
dismissed.

In your report you mention "after a while", how long would that be?
Are you seeing the problem with private browsing windows only, or also with 
normal windows?
Finally, with the latest update (63.0+build2-0ubuntu0.18.04.2), does the 
problem still exist?

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

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

Title:
  warning dialog when closing multiple private tabs can become
  unresponsive

Status in firefox package in Ubuntu:
  Incomplete

Bug description:
  Affecting Firefox 60 with Ubuntu 18.04.1: (Private Browsing)

  When closing down Private Browsing with 2 tabs or more, the 'warning'
  dialog box appears but if no selection is made after a while, the
  'Gnome' dialog box appears behind it incorrectly indicating Firefox is
  'unresponsive'. This causes the application to freeze as no selection
  can then be made as the 'Gnome' dialog box's selection is hidden
  (inactive window) behind Firefox's 'warning' dialog box (active
  window) which has now frozen (...awaiting the 'Gnome' dialog box's
  selection which cannot be made!)

  Thank you for passing this on to the appropriate teams for action.

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

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


[Desktop-packages] [Bug 1803696] [NEW] Togglable buttons status is very hard to see

2018-11-16 Thread White_Rabbit
Public bug reported:

Some buttons like "Snap to Snap Guides" can be toggled, but it's very
hard to understand in which status they are.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: libreoffice (not installed)
ProcVersionSignature: Ubuntu 4.15.0-39.42-generic 4.15.18
Uname: Linux 4.15.0-39-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.5
Architecture: amd64
CurrentDesktop: LXDE
Date: Fri Nov 16 12:21:50 2018
InstallationDate: Installed on 2018-10-31 (15 days ago)
InstallationMedia: Lubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
SourcePackage: libreoffice
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug bionic

** Attachment added: "Example of a menu with togglable buttons"
   
https://bugs.launchpad.net/bugs/1803696/+attachment/5213434/+files/2018-11-16-121030_1920x1080_scrot.png

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

Title:
  Togglable buttons status is very hard to see

Status in libreoffice package in Ubuntu:
  New

Bug description:
  Some buttons like "Snap to Snap Guides" can be toggled, but it's very
  hard to understand in which status they are.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: libreoffice (not installed)
  ProcVersionSignature: Ubuntu 4.15.0-39.42-generic 4.15.18
  Uname: Linux 4.15.0-39-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  CurrentDesktop: LXDE
  Date: Fri Nov 16 12:21:50 2018
  InstallationDate: Installed on 2018-10-31 (15 days ago)
  InstallationMedia: Lubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  SourcePackage: libreoffice
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1797373] Re: 3D slide transitions don't work at all or when played there is flashing screen

2018-11-16 Thread Saksham Kapoor
yes, hardware acceleration is checked.


** Attachment added: "Screenshot from 2018-11-16 16-49-49.png"
   
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1797373/+attachment/5213417/+files/Screenshot%20from%202018-11-16%2016-49-49.png

** Description changed:

  Normal effects *work*: Wipe, Wheel, Uncover, Bars, Checkers, Shape, Box,
  Wedge, Venetian, Fade, Cut, Cover, Dissolve, Comb, Push, Split,
  Diagonal.
  
  3D-Effects *don’t work*: Tiles, Cube, Circles, Helix, Fall, Turn Around,
  Iris, Turn Down, Rochade, 3D Venetian, Static, Fine Dissolve, Vortex,
  Ripple, Glitter, Honeycomb, Newsflash.
  
- Normal effects works perfectly, 3D-effects either don't work at all or
- when played with F5, shows a flashing screen.
+ Normal effects works perfectly, 3D-effects either don't work at all or when 
played with F5, shows a flashing screen.
+ Tearing is also seen. Hardware acceleration is checked.
+ 
  
  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: libreoffice 1:6.0.6-0ubuntu0.18.04.1
  ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18
  Uname: Linux 4.15.0-36-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.4
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Oct 11 17:59:04 2018
  InstallationDate: Installed on 2017-10-28 (348 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  ProcEnviron:
-  LANGUAGE=en_IN:en
-  PATH=(custom, no user)
-  XDG_RUNTIME_DIR=
-  LANG=en_IN
-  SHELL=/bin/bash
+  LANGUAGE=en_IN:en
+  PATH=(custom, no user)
+  XDG_RUNTIME_DIR=
+  LANG=en_IN
+  SHELL=/bin/bash
  SourcePackage: libreoffice
  UpgradeStatus: Upgraded to bionic on 2018-09-27 (14 days ago)

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

Title:
  3D slide transitions don't work at all or when played there is
  flashing screen

Status in libreoffice package in Ubuntu:
  Incomplete

Bug description:
  Normal effects *work*: Wipe, Wheel, Uncover, Bars, Checkers, Shape,
  Box, Wedge, Venetian, Fade, Cut, Cover, Dissolve, Comb, Push, Split,
  Diagonal.

  3D-Effects *don’t work*: Tiles, Cube, Circles, Helix, Fall, Turn
  Around, Iris, Turn Down, Rochade, 3D Venetian, Static, Fine Dissolve,
  Vortex, Ripple, Glitter, Honeycomb, Newsflash.

  Normal effects works perfectly, 3D-effects either don't work at all or when 
played with F5, shows a flashing screen.
  Tearing is also seen. Hardware acceleration is checked.

  
  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: libreoffice 1:6.0.6-0ubuntu0.18.04.1
  ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18
  Uname: Linux 4.15.0-36-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.4
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Oct 11 17:59:04 2018
  InstallationDate: Installed on 2017-10-28 (348 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  ProcEnviron:
   LANGUAGE=en_IN:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_IN
   SHELL=/bin/bash
  SourcePackage: libreoffice
  UpgradeStatus: Upgraded to bionic on 2018-09-27 (14 days ago)

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

-- 
Mailing list: https://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 1803583] Re: Xorg crash

2018-11-16 Thread AdrianChallinor
sudo ubuntu-bug _usr_lib_xorg_Xorg.0.crash

After updating /etc/apport/crashdb.conf as per bug 994921new bug
created:

https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1803694



On 16/11/2018 01:58, Daniel van Vugt wrote:
> Thanks for the bug report.
>
> The backtrace in your log may not be completely accurate:
>
> [ 83021.728] (EE) Backtrace:
> [ 83021.730] (EE) 0: /usr/lib/xorg/Xorg (OsLookupColor+0x139) [0x560581eab229]
> [ 83021.731] (EE) 1: /lib/x86_64-linux-gnu/libpthread.so.0 (funlockfile+0x50) 
> [0x7f3cc6de2e1f]
> [ 83021.731] (EE) 2: /usr/lib/xorg/modules/libglamoregl.so 
> (glamor_get_pixmap_texture+0x7d) [0x7f3cc557244d]
> [ 83021.732] (EE) 3: /usr/lib/xorg/modules/libglamoregl.so 
> (glamor_create_gc+0x7b08) [0x7f3cc5584988]
> [ 83021.732] (EE) 4: /usr/lib/xorg/modules/libglamoregl.so 
> (glamor_create_gc+0x7f3c) [0x7f3cc558512c]
> [ 83021.732] (EE) 5: /usr/lib/xorg/modules/libglamoregl.so 
> (glamor_create_gc+0x854e) [0x7f3cc55858ce]
> [ 83021.732] (EE) 6: /usr/lib/xorg/modules/libglamoregl.so 
> (glamor_create_gc+0xa54c) [0x7f3cc558952c]
> [ 83021.733] (EE) 7: /usr/lib/xorg/Xorg (DamageRegionAppend+0x6af) 
> [0x560581e2d79f]
> [ 83021.733] (EE) 8: /usr/lib/xorg/modules/libglamoregl.so 
> (glamor_create_gc+0x1137e) [0x7f3cc559787e]
> [ 83021.734] (EE) 9: /usr/lib/xorg/Xorg (AddTraps+0x41a5) [0x560581e260c5]
> [ 83021.734] (EE) 10: /usr/lib/xorg/Xorg (SendErrorToClient+0x35e) 
> [0x560581d4c97e]
> [ 83021.734] (EE) 11: /usr/lib/xorg/Xorg (InitFonts+0x3b6) [0x560581d50906]
> [ 83021.734] (EE) 12: /lib/x86_64-linux-gnu/libc.so.6 
> (__libc_start_main+0xeb) [0x7f3cc6c0409b]
> [ 83021.734] (EE) 13: /usr/lib/xorg/Xorg (_start+0x2a) [0x560581d3a67a]
>
> so we will need a better stack trace. To help us find the cause of the
> crash please follow these steps:
>
> 1. Look in /var/crash for crash files and if found run:
>  ubuntu-bug YOURFILE.crash
> Then tell us the ID of the newly-created bug.
>
> 2. If step 1 failed then look at https://errors.ubuntu.com/user/ID where
> ID is the content of file /var/lib/whoopsie/whoopsie-id on the machine.
> Do you find any links to recent problems on that page? If so then please
> send the links to us.
>
> 3. If step 2 also failed then apply the workaround from bug 994921,
> reboot, reproduce the crash, and retry step 1.
>
> Please take care to avoid attaching .crash files to bugs as we are
> unable to process them as file attachments. It would also be a security
> risk for yourself.
>
> ** Package changed: xorg (Ubuntu) => xorg-server (Ubuntu)
>
> ** Changed in: xorg-server (Ubuntu)
> Status: New => Incomplete
>
-- 
Adrian Challinor (FRAS)
m: +44-7860-290-883
e: adrian.challi...@osiris.co.uk
w: https://www.osiris.co.uk

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

Title:
  Xorg crash

Status in xorg-server package in Ubuntu:
  Incomplete

Bug description:
  This bug is happening approximately every 24 hours. Any changes to
  open files are lost (DATA LOSS BEING EXPERIENCED).

  System is a clean install of Ubuntu 18.10 (XUbuntu). System is up to
  date with all publish updates.

  System has two graphics card: 
  1) NVidia GK208B [GeForce GT 710]
  2) NVidia GT218 [GeForce 210]

  I am reluctant to switch to nvida drivers as google searches indicate
  that they do not support dual head systems.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: xorg 1:7.7+19ubuntu8
  ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12
  Uname: Linux 4.18.0-11-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: XFCE
  Date: Thu Nov 15 16:18:02 2018
  DistUpgraded: Fresh install
  DistroCodename: cosmic
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox, 5.2.18, 4.18.0-10-generic, x86_64: installed
   virtualbox, 5.2.18, 4.18.0-11-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   NVIDIA Corporation GK208B [GeForce GT 710] [10de:128b] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: NVIDIA Corporation GK208B [GeForce GT 710] [10de:128b]
   NVIDIA Corporation GT218 [GeForce 210] [10de:0a65] (rev a2) (prog-if 00 [VGA 
controller])
 Subsystem: ASUSTeK Computer Inc. GT218 [GeForce 210] [1043:852d]
  InstallationDate: Installed on 2018-11-07 (7 days ago)
  InstallationMedia: Xubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.2)
  MachineType: To be filled by O.E.M. To be filled by O.E.M.
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-11-generic 
root=UUID=9d341c90-212b-47c2-b0f0-a7e607ee860b ro quiet splash vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  Title: Xorg crash
  UpgradeStatus: No upgrade log 

[Desktop-packages] [Bug 1188569] Re: Some keyboard shortcuts randomly stop working

2018-11-16 Thread Arfian
@Khurshid your solution works but it seems it doesn't affect media keys.
Media keys (Play/Pause, Stop, Previous, Next) still don't work. Do you
think the root cause is the same?

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

Title:
  Some keyboard shortcuts randomly stop working

Status in GNOME Shell:
  New
Status in Unity:
  Confirmed
Status in unity package in Ubuntu:
  Invalid
Status in unity-settings-daemon package in Ubuntu:
  Confirmed

Bug description:
  Hi,
  Certain shortcuts randomly stops working in my computer. They are Super+s 
(workspace switcher), Super+Up (switch to workspace above) and Super+Down 
(switch to workspace below). Other shortcuts work fine.

  A few notes that might help:
  1- Reassigning shortcuts make them work again except for Super+s.
  2- Rebooting make shortcuts work.
  3- I have been using these shortcuts with many previous ubuntu versions and 
my preferences are old.
  4- I am not sure of certain steps that produces the problem. The shortcuts 
sometimes stop working but once they stop, they do not work unless I reassign 
them or reboot.

  I am using Ubuntu 13.04.

  Thank you

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: unity 7.0.0daily13.04.18~13.04-0ubuntu1
  ProcVersionSignature: Ubuntu 3.8.0-23.34-generic 3.8.11
  Uname: Linux 3.8.0-23-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.9.2-0ubuntu8.1
  Architecture: amd64
  CompizPlugins: 
[core,composite,opengl,compiztoolbox,decor,regex,grid,mousepoll,place,wall,snap,resize,vpswitch,session,animation,gnomecompat,imgpng,commands,move,workarounds,fade,unitymtgrabhandles,expo,scale,ezoom,unityshell]
  Date: Fri Jun  7 13:40:06 2013
  InstallationDate: Installed on 2013-05-27 (11 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  MarkForUpload: True
  SourcePackage: unity
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1761267] Re: issue is regarding boot hanging between work

2018-11-16 Thread Daniel van Vugt
Thank you for taking the time to report this bug and helping to make Ubuntu 
better. Please answer these questions:
* Is this reproducible?
* If so, what specific steps should we take to recreate this bug?

This will help us to find and resolve the problem.

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

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

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

Title:
  issue is regarding boot hanging between work

Status in Ubuntu:
  Incomplete

Bug description:
  while getting started it is hanged and sometime it doesnot open the
  required folder any software downloaded from internet is not installed
  in "exe." file especially sometime keyboard stops working

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-116.140-generic 4.4.98
  Uname: Linux 4.4.0-116-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  BootLog:
   Scanning for Btrfs filesystems
   UBUNTU: clean, 272012/29777920 files, 3537812/119111424 blocks
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Wed Apr  4 23:11:32 2018
  DistUpgraded: Fresh install
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-xenial-amd64-20160624-2
  DistroCodename: xenial
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation Device [8086:5916] (rev 02) (prog-if 00 [VGA controller])
 Subsystem: Dell Device [1028:0767]
  InstallationDate: Installed on 2018-02-22 (41 days ago)
  InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 
20160624-10:47
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 8087:0a2a Intel Corp. 
   Bus 001 Device 003: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card 
Reader Controller
   Bus 001 Device 002: ID 0c45:6a06 Microdia 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Inspiron 5567
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-116-generic.efi.signed 
root=UUID=a581e6e4-3ec8-44a1-96df-744ef70e8b7e ro acpi_rev_override locale=en_US
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/12/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.1.0
  dmi.board.name: 0C6XG5
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.1.0:bd01/12/2017:svnDellInc.:pnInspiron5567:pvr:rvnDellInc.:rn0C6XG5:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.name: Inspiron 5567
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.83-1~16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.8-0ubuntu0~16.04.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.8-0ubuntu0~16.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.7
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1.2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Wed Apr  4 20:29:12 2018
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id1317 
   vendor LGD
  xserver.version: 2:1.18.4-0ubuntu0.7

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

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


[Desktop-packages] [Bug 1761834] Re: Right-click doesn't work

2018-11-16 Thread Daniel van Vugt
*** This bug is a duplicate of bug 1759300 ***
https://bugs.launchpad.net/bugs/1759300

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


** This bug has been marked a duplicate of bug 1759300
   Gnome Shell: Touchpad right click (bottom right) area does not work

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

Title:
  Right-click doesn't work

Status in libinput package in Ubuntu:
  Confirmed

Bug description:
  I decided to try out the beta for 18.04 from 17.10.  Upon upgrading, I
  discovered that right-clicking no longer works on my trackpad, and
  right-clicks are handled as left-clicks would be.  Two-finger right
  click does not work either.  If I plug in a mouse with a physical
  right button, right clicking does work.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu6
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  Uname: Linux 4.15.0-13-generic x86_64
  ApportVersion: 2.20.9-0ubuntu2
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: GNOME
  Date: Fri Apr  6 11:26:00 2018
  DistUpgraded: 2018-04-06 11:14:08,949 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus:
   bbswitch, 0.8, 4.14.15-041415-generic, x86_64: installed
   bbswitch, 0.8, 4.15.0-13-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation HD Graphics 530 [8086:191b] (rev 06) (prog-if 00 [VGA 
controller])
 Subsystem: Dell HD Graphics 530 [1028:06e4]
 Subsystem: Dell GM107M [GeForce GTX 960M] [1028:06e4]
  InstallationDate: Installed on 2017-05-04 (337 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  MachineType: Dell Inc. XPS 15 9550
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-13-generic 
root=UUID=62d6bfc3-82e2-4ca2-9255-8dae5ad9b117 ro quiet splash vt.handoff=1
  SourcePackage: xorg
  UpgradeStatus: Upgraded to bionic on 2018-04-06 (0 days ago)
  dmi.bios.date: 08/21/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.4.0
  dmi.board.name: 0N7TVV
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.4.0:bd08/21/2017:svnDellInc.:pnXPS159550:pvr:rvnDellInc.:rn0N7TVV:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: XPS 15 9550
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.91-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
  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/libinput/+bug/1761834/+subscriptions

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


[Desktop-packages] [Bug 1767445] Re: Uninstalled snaps show most recent channel version, not version to be installed by default

2018-11-16 Thread Paweł Stołowski
I've check this with Chipaca, there is no plan to change anything in
snapd wrt this bug on the following basis: (a) user can look at the
channel map to know what's in stable, and (b) store can change what's
returned outside the channel map, which snapd will forward on.

** Changed in: snapd
   Status: New => Won't Fix

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

Title:
  Uninstalled snaps show most recent channel version, not version to be
  installed by default

Status in snapd:
  Won't Fix
Status in Snap Store:
  New
Status in gnome-software package in Ubuntu:
  Fix Released
Status in gnome-software source package in Xenial:
  Fix Released
Status in gnome-software source package in Bionic:
  Fix Released
Status in gnome-software source package in Cosmic:
  Fix Released

Bug description:
  [Impact]
  GNOME Software can show incorrect version of snap that will be installed on 
details page.

  [Test Case]
  1. Open GNOME Software. Ensure blender or spotify snap is not installed.
  2. Select blender or spotify  snap (tried 28-04-2018, may change if store 
versions are changed)

  Expected result:
  Version label shows version to be installed (stable channel by default)

  Observed result:
  Version label shows most recently uploaded version, i.e. from the edge 
channel. This is not the version that will be installed when clicking install.

  [Regression Potential]
  The logic around choosing which version value to show was changed. Could 
create other bugs with this data.

  Orignial text:

  Ubuntu Software, when showing metadata about a snap package, is most
  of the time, likely to get information which is misleading, since it
  shows info from the *most recently* uploaded snap, regardless of which
  channel the snap was uploaded to.

  An example of this is to search for blender, and see that the version
  shows the edge channel - 2.80-4de142e0b7b and not the stable channel -
  2.79.

  After actually installing the application, the correct metadata is
  shown.

  See https://forum.snapcraft.io/t/unexpected-revision-information-
  exposed-in-some-situations/5163 for more details.

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

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


  1   2   >