[Desktop-packages] [Bug 1825919] Re: Gedit right click context menu stops working

2019-04-23 Thread PJSingh5000
NON_DEFAULT EXTENSIONS
--

Dash to Dock
https://extensions.gnome.org/extension/307/dash-to-dock/
Note: I have removed gnome-shell-extension-ubuntu-dock

Bluetooth Quick Connect
https://extensions.gnome.org/extension/1401/bluetooth-quick-connect/

Caffeine [INACTIVE]
https://extensions.gnome.org/extension/517/caffeine/

Clipboard Indicator
https://extensions.gnome.org/extension/779/clipboard-indicator/

Coverflow Alt-Tab
https://extensions.gnome.org/extension/97/coverflow-alt-tab/

Printers
https://extensions.gnome.org/extension/1218/printers/

Refresh Wifi Connections
https://extensions.gnome.org/extension/905/refresh-wifi-connections/

Sound Input & Output Device Chooser
https://extensions.gnome.org/extension/906/sound-output-device-chooser/

TLP Switcher
https://extensions.gnome.org/extension/1212/tlp-switcher/

DEFAULT EXTENSIONS
--

Desktop Icons [INACTIVE]
Note: Default Ubuntu extension

Ubuntu appindicators
Note: Default Ubuntu extension


GEDIT PLUGINS
-

I have the following Gedit plugin packages installed:
1. gedit-plugins
2. gedit-source-code-browser-plugin

The following Gedit plugins are activated:
Character Map
Code Comment
Document Statistics
File Browser Panel
Find in Files
Insert Date/Time
Join/Split Lines
Smart Spaces
Sort
Source Code Browser
Spell Checker
Word Completion
Zeitgeist dataprovider

REPRODUCING ISSUE
-

I haven't been able to find a consistent way to reproduce this issue...

It occurs after using Gedit for a long time.
I use Gedit heavily, open many tabs, and open local and remote text documents.
I do  lot of cut-and-paste, I use the right-click context menu a frequently to 
cut or paste text.

While using Gedit, I simultaneously use Meld, and sometimes I have the same 
document(s) open in Gedit and in Meld.
I may edit a document at the same time in Meld and in Gedit. (When I do this, I 
simply reload the file when Meld or Gedit warn me that a file has changed).
One extension that I use heavily is Clipboard Indicator.

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

Title:
  Gedit right click context menu stops working

Status in gedit package in Ubuntu:
  Incomplete

Bug description:
  The Gedit text area right-click context menu stops appearing.

  This bug affects Ubuntu 19.04, but may be a regression of old Bug
  #1731581 from Ubuntu 17.10.

  Gedit version: 3.32.0-3
  Fresh install of Ubuntu 19.04
  gkt-3 version: 3.24.8-1ubuntu1

  RECREATING ISSUE

  When I first log in, the right-click context menus in Gedit works fine.
  After some time of usage, the right-click context menu no longer appears.

  SIDE-EFFECT

  A side-effect of this issue is that the mouse cursor does not revert
  to a pointer style after doing a right-click. It retains the "I"
  (Insert) shape even when you hover outside Gedit's text area.

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

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


[Desktop-packages] [Bug 1817243] Re: I have dual boot ubuntu. in Ubunt, there is no output sound devices and always keep muted. In windows sound working perfectly

2019-04-23 Thread Launchpad Bug Tracker
[Expired for pulseaudio (Ubuntu) because there has been no activity for
60 days.]

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

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

Title:
  I have dual boot ubuntu. in Ubunt, there is no output sound devices
  and always keep muted. In windows  sound working perfectly

Status in pulseaudio package in Ubuntu:
  Expired

Bug description:
  No output sound device available.
  Sound icon shows it is muted and the sound button on the keyboard as well. It 
does not let to unmute as well.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: pulseaudio 1:8.0-0ubuntu3.10
  ProcVersionSignature: Ubuntu 4.15.0-45.48~16.04.1-generic 4.15.18
  Uname: Linux 4.15.0-45-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/hwC0D2', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D10p', 
'/dev/snd/pcmC0D9p', '/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', 
'/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', 
'/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
  CurrentDesktop: Unity
  Date: Fri Feb 22 09:20:20 2019
  InstallationDate: Installed on 2019-02-06 (15 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  SourcePackage: pulseaudio
  Symptom: audio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/07/2015
  dmi.bios.vendor: HP
  dmi.bios.version: N76 Ver. 01.00
  dmi.board.name: 80FD
  dmi.board.vendor: HP
  dmi.board.version: KBC Version 22.36
  dmi.chassis.asset.tag: 5CG6097143
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.modalias: 
dmi:bvnHP:bvrN76Ver.01.00:bd12/07/2015:svnHP:pnHPProBook650G2:pvr:rvnHP:rn80FD:rvrKBCVersion22.36:cvnHP:ct10:cvr:
  dmi.product.family: 103C_5336AN G=N L=BUS B=HP S=PRO
  dmi.product.name: HP ProBook 650 G2
  dmi.sys.vendor: HP

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

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


[Desktop-packages] [Bug 1817222] Re: [nouveau] Xorg freeze

2019-04-23 Thread Launchpad Bug Tracker
[Expired for xorg-server (Ubuntu) because there has been no activity for
60 days.]

** Changed in: xorg-server (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  [nouveau] Xorg freeze

Status in xorg-server package in Ubuntu:
  Expired

Bug description:
  Update 22/2/2019 Hi again , logged in to my computer today and noted
  the driver was not set to nvidia the selection option was on xorg
  driver and would not change this would revert after selection.
  Attempted changing driver as user and also as admin no effect.  Did a
  manual update via terminal of all drivers '34 approximately' and then
  software updater  allowed the selection of nvidia display driver. I
  mention this as I posted yesterday that I had selected nvidia driver
  and found the same issue, based on today's finding this may have been
  factually incorrect and maybe the two crashes occurred while using
  xorg driver.

  21/2/2019
  I have selected the NVIDIA driver instead and can report the same problem - 
screen frozen one internet page open no other programs. Using Firefox as per 
original install, each time this freeze has occurred only when connected to 
wireless network and using the internet. So this is an update to the original 
logged error report.

  Have been using Ubuntu online/offline for occasional browsing or
  offline use since installation and no issues.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04

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

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


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

2019-04-23 Thread drs305
More info from post #4

Tried another upgrade from Ubuntu 18.10, which failed once again. I was
unable to upload the errors but at approximately the 60% mark of the
actual installation, a message was generated that the upgrade would
probably fail.

The error messages at this point included a GDK PixBuf Warning that it could 
not open the pixbuf loader module file:
"/usr/lib/x86_64-linux-gnu/gdk-pixbuf-2.0/2.10.0/loaders.cache': No such file 
or directory

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

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

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

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

  Expected results:
  * upgrade process ended without errors

  Actual results:
  * upgrade process ended with warning message:

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

  triggers looping, abandoned

  Workaround:

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

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

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

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

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


[Desktop-packages] [Bug 1726717] Re: Alignment of external screen limits placing of icons

2019-04-23 Thread ADFH
I had this bug in 18.10, but it's gone in 19.04 with move from nautilus
to gnome-shell-extension-desktop-icons which brings its own issues.

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

Title:
  Alignment of external screen limits placing of icons

Status in Nautilus:
  Won't Fix
Status in nautilus package in Ubuntu:
  Triaged

Bug description:
  Reporting against gnome-desktop since I do not know better. Please
  assign to appropriate package. Thanks!

  Using external monitors with the gnome desktop behaves unexpected in a few 
ways. One is, that the alignment of screens limits, where icons can be placed 
on that screens:
  My external monitor is higher than the internal screen of my laptop. I have 
aligned the screens at the bottom. This makes the bottom part of the (external, 
higher) screen unusable for placing icons.

  This is probably best seen on the attached screenshot.
  Thanks for caring!

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-session (not installed)
  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: ubuntu:GNOME
  Date: Tue Oct 24 08:49:30 2017
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2015-12-13 (680 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-session
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1825625] Re: Some apps appear blurry with framebuffer scaling

2019-04-23 Thread Daniel van Vugt
** No longer affects: mutter

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

Title:
  Some apps appear blurry with framebuffer scaling

Status in firefox package in Ubuntu:
  New
Status in libreoffice package in Ubuntu:
  New
Status in mutter package in Ubuntu:
  Invalid
Status in thunderbird package in Ubuntu:
  New

Bug description:
  Setting the framebuffer scaling (with gsettings set org.gnome.mutter
  experimental-features "['scale-monitor-framebuffer']") allows the
  display on HiDPi to be scaled to something different than
  100%/200%/300%.

  Which would be fine.

  However, the display is rendered such that most applications provide
  blurred display of text and graphics.

  This is not always the case (e.g. system settings are displayed
  correctly, Thunderbird and Firefox are blurred).

  Also the screen flickers when selection menus or resizing the windows.
  A black border appears around the windows where the shadow should appear. It 
gets removed a few seconds later but still is irritating.

  This issue is not urgent, just annoying. It can be worked around by
  removing the settings in gsetting / dconf.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: mutter 3.32.0+git20190410-1ubuntu1
  ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6
  Uname: Linux 5.0.0-13-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Apr 20 11:11:55 2019
  InstallationDate: Installed on 2018-04-30 (355 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  SourcePackage: mutter
  UpgradeStatus: Upgraded to disco on 2019-04-19 (0 days ago)

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

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


[Desktop-packages] [Bug 1825625] Re: Some apps appear blurry with framebuffer scaling

2019-04-23 Thread Bug Watch Updater
** Changed in: mutter
   Status: Unknown => Fix Released

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

Title:
  Some apps appear blurry with framebuffer scaling

Status in Mutter:
  Fix Released
Status in firefox package in Ubuntu:
  New
Status in libreoffice package in Ubuntu:
  New
Status in mutter package in Ubuntu:
  Invalid
Status in thunderbird package in Ubuntu:
  New

Bug description:
  Setting the framebuffer scaling (with gsettings set org.gnome.mutter
  experimental-features "['scale-monitor-framebuffer']") allows the
  display on HiDPi to be scaled to something different than
  100%/200%/300%.

  Which would be fine.

  However, the display is rendered such that most applications provide
  blurred display of text and graphics.

  This is not always the case (e.g. system settings are displayed
  correctly, Thunderbird and Firefox are blurred).

  Also the screen flickers when selection menus or resizing the windows.
  A black border appears around the windows where the shadow should appear. It 
gets removed a few seconds later but still is irritating.

  This issue is not urgent, just annoying. It can be worked around by
  removing the settings in gsetting / dconf.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: mutter 3.32.0+git20190410-1ubuntu1
  ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6
  Uname: Linux 5.0.0-13-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Apr 20 11:11:55 2019
  InstallationDate: Installed on 2018-04-30 (355 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  SourcePackage: mutter
  UpgradeStatus: Upgraded to disco on 2019-04-19 (0 days ago)

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

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


[Desktop-packages] [Bug 1769358] Re: Thumbnail previews in Files/Nautilus only show when zoom is 150% or more

2019-04-23 Thread Bug Watch Updater
** Changed in: nautilus
   Status: Unknown => New

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

Title:
  Thumbnail previews in Files/Nautilus only show when zoom is 150% or
  more

Status in Nautilus:
  New
Status in nautilus package in Ubuntu:
  Triaged

Bug description:
  Ubuntu 18.04 LTS
  Nautilus package: 1:3.26.3-0ubuntu4

  I don't get thumbnail previews in Files (Nautilus) at the default zoom
  level when using List view.

  If I select 150% in the hamburger menu the thumbnails are displayed,
  and they are displayed in Grid view at all sizes. They are also
  displayed in the Open File dialog, even though the icon size there is
  smaller than in Files!

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

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


[Desktop-packages] [Bug 1826081] [NEW] Ability to automatically arrange desktop icons gone in 19.04

2019-04-23 Thread ADFH
Public bug reported:

Upgraded from Ubuntu 18.10 to Ubuntu 19.04.

On the upside, Ubuntu 19.04 now handles my unusual desktop geometry, and
displays desktop icons within physical monitor dimensions (I have one
landscape, one portrait display).

The downside is there's no sort option for desktop icons anymore.

Icons are snapped to grid automatically, but all arrangement for now is
manual.

The restoration of "Sort by name" functionality at the very least, and
perhaps the addition of "Sort by type" would be even better.

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

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

Title:
  Ability to automatically arrange desktop icons gone in 19.04

Status in gnome-shell-extension-desktop-icons package in Ubuntu:
  New

Bug description:
  Upgraded from Ubuntu 18.10 to Ubuntu 19.04.

  On the upside, Ubuntu 19.04 now handles my unusual desktop geometry,
  and displays desktop icons within physical monitor dimensions (I have
  one landscape, one portrait display).

  The downside is there's no sort option for desktop icons anymore.

  Icons are snapped to grid automatically, but all arrangement for now
  is manual.

  The restoration of "Sort by name" functionality at the very least, and
  perhaps the addition of "Sort by type" would be even better.

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

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


[Desktop-packages] [Bug 1822515] Re: Touchscreen input doesn't rotate with the screen

2019-04-23 Thread Alexandre Jasmin
I'm using a vanilla ubuntu:GNOME session.

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

Title:
  Touchscreen input doesn't rotate with the screen

Status in mutter package in Ubuntu:
  New
Status in xorg-server package in Ubuntu:
  New

Bug description:
  When a touch screen is rotated, touch input is not mapped correctly.

  I'm testing 19.04 on an Acer-One S1003 where the default orientation
  is portrait.

  Ubuntu 19.04 support automatic screen rotation out of the box. But,
  when the tablet is in landscape, the touchscreen doesn't behave
  correctly. Moving a finger horizontally cause a vertical movement and
  vice versa.

  The same happens in both X11 and Wayland.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 19.04
  Package: xorg-server
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6
  Tags:  disco
  Uname: Linux 5.0.0-13-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True

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

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


[Desktop-packages] [Bug 1734095] Re: Software & Updates not showing authorization popup [gnome-shell[N]: pushModal: invocation of begin_modal failed]

2019-04-23 Thread Angel D. Segarra
I can also reproduce this reliably in Disco. I tried to enable Canonical
Partner packages so I think it's easy to trigger.

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

Title:
  Software & Updates not showing authorization popup [gnome-shell[N]:
  pushModal: invocation of begin_modal failed]

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

Bug description:
  After upgrading to Ubuntu 17.10 (from 17.04), if I open the Software
  and Updates app and attempt to change anything it does not popup the
  authorization dialog and will not let changes through.  In sylog I see

  Nov 23 10:07:04 tigger gnome-shell[2142]: polkitAuthenticationAgent: Received 
3 identities that can be used for authentication. Only considering one.
  Nov 23 10:07:04 tigger gnome-shell[2142]: pushModal: invocation of 
begin_modal failed
  Nov 23 10:07:04 tigger gnome-shell[2142]: polkitAuthenticationAgent: Failed 
to show modal dialog. Dismissing authentication request for action-id 
com.ubuntu.softwareproperties.applychanges cookie 
1-28e9d285258e7cd70c2af2980886a55b-1-cff4894642cc4a6c033597370ee1f740
  Nov 23 10:07:04 tigger software-properties-gnome.desktop[3367]: 
ERROR:root:Authentication canceled, changes have not been saved

  Before the upgrade it was ok.
  Other apps that require authorisation function as expected.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.26.1-0ubuntu5
  ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8
  Uname: Linux 4.13.0-17-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.5
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Thu Nov 23 10:07:44 2017
  DisplayManager: lightdm
  InstallationDate: Installed on 2014-10-21 (1128 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20141017)
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to artful on 2017-11-22 (0 days ago)

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

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


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

2019-04-23 Thread Alexandre Jasmin
apport information

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

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

Title:
  Touchscreen input doesn't rotate with the screen

Status in mutter package in Ubuntu:
  New
Status in xorg-server package in Ubuntu:
  New

Bug description:
  When a touch screen is rotated, touch input is not mapped correctly.

  I'm testing 19.04 on an Acer-One S1003 where the default orientation
  is portrait.

  Ubuntu 19.04 support automatic screen rotation out of the box. But,
  when the tablet is in landscape, the touchscreen doesn't behave
  correctly. Moving a finger horizontally cause a vertical movement and
  vice versa.

  The same happens in both X11 and Wayland.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 19.04
  Package: xorg-server
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6
  Tags:  disco
  Uname: Linux 5.0.0-13-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True

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

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


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

2019-04-23 Thread Alexandre Jasmin
apport information

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

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

Title:
  Touchscreen input doesn't rotate with the screen

Status in mutter package in Ubuntu:
  New
Status in xorg-server package in Ubuntu:
  New

Bug description:
  When a touch screen is rotated, touch input is not mapped correctly.

  I'm testing 19.04 on an Acer-One S1003 where the default orientation
  is portrait.

  Ubuntu 19.04 support automatic screen rotation out of the box. But,
  when the tablet is in landscape, the touchscreen doesn't behave
  correctly. Moving a finger horizontally cause a vertical movement and
  vice versa.

  The same happens in both X11 and Wayland.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 19.04
  Package: xorg-server
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6
  Tags:  disco
  Uname: Linux 5.0.0-13-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True

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

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


[Desktop-packages] [Bug 1825623] Re: [AppIndicatorSupport-FATAL] unable to update overlay icon

2019-04-23 Thread Angel D. Segarra
I see this error in the logs.

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

Title:
  [AppIndicatorSupport-FATAL] unable to update overlay icon

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

Bug description:
  After startup or login, An error occurs that just states cancel or
  report... but does not open a detail dialog

  Error messages in the syslog:

  ...
  Apr 20 10:47:19 mbpr13b gnome-shell[3595]: [AppIndicatorSupport-DEBUG] 
Registering 
StatusNotifierItem:1.95/org/ayatana/NotificationItem/software_update_available
  Apr 20 10:47:19 mbpr13b gnome-shell[3595]: [AppIndicatorSupport-FATAL] unable 
to update overlay icon
  Apr 20 10:47:19 mbpr13b gnome-shell[3595]: [AppIndicatorSupport-FATAL] unable 
to update overlay icon
  ...

  It seems that the update notifier cannot register its icon in the top
  bar.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: gnome-shell 3.32.0+git20190410-1ubuntu1
  ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6
  Uname: Linux 5.0.0-13-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Apr 20 10:49:27 2019
  DisplayManager: gdm3
  InstallationDate: Installed on 2018-04-30 (354 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to disco on 2019-04-19 (0 days ago)

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

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


[Desktop-packages] [Bug 1822515] Re: Touchscreen input doesn't rotate with the screen

2019-04-23 Thread Alexandre Jasmin
apport information

** Tags added: apport-collected

** Description changed:

  When a touch screen is rotated, touch input is not mapped correctly.
  
  I'm testing 19.04 on an Acer-One S1003 where the default orientation is
  portrait.
  
  Ubuntu 19.04 support automatic screen rotation out of the box. But, when
  the tablet is in landscape, the touchscreen doesn't behave correctly.
  Moving a finger horizontally cause a vertical movement and vice versa.
  
  The same happens in both X11 and Wayland.
+ --- 
+ ProblemType: Bug
+ ApportVersion: 2.20.10-0ubuntu27
+ Architecture: amd64
+ CurrentDesktop: ubuntu:GNOME
+ DistroRelease: Ubuntu 19.04
+ Package: xorg-server
+ PackageArchitecture: amd64
+ ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6
+ Tags:  disco
+ Uname: Linux 5.0.0-13-generic x86_64
+ UpgradeStatus: No upgrade log present (probably fresh install)
+ UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
+ _MarkForUpload: True

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

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

Title:
  Touchscreen input doesn't rotate with the screen

Status in mutter package in Ubuntu:
  New
Status in xorg-server package in Ubuntu:
  New

Bug description:
  When a touch screen is rotated, touch input is not mapped correctly.

  I'm testing 19.04 on an Acer-One S1003 where the default orientation
  is portrait.

  Ubuntu 19.04 support automatic screen rotation out of the box. But,
  when the tablet is in landscape, the touchscreen doesn't behave
  correctly. Moving a finger horizontally cause a vertical movement and
  vice versa.

  The same happens in both X11 and Wayland.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 19.04
  Package: xorg-server
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6
  Tags:  disco
  Uname: Linux 5.0.0-13-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True

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

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


[Desktop-packages] [Bug 1826078] [NEW] tracker-miner-fs brings system to its knees when indexing - scope for deduplicating hardlinked files?

2019-04-23 Thread ADFH
Public bug reported:

I've noticed since upgrading from 18.10 to 19.04 that tracker-miner-fs
has been going to town on trying to index my filesystem.. so much so,
I've had to switch off all the search options, and then switch off
search overall, as well as call "tracker reset -r" as it seems that just
turning off search in the settings -> search titlebar doesn't always
take effect.

Within my home directory, and in other parts of my filesystem, I have
some folders that have date stamped rsync backups of remote systems.
Between directories, identical files are hard-linked, so they're stored
once, if the same, but listed in multiple directories if they existed at
that time (so each folder is a ready to go "point in time" snapshot, but
identical data is only stored once).

I believe that tracker-miner-fs is treating each instance of a file
listing as an independent copy because they exist in separate
directories, even though they're hard linked, and subsequently
processing the same files again and again and again, consuming the
majority of IO bandwidth on my drives.

There is the UI for Gnome tracker, but it's not that granular, with
options for whether or not things like "Documents" are included, but not
folders below that.

Where this enters bug territory is that this behaviour makes the system
unusable due to the IO load, with no visible indication of what's going
on.

The fixes might be feature suggestions.. Perhaps scope for:
* A ".nomedia" or similar .file like Android that tells tracker "Do not index 
this folder"?
* Perhaps scope for tracker to keep a record of indexed inodes so it can skip 
files it already knows about?
* Flagging that indexing is taking place in notification area with ability to 
stop it, if it peaks at a certain IO utilisation?

** Affects: tracker-miners (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  tracker-miner-fs brings system to its knees when indexing - scope for
  deduplicating hardlinked files?

Status in tracker-miners package in Ubuntu:
  New

Bug description:
  I've noticed since upgrading from 18.10 to 19.04 that tracker-miner-fs
  has been going to town on trying to index my filesystem.. so much so,
  I've had to switch off all the search options, and then switch off
  search overall, as well as call "tracker reset -r" as it seems that
  just turning off search in the settings -> search titlebar doesn't
  always take effect.

  Within my home directory, and in other parts of my filesystem, I have
  some folders that have date stamped rsync backups of remote systems.
  Between directories, identical files are hard-linked, so they're
  stored once, if the same, but listed in multiple directories if they
  existed at that time (so each folder is a ready to go "point in time"
  snapshot, but identical data is only stored once).

  I believe that tracker-miner-fs is treating each instance of a file
  listing as an independent copy because they exist in separate
  directories, even though they're hard linked, and subsequently
  processing the same files again and again and again, consuming the
  majority of IO bandwidth on my drives.

  There is the UI for Gnome tracker, but it's not that granular, with
  options for whether or not things like "Documents" are included, but
  not folders below that.

  Where this enters bug territory is that this behaviour makes the
  system unusable due to the IO load, with no visible indication of
  what's going on.

  The fixes might be feature suggestions.. Perhaps scope for:
  * A ".nomedia" or similar .file like Android that tells tracker "Do not index 
this folder"?
  * Perhaps scope for tracker to keep a record of indexed inodes so it can skip 
files it already knows about?
  * Flagging that indexing is taking place in notification area with ability to 
stop it, if it peaks at a certain IO utilisation?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/tracker-miners/+bug/1826078/+subscriptions

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


[Desktop-packages] [Bug 1805444] Re: [nvidia] Fail to launch gnome-shell (Wayland) on Ubuntu with EGLDevice backend

2019-04-23 Thread Daniel van Vugt
Since this bug was optional and not planned to get fixed ("rls-bb-
notfixing"), it's not a blocking issue. But it does appear we get the
fix for free.

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

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

Title:
  [nvidia] Fail to launch gnome-shell (Wayland) on Ubuntu with EGLDevice
  backend

Status in mutter package in Ubuntu:
  Fix Released
Status in mutter source package in Bionic:
  Fix Committed

Bug description:
  [ Description ]

  Wayland sessions don't work with the Nvidia driver in 18.04, even
  after enabling them via the kernel command line 'nvidia-
  drm.modeset=1'.

  [ Fix ]

  See below for the changes from upstream that fix this, which we're
  uploading to disco-proposed now.

  [ QA ]

  Under the GNOME Micro Release Exception, you can believe this is
  fixed.

https://wiki.ubuntu.com/StableReleaseUpdates/GNOME

  It might be a good idea to test an nvidia machine, but it doesn't need
  explicit verification.

  [Original description]
  Fail to launch gnome-wayland-shell on Ubuntu-18.04 with EGLDevice backend due 
to following missing changes in mutter 3.28.3-2~ubuntu18.04.2

  commit 1bf2eb95b502ed0419b0fe8979c022cacaf79e84
  Author: Miguel A. Vico 
  Date:   Thu Jun 7 16:29:44 2018 -0700

  renderer/native: Choose first EGL config for non-GBM backends

  Commit 712ec30cd9be1f180c3789e7e6a042c5f7b5781d added the logic to only
  choose EGL configs that match the GBM_FORMAT_XRGB pixel format.
  However, there won't be any EGL config satisfying such criteria for
  non-GBM backends, such as EGLDevice.

  This change will let us choose the first EGL config for the EGLDevice
  backend, while still forcing GBM_FORMAT_XRGB configs for the GBM
  one.

  Related to: https://gitlab.gnome.org/GNOME/mutter/issues/2

  commit 8ee14a7cb7e8f072d2731d59c7dc735f83a9bb0b
  Author: Jonas Ådahl 
  Date:   Tue Nov 14 16:08:52 2017 +0800

  renderer/native: Also wrap flip closures for EGLStreams

  When using the EGLStream backend, the MetaRendererNative passed a
  GClosure to KMS when using EGLStreams, but KMS flip callback event
  handler in meta-gpu-kms.c expected a closure wrapped in a closure
  container, meaning it'd instead crash when using EGLStreams. Make the
  flip handler get what it expects also when using EGLStreams by wrapping
  the flip closure in the container before handing it over to EGL.

  https://bugzilla.gnome.org/show_bug.cgi?id=790316

  apt-cache policy mutter
  mutter:
  Installed: 3.28.3-2~ubuntu18.04.2
  Candidate: 3.28.3-2~ubuntu18.04.2
  Version table:
  *** 3.28.3-2~ubuntu18.04.2 500
  500 http://ports.ubuntu.com/ubuntu-ports bionic-updates/main arm64 Packages
  100 /var/lib/dpkg/status
  3.28.1-1ubuntu1 500
  500 http://ports.ubuntu.com/ubuntu-ports bionic/main arm64 Packages

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

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


[Desktop-packages] [Bug 1825126] Re: Shell dialog shadows are clipped on the top and left edges

2019-04-23 Thread Daniel van Vugt
** Changed in: mutter (Ubuntu)
 Assignee: (unassigned) => Daniel van Vugt (vanvugt)

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

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

Title:
  Shell dialog shadows are clipped on the top and left edges

Status in gnome-shell package in Ubuntu:
  New
Status in mutter package in Ubuntu:
  New

Bug description:
  Shell dialog shadows are clipped on the top and left edges.

  Although the shadow only seems to exist in the Yaru theme, not
  upstream, I can also fix the bug by removing:

  this._dialog.set_offscreen_redirect(Clutter.OffscreenRedirect.ALWAYS);

  from gnome-shell/js/ui/dialog.js

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: gnome-shell 3.32.0+git20190410-1ubuntu1
  ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6
  Uname: Linux 5.0.0-13-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  Date: Wed Apr 17 16:21:25 2019
  DisplayManager: gdm3
  InstallationDate: Installed on 2018-12-04 (134 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20181203)
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1826025] Re: gnome-shell trap int3 no desktop

2019-04-23 Thread Daniel van Vugt
Thank you for taking the time to report this bug and helping to make
Ubuntu better. It sounds like some part of the system has crashed. 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.

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

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

Title:
  gnome-shell trap int3 no desktop

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  After upgrade to 19.04, gnome-shell crashes on boot, leaving blinking
  cursor.

  [  498.989821] traps: gnome-shell[4066] trap int3 ip:7f7b604e6955
  sp:7fff92106950 error:0 in libglib-2.0.so.0.6000.0[7f7b604ad000+8]

  Restarting gdm3 service results in the same trap.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: xorg 1:7.7+19ubuntu12
  ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17
  Uname: Linux 4.18.0-13-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..02.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:02:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  390.116  Sun Jan 27 07:21:36 
PST 2019
   GCC version:  gcc version 8.3.0 (Ubuntu 8.3.0-6ubuntu1)
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  CompizPlugins: 
[core,bailer,detection,composite,opengl,compiztoolbox,decor,regex,gnomecompat,animation,vpswitch,grid,resize,imgpng,place,session,move,snap,unitymtgrabhandles,mousepoll,workarounds,expo,wall,ezoom,fade,scale,unityshell]
  Date: Tue Apr 23 09:56:22 2019
  DistUpgraded: 2019-04-22 15:16:02,086 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process 
“./xorg_fix_proprietary.py” (No such file or directory) (8))
  DistroCodename: disco
  DistroVariant: ubuntu
  DkmsStatus:
   nvidia, 390.116, 4.18.0-13-generic, x86_64: installed
   nvidia, 390.116, 5.0.0-13-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Matrox Electronics Systems Ltd. MGA G200eW WPCM450 [102b:0532] (rev 0a) 
(prog-if 00 [VGA controller])
 Subsystem: Super Micro Computer Inc MGA G200eW WPCM450 [15d9:0001]
   NVIDIA Corporation GP104 [GeForce GTX 1070] [10de:1b81] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: Gigabyte Technology Co., Ltd GP104 [GeForce GTX 1070] 
[1458:3703]
  InstallationDate: Installed on 2012-02-14 (2625 days ago)
  InstallationMedia: Ubuntu-Server 11.10 "Oneiric Ocelot" - Release amd64 
(20111011)
  MachineType: Supermicro X8DT3
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-13-generic 
root=/dev/mapper/mizuno-root ro nomdmonddf nomdmonisw nomdmonddf nomdmonisw 
nomdmonddf nomdmonisw nomdmonddf nomdmonisw
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to disco on 2019-04-22 (0 days ago)
  dmi.bios.date: 07/09/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2.2
  dmi.board.asset.tag: 1234567890
  dmi.board.name: X8DT3
  dmi.board.vendor: Supermicro
  dmi.board.version: 2.0
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 17
  dmi.chassis.vendor: Supermicro
  dmi.chassis.version: 1234567890
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2.2:bd07/09/2018:svnSupermicro:pnX8DT3:pvr1234567890:rvnSupermicro:rnX8DT3:rvr2.0:cvnSupermicro:ct17:cvr1234567890:
  dmi.product.family: 1234567890
  dmi.product.name: X8DT3
  dmi.product.sku: To Be Filled By O.E.M.
  dmi.product.version: 1234567890
  dmi.sys.vendor: Supermicro
  version.compiz: compiz 1:0.9.14.0+19.04.20190223.1-0ubuntu1
  version.libdrm2: libdrm2 2.4.97-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.2-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.2-1ubuntu1
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-0ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20180925-2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1
  

[Desktop-packages] [Bug 1825970] Re: "white noice" after resume from suspend

2019-04-23 Thread Daniel van Vugt
*** This bug is a duplicate of bug 1809407 ***
https://bugs.launchpad.net/bugs/1809407

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 1809407, 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 1809407
   [nvidia] Corrupted wallpaper after resuming from suspend

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

Title:
  "white noice" after resume from suspend

Status in xorg package in Ubuntu:
  New

Bug description:
  As a user, after I open my laptop to resume using it after it
  suspended by closing it, the background and some parts of some windows
  have this "white noice" instead.

  I can get rid of it if I restart gnome (alt+f2 / r / enter) but it's
  still very annoying.

  I'm using the latest nvidia driver 418

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: xorg 1:7.7+19ubuntu12
  ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6
  Uname: Linux 5.0.0-13-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  418.56  Fri Mar 15 12:59:26 
CDT 2019
   GCC version:  gcc version 8.3.0 (Ubuntu 8.3.0-6ubuntu1)
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Apr 23 04:02:14 2019
  DistUpgraded: Fresh install
  DistroCodename: disco
  DistroVariant: ubuntu
  DkmsStatus:
   anbox, 1, 5.0.0-13-generic, x86_64: installed
   nvidia, 418.56, 5.0.0-13-generic, x86_64: installed
   virtualbox, 6.0.6, 5.0.0-13-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: Dell 3rd Gen Core processor Graphics Controller [1028:054f]
   NVIDIA Corporation GK107M [GeForce GT 640M] [10de:0fd2] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: Dell GeForce GT 640M [1028:054f]
  InstallationDate: Installed on 2019-04-21 (1 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  MachineType: Dell Inc. XPS L521X
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-13-generic 
root=UUID=c42be4da-3229-4479-9793-032fb532c7e5 ro quiet splash vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/22/2013
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A14
  dmi.board.name: 029M77
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: A14
  dmi.modalias: 
dmi:bvnDellInc.:bvrA14:bd05/22/2013:svnDellInc.:pnXPSL521X:pvrA14:rvnDellInc.:rn029M77:rvrA00:cvnDellInc.:ct8:cvrA14:
  dmi.product.family: 103C_5335KV
  dmi.product.name: XPS L521X
  dmi.product.sku: XPS L521X
  dmi.product.version: A14
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.14.0+19.04.20190223.1-0ubuntu1
  version.libdrm2: libdrm2 2.4.97-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.2-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.2-1ubuntu1
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-0ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20180925-2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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

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


[Desktop-packages] [Bug 1826037] Re: Ubuntu Dock can't be transparent

2019-04-23 Thread Daniel van Vugt
** Changed in: gnome-shell-extension-ubuntu-dock (Ubuntu)
   Importance: Undecided => Medium

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

Title:
  Ubuntu Dock can't be transparent

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

Bug description:
  After  community changes in GNOME shell the Ubuntu Dock can't be transparent 
now, discussion here:
  https://gitlab.gnome.org/GNOME/gnome-shell/merge_requests/376

  It's looks like, the transparent for controls in gnome shell (top
  bar,right menu) it must be managed by extension

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

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


[Desktop-packages] [Bug 1825624] Re: Gnome 3.32 launcher not accepting icons

2019-04-23 Thread Daniel van Vugt
** Package changed: gnome-shell-extension-ubuntu-dock (Ubuntu) => gnome-
shell-extension-dashtodock (Ubuntu)

** Changed in: gnome-shell-extension-dashtodock (Ubuntu)
   Status: Incomplete => New

** Summary changed:

- Gnome 3.32 launcher not accepting icons
+ DashToDock launcher not accepting icons

** No longer affects: gnome-shell (Ubuntu)

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

Title:
  DashToDock launcher not accepting icons

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

Bug description:
  I am currently running Ubuntu 19.04 with vanilla Gnome shell 3.32
  installed.

  I find that the launcher in Gnome does not always accept the icon of a
  program. I have had difficulties with it accepting Firefox, Files and
  the Terminal icons.

  I "work around" seems to be to include the icon at the second last
  spot from the bottom.

  I have had this issue on two separate computers using the same configuration 
ie, Ubuntu 19.04 with vanilla Gnome shell 3.32.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  CurrentDesktop: GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 19.04
  GsettingsChanges:
   b'org.gnome.shell' b'favorite-apps' redacted by apport
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
  InstallationDate: Installed on 2019-04-18 (5 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  Package: gnome-shell-extension-ubuntu-dock
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6
  Tags: third-party-packages disco
  Uname: Linux 5.0.0-13-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True

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

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


[Desktop-packages] [Bug 1824855] Re: very long delay to display login prompt if there are a large number of uncleared desktop notifications

2019-04-23 Thread Daniel van Vugt
Also, it is gnome-shell requesting fprintd via js/gdm/fingerprint.js

** Package changed: gdm3 (Ubuntu) => gnome-shell (Ubuntu)

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

Title:
  very long delay to display login prompt if there are a large number of
  uncleared desktop notifications

Status in fprintd package in Ubuntu:
  Incomplete
Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  When waking my laptop screen up at the lock screen, it takes a very
  long time to display the password prompt (definitely longer than 30s,
  possibly longer than 1m - I didn't time it).  I notice that while
  waiting for the password prompt, the screen is showing a full list of
  (obfuscated) desktop notifications.  After logging in, I used the
  gnome-shell interface to clear the notifications; then I locked my
  screen again, at which point hitting the space bar caused the password
  prompt to show up immediately.

  So it looks like the time to display the password prompt might scale
  linearly with the number of notifications; which is not useful,
  because there is a finite number of (obfuscated!) notifications that
  will be displayed on the lock screen, and AFAIK you can't interact
  with them through the lock screen at all.  So we shouldn't be wasting
  time processing (and presumably rendering) notifications that will
  never be visible.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: gdm3 3.32.0-1ubuntu1
  ProcVersionSignature: Ubuntu 5.0.0-8.9-generic 5.0.1
  Uname: Linux 5.0.0-8-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Apr 15 09:58:23 2019
  InstallationDate: Installed on 2010-09-24 (3125 days ago)
  InstallationMedia: Ubuntu 10.04.1 LTS "Lucid Lynx" - Release amd64 
(20100816.1)
  SourcePackage: gdm3
  UpgradeStatus: Upgraded to disco on 2019-04-11 (3 days ago)

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

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


[Desktop-packages] [Bug 1824855] Re: very long delay to display login prompt if there are a large number of uncleared desktop notifications

2019-04-23 Thread Daniel van Vugt
Can you please try uninstalling 'fprintd'?

It sounds like all the detection, and the problem, is in there. Although
the kernel might also be reporting some device nodes that it shouldn't.

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

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

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

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

Title:
  very long delay to display login prompt if there are a large number of
  uncleared desktop notifications

Status in fprintd package in Ubuntu:
  Incomplete
Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  When waking my laptop screen up at the lock screen, it takes a very
  long time to display the password prompt (definitely longer than 30s,
  possibly longer than 1m - I didn't time it).  I notice that while
  waiting for the password prompt, the screen is showing a full list of
  (obfuscated) desktop notifications.  After logging in, I used the
  gnome-shell interface to clear the notifications; then I locked my
  screen again, at which point hitting the space bar caused the password
  prompt to show up immediately.

  So it looks like the time to display the password prompt might scale
  linearly with the number of notifications; which is not useful,
  because there is a finite number of (obfuscated!) notifications that
  will be displayed on the lock screen, and AFAIK you can't interact
  with them through the lock screen at all.  So we shouldn't be wasting
  time processing (and presumably rendering) notifications that will
  never be visible.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: gdm3 3.32.0-1ubuntu1
  ProcVersionSignature: Ubuntu 5.0.0-8.9-generic 5.0.1
  Uname: Linux 5.0.0-8-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Apr 15 09:58:23 2019
  InstallationDate: Installed on 2010-09-24 (3125 days ago)
  InstallationMedia: Ubuntu 10.04.1 LTS "Lucid Lynx" - Release amd64 
(20100816.1)
  SourcePackage: gdm3
  UpgradeStatus: Upgraded to disco on 2019-04-11 (3 days ago)

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

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


[Desktop-packages] [Bug 1824874] Re: undismissable, unclickable authentication dialog left on screen (top-left corner) after policykit authentication [pushModal: invocation of begin_modal failed]

2019-04-23 Thread Daniel van Vugt
** Summary changed:

- undismissable, unclickable authentication dialog left on screen after 
policykit authentication [pushModal: invocation of begin_modal failed]
+ undismissable, unclickable authentication dialog left on screen (top-left 
corner) after policykit authentication [pushModal: invocation of begin_modal 
failed]

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

Title:
  undismissable, unclickable authentication dialog left on screen (top-
  left corner) after policykit authentication [pushModal: invocation of
  begin_modal failed]

Status in gnome-shell package in Ubuntu:
  Confirmed

Bug description:
  In disco, when policykit prompted me for a password in order for
  update-manager to dispatch instructions to aptdaemon to perform
  package updates, the password dialog remained on the screen after I
  clicked 'authenticate'.

  The window is not clickable, it appears not to even be a window -
  mouse presses are received by the window underneath.  The exception is
  that the 'cancel' button is active and receives mouse events - but
  clicking it does nothing.

  This may be a gnome-shell issue rather than policykit.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: policykit-1 0.105-25
  ProcVersionSignature: Ubuntu 5.0.0-8.9-generic 5.0.1
  Uname: Linux 5.0.0-8-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Apr 15 13:14:33 2019
  InstallationDate: Installed on 2010-09-24 (3125 days ago)
  InstallationMedia: Ubuntu 10.04.1 LTS "Lucid Lynx" - Release amd64 
(20100816.1)
  SourcePackage: policykit-1
  UpgradeStatus: Upgraded to disco on 2019-04-11 (3 days ago)

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

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


[Desktop-packages] [Bug 1780058] Re: Failed to detect non-ascii encoding in "Extract here" of zip

2019-04-23 Thread Lance Tien
Sorry now I could only trigger bug that both extract method(open then
extract and 'Extract Here') did something wrong to filename. Attachment
is a sample zip file. `unar` will guess the right filename encoding.

** Attachment added: "pig+hive+spark+-+教学版.zip"
   
https://bugs.launchpad.net/ubuntu/+source/file-roller/+bug/1780058/+attachment/5258391/+files/pig+hive+spark+-+%E6%95%99%E5%AD%A6%E7%89%88.zip

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

Title:
  Failed to detect non-ascii encoding in "Extract here" of zip

Status in file-roller package in Ubuntu:
  Incomplete

Bug description:
  I'm glad to see that open a zip file and extract, file-roller could detect 
Chinese filename encoding without problem. But using right-click menu "Extract 
here", filename encoding are wrong. I guess these two ways should share same 
code.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2018-05-03 (62 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  NonfreeKernelModules: kpatch_livepatch_Ubuntu_4_15_0_23_25_generic_40
  Package: file-roller 3.28.0-1ubuntu1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
  Tags:  bionic
  Uname: Linux 4.15.0-23-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2018-05-03 (355 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  Package: file-roller 3.28.0-1ubuntu1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.15.0-47.50-generic 4.15.18
  Tags:  bionic
  Uname: Linux 4.15.0-47-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True

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

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


[Desktop-packages] [Bug 1215524] Re: Thunderbird deletes messages rather than move them to Deleted

2019-04-23 Thread Bug Watch Updater
** Changed in: thunderbird
   Status: New => Invalid

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

Title:
  Thunderbird deletes messages rather than move them to Deleted

Status in Mozilla Thunderbird:
  Invalid
Status in thunderbird package in Ubuntu:
  Confirmed

Bug description:
  On Ubuntu Precise 64 bit using Thunderbird v17.0.8, deleting a message
  (on Gmail account using IMAP) from Inbox, the message is not moved to
  the Deleted folder but is removed completely.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: thunderbird 17.0.8+build1-0ubuntu0.12.04.1
  ProcVersionSignature: Ubuntu 3.5.0-39.60~precise1-generic 3.5.7.17
  Uname: Linux 3.5.0-39-generic x86_64
  AddonCompatCheckDisabled: False
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.25.
  AplayDevices:
    List of PLAYBACK Hardware Devices 
   card 0: PCH [HDA Intel PCH], device 0: ALC887-VD Analog [ALC887-VD Analog]
 Subdevices: 1/1
 Subdevice #0: subdevice #0
  ApportVersion: 2.0.1-0ubuntu17.4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  john   2158 F pulseaudio
   /dev/snd/controlC1:  john   2158 F pulseaudio
  BuildID: 20130804001519
  CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 
not found.
  Card0.Amixer.info:
   Card hw:0 'PCH'/'HDA Intel PCH at 0xf7d0 irq 43'
 Mixer name : 'Realtek ALC887-VD'
 Components : 'HDA:10ec0887,1458a002,00100302'
 Controls  : 40
 Simple ctrls  : 21
  Card1.Amixer.info:
   Card hw:1 'U0x46d0x9a4'/'USB Device 0x46d:0x9a4 at usb-:00:1d.0-1.6.5, 
high speed'
 Mixer name : 'USB Mixer'
 Components : 'USB046d:09a4'
 Controls  : 2
 Simple ctrls  : 1
  Card1.Amixer.values:
   Simple mixer control 'Mic',0
 Capabilities: cvolume cvolume-joined cswitch cswitch-joined penum
 Capture channels: Mono
 Limits: Capture 0 - 14
 Mono: Capture 7 [50%] [29.00dB] [on]
  Channel: Unavailable
  Date: Thu Aug 22 17:11:42 2013
  ForcedLayersAccel: False
  IfupdownConfig:
   auto lo
   iface lo inet loopback
  InstallationMedia: Ubuntu 12.04.2 LTS "Precise Pangolin" - Release amd64 
(20130213)
  IpRoute:
   default via 192.168.1.1 dev eth0  proto static 
   169.254.0.0/16 dev eth0  scope link  metric 1000 
   192.168.1.0/24 dev eth0  proto kernel  scope link  src 192.168.1.12  metric 1
  IwConfig:
   eth0  no wireless extensions.
   
   lono wireless extensions.
  MarkForUpload: True
  PrefSources:
   prefs.js
   
[Profile]/extensions/{e2fda1a4-762b-4020-b5ad-a41df1933103}/defaults/preferences/lightning.js
   
[Profile]/extensions/{a62ef8ec-5fdc-40c2-873c-223b8a6925cc}/defaults/preferences/preferences.js
  ProcEnviron:
   LANGUAGE=en_GB:en
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  Profiles: Profile0 (Default) - LastVersion=17.0.8/20130804001519 (In use)
  RelatedPackageVersions:
   rhythmbox-mozilla 2.96-0ubuntu4.3
   totem-mozilla 3.0.1-0ubuntu21.1
  RfKill:
   0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
  RunningIncompatibleAddons: False
  SourcePackage: thunderbird
  UpgradeStatus: No upgrade log present (probably fresh install)
  WifiSyslog:
   
  dmi.bios.date: 12/19/2011
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: FA
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: H61M-S2PV
  dmi.board.vendor: INTEL Corporation
  dmi.board.version: To be filled by O.E.M.
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Tecohnology Co., Ltd.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrFA:bd12/19/2011:svnGigabyteTecohnologyCo.,Ltd.:pnH61M-S2PV:pvrTobefilledbyO.E.M.:rvnINTELCorporation:rnH61M-S2PV:rvrTobefilledbyO.E.M.:cvnGigabyteTecohnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: H61M-S2PV
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: Gigabyte Tecohnology Co., Ltd.

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

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


[Desktop-packages] [Bug 1822857] Re: Alt+Tab produces visual artefacts when a modal dialog is open [with mismatched mutter packages installed]

2019-04-23 Thread Daniel van Vugt
Thanks. I'm glad to have fixed it already then :)

https://gitlab.gnome.org/GNOME/mutter/merge_requests/117

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

Title:
  Alt+Tab produces visual artefacts when a modal dialog is open [with
  mismatched mutter packages installed]

Status in Mutter:
  Fix Released
Status in mutter package in Ubuntu:
  Won't Fix

Bug description:
  Steps to reproduce:

  0. Change the default Alt+Tab to switch windows
  1. Have some windows open to switch between them
  2. Start Thunderbird
  3. Go to Account Settings, which is a child window for account settings (or 
any child window of another app)
  4. Press Alt+Tab to switch windows

  Going through Alt+Tab produces visual artefacts. See the attached
  screencast.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.28.3+git20190124-0ubuntu18.04.1
  ProcVersionSignature: Ubuntu 4.18.0-16.17~18.04.1-generic 4.18.20
  Uname: Linux 4.18.0-16-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Apr  2 18:35:42 2019
  DisplayManager: gdm3
  InstallationDate: Installed on 2018-11-29 (123 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1820832] Re: [nvidia] [xorg] multiple monitors: limits the framerate of faster 120/144hz monitors to 60hz

2019-04-23 Thread Daniel van Vugt
Yes, sorry. I am trying to track hundreds of bugs in my head and I don't
always remember (or reread) the context of each one every day.

I have now modified the task list for this bug so it tracks both Nvidia
and AMD drivers.

** No longer affects: mutter

** Also affects: xserver-xorg-video-amdgpu (Ubuntu)
   Importance: Undecided
   Status: New

** Summary changed:

- [nvidia] [xorg] multiple monitors: limits the framerate of faster 120/144hz 
monitors to 60hz
+ [xorg] multiple monitors: limits the framerate of faster 120/144hz monitors 
to 60hz

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

Title:
  [xorg] multiple monitors: limits the framerate of faster 120/144hz
  monitors to 60hz

Status in mutter package in Ubuntu:
  Invalid
Status in nvidia-graphics-drivers-418 package in Ubuntu:
  Confirmed
Status in xserver-xorg-video-amdgpu package in Ubuntu:
  New

Bug description:
  multiple monitors on xorg
  =

  Was recently discussed over on
  https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1763892

  Another user + myself have the following issue:

  The slowest connected display limits the FPS. The test case we used is
  over at the top of the other bug report ^^

  This we found today happens with either amd vega graphics, or nvidia
  pascal graphics, the vendor doesn't seem to matter. We have both seen
  the same issue (xorg).

  This is on 18.10, and booting into the 'Gnome (xorg)' login option.
  With the FPS being logged by journalctl -f. With only single monitor
  attached. Then it initially goes as high as the primary monitor can
  show. (And glmark2 running in background, to maintain a continued
  load). Which is 120fps for my case. Then as soon as secondary monitor
  is plugged in, which is a 60hz TV. This is being plugged into the HDMI
  port of the same graphics card in real time. Then the FPS logged by
  'journalctl -f' drops, and becomes capped to 60hz, in the output being
  printed by journalctl -f.

  My setup:
  kernel 5.0.0-05-lowlatency #201903032031
  NVIDIA Driver for UNIX platforms 415.27 (the closed source one)
  ubuntu 18.10

  mutter version:

  mutter/cosmic-updates,now 3.30.2-1~ubuntu18.10.4 amd64 [installed]
  mutter-common/cosmic-updates,cosmic-updates,now 3.30.2-1~ubuntu18.10.4 all 
[installed]

  To confirm where the '.4' at the very end of the ~ubuntu18.10.4
  version number, it seems to be that we have updated now on our client
  machines the be most recent bugfix updates, kindly provided by Daniel.
  Which closed the other bug
  https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1763892 being
  referred to, as being solved for people's single monitor scenarios.

  Thanks again for the other recent bug fixes in this area, it is a nice
  progress. Very helpful! We hope you can also look into this latest
  problem / issue for the multiple monitor scenario.

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

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


[Desktop-packages] [Bug 1780058] Re: Failed to detect non-ascii encoding in "Extract here" of zip

2019-04-23 Thread Lance Tien
apport information

** Description changed:

  I'm glad to see that open a zip file and extract, file-roller could detect 
Chinese filename encoding without problem. But using right-click menu "Extract 
here", filename encoding are wrong. I guess these two ways should share same 
code.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2018-05-03 (62 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  NonfreeKernelModules: kpatch_livepatch_Ubuntu_4_15_0_23_25_generic_40
  Package: file-roller 3.28.0-1ubuntu1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
  Tags:  bionic
  Uname: Linux 4.15.0-23-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
+ --- 
+ ProblemType: Bug
+ ApportVersion: 2.20.9-0ubuntu7.6
+ Architecture: amd64
+ CurrentDesktop: ubuntu:GNOME
+ DistroRelease: Ubuntu 18.04
+ InstallationDate: Installed on 2018-05-03 (355 days ago)
+ InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
+ Package: file-roller 3.28.0-1ubuntu1
+ PackageArchitecture: amd64
+ ProcVersionSignature: Ubuntu 4.15.0-47.50-generic 4.15.18
+ Tags:  bionic
+ Uname: Linux 4.15.0-47-generic x86_64
+ UpgradeStatus: No upgrade log present (probably fresh install)
+ UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
+ _MarkForUpload: True

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

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

Title:
  Failed to detect non-ascii encoding in "Extract here" of zip

Status in file-roller package in Ubuntu:
  Incomplete

Bug description:
  I'm glad to see that open a zip file and extract, file-roller could detect 
Chinese filename encoding without problem. But using right-click menu "Extract 
here", filename encoding are wrong. I guess these two ways should share same 
code.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2018-05-03 (62 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  NonfreeKernelModules: kpatch_livepatch_Ubuntu_4_15_0_23_25_generic_40
  Package: file-roller 3.28.0-1ubuntu1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
  Tags:  bionic
  Uname: Linux 4.15.0-23-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2018-05-03 (355 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  Package: file-roller 3.28.0-1ubuntu1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.15.0-47.50-generic 4.15.18
  Tags:  bionic
  Uname: Linux 4.15.0-47-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True

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

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


[Desktop-packages] [Bug 1816231] Re: There is regular screen flickering/flashing (when the mouse isn't moving)

2019-04-23 Thread Daniel van Vugt
This looks like a low level problem. So either in the kernel, or in the
Xorg driver.

Since you are using the old Xorg driver 'xserver-xorg-video-intel', I
first recommend removing that package or changing your Xorg config to
NOT use the 'intel' driver. Your system is easily new enough to use the
recommended 'modesetting' driver instead.

Please remove the 'intel' driver and retest. Then please run:

  journalctl -b0 > journal.txt

and send us the file 'journal.txt'.

** Changed in: xorg-server (Ubuntu)
   Status: New => Incomplete

** Package changed: xorg-server (Ubuntu) => xserver-xorg-video-intel
(Ubuntu)

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

Title:
  There is regular screen flickering/flashing (when the mouse isn't
  moving)

Status in xserver-xorg-video-intel package in Ubuntu:
  Incomplete

Bug description:
  I have installed the 18.04.2 lts version. I have a basic intel graphics card
  It says unable to locate package pkgname when I type apt-cache policy 
pkgname. I think it's a problem with the xorg file. not sure.
  When the mouse tracker is moving there does'nt seem to be a problem.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.18.0-15.16~18.04.1-generic 4.18.20
  Uname: Linux 4.18.0-15-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Feb 16 18:06:57 2019
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: I just need to know a workaround
  GraphicsCard:
   Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA 
controller])
 Subsystem: ASUSTeK Computer Inc. HD Graphics 5500 [1043:19ad]
  InstallationDate: Installed on 2019-02-16 (0 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  MachineType: ASUSTeK COMPUTER INC. X555LAB
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-15-generic 
root=UUID=ef09309f-b8f6-4d98-9c90-7b08ac5e2392 ro quiet splash vt.handoff=1
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/19/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: X555LAB.303
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: X555LAB
  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.:bvrX555LAB.303:bd12/19/2014:svnASUSTeKCOMPUTERINC.:pnX555LAB:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX555LAB:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: X
  dmi.product.name: X555LAB
  dmi.product.sku: ASUS-NotebookSKU
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.95-1~18.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.2-0ubuntu1~18.04.2
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.2-0ubuntu1~18.04.2
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A

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

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


[Desktop-packages] [Bug 1816231] Re: There is a constant screen flickereing.

2019-04-23 Thread Daniel van Vugt
Thanks for the video...

https://drive.google.com/file/d/1ePqj5TCcUje1zcnjIyglkSqFW7qp2cW8/view

** Summary changed:

- There is a constant screen flickereing.
+ There is regular screen flickering/flashing (when the mouse isn't moving)

** Changed in: xorg-server (Ubuntu)
   Status: Expired => New

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

Title:
  There is regular screen flickering/flashing (when the mouse isn't
  moving)

Status in xserver-xorg-video-intel package in Ubuntu:
  Incomplete

Bug description:
  I have installed the 18.04.2 lts version. I have a basic intel graphics card
  It says unable to locate package pkgname when I type apt-cache policy 
pkgname. I think it's a problem with the xorg file. not sure.
  When the mouse tracker is moving there does'nt seem to be a problem.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.18.0-15.16~18.04.1-generic 4.18.20
  Uname: Linux 4.18.0-15-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Feb 16 18:06:57 2019
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: I just need to know a workaround
  GraphicsCard:
   Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA 
controller])
 Subsystem: ASUSTeK Computer Inc. HD Graphics 5500 [1043:19ad]
  InstallationDate: Installed on 2019-02-16 (0 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  MachineType: ASUSTeK COMPUTER INC. X555LAB
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-15-generic 
root=UUID=ef09309f-b8f6-4d98-9c90-7b08ac5e2392 ro quiet splash vt.handoff=1
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/19/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: X555LAB.303
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: X555LAB
  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.:bvrX555LAB.303:bd12/19/2014:svnASUSTeKCOMPUTERINC.:pnX555LAB:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX555LAB:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: X
  dmi.product.name: X555LAB
  dmi.product.sku: ASUS-NotebookSKU
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.95-1~18.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.2-0ubuntu1~18.04.2
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.2-0ubuntu1~18.04.2
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A

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

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


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

2019-04-23 Thread Lance Tien
apport information

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

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

Title:
  Failed to detect non-ascii encoding in "Extract here" of zip

Status in file-roller package in Ubuntu:
  Incomplete

Bug description:
  I'm glad to see that open a zip file and extract, file-roller could detect 
Chinese filename encoding without problem. But using right-click menu "Extract 
here", filename encoding are wrong. I guess these two ways should share same 
code.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2018-05-03 (62 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  NonfreeKernelModules: kpatch_livepatch_Ubuntu_4_15_0_23_25_generic_40
  Package: file-roller 3.28.0-1ubuntu1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
  Tags:  bionic
  Uname: Linux 4.15.0-23-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2018-05-03 (355 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  Package: file-roller 3.28.0-1ubuntu1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.15.0-47.50-generic 4.15.18
  Tags:  bionic
  Uname: Linux 4.15.0-47-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True

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

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


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

2019-04-23 Thread Lance Tien
apport information

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

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

Title:
  Failed to detect non-ascii encoding in "Extract here" of zip

Status in file-roller package in Ubuntu:
  Incomplete

Bug description:
  I'm glad to see that open a zip file and extract, file-roller could detect 
Chinese filename encoding without problem. But using right-click menu "Extract 
here", filename encoding are wrong. I guess these two ways should share same 
code.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2018-05-03 (62 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  NonfreeKernelModules: kpatch_livepatch_Ubuntu_4_15_0_23_25_generic_40
  Package: file-roller 3.28.0-1ubuntu1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
  Tags:  bionic
  Uname: Linux 4.15.0-23-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2018-05-03 (355 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  Package: file-roller 3.28.0-1ubuntu1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.15.0-47.50-generic 4.15.18
  Tags:  bionic
  Uname: Linux 4.15.0-47-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True

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

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


[Desktop-packages] [Bug 1825625] Re: Some apps appear blurry with framebuffer scaling

2019-04-23 Thread Daniel van Vugt
** Bug watch added: gitlab.gnome.org/GNOME/mutter/issues #566
   https://gitlab.gnome.org/GNOME/mutter/issues/566

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

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

Title:
  Some apps appear blurry with framebuffer scaling

Status in Mutter:
  Unknown
Status in firefox package in Ubuntu:
  New
Status in libreoffice package in Ubuntu:
  New
Status in mutter package in Ubuntu:
  Invalid
Status in thunderbird package in Ubuntu:
  New

Bug description:
  Setting the framebuffer scaling (with gsettings set org.gnome.mutter
  experimental-features "['scale-monitor-framebuffer']") allows the
  display on HiDPi to be scaled to something different than
  100%/200%/300%.

  Which would be fine.

  However, the display is rendered such that most applications provide
  blurred display of text and graphics.

  This is not always the case (e.g. system settings are displayed
  correctly, Thunderbird and Firefox are blurred).

  Also the screen flickers when selection menus or resizing the windows.
  A black border appears around the windows where the shadow should appear. It 
gets removed a few seconds later but still is irritating.

  This issue is not urgent, just annoying. It can be worked around by
  removing the settings in gsetting / dconf.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: mutter 3.32.0+git20190410-1ubuntu1
  ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6
  Uname: Linux 5.0.0-13-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Apr 20 11:11:55 2019
  InstallationDate: Installed on 2018-04-30 (355 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  SourcePackage: mutter
  UpgradeStatus: Upgraded to disco on 2019-04-19 (0 days ago)

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

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


[Desktop-packages] [Bug 1825580] Re: Gnome Online Accounts fails to sign in Exchange emails

2019-04-23 Thread KEVIN M LYON
Also seeing this:

Apr 23 19:43:57 kevin-Dell-17 gnome-control-c[5696]: 
goa_ews_client_autodiscover() failed: 401 — Unauthorized
Apr 23 19:44:52 kevin-Dell-17 gnome-control-c[5696]: 
goa_ews_client_autodiscover() failed: 401 — Unauthorized
Apr 23 19:45:52 kevin-Dell-17 gnome-control-c[5696]: 
goa_ews_client_autodiscover() failed: 7 — Could not connect: Socket I/O timed 
out

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

Title:
  Gnome Online Accounts fails to sign in Exchange emails

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

Bug description:
  After upgrading from 18.10 and/or on fresh install, a known-working
  Exchange email setup fails to sign in, giving "Error 7: Unexpected
  response from server".  Tested the same settings and credentials on a
  new install of 18.10 and it worked.

  I have Evolution and Evolution-ews installed on all instances, working
  in 18.10, not in 19.04.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: gnome-online-accounts 3.32.0-1ubuntu1
  ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6
  Uname: Linux 5.0.0-13-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Apr 19 16:38:32 2019
  InstallationDate: Installed on 2018-03-24 (391 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180208)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-online-accounts
  UpgradeStatus: Upgraded to disco on 2019-03-12 (38 days ago)

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

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


[Desktop-packages] [Bug 1825580] Re: Gnome Online Accounts fails to sign in Exchange emails

2019-04-23 Thread KEVIN M LYON
Added journalctl full log on a new install.  Let me know if there's more
specific info I can look up or provide.

** Attachment added: "Full systemctl output"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-online-accounts/+bug/1825580/+attachment/5258377/+files/full_log.txt

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

Title:
  Gnome Online Accounts fails to sign in Exchange emails

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

Bug description:
  After upgrading from 18.10 and/or on fresh install, a known-working
  Exchange email setup fails to sign in, giving "Error 7: Unexpected
  response from server".  Tested the same settings and credentials on a
  new install of 18.10 and it worked.

  I have Evolution and Evolution-ews installed on all instances, working
  in 18.10, not in 19.04.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: gnome-online-accounts 3.32.0-1ubuntu1
  ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6
  Uname: Linux 5.0.0-13-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Apr 19 16:38:32 2019
  InstallationDate: Installed on 2018-03-24 (391 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180208)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-online-accounts
  UpgradeStatus: Upgraded to disco on 2019-03-12 (38 days ago)

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

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


[Desktop-packages] [Bug 1825580] Re: Gnome Online Accounts fails to sign in Exchange emails

2019-04-23 Thread KEVIN M LYON
Added a log filtered for "goa-" items.  Let me know if there's more
specific info I can look up or provide.

** Attachment added: "Filtered for term goa-"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-online-accounts/+bug/1825580/+attachment/5258378/+files/goa.txt

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

Title:
  Gnome Online Accounts fails to sign in Exchange emails

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

Bug description:
  After upgrading from 18.10 and/or on fresh install, a known-working
  Exchange email setup fails to sign in, giving "Error 7: Unexpected
  response from server".  Tested the same settings and credentials on a
  new install of 18.10 and it worked.

  I have Evolution and Evolution-ews installed on all instances, working
  in 18.10, not in 19.04.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: gnome-online-accounts 3.32.0-1ubuntu1
  ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6
  Uname: Linux 5.0.0-13-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Apr 19 16:38:32 2019
  InstallationDate: Installed on 2018-03-24 (391 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180208)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-online-accounts
  UpgradeStatus: Upgraded to disco on 2019-03-12 (38 days ago)

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

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


[Desktop-packages] [Bug 1825396] Re: "Open in Terminal" returns "Text ended before matching quote was found for '"

2019-04-23 Thread Bug Watch Updater
** Changed in: gnome-shell-extension-desktop-icons
   Status: New => Fix Released

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

Title:
  "Open in Terminal" returns "Text ended before matching quote was found
  for '"

Status in gnome-shell-extension-desktop-icons:
  Fix Released
Status in gnome-shell-extension-desktop-icons package in Ubuntu:
  Confirmed

Bug description:
  Attempting to open a Desktop folder named "aaa'bbb" (without double
  quotes) using the "Open in Terminal" option from the context menu
  produces a notification message stating:

  Execution of "x-terminal-emulator --working-directory=/home/... 
  Text ended before matching quote was found for '. (The text was 
"x-terminal-emulator --working-directory=/home/x/Desktop/aaa'bbb")

  This suggests improper escaping (possible security impact with command
  injection).

  Steps to reproduce:

  1. On the Ubuntu 19.04.0 amd64 Desktop, right-click, and select "New folder"
  2. Enter the following folder name and press Enter: aaa'bbb
  3. Right-click on the newly created folder icon
  4. Select "Open in Terminal"
  5. The above notification pops up, no terminal window opens.

  The expected outcome would be:
  5. A terminal window opens in directory ~/Desktop/aaa'bbb

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: gnome-shell-extension-desktop-icons 19.01.1-1
  ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6
  Uname: Linux 5.0.0-13-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Apr 18 18:40:28 2019
  InstallationDate: Installed on 2019-04-14 (4 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190413.2)
  PackageArchitecture: all
  SourcePackage: gnome-shell-extension-desktop-icons
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1826063] Re: Broken package 0.30.2-3~ubuntu18.04.1

2019-04-23 Thread Dimitri John Ledkov
well, libssl1.1 >= 1.1.1 is available from bionic-proposed, but not yet
from bionic-updates.

I guess we should not have yet published neon27 into bionic-updates, and
should probably keep the update in bionic-proposed for now.

** Tags added: regression-update

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

** Changed in: neon27 (Ubuntu)
   Importance: Undecided => Critical

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

Title:
  Broken package 0.30.2-3~ubuntu18.04.1

Status in neon27 package in Ubuntu:
  Confirmed

Bug description:
  I think there might be a problem with this new neon27 package
  published for bionic:
  https://launchpad.net/ubuntu/+source/neon27/0.30.2-3~ubuntu18.04.1.

  The package now defines a dependency for libssl1.1 (>= 1.1.1) but not
  such version is available on Ubuntu 18.04:
  https://packages.ubuntu.com/bionic/libssl1.1.

  Therefore, the package can not be installed and leads to a broken
  package situation

  
  === apt install libneon27 ===

  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  Some packages could not be installed. This may mean that you have
  requested an impossible situation or if you are using the unstable
  distribution that some required packages have not yet been created
  or been moved out of Incoming.
  The following information may help to resolve the situation:
  The following packages have unmet dependencies:
   libneon27 : Depends: libssl1.1 (>= 1.1.1) but 1.1.0g-2ubuntu4.3 is to be 
installed
  E: Unable to correct problems, you have held broken packages.

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

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


[Desktop-packages] [Bug 871325] Re: Implement Unity Launcher API in Firefox for downloads' progress and quicklist

2019-04-23 Thread Bug Watch Updater
** Changed in: firefox
   Status: Confirmed => Won't Fix

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

Title:
  Implement Unity Launcher API in Firefox for downloads' progress and
  quicklist

Status in Mozilla Firefox:
  Won't Fix
Status in One Hundred Papercuts:
  Confirmed
Status in firefox package in Ubuntu:
  Confirmed

Bug description:
  In Ubuntu, Firefox should use the Unity Launcher API to show progress of the 
downloads and to show a quicklist (for example, New Window).
  There's yet an extension about the downloads' progress: UnityFox 
(https://launchpad.net/unityfox).
  Could you integrate the extension in Firefox by default?

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

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


[Desktop-packages] [Bug 871325]

2019-04-23 Thread Mcastelluccio
We can open a new bug for GNOME Shell, if they decide to support
progress bars (even if they do, I doubt they will use libunity).

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

Title:
  Implement Unity Launcher API in Firefox for downloads' progress and
  quicklist

Status in Mozilla Firefox:
  Won't Fix
Status in One Hundred Papercuts:
  Confirmed
Status in firefox package in Ubuntu:
  Confirmed

Bug description:
  In Ubuntu, Firefox should use the Unity Launcher API to show progress of the 
downloads and to show a quicklist (for example, New Window).
  There's yet an extension about the downloads' progress: UnityFox 
(https://launchpad.net/unityfox).
  Could you integrate the extension in Firefox by default?

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

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


[Desktop-packages] [Bug 871325]

2019-04-23 Thread Adolfo Jayme
libunity’s API is also consumed by third-party docks like Plank, and
I’ve heard there are plans to get progress bars into GNOME Shell, so…

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

Title:
  Implement Unity Launcher API in Firefox for downloads' progress and
  quicklist

Status in Mozilla Firefox:
  Won't Fix
Status in One Hundred Papercuts:
  Confirmed
Status in firefox package in Ubuntu:
  Confirmed

Bug description:
  In Ubuntu, Firefox should use the Unity Launcher API to show progress of the 
downloads and to show a quicklist (for example, New Window).
  There's yet an extension about the downloads' progress: UnityFox 
(https://launchpad.net/unityfox).
  Could you integrate the extension in Firefox by default?

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

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


[Desktop-packages] [Bug 871325]

2019-04-23 Thread Robert-strong-bugs
This would either be a widget or a theme bug

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

Title:
  Implement Unity Launcher API in Firefox for downloads' progress and
  quicklist

Status in Mozilla Firefox:
  Won't Fix
Status in One Hundred Papercuts:
  Confirmed
Status in firefox package in Ubuntu:
  Confirmed

Bug description:
  In Ubuntu, Firefox should use the Unity Launcher API to show progress of the 
downloads and to show a quicklist (for example, New Window).
  There's yet an extension about the downloads' progress: UnityFox 
(https://launchpad.net/unityfox).
  Could you integrate the extension in Firefox by default?

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

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


[Desktop-packages] [Bug 255345] Re: Comments field in Nautilus' Audio properties tab does not wrap for long comments on audio files

2019-04-23 Thread Bug Watch Updater
** Changed in: nautilus
   Status: Unknown => New

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

Title:
  Comments field in Nautilus' Audio properties tab does not wrap for
  long comments on audio files

Status in Nautilus:
  New
Status in Totem:
  Expired
Status in totem package in Ubuntu:
  Triaged

Bug description:
  Binary package hint: nautilus

  ---System Info---
  Description:  Ubuntu 8.04.1
  Release:  8.04

  ---Package Info---
  nautilus:
Installed: 1:2.22.3-0ubuntu2
Candidate: 1:2.22.3-0ubuntu2
Version table:
   *** 1:2.22.3-0ubuntu2 0
  500 http://ftp.ussg.iu.edu hardy-updates/main Packages
  100 /var/lib/dpkg/status
   1:2.22.2-0ubuntu4 0
  500 http://ftp.ussg.iu.edu hardy/main Packages

  ---Problem Info---
  When using Nautilus to view the properties of an audio file format that 
contains metadata (such as MP3s) the audio tab does not wrap the Comments data. 
 For longer comments, it makes it impossible to view the information about the 
file even when the File Properties window is expanded to its maximum size.

  See attached screenshot for an example.

  ProblemType: Bug
  Architecture: i386
  Date: Wed Aug  6 08:41:09 2008
  DistroRelease: Ubuntu 8.04
  ExecutablePath: /usr/bin/nautilus
  Package: nautilus 1:2.22.3-0ubuntu2
  PackageArchitecture: i386
  ProcEnviron:
   PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: nautilus
  Uname: Linux 2.6.24-19-generic i686

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

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


[Desktop-packages] [Bug 1826061] [NEW] gdm not displaying any graphics in Ubuntu 19.04

2019-04-23 Thread BertN45
Public bug reported:

My hardware: GT218 in a NVIDIA GeForce 8400GS rev 3.
Driver: Nvidia 340.107

Ubuntu 19.04 does not display any graphics, it stays at the display of
the CLI, after announcing the start of the gnome display manager.

I tried a fresh install of Ubuntu 19.04 and I tried to add the Ubuntu desktop 
to Xubuntu 19.04 with the same display manager, giving the same result.
The driver works well with Xubuntu 19.04 and Ubuntu Mate 19.04.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: gdm3 (not installed)
ProcVersionSignature: Ubuntu 4.15.0-47.50-generic 4.15.18
Uname: Linux 4.15.0-47-generic x86_64
NonfreeKernelModules: nvidia zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.9-0ubuntu7.6
Architecture: amd64
CurrentDesktop: MATE
Date: Tue Apr 23 16:15:02 2019
SourcePackage: gdm3
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug bionic

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

Title:
  gdm not displaying any graphics in Ubuntu 19.04

Status in gdm3 package in Ubuntu:
  New

Bug description:
  My hardware: GT218 in a NVIDIA GeForce 8400GS rev 3.
  Driver: Nvidia 340.107

  Ubuntu 19.04 does not display any graphics, it stays at the display of
  the CLI, after announcing the start of the gnome display manager.

  I tried a fresh install of Ubuntu 19.04 and I tried to add the Ubuntu desktop 
to Xubuntu 19.04 with the same display manager, giving the same result.
  The driver works well with Xubuntu 19.04 and Ubuntu Mate 19.04.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gdm3 (not installed)
  ProcVersionSignature: Ubuntu 4.15.0-47.50-generic 4.15.18
  Uname: Linux 4.15.0-47-generic x86_64
  NonfreeKernelModules: nvidia zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  CurrentDesktop: MATE
  Date: Tue Apr 23 16:15:02 2019
  SourcePackage: gdm3
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1826063] [NEW] Broken package 0.30.2-3~ubuntu18.04.1

2019-04-23 Thread Julien Langlois
Public bug reported:

I think there might be a problem with this new neon27 package published
for bionic:
https://launchpad.net/ubuntu/+source/neon27/0.30.2-3~ubuntu18.04.1.

The package now defines a dependency for libssl1.1 (>= 1.1.1) but not
such version is available on Ubuntu 18.04:
https://packages.ubuntu.com/bionic/libssl1.1.

Therefore, the package can not be installed and leads to a broken
package situation


=== apt install libneon27 ===

Reading package lists... Done
Building dependency tree   
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:
The following packages have unmet dependencies:
 libneon27 : Depends: libssl1.1 (>= 1.1.1) but 1.1.0g-2ubuntu4.3 is to be 
installed
E: Unable to correct problems, you have held broken packages.

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

** Attachment added: "apt-cache-show-libneon27.txt"
   
https://bugs.launchpad.net/bugs/1826063/+attachment/5258364/+files/apt-cache-show-libneon27.txt

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

Title:
  Broken package 0.30.2-3~ubuntu18.04.1

Status in neon27 package in Ubuntu:
  New

Bug description:
  I think there might be a problem with this new neon27 package
  published for bionic:
  https://launchpad.net/ubuntu/+source/neon27/0.30.2-3~ubuntu18.04.1.

  The package now defines a dependency for libssl1.1 (>= 1.1.1) but not
  such version is available on Ubuntu 18.04:
  https://packages.ubuntu.com/bionic/libssl1.1.

  Therefore, the package can not be installed and leads to a broken
  package situation

  
  === apt install libneon27 ===

  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  Some packages could not be installed. This may mean that you have
  requested an impossible situation or if you are using the unstable
  distribution that some required packages have not yet been created
  or been moved out of Incoming.
  The following information may help to resolve the situation:
  The following packages have unmet dependencies:
   libneon27 : Depends: libssl1.1 (>= 1.1.1) but 1.1.0g-2ubuntu4.3 is to be 
installed
  E: Unable to correct problems, you have held broken packages.

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

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


[Desktop-packages] [Bug 1818204] Re: Qualcomm Atheros QCA9377 wireless does not work

2019-04-23 Thread Launchpad Bug Tracker
This bug was fixed in the package linux - 4.18.0-18.19

---
linux (4.18.0-18.19) cosmic; urgency=medium

  * linux: 4.18.0-18.19 -proposed tracker (LP: #1822796)

  * Packaging resync (LP: #1786013)
- [Packaging] update helper scripts
- [Packaging] resync retpoline extraction

  * 3b080b2564287be91605bfd1d5ee985696e61d3c in ubuntu_btrfs_kernel_fixes
triggers system hang on i386 (LP: #1812845)
- btrfs: raid56: properly unmap parity page in finish_parity_scrub()

  * [SRU][B/C/OEM]IOMMU: add kernel dma protection (LP: #1820153)
- ACPI / property: Allow multiple property compatible _DSD entries
- PCI / ACPI: Identify untrusted PCI devices
- iommu/vt-d: Force IOMMU on for platform opt in hint
- iommu/vt-d: Do not enable ATS for untrusted devices
- thunderbolt: Export IOMMU based DMA protection support to userspace
- iommu/vt-d: Disable ATS support on untrusted devices

  * Huawei Hi1822 NIC has poor performance (LP: #1820187)
- net-next: hinic: fix a problem in free_tx_poll()
- hinic: remove ndo_poll_controller
- net-next/hinic: add checksum offload and TSO support
- hinic: Fix l4_type parameter in hinic_task_set_tunnel_l4
- net-next/hinic:replace multiply and division operators
- net-next/hinic:add rx checksum offload for HiNIC
- net-next/hinic:fix a bug in set mac address
- net-next/hinic: fix a bug in rx data flow
- net: hinic: fix null pointer dereference on pointer hwdev
- hinic: optmize rx refill buffer mechanism
- net-next/hinic:add shutdown callback
- net-next/hinic: replace disable_irq_nosync/enable_irq

  * [CONFIG] please enable highdpi font FONT_TER16x32 (LP: #1819881)
- Fonts: New Terminus large console font
- [Config]: enable highdpi Terminus 16x32 font support

  * [19.04 FEAT] qeth: Enhanced link speed - kernel part (LP: #1814892)
- s390/qeth: report 25Gbit link speed

  * Avoid potential memory corruption on HiSilicon SoCs (LP: #1819546)
- iommu/arm-smmu-v3: Avoid memory corruption from Hisilicon MSI payloads

  * CVE-2017-5715
- x86/speculation: Apply IBPB more strictly to avoid cross-process data leak
- x86/speculation: Propagate information about RSB filling mitigation to 
sysfs
- x86/speculation: Add RETPOLINE_AMD support to the inline asm CALL_NOSPEC
  variant
- x86/retpoline: Make CONFIG_RETPOLINE depend on compiler support
- x86/retpoline: Remove minimal retpoline support
- x86/speculation: Update the TIF_SSBD comment
- x86/speculation: Clean up spectre_v2_parse_cmdline()
- x86/speculation: Remove unnecessary ret variable in cpu_show_common()
- x86/speculation: Move STIPB/IBPB string conditionals out of
  cpu_show_common()
- x86/speculation: Disable STIBP when enhanced IBRS is in use
- x86/speculation: Rename SSBD update functions
- x86/speculation: Reorganize speculation control MSRs update
- sched/smt: Make sched_smt_present track topology
- x86/Kconfig: Select SCHED_SMT if SMP enabled
- sched/smt: Expose sched_smt_present static key
- x86/speculation: Rework SMT state change
- x86/l1tf: Show actual SMT state
- x86/speculation: Reorder the spec_v2 code
- x86/speculation: Mark string arrays const correctly
- x86/speculataion: Mark command line parser data __initdata
- x86/speculation: Unify conditional spectre v2 print functions
- x86/speculation: Add command line control for indirect branch speculation
- x86/speculation: Prepare for per task indirect branch speculation control
- x86/process: Consolidate and simplify switch_to_xtra() code
- x86/speculation: Avoid __switch_to_xtra() calls
- x86/speculation: Prepare for conditional IBPB in switch_mm()
- ptrace: Remove unused ptrace_may_access_sched() and MODE_IBRS
- x86/speculation: Split out TIF update
- x86/speculation: Prevent stale SPEC_CTRL msr content
- x86/speculation: Prepare arch_smt_update() for PRCTL mode
- x86/speculation: Add prctl() control for indirect branch speculation
- x86/speculation: Enable prctl mode for spectre_v2_user
- x86/speculation: Add seccomp Spectre v2 user space protection mode
- x86/speculation: Provide IBPB always command line options
- kvm: svm: Ensure an IBPB on all affected CPUs when freeing a vmcb
- x86/speculation: Change misspelled STIPB to STIBP
- x86/speculation: Add support for STIBP always-on preferred mode
- x86, modpost: Replace last remnants of RETPOLINE with CONFIG_RETPOLINE

  * [Ubuntu] vfio-ap: add subsystem to matrix device to avoid libudev failures
(LP: #1818854)
- s390: vfio_ap: link the vfio_ap devices to the vfio_ap bus subsystem

  * Kernel regularly logs: Bluetooth: hci0: last event is not cmd complete
(0x0f) (LP: #1748565)
- Bluetooth: Fix unnecessary error message for HCI request completion

  * HiSilicon HNS ethernet broken in 4.15.0-45 (LP: #1818294)
- net: hns: Fix WARNING when hns 

Re: [Desktop-packages] [Bug 1826052] Re: LibreOffice on Ubuntu 19.04 screws up text paragraph styling

2019-04-23 Thread Eamon
** Attachment added: "FLARE 11 layout N NO PICS.odt"
   
https://bugs.launchpad.net/bugs/1826052/+attachment/5258359/+files/FLARE%2011%20layout%20N%20NO%20PICS.odt

** Attachment added: "FLARE 11 layout N NO PICS.pdf"
   
https://bugs.launchpad.net/bugs/1826052/+attachment/5258360/+files/FLARE%2011%20layout%20N%20NO%20PICS.pdf

** Attachment added: "Screenshot_2019-04-23_22-11-41.png"
   
https://bugs.launchpad.net/bugs/1826052/+attachment/5258361/+files/Screenshot_2019-04-23_22-11-41.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/1826052

Title:
  LibreOffice on Ubuntu 19.04 screws up text paragraph styling

Status in libreoffice package in Ubuntu:
  Incomplete

Bug description:

  After updating Ubuntu to 19.04 documents previously created in
  LibreOffice had some of their paragraph styling wiped, e.g. a custom
  heading style was arbitrarily removed in some but not all instances in
  a document and was replaced with 'Default Style'.

  LibreOffice Version: 6.2.2.2
  Build ID: 1:6.2.2-0ubuntu2
  CPU threads: 4; OS: Linux 5.0; UI render: default; VCL: gtk3; 
  Locale: en-GB (en_GB.UTF-8); UI-Language: en-GB
  Calc: threaded

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

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


[Desktop-packages] [Bug 1825071] Re: Super + p does not work as expected, it's defective

2019-04-23 Thread Sebastien Bacher
** Package changed: linux (Ubuntu) => gnome-shell (Ubuntu)

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

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

Title:
  Super + p does not work as expected, it's defective

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  I have 3 monitors (2 landscape and 1 portrait), I normally need to
  change between my monitors due to my setup. If I want to play a game,
  I typically switch to a single monitor (Built-in) then I can switch
  back to Join and everything goes back to normal. That is what I would
  expect but that is NOT what happens.

  When using super+p there are 4 options:

  - Mirror
  - Join
  - External
  - Built-in

  The first two options work correctly, but the 3rd and 4th options do
  not.

  
  External and Built-in do the exact same thing: they simply shift my monitors 
around, lose all settings (reset everything). So all 3 monitors are still in 
use but settings are cleared (orientation, resolution, and frequency are 
reset). I have to then open up the settings to change it all back. When I go 
back to Join, I would expect the settings to return to normal. They do not. 
Super + P simply wipes out monitor settings in my case.

  
  I am using:
  - Ubuntu 4.15.0-47.50-generic 4.15.18
  - GeForce GTX 1080/PCIe/SSE2
  - I have attached: lspci-vnvn.log

  Description:  Ubuntu 18.04.2 LTS
  Release:  18.04

  
  With nvidia-driver-418 from: ppa:graphics-drivers/ppa

  $ apt-cache policy nvidia-driver-418
  nvidia-driver-418:
Installed: 418.56-0ubuntu0~gpu18.04.1
Candidate: 418.56-0ubuntu0~gpu18.04.1
Version table:
   *** 418.56-0ubuntu0~gpu18.04.1 500
  500 http://ppa.launchpad.net/graphics-drivers/ppa/ubuntu bionic/main 
amd64 Packages
  100 /var/lib/dpkg/status


  I am not sure if this is actually necessary because I don't think this
  has to do with the graphics card.

  I am not sure what other information you will need for this report. I can 
provide more data upon request.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  jpsimkins   3108 F pulseaudio
   /dev/snd/controlC1:  jpsimkins   3108 F pulseaudio
   /dev/snd/controlC0:  jpsimkins   3108 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2018-06-22 (298 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  MachineType: Gigabyte Technology Co., Ltd. Z97X-UD5H
  NonfreeKernelModules: nvidia_modeset nvidia wl
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-47-generic 
root=UUID=cc5d2207-1cfa-40c1-8401-26624ac706a4 ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-47.50-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-47-generic N/A
   linux-backports-modules-4.15.0-47-generic  N/A
   linux-firmware 1.173.3
  Tags:  bionic
  Uname: Linux 4.15.0-47-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 08/03/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F10
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: Z97X-UD5H
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF10:bd08/03/2015:svnGigabyteTechnologyCo.,Ltd.:pnZ97X-UD5H:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnZ97X-UD5H:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: Z97X-UD5H
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

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

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


[Desktop-packages] [Bug 1825624] Re: Gnome 3.32 launcher not accepting icons

2019-04-23 Thread Marais-hannes
apport information

** Tags added: apport-collected third-party-packages

** Description changed:

  I am currently running Ubuntu 19.04 with vanilla Gnome shell 3.32
  installed.
  
  I find that the launcher in Gnome does not always accept the icon of a
  program. I have had difficulties with it accepting Firefox, Files and
  the Terminal icons.
  
  I "work around" seems to be to include the icon at the second last spot
  from the bottom.
  
- I have had this issue on two separate computers using the same
- configuration ie, Ubuntu 19.04 with vanilla Gnome shell 3.32.
+ I have had this issue on two separate computers using the same configuration 
ie, Ubuntu 19.04 with vanilla Gnome shell 3.32.
+ --- 
+ ProblemType: Bug
+ ApportVersion: 2.20.10-0ubuntu27
+ Architecture: amd64
+ CurrentDesktop: GNOME
+ DisplayManager: gdm3
+ DistroRelease: Ubuntu 19.04
+ GsettingsChanges:
+  b'org.gnome.shell' b'favorite-apps' redacted by apport
+  b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
+ InstallationDate: Installed on 2019-04-18 (5 days ago)
+ InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
+ Package: gnome-shell-extension-ubuntu-dock
+ PackageArchitecture: amd64
+ ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6
+ Tags: third-party-packages disco
+ Uname: Linux 5.0.0-13-generic x86_64
+ UpgradeStatus: No upgrade log present (probably fresh install)
+ UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
+ _MarkForUpload: True

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

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

Title:
  Gnome 3.32 launcher not accepting icons

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

Bug description:
  I am currently running Ubuntu 19.04 with vanilla Gnome shell 3.32
  installed.

  I find that the launcher in Gnome does not always accept the icon of a
  program. I have had difficulties with it accepting Firefox, Files and
  the Terminal icons.

  I "work around" seems to be to include the icon at the second last
  spot from the bottom.

  I have had this issue on two separate computers using the same configuration 
ie, Ubuntu 19.04 with vanilla Gnome shell 3.32.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  CurrentDesktop: GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 19.04
  GsettingsChanges:
   b'org.gnome.shell' b'favorite-apps' redacted by apport
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
  InstallationDate: Installed on 2019-04-18 (5 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  Package: gnome-shell-extension-ubuntu-dock
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6
  Tags: third-party-packages disco
  Uname: Linux 5.0.0-13-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True

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

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


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

2019-04-23 Thread Marais-hannes
apport information

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

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

Title:
  Gnome 3.32 launcher not accepting icons

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

Bug description:
  I am currently running Ubuntu 19.04 with vanilla Gnome shell 3.32
  installed.

  I find that the launcher in Gnome does not always accept the icon of a
  program. I have had difficulties with it accepting Firefox, Files and
  the Terminal icons.

  I "work around" seems to be to include the icon at the second last
  spot from the bottom.

  I have had this issue on two separate computers using the same configuration 
ie, Ubuntu 19.04 with vanilla Gnome shell 3.32.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  CurrentDesktop: GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 19.04
  GsettingsChanges:
   b'org.gnome.shell' b'favorite-apps' redacted by apport
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
  InstallationDate: Installed on 2019-04-18 (5 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  Package: gnome-shell-extension-ubuntu-dock
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6
  Tags: third-party-packages disco
  Uname: Linux 5.0.0-13-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True

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

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


[Desktop-packages] [Bug 1823650] Re: v4l-utils ftbfs in cosmic

2019-04-23 Thread Sebastien Bacher
** Changed in: v4l-utils (Ubuntu)
   Importance: High => Low

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

Title:
  v4l-utils ftbfs in cosmic

Status in v4l-utils package in Ubuntu:
  New

Bug description:
  https://launchpadlibrarian.net/418304769/buildlog_ubuntu-cosmic-amd64
  .v4l-utils_1.14.2-1_BUILDING.txt.gz

  g++  -I. -I../..  -I../../utils/common -I../../lib/include -Wall 
-Wpointer-arith -D_GNU_SOURCE -I../../include -Wdate-time -D_FORTIFY_SOURCE=2  
-g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -c -o v4l2_compliance-v4l2-compliance.o `test -f 
'v4l2-compliance.cpp' || echo './'`v4l2-compliance.cpp
  In file included from v4l2-compliance.h:42,
   from v4l2-compliance.cpp:38:
  ../../utils/common/cv4l-helpers.h: In member function ‘void 
cv4l_buffer::init(const cv4l_buffer&)’:
  ../../utils/common/cv4l-helpers.h:843:29: warning: ‘void* memcpy(void*, const 
void*, size_t)’ writing to an object of type ‘class cv4l_buffer’ with no 
trivial copy-assignment; use copy-assignment or copy-initialization instead 
[-Wclass-memaccess]
 memcpy(this, , sizeof(b));
   ^
  ../../utils/common/cv4l-helpers.h:817:7: note: ‘class cv4l_buffer’ declared 
here
   class cv4l_buffer : public v4l_buffer {
 ^~~
  g++  -I. -I../..  -I../../utils/common -I../../lib/include -Wall 
-Wpointer-arith -D_GNU_SOURCE -I../../include -Wdate-time -D_FORTIFY_SOURCE=2  
-g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -c -o v4l2_compliance-v4l2-test-debug.o `test -f 
'v4l2-test-debug.cpp' || echo './'`v4l2-test-debug.cpp
  In file included from v4l2-compliance.h:42,
   from v4l2-test-debug.cpp:35:
  ../../utils/common/cv4l-helpers.h: In member function ‘void 
cv4l_buffer::init(const cv4l_buffer&)’:
  ../../utils/common/cv4l-helpers.h:843:29: warning: ‘void* memcpy(void*, const 
void*, size_t)’ writing to an object of type ‘class cv4l_buffer’ with no 
trivial copy-assignment; use copy-assignment or copy-initialization instead 
[-Wclass-memaccess]
 memcpy(this, , sizeof(b));
   ^
  ../../utils/common/cv4l-helpers.h:817:7: note: ‘class cv4l_buffer’ declared 
here
   class cv4l_buffer : public v4l_buffer {
 ^~~
  g++  -I. -I../..  -I../../utils/common -I../../lib/include -Wall 
-Wpointer-arith -D_GNU_SOURCE -I../../include -Wdate-time -D_FORTIFY_SOURCE=2  
-g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -c -o v4l2_compliance-v4l2-test-input-output.o `test -f 
'v4l2-test-input-output.cpp' || echo './'`v4l2-test-input-output.cpp
  In file included from v4l2-compliance.h:42,
   from v4l2-test-input-output.cpp:32:
  ../../utils/common/cv4l-helpers.h: In member function ‘void 
cv4l_buffer::init(const cv4l_buffer&)’:
  ../../utils/common/cv4l-helpers.h:843:29: warning: ‘void* memcpy(void*, const 
void*, size_t)’ writing to an object of type ‘class cv4l_buffer’ with no 
trivial copy-assignment; use copy-assignment or copy-initialization instead 
[-Wclass-memaccess]
 memcpy(this, , sizeof(b));
   ^
  ../../utils/common/cv4l-helpers.h:817:7: note: ‘class cv4l_buffer’ declared 
here
   class cv4l_buffer : public v4l_buffer {
 ^~~
  g++  -I. -I../..  -I../../utils/common -I../../lib/include -Wall 
-Wpointer-arith -D_GNU_SOURCE -I../../include -Wdate-time -D_FORTIFY_SOURCE=2  
-g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -c -o v4l2_compliance-v4l2-test-controls.o `test -f 
'v4l2-test-controls.cpp' || echo './'`v4l2-test-controls.cpp
  In file included from v4l2-compliance.h:42,
   from v4l2-test-controls.cpp:33:
  ../../utils/common/cv4l-helpers.h: In member function ‘void 
cv4l_buffer::init(const cv4l_buffer&)’:
  ../../utils/common/cv4l-helpers.h:843:29: warning: ‘void* memcpy(void*, const 
void*, size_t)’ writing to an object of type ‘class cv4l_buffer’ with no 
trivial copy-assignment; use copy-assignment or copy-initialization instead 
[-Wclass-memaccess]
 memcpy(this, , sizeof(b));
   ^
  ../../utils/common/cv4l-helpers.h:817:7: note: ‘class cv4l_buffer’ declared 
here
   class cv4l_buffer : public v4l_buffer {
 ^~~
  g++  -I. -I../..  -I../../utils/common -I../../lib/include -Wall 
-Wpointer-arith -D_GNU_SOURCE -I../../include -Wdate-time -D_FORTIFY_SOURCE=2  
-g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -c -o v4l2_compliance-v4l2-test-io-config.o `test -f 
'v4l2-test-io-config.cpp' || echo './'`v4l2-test-io-config.cpp
  In file included from v4l2-compliance.h:42,
   from v4l2-test-io-config.cpp:32:
  ../../utils/common/cv4l-helpers.h: 

[Desktop-packages] [Bug 1826057] [NEW] Automatically signed out of Ubuntu One on terminating session

2019-04-23 Thread Mike L
Public bug reported:

If the user reboots or shuts down (uncertain about logging off and back
on), they will be signed out from Ubuntu One. Previously, Ubuntu
Software on 18.10 and earlier, the user would be signed out of Ubuntu
One after closing the Software Store, but now it takes a reboot or
something similar and the user is signed out of Ubuntu One. At least the
bug is now less annoying. Running Ubuntu 19.04 amd64 with gnome-software
3.30.6-2ubuntu3.

ProblemType: Bug
DistroRelease: Ubuntu 19.04
Package: gnome-software 3.30.6-2ubuntu3
ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6
Uname: Linux 5.0.0-13-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.10-0ubuntu27
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Tue Apr 23 16:38:51 2019
InstallationDate: Installed on 2018-11-11 (162 days ago)
InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3)
InstalledPlugins:
 gnome-software-plugin-flatpak 3.30.6-2ubuntu3
 gnome-software-plugin-snap3.30.6-2ubuntu3
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 disco on 2019-04-17 (6 days ago)

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


** Tags: amd64 apport-bug disco

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

Title:
  Automatically signed out of Ubuntu One on terminating session

Status in gnome-software package in Ubuntu:
  New

Bug description:
  If the user reboots or shuts down (uncertain about logging off and
  back on), they will be signed out from Ubuntu One. Previously, Ubuntu
  Software on 18.10 and earlier, the user would be signed out of Ubuntu
  One after closing the Software Store, but now it takes a reboot or
  something similar and the user is signed out of Ubuntu One. At least
  the bug is now less annoying. Running Ubuntu 19.04 amd64 with gnome-
  software 3.30.6-2ubuntu3.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: gnome-software 3.30.6-2ubuntu3
  ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6
  Uname: Linux 5.0.0-13-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Apr 23 16:38:51 2019
  InstallationDate: Installed on 2018-11-11 (162 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  InstalledPlugins:
   gnome-software-plugin-flatpak 3.30.6-2ubuntu3
   gnome-software-plugin-snap3.30.6-2ubuntu3
  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 disco on 2019-04-17 (6 days ago)

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

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


[Desktop-packages] [Bug 1825624] Re: Gnome 3.32 launcher not accepting icons

2019-04-23 Thread Marais-hannes
I attach a screen shot. You will see that there are only two icons in
the Dash to Dock Gnome extension. For the sake of clarity, I am not
using the Ubuntu Dock extension.

I have tried to include other icons such as Files and software but it
seems that it is the luck of the draw that decides which icons to
display.

** Attachment added: "Screenshot from 2019-04-23 22-33-36.png"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1825624/+attachment/5258356/+files/Screenshot%20from%202019-04-23%2022-33-36.png

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

Title:
  Gnome 3.32 launcher not accepting icons

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

Bug description:
  I am currently running Ubuntu 19.04 with vanilla Gnome shell 3.32
  installed.

  I find that the launcher in Gnome does not always accept the icon of a
  program. I have had difficulties with it accepting Firefox, Files and
  the Terminal icons.

  I "work around" seems to be to include the icon at the second last
  spot from the bottom.

  I have had this issue on two separate computers using the same configuration 
ie, Ubuntu 19.04 with vanilla Gnome shell 3.32.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  CurrentDesktop: GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 19.04
  GsettingsChanges:
   b'org.gnome.shell' b'favorite-apps' redacted by apport
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
  InstallationDate: Installed on 2019-04-18 (5 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  Package: gnome-shell-extension-ubuntu-dock
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6
  Tags: third-party-packages disco
  Uname: Linux 5.0.0-13-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True

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

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


[Desktop-packages] [Bug 1825708] Re: Please Include Package Names

2019-04-23 Thread Sebastien Bacher
** Changed in: gnome-software (Ubuntu)
   Importance: Undecided => Wishlist

** Changed in: gnome-software (Ubuntu)
   Status: Confirmed => Triaged

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

Title:
  Please Include Package Names

Status in GNOME Software:
  New
Status in gnome-software package in Ubuntu:
  Triaged

Bug description:
  Gnome-Software does not include a software package's name in the
  details section of each software it catalogs and I want this to be
  added for the following reasons.

  1) When submitting bug reports and feature requests, it is necessary
  to know the package name. When I use gnome-software to install a piece
  of software, I expect to be able to go back to gnome-software to
  discover software's package name. Since it doesn't include this
  pertinent detail, I'm having to use a number of command to discover
  it.

  2) Although I use gnome-software to discover available software, I
  always like to collect that software's package name, so I can add to
  my "sudo apt install" list, so that when I set up my computer from
  scratch, I can use one command to reinstall all the software packages
  I've installed previously.

  These are my two reason, but I'm sure others have more. The bottom
  line is, the package name is a very pertinent piece of information
  that gnome-software should include in the details section of each
  software it catalogs. Look at what is in the details section right
  now. Hardly any of those details are anything I'll ever be interested
  in, but the package name is VERY pertinent to me.

  Please add this.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: gnome-software 3.30.6-2ubuntu3
  ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6
  Uname: Linux 5.0.0-13-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Apr 21 05:03:55 2019
  InstallationDate: Installed on 2019-01-07 (103 days ago)
  InstallationMedia: Ubuntu 16.04.5 LTS "Xenial Xerus" - Release amd64 
(20180731)
  InstalledPlugins:
   gnome-software-plugin-flatpak N/A
   gnome-software-plugin-snap3.30.6-2ubuntu3
  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 disco on 2019-04-21 (0 days ago)

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

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


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

2019-04-23 Thread Marais-hannes
apport information

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

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

Title:
  Gnome 3.32 launcher not accepting icons

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

Bug description:
  I am currently running Ubuntu 19.04 with vanilla Gnome shell 3.32
  installed.

  I find that the launcher in Gnome does not always accept the icon of a
  program. I have had difficulties with it accepting Firefox, Files and
  the Terminal icons.

  I "work around" seems to be to include the icon at the second last
  spot from the bottom.

  I have had this issue on two separate computers using the same configuration 
ie, Ubuntu 19.04 with vanilla Gnome shell 3.32.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  CurrentDesktop: GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 19.04
  GsettingsChanges:
   b'org.gnome.shell' b'favorite-apps' redacted by apport
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
  InstallationDate: Installed on 2019-04-18 (5 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  Package: gnome-shell-extension-ubuntu-dock
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6
  Tags: third-party-packages disco
  Uname: Linux 5.0.0-13-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True

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

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


[Desktop-packages] [Bug 1825547] Re: old bug "nm-applet stop showing vpn status" is back

2019-04-23 Thread Sebastien Bacher
Could you take a screenshot showing the issue?

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

Title:
  old bug "nm-applet stop showing vpn status" is back

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  old bug  #1756720 "nm-applet stop showing vpn status" is back after upgrade 
to Ubuntu 19.04
  ---

  1. The specific steps or actions you took that caused you to encounter
  the problem.

Connect to any VPN. Connection is open.

  
  2. The behavior you expected.

VPN connection should be displayed as connected in
  "Settings->Network->VPN" as well as in nm-applet (upper right corner
  of display)

  
  3. The behavior you actually encountered (in as much detail as possible).

In "Settings->Network->VPN" it is shown as open but in nm-applet
  as closed.

  ---
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 19.04
  InstallationDate: Installed on 2018-04-27 (361 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: gnome-shell 3.32.0+git20190410-1ubuntu1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6
  Tags: disco third-party-packages
  Uname: Linux 5.0.0-13-generic x86_64
  UpgradeStatus: Upgraded to disco on 2019-04-19 (4 days ago)
  UserGroups: adm cdrom dialout dip docker libvirt lpadmin plugdev sambashare 
sudo vboxusers
  _MarkForUpload: True

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

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


[Desktop-packages] [Bug 1825963] Re: Abysmal memory leak on tracker-extract

2019-04-23 Thread Sebastien Bacher
** Changed in: tracker (Ubuntu)
   Status: Incomplete => New

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

Title:
  Abysmal memory leak on tracker-extract

Status in tracker package in Ubuntu:
  New

Bug description:
  After upgrading from 18.10 to 19.04 my Ubuntu desktop started lagging
  madly. It became very difficult to use and I discovered the problem to
  be tracker-extract running and very rapidly leaking memory up to 100%
  and breaching into swap memory. I tried killing it several times but
  Tracker appears to relaunch it every time, so I deleted it from
  /usr/lib/tracker entirely.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: tracker 2.1.8-2
  ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6
  Uname: Linux 5.0.0-13-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Apr 23 13:02:25 2019
  InstallationDate: Installed on 2019-03-11 (42 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  SourcePackage: tracker
  UpgradeStatus: Upgraded to disco on 2019-04-23 (0 days ago)

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

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


[Desktop-packages] [Bug 1826025] Re: gnome-shell trap int3 no desktop

2019-04-23 Thread Sebastien Bacher
** Package changed: xorg (Ubuntu) => gnome-shell (Ubuntu)

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

Title:
  gnome-shell trap int3 no desktop

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  After upgrade to 19.04, gnome-shell crashes on boot, leaving blinking
  cursor.

  [  498.989821] traps: gnome-shell[4066] trap int3 ip:7f7b604e6955
  sp:7fff92106950 error:0 in libglib-2.0.so.0.6000.0[7f7b604ad000+8]

  Restarting gdm3 service results in the same trap.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: xorg 1:7.7+19ubuntu12
  ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17
  Uname: Linux 4.18.0-13-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..02.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:02:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  390.116  Sun Jan 27 07:21:36 
PST 2019
   GCC version:  gcc version 8.3.0 (Ubuntu 8.3.0-6ubuntu1)
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  CompizPlugins: 
[core,bailer,detection,composite,opengl,compiztoolbox,decor,regex,gnomecompat,animation,vpswitch,grid,resize,imgpng,place,session,move,snap,unitymtgrabhandles,mousepoll,workarounds,expo,wall,ezoom,fade,scale,unityshell]
  Date: Tue Apr 23 09:56:22 2019
  DistUpgraded: 2019-04-22 15:16:02,086 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process 
“./xorg_fix_proprietary.py” (No such file or directory) (8))
  DistroCodename: disco
  DistroVariant: ubuntu
  DkmsStatus:
   nvidia, 390.116, 4.18.0-13-generic, x86_64: installed
   nvidia, 390.116, 5.0.0-13-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Matrox Electronics Systems Ltd. MGA G200eW WPCM450 [102b:0532] (rev 0a) 
(prog-if 00 [VGA controller])
 Subsystem: Super Micro Computer Inc MGA G200eW WPCM450 [15d9:0001]
   NVIDIA Corporation GP104 [GeForce GTX 1070] [10de:1b81] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: Gigabyte Technology Co., Ltd GP104 [GeForce GTX 1070] 
[1458:3703]
  InstallationDate: Installed on 2012-02-14 (2625 days ago)
  InstallationMedia: Ubuntu-Server 11.10 "Oneiric Ocelot" - Release amd64 
(20111011)
  MachineType: Supermicro X8DT3
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-13-generic 
root=/dev/mapper/mizuno-root ro nomdmonddf nomdmonisw nomdmonddf nomdmonisw 
nomdmonddf nomdmonisw nomdmonddf nomdmonisw
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to disco on 2019-04-22 (0 days ago)
  dmi.bios.date: 07/09/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2.2
  dmi.board.asset.tag: 1234567890
  dmi.board.name: X8DT3
  dmi.board.vendor: Supermicro
  dmi.board.version: 2.0
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 17
  dmi.chassis.vendor: Supermicro
  dmi.chassis.version: 1234567890
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2.2:bd07/09/2018:svnSupermicro:pnX8DT3:pvr1234567890:rvnSupermicro:rnX8DT3:rvr2.0:cvnSupermicro:ct17:cvr1234567890:
  dmi.product.family: 1234567890
  dmi.product.name: X8DT3
  dmi.product.sku: To Be Filled By O.E.M.
  dmi.product.version: 1234567890
  dmi.sys.vendor: Supermicro
  version.compiz: compiz 1:0.9.14.0+19.04.20190223.1-0ubuntu1
  version.libdrm2: libdrm2 2.4.97-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.2-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.2-1ubuntu1
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-0ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20180925-2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1
  xserver.bootTime: Mon Apr 22 20:53:09 2019
  xserver.configfile: /home/greg/xorg.conf.new
  xserver.devices:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   
  xserver.version: 2:1.20.4-1ubuntu3

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

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


[Desktop-packages] [Bug 1825071] [NEW] Super + p does not work as expected, it's defective

2019-04-23 Thread Launchpad Bug Tracker
You have been subscribed to a public bug:

I have 3 monitors (2 landscape and 1 portrait), I normally need to
change between my monitors due to my setup. If I want to play a game, I
typically switch to a single monitor (Built-in) then I can switch back
to Join and everything goes back to normal. That is what I would expect
but that is NOT what happens.

When using super+p there are 4 options:

- Mirror
- Join
- External
- Built-in

The first two options work correctly, but the 3rd and 4th options do
not.


External and Built-in do the exact same thing: they simply shift my monitors 
around, lose all settings (reset everything). So all 3 monitors are still in 
use but settings are cleared (orientation, resolution, and frequency are 
reset). I have to then open up the settings to change it all back. When I go 
back to Join, I would expect the settings to return to normal. They do not. 
Super + P simply wipes out monitor settings in my case.


I am using:
- Ubuntu 4.15.0-47.50-generic 4.15.18
- GeForce GTX 1080/PCIe/SSE2
- I have attached: lspci-vnvn.log

Description:Ubuntu 18.04.2 LTS
Release:18.04


With nvidia-driver-418 from: ppa:graphics-drivers/ppa

$ apt-cache policy nvidia-driver-418
nvidia-driver-418:
  Installed: 418.56-0ubuntu0~gpu18.04.1
  Candidate: 418.56-0ubuntu0~gpu18.04.1
  Version table:
 *** 418.56-0ubuntu0~gpu18.04.1 500
500 http://ppa.launchpad.net/graphics-drivers/ppa/ubuntu bionic/main 
amd64 Packages
100 /var/lib/dpkg/status


I am not sure if this is actually necessary because I don't think this
has to do with the graphics card.

I am not sure what other information you will need for this report. I can 
provide more data upon request.
--- 
ProblemType: Bug
ApportVersion: 2.20.9-0ubuntu7.6
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC2:  jpsimkins   3108 F pulseaudio
 /dev/snd/controlC1:  jpsimkins   3108 F pulseaudio
 /dev/snd/controlC0:  jpsimkins   3108 F pulseaudio
CurrentDesktop: ubuntu:GNOME
DistroRelease: Ubuntu 18.04
InstallationDate: Installed on 2018-06-22 (298 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
MachineType: Gigabyte Technology Co., Ltd. Z97X-UD5H
NonfreeKernelModules: nvidia_modeset nvidia wl
Package: linux (not installed)
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcFB: 0 EFI VGA
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-47-generic 
root=UUID=cc5d2207-1cfa-40c1-8401-26624ac706a4 ro quiet splash vt.handoff=1
ProcVersionSignature: Ubuntu 4.15.0-47.50-generic 4.15.18
RelatedPackageVersions:
 linux-restricted-modules-4.15.0-47-generic N/A
 linux-backports-modules-4.15.0-47-generic  N/A
 linux-firmware 1.173.3
Tags:  bionic
Uname: Linux 4.15.0-47-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo
_MarkForUpload: True
dmi.bios.date: 08/03/2015
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: F10
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: Z97X-UD5H
dmi.board.vendor: Gigabyte Technology Co., Ltd.
dmi.board.version: x.x
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF10:bd08/03/2015:svnGigabyteTechnologyCo.,Ltd.:pnZ97X-UD5H:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnZ97X-UD5H:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: Z97X-UD5H
dmi.product.version: To be filled by O.E.M.
dmi.sys.vendor: Gigabyte Technology Co., Ltd.

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


** Tags: apport-collected bionic
-- 
Super + p does not work as expected, it's defective
https://bugs.launchpad.net/bugs/1825071
You received this bug notification because you are a member of Desktop 
Packages, which is subscribed to gnome-shell 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 1825447] Re: 19.04 packaging is from master (or wrong commit) and not ubuntu branch (breaks scroll events)

2019-04-23 Thread Ed Bruck
** Summary changed:

- 19.04 packaging is from master and not ubuntu branch (breaks scroll events)
+ 19.04 packaging is from master (or wrong commit) and not ubuntu branch 
(breaks scroll events)

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

Title:
  19.04 packaging is from master (or wrong commit) and not ubuntu branch
  (breaks scroll events)

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

Bug description:
  It appears the code used in the 19.04 packaging of the appindicator is
  from master and not the tagged ubuntu-19.04 commit from the ubuntu
  branch. The master branch is not delivering scroll events, which stops
  my application (radiotray-ng) from being able to adjust its volume
  levels.

  I've swapped out the code under /usr/share/gnome-shell/extensions
  /ubuntu-appindicat...@ubuntu.com/ with the ubuntu branch and scrolling
  on an indicator icon works again.

  I've filed an issue on github as well.

  https://github.com/ubuntu/gnome-shell-extension-
  appindicator/issues/169

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

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


[Desktop-packages] [Bug 1804467] Re: gnome-shell: stray configure notify event

2019-04-23 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

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

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

Title:
  gnome-shell: stray configure notify event

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

Bug description:
  https://gitlab.gnome.org/GNOME/mutter/issues/400

  ---

  When unmapping X11 client, Gnome sends a stray configure notify event,
  where 'y' has been moved up by the height of the window decoration.
  Originally reported here: https://bugreports.qt.io/browse/QTBUG-71671

  From xtrace output I see that gnome re-parents the window to the root
  window and mistakenly adjusts 'y' coordinate. There are no plausible
  reasons why WM should change window's coordinates when unmapping.

  000:>:01c6: Event (generated) ConfigureNotify(22) event=0x02a5 
window=0x02a5 above-sibling=None(0x) x=600 y=526 width=200 
height=200 border-width=0 override-redirect=false(0x00)
  000:>:01c6: Event ReparentNotify(21) event=0x02a5 window=0x02a5 
parent=0x011b x=600 y=526 override-redirect=false(0x00)

  Where:

  root window id = 0x011b
  0x02a5 = window which coordinates before calling unmap are x=600, y=600

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.28.2-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.2
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Wed Nov 21 15:33:14 2018
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  GsettingsChanges:
   b'org.gnome.shell' b'enabled-extensions' b"['ubuntu-d...@ubuntu.com']"
   b'org.gnome.shell' b'favorite-apps' redacted by apport
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
  InstallationDate: Installed on 2018-08-16 (97 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1804467] Re: gnome-shell: stray configure notify event

2019-04-23 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

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

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

Title:
  gnome-shell: stray configure notify event

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

Bug description:
  https://gitlab.gnome.org/GNOME/mutter/issues/400

  ---

  When unmapping X11 client, Gnome sends a stray configure notify event,
  where 'y' has been moved up by the height of the window decoration.
  Originally reported here: https://bugreports.qt.io/browse/QTBUG-71671

  From xtrace output I see that gnome re-parents the window to the root
  window and mistakenly adjusts 'y' coordinate. There are no plausible
  reasons why WM should change window's coordinates when unmapping.

  000:>:01c6: Event (generated) ConfigureNotify(22) event=0x02a5 
window=0x02a5 above-sibling=None(0x) x=600 y=526 width=200 
height=200 border-width=0 override-redirect=false(0x00)
  000:>:01c6: Event ReparentNotify(21) event=0x02a5 window=0x02a5 
parent=0x011b x=600 y=526 override-redirect=false(0x00)

  Where:

  root window id = 0x011b
  0x02a5 = window which coordinates before calling unmap are x=600, y=600

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.28.2-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.2
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Wed Nov 21 15:33:14 2018
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  GsettingsChanges:
   b'org.gnome.shell' b'enabled-extensions' b"['ubuntu-d...@ubuntu.com']"
   b'org.gnome.shell' b'favorite-apps' redacted by apport
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
  InstallationDate: Installed on 2018-08-16 (97 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

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

-- 
Mailing list: https://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 1826052] Re: LibreOffice on Ubuntu 19.04 screws up text paragraph styling

2019-04-23 Thread Eamon
It's pretty gigantic document (big images) ans not ideal for sharing. I
will see if I can get the same outcome with a lighter document.

FYI the same ODT opens fine in LibreOffice version 6.132 on a Windows 10
netbook.


⁣Get BlueMail for Android ​

On 23 Apr 2019, 21:03, at 21:03, Olivier Tilloy  
wrote:
>Thanks for the report Eamon.
>Would you be able to share such a document, so that others can test,
>confirm and investigate the problem?
>
>** 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/1826052
>
>Title:
>  LibreOffice on Ubuntu 19.04 screws up text paragraph styling
>
>Status in libreoffice package in Ubuntu:
>  Incomplete
>
>Bug description:
>
>  After updating Ubuntu to 19.04 documents previously created in
>  LibreOffice had some of their paragraph styling wiped, e.g. a custom
> heading style was arbitrarily removed in some but not all instances in
>  a document and was replaced with 'Default Style'.
>
>  LibreOffice Version: 6.2.2.2
>  Build ID: 1:6.2.2-0ubuntu2
>  CPU threads: 4; OS: Linux 5.0; UI render: default; VCL: gtk3; 
>  Locale: en-GB (en_GB.UTF-8); UI-Language: en-GB
>  Calc: threaded
>
>To manage notifications about this bug go to:
>https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1826052/+subscriptions

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

Title:
  LibreOffice on Ubuntu 19.04 screws up text paragraph styling

Status in libreoffice package in Ubuntu:
  Incomplete

Bug description:

  After updating Ubuntu to 19.04 documents previously created in
  LibreOffice had some of their paragraph styling wiped, e.g. a custom
  heading style was arbitrarily removed in some but not all instances in
  a document and was replaced with 'Default Style'.

  LibreOffice Version: 6.2.2.2
  Build ID: 1:6.2.2-0ubuntu2
  CPU threads: 4; OS: Linux 5.0; UI render: default; VCL: gtk3; 
  Locale: en-GB (en_GB.UTF-8); UI-Language: en-GB
  Calc: threaded

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

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


[Desktop-packages] [Bug 1825547] Re: old bug "nm-applet stop showing vpn status" is back

2019-04-23 Thread Miroslav Zaťko
** Description changed:

  old bug  #1756720 "nm-applet stop showing vpn status" is back after upgrade 
to Ubuntu 19.04
- --- 
+ ---
+ 
+ 1. The specific steps or actions you took that caused you to encounter
+ the problem.
+ 
+   Connect to any VPN. Connection is open.
+ 
+ 
+ 2. The behavior you expected.
+ 
+   VPN connection should be displayed as connected in
+ "Settings->Network->VPN" as well as in nm-applet (upper right corner of
+ display)
+ 
+ 
+ 3. The behavior you actually encountered (in as much detail as possible).
+ 
+   In "Settings->Network->VPN" it is shown as open but in nm-applet
+ as closed.
+ 
+ ---
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 19.04
  InstallationDate: Installed on 2018-04-27 (361 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: gnome-shell 3.32.0+git20190410-1ubuntu1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6
  Tags: disco third-party-packages
  Uname: Linux 5.0.0-13-generic x86_64
  UpgradeStatus: Upgraded to disco on 2019-04-19 (4 days ago)
  UserGroups: adm cdrom dialout dip docker 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-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1825547

Title:
  old bug "nm-applet stop showing vpn status" is back

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  old bug  #1756720 "nm-applet stop showing vpn status" is back after upgrade 
to Ubuntu 19.04
  ---

  1. The specific steps or actions you took that caused you to encounter
  the problem.

Connect to any VPN. Connection is open.

  
  2. The behavior you expected.

VPN connection should be displayed as connected in
  "Settings->Network->VPN" as well as in nm-applet (upper right corner
  of display)

  
  3. The behavior you actually encountered (in as much detail as possible).

In "Settings->Network->VPN" it is shown as open but in nm-applet
  as closed.

  ---
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 19.04
  InstallationDate: Installed on 2018-04-27 (361 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: gnome-shell 3.32.0+git20190410-1ubuntu1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6
  Tags: disco third-party-packages
  Uname: Linux 5.0.0-13-generic x86_64
  UpgradeStatus: Upgraded to disco on 2019-04-19 (4 days ago)
  UserGroups: adm cdrom dialout dip docker libvirt lpadmin plugdev sambashare 
sudo vboxusers
  _MarkForUpload: True

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

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


[Desktop-packages] [Bug 1826056] [NEW] Desktop context: Keep aligned, Organize desktop by name missing in 19.04

2019-04-23 Thread JOSEPH E CONNER
Public bug reported:

After upgrading from 18.10 to 19.04 the desktop context menu no longer
contains the choices:

Keep aligned
Organize desktop by name

These were very useful to me. I would like them to be restored.

Ubuntu 19.04, 64bit
Gnome 3.32.1

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

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

Title:
  Desktop context: Keep aligned, Organize desktop by name missing in
  19.04

Status in tracker package in Ubuntu:
  New

Bug description:
  After upgrading from 18.10 to 19.04 the desktop context menu no longer
  contains the choices:

  Keep aligned
  Organize desktop by name

  These were very useful to me. I would like them to be restored.

  Ubuntu 19.04, 64bit
  Gnome 3.32.1

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

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


[Desktop-packages] [Bug 1825547] GsettingsChanges.txt

2019-04-23 Thread Miroslav Zaťko
apport information

** Attachment added: "GsettingsChanges.txt"
   
https://bugs.launchpad.net/bugs/1825547/+attachment/5258350/+files/GsettingsChanges.txt

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

Title:
  old bug "nm-applet stop showing vpn status" is back

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  old bug  #1756720 "nm-applet stop showing vpn status" is back after upgrade 
to Ubuntu 19.04
  ---

  1. The specific steps or actions you took that caused you to encounter
  the problem.

Connect to any VPN. Connection is open.

  
  2. The behavior you expected.

VPN connection should be displayed as connected in
  "Settings->Network->VPN" as well as in nm-applet (upper right corner
  of display)

  
  3. The behavior you actually encountered (in as much detail as possible).

In "Settings->Network->VPN" it is shown as open but in nm-applet
  as closed.

  ---
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 19.04
  InstallationDate: Installed on 2018-04-27 (361 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: gnome-shell 3.32.0+git20190410-1ubuntu1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6
  Tags: disco third-party-packages
  Uname: Linux 5.0.0-13-generic x86_64
  UpgradeStatus: Upgraded to disco on 2019-04-19 (4 days ago)
  UserGroups: adm cdrom dialout dip docker libvirt lpadmin plugdev sambashare 
sudo vboxusers
  _MarkForUpload: True

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

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


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

2019-04-23 Thread Miroslav Zaťko
apport information

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

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

Title:
  old bug "nm-applet stop showing vpn status" is back

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  old bug  #1756720 "nm-applet stop showing vpn status" is back after upgrade 
to Ubuntu 19.04
  ---

  1. The specific steps or actions you took that caused you to encounter
  the problem.

Connect to any VPN. Connection is open.

  
  2. The behavior you expected.

VPN connection should be displayed as connected in
  "Settings->Network->VPN" as well as in nm-applet (upper right corner
  of display)

  
  3. The behavior you actually encountered (in as much detail as possible).

In "Settings->Network->VPN" it is shown as open but in nm-applet
  as closed.

  ---
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 19.04
  InstallationDate: Installed on 2018-04-27 (361 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: gnome-shell 3.32.0+git20190410-1ubuntu1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6
  Tags: disco third-party-packages
  Uname: Linux 5.0.0-13-generic x86_64
  UpgradeStatus: Upgraded to disco on 2019-04-19 (4 days ago)
  UserGroups: adm cdrom dialout dip docker libvirt lpadmin plugdev sambashare 
sudo vboxusers
  _MarkForUpload: True

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

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


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

2019-04-23 Thread Miroslav Zaťko
apport information

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

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

Title:
  old bug "nm-applet stop showing vpn status" is back

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  old bug  #1756720 "nm-applet stop showing vpn status" is back after upgrade 
to Ubuntu 19.04
  ---

  1. The specific steps or actions you took that caused you to encounter
  the problem.

Connect to any VPN. Connection is open.

  
  2. The behavior you expected.

VPN connection should be displayed as connected in
  "Settings->Network->VPN" as well as in nm-applet (upper right corner
  of display)

  
  3. The behavior you actually encountered (in as much detail as possible).

In "Settings->Network->VPN" it is shown as open but in nm-applet
  as closed.

  ---
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 19.04
  InstallationDate: Installed on 2018-04-27 (361 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: gnome-shell 3.32.0+git20190410-1ubuntu1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6
  Tags: disco third-party-packages
  Uname: Linux 5.0.0-13-generic x86_64
  UpgradeStatus: Upgraded to disco on 2019-04-19 (4 days ago)
  UserGroups: adm cdrom dialout dip docker libvirt lpadmin plugdev sambashare 
sudo vboxusers
  _MarkForUpload: True

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

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


[Desktop-packages] [Bug 1825547] Re: old bug "nm-applet stop showing vpn status" is back

2019-04-23 Thread Miroslav Zaťko
apport information

** Tags added: apport-collected third-party-packages

** Description changed:

- old bug  #1756720 "nm-applet stop showing vpn status" is back after
- upgrade to Ubuntu 19.04
+ old bug  #1756720 "nm-applet stop showing vpn status" is back after upgrade 
to Ubuntu 19.04
+ --- 
+ ProblemType: Bug
+ ApportVersion: 2.20.10-0ubuntu27
+ Architecture: amd64
+ CurrentDesktop: ubuntu:GNOME
+ DisplayManager: gdm3
+ DistroRelease: Ubuntu 19.04
+ InstallationDate: Installed on 2018-04-27 (361 days ago)
+ InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
+ NonfreeKernelModules: nvidia_modeset nvidia
+ Package: gnome-shell 3.32.0+git20190410-1ubuntu1
+ PackageArchitecture: amd64
+ ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6
+ Tags: disco third-party-packages
+ Uname: Linux 5.0.0-13-generic x86_64
+ UpgradeStatus: Upgraded to disco on 2019-04-19 (4 days ago)
+ UserGroups: adm cdrom dialout dip docker libvirt lpadmin plugdev sambashare 
sudo vboxusers
+ _MarkForUpload: True

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

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

Title:
  old bug "nm-applet stop showing vpn status" is back

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  old bug  #1756720 "nm-applet stop showing vpn status" is back after upgrade 
to Ubuntu 19.04
  ---

  1. The specific steps or actions you took that caused you to encounter
  the problem.

Connect to any VPN. Connection is open.

  
  2. The behavior you expected.

VPN connection should be displayed as connected in
  "Settings->Network->VPN" as well as in nm-applet (upper right corner
  of display)

  
  3. The behavior you actually encountered (in as much detail as possible).

In "Settings->Network->VPN" it is shown as open but in nm-applet
  as closed.

  ---
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 19.04
  InstallationDate: Installed on 2018-04-27 (361 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: gnome-shell 3.32.0+git20190410-1ubuntu1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6
  Tags: disco third-party-packages
  Uname: Linux 5.0.0-13-generic x86_64
  UpgradeStatus: Upgraded to disco on 2019-04-19 (4 days ago)
  UserGroups: adm cdrom dialout dip docker libvirt lpadmin plugdev sambashare 
sudo vboxusers
  _MarkForUpload: True

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

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


[Desktop-packages] [Bug 1825497] Re: flash player does not work in chromium

2019-04-23 Thread nico
i've only installed the package adobe-flashplugin (it worked in both
browsers until 20th april, now only works on firefox) from the canonical
software repo.   google-chrome (not chromium) it's supposed to have
integrated flash, but it didn't work either.

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

Title:
  flash player does not work in chromium

Status in chromium-browser package in Ubuntu:
  Confirmed
Status in firefox package in Ubuntu:
  Invalid

Bug description:
  after you allow it to run it doesn't.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: chromium-browser 73.0.3683.103-0ubuntu1
  ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6
  Uname: Linux 5.0.0-13-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  DRM.card0-DP-1:
   enabled: disabled
   dpms: Off
   status: disconnected
   edid-base64: 
   modes:
  DRM.card0-HDMI-A-1:
   enabled: enabled
   dpms: On
   status: connected
   edid-base64: 
AP///wAEcqMAdkcABTIUAQOANR146mCFplZKnCUSUFSzDABxT4EAlQDRwIGAAQEBAQEBAjqAGHE4LUBYLEUAEyohAAAa/ABWMjQzSAogICAgICAg/QA4TB9TEgAKICAgICAg/wBMRlYwQzAyMTQwRjEKAPU=
   modes: 1920x1080 1280x1024 1440x900 1280x800 1152x864 1024x768 1024x768 
800x600 800x600 640x480 640x480 720x400
  DRM.card0-HDMI-A-2:
   enabled: disabled
   dpms: Off
   status: disconnected
   edid-base64: 
   modes:
  Date: Fri Apr 19 04:29:19 2019
  Desktop-Session:
   'ubuntu'
   '/etc/xdg/xdg-ubuntu:/etc/xdg'
   
'/usr/share/ubuntu:/usr/local/share:/usr/share:/var/lib/snapd/desktop:/var/lib/snapd/desktop'
  DetectedPlugins:
   
  Env:
   'None'
   'None'
  ExecutablePath: /usr/lib/chromium-browser/chromium-browser
  InstallationDate: Installed on 2017-04-20 (729 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  Load-Avg-1min: 1.18
  Load-Processes-Running-Percent:   0.4%
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 04ca:0050 Lite-On Technology Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: System manufacturer System Product Name
  ProcEnviron:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-13-generic 
root=UUID=71d156ea-3173-43e9-9a5e-00edcd2137f2 ro splash quiet vt.handoff=1
  SourcePackage: chromium-browser
  UpgradeStatus: Upgraded to disco on 2019-04-19 (0 days ago)
  dmi.bios.date: 02/28/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 4202
  dmi.board.asset.tag: Default string
  dmi.board.name: H110M-A/M.2
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr4202:bd02/28/2019:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnH110M-A/M.2:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.sku: SKU
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer
  etcconfigcpepperflashpluginnonfree:
   flashso="/usr/lib/pepperflashplugin-nonfree/libpepflashplayer.so"
   flashversion=`strings $flashso 2> /dev/null | grep LNX | cut -d ' ' -f 2 | 
sed -e "s/,/./g"`
   CHROMIUM_FLAGS="$CHROMIUM_FLAGS --ppapi-flash-path=$flashso 
--ppapi-flash-version=$flashversion"
  modified.conffile..etc.default.chromium-browser: [deleted]

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

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


[Desktop-packages] [Bug 1826052] Re: LibreOffice on Ubuntu 19.04 screws up text paragraph styling

2019-04-23 Thread Olivier Tilloy
Thanks for the report Eamon.
Would you be able to share such a document, so that others can test, confirm 
and investigate the problem?

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

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

Title:
  LibreOffice on Ubuntu 19.04 screws up text paragraph styling

Status in libreoffice package in Ubuntu:
  Incomplete

Bug description:

  After updating Ubuntu to 19.04 documents previously created in
  LibreOffice had some of their paragraph styling wiped, e.g. a custom
  heading style was arbitrarily removed in some but not all instances in
  a document and was replaced with 'Default Style'.

  LibreOffice Version: 6.2.2.2
  Build ID: 1:6.2.2-0ubuntu2
  CPU threads: 4; OS: Linux 5.0; UI render: default; VCL: gtk3; 
  Locale: en-GB (en_GB.UTF-8); UI-Language: en-GB
  Calc: threaded

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

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


[Desktop-packages] [Bug 1825983] Re: chromium-browser ignores system proxy settings

2019-04-23 Thread Olivier Tilloy
Can you compare the output of the following page when chromium is
launched with and without the --proxy-server command-line parameter?

chrome://net-internals/#proxy

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

Title:
  chromium-browser ignores system proxy settings

Status in chromium-browser package in Ubuntu:
  New

Bug description:
  Ubuntu 18.04.2
  chromium-browser 73.0.3683.86

  Network proxy is configured via Settings GUI dialog. chromium-browser
  is started with verbose output:

  [9810:9810:0423/134338.510775:VERBOSE1:proxy_config_service_linux.cc(484)] 
All gsettings tests OK. Will get proxy config from gsettings.
  [9810:9810:0423/134338.510926:VERBOSE1:proxy_config_service_linux.cc(1243)] 
Obtained proxy settings from annotation hash code 11258689
  
[9810:9810:0423/134338.510949:VERBOSE1:pref_proxy_config_tracker_impl.cc(184)] 
0x55e7b2944b00: set chrome proxy config service to 0x55e7b27e3f10

  Listing all gsettings with proxy:
  ~$ gsettings list-recursively | grep proxy
  will return:

  org.gnome.system.proxy.http host 'gse.auk.cvclab.lan'
  org.gnome.system.proxy.http port 9191
  org.gnome.system.proxy.http use-authentication false
  org.gnome.system.proxy.http authentication-password ''
  org.gnome.system.proxy.http authentication-user ''
  org.gnome.system.proxy.http enabled false
  org.gnome.evolution.shell.network-config proxy-type 0
  org.gnome.evolution.shell.network-config use-http-proxy false
  org.gnome.system.proxy.https host ''
  org.gnome.system.proxy.https port 0
  org.gnome.system.proxy.socks host ''
  org.gnome.system.proxy.socks port 0
  org.gnome.system.proxy.ftp host ''
  org.gnome.system.proxy.ftp port 0
  org.gnome.system.proxy use-same-proxy true
  org.gnome.system.proxy mode 'manual'
  org.gnome.system.proxy autoconfig-url ''
  org.gnome.system.proxy ignore-hosts ['localhost', '127.0.0.0/8', '::1']
  org.gnome.settings-daemon.plugins.screensaver-proxy active true
  org.gnome.settings-daemon.plugins.screensaver-proxy priority 0

  chromium-browsers fails to connect to the internet with the error
  message: ERR_CONNECTION_TIMED_OUT

  
  Starting chromium-browser with the proxy command line parameter:
  ~$ chromium-browser --proxy-server="gse.auk.cvclab.lan:9191"
  This starts the browser and the internet connection works fine.

  With Firefox there are no issues, it works with the configured system
  proxy settings.

  Regards

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

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


[Desktop-packages] [Bug 1825963] Re: Abysmal memory leak on tracker-extract

2019-04-23 Thread gert7
I have the same game installed as well.

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

Title:
  Abysmal memory leak on tracker-extract

Status in tracker package in Ubuntu:
  Incomplete

Bug description:
  After upgrading from 18.10 to 19.04 my Ubuntu desktop started lagging
  madly. It became very difficult to use and I discovered the problem to
  be tracker-extract running and very rapidly leaking memory up to 100%
  and breaching into swap memory. I tried killing it several times but
  Tracker appears to relaunch it every time, so I deleted it from
  /usr/lib/tracker entirely.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: tracker 2.1.8-2
  ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6
  Uname: Linux 5.0.0-13-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Apr 23 13:02:25 2019
  InstallationDate: Installed on 2019-03-11 (42 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  SourcePackage: tracker
  UpgradeStatus: Upgraded to disco on 2019-04-23 (0 days ago)

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

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


[Desktop-packages] [Bug 1825497] Re: flash player does not work in firefox or chromium

2019-04-23 Thread Olivier Tilloy
Works here in firefox (you'll need to install flashplugin-installer).

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

** Summary changed:

- flash player does not work in firefox or chromium
+ flash player does not work in chromium

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

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

Title:
  flash player does not work in chromium

Status in chromium-browser package in Ubuntu:
  Confirmed
Status in firefox package in Ubuntu:
  Invalid

Bug description:
  after you allow it to run it doesn't.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: chromium-browser 73.0.3683.103-0ubuntu1
  ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6
  Uname: Linux 5.0.0-13-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  DRM.card0-DP-1:
   enabled: disabled
   dpms: Off
   status: disconnected
   edid-base64: 
   modes:
  DRM.card0-HDMI-A-1:
   enabled: enabled
   dpms: On
   status: connected
   edid-base64: 
AP///wAEcqMAdkcABTIUAQOANR146mCFplZKnCUSUFSzDABxT4EAlQDRwIGAAQEBAQEBAjqAGHE4LUBYLEUAEyohAAAa/ABWMjQzSAogICAgICAg/QA4TB9TEgAKICAgICAg/wBMRlYwQzAyMTQwRjEKAPU=
   modes: 1920x1080 1280x1024 1440x900 1280x800 1152x864 1024x768 1024x768 
800x600 800x600 640x480 640x480 720x400
  DRM.card0-HDMI-A-2:
   enabled: disabled
   dpms: Off
   status: disconnected
   edid-base64: 
   modes:
  Date: Fri Apr 19 04:29:19 2019
  Desktop-Session:
   'ubuntu'
   '/etc/xdg/xdg-ubuntu:/etc/xdg'
   
'/usr/share/ubuntu:/usr/local/share:/usr/share:/var/lib/snapd/desktop:/var/lib/snapd/desktop'
  DetectedPlugins:
   
  Env:
   'None'
   'None'
  ExecutablePath: /usr/lib/chromium-browser/chromium-browser
  InstallationDate: Installed on 2017-04-20 (729 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  Load-Avg-1min: 1.18
  Load-Processes-Running-Percent:   0.4%
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 04ca:0050 Lite-On Technology Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: System manufacturer System Product Name
  ProcEnviron:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-13-generic 
root=UUID=71d156ea-3173-43e9-9a5e-00edcd2137f2 ro splash quiet vt.handoff=1
  SourcePackage: chromium-browser
  UpgradeStatus: Upgraded to disco on 2019-04-19 (0 days ago)
  dmi.bios.date: 02/28/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 4202
  dmi.board.asset.tag: Default string
  dmi.board.name: H110M-A/M.2
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr4202:bd02/28/2019:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnH110M-A/M.2:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.sku: SKU
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer
  etcconfigcpepperflashpluginnonfree:
   flashso="/usr/lib/pepperflashplugin-nonfree/libpepflashplayer.so"
   flashversion=`strings $flashso 2> /dev/null | grep LNX | cut -d ' ' -f 2 | 
sed -e "s/,/./g"`
   CHROMIUM_FLAGS="$CHROMIUM_FLAGS --ppapi-flash-path=$flashso 
--ppapi-flash-version=$flashversion"
  modified.conffile..etc.default.chromium-browser: [deleted]

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

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


[Desktop-packages] [Bug 1825497] Re: flash player does not work in firefox or chromium

2019-04-23 Thread Olivier Tilloy
Chromium upstream bug report:
https://bugs.chromium.org/p/chromium/issues/detail?id=949312.

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

Title:
  flash player does not work in chromium

Status in chromium-browser package in Ubuntu:
  Confirmed
Status in firefox package in Ubuntu:
  Invalid

Bug description:
  after you allow it to run it doesn't.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: chromium-browser 73.0.3683.103-0ubuntu1
  ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6
  Uname: Linux 5.0.0-13-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  DRM.card0-DP-1:
   enabled: disabled
   dpms: Off
   status: disconnected
   edid-base64: 
   modes:
  DRM.card0-HDMI-A-1:
   enabled: enabled
   dpms: On
   status: connected
   edid-base64: 
AP///wAEcqMAdkcABTIUAQOANR146mCFplZKnCUSUFSzDABxT4EAlQDRwIGAAQEBAQEBAjqAGHE4LUBYLEUAEyohAAAa/ABWMjQzSAogICAgICAg/QA4TB9TEgAKICAgICAg/wBMRlYwQzAyMTQwRjEKAPU=
   modes: 1920x1080 1280x1024 1440x900 1280x800 1152x864 1024x768 1024x768 
800x600 800x600 640x480 640x480 720x400
  DRM.card0-HDMI-A-2:
   enabled: disabled
   dpms: Off
   status: disconnected
   edid-base64: 
   modes:
  Date: Fri Apr 19 04:29:19 2019
  Desktop-Session:
   'ubuntu'
   '/etc/xdg/xdg-ubuntu:/etc/xdg'
   
'/usr/share/ubuntu:/usr/local/share:/usr/share:/var/lib/snapd/desktop:/var/lib/snapd/desktop'
  DetectedPlugins:
   
  Env:
   'None'
   'None'
  ExecutablePath: /usr/lib/chromium-browser/chromium-browser
  InstallationDate: Installed on 2017-04-20 (729 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  Load-Avg-1min: 1.18
  Load-Processes-Running-Percent:   0.4%
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 04ca:0050 Lite-On Technology Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: System manufacturer System Product Name
  ProcEnviron:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-13-generic 
root=UUID=71d156ea-3173-43e9-9a5e-00edcd2137f2 ro splash quiet vt.handoff=1
  SourcePackage: chromium-browser
  UpgradeStatus: Upgraded to disco on 2019-04-19 (0 days ago)
  dmi.bios.date: 02/28/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 4202
  dmi.board.asset.tag: Default string
  dmi.board.name: H110M-A/M.2
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr4202:bd02/28/2019:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnH110M-A/M.2:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.sku: SKU
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer
  etcconfigcpepperflashpluginnonfree:
   flashso="/usr/lib/pepperflashplugin-nonfree/libpepflashplayer.so"
   flashversion=`strings $flashso 2> /dev/null | grep LNX | cut -d ' ' -f 2 | 
sed -e "s/,/./g"`
   CHROMIUM_FLAGS="$CHROMIUM_FLAGS --ppapi-flash-path=$flashso 
--ppapi-flash-version=$flashversion"
  modified.conffile..etc.default.chromium-browser: [deleted]

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

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


[Desktop-packages] [Bug 917318] Re: totem crashed with SIGSEGV in g_rec_mutex_get_impl()

2019-04-23 Thread Paul White
We are sorry that we do not always have the capacity to review all
reported bugs in a timely manner. You reported this bug some time ago
and there have been many changes in Ubuntu since that time.

Ubuntu 12.04 (precise) reached end-of-life on April 28, 2017.

Do you still see a problem related to the one that you reported in a
currently supported version of Ubuntu? Please let us know if you do
otherwise this report can be left to expire in approximately 60 days
time.

Thank you for helping make Ubuntu better.

Paul White
[Ubuntu Bug Squad]


** Changed in: totem (Ubuntu)
   Status: Confirmed => Incomplete

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

Title:
  totem crashed with SIGSEGV in g_rec_mutex_get_impl()

Status in totem package in Ubuntu:
  Incomplete

Bug description:
  Description:  Ubuntu precise (development branch)
  Release:  12.04

  I closed totem, it appeared to close fine, but then I got a crash
  report dialogue.

  ProblemType: Crash
  DistroRelease: Ubuntu 12.04
  Package: totem 3.0.1-0ubuntu15
  ProcVersionSignature: Ubuntu 3.2.0-9.16-generic 3.2.1
  Uname: Linux 3.2.0-9-generic x86_64
  ApportVersion: 1.90-0ubuntu2
  Architecture: amd64
  Date: Mon Jan 16 19:15:52 2012
  ExecutablePath: /usr/bin/totem
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Alpha amd64 
(20120112)
  ProcCmdline: totem
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  SegvAnalysis:
   Segfault happened at: 0x7f7d6fe65d14 :   mov
(%rdi),%rax
   PC (0x7f7d6fe65d14) ok
   source "(%rdi)" (0x) not located in a known VMA region 
(needed readable region)!
   destination "%rax" ok
  SegvReason: reading unknown VMA
  Signal: 11
  SourcePackage: totem
  StacktraceTop:
   g_rec_mutex_lock () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_static_rec_mutex_lock () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/gstreamer-0.10/libgstplaybin.so
   ?? () from /usr/lib/x86_64-linux-gnu/gstreamer-0.10/libgstplaybin.so
   ?? () from /usr/lib/x86_64-linux-gnu/gstreamer-0.10/libgstplaybin.so
  Title: totem crashed with SIGSEGV in g_rec_mutex_lock()
  UpgradeStatus: Upgraded to precise on 2012-01-13 (2 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

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

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


[Desktop-packages] [Bug 1681544] Re: i am not able to use media player and vlc audio and video is not coming also i m not able to install xampp 1.8.3 on my ubuntu os

2019-04-23 Thread Paul White
We are sorry that we do not always have the capacity to review all
reported bugs in a timely manner. You reported this bug some time ago
and there have been many changes in Ubuntu since that time.

Ubuntu 12.04 (precise) reached end-of-life on April 28, 2017.

Do you still see problems related to those that you reported using a
currently supported version of Ubuntu? Please let us know if you do
otherwise this report can be left to expire in approximately 60 days
time.

Thank you for helping make Ubuntu better.

Paul White
[Ubuntu Bug Squad]


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

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

Title:
  i am not able to use media player and vlc audio and video is not
  coming also i m not able to install xampp 1.8.3 on my ubuntu os

Status in totem package in Ubuntu:
  Incomplete

Bug description:
  My issue with related to media palyer and vlc media player i m not
  able to work with xampp 1.8.3 on my ubuntu os

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: totem 3.0.1-0ubuntu21.1
  ProcVersionSignature: Ubuntu 3.2.0-56.86-generic 3.2.51
  Uname: Linux 3.2.0-56-generic x86_64
  ApportVersion: 2.0.1-0ubuntu17.6
  Architecture: amd64
  Date: Tue Apr 11 00:01:57 2017
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 
(20120425)
  MarkForUpload: True
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: totem
  UpgradeStatus: Upgraded to precise on 2017-04-10 (0 days ago)

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

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


[Desktop-packages] [Bug 1826052] [NEW] LibreOffice on Ubuntu 19.04 screws up text paragraph styling

2019-04-23 Thread Eamon
Public bug reported:


After updating Ubuntu to 19.04 documents previously created in
LibreOffice had some of their paragraph styling wiped, e.g. a custom
heading style was arbitrarily removed in some but not all instances in a
document and was replaced with 'Default Style'.

LibreOffice Version: 6.2.2.2
Build ID: 1:6.2.2-0ubuntu2
CPU threads: 4; OS: Linux 5.0; UI render: default; VCL: gtk3; 
Locale: en-GB (en_GB.UTF-8); UI-Language: en-GB
Calc: threaded

** Affects: libreoffice (Ubuntu)
 Importance: Undecided
 Status: 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/1826052

Title:
  LibreOffice on Ubuntu 19.04 screws up text paragraph styling

Status in libreoffice package in Ubuntu:
  New

Bug description:

  After updating Ubuntu to 19.04 documents previously created in
  LibreOffice had some of their paragraph styling wiped, e.g. a custom
  heading style was arbitrarily removed in some but not all instances in
  a document and was replaced with 'Default Style'.

  LibreOffice Version: 6.2.2.2
  Build ID: 1:6.2.2-0ubuntu2
  CPU threads: 4; OS: Linux 5.0; UI render: default; VCL: gtk3; 
  Locale: en-GB (en_GB.UTF-8); UI-Language: en-GB
  Calc: threaded

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

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


[Desktop-packages] [Bug 1025557] Re: ".O" or ".Z" in folder = Could not open location; you might not have permission to open the file

2019-04-23 Thread Paul White
We are sorry that we do not always have the capacity to review all
reported bugs in a timely manner. You reported this bug some time ago
and there have been many changes in Ubuntu since that time.

Ubuntu 12.04 (precise) reached end-of-life on April 28, 2017.

Do you still see a problem related to the one that you reported in a
currently supported version of Ubuntu? Please let us know if you do
otherwise this report can be left to expire in approximately 60 days
time.

Thank you for helping make Ubuntu better.

Paul White
[Ubuntu Bug Squad]


** Changed in: totem (Ubuntu)
   Status: Confirmed => Incomplete

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

Title:
  ".O" or ".Z" in folder = Could not open location; you might not have
  permission to open the file

Status in totem package in Ubuntu:
  Incomplete

Bug description:
  You can open folders using totem if you right-click a folder  > open with > 
totem (movie player).
  There is a problem however, if you try and open a folder that ends with ".o" 
or ".z" (capital or lower letters)

  How to reproduce: Rename a folder to "Myfolder.O" and try to open it
  with totem using right-click.

  MyfolderO opens fine.
  Myfolder.O causes an error:  An error occurred -- Could not open location; 
you might not have permission to open the file.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: libgstreamer0.10-0 0.10.36-1ubuntu1
  ProcVersionSignature: Ubuntu 3.2.0-26.41-generic 3.2.19
  Uname: Linux 3.2.0-26-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.0.1-0ubuntu8
  Architecture: amd64
  Date: Tue Jul 17 09:32:36 2012
  EcryptfsInUse: Yes
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 
(20120425)
  SourcePackage: gstreamer0.10
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1826046] Re: gnome-disk-utility partition display wrong

2019-04-23 Thread BertN45
SORRY Rebooting the system restores the correct display, restarting the
disk utility did not help. Any action in the extended partitions
distorts the display of those logical partitions.

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

Title:
  gnome-disk-utility partition display wrong

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

Bug description:
  See screenshot with comparison gparted and gnome-disk-utility, the
  display of gparted is correct. The display of the gnome-disk utility
  was distorted after I deleted the swap partition, recreating that
  partition with gparted did not correct the display. Rebooting did not
  correct the display.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-disk-utility 3.28.3-0ubuntu1~18.04.1
  ProcVersionSignature: Ubuntu 4.15.0-47.50-generic 4.15.18
  Uname: Linux 4.15.0-47-generic x86_64
  NonfreeKernelModules: nvidia zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  CurrentDesktop: MATE
  Date: Tue Apr 23 15:04:19 2019
  SourcePackage: gnome-disk-utility
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1824855] Re: very long delay to display login prompt if there are a large number of uncleared desktop notifications

2019-04-23 Thread Steve Langasek
After locking my screen and trying to log in, here's what I see in the
log corresponding to a delay in the login prompt being shown.

I have not configured fingerprint authentication and never will, so I
don't know why this is spawned or failing to spawn.

$ journalctl -b0 --since '2019-04-23 12:18' --no-pager
-- Logs begin at Sat 2019-02-02 22:33:11 PST, end at Tue 2019-04-23 12:19:26 
PDT. --
Apr 23 12:18:41 virgil gnome-shell[4982]: JS WARNING: 
[resource:///org/gnome/gjs/modules/signals.js 128]: Too many arguments to 
method Clutter.Actor.destroy: expected 0, got 1
Apr 23 12:18:45 virgil dbus-daemon[2096]: [system] Activating via systemd: 
service name='net.reactivated.Fprint' unit='fprintd.service' requested by 
':1.360' (uid=1000 pid=4982 comm="/usr/bin/gnome-shell " label="unconfined")
Apr 23 12:18:45 virgil systemd[1]: Starting Fingerprint Authentication Daemon...
Apr 23 12:19:10 virgil dbus-daemon[2096]: [system] Failed to activate service 
'net.reactivated.Fprint': timed out (service_start_timeout=25000ms)
Apr 23 12:19:10 virgil gnome-shell[4982]: Failed to connect to Fprint service: 
Error calling StartServiceByName for net.reactivated.Fprint: 
GDBus.Error:org.freedesktop.DBus.Error.TimedOut: Failed to activate service 
'net.reactivated.Fprint': timed out (service_start_timeout=25000ms)
Apr 23 12:19:12 virgil gdm-password][23487]: pam_krb5(gdm-password:auth): user 
vorlon authenticated as [REDACTED]
Apr 23 12:19:12 virgil gdm-password][23487]: gkr-pam: unlocked login keyring
Apr 23 12:19:13 virgil NetworkManager[2098]:   [1556047153.6710] 
agent-manager: req[0x55dda12f3ae0, :1.360/org.gnome.Shell.NetworkAgent/1000]: 
agent registered
Apr 23 12:19:13 virgil /usr/lib/gdm3/gdm-x-session[4767]: dbus-daemon[4783]: 
[session uid=1000 pid=4783] Activating service name='org.gnome.Nautilus' 
requested by ':1.26' (uid=1000 pid=4982 comm="/usr/bin/gnome-shell " 
label="unconfined")
Apr 23 12:19:13 virgil /usr/lib/gdm3/gdm-x-session[4767]: dbus-daemon[4783]: 
[session uid=1000 pid=4783] Activating service 
name='org.freedesktop.FileManager1' requested by ':1.26' (uid=1000 pid=4982 
comm="/usr/bin/gnome-shell " label="unconfined")
Apr 23 12:19:14 virgil /usr/lib/gdm3/gdm-x-session[4767]: dbus-daemon[4783]: 
[session uid=1000 pid=4783] Successfully activated service 'org.gnome.Nautilus'
Apr 23 12:19:14 virgil /usr/lib/gdm3/gdm-x-session[4767]: Failed to register: 
Unable to acquire bus name 'org.gnome.Nautilus'
Apr 23 12:19:14 virgil /usr/lib/gdm3/gdm-x-session[4767]: dbus-daemon[4783]: 
[session uid=1000 pid=4783] Activated service 'org.freedesktop.FileManager1' 
failed: Process org.freedesktop.FileManager1 exited with status 1
Apr 23 12:19:18 virgil gnome-shell[4982]: Couldn’t parse steam.desktop as a 
desktop file, will treat it as a regular file.
Apr 23 12:19:18 virgil gnome-shell[4982]: Error connecting to Nautilus
Apr 23 12:19:19 virgil gnome-shell[4982]: [AppIndicatorSupport-DEBUG] Using 
Brute-force mode for StatusNotifierItem 
:1.83/org/ayatana/NotificationItem/software_update_available
Apr 23 12:19:19 virgil gnome-shell[4982]: [AppIndicatorSupport-DEBUG] 
Registering StatusNotifierItem 
:1.83/org/ayatana/NotificationItem/software_update_available
Apr 23 12:19:23 virgil org.gnome.Shell.desktop[4982]: Window manager warning: 
Overwriting existing binding of keysym 31 with keysym 31 (keycode a).
Apr 23 12:19:23 virgil org.gnome.Shell.desktop[4982]: Window manager warning: 
Overwriting existing binding of keysym 32 with keysym 32 (keycode b).
Apr 23 12:19:23 virgil org.gnome.Shell.desktop[4982]: Window manager warning: 
Overwriting existing binding of keysym 33 with keysym 33 (keycode c).
Apr 23 12:19:23 virgil org.gnome.Shell.desktop[4982]: Window manager warning: 
Overwriting existing binding of keysym 34 with keysym 34 (keycode d).
Apr 23 12:19:23 virgil org.gnome.Shell.desktop[4982]: Window manager warning: 
Overwriting existing binding of keysym 35 with keysym 35 (keycode e).
Apr 23 12:19:23 virgil org.gnome.Shell.desktop[4982]: Window manager warning: 
Overwriting existing binding of keysym 38 with keysym 38 (keycode 11).
Apr 23 12:19:23 virgil org.gnome.Shell.desktop[4982]: Window manager warning: 
Overwriting existing binding of keysym 39 with keysym 39 (keycode 12).
Apr 23 12:19:23 virgil org.gnome.Shell.desktop[4982]: Window manager warning: 
Overwriting existing binding of keysym 36 with keysym 36 (keycode f).
Apr 23 12:19:23 virgil org.gnome.Shell.desktop[4982]: Window manager warning: 
Overwriting existing binding of keysym 37 with keysym 37 (keycode 10).


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

** Changed in: gdm3 (Ubuntu)
   Status: Opinion => New

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

Title:
  very long delay to display login prompt if there are a large number of
  uncleared desktop notifications

Status in gdm3 package in Ubuntu:

[Desktop-packages] [Bug 255345] Re: Comments field in Nautilus' Audio properties tab does not wrap for long comments on audio files

2019-04-23 Thread Paul White
Issue now being tracked at:
https://gitlab.gnome.org/GNOME/nautilus/issues/896

** Bug watch added: gitlab.gnome.org/GNOME/nautilus/issues #896
   https://gitlab.gnome.org/GNOME/nautilus/issues/896

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

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

Title:
  Comments field in Nautilus' Audio properties tab does not wrap for
  long comments on audio files

Status in Nautilus:
  Unknown
Status in Totem:
  Expired
Status in totem package in Ubuntu:
  Triaged

Bug description:
  Binary package hint: nautilus

  ---System Info---
  Description:  Ubuntu 8.04.1
  Release:  8.04

  ---Package Info---
  nautilus:
Installed: 1:2.22.3-0ubuntu2
Candidate: 1:2.22.3-0ubuntu2
Version table:
   *** 1:2.22.3-0ubuntu2 0
  500 http://ftp.ussg.iu.edu hardy-updates/main Packages
  100 /var/lib/dpkg/status
   1:2.22.2-0ubuntu4 0
  500 http://ftp.ussg.iu.edu hardy/main Packages

  ---Problem Info---
  When using Nautilus to view the properties of an audio file format that 
contains metadata (such as MP3s) the audio tab does not wrap the Comments data. 
 For longer comments, it makes it impossible to view the information about the 
file even when the File Properties window is expanded to its maximum size.

  See attached screenshot for an example.

  ProblemType: Bug
  Architecture: i386
  Date: Wed Aug  6 08:41:09 2008
  DistroRelease: Ubuntu 8.04
  ExecutablePath: /usr/bin/nautilus
  Package: nautilus 1:2.22.3-0ubuntu2
  PackageArchitecture: i386
  ProcEnviron:
   PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: nautilus
  Uname: Linux 2.6.24-19-generic i686

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

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


[Desktop-packages] [Bug 1768976] Re: Ubuntu 18.04 is overheating after upgrade from 16.04

2019-04-23 Thread Simon Ádám
UPDATE:
After blacklisting nuoveau and installing nvidia driver, there was no overheat 
shutdown, but the cpu is on full speed all the time. and the tempetature is 87 
celsius constantly.
I tried disabling pstate, using tlp, neither worked so far.
Here is a usual frame from top:

top - 21:19:30 up 27 min,  1 user,  load average: 2,84, 2,52, 2,26
Tasks: 251 total,   3 running, 197 sleeping,   0 stopped,   1 zombie
%Cpu(s): 65,2 us, 20,7 sy,  0,1 ni, 13,3 id,  0,1 wa,  0,0 hi,  0,7 si,  0,0 st
KiB Mem :  3780788 total,   152620 free,  2611464 used,  1016704 buff/cache
KiB Swap:  8000508 total,  7999228 free, 1280 used.   794276 avail Mem 

  PID USER  PR  NIVIRTRESSHR S  %CPU %MEM TIME+ COMMAND
  275 root  20   0  227032 182460   3284 R  94,4  4,8  24:46.69 
systemd-udevd
  283 root  20   0   45892   5740   4568 R  16,7  0,2   5:12.21 
systemd-udevd
  758 root  20   0 1077448  26772  12596 S  11,1  0,7   1:48.09 snapd
 4408 adtewa20   0   52876   3992   3396 R  11,1  0,1   0:00.02 top
7 root  20   0   0  0  0 S   5,6  0,0   0:02.51 ksoftirqd/0
  261 root  19  -1  164940  55772  54552 S   5,6  1,5   1:07.56 
systemd-journal
1 root  20   0  159928   9212   6696 S   0,0  0,2   0:01.86 systemd

systemd-udevd is running near 100% all the time.

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

Title:
  Ubuntu 18.04 is overheating after upgrade from 16.04

Status in linux package in Ubuntu:
  Confirmed
Status in xserver-xorg-video-nouveau package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu is overheating at my laptop. Opening youtube on firefox is
  enough for critical temperature shutdown.

  Using lm-sensors for monitoring on 18.04 the temp varies between 70 and 85°C 
with only firefox or chrome open and doing nothing. 
  On my old 16.04 with same using, the temp varies between 55 and 70°C.

  First thought was the driver nouveau is the problem, and finally I was
  able to install by add "nouveau.modeset=0" at livecd boot options,
  without temp shutdown.

  After install I disable the nouveau at modprobe blacklist, but the
  system continues overheating and shutdown with basic usage.

  
  I have no idea what's happening with the bionic at my laptop.

  My laptop is a Samsung RF411 i5 2nd Generation and Geforce 540M.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: ubuntu-release-upgrader-core 1:18.04.17
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CrashDB: ubuntu
  CurrentDesktop: ubuntu:GNOME
  Date: Thu May  3 16:22:40 2018
  InstallationDate: Installed on 2018-04-27 (6 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: dist-upgrade
  UpgradeStatus: No upgrade log present (probably fresh install)
  VarLogDistupgradeAptHistorylog:
   Start-Date: 2018-04-27  15:46:02
   End-Date: 2018-04-27  15:46:02
  VarLogDistupgradeAptlog:
   Log time: 2018-04-27 15:45:39.753331
   Starting pkgProblemResolver with broken count: 0
   Starting 2 pkgProblemResolver with broken count: 0
   Done
   Log time: 2018-04-27 15:46:04.859979
  VarLogDistupgradeApttermlog:
   Log started: 2018-04-27  15:46:02
   Log ended: 2018-04-27  15:46:02
  --- 
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.9-0ubuntu7.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  edir   2354 F pulseaudio
  CompositorRunning: None
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroRelease: Ubuntu 18.04
  DistroVariant: ubuntu
  DkmsStatus:
   bcmwl, 6.30.223.271+bdcom, 4.15.0-20-generic, x86_64: installed
   bcmwl, 6.30.223.271+bdcom, 4.15.0-22-generic, x86_64: installed
  GraphicsCard:
   Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: Samsung Electronics Co Ltd 2nd Generation Core Processor Family 
Integrated Graphics Controller [144d:c0a5]
 Subsystem: Samsung Electronics Co Ltd GF108M [GeForce GT 540M] [144d:c0a5]
  HibernationDevice: RESUME=UUID=e7a61aee-64c2-4c88-b4e1-4de481d0f88d
  InstallationDate: Installed on 2018-04-27 (36 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  MachineType: SAMSUNG ELECTRONICS CO., LTD. RF511/RF411/RF711
  NonfreeKernelModules: wl
  Package: xserver-xorg-video-nouveau 1:1.0.15-2
  PackageArchitecture: amd64
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-22-generic 
root=UUID=db38a22c-0e9f-4e1a-b9f7-f7aac2544394 ro quiet splash nouveau.runpm=0
  ProcVersionSignature: Ubuntu 

[Desktop-packages] [Bug 475707] Re: Totem crashes when exiting fullscreen mode and Compiz's Wobbly Windows is turned on

2019-04-23 Thread Paul White
Last comment from reporter was over 9 years ago and
he/she did not respond to comments #4, #5 or #6. 

Bug report would have expired but set to "In Progress"
without any explanation so closing now as "Invalid".


** Changed in: totem (Ubuntu)
   Status: In Progress => Invalid

** Changed in: totem
   Status: New => Invalid

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

Title:
  Totem crashes when exiting fullscreen mode and Compiz's Wobbly Windows
  is turned on

Status in Totem:
  Invalid
Status in totem package in Ubuntu:
  Invalid

Bug description:
  Binary package hint: totem

  When watching a DVD in Fullscreen mode with Compiz's Wobbly Windows
  turned on, the DVD didn't render itself to 16:9 correctly, and Totem
  crashed as soon as I exited Fullscreen mode. The work around is to
  turn off Wobbly Windows. I'm using the version of Totem that came with
  Ubuntu 9.10 and I am using the NVIDIA 185 driver.

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

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


[Desktop-packages] [Bug 1826046] [NEW] gnome-disk-utility partition display wrong

2019-04-23 Thread BertN45
Public bug reported:

See screenshot with comparison gparted and gnome-disk-utility, the
display of gparted is correct. The display of the gnome-disk utility was
distorted after I deleted the swap partition, recreating that partition
with gparted did not correct the display. Rebooting did not correct the
display.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: gnome-disk-utility 3.28.3-0ubuntu1~18.04.1
ProcVersionSignature: Ubuntu 4.15.0-47.50-generic 4.15.18
Uname: Linux 4.15.0-47-generic x86_64
NonfreeKernelModules: nvidia zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.9-0ubuntu7.6
Architecture: amd64
CurrentDesktop: MATE
Date: Tue Apr 23 15:04:19 2019
SourcePackage: gnome-disk-utility
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug bionic

** Attachment added: "Screenshot at 2019-04-23 15-03-18.png"
   
https://bugs.launchpad.net/bugs/1826046/+attachment/5258321/+files/Screenshot%20at%202019-04-23%2015-03-18.png

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

Title:
  gnome-disk-utility partition display wrong

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

Bug description:
  See screenshot with comparison gparted and gnome-disk-utility, the
  display of gparted is correct. The display of the gnome-disk utility
  was distorted after I deleted the swap partition, recreating that
  partition with gparted did not correct the display. Rebooting did not
  correct the display.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-disk-utility 3.28.3-0ubuntu1~18.04.1
  ProcVersionSignature: Ubuntu 4.15.0-47.50-generic 4.15.18
  Uname: Linux 4.15.0-47-generic x86_64
  NonfreeKernelModules: nvidia zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  CurrentDesktop: MATE
  Date: Tue Apr 23 15:04:19 2019
  SourcePackage: gnome-disk-utility
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1044988] Re: double click opens totem twice and freezes

2019-04-23 Thread Paul White
We are sorry that we do not always have the capacity to review all
reported bugs in a timely manner. This bug was reported some time ago
and there have been many changes in Ubuntu since that time.

Ubuntu 12.10 (quantal) reached end-of-life on May 16, 2014.

Does anyone still see a problem related to the one that was reported
using a currently supported version of Ubuntu? Please let us know if you
do otherwise this report can be left to expire in approximately 60 days
time.

Thank you for helping make Ubuntu better.

Paul White
[Ubuntu Bug Squad]

** Changed in: totem (Ubuntu)
 Assignee: Rohit (rp-patil) => (unassigned)

** Changed in: totem (Ubuntu)
   Status: Confirmed => Incomplete

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

Title:
  double click opens totem twice and freezes

Status in totem package in Ubuntu:
  Incomplete

Bug description:
  Steps to reproduce:
  1. Open nautilus
  2. Double click on film
  3. Totem opens twice and windows are grayed and frozen

  ProblemType: Bug
  DistroRelease: Ubuntu 12.10
  Package: totem 3.4.3-0ubuntu2
  ProcVersionSignature: Ubuntu 3.5.0-13.14-generic 3.5.3
  Uname: Linux 3.5.0-13-generic x86_64
  ApportVersion: 2.5.1-0ubuntu4
  Architecture: amd64
  Date: Sun Sep  2 15:20:47 2012
  EcryptfsInUse: Yes
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Beta amd64 (20120328)
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=sk_SK.UTF-8
   SHELL=/bin/bash
  SourcePackage: totem
  UpgradeStatus: Upgraded to quantal on 2012-06-04 (89 days ago)

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

-- 
Mailing list: https://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 1825669] Re: gnome-control-center is crashing when trying to access the privacy tab

2019-04-23 Thread Edson T. Marques
The case has been settled.
I apologize for wasting your time with a vacillation on my part. I
inadvertently upgraded this package to a 3.32.n version available in an
unstable Debian repository.
I will try to be a tester more consistent with ubuntu.

Thank you!

Em ter, 23 de abr de 2019 às 06:21, Sebastien Bacher 
escreveu:

> Thank you for your bug report. As you pointed it out in your description
> though, it's a local configuration/installation issue, not an Ubuntu one
> (you seem to have installed a local gsettings-desktop-schemas missing a
> gsettings key which is taking precedence over the system version)
>
> ** Changed in: gnome-control-center (Ubuntu)
>Importance: Undecided => Low
>
> ** Changed in: gnome-control-center (Ubuntu)
>Status: New => Invalid
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1825669
>
> Title:
>   gnome-control-center is crashing when trying to access the privacy tab
>
> Status in gnome-control-center package in Ubuntu:
>   Invalid
>
> Bug description:
>   Hello,
>   I am informing that when I try to enter the Privacy settings of
> gnome-control-center, the program hangs and then crash.
>
>   After that, gnome-control-center no longer runs. When I try to run it
>   from the command line, it returns the following:
>
>   "
>   etm@etm:~$ gnome-control-center
>
>   (gnome-control-center: 14329): Gtk-WARNING **: 15: 12: 03.025: Theme
>   parsing error: gtk.css: 2281: 23: Expected a valid selector
>
>   (gnome-control-center: 14329): Gtk-WARNING **: 15: 12: 03.034: Theme
>   parsing error: gtk.css: 11535: 3: '/ *' in comment block
>
>   (gnome-control-center: 14329): Gtk-WARNING **: 15: 12: 03.034: Theme
>   parsing error: gtk.css: 11641: 2: '/ *' in comment block
>
>   (gnome-control-center: 14329): Clutter-WARNING **: 15: 12: 03.069:
>   Whoever translated default: LTR did so wrongly.
>
>   (gnome-control-center: 14329): GLib-GIO-ERROR **: 15: 12: 03.208:
> Settings schema 'org.gnome.desktop.screensaver' does not contain a key
> named 'ubuntu-lock-on-suspend'
>   Trace/breakpoint trap (recorded core image)
>   etm@etm:~$
>   "
>
>   To make it work again, delete the user's dconf folder:
>
>   etm@etm:~$ rm -R ~/.config/dconf/
>
>   Regards,
>
>   ProblemType: Bug
>   DistroRelease: Ubuntu 19.04
>   Package: gnome-control-center 1:3.32.1-1ubuntu4
>   ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6
>   Uname: Linux 5.0.0-13-generic x86_64
>   NonfreeKernelModules: nvidia_modeset nvidia
>   ApportVersion: 2.20.10-0ubuntu27
>   Architecture: amd64
>   CurrentDesktop: GNOME
>   Date: Sat Apr 20 15:02:08 2019
>   InstallationDate: Installed on 2019-01-30 (80 days ago)
>   InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190119)
>   SourcePackage: gnome-control-center
>   UpgradeStatus: No upgrade log present (probably fresh install)
>
> To manage notifications about this bug go to:
>
> https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1825669/+subscriptions
>

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

Title:
  gnome-control-center is crashing when trying to access the privacy tab

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

Bug description:
  Hello,
  I am informing that when I try to enter the Privacy settings of 
gnome-control-center, the program hangs and then crash.

  After that, gnome-control-center no longer runs. When I try to run it
  from the command line, it returns the following:

  "
  etm@etm:~$ gnome-control-center

  (gnome-control-center: 14329): Gtk-WARNING **: 15: 12: 03.025: Theme
  parsing error: gtk.css: 2281: 23: Expected a valid selector

  (gnome-control-center: 14329): Gtk-WARNING **: 15: 12: 03.034: Theme
  parsing error: gtk.css: 11535: 3: '/ *' in comment block

  (gnome-control-center: 14329): Gtk-WARNING **: 15: 12: 03.034: Theme
  parsing error: gtk.css: 11641: 2: '/ *' in comment block

  (gnome-control-center: 14329): Clutter-WARNING **: 15: 12: 03.069:
  Whoever translated default: LTR did so wrongly.

  (gnome-control-center: 14329): GLib-GIO-ERROR **: 15: 12: 03.208: Settings 
schema 'org.gnome.desktop.screensaver' does not contain a key named 
'ubuntu-lock-on-suspend'
  Trace/breakpoint trap (recorded core image)
  etm@etm:~$
  "

  To make it work again, delete the user's dconf folder:

  etm@etm:~$ rm -R ~/.config/dconf/

  Regards,

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: gnome-control-center 1:3.32.1-1ubuntu4
  ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6
  Uname: Linux 5.0.0-13-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Sat Apr 20 15:02:08 2019
  InstallationDate: Installed on 2019-01-30 (80 days ago)
  InstallationMedia: 

[Desktop-packages] [Bug 1163462] Re: totem-video-thumbnailer crashed with SIGABRT in raise()

2019-04-23 Thread Paul White
We are sorry that we do not always have the capacity to review all
reported bugs in a timely manner. You reported this bug some time ago
and there have been many changes in Ubuntu since that time.

Ubuntu 13.04 (raring) reached end-of-life on January 27, 2014.

Do you still see a problem related to the one that you reported in a
currently supported version of Ubuntu? Please let us know if you do
otherwise this report can be left to expire in approximately 60 days
time.

Thank you for helping make Ubuntu better.

Paul White
[Ubuntu Bug Squad]


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

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

Title:
  totem-video-thumbnailer crashed with SIGABRT in raise()

Status in totem package in Ubuntu:
  Incomplete

Bug description:
  sary@n1x:~$ lsb_release -rd; uname -a
  Description:  Ubuntu Raring Ringtail (development branch)
  Release:  13.04
  Linux n1x 3.8.0-16-generic #26-Ubuntu SMP Mon Apr 1 19:52:57 UTC 2013 x86_64 
x86_64 x86_64 GNU/Linux

  ProblemType: Crash
  DistroRelease: Ubuntu 13.04
  Package: totem 3.6.3-0ubuntu4
  ProcVersionSignature: Ubuntu 3.8.0-16.26-generic 3.8.5
  Uname: Linux 3.8.0-16-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.9.2-0ubuntu5
  Architecture: amd64
  Date: Tue Apr  2 19:44:21 2013
  ExecutablePath: /usr/bin/totem-video-thumbnailer
  InstallationDate: Installed on 2013-04-01 (1 days ago)
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 
(20120425)
  MarkForUpload: True
  ProcCmdline: /usr/bin/totem-video-thumbnailer -s 128 
file:///media/username/My%20Passport/WD%20Sync%20Data/User 
Name/s1m/Freedom/The%201ap/V%C2%B9%C2%B7%C2%B2/The.Notebook.2004.1080p.Bluray.x264.anoXmous/The.Notebook.2004.1080p.Bluray.x264.anoXmous.mov
 /tmp/.gnome_desktop_thumbnail.G3WYUW
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  Signal: 6
  SourcePackage: totem
  StacktraceTop:
   raise () from /lib/x86_64-linux-gnu/libc.so.6
   abort () from /lib/x86_64-linux-gnu/libc.so.6
   g_assertion_message () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_assertion_message_expr () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
  Title: totem-video-thumbnailer crashed with SIGABRT in raise()
  UpgradeStatus: Upgraded to raring on 2013-04-01 (1 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

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

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


[Desktop-packages] [Bug 1084869] Re: totem-video-thumbnailer hangs and will not generate thumbnails in nautilus

2019-04-23 Thread Paul White
Closing as fixed due to comment #5 made by reporter.

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

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

Title:
  totem-video-thumbnailer hangs and will not generate thumbnails in
  nautilus

Status in totem package in Ubuntu:
  Fix Released

Bug description:
  The process will run for a while and make thumbs, then it will will
  randomly hang and all thumbnail activity will stop. The proccess never
  unfreezes. Executing nautilus -q will reset everything and it will
  begin working for a few minutes before hanging again. Seems to only
  happen on remote shares. Was never a problem on 12.04. Booting 12.04
  will generate thumbnails for the same video files.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.10
  Package: totem 3.4.3-0ubuntu5
  ProcVersionSignature: Ubuntu 3.5.0-18.29-generic 3.5.7
  Uname: Linux 3.5.0-18-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.6.1-0ubuntu6
  Architecture: amd64
  Date: Thu Nov 29 21:58:03 2012
  ExecutablePath: /usr/bin/totem-video-thumbnailer
  InstallationDate: Installed on 2012-04-07 (236 days ago)
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Beta amd64 (20120328)
  MarkForUpload: True
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: totem
  UpgradeStatus: Upgraded to quantal on 2012-11-27 (2 days ago)

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

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


[Desktop-packages] [Bug 1168075] Re: totem crashed with signal 5 in cogl_display_setup()

2019-04-23 Thread Paul White
We are sorry that we do not always have the capacity to review all
reported bugs in a timely manner. You reported this bug some time ago
and there have been many changes in Ubuntu since that time.

Ubuntu 13.04 (raring) reached end-of-life on January 27, 2014.

Do you still see a problem related to the one that you reported in a
currently supported version of Ubuntu? Please let us know if you do
otherwise this report can be left to expire in approximately 60 days
time.

Thank you for helping make Ubuntu better.

Paul White
[Ubuntu Bug Squad]


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

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

Title:
  totem crashed with signal 5 in cogl_display_setup()

Status in totem package in Ubuntu:
  Incomplete

Bug description:
  Totem is not at all working on my system. It simply crashes out. VLC
  is fine. When I tried to run from terminal it gave following output :-

  manish@SR1931IL:~$ totem

  (totem:4676): Gdk-ERROR **: The program 'totem' received an X Window System 
error.
  This probably reflects a bug in the program.
  The error was 'GLXBadContext'.
(Details: serial 159 error_code 169 request_code 153 minor_code 6)
(Note to programmers: normally, X errors are reported asynchronously;
 that is, you will receive the error a while after causing it.
 To debug your program, run it with the GDK_SYNCHRONIZE environment
 variable to change this behavior. You can then get a meaningful
 backtrace from your debugger if you break on the gdk_x_error() function.)
  Trace/breakpoint trap (core dumped)

  Extra info :-

  1) manish@SR1931IL:~$ lsb_release -rd
  Description:  Ubuntu Raring Ringtail (development branch)
  Release:  13.04
  2) manish@SR1931IL:~$ apt-cache policy totem
  totem:
Installed: 3.6.3-0ubuntu4
Candidate: 3.6.3-0ubuntu4
Version table:
   *** 3.6.3-0ubuntu4 0
  500 http://archive.ubuntu.com/ubuntu/ raring/main i386 Packages
  100 /var/lib/dpkg/status

  ProblemType: Crash
  DistroRelease: Ubuntu 13.04
  Package: totem 3.6.3-0ubuntu4
  ProcVersionSignature: Ubuntu 3.8.0-17.27-generic 3.8.6
  Uname: Linux 3.8.0-17-generic i686
  ApportVersion: 2.9.2-0ubuntu5
  Architecture: i386
  Date: Thu Apr 11 23:11:08 2013
  ExecutablePath: /usr/bin/totem
  InstallationDate: Installed on 2013-03-15 (26 days ago)
  InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release i386 (20121017.2)
  MarkForUpload: True
  ProcCmdline: totem
  ProcEnviron:
   LANGUAGE=en_IN:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_IN
   SHELL=/bin/bash
  Signal: 5
  SourcePackage: totem
  StacktraceTop:
   ?? () from /usr/lib/i386-linux-gnu/mesa/libGL.so.1
   ?? () from /usr/lib/i386-linux-gnu/mesa/libGL.so.1
   ?? () from /usr/lib/i386-linux-gnu/libcogl.so.12
   cogl_display_setup () from /usr/lib/i386-linux-gnu/libcogl.so.12
   cogl_renderer_check_onscreen_template () from 
/usr/lib/i386-linux-gnu/libcogl.so.12
  Title: totem crashed with signal 5 in cogl_display_setup()
  UpgradeStatus: Upgraded to raring on 2013-03-31 (10 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

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

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


[Desktop-packages] [Bug 1179194] Re: [Lenovo G580, Conexant CX20590, Speaker, Internal] No sound at all

2019-04-23 Thread Paul White
We are sorry that we do not always have the capacity to review all
reported bugs in a timely manner. You reported this bug some time ago
and there have been many changes in Ubuntu since that time.

Ubuntu 13.04 (raring) reached end-of-life on January 27, 2014.

Do you still see a problem related to the one that you reported in a
currently supported version of Ubuntu? Please let us know if you do
otherwise this report can be left to expire in approximately 60 days
time.

Thank you for helping make Ubuntu better.

Paul White
[Ubuntu Bug Squad]


** Changed in: gstreamer1.0 (Ubuntu)
   Status: New => Incomplete

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

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

Title:
  [Lenovo G580, Conexant CX20590, Speaker, Internal] No sound at all

Status in gstreamer1.0 package in Ubuntu:
  Incomplete
Status in totem package in Ubuntu:
  Incomplete

Bug description:
  Totem player crashed after trying to unmute it.

  Details are;
  Description:  Ubuntu 13.04
  Release:  13.04

  # apt-cache policy totem
  totem:
Installed: 3.6.3-0ubuntu6
Candidate: 3.6.3-0ubuntu6
Version table:
   *** 3.6.3-0ubuntu6 0
  500 http://ke.archive.ubuntu.com/ubuntu/ raring/main amd64 Packages
  100 /var/lib/dpkg/status

  I expected it to unmute and continue playing ;)

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu4
  ProcVersionSignature: Ubuntu 3.8.0-19.30-generic 3.8.8
  Uname: Linux 3.8.0-19-generic x86_64
  ApportVersion: 2.9.2-0ubuntu8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  mbadi  2863 F pulseaudio
  Date: Sun May 12 14:56:52 2013
  InstallationDate: Installed on 2013-04-25 (16 days ago)
  InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5)
  MarkForUpload: True
  PackageArchitecture: all
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  mbadi  2863 F pulseaudio
  Symptom_Jack: Speaker, Internal
  Symptom_PulsePlaybackTest: PulseAudio playback test successful
  Symptom_Type: No sound at all
  Title: [Lenovo G580, Conexant CX20590, Speaker, Internal] No sound at all
  UpgradeStatus: Upgraded to raring on 2013-04-26 (15 days ago)
  dmi.bios.date: 06/06/2012
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 5ECN33WW(V2.03)
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: Product Name
  dmi.board.vendor: LENOVO
  dmi.board.version: Mainboard version
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo G580
  dmi.modalias: 
dmi:bvnLENOVO:bvr5ECN33WW(V2.03):bd06/06/2012:svnLENOVO:pnLenovoG580:pvrLenovoG580:rvnLENOVO:rnProductName:rvrMainboardversion:cvnLENOVO:ct10:cvrLenovoG580:
  dmi.product.name: Lenovo G580
  dmi.product.version: Lenovo G580
  dmi.sys.vendor: LENOVO

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

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


[Desktop-packages] [Bug 1824257] Re: AUCTeX/Evince: server does not start, poor direct search, inverse search does not work

2019-04-23 Thread Cédric M . Campos
SOLVED. Some non-official package installed Evince through flatpak,
which did not communicate properly with AUCTeX through D-Bus.

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

Title:
  AUCTeX/Evince: server does not start, poor direct search, inverse
  search does not work

Status in auctex package in Ubuntu:
  New

Bug description:
  Ubuntu release: Ubuntu 18.04.2 LTS (fully updated as per today)
  Package version: AUCTeX 11.91 (Emacs 25.2)

  *** Summary ***
  1) Evince server does not start, so each "C-c C-v" issued opens a new Evince 
instance, capturing the keyboard focus and bloating the screen.
  2) Direct search works partially, it merely searches for the page and not the 
specific line.
  3) Inverse search simply does not work.

  *** Note ***
  I have attached a basic configuration to start a server and activate 
direct/inverse search according to this: 
https://www.gnu.org/software/auctex/manual/auctex/I_002fO-Correlation.html

  *** What is to be expected ***
  1) Open a .tex file with Emacs/AUCTeX.
  2) Compile (C-c C-c).
  3) View pdf output (C-c C-v).
  >> An Evince server for that file is started.
  >> Evince opens the pdf file.
  >> Focus is still on Emacs instance.
  3) Move to some line (in Emacs).
  4) View pdf output (C-c C-v).
  >> No new Evince instance is opened for that file.
  >> The current Evince instance moves to the specific line corresponding to 
the cursor position in Emacs.
  >> Focus is still on Emacs instance.
  5) On Evince "control+left click" some line.
  >> Emacs moves to the specific line corresponding to the pointed line in 
Evince.
  >> Emacs instance captures the focus.

  *** What happens ***
  1) Open a .tex file with Emacs/AUCTeX.
  2) Compile (C-c C-c).
  3) View pdf output (C-c C-v).
  >> No Evince server is started.
  >> Evince opens the pdf file.
  >> Focus is captured by Evince.
  3) Move to some line (in Emacs).
  4) View pdf output (C-c C-v).
  >> A new Evince instance is opened for that file.
  >> The new Evince instance moves to the page (not the line) corresponding to 
the cursor position in Emacs.
  >> Focus is captured by the new Evince instance.
  5) On Evince "control+left click" some line.
  >> Nothing happens and Winter Is Coming.

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

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


[Desktop-packages] [Bug 1826043] [NEW] Events spanning multiple days are displayed on the wrong day in week view

2019-04-23 Thread Riccardo Maffei
Public bug reported:

In gnome-calendar week view, events spanning multiple days are shown in
the wrong day. Also, the event is shown in only one day (ending at
midnight).

Steps to reproduce:
 1. Add an event starting on Monday at 21:00 and ending on Tuesday at 06:00.
 2. Switch to week view.

Expected behavior:
The event should be shown both on Monday and on Tuesday. In particular should 
be 21:00->midnight on Monday and midnight->06:00 on Tuesday.

Actual behavior:
 1. The event is shown on the wrong day (Wednesday).
 2. The event is shown only in one day (only the part 21:00->midnight is shown)

Package version: 3.28.2-0ubuntu0.18.04.1
OS version: Ubuntu 18.04.2 LTS

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

** Description changed:

- In gnome-calendar week view events spanning multiple days are shown in
+ In gnome-calendar week view, events spanning multiple days are shown in
  the wrong day. Also, the event is shown in only one day (ending at
  midnight).
  
  Steps to reproduce:
-  1. Add an event starting on Monday at 21:00 and ending on Tuesday at 06:00.
-  2. Switch to week view.
+  1. Add an event starting on Monday at 21:00 and ending on Tuesday at 06:00.
+  2. Switch to week view.
  
  Expected behavior:
  The event should be shown both on Monday and on Tuesday. In particular should 
be 21:00->midnight on Monday and midnight->06:00 on Tuesday.
  
  Actual behavior:
-  1. The event is shown on the wrong day (Wednesday).
-  2. The event is shown only in one day (only the part 21:00->midnight is 
shown)
+  1. The event is shown on the wrong day (Wednesday).
+  2. The event is shown only in one day (only the part 21:00->midnight is 
shown)
  
  Package version: 3.28.2-0ubuntu0.18.04.1
  OS version: Ubuntu 18.04.2 LTS

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

Title:
  Events spanning multiple days are displayed on the wrong day in week
  view

Status in gnome-calendar package in Ubuntu:
  New

Bug description:
  In gnome-calendar week view, events spanning multiple days are shown
  in the wrong day. Also, the event is shown in only one day (ending at
  midnight).

  Steps to reproduce:
   1. Add an event starting on Monday at 21:00 and ending on Tuesday at 06:00.
   2. Switch to week view.

  Expected behavior:
  The event should be shown both on Monday and on Tuesday. In particular should 
be 21:00->midnight on Monday and midnight->06:00 on Tuesday.

  Actual behavior:
   1. The event is shown on the wrong day (Wednesday).
   2. The event is shown only in one day (only the part 21:00->midnight is 
shown)

  Package version: 3.28.2-0ubuntu0.18.04.1
  OS version: Ubuntu 18.04.2 LTS

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

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


[Desktop-packages] [Bug 1811900] Re: SRU 3.28 latest git to bionic

2019-04-23 Thread Mantas Kriaučiūnas
Can you speed up publishing fixed gnome-shell to bionic-updates

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

Title:
  SRU 3.28 latest git to bionic

Status in gnome-shell package in Ubuntu:
  Invalid
Status in mutter package in Ubuntu:
  Invalid
Status in gnome-shell source package in Bionic:
  Fix Committed
Status in mutter source package in Bionic:
  Fix Committed
Status in gnome-shell source package in Disco:
  Invalid
Status in mutter source package in Disco:
  Invalid

Bug description:
  [ Description ]

  3.28 gnome git branch has various upstream approved fixes for many
  months now, but no release has been done yet, thus we're releasing a
  git snapshot of the latest approved fixes.

  [ QA ]

  Run Ubuntu session, expect the shell to work normally with various
  setups

  https://wiki.ubuntu.com/StableReleaseUpdates/GNOME

  [ Regresison potential ]

  Many patches we were including already have been included in upstream
  git now, various optimizations to clutter actors could cause drawing
  issues.

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

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


[Desktop-packages] [Bug 1070606] Re: executing command totem --debug from terminal

2019-04-23 Thread Paul White
Ubuntu 12.04 (precise) reached end-of-life on April 28, 2017.
Reverting "In Progress" to close bug.


** Changed in: totem (Ubuntu)
   Status: In Progress => Invalid

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

Title:
  executing command totem --debug from terminal

Status in totem package in Ubuntu:
  Invalid

Bug description:
  when checking for issues executing the totem --debug command this
  appears:

  (totem:26178): GLib-GObject-CRITICAL **: Read/writable property
  'object' on class 'ZeitgeistDpPlugin' has type 'TotemObject' which is
  not exactly equal to the type 'GObject' of the property on the
  interface 'PeasActivatable' < -- this last code is funny peas
  activatablewhere did this come from ... while program loads some
  times therws a forced quit and other times it freezes when i want to
  skip frames on video or i try to stop playback

  Description:  Ubuntu 12.04.1 LTS
  Release:  12.04
  totem:
    Installed: 3.0.1-0ubuntu21.1
    Candidate: 3.0.1-0ubuntu21.1
    Version table:
   *** 3.0.1-0ubuntu21.1 0
  500 http://nz.archive.ubuntu.com/ubuntu/ precise-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   3.0.1-0ubuntu21 0
  500 http://nz.archive.ubuntu.com/ubuntu/ precise/main amd64 Packages

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: totem 3.0.1-0ubuntu21.1
  ProcVersionSignature: Ubuntu 3.2.0-32.51-generic 3.2.30
  Uname: Linux 3.2.0-32-generic x86_64
  ApportVersion: 2.0.1-0ubuntu13
  Architecture: amd64
  CheckboxSubmission: b10bf83492d3467dca85252ba91df3e2
  CheckboxSystem: daed2f3d6643b4a84b4520a2427f8c2b
  Date: Wed Oct 24 12:52:57 2012
  InstallationMedia: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release amd64 
(20120823.1)
  ProcEnviron:
   LANGUAGE=en_NZ:en
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_NZ.UTF-8
   SHELL=/bin/bash
  SourcePackage: totem
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 985451] Re: totem flickers between cover art and visualisation

2019-04-23 Thread Paul White
We are sorry that we do not always have the capacity to review all
reported bugs in a timely manner. You reported this bug some time ago
and there have been many changes in Ubuntu since that time.

Ubuntu 12.04 (precise) reached end-of-life on April 28, 2017.

Do you still see a problem related to the one that you reported in a
currently supported version of Ubuntu? Please let us know if you do
otherwise this report can be left to expire in approximately 60 days
time.

Thank you for helping make Ubuntu better.

Paul White
[Ubuntu Bug Squad]

** Changed in: totem (Ubuntu)
   Status: Confirmed => Incomplete

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

Title:
  totem flickers between cover art and visualisation

Status in totem package in Ubuntu:
  Incomplete

Bug description:
  When playing an MP3 that has embedded cover art, the visualisation
  appears. However, once or twice a second (roughly) the cover art
  flicks up for about a frame.

  This doesn't detract from the playing, it's just quite distracting.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: totem 3.0.1-0ubuntu21
  ProcVersionSignature: Ubuntu 3.2.0-23.36-generic 3.2.14
  Uname: Linux 3.2.0-23-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.0.1-0ubuntu5
  Architecture: amd64
  Date: Thu Apr 19 19:44:15 2012
  InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007)
  SourcePackage: totem
  UpgradeStatus: Upgraded to precise on 2012-03-16 (33 days ago)

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

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


[Desktop-packages] [Bug 1045199] Re: Nautilus freezes when opening file properties of a .mp4 file

2019-04-23 Thread Paul White
We are sorry that we do not always have the capacity to review all
reported bugs in a timely manner. You reported this bug some time ago
and there have been many changes in Ubuntu since that time.

Ubuntu 12.04 (precise) reached end-of-life on April 28, 2017.

Do you still see a problem related to the one that you reported in a
currently supported version of Ubuntu? Please let us know if you do
otherwise this report can be left to expire in approximately 60 days
time.

Thank you for helping make Ubuntu better.

Paul White
[Ubuntu Bug Squad]

** Changed in: totem (Ubuntu)
   Status: Confirmed => Incomplete

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

Title:
  Nautilus freezes when opening file properties of a .mp4 file

Status in totem package in Ubuntu:
  Incomplete

Bug description:
  Steps to reproduce:

   - Find a .mp4 file
   - Right-click, properties
   - Nautilus freezes
   - Nautilus displays the properties dialog after long wait (~10 mins)

  This may be a duplicate of #987274

  I'll try to get a backtrace of the bug later if it reoccurs, but looks 
  like the dialog works now.

  
  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: nautilus 1:3.4.2-0ubuntu4
  ProcVersionSignature: Ubuntu 3.2.0-29.46-generic-pae 3.2.24
  Uname: Linux 3.2.0-29-generic-pae i686
  NonfreeKernelModules: nvidia
  ApportVersion: 2.0.1-0ubuntu12
  Architecture: i386
  CheckboxSubmission: 5411b7083f2413511daec522a712c016
  CheckboxSystem: b845c366ea09c60efa3a45c1b5b21525
  Date: Mon Sep  3 10:33:43 2012
  EcryptfsInUse: Yes
  ExecutablePath: /usr/bin/nautilus
  GsettingsChanges:
   org.gnome.nautilus.window-state geometry '1141x678+53+75'
   org.gnome.nautilus.window-state sidebar-width 301
  InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release i386 (20110427.1)
  ProcEnviron:
   PATH=(custom, user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: nautilus
  UpgradeStatus: Upgraded to precise on 2012-05-03 (122 days ago)

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

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


[Desktop-packages] [Bug 1210235] Re: Totem crashes after finishing all the list of reproduction of mp3 files

2019-04-23 Thread Paul White
** Changed in: totem (Ubuntu)
   Status: New => Incomplete

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

Title:
  Totem crashes after finishing all the list of reproduction of mp3
  files

Status in totem package in Ubuntu:
  Incomplete

Bug description:
  Hello. Totem crashes after finishing all the list of reproduction of
  mp3 files. The problem is when there are some files.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: totem 3.0.1-0ubuntu21.1
  ProcVersionSignature: Ubuntu 3.5.0-37.58~precise1-generic 3.5.7.16
  Uname: Linux 3.5.0-37-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.0.1-0ubuntu17.3
  Architecture: amd64
  Date: Thu Aug  8 21:48:59 2013
  ExecutablePath: /usr/bin/totem
  InstallationMedia: Ubuntu 12.04.2 LTS "Precise Pangolin" - Release amd64 
(20130213)
  MarkForUpload: True
  ProcEnviron:
   PATH=(custom, no user)
   LANG=ru_RU.UTF-8
   SHELL=/bin/bash
  SourcePackage: totem
  UpgradeStatus: No upgrade log present (probably fresh install)
  XsessionErrors:
   (compiz:1558): GConf-CRITICAL **: gconf_client_add_dir: assertion 
`gconf_valid_key (dirname, NULL)' failed
   (firefox:1845): LIBDBUSMENU-GTK-CRITICAL **: 
dbusmenu_menuitem_property_set_shortcut: assertion `gtk_accelerator_valid(key, 
modifier)' failed
   (totem:3281): GLib-GObject-CRITICAL **: Read/writable property 'object' on 
class 'ZeitgeistDpPlugin' has type 'TotemObject' which is not exactly equal to 
the type 'GObject' of the property on the interface 'PeasActivatable'
   (totem:3488): GLib-GObject-CRITICAL **: Read/writable property 'object' on 
class 'ZeitgeistDpPlugin' has type 'TotemObject' which is not exactly equal to 
the type 'GObject' of the property on the interface 'PeasActivatable'
   (totem:3615): GLib-GObject-CRITICAL **: Read/writable property 'object' on 
class 'ZeitgeistDpPlugin' has type 'TotemObject' which is not exactly equal to 
the type 'GObject' of the property on the interface 'PeasActivatable'

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

-- 
Mailing list: https://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   3   >