[Desktop-packages] [Bug 1682548] Re: "Details" does not show GNOME version

2018-03-20 Thread Bug Watch Updater
** Changed in: gnome-user-docs
   Status: Confirmed => Fix Released

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

Title:
  "Details" does not show GNOME version

Status in Gnome Documentation:
  Fix Released
Status in gnome-user-docs package in Ubuntu:
  Confirmed

Bug description:
  From the Gnome Help >> Tips & Tricks >> Determine which version of
  GNOME is running

  You can determine the version of GNOME that is running on your system by 
going to the Details panel in Settings.
  Open the Activities overview and start typing Details.
  Click on Details to open the panel.
  A window appears showing information about your system, including your 
distribution's name and the GNOME version.

  yet...opening up 
  Activities > Details 

  the details window does not show either my distribution's name *or*
  GNOME version.

  Either 
  1) This behaviour changed and the documentation is out of date
  or 
  2) there's a bug in "Details" window.

  Ubuntu: 17.04 zesty

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: gnome (not installed)
  ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8
  Uname: Linux 4.10.0-19-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Thu Apr 13 13:44:58 2017
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2014-07-09 (1008 days ago)
  InstallationMedia: Ubuntu-GNOME 14.10 "Utopic Unicorn" - Alpha amd64 
(20140708)
  SourcePackage: meta-gnome3
  UpgradeStatus: Upgraded to zesty on 2017-04-13 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-user-docs/+bug/1682548/+subscriptions

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


[Desktop-packages] [Bug 1757058] [NEW] gnome-calendar (11) gtk_image_reset → gtk_image_clear → update_weather → g_closure_invoke → signal_emit_unlocked_R

2018-03-20 Thread errors.ubuntu.com bug bridge
Public bug reported:

The Ubuntu Error Tracker has been receiving reports about a problem regarding 
gnome-calendar.  This problem was most recently seen with package version 
3.27.90-1build1, the problem page at 
https://errors.ubuntu.com/problem/10133d642d3e26786b82ac7e8f7f53f804cf1714 
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/.

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


** Tags: bionic

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

Title:
  gnome-calendar (11) gtk_image_reset → gtk_image_clear → update_weather
  → g_closure_invoke → signal_emit_unlocked_R

Status in gnome-calendar package in Ubuntu:
  New

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
gnome-calendar.  This problem was most recently seen with package version 
3.27.90-1build1, the problem page at 
https://errors.ubuntu.com/problem/10133d642d3e26786b82ac7e8f7f53f804cf1714 
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/gnome-calendar/+bug/1757058/+subscriptions

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


[Desktop-packages] [Bug 1757058] Re: gnome-calendar (11) gtk_image_reset → gtk_image_clear → update_weather → g_closure_invoke → signal_emit_unlocked_R

2018-03-20 Thread Jean-Baptiste Lallement
** Summary changed:

- 
/usr/bin/gnome-calendar:11:gtk_image_reset:gtk_image_clear:update_weather:g_closure_invoke:signal_emit_unlocked_R
+ gnome-calendar (11) gtk_image_reset → gtk_image_clear → update_weather → 
g_closure_invoke → signal_emit_unlocked_R

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

Title:
  gnome-calendar (11) gtk_image_reset → gtk_image_clear → update_weather
  → g_closure_invoke → signal_emit_unlocked_R

Status in gnome-calendar package in Ubuntu:
  New

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
gnome-calendar.  This problem was most recently seen with package version 
3.27.90-1build1, the problem page at 
https://errors.ubuntu.com/problem/10133d642d3e26786b82ac7e8f7f53f804cf1714 
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/gnome-calendar/+bug/1757058/+subscriptions

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


[Desktop-packages] [Bug 1756569] Re: Provide separate Korean package

2018-03-20 Thread Launchpad Bug Tracker
This bug was fixed in the package gnome-user-docs - 3.28.0-0ubuntu2

---
gnome-user-docs (3.28.0-0ubuntu2) bionic; urgency=medium

  * debian/control.in, debian/rules:
- Separate package for Korean (LP: #1756569)
- Start installing keyboard-layouts.page - previous Ubuntu delta
  has been committed upstream.

 -- Gunnar Hjalmarsson   Tue, 20 Mar 2018 04:46:00
+0100

** Changed in: gnome-user-docs (Ubuntu)
   Status: In Progress => Fix Released

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

Title:
  Provide separate Korean package

Status in gnome-user-docs package in Ubuntu:
  Fix Released

Bug description:
  https://launchpad.net/ubuntu/+source/gnome-user-docs/3.28.0-0ubuntu1

  Minor detail, but I think it would be better to go ahead and move the
  Korean translations to a separate package. The separate package will
  still depend on the standard English translations so it shouldn't
  cause a problem if the Korean package is installed for Korean users.

  You'll need to add a Breaks/Replaces relationship for the file move.

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

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


[Desktop-packages] [Bug 1755144] Re: No audio on vlc or videos sound or video files

2018-03-20 Thread John Rose
I've tried mp3, ogg, wav and aac: all fail to make audio work.

Screen shot of vlc->Tools->Preferences->Audio attached.

This command does NOT make audio work in Totem for an mp4 video file?
   sudo apt remove gstreamer1.0-libav
It actually caused vlc to say that it needed the gstreamer1.0-libav plugin to 
play the H.264 decoder. So I let vlc invoke installation of gstreamer1.0-libav 
but it still didn't make audio work.

** Attachment added: "vlcToolsPreferencesAudioScreenshot.png"
   
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1755144/+attachment/5084723/+files/vlcToolsPreferencesAudioScreenshot.png

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

Title:
  No audio on vlc or videos sound or video files

Status in ffmpeg package in Ubuntu:
  Incomplete
Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  Up until a few weeks ago there was no problem with playing sound from mp3 
files. I have a pair of usb speakers. Audio plays Ok on them for video clips 
using Chrome (e.g. from BBC website). Using vlc 2.2.2 (from Ubuntu repos), 
neither a CD nor DVD (video is Ok) nor mp3 file plays audio. mp3 files play Ok 
using Rhythmbox. I've also tried vlc 3.0 with no success.
  Interestingly, the standard Videos app (Totem?) also doesn't play sound on 
these speakers either of an mp4 file (downloaded from YouTube, though it plays 
Ok on YouTube website using Chrome) or a DVD. Clemenetine plays mp3 files Ok. I 
first reported this as bug 1752267 as I thought that the problem was with vlc. 
On that bug, it was suggested that the problem is with Pulseaudio.
  Just now, I've tried to play sound through my monitor's built in speakers 
connected by hdmi (though the monitor displays Ok) with no success even though 
the built-in speakers play sound using pavucontrol when testing is invoked.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: pulseaudio 1:8.0-0ubuntu3.8
  ProcVersionSignature: Ubuntu 4.4.0-116.140-generic 4.4.98
  Uname: Linux 4.4.0-116-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  john   2410 F pulseaudio
   /dev/snd/controlC0:  john   2410 F pulseaudio
  CurrentDesktop: Unity
  Date: Mon Mar 12 11:06:46 2018
  InstallationDate: Installed on 2016-12-08 (458 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/04/2015
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: PYBSWCEL.86A.0043.2015.0904.1904
  dmi.board.name: NUC5CPYB
  dmi.board.vendor: Intel Corporation
  dmi.board.version: H61145-404
  dmi.chassis.type: 3
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrPYBSWCEL.86A.0043.2015.0904.1904:bd09/04/2015:svn:pn:pvr:rvnIntelCorporation:rnNUC5CPYB:rvrH61145-404:cvn:ct3:cvr:

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

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


[Desktop-packages] [Bug 1757030] Re: Lite-On DS8A1H Slimline fails to record dual layer DVD+R

2018-03-20 Thread Thomas Schmitt
Hi,

the problem looks like it is triggered by growisofs' habit to explicitely
set the layer break position. See its message

  /dev/dvdrw: splitting layers at 2009552 blocks

and its error message

 4115562496/8231090176 (50.0%) @0.0x, remaining 16:15 RBU 100.0% UBU 100.0%
 :-[ WRITE@LBA=1ea9d0h failed with SK=5h/ASC=21h/ACQ=04h]: Invalid argument

The numbers match: 4115562496 / 2048 = 2009552 = 0x1ea9d0


Somewhat riddling is the message from dmesg

   Write(10) 2a 00 00 1e d8 40 00 00 10 00

Some entity tried to write block 0x1ed840 = 2021440 = 2009552 + 11888.
The drive did not like this. (And the culprit should be ashamed.)


> xorriso is fine:

Years ago i decided in libburn against that growisofs gesture. DVD+R DL
are unreliable enough. Complicating their operation by smart commands
seemed unwise.
But on the other hand there were reports that drives worked with growisofs
and DVD+R DL whereas libburn (in that case underneath Xfburn) failed.

In growisofs_mmc.cpp one can see the occasion where sending the
layer break is decided:

if (profile==0x2B && next_track==1 && dvd_compat && leadout)
plus_r_dl_split (cmd,leadout);

Influencable from growisofs options is "dvd_compat". 
It gets set to non-zero if one fo these options is used:
  -dvd-compat
  -use-the-force-luke=dao
  -dvd-video
 
So maybe you get a better result when omitting -dvd-compat.
(This might yield an appendable medium which some entertainment DVD player
 might hate. But computer drives should be ok with it.)


> xorrecord dev='/dev/sr0' -v -dao -pad 2017.iso

Padding is needed only to prevent the Linux TAO CD read-ahead bug.
This special misperception of the readable size cannot happen with DVD media.

So if you ever need those last 300 KiB of a non-CD medium or a CD written
by write type SAO, then replace option "-pad" by "-nopad".


Have a nice day :)

Thomas

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

Title:
  Lite-On DS8A1H Slimline fails to record dual layer DVD+R

Status in dvd+rw-tools package in Ubuntu:
  New

Bug description:
  I tried Verbatim 8x and 2.4x DVD+R DL.  The failure is always exactly
  the same.

  $ growisofs -dvd-compat -Z /dev/dvdrw=2017.iso
  Executing 'builtin_dd if=2017.iso of=/dev/dvdrw obs=32k seek=0'
  /dev/dvdrw: splitting layers at 2009552 blocks
  /dev/dvdrw: "Current Write Speed" is 1.6x1352KBps.
  9175040/8231090176 ( 0.1%) @2.0x, remaining 74:40 RBU 100.0% UBU   7.4%
 21135360/8231090176 ( 0.3%) @2.6x, remaining 58:16 RBU 100.0% UBU  98.8%
 33095680/8231090176 ( 0.4%) @2.6x, remaining 49:32 RBU 100.0% UBU  98.6%
 45056000/8231090176 ( 0.5%) @2.6x, remaining 45:25 RBU 100.0% UBU  98.8%
 57016320/8231090176 ( 0.7%) @2.6x, remaining 45:23 RBU 100.0% UBU  98.8%
 69009408/8231090176 ( 0.8%) @2.6x, remaining 43:22 RBU 100.0% UBU  98.8%
 80969728/8231090176 ( 1.0%) @2.6x, remaining 41:56 RBU 100.0% UBU  98.6%
 92930048/8231090176 ( 1.1%) @2.6x, remaining 42:19 RBU 100.0% UBU  98.6%
  [..]
   4077289472/8231090176 (49.5%) @4.1x, remaining 15:15 RBU  90.0% UBU  88.4%
   4096065536/8231090176 (49.8%) @4.1x, remaining 15:11 RBU  43.0% UBU  97.9%
   4114808832/8231090176 (50.0%) @4.1x, remaining 15:06 RBU  28.0% UBU  97.9%
   4115562496/8231090176 (50.0%) @0.2x, remaining 15:08 RBU  69.4% UBU 100.0%
   4115562496/8231090176 (50.0%) @0.0x, remaining 15:12 RBU 100.0% UBU 100.0%
   4115562496/8231090176 (50.0%) @0.0x, remaining 15:15 RBU 100.0% UBU 100.0%
   4115562496/8231090176 (50.0%) @0.0x, remaining 15:18 RBU 100.0% UBU 100.0%
   4115562496/8231090176 (50.0%) @0.0x, remaining 15:22 RBU 100.0% UBU 100.0%
   4115562496/8231090176 (50.0%) @0.0x, remaining 15:25 RBU 100.0% UBU 100.0%
   4115562496/8231090176 (50.0%) @0.0x, remaining 15:28 RBU 100.0% UBU 100.0%
   4115562496/8231090176 (50.0%) @0.0x, remaining 15:32 RBU 100.0% UBU 100.0%
   4115562496/8231090176 (50.0%) @0.0x, remaining 15:35 RBU 100.0% UBU 100.0%
   4115562496/8231090176 (50.0%) @0.0x, remaining 15:38 RBU 100.0% UBU 100.0%
   4115562496/8231090176 (50.0%) @0.0x, remaining 15:42 RBU 100.0% UBU 100.0%
   4115562496/8231090176 (50.0%) @0.0x, remaining 15:45 RBU 100.0% UBU 100.0%
   4115562496/8231090176 (50.0%) @0.0x, remaining 15:48 RBU 100.0% UBU 100.0%
   4115562496/8231090176 (50.0%) @0.0x, remaining 15:52 RBU 100.0% UBU 100.0%
   4115562496/8231090176 (50.0%) @0.0x, remaining 15:55 RBU 100.0% UBU 100.0%
   4115562496/8231090176 (50.0%) @0.0x, remaining 15:58 RBU 100.0% UBU 100.0%
   4115562496/8231090176 (50.0%) @0.0x, remaining 16:02 RBU 100.0% UBU 100.0%
   4115562496/8231090176 (50.0%) @0.0x, remaining 16:05 RBU 100.0% UBU 100.0%
   4115562496/8231090176 (50.0%) @0.0x, remaining 16:08 RBU 100.0% UBU 100.0%
   4115562496/8231090176 (50.0%) @0.0x, remaining 16:12 RBU 100.0% UBU 100.0%
   4115562496/8231090176 (50.0%) @0.0x, remaining 16:15 RBU 100.0% UBU 100.

[Desktop-packages] [Bug 1755144] Re: No audio on vlc or videos sound or video files

2018-03-20 Thread Daniel van Vugt
I think you mean "totem", not "vlc", right?

That complaint from totem is half-expected. I thought gstreamer had
alternative plugins to cover common mp4 cases, but I can't find those
alternatives. So we're stuck with gstreamer1.0-libav, which depends on
your broken ffmpeg installation.

And that's what this seems to be. A uniquely broken ffmpeg
configuration. It doesn't seem to be a reproducible problem on other
machines. If I had more ideas on how to fix it (other than a complete
reinstall) then I would suggest them.

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

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

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

Title:
  No audio on vlc or videos sound or video files

Status in ffmpeg package in Ubuntu:
  New
Status in pulseaudio package in Ubuntu:
  Invalid

Bug description:
  Up until a few weeks ago there was no problem with playing sound from mp3 
files. I have a pair of usb speakers. Audio plays Ok on them for video clips 
using Chrome (e.g. from BBC website). Using vlc 2.2.2 (from Ubuntu repos), 
neither a CD nor DVD (video is Ok) nor mp3 file plays audio. mp3 files play Ok 
using Rhythmbox. I've also tried vlc 3.0 with no success.
  Interestingly, the standard Videos app (Totem?) also doesn't play sound on 
these speakers either of an mp4 file (downloaded from YouTube, though it plays 
Ok on YouTube website using Chrome) or a DVD. Clemenetine plays mp3 files Ok. I 
first reported this as bug 1752267 as I thought that the problem was with vlc. 
On that bug, it was suggested that the problem is with Pulseaudio.
  Just now, I've tried to play sound through my monitor's built in speakers 
connected by hdmi (though the monitor displays Ok) with no success even though 
the built-in speakers play sound using pavucontrol when testing is invoked.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: pulseaudio 1:8.0-0ubuntu3.8
  ProcVersionSignature: Ubuntu 4.4.0-116.140-generic 4.4.98
  Uname: Linux 4.4.0-116-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  john   2410 F pulseaudio
   /dev/snd/controlC0:  john   2410 F pulseaudio
  CurrentDesktop: Unity
  Date: Mon Mar 12 11:06:46 2018
  InstallationDate: Installed on 2016-12-08 (458 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/04/2015
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: PYBSWCEL.86A.0043.2015.0904.1904
  dmi.board.name: NUC5CPYB
  dmi.board.vendor: Intel Corporation
  dmi.board.version: H61145-404
  dmi.chassis.type: 3
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrPYBSWCEL.86A.0043.2015.0904.1904:bd09/04/2015:svn:pn:pvr:rvnIntelCorporation:rnNUC5CPYB:rvrH61145-404:cvn:ct3:cvr:

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

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


[Desktop-packages] [Bug 1757068] [NEW] Night light brakes when screen dims

2018-03-20 Thread Firen
Public bug reported:

I'm using the night light function in Budgie which is set to a
temperature of 4000 and the schedule is set from sunset to sunrise. When
my display dims after X minutes of inactivity the night light function
breaks which results in a much blue-er screen. When I move my mouse the
dimming effect dissapears but and the temperature and brightness of my
screen go back to the default value as if the night light function isn't
on. Disabling and enabling the night light function fixes the issue
until my screen dims again.

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

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

Title:
  Night light brakes when screen dims

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

Bug description:
  I'm using the night light function in Budgie which is set to a
  temperature of 4000 and the schedule is set from sunset to sunrise.
  When my display dims after X minutes of inactivity the night light
  function breaks which results in a much blue-er screen. When I move my
  mouse the dimming effect dissapears but and the temperature and
  brightness of my screen go back to the default value as if the night
  light function isn't on. Disabling and enabling the night light
  function fixes the issue until my screen dims again.

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

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


[Desktop-packages] [Bug 1757068] Re: Night light brakes when screen dims

2018-03-20 Thread Firen
Sorry, I think I've created this bug on the wrong package (so the wrong
place). But I have no idea where it should go. My apologies.

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

Title:
  Night light brakes when screen dims

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

Bug description:
  I'm using the night light function in Budgie which is set to a
  temperature of 4000 and the schedule is set from sunset to sunrise.
  When my display dims after X minutes of inactivity the night light
  function breaks which results in a much blue-er screen. When I move my
  mouse the dimming effect dissapears but and the temperature and
  brightness of my screen go back to the default value as if the night
  light function isn't on. Disabling and enabling the night light
  function fixes the issue until my screen dims again.

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

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


[Desktop-packages] [Bug 1755144] Re: No audio on vlc or videos sound or video files

2018-03-20 Thread John Rose
Yes you're correct in that I meant totem (not vlc) when I was referring to 
playing a video file after "sudo apt remove gstreamer1.0-libav".
When you say a complete reinstall, do you mean a complete reinstall of Ubuntu? 
Isn't there a way of removing ffmpeg packages and reinstalling them?

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

Title:
  No audio on vlc or videos sound or video files

Status in ffmpeg package in Ubuntu:
  New
Status in pulseaudio package in Ubuntu:
  Invalid

Bug description:
  Up until a few weeks ago there was no problem with playing sound from mp3 
files. I have a pair of usb speakers. Audio plays Ok on them for video clips 
using Chrome (e.g. from BBC website). Using vlc 2.2.2 (from Ubuntu repos), 
neither a CD nor DVD (video is Ok) nor mp3 file plays audio. mp3 files play Ok 
using Rhythmbox. I've also tried vlc 3.0 with no success.
  Interestingly, the standard Videos app (Totem?) also doesn't play sound on 
these speakers either of an mp4 file (downloaded from YouTube, though it plays 
Ok on YouTube website using Chrome) or a DVD. Clemenetine plays mp3 files Ok. I 
first reported this as bug 1752267 as I thought that the problem was with vlc. 
On that bug, it was suggested that the problem is with Pulseaudio.
  Just now, I've tried to play sound through my monitor's built in speakers 
connected by hdmi (though the monitor displays Ok) with no success even though 
the built-in speakers play sound using pavucontrol when testing is invoked.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: pulseaudio 1:8.0-0ubuntu3.8
  ProcVersionSignature: Ubuntu 4.4.0-116.140-generic 4.4.98
  Uname: Linux 4.4.0-116-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  john   2410 F pulseaudio
   /dev/snd/controlC0:  john   2410 F pulseaudio
  CurrentDesktop: Unity
  Date: Mon Mar 12 11:06:46 2018
  InstallationDate: Installed on 2016-12-08 (458 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/04/2015
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: PYBSWCEL.86A.0043.2015.0904.1904
  dmi.board.name: NUC5CPYB
  dmi.board.vendor: Intel Corporation
  dmi.board.version: H61145-404
  dmi.chassis.type: 3
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrPYBSWCEL.86A.0043.2015.0904.1904:bd09/04/2015:svn:pn:pvr:rvnIntelCorporation:rnNUC5CPYB:rvrH61145-404:cvn:ct3:cvr:

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

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


[Desktop-packages] [Bug 1755144] Re: No audio on vlc or videos sound or video files

2018-03-20 Thread Daniel van Vugt
We already reinstalled the ffmpeg (libav) packages in comment #19-#20.

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

Title:
  No audio on vlc or videos sound or video files

Status in ffmpeg package in Ubuntu:
  New
Status in pulseaudio package in Ubuntu:
  Invalid

Bug description:
  Up until a few weeks ago there was no problem with playing sound from mp3 
files. I have a pair of usb speakers. Audio plays Ok on them for video clips 
using Chrome (e.g. from BBC website). Using vlc 2.2.2 (from Ubuntu repos), 
neither a CD nor DVD (video is Ok) nor mp3 file plays audio. mp3 files play Ok 
using Rhythmbox. I've also tried vlc 3.0 with no success.
  Interestingly, the standard Videos app (Totem?) also doesn't play sound on 
these speakers either of an mp4 file (downloaded from YouTube, though it plays 
Ok on YouTube website using Chrome) or a DVD. Clemenetine plays mp3 files Ok. I 
first reported this as bug 1752267 as I thought that the problem was with vlc. 
On that bug, it was suggested that the problem is with Pulseaudio.
  Just now, I've tried to play sound through my monitor's built in speakers 
connected by hdmi (though the monitor displays Ok) with no success even though 
the built-in speakers play sound using pavucontrol when testing is invoked.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: pulseaudio 1:8.0-0ubuntu3.8
  ProcVersionSignature: Ubuntu 4.4.0-116.140-generic 4.4.98
  Uname: Linux 4.4.0-116-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  john   2410 F pulseaudio
   /dev/snd/controlC0:  john   2410 F pulseaudio
  CurrentDesktop: Unity
  Date: Mon Mar 12 11:06:46 2018
  InstallationDate: Installed on 2016-12-08 (458 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/04/2015
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: PYBSWCEL.86A.0043.2015.0904.1904
  dmi.board.name: NUC5CPYB
  dmi.board.vendor: Intel Corporation
  dmi.board.version: H61145-404
  dmi.chassis.type: 3
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrPYBSWCEL.86A.0043.2015.0904.1904:bd09/04/2015:svn:pn:pvr:rvnIntelCorporation:rnNUC5CPYB:rvrH61145-404:cvn:ct3:cvr:

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

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


[Desktop-packages] [Bug 1730900] Re: "Login Screen" button not present in Region & Language

2018-03-20 Thread Bug Watch Updater
** Changed in: gnome-user-docs
   Status: Confirmed => Fix Released

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

Title:
  "Login Screen" button not present in Region & Language

Status in Gnome Documentation:
  Fix Released
Status in gnome-control-center package in Ubuntu:
  Invalid
Status in gnome-user-docs package in Ubuntu:
  Triaged

Bug description:
  On my Ubuntu 17.10, which was upgraded from 17.04, the Settings ->
  Region & Language window includes a "Login Screen" button at the top
  right, which allows me to set language, format and input sources also
  system wide, i.e. affecting the login screen. The Ask Ubuntu answer
   shows its location.

  However, on an (almost) fresh install of Ubuntu 17.10, that button is
  not present.

  I don't know what the intended design is in this respect.

  * If the button is supposed to be there, some dependency necessary for
  it to function might be missing.

  * If the button is not supposed to be there, is there some other GUI
  way to control those settings system wide?

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-user-docs/+bug/1730900/+subscriptions

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


[Desktop-packages] [Bug 1756901] Re: GNOME Calendar crashes when I try to add my Google Calendar account

2018-03-20 Thread Alexandru Tenie
Moved here: https://gitlab.gnome.org/GNOME/gnome-calendar/issues/264

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

Title:
  GNOME Calendar crashes when I try to add my Google Calendar account

Status in gnome-calendar package in Ubuntu:
  New

Bug description:
  I clicked the following: Manage your calendars -> Calendar settings,
  which led me to the Settings program, the Online Accounts section,
  selected "Google account", entered my data. My data was successfully
  taken. GNOME Calendar did not load my calendar and crashed. Upon
  restarting GNOME Calendar/restarting Ubuntu, it did not load my
  calendar either. Clicking "Synchronise" did not fix the situation
  either.

  Why do I think this is a security vulnerability? I am just a Computer
  Science student, but I imagine something might possibly come in the
  way so that personal data could be taken.

  It happens if I run the vanilla gnome-session as well.

  -Ubuntu Bionic Beaver (development branch), 18.04, on a fresh install.
  -GNOME Calendar version: 3.28.0-1 (Version table: 3.28.0-1 500)
  -What I expected to happen: load my Google Calendar data.
  -What happened instead: crashed, didn't load my Google Calendar data, even if 
my Google account data is loaded my GNOME.

  I hope Apport uploaded the debug information properly. If not, I can
  try to recreate the bug and upload the debug data, if necessary.

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: gnome-calendar 3.28.0-1
  ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7
  Uname: Linux 4.15.0-12-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Mar 19 16:40:14 2018
  ExecutablePath: /usr/bin/gnome-calendar
  InstallationDate: Installed on 2018-03-19 (0 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180319)
  ProcCmdline: /usr/bin/gnome-calendar --gapplication-service
  SegvAnalysis:
   Segfault happened at: 0x7f3513ec4d12 :
mov(%rdi),%rbp
   PC (0x7f3513ec4d12) ok
   source "(%rdi)" (0x2c6e616d656c6f63) not located in a known VMA region 
(needed readable region)!
   destination "%rbp" ok
  SegvReason: reading unknown VMA
  Signal: 11
  SourcePackage: gnome-calendar
  StacktraceTop:
   g_type_check_instance_cast () from 
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   ?? ()
   g_closure_invoke () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   g_signal_emit_valist () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
  Title: gnome-calendar crashed with SIGSEGV in g_type_check_instance_cast()
  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-calendar/+bug/1756901/+subscriptions

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


[Desktop-packages] [Bug 1698792] Re: Activities overview causes increased CPU in Wayland & Xorg

2018-03-20 Thread Daniel van Vugt
** Summary changed:

- gnome-shell high CPU in activities overview
+ Activities overview causes increased CPU in Wayland & Xorg

** This bug is no longer a duplicate of bug 1750197
   Activities overview causes heavy CPU spikes in Wayland & Xorg

** Changed in: gnome-shell (Ubuntu)
 Assignee: (unassigned) => Daniel van Vugt (vanvugt)

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

** Changed in: mutter (Ubuntu)
 Assignee: (unassigned) => Daniel van Vugt (vanvugt)

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

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

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

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

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

Title:
  Activities overview causes increased CPU in Wayland & Xorg

Status in gnome-shell package in Ubuntu:
  In Progress
Status in mutter package in Ubuntu:
  In Progress

Bug description:
  I am reporting this as a separate bug because the earlier bugs apply
  to earlier versions of Ubuntu and have been invalidated.

  My system is Ubuntu 17.04 (updated not clean install)

  The problem occurs after a few hours of work.

  Steps to reproduce:
  1. Keep working on the system for some hours
  2. Press the Left Win key to get into search mode

  What happens then:
  An overview of windows will be displayed. The UI will freeze or become 
unresponsive. Mouse pointed can be moved around but clicking on any window 
thumbnail does not give the focus to it

  Switch to a shell using Ctrl+Alt+F1. Run top. gnome-shell is at the
  top with 100% CPU usage.

  I tried disabling some extensions to see if these cause the problem. I
  also tried changing the gnome-shell theme to default but no impact.
  Problem remains.

  If someone could point me to what more information needs to be
  gathered, I will be happy to provide it.

  Thanks

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: gnome-shell 3.24.2-0ubuntu0.1
  ProcVersionSignature: Ubuntu 4.10.0-22.24-generic 4.10.15
  Uname: Linux 4.10.0-22-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4.1
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Mon Jun 19 16:57:19 2017
  DisplayManager: lightdm
  InstallationDate: Installed on 2017-01-16 (154 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to zesty on 2017-04-17 (62 days ago)

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

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


[Desktop-packages] [Bug 1756380] Re: vaapi VP9 hardware decoding not working anymore in bionic

2018-03-20 Thread Timo Aaltonen
I think this could be fallout caused by stripping the shaders from the
driver package.. which is why building from github works.

building 2.0.0 from github would prove this false/right

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

Title:
  vaapi VP9 hardware decoding not working anymore in bionic

Status in intel-vaapi-driver package in Ubuntu:
  Confirmed
Status in libva package in Ubuntu:
  Invalid

Bug description:
  Hardware: Dell XPS13 9365, i7-7Y75
  System: Ubuntu Bionic Beaver (development branch)

  
  vainfo output on bionic is:

  libva info: VA-API version 1.1.0
  libva info: va_getDriverName() returns 0
  libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/i965_drv_video.so
  libva info: Found init function __vaDriverInit_1_0
  libva info: va_openDriver() returns 0
  vainfo: VA-API version: 1.1 (libva 2.1.0)
  vainfo: Driver version: Intel i965 driver for Intel(R) Kaby Lake - 2.0.0
  vainfo: Supported profile and entrypoints
VAProfileMPEG2Simple:   VAEntrypointVLD
VAProfileMPEG2Simple:   VAEntrypointEncSlice
VAProfileMPEG2Main  :   VAEntrypointVLD
VAProfileMPEG2Main  :   VAEntrypointEncSlice
VAProfileH264ConstrainedBaseline:   VAEntrypointVLD
VAProfileH264ConstrainedBaseline:   VAEntrypointEncSlice
VAProfileH264ConstrainedBaseline:   VAEntrypointEncSliceLP
VAProfileH264Main   :   VAEntrypointVLD
VAProfileH264Main   :   VAEntrypointEncSlice
VAProfileH264Main   :   VAEntrypointEncSliceLP
VAProfileH264High   :   VAEntrypointVLD
VAProfileH264High   :   VAEntrypointEncSlice
VAProfileH264High   :   VAEntrypointEncSliceLP
VAProfileH264MultiviewHigh  :   VAEntrypointVLD
VAProfileH264MultiviewHigh  :   VAEntrypointEncSlice
VAProfileH264StereoHigh :   VAEntrypointVLD
VAProfileH264StereoHigh :   VAEntrypointEncSlice
VAProfileVC1Simple  :   VAEntrypointVLD
VAProfileVC1Main:   VAEntrypointVLD
VAProfileVC1Advanced:   VAEntrypointVLD
VAProfileNone   :   VAEntrypointVideoProc
VAProfileJPEGBaseline   :   VAEntrypointVLD
VAProfileJPEGBaseline   :   VAEntrypointEncPicture
VAProfileVP8Version0_3  :   VAEntrypointVLD
VAProfileHEVCMain   :   VAEntrypointVLD
VAProfileHEVCMain   :   VAEntrypointEncSlice
VAProfileHEVCMain10 :   VAEntrypointVLD
VAProfileHEVCMain10 :   VAEntrypointEncSlice

  As you can see, VP9 entrypoints are missing.

  vainfo output on 17.10 was:

  libva info: VA-API version 0.40.0
  libva info: va_getDriverName() returns 0
  libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/i965_drv_video.so
  libva info: Found init function __vaDriverInit_0_40
  libva info: va_openDriver() returns 0
  vainfo: VA-API version: 0.40 (libva )
  vainfo: Driver version: Intel i965 driver for Intel(R) Kabylake - 1.8.3
  vainfo: Supported profile and entrypoints
VAProfileMPEG2Simple:VAEntrypointVLD
VAProfileMPEG2Simple:VAEntrypointEncSlice
VAProfileMPEG2Main  :VAEntrypointVLD
VAProfileMPEG2Main  :VAEntrypointEncSlice
VAProfileH264ConstrainedBaseline:VAEntrypointVLD
VAProfileH264ConstrainedBaseline:VAEntrypointEncSlice
VAProfileH264ConstrainedBaseline:VAEntrypointEncSliceLP
VAProfileH264Main   :VAEntrypointVLD
VAProfileH264Main   :VAEntrypointEncSlice
VAProfileH264Main   :VAEntrypointEncSliceLP
VAProfileH264High   :VAEntrypointVLD
VAProfileH264High   :VAEntrypointEncSlice
VAProfileH264High   :VAEntrypointEncSliceLP
VAProfileH264MultiviewHigh  :VAEntrypointVLD
VAProfileH264MultiviewHigh  :VAEntrypointEncSlice
VAProfileH264StereoHigh :VAEntrypointVLD
VAProfileH264StereoHigh :VAEntrypointEncSlice
VAProfileVC1Simple  :VAEntrypointVLD
VAProfileVC1Main:VAEntrypointVLD
VAProfileVC1Advanced:VAEntrypointVLD
VAProfileNone   :VAEntrypointVideoProc
VAProfileJPEGBaseline   :VAEntrypointVLD
VAProfileJPEGBaseline   :VAEntrypointEncPicture
VAProfileVP8Version0_3  :VAEntrypointVLD
VAProfileVP8Version0

[Desktop-packages] [Bug 1756380] Re: vaapi VP9 hardware decoding not working anymore in bionic

2018-03-20 Thread Sebastian Stark
I also tried running uupdate on the existing intel-vaapi-driver package
and build and install this. Worked right away.

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

Title:
  vaapi VP9 hardware decoding not working anymore in bionic

Status in intel-vaapi-driver package in Ubuntu:
  Confirmed
Status in libva package in Ubuntu:
  Invalid

Bug description:
  Hardware: Dell XPS13 9365, i7-7Y75
  System: Ubuntu Bionic Beaver (development branch)

  
  vainfo output on bionic is:

  libva info: VA-API version 1.1.0
  libva info: va_getDriverName() returns 0
  libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/i965_drv_video.so
  libva info: Found init function __vaDriverInit_1_0
  libva info: va_openDriver() returns 0
  vainfo: VA-API version: 1.1 (libva 2.1.0)
  vainfo: Driver version: Intel i965 driver for Intel(R) Kaby Lake - 2.0.0
  vainfo: Supported profile and entrypoints
VAProfileMPEG2Simple:   VAEntrypointVLD
VAProfileMPEG2Simple:   VAEntrypointEncSlice
VAProfileMPEG2Main  :   VAEntrypointVLD
VAProfileMPEG2Main  :   VAEntrypointEncSlice
VAProfileH264ConstrainedBaseline:   VAEntrypointVLD
VAProfileH264ConstrainedBaseline:   VAEntrypointEncSlice
VAProfileH264ConstrainedBaseline:   VAEntrypointEncSliceLP
VAProfileH264Main   :   VAEntrypointVLD
VAProfileH264Main   :   VAEntrypointEncSlice
VAProfileH264Main   :   VAEntrypointEncSliceLP
VAProfileH264High   :   VAEntrypointVLD
VAProfileH264High   :   VAEntrypointEncSlice
VAProfileH264High   :   VAEntrypointEncSliceLP
VAProfileH264MultiviewHigh  :   VAEntrypointVLD
VAProfileH264MultiviewHigh  :   VAEntrypointEncSlice
VAProfileH264StereoHigh :   VAEntrypointVLD
VAProfileH264StereoHigh :   VAEntrypointEncSlice
VAProfileVC1Simple  :   VAEntrypointVLD
VAProfileVC1Main:   VAEntrypointVLD
VAProfileVC1Advanced:   VAEntrypointVLD
VAProfileNone   :   VAEntrypointVideoProc
VAProfileJPEGBaseline   :   VAEntrypointVLD
VAProfileJPEGBaseline   :   VAEntrypointEncPicture
VAProfileVP8Version0_3  :   VAEntrypointVLD
VAProfileHEVCMain   :   VAEntrypointVLD
VAProfileHEVCMain   :   VAEntrypointEncSlice
VAProfileHEVCMain10 :   VAEntrypointVLD
VAProfileHEVCMain10 :   VAEntrypointEncSlice

  As you can see, VP9 entrypoints are missing.

  vainfo output on 17.10 was:

  libva info: VA-API version 0.40.0
  libva info: va_getDriverName() returns 0
  libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/i965_drv_video.so
  libva info: Found init function __vaDriverInit_0_40
  libva info: va_openDriver() returns 0
  vainfo: VA-API version: 0.40 (libva )
  vainfo: Driver version: Intel i965 driver for Intel(R) Kabylake - 1.8.3
  vainfo: Supported profile and entrypoints
VAProfileMPEG2Simple:VAEntrypointVLD
VAProfileMPEG2Simple:VAEntrypointEncSlice
VAProfileMPEG2Main  :VAEntrypointVLD
VAProfileMPEG2Main  :VAEntrypointEncSlice
VAProfileH264ConstrainedBaseline:VAEntrypointVLD
VAProfileH264ConstrainedBaseline:VAEntrypointEncSlice
VAProfileH264ConstrainedBaseline:VAEntrypointEncSliceLP
VAProfileH264Main   :VAEntrypointVLD
VAProfileH264Main   :VAEntrypointEncSlice
VAProfileH264Main   :VAEntrypointEncSliceLP
VAProfileH264High   :VAEntrypointVLD
VAProfileH264High   :VAEntrypointEncSlice
VAProfileH264High   :VAEntrypointEncSliceLP
VAProfileH264MultiviewHigh  :VAEntrypointVLD
VAProfileH264MultiviewHigh  :VAEntrypointEncSlice
VAProfileH264StereoHigh :VAEntrypointVLD
VAProfileH264StereoHigh :VAEntrypointEncSlice
VAProfileVC1Simple  :VAEntrypointVLD
VAProfileVC1Main:VAEntrypointVLD
VAProfileVC1Advanced:VAEntrypointVLD
VAProfileNone   :VAEntrypointVideoProc
VAProfileJPEGBaseline   :VAEntrypointVLD
VAProfileJPEGBaseline   :VAEntrypointEncPicture
VAProfileVP8Version0_3  :VAEntrypointVLD
VAProfileVP8Version0_3  :VAEntrypointEncSlice
VAProfileHEVCMain

[Desktop-packages] [Bug 1750197] Re: App drawer animation causes heavy CPU spikes in Wayland & Xorg

2018-03-20 Thread Daniel van Vugt
Sorry, I just realised these are indeed two very different bugs.

I am moving to bug 1698792 to focus on the activities overview.

P.S. I also have a patch which should help this bug 1750197 a bit:
https://gitlab.gnome.org/GNOME/mutter/merge_requests/26

P.P.S. Please use only Xorg sessions for now if you need the best performance. 
Wayland has its own unique performance bottlenecks I will work on later, 
probably in 18.10:
https://trello.com/c/Q6JYXPPs



** Summary changed:

- Activities overview causes heavy CPU spikes in Wayland & Xorg
+ App drawer animation causes heavy CPU spikes in Wayland & Xorg

** Changed in: gnome-shell (Ubuntu)
 Assignee: Daniel van Vugt (vanvugt) => (unassigned)

** Changed in: mutter (Ubuntu)
 Assignee: Daniel van Vugt (vanvugt) => (unassigned)

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

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

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

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

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

Title:
  App drawer animation causes heavy CPU spikes in Wayland & Xorg

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

Bug description:
  Ubuntu Release: 17.10 and 18.04
  gnome-shell version: 3.26.2
  System Theme: CommuniTheme Beta

  Upon navigating through various areas of the system, GUI animations
  are very stuttery. This heavily affects the CPU usage of my device.
  For instance, opening the shell app drawer displays a very janky
  animation, and my CPU will spike to nearly 85% for each open/close.
  This happens regardless of using XOrg or Wayland; however Wayland
  appears to have an overall lower impact on resource usage. The CPU in
  this laptop isn't the greatest (being a 2014 Celeron), but this is
  noticeably more sluggish compared to previous releases like 16.04 and
  16.10.

  This same issue is still existent, but somewhat less noticeable on my
  other i5-6400 (GTX 1050) machine. Also, emulating this release in a VM
  with 2 CPUS and 4096MB of RAM renders it unresponsive for 3-5 seconds
  after opening/closing the app drawer.

  Please do not hesitate to follow up with requests for more info, as I
  will be happy to help.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.26.2-0ubuntu0.1
  ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  CurrentDesktop: ubuntu-communitheme:ubuntu:GNOME
  Date: Sat Feb 17 19:13:00 2018
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  InstallationDate: Installed on 2018-02-17 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.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/1750197/+subscriptions

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


[Desktop-packages] [Bug 1757088] [NEW] Activities overview causes increased CPU in Wayland & Xorg

2018-03-20 Thread Daniel van Vugt
Public bug reported:

gnome-shell CPU usage increases about another 50% when in activities
overview

** Affects: gnome-shell (Ubuntu)
 Importance: Medium
 Assignee: Daniel van Vugt (vanvugt)
 Status: In Progress

** Affects: mutter (Ubuntu)
 Importance: Medium
 Assignee: Daniel van Vugt (vanvugt)
 Status: In Progress


** Tags: bionic performance

** Summary changed:

- gnome-shell CPU usage increases about another 50% when in activities overview
+ Activities overview causes increased CPU in Wayland & Xorg

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

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

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

** Changed in: mutter (Ubuntu)
 Assignee: (unassigned) => Daniel van Vugt (vanvugt)

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

Title:
  Activities overview causes increased CPU in Wayland & Xorg

Status in gnome-shell package in Ubuntu:
  In Progress
Status in mutter package in Ubuntu:
  In Progress

Bug description:
  gnome-shell CPU usage increases about another 50% when in activities
  overview

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

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


[Desktop-packages] [Bug 1756919] Re: package libreoffice-pdfimport 1:4.4.6~rc3-0ubuntu1 failed to install/upgrade: el subproceso script pre-installation nuevo devolvió el código de salida de error 1

2018-03-20 Thread Olivier Tilloy
*** This bug is a duplicate of bug 1756906 ***
https://bugs.launchpad.net/bugs/1756906

** This bug has been marked a duplicate of bug 1756906
   package libreoffice-calc 1:4.4.6~rc3-0ubuntu1 failed to install/upgrade: el 
subproceso script pre-installation nuevo devolvió el código de salida de error 1

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

Title:
  package libreoffice-pdfimport 1:4.4.6~rc3-0ubuntu1 failed to
  install/upgrade: el subproceso script pre-installation nuevo devolvió
  el código de salida de error 1

Status in libreoffice package in Ubuntu:
  New

Bug description:
  no actualiza

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libreoffice-pdfimport 1:4.4.6~rc3-0ubuntu1
  ProcVersionSignature: Ubuntu 3.19.0-84.92-generic 3.19.8-ckt22
  Uname: Linux 3.19.0-84-generic i686
  NonfreeKernelModules: wl
  ApportVersion: 2.17.2-0ubuntu1.8
  Architecture: i386
  Date: Mon Mar 19 11:38:49 2018
  DuplicateSignature: package:libreoffice-pdfimport:1:4.4.6~rc3-0ubuntu1:el 
subproceso script pre-installation nuevo devolvió el código de salida de error 1
  ErrorMessage: el subproceso script pre-installation nuevo devolvió el código 
de salida de error 1
  InstallationDate: Installed on 2017-11-07 (131 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release i386 (20150422)
  RelatedPackageVersions:
   dpkg 1.17.25ubuntu1.1
   apt  1.0.9.7ubuntu4.2
  SourcePackage: libreoffice
  Title: package libreoffice-pdfimport 1:4.4.6~rc3-0ubuntu1 failed to 
install/upgrade: el subproceso script pre-installation nuevo devolvió el código 
de salida de error 1
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1755030] Re: Dell XPS 13 (9350) problems with suspend to memory fixed after disabling AppArmor

2018-03-20 Thread ktecho
I don't know how, but this got fixed. Maybe one of the latest package
updates fixed it.

Thanks, this bug can be closed.

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

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

Title:
  Dell XPS 13 (9350) problems with suspend to memory fixed after
  disabling AppArmor

Status in xorg package in Ubuntu:
  Invalid

Bug description:
  After installing latest Kubuntu 18.04 daily ISO and upgrading to
  latest packages, I've had problems with suspend functionality:

  0- Kubuntu installed correctly.
  1- From Plasma, choose "Suspend to memory". Screen goes off.
  2- When I power on the notebook, it starts with Grub and then a new Kubuntu 
session starts.
  3- After reading in forums that the problem could be SELinux, I disable 
AppArmor by doing "/etc/init.d/apparmor stop".
  4- From Plasma, choose "Suspend to memory". Screen goes off.
  5- When I power on the notebook, it continues in the same place where I left 
it.

  It seems that AppArmor is screwing Suspend in any way.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu5
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  BootLog: Error: [Errno 13] Permiso denegado: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: KDE
  Date: Sun Mar 11 21:25:04 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: kubuntu
  ExtraDebuggingInterest: No
  GraphicsCard:
   Intel Corporation HD Graphics 520 [8086:1916] (rev 07) (prog-if 00 [VGA 
controller])
 Subsystem: Dell Skylake GT2 [HD Graphics 520] [1028:0704]
  InstallationDate: Installed on 2018-03-11 (0 days ago)
  InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180310)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 0c45:670c Microdia 
   Bus 001 Device 003: ID 0a5c:6412 Broadcom Corp. 
   Bus 001 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. XPS 13 9350
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-10-generic.efi.signed 
root=UUID=007be772-95a8-4b68-9f65-de19978e0979 ro quiet splash vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/14/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.6.1
  dmi.board.name: 07TYC2
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A01
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.6.1:bd12/14/2017:svnDellInc.:pnXPS139350:pvr:rvnDellInc.:rn07TYC2:rvrA01:cvnDellInc.:ct9:cvr:
  dmi.product.family: NULL
  dmi.product.name: XPS 13 9350
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.90-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc4-1ubuntu3
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc4-1ubuntu3
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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

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


[Desktop-packages] [Bug 1750197] Re: App drawer animation causes heavy CPU spikes in Wayland & Xorg

2018-03-20 Thread Daniel van Vugt
Sorry, I just realised these are indeed two very different bugs.

I am moving to bug 1757088 to focus on the activities overview.

P.S. I also have a patch which should help this bug 1750197 a bit:
https://gitlab.gnome.org/GNOME/mutter/merge_requests/26

P.P.S. Please use only Xorg sessions for now if you need the best performance. 
Wayland has its own unique performance bottlenecks I will work on later, 
probably in 18.10:
https://trello.com/c/Q6JYXPPs

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

Title:
  App drawer animation causes heavy CPU spikes in Wayland & Xorg

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

Bug description:
  Ubuntu Release: 17.10 and 18.04
  gnome-shell version: 3.26.2
  System Theme: CommuniTheme Beta

  Upon navigating through various areas of the system, GUI animations
  are very stuttery. This heavily affects the CPU usage of my device.
  For instance, opening the shell app drawer displays a very janky
  animation, and my CPU will spike to nearly 85% for each open/close.
  This happens regardless of using XOrg or Wayland; however Wayland
  appears to have an overall lower impact on resource usage. The CPU in
  this laptop isn't the greatest (being a 2014 Celeron), but this is
  noticeably more sluggish compared to previous releases like 16.04 and
  16.10.

  This same issue is still existent, but somewhat less noticeable on my
  other i5-6400 (GTX 1050) machine. Also, emulating this release in a VM
  with 2 CPUS and 4096MB of RAM renders it unresponsive for 3-5 seconds
  after opening/closing the app drawer.

  Please do not hesitate to follow up with requests for more info, as I
  will be happy to help.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.26.2-0ubuntu0.1
  ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  CurrentDesktop: ubuntu-communitheme:ubuntu:GNOME
  Date: Sat Feb 17 19:13:00 2018
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  InstallationDate: Installed on 2018-02-17 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.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/1750197/+subscriptions

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


[Desktop-packages] [Bug 1698792] Re: Activities overview causes increased CPU in Wayland & Xorg

2018-03-20 Thread Daniel van Vugt
Ah, sorry. This is also the wrong bug.


** Tags added: artful bionic

** Summary changed:

- Activities overview causes increased CPU in Wayland & Xorg
+ Activities overview freezes and becomes unresponsive after a few hours

** Changed in: gnome-shell (Ubuntu)
 Assignee: Daniel van Vugt (vanvugt) => (unassigned)

** Changed in: mutter (Ubuntu)
 Assignee: Daniel van Vugt (vanvugt) => (unassigned)

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

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

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

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

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

Title:
  Activities overview freezes and becomes unresponsive after a few hours

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

Bug description:
  I am reporting this as a separate bug because the earlier bugs apply
  to earlier versions of Ubuntu and have been invalidated.

  My system is Ubuntu 17.04 (updated not clean install)

  The problem occurs after a few hours of work.

  Steps to reproduce:
  1. Keep working on the system for some hours
  2. Press the Left Win key to get into search mode

  What happens then:
  An overview of windows will be displayed. The UI will freeze or become 
unresponsive. Mouse pointed can be moved around but clicking on any window 
thumbnail does not give the focus to it

  Switch to a shell using Ctrl+Alt+F1. Run top. gnome-shell is at the
  top with 100% CPU usage.

  I tried disabling some extensions to see if these cause the problem. I
  also tried changing the gnome-shell theme to default but no impact.
  Problem remains.

  If someone could point me to what more information needs to be
  gathered, I will be happy to provide it.

  Thanks

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: gnome-shell 3.24.2-0ubuntu0.1
  ProcVersionSignature: Ubuntu 4.10.0-22.24-generic 4.10.15
  Uname: Linux 4.10.0-22-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4.1
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Mon Jun 19 16:57:19 2017
  DisplayManager: lightdm
  InstallationDate: Installed on 2017-01-16 (154 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to zesty on 2017-04-17 (62 days ago)

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

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


[Desktop-packages] [Bug 1698792] Re: Activities overview freezes and becomes unresponsive after a few hours

2018-03-20 Thread Daniel van Vugt
Thank you for reporting this bug to Ubuntu.
Ubuntu 17.04 (zesty) reached end-of-life on January 13, 2018.

See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases

We appreciate that this bug may be old and you might not be interested
in discussing it any more. But if you are then please upgrade to the
latest Ubuntu version and re-test.


** Tags removed: artful bionic

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

Title:
  Activities overview freezes and becomes unresponsive after a few hours

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

Bug description:
  I am reporting this as a separate bug because the earlier bugs apply
  to earlier versions of Ubuntu and have been invalidated.

  My system is Ubuntu 17.04 (updated not clean install)

  The problem occurs after a few hours of work.

  Steps to reproduce:
  1. Keep working on the system for some hours
  2. Press the Left Win key to get into search mode

  What happens then:
  An overview of windows will be displayed. The UI will freeze or become 
unresponsive. Mouse pointed can be moved around but clicking on any window 
thumbnail does not give the focus to it

  Switch to a shell using Ctrl+Alt+F1. Run top. gnome-shell is at the
  top with 100% CPU usage.

  I tried disabling some extensions to see if these cause the problem. I
  also tried changing the gnome-shell theme to default but no impact.
  Problem remains.

  If someone could point me to what more information needs to be
  gathered, I will be happy to provide it.

  Thanks

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: gnome-shell 3.24.2-0ubuntu0.1
  ProcVersionSignature: Ubuntu 4.10.0-22.24-generic 4.10.15
  Uname: Linux 4.10.0-22-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4.1
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Mon Jun 19 16:57:19 2017
  DisplayManager: lightdm
  InstallationDate: Installed on 2017-01-16 (154 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to zesty on 2017-04-17 (62 days ago)

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

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


[Desktop-packages] [Bug 1757091] [NEW] systemctl enable lightdm

2018-03-20 Thread jose hayek
Public bug reported:

Synchronizing state of lightdm.service with SysV service script with 
/lib/systemd/systemd-sysv-install.
Executing: /lib/systemd/systemd-sysv-install enable lightdm
The unit files have no installation config (WantedBy, RequiredBy, Also, Alias
settings in the [Install] section, and DefaultInstance for template units).
This means they are not meant to be enabled using systemctl.
Possible reasons for having this kind of units are:
1) A unit may be statically enabled by being symlinked from another unit's
   .wants/ or .requires/ directory.
2) A unit's purpose may be to act as a helper for some other unit which has
   a requirement dependency on it.
3) A unit may be started when needed via activation (socket, path, timer,
   D-Bus, udev, scripted systemctl call, ...).
4) In case of template units, the unit is meant to be enabled with some
   instance name specified.

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: lightdm 1.24.0-0ubuntu1
ProcVersionSignature: Ubuntu 4.13.0-37.42-generic 4.13.13
Uname: Linux 4.13.0-37-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
ApportVersion: 2.20.7-0ubuntu3.7
Architecture: amd64
Date: Tue Mar 20 11:44:46 2018
InstallationDate: Installed on 2018-01-22 (57 days ago)
InstallationMedia: Ubuntu-Server 17.10 "Artful Aardvark" - Release amd64 
(20171017.1)
ProcEnviron:
 TERM=xterm
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: lightdm
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug artful third-party-packages

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

Title:
  systemctl enable lightdm

Status in lightdm package in Ubuntu:
  New

Bug description:
  Synchronizing state of lightdm.service with SysV service script with 
/lib/systemd/systemd-sysv-install.
  Executing: /lib/systemd/systemd-sysv-install enable lightdm
  The unit files have no installation config (WantedBy, RequiredBy, Also, Alias
  settings in the [Install] section, and DefaultInstance for template units).
  This means they are not meant to be enabled using systemctl.
  Possible reasons for having this kind of units are:
  1) A unit may be statically enabled by being symlinked from another unit's
 .wants/ or .requires/ directory.
  2) A unit's purpose may be to act as a helper for some other unit which has
 a requirement dependency on it.
  3) A unit may be started when needed via activation (socket, path, timer,
 D-Bus, udev, scripted systemctl call, ...).
  4) In case of template units, the unit is meant to be enabled with some
 instance name specified.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: lightdm 1.24.0-0ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-37.42-generic 4.13.13
  Uname: Linux 4.13.0-37-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  Date: Tue Mar 20 11:44:46 2018
  InstallationDate: Installed on 2018-01-22 (57 days ago)
  InstallationMedia: Ubuntu-Server 17.10 "Artful Aardvark" - Release amd64 
(20171017.1)
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: lightdm
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1631424] Re: GTK theme is not applied in Classic session

2018-03-20 Thread Daniel van Vugt
Thank you for reporting this bug to Ubuntu.
Ubuntu 16.10 (yakkety) reached end-of-life on July 20, 2017.

See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases 

We appreciate that this bug may be old and you might not be interested
in discussing it any more. But if you are then please upgrade to the
latest Ubuntu version and re-test. If you then find the bug is still
present in the newer Ubuntu version, please add a comment here telling
us which new version it is in and change the bug status to Confirmed.


** Changed in: gnome-session (Ubuntu)
   Status: Confirmed => Incomplete

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

Title:
  GTK theme is not applied in Classic session

Status in gnome-session package in Ubuntu:
  Incomplete

Bug description:
  The Adwaita GTK theme is not applied to the Classic session.
  Instead it forces the Ubuntu Ambiance theme.

  I can chose to use Adwaita in GNOME Tweak Tool and it works in GNOME
  but not in GNOME Classic session.

  This is a regression, it worked fine 2-3 days ago. Then the Unity 8 /
  Mir thing was pushed out, and that's when it broke.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: gnome-session 3.20.2-1ubuntu7
  ProcVersionSignature: Ubuntu 4.8.0-19.21-generic 4.8.0-rc8
  Uname: Linux 4.8.0-19-generic x86_64
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: amd64
  CurrentDesktop: GNOME-Classic:GNOME
  Date: Fri Oct  7 18:10:06 2016
  InstallationDate: Installed on 2013-12-26 (1015 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  PackageArchitecture: all
  SourcePackage: gnome-session
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1639536] Re: gnome-session-inhibit passes arguments to execvp incorrectly

2018-03-20 Thread Daniel van Vugt
Thank you for reporting this bug to Ubuntu.
Ubuntu 16.10 (yakkety) reached end-of-life on July 20, 2017.

See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases 

We appreciate that this bug may be old and you might not be interested
in discussing it any more. But if you are then please upgrade to the
latest Ubuntu version and re-test. If you then find the bug is still
present in the newer Ubuntu version, please add a comment here telling
us which new version it is in and change the bug status to Confirmed.


** Changed in: gnome-session (Ubuntu)
   Status: Confirmed => Incomplete

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

Title:
  gnome-session-inhibit passes arguments to execvp incorrectly

Status in gnome-session package in Ubuntu:
  Incomplete

Bug description:
  steps to reproduce:

  gnome-session-inhibit sh -c "sleep 10"

  Excepted result is of course wait for 10 seconds before termination.

  Actual result:
  Failed to open "sleep 10"

  That is causes because shell ignores the first argument that should be
  the program name. But inhibit passes "-c" as the first argument.

  Attached patch fixes the inhibit to work correctly. Exactly like sudo,
  parallel, systemd-inhibit or any similar program works.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: gnome-session-bin 3.20.2-1ubuntu7
  ProcVersionSignature: Ubuntu 4.8.0-26.28-generic 4.8.0
  Uname: Linux 4.8.0-26-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Sun Nov  6 07:22:38 2016
  InstallationDate: Installed on 2037-12-25 (-7719 days ago)
  InstallationMedia: Lubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  SourcePackage: gnome-session
  UpgradeStatus: Upgraded to yakkety on 2016-10-21 (15 days ago)

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

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


[Desktop-packages] [Bug 1686081] Re: If -synaptics is installed, GNOME Mouse & Touchpad Settings doesn't work

2018-03-20 Thread Alex
Hello!

After these patches gnome no longer respects settings in
/etc/X11/xorg.conf.d/*-synaptics.conf file, like Option "TapButton1"
"1", Option "TapButton2" "2", Option "TapButton3" "3" etc.

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

Title:
  If -synaptics is installed, GNOME Mouse & Touchpad Settings doesn't
  work

Status in Release Notes for Ubuntu:
  Fix Released
Status in gnome-control-center package in Ubuntu:
  Fix Released
Status in gtk+3.0 package in Ubuntu:
  In Progress
Status in mutter package in Ubuntu:
  Fix Released
Status in xorg package in Ubuntu:
  Invalid
Status in xubuntu-meta package in Ubuntu:
  Fix Released
Status in gnome-control-center source package in Artful:
  Confirmed
Status in mutter source package in Artful:
  Confirmed
Status in xorg source package in Artful:
  Invalid
Status in xubuntu-meta source package in Artful:
  Fix Released

Bug description:
  I'm splitting this issue off from LP: #1685542 (which made xserver-
  xorg-input-all no longer recommend xserver-xorg-input-synaptics) for
  tracking the remaining issues.

  gnome-control-center only supports libinput. If xserver-xorg-input-
  synaptics is installed (because it's used by some desktops which
  haven't been ported to libinput yet), synaptics overrides libinput.
  That makes gnome-control-center's Mouse & Touchpad settings panel only
  show basic settings and important configurations don't work.

  Questions
  -
  1. Which desktops/apps still need -synaptics?
  - Unity
  - Xfce?
  - LXDE? LXQt?
  All the other major desktops have already been ported (LP: #1417980)

  2. Can these apps be ported or removed before 18.04 LTS is released?

  3. Can the desktops be ported and how bad is it if they are not ported
  and -synaptics is no longer available?

  4. If -synaptics can't be removed completely from 18.04 LTS, does it
  make sense to have gnome-control-center Conflicts: xserver-xorg-input-
  synaptics?

  5. Is there any other way we can fix this conflict?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-release-notes/+bug/1686081/+subscriptions

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


[Desktop-packages] [Bug 1669531] Re: gnome-session-binary crashed with SIGABRT in g_assertion_message()

2018-03-20 Thread Daniel van Vugt
Thank you for reporting this bug to Ubuntu.
Ubuntu 17.04 (zesty) reached end-of-life on January 13, 2018.

See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases 

We appreciate that this bug may be old and you might not be interested
in discussing it any more. But if you are then please upgrade to the
latest Ubuntu version and re-test. If you then find the bug is still
present in the newer Ubuntu version, please add a comment here telling
us which new version it is in and change the bug status to Confirmed.

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

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

Title:
  gnome-session-binary crashed with SIGABRT in g_assertion_message()

Status in gnome-session package in Ubuntu:
  Incomplete

Bug description:
  This is new with my recent upgrade to 17.04 beta

  ProblemType: Crash
  DistroRelease: Ubuntu 17.04
  Package: gnome-session-bin 3.23.91-0ubuntu1
  ProcVersionSignature: Ubuntu 4.10.0-11.13-generic 4.10.1
  Uname: Linux 4.10.0-9-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.4-0ubuntu2
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: Unity:Unity7
  Date: Thu Mar  2 09:50:19 2017
  ExecutablePath: /usr/lib/gnome-session/gnome-session-binary
  InstallationDate: Installed on 2015-12-17 (440 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  ProcCmdline: /usr/lib/gnome-session/gnome-session-binary --session=ubuntu
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  Signal: 6
  SourcePackage: gnome-session
  StacktraceTop:
   g_assertion_message () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_assertion_message_expr () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? ()
   g_closure_invoke () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
  Title: gnome-session-binary crashed with SIGABRT in g_assertion_message()
  UpgradeStatus: Upgraded to zesty on 2017-02-14 (15 days ago)
  UserGroups: adm cdrom dip kismet libvirt lpadmin plugdev sambashare sudo 
ubridge

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

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


[Desktop-packages] [Bug 1708497] Re: gpg-agent not started automatically

2018-03-20 Thread Daniel van Vugt
Thank you for reporting this bug to Ubuntu.
Ubuntu 17.04 (zesty) reached end-of-life on January 13, 2018.

See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases 

We appreciate that this bug may be old and you might not be interested
in discussing it any more. But if you are then please upgrade to the
latest Ubuntu version and re-test. If you then find the bug is still
present in the newer Ubuntu version, please add a comment here telling
us which new version it is in and change the bug status to Confirmed.


** Changed in: gnome-session (Ubuntu)
   Status: Confirmed => Incomplete

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

Title:
  gpg-agent not started automatically

Status in gnome-session package in Ubuntu:
  Incomplete

Bug description:
  My suspicion is that there's an issue with gnome-session, but that's
  somewhat of a guess. systemd isn't starting the graphical-session-
  pre.target, which would start gpg-agent.service. This is on a fresh
  zesty install with minimal packages added.

  What I expect to see:

  pgrep gpg-agent

  This should report a process ID. Instead I see it is not running.
  Configuring gpg to use the agent results in errors because gpg can't
  communicate with an agent that doesn't exist.

  What additional information can I provide that would be of benefit?

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: gnome-session 3.24.0-0ubuntu1
  ProcVersionSignature: Ubuntu 4.10.0-30.34-generic 4.10.17
  Uname: Linux 4.10.0-30-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4.5
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Thu Aug  3 12:17:06 2017
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2017-07-15 (19 days ago)
  InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-session
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1628179] Re: gnome-session does not show version info

2018-03-20 Thread Daniel van Vugt
Thank you for reporting this bug to Ubuntu.
Ubuntu 16.10 (yakkety) reached end-of-life on July 20, 2017.

See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases 

We appreciate that this bug may be old and you might not be interested
in discussing it any more. But if you are then please upgrade to the
latest Ubuntu version and re-test. If you then find the bug is still
present in the newer Ubuntu version, please add a comment here telling
us which new version it is in and change the bug status to Confirmed.

** Changed in: gnome-session (Ubuntu)
   Status: Triaged => Incomplete

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

Title:
  gnome-session does not show version info

Status in gnome-session package in Ubuntu:
  Incomplete

Bug description:
  Following command has no output.
  $ gnome-session --version
  However, help says,
  $ gnome-session --help
  Usage:
gnome-session-binary [OPTION...]  - the GNOME session manager

  Help Options:
-h, --helpShow help options

  Application Options:
-a, --autostart=AUTOSTART_DIR Override standard autostart directories
--session=SESSION_NAMESession to use
--debug   Enable debugging code
-f, --failsafeDo not load user-specified applications
--version Version of this application
--whale   Show the fail whale dialog for testing
--disable-acceleration-check  Disable hardware acceleration check

  Also, in man, there in no entry for gnome-session.

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

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


[Desktop-packages] [Bug 1662281] Re: Firefox shows post-crash page after reboot or logoff

2018-03-20 Thread Daniel van Vugt
** Bug watch removed: GNOME Bug Tracker #779306
   https://bugzilla.gnome.org/show_bug.cgi?id=779306

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

Title:
  Firefox shows post-crash page after reboot or logoff

Status in gnome-session:
  Invalid
Status in firefox package in Ubuntu:
  Incomplete
Status in gnome-session package in Ubuntu:
  Incomplete

Bug description:
  When rebooting or logging off, Firefox and thinks it crashed, and
  shows the post-crash session restore  page.

  See also Mozilla bug
  https://bugzilla.mozilla.org/show_bug.cgi?id=557601 and related bugs
  there.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: firefox 51.0.1+build2-0ubuntu0.16.10.2
  ProcVersionSignature: Ubuntu 4.8.0-37.39-generic 4.8.16
  Uname: Linux 4.8.0-37-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  AddonCompatCheckDisabled: False
  ApportVersion: 2.20.3-0ubuntu8.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  reuben 1902 F pulseaudio
   /dev/snd/controlC1:  reuben 1902 F pulseaudio
  BuildID: 20170201174907
  Channel: Unavailable
  CurrentDesktop: Unity
  Date: Mon Feb  6 16:04:15 2017
  Extensions: extensions.sqlite corrupt or missing
  ForcedLayersAccel: False
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  IncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
  InstallationDate: Installed on 2017-02-02 (3 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  IpRoute:
   default via 192.168.2.1 dev enp0s31f6  proto static  metric 100 
   169.254.0.0/16 dev enp0s31f6  scope link  metric 1000 
   192.168.2.0/24 dev enp0s31f6  proto kernel  scope link  src 192.168.2.6  
metric 100
  IwConfig:
   enp0s31f6  no wireless extensions.
   
   lono wireless extensions.
  Locales: extensions.sqlite corrupt or missing
  Plugins: Shockwave Flash - /usr/lib/flashplugin-installer/libflashplayer.so
  PrefSources: prefs.js
  Profiles: Profile0 (Default) - LastVersion=51.0.1/20170201174907 (In use)
  RfKill:
   
  RunningIncompatibleAddons: False
  SourcePackage: firefox
  Themes: extensions.sqlite corrupt or missing
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/20/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0225
  dmi.board.asset.tag: Default string
  dmi.board.name: TUF Z270 MARK 2
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0225:bd10/20/2016:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnTUFZ270MARK2:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

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

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


[Desktop-packages] [Bug 1599327] Re: gnome-session crashes with pixman_region32_init_rect: Invalid rectangle passed

2018-03-20 Thread Daniel van Vugt
Thank you for reporting this bug to Ubuntu.
Ubuntu 16.10 (yakkety) reached end-of-life on July 20, 2017.

See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases 

We appreciate that this bug may be old and you might not be interested
in discussing it any more. But if you are then please upgrade to the
latest Ubuntu version and re-test. If you then find the bug is still
present in the newer Ubuntu version, please add a comment here telling
us which new version it is in and change the bug status to Confirmed.


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

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

Title:
  gnome-session crashes with pixman_region32_init_rect: Invalid
  rectangle passed

Status in gnome-session package in Ubuntu:
  Incomplete

Bug description:
  When the problem appears, all the computer screens stop showing the apps (and 
unity) for a moment, then everything recovers, including the apps. It's simply 
annoying because it's surprising and it takes a moment to recover.
  I get this messages in journalctl, repeated multiple times:

  Jul 06 07:40:44 maldita gnome-session[4791]: *** BUG ***
  Jul 06 07:40:44 maldita gnome-session[4791]: In pixman_region32_init_rect: 
Invalid rectangle passed
  Jul 06 07:40:44 maldita gnome-session[4791]: Set a breakpoint on 
'_pixman_log_error' to debug

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: gnome-session 3.18.1.2-1ubuntu2
  ProcVersionSignature: Ubuntu 4.4.0-30.49-generic 4.4.13
  Uname: Linux 4.4.0-30-generic x86_64
  ApportVersion: 2.20.2-0ubuntu1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Wed Jul  6 07:42:38 2016
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2012-11-25 (1318 days ago)
  InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Alpha amd64 (20120627)
  PackageArchitecture: all
  ProcEnviron:
   LANGUAGE=en_SG:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_SG.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-session
  UpgradeStatus: Upgraded to yakkety on 2015-03-14 (479 days ago)

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

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


[Desktop-packages] [Bug 971051] Re: No Alt+Tab in gnome classic session (switcher plugin not loaded)

2018-03-20 Thread Daniel van Vugt
** Changed in: gnome-session (Ubuntu)
   Status: New => Invalid

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

Title:
  No Alt+Tab in gnome classic session (switcher plugin not loaded)

Status in Compiz:
  Invalid
Status in Ubuntu GNOME Flashback:
  New
Status in compiz package in Ubuntu:
  Fix Released
Status in gnome-session package in Ubuntu:
  Invalid
Status in Baltix:
  New

Bug description:
  When using the Gnome Classic session (with Compiz) in Ubuntu Precise
  Pangolin, I cannot use alt + tab to switch applications.

  WORKAROUND:
  1. Install packages:
 sudo apt-get install compiz-plugins compizconfig-settings-manager
  2. Run "ccsm"
  3. Scroll down to Window Management and enable (tick) "Application Switcher".

  
  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: gnome-panel 1:3.4.0-0ubuntu1
  Uname: Linux 3.3.0-030300-generic x86_64
  ApportVersion: 2.0-0ubuntu2
  Architecture: amd64
  Date: Sun Apr  1 21:01:11 2012
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Alpha amd64 
(20120108)
  ProcEnviron:
   LANGUAGE=en_GB:en
   TERM=xterm
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-panel
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1509079] Re: logging in to gnome wayland show blank screen and lightdm is restarted

2018-03-20 Thread Daniel van Vugt
Thank you for reporting this bug to Ubuntu.
Ubuntu 15.10 (wily) reached end-of-life on July 28, 2016.

See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases 

We appreciate that this bug may be old and you might not be interested
in discussing it any more. But if you are then please upgrade to the
latest Ubuntu version and re-test. If you then find the bug is still
present in the newer Ubuntu version, please add a comment here telling
us which new version it is in and change the bug status to Confirmed.


** Changed in: gnome-session (Ubuntu)
   Status: Confirmed => Incomplete

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

Title:
  logging in to gnome wayland show blank screen and lightdm is restarted

Status in gnome-session package in Ubuntu:
  Incomplete

Bug description:
  I select the Gnome on Wayland login option, then type my password in
  and press Enter. A blank screen with a blinking cursor appears, and
  then I am thrown back into the lightdm login screen, without any error
  message. I am attaching the lightdm.log which has some intriguing
  error messages.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: gnome-session-wayland 3.16.0-1ubuntu2
  ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3
  Uname: Linux 4.2.0-16-generic i686
  ApportVersion: 2.19.1-0ubuntu3
  Architecture: i386
  CurrentDesktop: Unity
  Date: Thu Oct 22 22:06:22 2015
  InstallationDate: Installed on 2013-08-17 (796 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release i386 (20130424)
  SourcePackage: gnome-session
  UpgradeStatus: Upgraded to wily on 2015-10-22 (0 days ago)

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

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


[Desktop-packages] [Bug 1474182] Re: Mystery keyring password prompts pop up for no reason

2018-03-20 Thread Daniel van Vugt
Thank you for reporting this bug to Ubuntu.
Ubuntu 15.04 (vivid) reached end-of-life on February 4, 2016.

See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases 

We appreciate that this bug may be old and you might not be interested
in discussing it any more. But if you are then please upgrade to the
latest Ubuntu version and re-test. If you then find the bug is still
present in the newer Ubuntu version, please add a comment here telling
us which new version it is in and change the bug status to Confirmed.


** Changed in: gnome-session (Ubuntu)
   Status: Confirmed => Invalid

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

Title:
  Mystery keyring password prompts pop up for no reason

Status in gnome-session package in Ubuntu:
  Invalid

Bug description:
  A prompt box periodically pops up for no apparent reason asking me for
  my default keyring password.If I click Cancel, it re-appears again
  after a few minutes.  There is absolutely no information about what
  program is asking or why.   Is this a phishing scam?!?

  I'm marking this as "security vulnerability" because the "mystery"
  prompt is asking for extremely sensitive information which users
  should not give out without knowing what program will use it.

  * My homedir is not encrypted
  * I do use automatic login, but it succeeded and everything works, including 
network.
  * My system has slept/resumed a few times (don't know if that's relevant)
  * I use a wired Ethernet connection, not WiFi (so no password is needed for 
network access).
  * I am not running any commands that I know of which use encryption or 
require access to my private keys.

  Since I am  not doing anything which actually requires my private key,
  something is asking to unlock the keyring wrongly;

  Or else a background process (or trojan) is trying to communicate with
  somebody behind my back, using my private keys.

  This seems to be new (REGRESSION) as of 15.04, it did not occur before
  upgrading.

  The programs I *am* running are:
   *  Firefox
   * Thunderbird (I typed in it's Master Password previously, and it is working 
fine)
   *  Terminals
   *  A Java based web app (Interactive Brokers Trader Workstation)

  /var/log/auth.log contains the following:

  : Executing command [USER=root] [TTY=unknown] 
[CWD=/home/] [COMMAND=/usr/lib/update-notifier/package-system-locked]
  bus acquired: org.gnome.keyring.SystemPrompter
  Gcr: registering prompter
  bus acquired: org.gnome.keyring.PrivatePrompter
  Gcr: received BeginPrompting call from callback 
/org/gnome/keyring/Prompt/p22@:1.259
  Gcr: preparing a prompt for callback /org/gnome/keyring/Prompt/p22@:1.259
  Gcr: creating new GcrPromptDialog prompt
  Gcr: automatically selecting secret exchange protocol
  Gcr: generating public key
  Gcr: beginning the secret exchange: 
[sx-aes-1]\npublic=RnT9opj6kZDvJpr8QyIBH4DE/xn3wid1Di7mdEuIgT/GCBA1mLB3VdsldoT6WMdJeD15xlSIvvmAiLLR59dffthvV+cifN3K1WoJhFdBDSiBLmkI4wfGXEnQTmJn7iZfyGWsIVqL5cSgG3AEMGKgY4ORzBARp8TLqjnfnoJB3YSh/gNFVs5OT5pCATNeaDN1mx9LzOCuCSwVDXIIY6uV8sjhBpBvQQCNNEV960L2pZYvGsBYMKeriKxvZAJfiO04\n
  Gcr: calling the PromptReady method on /org/gnome/keyring/Prompt/p22@:1.259
  acquired name: org.gnome.keyring.SystemPrompter
  acquired name: org.gnome.keyring.PrivatePrompter
  Gcr: returned from the PromptReady method on 
/org/gnome/keyring/Prompt/p22@:1.259
  Gcr: received PerformPrompt call from callback 
/org/gnome/keyring/Prompt/p22@:1.259
  Gcr: receiving secret exchange: 
[sx-aes-1]\npublic=RL9s/tyPJRw80JDQNBGC+0uQxXfk1uAvJH9XoAULcI4ys/b/Rfz9QNvujXVlhp02Yot7S7K6l5KLBc3i6Ry9SPECjeDm6Y5E4Ry43OmOKjBf7JBUcUvrzfUvwJ87YZ0fYCW8j9nDgrBxt1utCOUDJDHVVANdIK8CMIEXnffiKYjsPq8yjueenqdnM+G8VUoBke8U1Bmc0IHs8elTBBWnoeLQdpnLcpn7k245vO5V4w8Gl3ZZtYrw7t6xxZstRAXR\n
  Gcr: deriving shared transport key
  Gcr: deriving transport key
  Gcr: starting password prompt for callback 
/org/gnome/keyring/Prompt/p22@:1.259
  Gtk: GtkDialog mapped without a transient parent. This is discouraged.
  Gcr: completed password prompt for callback 
:1.259@/org/gnome/keyring/Prompt/p22
  Gcr: sending the secret exchange: 
[sx-aes-1]\npublic=RnT9opj6kZDvJpr8QyIBH4DE/xn3wid1Di7mdEuIgT/GCBA1mLB3VdsldoT6WMdJeD15xlSIvvmAiLLR59dffthvV+cifN3K1WoJhFdBDSiBLmkI4wfGXEnQTmJn7iZfyGWsIVqL5cSgG3AEMGKgY4ORzBARp8TLqjnfnoJB3YSh/gNFVs5OT5pCATNeaDN1mx9LzOCuCSwVDXIIY6uV8sjhBpBvQQCNNEV960L2pZYvGsBYMKeriKxvZAJfiO04\n
  Gcr: calling the PromptReady method on /org/gnome/keyring/Prompt/p22@:1.259
  Gcr: returned from the PromptReady method on 
/org/gnome/keyring/Prompt/p22@:1.259
  Gcr: received PerformPrompt call from callback 
/org/gnome/keyring/Prompt/p22@:1.259
  Gcr: stopping prompting for operation /org/gnome/keyring/Prompt/p22@:1.259
  Gcr: closing the prompt

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: gnome-session-bin 3.14.0-

[Desktop-packages] [Bug 1453448] Re: Cant run any program after login

2018-03-20 Thread Daniel van Vugt
Thank you for reporting this bug to Ubuntu.
Ubuntu 15.04 (vivid) reached end-of-life on February 4, 2016.

See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases 

We appreciate that this bug may be old and you might not be interested
in discussing it any more. But if you are then please upgrade to the
latest Ubuntu version and re-test. If you then find the bug is still
present in the newer Ubuntu version, please add a comment here telling
us which new version it is in and change the bug status to Confirmed.


** Changed in: gnome-session (Ubuntu)
   Status: New => Invalid

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

Title:
  Cant run any program after login

Status in gnome-session package in Ubuntu:
  Invalid

Bug description:
  After login to my profile I cant run any program. In syslog appears
  that errors:

  May  9 21:10:32 drag0n gnome-session[18284]: classicmenu-indicator: Fatal IO 
error 11 (Zasoby chwilowo niedostępne) on X server :0.
  May  9 21:10:32 drag0n gnome-session[18284]: 
(unity-fallback-mount-helper:18572): Gdk-WARNING **: 
unity-fallback-mount-helper: Fatal IO error 11 (Zasoby chwilowo niedostępne) on 
X server :0.
  May  9 21:10:32 drag0n gnome-session[18284]: 
[18704:18704:0509/191032:ERROR:x11_util.cc(82)] X IO error received (X server 
probably went away)
  May  9 21:10:32 drag0n gnome-session[18284]: 
(polkit-gnome-authentication-agent-1:18586): Gdk-WARNING **: 
polkit-gnome-authentication-agent-1: Fatal IO error 11 (Zasoby chwilowo 
niedostępne) on X server :0.
  May  9 21:10:32 drag0n gnome-session[18284]: owncloud: Fatal IO error 11 
(Zasoby chwilowo niedostępne) on X server :0.
  May  9 21:10:32 drag0n gnome-session[18284]: XIO:  fatal IO error 11 
(Resource temporarily unavailable) on X server ":0"
  May  9 21:10:32 drag0n gnome-session[18284]: after 301814 requests (301814 
known processed) with 0 events remaining.
  May  9 21:10:32 drag0n gnome-session[18284]: g_dbus_connection_real_closed: 
Remote peer vanished with error: Error receiving message: Connection reset by 
peer (g-io-error-quark, 44). Exiting.

  When I'm skip to virtual console (ctrl+alt+f1) and run 
  sudo service lightdm restart
  command and login again everything back to normal.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: gnome-session-bin 3.14.0-2ubuntu5
  ProcVersionSignature: Ubuntu 3.19.0-17.17-lowlatency 3.19.6
  Uname: Linux 3.19.0-17-lowlatency x86_64
  ApportVersion: 2.17.2-0ubuntu1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sat May  9 21:35:15 2015
  InstallationDate: Installed on 2015-02-13 (84 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1)
  SourcePackage: gnome-session
  UpgradeStatus: Upgraded to vivid on 2015-04-25 (14 days ago)

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

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


[Desktop-packages] [Bug 1543769] Re: After resume no scripts from /etc/pm/sleep.d/ executed. Problem with gnome-session-quit

2018-03-20 Thread Daniel van Vugt
Thank you for reporting this bug to Ubuntu.
Ubuntu 15.10 (wily) reached end-of-life on July 28, 2016.

See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases 

We appreciate that this bug may be old and you might not be interested
in discussing it any more. But if you are then please upgrade to the
latest Ubuntu version and re-test. If you then find the bug is still
present in the newer Ubuntu version, please add a comment here telling
us which new version it is in and change the bug status to Confirmed.


** Changed in: gnome-session (Ubuntu)
   Status: New => Invalid

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

Title:
  After resume no scripts from /etc/pm/sleep.d/ executed. Problem with
  gnome-session-quit

Status in gnome-session package in Ubuntu:
  Invalid

Bug description:
  With 15.10 I am struggling with a problem after resume from sleep. I
  tried to start some script when returning from suspend to ram but no
  script is executed. Even the predefined scripts are not started.

  How to reproduce: Create any script in /etc/pm/sleep.d/. Start gnome-
  session-quit program. Choose "suspend". When now resuming from suspend
  the scripts in /etc/pm/sleep.d/ will not be executed.

  It looks like a problem of gnome-session-quit because when suspending
  the PC by starting pm-suspend directly all scripts are executed
  correctly on resume.

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

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


[Desktop-packages] [Bug 1533985] Re: dell inspiron 7548 touch pad not recognized with multi touch pinch or swipe

2018-03-20 Thread Daniel van Vugt
Thank you for reporting this bug to Ubuntu.
Ubuntu 15.10 (wily) reached end-of-life on July 28, 2016.

See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases 

We appreciate that this bug may be old and you might not be interested
in discussing it any more. But if you are then please upgrade to the
latest Ubuntu version and re-test. If you then find the bug is still
present in the newer Ubuntu version, please add a comment here telling
us which new version it is in and change the bug status to Confirmed.


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

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

Title:
  dell inspiron 7548 touch pad not recognized with multi touch pinch or
  swipe

Status in gnome-session package in Ubuntu:
  Incomplete

Bug description:
  two and three finger tap work as expected.

  Please let me know what kind of information is needed to help track
  this down.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: linux-image-4.2.0-23-generic 4.2.0-23.28
  ProcVersionSignature: Ubuntu 4.2.0-23.28-generic 4.2.6
  Uname: Linux 4.2.0-23-generic x86_64
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  jeremy 1565 F pulseaudio
   /dev/snd/controlC1:  jeremy 1565 F pulseaudio
  CurrentDesktop: GNOME
  Date: Wed Jan 13 22:45:41 2016
  HibernationDevice: RESUME=UUID=a25bc1be-6c46-466a-a622-6b575e8a28cf
  InstallationDate: Installed on 2015-03-11 (308 days ago)
  InstallationMedia: Ubuntu-GNOME 14.10 "Utopic Unicorn" - Release amd64 
(20141022.1)
  MachineType: Dell Inc. Inspiron 7548
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB:
   0 inteldrmfb
   1 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-23-generic 
root=UUID=225b7c83-fbf8-4bb1-b1f0-be2bb6cf785f ro i915.enable_ips=0 quiet 
splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.2.0-23-generic N/A
   linux-backports-modules-4.2.0-23-generic  N/A
   linux-firmware1.149.3
  SourcePackage: linux
  UpgradeStatus: Upgraded to wily on 2015-12-10 (34 days ago)
  dmi.bios.date: 07/20/2015
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A05
  dmi.board.name: 0AM6R0
  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.:bvrA05:bd07/20/2015:svnDellInc.:pnInspiron7548:pvrA05:rvnDellInc.:rn0AM6R0:rvrA00:cvnDellInc.:ct8:cvrNotSpecified:
  dmi.product.name: Inspiron 7548
  dmi.product.version: A05
  dmi.sys.vendor: Dell Inc.
  --- 
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  jeremy 7956 F pulseaudio
   /dev/snd/controlC1:  jeremy 7956 F pulseaudio
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 15.10
  HibernationDevice: RESUME=UUID=a25bc1be-6c46-466a-a622-6b575e8a28cf
  InstallationDate: Installed on 2015-03-11 (308 days ago)
  InstallationMedia: Ubuntu-GNOME 14.10 "Utopic Unicorn" - Release amd64 
(20141022.1)
  MachineType: Dell Inc. Inspiron 7548
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB:
   0 inteldrmfb
   1 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-23-generic 
root=UUID=225b7c83-fbf8-4bb1-b1f0-be2bb6cf785f ro i915.enable_ips=0 quiet 
splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.2.0-23.28-generic 4.2.6
  RelatedPackageVersions:
   linux-restricted-modules-4.2.0-23-generic N/A
   linux-backports-modules-4.2.0-23-generic  N/A
   linux-firmware1.149.3
  Tags:  wily
  Uname: Linux 4.2.0-23-generic x86_64
  UpgradeStatus: Upgraded to wily on 2015-12-10 (34 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers
  _MarkForUpload: True
  dmi.bios.date: 07/20/2015
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A05
  dmi.board.name: 0AM6R0
  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.:bvrA05:bd07/20/2015:svnDellInc.:pnInspiron7548:pvrA05:rvnDellInc.:rn0AM6R0:rvrA00:cvnDellInc.:ct8:cvrNotSpecified:
  dmi.product.name: Inspiron 7548
  dmi.product.version: A05
  dmi.sys.vendor: Dell Inc.

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

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

[Desktop-packages] [Bug 1756877] Re: Input latency in 18.04

2018-03-20 Thread John Skottis
dmesg

** Attachment added: "dmesg.txt"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1756877/+attachment/5084789/+files/dmesg.txt

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

Title:
  Input latency in 18.04

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  I am on an Dell xps 9530 laptop and I had recently cleaned installed
  17.10. A few days back I decided to updated to 18.04 to check it out
  and report some bugs. The most annoying bug so far is the insane
  amount of input latency this update has brought with it to a degree
  that it makes it impossible to be productive. The issue is observable
  when using either the mouse or the keyboard. The mouse does not move
  immediately but it needs a second or two to register and start moving
  and even then at some point it freezes for half a second at some
  random point and then moves again. Also if I have two applications
  side by side and I try an move focus from one to the next at around
  the edges of each window the mouse freezes for a second and then
  moves. The keyboard freezes if it hasn't been used for a while and on
  the first keystroke will take a second to register and for a bonus you
  get the first keystorke repeated for around 15-30 times. So if you are
  trying to write "and" will become "aaand" or pressing
  "ctrl + T" in the browser will open not one but 20 tabs!

  I am reporting it here cause I am not sure what is causing all this
  latency (it could be libinput or something else entirely) but please
  try and fix this as soon as possible!!

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.28.0-0ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  Uname: Linux 4.15.0-13-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Mar 19 13:04:05 2018
  DisplayManager: gdm3
  InstallationDate: Installed on 2018-02-14 (32 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to bionic on 2018-03-15 (3 days ago)

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

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


[Desktop-packages] [Bug 1756877] Re: Input latency in 18.04

2018-03-20 Thread John Skottis
I am running Ubuntu from my laptop so sometime I use USB keyboard and
wireless mouse and some times just my laptop's keyboard and touch pad
and I have had this issue with both, with or without any extensions
active

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

Title:
  Input latency in 18.04

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  I am on an Dell xps 9530 laptop and I had recently cleaned installed
  17.10. A few days back I decided to updated to 18.04 to check it out
  and report some bugs. The most annoying bug so far is the insane
  amount of input latency this update has brought with it to a degree
  that it makes it impossible to be productive. The issue is observable
  when using either the mouse or the keyboard. The mouse does not move
  immediately but it needs a second or two to register and start moving
  and even then at some point it freezes for half a second at some
  random point and then moves again. Also if I have two applications
  side by side and I try an move focus from one to the next at around
  the edges of each window the mouse freezes for a second and then
  moves. The keyboard freezes if it hasn't been used for a while and on
  the first keystroke will take a second to register and for a bonus you
  get the first keystorke repeated for around 15-30 times. So if you are
  trying to write "and" will become "aaand" or pressing
  "ctrl + T" in the browser will open not one but 20 tabs!

  I am reporting it here cause I am not sure what is causing all this
  latency (it could be libinput or something else entirely) but please
  try and fix this as soon as possible!!

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.28.0-0ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  Uname: Linux 4.15.0-13-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Mar 19 13:04:05 2018
  DisplayManager: gdm3
  InstallationDate: Installed on 2018-02-14 (32 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to bionic on 2018-03-15 (3 days ago)

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

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


[Desktop-packages] [Bug 1756877] Re: Input latency in 18.04

2018-03-20 Thread John Skottis
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 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 004: ID 8087:07dc Intel Corp. 
Bus 003 Device 003: ID 06cb:0ac3 Synaptics, Inc. 
Bus 003 Device 005: ID 0bda:573c Realtek Semiconductor Corp. 
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

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

Title:
  Input latency in 18.04

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  I am on an Dell xps 9530 laptop and I had recently cleaned installed
  17.10. A few days back I decided to updated to 18.04 to check it out
  and report some bugs. The most annoying bug so far is the insane
  amount of input latency this update has brought with it to a degree
  that it makes it impossible to be productive. The issue is observable
  when using either the mouse or the keyboard. The mouse does not move
  immediately but it needs a second or two to register and start moving
  and even then at some point it freezes for half a second at some
  random point and then moves again. Also if I have two applications
  side by side and I try an move focus from one to the next at around
  the edges of each window the mouse freezes for a second and then
  moves. The keyboard freezes if it hasn't been used for a while and on
  the first keystroke will take a second to register and for a bonus you
  get the first keystorke repeated for around 15-30 times. So if you are
  trying to write "and" will become "aaand" or pressing
  "ctrl + T" in the browser will open not one but 20 tabs!

  I am reporting it here cause I am not sure what is causing all this
  latency (it could be libinput or something else entirely) but please
  try and fix this as soon as possible!!

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.28.0-0ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  Uname: Linux 4.15.0-13-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Mar 19 13:04:05 2018
  DisplayManager: gdm3
  InstallationDate: Installed on 2018-02-14 (32 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to bionic on 2018-03-15 (3 days ago)

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

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


[Desktop-packages] [Bug 1326038] Re: No logout from remote flashback session in trusty

2018-03-20 Thread Daniel van Vugt
Thank you for reporting this bug to Ubuntu.
Ubuntu 13.10 (saucy) reached end-of-life on July 17, 2014.

See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases 

We appreciate that this bug may be old and you might not be interested
in discussing it any more. But if you are then please upgrade to the
latest Ubuntu version and re-test. If you then find the bug is still
present in the newer Ubuntu version, please add a comment here telling
us which new version it is in and change the bug status to Confirmed.


** Changed in: gnome-session (Ubuntu)
   Status: Confirmed => Invalid

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

Title:
  No logout from remote flashback session in trusty

Status in gnome-session package in Ubuntu:
  Invalid

Bug description:
  Since I upgraded our LTSP server to trusty, users cannot log out any
  more from the gnome session. The logout entry from the system menu and
  the logout button added to gnome-panel simply do nothing.

  Running "gnome-session-quit" from the terminal, I get the following:
  > ** (gnome-session-quit:2390): WARNING **: Failed to call logout: Logout 
interface is only available during the Running phase

  The only way to end the session is "killall -u $USER".

  Note that the X session is running remote (LTSP thin client). Same
  problem when running via XDMCP.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: gnome-session-flashback 1:3.6.2-0ubuntu15
  ProcVersionSignature: Ubuntu 3.11.0-20.35-generic 3.11.10.6
  Uname: Linux 3.11.0-20-generic x86_64
  ApportVersion: 2.12.5-0ubuntu2.2
  Architecture: amd64
  Date: Tue Jun  3 18:13:39 2014
  GsettingsChanges:
   
  InstallationDate: Installed on 2014-03-15 (80 days ago)
  InstallationMedia: Edubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  MarkForUpload: True
  PackageArchitecture: all
  SourcePackage: gnome-panel
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1476137] Re: pa_context_connect() failed: Connection refused

2018-03-20 Thread Daniel van Vugt
Thank you for reporting this bug to Ubuntu.
Ubuntu 15.04 (vivid) reached end-of-life on February 4, 2016.

See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases 

We appreciate that this bug may be old and you might not be interested
in discussing it any more. But if you are then please upgrade to the
latest Ubuntu version and re-test. If you then find the bug is still
present in the newer Ubuntu version, please add a comment here telling
us which new version it is in and change the bug status to Confirmed.


** Changed in: gnome-session (Ubuntu)
   Status: New => Invalid

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

Title:
  pa_context_connect() failed: Connection refused

Status in gnome-session package in Ubuntu:
  Invalid

Bug description:
  This is logged when I attempt to start chrome-remote-desktop.

  journalctl -r log entries:

  Jul 20 00:40:37 theark gnome-session[11215]: ** (nautilus:11320): WARNING **: 
Can not determine workarea, guessing at layout
  Jul 20 00:40:37 theark gnome-session[11215]: ** (nautilus:11320): WARNING **: 
Can not get _NET_WORKAREA
  Jul 20 00:40:37 theark gnome-session[11215]: ** (nautilus:11320): WARNING **: 
Can not calculate _NET_NUMBER_OF_DESKTOPS
  Jul 20 00:40:37 theark gnome-session[11215]: ** (nautilus:11320): WARNING **: 
Can not calculate _NET_NUMBER_OF_DESKTOPS
  Jul 20 00:40:36 theark org.gtk.Private.AfcVolumeMonitor[11219]: Volume 
monitor alive
  Jul 20 00:40:36 theark pulseaudio[11370]: [pulseaudio] sink.c: Default and 
alternate sample rates are the same.
  Jul 20 00:40:36 theark gnome-session[11215]: (process:11335): 
indicator-sound-WARNING **: volume-control-pulse.vala:686: unable to get pulse 
unix socket: GDBus.Error:org.freedesktop.DBus.Error.Servi
  Jul 20 00:40:36 theark gnome-session[11215]: Entering running state
  Jul 20 00:40:36 theark gnome-session[11215]: initctl: UPSTART_SESSION isn't 
set in the environment. Unable to locate the Upstart instance.
  Jul 20 00:40:36 theark gnome-session[11215]: ** (process:11314): CRITICAL **: 
bluez.vala:104: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name 
org.bluez was not provided by any .servi
  Jul 20 00:40:36 theark gnome-session[11215]: 
(polkit-gnome-authentication-agent-1:11312): polkit-gnome-1-WARNING **: Unable 
to determine the session we are in: No session for pid 11312
  Jul 20 00:40:36 theark gnome-session[11215]: ** (process:11314): WARNING **: 
killswitch.vala:103: Can't open /dev/rfkill for use as a killswitch backend: 
Permission denied
  Jul 20 00:40:36 theark gnome-session[11215]: gnome-session[11215]: WARNING: 
App 'pulseaudio.desktop' exited with code 1
  Jul 20 00:40:36 theark gnome-session[11215]: WARNING: App 
'pulseaudio.desktop' exited with code 1
  Jul 20 00:40:36 theark gnome-session[11215]: pa_context_connect() failed: 
Connection refused
  Jul 20 00:40:36 theark gnome-session[11215]: Connection failure: Connection 
refused
  Jul 20 00:40:35 theark gnome-session[11215]: gnome-session[11215]: WARNING: 
Could not get session id for session. Check that logind is properly installed 
and pam_systemd is getting used at login.
  Jul 20 00:40:35 theark gnome-session[11215]: WARNING: Could not get session 
id for session. Check that logind is properly installed and pam_systemd is 
getting used at login.
  Jul 20 00:40:35 theark gnome-session[11215]: gnome-session-is-accelerated: 
llvmpipe detected.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: gnome-session (not installed)
  Uname: Linux 4.1.2-040102-generic x86_64
  ApportVersion: 2.17.2-0ubuntu1.1
  Architecture: amd64
  Date: Mon Jul 20 00:55:38 2015
  InstallationDate: Installed on 2015-05-10 (71 days ago)
  InstallationMedia: Ubuntu-Server 15.04 "Vivid Vervet" - Release amd64 
(20150422)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-session
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1212169] Re: Shutdown/reboot/logout triggers standby on lenovo x230 with lid closed on docking station

2018-03-20 Thread Daniel van Vugt
Thank you for reporting this bug to Ubuntu.
Ubuntu 13.10 (saucy) reached end-of-life on July 17, 2014.

See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases 

We appreciate that this bug may be old and you might not be interested
in discussing it any more. But if you are then please upgrade to the
latest Ubuntu version and re-test. If you then find the bug is still
present in the newer Ubuntu version, please add a comment here telling
us which new version it is in and change the bug status to Confirmed.


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

** Changed in: gnome-session (Ubuntu)
   Status: New => Invalid

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

Title:
  Shutdown/reboot/logout triggers standby on lenovo x230 with lid closed
  on docking station

Status in Unity:
  Invalid
Status in gnome-session package in Ubuntu:
  Invalid
Status in linux package in Ubuntu:
  Invalid
Status in unity package in Ubuntu:
  Invalid

Bug description:
  I generally use my x230 attached to a docking station + external
  monitor etc.

  Using the restart or shutdown options from with Ubuntu results in the
  laptop going into standby mode if the lid of the laptop is closed.

  Opening the lid wakes up OK at which point the requested action does
  complete.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: linux-image-3.11.0-1-generic 3.11.0-1.4
  ProcVersionSignature: Ubuntu 3.11.0-1.4-generic 3.11.0-rc4
  Uname: Linux 3.11.0-1-generic x86_64
  ApportVersion: 2.12-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  jamespage   2944 F pulseaudio
   /dev/snd/controlC0:  jamespage   2944 F pulseaudio
  Date: Wed Aug 14 10:26:17 2013
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=9cabca8b-d2e3-4f65-a113-3c165c5ecbc6
  InstallationDate: Installed on 2013-04-23 (112 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130423)
  MachineType: LENOVO 2324CTO
  MarkForUpload: True
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-1-generic.efi.signed 
root=UUID=88b94abf-33eb-4e05-888d-9dacbe025054 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-3.11.0-1-generic N/A
   linux-backports-modules-3.11.0-1-generic  N/A
   linux-firmware1.113
  SourcePackage: linux
  UpgradeStatus: Upgraded to saucy on 2013-06-15 (59 days ago)
  dmi.bios.date: 01/14/2013
  dmi.bios.vendor: LENOVO
  dmi.bios.version: G2ET91WW (2.51 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 2324CTO
  dmi.board.vendor: LENOVO
  dmi.board.version: Win8 Pro DPK TPG
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrG2ET91WW(2.51):bd01/14/2013:svnLENOVO:pn2324CTO:pvrThinkPadX230:rvnLENOVO:rn2324CTO:rvrWin8ProDPKTPG:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 2324CTO
  dmi.product.version: ThinkPad X230
  dmi.sys.vendor: LENOVO

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

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


[Desktop-packages] [Bug 1269838] Re: gnome-session.log takes 8 GB in a few hours

2018-03-20 Thread Daniel van Vugt
Bryce,

Please open a fresh bug detailing exactly which messages are filling
your log.

This bug is too old to ever be resolved adequately.

** Changed in: gnome-session (Ubuntu)
   Status: New => Invalid

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

Title:
  gnome-session.log takes 8 GB in a few hours

Status in gnome-session package in Ubuntu:
  Invalid

Bug description:
  Hello,

  On a fresh install of saucy 64 bits, ~/.cache/upstart/gnome-session.log grows 
incredibly fast. 8 GB in a few hours.
  Worked it around with a rm as cron task.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: upstart 1.10-0ubuntu7
  ProcVersionSignature: Ubuntu 3.11.0-15.23-generic 3.11.10
  Uname: Linux 3.11.0-15-generic x86_64
  ApportVersion: 2.12.5-0ubuntu2.2
  Architecture: amd64
  Date: Thu Jan 16 16:02:23 2014
  InstallationDate: Installed on 2014-01-10 (5 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  MarkForUpload: True
  SourcePackage: upstart
  UpgradeStatus: No upgrade log present (probably fresh install)
  UpstartBugCategory: Session
  UpstartRunningSessionCount: 1
  UpstartRunningSessionVersion: init (upstart 1.10)
  UpstartRunningSystemVersion: init (upstart 1.10)
  upstart.upstart-file-bridge.log:
   Job got added /com/ubuntu/Upstart/jobs/unicast_2dlocal_2davahi
   Job got added /com/ubuntu/Upstart/jobs/update_2dnotifier_2dcrash
   Job got added /com/ubuntu/Upstart/jobs/update_2dnotifier_2drelease

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

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


[Desktop-packages] [Bug 1414538] Re: package gnome-session-bin 3.9.90-0ubuntu16 failed to install/upgrade: subprocess installed post-installation script returned error exit status 2

2018-03-20 Thread Daniel van Vugt
Thank you for reporting this bug to Ubuntu.
Ubuntu 14.10 (utopic) reached end-of-life on July 23, 2015.

See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases 

We appreciate that this bug may be old and you might not be interested
in discussing it any more. But if you are then please upgrade to the
latest Ubuntu version and re-test. If you then find the bug is still
present in the newer Ubuntu version, please add a comment here telling
us which new version it is in and change the bug status to Confirmed.


** Changed in: gnome-session (Ubuntu)
   Status: New => Invalid

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

Title:
  package gnome-session-bin 3.9.90-0ubuntu16 failed to install/upgrade:
  subprocess installed post-installation script returned error exit
  status 2

Status in gnome-session package in Ubuntu:
  Invalid

Bug description:
  Problem with dpkg ftp package is causing errors while installing any
  updates

  ProblemType: Package
  DistroRelease: Ubuntu 14.10
  Package: gnome-session-bin 3.9.90-0ubuntu16
  ProcVersionSignature: Ubuntu 3.16.0-29.39-generic 3.16.7-ckt2
  Uname: Linux 3.16.0-29-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.14.7-0ubuntu8
  Architecture: amd64
  Date: Sun Jan 25 11:46:18 2015
  DuplicateSignature: package:gnome-session-bin:3.9.90-0ubuntu16:subprocess 
installed post-installation script returned error exit status 2
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 2
  InstallationDate: Installed on 2013-10-27 (455 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  SourcePackage: gnome-session
  Title: package gnome-session-bin 3.9.90-0ubuntu16 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 2
  UpgradeStatus: Upgraded to utopic on 2014-11-16 (70 days ago)

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

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


[Desktop-packages] [Bug 1455809] Re: [vivid] Ubuntu session crashes on LDAP login via SSSD

2018-03-20 Thread Daniel van Vugt
Thank you for reporting this bug to Ubuntu.
Ubuntu 15.04 (vivid) reached end-of-life on February 4, 2016.

See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases 

We appreciate that this bug may be old and you might not be interested
in discussing it any more. But if you are then please upgrade to the
latest Ubuntu version and re-test. If you then find the bug is still
present in the newer Ubuntu version, please add a comment here telling
us which new version it is in and change the bug status to Confirmed.


** Changed in: gnome-session (Ubuntu)
   Status: New => Invalid

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

Title:
  [vivid] Ubuntu session crashes on LDAP login via SSSD

Status in gnome-session package in Ubuntu:
  Invalid

Bug description:
  Following situation:

  - Ubuntu is configured use SSSD to permit login of LDAP users
  - Automatic creation of home directories is switched on and confirmed to work
  - LDAP users (as well as local users) can login to
* local console
* SSH console
* LXDE (via LightDM)
* Openbox (via LightDM)
  - However, LDAP users can't use the standard Ubuntu session (Unity) because 
it crashes right after LightDM permits the login (returning to the LightDM 
greeter)
  - Local users can login to the standard Ubuntu session without any problems
  - For LDAP users, after each failed login attempt, a file like 
"upstart-udev-bridge.21334.pid" containing a five digit number different from 
that in the file name is left back in the home directory

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

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


[Desktop-packages] [Bug 1386872] Re: Incorrect termination Firefox when shutdown Ubuntu

2018-03-20 Thread Daniel van Vugt
Thank you for reporting this bug to Ubuntu.
Ubuntu 14.10 (utopic) reached end-of-life on July 23, 2015.

See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases 

We appreciate that this bug may be old and you might not be interested
in discussing it any more. But if you are then please upgrade to the
latest Ubuntu version and re-test. If you then find the bug is still
present in the newer Ubuntu version, please add a comment here telling
us which new version it is in and change the bug status to Confirmed.


** Changed in: gnome-session (Ubuntu)
   Status: Confirmed => Invalid

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

Title:
  Incorrect termination Firefox when shutdown Ubuntu

Status in Unity:
  Won't Fix
Status in gnome-session package in Ubuntu:
  Invalid
Status in unity package in Ubuntu:
  Won't Fix

Bug description:
  1. In Firefox go to Preference -> General tab, choose Show my windows and 
tabs from last time in When Firefox starts field.
  2. Shutdown Ubuntu
  3. Start Ubuntu
  4. Open Firefox

  Actual result: Firefox opens with message "Firefox was not closed
  properly"

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: unity 7.3.1+14.10.20141016-0ubuntu1
  ProcVersionSignature: Ubuntu 3.16.0-23.31-generic 3.16.4
  Uname: Linux 3.16.0-23-generic x86_64
  ApportVersion: 2.14.7-0ubuntu8
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CurrentDesktop: Unity
  Date: Tue Oct 28 22:20:52 2014
  InstallationDate: Installed on 2014-10-25 (3 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1)
  SourcePackage: unity
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1193291] Re: gnome-session crashed with SIGSEGV

2018-03-20 Thread Daniel van Vugt
Thank you for reporting this bug to Ubuntu.
Ubuntu 13.10 (saucy) reached end-of-life on July 17, 2014.

See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases 

We appreciate that this bug may be old and you might not be interested
in discussing it any more. But if you are then please upgrade to the
latest Ubuntu version and re-test. If you then find the bug is still
present in the newer Ubuntu version, please add a comment here telling
us which new version it is in and change the bug status to Confirmed.


** Changed in: gnome-session (Ubuntu)
   Status: New => Invalid

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

Title:
  gnome-session crashed with SIGSEGV

Status in gnome-session package in Ubuntu:
  Invalid

Bug description:
  Patched g-s-d to force use of the background plugin & enabled it.

  Nautilus 3.8.

  ProblemType: Crash
  DistroRelease: Ubuntu 13.10
  Package: gnome-session-bin 3.8.2.1-1ubuntu2
  ProcVersionSignature: Ubuntu 3.9.0-6.13-generic 3.9.6
  Uname: Linux 3.9.0-6-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.10.2-0ubuntu1
  Architecture: amd64
  Date: Fri Jun 21 11:11:16 2013
  ExecutablePath: /usr/bin/gnome-session
  InstallationDate: Installed on 2012-10-07 (256 days ago)
  InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Beta amd64 (20121007)
  MarkForUpload: True
  ProcCmdline: gnome-session --session=ubuntu
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, user)
   XDG_RUNTIME_DIR=
   LANG=en_GB.UTF-8
   SHELL=/bin/zsh
  SegvAnalysis:
   Segfault happened at: 0x41d76e:  mov0x8(%rax),%rcx
   PC (0x0041d76e) ok
   source "0x8(%rax)" (0x0008) not located in a known VMA region (needed 
readable region)!
   destination "%rcx" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: gnome-session
  Stacktrace:
   #0  0x0041d76e in ?? ()
   No symbol table info available.
   Cannot access memory at address 0x7fff02857ab8
  StacktraceTop: ?? ()
  Title: gnome-session crashed with SIGSEGV
  UpgradeStatus: Upgraded to saucy on 2013-05-07 (45 days ago)
  UserGroups: adm autopilot cdrom dip kvm libvirtd lpadmin plugdev sambashare 
sudo vboxusers

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

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


[Desktop-packages] [Bug 1084045] Re: raring startup applications don't work after latest update

2018-03-20 Thread Daniel van Vugt
Thank you for reporting this bug to Ubuntu.
Ubuntu 13.04 (raring) reached end-of-life on January 27, 2014.

See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases 

We appreciate that this bug may be old and you might not be interested
in discussing it any more. But if you are then please upgrade to the
latest Ubuntu version and re-test. If you then find the bug is still
present in the newer Ubuntu version, please add a comment here telling
us which new version it is in and change the bug status to Confirmed.


** Changed in: gnome-session (Ubuntu)
   Status: New => Won't Fix

** Changed in: gnome-session (Ubuntu)
   Status: Won't Fix => Invalid

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

Title:
  raring startup applications don't work after latest update

Status in gnome-session package in Ubuntu:
  Invalid

Bug description:
  Before updates this week startup application commands were working now they 
are never issued.  I do them manually after boot they work fine.  Example:
   sudo iwconfig wlan0 essid LAUREL
  xrandr --newmode "1366x768_60.00"   85.25  1366 1440 1576 1784  768 771 781 
798 -hsync +vsync
  which used to  work.
  One of them uses sudo the other doesn't.  Last week they were working fine 
then apt-get update, apt-get dist-upgrade they are never issued by unity 
startup applications.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: unity 6.12.0-0ubuntu4
  ProcVersionSignature: Ubuntu 3.7.0-3.9-generic 3.7.0-rc6
  Uname: Linux 3.7.0-3-generic i686
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.6.2-0ubuntu5
  Architecture: i386
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  Date: Wed Nov 28 07:00:00 2012
  DistUpgraded: Fresh install
  DistroCodename: raring
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation Atom Processor D4xx/D5xx/N4xx/N5xx Integrated Graphics 
Controller [8086:a011] (prog-if 00 [VGA controller])
 Subsystem: Acer Incorporated [ALI] Device [1025:0349]
 Subsystem: Acer Incorporated [ALI] Device [1025:0349]
  InstallationDate: Installed on 2012-11-27 (1 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Alpha i386 (20121127)
  MachineType: Acer AOD255E
  MarkForUpload: True
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.7.0-3-generic 
root=UUID=ce422c9d-4d8e-4311-8b95-0b4733e8142f ro quiet splash vt.handoff=7
  SourcePackage: unity
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/16/2010
  dmi.bios.vendor: Acer
  dmi.bios.version: V3.12(DDR3)
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: JE02_PT
  dmi.board.vendor: Acer
  dmi.board.version: V3.12(DDR3)
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: V3.12(DDR3)
  dmi.modalias: 
dmi:bvnAcer:bvrV3.12(DDR3):bd12/16/2010:svnAcer:pnAOD255E:pvrV3.12(DDR3):rvnAcer:rnJE02_PT:rvrV3.12(DDR3):cvnAcer:ct10:cvrV3.12(DDR3):
  dmi.product.name: AOD255E
  dmi.product.version: V3.12(DDR3)
  dmi.sys.vendor: Acer
  version.compiz: compiz 1:0.9.8.4+bzr3412-0ubuntu1
  version.libdrm2: libdrm2 2.4.40-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 9.0.1-0ubuntu1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 9.0.1-0ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.13.0-0ubuntu8
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.0.0-0ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.20.13-0ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.4-0ubuntu1
  xserver.bootTime: Wed Nov 28 06:56:39 2012
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.13.0-0ubuntu8
  xserver.video_driver: intel

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

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


[Desktop-packages] [Bug 907561] Re: gnome-session crashed with signal 5 in g_object_newv()

2018-03-20 Thread Daniel van Vugt
Thank you for reporting this bug to Ubuntu.
Ubuntu 13.04 (raring) reached end-of-life on January 27, 2014.

See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases 

We appreciate that this bug may be old and you might not be interested
in discussing it any more. But if you are then please upgrade to the
latest Ubuntu version and re-test. If you then find the bug is still
present in the newer Ubuntu version, please add a comment here telling
us which new version it is in and change the bug status to Confirmed.


** Changed in: gnome-session (Ubuntu)
   Status: Confirmed => Invalid

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

Title:
  gnome-session crashed with signal 5 in g_object_newv()

Status in gnome-session package in Ubuntu:
  Invalid

Bug description:
  afta bt

  ProblemType: Crash
  DistroRelease: Ubuntu 12.04
  Package: gnome-session-bin 3.2.1-0ubuntu4
  ProcVersionSignature: Ubuntu 3.2.0-6.12-generic 3.2.0-rc6
  Uname: Linux 3.2.0-6-generic x86_64
  ApportVersion: 1.90-0ubuntu1
  Architecture: amd64
  Date: Wed Dec 21 23:51:44 2011
  ExecutablePath: /usr/bin/gnome-session
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Alpha amd64 
(2029.1)
  ProcCmdline: gnome-session --session=gnome-classic
  ProcEnviron:
   PATH=(custom, no user)
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  Signal: 5
  SourcePackage: gnome-session
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   g_object_newv () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   g_object_new_valist () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   g_object_new () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
  Title: gnome-session crashed with signal 5 in g_object_newv()
  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-session/+bug/907561/+subscriptions

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


[Desktop-packages] [Bug 1194546] Re: gnome-session-properties crashed with signal 5 in g_cclosure_marshal_VOID__BOXEDv()

2018-03-20 Thread Daniel van Vugt
Thank you for reporting this bug to Ubuntu.
Ubuntu 13.10 (saucy) reached end-of-life on July 17, 2014.

See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases 

We appreciate that this bug may be old and you might not be interested
in discussing it any more. But if you are then please upgrade to the
latest Ubuntu version and re-test. If you then find the bug is still
present in the newer Ubuntu version, please add a comment here telling
us which new version it is in and change the bug status to Confirmed.


** Changed in: gnome-session (Ubuntu)
   Status: Confirmed => Invalid

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

Title:
  gnome-session-properties crashed with signal 5 in
  g_cclosure_marshal_VOID__BOXEDv()

Status in gnome-session package in Ubuntu:
  Invalid

Bug description:
  Clicked on "Startup Applications" from Dash. Crashes immediately.

  Ubuntu 13.10 32-bit desktop, all updates current

  ProblemType: Crash
  DistroRelease: Ubuntu 13.10
  Package: gnome-session-bin 3.8.2.1-1ubuntu3
  ProcVersionSignature: Ubuntu 3.9.0-7.15-generic 3.9.7
  Uname: Linux 3.9.0-7-generic i686
  ApportVersion: 2.10.2-0ubuntu2
  Architecture: i386
  CrashCounter: 1
  Date: Tue Jun 25 10:18:57 2013
  EcryptfsInUse: Yes
  ExecutablePath: /usr/bin/gnome-session-properties
  InstallationDate: Installed on 2013-06-25 (0 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha i386 (20130618)
  MarkForUpload: True
  ProcCmdline: gnome-session-properties
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  Signal: 5
  SourcePackage: gnome-session
  StacktraceTop:
   ?? () from /usr/lib/i386-linux-gnu/libgtk-3.so.0
   g_cclosure_marshal_VOID__BOXEDv () from 
/usr/lib/i386-linux-gnu/libgobject-2.0.so.0
   ?? () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0
   ?? () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0
   g_signal_emit_valist () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0
  Title: gnome-session-properties crashed with signal 5 in 
g_cclosure_marshal_VOID__BOXEDv()
  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-session/+bug/1194546/+subscriptions

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


[Desktop-packages] [Bug 1757099] [NEW] CSS "pointer-events" wrongly highlighted/colored

2018-03-20 Thread dinamic
Public bug reported:

ubuntu 16.04, gedit 3.18.3

open new document, paste this CSS
.green-bar{
pointer-events: none; 
background: #8abf00; 
z-index:1; 
height: 8px; 
position: absolute; 
top: 9px; 
border-radius: 20px;"
}

pointer-events: should be with bold red but it's not, it's like gedit
doesn't recognize that specific CSS keyword. the rest are ok background,
z-index etc.

https://developer.mozilla.org/en-US/docs/Web/CSS/pointer-events

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

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

Title:
  CSS "pointer-events" wrongly highlighted/colored

Status in gedit package in Ubuntu:
  New

Bug description:
  ubuntu 16.04, gedit 3.18.3

  open new document, paste this CSS
  .green-bar{
pointer-events: none; 
background: #8abf00; 
z-index:1; 
height: 8px; 
position: absolute; 
top: 9px; 
border-radius: 20px;"
  }

  pointer-events: should be with bold red but it's not, it's like gedit
  doesn't recognize that specific CSS keyword. the rest are ok
  background, z-index etc.

  https://developer.mozilla.org/en-US/docs/Web/CSS/pointer-events

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

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


[Desktop-packages] [Bug 1756877] Re: Input latency in 18.04

2018-03-20 Thread John Skottis
I should note however that the problem is less noticeable today, maybe
due to some update.

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

Title:
  Input latency in 18.04

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  I am on an Dell xps 9530 laptop and I had recently cleaned installed
  17.10. A few days back I decided to updated to 18.04 to check it out
  and report some bugs. The most annoying bug so far is the insane
  amount of input latency this update has brought with it to a degree
  that it makes it impossible to be productive. The issue is observable
  when using either the mouse or the keyboard. The mouse does not move
  immediately but it needs a second or two to register and start moving
  and even then at some point it freezes for half a second at some
  random point and then moves again. Also if I have two applications
  side by side and I try an move focus from one to the next at around
  the edges of each window the mouse freezes for a second and then
  moves. The keyboard freezes if it hasn't been used for a while and on
  the first keystroke will take a second to register and for a bonus you
  get the first keystorke repeated for around 15-30 times. So if you are
  trying to write "and" will become "aaand" or pressing
  "ctrl + T" in the browser will open not one but 20 tabs!

  I am reporting it here cause I am not sure what is causing all this
  latency (it could be libinput or something else entirely) but please
  try and fix this as soon as possible!!

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.28.0-0ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  Uname: Linux 4.15.0-13-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Mar 19 13:04:05 2018
  DisplayManager: gdm3
  InstallationDate: Installed on 2018-02-14 (32 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to bionic on 2018-03-15 (3 days ago)

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

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


[Desktop-packages] [Bug 1084188] Re: should unmount the devices owned by an user who logs out

2018-03-20 Thread Daniel van Vugt
Thank you for reporting this bug to Ubuntu.
Ubuntu 12.10 (quantal) reached end-of-life on May 16, 2014.

See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases 

We appreciate that this bug may be old and you might not be interested
in discussing it any more. But if you are then please upgrade to the
latest Ubuntu version and re-test. If you then find the bug is still
present in the newer Ubuntu version, please add a comment here telling
us which new version it is in and change the bug status to Confirmed.


** Changed in: gnome-session (Ubuntu)
   Status: Confirmed => Invalid

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

Title:
  should unmount the devices owned by an user who logs out

Status in gnome-session package in Ubuntu:
  Invalid
Status in udisks2 package in Ubuntu:
  Invalid

Bug description:
  Steps to reproduce:
  1. Start computer with USB drive connected.
  2. Log in to guest session.
  3. Log out.
  4. Log in to default user.
  5. Start Nautilus.
  6. Click on a drive icon on the left.

  Result:
  Error:
  Could not display "/media/guest-dmJR8h/hit_tmp".
  The location is not a folder.

  Expected result:
  Nautilus opens the top directory of the selected drive/partition.

  An additional note:
  Clicking on drive icons on Unity Launcher does nothing.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.10
  Package: nautilus 1:3.5.90.really.3.4.2-0ubuntu4
  ProcVersionSignature: Ubuntu 3.5.0-18.29-generic 3.5.7
  Uname: Linux 3.5.0-18-generic x86_64
  ApportVersion: 2.6.1-0ubuntu6
  Architecture: amd64
  Date: Wed Nov 28 19:09:25 2012
  GsettingsChanges:
   b'org.gnome.nautilus.window-state' b'geometry' b"'800x550+123+159'"
   b'org.gnome.nautilus.window-state' b'maximized' b'true'
   b'org.gnome.nautilus.window-state' b'sidebar-width' b'174'
  InstallationDate: Installed on 2012-11-12 (15 days ago)
  InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5)
  MarkForUpload: True
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.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/gnome-session/+bug/1084188/+subscriptions

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


[Desktop-packages] [Bug 1069810] Re: "Startup Application Preferences" should have an icon in Control Center

2018-03-20 Thread Daniel van Vugt
Thank you for reporting this bug to Ubuntu.
Ubuntu 15.10 (wily) reached end-of-life on July 28, 2016.
Ubuntu 12.10 (quantal) reached end-of-life on May 16, 2014.

See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases 

We appreciate that this bug may be old and you might not be interested
in discussing it any more. But if you are then please upgrade to the
latest Ubuntu version and re-test. If you then find the bug is still
present in the newer Ubuntu version, please add a comment here telling
us which new version it is in and change the bug status to Confirmed.


** Changed in: gnome-session (Ubuntu)
   Status: Triaged => Invalid

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

Title:
  "Startup Application Preferences" should have an icon in Control
  Center

Status in gnome-session package in Ubuntu:
  Invalid

Bug description:
  In 12.10 "Startup Application Preferences" has been removed from the
  session indicator. It should have an icon in Control Center so users
  can find it.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.10
  Package: gnome-session-bin 3.6.0-0ubuntu1
  ProcVersionSignature: Ubuntu 3.5.0-17.28-generic 3.5.5
  Uname: Linux 3.5.0-17-generic i686
  NonfreeKernelModules: nvidia
  ApportVersion: 2.6.1-0ubuntu3
  Architecture: i386
  Date: Mon Oct 22 15:28:08 2012
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release i386 
(20120423)
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/zsh
  SourcePackage: gnome-session
  UpgradeStatus: Upgraded to quantal on 2012-10-19 (3 days ago)

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

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


[Desktop-packages] [Bug 1210938] Re: No window decoration on GNOME Fallback

2018-03-20 Thread Daniel van Vugt
Thank you for reporting this bug to Ubuntu.
Ubuntu 13.04 (raring) reached end-of-life on January 27, 2014.

See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases 

We appreciate that this bug may be old and you might not be interested
in discussing it any more. But if you are then please upgrade to the
latest Ubuntu version and re-test. If you then find the bug is still
present in the newer Ubuntu version, please add a comment here telling
us which new version it is in and change the bug status to Confirmed.


** Changed in: gnome-session (Ubuntu)
   Status: Confirmed => Invalid

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

Title:
  No window decoration on GNOME Fallback

Status in gnome-session package in Ubuntu:
  Invalid

Bug description:
  all programs have no window decoration in Ubuntu 13.04 in a VirtualBox under 
GNOME Fallback (compiz with 3D-effects, cube etc.).
  ~$ /usr/bin/gtk-window-decorator --replace
  has no effect.
  A error message is in Attachment below.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: linux-image-3.8.0-27-generic 3.8.0-27.40
  ProcVersionSignature: Ubuntu 3.8.0-27.40-generic 3.8.13.4
  Uname: Linux 3.8.0-27-generic i686
  ApportVersion: 2.9.2-0ubuntu8.3
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  opa1853 F pulseaudio
  CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 
not found.
  Date: Sun Aug 11 09:47:06 2013
  HibernationDevice: RESUME=UUID=bb20c2b4-5792-47ab-9aa3-31f9d10c0a5b
  InstallationDate: Installed on 2012-01-17 (571 days ago)
  InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release i386 (20111012)
  IwConfig:
   lono wireless extensions.
   
   eth4  no wireless extensions.
  Lsusb:
   Bus 002 Device 002: ID 80ee:0021 VirtualBox USB Tablet
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: innotek GmbH VirtualBox
  MarkForUpload: True
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-27-generic 
root=UUID=a74fe42d-7eb8-4664-a50f-6478696b72fc ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-3.8.0-27-generic N/A
   linux-backports-modules-3.8.0-27-generic  N/A
   linux-firmware1.106
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: Upgraded to raring on 2013-04-27 (105 days ago)
  WifiSyslog:
   
  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.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/gnome-session/+bug/1210938/+subscriptions

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


[Desktop-packages] [Bug 1190584] Re: Gnome screensaver don't disappear after login - screen hanged

2018-03-20 Thread Daniel van Vugt
Thank you for reporting this bug to Ubuntu.
Ubuntu 13.04 (raring) reached end-of-life on January 27, 2014.

See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases 

We appreciate that this bug may be old and you might not be interested
in discussing it any more. But if you are then please upgrade to the
latest Ubuntu version and re-test. If you then find the bug is still
present in the newer Ubuntu version, please add a comment here telling
us which new version it is in and change the bug status to Confirmed.


** Changed in: gnome-session (Ubuntu)
   Status: New => Invalid

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

Title:
  Gnome screensaver don't disappear after login - screen hanged

Status in gnome-session package in Ubuntu:
  Invalid

Bug description:
  If my computer is locked and I would like to open it and return back to 
desktop, screensaver will hang.
  Steps to reproduce:
  1) Lock desktop using standard Gnome3 feature
  2) Hit Escape key to raise curtain, place password and hit Enter
  3) Now  password dialog disappear, but gray dusty background stays. It seems 
it is only a problem of visible screensaver background, because desktop is 
still responsive. Mouse cursor is moving, Alt-Tab displays Application 
switcher, Ctrl-Alt-Delete shows Logout dialog etc. I can even close 
applications using Alt-F4 shortcut (they disappear from Application switcher), 
but still I can't see them. They are hiddend somewhere under Gnome screensaver.

  This issue occure time by time. Maybe something must be launched, but
  it is very annoying, because I must close my session without
  possibility to save my work.

  Description:  Ubuntu 13.04
  Release:  13.04

  gnome-session:
Installed: 3.6.2-0ubuntu5
Candidate: 3.6.2-0ubuntu5
Version table:
   *** 3.6.2-0ubuntu5 0
  500 http://cz.archive.ubuntu.com/ubuntu/ raring/main amd64 Packages
  100 /var/lib/dpkg/status

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: gnome-session-bin 3.6.2-0ubuntu5
  ProcVersionSignature: Ubuntu 3.8.0-23.34-generic 3.8.11
  Uname: Linux 3.8.0-23-generic x86_64
  ApportVersion: 2.9.2-0ubuntu8.1
  Architecture: amd64
  Date: Thu Jun 13 13:57:15 2013
  ExecutablePath: /usr/bin/gnome-session
  InstallationDate: Installed on 2013-05-05 (39 days ago)
  InstallationMedia: Ubuntu-GNOME 13.04 "Raring Ringtail" - Release amd64 
(20130424)
  MarkForUpload: True
  SourcePackage: gnome-session
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1182461] Re: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.#012

2018-03-20 Thread Daniel van Vugt
Thank you for reporting this bug to Ubuntu.
Ubuntu 13.04 (raring) reached end-of-life on January 27, 2014.

See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases 

We appreciate that this bug may be old and you might not be interested
in discussing it any more. But if you are then please upgrade to the
latest Ubuntu version and re-test. If you then find the bug is still
present in the newer Ubuntu version, please add a comment here telling
us which new version it is in and change the bug status to Confirmed.


** Changed in: gnome-session (Ubuntu)
   Status: New => Invalid

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

Title:
  Fatal IO error 11 (Resource temporarily unavailable) on X server
  :0.#012

Status in gnome-session package in Ubuntu:
  Invalid

Bug description:
  This might be related to bug #1053550. However this problem is now
  occuring after a few minutes within a gnome session. I am currently
  using the xorg-edgers ppa and now this error occurs.

  Prior to loading the xorg-edgers ppa, my desktop sessions would freeze
  and would have to resort to restarting lightdm to get a desktop
  session back. The error that occurred prior to me testing with the
  xorg-edgers ppa was:

  May 20 10:31:37 tank kernel: [ 9246.195078] [drm:i915_hangcheck_hung] *ERROR* 
Hangcheck timer elapsed... GPU hung
  May 20 10:31:37 tank kernel: [ 9246.195086] [drm] capturing error event; look 
for more information in /debug/dri/0/i915_error_state

  I have also been seeing a lot of these entries over the last two
  weeks:

  [   21.725218] ACPI Warning: 0x0428-0x042f SystemIO 
conflicts with Region \PMIO 1 (20121018/utaddress-251)
  [   21.725228] ACPI: If an ACPI driver is available for this device, you 
should use it instead of the native driver
  [   21.725233] ACPI Warning: 0x0540-0x054f SystemIO 
conflicts with Region \GPIO 1 (20121018/utaddress-251)
  [   21.725238] ACPI Warning: 0x0540-0x054f SystemIO 
conflicts with Region \_SB_.WMID.GPIO 2 (20121018/utaddress-251)
  [   21.725243] ACPI Warning: 0x0540-0x054f SystemIO 
conflicts with Region \_SB_.PCI0.PEG0.GPIO 3 (20121018/utaddress-251)
  [   21.725247] ACPI Warning: 0x0540-0x054f SystemIO 
conflicts with Region \_SB_.PCI0.PEG0.PEGP.GPIO 4 (20121018/utaddress-251)
  [   21.725251] ACPI Warning: 0x0540-0x054f SystemIO 
conflicts with Region \_SB_.PCI0.LPCB.GPIO 5 (20121018/utaddress-251)
  [   21.725255] ACPI: If an ACPI driver is available for this device, you 
should use it instead of the native driver
  [   21.725257] ACPI Warning: 0x0530-0x053f SystemIO 
conflicts with Region \GPIO 1 (20121018/utaddress-251)
  [   21.725260] ACPI Warning: 0x0530-0x053f SystemIO 
conflicts with Region \_SB_.WMID.GPIO 2 (20121018/utaddress-251)
  [   21.725264] ACPI Warning: 0x0530-0x053f SystemIO 
conflicts with Region \_SB_.PCI0.PEG0.GPIO 3 (20121018/utaddress-251)
  [   21.725268] ACPI Warning: 0x0530-0x053f SystemIO 
conflicts with Region \_SB_.PCI0.PEG0.PEGP.GPIO 4 (20121018/utaddress-251)
  [   21.725272] ACPI Warning: 0x0530-0x053f SystemIO 
conflicts with Region \_SB_.PCI0.LPCB.GPIO 5 (20121018/utaddress-251)
  [   21.725275] ACPI: If an ACPI driver is available for this device, you 
should use it instead of the native driver
  [   21.725277] ACPI Warning: 0x0500-0x052f SystemIO 
conflicts with Region \GPIO 1 (20121018/utaddress-251)
  [   21.725281] ACPI Warning: 0x0500-0x052f SystemIO 
conflicts with Region \_SB_.WMID.GPIO 2 (20121018/utaddress-251)
  [   21.725285] ACPI Warning: 0x0500-0x052f SystemIO 
conflicts with Region \_SB_.PCI0.PEG0.GPIO 3 (20121018/utaddress-251)
  [   21.725289] ACPI Warning: 0x0500-0x052f SystemIO 
conflicts with Region \_SB_.PCI0.PEG0.PEGP.GPIO 4 (20121018/utaddress-251)
  [   21.725293] ACPI Warning: 0x0500-0x052f SystemIO 
conflicts with Region \_SB_.PCI0.LPCB.GPIO 5 (20121018/utaddress-251)
  [   21.725296] ACPI: If an ACPI driver is available for this device, you 
should use it instead of the native driver

  Not sure if it is related, but I'm posting it here just in case.

  I am now going to attempt loading the proprietry drivers to see if
  this resolves my previous problem.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: gnome-session 3.6.2-0ubuntu5
  ProcVersionSignature: Ubuntu 3.8.0-21.32-generic 3.8.8
  Uname: Linux 3.8.0-21-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.9.2-0ubuntu8
  Architecture: amd64
  Date: Tue May 21 14:55:16 2013
  Installation

[Desktop-packages] [Bug 1078747] Re: Missing Feature to Control the Order in which Startup Applications are Launched

2018-03-20 Thread Daniel van Vugt
Thank you for reporting this bug to Ubuntu.
Ubuntu 12.10 (quantal) reached end-of-life on May 16, 2014.

See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases 

We appreciate that this bug may be old and you might not be interested
in discussing it any more. But if you are then please upgrade to the
latest Ubuntu version and re-test. If you then find the bug is still
present in the newer Ubuntu version, please add a comment here telling
us which new version it is in and change the bug status to Confirmed.

** Changed in: gnome-session (Ubuntu)
   Status: New => Invalid

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

Title:
  Missing Feature to Control the Order in which Startup Applications are
  Launched

Status in gnome-session package in Ubuntu:
  Invalid

Bug description:
  The Startup Application console allows you to specify all the
  applications you'd like to launch during start-up, but it doesn't
  allow you to control the order in which they are launched.

  I'd like the ability to specify the order without having to write a
  custom script. So this is a feature request.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.10
  Package: gnome-session-common 3.6.0-0ubuntu1
  ProcVersionSignature: Ubuntu 3.5.0-18.29-generic 3.5.7
  Uname: Linux 3.5.0-18-generic x86_64
  ApportVersion: 2.6.1-0ubuntu6
  Architecture: amd64
  Date: Wed Nov 14 08:44:57 2012
  Dependencies:
   
  InstallationDate: Installed on 2012-10-19 (26 days ago)
  InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5)
  MarkForUpload: True
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-session
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1078752] Re: Start-UP Command Field Doesn't Support More Than One Command

2018-03-20 Thread Daniel van Vugt
Thank you for reporting this bug to Ubuntu.
Ubuntu 12.10 (quantal) reached end-of-life on May 16, 2014.

See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases 

We appreciate that this bug may be old and you might not be interested
in discussing it any more. But if you are then please upgrade to the
latest Ubuntu version and re-test. If you then find the bug is still
present in the newer Ubuntu version, please add a comment here telling
us which new version it is in and change the bug status to Confirmed.

** Changed in: gnome-session (Ubuntu)
   Status: New => Invalid

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

Title:
  Start-UP Command Field Doesn't Support More Than One Command

Status in gnome-session package in Ubuntu:
  Invalid

Bug description:
  I have an application (sudo apt-get install autokey-qt) that doesn't
  provide an option to launch minimized (see
  https://bugs.launchpad.net/ubuntu/+source/autokey/+bug/1064085 ).

  In Startup Applications, I attempted to solve this problem by running two 
command at once:
  autokey-qt ; wmctrl -k on

  From the command line the line above both launches autokey-qt and
  minimizes all windows, but as a Startup-Application-command it fails
  to even launch autokey-qt.

  It would be nice if Startup Applications supported the ability to both
  (1) "allow you to launch an application" and (2) allow you to provide
  an additional command for controlling the window of that application.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.10
  Package: gnome-session-common 3.6.0-0ubuntu1
  ProcVersionSignature: Ubuntu 3.5.0-18.29-generic 3.5.7
  Uname: Linux 3.5.0-18-generic x86_64
  ApportVersion: 2.6.1-0ubuntu6
  Architecture: amd64
  Date: Wed Nov 14 08:51:32 2012
  Dependencies:

  InstallationDate: Installed on 2012-10-19 (26 days ago)
  InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5)
  MarkForUpload: True
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-session
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 873368] Re: Session fails to start when root system full

2018-03-20 Thread Daniel van Vugt
Is this still a bug?

** Changed in: gnome-session (Ubuntu)
 Assignee: Canonical Desktop Team (canonical-desktop-team) => (unassigned)

** Changed in: gnome-session (Ubuntu)
   Status: Triaged => Incomplete

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

Title:
  Session fails to start when root system full

Status in gnome-session package in Ubuntu:
  Incomplete

Bug description:
  When the root filesystem is full, LightDM and GDM loop back to
  themselves after a couple of seconds instead of starting the main
  desktop.

  Ideally the user should be warned that it is not going to be possible
  to proceed, and what they need to do in order to allow login to
  proceed (make space available on the root partition, rather than their
  home partition).

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

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


[Desktop-packages] [Bug 1757104] Re: Error generated shortly after boot (while running apt-get update)

2018-03-20 Thread Apport retracing service
*** This bug is a duplicate of bug 1748450 ***
https://bugs.launchpad.net/bugs/1748450

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

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

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

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

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

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

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

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

** This bug has been marked a duplicate of bug 1748450
   gnome-shell crashed with SIGTRAP in _g_log_abort() from 
g_log_default_handler() from default_log_handler(message="Connection to 
xwayland lost") from g_logv() from g_log() from 

** Information type changed from Private to Public

** Tags removed: need-amd64-retrace

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

Title:
  Error generated shortly after boot (while running apt-get update)

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  Happens every time computer is rebooted.

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.28.0-0ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7
  Uname: Linux 4.15.0-12-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: GNOME-Greeter:GNOME
  Date: Fri Mar 16 17:53:48 2018
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  GsettingsChanges:
   
  InstallationDate: Installed on 2018-03-12 (7 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180222)
  ProcCmdline: /usr/bin/gnome-shell
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_GB.UTF-8
   SHELL=/bin/false
  Signal: 5
  SourcePackage: gnome-shell
  StacktraceTop:
   ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_log_default_handler () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? ()
   g_logv () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_log () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
  Title: gnome-shell crashed with signal 5 in g_log_default_handler()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

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

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


[Desktop-packages] [Bug 1756857] Re: Routine system hang across multiple versions and devices

2018-03-20 Thread Olivier Tilloy
@Cefn, would you be able to confirm whether the same type of hang
happens with chromium-browser from the ubuntu repositories?

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

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

Title:
  Routine system hang across multiple versions and devices

Status in chromium-browser package in Ubuntu:
  Incomplete

Bug description:
  I have been experiencing a hang (typically triggered when Google
  Chrome is open, but then Google Chrome is always open on my laptops).

  It makes the system entirely unresponsive to mouse or keyboard
  (including CTRL+ALT+F1) for several minutes, at which point it
  suddenly catches up with a whole load of input events and returns to
  full responsiveness. Happens once or twice a day, and happens very
  frequently when I return to a machine which has been idle for a while.

  I have experienced this with both Lubuntu Artful 17.10 (the Thinkpad
  X230 machine I am reporting from), but also two other machines a
  Toshiba Portege R600 and a Dell N5110 both running Bionic. It may be
  related to accessing the filesystem (e.g. launching a Save file dialog
  from Chrome), but can equally be triggered by e.g. launching a
  Terminal, which presumably causes the /etc/profile file to be read.

  At this stage I can't even establish what is going on. Can anyone
  suggest diagnostic steps?

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: lubuntu-core 0.83
  ProcVersionSignature: Ubuntu 4.13.0-21.24-generic 4.13.13
  Uname: Linux 4.13.0-21-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  CurrentDesktop: LXDE
  Date: Mon Mar 19 11:43:08 2018
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2017-10-15 (154 days ago)
  InstallationMedia: Lubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926)
  SourcePackage: lubuntu-meta
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 689349] Re: [Upstream] Draw file exported to PDF have erroneous pixel-sized dots in Acroread, not in Evince

2018-03-20 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/689349

Title:
  [Upstream] Draw file exported to PDF have erroneous pixel-sized dots
  in Acroread, not in Evince

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

Bug description:
  Binary package hint: openoffice.org
  Binary package hint: libreoffice

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

  2) apt-cache policy libreoffice-draw
  libreoffice-draw:
    Installed: 1:3.6.2~rc2-0ubuntu4
    Candidate: 1:3.6.2~rc2-0ubuntu4
    Version table:
   *** 1:3.6.2~rc2-0ubuntu4 0
  900 http://archive.ubuntu.com/ubuntu/ quantal-updates/main i386 
Packages
  400 http://archive.ubuntu.com/ubuntu/ quantal-proposed/main i386 
Packages
  100 /var/lib/dpkg/status
   1:3.6.2~rc2-0ubuntu3 0
  500 http://archive.ubuntu.com/ubuntu/ quantal/main i386 Packages

  apt-cache policy acroread
  acroread:
    Installed: 9.5.1-1precise1
    Candidate: 9.5.1-1precise1
    Version table:
   *** 9.5.1-1precise1 0
  100 /var/lib/dpkg/status

  apt-cache policy evince
  evince:
    Installed: 3.6.0-0ubuntu2
    Candidate: 3.6.0-0ubuntu2
    Version table:
   *** 3.6.0-0ubuntu2 0
  500 http://archive.ubuntu.com/ubuntu/ quantal/main i386 Packages
  100 /var/lib/dpkg/status

  3) What is expected to happen is when one performs at the Terminal:
  cd ~/Desktop && wget 
https://bugs.launchpad.net/ubuntu/+source/openoffice.org/+bug/689349/+attachment/1763870/+files/classnetwork.odg
 && unoconv --listener && unoconv -f pdf classnetwork.odg && acroread 
classnetwork.pdf

  is it looks as it does in Evince.

  4) What happens instead is acroread displays erroneous pixel-sized
  dots as per screenshot
  
https://bugs.launchpad.net/ubuntu/+source/openoffice.org/+bug/689349/+attachment/1763844/+files/garbagescreenshot.png
  , while evince does not.

  First reproduced in Maverick 1:3.3.1-1ubuntu3~maverick1, and
  reproduced in Natty, and Precise.

  Unconfirmed OOo WORKAROUND: The upstream version does _not_ produce
  these effects and is fine.

  ApportVersion: 2.6.1-0ubuntu6
  Architecture: i386
  CheckboxSubmission: 30b6638832e19720cfe8f7a91e5798a4
  CheckboxSystem: 2954e74ba17fb0e37fc942cd1d9fab4e
  DistroRelease: Ubuntu 12.10
  InstallationDate: Installed on 2012-06-11 (164 days ago)
  InstallationMedia: Xubuntu 12.04 "Precise Pangolin" - Alpha i386 (20120131.1)
  MarkForUpload: True
  Package: libreoffice 1:3.6.2~rc2-0ubuntu4
  PackageArchitecture: i386
  ProcEnviron:
   LANGUAGE=en_US:en
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 3.5.0-17.28-generic 3.5.5
  Tags: quantal
  Uname: Linux 3.5.0-17-generic i686
  UpgradeStatus: Upgraded to quantal on 2012-09-14 (68 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

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

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


[Desktop-packages] [Bug 1756877] Re: Input latency in 18.04

2018-03-20 Thread John Skottis
Other configuration i have tried is with or without an external screen.
I am running the mesa graphics driver and not the proprietary Nvidia
one.

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

Title:
  Input latency in 18.04

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  I am on an Dell xps 9530 laptop and I had recently cleaned installed
  17.10. A few days back I decided to updated to 18.04 to check it out
  and report some bugs. The most annoying bug so far is the insane
  amount of input latency this update has brought with it to a degree
  that it makes it impossible to be productive. The issue is observable
  when using either the mouse or the keyboard. The mouse does not move
  immediately but it needs a second or two to register and start moving
  and even then at some point it freezes for half a second at some
  random point and then moves again. Also if I have two applications
  side by side and I try an move focus from one to the next at around
  the edges of each window the mouse freezes for a second and then
  moves. The keyboard freezes if it hasn't been used for a while and on
  the first keystroke will take a second to register and for a bonus you
  get the first keystorke repeated for around 15-30 times. So if you are
  trying to write "and" will become "aaand" or pressing
  "ctrl + T" in the browser will open not one but 20 tabs!

  I am reporting it here cause I am not sure what is causing all this
  latency (it could be libinput or something else entirely) but please
  try and fix this as soon as possible!!

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.28.0-0ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  Uname: Linux 4.15.0-13-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Mar 19 13:04:05 2018
  DisplayManager: gdm3
  InstallationDate: Installed on 2018-02-14 (32 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to bionic on 2018-03-15 (3 days ago)

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

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


[Desktop-packages] [Bug 1757113] Re: gnome-shell crashed with signal 5

2018-03-20 Thread Apport retracing service
*** This bug is a duplicate of bug 1748450 ***
https://bugs.launchpad.net/bugs/1748450

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

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

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

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

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

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

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

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

** This bug has been marked a duplicate of bug 1748450
   gnome-shell crashed with SIGTRAP in _g_log_abort() from 
g_log_default_handler() from default_log_handler(message="Connection to 
xwayland lost") from g_logv() from g_log() from 

** Information type changed from Private to Public

** Tags removed: need-amd64-retrace

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

Title:
  gnome-shell crashed with signal 5

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  Restarted system and upon first login, encountered this crash.

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.28.0-0ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7
  Uname: Linux 4.15.0-12-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: GNOME-Greeter:GNOME
  Date: Tue Mar 20 07:06:22 2018
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  GsettingsChanges:
   
  InstallationDate: Installed on 2018-03-12 (7 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180311)
  ProcCmdline: /usr/bin/gnome-shell
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/false
  Signal: 5
  SourcePackage: gnome-shell
  StacktraceTop:
   () at /usr/lib/x86_64-linux-gnu/libmutter-2.so.0
   _XIOError () at /usr/lib/x86_64-linux-gnu/libX11.so.6
   _XEventsQueued () at /usr/lib/x86_64-linux-gnu/libX11.so.6
   XPending () at /usr/lib/x86_64-linux-gnu/libX11.so.6
   () at /usr/lib/x86_64-linux-gnu/libgdk-3.so.0
  Title: gnome-shell crashed with signal 5
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

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

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


[Desktop-packages] [Bug 1755106] Re: /org/gnome/settings-daemon/plugins/media-keys/custom-keybindings/ fails to load

2018-03-20 Thread Péter Prőhle
I wish to provide better diagnostic information, but I do not know what
to submit in this particular situation.

I am also ready to install some sort of Watchdog daemon, which can
better detect what is going on in this kind of situation.  I can imagine
a say a small shell script or something alike as well.

Right now I have again a boot resulting no custom keybindings while all
the other keybindings work.

Again: "ps acuwx | fgrep gsd" is empty, and "journalctl | grep gsd" has
no new entry since "Mar 12 08:47:48".

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

Title:
  /org/gnome/settings-daemon/plugins/media-keys/custom-keybindings/
  fails to load

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

Bug description:
  $ dconf dump /org/gnome/settings-daemon/plugins/media-keys/custom-keybindings/
  [custom1]
  binding='BackSpace'
  command='gnome-session-quit --power-off'
  name='gnome-session-quit --power-off'

  [custom0]
  binding='g'
  command='gnome-terminal --geometry=80x99-0+0'
  name='gnome-terminal --geometry=80x99-0+0'
  $

  In spite of the above, time to time, not always, but since 18.04 much
  much more frequently this settings fails to become active just after
  booting, ... my account is logged in automatically just after boot.

  If I log out and log in again, then these key bindings work.

  If I go to the system settings, and define again, then these work
  again.

  Earlier, before 18.04 this phenomenon was rare, namely once a week at
  most.

  But since 18.04 it is almost guaranteed, not deterministic, but highly
  probable, that after an initial boot or a warm reboot these key
  bindings will not work.

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

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


[Desktop-packages] [Bug 1754803] Re: [FFe] Disable telepathy support in gnome-contacts

2018-03-20 Thread Iain Lane
this makes sense. I'd prefer to sync an update doing this from Debian,
but your call, go ahead.

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

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

Title:
  [FFe] Disable telepathy support in gnome-contacts

Status in gnome-contacts package in Ubuntu:
  Confirmed

Bug description:
  We would like to disable (at buildtime) telepathy support in gnome-
  contacts

  
  Feature Freeze Justification
  
  Telepathy support is largely being deprecated in GNOME. Gnome-contacts is one 
of few GNOME modules still using it. It has been disabled in 
gnome-online-accounts (and will be completely removed from GOA next cycle[1]).

  With the GOA provider gone it is less useful since you won't get
  contacts from telepathy clients and you can't make calls. presumably
  the chat still works though if manually configured.

  Debian is considering disabling it this cycle.
  Upstream will consider it next cycle

  gnome-contacts is not seeded on any flavors, other than the vanilla-
  gnome-desktop.

  gnome-contacts is currently the only thing pulling in telepathy and
  all its deps when installing vanilla-gnome-desktop.

  
  [1] 
https://mail.gnome.org/archives/desktop-devel-list/2017-October/msg00040.html

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

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


[Desktop-packages] [Bug 1754803] Re: [FFe] Disable telepathy support in gnome-contacts

2018-03-20 Thread Tim Lunn
I would also, but don't think that is likely to happen in time for
bionic.

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

Title:
  [FFe] Disable telepathy support in gnome-contacts

Status in gnome-contacts package in Ubuntu:
  Confirmed

Bug description:
  We would like to disable (at buildtime) telepathy support in gnome-
  contacts

  
  Feature Freeze Justification
  
  Telepathy support is largely being deprecated in GNOME. Gnome-contacts is one 
of few GNOME modules still using it. It has been disabled in 
gnome-online-accounts (and will be completely removed from GOA next cycle[1]).

  With the GOA provider gone it is less useful since you won't get
  contacts from telepathy clients and you can't make calls. presumably
  the chat still works though if manually configured.

  Debian is considering disabling it this cycle.
  Upstream will consider it next cycle

  gnome-contacts is not seeded on any flavors, other than the vanilla-
  gnome-desktop.

  gnome-contacts is currently the only thing pulling in telepathy and
  all its deps when installing vanilla-gnome-desktop.

  
  [1] 
https://mail.gnome.org/archives/desktop-devel-list/2017-October/msg00040.html

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

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


[Desktop-packages] [Bug 1754803] Re: [FFe] Disable telepathy support in gnome-contacts

2018-03-20 Thread Jeremy Bicha
You can tweak debian/rules to apply different configure flags when this
package is built for Ubuntu. But go ahead and ask Debian again if they
want this change themselves too.

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

Title:
  [FFe] Disable telepathy support in gnome-contacts

Status in gnome-contacts package in Ubuntu:
  Confirmed

Bug description:
  We would like to disable (at buildtime) telepathy support in gnome-
  contacts

  
  Feature Freeze Justification
  
  Telepathy support is largely being deprecated in GNOME. Gnome-contacts is one 
of few GNOME modules still using it. It has been disabled in 
gnome-online-accounts (and will be completely removed from GOA next cycle[1]).

  With the GOA provider gone it is less useful since you won't get
  contacts from telepathy clients and you can't make calls. presumably
  the chat still works though if manually configured.

  Debian is considering disabling it this cycle.
  Upstream will consider it next cycle

  gnome-contacts is not seeded on any flavors, other than the vanilla-
  gnome-desktop.

  gnome-contacts is currently the only thing pulling in telepathy and
  all its deps when installing vanilla-gnome-desktop.

  
  [1] 
https://mail.gnome.org/archives/desktop-devel-list/2017-October/msg00040.html

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

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


[Desktop-packages] [Bug 1756380] Re: vaapi VP9 hardware decoding not working anymore in bionic

2018-03-20 Thread Sebastian Stark
@tjaalton looks like. This is with the ubuntu supplied libva and driver
version 2.0.0 from github:

> vainfo
libva info: VA-API version 1.1.0
libva info: va_getDriverName() returns 0
libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/i965_drv_video.so
libva info: Found init function __vaDriverInit_1_1
libva info: va_openDriver() returns 0
vainfo: VA-API version: 1.1 (libva 2.1.0)
vainfo: Driver version: Intel i965 driver for Intel(R) Kaby Lake - 2.0.0
vainfo: Supported profile and entrypoints
  VAProfileMPEG2Simple: VAEntrypointVLD
  VAProfileMPEG2Simple: VAEntrypointEncSlice
  VAProfileMPEG2Main  : VAEntrypointVLD
  VAProfileMPEG2Main  : VAEntrypointEncSlice
  VAProfileH264ConstrainedBaseline: VAEntrypointVLD
  VAProfileH264ConstrainedBaseline: VAEntrypointEncSlice
  VAProfileH264ConstrainedBaseline: VAEntrypointEncSliceLP
  VAProfileH264Main   : VAEntrypointVLD
  VAProfileH264Main   : VAEntrypointEncSlice
  VAProfileH264Main   : VAEntrypointEncSliceLP
  VAProfileH264High   : VAEntrypointVLD
  VAProfileH264High   : VAEntrypointEncSlice
  VAProfileH264High   : VAEntrypointEncSliceLP
  VAProfileH264MultiviewHigh  : VAEntrypointVLD
  VAProfileH264MultiviewHigh  : VAEntrypointEncSlice
  VAProfileH264StereoHigh : VAEntrypointVLD
  VAProfileH264StereoHigh : VAEntrypointEncSlice
  VAProfileVC1Simple  : VAEntrypointVLD
  VAProfileVC1Main: VAEntrypointVLD
  VAProfileVC1Advanced: VAEntrypointVLD
  VAProfileNone   : VAEntrypointVideoProc
  VAProfileJPEGBaseline   : VAEntrypointVLD
  VAProfileJPEGBaseline   : VAEntrypointEncPicture
  VAProfileVP8Version0_3  : VAEntrypointVLD
  VAProfileVP8Version0_3  : VAEntrypointEncSlice
  VAProfileHEVCMain   : VAEntrypointVLD
  VAProfileHEVCMain   : VAEntrypointEncSlice
  VAProfileHEVCMain10 : VAEntrypointVLD
  VAProfileHEVCMain10 : VAEntrypointEncSlice
  VAProfileVP9Profile0: VAEntrypointVLD
  VAProfileVP9Profile0: VAEntrypointEncSlice
  VAProfileVP9Profile2: VAEntrypointVLD

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

Title:
  vaapi VP9 hardware decoding not working anymore in bionic

Status in intel-vaapi-driver package in Ubuntu:
  Confirmed
Status in libva package in Ubuntu:
  Invalid

Bug description:
  Hardware: Dell XPS13 9365, i7-7Y75
  System: Ubuntu Bionic Beaver (development branch)

  
  vainfo output on bionic is:

  libva info: VA-API version 1.1.0
  libva info: va_getDriverName() returns 0
  libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/i965_drv_video.so
  libva info: Found init function __vaDriverInit_1_0
  libva info: va_openDriver() returns 0
  vainfo: VA-API version: 1.1 (libva 2.1.0)
  vainfo: Driver version: Intel i965 driver for Intel(R) Kaby Lake - 2.0.0
  vainfo: Supported profile and entrypoints
VAProfileMPEG2Simple:   VAEntrypointVLD
VAProfileMPEG2Simple:   VAEntrypointEncSlice
VAProfileMPEG2Main  :   VAEntrypointVLD
VAProfileMPEG2Main  :   VAEntrypointEncSlice
VAProfileH264ConstrainedBaseline:   VAEntrypointVLD
VAProfileH264ConstrainedBaseline:   VAEntrypointEncSlice
VAProfileH264ConstrainedBaseline:   VAEntrypointEncSliceLP
VAProfileH264Main   :   VAEntrypointVLD
VAProfileH264Main   :   VAEntrypointEncSlice
VAProfileH264Main   :   VAEntrypointEncSliceLP
VAProfileH264High   :   VAEntrypointVLD
VAProfileH264High   :   VAEntrypointEncSlice
VAProfileH264High   :   VAEntrypointEncSliceLP
VAProfileH264MultiviewHigh  :   VAEntrypointVLD
VAProfileH264MultiviewHigh  :   VAEntrypointEncSlice
VAProfileH264StereoHigh :   VAEntrypointVLD
VAProfileH264StereoHigh :   VAEntrypointEncSlice
VAProfileVC1Simple  :   VAEntrypointVLD
VAProfileVC1Main:   VAEntrypointVLD
VAProfileVC1Advanced:   VAEntrypointVLD
VAProfileNone   :   VAEntrypointVideoProc
VAProfileJPEGBaseline   :   VAEntrypointVLD
VAProfileJPEGBaseline   :   VAEntrypointEncPicture
VAProfileVP8Version0_3  :   VAEntrypointVLD
VAProfileHEVCMain   :   VAEntrypointVLD
VAProfileHEVCMain   :   VAEn

[Desktop-packages] [Bug 1751460] Re: [regression] deja-dup-monitor crashed with SIGSEGV in Gigacage::::operator()

2018-03-20 Thread Vej
You fixed by removing a fix without taking measurements to prevent the problem 
the fix was for?
Are you going to handle that as well or are we just going to see the OOM bugs 
again?

If you are handling this in another bug: Please link it here.

Thanks

Vej

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

Title:
  [regression] deja-dup-monitor crashed with SIGSEGV in
  Gigacageoperator()

Status in Déjà Dup:
  New
Status in WebKit:
  Fix Released
Status in deja-dup package in Ubuntu:
  Fix Released
Status in webkit2gtk package in Ubuntu:
  Triaged
Status in deja-dup source package in Xenial:
  Triaged
Status in webkit2gtk source package in Xenial:
  Confirmed
Status in deja-dup source package in Artful:
  Triaged
Status in webkit2gtk source package in Artful:
  Confirmed
Status in deja-dup source package in Bionic:
  Fix Released
Status in webkit2gtk source package in Bionic:
  Triaged

Bug description:
  https://errors.ubuntu.com/problem/27441b78823246dd5392ee29ac30546f6464289e

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: deja-dup 37.1-1fakesync1
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: GNOME
  Date: Sat Feb 24 14:30:47 2018
  ExecutablePath: /usr/lib/deja-dup/deja-dup-monitor
  InstallationDate: Installed on 2017-12-27 (59 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  ProcCmdline: /usr/lib/deja-dup/deja-dup-monitor
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  SegvAnalysis:
   Segfault happened at: 0x7ff1c3dda588:movl   $0x0,(%rax)
   PC (0x7ff1c3dda588) ok
   source "$0x0" ok
   destination "(%rax)" (0xbbadbeef) not located in a known VMA region (needed 
writable region)!
  SegvReason: writing unknown VMA
  Signal: 11
  SourcePackage: deja-dup
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/libjavascriptcoregtk-4.0.so.18
   __pthread_once_slow (once_control=0x7ff1c404202c, 
init_routine=0x7ff1baec0490 <__once_proxy>) at pthread_once.c:116
   Gigacage::ensureGigacage() () from 
/usr/lib/x86_64-linux-gnu/libjavascriptcoregtk-4.0.so.18
   bmalloc::Heap::Heap(bmalloc::HeapKind, 
std::lock_guard&) () from 
/usr/lib/x86_64-linux-gnu/libjavascriptcoregtk-4.0.so.18
   bmalloc::PerProcess >::getSlowCase() () 
from /usr/lib/x86_64-linux-gnu/libjavascriptcoregtk-4.0.so.18
  Title: deja-dup-monitor crashed with SIGSEGV in __pthread_once_slow()
  UpgradeStatus: Upgraded to bionic on 2018-02-24 (0 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

To manage notifications about this bug go to:
https://bugs.launchpad.net/deja-dup/+bug/1751460/+subscriptions

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


[Desktop-packages] [Bug 360970] Re: Multi-monitor - When using two displays with different vertical resolution, icons get lost on the shorter display

2018-03-20 Thread Robert Pollina
Still in Ubuntu 18.04 beta.

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

Title:
  Multi-monitor - When using two displays with different vertical
  resolution, icons get lost on the shorter display

Status in Ayatana Design:
  Fix Committed
Status in Nautilus:
  Expired
Status in Unity:
  Confirmed
Status in nautilus package in Ubuntu:
  Triaged

Bug description:
  On a Multi-Monitor setup, where the extended desktop is non-
  rectangular in shape (ie. the displays are of a different resolution,
  and their top/bottom/left/right edges are not aligned), desktop icons
  are placed in non-accessible areas when arranged using the menu option
  'View-Organise Desktop by Name' from the Desktop.

  See the attached image. The top three desktop items are not
  accessible, and can only be seen in the Workspace Switcher.

  Please also refer to the 'Non-Rectangular Extended Desktops' section of the 
Multi-Monitor spec:
  
https://docs.google.com/a/canonical.com/document/d/1aHvJ-iIw-59bXTYBmIhQqEx0za2h9jpFE_RhZ2VOvJc/edit#bookmark=id.yph05n82oeff

  --

  [Test Case]
  1. Set up two monitors side by side
  2. Set left monitor to a smaller vertical resolution than the right monitor
  3. for i in $(seq 1 50) ; do touch file-${i} ; done
  4. Right click on desktop to bring up context menu, then 'Organize Desktop by 
Name'
  5. Should be: All icons from file-1 to file-50 (or as many fit on the screen) 
should be visible
   Is: Icons for files at the top and/or bottom of the arranged columns are 
not visible on any display
  6. xrandr --output LVDS1 --off
  7. Verify icons are arranged properly on the external monitor
  8. Set up monitors one over the other
  9. Verify icons are displayed in long columns spanning both displays with all 
icons shown

To manage notifications about this bug go to:
https://bugs.launchpad.net/ayatana-design/+bug/360970/+subscriptions

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


[Desktop-packages] [Bug 1754803] Re: [FFe] Disable telepathy support in gnome-contacts

2018-03-20 Thread Ubuntu Foundations Team Bug Bot
** Tags added: patch

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

Title:
  [FFe] Disable telepathy support in gnome-contacts

Status in gnome-contacts package in Ubuntu:
  Confirmed

Bug description:
  We would like to disable (at buildtime) telepathy support in gnome-
  contacts

  
  Feature Freeze Justification
  
  Telepathy support is largely being deprecated in GNOME. Gnome-contacts is one 
of few GNOME modules still using it. It has been disabled in 
gnome-online-accounts (and will be completely removed from GOA next cycle[1]).

  With the GOA provider gone it is less useful since you won't get
  contacts from telepathy clients and you can't make calls. presumably
  the chat still works though if manually configured.

  Debian is considering disabling it this cycle.
  Upstream will consider it next cycle

  gnome-contacts is not seeded on any flavors, other than the vanilla-
  gnome-desktop.

  gnome-contacts is currently the only thing pulling in telepathy and
  all its deps when installing vanilla-gnome-desktop.

  
  [1] 
https://mail.gnome.org/archives/desktop-devel-list/2017-October/msg00040.html

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

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


[Desktop-packages] [Bug 1751460] Re: [regression] deja-dup-monitor crashed with SIGSEGV in Gigacage::::operator()

2018-03-20 Thread Jeremy Bicha
Vej, please file a separate bug if you can reproduce the original memory
consumption bug.

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

Title:
  [regression] deja-dup-monitor crashed with SIGSEGV in
  Gigacageoperator()

Status in Déjà Dup:
  New
Status in WebKit:
  Fix Released
Status in deja-dup package in Ubuntu:
  Fix Released
Status in webkit2gtk package in Ubuntu:
  Triaged
Status in deja-dup source package in Xenial:
  Triaged
Status in webkit2gtk source package in Xenial:
  Confirmed
Status in deja-dup source package in Artful:
  Triaged
Status in webkit2gtk source package in Artful:
  Confirmed
Status in deja-dup source package in Bionic:
  Fix Released
Status in webkit2gtk source package in Bionic:
  Triaged

Bug description:
  https://errors.ubuntu.com/problem/27441b78823246dd5392ee29ac30546f6464289e

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: deja-dup 37.1-1fakesync1
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: GNOME
  Date: Sat Feb 24 14:30:47 2018
  ExecutablePath: /usr/lib/deja-dup/deja-dup-monitor
  InstallationDate: Installed on 2017-12-27 (59 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  ProcCmdline: /usr/lib/deja-dup/deja-dup-monitor
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  SegvAnalysis:
   Segfault happened at: 0x7ff1c3dda588:movl   $0x0,(%rax)
   PC (0x7ff1c3dda588) ok
   source "$0x0" ok
   destination "(%rax)" (0xbbadbeef) not located in a known VMA region (needed 
writable region)!
  SegvReason: writing unknown VMA
  Signal: 11
  SourcePackage: deja-dup
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/libjavascriptcoregtk-4.0.so.18
   __pthread_once_slow (once_control=0x7ff1c404202c, 
init_routine=0x7ff1baec0490 <__once_proxy>) at pthread_once.c:116
   Gigacage::ensureGigacage() () from 
/usr/lib/x86_64-linux-gnu/libjavascriptcoregtk-4.0.so.18
   bmalloc::Heap::Heap(bmalloc::HeapKind, 
std::lock_guard&) () from 
/usr/lib/x86_64-linux-gnu/libjavascriptcoregtk-4.0.so.18
   bmalloc::PerProcess >::getSlowCase() () 
from /usr/lib/x86_64-linux-gnu/libjavascriptcoregtk-4.0.so.18
  Title: deja-dup-monitor crashed with SIGSEGV in __pthread_once_slow()
  UpgradeStatus: Upgraded to bionic on 2018-02-24 (0 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

To manage notifications about this bug go to:
https://bugs.launchpad.net/deja-dup/+bug/1751460/+subscriptions

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


[Desktop-packages] [Bug 1757126] Re: gnome-software crashed with signal 5 in g_main_context_new()

2018-03-20 Thread Apport retracing service
*** This bug is a duplicate of bug 1755064 ***
https://bugs.launchpad.net/bugs/1755064

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

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

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

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

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

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

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

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

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

** Information type changed from Private to Public

** Tags removed: need-amd64-retrace

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

Title:
  gnome-software crashed with signal 5 in g_main_context_new()

Status in gnome-software package in Ubuntu:
  New

Bug description:
  I had installed Ubuntu 18.04 daily build from 13 March 2018 with a
  minimal gnome install.  Today I decided to install gnome from
  terminal, and while it was installing I noticed there were two
  calculators.  So I clicked "show details" and it opened Gnome
  Software, which I closed and then there was the bug report interface.

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: gnome-software 3.28.0-0ubuntu4
  ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7
  Uname: Linux 4.15.0-12-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Mar 20 07:21:55 2018
  ExecutablePath: /usr/bin/gnome-software
  InstallationDate: Installed on 2018-03-17 (2 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180313)
  InstalledPlugins:
   gnome-software-plugin-flatpak N/A
   gnome-software-plugin-limba   N/A
   gnome-software-plugin-snap3.28.0-0ubuntu4
  ProcCmdline: /usr/bin/gnome-software --gapplication-service
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  Signal: 5
  SourcePackage: gnome-software
  StacktraceTop:
   ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_main_context_new () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   pk_client_resolve () from /usr/lib/x86_64-linux-gnu/libpackagekit-glib2.so.18
   ?? () from 
/usr/lib/x86_64-linux-gnu/gs-plugins-11/libgs_plugin_packagekit-refine.so
   gs_plugin_refine () from 
/usr/lib/x86_64-linux-gnu/gs-plugins-11/libgs_plugin_packagekit-refine.so
  Title: gnome-software crashed with signal 5 in g_main_context_new()
  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-software/+bug/1757126/+subscriptions

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


[Desktop-packages] [Bug 1756380] Re: vaapi VP9 hardware decoding not working anymore in bionic

2018-03-20 Thread Timo Aaltonen
Yeah, I've prepared a package which restores the shader files in the
same package again, but it would end up in multiverse

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

Title:
  vaapi VP9 hardware decoding not working anymore in bionic

Status in intel-vaapi-driver package in Ubuntu:
  Confirmed
Status in libva package in Ubuntu:
  Invalid

Bug description:
  Hardware: Dell XPS13 9365, i7-7Y75
  System: Ubuntu Bionic Beaver (development branch)

  
  vainfo output on bionic is:

  libva info: VA-API version 1.1.0
  libva info: va_getDriverName() returns 0
  libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/i965_drv_video.so
  libva info: Found init function __vaDriverInit_1_0
  libva info: va_openDriver() returns 0
  vainfo: VA-API version: 1.1 (libva 2.1.0)
  vainfo: Driver version: Intel i965 driver for Intel(R) Kaby Lake - 2.0.0
  vainfo: Supported profile and entrypoints
VAProfileMPEG2Simple:   VAEntrypointVLD
VAProfileMPEG2Simple:   VAEntrypointEncSlice
VAProfileMPEG2Main  :   VAEntrypointVLD
VAProfileMPEG2Main  :   VAEntrypointEncSlice
VAProfileH264ConstrainedBaseline:   VAEntrypointVLD
VAProfileH264ConstrainedBaseline:   VAEntrypointEncSlice
VAProfileH264ConstrainedBaseline:   VAEntrypointEncSliceLP
VAProfileH264Main   :   VAEntrypointVLD
VAProfileH264Main   :   VAEntrypointEncSlice
VAProfileH264Main   :   VAEntrypointEncSliceLP
VAProfileH264High   :   VAEntrypointVLD
VAProfileH264High   :   VAEntrypointEncSlice
VAProfileH264High   :   VAEntrypointEncSliceLP
VAProfileH264MultiviewHigh  :   VAEntrypointVLD
VAProfileH264MultiviewHigh  :   VAEntrypointEncSlice
VAProfileH264StereoHigh :   VAEntrypointVLD
VAProfileH264StereoHigh :   VAEntrypointEncSlice
VAProfileVC1Simple  :   VAEntrypointVLD
VAProfileVC1Main:   VAEntrypointVLD
VAProfileVC1Advanced:   VAEntrypointVLD
VAProfileNone   :   VAEntrypointVideoProc
VAProfileJPEGBaseline   :   VAEntrypointVLD
VAProfileJPEGBaseline   :   VAEntrypointEncPicture
VAProfileVP8Version0_3  :   VAEntrypointVLD
VAProfileHEVCMain   :   VAEntrypointVLD
VAProfileHEVCMain   :   VAEntrypointEncSlice
VAProfileHEVCMain10 :   VAEntrypointVLD
VAProfileHEVCMain10 :   VAEntrypointEncSlice

  As you can see, VP9 entrypoints are missing.

  vainfo output on 17.10 was:

  libva info: VA-API version 0.40.0
  libva info: va_getDriverName() returns 0
  libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/i965_drv_video.so
  libva info: Found init function __vaDriverInit_0_40
  libva info: va_openDriver() returns 0
  vainfo: VA-API version: 0.40 (libva )
  vainfo: Driver version: Intel i965 driver for Intel(R) Kabylake - 1.8.3
  vainfo: Supported profile and entrypoints
VAProfileMPEG2Simple:VAEntrypointVLD
VAProfileMPEG2Simple:VAEntrypointEncSlice
VAProfileMPEG2Main  :VAEntrypointVLD
VAProfileMPEG2Main  :VAEntrypointEncSlice
VAProfileH264ConstrainedBaseline:VAEntrypointVLD
VAProfileH264ConstrainedBaseline:VAEntrypointEncSlice
VAProfileH264ConstrainedBaseline:VAEntrypointEncSliceLP
VAProfileH264Main   :VAEntrypointVLD
VAProfileH264Main   :VAEntrypointEncSlice
VAProfileH264Main   :VAEntrypointEncSliceLP
VAProfileH264High   :VAEntrypointVLD
VAProfileH264High   :VAEntrypointEncSlice
VAProfileH264High   :VAEntrypointEncSliceLP
VAProfileH264MultiviewHigh  :VAEntrypointVLD
VAProfileH264MultiviewHigh  :VAEntrypointEncSlice
VAProfileH264StereoHigh :VAEntrypointVLD
VAProfileH264StereoHigh :VAEntrypointEncSlice
VAProfileVC1Simple  :VAEntrypointVLD
VAProfileVC1Main:VAEntrypointVLD
VAProfileVC1Advanced:VAEntrypointVLD
VAProfileNone   :VAEntrypointVideoProc
VAProfileJPEGBaseline   :VAEntrypointVLD
VAProfileJPEGBaseline   :VAEntrypointEncPicture
VAProfileVP8Version0_3  :VAEntrypointVLD
VAProfileVP8Version0_3  :VAEntrypointEncSlice
VAProfileHEVCMain

[Desktop-packages] [Bug 1724977] Re: two mouse cursors visible at the same time on rotated screen

2018-03-20 Thread Mariano Jesús Alda Membrives
Just FYI if it can help you guys in any way (I do know this is an Ubuntu
forum), I'm adding a confirmation that this is not Ubuntu specific. I've
also reproduced it in Fedora 27 under Wayland with 3 monitors: left
horizontal, middle vertical (rotated right), right horizontal. There's
algo an open bug in Fedora Bugzilla: see RedHat bug:
https://bugzilla.redhat.com/show_bug.cgi?id=1513160.

** Bug watch added: Red Hat Bugzilla #1513160
   https://bugzilla.redhat.com/show_bug.cgi?id=1513160

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

Title:
  two mouse cursors visible at the same time on rotated screen

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

Bug description:
  When my 2nd Asus (Ancor) display is in portrait mode and is set to be
  to the left of my centered landscape display in extended mode, moving
  the mouse to roughly the left 20% of my landscape display will show a
  mouse cursor on my landcape display AND portrait display at the same
  time.  Oddly moving a window into this area only shows on the
  landscape display.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: xorg 1:7.7+19ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Oct 19 13:43:30 2017
  DistUpgraded: Fresh install
  DistroCodename: artful
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: Lenovo 3rd Gen Core processor Graphics Controller [17aa:2203]
  InstallationDate: Installed on 2017-10-19 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  MachineType: LENOVO 343522U
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic.efi.signed 
root=UUID=df6662ff-9496-4ff5-8165-82efdbf0b335 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/28/2014
  dmi.bios.vendor: LENOVO
  dmi.bios.version: GCET99WW (2.59 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 343522U
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrGCET99WW(2.59):bd05/28/2014:svnLENOVO:pn343522U:pvrThinkPadX230Tablet:rvnLENOVO:rn343522U:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.family: ThinkPad X230 Tablet
  dmi.product.name: 343522U
  dmi.product.version: ThinkPad X230 Tablet
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.83-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.2-0ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.2-0ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20170309-0ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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

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


[Desktop-packages] [Bug 1074617] Re: liferea crashes when I add a new subscription

2018-03-20 Thread berkes
Happens also when running `liferea-add-feed` which is a wrapper around
`liferea --add-feed`. The latter also causes a crash.

Attached is a strace log, created by running `strace -o liferea-
crash.log /usr/bin/liferea --add-feed
http://feeds.bbci.co.uk/news/rss.xml`.

** Attachment added: "Attached is a strace log, created by running `strace -o 
liferea-crash.log /usr/bin/liferea --add-feed 
http://feeds.bbci.co.uk/news/rss.xml`.";
   
https://bugs.launchpad.net/ubuntu/+source/liferea/+bug/1074617/+attachment/5084904/+files/liferea-crash.log

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

Title:
  liferea crashes when I add a new subscription

Status in liferea package in Ubuntu:
  Confirmed

Bug description:
  When I try to add a subscription using the button Liferea you close
  without completing the operation

  ProblemType: Bug
  DistroRelease: Ubuntu 12.10
  Package: liferea 1.8.3-0.1ubuntu2 [modified: usr/bin/liferea]
  Uname: Linux 3.6.5-030605-generic i686
  ApportVersion: 2.6.1-0ubuntu6
  Architecture: i386
  Date: Sat Nov  3 12:27:11 2012
  InstallationDate: Installed on 2012-09-05 (58 days ago)
  InstallationMedia: Lubuntu 12.04 "Precise Pangolin" - Release i386 (20120423)
  MarkForUpload: True
  SourcePackage: liferea
  UpgradeStatus: Upgraded to quantal on 2012-10-18 (15 days ago)

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

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


[Desktop-packages] [Bug 1074617] Re: liferea crashes when I add a new subscription

2018-03-20 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

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

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

Title:
  liferea crashes when I add a new subscription

Status in liferea package in Ubuntu:
  Confirmed

Bug description:
  When I try to add a subscription using the button Liferea you close
  without completing the operation

  ProblemType: Bug
  DistroRelease: Ubuntu 12.10
  Package: liferea 1.8.3-0.1ubuntu2 [modified: usr/bin/liferea]
  Uname: Linux 3.6.5-030605-generic i686
  ApportVersion: 2.6.1-0ubuntu6
  Architecture: i386
  Date: Sat Nov  3 12:27:11 2012
  InstallationDate: Installed on 2012-09-05 (58 days ago)
  InstallationMedia: Lubuntu 12.04 "Precise Pangolin" - Release i386 (20120423)
  MarkForUpload: True
  SourcePackage: liferea
  UpgradeStatus: Upgraded to quantal on 2012-10-18 (15 days ago)

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

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


[Desktop-packages] [Bug 1756380] Re: vaapi VP9 hardware decoding not working anymore in bionic

2018-03-20 Thread Sebastian Stark
great, multiverse is still better than some ppa

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

Title:
  vaapi VP9 hardware decoding not working anymore in bionic

Status in intel-vaapi-driver package in Ubuntu:
  Confirmed
Status in libva package in Ubuntu:
  Invalid

Bug description:
  Hardware: Dell XPS13 9365, i7-7Y75
  System: Ubuntu Bionic Beaver (development branch)

  
  vainfo output on bionic is:

  libva info: VA-API version 1.1.0
  libva info: va_getDriverName() returns 0
  libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/i965_drv_video.so
  libva info: Found init function __vaDriverInit_1_0
  libva info: va_openDriver() returns 0
  vainfo: VA-API version: 1.1 (libva 2.1.0)
  vainfo: Driver version: Intel i965 driver for Intel(R) Kaby Lake - 2.0.0
  vainfo: Supported profile and entrypoints
VAProfileMPEG2Simple:   VAEntrypointVLD
VAProfileMPEG2Simple:   VAEntrypointEncSlice
VAProfileMPEG2Main  :   VAEntrypointVLD
VAProfileMPEG2Main  :   VAEntrypointEncSlice
VAProfileH264ConstrainedBaseline:   VAEntrypointVLD
VAProfileH264ConstrainedBaseline:   VAEntrypointEncSlice
VAProfileH264ConstrainedBaseline:   VAEntrypointEncSliceLP
VAProfileH264Main   :   VAEntrypointVLD
VAProfileH264Main   :   VAEntrypointEncSlice
VAProfileH264Main   :   VAEntrypointEncSliceLP
VAProfileH264High   :   VAEntrypointVLD
VAProfileH264High   :   VAEntrypointEncSlice
VAProfileH264High   :   VAEntrypointEncSliceLP
VAProfileH264MultiviewHigh  :   VAEntrypointVLD
VAProfileH264MultiviewHigh  :   VAEntrypointEncSlice
VAProfileH264StereoHigh :   VAEntrypointVLD
VAProfileH264StereoHigh :   VAEntrypointEncSlice
VAProfileVC1Simple  :   VAEntrypointVLD
VAProfileVC1Main:   VAEntrypointVLD
VAProfileVC1Advanced:   VAEntrypointVLD
VAProfileNone   :   VAEntrypointVideoProc
VAProfileJPEGBaseline   :   VAEntrypointVLD
VAProfileJPEGBaseline   :   VAEntrypointEncPicture
VAProfileVP8Version0_3  :   VAEntrypointVLD
VAProfileHEVCMain   :   VAEntrypointVLD
VAProfileHEVCMain   :   VAEntrypointEncSlice
VAProfileHEVCMain10 :   VAEntrypointVLD
VAProfileHEVCMain10 :   VAEntrypointEncSlice

  As you can see, VP9 entrypoints are missing.

  vainfo output on 17.10 was:

  libva info: VA-API version 0.40.0
  libva info: va_getDriverName() returns 0
  libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/i965_drv_video.so
  libva info: Found init function __vaDriverInit_0_40
  libva info: va_openDriver() returns 0
  vainfo: VA-API version: 0.40 (libva )
  vainfo: Driver version: Intel i965 driver for Intel(R) Kabylake - 1.8.3
  vainfo: Supported profile and entrypoints
VAProfileMPEG2Simple:VAEntrypointVLD
VAProfileMPEG2Simple:VAEntrypointEncSlice
VAProfileMPEG2Main  :VAEntrypointVLD
VAProfileMPEG2Main  :VAEntrypointEncSlice
VAProfileH264ConstrainedBaseline:VAEntrypointVLD
VAProfileH264ConstrainedBaseline:VAEntrypointEncSlice
VAProfileH264ConstrainedBaseline:VAEntrypointEncSliceLP
VAProfileH264Main   :VAEntrypointVLD
VAProfileH264Main   :VAEntrypointEncSlice
VAProfileH264Main   :VAEntrypointEncSliceLP
VAProfileH264High   :VAEntrypointVLD
VAProfileH264High   :VAEntrypointEncSlice
VAProfileH264High   :VAEntrypointEncSliceLP
VAProfileH264MultiviewHigh  :VAEntrypointVLD
VAProfileH264MultiviewHigh  :VAEntrypointEncSlice
VAProfileH264StereoHigh :VAEntrypointVLD
VAProfileH264StereoHigh :VAEntrypointEncSlice
VAProfileVC1Simple  :VAEntrypointVLD
VAProfileVC1Main:VAEntrypointVLD
VAProfileVC1Advanced:VAEntrypointVLD
VAProfileNone   :VAEntrypointVideoProc
VAProfileJPEGBaseline   :VAEntrypointVLD
VAProfileJPEGBaseline   :VAEntrypointEncPicture
VAProfileVP8Version0_3  :VAEntrypointVLD
VAProfileVP8Version0_3  :VAEntrypointEncSlice
VAProfileHEVCMain   :VAEntrypointVLD
VAProfileHEVCMain  

[Desktop-packages] [Bug 1757129] Re: gnome-control-center crashed with SIGSEGV in g_main_context_dispatch()

2018-03-20 Thread Apport retracing service
*** This bug is a duplicate of bug 1754924 ***
https://bugs.launchpad.net/bugs/1754924

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

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

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

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

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

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

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

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

** This bug has been marked a duplicate of bug 1754924
   gnome-control-center crashed with SIGSEGV in actualize_printers_list()

** Information type changed from Private to Public

** Tags removed: need-amd64-retrace

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

Title:
  gnome-control-center crashed with SIGSEGV in g_main_context_dispatch()

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

Bug description:
  Occurred shortly after update and restart.

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: gnome-control-center 1:3.28.0-0ubuntu2
  ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7
  Uname: Linux 4.15.0-12-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Mar 20 07:45:06 2018
  ExecutablePath: /usr/bin/gnome-control-center
  InstallationDate: Installed on 2018-03-17 (3 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180316)
  JournalErrors:
   -- Logs begin at Sat 2018-03-17 04:03:20 CDT, end at Tue 2018-03-20 07:50:56 
CDT. --
   Mar 20 07:30:58 hostname wpa_supplicant[966]: dbus: 
wpa_dbus_get_object_properties: failed to get object properties: (none) none
   Mar 20 07:30:58 hostname wpa_supplicant[966]: dbus: Failed to construct 
signal
   Mar 20 07:31:09 hostname pulseaudio[1422]: [pulseaudio] backend-ofono.c: 
Failed to register as a handsfree audio agent with ofono: 
org.freedesktop.DBus.Error.ServiceUnknown: The name org.ofono was not provided 
by any .service files
   Mar 20 07:31:13 hostname spice-vdagent[1552]: Cannot access vdagent virtio 
channel /dev/virtio-ports/com.redhat.spice.0
  ProcCmdline: gnome-control-center background
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SegvAnalysis:
   Segfault happened at: 0x5575de6eb641:mov0x90(%rbp),%rsi
   PC (0x5575de6eb641) ok
   source "0x90(%rbp)" (0x0090) not located in a known VMA region (needed 
readable region)!
   destination "%rsi" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: gnome-control-center
  StacktraceTop:
   ?? ()
   ?? ()
   ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
   g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
  Title: gnome-control-center crashed with SIGSEGV in g_main_context_dispatch()
  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-control-center/+bug/1757129/+subscriptions

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


[Desktop-packages] [Bug 1756380] Re: vaapi VP9 hardware decoding not working anymore in bionic

2018-03-20 Thread Julian Andres Klode
** Changed in: intel-vaapi-driver (Ubuntu)
   Status: Confirmed => Fix Committed

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

Title:
  vaapi VP9 hardware decoding not working anymore in bionic

Status in intel-vaapi-driver package in Ubuntu:
  Fix Committed
Status in libva package in Ubuntu:
  Invalid

Bug description:
  Hardware: Dell XPS13 9365, i7-7Y75
  System: Ubuntu Bionic Beaver (development branch)

  
  vainfo output on bionic is:

  libva info: VA-API version 1.1.0
  libva info: va_getDriverName() returns 0
  libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/i965_drv_video.so
  libva info: Found init function __vaDriverInit_1_0
  libva info: va_openDriver() returns 0
  vainfo: VA-API version: 1.1 (libva 2.1.0)
  vainfo: Driver version: Intel i965 driver for Intel(R) Kaby Lake - 2.0.0
  vainfo: Supported profile and entrypoints
VAProfileMPEG2Simple:   VAEntrypointVLD
VAProfileMPEG2Simple:   VAEntrypointEncSlice
VAProfileMPEG2Main  :   VAEntrypointVLD
VAProfileMPEG2Main  :   VAEntrypointEncSlice
VAProfileH264ConstrainedBaseline:   VAEntrypointVLD
VAProfileH264ConstrainedBaseline:   VAEntrypointEncSlice
VAProfileH264ConstrainedBaseline:   VAEntrypointEncSliceLP
VAProfileH264Main   :   VAEntrypointVLD
VAProfileH264Main   :   VAEntrypointEncSlice
VAProfileH264Main   :   VAEntrypointEncSliceLP
VAProfileH264High   :   VAEntrypointVLD
VAProfileH264High   :   VAEntrypointEncSlice
VAProfileH264High   :   VAEntrypointEncSliceLP
VAProfileH264MultiviewHigh  :   VAEntrypointVLD
VAProfileH264MultiviewHigh  :   VAEntrypointEncSlice
VAProfileH264StereoHigh :   VAEntrypointVLD
VAProfileH264StereoHigh :   VAEntrypointEncSlice
VAProfileVC1Simple  :   VAEntrypointVLD
VAProfileVC1Main:   VAEntrypointVLD
VAProfileVC1Advanced:   VAEntrypointVLD
VAProfileNone   :   VAEntrypointVideoProc
VAProfileJPEGBaseline   :   VAEntrypointVLD
VAProfileJPEGBaseline   :   VAEntrypointEncPicture
VAProfileVP8Version0_3  :   VAEntrypointVLD
VAProfileHEVCMain   :   VAEntrypointVLD
VAProfileHEVCMain   :   VAEntrypointEncSlice
VAProfileHEVCMain10 :   VAEntrypointVLD
VAProfileHEVCMain10 :   VAEntrypointEncSlice

  As you can see, VP9 entrypoints are missing.

  vainfo output on 17.10 was:

  libva info: VA-API version 0.40.0
  libva info: va_getDriverName() returns 0
  libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/i965_drv_video.so
  libva info: Found init function __vaDriverInit_0_40
  libva info: va_openDriver() returns 0
  vainfo: VA-API version: 0.40 (libva )
  vainfo: Driver version: Intel i965 driver for Intel(R) Kabylake - 1.8.3
  vainfo: Supported profile and entrypoints
VAProfileMPEG2Simple:VAEntrypointVLD
VAProfileMPEG2Simple:VAEntrypointEncSlice
VAProfileMPEG2Main  :VAEntrypointVLD
VAProfileMPEG2Main  :VAEntrypointEncSlice
VAProfileH264ConstrainedBaseline:VAEntrypointVLD
VAProfileH264ConstrainedBaseline:VAEntrypointEncSlice
VAProfileH264ConstrainedBaseline:VAEntrypointEncSliceLP
VAProfileH264Main   :VAEntrypointVLD
VAProfileH264Main   :VAEntrypointEncSlice
VAProfileH264Main   :VAEntrypointEncSliceLP
VAProfileH264High   :VAEntrypointVLD
VAProfileH264High   :VAEntrypointEncSlice
VAProfileH264High   :VAEntrypointEncSliceLP
VAProfileH264MultiviewHigh  :VAEntrypointVLD
VAProfileH264MultiviewHigh  :VAEntrypointEncSlice
VAProfileH264StereoHigh :VAEntrypointVLD
VAProfileH264StereoHigh :VAEntrypointEncSlice
VAProfileVC1Simple  :VAEntrypointVLD
VAProfileVC1Main:VAEntrypointVLD
VAProfileVC1Advanced:VAEntrypointVLD
VAProfileNone   :VAEntrypointVideoProc
VAProfileJPEGBaseline   :VAEntrypointVLD
VAProfileJPEGBaseline   :VAEntrypointEncPicture
VAProfileVP8Version0_3  :VAEntrypointVLD
VAProfileVP8Version0_3  :VAEntrypointEncSlice
VAProfileHEVCMain   :VAEntrypointVL

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

2018-03-20 Thread Apport retracing service
*** This bug is a duplicate of bug 1748450 ***
https://bugs.launchpad.net/bugs/1748450

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

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

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

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

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

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

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

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

** This bug has been marked a duplicate of bug 1748450
   gnome-shell crashed with SIGTRAP in _g_log_abort() from 
g_log_default_handler() from default_log_handler(message="Connection to 
xwayland lost") from g_logv() from g_log() from 

** Information type changed from Private to Public

** Tags removed: need-amd64-retrace

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

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

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  sorry it just give me message system problem

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.28.0-0ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7
  Uname: Linux 4.15.0-12-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CurrentDesktop: GNOME-Greeter:GNOME
  Date: Mon Mar 19 21:39:38 2018
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  GsettingsChanges:
   
  InstallationDate: Installed on 2018-03-19 (0 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180225)
  ProcCmdline: /usr/bin/gnome-shell
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_GB.UTF-8
   SHELL=/bin/false
  Signal: 5
  SourcePackage: gnome-shell
  StacktraceTop:
   ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_log_default_handler () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? ()
   g_logv () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_log () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
  Title: gnome-shell crashed with signal 5 in g_log_default_handler()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

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

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


[Desktop-packages] [Bug 1754803] Re: [FFe] Disable telepathy support in gnome-contacts

2018-03-20 Thread Launchpad Bug Tracker
This bug was fixed in the package gnome-contacts - 3.28.0-1ubuntu1

---
gnome-contacts (3.28.0-1ubuntu1) bionic; urgency=medium

  * Disable building telepathy support and drop related dependencies
(LP: #1754803)

 -- Tim Lunn   Tue, 20 Mar 2018 23:06:31 +1100

** Changed in: gnome-contacts (Ubuntu)
   Status: Confirmed => Fix Released

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

Title:
  [FFe] Disable telepathy support in gnome-contacts

Status in gnome-contacts package in Ubuntu:
  Fix Released

Bug description:
  We would like to disable (at buildtime) telepathy support in gnome-
  contacts

  
  Feature Freeze Justification
  
  Telepathy support is largely being deprecated in GNOME. Gnome-contacts is one 
of few GNOME modules still using it. It has been disabled in 
gnome-online-accounts (and will be completely removed from GOA next cycle[1]).

  With the GOA provider gone it is less useful since you won't get
  contacts from telepathy clients and you can't make calls. presumably
  the chat still works though if manually configured.

  Debian is considering disabling it this cycle.
  Upstream will consider it next cycle

  gnome-contacts is not seeded on any flavors, other than the vanilla-
  gnome-desktop.

  gnome-contacts is currently the only thing pulling in telepathy and
  all its deps when installing vanilla-gnome-desktop.

  
  [1] 
https://mail.gnome.org/archives/desktop-devel-list/2017-October/msg00040.html

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

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


[Desktop-packages] [Bug 1715582] Re: "Operation not supported by backend" when backing up to smb server

2018-03-20 Thread cement_head
Just upgraded to 17.10; can't use DejaDup to backup to network NAS
drive.  Got this error.  Is there a workaround, or do I have to wait for
the new 18.04 release?

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

Title:
  "Operation not supported by backend" when backing up to smb server

Status in Déjà Dup:
  Fix Released
Status in deja-dup package in Ubuntu:
  Fix Released

Bug description:
  OS: Ubuntu 17.10 beta
  setting up deja-dup to backup to smb/ssh server fails

  With ssh: Permission denied
  syslog:
  Sep  7 10:30:05 mbpr13b deja-dup[30252]: Allocating size to AssistantBackup 
0x55d581f75f50 without calling gtk_widget_get_preferred_width/height(). How 
does the code know the size to allocate?
  Sep  7 10:30:05 mbpr13b PackageKit: resolve transaction /149_caabebdc from 
uid 1000 finished with success after 414ms

  
  with smb: Backup failed
  InvalidBackendURL: missing // - relative paths not supported for scheme 
gio+invalid: gio+invalid://
  syslog:
  Sep  7 10:32:45 mbpr13b deja-dup[30252]: Allocating size to AssistantBackup 
0x55d581fecb70 without calling gtk_widget_get_preferred_width/height(). How 
does the code know the size to allocate?
  Sep  7 10:32:45 mbpr13b PackageKit: resolve transaction /150_abaacaad from 
uid 1000 finished with success after 402ms

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: deja-dup 35.6-0ubuntu1
  ProcVersionSignature: Ubuntu 4.12.0-13.14-generic 4.12.10
  Uname: Linux 4.12.0-13-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Sep  7 10:30:37 2017
  InstallationDate: Installed on 2017-09-05 (1 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170902)
  SourcePackage: deja-dup
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/deja-dup/+bug/1715582/+subscriptions

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


[Desktop-packages] [Bug 1721428] Re: Artful (17.10) Session logout after screen turned off

2018-03-20 Thread Matt Mahin
Seeing this issue on gnome shell after recent 17.10 upgrade from 16.04
LTS.  Anytime the screen turns off, my gnome session crashes.

// seems like everything up to date with these except for xorg
sudo apt-get update
sudo apt-get upgrade
sudo apt-get dist-upgrade

$ cat /proc/version
Linux version 4.13.0-37-generic (buildd@lcy01-amd64-026) (gcc version 7.2.0 
(Ubuntu 7.2.0-8ubuntu3.2)) #42-Ubuntu SMP Wed Mar 7 14:13:23 UTC 2018


[63316.108041] [drm] Reducing the compressed framebuffer size. This may lead to 
less power savings than a non-reduced-size. Try to increase stolen memory size 
if available in BIOS.
[81819.033174] [drm] Reducing the compressed framebuffer size. This may lead to 
less power savings than a non-reduced-size. Try to increase stolen memory size 
if available in BIOS.
[81828.179633] [drm:drm_scdc_set_high_tmds_clock_ratio [drm_kms_helper]] 
*ERROR* Failed to read tmds config, err=-6
[81828.179726] [drm:intel_hdmi_handle_sink_scrambling [i915]] *ERROR* Set TMDS 
ratio failed
[81828.208165] gnome-shell[2815]: segfault at 38 ip 7f039c0bac30 sp 
7ffcecb5f918 error 4 in libmutter-1.so.0.0.0[7f039c068000+141000]
[81828.318684] rfkill: input handler enabled
[81828.328347] [drm:drm_scdc_set_high_tmds_clock_ratio [drm_kms_helper]] 
*ERROR* Failed to read tmds config, err=-6
[81828.328387] [drm:intel_hdmi_handle_sink_scrambling [i915]] *ERROR* Set TMDS 
ratio failed
[81828.328392] [drm] Reducing the compressed framebuffer size. This may lead to 
less power savings than a non-reduced-size. Try to increase stolen memory size 
if available in BIOS.
[81828.382297] [drm:drm_scdc_set_high_tmds_clock_ratio [drm_kms_helper]] 
*ERROR* Failed to read tmds config, err=-6
[81828.382318] [drm:intel_hdmi_handle_sink_scrambling [i915]] *ERROR* Set TMDS 
ratio failed
[81831.917503] [drm:drm_add_edid_modes.part.27 [drm]] *ERROR* Unknown HDMI VIC: 0
[81831.984981] [drm] Reducing the compressed framebuffer size. This may lead to 
less power savings than a non-reduced-size. Try to increase stolen memory size 
if available in BIOS.
[81879.389515] [drm:drm_add_edid_modes.part.27 [drm]] *ERROR* Unknown HDMI VIC: 0
[81880.918441] rfkill: input handler disabled
--
[82380.490818] [drm:drm_scdc_set_high_tmds_clock_ratio [drm_kms_helper]] 
*ERROR* Failed to read tmds config, err=-6
[82380.490848] [drm:intel_hdmi_handle_sink_scrambling [i915]] *ERROR* Set TMDS 
ratio failed
[82380.522584] gnome-shell[26432]: segfault at 18 ip 7f433fedfd94 sp 
7fffac254b88 error 4 in libmutter-1.so.0.0.0[7f433fe41000+141000]
[82380.633077] rfkill: input handler enabled
[82384.241961] [drm:drm_add_edid_modes.part.27 [drm]] *ERROR* Unknown HDMI VIC: 0
[82384.319360] [drm] Reducing the compressed framebuffer size. This may lead to 
less power savings than a non-reduced-size. Try to increase stolen memory size 
if available in BIOS.
[82403.842828] [drm:drm_add_edid_modes.part.27 [drm]] *ERROR* Unknown HDMI VIC: 0
[82406.263963] rfkill: input handler disabled
--
[83520.980283] [drm:drm_scdc_set_high_tmds_clock_ratio [drm_kms_helper]] 
*ERROR* Failed to read tmds config, err=-6
[83520.980375] [drm:intel_hdmi_handle_sink_scrambling [i915]] *ERROR* Set TMDS 
ratio failed
[83521.030747] gnome-shell[28547]: segfault at 204 ip 0204 sp 
7fff0db270d8 error 14
[83521.142243] rfkill: input handler enabled
[83521.146802] [drm:drm_scdc_set_high_tmds_clock_ratio [drm_kms_helper]] 
*ERROR* Failed to read tmds config, err=-6
[83521.146837] [drm:intel_hdmi_handle_sink_scrambling [i915]] *ERROR* Set TMDS 
ratio failed
[83521.146842] [drm] Reducing the compressed framebuffer size. This may lead to 
less power savings than a non-reduced-size. Try to increase stolen memory size 
if available in BIOS.
[83521.200710] [drm:drm_scdc_set_high_tmds_clock_ratio [drm_kms_helper]] 
*ERROR* Failed to read tmds config, err=-6
[83521.200729] [drm:intel_hdmi_handle_sink_scrambling [i915]] *ERROR* Set TMDS 
ratio failed
[83524.729044] [drm:drm_add_edid_modes.part.27 [drm]] *ERROR* Unknown HDMI VIC: 0
[83524.791074] [drm] Reducing the compressed framebuffer size. This may lead to 
less power savings than a non-reduced-size. Try to increase stolen memory size 
if available in BIOS.
[83537.884721] [drm:drm_add_edid_modes.part.27 [drm]] *ERROR* Unknown HDMI VIC: 0
[83539.367993] rfkill: input handler disabled
[83545.807155] sd 2:0:0:0: [sda] tag#0 FAILED Result: hostbyte=DID_OK 
driverbyte=DRIVER_SENSE
[83545.807160] sd 2:0:0:0: [sda] tag#0 Sense Key : Not Ready [current] 
[83545.807164] sd 2:0:0:0: [sda] tag#0 Add. Sense: Medium not present
[83545.807169] sd 2:0:0:0: [sda] tag#0 CDB: Read(10) 28 00 00 00 20 00 00 00 01 
00
[83545.807171] print_req_error: I/O error, dev sda, sector 8192
[83545.807191] FAT-fs (sda1): unable to read boot sector

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

Title:
  Artful (17.10) Session 

[Desktop-packages] [Bug 1754296] Re: [bionic] startx / xinit crashes with GLX backtrace if Composite Disabled in xorg.conf (intel mesa driver)

2018-03-20 Thread Christian Niemeyer
** Summary changed:

- [bionic] startx / xinit crashes with GLX backtrace if Composite Disabled in 
xorg.conf
+ [bionic] startx / xinit crashes with GLX backtrace if Composite Disabled in 
xorg.conf (intel mesa driver)

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

Title:
  [bionic] startx / xinit crashes with GLX backtrace if Composite
  Disabled in xorg.conf (intel mesa driver)

Status in xorg package in Ubuntu:
  New

Bug description:
  [New bug filed with ubuntu-bug/apport. However there was nothing to
  file against in /var/crashes]

  For certain games I disable the Composite extension in my
  /etc/X11/xorg.conf when using a non-composited window manager like
  openbox, fluxbox or marco. Disabling the Composite extension prevents
  tearing in (some) games and sometimes is an additional performance
  boost.

  This worked flawlessly in all previous Ubuntu versions including 17.10
  (artful).

  This stopped working with Ubuntu 18.04 (bionic). I tested with the
  mainline kernel 4.16 and the current 4.15 kernel in bionic-proposed
  and bionic. Xserver will crash with "Option "Composite"
  "0/False/Disable"

  When I comment out the specific line in the Extensions section (that
  means *enabling* Composite) it works again with this xorg.conf. I can
  also do other stuff like disabling DRI3 or AIGLX. No crashes in these
  cases.

  My xorg.conf:
  Section "Device"
  Identifier "Intel GMA45" ##just a trivial name as Identifier
  Driver "intel"
  EndSection

  Section "Extensions"
  Option "Composite" "0"
  EndSection

  It has a backtrace and caughts signal 6.

  My Xorg.0.log:
  [ 35.779]
  X.Org X Server 1.19.6
  Release Date: 2017-12-20
  [ 35.781] X Protocol Version 11, Revision 0
  [ 35.782] Build Operating System: Linux 4.4.0-101-generic x86_64 Ubuntu
  [ 35.783] Current Operating System: Linux bdcomputerclub 4.16.0-994-generic 
#201803022100 SMP Sat Mar 3 02:03:37 UTC 2018 x86_64
  [ 35.784] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-4.16.0-994-generic 
root=UUID=cb2eb60a-9760-4805-95eb-0db77947ac82 ro quiet splash
  [ 35.787] Build Date: 22 February 2018 08:04:42PM
  [ 35.788] xorg-server 2:1.19.6-1ubuntu2 (For technical support please see 
http://www.ubuntu.com/support)
  [ 35.789] Current version of pixman: 0.34.0
  [ 35.792] Before reporting problems, check http://wiki.x.org
   to make sure that you have the latest version.
  [ 35.792] Markers: (--) probed, (**) from config file, (==) default setting,
   (++) from command line, (!!) notice, (II) informational,
   (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
  [ 35.799] (==) Log file: "/home/christian/.local/share/xorg/Xorg.0.log", 
Time: Wed Mar 7 22:43:35 2018
  [ 35.801] (==) Using config file: "/etc/X11/xorg.conf"
  [ 35.803] (==) Using system config directory "/usr/share/X11/xorg.conf.d"
  [ 35.803] (==) No Layout section. Using the first Screen section.
  [ 35.803] (==) No screen section available. Using defaults.
  [ 35.803] (**) |-->Screen "Default Screen Section" (0)
  [ 35.803] (**) | |-->Monitor ""
  [ 35.804] (==) No device specified for screen "Default Screen Section".
   Using the first device section listed.
  [ 35.804] (**) | |-->Device "Intel GMA45 Express Chipset"
  [ 35.804] (==) No monitor specified for screen "Default Screen Section".
   Using a default monitor configuration.
  [ 35.804] (==) Automatically adding devices
  [ 35.804] (==) Automatically enabling devices
  [ 35.804] (==) Automatically adding GPU devices
  [ 35.804] (==) Automatically binding GPU devices
  [ 35.804] (==) Max clients allowed: 256, resource mask: 0x1f
  [ 35.809] (WW) The directory "/usr/share/fonts/X11/cyrillic" does not exist.
  [ 35.809] Entry deleted from font path.
  [ 35.822] (==) FontPath set to:
   /usr/share/fonts/X11/misc,
   /usr/share/fonts/X11/100dpi/:unscaled,
   /usr/share/fonts/X11/75dpi/:unscaled,
   /usr/share/fonts/X11/Type1,
   /usr/share/fonts/X11/100dpi,
   /usr/share/fonts/X11/75dpi,
   built-ins
  [ 35.822] (==) ModulePath set to "/usr/lib/xorg/modules"
  [ 35.822] (**) Extension "Composite" is disabled
  [ 35.822] (II) The server relies on udev to provide the list of input devices.
   If no devices become available, reconfigure udev or disable AutoAddDevices.
  [ 35.822] (II) Loader magic: 0x55cfd2964020
  [ 35.822] (II) Module ABI versions:
  [ 35.822] X.Org ANSI C Emulation: 0.4
  [ 35.822] X.Org Video Driver: 23.0
  [ 35.822] X.Org XInput driver : 24.1
  [ 35.822] X.Org Server Extension : 10.0
  [ 35.824] (++) using VT number 1

  [ 35.827] (II) systemd-logind: took control of session 
/org/freedesktop/login1/session/_32
  [ 35.828] (II) xfree86: Adding drm device (/dev/dri/card0)
  [ 35.829] (II) systemd-logind: got fd for /dev/dri/card0 226:0 fd 11 paused 0
  [ 35.832] (--) PCI:*(0:0:2:0) 8086:2a42:1025:0459 rev 9, Mem @ 
0xd000/4194304, 0xc000/268435456, I/O @ 0x50

Re: [Desktop-packages] [Bug 1074617] Re: liferea crashes when I add a new subscription

2018-03-20 Thread Paul Gevers
@Bèr,

On 20-03-18 13:59, Bèr Kessels (berkes) wrote:
> Happens also when running `liferea-add-feed` which is a wrapper around
> `liferea --add-feed`. The latter also causes a crash.

Which version of liferea are you using? (Or, on which version of Ubuntu
are you running?)

> Attached is a strace log, created by running `strace -o liferea-
> crash.log /usr/bin/liferea --add-feed
> http://feeds.bbci.co.uk/news/rss.xml`.
> 
> ** Attachment added: "Attached is a strace log, created by running `strace -o 
> liferea-crash.log /usr/bin/liferea --add-feed 
> http://feeds.bbci.co.uk/news/rss.xml`.";
>
> https://bugs.launchpad.net/ubuntu/+source/liferea/+bug/1074617/+attachment/5084904/+files/liferea-crash.log

This exact same command doesn't crash for me (on Debian buster in KDE).
The issue may be resolved in the mean time, or we need to figure out
what really triggers the issue.

Paul

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

Title:
  liferea crashes when I add a new subscription

Status in liferea package in Ubuntu:
  Confirmed

Bug description:
  When I try to add a subscription using the button Liferea you close
  without completing the operation

  ProblemType: Bug
  DistroRelease: Ubuntu 12.10
  Package: liferea 1.8.3-0.1ubuntu2 [modified: usr/bin/liferea]
  Uname: Linux 3.6.5-030605-generic i686
  ApportVersion: 2.6.1-0ubuntu6
  Architecture: i386
  Date: Sat Nov  3 12:27:11 2012
  InstallationDate: Installed on 2012-09-05 (58 days ago)
  InstallationMedia: Lubuntu 12.04 "Precise Pangolin" - Release i386 (20120423)
  MarkForUpload: True
  SourcePackage: liferea
  UpgradeStatus: Upgraded to quantal on 2012-10-18 (15 days ago)

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

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


[Desktop-packages] [Bug 1757154] [NEW] can't start lightdm.service unit

2018-03-20 Thread JoK
Public bug reported:

On today Ubuntu 18.04 daylibuild
i can launch it without error with lightdm –-test-mode --debug
but i can't start systemd unit
error : lightdm.service: Start request repeated too quickly

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

** Attachment added: "journalctl logs"
   
https://bugs.launchpad.net/bugs/1757154/+attachment/5084939/+files/journalctl.lightdm

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

Title:
  can't start lightdm.service unit

Status in lightdm package in Ubuntu:
  New

Bug description:
  On today Ubuntu 18.04 daylibuild
  i can launch it without error with lightdm –-test-mode --debug
  but i can't start systemd unit
  error : lightdm.service: Start request repeated too quickly

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

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


[Desktop-packages] [Bug 1756380] Re: vaapi VP9 hardware decoding not working anymore in bionic

2018-03-20 Thread Launchpad Bug Tracker
This bug was fixed in the package intel-vaapi-driver - 2.1.0-0ubuntu1

---
intel-vaapi-driver (2.1.0-0ubuntu1) bionic; urgency=medium

  * New upstream release. (LP: #1729467)
- support Cannonlake
  * Un-split the package, restore support for shaders. (LP: #1756380)
  * control: Update maintainer, add new platforms to description.

 -- Timo Aaltonen   Tue, 20 Mar 2018 14:28:10 +0200

** Changed in: intel-vaapi-driver (Ubuntu)
   Status: Fix Committed => Fix Released

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

Title:
  vaapi VP9 hardware decoding not working anymore in bionic

Status in intel-vaapi-driver package in Ubuntu:
  Fix Released
Status in libva package in Ubuntu:
  Invalid

Bug description:
  Hardware: Dell XPS13 9365, i7-7Y75
  System: Ubuntu Bionic Beaver (development branch)

  
  vainfo output on bionic is:

  libva info: VA-API version 1.1.0
  libva info: va_getDriverName() returns 0
  libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/i965_drv_video.so
  libva info: Found init function __vaDriverInit_1_0
  libva info: va_openDriver() returns 0
  vainfo: VA-API version: 1.1 (libva 2.1.0)
  vainfo: Driver version: Intel i965 driver for Intel(R) Kaby Lake - 2.0.0
  vainfo: Supported profile and entrypoints
VAProfileMPEG2Simple:   VAEntrypointVLD
VAProfileMPEG2Simple:   VAEntrypointEncSlice
VAProfileMPEG2Main  :   VAEntrypointVLD
VAProfileMPEG2Main  :   VAEntrypointEncSlice
VAProfileH264ConstrainedBaseline:   VAEntrypointVLD
VAProfileH264ConstrainedBaseline:   VAEntrypointEncSlice
VAProfileH264ConstrainedBaseline:   VAEntrypointEncSliceLP
VAProfileH264Main   :   VAEntrypointVLD
VAProfileH264Main   :   VAEntrypointEncSlice
VAProfileH264Main   :   VAEntrypointEncSliceLP
VAProfileH264High   :   VAEntrypointVLD
VAProfileH264High   :   VAEntrypointEncSlice
VAProfileH264High   :   VAEntrypointEncSliceLP
VAProfileH264MultiviewHigh  :   VAEntrypointVLD
VAProfileH264MultiviewHigh  :   VAEntrypointEncSlice
VAProfileH264StereoHigh :   VAEntrypointVLD
VAProfileH264StereoHigh :   VAEntrypointEncSlice
VAProfileVC1Simple  :   VAEntrypointVLD
VAProfileVC1Main:   VAEntrypointVLD
VAProfileVC1Advanced:   VAEntrypointVLD
VAProfileNone   :   VAEntrypointVideoProc
VAProfileJPEGBaseline   :   VAEntrypointVLD
VAProfileJPEGBaseline   :   VAEntrypointEncPicture
VAProfileVP8Version0_3  :   VAEntrypointVLD
VAProfileHEVCMain   :   VAEntrypointVLD
VAProfileHEVCMain   :   VAEntrypointEncSlice
VAProfileHEVCMain10 :   VAEntrypointVLD
VAProfileHEVCMain10 :   VAEntrypointEncSlice

  As you can see, VP9 entrypoints are missing.

  vainfo output on 17.10 was:

  libva info: VA-API version 0.40.0
  libva info: va_getDriverName() returns 0
  libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/i965_drv_video.so
  libva info: Found init function __vaDriverInit_0_40
  libva info: va_openDriver() returns 0
  vainfo: VA-API version: 0.40 (libva )
  vainfo: Driver version: Intel i965 driver for Intel(R) Kabylake - 1.8.3
  vainfo: Supported profile and entrypoints
VAProfileMPEG2Simple:VAEntrypointVLD
VAProfileMPEG2Simple:VAEntrypointEncSlice
VAProfileMPEG2Main  :VAEntrypointVLD
VAProfileMPEG2Main  :VAEntrypointEncSlice
VAProfileH264ConstrainedBaseline:VAEntrypointVLD
VAProfileH264ConstrainedBaseline:VAEntrypointEncSlice
VAProfileH264ConstrainedBaseline:VAEntrypointEncSliceLP
VAProfileH264Main   :VAEntrypointVLD
VAProfileH264Main   :VAEntrypointEncSlice
VAProfileH264Main   :VAEntrypointEncSliceLP
VAProfileH264High   :VAEntrypointVLD
VAProfileH264High   :VAEntrypointEncSlice
VAProfileH264High   :VAEntrypointEncSliceLP
VAProfileH264MultiviewHigh  :VAEntrypointVLD
VAProfileH264MultiviewHigh  :VAEntrypointEncSlice
VAProfileH264StereoHigh :VAEntrypointVLD
VAProfileH264StereoHigh :VAEntrypointEncSlice
VAProfileVC1Simple  :VAEntrypointVLD
VAProfileVC1Main:VAEntrypointVLD
VAProfileVC1Advanced  

[Desktop-packages] [Bug 1757154] Re: can't start lightdm.service unit

2018-03-20 Thread JoK
** Attachment added: "test-mode with debug"
   
https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1757154/+attachment/5084940/+files/lightdm.test-mode.debug

** Description changed:

+ On today Ubuntu 18.04 daylibuild
  i can launch it without error with lightdm –-test-mode --debug
  but i can't start systemd unit
  error : lightdm.service: Start request repeated too quickly

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

Title:
  can't start lightdm.service unit

Status in lightdm package in Ubuntu:
  New

Bug description:
  On today Ubuntu 18.04 daylibuild
  i can launch it without error with lightdm –-test-mode --debug
  but i can't start systemd unit
  error : lightdm.service: Start request repeated too quickly

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

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


[Desktop-packages] [Bug 1721428] Re: Artful (17.10) Session logout after screen turned off

2018-03-20 Thread Matt Mahin
Issue is mitigated by enabling Automatic screen lock when screen turns
off.

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

Title:
  Artful (17.10) Session logout after screen turned off

Status in GNOME Shell:
  Unknown
Status in gnome-shell package in Ubuntu:
  Invalid
Status in mutter package in Ubuntu:
  Invalid

Bug description:
  Whenever I turn off my screen, the computer (a desktop PC) logs me out
  of my session.

  Here is a discussion thread with users of similar issue:
  
https://ubuntuforums.org/showthread.php?t=2372388&p=13694312&posted=1#post13694312

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

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


[Desktop-packages] [Bug 1756389] Re: Delay startup of evolution-calendar-factory

2018-03-20 Thread Jeremy Bicha
Could you please propose this upstream (with a patch if you can) ?

https://bugzilla.gnome.org/enter_bug.cgi?product=evolution-data-server

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

Title:
  Delay startup of evolution-calendar-factory

Status in evolution-data-server package in Ubuntu:
  New

Bug description:
  On a default Bionic Desktop installation, evolution-calendar-factory starts 
early and slows down session startup. In the bootchart attached, it overlaps 
with gnome-shell startup which is also resource intensive.
  With evolution-calendar-factory delayed gnome-shell starts 2 seconds faster.

  evolution-calendar-factory startup should be delayed if it cannot be
  disabled completely.

  The following changes to evolution-calendar-factory.service do this:
  """ 
  [Unit]
  Description=Evolution calendar service

  [Service]
  Type=dbus
  BusName=org.gnome.evolution.dataserver.Calendar7
  ExecStartPre=/bin/sleep 60
  ExecStart=/usr/lib/evolution/evolution-calendar-factory
  """

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: evolution-data-server 3.28.0-1ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Mar 16 17:52:45 2018
  InstallationDate: Installed on 2013-09-03 (1654 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130902)
  ProcEnviron:
   TERM=screen-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  SourcePackage: evolution-data-server
  UpgradeStatus: Upgraded to bionic on 2018-01-26 (49 days ago)

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

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


[Desktop-packages] [Bug 1721428] Re: Artful (17.10) Session logout after screen turned off

2018-03-20 Thread Matt Mahin
Seeing this issue on gnome shell after recent 17.10 upgrade from 16.04
LTS.  Anytime the screen turns off, my gnome session crashes.

// seems like everything up to date with these except for xorg
sudo apt-get update
sudo apt-get upgrade
sudo apt-get dist-upgrade

$ cat /proc/version
Linux version 4.13.0-37-generic (buildd@lcy01-amd64-026) (gcc version 7.2.0 
(Ubuntu 7.2.0-8ubuntu3.2)) #42-Ubuntu SMP Wed Mar 7 14:13:23 UTC 2018


[63316.108041] [drm] Reducing the compressed framebuffer size. This may lead to 
less power savings than a non-reduced-size. Try to increase stolen memory size 
if available in BIOS.
[81819.033174] [drm] Reducing the compressed framebuffer size. This may lead to 
less power savings than a non-reduced-size. Try to increase stolen memory size 
if available in BIOS.
[81828.179633] [drm:drm_scdc_set_high_tmds_clock_ratio [drm_kms_helper]] 
*ERROR* Failed to read tmds config, err=-6
[81828.179726] [drm:intel_hdmi_handle_sink_scrambling [i915]] *ERROR* Set TMDS 
ratio failed
[81828.208165] gnome-shell[2815]: segfault at 38 ip 7f039c0bac30 sp 
7ffcecb5f918 error 4 in libmutter-1.so.0.0.0[7f039c068000+141000]
[81828.318684] rfkill: input handler enabled
[81828.328347] [drm:drm_scdc_set_high_tmds_clock_ratio [drm_kms_helper]] 
*ERROR* Failed to read tmds config, err=-6
[81828.328387] [drm:intel_hdmi_handle_sink_scrambling [i915]] *ERROR* Set TMDS 
ratio failed
[81828.328392] [drm] Reducing the compressed framebuffer size. This may lead to 
less power savings than a non-reduced-size. Try to increase stolen memory size 
if available in BIOS.
[81828.382297] [drm:drm_scdc_set_high_tmds_clock_ratio [drm_kms_helper]] 
*ERROR* Failed to read tmds config, err=-6
[81828.382318] [drm:intel_hdmi_handle_sink_scrambling [i915]] *ERROR* Set TMDS 
ratio failed
[81831.917503] [drm:drm_add_edid_modes.part.27 [drm]] *ERROR* Unknown HDMI VIC: 0
[81831.984981] [drm] Reducing the compressed framebuffer size. This may lead to 
less power savings than a non-reduced-size. Try to increase stolen memory size 
if available in BIOS.
[81879.389515] [drm:drm_add_edid_modes.part.27 [drm]] *ERROR* Unknown HDMI VIC: 0
[81880.918441] rfkill: input handler disabled
--
[82380.490818] [drm:drm_scdc_set_high_tmds_clock_ratio [drm_kms_helper]] 
*ERROR* Failed to read tmds config, err=-6
[82380.490848] [drm:intel_hdmi_handle_sink_scrambling [i915]] *ERROR* Set TMDS 
ratio failed
[82380.522584] gnome-shell[26432]: segfault at 18 ip 7f433fedfd94 sp 
7fffac254b88 error 4 in libmutter-1.so.0.0.0[7f433fe41000+141000]
[82380.633077] rfkill: input handler enabled
[82384.241961] [drm:drm_add_edid_modes.part.27 [drm]] *ERROR* Unknown HDMI VIC: 0
[82384.319360] [drm] Reducing the compressed framebuffer size. This may lead to 
less power savings than a non-reduced-size. Try to increase stolen memory size 
if available in BIOS.
[82403.842828] [drm:drm_add_edid_modes.part.27 [drm]] *ERROR* Unknown HDMI VIC: 0
[82406.263963] rfkill: input handler disabled
--
[83520.980283] [drm:drm_scdc_set_high_tmds_clock_ratio [drm_kms_helper]] 
*ERROR* Failed to read tmds config, err=-6
[83520.980375] [drm:intel_hdmi_handle_sink_scrambling [i915]] *ERROR* Set TMDS 
ratio failed
[83521.030747] gnome-shell[28547]: segfault at 204 ip 0204 sp 
7fff0db270d8 error 14
[83521.142243] rfkill: input handler enabled
[83521.146802] [drm:drm_scdc_set_high_tmds_clock_ratio [drm_kms_helper]] 
*ERROR* Failed to read tmds config, err=-6
[83521.146837] [drm:intel_hdmi_handle_sink_scrambling [i915]] *ERROR* Set TMDS 
ratio failed
[83521.146842] [drm] Reducing the compressed framebuffer size. This may lead to 
less power savings than a non-reduced-size. Try to increase stolen memory size 
if available in BIOS.
[83521.200710] [drm:drm_scdc_set_high_tmds_clock_ratio [drm_kms_helper]] 
*ERROR* Failed to read tmds config, err=-6
[83521.200729] [drm:intel_hdmi_handle_sink_scrambling [i915]] *ERROR* Set TMDS 
ratio failed
[83524.729044] [drm:drm_add_edid_modes.part.27 [drm]] *ERROR* Unknown HDMI VIC: 0
[83524.791074] [drm] Reducing the compressed framebuffer size. This may lead to 
less power savings than a non-reduced-size. Try to increase stolen memory size 
if available in BIOS.
[83537.884721] [drm:drm_add_edid_modes.part.27 [drm]] *ERROR* Unknown HDMI VIC: 0
[83539.367993] rfkill: input handler disabled
[83545.807155] sd 2:0:0:0: [sda] tag#0 FAILED Result: hostbyte=DID_OK 
driverbyte=DRIVER_SENSE
[83545.807160] sd 2:0:0:0: [sda] tag#0 Sense Key : Not Ready [current] 
[83545.807164] sd 2:0:0:0: [sda] tag#0 Add. Sense: Medium not present
[83545.807169] sd 2:0:0:0: [sda] tag#0 CDB: Read(10) 28 00 00 00 20 00 00 00 01 
00
[83545.807171] print_req_error: I/O error, dev sda, sector 8192
[83545.807191] FAT-fs (sda1): unable to read boot sector

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

Title:
  Artful (17.10) Session 

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

2018-03-20 Thread Apport retracing service
*** This bug is a duplicate of bug 1748450 ***
https://bugs.launchpad.net/bugs/1748450

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

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

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

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

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

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

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

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

** This bug has been marked a duplicate of bug 1748450
   gnome-shell crashed with SIGTRAP in _g_log_abort() from 
g_log_default_handler() from default_log_handler(message="Connection to 
xwayland lost") from g_logv() from g_log() from 

** Information type changed from Private to Public

** Tags removed: need-amd64-retrace

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

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

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  Happens on boot up. Also, System still hangs when HDMI is plugged in.
  If I remove the HDMI on reboot and only plug it back in after login is
  initiated then it continues to boot. Otherwise I need to reboot again
  with the HDMI unplugged. A new occurrence is the fact that I now get
  Dummy Audio Output along with Surround 5.1, 7.1, HDMI and Speakers. I
  must reboot, turn off the monitor and then pull the HDMI cable and
  replug in. I have swapped HDMI cables to no avail. Just FYI. Before
  the last 3 updates all of these things worked fine. Thanks!

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.28.0-0ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7
  Uname: Linux 4.15.0-12-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: GNOME-Greeter:GNOME
  Date: Tue Mar 20 10:21:05 2018
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  GsettingsChanges:
   
  InstallationDate: Installed on 2017-06-27 (265 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  ProcCmdline: /usr/bin/gnome-shell
  ProcEnviron:
   LANGUAGE=en_CA:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_CA.UTF-8
   SHELL=/bin/false
  Signal: 5
  SourcePackage: gnome-shell
  StacktraceTop:
   ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_log_default_handler () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? ()
   g_logv () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_log () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
  Title: gnome-shell crashed with signal 5 in g_log_default_handler()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

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

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


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

2018-03-20 Thread dwmw2
This is CVE-2018-1000135. For some reason the 'Link to CVE' option above
doesn't seem to work.

https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-1000135


** CVE added: https://cve.mitre.org/cgi-
bin/cvename.cgi?name=2018-1000135

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

Title:
  Full-tunnel VPN DNS leakage regression

Status in network-manager package in Ubuntu:
  Confirmed

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

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

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

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

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

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


[Desktop-packages] [Bug 1757160] Re: gnome-shell crashed with signal 5

2018-03-20 Thread Apport retracing service
*** This bug is a duplicate of bug 1748450 ***
https://bugs.launchpad.net/bugs/1748450

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

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

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

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

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

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

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

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

** This bug has been marked a duplicate of bug 1748450
   gnome-shell crashed with SIGTRAP in _g_log_abort() from 
g_log_default_handler() from default_log_handler(message="Connection to 
xwayland lost") from g_logv() from g_log() from 

** Information type changed from Private to Public

** Tags removed: need-amd64-retrace

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

Title:
  gnome-shell crashed with signal 5

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  bug

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.28.0-0ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7
  Uname: Linux 4.15.0-12-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CurrentDesktop: GNOME-Greeter:GNOME
  Date: Tue Mar 20 19:55:06 2018
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  GsettingsChanges:
   
  InstallationDate: Installed on 2016-01-08 (802 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  ProcCmdline: /usr/bin/gnome-shell
  Signal: 5
  SourcePackage: gnome-shell
  StacktraceTop:
   () at /usr/lib/x86_64-linux-gnu/libmutter-2.so.0
   _XIOError () at /usr/lib/x86_64-linux-gnu/libX11.so.6
   _XEventsQueued () at /usr/lib/x86_64-linux-gnu/libX11.so.6
   XPending () at /usr/lib/x86_64-linux-gnu/libX11.so.6
   () at /usr/lib/x86_64-linux-gnu/libgdk-3.so.0
  Title: gnome-shell crashed with signal 5
  UpgradeStatus: Upgraded to bionic on 2018-01-24 (54 days ago)
  UserGroups:

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

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


[Desktop-packages] [Bug 1756160] Re: cupsd crashed with SIGSEGV in mime_compare_srcs()

2018-03-20 Thread Till Kamppeter
Ralph Gauges, can you please attach all files which you have in
/etc/cups/ppd/? Please attach the files one by one, do not compress them
and do not package them together.

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

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

Title:
  cupsd crashed with SIGSEGV in mime_compare_srcs()

Status in CUPS:
  Unknown
Status in cups package in Ubuntu:
  Incomplete

Bug description:
  No clue. This came up after the update this afternoon.

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: cups-daemon 2.2.6-5
  ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7
  Uname: Linux 4.15.0-10-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CupsErrorLog:
   
  Date: Wed Mar  7 16:41:29 2018
  ExecutablePath: /usr/sbin/cupsd
  ExecutableTimestamp: 1518257679
  InstallationDate: Installed on 2018-03-05 (10 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  Lpstat: device for LBP252: smb://izcpm3/Canon-P-64
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 0c45:6713 Microdia 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. XPS 15 9560
  Papersize: a4
  PpdFiles: LBP252: Canon LBP252 PPD PS
  ProcAttrCurrent: /usr/sbin/cupsd (enforce)
  ProcCmdline: /usr/sbin/cupsd -l
  ProcCwd: /
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-12-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro acpi_rev_override=1 enable_fbc=1 
enable_psr=1 disable_power_well=0 pci=nommconf
  SegvAnalysis:
   Segfault happened at: 0x7fb76b986e8e <__strcmp_sse2_unaligned+30>:   movdqu 
(%rsi),%xmm0
   PC (0x7fb76b986e8e) ok
   source "(%rsi)" (0x353250424c4e4334) not located in a known VMA region 
(needed readable region)!
   destination "%xmm0" ok
   Stack memory exhausted (SP below stack segment)
  SegvReason: reading unknown VMA
  Signal: 11
  SourcePackage: cups
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/libcupsmime.so.1
   ?? () from /usr/lib/x86_64-linux-gnu/libcups.so.2
   mimeFilter2 () from /usr/lib/x86_64-linux-gnu/libcupsmime.so.1
   ?? ()
   ?? ()
  Title: cupsd crashed with SIGSEGV in mimeFilter2()
  UpgradeStatus: Upgraded to bionic on 2018-03-05 (10 days ago)
  UserGroups:
   
  dmi.bios.date: 11/12/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.6.2
  dmi.board.name: 05FFDN
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.6.2:bd11/12/2017:svnDellInc.:pnXPS159560:pvr:rvnDellInc.:rn05FFDN:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 15 9560
  dmi.sys.vendor: Dell Inc.

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

-- 
Mailing list: https://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   >