[Desktop-packages] [Bug 1822839] Re: LibreOffice doesn't detect JVM because of unexpected java.vendor property value

2019-04-04 Thread Launchpad Bug Tracker
This bug was fixed in the package libreoffice - 1:6.2.2-0ubuntu2

---
libreoffice (1:6.2.2-0ubuntu2) disco; urgency=medium

  [ Rene Engelhard ]
  * debian/patches/java.vendor-Debian.diff: make jvmfwk recognize "Debian"
as java.vendor as that's what is set in openjdk 11 >= 11.0.3+4-2
- see #926009 (closes: #926318)

  [ Olivier Tilloy ]
  * debian/patches/java.vendor-Ubuntu.patch: also make jvmfwk recognize
"Ubuntu" as java.vendor (LP: #1822839)

 -- Olivier Tilloy   Thu, 04 Apr 2019
11:23:38 +0200

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

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

Title:
  LibreOffice doesn't detect JVM because of unexpected java.vendor
  property value

Status in LibreOffice:
  Confirmed
Status in libreoffice package in Ubuntu:
  Fix Released
Status in openjdk-lts package in Ubuntu:
  New
Status in libreoffice package in Debian:
  New

Bug description:
  libreoffice autopkgtests are failing on disco with openjdk
  11.0.3+4-2ubuntu1.

  The likely culprit is that change:

  +openjdk-lts (11.0.3+4-2ubuntu1) disco; urgency=medium
  +
  +  * Sync packages with 11.0.3+4-2:
  +[ Matthias Klose ]
  +- Configure with vendor flags.

  Indeed with version 11.0.3+4-1ubuntu1:

  $ java -XshowSettings -version 2>&1 | grep "java.vendor "
  java.vendor = Oracle Corporation

  And with version 11.0.3+4-2ubuntu1:

  $ java -XshowSettings -version 2>&1 | grep "java.vendor "
  java.vendor = Private Build

  Looking at the code in Libreoffice that looks for a JVM, it validates
  the vendor against a hardcoded list of known vendors:
  
https://cgit.freedesktop.org/libreoffice/core/tree/jvmfwk/plugins/sunmajor/pluginlib/vendorlist.cxx?h=libreoffice-6-2#n33

  Not sure what the purpose of that upstream code is, but this means the
  new openjdk-11 build in Ubuntu breaks it.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: openjdk-11-jre-headless 11.0.3+4-2ubuntu1
  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-0ubuntu23
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Apr  2 17:06:25 2019
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2016-07-02 (1003 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  SourcePackage: openjdk-lts
  UpgradeStatus: Upgraded to disco on 2019-03-16 (16 days ago)

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

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


[Desktop-packages] [Bug 1225423] Re: Firefox in Ubuntu Unity menu lacks a localised String (NL)

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

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

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

Title:
  Firefox in Ubuntu Unity menu lacks a localised String (NL)

Status in firefox package in Ubuntu:
  Expired

Bug description:
  The firefox.desktop file doesn't contain a localised string for
  opening a new private window for the Dutch language. It defaults to
  the English string, while the others are in Dutch.


  Suggestion:

  Add

  Name[nl]=Nieuw privévenster openen

  to

  [Desktop Action NewPrivateWindow]

  
  Ubuntu version: Release:  13.04
  Firefox version: 23.0+build2-0ubuntu0.13.04.1

  Expectation: All strings localised
  What happened instead: Found an English string between Dutch strings

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

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


[Desktop-packages] [Bug 1314641] Re: Options Number of elements & thumbnails set for local folders but are active for remote folders as well

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

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

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

Title:
  Options Number of elements & thumbnails set for local folders but are
  active for remote folders as well

Status in nautilus package in Ubuntu:
  Expired

Bug description:
  On Debian wheezy - Nautilus 3.4.2
  On Ubuntu 14.04 - Nautilus 3.10.1
  

  Both the options "Show Thumbnails" & "Show number of elements" are set
  to "Local folders only".

  What you expected to happen
  -
  When I mount a davfs or cifs remote folder, only shown folder names without 
the number of elements inside the folder and for the images, their file names 
with generic thumbnails.

  What happened instead
  ---
  When I mount a davfs or cifs remote folder, thumbnails are created for images 
and pdf and the number of elements is showed.

  For folders with lots of images, pdf or dir & subdirs, it takes really
  a long time to show its content and it consumes lots of unnecessary
  process on the server.

  If I set these 2 options to never, the content of the remote folders
  are much much quicker (like 3 sec instead of 30 sec)

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

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


[Desktop-packages] [Bug 182187] Re: user set middlemouse.contentLoadURL reset to Ubuntu default on fresh install

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

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

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

Title:
  user set middlemouse.contentLoadURL reset to Ubuntu default on fresh
  install

Status in firefox package in Ubuntu:
  Expired

Bug description:
  Binary package hint: firefox

  On two separate installs of Hardy where /home is preserved, I've had
  the preference middlemouse.contentLoadURL reset to Ubuntu's default.
  Fortunately, after I toggle it back to true, it stays where I set it.

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

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


[Desktop-packages] [Bug 452655] Re: Mozilla Thunderbird Presents Gap in Subject - Thunderbird does not compact /t into a space

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

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

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

Title:
  Mozilla Thunderbird Presents Gap in Subject - Thunderbird does not
  compact /t into a space

Status in dovecot package in Ubuntu:
  Invalid
Status in thunderbird package in Ubuntu:
  Expired

Bug description:
  Binary package hint: thunderbird

  Mozilla Thunderbird Presents Gap in Subject. Thunderbird does not
  compact /t into a space.

  This has always been an issue but recently I have compared the gap in
  email subject lines on one of my imap servers (Postfix -> Dovecot ->
  Thunderbird) to the lack of gap in email subject lines on
  imap.gmail.com, and I think there is something wrong with the mail
  server which adds spaces after a certain number of words/chars...

  When I contacted my system administrator with this concerned his response was 
the following:
  ==
  This is not a bug in the IMAP server.  It's possibly a bug in Thunderbird.  
Taking a random email from your screenshot, the original header looks like this 
on disk.

  | Subject: [Bug 179042] Re: Videos tear and "blink" when enabling
  compiz [AMD Feature #7647] [EPR#257833]

  (Which is 'AMD\n\tFeature')

  Other MUAs (including at least Mutt and Gnus) compact the \t down to a single 
space.  I don't know RFC 2821 well enough to know off the top of my head if 
Thunderbird's behaviour is unequivocally a bug, but it's certainly unintuitive 
and I'd recommend you file a bug against it in Ubuntu.
  ==

  The server which gives me this problem runs dovecot-imapd
  1:1.0.10-1ubuntu5.2 on Ubuntu 8.04 (Hardy Herron). My client is
  Thunderbird on 9.10 (details below) but this issue has been happening
  since ~2007 (that's when I noticed it) as far as I remember.

  ProblemType: Bug
  Architecture: i386
  CheckboxSubmission: 37b6e744530b0903e91adb26018991f0
  CheckboxSystem: d00f84de8a555815fa1c4660280da308
  Date: Thu Oct 15 19:36:46 2009
  DistroRelease: Ubuntu 9.10
  NonfreeKernelModules: wl
  Package: thunderbird 2.0.0.23+build1+nobinonly-0ubuntu1
  ProcEnviron:
   LANGUAGE=en_CA.UTF-8
   PATH=(custom, user)
   LANG=en_CA.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 2.6.31-12.41-generic
  SourcePackage: thunderbird
  Uname: Linux 2.6.31-12-generic i686

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

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


[Desktop-packages] [Bug 272457] Re: By default, firefox won't open some txt files

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

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

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

Title:
  By default, firefox won't open some txt files

Status in firefox package in Ubuntu:
  Expired

Bug description:
  Binary package hint: firefox-3.0

  Intrepid alpha6 fully updated.

  By default, firefox won't open some txt files.
  You can reproduce it:
  1- Go to http://ubuntuforums.org/showpost.php?p=5469447=5
  2- Click on the bottom attached file "xorg.conf"
  3- Choose open (note that you'll open it with a text editor by default)

  Firefox says that the default application to view this file doesn't exist.
  The file is saved to /tmp.

  ProblemType: Bug
  Architecture: i386
  DistroRelease: Ubuntu 8.10
  NonfreeKernelModules: wl
  Package: firefox 3.0.2+build3+nobinonly-0ubuntu2
  PackageArchitecture: all
  ProcEnviron:
   SHELL=/bin/bash
   PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
   LANG=es_ES.UTF-8
  SourcePackage: firefox-3.0
  Uname: Linux 2.6.27-3-generic i686

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

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


[Desktop-packages] [Bug 1383355] Re: mouse right click responsiveness only after button being held down for 5-10 seconds

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

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

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

Title:
  mouse right click responsiveness only after button being held down for
  5-10 seconds

Status in nautilus package in Ubuntu:
  Expired

Bug description:
  My Ubuntu terminal session returns command lsb_release -a as:
  root@BobbyB-LinuxLaptop:/home/bobbyb# lsb_release -a 
  LSB Version:  
core-2.0-ia32:core-2.0-noarch:core-3.0-ia32:core-3.0-noarch:core-3.1-ia32:core-3.1-noarch:core-3.2-ia32:core-3.2-noarch:core-4.0-ia32:core-4.0-noarch
 
  Distributor ID:   Ubuntu 
  Description:  Ubuntu 12.04.5 LTS 
  Release:  12.04 
  Codename: precise 

  I have the unity-2d-shell running and the attached .png image file is
  from my desktop_window Nautilus.  The only other 'application" that I
  have started is "Screenshot" to take the .png image to reference what
  I am reporting as the issue.

  As a reference the .png image I took using the application Screenshot
  after hoklding the right click mouse button down for about 10 seconds
  more or less (Screenshot 2014-10-20 09:49:07
  TenSecondHoldMouseRightClickButton.png).

  The problem is that if I right click the mouse while the pointer is
  over anything on  my desktop (e.g., a file, a folder, an image, etc
  etc etc) and this right click is just a simple one time single right
  mouse button click done just once, the drop down contextual  menu
  (such as shown in the .png image) does not appear/drop down.  I have
  to hold the right click mouse button down for an extended period of
  time (sometimes it is a few seconds, sometimes 10seconds, sometimes a
  bit longer) and then the drop down menu appears.  This is the
  problemfailure to respond to a single simple right mouse click
  without my having to hold the button down for an extended period of
  time.

  This same type of thing happens when I am in my browser (e.g.,
  Chromium or Firefox.  I do a GOOGLE Search for example and the
  response comes back showing a list of web page possibilities and I put
  the mouse pointer over the link I want to open and right click the
  mouse once, nothing happens.  I right click the mouse once again (or
  once again or again or again etc etc etc) waiting seconds between any
  subsequent right mouse button pressing and nothing happens.  If,
  however, I position the mouse pointer over the web page link and I
  right click the mouse and hold the right click button down for a few
  seconds (maybe as long as ten seconds sometimes more or less) then the
  web link is activated as I had initially expected that it should.
  This delay in responding to the right click is annoying and was not
  there a week ago  but is there consistently now.  How do I change the
  mouse responsiveness or better yet, why has it changed to behave like
  it does?

  I have had this problem many many months ago off and on and on
  different loads in 12.04LTS.  Not sure if it does or does not occur on
  any previous releases or in 13.10 or 14.04.  It would occur for weeks
  on end and then I would not see it again and mouse right click goes
  back to working 'normally'.  I cannot say I did anything to change the
  mouse right click behaviour.  But, now it is back again.  It seems to
  be elusive in when it will/may occur and I cannot say for certain that
  it is in relation to anything else I am doing or any other application
  I have activated or using or that it is related to any specific mouse
  activities or sequence of actions.  I have not changed/adjusted any
  parameters related to mouse responsiveness and know of nothing
  available that I may use to query mouse responsiveness or reset/change
  the mouse right click responsiveness.

  I am using and have more than always used a USB optical Microsoft 3
  button wheel mouse.  I am right handed.  I don't think the mouse
  type/manufacture or whether it is right or left handed is significant
  to the problem.  I get no logs or anything indicating that there is a
  problem with messaging or any problem with the system or the USB
  hardware or the mouse itself.

  I know that once it starts occurring then it happens all the time for
  a period of sometime then, magically, it seems to clear itself up
  reverting back to a one click mouse right click responding immediately
  as expected.  Sometimes it reverts back only after days/weeks of
  computer use.  I have restarted my system many times with nothing
  changing.  I have used different USB ports for the mouse and it still
  happens.  I have tried different types/makes/models/manufacturers of
  mouse(s) (mice??) and it happens.  It happened when I had 12.04:LTS
  Linux 3.2.0-67-generic or even with this latest updated kernel load
  that was downloaded/applied 

[Desktop-packages] [Bug 1366960] Re: Arabic interface files selection problem

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

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

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

Title:
  Arabic interface files selection problem

Status in nautilus package in Ubuntu:
  Expired

Bug description:
  When using arabic user interface (and probably any right to left
  language), files and folders are not selected in the expected order
  when navigating using the keyboard. They are still sorted correctly.

  For example, assume we have 11 files named from 1 to 11 in a certain
  directory sorted alphabetically. They are displayed correctly from
  right to left, top to bottom like this:

  4   3   2   1
  8   7   6   5
   11 10   9

  however, if I press "Home" button which should select the first file,
  file "4" is selected instead of 1. If I press "End" button, file 9 is
  selected instead of 11.

  Also when using arrow keys, I expect pressing "Left" while on file "4" 
changes to file "5". However, nothing happens as if file "4" is the first file 
and I am going backwards.
  When I press "Right" button while on file "1", I expect nothing to happen 
since I am in the first file and I am going backwards. However, file "8" is 
selected instead as if it is after file "1".
  Similarly, if I press "Right" while on file "5", file "11" is selected while 
I expect to select file "4" as it is located before file "5".

  Thank you very much
  Mohammad

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

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


[Desktop-packages] [Bug 1375527] Re: Modal Window Requires Password, Blocks Use of Password Management Program

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

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

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

Title:
  Modal Window Requires Password, Blocks Use of Password Management
  Program

Status in gnome-keyring package in Ubuntu:
  Expired

Bug description:
  I am a novice Linux user learning Ubuntu.  I just tried rebooting my
  system.  After reboot a modal window appeared on the desktop asking
  for authentication of my Gmail account.   I believe this came from the
  "online accounts" I configured to access my Google contacts.

  This window captures the keyboard and nothing can be done on the
  system until it has been dismissed.  I manage my passwords using an
  online password management system that is integrated with the web
  browser.  For me to get my passwords, I must be able to change focus,
  enter my master password, and copy-paste the long password to the
  dialog.  But none of this is possible while this dialog captures
  focus.

  Can you please change this Window and make it not modal to the entire
  desktop?

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: nautilus 1:3.10.1-0ubuntu13
  ProcVersionSignature: Ubuntu 3.16.0-14.20-generic 3.16.2
  Uname: Linux 3.16.0-14-generic x86_64
  ApportVersion: 2.14.7-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue Sep 30 09:26:21 2014
  ExecutablePath: /usr/bin/nautilus
  GsettingsChanges:
   
  ProcEnviron:
   LANGUAGE=en_HK:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_HK.UTF-8
   SHELL=/bin/bash
  SourcePackage: nautilus
  UpgradeStatus: Upgraded to utopic on 2014-09-12 (17 days ago)

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

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


[Desktop-packages] [Bug 1358645] Re: error while creating shortcut

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

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

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

Title:
  error while creating shortcut

Status in nautilus package in Ubuntu:
  Expired

Bug description:
  I can't create shortcut on the desktop and I cant create anything on
  the desktop

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: nautilus 1:3.10.1-0ubuntu9.3
  ProcVersionSignature: Ubuntu 3.13.0-34.60-generic 3.13.11.4
  Uname: Linux 3.13.0-34-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.3
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue Aug 19 10:42:14 2014
  ExecutablePath: /usr/bin/nautilus
  GsettingsChanges:
   
  InstallationDate: Installed on 2014-07-23 (26 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  ProcEnviron:
   LANGUAGE=tr
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=tr_TR.UTF-8
   SHELL=/bin/bash
  SourcePackage: nautilus
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1319155] Re: Changing combined size when selecting multiple folders

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

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

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

Title:
  Changing combined size when selecting multiple folders

Status in nautilus package in Ubuntu:
  Expired

Bug description:
  When selecting multiple folders with locations including japanese
  characters and opening the properties dialogue, combined size and
  number of files included fluctuate.

  For example, the first second it shows "600 items, totalling 7 GB",
  the next shows "520 items, totalling 6.2 GB", and the next after that
  is different as well.

  With the variety of folders I've tested, it only occurs when the
  selection includes japanese, chinese, or any other non-english
  characters.

  Update: The nemo manager does not have this issue.

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

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


[Desktop-packages] [Bug 1341222] Re: Can't mount USB drives when using xrdp

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

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

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

Title:
  Can't mount USB drives when using xrdp

Status in nautilus package in Ubuntu:
  Expired

Bug description:
  USB drives and partitions on my USB hard drives show up in nautilus
  and I can mount them when sitting at the console but when using xrdp
  to remotely operate the machine I cannot mount or unmount the drives
  by clicking on them. I get a "not authorized" message. In previous
  versions I was able to do this.

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

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


[Desktop-packages] [Bug 1397737] Re: nautilus page down mouse click moves to the click - not to the next page

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

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

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

Title:
  nautilus page down mouse click moves to the click - not to the next
  page

Status in nautilus package in Ubuntu:
  Expired

Bug description:
  Show any folder (in a details list) that has many files in it. Using
  scrollbars (not the hidden type) and clicking within the region
  between the scroll bar indicator and the up or down scroll icons, and
  the listing should advance or go back one page (page is defined as
  number of files/line items displayed). Actual operation moves the
  scroll indicator to where the mouse was clicked, which can be more or
  less than a page size. This operation is at odds with normal UI
  conventions. Thunar works correctly.

  ubuntu release 14.04

  nautilus:
Installed: 1:3.10.1-0ubuntu9.3
Candidate: 1:3.10.1-0ubuntu9.4
Version table:
   1:3.10.1-0ubuntu9.4 0
  500 http://us.archive.ubuntu.com/ubuntu/ trusty-updates/main amd64 
Packages
   *** 1:3.10.1-0ubuntu9.3 0
  100 /var/lib/dpkg/status
   1:3.10.1-0ubuntu8 0
  500 http://us.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: nautilus 1:3.10.1-0ubuntu9.3
  ProcVersionSignature: Ubuntu 3.13.0-40.69-generic 3.13.11.10
  Uname: Linux 3.13.0-40-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.5
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sun Nov 30 13:53:22 2014
  InstallationDate: Installed on 2014-06-01 (182 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64+mac 
(20140417)
  SourcePackage: nautilus
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1356616] Re: unsuccessful password attempts for decrypting sdcard eventually opens mutiple windows when successful

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

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

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

Title:
  unsuccessful password attempts for decrypting sdcard eventually opens
  mutiple windows when successful

Status in nautilus package in Ubuntu:
  Expired

Bug description:
  Description:  Ubuntu 14.04.1 LTS
  Release:  14.04

  nautilus:
Installed: 1:3.10.1-0ubuntu9.2
Candidate: 1:3.10.1-0ubuntu9.3
Version table:
   1:3.10.1-0ubuntu9.3 0
  500 http://mirror.it.ubc.ca/ubuntu/ trusty-updates/main amd64 Packages
   *** 1:3.10.1-0ubuntu9.2 0
  100 /var/lib/dpkg/status
   1:3.10.1-0ubuntu8 0
  500 http://mirror.it.ubc.ca/ubuntu/ trusty/main amd64 Packages

  ---

  I have an encrypted SD card. When mounted, I am prompted for the
  password. If the password is entered correctly, then nautilus will
  open a window displaying the SD card contents.

  If I make a mistake typing the password then the SD is not decrypted
  and no window opens. This is normal. However, when I do successfully
  enter the password, nautilus opens a window for each unsuccessful
  attempt on top of the correct one.

  e.g. Insert SD card:
  - Prompt for password: enter wrong password (1)
  -Second try: enter wrong password (2)
  -Third try: enter correct password (3)
  -Three nautilus windows open

  I would expect that only one window would open, and that each
  unsuccessful attempt would reset any command to open a window.

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

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


[Desktop-packages] [Bug 1362767] Re: Display content of a folder takes ages. Rebuilds image thumbs every time

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

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

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

Title:
  Display content of a folder takes ages. Rebuilds image thumbs every
  time

Status in nautilus package in Ubuntu:
  Expired

Bug description:
  My ~/Pictures folder currently contains about 800 images. It's not
  much.

  Every single time I open it in Nautilus, it takes ages to load. About ONE 
MINUTE "loading..." before I can see the contents.
  I guess it's rebuilding the thumbnails of the images every time. Something is 
wrong if they are not cached.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: nautilus 1:3.10.1-0ubuntu9.1
  ProcVersionSignature: Ubuntu 3.13.0-34.60-generic 3.13.11.4
  Uname: Linux 3.13.0-34-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Thu Aug 28 20:47:26 2014
  GsettingsChanges:
   b'org.gnome.nautilus.list-view' b'use-tree-view' b'true'
   b'org.gnome.nautilus.list-view' b'default-column-order' b"['name', 'size', 
'type', 'date_modified', 'date_accessed', 'owner', 'group', 'permissions', 
'mime_type', 'where']"
  InstallationDate: Installed on 2013-10-11 (321 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  SourcePackage: nautilus
  UpgradeStatus: Upgraded to trusty on 2014-05-24 (96 days ago)

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

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


[Desktop-packages] [Bug 1368149] Re: "File not found" on attempt to browse windows shares

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

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

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

Title:
  "File not found" on attempt to browse windows shares

Status in nautilus package in Ubuntu:
  Expired

Bug description:
  On a freshly installed Ubuntu 14.04.1:

  * Open Nautilus
  * Choose "Browse Network" in the sidebar
  * Double-click on "Windows Network"

  Instead of displaying computers in the network, Nautilus
  reproducibably displays the following error message (guessing a bit
  because I am using the German version):

  "Failed to retrieve share list from server: File or directory not
  found"

  This happens on both my Ubuntu laptop and desktop PC, every time.

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

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


[Desktop-packages] [Bug 1490989] Re: Nautilus does not show the user name of a new user

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

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

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

Title:
  Nautilus does not show the user name of a new user

Status in nautilus package in Ubuntu:
  Expired

Bug description:
  1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> 
About Ubuntu
  ubuntu 14.04 LTS
  2) The version of the package you are using, via 'apt-cache policy pkgname' 
or by checking in Software Center
  nautilus 1:3.10.1-0ubuntu9.7
  3) What you expected to happen
  I created a new user named New User and opened the directory /home in 
Nautilus.
  I told Nautilus to switch to List view and show Owner.
  The owner of the directory newuser should display New User.
  4) What happened instead
  The owner of directory newuser is displayed as user # 1006.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: nautilus 1:3.10.1-0ubuntu9.7
  ProcVersionSignature: Ubuntu 3.13.0-62.102-generic 3.13.11-ckt24
  Uname: Linux 3.13.0-62-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.12
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue Sep  1 15:35:06 2015
  GsettingsChanges: b'org.gnome.nautilus.list-view' b'default-column-order' 
b"['name', 'size', 'type', 'date_modified', 'date_accessed', 'owner', 'group', 
'permissions', 'mime_type', 'where']"
  InstallationDate: Installed on 2014-08-20 (376 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  SourcePackage: nautilus
  UpgradeStatus: No upgrade log present (probably fresh install)
  usr_lib_nautilus:
   brasero 3.10.0-0ubuntu1
   deja-dup30.0-0ubuntu4
   evince  3.10.3-0ubuntu10.2
   file-roller 3.10.2.1-0ubuntu4.1
   totem   3.10.1-1ubuntu4

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

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


[Desktop-packages] [Bug 1447506] Re: Samba connection dialog falls into illegal state

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

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

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

Title:
  Samba connection dialog falls into illegal state

Status in nautilus package in Ubuntu:
  Expired

Bug description:
  "Connect" and "Cancel" buttons are enabled while the rest of the
  dialog is disabled. The state is entered after a connection failure
  without feedback (invoking `sudo mount.cifs
  //192.168.178.130/data_extension /mnt/data_extension --verbose -o
  uid=1000,gid=1000,rw,user=user` in a terminal gives feedback `I/O
  Error`). Pressing the "Connect" button again causes connection failure
  and a dialog ~"Oops! Something went went wrong" with content ~"Unknown
  error message no such file or directory".

  see attached screenshot for details

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: nautilus 1:3.14.2-0ubuntu9
  Uname: Linux 4.0.0-04-generic x86_64
  ApportVersion: 2.17.2-0ubuntu1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Thu Apr 23 11:01:26 2015
  EcryptfsInUse: Yes
  GsettingsChanges: b'org.gnome.nautilus.list-view' b'default-column-order' 
b"['name', 'size', 'type', 'date_modified', 'date_accessed', 'owner', 'group', 
'permissions', 'mime_type', 'where']"
  InstallationDate: Installed on 2015-04-02 (20 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Beta amd64 (20150326)
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  SourcePackage: nautilus
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1370063] Re: webdav thumbnail large file freeze

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

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

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

Title:
  webdav thumbnail large file freeze

Status in nautilus package in Ubuntu:
  Expired

Bug description:
  When viewing a webDAV mounted share in nautilus it will proceed to
  download all the files in order to generate thumbnails, including
  large files. This results in GB's of data being downloaded and freezes
  nautilus. This even happens if under Preferences > Preview a tick is
  placed at Local Files only and only files smaller than (<10MB).

  From this I conclude that nautilus sees a remote webDAV share as local
  (or just doesn't check) and that it doesn't check file size (or only
  checks file size if it already has downloaded/cached the entire file).

  This is in Nautilus 3.10.1 on Ubuntu 14.04 LTS

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

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


[Desktop-packages] [Bug 1542146] Re: Nautilus fails to preserve directory timestamp on move

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

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

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

Title:
  Nautilus fails to preserve directory timestamp on move

Status in nautilus package in Ubuntu:
  Expired

Bug description:
  Move a directory using mv and its mtime will be preserved. Move a
  directory using Nautilus, and its mtime will be set to the time it was
  moved. This is a bug.

  Nautilus preserves mtime for file and directory copies as well as file
  moves. Moveover, if the user attempts to move a directory that the
  user does not have permission to delete (e.g. it is owned by another
  user), a copy will be created with the correct mtime. This indicates
  that Nautilus is taking an additional step that blats the mtime, but
  only on moves, and only after they have already successfully created
  the destination file.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: nautilus 1:3.14.2-0ubuntu13
  ProcVersionSignature: Ubuntu 4.2.0-25.30-generic 4.2.6
  Uname: Linux 4.2.0-25-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Feb  5 14:08:02 2016
  GsettingsChanges: b'org.gnome.nautilus.list-view' b'default-column-order' 
b"['name', 'size', 'type', 'date_modified', 'date_accessed', 'group', 'where', 
'mime_type', 'owner', 'permissions']"
  InstallationDate: Installed on 2013-04-15 (1025 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Alpha amd64 (20130413)
  SourcePackage: nautilus
  UpgradeStatus: Upgraded to wily on 2015-08-31 (157 days ago)

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

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


[Desktop-packages] [Bug 1814174] Re: Xorg crash report after resume

2019-04-04 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/1814174

Title:
  Xorg crash report after resume

Status in xorg-server package in Ubuntu:
  Expired

Bug description:
  Crash Report when resuming from sleep.
  Similar to https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1586223
  This is a Sager NP8278 (Clevo P170SM-A) laptop with an Nvidia GeForce GTX 
970M, driver 390.77
  The crash log doesn't have much info in it IMO, but I uploaded here 
http://s000.tinyupload.com/?file_id=09497843963607449328

  Output from sudo dmidecode -s bios-version && sudo dmidecode -s 
bios-release-date
  4.6.5
  11/14/2014

  Output from uname -a
  Linux dksager2linux 4.15.0-44-generic #47-Ubuntu SMP Mon Jan 14 11:26:59 UTC 
2019 x86_64 x86_64 x86_64 GNU/Linux

  Output from cat /etc/*ase
  DISTRIB_ID=Ubuntu
  DISTRIB_RELEASE=18.04
  DISTRIB_CODENAME=bionic
  DISTRIB_DESCRIPTION="Ubuntu 18.04.1 LTS"
  NAME="Ubuntu"
  VERSION="18.04.1 LTS (Bionic Beaver)"
  ID=ubuntu
  ID_LIKE=debian
  PRETTY_NAME="Ubuntu 18.04.1 LTS"
  VERSION_ID="18.04"
  HOME_URL="https://www.ubuntu.com/;
  SUPPORT_URL="https://help.ubuntu.com/;
  BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/;
  
PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy;
  VERSION_CODENAME=bionic
  UBUNTU_CODENAME=bionic

  Output from lspci
  00:00.0 Host bridge: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor 
DRAM Controller (rev 06)
  00:01.0 PCI bridge: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor 
PCI Express x16 Controller (rev 06)
  00:02.0 VGA compatible controller: Intel Corporation 4th Gen Core Processor 
Integrated Graphics Controller (rev 06)
  00:03.0 Audio device: Intel Corporation Xeon E3-1200 v3/4th Gen Core 
Processor HD Audio Controller (rev 06)
  00:14.0 USB controller: Intel Corporation 8 Series/C220 Series Chipset Family 
USB xHCI (rev 05)
  00:16.0 Communication controller: Intel Corporation 8 Series/C220 Series 
Chipset Family MEI Controller #1 (rev 04)
  00:1a.0 USB controller: Intel Corporation 8 Series/C220 Series Chipset Family 
USB EHCI #2 (rev 05)
  00:1b.0 Audio device: Intel Corporation 8 Series/C220 Series Chipset High 
Definition Audio Controller (rev 05)
  00:1c.0 PCI bridge: Intel Corporation 8 Series/C220 Series Chipset Family PCI 
Express Root Port #1 (rev d5)
  00:1c.1 PCI bridge: Intel Corporation 8 Series/C220 Series Chipset Family PCI 
Express Root Port #2 (rev d5)
  00:1c.2 PCI bridge: Intel Corporation 8 Series/C220 Series Chipset Family PCI 
Express Root Port #3 (rev d5)
  00:1c.3 PCI bridge: Intel Corporation 8 Series/C220 Series Chipset Family PCI 
Express Root Port #4 (rev d5)
  00:1d.0 USB controller: Intel Corporation 8 Series/C220 Series Chipset Family 
USB EHCI #1 (rev 05)
  00:1f.0 ISA bridge: Intel Corporation HM87 Express LPC Controller (rev 05)
  00:1f.2 SATA controller: Intel Corporation 8 Series/C220 Series Chipset 
Family 6-port SATA Controller 1 [AHCI mode] (rev 05)
  00:1f.3 SMBus: Intel Corporation 8 Series/C220 Series Chipset Family SMBus 
Controller (rev 05)
  01:00.0 VGA compatible controller: NVIDIA Corporation GM204M [GeForce GTX 
970M] (rev a1)
  03:00.0 PCI bridge: Texas Instruments XIO2213A/B/XIO2221 PCI Express to PCI 
Bridge [Cheetah Express] (rev 01)
  04:00.0 FireWire (IEEE 1394): Texas Instruments XIO2213A/B/XIO2221 IEEE-1394b 
OHCI Controller [Cheetah Express] (rev 01)
  05:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. RTL8411 PCI 
Express Card Reader (rev 01)
  05:00.2 Ethernet controller: Realtek Semiconductor Co., Ltd. 
RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 0a)
  06:00.0 Network controller: Intel Corporation Wireless 7260 (rev bb)

  The nuisance inspired me to create a script on the desktop called 
ClearCrashLog.sh (info I got from a YouTube video)
  ls /var/crash
  sudo rm /var/crash/*

  It's annoying to have to type the password every time, but since root owns 
the crash log it's necessary.
  I've used Lubuntu for years.  My prior laptop was a Sager with an AMD card.  
It had the same sort of issue versions ago.  I got in the habit of just 
clicking it away.  I think that the Report Crash fails because the log is owned 
by root and I don't have rights to it.  Perhaps adding myself to the whoopsie 
group would resolve that (and needing sudo to delete too), so I think I'll try 
that.
  It's the only thing about Lubuntu that would be a turn off to new users. 

  It's not a high priority thing, because the system works just fine.
  But it is a nuisance.

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

-- 
Mailing list: 

[Desktop-packages] [Bug 1814454] Re: gnome-calculator incorrect use of dot/comma

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

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

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

Title:
  gnome-calculator incorrect use of dot/comma

Status in gnome-calculator package in Ubuntu:
  Expired

Bug description:
  Pressing numeric keypad delete/dot has strange behavior
  Having locale LC_NUMERIC=it_IT.UTF-8 gnome-calculator get the dot only in 1st 
position, then after 1st position pressing numeric keypad delete does nothing 
and i have to press num lock to have the comma i need because my locale. 
  Having locale LC_NUMERIC=it_IT.UTF-8 gnome-calculator should interpret the 
numeric keypad delete/dot as a comma according locale.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: gnome-calculator 1:3.30.1-1ubuntu1
  ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12
  Uname: Linux 4.18.0-11-generic x86_64
  ApportVersion: 2.20.10-0ubuntu19
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Feb  3 15:41:06 2019
  ExecutablePath: /usr/bin/gnome-calculator
  InstallationDate: Installed on 2019-01-22 (12 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190122)
  SourcePackage: gnome-calculator
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1807778] Re: mutter crashed with SIGSEGV in xkb_state_serialize_layout() from init_xkb_state() from meta_backend_x11_initable_init() from meta_init_backend() from meta_init()

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

- 
/usr/bin/mutter:11:xkb_state_serialize_layout:init_xkb_state:meta_backend_x11_initable_init:meta_init_backend:meta_init
+ mutter crashed with SIGSEGV in xkb_state_serialize_layout() from 
init_xkb_state() from meta_backend_x11_initable_init() from meta_init_backend() 
from meta_init()

** Tags removed: artful kylin-17.10

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

Title:
  mutter crashed with SIGSEGV in xkb_state_serialize_layout() from
  init_xkb_state() from meta_backend_x11_initable_init() from
  meta_init_backend() from meta_init()

Status in mutter package in Ubuntu:
  New

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
mutter.  This problem was most recently seen with package version 
3.30.2-1~ubuntu18.10.1, the problem page at 
https://errors.ubuntu.com/problem/c9276f65c87660639a259684a4068d333e24feb9 
contains more details, including versions of packages affected, stacktrace or 
traceback, and individual crash reports.
  If you do not have access to the Ubuntu Error Tracker and are a software 
developer, you can request it at http://forms.canonical.com/reports/.

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

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


[Desktop-packages] [Bug 1817609] Re: Spinning mouse cursor is invisible when zoom is enabled

2019-04-04 Thread Daniel van Vugt
** Tags added: cursor

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

Title:
  Spinning mouse cursor is invisible when zoom is enabled

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

Bug description:
  I have enabled the zoom accessibility feature in GNOME Settings in
  Ubuntu 18.04.2, but the mouse  cursor will be missing every time the
  mouse cursor changes to the spinning one (e.g. when the application is
  doing some tasks in the background or when the application is not
  responding). Mouse cursor will be visible again when the cursor
  changes back to the normal mouse pointer. This happens in both Ubuntu
  (Ambiance-themed) session and the communitheme session. With regard to
  the display server, It happens in X.Org, but in Wayland, the spinning
  cursor is visible but is not spinning. (It stays still)

  Please note that this bug is not related to the bug
  https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1767648 and the
  proposed update for that bug as this newly-reported bug happens both
  before and after I install the update. Another observation is that the
  bug may be specific to Ubuntu as I previously installed Arch Linux and
  didn't notice this issue.

  Steps to reproduce.
  1. Go to Settings > Universal Access > Zoom and enable it.
  2. Do something that would normally change mouse cursor to the spinning one. 
(e.g. open Synaptic Package Manager)
  3. When the package list is loading, instead of seeing a spinning cursor, the 
mouse cursor becomes invisible.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.28.3-0ubuntu0.18.04.4
  ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18
  Uname: Linux 4.15.0-45-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  CurrentDesktop: communitheme:ubuntu:GNOME
  Date: Tue Feb 26 00:58:52 2019
  DisplayManager: gdm3
  GsettingsChanges:
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
   b'org.gnome.desktop.interface' b'cursor-size' b'48'
  InstallationDate: Installed on 2019-02-24 (0 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/1817609/+subscriptions

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


[Desktop-packages] [Bug 1817685] Re: Dell XPS 15 reboots when resuming from suspend

2019-04-04 Thread Daniel van Vugt
Next time the problem happens, after rebooting, please run:

  journalctl -b-1 > prevboot.txt

and send us the file 'prevboot.txt'.

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

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

Title:
  Dell XPS 15 reboots when resuming from suspend

Status in mutter package in Ubuntu:
  Incomplete

Bug description:
  After upgrading to version 3.30.2-1~ubuntu18.10.3, when I resume from
  suspend my laptop reboots. It seems to suspend correctly but when i
  try to resume it simply reboots. Every time.

  After downgrading to 3.30.1-1, everything is fine again.

  This happened only with 3.30.2-1~ubuntu18.10.3. Before that I was
  running 3.30.2-1~ubuntu18.10.2 with no issues.

  Is there something I can do to help debug this issue?

  I'm running Ubuntu 18.10.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: mutter 3.30.1-1
  ProcVersionSignature: Ubuntu 4.18.0-15.16-generic 4.18.20
  Uname: Linux 4.18.0-15-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Feb 26 10:23:25 2019
  InstallationDate: Installed on 2017-12-14 (438 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  SourcePackage: mutter
  UpgradeStatus: Upgraded to cosmic on 2018-10-19 (129 days ago)
  mtime.conffile..etc.apport.crashdb.conf: 2018-11-21T09:13:30.219492

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

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


[Desktop-packages] [Bug 1564078] Re: gnome-shell crashed with SIGSEGV in meta_window_appears_focused() from meta_window_actor_get_paint_volume() from _clutter_actor_get_paint_volume_mutable()

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

- gnome-shell crashed with SIGSEGV in meta_window_appears_focused()
+ gnome-shell crashed with SIGSEGV in meta_window_appears_focused() from 
meta_window_actor_get_paint_volume() from 
_clutter_actor_get_paint_volume_mutable()

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

Title:
  gnome-shell crashed with SIGSEGV in meta_window_appears_focused() from
  meta_window_actor_get_paint_volume() from
  _clutter_actor_get_paint_volume_mutable()

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  Computer was suspended on battery power. Plug in AC, Ethernet, then resume 
from suspension. gnome-shell freezes for a while, and then works as usual.
  Plug in 2 USB hubs. gnome-shell freezes for a while, then crashes. 
  (If I also plug in a monitor using HDMI->DVI adapter usually both screens go 
blank after 5 seconds, though programs are still running.)

  results of lsusb:
  Bus 002 Device 002: ID 8087:8000 Intel Corp. 
  Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Bus 001 Device 002: ID 8087:8008 Intel Corp. 
  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Bus 004 Device 003: ID 0bc2:ab20 Seagate RSS LLC Backup Plus Portable Drive
  Bus 004 Device 004: ID 0bc2:3320 Seagate RSS LLC SRD00F2 [Expansion Desktop 
Drive]
  Bus 004 Device 002: ID 2109:0812 VIA Labs, Inc. VL812 Hub
  Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
  Bus 003 Device 002: ID 8087:07dc Intel Corp. 
  Bus 003 Device 016: ID 28de:1142  
  Bus 003 Device 015: ID 046d:082c Logitech, Inc. 
  Bus 003 Device 014: ID 0424:2514 Standard Microsystems Corp. USB 2.0 Hub
  Bus 003 Device 013: ID 045e:07a5 Microsoft Corp. Wireless Receiver 1461C
  Bus 003 Device 012: ID 050d:0307 Belkin Components USB 2.0 - 7 ports Hub 
[FSU307]
  Bus 003 Device 011: ID 2109:2812 VIA Labs, Inc. VL812 Hub
  Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

  Might be a duplicate of expired bug #871250.
  Probably not a security issue.

  ProblemType: Crash
  DistroRelease: Ubuntu 16.04
  Package: gnome-shell 3.18.4-0ubuntu2
  ProcVersionSignature: Ubuntu 4.4.0-16.32-generic 4.4.6
  Uname: Linux 4.4.0-16-generic x86_64
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: GNOME
  Date: Wed Mar 30 16:31:49 2016
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  InstallationDate: Installed on 2016-03-03 (27 days ago)
  InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Alpha amd64 
(20160303)
  ProcCmdline: /usr/bin/gnome-shell
  SegvAnalysis:
   Segfault happened at: 0x7fc4b70505c0 :  cmpb   
$0x0,0x15d(%rdi)
   PC (0x7fc4b70505c0) ok
   source "$0x0" ok
   destination "0x15d(%rdi)" (0x015d) not located in a known VMA region 
(needed writable region)!
  SegvReason: writing NULL VMA
  Signal: 11
  SourcePackage: gnome-shell
  StacktraceTop:
   meta_window_appears_focused () at /usr/lib/libmutter.so.0
   () at /usr/lib/libmutter.so.0
   () at /usr/lib/x86_64-linux-gnu/libclutter-1.0.so.0
   () at /usr/lib/x86_64-linux-gnu/libclutter-1.0.so.0
   () at /usr/lib/x86_64-linux-gnu/libclutter-1.0.so.0
  Title: gnome-shell crashed with SIGSEGV in meta_window_appears_focused()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

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

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


[Desktop-packages] [Bug 1795342] Re: Higher power consumption when running gnome-shell compared to unity

2019-04-04 Thread Daniel van Vugt
** Changed in: ubuntu-power-consumption
   Status: New => Incomplete

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

Title:
  Higher power consumption when running gnome-shell compared to unity

Status in The Ubuntu Power Consumption Project:
  Incomplete
Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  Hi,

  I am running Ubuntu on Thinkpad. I am facing battery back up issues on both 
18.04 and 18.10 versions. Before that I was running Ubuntu 16.04 with a normal 
back of almost 4 hours ( 2 Sony Batteries with normal back up of up to min of 6 
hours on Linux Mint 19) and when upgrading to 18.04 it reduced to 3 hours max 
on normal usage and less than 2 hours on heavy use.
  I tried installing Unity session on 18.04/10, the back up increased. I think 
it is Gnome doing the mess.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu13.1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 18.10
  InstallationDate: Installed on 2018-12-02 (1 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  Package: gnome-shell 3.30.1-2ubuntu1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12
  Tags:  cosmic
  Uname: Linux 4.18.0-11-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-power-consumption/+bug/1795342/+subscriptions

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


[Desktop-packages] [Bug 1822426] Re: 19.04 Built in Intel HDA sound is disabled upon resume

2019-04-04 Thread Hui Wang
According to the log, when problem happens, the Nvidia hdmi codec
doesn't response the HDA controller, Usually it is nvidia graphic
driver's issue.

Let us disable the nvidia hdmi audio temporarily and see if this problem
still exists?

edit /proc/modprobe.d/alsa-base.conf and add "options snd-hda-intel
enable=1,0", then reboot and check if there is only hda built-in audio,
if yes, please go ahead to do the test.

thx.

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

Title:
  19.04 Built in Intel HDA sound is disabled upon resume

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

Bug description:
  With 19.04, Intel Corporation 8 Series/C220 Series Chipset High
  Definition Audio Controller intermittently is not enabled when
  resuming from sleep. The HDMI sound device is enabled but that is not
  hooked up on my system.  New with 19.04, when sound works after
  resume, an icon labeled "Built in Audio Stereo" appears during the
  resume process.

  Unsure if this is related, but sound seems to sleep when not in use.
  Launching sound enabled apps produces a quiet "tick, thud" sound as
  sound system turns on.

  When sound is not working, killall pusleaudio "fixes" the issue.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: pulseaudio 1:12.2-2ubuntu1
  ProcVersionSignature: Ubuntu 5.0.0-8.9-generic 5.0.1
  Uname: Linux 5.0.0-8-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.10-0ubuntu23
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  darin  4814 F pulseaudio
   /dev/snd/controlC1:  darin  4814 F pulseaudio
   /dev/snd/controlC0:  darin  4814 F pulseaudio
  CurrentDesktop: KDE
  Date: Sat Mar 30 10:20:24 2019
  InstallationDate: Installed on 2018-01-13 (441 days ago)
  InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180112)
  SourcePackage: pulseaudio
  UpgradeStatus: Upgraded to disco on 2019-03-27 (3 days ago)
  dmi.bios.date: 08/18/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2103
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: Z87-PRO
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2103:bd08/18/2014:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ87-PRO:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.family: ASUS MB
  dmi.product.name: All Series
  dmi.product.sku: All
  dmi.product.version: System Version
  dmi.sys.vendor: ASUS

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

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


[Desktop-packages] [Bug 1823175] Re: Battery status shows "Estimating..." when fully charged

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

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

Title:
  Battery status shows "Estimating..." when fully charged

Status in GNOME Shell:
  Fix Released
Status in gnome-shell package in Ubuntu:
  Fix Released
Status in gnome-shell source package in Bionic:
  Triaged
Status in gnome-shell source package in Cosmic:
  Triaged
Status in gnome-shell source package in Disco:
  Fix Released

Bug description:
  My battery is fully charged and it shows 100%. When it's connected to 
charger, Battery symbol changes to battery-missing-symbol. It also shows 
"Estimating..." for time remaining.
  I'm using "Asus VivoBook x510uf"
  My battery status when connected to AC power:

  $ upower -d
  Device: /org/freedesktop/UPower/devices/line_power_AC0
    native-path:  AC0
    power supply: yes
    updated:  Thu 04 Apr 2019 08:26:58 PM +0430 (-11482 seconds ago)
    has history:  no
    has statistics:   no
    line-power
  warning-level:   none
  online:  yes
  icon-name:  'ac-adapter-symbolic'

  Device: /org/freedesktop/UPower/devices/battery_BAT0
    native-path:  BAT0
    vendor:   ASUSTeK
    model:ASUS Battery
    power supply: yes
    updated:  Thu 04 Apr 2019 05:14:53 PM +0430 (43 seconds ago)
    has history:  yes
    has statistics:   yes
    battery
  present: yes
  rechargeable:yes
  state:   pending-charge
  warning-level:   none
  energy:  40.367 Wh
  energy-empty:0 Wh
  energy-full: 40.367 Wh
  energy-full-design:  43.046 Wh
  energy-rate: 0 W
  voltage: 11.55 V
  percentage:  100%
  capacity:93.7764%
  technology:  lithium-ion
  icon-name:  'battery-full-charging-symbolic'
    History (charge):
  15543934180.000   unknown
    History (rate):
  15543934180.000   unknown

  Device: /org/freedesktop/UPower/devices/DisplayDevice
    power supply: yes
    updated:  Thu 04 Apr 2019 08:26:58 PM +0430 (-11482 seconds ago)
    has history:  no
    has statistics:   no
    battery
  present: yes
  state:   unknown
  warning-level:   none
  energy:  40.367 Wh
  energy-full: 40.367 Wh
  energy-rate: 0 W
  percentage:  100%
  icon-name:  'battery-missing-symbolic'

  Daemon:
    daemon-version:  0.99.7
    on-battery:  no
    lid-is-closed:   no
    lid-is-present:  yes
    critical-action: HybridSleep

  -

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.28.3-0ubuntu0.18.04.4
  ProcVersionSignature: Ubuntu 4.18.0-17.18~18.04.1-generic 4.18.20
  Uname: Linux 4.18.0-17-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Apr  4 17:04:22 2019
  DisplayManager: gdm3
  InstallationDate: Installed on 2019-03-30 (4 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1823175] Re: Battery status shows "Estimating..." when fully charged

2019-04-04 Thread Daniel van Vugt
Upstream bug: https://gitlab.gnome.org/GNOME/gnome-shell/issues/701

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

Title:
  Battery status shows "Estimating..." when fully charged

Status in GNOME Shell:
  Unknown
Status in gnome-shell package in Ubuntu:
  Fix Released
Status in gnome-shell source package in Bionic:
  Triaged
Status in gnome-shell source package in Cosmic:
  Triaged
Status in gnome-shell source package in Disco:
  Fix Released

Bug description:
  My battery is fully charged and it shows 100%. When it's connected to 
charger, Battery symbol changes to battery-missing-symbol. It also shows 
"Estimating..." for time remaining.
  I'm using "Asus VivoBook x510uf"
  My battery status when connected to AC power:

  $ upower -d
  Device: /org/freedesktop/UPower/devices/line_power_AC0
    native-path:  AC0
    power supply: yes
    updated:  Thu 04 Apr 2019 08:26:58 PM +0430 (-11482 seconds ago)
    has history:  no
    has statistics:   no
    line-power
  warning-level:   none
  online:  yes
  icon-name:  'ac-adapter-symbolic'

  Device: /org/freedesktop/UPower/devices/battery_BAT0
    native-path:  BAT0
    vendor:   ASUSTeK
    model:ASUS Battery
    power supply: yes
    updated:  Thu 04 Apr 2019 05:14:53 PM +0430 (43 seconds ago)
    has history:  yes
    has statistics:   yes
    battery
  present: yes
  rechargeable:yes
  state:   pending-charge
  warning-level:   none
  energy:  40.367 Wh
  energy-empty:0 Wh
  energy-full: 40.367 Wh
  energy-full-design:  43.046 Wh
  energy-rate: 0 W
  voltage: 11.55 V
  percentage:  100%
  capacity:93.7764%
  technology:  lithium-ion
  icon-name:  'battery-full-charging-symbolic'
    History (charge):
  15543934180.000   unknown
    History (rate):
  15543934180.000   unknown

  Device: /org/freedesktop/UPower/devices/DisplayDevice
    power supply: yes
    updated:  Thu 04 Apr 2019 08:26:58 PM +0430 (-11482 seconds ago)
    has history:  no
    has statistics:   no
    battery
  present: yes
  state:   unknown
  warning-level:   none
  energy:  40.367 Wh
  energy-full: 40.367 Wh
  energy-rate: 0 W
  percentage:  100%
  icon-name:  'battery-missing-symbolic'

  Daemon:
    daemon-version:  0.99.7
    on-battery:  no
    lid-is-closed:   no
    lid-is-present:  yes
    critical-action: HybridSleep

  -

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.28.3-0ubuntu0.18.04.4
  ProcVersionSignature: Ubuntu 4.18.0-17.18~18.04.1-generic 4.18.20
  Uname: Linux 4.18.0-17-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Apr  4 17:04:22 2019
  DisplayManager: gdm3
  InstallationDate: Installed on 2019-03-30 (4 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1823176] Re: After connecting the usb docking station, the gnome-shell process loads one processor core 100%

2019-04-04 Thread Daniel van Vugt
Thanks for the bug report.

Can you say what model of dock and laptop it is?


** Tags added: performance

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

Title:
  After connecting the usb docking station, the gnome-shell process
  loads one processor core 100%

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  After connecting the usb docking station, the gnome-shell process
  loads one processor core 100%

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.28.3-0ubuntu0.18.04.4
  ProcVersionSignature: Ubuntu 4.18.0-17.18~18.04.1-generic 4.18.20
  Uname: Linux 4.18.0-17-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Apr  4 20:15:25 2019
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  InstallationDate: Installed on 2019-03-20 (15 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=ru_RU.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1823217] Re: Portrait display cuts off below primary monitor

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

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 1822513, 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 1822513
   [regression] gnome-shell aspect ratio doesn't rotate with the rest of the 
screen

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

Title:
  Portrait display cuts off below primary monitor

Status in xorg package in Ubuntu:
  New

Bug description:
  Using beta of Disco Dingo, so gnome-shell 3.32.0-1ubuntu1.

  Two monitors, place one Portrait right.  Any part of that screen that
  extends below the primary monitor is cut off.  The mouse cursor will
  go in there, but any window you drag in there disappears.  If you take
  a screen shot, the screenshot tool thinks that area does not exist.
  Screenshots attached.

  I've used this same monitor layout for years, this issue did not exist
  in Cosmic.  I was able to reproduce it in a clean install in
  Virtualbox, so it's not limited to my hardware or any extensions/apps
  I'm using.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: xorg 1:7.7+19ubuntu12
  ProcVersionSignature: Ubuntu 5.0.0-8.9-generic 5.0.1
  Uname: Linux 5.0.0-8-generic x86_64
  ApportVersion: 2.20.10-0ubuntu23
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Apr  4 14:02:45 2019
  DistUpgraded: Fresh install
  DistroCodename: disco
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox, 6.0.4, 5.0.0-7-generic, x86_64: installed
   virtualbox, 6.0.4, 5.0.0-8-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Crystal Well Integrated Graphics Controller [8086:0d26] 
(rev 08) (prog-if 00 [VGA controller])
 Subsystem: CLEVO/KAPOK Computer Crystal Well Integrated Graphics 
Controller [1558:7410]
  InstallationDate: Installed on 2019-03-26 (8 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190325)
  MachineType: System76, Inc. Galago UltraPro
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-8-generic 
root=UUID=6429a565-4509-46ef-9be8-1558a2b094e4 ro quiet splash vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/09/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 4.6.5
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: Galago UltraPro
  dmi.board.vendor: System76, Inc.
  dmi.board.version: galu1
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: System76, Inc,
  dmi.chassis.version: galu1
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd07/09/2013:svnSystem76,Inc.:pnGalagoUltraPro:pvrgalu1:rvnSystem76,Inc.:rnGalagoUltraPro:rvrgalu1:cvnSystem76,Inc,:ct9:cvrgalu1:
  dmi.product.family: Not Applicable
  dmi.product.name: Galago UltraPro
  dmi.product.sku: Not Applicable
  dmi.product.version: galu1
  dmi.sys.vendor: System76, Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.97-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.1-1ubuntu2
  version.libgl1-mesa-glx: libgl1-mesa-glx 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/1823217/+subscriptions

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


[Desktop-packages] [Bug 1823261] Re: PCI/internal sound card not detected

2019-04-04 Thread Daniel van Vugt
It appears the kernel has stopped reporting any sound devices:

!!Loaded ALSA modules
!!---


!!Sound Servers on this system
!!

Pulseaudio:
  Installed - Yes (/usr/bin/pulseaudio)
  Running - Yes


!!Soundcards recognised by ALSA
!!-

--- no soundcards ---

** Package changed: alsa-driver (Ubuntu) => linux (Ubuntu)

** Tags added: regression-update

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

Title:
  PCI/internal sound card not detected

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  It was ok previously but it stopped some days back. my tracking results no 
sound card found.
  may be a driver problem or something.
  no hardware changes have been made since i started using the device.
  lspci -v says there is intel corp. broadwell-U audio controller is there.
  please help or advise.
  i am using ubuntu 14.04 lts.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu4
  ProcVersionSignature: Ubuntu 3.13.0-52.86+bdw1-generic 3.13.11-ckt18
  Uname: Linux 3.13.0-52-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.29
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CurrentDesktop: Unity
  Date: Fri Apr  5 02:13:22 2019
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-trusty-amd64-20140620-0
  InstallationDate: Installed on 2019-03-19 (16 days ago)
  InstallationMedia: Ubuntu 14.04 "Trusty" - Build amd64 LIVE Binary 
20140620-04:25
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Title: PCI/internal sound card not detected
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/16/2015
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A07
  dmi.board.name: 0RG2FR
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: Not Specified
  dmi.modalias: 
dmi:bvnDellInc.:bvrA07:bd10/16/2015:svnDellInc.:pnInspiron3543:pvrA07:rvnDellInc.:rn0RG2FR:rvrA00:cvnDellInc.:ct8:cvrNotSpecified:
  dmi.product.name: Inspiron 3543
  dmi.product.version: A07
  dmi.sys.vendor: Dell Inc.

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

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


[Desktop-packages] [Bug 1823175] Re: battery status shows "estimating" when fully charged

2019-04-04 Thread Daniel van Vugt
This was fixed in Ubuntu 19.04, specifically in gnome-shell version
3.31.4 onward.


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

** Bug watch added: gitlab.gnome.org/GNOME/gnome-shell/issues #701
   https://gitlab.gnome.org/GNOME/gnome-shell/issues/701

** Also affects: gnome-shell via
   https://gitlab.gnome.org/GNOME/gnome-shell/issues/701
   Importance: Unknown
   Status: Unknown

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

** Changed in: gnome-shell (Ubuntu)
   Importance: Undecided => Medium

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

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

** Also affects: gnome-shell (Ubuntu Disco)
   Importance: Medium
   Status: Triaged

** Also affects: gnome-shell (Ubuntu Cosmic)
   Importance: Undecided
   Status: New

** Changed in: gnome-shell (Ubuntu Disco)
   Status: Triaged => Fix Released

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

** Changed in: gnome-shell (Ubuntu Cosmic)
   Importance: Undecided => Medium

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

** Changed in: gnome-shell (Ubuntu Bionic)
   Importance: Undecided => Medium

** Summary changed:

- battery status shows "estimating" when fully charged
+ Battery status shows "Estimating..." when fully charged

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

Title:
  Battery status shows "Estimating..." when fully charged

Status in GNOME Shell:
  Unknown
Status in gnome-shell package in Ubuntu:
  Fix Released
Status in gnome-shell source package in Bionic:
  Triaged
Status in gnome-shell source package in Cosmic:
  Triaged
Status in gnome-shell source package in Disco:
  Fix Released

Bug description:
  My battery is fully charged and it shows 100%. When it's connected to 
charger, Battery symbol changes to battery-missing-symbol. It also shows 
"Estimating..." for time remaining.
  I'm using "Asus VivoBook x510uf"
  My battery status when connected to AC power:

  $ upower -d
  Device: /org/freedesktop/UPower/devices/line_power_AC0
    native-path:  AC0
    power supply: yes
    updated:  Thu 04 Apr 2019 08:26:58 PM +0430 (-11482 seconds ago)
    has history:  no
    has statistics:   no
    line-power
  warning-level:   none
  online:  yes
  icon-name:  'ac-adapter-symbolic'

  Device: /org/freedesktop/UPower/devices/battery_BAT0
    native-path:  BAT0
    vendor:   ASUSTeK
    model:ASUS Battery
    power supply: yes
    updated:  Thu 04 Apr 2019 05:14:53 PM +0430 (43 seconds ago)
    has history:  yes
    has statistics:   yes
    battery
  present: yes
  rechargeable:yes
  state:   pending-charge
  warning-level:   none
  energy:  40.367 Wh
  energy-empty:0 Wh
  energy-full: 40.367 Wh
  energy-full-design:  43.046 Wh
  energy-rate: 0 W
  voltage: 11.55 V
  percentage:  100%
  capacity:93.7764%
  technology:  lithium-ion
  icon-name:  'battery-full-charging-symbolic'
    History (charge):
  15543934180.000   unknown
    History (rate):
  15543934180.000   unknown

  Device: /org/freedesktop/UPower/devices/DisplayDevice
    power supply: yes
    updated:  Thu 04 Apr 2019 08:26:58 PM +0430 (-11482 seconds ago)
    has history:  no
    has statistics:   no
    battery
  present: yes
  state:   unknown
  warning-level:   none
  energy:  40.367 Wh
  energy-full: 40.367 Wh
  energy-rate: 0 W
  percentage:  100%
  icon-name:  'battery-missing-symbolic'

  Daemon:
    daemon-version:  0.99.7
    on-battery:  no
    lid-is-closed:   no
    lid-is-present:  yes
    critical-action: HybridSleep

  -

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.28.3-0ubuntu0.18.04.4
  ProcVersionSignature: Ubuntu 4.18.0-17.18~18.04.1-generic 4.18.20
  Uname: Linux 4.18.0-17-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Apr  4 17:04:22 2019
  DisplayManager: gdm3
  InstallationDate: Installed on 2019-03-30 (4 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

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

-- 
Mailing list: 

[Desktop-packages] [Bug 1822184] Re: clear_console locks up video when X is running and you log out from a plain text console

2019-04-04 Thread Bug Watch Updater
** Changed in: xorg-server (Debian)
   Status: Confirmed => Fix Released

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

Title:
  clear_console locks up video when X is running and you log out from a
  plain text console

Status in X.Org X server:
  New
Status in bash package in Ubuntu:
  Fix Released
Status in xorg-server package in Ubuntu:
  Confirmed
Status in xorg package in Debian:
  New
Status in xorg-server package in Debian:
  Fix Released

Bug description:
  References:
  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=810660
  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=866898

  
  If X is running and you switch to a plain text console (ie ctrl-alt-f3), log 
in as a regular user, and then log out, the display switches back to the 
graphical login screen and locks up.  The system is still functioning (can ssh 
in, etc) but the video output is frozen.

  The underlying cause is:
  https://gitlab.freedesktop.org/xorg/xserver/issues/492

  However, the problem can at least be worked around by making
  clear_console switch to tty 6 and back instead of switching to 1 and
  back.  This patch corrects the problem:

  
  --- bash-4.4.18.orig/debian/clear_console.c 2019-03-28 12:09:02.415907787 
-0400
  +++ bash-4.4.18/debian/clear_console.c  2019-03-28 12:08:11.984366858 -0400
  @@ -205,7 +205,7 @@
   #if defined(__linux__)
 num = vtstat.v_active;
   #endif
  -  tmp_num = (num == 1 ? 2 : 1);
  +  tmp_num = (num == 6 ? 5 : 6);
   
 /* switch vt to clear the scrollback buffer */
 if (ioctl(fd, VT_ACTIVATE, tmp_num))

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

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


[Desktop-packages] [Bug 1823110] Re: Screen not resized when rotating 90*

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

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 1822513, 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 1822513
   [regression] gnome-shell aspect ratio doesn't rotate with the rest of the 
screen

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

Title:
  Screen not resized when rotating 90*

Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  Running 19.04 beta on a Microsoft Surface Pro 3.
  Screen resolution 2160x1440 works in normal landscape mode (Docked mode) 
however if I rotate the device 90* clockwise or counter-clockwise, the screen 
resolution doesn't change to 1440x2160. The screen actually rotates however it 
hasn't flipped the dimensions to fit.
  This was previously working on Ubuntu 18.10.

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

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


[Desktop-packages] [Bug 1823175] [NEW] battery status shows "estimating" when fully charged

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

My battery is fully charged and it shows 100%. When it's connected to charger, 
Battery symbol changes to battery-missing-symbol. It also shows "Estimating..." 
for time remaining.
I'm using "Asus VivoBook x510uf"
My battery status when connected to AC power:

$ upower -d
Device: /org/freedesktop/UPower/devices/line_power_AC0
  native-path:  AC0
  power supply: yes
  updated:  Thu 04 Apr 2019 08:26:58 PM +0430 (-11482 seconds ago)
  has history:  no
  has statistics:   no
  line-power
warning-level:   none
online:  yes
icon-name:  'ac-adapter-symbolic'

Device: /org/freedesktop/UPower/devices/battery_BAT0
  native-path:  BAT0
  vendor:   ASUSTeK
  model:ASUS Battery
  power supply: yes
  updated:  Thu 04 Apr 2019 05:14:53 PM +0430 (43 seconds ago)
  has history:  yes
  has statistics:   yes
  battery
present: yes
rechargeable:yes
state:   pending-charge
warning-level:   none
energy:  40.367 Wh
energy-empty:0 Wh
energy-full: 40.367 Wh
energy-full-design:  43.046 Wh
energy-rate: 0 W
voltage: 11.55 V
percentage:  100%
capacity:93.7764%
technology:  lithium-ion
icon-name:  'battery-full-charging-symbolic'
  History (charge):
1554393418  0.000   unknown
  History (rate):
1554393418  0.000   unknown

Device: /org/freedesktop/UPower/devices/DisplayDevice
  power supply: yes
  updated:  Thu 04 Apr 2019 08:26:58 PM +0430 (-11482 seconds ago)
  has history:  no
  has statistics:   no
  battery
present: yes
state:   unknown
warning-level:   none
energy:  40.367 Wh
energy-full: 40.367 Wh
energy-rate: 0 W
percentage:  100%
icon-name:  'battery-missing-symbolic'

Daemon:
  daemon-version:  0.99.7
  on-battery:  no
  lid-is-closed:   no
  lid-is-present:  yes
  critical-action: HybridSleep

-

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: gnome-shell 3.28.3-0ubuntu0.18.04.4
ProcVersionSignature: Ubuntu 4.18.0-17.18~18.04.1-generic 4.18.20
Uname: Linux 4.18.0-17-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.6
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Thu Apr  4 17:04:22 2019
DisplayManager: gdm3
InstallationDate: Installed on 2019-03-30 (4 days ago)
InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210)
SourcePackage: gnome-shell
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug bionic
-- 
battery status shows "estimating" when fully charged
https://bugs.launchpad.net/bugs/1823175
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 1752680] Re: Night light does not work in some cases

2019-04-04 Thread Daniel van Vugt
** Tags removed: artful

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

Title:
  Night light does not work in some cases

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

Bug description:
  The night light feature does not work in these cases
   * Computer's screen shuts off due to timeout, and then is reactivated.
   * Computer is brought back from suspend
   * Computer desktop is locked, and unlocked using the password

  In all these cases, the night light icon is present in the
  notification area, and it says "Night Light On". But the screen
  temperature is that of normal daylight.

  In all these cases, disabling and re-enabling the night light using
  the notification area icon reactivates the night light.

  Version information

  Gnome desktop on Ubuntu 4.13.0-36.40-generic 4.13.13

  4.13.0-36-generic #40-Ubuntu SMP Fri Feb 16 20:07:48 UTC 2018 x86_64
  x86_64 x86_64 GNU/Linux

  17.10 Artful Aardvark

  Hardware : MSI GP62 QE - with i5-6300HQ, using the Intel graphics driver.
  ---
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  AudioDevicesInUse:
   USER PID ACCESS COMMAND
   /dev/snd/pcmC0D0p: talonx 2732 F...m pulseaudio
   /dev/snd/controlC0: talonx 2732 F pulseaudio
  CurrentDesktop: GNOME-Classic:GNOME
  DistroRelease: Ubuntu 17.10
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=7808c7a8-dd4d-41e7-a2f2-032701229a6a
  InstallationDate: Installed on 2016-05-05 (659 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: Micro-Star International Co., Ltd. GP62 6QE
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-36-generic 
root=UUID=70280d26-8667-4d1b-9bbd-683373c14707 ro priority=low quiet splash 
acpi_osi= i8042.nomux=1 i8042.reset i8042.nopnp i8042.noloop 
usbcore.autosuspend=-1 vt.handoff=7
  ProcVersionSignature: Ubuntu 4.13.0-36.40-generic 4.13.13
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-36-generic N/A
   linux-backports-modules-4.13.0-36-generic N/A
   linux-firmware 1.169.3
  Tags: artful
  Uname: Linux 4.13.0-36-generic x86_64
  UpgradeStatus: Upgraded to artful on 2017-11-02 (114 days ago)
  UserGroups: adm bumblebee cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 04/25/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: E16J5IMS.113
  dmi.board.asset.tag: Default string
  dmi.board.name: MS-16J5
  dmi.board.vendor: Micro-Star International Co., Ltd.
  dmi.board.version: REV:0.A
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 10
  dmi.chassis.vendor: Micro-Star International Co., Ltd.
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrE16J5IMS.113:bd04/25/2016:svnMicro-StarInternationalCo.,Ltd.:pnGP626QE:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-16J5:rvrREV0.A:cvnMicro-StarInternationalCo.,Ltd.:ct10:cvrDefaultstring:
  dmi.product.name: GP62 6QE
  dmi.product.version: REV:1.0
  dmi.sys.vendor: Micro-Star International Co., Ltd.

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

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


[Desktop-packages] [Bug 1822426] Re: 19.04 Built in Intel HDA sound is disabled upon resume

2019-04-04 Thread Daniel van Vugt
Cristian,

And if your issue is just timidity then that is bug 1793640.

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

Title:
  19.04 Built in Intel HDA sound is disabled upon resume

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

Bug description:
  With 19.04, Intel Corporation 8 Series/C220 Series Chipset High
  Definition Audio Controller intermittently is not enabled when
  resuming from sleep. The HDMI sound device is enabled but that is not
  hooked up on my system.  New with 19.04, when sound works after
  resume, an icon labeled "Built in Audio Stereo" appears during the
  resume process.

  Unsure if this is related, but sound seems to sleep when not in use.
  Launching sound enabled apps produces a quiet "tick, thud" sound as
  sound system turns on.

  When sound is not working, killall pusleaudio "fixes" the issue.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: pulseaudio 1:12.2-2ubuntu1
  ProcVersionSignature: Ubuntu 5.0.0-8.9-generic 5.0.1
  Uname: Linux 5.0.0-8-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.10-0ubuntu23
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  darin  4814 F pulseaudio
   /dev/snd/controlC1:  darin  4814 F pulseaudio
   /dev/snd/controlC0:  darin  4814 F pulseaudio
  CurrentDesktop: KDE
  Date: Sat Mar 30 10:20:24 2019
  InstallationDate: Installed on 2018-01-13 (441 days ago)
  InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180112)
  SourcePackage: pulseaudio
  UpgradeStatus: Upgraded to disco on 2019-03-27 (3 days ago)
  dmi.bios.date: 08/18/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2103
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: Z87-PRO
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2103:bd08/18/2014:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ87-PRO:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.family: ASUS MB
  dmi.product.name: All Series
  dmi.product.sku: All
  dmi.product.version: System Version
  dmi.sys.vendor: ASUS

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

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


[Desktop-packages] [Bug 1812014] Re: keyboard not responding after suspend after some time

2019-04-04 Thread Daniel van Vugt
Please keep this bug about the keyboard only.

Performance issues should be logged as separate bugs, although it sounds
like bug 1808108 is one of the issues.

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

Title:
  keyboard not responding after suspend after some time

Status in gnome-shell package in Ubuntu:
  Incomplete
Status in nvidia-graphics-drivers-390 package in Ubuntu:
  Incomplete
Status in upower package in Ubuntu:
  Incomplete

Bug description:
  I work on Lenovo laptop y-700. When I resume system after suspend, keyboards 
stop working, and sometimes there are performance problems visible when playing 
videos. It happens not immediately but after a few minutes or even a few hours 
of working. Restart or shutdown does not finish correctly and I need to hold 
the power button for a few seconds.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu13.1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 18.10
  GsettingsChanges:
   b'org.gnome.shell' b'had-bluetooth-devices-setup' b'true'
   b'org.gnome.shell' b'app-picker-view' b'uint32 1'
   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-06 (165 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: gnome-shell 3.30.1-2ubuntu1.18.10.2
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=pl_PL.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17
  Tags:  cosmic
  Uname: Linux 4.18.0-13-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip kvm libvirt lpadmin plugdev sambashare sudo
  _MarkForUpload: True

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

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


[Desktop-packages] [Bug 1822426] Re: 19.04 Built in Intel HDA sound is disabled upon resume

2019-04-04 Thread Daniel van Vugt
Cristian,

Please log that issue as a new bug by running:

  ubuntu-bug pulseaudio

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

Title:
  19.04 Built in Intel HDA sound is disabled upon resume

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

Bug description:
  With 19.04, Intel Corporation 8 Series/C220 Series Chipset High
  Definition Audio Controller intermittently is not enabled when
  resuming from sleep. The HDMI sound device is enabled but that is not
  hooked up on my system.  New with 19.04, when sound works after
  resume, an icon labeled "Built in Audio Stereo" appears during the
  resume process.

  Unsure if this is related, but sound seems to sleep when not in use.
  Launching sound enabled apps produces a quiet "tick, thud" sound as
  sound system turns on.

  When sound is not working, killall pusleaudio "fixes" the issue.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: pulseaudio 1:12.2-2ubuntu1
  ProcVersionSignature: Ubuntu 5.0.0-8.9-generic 5.0.1
  Uname: Linux 5.0.0-8-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.10-0ubuntu23
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  darin  4814 F pulseaudio
   /dev/snd/controlC1:  darin  4814 F pulseaudio
   /dev/snd/controlC0:  darin  4814 F pulseaudio
  CurrentDesktop: KDE
  Date: Sat Mar 30 10:20:24 2019
  InstallationDate: Installed on 2018-01-13 (441 days ago)
  InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180112)
  SourcePackage: pulseaudio
  UpgradeStatus: Upgraded to disco on 2019-03-27 (3 days ago)
  dmi.bios.date: 08/18/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2103
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: Z87-PRO
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2103:bd08/18/2014:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ87-PRO:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.family: ASUS MB
  dmi.product.name: All Series
  dmi.product.sku: All
  dmi.product.version: System Version
  dmi.sys.vendor: ASUS

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

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


[Desktop-packages] [Bug 1820078] Re: totem assert failure: corrupted double-linked list

2019-04-04 Thread Daniel van Vugt
Alternatively, please just try adding this to your /etc/environment:

  MALLOC_CHECK_=3

Then reboot and try to reproduce the crash. Any crash reports with
MALLOC_CHECK_=3 set should be better at showing us the root cause here.

** Project changed: totem => ubuntu

** No longer affects: ubuntu

** Bug watch removed: gitlab.gnome.org/GNOME/totem/issues #312
   https://gitlab.gnome.org/GNOME/totem/issues/312

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

Title:
  totem assert failure: corrupted double-linked list

Status in totem package in Ubuntu:
  Incomplete

Bug description:
  https://gitlab.gnome.org/GNOME/totem/issues/312

  ---

  I do not know how this happened.

  ProblemType: Crash
  DistroRelease: Ubuntu 19.04
  Package: totem 3.32.0-1ubuntu1
  Uname: Linux 5.0.1-050001-generic x86_64
  ApportVersion: 2.20.10-0ubuntu23
  Architecture: amd64
  AssertionMessage: corrupted double-linked list
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Mar 13 13:53:15 2019
  ExecutablePath: /usr/bin/totem
  InstallationDate: Installed on 2018-12-02 (101 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  ProcCmdline: /usr/bin/totem --gapplication-service
  ProcEnviron:
   XDG_RUNTIME_DIR=
   SHELL=/bin/bash
   LANGUAGE=es_CL:es
   PATH=(custom, no user)
   LANG=es_CL.UTF-8
  Signal: 6
  SourcePackage: totem
  StacktraceTop:
   __libc_message (action=action@entry=do_abort, fmt=fmt@entry=0x7f75c1e67952 
"%s\n") at ../sysdeps/posix/libc_fatal.c:181
   malloc_printerr (str=str@entry=0x7f75c1e659cd "corrupted double-linked 
list") at malloc.c:5352
   unlink_chunk (p=p@entry=0x7f75780e95d0, av=0x7f757820) at malloc.c:1470
   _int_free (av=0x7f757820, p=0x7f75780e9480, have_lock=) 
at malloc.c:4350
   tcache_thread_shutdown () at malloc.c:2977
  Title: totem assert failure: corrupted double-linked list
  UpgradeStatus: Upgraded to disco on 2018-12-02 (101 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  separator:

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

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


[Desktop-packages] [Bug 1823035] Re: Buttons in Night Light menu in settings weird behaviour

2019-04-04 Thread Daniel van Vugt
Sounds like this might be Nvidia related. See also...

  * bug 1772212
  * bug 1752680
  * https://gitlab.gnome.org/GNOME/mutter/issues/290


** Bug watch added: gitlab.gnome.org/GNOME/mutter/issues #290
   https://gitlab.gnome.org/GNOME/mutter/issues/290

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

Title:
  Buttons in Night Light menu in settings weird behaviour

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

Bug description:
  When you press the pressed button (eg the sunset to sunrise button), it gets 
unpressed and nothing changes.
  Then, when you press that button again, the opposite button (manual) is 
pressed.

  Ubuntu 18.10
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu13.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.10
  InstallationDate: Installed on 2018-10-25 (160 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: gnome-control-center 1:3.30.2-1ubuntu0.18.10.2
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.18.0-17.18-generic 4.18.20
  Tags:  cosmic
  Uname: Linux 4.18.0-17-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-control-center/+bug/1823035/+subscriptions

-- 
Mailing list: https://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 1821849] Re: LibreOffice Impress 6.2.2.2 Embedded Video Problem

2019-04-04 Thread Sam Colegrove
Hi Olivier,

In all your replies you have not stated the distribution you used for 
testing.  On the launchpad site it is stated that others have 
encountered this problem.  Did you do it on Disco?

Sam

On 04/04/19 17:46, Olivier Tilloy wrote:
> Thanks for testing and the feedback Sam.
> I haven't been able to reproduce the problems you're seeing locally.
> Please file a bug report upstream, this might be a known issue, and if not 
> upstream developers should be able to help us nail it down.
>

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

Title:
  LibreOffice Impress 6.2.2.2 Embedded Video Problem

Status in libreoffice package in Ubuntu:
  Confirmed

Bug description:
  The following bugs are for LibreOffice 6.2.2.2 Impress on Kubuntu
  19.04.

  When I start a slide-show with Impress by using either F5 or Shift F5,
  I get a white screen.  When I click on it, the slide is displayed.
  When I exit the presentation with say "Esc", soffice.bin is in the
  taskbar with the odp file used for the presentation.  If I click on
  the odp file and exit, both tasks are removed.

  Now when I advance to an embedded video I get the image shown with
  this report. When the video is started, the previous slide is shown on
  top of the video as it is being played. Not a good view This
  happens when either starting from the first slide or the one preceding
  embedded video.

  I have tried the gtk3 options in https://launchpad.net/bugs/1820062
  and the changes make no difference to this problem.  I have also
  installed gstreamer1.0-plugins-* which solved  previous problem with
  LibreOffice.

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

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


[Desktop-packages] [Bug 1815550] Re: [nvidia] gnome-shell RSS grows without limit, general slowness

2019-04-04 Thread Chris Halse Rogers
This is *not* specific to nvidia_drm.modeset=1¹. With KMS disabled
gnome-shell still freezes for a second or two and its RSS grows by ~50MB
each time a zsh prompt is displayed.

This is also a regression from Cosmic. I did not experience this
behaviour on Cosmic.

¹: Although some other quirks are.

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

Title:
  [nvidia] gnome-shell RSS grows without limit, general slowness

Status in gnome-shell package in Ubuntu:
  Confirmed
Status in gnome-shell source package in Disco:
  Confirmed

Bug description:
  This *may* be an nvidia-specific problem, but the RSS of gnome-shell
  on my system grows without limit (over a couple of hours it's
  increased past 10G).

  At the same time, gnome-shell appears to become progressively less
  responsive.

  Restarting gnome-shell (via  restart) drops shell RSS down to
  ~400MB and improves system responsiveness a bit.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: gnome-shell 3.30.2-2ubuntu2
  ProcVersionSignature: Ubuntu 4.20.0+bcachefs.git20190130.d1f70147-1.0-generic 
4.20.0
  Uname: Linux 4.20.0+bcachefs.git20190130.d1f70147-1-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.10-0ubuntu20
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Feb 12 13:35:59 2019
  DisplayManager: gdm3
  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/1815550/+subscriptions

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


[Desktop-packages] [Bug 1823272] [NEW] package sgml-base 1.29 failed to install/upgrade: eindeloze triggerlus; afgebroken

2019-04-04 Thread FrankThuis
Public bug reported:

upgrade from 18:10 to 19:04

ProblemType: Package
DistroRelease: Ubuntu 19.04
Package: sgml-base 1.29
ProcVersionSignature: Ubuntu 5.0.0-8.9-generic 5.0.1
Uname: Linux 5.0.0-8-generic x86_64
ApportVersion: 2.20.10-0ubuntu25
Architecture: amd64
Date: Fri Apr  5 00:33:37 2019
ErrorMessage: eindeloze triggerlus; afgebroken
InstallationDate: Installed on 2016-12-31 (824 days ago)
InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
PackageArchitecture: all
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:
 dpkg 1.19.6ubuntu1
 apt  1.8.0
SourcePackage: sgml-base
Title: package sgml-base 1.29 failed to install/upgrade: eindeloze triggerlus; 
afgebroken
UpgradeStatus: Upgraded to disco on 2019-04-04 (0 days ago)

** Affects: sgml-base (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package disco

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

Title:
  package sgml-base 1.29 failed to install/upgrade: eindeloze
  triggerlus; afgebroken

Status in sgml-base package in Ubuntu:
  New

Bug description:
  upgrade from 18:10 to 19:04

  ProblemType: Package
  DistroRelease: Ubuntu 19.04
  Package: sgml-base 1.29
  ProcVersionSignature: Ubuntu 5.0.0-8.9-generic 5.0.1
  Uname: Linux 5.0.0-8-generic x86_64
  ApportVersion: 2.20.10-0ubuntu25
  Architecture: amd64
  Date: Fri Apr  5 00:33:37 2019
  ErrorMessage: eindeloze triggerlus; afgebroken
  InstallationDate: Installed on 2016-12-31 (824 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  PackageArchitecture: all
  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:
   dpkg 1.19.6ubuntu1
   apt  1.8.0
  SourcePackage: sgml-base
  Title: package sgml-base 1.29 failed to install/upgrade: eindeloze 
triggerlus; afgebroken
  UpgradeStatus: Upgraded to disco on 2019-04-04 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/sgml-base/+bug/1823272/+subscriptions

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


[Desktop-packages] [Bug 1823270] Re: package libgles1 (not installed) failed to install/upgrade: trying to overwrite '/usr/lib/x86_64-linux-gnu/libGLESv1_CM.so.1', which is also in package nvidia-340

2019-04-04 Thread Apport retracing service
** Tags removed: need-duplicate-check

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

Title:
  package libgles1 (not installed) failed to install/upgrade: trying to
  overwrite '/usr/lib/x86_64-linux-gnu/libGLESv1_CM.so.1', which is also
  in package nvidia-340 340.106-0ubuntu3

Status in libglvnd package in Ubuntu:
  New

Bug description:
  I suppose I messed up with the package installer system programs -

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: libgles1 (not installed)
  ProcVersionSignature: Ubuntu 4.15.0-32.35-generic 4.15.18
  Uname: Linux 4.15.0-32-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.20.9-0ubuntu7.2
  AptOrdering:
   libglvnd-dev:amd64: Install
   libgles1:amd64: Install
   gnome-gmail:amd64: Install
   NULL: ConfigurePending
  Architecture: amd64
  Date: Thu Apr  4 18:51:21 2019
  DpkgHistoryLog:
   Start-Date: 2019-04-04  18:51:19
   Commandline: packagekit role='install-packages'
   Requested-By: scoobbs (1000)
   Install: libgles1:amd64 (1.0.0-2ubuntu2.2, automatic), gnome-gmail:amd64 
(2.5.4-3)
   Upgrade: libglvnd-dev:amd64 (1.0.0-2ubuntu2.1, 1.0.0-2ubuntu2.2)
  DuplicateSignature:
   package:libgles1:(not installed)
   Unpacking libglvnd-dev:amd64 (1.0.0-2ubuntu2.2) over (1.0.0-2ubuntu2.1) ...
   dpkg: error processing archive 
/var/cache/apt/archives/libglvnd-dev_1.0.0-2ubuntu2.2_amd64.deb (--unpack):
trying to overwrite '/usr/lib/x86_64-linux-gnu/libGLESv1_CM.so', which is 
also in package nvidia-340 340.106-0ubuntu3
  ErrorMessage: trying to overwrite 
'/usr/lib/x86_64-linux-gnu/libGLESv1_CM.so.1', which is also in package 
nvidia-340 340.106-0ubuntu3
  InstallationDate: Installed on 2018-08-09 (238 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  Python3Details: /usr/bin/python3.6, Python 3.6.7, python3-minimal, 
3.6.7-1~18.04
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu2.1
   apt  1.6.3
  SourcePackage: libglvnd
  Title: package libgles1 (not installed) failed to install/upgrade: trying to 
overwrite '/usr/lib/x86_64-linux-gnu/libGLESv1_CM.so.1', which is also in 
package nvidia-340 340.106-0ubuntu3
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1823269] Re: vm ubuntu Canon printer will not print

2019-04-04 Thread Raymond Schutte
** Attachment added: "troubleshoot.txt"
   
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1823269/+attachment/5252961/+files/troubleshoot.txt

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

Title:
  vm ubuntu Canon printer will not print

Status in cups package in Ubuntu:
  New

Bug description:
  Printer stays in processing mode and does not print

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: cups 2.2.10-4
  ProcVersionSignature: Ubuntu 5.0.0-8.9-generic 5.0.1
  Uname: Linux 5.0.0-8-generic x86_64
  ApportVersion: 2.20.10-0ubuntu23
  Architecture: amd64
  CupsErrorLog: Error: [Errno 13] Permission denied: '/var/log/cups/error_log'
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Apr  4 16:52:17 2019
  InstallationDate: Installed on 2017-07-06 (637 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  Lpstat:
   device for iR-ADV-C5535-5540-III-UFR-II: socket://192.168.5.8
   device for iR-ADV-C5535-5540-III-UFR-II-2: socket://192.168.5.9
  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
  Papersize: letter
  PpdFiles:
   Error: command ['fgrep', '-H', '*NickName', 
'/etc/cups/ppd/iR-ADV-C5535-5540-III-UFR-II.ppd', 
'/etc/cups/ppd/iR-ADV-C5535-5540-III-UFR-II-2.ppd'] failed with exit code 2: 
grep: /etc/cups/ppd/iR-ADV-C5535-5540-III-UFR-II.ppd: Permission denied
   grep: /etc/cups/ppd/iR-ADV-C5535-5540-III-UFR-II-2.ppd: Permission denied
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-8-generic 
root=UUID=0da1d663-4b5f-454a-aecf-80ce65eb22d3 ro cgroup_enable=memory 
swapaccount=1 splash
  SourcePackage: cups
  UpgradeStatus: Upgraded to disco on 2019-04-04 (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/+source/cups/+bug/1823269/+subscriptions

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


[Desktop-packages] [Bug 1823269] [NEW] vm ubuntu Canon printer will not print

2019-04-04 Thread Raymond Schutte
Public bug reported:

Printer stays in processing mode and does not print

ProblemType: Bug
DistroRelease: Ubuntu 19.04
Package: cups 2.2.10-4
ProcVersionSignature: Ubuntu 5.0.0-8.9-generic 5.0.1
Uname: Linux 5.0.0-8-generic x86_64
ApportVersion: 2.20.10-0ubuntu23
Architecture: amd64
CupsErrorLog: Error: [Errno 13] Permission denied: '/var/log/cups/error_log'
CurrentDesktop: ubuntu:GNOME
Date: Thu Apr  4 16:52:17 2019
InstallationDate: Installed on 2017-07-06 (637 days ago)
InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
Lpstat:
 device for iR-ADV-C5535-5540-III-UFR-II: socket://192.168.5.8
 device for iR-ADV-C5535-5540-III-UFR-II-2: socket://192.168.5.9
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
Papersize: letter
PpdFiles:
 Error: command ['fgrep', '-H', '*NickName', 
'/etc/cups/ppd/iR-ADV-C5535-5540-III-UFR-II.ppd', 
'/etc/cups/ppd/iR-ADV-C5535-5540-III-UFR-II-2.ppd'] failed with exit code 2: 
grep: /etc/cups/ppd/iR-ADV-C5535-5540-III-UFR-II.ppd: Permission denied
 grep: /etc/cups/ppd/iR-ADV-C5535-5540-III-UFR-II-2.ppd: Permission denied
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-8-generic 
root=UUID=0da1d663-4b5f-454a-aecf-80ce65eb22d3 ro cgroup_enable=memory 
swapaccount=1 splash
SourcePackage: cups
UpgradeStatus: Upgraded to disco on 2019-04-04 (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

** Affects: cups (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 cups in Ubuntu.
https://bugs.launchpad.net/bugs/1823269

Title:
  vm ubuntu Canon printer will not print

Status in cups package in Ubuntu:
  New

Bug description:
  Printer stays in processing mode and does not print

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: cups 2.2.10-4
  ProcVersionSignature: Ubuntu 5.0.0-8.9-generic 5.0.1
  Uname: Linux 5.0.0-8-generic x86_64
  ApportVersion: 2.20.10-0ubuntu23
  Architecture: amd64
  CupsErrorLog: Error: [Errno 13] Permission denied: '/var/log/cups/error_log'
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Apr  4 16:52:17 2019
  InstallationDate: Installed on 2017-07-06 (637 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  Lpstat:
   device for iR-ADV-C5535-5540-III-UFR-II: socket://192.168.5.8
   device for iR-ADV-C5535-5540-III-UFR-II-2: socket://192.168.5.9
  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
  Papersize: letter
  PpdFiles:
   Error: command ['fgrep', '-H', '*NickName', 
'/etc/cups/ppd/iR-ADV-C5535-5540-III-UFR-II.ppd', 
'/etc/cups/ppd/iR-ADV-C5535-5540-III-UFR-II-2.ppd'] failed with exit code 2: 
grep: /etc/cups/ppd/iR-ADV-C5535-5540-III-UFR-II.ppd: Permission denied
   grep: /etc/cups/ppd/iR-ADV-C5535-5540-III-UFR-II-2.ppd: Permission denied
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-8-generic 
root=UUID=0da1d663-4b5f-454a-aecf-80ce65eb22d3 ro cgroup_enable=memory 
swapaccount=1 splash
  SourcePackage: cups
  UpgradeStatus: Upgraded to disco on 2019-04-04 (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/+source/cups/+bug/1823269/+subscriptions

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

[Desktop-packages] [Bug 1822394] Re: [Dell XPS 15 9575] laptop keyboard & touchpad not working at gdm screen after boot

2019-04-04 Thread Joe Barnett
Perhaps this is somehow related to the convertible lid hinge.
Ordinarily when the laptop is in "tablet" mode (hinge open > 180
degrees), the keyboard and touchpad are disabled.  Even more reliably
than using an external device, switching into and then back out of
tablet mode by opening/closing the hinge seems to restore
keyboard/touchpad functionality.  Not sure why they appear to work until
the gdm screen though, or why sometimes using an external device causes
them to work again.

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

Title:
  [Dell XPS 15 9575] laptop keyboard & touchpad not working at gdm
  screen after boot

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

Bug description:
  On a dell XPS 15 2-in-1 with the latest 1.4.0 bios, my touchpad and keyboard 
are unresponsive at the gdm login screen.  Keyboard works to unlock encrypted 
harddrive before that though.  If I plug in a USB keyboard or activate my 
bluetooth mouse, I can use those to log in, and then after logging in the 
laptop touchpad and keyboard work again.  Logging out of the desktop results
  in the laptop touchpad and keyboard working on the gdm screen.  Did not see 
  this behavior before upgrading from 1.2.0 bios to 1.4.0 bios, but also had
  not rebooted in a while, so not sure if bios or package upgrades triggered 
  this behavior.

  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
  ApportVersion: 2.20.10-0ubuntu23
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Fri Mar 29 17:51:00 2019
  InstallationDate: Installed on 2018-09-26 (184 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  SourcePackage: gdm3
  UpgradeStatus: Upgraded to disco on 2019-03-11 (18 days ago)

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

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


[Desktop-packages] [Bug 1823270] [NEW] package libgles1 (not installed) failed to install/upgrade: trying to overwrite '/usr/lib/x86_64-linux-gnu/libGLESv1_CM.so.1', which is also in package nvidia-34

2019-04-04 Thread scoobbs
Public bug reported:

I suppose I messed up with the package installer system programs -

ProblemType: Package
DistroRelease: Ubuntu 18.04
Package: libgles1 (not installed)
ProcVersionSignature: Ubuntu 4.15.0-32.35-generic 4.15.18
Uname: Linux 4.15.0-32-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.20.9-0ubuntu7.2
AptOrdering:
 libglvnd-dev:amd64: Install
 libgles1:amd64: Install
 gnome-gmail:amd64: Install
 NULL: ConfigurePending
Architecture: amd64
Date: Thu Apr  4 18:51:21 2019
DpkgHistoryLog:
 Start-Date: 2019-04-04  18:51:19
 Commandline: packagekit role='install-packages'
 Requested-By: scoobbs (1000)
 Install: libgles1:amd64 (1.0.0-2ubuntu2.2, automatic), gnome-gmail:amd64 
(2.5.4-3)
 Upgrade: libglvnd-dev:amd64 (1.0.0-2ubuntu2.1, 1.0.0-2ubuntu2.2)
DuplicateSignature:
 package:libgles1:(not installed)
 Unpacking libglvnd-dev:amd64 (1.0.0-2ubuntu2.2) over (1.0.0-2ubuntu2.1) ...
 dpkg: error processing archive 
/var/cache/apt/archives/libglvnd-dev_1.0.0-2ubuntu2.2_amd64.deb (--unpack):
  trying to overwrite '/usr/lib/x86_64-linux-gnu/libGLESv1_CM.so', which is 
also in package nvidia-340 340.106-0ubuntu3
ErrorMessage: trying to overwrite 
'/usr/lib/x86_64-linux-gnu/libGLESv1_CM.so.1', which is also in package 
nvidia-340 340.106-0ubuntu3
InstallationDate: Installed on 2018-08-09 (238 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
Python3Details: /usr/bin/python3.6, Python 3.6.7, python3-minimal, 3.6.7-1~18.04
PythonDetails: N/A
RelatedPackageVersions:
 dpkg 1.19.0.5ubuntu2.1
 apt  1.6.3
SourcePackage: libglvnd
Title: package libgles1 (not installed) failed to install/upgrade: trying to 
overwrite '/usr/lib/x86_64-linux-gnu/libGLESv1_CM.so.1', which is also in 
package nvidia-340 340.106-0ubuntu3
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-package bionic package-conflict

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

Title:
  package libgles1 (not installed) failed to install/upgrade: trying to
  overwrite '/usr/lib/x86_64-linux-gnu/libGLESv1_CM.so.1', which is also
  in package nvidia-340 340.106-0ubuntu3

Status in libglvnd package in Ubuntu:
  New

Bug description:
  I suppose I messed up with the package installer system programs -

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: libgles1 (not installed)
  ProcVersionSignature: Ubuntu 4.15.0-32.35-generic 4.15.18
  Uname: Linux 4.15.0-32-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.20.9-0ubuntu7.2
  AptOrdering:
   libglvnd-dev:amd64: Install
   libgles1:amd64: Install
   gnome-gmail:amd64: Install
   NULL: ConfigurePending
  Architecture: amd64
  Date: Thu Apr  4 18:51:21 2019
  DpkgHistoryLog:
   Start-Date: 2019-04-04  18:51:19
   Commandline: packagekit role='install-packages'
   Requested-By: scoobbs (1000)
   Install: libgles1:amd64 (1.0.0-2ubuntu2.2, automatic), gnome-gmail:amd64 
(2.5.4-3)
   Upgrade: libglvnd-dev:amd64 (1.0.0-2ubuntu2.1, 1.0.0-2ubuntu2.2)
  DuplicateSignature:
   package:libgles1:(not installed)
   Unpacking libglvnd-dev:amd64 (1.0.0-2ubuntu2.2) over (1.0.0-2ubuntu2.1) ...
   dpkg: error processing archive 
/var/cache/apt/archives/libglvnd-dev_1.0.0-2ubuntu2.2_amd64.deb (--unpack):
trying to overwrite '/usr/lib/x86_64-linux-gnu/libGLESv1_CM.so', which is 
also in package nvidia-340 340.106-0ubuntu3
  ErrorMessage: trying to overwrite 
'/usr/lib/x86_64-linux-gnu/libGLESv1_CM.so.1', which is also in package 
nvidia-340 340.106-0ubuntu3
  InstallationDate: Installed on 2018-08-09 (238 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  Python3Details: /usr/bin/python3.6, Python 3.6.7, python3-minimal, 
3.6.7-1~18.04
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu2.1
   apt  1.6.3
  SourcePackage: libglvnd
  Title: package libgles1 (not installed) failed to install/upgrade: trying to 
overwrite '/usr/lib/x86_64-linux-gnu/libGLESv1_CM.so.1', which is also in 
package nvidia-340 340.106-0ubuntu3
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


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

2019-04-04 Thread leihao
I had this issue until i uninstalled chrome remote desktop.

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

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

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

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

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

  journalctl output during the issue:

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

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

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

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


[Desktop-packages] [Bug 1823175] Re: battery status shows "estimating" when fully charged

2019-04-04 Thread Mohammad Kazemi
I'm not sure which package

** Package changed: gnome-shell (Ubuntu) => 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/1823175

Title:
  battery status shows "estimating" when fully charged

Status in Ubuntu:
  New

Bug description:
  My battery is fully charged and it shows 100%. When it's connected to 
charger, Battery symbol changes to battery-missing-symbol. It also shows 
"Estimating..." for time remaining.
  I'm using "Asus VivoBook x510uf"
  My battery status when connected to AC power:

  $ upower -d
  Device: /org/freedesktop/UPower/devices/line_power_AC0
    native-path:  AC0
    power supply: yes
    updated:  Thu 04 Apr 2019 08:26:58 PM +0430 (-11482 seconds ago)
    has history:  no
    has statistics:   no
    line-power
  warning-level:   none
  online:  yes
  icon-name:  'ac-adapter-symbolic'

  Device: /org/freedesktop/UPower/devices/battery_BAT0
    native-path:  BAT0
    vendor:   ASUSTeK
    model:ASUS Battery
    power supply: yes
    updated:  Thu 04 Apr 2019 05:14:53 PM +0430 (43 seconds ago)
    has history:  yes
    has statistics:   yes
    battery
  present: yes
  rechargeable:yes
  state:   pending-charge
  warning-level:   none
  energy:  40.367 Wh
  energy-empty:0 Wh
  energy-full: 40.367 Wh
  energy-full-design:  43.046 Wh
  energy-rate: 0 W
  voltage: 11.55 V
  percentage:  100%
  capacity:93.7764%
  technology:  lithium-ion
  icon-name:  'battery-full-charging-symbolic'
    History (charge):
  15543934180.000   unknown
    History (rate):
  15543934180.000   unknown

  Device: /org/freedesktop/UPower/devices/DisplayDevice
    power supply: yes
    updated:  Thu 04 Apr 2019 08:26:58 PM +0430 (-11482 seconds ago)
    has history:  no
    has statistics:   no
    battery
  present: yes
  state:   unknown
  warning-level:   none
  energy:  40.367 Wh
  energy-full: 40.367 Wh
  energy-rate: 0 W
  percentage:  100%
  icon-name:  'battery-missing-symbolic'

  Daemon:
    daemon-version:  0.99.7
    on-battery:  no
    lid-is-closed:   no
    lid-is-present:  yes
    critical-action: HybridSleep

  -

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.28.3-0ubuntu0.18.04.4
  ProcVersionSignature: Ubuntu 4.18.0-17.18~18.04.1-generic 4.18.20
  Uname: Linux 4.18.0-17-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Apr  4 17:04:22 2019
  DisplayManager: gdm3
  InstallationDate: Installed on 2019-03-30 (4 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1823261] [NEW] PCI/internal sound card not detected

2019-04-04 Thread SIDDHARTHA NATH
Public bug reported:

It was ok previously but it stopped some days back. my tracking results no 
sound card found.
may be a driver problem or something.
no hardware changes have been made since i started using the device.
lspci -v says there is intel corp. broadwell-U audio controller is there.
please help or advise.
i am using ubuntu 14.04 lts.

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: alsa-base 1.0.25+dfsg-0ubuntu4
ProcVersionSignature: Ubuntu 3.13.0-52.86+bdw1-generic 3.13.11-ckt18
Uname: Linux 3.13.0-52-generic x86_64
ApportVersion: 2.14.1-0ubuntu3.29
Architecture: amd64
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
CurrentDesktop: Unity
Date: Fri Apr  5 02:13:22 2019
DistributionChannelDescriptor:
 # This is a distribution channel descriptor
 # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor
 canonical-oem-somerville-trusty-amd64-20140620-0
InstallationDate: Installed on 2019-03-19 (16 days ago)
InstallationMedia: Ubuntu 14.04 "Trusty" - Build amd64 LIVE Binary 
20140620-04:25
PackageArchitecture: all
SourcePackage: alsa-driver
Symptom: audio
Title: PCI/internal sound card not detected
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 10/16/2015
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A07
dmi.board.name: 0RG2FR
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 8
dmi.chassis.vendor: Dell Inc.
dmi.chassis.version: Not Specified
dmi.modalias: 
dmi:bvnDellInc.:bvrA07:bd10/16/2015:svnDellInc.:pnInspiron3543:pvrA07:rvnDellInc.:rn0RG2FR:rvrA00:cvnDellInc.:ct8:cvrNotSpecified:
dmi.product.name: Inspiron 3543
dmi.product.version: A07
dmi.sys.vendor: Dell Inc.

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


** Tags: amd64 apport-bug trusty

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

Title:
  PCI/internal sound card not detected

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  It was ok previously but it stopped some days back. my tracking results no 
sound card found.
  may be a driver problem or something.
  no hardware changes have been made since i started using the device.
  lspci -v says there is intel corp. broadwell-U audio controller is there.
  please help or advise.
  i am using ubuntu 14.04 lts.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu4
  ProcVersionSignature: Ubuntu 3.13.0-52.86+bdw1-generic 3.13.11-ckt18
  Uname: Linux 3.13.0-52-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.29
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CurrentDesktop: Unity
  Date: Fri Apr  5 02:13:22 2019
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-trusty-amd64-20140620-0
  InstallationDate: Installed on 2019-03-19 (16 days ago)
  InstallationMedia: Ubuntu 14.04 "Trusty" - Build amd64 LIVE Binary 
20140620-04:25
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Title: PCI/internal sound card not detected
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/16/2015
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A07
  dmi.board.name: 0RG2FR
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: Not Specified
  dmi.modalias: 
dmi:bvnDellInc.:bvrA07:bd10/16/2015:svnDellInc.:pnInspiron3543:pvrA07:rvnDellInc.:rn0RG2FR:rvrA00:cvnDellInc.:ct8:cvrNotSpecified:
  dmi.product.name: Inspiron 3543
  dmi.product.version: A07
  dmi.sys.vendor: Dell Inc.

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

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


[Desktop-packages] [Bug 1812014] Re: keyboard not responding after suspend after some time

2019-04-04 Thread Krzysztof
Hi, recently I had changed the gpu driver to the latest one from nvidia
nvidia-driver-418(opensource) and I since then, I started experiencing
performance problems similar to those mentioned earlier: "'upower' using
100% CPU and another shows 'kworker/6:0-events' using 100%.". The
prolems starts after suspending my system and bringing it back to life
like previously, but this time keyboard is working fine.

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

Title:
  keyboard not responding after suspend after some time

Status in gnome-shell package in Ubuntu:
  Incomplete
Status in nvidia-graphics-drivers-390 package in Ubuntu:
  Incomplete
Status in upower package in Ubuntu:
  Incomplete

Bug description:
  I work on Lenovo laptop y-700. When I resume system after suspend, keyboards 
stop working, and sometimes there are performance problems visible when playing 
videos. It happens not immediately but after a few minutes or even a few hours 
of working. Restart or shutdown does not finish correctly and I need to hold 
the power button for a few seconds.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu13.1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 18.10
  GsettingsChanges:
   b'org.gnome.shell' b'had-bluetooth-devices-setup' b'true'
   b'org.gnome.shell' b'app-picker-view' b'uint32 1'
   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-06 (165 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: gnome-shell 3.30.1-2ubuntu1.18.10.2
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=pl_PL.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17
  Tags:  cosmic
  Uname: Linux 4.18.0-13-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip kvm libvirt lpadmin plugdev sambashare sudo
  _MarkForUpload: True

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

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


[Desktop-packages] [Bug 1823217] [NEW] Portrait display cuts off below primary monitor

2019-04-04 Thread Douglas Hitchcock
Public bug reported:

Using beta of Disco Dingo, so gnome-shell 3.32.0-1ubuntu1.

Two monitors, place one Portrait right.  Any part of that screen that
extends below the primary monitor is cut off.  The mouse cursor will go
in there, but any window you drag in there disappears.  If you take a
screen shot, the screenshot tool thinks that area does not exist.
Screenshots attached.

I've used this same monitor layout for years, this issue did not exist
in Cosmic.  I was able to reproduce it in a clean install in Virtualbox,
so it's not limited to my hardware or any extensions/apps I'm using.

ProblemType: Bug
DistroRelease: Ubuntu 19.04
Package: xorg 1:7.7+19ubuntu12
ProcVersionSignature: Ubuntu 5.0.0-8.9-generic 5.0.1
Uname: Linux 5.0.0-8-generic x86_64
ApportVersion: 2.20.10-0ubuntu23
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Thu Apr  4 14:02:45 2019
DistUpgraded: Fresh install
DistroCodename: disco
DistroVariant: ubuntu
DkmsStatus:
 virtualbox, 6.0.4, 5.0.0-7-generic, x86_64: installed
 virtualbox, 6.0.4, 5.0.0-8-generic, x86_64: installed
ExtraDebuggingInterest: Yes
GraphicsCard:
 Intel Corporation Crystal Well Integrated Graphics Controller [8086:0d26] (rev 
08) (prog-if 00 [VGA controller])
   Subsystem: CLEVO/KAPOK Computer Crystal Well Integrated Graphics Controller 
[1558:7410]
InstallationDate: Installed on 2019-03-26 (8 days ago)
InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190325)
MachineType: System76, Inc. Galago UltraPro
ProcEnviron:
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-8-generic 
root=UUID=6429a565-4509-46ef-9be8-1558a2b094e4 ro quiet splash vt.handoff=1
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 07/09/2013
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 4.6.5
dmi.board.asset.tag: Tag 12345
dmi.board.name: Galago UltraPro
dmi.board.vendor: System76, Inc.
dmi.board.version: galu1
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 9
dmi.chassis.vendor: System76, Inc,
dmi.chassis.version: galu1
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd07/09/2013:svnSystem76,Inc.:pnGalagoUltraPro:pvrgalu1:rvnSystem76,Inc.:rnGalagoUltraPro:rvrgalu1:cvnSystem76,Inc,:ct9:cvrgalu1:
dmi.product.family: Not Applicable
dmi.product.name: Galago UltraPro
dmi.product.sku: Not Applicable
dmi.product.version: galu1
dmi.sys.vendor: System76, Inc.
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.97-1ubuntu1
version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.1-1ubuntu2
version.libgl1-mesa-glx: libgl1-mesa-glx 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

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


** Tags: amd64 apport-bug disco ubuntu

** Attachment added: "Picture of screen, since screenshot doesn't capture the 
blackness"
   
https://bugs.launchpad.net/bugs/1823217/+attachment/5252896/+files/IMG_20190404_121441.jpg

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

Title:
  Portrait display cuts off below primary monitor

Status in xorg package in Ubuntu:
  New

Bug description:
  Using beta of Disco Dingo, so gnome-shell 3.32.0-1ubuntu1.

  Two monitors, place one Portrait right.  Any part of that screen that
  extends below the primary monitor is cut off.  The mouse cursor will
  go in there, but any window you drag in there disappears.  If you take
  a screen shot, the screenshot tool thinks that area does not exist.
  Screenshots attached.

  I've used this same monitor layout for years, this issue did not exist
  in Cosmic.  I was able to reproduce it in a clean install in
  Virtualbox, so it's not limited to my hardware or any extensions/apps
  I'm using.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: xorg 1:7.7+19ubuntu12
  ProcVersionSignature: Ubuntu 5.0.0-8.9-generic 5.0.1
  Uname: Linux 5.0.0-8-generic x86_64
  ApportVersion: 2.20.10-0ubuntu23
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Apr  4 14:02:45 2019
  DistUpgraded: Fresh install
  DistroCodename: disco
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox, 6.0.4, 5.0.0-7-generic, x86_64: installed
   virtualbox, 6.0.4, 5.0.0-8-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Crystal Well Integrated Graphics Controller 

[Desktop-packages] [Bug 1792424] Re: Left panel flickers like crazy during several seconds after deleting a bunch of files

2019-04-04 Thread Cibin Joseph
Affects me too.

OS: Ubuntu 16.04
Nautilus version: 3.14.3
Architecture: amd64
CurrentDesktop: Unity
Date: Thu Apr 4 2019
Possible Trigger: Large amount of files in Trash folder and then executing 
'Empty Trash'.
Note: Flickering occurs during the time files are being removed from the 
~/.local/share/Trash folder and a large amount of files in the Trash folder 
requiring longer times to remove probably makes it noticeable.

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

Title:
  Left panel flickers like crazy during several seconds after deleting a
  bunch of files

Status in nautilus package in Ubuntu:
  Expired

Bug description:
  I have no idea if there are some requirements to trigger this issue,
  so I don't know whether you'll be able to reproduce it by just
  following my steps.

  Anyway, I can reproduce it 100% of the times:

  1. Open some folder in Nautilus
  2. Select a few files. Make sure you select quite a few
  3. Delete them by pressing the DEL key

  Expected:
  Nothing, a part from the files being deleted and disappearing from the 
displayed folder contents.

  Observed:
  During a few seconds after you hit Delete (I guess the time it takes to move 
the files to Trash and do some associated action, which by the way I don't know 
what it is that can take so long when deleting just a handful of files), the 
items in the list of shortcuts in the left panel (see screenshot) start 
flickering frantically, like crazy. It's pathetic.

  It looks like the item called "Networks", just below "Trash",
  disappears and reappears several times very quickly, causing all the
  items below it to move down and up, hence the flickering.

  Obviously it makes no sense.

  Note: there's nothing wrong to be appreciated in my screenshot, it
  just indicates where the flickering happens.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: nautilus 1:3.18.4.is.3.14.3-0ubuntu6
  ProcVersionSignature: Ubuntu 4.4.0-135.161-generic 4.4.140
  Uname: Linux 4.4.0-135-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Thu Sep 13 19:24:36 2018
  GsettingsChanges:
   b'org.gnome.nautilus.window-state' b'sidebar-width' b'190'
   b'org.gnome.nautilus.window-state' b'geometry' b"'1044x767+374+165'"
   b'org.gnome.nautilus.list-view' b'use-tree-view' b'true'
   b'org.gnome.nautilus.list-view' b'default-column-order' b"['name', 'size', 
'type', 'date_modified', 'date_accessed', 'owner', 'group', 'permissions', 
'mime_type', 'where']"
  InstallationDate: Installed on 2013-10-11 (1797 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  SourcePackage: nautilus
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1821264] Re: gnome-software from xps 13 9365 with Dell-oem running Ubuntu 16.04 segfaults

2019-04-04 Thread Jill Manfield
Customer installed U18.04 Dell OEM and that works as expected.  We can
drop the severity.  I installed the Base Dell OEM image to confirm the
issue.  When I first booted the issue was not there.  Then when I loaded
the updates/upgrades and rebooted the segfaults came back.  I have
nothing else installed on the image.  Let me know if you need me to redo
the valgrind, apptrace, and or backtraces.  Looks like this issue is
tied to U16

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

Title:
  gnome-software from xps 13 9365 with Dell-oem running Ubuntu 16.04
  segfaults

Status in gnome-software package in Ubuntu:
  New

Bug description:
  installing Dell Oem.
  Running update/upgrade
  sudo -s
  sudo apt-get update && sudo apt-get upgrade -y

  Then running gnome-software results in the GUI loading but after 10
  seconds it crashes and you see a segfault.

  I tried information in +Bug/1798236 but U16 does not have a later
  version of gnome-software.  I also saw a bug similar that mentioned we
  need packagekit 1.12 but U16 doesn't bundle that only U19 does.  I
  tried download a package for testing purposes but it does not resolve
  the issue.  I saw another case within our Dell database that suggests
  appstream might cause the crash so I removed appstream and did and
  update/upgrade again.  It stopped the crash initially but not on
  reboot.  I also added the gnome3 repository in hopes I could get the
  updates that way and that did not help either.

  It is unclear what is needed to resolve this issue.  Please let me
  know what logs you need me to provide to look into this further.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: gnome-software 3.20.5-0ubuntu0.16.04.11
  ProcVersionSignature: Ubuntu 4.15.0-47.50~16.04.1-generic 4.15.18
  Uname: Linux 4.15.0-47-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Thu Mar 21 19:11:27 2019
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-xenial-amd64-rebase-20170712-0
  InstallationDate: Installed on 2019-03-04 (17 days ago)
  InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 
20170712-02:34
  SourcePackage: gnome-software
  UpgradeStatus: No upgrade log present (probably fresh install)

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

-- 
Mailing list: https://launchpad.net/~desktop-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-04 Thread Ubuntu Kernel Bot
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
bionic' to 'verification-done-bionic'. If the problem still exists,
change the tag 'verification-needed-bionic' to 'verification-failed-
bionic'.

If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!

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

Title:
  Qualcomm Atheros QCA9377 wireless does not work

Status in linux package in Ubuntu:
  Fix Committed
Status in network-manager package in Ubuntu:
  Invalid
Status in linux source package in Bionic:
  Fix Committed
Status in network-manager source package in Bionic:
  Invalid
Status in linux source package in Cosmic:
  Fix Committed
Status in network-manager source package in Cosmic:
  Invalid

Bug description:
  === SRU Justification ===
  [Impact] 
  Lenovo ideapad 530S-14ARR Wifi rfkill hard blocked

  [Fix]
  The platform in question doesn't have hardware RF switch, so quirk it
  off.
   
  [Test]
  User confirm it fixes the issue.

  [Regression Potential]
  Minimal. This fix is limited to one specific platform.

  === Original Bug Report ===
  I have Lenovo 530s laptop with Qualcomm Atheros QCA9377 802.11ac Wireless 
Network Adapter (rev 31).

  The menu shows that wireless is off. Turning on the wireless from the
  menu does not do anything.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: network-manager 1.10.6-2ubuntu1.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
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Mar  1 11:42:34 2019
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2019-02-20 (8 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  IpRoute:
   default via 130.232.69.254 dev enx00e04c704f68 proto dhcp metric 100
   130.232.69.0/24 dev enx00e04c704f68 proto kernel scope link src 
130.232.69.176 metric 100
   169.254.0.0/16 dev virbr0 scope link metric 1000 linkdown
   192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1 
linkdown
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-con:
   NAMEUUID  TYPE  
TIMESTAMP   TIMESTAMP-REALAUTOCONNECT  AUTOCONNECT-PRIORITY 
 READONLY  DBUS-PATH   ACTIVE  DEVICE   
STATE  ACTIVE-PATH  SLAVE
   Wired connection 1  ada277fe-966d-33ff-aba2-8ba32d6ce5a9  ethernet  
155143  pe  1. maaliskuuta 2019 11.42.13  yes  4294966297   
 no/org/freedesktop/NetworkManager/Settings/1  yes enx00e04c704f68  
activated  /org/freedesktop/NetworkManager/ActiveConnection/11  --
   virbr0  dc46fe89-5b22-438a-85d5-37be48a077ea  bridge
155143  pe  1. maaliskuuta 2019 11.42.13  no   0
 no/org/freedesktop/NetworkManager/Settings/2  yes virbr0   
activated  /org/freedesktop/NetworkManager/ActiveConnection/1   --
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI  WWAN-HW  WWAN
   running  1.10.6   connected  started  full  enabled enabled  
disabled  enabled  enabled
  ---
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  sami   1315 F pulseaudio
   /dev/snd/controlC0:  sami   1315 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2019-02-20 (11 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  IpRoute:
   default via 130.232.69.254 dev enx00e04c704f68 proto dhcp metric 100
   130.232.69.0/24 dev enx00e04c704f68 proto kernel scope link src 
130.232.69.176 metric 100
   169.254.0.0/16 dev virbr0 scope link metric 1000 linkdown
   192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1 
linkdown
  MachineType: LENOVO 81H1
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  

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

2019-04-04 Thread Ubuntu Kernel Bot
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
cosmic' to 'verification-done-cosmic'. If the problem still exists,
change the tag 'verification-needed-cosmic' to 'verification-failed-
cosmic'.

If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!


** Tags added: verification-needed-cosmic

** Tags added: verification-needed-bionic

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

Title:
  Qualcomm Atheros QCA9377 wireless does not work

Status in linux package in Ubuntu:
  Fix Committed
Status in network-manager package in Ubuntu:
  Invalid
Status in linux source package in Bionic:
  Fix Committed
Status in network-manager source package in Bionic:
  Invalid
Status in linux source package in Cosmic:
  Fix Committed
Status in network-manager source package in Cosmic:
  Invalid

Bug description:
  === SRU Justification ===
  [Impact] 
  Lenovo ideapad 530S-14ARR Wifi rfkill hard blocked

  [Fix]
  The platform in question doesn't have hardware RF switch, so quirk it
  off.
   
  [Test]
  User confirm it fixes the issue.

  [Regression Potential]
  Minimal. This fix is limited to one specific platform.

  === Original Bug Report ===
  I have Lenovo 530s laptop with Qualcomm Atheros QCA9377 802.11ac Wireless 
Network Adapter (rev 31).

  The menu shows that wireless is off. Turning on the wireless from the
  menu does not do anything.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: network-manager 1.10.6-2ubuntu1.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
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Mar  1 11:42:34 2019
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2019-02-20 (8 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  IpRoute:
   default via 130.232.69.254 dev enx00e04c704f68 proto dhcp metric 100
   130.232.69.0/24 dev enx00e04c704f68 proto kernel scope link src 
130.232.69.176 metric 100
   169.254.0.0/16 dev virbr0 scope link metric 1000 linkdown
   192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1 
linkdown
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-con:
   NAMEUUID  TYPE  
TIMESTAMP   TIMESTAMP-REALAUTOCONNECT  AUTOCONNECT-PRIORITY 
 READONLY  DBUS-PATH   ACTIVE  DEVICE   
STATE  ACTIVE-PATH  SLAVE
   Wired connection 1  ada277fe-966d-33ff-aba2-8ba32d6ce5a9  ethernet  
155143  pe  1. maaliskuuta 2019 11.42.13  yes  4294966297   
 no/org/freedesktop/NetworkManager/Settings/1  yes enx00e04c704f68  
activated  /org/freedesktop/NetworkManager/ActiveConnection/11  --
   virbr0  dc46fe89-5b22-438a-85d5-37be48a077ea  bridge
155143  pe  1. maaliskuuta 2019 11.42.13  no   0
 no/org/freedesktop/NetworkManager/Settings/2  yes virbr0   
activated  /org/freedesktop/NetworkManager/ActiveConnection/1   --
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI  WWAN-HW  WWAN
   running  1.10.6   connected  started  full  enabled enabled  
disabled  enabled  enabled
  ---
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  sami   1315 F pulseaudio
   /dev/snd/controlC0:  sami   1315 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2019-02-20 (11 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  IpRoute:
   default via 130.232.69.254 dev enx00e04c704f68 proto dhcp metric 100
   130.232.69.0/24 dev enx00e04c704f68 proto kernel scope link src 
130.232.69.176 metric 100
   169.254.0.0/16 dev virbr0 scope link metric 1000 linkdown
   192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1 
linkdown
  MachineType: LENOVO 81H1
  

[Desktop-packages] [Bug 1822426] Re: 19.04 Built in Intel HDA sound is disabled upon resume

2019-04-04 Thread Cristian Măgherușan-Stanciu
Looks like my problem was unrelated to this issue, it was actually
caused by timidity blocking the physical sound device.

This workaround fixed it: https://askubuntu.com/questions/1085174/no-
sound-after-upgrade-to-18-10-only-a-dummy-device-is-shown

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

Title:
  19.04 Built in Intel HDA sound is disabled upon resume

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

Bug description:
  With 19.04, Intel Corporation 8 Series/C220 Series Chipset High
  Definition Audio Controller intermittently is not enabled when
  resuming from sleep. The HDMI sound device is enabled but that is not
  hooked up on my system.  New with 19.04, when sound works after
  resume, an icon labeled "Built in Audio Stereo" appears during the
  resume process.

  Unsure if this is related, but sound seems to sleep when not in use.
  Launching sound enabled apps produces a quiet "tick, thud" sound as
  sound system turns on.

  When sound is not working, killall pusleaudio "fixes" the issue.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: pulseaudio 1:12.2-2ubuntu1
  ProcVersionSignature: Ubuntu 5.0.0-8.9-generic 5.0.1
  Uname: Linux 5.0.0-8-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.10-0ubuntu23
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  darin  4814 F pulseaudio
   /dev/snd/controlC1:  darin  4814 F pulseaudio
   /dev/snd/controlC0:  darin  4814 F pulseaudio
  CurrentDesktop: KDE
  Date: Sat Mar 30 10:20:24 2019
  InstallationDate: Installed on 2018-01-13 (441 days ago)
  InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180112)
  SourcePackage: pulseaudio
  UpgradeStatus: Upgraded to disco on 2019-03-27 (3 days ago)
  dmi.bios.date: 08/18/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2103
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: Z87-PRO
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2103:bd08/18/2014:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ87-PRO:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.family: ASUS MB
  dmi.product.name: All Series
  dmi.product.sku: All
  dmi.product.version: System Version
  dmi.sys.vendor: ASUS

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

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


[Desktop-packages] [Bug 1821609] Re: lightdm login screen briefly appears and then blanks out on Intel(R) Core(TM)2 Duo CPU T5870 (using "foreign grub")

2019-04-04 Thread Derk Willem te Bokkel
whoops added the wrong attachment above it is the one including the
grub-update dialog .. instead of being the bot after the command

** Attachment added: "this one is after  the grub-update .. accidental switch"
   
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1821609/+attachment/5252871/+files/zl04-current3-sgrub-boot-apr4.log

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

Title:
  lightdm login screen briefly appears and then blanks out on Intel(R)
  Core(TM)2 Duo CPU T5870 (using "foreign grub")

Status in lightdm package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Incomplete
Status in xorg-server package in Ubuntu:
  Invalid

Bug description:
  Okay the has happened recently at least since march 18, 2019 iso and
  march 22, 2019 iso are both effected very similar to one of my
  previously reported bugs .. which was related to xorg not being
  installed ..

  
  back ground .. PC is lenovo sl 500 with evo860 SSD drive

  3 partions contain installs of disco sda1 -- main working system -- I
  usually install grub from here as master ..

  sda6 and sda7 are test installs of disco daily iso's 03-18-2019,
  03-22-2019 repectively

  
  on the test installs as long as the iso is using the grub boot loader 
installed from that install the system will boot normally .. the display manger 
tends to flicker on and off but does final start and login can proceed. 

  but if another install re-installs grub as master  the display manager
  fails to stay active or even come-up  for sda6 or sda7 only if their
  own grubs are reinstalled will they work normally

  sda1 display manager/xorg login works always no matter which "grub-
  source" is in control.

  if I use rescue boot from any grub as master I can get the displays to work 
by running dpkg fix which does nothing .. and then resuming the boot .. then 
things work normally..
  if the "non-rescue" boots are used the screen/computer locks and only a power 
down and reboot gives access. (sometime requiring radical depowering .. 
unpluging and removing battery)

  now the is a message that appears that RCs??? level is missing.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: xorg 1:7.7+19ubuntu11
  ProcVersionSignature: Ubuntu 5.0.0-7.8-generic 5.0.0
  Uname: Linux 5.0.0-7-generic x86_64
  ApportVersion: 2.20.10-0ubuntu23
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: XFCE
  Date: Mon Mar 25 11:25:58 2019
  DistUpgraded: Fresh install
  DistroCodename: disco
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GpuHangFrequency: Several times a day
  GpuHangReproducibility: Yes, I can easily reproduce it
  GpuHangStarted: Immediately after installing this version of Ubuntu
  GraphicsCard:
   Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller 
[8086:2a42] (rev 07) (prog-if 00 [VGA controller])
 Subsystem: Lenovo Mobile 4 Series Chipset Integrated Graphics Controller 
[17aa:20e4]
 Subsystem: Lenovo Mobile 4 Series Chipset Integrated Graphics Controller 
[17aa:20e4]
  InstallationDate: Installed on 2019-03-23 (1 days ago)
  InstallationMedia: Xubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190322)
  MachineType: LENOVO 2746CTO
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-7-generic 
root=UUID=1d61086d-275b-4537-bed5-f2d3080670eb ro recovery nomodeset
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/01/2010
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 6AET64WW
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: 2746CTO
  dmi.board.vendor: LENOVO
  dmi.board.version: LENOVO 6AET64WW
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: LENOVO 6AET64WW
  dmi.modalias: 
dmi:bvnLENOVO:bvr6AET64WW:bd12/01/2010:svnLENOVO:pn2746CTO:pvrThinkPadSL500:rvnLENOVO:rn2746CTO:rvrLENOVO6AET64WW:cvnLENOVO:ct10:cvrLENOVO6AET64WW:
  dmi.product.name: 2746CTO
  dmi.product.version: ThinkPad SL500
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.97-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.0-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  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/lightdm/+bug/1821609/+subscriptions

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

[Desktop-packages] [Bug 1729077] Re: wrong color of horizontally centered area of scan with CanoScan Lide 200

2019-04-04 Thread Metal Matze
*** This bug is a duplicate of bug 1731459 ***
https://bugs.launchpad.net/bugs/1731459

I have the same problem with the Canon LiDe 100

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

Title:
  wrong color of horizontally centered area of scan with CanoScan Lide
  200

Status in sane-backends:
  New
Status in sane-backends package in Ubuntu:
  Confirmed

Bug description:
  This problem is 100% reproducable, also across reboots.

  On a Ubuntu 16.04 and 17.04 and Windows7 system the Scanner CanoScan
  Lide 200 works still completely fine.

  Problem with Ubuntu 17.10 :
  In a horizontally centered zone of about 1 centimeter width of the scan 
surface, over the full height of the surface, estimated 90% of the pixel values 
are completely wrong.
  The distribution of the wrong pixels in this zone appears random.
  With lineart and gray scan, the wrong pixels are black. With color scan, the 
wrong pixels are black or similar to red. The other pixels in the zone are a 
bit too bright. The effect is the same at all resolutions. See attached example 
snippets. The effect would continue vertically over the entire scan surface. 
The original was uniformly colored.

  The scanner worked again with Ubuntu 17.10 after purging sane-
  utils,libsane1,libsane-common (by overriding dependency-errors) and
  installing libsane-common_1.0.25+git20150528-1ubuntu4_all.deb
  libsane_1.0.25+git20150528-1ubuntu4_amd64.deb sane-
  utils_1.0.25+git20150528-1ubuntu4_amd64.deb (again by overriding
  dependency-errors) (and maybe re-plug scanner / reboot)

  Trying these versions had the same problem as default Ubuntu 17.10:
  archive.ubuntu.com : 1.0.27-1~experimental2ubuntu2.1, 
launchpad.net/~rolfbensch/+archive/ubuntu/sane-git : 1.0.27+git20171012-artful0

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: libsane1 1.0.27-1~experimental2ubuntu1
  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.1
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Tue Oct 31 20:48:39 2017
  InstallationDate: Installed on 2015-12-31 (670 days ago)
  InstallationMedia: Xubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  SourcePackage: sane-backends
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1821609] Re: lightdm login screen briefly appears and then blanks out on Intel(R) Core(TM)2 Duo CPU T5870 (using "foreign grub")

2019-04-04 Thread Derk Willem te Bokkel
okay generated the default grub.cfg via sda6 grub-install boot instance
.. vt.handle=1 is set by default for self root boot about a minute to
boot

 no change .. still no plymouth on boot but there is a flicker with
lightdm .. which restarts once video mode switch has happened ..


note all grub installs use the same command line: sudo grub-install /dev/sda  
only the source partition varies .. 

again .. any more ideas why the newer iso's fail?


I've skipped posting the boot between for sudo update-grub .. but I did save 
the log .. it has all the update-grub action recorded .. any use? I can post it.

** Attachment added: "zlink4 /sda6 self grub boot log - with default 
grub-update grub.cfg"
   
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1821609/+attachment/5252856/+files/zl04-sgrub-current2-apr4boot.log

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

Title:
  lightdm login screen briefly appears and then blanks out on Intel(R)
  Core(TM)2 Duo CPU T5870 (using "foreign grub")

Status in lightdm package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Incomplete
Status in xorg-server package in Ubuntu:
  Invalid

Bug description:
  Okay the has happened recently at least since march 18, 2019 iso and
  march 22, 2019 iso are both effected very similar to one of my
  previously reported bugs .. which was related to xorg not being
  installed ..

  
  back ground .. PC is lenovo sl 500 with evo860 SSD drive

  3 partions contain installs of disco sda1 -- main working system -- I
  usually install grub from here as master ..

  sda6 and sda7 are test installs of disco daily iso's 03-18-2019,
  03-22-2019 repectively

  
  on the test installs as long as the iso is using the grub boot loader 
installed from that install the system will boot normally .. the display manger 
tends to flicker on and off but does final start and login can proceed. 

  but if another install re-installs grub as master  the display manager
  fails to stay active or even come-up  for sda6 or sda7 only if their
  own grubs are reinstalled will they work normally

  sda1 display manager/xorg login works always no matter which "grub-
  source" is in control.

  if I use rescue boot from any grub as master I can get the displays to work 
by running dpkg fix which does nothing .. and then resuming the boot .. then 
things work normally..
  if the "non-rescue" boots are used the screen/computer locks and only a power 
down and reboot gives access. (sometime requiring radical depowering .. 
unpluging and removing battery)

  now the is a message that appears that RCs??? level is missing.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: xorg 1:7.7+19ubuntu11
  ProcVersionSignature: Ubuntu 5.0.0-7.8-generic 5.0.0
  Uname: Linux 5.0.0-7-generic x86_64
  ApportVersion: 2.20.10-0ubuntu23
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: XFCE
  Date: Mon Mar 25 11:25:58 2019
  DistUpgraded: Fresh install
  DistroCodename: disco
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GpuHangFrequency: Several times a day
  GpuHangReproducibility: Yes, I can easily reproduce it
  GpuHangStarted: Immediately after installing this version of Ubuntu
  GraphicsCard:
   Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller 
[8086:2a42] (rev 07) (prog-if 00 [VGA controller])
 Subsystem: Lenovo Mobile 4 Series Chipset Integrated Graphics Controller 
[17aa:20e4]
 Subsystem: Lenovo Mobile 4 Series Chipset Integrated Graphics Controller 
[17aa:20e4]
  InstallationDate: Installed on 2019-03-23 (1 days ago)
  InstallationMedia: Xubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190322)
  MachineType: LENOVO 2746CTO
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-7-generic 
root=UUID=1d61086d-275b-4537-bed5-f2d3080670eb ro recovery nomodeset
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/01/2010
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 6AET64WW
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: 2746CTO
  dmi.board.vendor: LENOVO
  dmi.board.version: LENOVO 6AET64WW
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: LENOVO 6AET64WW
  dmi.modalias: 
dmi:bvnLENOVO:bvr6AET64WW:bd12/01/2010:svnLENOVO:pn2746CTO:pvrThinkPadSL500:rvnLENOVO:rn2746CTO:rvrLENOVO6AET64WW:cvnLENOVO:ct10:cvrLENOVO6AET64WW:
  dmi.product.name: 2746CTO
  dmi.product.version: ThinkPad SL500
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.97-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.0-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu2
  

[Desktop-packages] [Bug 1822839]

2019-04-04 Thread Olivier Tilloy
Similar distro-patch for Ubuntu:
https://git.launchpad.net/~libreoffice/ubuntu/+source/libreoffice/tree/patches/java
.vendor-Ubuntu.patch?h=ubuntu-disco-6.2

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

Title:
  LibreOffice doesn't detect JVM because of unexpected java.vendor
  property value

Status in LibreOffice:
  Confirmed
Status in libreoffice package in Ubuntu:
  In Progress
Status in openjdk-lts package in Ubuntu:
  New
Status in libreoffice package in Debian:
  New

Bug description:
  libreoffice autopkgtests are failing on disco with openjdk
  11.0.3+4-2ubuntu1.

  The likely culprit is that change:

  +openjdk-lts (11.0.3+4-2ubuntu1) disco; urgency=medium
  +
  +  * Sync packages with 11.0.3+4-2:
  +[ Matthias Klose ]
  +- Configure with vendor flags.

  Indeed with version 11.0.3+4-1ubuntu1:

  $ java -XshowSettings -version 2>&1 | grep "java.vendor "
  java.vendor = Oracle Corporation

  And with version 11.0.3+4-2ubuntu1:

  $ java -XshowSettings -version 2>&1 | grep "java.vendor "
  java.vendor = Private Build

  Looking at the code in Libreoffice that looks for a JVM, it validates
  the vendor against a hardcoded list of known vendors:
  
https://cgit.freedesktop.org/libreoffice/core/tree/jvmfwk/plugins/sunmajor/pluginlib/vendorlist.cxx?h=libreoffice-6-2#n33

  Not sure what the purpose of that upstream code is, but this means the
  new openjdk-11 build in Ubuntu breaks it.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: openjdk-11-jre-headless 11.0.3+4-2ubuntu1
  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-0ubuntu23
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Apr  2 17:06:25 2019
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2016-07-02 (1003 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  SourcePackage: openjdk-lts
  UpgradeStatus: Upgraded to disco on 2019-03-16 (16 days ago)

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

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


[Desktop-packages] [Bug 1823110] Re: Screen not resized when rotating 90*

2019-04-04 Thread Brian Murray
This may be a duplicate of bug 1822513.

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

Title:
  Screen not resized when rotating 90*

Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  Running 19.04 beta on a Microsoft Surface Pro 3.
  Screen resolution 2160x1440 works in normal landscape mode (Docked mode) 
however if I rotate the device 90* clockwise or counter-clockwise, the screen 
resolution doesn't change to 1440x2160. The screen actually rotates however it 
hasn't flipped the dimensions to fit.
  This was previously working on Ubuntu 18.10.

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

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


[Desktop-packages] [Bug 1822478] Re: [regression][nvidia] All on screen text is tiny. Icons are normal size but text is nearly unreadable.

2019-04-04 Thread Alberto Milone
I can't reproduce the problem here on my nvidia system with the 418
driver.

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

Title:
  [regression][nvidia] All on screen text is tiny. Icons are normal size
  but text is nearly unreadable.

Status in gnome-shell package in Ubuntu:
  Triaged
Status in mutter package in Ubuntu:
  Triaged
Status in nvidia-graphics-drivers-418 package in Ubuntu:
  Confirmed
Status in gnome-shell source package in Disco:
  Triaged
Status in mutter source package in Disco:
  Triaged
Status in nvidia-graphics-drivers-418 source package in Disco:
  Confirmed

Bug description:
  Recently upgraded to Disco beta.

  Running a 1080p screen at 100% scaling.

  uname -a  :
  Linux giga 5.0.0-8-generic #9-Ubuntu SMP Tue Mar 12 21:58:11 UTC 2019 x86_64 
x86_64 x86_64 GNU/Linux

  Graphics card : GeForce GT 710/PCIe/SSE2
  Drivers version:  Nvidia-Driver-418

  
  Not 100% sure this is a Gnome-Shell issue (Not sure if this is the correct 
package to log it against) or an "Idiot User" issue. As I've upgraded this 
system for the past 3 releases (18.02, 18.10 & 19.04 beta) without a clean 
install between upgrades.

  When I reboot, all on screen text is tiny. Icons are normal size but text is 
nearly unreadable. This also effects any text input boxes (i.e. user password)
  Text in "Show Applications" screen is also effected.

  *Workaroud*

  Only work around for the desktop is to go in to "Settings" then
  "Devices" then Adjust the scaling to 200%, hit Apply, then press
  "Revert Changes", this resets the scaling to normal.

  This does not fix the scaling in the "Show Applications" screen.

  Attached images in Scaling_Issues.zip :
  Image of text scaling after reboot : Scaling_Small.png
  Image after the "workaround" to show how it should look like: 
Scaling_Normal.png
  Image of "Show Applications" screen which is still effected : 
Applications_Small.png

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: gnome-shell 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 nvidia_modeset 
nvidia
  ApportVersion: 2.20.10-0ubuntu23
  Architecture: amd64
  Date: Sun Mar 31 16:00:21 2019
  DisplayManager: gdm3
  GsettingsChanges:
   b'org.gnome.shell' b'app-picker-view' b'uint32 1'
   b'org.gnome.shell' b'favorite-apps' redacted by apport
   b'org.gnome.shell' b'enabled-extensions' b"['ubuntu-d...@ubuntu.com', 
'ubuntu-appindicat...@ubuntu.com', 'openweather-extens...@jenslody.de', 
'desktop-icons@csoriano']"
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
  InstallationDate: Installed on 2018-07-09 (264 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to disco on 2019-03-29 (1 days ago)

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

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


[Desktop-packages] [Bug 1424201] Re: Web browsers lacking hardware-accelerated video decoding

2019-04-04 Thread Olivier Tilloy
The vaapi-enabled snap currently lives in the candidate/vaapi channel,
which was automatically closed due to lack of updates, but an update
bringing it to the latest stable version is pending publication, so it
will soon be re-opened and available.

Once confirmed this works as expected, I plan to merge this branch into
the stable one, at which point a separate channel won't be required.

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

Title:
  Web browsers lacking hardware-accelerated video decoding

Status in Chromium Browser:
  Unknown
Status in Mozilla Firefox:
  New
Status in chromium-browser package in Ubuntu:
  Confirmed
Status in firefox package in Ubuntu:
  Confirmed
Status in chromium-browser package in CentOS:
  Unknown

Bug description:
  The chromium team has done a great job to totally disable hardware
  decoding on Linux.

  Even ignoring the GPU blacklist does not enable GPU decoding.

  How ever the patch is quite simple and it's already working using this
  PPA ( using libVA ) :

  https://launchpad.net/~saiarcot895/+archive/ubuntu/chromium-dev

  the corresponding patch is here :

  http://bazaar.launchpad.net/~saiarcot895/chromium-browser/chromium-
  browser.trusty.beta/view/head:/debian/patches/enable_vaapi_on_linux.diff

  that would be great if we could have this patch indefault Ubuntu
  chromium build, this situation is really sad right now, google use
  linux to make chromeOS so chromebook are really good at playing videos
  but GNU/Linux chromium is slow at doing it.

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

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


[Desktop-packages] [Bug 1823175] Re: battery status shows "estimating" when fully charged

2019-04-04 Thread Mohammad Kazemi
** Description changed:

  My battery is fully charged and it shows 100%. When it's connected connected 
to charger, Battery symbol changes to battery-missing-symbol. It also shows 
"Estimating..." for time remaining.
  I'm using "Asus VivoBook x510uf"
  My battery status when connected to AC power:
  
  $ upower -d
  Device: /org/freedesktop/UPower/devices/line_power_AC0
    native-path:  AC0
    power supply: yes
    updated:  Thu 04 Apr 2019 08:26:58 PM +0430 (-11482 seconds ago)
    has history:  no
    has statistics:   no
    line-power
  warning-level:   none
  online:  yes
  icon-name:  'ac-adapter-symbolic'
  
  Device: /org/freedesktop/UPower/devices/battery_BAT0
    native-path:  BAT0
    vendor:   ASUSTeK
    model:ASUS Battery
    power supply: yes
    updated:  Thu 04 Apr 2019 05:14:53 PM +0430 (43 seconds ago)
    has history:  yes
    has statistics:   yes
    battery
  present: yes
  rechargeable:yes
  state:   pending-charge
  warning-level:   none
  energy:  40.367 Wh
  energy-empty:0 Wh
  energy-full: 40.367 Wh
  energy-full-design:  43.046 Wh
  energy-rate: 0 W
  voltage: 11.55 V
  percentage:  100%
  capacity:93.7764%
  technology:  lithium-ion
  icon-name:  'battery-full-charging-symbolic'
    History (charge):
  15543934180.000   unknown
    History (rate):
  15543934180.000   unknown
  
  Device: /org/freedesktop/UPower/devices/DisplayDevice
    power supply: yes
    updated:  Thu 04 Apr 2019 08:26:58 PM +0430 (-11482 seconds ago)
    has history:  no
    has statistics:   no
    battery
  present: yes
  state:   unknown
  warning-level:   none
  energy:  40.367 Wh
  energy-full: 40.367 Wh
  energy-rate: 0 W
  percentage:  100%
  icon-name:  'battery-missing-symbolic'
  
  Daemon:
    daemon-version:  0.99.7
    on-battery:  no
    lid-is-closed:   no
    lid-is-present:  yes
    critical-action: HybridSleep
  
+ -
+ 
  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.28.3-0ubuntu0.18.04.4
  ProcVersionSignature: Ubuntu 4.18.0-17.18~18.04.1-generic 4.18.20
  Uname: Linux 4.18.0-17-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Apr  4 17:04:22 2019
  DisplayManager: gdm3
  InstallationDate: Installed on 2019-03-30 (4 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

** Description changed:

- My battery is fully charged and it shows 100%. When it's connected connected 
to charger, Battery symbol changes to battery-missing-symbol. It also shows 
"Estimating..." for time remaining.
+ My battery is fully charged and it shows 100%. When it's connected to 
charger, Battery symbol changes to battery-missing-symbol. It also shows 
"Estimating..." for time remaining.
  I'm using "Asus VivoBook x510uf"
  My battery status when connected to AC power:
  
  $ upower -d
  Device: /org/freedesktop/UPower/devices/line_power_AC0
    native-path:  AC0
    power supply: yes
    updated:  Thu 04 Apr 2019 08:26:58 PM +0430 (-11482 seconds ago)
    has history:  no
    has statistics:   no
    line-power
  warning-level:   none
  online:  yes
  icon-name:  'ac-adapter-symbolic'
  
  Device: /org/freedesktop/UPower/devices/battery_BAT0
    native-path:  BAT0
    vendor:   ASUSTeK
    model:ASUS Battery
    power supply: yes
    updated:  Thu 04 Apr 2019 05:14:53 PM +0430 (43 seconds ago)
    has history:  yes
    has statistics:   yes
    battery
  present: yes
  rechargeable:yes
  state:   pending-charge
  warning-level:   none
  energy:  40.367 Wh
  energy-empty:0 Wh
  energy-full: 40.367 Wh
  energy-full-design:  43.046 Wh
  energy-rate: 0 W
  voltage: 11.55 V
  percentage:  100%
  capacity:93.7764%
  technology:  lithium-ion
  icon-name:  'battery-full-charging-symbolic'
    History (charge):
  15543934180.000   unknown
    History (rate):
  15543934180.000   unknown
  
  Device: /org/freedesktop/UPower/devices/DisplayDevice
    power supply: yes
    updated:  Thu 04 Apr 2019 08:26:58 PM +0430 (-11482 seconds ago)
    has 

[Desktop-packages] [Bug 1821609] Re: lightdm login screen briefly appears and then blanks out on Intel(R) Core(TM)2 Duo CPU T5870 (using "foreign grub")

2019-04-04 Thread Derk Willem te Bokkel
here is the journalctl boot log for sda6 /zlink4 booted by it's own
install of grub (self grub)

(it was reinstalled for this purpose  .. to show it works .. however
plymouth does not show on the screen at all on boot but does on shutdown
)

now one change is addition of a vt.handoff=1 to the end of the grub entry 
(originally a $vt_handoff)   i'll shortly revert this and regenerate this log 
again.. 

size is about same as zlink1 version also about 1 minute long

note every problem boot has a much shorter journalctl boot log..why?

some stuff is not getting done .. only because the source of the grub-
install has changed and the controlling partition grub.cfg used instead
..   ??

these are generic auto-generated by update-grub .. so why the different
behaviours





** Attachment added: "zlink4 / sda6 boot log -- self grub boot"
   
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1821609/+attachment/5252840/+files/zl04-apr-4-sgrub-currentboot.log

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

Title:
  lightdm login screen briefly appears and then blanks out on Intel(R)
  Core(TM)2 Duo CPU T5870 (using "foreign grub")

Status in lightdm package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Incomplete
Status in xorg-server package in Ubuntu:
  Invalid

Bug description:
  Okay the has happened recently at least since march 18, 2019 iso and
  march 22, 2019 iso are both effected very similar to one of my
  previously reported bugs .. which was related to xorg not being
  installed ..

  
  back ground .. PC is lenovo sl 500 with evo860 SSD drive

  3 partions contain installs of disco sda1 -- main working system -- I
  usually install grub from here as master ..

  sda6 and sda7 are test installs of disco daily iso's 03-18-2019,
  03-22-2019 repectively

  
  on the test installs as long as the iso is using the grub boot loader 
installed from that install the system will boot normally .. the display manger 
tends to flicker on and off but does final start and login can proceed. 

  but if another install re-installs grub as master  the display manager
  fails to stay active or even come-up  for sda6 or sda7 only if their
  own grubs are reinstalled will they work normally

  sda1 display manager/xorg login works always no matter which "grub-
  source" is in control.

  if I use rescue boot from any grub as master I can get the displays to work 
by running dpkg fix which does nothing .. and then resuming the boot .. then 
things work normally..
  if the "non-rescue" boots are used the screen/computer locks and only a power 
down and reboot gives access. (sometime requiring radical depowering .. 
unpluging and removing battery)

  now the is a message that appears that RCs??? level is missing.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: xorg 1:7.7+19ubuntu11
  ProcVersionSignature: Ubuntu 5.0.0-7.8-generic 5.0.0
  Uname: Linux 5.0.0-7-generic x86_64
  ApportVersion: 2.20.10-0ubuntu23
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: XFCE
  Date: Mon Mar 25 11:25:58 2019
  DistUpgraded: Fresh install
  DistroCodename: disco
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GpuHangFrequency: Several times a day
  GpuHangReproducibility: Yes, I can easily reproduce it
  GpuHangStarted: Immediately after installing this version of Ubuntu
  GraphicsCard:
   Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller 
[8086:2a42] (rev 07) (prog-if 00 [VGA controller])
 Subsystem: Lenovo Mobile 4 Series Chipset Integrated Graphics Controller 
[17aa:20e4]
 Subsystem: Lenovo Mobile 4 Series Chipset Integrated Graphics Controller 
[17aa:20e4]
  InstallationDate: Installed on 2019-03-23 (1 days ago)
  InstallationMedia: Xubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190322)
  MachineType: LENOVO 2746CTO
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-7-generic 
root=UUID=1d61086d-275b-4537-bed5-f2d3080670eb ro recovery nomodeset
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/01/2010
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 6AET64WW
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: 2746CTO
  dmi.board.vendor: LENOVO
  dmi.board.version: LENOVO 6AET64WW
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: LENOVO 6AET64WW
  dmi.modalias: 
dmi:bvnLENOVO:bvr6AET64WW:bd12/01/2010:svnLENOVO:pn2746CTO:pvrThinkPadSL500:rvnLENOVO:rn2746CTO:rvrLENOVO6AET64WW:cvnLENOVO:ct10:cvrLENOVO6AET64WW:
  dmi.product.name: 2746CTO
  dmi.product.version: ThinkPad SL500
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.97-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.0-1ubuntu1

[Desktop-packages] [Bug 1821609] Re: lightdm login screen briefly appears and then blanks out on Intel(R) Core(TM)2 Duo CPU T5870 (using "foreign grub")

2019-04-04 Thread Derk Willem te Bokkel
here we have a normal journalctl boot log .. notice the size .. more
entries .. about 1 minute start to finish source the partition that
always works lightdm starts normally plymouth appears on screen etc.

this one was booted by grub installed by zlink4 - on sda6 ..

** Attachment added: "zlink1 / sda1 .. booted from foreign grub .. installed by 
 zl04/sda6"
   
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1821609/+attachment/5252838/+files/zl01-current-04-04fg-zl04boot.log

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

Title:
  lightdm login screen briefly appears and then blanks out on Intel(R)
  Core(TM)2 Duo CPU T5870 (using "foreign grub")

Status in lightdm package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Incomplete
Status in xorg-server package in Ubuntu:
  Invalid

Bug description:
  Okay the has happened recently at least since march 18, 2019 iso and
  march 22, 2019 iso are both effected very similar to one of my
  previously reported bugs .. which was related to xorg not being
  installed ..

  
  back ground .. PC is lenovo sl 500 with evo860 SSD drive

  3 partions contain installs of disco sda1 -- main working system -- I
  usually install grub from here as master ..

  sda6 and sda7 are test installs of disco daily iso's 03-18-2019,
  03-22-2019 repectively

  
  on the test installs as long as the iso is using the grub boot loader 
installed from that install the system will boot normally .. the display manger 
tends to flicker on and off but does final start and login can proceed. 

  but if another install re-installs grub as master  the display manager
  fails to stay active or even come-up  for sda6 or sda7 only if their
  own grubs are reinstalled will they work normally

  sda1 display manager/xorg login works always no matter which "grub-
  source" is in control.

  if I use rescue boot from any grub as master I can get the displays to work 
by running dpkg fix which does nothing .. and then resuming the boot .. then 
things work normally..
  if the "non-rescue" boots are used the screen/computer locks and only a power 
down and reboot gives access. (sometime requiring radical depowering .. 
unpluging and removing battery)

  now the is a message that appears that RCs??? level is missing.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: xorg 1:7.7+19ubuntu11
  ProcVersionSignature: Ubuntu 5.0.0-7.8-generic 5.0.0
  Uname: Linux 5.0.0-7-generic x86_64
  ApportVersion: 2.20.10-0ubuntu23
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: XFCE
  Date: Mon Mar 25 11:25:58 2019
  DistUpgraded: Fresh install
  DistroCodename: disco
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GpuHangFrequency: Several times a day
  GpuHangReproducibility: Yes, I can easily reproduce it
  GpuHangStarted: Immediately after installing this version of Ubuntu
  GraphicsCard:
   Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller 
[8086:2a42] (rev 07) (prog-if 00 [VGA controller])
 Subsystem: Lenovo Mobile 4 Series Chipset Integrated Graphics Controller 
[17aa:20e4]
 Subsystem: Lenovo Mobile 4 Series Chipset Integrated Graphics Controller 
[17aa:20e4]
  InstallationDate: Installed on 2019-03-23 (1 days ago)
  InstallationMedia: Xubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190322)
  MachineType: LENOVO 2746CTO
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-7-generic 
root=UUID=1d61086d-275b-4537-bed5-f2d3080670eb ro recovery nomodeset
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/01/2010
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 6AET64WW
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: 2746CTO
  dmi.board.vendor: LENOVO
  dmi.board.version: LENOVO 6AET64WW
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: LENOVO 6AET64WW
  dmi.modalias: 
dmi:bvnLENOVO:bvr6AET64WW:bd12/01/2010:svnLENOVO:pn2746CTO:pvrThinkPadSL500:rvnLENOVO:rn2746CTO:rvrLENOVO6AET64WW:cvnLENOVO:ct10:cvrLENOVO6AET64WW:
  dmi.product.name: 2746CTO
  dmi.product.version: ThinkPad SL500
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.97-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.0-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

To manage notifications about this bug go to:

[Desktop-packages] [Bug 1823194] Re: Windows share (CIFS) mounted over gvfs (by tool Files) is about 10 times slower than mounted by mount -t cifs

2019-04-04 Thread Josef Mašek
Problem is not in gvfs.
I found that I am connected to the same network by the 1 Gigabit copper 
interface and by the wireless. When I used mount, traffic went through 1 Gbit 
copper, when I used gvfs, traffic went by Wireless (~100 Mbit).
Maybe is issue of the network manager?

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

Title:
  Windows share (CIFS) mounted over gvfs (by tool Files) is about 10
  times slower than mounted by mount -t cifs

Status in gvfs package in Ubuntu:
  New

Bug description:
  Copying data by Files says 5MB/s - when I use "Files" and I mounted
  windows share (from Freenas 9.x stable) and copy to local disk (also
  by Files).

  When I use "old way" 
  in /etc/fstab is:
  //192.168.x.x/public  /media/netio  cifs  noauto,guest,iocharset=utf8
  mount /medi/netio
  and copy files by any tool (also files), it tooks about 1,5 hours and 44 MB/s.

  I am copying 170 GB and by gvfs it tooks about 9 hours - more than
  working day, by mount and copy only 1,5 hour.

  I have updated 18.04, packages:

  In Ubuntu 16.04 gvfs and mount worked almost the same speed.

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

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


[Desktop-packages] [Bug 1236619] Re: gvfs smb / cifs file copy performance is terribly slow

2019-04-04 Thread Josef Mašek
Problem in my case found - I am connected to the same network by the 1
Gigabit copper interface and by the wireless. When I used mount, traffic
wen through 1 Gbit copper, when I used gvfs, traffic went by Wireless
(~100 Mbit)

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

Title:
  gvfs smb / cifs file copy performance is terribly slow

Status in gvfs package in Ubuntu:
  Confirmed

Bug description:
  Copying moderate-size files to a samba share using gvfs is
  ridiculously slow compared to doing the same via mount.cifs.  For
  example:

  $ ls -sh testfile
  1.2G testfile
  $ time cp testfile ~/mnt/share-gvfs/
  real  2m37.053s
  user  0m0.056s
  sys   0m5.120s
  $ time cp testfile ~/mnt/share/
  real  0m26.134s
  user  0m0.004s
  sys   0m1.724s

  I'm running Xubuntu 13.04 (raring) amd64, gvfs 1.16.1-0ubuntu1.1.

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

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


[Desktop-packages] [Bug 1822184] Re: clear_console locks up video when X is running and you log out from a plain text console

2019-04-04 Thread Quesar
Thanks!  This also affects 18.04 and will need to be fixed there too
please.

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

Title:
  clear_console locks up video when X is running and you log out from a
  plain text console

Status in X.Org X server:
  New
Status in bash package in Ubuntu:
  Fix Released
Status in xorg-server package in Ubuntu:
  Confirmed
Status in xorg package in Debian:
  New
Status in xorg-server package in Debian:
  Confirmed

Bug description:
  References:
  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=810660
  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=866898

  
  If X is running and you switch to a plain text console (ie ctrl-alt-f3), log 
in as a regular user, and then log out, the display switches back to the 
graphical login screen and locks up.  The system is still functioning (can ssh 
in, etc) but the video output is frozen.

  The underlying cause is:
  https://gitlab.freedesktop.org/xorg/xserver/issues/492

  However, the problem can at least be worked around by making
  clear_console switch to tty 6 and back instead of switching to 1 and
  back.  This patch corrects the problem:

  
  --- bash-4.4.18.orig/debian/clear_console.c 2019-03-28 12:09:02.415907787 
-0400
  +++ bash-4.4.18/debian/clear_console.c  2019-03-28 12:08:11.984366858 -0400
  @@ -205,7 +205,7 @@
   #if defined(__linux__)
 num = vtstat.v_active;
   #endif
  -  tmp_num = (num == 1 ? 2 : 1);
  +  tmp_num = (num == 6 ? 5 : 6);
   
 /* switch vt to clear the scrollback buffer */
 if (ioctl(fd, VT_ACTIVATE, tmp_num))

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

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


[Desktop-packages] [Bug 1424201] Re: Web browsers lacking hardware-accelerated video decoding

2019-04-04 Thread Chris Cheney
wrt #91 which snaps might those be?

If its the regular 'chromium' snap it certainly doesn't make any mention
of the fact it supports hardware video acceleration or includes the
vaapi patch.


# snap info chromium
name:  chromium
summary:   Chromium web browser, open-source version of Chrome
publisher: Canonical✓
contact:   
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bugs?field.tag=snap
license:   Apache-2.0 AND BSD-3-Clause AND LGPL-2.0 AND LGPL-2.1 AND MIT AND 
MS-PL AND (GPL-2.0+ OR LGPL-2.1+ OR MPL-1.1)
description: |
  An open-source browser project that aims to build a safer, faster, and more 
stable way for all
  Internet users to experience the web.
snap-id: XKEcBqPM06H1Z7zGOdG5fbICuf8NWK5R
channels:
  stable:73.0.3683.75 2019-03-14 (660) 161MB -
  candidate: 73.0.3683.75 2019-03-13 (660) 161MB -
  beta:  73.0.3683.75 2019-03-13 (660) 161MB -
  edge:  74.0.3729.22 2019-03-20 (667) 162MB -

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

Title:
  Web browsers lacking hardware-accelerated video decoding

Status in Chromium Browser:
  Unknown
Status in Mozilla Firefox:
  New
Status in chromium-browser package in Ubuntu:
  Confirmed
Status in firefox package in Ubuntu:
  Confirmed
Status in chromium-browser package in CentOS:
  Unknown

Bug description:
  The chromium team has done a great job to totally disable hardware
  decoding on Linux.

  Even ignoring the GPU blacklist does not enable GPU decoding.

  How ever the patch is quite simple and it's already working using this
  PPA ( using libVA ) :

  https://launchpad.net/~saiarcot895/+archive/ubuntu/chromium-dev

  the corresponding patch is here :

  http://bazaar.launchpad.net/~saiarcot895/chromium-browser/chromium-
  browser.trusty.beta/view/head:/debian/patches/enable_vaapi_on_linux.diff

  that would be great if we could have this patch indefault Ubuntu
  chromium build, this situation is really sad right now, google use
  linux to make chromeOS so chromebook are really good at playing videos
  but GNU/Linux chromium is slow at doing it.

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

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


[Desktop-packages] [Bug 1821609] Re: lightdm login screen briefly appears and then blanks out on Intel(R) Core(TM)2 Duo CPU T5870 (using "foreign grub")

2019-04-04 Thread Derk Willem te Bokkel
** Summary changed:

- lightdm login screen briefly appears and then blanks out on Intel(R) 
Core(TM)2 Duo CPU T5870 - failure to load i915 kernel module
+ lightdm login screen briefly appears and then blanks out on Intel(R) 
Core(TM)2 Duo CPU T5870 (using "foreign grub")

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

Title:
  lightdm login screen briefly appears and then blanks out on Intel(R)
  Core(TM)2 Duo CPU T5870 (using "foreign grub")

Status in lightdm package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Incomplete
Status in xorg-server package in Ubuntu:
  Invalid

Bug description:
  Okay the has happened recently at least since march 18, 2019 iso and
  march 22, 2019 iso are both effected very similar to one of my
  previously reported bugs .. which was related to xorg not being
  installed ..

  
  back ground .. PC is lenovo sl 500 with evo860 SSD drive

  3 partions contain installs of disco sda1 -- main working system -- I
  usually install grub from here as master ..

  sda6 and sda7 are test installs of disco daily iso's 03-18-2019,
  03-22-2019 repectively

  
  on the test installs as long as the iso is using the grub boot loader 
installed from that install the system will boot normally .. the display manger 
tends to flicker on and off but does final start and login can proceed. 

  but if another install re-installs grub as master  the display manager
  fails to stay active or even come-up  for sda6 or sda7 only if their
  own grubs are reinstalled will they work normally

  sda1 display manager/xorg login works always no matter which "grub-
  source" is in control.

  if I use rescue boot from any grub as master I can get the displays to work 
by running dpkg fix which does nothing .. and then resuming the boot .. then 
things work normally..
  if the "non-rescue" boots are used the screen/computer locks and only a power 
down and reboot gives access. (sometime requiring radical depowering .. 
unpluging and removing battery)

  now the is a message that appears that RCs??? level is missing.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: xorg 1:7.7+19ubuntu11
  ProcVersionSignature: Ubuntu 5.0.0-7.8-generic 5.0.0
  Uname: Linux 5.0.0-7-generic x86_64
  ApportVersion: 2.20.10-0ubuntu23
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: XFCE
  Date: Mon Mar 25 11:25:58 2019
  DistUpgraded: Fresh install
  DistroCodename: disco
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GpuHangFrequency: Several times a day
  GpuHangReproducibility: Yes, I can easily reproduce it
  GpuHangStarted: Immediately after installing this version of Ubuntu
  GraphicsCard:
   Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller 
[8086:2a42] (rev 07) (prog-if 00 [VGA controller])
 Subsystem: Lenovo Mobile 4 Series Chipset Integrated Graphics Controller 
[17aa:20e4]
 Subsystem: Lenovo Mobile 4 Series Chipset Integrated Graphics Controller 
[17aa:20e4]
  InstallationDate: Installed on 2019-03-23 (1 days ago)
  InstallationMedia: Xubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190322)
  MachineType: LENOVO 2746CTO
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-7-generic 
root=UUID=1d61086d-275b-4537-bed5-f2d3080670eb ro recovery nomodeset
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/01/2010
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 6AET64WW
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: 2746CTO
  dmi.board.vendor: LENOVO
  dmi.board.version: LENOVO 6AET64WW
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: LENOVO 6AET64WW
  dmi.modalias: 
dmi:bvnLENOVO:bvr6AET64WW:bd12/01/2010:svnLENOVO:pn2746CTO:pvrThinkPadSL500:rvnLENOVO:rn2746CTO:rvrLENOVO6AET64WW:cvnLENOVO:ct10:cvrLENOVO6AET64WW:
  dmi.product.name: 2746CTO
  dmi.product.version: ThinkPad SL500
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.97-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.0-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  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/lightdm/+bug/1821609/+subscriptions

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

[Desktop-packages] [Bug 1822402] Re: gnome calendar automatically moves event back 1 day

2019-04-04 Thread Toan Nguyen
The latest Ubuntu 19.04 beta and Calendar 3.32.0.

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

Title:
  gnome calendar automatically moves event back 1 day

Status in gnome-calendar package in Ubuntu:
  Incomplete

Bug description:
  Step to reproduce:
  1. Create an all day event
  2. Set it to repeat monthly
  --> Surprise, it goes back one day

  Additional information:
  Time belt: GMT+7

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

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


[Desktop-packages] [Bug 1823110] Re: Screen not resized when rotating 90*

2019-04-04 Thread Brian Murray
** Package changed: ubuntu => xorg (Ubuntu)

** Tags added: regression-release

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

Title:
  Screen not resized when rotating 90*

Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  Running 19.04 beta on a Microsoft Surface Pro 3.
  Screen resolution 2160x1440 works in normal landscape mode (Docked mode) 
however if I rotate the device 90* clockwise or counter-clockwise, the screen 
resolution doesn't change to 1440x2160. The screen actually rotates however it 
hasn't flipped the dimensions to fit.
  This was previously working on Ubuntu 18.10.

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

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


[Desktop-packages] [Bug 1236619] Re: gvfs smb / cifs file copy performance is terribly slow

2019-04-04 Thread Josef Mašek
In my case, in 16.04 gvfs was same fast as mount -t cifs, but now in
18.04 I have gvfs about 9 times slower than mount (5 MB/s GVFS, 44
MBit/s mount and is probably disk limit now)

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

Title:
  gvfs smb / cifs file copy performance is terribly slow

Status in gvfs package in Ubuntu:
  Confirmed

Bug description:
  Copying moderate-size files to a samba share using gvfs is
  ridiculously slow compared to doing the same via mount.cifs.  For
  example:

  $ ls -sh testfile
  1.2G testfile
  $ time cp testfile ~/mnt/share-gvfs/
  real  2m37.053s
  user  0m0.056s
  sys   0m5.120s
  $ time cp testfile ~/mnt/share/
  real  0m26.134s
  user  0m0.004s
  sys   0m1.724s

  I'm running Xubuntu 13.04 (raring) amd64, gvfs 1.16.1-0ubuntu1.1.

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

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


[Desktop-packages] [Bug 1823194] Re: Windows share (CIFS) mounted over gvfs (by tool Files) is about 10 times slower than mounted by mount -t cifs

2019-04-04 Thread Josef Mašek
gvfs/bionic-updates,bionic-security,now 1.36.1-0ubuntu1.3 amd64 [installed]
cifs-utils/bionic,now 2:6.8-1 amd64 [installed]
mount/bionic-updates,now 2.31.1-0.4ubuntu3.3 amd64 [installed]

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

Title:
  Windows share (CIFS) mounted over gvfs (by tool Files) is about 10
  times slower than mounted by mount -t cifs

Status in gvfs package in Ubuntu:
  New

Bug description:
  Copying data by Files says 5MB/s - when I use "Files" and I mounted
  windows share (from Freenas 9.x stable) and copy to local disk (also
  by Files).

  When I use "old way" 
  in /etc/fstab is:
  //192.168.x.x/public  /media/netio  cifs  noauto,guest,iocharset=utf8
  mount /medi/netio
  and copy files by any tool (also files), it tooks about 1,5 hours and 44 MB/s.

  I am copying 170 GB and by gvfs it tooks about 9 hours - more than
  working day, by mount and copy only 1,5 hour.

  I have updated 18.04, packages:

  In Ubuntu 16.04 gvfs and mount worked almost the same speed.

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

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


[Desktop-packages] [Bug 1823194] [NEW] Windows share (CIFS) mounted over gvfs (by tool Files) is about 10 times slower than mounted by mount -t cifs

2019-04-04 Thread Josef Mašek
Public bug reported:

Copying data by Files says 5MB/s - when I use "Files" and I mounted
windows share (from Freenas 9.x stable) and copy to local disk (also by
Files).

When I use "old way" 
in /etc/fstab is:
//192.168.x.x/public  /media/netio  cifs  noauto,guest,iocharset=utf8
mount /medi/netio
and copy files by any tool (also files), it tooks about 1,5 hours and 44 MB/s.

I am copying 170 GB and by gvfs it tooks about 9 hours - more than
working day, by mount and copy only 1,5 hour.

I have updated 18.04, packages:

In Ubuntu 16.04 gvfs and mount worked almost the same speed.

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

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

Title:
  Windows share (CIFS) mounted over gvfs (by tool Files) is about 10
  times slower than mounted by mount -t cifs

Status in gvfs package in Ubuntu:
  New

Bug description:
  Copying data by Files says 5MB/s - when I use "Files" and I mounted
  windows share (from Freenas 9.x stable) and copy to local disk (also
  by Files).

  When I use "old way" 
  in /etc/fstab is:
  //192.168.x.x/public  /media/netio  cifs  noauto,guest,iocharset=utf8
  mount /medi/netio
  and copy files by any tool (also files), it tooks about 1,5 hours and 44 MB/s.

  I am copying 170 GB and by gvfs it tooks about 9 hours - more than
  working day, by mount and copy only 1,5 hour.

  I have updated 18.04, packages:

  In Ubuntu 16.04 gvfs and mount worked almost the same speed.

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

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


[Desktop-packages] [Bug 1823110] [NEW] Screen not resized when rotating 90*

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

Running 19.04 beta on a Microsoft Surface Pro 3.
Screen resolution 2160x1440 works in normal landscape mode (Docked mode) 
however if I rotate the device 90* clockwise or counter-clockwise, the screen 
resolution doesn't change to 1440x2160. The screen actually rotates however it 
hasn't flipped the dimensions to fit.
This was previously working on Ubuntu 18.10.

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


** Tags: bot-comment disco
-- 
Screen not resized when rotating 90*
https://bugs.launchpad.net/bugs/1823110
You received this bug notification because you are a member of Desktop 
Packages, which is subscribed to xorg 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 1817223] Re: [disco-proposed] The list of applications in Ubuntu Software is empty

2019-04-04 Thread Mario Limonciello
** Changed in: libxmlb (Ubuntu)
   Status: Triaged => Fix Released

** Changed in: libxmlb (Ubuntu Disco)
   Status: Won't Fix => Fix Released

** Changed in: libxmlb (Ubuntu)
 Assignee: Robert Ancell (robert-ancell) => Mario Limonciello (superm1)

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

Title:
  [disco-proposed] The list of applications in Ubuntu Software is empty

Status in gnome-software package in Ubuntu:
  Triaged
Status in libxmlb package in Ubuntu:
  Fix Released
Status in gnome-software source package in Disco:
  Won't Fix
Status in libxmlb source package in Disco:
  Fix Released

Bug description:
  Hi

  The COMPLETE LIST of applications in Ubuntu Software is not showing up

  See attached image

  Thank you

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: gnome-software 3.31.2-0ubuntu1
  ProcVersionSignature: Ubuntu 4.19.0-13.14-generic 4.19.20
  Uname: Linux 4.19.0-13-generic x86_64
  ApportVersion: 2.20.10-0ubuntu21
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Feb 21 19:11:23 2019
  ExecutablePath: /usr/bin/gnome-software
  InstallationDate: Installed on 2019-02-11 (10 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190203)
  InstalledPlugins:
   gnome-software-plugin-flatpak N/A
   gnome-software-plugin-snap3.31.2-0ubuntu1
  SourcePackage: gnome-software
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1822351] Re: Nautilus does not open after updating to 19.04

2019-04-04 Thread Sebastien Bacher
Thank you for taking the time to report this bug and helping to make
Ubuntu better. Please try to obtain a backtrace following the
instructions at http://wiki.ubuntu.com/DebuggingProgramCrash and upload
the backtrace (as an attachment) to the bug report. This will greatly
help us in tracking down your problem.

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

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

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

Title:
  Nautilus does not open after updating to 19.04

Status in nautilus package in Ubuntu:
  Incomplete

Bug description:
  After updating to Ubuntu 19.04 dev branch, nautilus does not open at
  all. Moreover, trying to open nautilus from the terminal does not give
  any error, nor any output at all, and no window opens.

  I don't really know how to report this bug without any terminal
  output.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: nautilus 1:3.32.0-0ubuntu1
  ProcVersionSignature: Ubuntu 5.0.0-7.8-generic 5.0.0
  Uname: Linux 5.0.0-7-generic x86_64
  ApportVersion: 2.20.10-0ubuntu23
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Mar 29 13:58:12 2019
  InstallationDate: Installed on 2018-02-23 (398 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180222)
  SourcePackage: nautilus
  UpgradeStatus: Upgraded to disco on 2019-03-29 (0 days ago)
  usr_lib_nautilus:

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

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


[Desktop-packages] [Bug 1819193] Re: Document search does not work

2019-04-04 Thread Sebastien Bacher
** Changed in: gnome-shell (Ubuntu)
   Importance: Undecided => Low

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

Title:
  Document search does not work

Status in GNOME Documents:
  New
Status in gnome-documents package in Ubuntu:
  New
Status in gnome-shell package in Ubuntu:
  New

Bug description:
  1. Description: Ubuntu 18.04.2 LTS
  2. 3.28.3-0ubuntu0.18.04.4
  3. I expect to be able to search document by content from the gnome shell 
("Type to search..."). The option is enabled from settings.
  4. Nothing happens. No documents are retrieved. 

  I get the following error message in logs repeatedly:

  "Wrong number of result metas returned by search provider
  org.gnome.Documents.desktop: expected 5 but got 0"

  gnome-documents also gives this:
  "JS ERROR: GLib.Error g-invoke-error-quark: Could not locate 
gd_filename_strip_extension: (null)"

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

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


[Desktop-packages] [Bug 1822103] Re: upgrade from 18.4 to 18.10 iio-sensor-proxy not working

2019-04-04 Thread Sebastien Bacher
Could you add the output of 
$ udevadm info --export-db
$ sudo systemctl stop iio-sensor-proxy.service 
$ G_MESSAGES_DEBUG=all sudo /usr/sbin/iio-sensor-proxy

** Changed in: iio-sensor-proxy (Ubuntu)
   Importance: Undecided => Low

** Changed in: iio-sensor-proxy (Ubuntu)
   Status: New => Incomplete

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

Title:
  upgrade from 18.4 to 18.10 iio-sensor-proxy not working

Status in iio-sensor-proxy package in Ubuntu:
  Incomplete

Bug description:
  After upgrade from 18.4 to 18.10 iio-sensor-proxy did not pickup
  hardware. I had no problem with ubuntu 18.4. The iio-sensor-proxy says
  that it support my hardware on github. Prehapse a new build or
  rollback build for the new repository?

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: iio-sensor-proxy 2.5-0ubuntu1
  ProcVersionSignature: Ubuntu 4.18.0-16.17-generic 4.18.20
  Uname: Linux 4.18.0-16-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Mar 28 09:06:48 2019
  InstallationDate: Installed on 2019-03-27 (0 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: iio-sensor-proxy
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/iio-sensor-proxy/+bug/1822103/+subscriptions

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


[Desktop-packages] [Bug 1822402] Re: gnome calendar automatically moves event back 1 day

2019-04-04 Thread Sebastien Bacher
Thank you for your bug report. What Ubuntu version and type of calendar
do you use?

** Changed in: gnome-calendar (Ubuntu)
   Importance: Undecided => Low

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

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

Title:
  gnome calendar automatically moves event back 1 day

Status in gnome-calendar package in Ubuntu:
  Incomplete

Bug description:
  Step to reproduce:
  1. Create an all day event
  2. Set it to repeat monthly
  --> Surprise, it goes back one day

  Additional information:
  Time belt: GMT+7

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

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


[Desktop-packages] [Bug 1822587] Re: wifi service stops occasionally.

2019-04-04 Thread Sebastien Bacher
** Changed in: network-manager (Ubuntu)
   Importance: Undecided => Low

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

Title:
  wifi service stops occasionally.

Status in network-manager package in Ubuntu:
  New

Bug description:
  wifi service stops occasionally: ('?' in the top right icon). an old
  bug that disappeared a few updates back, back now after yesterday's
  update.  'service network-manager restart' gets it working again.
  annoying as i thought it gone.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: network-manager 1.12.4-1ubuntu1.2
  ProcVersionSignature: Ubuntu 4.18.0-16.17-generic 4.18.20
  Uname: Linux 4.18.0-16-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Apr  1 14:50:50 2019
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2016-07-30 (975 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  IpRoute:
   default via 192.168.8.1 dev wlp3s0f0 proto dhcp metric 600 
   169.254.0.0/16 dev wlp3s0f0 scope link metric 1000 
   192.168.8.0/24 dev wlp3s0f0 proto kernel scope link src 192.168.8.100 metric 
600
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=false
  ProcEnviron:
   LANGUAGE=en_ZA:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_ZA.UTF-8
   SHELL=/bin/bash
  SourcePackage: network-manager
  UpgradeStatus: Upgraded to cosmic on 2018-12-06 (116 days ago)
  nmcli-dev:
   DEVICE TYPE  STATE DBUS-PATH 
 CONNECTIONCON-UUID  CON-PATH   

   wlp3s0f0   wifi  connected 
/org/freedesktop/NetworkManager/Devices/3  HUAWEI-B315-D7CD  
01a82e09-44b7-4509-af07-4bf05f76759a  
/org/freedesktop/NetworkManager/ActiveConnection/1 
   1C:AF:05:F7:CE:56  btdisconnected  
/org/freedesktop/NetworkManager/Devices/4  ---- 
   -- 
   enp2s0f1   ethernet  unavailable   
/org/freedesktop/NetworkManager/Devices/2  ---- 
   -- 
   lo loopback  unmanaged 
/org/freedesktop/NetworkManager/Devices/1  ---- 
   --
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN 
   running  1.12.4   connected  started  full  enabled enabled  
enabled  enabled  disabled

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

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


[Desktop-packages] [Bug 1709194] Re: Power notification appears with no detail

2019-04-04 Thread Sebastien Bacher
The issue should be fixed in Disco now

** Changed in: gnome-settings-daemon (Ubuntu)
   Status: Fix Committed => Fix Released

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

Title:
  Power notification appears with no detail

Status in GNOME Settings Daemon:
  Confirmed
Status in gnome-settings-daemon package in Ubuntu:
  Fix Released

Bug description:
  I locked my laptop screen. Some time later a notification appeared
  (see screenshot).

  "Power"
  "1 new notification"

  If I move the mouse the notification disappears. If I unlock the
  laptop there are no notifications pending anywhere. I have no idea
  where this text comes from or what it means. Is my battery low? is it
  full? Is there some other issue?

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-power-manager 3.24.0-0ubuntu1
  ProcVersionSignature: Ubuntu 4.11.0-10.15-generic 4.11.8
  Uname: Linux 4.11.0-10-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
  ApportVersion: 2.20.6-0ubuntu4
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Mon Aug  7 23:26:58 2017
  InstallationDate: Installed on 2017-08-02 (5 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170712)
  SourcePackage: gnome-power-manager
  UpgradeStatus: No upgrade log present (probably fresh install)

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

-- 
Mailing list: https://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 1822480] Re: Scrollbar Missing in Font Selection for Insert Character Form

2019-04-04 Thread Bryce
I'm not sure what GTK theme I'm using. I did realize, however, that I'm 
not using a Snap package. I had to switch to the latest .deb because 
Mendeley extension integration wouldn't work with a Snap. I'll determine 
more information and resubmit the bug report.

The error is reproducible on my system, otherwise.

On 2019-04-01 1:41 p.m., Olivier Tilloy wrote:
> I am not seeing that in a 18.10 VM with the latest libreoffice snap from
> the stable channel. The list of fonts has arrows at its top and bottom,
> scrolling with the mouse wheel and arrow keys works.
>
> Is this something that can be consistently reproduced?
>
> What GTK theme are you using?
>
> ** 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/1822480

Title:
  Scrollbar Missing in Font Selection for Insert Character Form

Status in libreoffice package in Ubuntu:
  Incomplete

Bug description:
  On an Ubuntu 18.10 system, using LibreOffice 6.2.2-2 Snap package, a
  scroll-bar is not displayed in the font listing within the ‘Special
  Characters’ dialogue; the field of displayed fonts cannot be moved
  through with the arrow keys or the scroll-wheel on the mouse, but the
  selected font can be changed with the arrow keys.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: libreoffice-writer (not installed)
  ProcVersionSignature: Ubuntu 4.18.0-16.17-generic 4.18.20
  Uname: Linux 4.18.0-16-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Mar 31 09:13:57 2019
  InstallationDate: Installed on 2018-12-30 (91 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  SourcePackage: libreoffice
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1822593] Re: No option to disable devices low battery notifications

2019-04-04 Thread Sebastien Bacher
Thanks, that's the same issue than bug #1798166

** Changed in: gnome-settings-daemon (Ubuntu)
   Importance: Undecided => Low

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

Title:
  No option to disable devices low battery notifications

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

Bug description:
  You can find the battery levels of devices in Settings->Power.

  It would be nice if the notifications about the batteries could be
  disabled. I keep getting them, but my devices keep working for a long
  time (even when they themselves flash red due to low battery).

  Ubuntu 18.10
  Gnome 3.30.1

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

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


[Desktop-packages] [Bug 1704740]

2019-04-04 Thread Xiscofauli
You're right!!
This is fixed by 
https://cgit.freedesktop.org/libreoffice/core/commit/?id=7fdc5df36f5b50e0629405a47ff3d5765fcfeb93

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

Title:
  calc: move cell does not update row sum

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

Bug description:
  See attached test case.  Sum two rows: A1 + B1 = C1; A2 + B2 = C2
  where B1 is blank.  Cut B2 and paste into B1.  Result C2 is
  decremented correctly by old B2 value; but result C1 is NOT
  incremented by new B1 value.  Formula of C1 remains correct
  =SUM($Sheet1.A1:B1) as is C2's formula but C1 result is wrong.  Saving
  file, close and re-open does not fix incorrect C1 result.  Undo undo
  to return to initial state results in C2 now having incorrect result.
  Bug occurs whether drag and drop or control-x/control-v used. This is
  a data integrity issue as the wrong answer is being displayed.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: libreoffice-calc 1:5.1.6~rc2-0ubuntu1~xenial2
  ProcVersionSignature: Ubuntu 4.4.0-83.106-generic 4.4.70
  Uname: Linux 4.4.0-83-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.1-0ubuntu2.9
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Mon Jul 17 17:33:42 2017
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2016-05-08 (435 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  SourcePackage: libreoffice
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1704740] Re: calc: move cell does not update row sum

2019-04-04 Thread Bug Watch Updater
** Changed in: df-libreoffice
   Status: Confirmed => Fix Released

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

Title:
  calc: move cell does not update row sum

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

Bug description:
  See attached test case.  Sum two rows: A1 + B1 = C1; A2 + B2 = C2
  where B1 is blank.  Cut B2 and paste into B1.  Result C2 is
  decremented correctly by old B2 value; but result C1 is NOT
  incremented by new B1 value.  Formula of C1 remains correct
  =SUM($Sheet1.A1:B1) as is C2's formula but C1 result is wrong.  Saving
  file, close and re-open does not fix incorrect C1 result.  Undo undo
  to return to initial state results in C2 now having incorrect result.
  Bug occurs whether drag and drop or control-x/control-v used. This is
  a data integrity issue as the wrong answer is being displayed.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: libreoffice-calc 1:5.1.6~rc2-0ubuntu1~xenial2
  ProcVersionSignature: Ubuntu 4.4.0-83.106-generic 4.4.70
  Uname: Linux 4.4.0-83-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.1-0ubuntu2.9
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Mon Jul 17 17:33:42 2017
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2016-05-08 (435 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  SourcePackage: libreoffice
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1704740]

2019-04-04 Thread Xiscofauli
No need a test for this, this is already covered by
https://gerrit.libreoffice.org/plugins/gitiles/core/+/6280b5c1c62ad40b5b9780a93c7cbee9ca0260f8%5E%21

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

Title:
  calc: move cell does not update row sum

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

Bug description:
  See attached test case.  Sum two rows: A1 + B1 = C1; A2 + B2 = C2
  where B1 is blank.  Cut B2 and paste into B1.  Result C2 is
  decremented correctly by old B2 value; but result C1 is NOT
  incremented by new B1 value.  Formula of C1 remains correct
  =SUM($Sheet1.A1:B1) as is C2's formula but C1 result is wrong.  Saving
  file, close and re-open does not fix incorrect C1 result.  Undo undo
  to return to initial state results in C2 now having incorrect result.
  Bug occurs whether drag and drop or control-x/control-v used. This is
  a data integrity issue as the wrong answer is being displayed.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: libreoffice-calc 1:5.1.6~rc2-0ubuntu1~xenial2
  ProcVersionSignature: Ubuntu 4.4.0-83.106-generic 4.4.70
  Uname: Linux 4.4.0-83-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.1-0ubuntu2.9
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Mon Jul 17 17:33:42 2017
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2016-05-08 (435 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  SourcePackage: libreoffice
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1813701] Re: [amdgpu] Flickering graphics corruption (but none observed in kernels 4.18.10-4.18.12)

2019-04-04 Thread Ivan Grigoryev
and https://bugs.freedesktop.org/show_bug.cgi?id=102646

** Bug watch added: freedesktop.org Bugzilla #102646
   https://bugs.freedesktop.org/show_bug.cgi?id=102646

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

Title:
  [amdgpu] Flickering graphics corruption (but none observed in kernels
  4.18.10-4.18.12)

Status in linux package in Ubuntu:
  Confirmed
Status in xserver-xorg-video-amdgpu package in Ubuntu:
  Confirmed

Bug description:
  The screen always flickers at a frequency of 75 GHz on the AMD RX 580 gpu. At 
60 and 50 GHz, if you switch to any other than 75, the flickering will 
disappear until the display turns off. After switching on, flicker returns. At 
the core of 4.18.0-10, just like on the AMD Radeon HD7970 gpu, the problem is 
not visible. More in the video
  https://www.youtube.com/watch?v=d_LXHqWKTbk

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: xorg 1:7.7+19ubuntu8
  ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17
  Uname: Linux 4.18.0-13-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13.1
  Architecture: amd64
  BootLog: Error: [Errno 13] Отказано в доступе: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jan 29 13:13:19 2019
  DistUpgraded: Fresh install
  DistroCodename: cosmic
  DistroVariant: ubuntu
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Ellesmere [Radeon RX 
470/480/570/570X/580/580X] [1002:67df] (rev e7) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. Ellesmere [Radeon RX 
470/480/570/570X/580/580X] [1043:0519]
  InstallationDate: Installed on 2019-01-22 (6 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  MachineType: MSI MS-7693
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=ru_RU.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-13-generic 
root=UUID=ad22bc6d-c4e8-4393-a30b-6c247159b9dd ro quiet splash vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/08/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: V10.6
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: 970A-G43 (MS-7693)
  dmi.board.vendor: MSI
  dmi.board.version: 3.0
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: MSI
  dmi.chassis.version: 3.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrV10.6:bd01/08/2016:svnMSI:pnMS-7693:pvr3.0:rvnMSI:rn970A-G43(MS-7693):rvr3.0:cvnMSI:ct3:cvr3.0:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: MS-7693
  dmi.product.sku: To be filled by O.E.M.
  dmi.product.version: 3.0
  dmi.sys.vendor: MSI
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.97+git1901221830.b7a7a9~oibaf~c
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.0~git1901280730.d1d2bb~oibaf~c
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.1-3ubuntu2.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-3

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

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


[Desktop-packages] [Bug 1813701] Re: [amdgpu] Flickering graphics corruption (but none observed in kernels 4.18.10-4.18.12)

2019-04-04 Thread Ivan Grigoryev
has already
https://bugs.freedesktop.org/show_bug.cgi?id=110199

** Bug watch added: freedesktop.org Bugzilla #110199
   https://bugs.freedesktop.org/show_bug.cgi?id=110199

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

Title:
  [amdgpu] Flickering graphics corruption (but none observed in kernels
  4.18.10-4.18.12)

Status in linux package in Ubuntu:
  Confirmed
Status in xserver-xorg-video-amdgpu package in Ubuntu:
  Confirmed

Bug description:
  The screen always flickers at a frequency of 75 GHz on the AMD RX 580 gpu. At 
60 and 50 GHz, if you switch to any other than 75, the flickering will 
disappear until the display turns off. After switching on, flicker returns. At 
the core of 4.18.0-10, just like on the AMD Radeon HD7970 gpu, the problem is 
not visible. More in the video
  https://www.youtube.com/watch?v=d_LXHqWKTbk

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: xorg 1:7.7+19ubuntu8
  ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17
  Uname: Linux 4.18.0-13-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13.1
  Architecture: amd64
  BootLog: Error: [Errno 13] Отказано в доступе: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jan 29 13:13:19 2019
  DistUpgraded: Fresh install
  DistroCodename: cosmic
  DistroVariant: ubuntu
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Ellesmere [Radeon RX 
470/480/570/570X/580/580X] [1002:67df] (rev e7) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. Ellesmere [Radeon RX 
470/480/570/570X/580/580X] [1043:0519]
  InstallationDate: Installed on 2019-01-22 (6 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  MachineType: MSI MS-7693
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=ru_RU.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-13-generic 
root=UUID=ad22bc6d-c4e8-4393-a30b-6c247159b9dd ro quiet splash vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/08/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: V10.6
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: 970A-G43 (MS-7693)
  dmi.board.vendor: MSI
  dmi.board.version: 3.0
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: MSI
  dmi.chassis.version: 3.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrV10.6:bd01/08/2016:svnMSI:pnMS-7693:pvr3.0:rvnMSI:rn970A-G43(MS-7693):rvr3.0:cvnMSI:ct3:cvr3.0:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: MS-7693
  dmi.product.sku: To be filled by O.E.M.
  dmi.product.version: 3.0
  dmi.sys.vendor: MSI
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.97+git1901221830.b7a7a9~oibaf~c
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.0~git1901280730.d1d2bb~oibaf~c
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.1-3ubuntu2.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-3

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

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


[Desktop-packages] [Bug 1823148] Re: eog crashed with SIGSEGV in g_mutex_lock()

2019-04-04 Thread Sebastien Bacher
Thanks, sent upstream on https://gitlab.gnome.org/GNOME/eog/issues/50

** Bug watch added: gitlab.gnome.org/GNOME/eog/issues #50
   https://gitlab.gnome.org/GNOME/eog/issues/50

** Changed in: eog (Ubuntu)
   Status: New => Triaged

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

Title:
  eog crashed with SIGSEGV in g_mutex_lock()

Status in eog package in Ubuntu:
  Triaged

Bug description:
  Hi,

  to reproduce this bug:

   - in eog load an image from a directory that contains several images
   - press F5

  ProblemType: Crash
  DistroRelease: Ubuntu 19.04
  Package: eog 3.32.0-1
  Uname: Linux 5.0.6-050006-generic x86_64
  ApportVersion: 2.20.10-0ubuntu23
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Thu Apr  4 11:41:28 2019
  ExecutablePath: /usr/bin/eog
  JournalErrors:
   Error: command ['journalctl', '-b', '--priority=warning', '--lines=1000'] 
failed with exit code 1: Hint: You are currently not seeing messages from other 
users and the system.
 Users in the 'systemd-journal' group can see all messages. Pass -q to
 turn off this notice.
   No journal files were opened due to insufficient permissions.
  ProcCmdline: eog P1000443.jpg
  ProcEnviron:
   SHELL=/bin/bash
   LANG=en_US.UTF-8
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
   PATH=(custom, no user)
  SegvAnalysis:
   Segfault happened at: 0x7f53db0ce945 :   lock xadd 
%eax,(%rdi)
   PC (0x7f53db0ce945) ok
   source "%eax" ok
   destination "(%rdi)" (0x7575757575757575) not located in a known VMA region 
(needed writable region)!
  SegvReason: writing unknown VMA
  Signal: 11
  SourcePackage: eog
  StacktraceTop:
   g_mutex_lock (mutex=mutex@entry=0x7575757575757575) at 
../../../glib/gthread-posix.c:1354
   g_source_destroy_internal (source=0x5611bb416f10, 
context=0x7575757575757575, have_lock=0) at ../../../glib/gmain.c:1219
   g_source_destroy (source=) at ../../../glib/gmain.c:1287
   slideshow_clear_timeout (window=window@entry=0x5611bb1637e0 [EogWindow]) at 
../src/eog-window.c:1827
   slideshow_set_timeout (window=window@entry=0x5611bb1637e0 [EogWindow]) at 
../src/eog-window.c:1840
  Title: eog crashed with SIGSEGV in g_mutex_lock()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm admin cdrom dialout kvm lpadmin lxd plugdev sambashare staff
  separator:

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

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


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

2019-04-04 Thread Efthimios Chaskaris
apport information

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

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

Title:
  Buttons in Night Light menu in settings weird behaviour

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

Bug description:
  When you press the pressed button (eg the sunset to sunrise button), it gets 
unpressed and nothing changes.
  Then, when you press that button again, the opposite button (manual) is 
pressed.

  Ubuntu 18.10
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu13.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.10
  InstallationDate: Installed on 2018-10-25 (160 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: gnome-control-center 1:3.30.2-1ubuntu0.18.10.2
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.18.0-17.18-generic 4.18.20
  Tags:  cosmic
  Uname: Linux 4.18.0-17-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-control-center/+bug/1823035/+subscriptions

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


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

2019-04-04 Thread Efthimios Chaskaris
apport information

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

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

Title:
  Buttons in Night Light menu in settings weird behaviour

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

Bug description:
  When you press the pressed button (eg the sunset to sunrise button), it gets 
unpressed and nothing changes.
  Then, when you press that button again, the opposite button (manual) is 
pressed.

  Ubuntu 18.10
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu13.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.10
  InstallationDate: Installed on 2018-10-25 (160 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: gnome-control-center 1:3.30.2-1ubuntu0.18.10.2
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.18.0-17.18-generic 4.18.20
  Tags:  cosmic
  Uname: Linux 4.18.0-17-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-control-center/+bug/1823035/+subscriptions

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


[Desktop-packages] [Bug 1823035] Re: Buttons in Night Light menu in settings weird behaviour

2019-04-04 Thread Efthimios Chaskaris
apport information

** Tags added: apport-collected

** Description changed:

  When you press the pressed button (eg the sunset to sunrise button), it gets 
unpressed and nothing changes.
  Then, when you press that button again, the opposite button (manual) is 
pressed.
  
  Ubuntu 18.10
+ --- 
+ ProblemType: Bug
+ ApportVersion: 2.20.10-0ubuntu13.2
+ Architecture: amd64
+ CurrentDesktop: ubuntu:GNOME
+ DistroRelease: Ubuntu 18.10
+ InstallationDate: Installed on 2018-10-25 (160 days ago)
+ InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
+ NonfreeKernelModules: nvidia_modeset nvidia
+ Package: gnome-control-center 1:3.30.2-1ubuntu0.18.10.2
+ PackageArchitecture: amd64
+ ProcVersionSignature: Ubuntu 4.18.0-17.18-generic 4.18.20
+ Tags:  cosmic
+ Uname: Linux 4.18.0-17-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/1823035/+attachment/5252796/+files/Dependencies.txt

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

Title:
  Buttons in Night Light menu in settings weird behaviour

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

Bug description:
  When you press the pressed button (eg the sunset to sunrise button), it gets 
unpressed and nothing changes.
  Then, when you press that button again, the opposite button (manual) is 
pressed.

  Ubuntu 18.10
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu13.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.10
  InstallationDate: Installed on 2018-10-25 (160 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: gnome-control-center 1:3.30.2-1ubuntu0.18.10.2
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.18.0-17.18-generic 4.18.20
  Tags:  cosmic
  Uname: Linux 4.18.0-17-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-control-center/+bug/1823035/+subscriptions

-- 
Mailing list: https://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   >