date:20171105

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

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

Title:
  VA-API fails to initialize in a Gnome Shell Wayland session

Status in Libva:
  New
Status in Mutter:
  Confirmed
Status in Totem:
  Confirmed
Status in VLC media player:
  New
Status in chromium-browser package in Ubuntu:
  Confirmed
Status in gst-plugins-bad1.0 package in Ubuntu:
  Fix Released
Status in gstreamer-vaapi package in Ubuntu:
  Won't Fix
Status in libva package in Ubuntu:
  Triaged
Status in mpv package in Ubuntu:
  Fix Released
Status in mutter package in Ubuntu:
  Triaged
Status in vlc package in Ubuntu:
  New

Bug description:
  The Intel i965 VA-API driver works well in Xorg sessions (Unity7 and
  Gnome Shell). But it refuses to load when in a Wayland session:

  $ totem bbb_sunflower_1080p_60fps_normal.mp4
  libva error: va_getDriverName() failed with unknown libva 
error,driver_name=(null)

  $ env LIBVA_DRIVER_NAME=i965 totem bbb_sunflower_1080p_60fps_normal.mp4
  totem: intel_driver.c:112: intel_driver_init: Assertion 
`VA_CHECK_DRM_AUTH_TYPE(ctx, VA_DRM_AUTH_DRI1) || VA_CHECK_DRM_AUTH_TYPE(ctx, 
VA_DRM_AUTH_DRI2) || VA_CHECK_DRM_AUTH_TYPE(ctx, VA_DRM_AUTH_CUSTOM)' failed.
  Aborted (core dumped)

  $ gst-play-1.0 bbb_sunflower_1080p_60fps_normal.mp4
  Press 'k' to see a list of keyboard shortcuts.
  Now playing /home/dan/Videos/bbb_sunflower_1080p_60fps_normal.mp4
  Redistribute latency...
  Redistribute latency...
  ERROR Internal error: could not render surface for 
file:///home/dan/Videos/bbb_sunflower_1080p_60fps_normal.mp4
  ERROR debug information: ../../../gst/vaapi/gstvaapisink.c(1482): 
gst_vaapisink_show_frame_unlocked (): 
/GstPlayBin:playbin/GstPlaySink:playsink/GstBin:vbin/GstVaapiSink:vaapisink0

  WORKAROUNDS:

   * Use weston instead of gnome-shell; or
   * $ env -uDISPLAY totem ... # but creates corruption -> bug 1701463
   * $ env GST_GL_WINDOW=wayland totem ... # but creates corruption -> bug 
1701463
   * $ env GST_GL_WINDOW=wayland gst-play-1.0 --videosink glimagesink ...
   * $ env -uDISPLAY mpv --hwdec --opengl-backend=wayland ...

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: i965-va-driver 1.8.1-1
  ProcVersionSignature: Ubuntu 4.10.0-22.24-generic 4.10.15
  Uname: Linux 4.10.0-22-generic x86_64
  ApportVersion: 2.20.5-0ubuntu4
  Architecture: amd64
  Date: Fri Jun 16 13:40:38 2017
  InstallationDate: Installed on 2017-05-03 (44 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170502)
  SourcePackage: intel-vaapi-driver
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

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

2017-11-05 Thread PeterPall

My hope was that all the bug fixes you have collected make it to the
official .Deb package for Ubuntu and Debian instead.

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

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

Status in sane-backends package in Ubuntu:
  Confirmed

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

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

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

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

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

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

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

2017-11-05 Thread staedtler-przyborski

'I have written to Brother support'

Nothing will happen. As only Ubuntu 17.10 is affected, no other Ubuntu-
Release, no other Linux-Distribution (e.g. Arch-Linux uses libsane
1.0.27 and no extra pecularities are reported) .

Hopefully Ubuntu switches at least for 18.04 LTS back to use non-
experimental libraries and frameworks.

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

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

Status in sane-backends package in Ubuntu:
  Confirmed

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

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

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

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

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

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

[Desktop-packages] [Bug 1689356] Re: UI scale being reset to 1 everytime when display sleeps for a while

2017-11-05 Thread Mattias Sandstrom

Also it is pretty annoying to restart all automatically started
application (for example Slack, shutter and owncloud) that doesn't
pickup the correct setting and the window layout is messed up.

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

Title:
  UI scale being reset to 1 everytime when display sleeps for a while

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

Bug description:
  After upgrading to Ubuntu 17.04,
  the HiDPI setting(Scale for menu and title bars)
  is being reset to 1 everytime when display sleeps for a while,
  making everything looks small.

  If the display sleeps and I resume it instantly, it's fine,
  but if the display slept for long, the HiDPI setting gets reset to 1.

  My guess is that if a display is plugged in(detected), the old DPI
  setting is not restored.

  This issue is not present on previous Ubuntu versions
  and the same issue persists even after a fresh install.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: xorg 1:7.7+16ubuntu3
  Uname: Linux 4.10.14-zen+ x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  375.66  Mon May  1 15:29:16 
PDT 2017
   GCC version:  gcc version 6.3.0 20170406 (Ubuntu 6.3.0-12ubuntu2)
  .proc.driver.nvidia.warnings.fbdev:
   Your system is not currently configured to drive a VGA console
   on the primary VGA device. The NVIDIA Linux graphics driver
   requires the use of a text-mode VGA console. Use of other console
   drivers including, but not limited to, vesafb, may result in
   corruption and stability problems, and is not supported.
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity:Unity7
  Date: Tue May  9 02:08:25 2017
  DistUpgraded: Fresh install
  DistroCodename: zesty
  DistroVariant: ubuntu
  DkmsStatus: nvidia, 375.66, 4.10.14-zen+, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   NVIDIA Corporation GP104 [GeForce GTX 1080] [10de:1b80] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: ASUSTeK Computer Inc. GP104 [GeForce GTX 1080] [1043:85aa]
   Advanced Micro Devices, Inc. [AMD/ATI] Bonaire XTX [Radeon R7 260X/360] 
[1002:6658] (prog-if 00 [VGA controller])
 Subsystem: Gigabyte Technology Co., Ltd Bonaire XTX [Radeon R7 260X/360] 
[1458:227b]
  InstallationDate: Installed on 2017-05-06 (1 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  MachineType: ASUS All Series
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.10.14-zen+ 
root=UUID=e1130f0b-d82f-4976-989f-c8b18f0965eb ro intel_iommu=on 
vfio_iommu_type1.allow_unsafe_interrupts=1
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/18/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 3402
  dmi.board.asset.tag: Default string
  dmi.board.name: X99-A
  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.:bvr3402:bd08/18/2016:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnX99-A:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.name: All Series
  dmi.product.version: System Version
  dmi.sys.vendor: ASUS
  version.compiz: compiz 1:0.9.13.1+17.04.20170109-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.76-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.3-1ubuntu1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.3-1ubuntu1
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.3-1ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.9.0-0ubuntu1
  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.14-0ubuntu1
  xserver.bootTime: Tue May  9 00:26:57 2017
  xserver.configfile: /etc/X11/xorg.conf
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   
  xserver.version: 2:1.19.3-1ubuntu1

To manage notifications about this bug go to:

[Desktop-packages] [Bug 1528915] Re: Allow changing of the top panel's colour and transparency levels without need to install extension - feature request

Wishlist was correct back in May since the panel was always black back
then.

Yes, I agree the importance is now higher due to problems with the new
transparent panel.

** Changed in: gnome-control-center (Ubuntu)
   Importance: Wishlist => Medium

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

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

Title:
  Allow changing of the top panel's colour and transparency levels
  without need to install extension - feature request

Status in gnome-control-center:
  Unknown
Status in Ubuntu GNOME:
  Confirmed
Status in gnome-control-center package in Ubuntu:
  Confirmed
Status in gnome-shell package in Ubuntu:
  Confirmed

Bug description:
  Currently if one wants to change the colour or transparency levels of
  the top panel they have to install an extension, I think that this
  functionality should be built-in so that one can just change these
  settings in the gnome-control-center rather than having to install
  some third-party extension.

  I am running Ubuntu GNOME 15.10 with GNOME 3.18.

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

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

[Desktop-packages] [Bug 1698287] Re: VA-API fails to initialize in a Gnome Shell Wayland session

2017-11-05 Thread Andrea Agnolin

Generate video h264 file (however I get the same behavior for every file I 
tested).
$ ffmpeg -f lavfi -i color=white;fade=t=out:d=10 -t 10 -c:v libx264 test.mkv

Within the "Ubuntu" session

Selecting the option "Decoder VA-API throught DRM"
$ vlc test.mkv 
VLC media player 2.2.6 Umbrella (revision 2.2.6-0-g1aae78981c)
[55d996caf9d8] core libvlc: Esecuzione di vlc con l'interfaccia 
predefinita. Usa 'cvlc' per utilizzare vlc senza interfaccia.
libva info: VA-API version 0.40.0
libva info: va_getDriverName() returns 1
libva error: va_getDriverName() failed with operation failed,driver_name=i965
[7f9ecc000c18] vaapi_drm generic error: Failed to initialize the VAAPI 
device
Failed to open VDPAU backend libvdpau_nvidia.so: impossibile aprire il file 
oggetto condiviso: File o directory non esistente

Within the "Ubuntu on Xorg" session

Selecting the option "Decoder VA-API throught X11"
$ vlc test.mkv 
VLC media player 2.2.6 Umbrella (revision 2.2.6-0-g1aae78981c)
[563a5bfb79d8] core libvlc: Esecuzione di vlc con l'interfaccia 
predefinita. Usa 'cvlc' per utilizzare vlc senza interfaccia.
libva info: VA-API version 0.40.0
libva info: va_getDriverName() returns -1
libva error: va_getDriverName() failed with unknown libva 
error,driver_name=(null)
[7f8ff4000c18] vaapi_x11 generic error: Failed to initialize the VAAPI 
device
Failed to open VDPAU backend libvdpau_nvidia.so: impossibile aprire il file 
oggetto condiviso: File o directory non esistente
QObject::~QObject: Timers cannot be stopped from another thread

Selecting the option "Decoder VA-API throught DRM"
$ vlc test.mkv 
VLC media player 2.2.6 Umbrella (revision 2.2.6-0-g1aae78981c)
[55adbab999d8] core libvlc: Esecuzione di vlc con l'interfaccia 
predefinita. Usa 'cvlc' per utilizzare vlc senza interfaccia.
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
[7f88b4c0d8b8] avcodec decoder: Using Intel i965 driver for Intel(R) 
Haswell Mobile - 1.8.3 for hardware decoding.
Failed to open VDPAU backend libvdpau_i965.so: impossibile aprire il file 
oggetto condiviso: File o directory non esistente
QObject::~QObject: Timers cannot be stopped from another thread

Selecting the option "Decoder VA-API throught X11"
$ vlc test.mkv 
VLC media player 2.2.6 Umbrella (revision 2.2.6-0-g1aae78981c)
[5636cc1249d8] core libvlc: Esecuzione di vlc con l'interfaccia 
predefinita. Usa 'cvlc' per utilizzare vlc senza interfaccia.
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
[7fbd00c0d8b8] avcodec decoder: Using Intel i965 driver for Intel(R) 
Haswell Mobile - 1.8.3 for hardware decoding.
Failed to open VDPAU backend libvdpau_i965.so: impossibile aprire il file 
oggetto condiviso: File o directory non esistente

For other bigger files there is a noticeable difference in the CPU usage
between the Xorg and Wayland session (Xorg lower).

I also attach vlcrc file from .config/vlc/

** Attachment added: "vlcrc"
   
https://bugs.launchpad.net/ubuntu/+source/gstreamer-vaapi/+bug/1698287/+attachment/5004461/+files/vlcrc

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

Title:
  VA-API fails to initialize in a Gnome Shell Wayland session

Status in Libva:
  New
Status in Mutter:
  Confirmed
Status in Totem:
  Confirmed
Status in VLC media player:
  New
Status in chromium-browser package in Ubuntu:
  Confirmed
Status in gst-plugins-bad1.0 package in Ubuntu:
  Fix Released
Status in gstreamer-vaapi package in Ubuntu:
  Won't Fix
Status in libva package in Ubuntu:
  Triaged
Status in mpv package in Ubuntu:
  Fix Released
Status in mutter package in Ubuntu:
  Triaged
Status in vlc package in Ubuntu:
  Incomplete

Bug description:
  The Intel i965 VA-API driver works well in Xorg sessions (Unity7 and
  Gnome Shell). But it refuses to load when in a Wayland session:

  $ totem bbb_sunflower_1080p_60fps_normal.mp4
  libva error: va_getDriverName() failed with unknown libva 
error,driver_name=(null)

  $ env LIBVA_DRIVER_NAME=i965 totem bbb_sunflower_1080p_60fps_normal.mp4
  totem: intel_driver.c:112: intel_driver_init: Assertion 
`VA_CHECK_DRM_AUTH_TYPE(ctx, VA_DRM_AUTH_DRI1) || VA_CHECK_DRM_AUTH_TYPE(ctx, 
VA_DRM_AUTH_DRI2) || VA_CHECK_DRM_AUTH_TYPE(ctx, VA_DRM_AUTH_CUSTOM)' failed.
  Aborted (core dumped)

  $ gst-play-1.0 bbb_sunflower_1080p_60fps_normal.mp4
  Press 'k' to see a list of keyboard shortcuts.
  Now playing /home/dan/Videos/bbb_sunflower_1080p_60fps_normal.mp4
  Redistribute latency...
  Redistribute latency...
  ERROR Internal error: could not render

[Desktop-packages] [Bug 1730195] Re: Make the panel and dock transparency configurable

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

Ubuntu's direct involvement in Gnome Shell is only getting started, so
don't let the age of existing bug reports get you down. Just last week I
closed an upstream Gnome Shell bug that had been open for over 6 years.

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

Title:
  Make the panel and dock transparency configurable

Status in gnome-shell package in Ubuntu:
  Triaged

Bug description:
  Make the panel and dock transparency configurable.

  Some people prefer them more opaque, some prefer more translucent, and
  some prefer that the appearance doesn't change at all.

  This was all configurable in Unity and it would be helpful if Ubuntu
  users of Gnome Shell could continue to do the same.

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

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

[Desktop-packages] [Bug 1528915] Re: Allow changing of the top panel's colour and transparency levels without need to install extension - feature request

2017-11-05 Thread James Lewis

This issue, whether you call it a wishlist item, or not... makes system
tray icons invisible in 17.10... surely invisible icons is a bug, not a
wish?

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

Title:
  Allow changing of the top panel's colour and transparency levels
  without need to install extension - feature request

Status in gnome-control-center:
  Unknown
Status in Ubuntu GNOME:
  Confirmed
Status in gnome-control-center package in Ubuntu:
  Confirmed
Status in gnome-shell package in Ubuntu:
  Confirmed

Bug description:
  Currently if one wants to change the colour or transparency levels of
  the top panel they have to install an extension, I think that this
  functionality should be built-in so that one can just change these
  settings in the gnome-control-center rather than having to install
  some third-party extension.

  I am running Ubuntu GNOME 15.10 with GNOME 3.18.

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

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

[Desktop-packages] [Bug 1730195] Re: Make the panel and dock transparency configurable

2017-11-05 Thread James Lewis

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

I understand that it's not you specifically, and I apologise that I did
not find the earlier duplicate... the search did not find it, although
to be fair it is more than 2 years old, and logged against a respin...
which makes me think it's a hopeless cause like many other issues,
how likely is a duplicate of a 2 year old issue in the gnome respin ever
likely to be considered again?

I cannot deny that the work done to make Gnome 3 acceptable to regular
Ubuntu users over the last few months has been nothing more than
incredible, but I can't help but think it shouldn't have been necessary.

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

Title:
  Make the panel and dock transparency configurable

Status in gnome-shell package in Ubuntu:
  Triaged

Bug description:
  Make the panel and dock transparency configurable.

  Some people prefer them more opaque, some prefer more translucent, and
  some prefer that the appearance doesn't change at all.

  This was all configurable in Unity and it would be helpful if Ubuntu
  users of Gnome Shell could continue to do the same.

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

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

[Desktop-packages] [Bug 1698287] Re: VA-API fails to initialize in a Gnome Shell Wayland session

Andrea,

What errors do you see in VLC relating to this bug?

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

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

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

Title:
  VA-API fails to initialize in a Gnome Shell Wayland session

Status in Libva:
  New
Status in Mutter:
  Confirmed
Status in Totem:
  Confirmed
Status in VLC media player:
  New
Status in chromium-browser package in Ubuntu:
  Confirmed
Status in gst-plugins-bad1.0 package in Ubuntu:
  Fix Released
Status in gstreamer-vaapi package in Ubuntu:
  Won't Fix
Status in libva package in Ubuntu:
  Triaged
Status in mpv package in Ubuntu:
  Fix Released
Status in mutter package in Ubuntu:
  Triaged
Status in vlc package in Ubuntu:
  Incomplete

Bug description:
  The Intel i965 VA-API driver works well in Xorg sessions (Unity7 and
  Gnome Shell). But it refuses to load when in a Wayland session:

  $ totem bbb_sunflower_1080p_60fps_normal.mp4
  libva error: va_getDriverName() failed with unknown libva 
error,driver_name=(null)

  $ env LIBVA_DRIVER_NAME=i965 totem bbb_sunflower_1080p_60fps_normal.mp4
  totem: intel_driver.c:112: intel_driver_init: Assertion 
`VA_CHECK_DRM_AUTH_TYPE(ctx, VA_DRM_AUTH_DRI1) || VA_CHECK_DRM_AUTH_TYPE(ctx, 
VA_DRM_AUTH_DRI2) || VA_CHECK_DRM_AUTH_TYPE(ctx, VA_DRM_AUTH_CUSTOM)' failed.
  Aborted (core dumped)

  $ gst-play-1.0 bbb_sunflower_1080p_60fps_normal.mp4
  Press 'k' to see a list of keyboard shortcuts.
  Now playing /home/dan/Videos/bbb_sunflower_1080p_60fps_normal.mp4
  Redistribute latency...
  Redistribute latency...
  ERROR Internal error: could not render surface for 
file:///home/dan/Videos/bbb_sunflower_1080p_60fps_normal.mp4
  ERROR debug information: ../../../gst/vaapi/gstvaapisink.c(1482): 
gst_vaapisink_show_frame_unlocked (): 
/GstPlayBin:playbin/GstPlaySink:playsink/GstBin:vbin/GstVaapiSink:vaapisink0

  WORKAROUNDS:

   * Use weston instead of gnome-shell; or
   * $ env -uDISPLAY totem ... # but creates corruption -> bug 1701463
   * $ env GST_GL_WINDOW=wayland totem ... # but creates corruption -> bug 
1701463
   * $ env GST_GL_WINDOW=wayland gst-play-1.0 --videosink glimagesink ...
   * $ env -uDISPLAY mpv --hwdec --opengl-backend=wayland ...

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: i965-va-driver 1.8.1-1
  ProcVersionSignature: Ubuntu 4.10.0-22.24-generic 4.10.15
  Uname: Linux 4.10.0-22-generic x86_64
  ApportVersion: 2.20.5-0ubuntu4
  Architecture: amd64
  Date: Fri Jun 16 13:40:38 2017
  InstallationDate: Installed on 2017-05-03 (44 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170502)
  SourcePackage: intel-vaapi-driver
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1730229] Re: Desktop stops accepting input from mouse, keyboard, touchpad, or touchscreen, but topbar and dock still accept input

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

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


** Tags added: noclick

** This bug has been marked a duplicate of bug 1181666
   gnome-shell randomly blocks mouse clicks from working in app windows

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

Title:
  Desktop stops accepting input from mouse, keyboard, touchpad, or
  touchscreen, but topbar and dock still accept input

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  The desktop area stops accepting inputs from the mouse, keyboard,
  trackpad, and touchscreen.

  However, gnome session is not frozen, because I can still interact
  with the topbar and the Ubuntu Dock using the pointer or keyboard.

  I can move the pointer using the trackpad, or attached mouse, but
  clicking or typing in windows on the desktop area has no effect.

  What I can not do:
  - I can not close windows using the window buttons.
  - I can not move windows.
  - I can not bring windows to the foreground.
  - I can not click on any dialog buttons.
  - I can not type in any test areas (such as in gedit).

  What I can do:
  - I can start the activities view by clicking on Activities in the top left 
corner.
  - I can launch programs from the dock and from the applications button.
  - I can also interact with the notifications area or the indicator icons at 
the right of the topbar.
  - I can type and search for applications after entering the Activities 
overview.

  Logging-out and loggin-in does not resolve the problem.
  - Note that GDM accepts mouse and keyboard inputs.
  - After logging back into the desktop, I can not interact with the desktop 
area, as before.

  Restating is the only way to regain ability to interact with the
  windows and desktop area.

  I experience this issue on my laptop running Ubuntu 17.10, but I have
  not had this issue on my desktop running Ubuntu 17.10.

  Additional Information (Laptop):
    2017 HP Spectre x360 Convertible Laptop - 15t touch
    GeForce MX150
    Using xserver-xorg 1:7.7+19ubuntu3 amd64
    Using Nvidia binary driver version 384.90
    $ lsb_release -rd
    Description:Ubuntu 17.10
    Release:17.10
    $ gnome-shell --version
    GNOME Shell 3.26.1
    $ mutter --version
    mutter 3.26.1

  Note: My desktop (which does not have this issue) is also running
  Ubuntu 17.10, has an Nvidia card, and is using the proprietary driver
  with xorg.

  I'm not sure if mutter is responsible for handling mouse/keyboard
  inputs separately from GDM, extensions, and the topbar, so I opened
  this bug against gnome-shell.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.26.1-0ubuntu5
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Sun Nov  5 14:19:45 2017
  DisplayManager: gdm3
  GsettingsChanges:
   b'org.gnome.shell' b'had-bluetooth-devices-setup' b'true'
   b'org.gnome.shell' b'app-picker-view' b'uint32 1'
   b'org.gnome.shell' b'favorite-apps' b"['google-chrome.desktop', 
'chrome-eppojlglocelodeimnohnlnionkobfln-Default.desktop', 
'org.gnome.Nautilus.desktop', 'org.gnome.gedit.desktop', 
'org.gnome.Terminal.desktop', 'libreoffice-writer.desktop', 
'libreoffice-calc.desktop', 'org.gnome.Software.desktop', 
'gnome-system-monitor.desktop']"
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
  InstallationDate: Installed on 2017-11-03 (1 days ago)
  InstallationMedia: Ubuntu 17.10.0 2017.10.23 amd64 "Custom Artful Aardvark"
  ProcEnviron:
   TERM=xterm-256color
   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/1730229/+subscriptions

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

[Desktop-packages] [Bug 1730281] Re: Application icons appear and suddenly disappear when Applications Button is activated via a touchscreen

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

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

Title:
  Application icons appear and suddenly disappear when Applications
  Button is activated via a touchscreen

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

Bug description:
  Clicking on the application button (with a mouse) in the Ubuntu Dock
  causes the applications icons to be displayed.

  ISSUE

  On a Touch Screen...

  The issue is, if you touch the application button in the Ubuntu Dock,
  the applications icons appear (expand out from the button using
  animation) but then they suddenly disappear (contract back into the
  button using animation).

  If you touch the button and do not remove your finger, all of the
  icons are displayed on the screen.  As soon as you remove your finger,
  the icons recede back into the button.

  EXPECTED

  Touching the application button (with a finger) in the Ubuntu Dock should 
cause the applications icons to be displayed.  They should continue to be 
displayed until the user selects an application, 
   presses the ESC key, or clicks an icon on the dock.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell-extension-ubuntu-dock 0.7
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Mon Nov  6 00:24:05 2017
  InstallationDate: Installed on 2017-11-03 (2 days ago)
  InstallationMedia: Ubuntu 17.10.0 2017.10.23 amd64 "Custom Artful Aardvark"
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-shell-extension-ubuntu-dock
  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/1730281/+subscriptions

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

[Desktop-packages] [Bug 1566357] Re: Unable to type passwords with non-English/non-Latin non-physical input methods

Nevermind. I should have googled some more to confirm Gunnar is right.
We should probably work to distinguish these bugs better if not
combining them.

** Summary changed:

- Unable to type passwords with non-English/non-Latin  non-physical input 
methods
+ Unable to type passwords with the "Japanese (Anthy)" input method

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

Title:
  Unable to type passwords with the "Japanese (Anthy)" input method

Status in GNOME Shell:
  Confirmed
Status in Ubuntu GNOME:
  Confirmed
Status in gdm3 package in Ubuntu:
  Confirmed
Status in gnome-control-center package in Ubuntu:
  Confirmed
Status in gnome-shell package in Ubuntu:
  Confirmed

Bug description:
  I recently found that I am unable to type using the "Japanese (Anthy)"
  input source in password fields in gnome-shell. That is I am unable to
  type using it (I just get English) on the login screen in the password
  field (though I haven't tried the username field), I am unable to type
  using it in the graphical prompts for authentication, and I am unable
  to type using it when setting a new password through the gnome-
  control-center.

  I am running Ubuntu GNOME 15.10 with GNOME 3.18 but have also
  experienced this issue with Ubuntu GNOME 16.04 with GNOME 3.18 as well
  as with GNOME 3.20.

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

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

[Desktop-packages] [Bug 1566357] Re: Unable to type passwords with non-English/non-Latin input source

Nikita, can you please clarify what you mean by "input source"? Is that
a physical keyboard or graphical input method?

** Summary changed:

- Unable to type passwords with non-English/non-Latin input source
+ Unable to type passwords with non-English/non-Latin  non-physical input 
methods

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

Title:
  Unable to type passwords with the "Japanese (Anthy)" input method

Status in GNOME Shell:
  Confirmed
Status in Ubuntu GNOME:
  Confirmed
Status in gdm3 package in Ubuntu:
  Confirmed
Status in gnome-control-center package in Ubuntu:
  Confirmed
Status in gnome-shell package in Ubuntu:
  Confirmed

Bug description:
  I recently found that I am unable to type using the "Japanese (Anthy)"
  input source in password fields in gnome-shell. That is I am unable to
  type using it (I just get English) on the login screen in the password
  field (though I haven't tried the username field), I am unable to type
  using it in the graphical prompts for authentication, and I am unable
  to type using it when setting a new password through the gnome-
  control-center.

  I am running Ubuntu GNOME 15.10 with GNOME 3.18 but have also
  experienced this issue with Ubuntu GNOME 16.04 with GNOME 3.18 as well
  as with GNOME 3.20.

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

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

[Desktop-packages] [Bug 1728187] Re: Wacom pointer disappears completely, after using the tablet for few seconds (Ubuntu 17.10)

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

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


** This bug has been marked a duplicate of bug 1726224
   wacom invisible mouse pointer in wayland

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

Title:
  Wacom pointer disappears completely, after using the tablet for few
  seconds (Ubuntu 17.10)

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

Bug description:
  I recently upgraded to Ubuntu 17.10(gnome, Wayland,
  4.10.0-37-generic). The Wacom tablet works fine for few seconds while
  drawing, and then the pointer would suddenly disappears. I can still
  use the tablet to draw stuff, but there is no visible pointer on
  screen, so I am doing it blindly. Just so you know the mouse pointer
  appears separately and works fine.

  If you need additional info, just send me the set of commands I need
  to run.

  Thanks!!

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

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

[Desktop-packages] [Bug 1728187] Re: Wacom pointer disappears completely, after using the tablet for few seconds (Ubuntu 17.10)

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

Please don't assign bugs to "wayland". The "wayland" package is only
protocol libraries. Graphics problems such as this should be assigned to
the display server: gnome-shell.

Remember Wayland is not a display server. It is only a protocol.

** No longer affects: wayland (Ubuntu)

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

** Tags added: cursor wacom wayland

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

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

Title:
  Wacom pointer disappears completely, after using the tablet for few
  seconds (Ubuntu 17.10)

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

Bug description:
  I recently upgraded to Ubuntu 17.10(gnome, Wayland,
  4.10.0-37-generic). The Wacom tablet works fine for few seconds while
  drawing, and then the pointer would suddenly disappears. I can still
  use the tablet to draw stuff, but there is no visible pointer on
  screen, so I am doing it blindly. Just so you know the mouse pointer
  appears separately and works fine.

  If you need additional info, just send me the set of commands I need
  to run.

  Thanks!!

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

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

[Desktop-packages] [Bug 1418357] Re: gnome-system-log auto-scrolls away from entry being viewed

2017-11-05 Thread jay armstrong

In 16.04, I have the option to disable autoscroll but the sane default
expected by the OP still seems much more useful, convenient, and common.

Additionally, with autoscroll enabled, the app will change the log file
being viewed every few seconds - in this case, from syslog to
Xorg.0.log. That makes even less sense.

gnome-system-log v3.9.90

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

Title:
  gnome-system-log auto-scrolls away from entry being viewed

Status in One Hundred Papercuts:
  Confirmed
Status in gnome-system-log package in Ubuntu:
  Confirmed

Bug description:
  If you run gnome-system-log (the gnome app that hasn't been modified
  to fit in with the Unity theme) and scroll to look at a particular
  line, ie so you are not on the last line of the log, when the system
  adds another log entry gnome-system-log automatically scrolls to this
  new entry, losing your previous position. This makes it very difficult
  to use.

  I would expect it to follow its previous behaviour, which is that if
  you are on the last line of the log, it auto-scrolls to show new
  entries, but if you are not on the last line, it never auto-scrolls.
  It would even be preferable if it never auto-scrolled or if there were
  an option to turn auto-scrolling on and off.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: gnome-system-log 3.9.90-2
  Uname: Linux 3.19.0-031900rc7-generic x86_64
  ApportVersion: 2.15.1-0ubuntu4
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Thu Feb  5 14:19:41 2015
  InstallationDate: Installed on 2015-01-02 (34 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Alpha amd64 (20141220)
  SourcePackage: gnome-system-log
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1730195] Re: Make the panel and dock transparency configurable

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

On the other hand, the feature request already exists -> bug 1528915

** This bug has been marked a duplicate of bug 1528915
   Allow changing of the top panel's colour and transparency levels without 
need to install extension - feature request

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

Title:
  Make the panel and dock transparency configurable

Status in gnome-shell package in Ubuntu:
  Triaged

Bug description:
  Make the panel and dock transparency configurable.

  Some people prefer them more opaque, some prefer more translucent, and
  some prefer that the appearance doesn't change at all.

  This was all configurable in Unity and it would be helpful if Ubuntu
  users of Gnome Shell could continue to do the same.

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

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

[Desktop-packages] [Bug 1730195] Re: Launcher transparrency is applied to the top bar, invisible icons.

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

I understand. Reporting bugs is messy and more complicated than many of
us would like.

Also this feature is not one that Ubuntu would have chosen to implement.
We just inherited it from Gnome.

I marked this bug as invalid because the way it is worded is presently
invalid (not a bug at all, but a feature). As mentioned in comment #2,
if you would like to convert this into an enhancement request then it
needs to be reworded significantly or replaced by a new bug report. I
will try to do that now for you so that you don't need to...

** Summary changed:

- Launcher transparrency is applied to the top bar, invisible icons.
+ Make the panel and dock transparency configurable

** Description changed:

- The new launcher in Ubuntu 17.10's gnome-shell setup has auto
- transparency... but this is also applied to the top bar, which it was
- not in Unity.
+ Make the panel and dock transparency configurable.
  
- As a result, using a light background makes the light icons in the bar
- almost invisible.
+ Some people prefer them more opaque, some prefer more translucent, and
+ some prefer that the appearance doesn't change at all.
  
- The top bar transparency should not be linked to the launcher, and
- probably there should not be transparrency on the top bar.
- 
- It would also be nice if there was a slider to control the level of
- transparrency in the launcher.
- 
- See attached image of near invisible icons.
+ This was all configurable in Unity and it would be helpful if Ubuntu
+ users of Gnome Shell could continue to do the same.

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

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

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

Title:
  Make the panel and dock transparency configurable

Status in gnome-shell package in Ubuntu:
  Triaged

Bug description:
  Make the panel and dock transparency configurable.

  Some people prefer them more opaque, some prefer more translucent, and
  some prefer that the appearance doesn't change at all.

  This was all configurable in Unity and it would be helpful if Ubuntu
  users of Gnome Shell could continue to do the same.

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

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

[Desktop-packages] [Bug 1725315] Re: evolution crashed with SIGSEGV in g_hash_table_lookup_node()

2017-11-05 Thread Mauro Gaspari

Per comment #9, I confirm it only happens on gnome-shell on wayland mode.
I tested thoroughly over the last few days and I did not experience a single 
crash on gnome-shell on Xorg.Once I switch back to gnome-shell on wayland, the 
frequent crashes start happening again.

Per comment #10, I tested the workaround: uninstall evolution-indicator
package, and I confirm it works. No more evolution crashes on gnome-
shell on wayland.

PS
I ran the tests mentioned above on 2 machines: on Virtualbox VM, and on 
Hardware. Same results on both.

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

Title:
  evolution crashed with SIGSEGV in g_hash_table_lookup_node()

Status in evolution package in Ubuntu:
  Confirmed

Bug description:
  Every few minutes, evolution exits the desktop.  Sometimes it will
  only stay up for seconds, and sometimes it exits in the first second.
  Occasionally it stays up for ~20 minutes.  When it is running, it
  seems to function normally.  This machine was upgraded from 17.04
  (where Evolution was stable) to 17.10 release.

  Apport crashdump analysis attached.

  Looking at /var/log/syslog after one of these crashes, I see the
  following entries:

  Oct 20 09:50:00 es-lzz-det470s org.gnome.Shell.desktop[2287]: 
/usr/share/themes/Ambiance/gtk-2.0/apps/mate-panel.rc:30: error: invalid string 
constant "murrine-scrollbar", expected valid string constant
  Oct 20 09:50:00 es-lzz-det470s org.gnome.Shell.desktop[2287]: [Parent 8840] 
WARNING: pipe error (254): Connection reset by peer: file 
/build/firefox-9cfKiA/firefox-56.0+build6/ipc/chromium/src/chrome/common/ipc_channel_posix.cc,
 line 353
  Oct 20 09:50:52 es-lzz-det470s org.gnome.Shell.desktop[2287]: [Parent 8840] 
WARNING: pipe error (287): Connection reset by peer: file 
/build/firefox-9cfKiA/firefox-56.0+build6/ipc/chromium/src/chrome/common/ipc_channel_posix.cc,
 line 353
  Oct 20 09:50:52 es-lzz-det470s org.gnome.Shell.desktop[2287]: [Parent 8840] 
WARNING: pipe error (300): Connection reset by peer: file 
/build/firefox-9cfKiA/firefox-56.0+build6/ipc/chromium/src/chrome/common/ipc_channel_posix.cc,
 line 353
  Oct 20 09:50:52 es-lzz-det470s org.gnome.Shell.desktop[2287]: [Parent 8840] 
WARNING: pipe error (417): Connection reset by peer: file 
/build/firefox-9cfKiA/firefox-56.0+build6/ipc/chromium/src/chrome/common/ipc_channel_posix.cc,
 line 353
  Oct 20 09:50:57 es-lzz-det470s kernel: [88013.689438] evolution[1461]: 
segfault at 0 ip   (null) sp 7ffee4f96718 error 14 in 
evolution[557e54c52000+7000]

  It is not clear that the first few syslog entries are related.

  Running evolution with debugging enabled:
  CAMEL_DEBUG=all evolution

  I see the following output when the crash occurs:

  ###
  message_list_regen_thread: got 1521 uids in folder 0x5615e38015f0 
(john.mel...@esentire.com : Inbox) for expression:---(and (match-all (and (not 
(system-flag "deleted")) (not (system-flag "junk" (and  (and  (match-all 
(not (or (= (user-tag "label") "important") (user-flag "$Labelimportant") 
(user-flag "important" (match-all (not (or (= (user-tag "label") "work") 
(user-flag "$Labelwork") (user-flag "work" (match-all (not (or (= (user-tag 
"label") "personal") (user-flag "$Labelpersonal") (user-flag "personal" 
(match-all (not (or (= (user-tag "label") "todo") (user-flag "$Labeltodo") 
(user-flag "todo" (match-all (not (or (= (user-tag "label") "later") 
(user-flag "$Labellater") (user-flag "later")))---
 message_list_regen_thread: got 1521 uids in folder 0x5615e38015f0 
(john.mel...@esentire.com : Inbox) after tweak, hide_deleted:1, hide_junk:1
  Segmentation fault (core dumped)

  Not sure if I can provide further information.  This crash is highly-
  repeatable, happening hundreds of times/day.

  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: evolution 3.26.1-1
  ProcVersionSignature: Ubuntu 4.13.0-16.19-lowlatency 4.13.4
  Uname: Linux 4.13.0-16-lowlatency x86_64
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Oct 20 09:50:57 2017
  Disassembly: => 0x0:  Cannot access memory at address 0x0
  ExecutablePath: /usr/bin/evolution
  InstallationDate: Installed on 2017-05-31 (142 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  ProcCmdline: evolution -c current
  ProcEnviron:
   LANGUAGE=en_CA:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_CA.UTF-8
   SHELL=/bin/bash
  SegvAnalysis:
   Segfault happened at: 0x0:   Cannot access memory at address 0x0
   PC (0x) not located in a known VMA region (needed executable region)!
  SegvReason: executing NULL VMA
  Signal: 11
  SourcePackage: evolution
  StacktraceTop:
   ?? ()
   g_hash_table_lookup () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   gdk_x11_atom_to_xatom_for_display ()

[Desktop-packages] [Bug 1728187] Re: Wacom pointer disappears completely, after using the tablet for few seconds (Ubuntu 17.10)

2017-11-05 Thread Anubhav Singh

Additional Observation: This issue seems specific to Wayland. The tablet
is usable when switched to Xorg.

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

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

Title:
  Wacom pointer disappears completely, after using the tablet for few
  seconds (Ubuntu 17.10)

Status in libwacom package in Ubuntu:
  Confirmed
Status in wayland package in Ubuntu:
  New

Bug description:
  I recently upgraded to Ubuntu 17.10(gnome, Wayland,
  4.10.0-37-generic). The Wacom tablet works fine for few seconds while
  drawing, and then the pointer would suddenly disappears. I can still
  use the tablet to draw stuff, but there is no visible pointer on
  screen, so I am doing it blindly. Just so you know the mouse pointer
  appears separately and works fine.

  If you need additional info, just send me the set of commands I need
  to run.

  Thanks!!

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

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

[Desktop-packages] [Bug 1728187] Re: Wacom pointer disappears completely, after using the tablet for few seconds (Ubuntu 17.10)

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

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

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

Title:
  Wacom pointer disappears completely, after using the tablet for few
  seconds (Ubuntu 17.10)

Status in libwacom package in Ubuntu:
  Confirmed

Bug description:
  I recently upgraded to Ubuntu 17.10(gnome, Wayland,
  4.10.0-37-generic). The Wacom tablet works fine for few seconds while
  drawing, and then the pointer would suddenly disappears. I can still
  use the tablet to draw stuff, but there is no visible pointer on
  screen, so I am doing it blindly. Just so you know the mouse pointer
  appears separately and works fine.

  If you need additional info, just send me the set of commands I need
  to run.

  Thanks!!

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

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

[Desktop-packages] [Bug 1730195] Re: Launcher transparrency is applied to the top bar, invisible icons.

2017-11-05 Thread James Lewis

You know... I thought things might have changed, if those working on the
project don't like something, but can't get it changed, what hope do I
have??  Why mark this bug as invalid if you agree that it's a problem.

Canonical's customers do not understand the shifting relationships
between different components of the distribution, let alone what this
new relationship with upstream gnome means... I have no idea where else
to report such a thing.

So, be it, I have reported it, Canonical doesn't care, end of story...
just like almost every other bug I've ever reported. I wonder why I
bother.

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

Title:
  Launcher transparrency is applied to the top bar, invisible icons.

Status in gnome-shell package in Ubuntu:
  Invalid

Bug description:
  The new launcher in Ubuntu 17.10's gnome-shell setup has auto
  transparency... but this is also applied to the top bar, which it was
  not in Unity.

  As a result, using a light background makes the light icons in the bar
  almost invisible.

  The top bar transparency should not be linked to the launcher, and
  probably there should not be transparrency on the top bar.

  It would also be nice if there was a slider to control the level of
  transparrency in the launcher.

  See attached image of near invisible icons.

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

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

[Desktop-packages] [Bug 1728187] Re: Wacom pointer disappears completely, after using the tablet for few seconds (Ubuntu 17.10)

2017-11-05 Thread Bob

I have the same issue. My desperate workaround is to pull the USB plug
and reinsert it. That seems to reset the tablet and make it work again,
but the problem returns after a few minutes. Another workaround is to
flip the pen and use the eraser end, which buys a bit more time before
having to pull the plug again. It was flawless before the 17.10 upgrade.

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

Title:
  Wacom pointer disappears completely, after using the tablet for few
  seconds (Ubuntu 17.10)

Status in libwacom package in Ubuntu:
  Confirmed

Bug description:
  I recently upgraded to Ubuntu 17.10(gnome, Wayland,
  4.10.0-37-generic). The Wacom tablet works fine for few seconds while
  drawing, and then the pointer would suddenly disappears. I can still
  use the tablet to draw stuff, but there is no visible pointer on
  screen, so I am doing it blindly. Just so you know the mouse pointer
  appears separately and works fine.

  If you need additional info, just send me the set of commands I need
  to run.

  Thanks!!

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

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

[Desktop-packages] [Bug 706966] Re: [natty] firefox copy text to middle button clipboard

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

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

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

Title:
  [natty] firefox copy text to middle button clipboard

Status in firefox package in Ubuntu:
  Expired

Bug description:
  Binary package hint: firefox

  Hi,

  With firefox 4.0 on natty, when copying some text using ctrl-c or the
  contextual menu entry, the text is not put into the primary clipboard
  but in the"middle mouse button" clipboard

  1) Copy some url with the  "Copy Link Location" contextual menu entry
  2) Try to paste the URL with CTRL-C in the terminal -> Nothing is paste
  3) Push the middle button of the mouse -> URL is paste in the terminal

  This is not consistent with the behavior of the rest of the system

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

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

[Desktop-packages] [Bug 1715157] Re: Ubuntu software center won't install updates.

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

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

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

Title:
  Ubuntu software center won't install updates.

Status in gnome-software package in Ubuntu:
  Expired

Bug description:
  The updates I'm trying to install are OS Updates and Software 3.20.5.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: gnome-software-common 3.20.5-0ubuntu0.16.04.5
  ProcVersionSignature: Ubuntu 4.10.0-33.37~16.04.1-generic 4.10.17
  Uname: Linux 4.10.0-33-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  Date: Tue Sep  5 09:56:20 2017
  Dependencies:
   
  DuplicateSignature:
   package:gnome-software-common:3.20.5-0ubuntu0.16.04.5
   Processing triggers for fontconfig (2.11.94-0ubuntu1.1) ...
   dpkg: error processing package gnome-software-common (--configure):
package is in a very bad inconsistent state; you should
  ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
  InstallationDate: Installed on 2017-07-01 (65 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.24
  SourcePackage: gnome-software
  Title: package gnome-software-common 3.20.5-0ubuntu0.16.04.5 failed to 
install/upgrade: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1730079] Re: package libgl1-mesa-dri 11.2.0-1ubuntu2.2~somerville2 failed to install/upgrade: попытка перезаписать общий «/usr/share/doc/libgl1-mesa-dri/copyright», который отл

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

** This bug has been marked a duplicate of bug 1730077
   package libdrm-amdgpu1 2.4.67-1ubuntu0.16.04.1 failed to install/upgrade: 
попытка перезаписать общий «/usr/share/doc/libdrm-amdgpu1/copyright», который 
отличается от других экземпляров пакета libdrm-amdgpu1:amd64

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

Title:
  package libgl1-mesa-dri 11.2.0-1ubuntu2.2~somerville2 failed to
  install/upgrade: попытка перезаписать общий «/usr/share/doc/libgl1
  -mesa-dri/copyright», который отличается от других экземпляров пакета
  libgl1-mesa-dri:amd64

Status in mesa package in Ubuntu:
  New

Bug description:
  Installing amdgpu driver from amd.com

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libgl1-mesa-dri 11.2.0-1ubuntu2.2~somerville2
  ProcVersionSignature: Ubuntu 4.4.0-98.121-generic 4.4.90
  Uname: Linux 4.4.0-98-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Sat Nov  4 15:18:26 2017
  DistUpgraded: Fresh install
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-xenial-amd64-20160624-2
  DistroCodename: xenial
  DistroVariant: ubuntu
  ErrorMessage: попытка перезаписать общий 
«/usr/share/doc/libgl1-mesa-dri/copyright», который отличается от других 
экземпляров пакета libgl1-mesa-dri:amd64
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Device [1002:98e4] (rev c6) (prog-if 
00 [VGA controller])
 Subsystem: Dell Device [1028:076b]
  InstallationDate: Installed on 2017-02-18 (259 days ago)
  InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 
20160624-10:47
  MachineType: Dell Inc. Inspiron 5565
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-98-generic.efi.signed 
root=UUID=be504170-c332-4d45-9258-33545039adde ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.24
  SourcePackage: mesa
  Title: package libgl1-mesa-dri 11.2.0-1ubuntu2.2~somerville2 failed to 
install/upgrade: попытка перезаписать общий 
«/usr/share/doc/libgl1-mesa-dri/copyright», который отличается от других 
экземпляров пакета libgl1-mesa-dri:amd64
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/18/2016
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.0.5
  dmi.board.name: 0WJM4N
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: 1.0.5
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.0.5:bd10/18/2016:svnDellInc.:pnInspiron5565:pvr1.0.5:rvnDellInc.:rn0WJM4N:rvrA00:cvnDellInc.:ct10:cvr1.0.5:
  dmi.product.name: Inspiron 5565
  dmi.product.version: 1.0.5
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.76-1~ubuntu16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2.2~somerville2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2.2~somerville2
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.7
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1.2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2

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

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

[Desktop-packages] [Bug 1730077] Re: package libdrm-amdgpu1 2.4.67-1ubuntu0.16.04.1 failed to install/upgrade: попытка перезаписать общий «/usr/share/doc/libdrm-amdgpu1/copyright», который отличается

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

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

Title:
  package libdrm-amdgpu1 2.4.67-1ubuntu0.16.04.1 failed to
  install/upgrade: попытка перезаписать общий «/usr/share/doc/libdrm-
  amdgpu1/copyright», который отличается от других экземпляров пакета
  libdrm-amdgpu1:amd64

Status in libdrm package in Ubuntu:
  New
Status in mesa package in Ubuntu:
  New

Bug description:
  Trying to install amdgpu driver from official amd.com site

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libdrm-amdgpu1 2.4.67-1ubuntu0.16.04.1
  ProcVersionSignature: Ubuntu 4.4.0-98.121-generic 4.4.90
  Uname: Linux 4.4.0-98-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Sat Nov  4 15:18:20 2017
  Dependencies:
   gcc-6-base 6.0.1-0ubuntu1
   libc6 2.23-0ubuntu9
   libdrm2 2.4.76-1~ubuntu16.04.1
   libgcc1 1:6.0.1-0ubuntu1
  DistUpgraded: Fresh install
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-xenial-amd64-20160624-2
  DistroCodename: xenial
  DistroVariant: ubuntu
  ErrorMessage: попытка перезаписать общий 
«/usr/share/doc/libdrm-amdgpu1/copyright», который отличается от других 
экземпляров пакета libdrm-amdgpu1:amd64
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Device [1002:98e4] (rev c6) (prog-if 
00 [VGA controller])
 Subsystem: Dell Device [1028:076b]
  InstallationDate: Installed on 2017-02-18 (259 days ago)
  InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 
20160624-10:47
  MachineType: Dell Inc. Inspiron 5565
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-98-generic.efi.signed 
root=UUID=be504170-c332-4d45-9258-33545039adde ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.24
  SourcePackage: libdrm
  Title: package libdrm-amdgpu1 2.4.67-1ubuntu0.16.04.1 failed to 
install/upgrade: попытка перезаписать общий 
«/usr/share/doc/libdrm-amdgpu1/copyright», который отличается от других 
экземпляров пакета libdrm-amdgpu1:amd64
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/18/2016
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.0.5
  dmi.board.name: 0WJM4N
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: 1.0.5
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.0.5:bd10/18/2016:svnDellInc.:pnInspiron5565:pvr1.0.5:rvnDellInc.:rn0WJM4N:rvrA00:cvnDellInc.:ct10:cvr1.0.5:
  dmi.product.name: Inspiron 5565
  dmi.product.version: 1.0.5
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.76-1~ubuntu16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2.2~somerville2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2.2~somerville2
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.7
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1.2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2

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

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

[Desktop-packages] [Bug 1730195] Re: Launcher transparrency is applied to the top bar, invisible icons.

This actually has nothing to do with the dock/launcher.

The decision to make the panel (top bar) transparent was an upstream
decision by the Gnome guys. It's just a coincidence that the
dock/launcher is also transparent.

I don't like it either. Maybe log a new bug to disable or make the
transparency level in the panel (top bar) configurable. Or reword this
bug in that way.

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

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

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

Title:
  Launcher transparrency is applied to the top bar, invisible icons.

Status in gnome-shell package in Ubuntu:
  Invalid

Bug description:
  The new launcher in Ubuntu 17.10's gnome-shell setup has auto
  transparency... but this is also applied to the top bar, which it was
  not in Unity.

  As a result, using a light background makes the light icons in the bar
  almost invisible.

  The top bar transparency should not be linked to the launcher, and
  probably there should not be transparrency on the top bar.

  It would also be nice if there was a slider to control the level of
  transparrency in the launcher.

  See attached image of near invisible icons.

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

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

[Desktop-packages] [Bug 1703300] Re: gnome-shell crashed with SIGSEGV in g_dbus_connection_signal_unsubscribe()

Also tracking in:
https://errors.ubuntu.com/problem/2258b834217f97f59fe38634745b76a577b781d1

** Description changed:

+ https://errors.ubuntu.com/problem/2258b834217f97f59fe38634745b76a577b781d1
+ 
+ ---
+ 
  Automatically generated crash report after I switched to gdm3 and gnome-
  shell.
  
  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.24.2-0ubuntu7
  ProcVersionSignature: Ubuntu 4.10.0-26.30-generic 4.10.17
  Uname: Linux 4.10.0-26-generic x86_64
  ApportVersion: 2.20.5-0ubuntu5
  Architecture: amd64
  CurrentDesktop: GNOME-Greeter:GNOME
  Date: Sun Jul  9 19:35:05 2017
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  GsettingsChanges:
-  
+ 
  InstallationDate: Installed on 2015-05-21 (781 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150517)
  ProcCmdline: /usr/bin/gnome-shell
  SegvAnalysis:
-  Segfault happened at: 0x7fd359c8a2e2 
:  cmp(%rdx),%rax
-  PC (0x7fd359c8a2e2) ok
-  source "(%rdx)" (0x1e01) not located in a known VMA region (needed 
readable region)!
-  destination "%rax" ok
+  Segfault happened at: 0x7fd359c8a2e2 
:  cmp(%rdx),%rax
+  PC (0x7fd359c8a2e2) ok
+  source "(%rdx)" (0x1e01) not located in a known VMA region (needed 
readable region)!
+  destination "%rax" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: gnome-shell
  StacktraceTop:
-  g_dbus_connection_signal_unsubscribe () at 
/usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
-  () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
-  g_object_unref () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
-  () at /usr/lib/libgjs.so.0
-  () at /usr/lib/libgjs.so.0
+  g_dbus_connection_signal_unsubscribe () at 
/usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
+  () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
+  g_object_unref () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
+  () at /usr/lib/libgjs.so.0
+  () at /usr/lib/libgjs.so.0
  Title: gnome-shell crashed with SIGSEGV in 
g_dbus_connection_signal_unsubscribe()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

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

Title:
  gnome-shell crashed with SIGSEGV in
  g_dbus_connection_signal_unsubscribe()

Status in gnome-shell package in Ubuntu:
  Confirmed

Bug description:
  https://errors.ubuntu.com/problem/2258b834217f97f59fe38634745b76a577b781d1

  ---

  Automatically generated crash report after I switched to gdm3 and
  gnome-shell.

  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.24.2-0ubuntu7
  ProcVersionSignature: Ubuntu 4.10.0-26.30-generic 4.10.17
  Uname: Linux 4.10.0-26-generic x86_64
  ApportVersion: 2.20.5-0ubuntu5
  Architecture: amd64
  CurrentDesktop: GNOME-Greeter:GNOME
  Date: Sun Jul  9 19:35:05 2017
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  GsettingsChanges:

  InstallationDate: Installed on 2015-05-21 (781 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150517)
  ProcCmdline: /usr/bin/gnome-shell
  SegvAnalysis:
   Segfault happened at: 0x7fd359c8a2e2 
:  cmp(%rdx),%rax
   PC (0x7fd359c8a2e2) ok
   source "(%rdx)" (0x1e01) not located in a known VMA region (needed 
readable region)!
   destination "%rax" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: gnome-shell
  StacktraceTop:
   g_dbus_connection_signal_unsubscribe () at 
/usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
   () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
   g_object_unref () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   () at /usr/lib/libgjs.so.0
   () at /usr/lib/libgjs.so.0
  Title: gnome-shell crashed with SIGSEGV in 
g_dbus_connection_signal_unsubscribe()
  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/1703300/+subscriptions

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

[Desktop-packages] [Bug 1730184] Re: org.gnome.Shell.desktop[29954]: intel_do_flush_locked failed: Bad address

Please attach more of the syslog or output from 'journalctl'.

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

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

Title:
  org.gnome.Shell.desktop[29954]: intel_do_flush_locked failed: Bad
  address

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  Went to log into my fairly newly upgraded ubuntu artful system today
  but was presented with a new login instead of a login with all my
  applications running, similar to #1728474 (
  https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1728474 ),
  only I didn't have to Ctrl-Alt-F1 to get a new login, I was presented
  with one when I came to log in in the morning.

  syslog gives a clue:

  Nov  5 02:17:43 eva org.gnome.Shell.desktop[29954]: intel_do_flush_locked 
failed: Bad address
  Nov  5 02:17:44 eva gnome-shell[29954]: Connection to xwayland lost
  Nov  5 02:17:44 eva kernel: [1339701.543472] traps: gnome-shell[29954] trap 
int3 ip:7fcceb716961 sp:7ffd8b486020 error:0 in 
libglib-2.0.so.0.5400.1[7fcceb6c6000+111000]

  This, followed by everything that was running failing to various
  degrees of cleanness.

  intel-microcode:
    Installed: 3.20170707.1
    Candidate: 3.20170707.1
    Version table:
   *** 3.20170707.1 500
  500 https://gpl.savoirfairelinux.net/pub/mirrors/ubuntu 
artful/restricted amd64 Packages
  500 https://mirror.its.sfu.ca/mirror/ubuntu artful/restricted amd64 
Packages
  100 /var/lib/dpkg/status

  xserver-xorg-video-intel:
    Installed: 2:2.99.917+git20170309-0ubuntu1
    Candidate: 2:2.99.917+git20170309-0ubuntu1
    Version table:
   *** 2:2.99.917+git20170309-0ubuntu1 500
  500 https://gpl.savoirfairelinux.net/pub/mirrors/ubuntu artful/main 
amd64 Packages
  500 https://mirror.its.sfu.ca/mirror/ubuntu artful/main amd64 Packages
  100 /var/lib/dpkg/status

  libglib2.0-0:
    Installed: 2.54.1-1ubuntu1
    Candidate: 2.54.1-1ubuntu1
    Version table:
   *** 2.54.1-1ubuntu1 500
  500 https://gpl.savoirfairelinux.net/pub/mirrors/ubuntu artful/main 
amd64 Packages
  500 https://mirror.its.sfu.ca/mirror/ubuntu artful/main amd64 Packages
  100 /var/lib/dpkg/status

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.26.1-0ubuntu5
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Nov  5 07:27:04 2017
  DisplayManager: gdm3
  GsettingsChanges:
   b'org.gnome.shell' b'favorite-apps' b"['org.gnome.Nautilus.desktop', 
'libreoffice-calc.desktop', 'gnome-control-center.desktop', 
'org.gnome.Terminal.desktop', 'userapp-New Moon-YU8MZY.desktop', 
'onioncircuits.desktop', 'org.gnome.Screenshot.desktop', 'emacs25.desktop', 
'ricochet-im.desktop', 'gpa.desktop', 'org.gnome.Cheese.desktop']"
   b'org.gnome.desktop.interface' b'cursor-blink-time' b'1264'
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
  InstallationDate: Installed on 2017-04-18 (200 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  JournalErrors:
   Error: command ['journalctl', '-b', '--priority=warning', '--lines=1000'] 
failed with exit code 1: Hint: You are currently not seeing messages from other 
users and the system.
     Users in the 'systemd-journal' group can see all messages. Pass -q to
     turn off this notice.
   No journal files were opened due to insufficient permissions.
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to artful on 2017-10-19 (16 days ago)

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

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

[Desktop-packages] [Bug 1730268] Re: /usr/bin/gnome-shell:11:g_dbus_connection_signal_unsubscribe:g_dbus_proxy_finalize:g_object_unref:release_native_object:object_instance_finalize

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

** This bug has been marked a duplicate of bug 1703300
   gnome-shell crashed with SIGSEGV in g_dbus_connection_signal_unsubscribe()

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

Title:
  /usr/bin/gnome-
  
shell:11:g_dbus_connection_signal_unsubscribe:g_dbus_proxy_finalize:g_object_unref:release_native_object:object_instance_finalize

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
gnome-shell.  This problem was most recently seen with package version 
3.26.1-0ubuntu5, the problem page at 
https://errors.ubuntu.com/problem/2258b834217f97f59fe38634745b76a577b781d1 
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-shell/+bug/1730268/+subscriptions

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

[Desktop-packages] [Bug 1725190] Re: Please update modemmanager in xenial to the 1.6 series

2017-11-05 Thread Yuan-Chen Cheng

@Lukasz, do you mind that we backport zesty package to xenial first ?

Not sure how much time it takes for those Plano patch to get MM
upstream.

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

Title:
  Please update modemmanager in xenial to the 1.6 series

Status in OEM Priority Project:
  Confirmed
Status in modemmanager package in Ubuntu:
  In Progress

Bug description:
  We would like to upgrade xenial to 1.6 series so it supports the same
  modems as the modem-manager snap, specifically some new Sierra modems
  (HL8548 and others from HL series, popular in IoT devices). These are
  the packages that would need to be updated:

  libmbim: 1.12.2-2ubuntu1 in xenial, 1.14.0 in snap
  libqmi: 1.12.6-1 in xenial, 1.16.2 in snap
  modemmanager: 1.4.12-1ubuntu1 in xenial, 1.6.2 in snap

  This is also related to bug #1693756 which includes a subset of
  patches of what would be updated.

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

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

[Desktop-packages] [Bug 1730268] [NEW] /usr/bin/gnome-shell:11:g_dbus_connection_signal_unsubscribe:g_dbus_proxy_finalize:g_object_unref:release_native_object:object_instance_finalize

2017-11-05 Thread errors.ubuntu.com bug bridge

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

Public bug reported:

The Ubuntu Error Tracker has been receiving reports about a problem regarding 
gnome-shell.  This problem was most recently seen with package version 
3.26.1-0ubuntu5, the problem page at 
https://errors.ubuntu.com/problem/2258b834217f97f59fe38634745b76a577b781d1 
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-shell (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: artful wily xenial zesty

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

Title:
  /usr/bin/gnome-
  
shell:11:g_dbus_connection_signal_unsubscribe:g_dbus_proxy_finalize:g_object_unref:release_native_object:object_instance_finalize

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
gnome-shell.  This problem was most recently seen with package version 
3.26.1-0ubuntu5, the problem page at 
https://errors.ubuntu.com/problem/2258b834217f97f59fe38634745b76a577b781d1 
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-shell/+bug/1730268/+subscriptions

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

[Desktop-packages] [Bug 1726125] Re: gnome-shell crashed with SIGSEGV in g_type_check_instance_is_a() from g_dbus_connection_signal_unsubscribe()

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

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


** This bug has been marked a duplicate of bug 1703300
   gnome-shell crashed with SIGSEGV in g_dbus_connection_signal_unsubscribe()

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

Title:
  gnome-shell crashed with SIGSEGV in g_type_check_instance_is_a() from
  g_dbus_connection_signal_unsubscribe()

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  crash at startup

  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.26.1-0ubuntu4
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: GNOME-Greeter:GNOME
  Date: Sun Oct 22 21:00:49 2017
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  GsettingsChanges:
   
  ProcCmdline: /usr/bin/gnome-shell
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/false
  SegvAnalysis:
   Segfault happened at: 0x7f6a8d46b77e :
testb  $0x4,0x16(%rdx)
   PC (0x7f6a8d46b77e) ok
   source "$0x4" ok
   destination "0x16(%rdx)" (0x1e16) not located in a known VMA region 
(needed writable region)!
  SegvReason: writing NULL VMA
  Signal: 11
  SourcePackage: gnome-shell
  StacktraceTop:
   g_type_check_instance_is_a () from 
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   g_dbus_connection_signal_unsubscribe () 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_object_unref () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   ?? () from /usr/lib/libgjs.so.0
  Title: gnome-shell crashed with SIGSEGV in g_type_check_instance_is_a()
  UpgradeStatus: Upgraded to artful on 2017-10-20 (1 days ago)
  UserGroups:

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

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

[Desktop-packages] [Bug 1730091] Re: session freezes/hangs after undetermined amount of time

Please look in /var/crash for crashes. If there are none then log into a
VT (if you can - Ctrl+Alt+F4) and run:

  killall -ABRT gnome-shell

Now look in /var/crash again. And upload the file using:

  ubuntu-bug /var/crash/_my_crash_report.crash

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

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

Title:
  session freezes/hangs after undetermined amount of time

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  Currently using the default wayland session on 17.10: the computer
  eventually hangs/freezes after an undetermined amount of time, whether
  it'S still powered on and unused or when put on standby. Resuming the
  session is impossible as the device is frozen and needs to bee reset
  with power button.

  Critical bug as the issues has provoked major data loss and work in
  progress loss.

  Possibly a functional regression due to the use of wayland or the
  newer kernel provided with this release.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.26.1-0ubuntu5
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Nov  4 12:29:03 2017
  DisplayManager: gdm3
  InstallationDate: Installed on 2017-10-20 (15 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  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/1730091/+subscriptions

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

[Desktop-packages] [Bug 1720820] Re: Totem with gstreamer1.0-vaapi and Wayland is just a black screen, then crashes on AMD/radeon graphics

** Description changed:

+ WORKAROUNDS
+ 
+ Just for totem:  sudo apt remove gstreamer1.0-vaapi
+ 
+ Or to workaround in all players:  sudo apt remove mesa-va-drivers
+ 
+ 
+ ORIGINAL DESCRIPTION
+ 
  Totem with gstreamer1.0-vaapi and Wayland crashes on my machine with AMD
  Fury graphics card and open source drivers. Video output is just a black
  frame and crash happens within just a few seconds after video playback
  starts.
  
  Could not reproduce bug on two older Intel laptops with iGPU's where
  hardware acceleration seemed to work fine under Wayland.
  
  Issue is only present on Wayland, not x.
  
  I can get hardware accelerated video playback working on Wayland with
  'mpv --hwdec=vaapi-copy --opengl-backend=wayland' but this is the only
  way I have found so far. Even in mpv, no other option than vaapi-copy
  works.
  
  gst-play-1.0 outputs the following error:
  ERROR Internal error: could not render surface for file:///***
  ERROR debug information: ../../../gst/vaapi/gstvaapisink.c(1483): 
gst_vaapisink_show_frame_unlocked (): 
/GstPlayBin:playbin/GstPlaySink:playsink/GstBin:vbin/GstVaapiSink:vaapisink0
  
- 
- 
  lsb_release -rd
  Description:  Ubuntu Artful Aardvark (development branch)
  Release:  17.10
  
  totem   3.25.90.1-0ubuntu3
  gstreamer1.0-vaapi:amd641.12.3-1ubuntu1

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

Title:
  Totem with gstreamer1.0-vaapi and Wayland is just a black screen, then
  crashes on AMD/radeon graphics

Status in gstreamer-vaapi package in Ubuntu:
  Confirmed
Status in totem package in Ubuntu:
  Confirmed

Bug description:
  WORKAROUNDS

  Just for totem:  sudo apt remove gstreamer1.0-vaapi

  Or to workaround in all players:  sudo apt remove mesa-va-drivers

  
  ORIGINAL DESCRIPTION

  Totem with gstreamer1.0-vaapi and Wayland crashes on my machine with
  AMD Fury graphics card and open source drivers. Video output is just a
  black frame and crash happens within just a few seconds after video
  playback starts.

  Could not reproduce bug on two older Intel laptops with iGPU's where
  hardware acceleration seemed to work fine under Wayland.

  Issue is only present on Wayland, not x.

  I can get hardware accelerated video playback working on Wayland with
  'mpv --hwdec=vaapi-copy --opengl-backend=wayland' but this is the only
  way I have found so far. Even in mpv, no other option than vaapi-copy
  works.

  gst-play-1.0 outputs the following error:
  ERROR Internal error: could not render surface for file:///***
  ERROR debug information: ../../../gst/vaapi/gstvaapisink.c(1483): 
gst_vaapisink_show_frame_unlocked (): 
/GstPlayBin:playbin/GstPlaySink:playsink/GstBin:vbin/GstVaapiSink:vaapisink0

  lsb_release -rd
  Description:  Ubuntu Artful Aardvark (development branch)
  Release:  17.10

  totem   3.25.90.1-0ubuntu3
  gstreamer1.0-vaapi:amd641.12.3-1ubuntu1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gstreamer-vaapi/+bug/1720820/+subscriptions

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

[Desktop-packages] [Bug 1730250] Re: Location Services settings change doesn't reflect immediately

2017-11-05 Thread Bug Watch Updater

** Changed in: gnome-control-center
   Status: Unknown => Confirmed

** Changed in: gnome-control-center
   Importance: Unknown => Medium

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

Title:
  Location Services settings change doesn't reflect immediately

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

Bug description:
  In Privacy -> Location Services, clicking the toggle to either On or
  Off and then closing the dialog doesn't cause it to show a different
  value in the Privacy pane. You have to click a different pane and then
  go back to Privacy to reflect the change.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-control-center 1:3.26.1-0ubuntu5
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Nov  5 14:42:35 2017
  InstallationDate: Installed on 2017-06-20 (138 days ago)
  InstallationMedia: Ubuntu 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-control-center
  UpgradeStatus: Upgraded to artful on 2017-11-05 (0 days ago)

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

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

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

apport information

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

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

Title:
  ibus not working, Error: traps: ibus-ui-gtk3[4578] general protection
  ip:7fb85293d253 sp:7ffeecf73800 error:0 in
  libX11.so.6.3.0[7fb8528a+134000]

Status in ibus package in Ubuntu:
  Incomplete

Bug description:
  uname -a
  Linux Danny-Yoga 4.13.0-16-lowlatency #19-Ubuntu SMP PREEMPT Wed Oct 11 
19:51:52 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux

  
  lsb_release -a
  LSB Version:  
core-9.20160110ubuntu5-amd64:core-9.20160110ubuntu5-noarch:security-9.20160110ubuntu5-amd64:security-9.20160110ubuntu5-noarch
  Distributor ID:   Ubuntu
  Description:  Ubuntu 17.10
  Release:  17.10
  Codename: artful

  read-config
  SCHEMA: org.freedesktop.ibus.general
dconf-preserve-name-prefixes: ['/desktop/ibus/engine/pinyin', 
'/desktop/ibus/engine/bopomofo', '/desktop/ibus/engine/hangul']
use-system-keyboard-layout: true
embed-preedit-text: true
enable-by-default: false
use-global-engine: false
use-xmodmap: true
switcher-delay-time: 400
version: '1.5.14'
engines-order: ['libpinyin']
preload-engines: ['libpinyin', 'xkb:us::eng']
xkb-latin-layouts: ['ara', 'bg', 'cz', 'dev', 'gr', 'gur', 'in', 
'jp(kana)', 'mal', 'mkd', 'ru', 'ua']
  SCHEMA: org.freedesktop.ibus.general.hotkey
next-engine: ['Alt+Shift_L']
disable-unconditional: @as []
enable-unconditional: @as []
trigger: ['Control+space', 'Zenkaku_Hankaku', 'Alt+Kanji', 'Alt+grave', 
'Hangul', 'Alt+Release+Alt_R']
previous-engine: @as []
prev-engine: @as []
next-engine-in-menu: ['Alt+Shift_L']
triggers: ['space']
  SCHEMA: org.freedesktop.ibus.panel
x: -1
property-icon-delay-time: 500
y: -1
lookup-table-orientation: 1
show: 2
xkb-icon-rgba: '#415099'
auto-hide-timeout: 1
show-im-name: false
follow-input-cursor-when-always-shown: false
custom-font: 'Sans 10'
show-icon-on-systray: true
use-custom-font: false

  ibus engine
  xkb:us::eng

  ps -ef|grep ibus
  gdm   1969  1647  0 12:42 tty1 00:00:00 ibus-daemon --xim --panel 
disable
  gdm   1972  1969  0 12:42 tty1 00:00:00 /usr/lib/ibus/ibus-dconf
  gdm   1975 1  0 12:42 tty1 00:00:00 /usr/lib/ibus/ibus-x11 
--kill-daemon
  gdm   2046  1969  0 12:42 tty1 00:00:00 
/usr/lib/ibus/ibus-engine-simple
  hdzhong   2516  2433  0 12:42 tty2 00:00:02 ibus-daemon --xim --panel 
disable
  hdzhong   3966  2516  0 12:53 tty2 00:00:00 /usr/lib/ibus/ibus-dconf
  hdzhong   3968 1  0 12:53 tty2 00:00:00 /usr/lib/ibus/ibus-x11 
--kill-daemon
  hdzhong   3984  2516  0 12:53 tty2 00:00:00 
/usr/lib/ibus/ibus-engine-simple
  hdzhong   4198  3939  0 12:58 pts/100:00:00 grep --color=auto ibus

  dpkg:

  ii  ibus 1.5.14-2ubuntu1  amd64
Intelligent Input Bus - core
  ii  ibus-anthy   1.5.9-2  amd64anthy 
engine for IBus
  ii  ibus-clutter:amd64   0.0+git20090728.a936bacf-5.1 amd64ibus 
input method framework for clutter
  ii  ibus-gtk:amd64   1.5.14-2ubuntu1  amd64
Intelligent Input Bus - GTK+2 support
  ii  ibus-gtk3:amd64  1.5.14-2ubuntu1  amd64
Intelligent Input Bus - GTK+3 support
  ii  ibus-libpinyin   1.7.3-2  amd64
Intelligent Pinyin engine based on libpinyin for IBus
  ii  ibus-qt4 1.3.3-1  amd64
qt-immodule for ibus (QT4) (plugin)
  ii  ibus-sunpinyin   2.0.3-5build3amd64
sunpinyin engine for ibus
  ii  ibus-table   1.9.14-3 all  table 
engine for IBus
  ii  ibus-table-wubi  1.8.2-2  all  
ibus-table input method: Wubi
  ii  ibus-wayland 1.5.14-2ubuntu1  amd64
Intelligent Input Bus - Wayland support
  ii  libibus-1.0-5:amd64   1.5.14-2ubuntu1 amd64Intelligent Input Bus 
- shared library
  ii  libibus-1.0-dev:amd64 1.5.14-2ubuntu1 amd64Intelligent Input Bus 
- development file
  ii  libibus-qt1   1.3.3-1 amd64qt-immodule for ibus 
(QT4) (library)

  
  execute command: "ibus-daemon -rdx" won't fixed the issue.

  and no system tray in the topbar.
  --- 
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 17.10
  InstallationDate: Installed on 2014-05-02 (1283 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  Package: ibus 1.5.14-2ubuntu1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu

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

apport information

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

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

Title:
  ibus not working, Error: traps: ibus-ui-gtk3[4578] general protection
  ip:7fb85293d253 sp:7ffeecf73800 error:0 in
  libX11.so.6.3.0[7fb8528a+134000]

Status in ibus package in Ubuntu:
  Incomplete

Bug description:
  uname -a
  Linux Danny-Yoga 4.13.0-16-lowlatency #19-Ubuntu SMP PREEMPT Wed Oct 11 
19:51:52 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux

  
  lsb_release -a
  LSB Version:  
core-9.20160110ubuntu5-amd64:core-9.20160110ubuntu5-noarch:security-9.20160110ubuntu5-amd64:security-9.20160110ubuntu5-noarch
  Distributor ID:   Ubuntu
  Description:  Ubuntu 17.10
  Release:  17.10
  Codename: artful

  read-config
  SCHEMA: org.freedesktop.ibus.general
dconf-preserve-name-prefixes: ['/desktop/ibus/engine/pinyin', 
'/desktop/ibus/engine/bopomofo', '/desktop/ibus/engine/hangul']
use-system-keyboard-layout: true
embed-preedit-text: true
enable-by-default: false
use-global-engine: false
use-xmodmap: true
switcher-delay-time: 400
version: '1.5.14'
engines-order: ['libpinyin']
preload-engines: ['libpinyin', 'xkb:us::eng']
xkb-latin-layouts: ['ara', 'bg', 'cz', 'dev', 'gr', 'gur', 'in', 
'jp(kana)', 'mal', 'mkd', 'ru', 'ua']
  SCHEMA: org.freedesktop.ibus.general.hotkey
next-engine: ['Alt+Shift_L']
disable-unconditional: @as []
enable-unconditional: @as []
trigger: ['Control+space', 'Zenkaku_Hankaku', 'Alt+Kanji', 'Alt+grave', 
'Hangul', 'Alt+Release+Alt_R']
previous-engine: @as []
prev-engine: @as []
next-engine-in-menu: ['Alt+Shift_L']
triggers: ['space']
  SCHEMA: org.freedesktop.ibus.panel
x: -1
property-icon-delay-time: 500
y: -1
lookup-table-orientation: 1
show: 2
xkb-icon-rgba: '#415099'
auto-hide-timeout: 1
show-im-name: false
follow-input-cursor-when-always-shown: false
custom-font: 'Sans 10'
show-icon-on-systray: true
use-custom-font: false

  ibus engine
  xkb:us::eng

  ps -ef|grep ibus
  gdm   1969  1647  0 12:42 tty1 00:00:00 ibus-daemon --xim --panel 
disable
  gdm   1972  1969  0 12:42 tty1 00:00:00 /usr/lib/ibus/ibus-dconf
  gdm   1975 1  0 12:42 tty1 00:00:00 /usr/lib/ibus/ibus-x11 
--kill-daemon
  gdm   2046  1969  0 12:42 tty1 00:00:00 
/usr/lib/ibus/ibus-engine-simple
  hdzhong   2516  2433  0 12:42 tty2 00:00:02 ibus-daemon --xim --panel 
disable
  hdzhong   3966  2516  0 12:53 tty2 00:00:00 /usr/lib/ibus/ibus-dconf
  hdzhong   3968 1  0 12:53 tty2 00:00:00 /usr/lib/ibus/ibus-x11 
--kill-daemon
  hdzhong   3984  2516  0 12:53 tty2 00:00:00 
/usr/lib/ibus/ibus-engine-simple
  hdzhong   4198  3939  0 12:58 pts/100:00:00 grep --color=auto ibus

  dpkg:

  ii  ibus 1.5.14-2ubuntu1  amd64
Intelligent Input Bus - core
  ii  ibus-anthy   1.5.9-2  amd64anthy 
engine for IBus
  ii  ibus-clutter:amd64   0.0+git20090728.a936bacf-5.1 amd64ibus 
input method framework for clutter
  ii  ibus-gtk:amd64   1.5.14-2ubuntu1  amd64
Intelligent Input Bus - GTK+2 support
  ii  ibus-gtk3:amd64  1.5.14-2ubuntu1  amd64
Intelligent Input Bus - GTK+3 support
  ii  ibus-libpinyin   1.7.3-2  amd64
Intelligent Pinyin engine based on libpinyin for IBus
  ii  ibus-qt4 1.3.3-1  amd64
qt-immodule for ibus (QT4) (plugin)
  ii  ibus-sunpinyin   2.0.3-5build3amd64
sunpinyin engine for ibus
  ii  ibus-table   1.9.14-3 all  table 
engine for IBus
  ii  ibus-table-wubi  1.8.2-2  all  
ibus-table input method: Wubi
  ii  ibus-wayland 1.5.14-2ubuntu1  amd64
Intelligent Input Bus - Wayland support
  ii  libibus-1.0-5:amd64   1.5.14-2ubuntu1 amd64Intelligent Input Bus 
- shared library
  ii  libibus-1.0-dev:amd64 1.5.14-2ubuntu1 amd64Intelligent Input Bus 
- development file
  ii  libibus-qt1   1.3.3-1 amd64qt-immodule for ibus 
(QT4) (library)

  
  execute command: "ibus-daemon -rdx" won't fixed the issue.

  and no system tray in the topbar.
  --- 
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 17.10
  InstallationDate: Installed on 2014-05-02 (1283 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  Package: ibus 1.5.14-2ubuntu1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.13.0-16.19-lowlatency

[Desktop-packages] [Bug 1727174] Re: ibus not working, Error: traps: ibus-ui-gtk3[4578] general protection ip:7fb85293d253 sp:7ffeecf73800 error:0 in libX11.so.6.3.0[7fb8528a0000+134000]

apport information

** Tags added: apport-collected wayland-session

** Description changed:

  uname -a
  Linux Danny-Yoga 4.13.0-16-lowlatency #19-Ubuntu SMP PREEMPT Wed Oct 11 
19:51:52 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux
  
  
  lsb_release -a
  LSB Version:  
core-9.20160110ubuntu5-amd64:core-9.20160110ubuntu5-noarch:security-9.20160110ubuntu5-amd64:security-9.20160110ubuntu5-noarch
  Distributor ID:   Ubuntu
  Description:  Ubuntu 17.10
  Release:  17.10
  Codename: artful
  
  read-config
  SCHEMA: org.freedesktop.ibus.general
dconf-preserve-name-prefixes: ['/desktop/ibus/engine/pinyin', 
'/desktop/ibus/engine/bopomofo', '/desktop/ibus/engine/hangul']
use-system-keyboard-layout: true
embed-preedit-text: true
enable-by-default: false
use-global-engine: false
use-xmodmap: true
switcher-delay-time: 400
version: '1.5.14'
engines-order: ['libpinyin']
preload-engines: ['libpinyin', 'xkb:us::eng']
xkb-latin-layouts: ['ara', 'bg', 'cz', 'dev', 'gr', 'gur', 'in', 
'jp(kana)', 'mal', 'mkd', 'ru', 'ua']
  SCHEMA: org.freedesktop.ibus.general.hotkey
next-engine: ['Alt+Shift_L']
disable-unconditional: @as []
enable-unconditional: @as []
trigger: ['Control+space', 'Zenkaku_Hankaku', 'Alt+Kanji', 'Alt+grave', 
'Hangul', 'Alt+Release+Alt_R']
previous-engine: @as []
prev-engine: @as []
next-engine-in-menu: ['Alt+Shift_L']
triggers: ['space']
  SCHEMA: org.freedesktop.ibus.panel
x: -1
property-icon-delay-time: 500
y: -1
lookup-table-orientation: 1
show: 2
xkb-icon-rgba: '#415099'
auto-hide-timeout: 1
show-im-name: false
follow-input-cursor-when-always-shown: false
custom-font: 'Sans 10'
show-icon-on-systray: true
use-custom-font: false
  
  ibus engine
  xkb:us::eng
  
  ps -ef|grep ibus
  gdm   1969  1647  0 12:42 tty1 00:00:00 ibus-daemon --xim --panel 
disable
  gdm   1972  1969  0 12:42 tty1 00:00:00 /usr/lib/ibus/ibus-dconf
  gdm   1975 1  0 12:42 tty1 00:00:00 /usr/lib/ibus/ibus-x11 
--kill-daemon
  gdm   2046  1969  0 12:42 tty1 00:00:00 
/usr/lib/ibus/ibus-engine-simple
  hdzhong   2516  2433  0 12:42 tty2 00:00:02 ibus-daemon --xim --panel 
disable
  hdzhong   3966  2516  0 12:53 tty2 00:00:00 /usr/lib/ibus/ibus-dconf
  hdzhong   3968 1  0 12:53 tty2 00:00:00 /usr/lib/ibus/ibus-x11 
--kill-daemon
  hdzhong   3984  2516  0 12:53 tty2 00:00:00 
/usr/lib/ibus/ibus-engine-simple
  hdzhong   4198  3939  0 12:58 pts/100:00:00 grep --color=auto ibus
  
  dpkg:
  
  ii  ibus 1.5.14-2ubuntu1  amd64
Intelligent Input Bus - core
  ii  ibus-anthy   1.5.9-2  amd64anthy 
engine for IBus
  ii  ibus-clutter:amd64   0.0+git20090728.a936bacf-5.1 amd64ibus 
input method framework for clutter
  ii  ibus-gtk:amd64   1.5.14-2ubuntu1  amd64
Intelligent Input Bus - GTK+2 support
  ii  ibus-gtk3:amd64  1.5.14-2ubuntu1  amd64
Intelligent Input Bus - GTK+3 support
  ii  ibus-libpinyin   1.7.3-2  amd64
Intelligent Pinyin engine based on libpinyin for IBus
  ii  ibus-qt4 1.3.3-1  amd64
qt-immodule for ibus (QT4) (plugin)
  ii  ibus-sunpinyin   2.0.3-5build3amd64
sunpinyin engine for ibus
  ii  ibus-table   1.9.14-3 all  table 
engine for IBus
  ii  ibus-table-wubi  1.8.2-2  all  
ibus-table input method: Wubi
  ii  ibus-wayland 1.5.14-2ubuntu1  amd64
Intelligent Input Bus - Wayland support
  ii  libibus-1.0-5:amd64   1.5.14-2ubuntu1 amd64Intelligent Input Bus 
- shared library
  ii  libibus-1.0-dev:amd64 1.5.14-2ubuntu1 amd64Intelligent Input Bus 
- development file
  ii  libibus-qt1   1.3.3-1 amd64qt-immodule for ibus 
(QT4) (library)
  
  
  execute command: "ibus-daemon -rdx" won't fixed the issue.
  
  and no system tray in the topbar.
+ --- 
+ ApportVersion: 2.20.7-0ubuntu3.1
+ Architecture: amd64
+ CurrentDesktop: ubuntu:GNOME
+ DistroRelease: Ubuntu 17.10
+ InstallationDate: Installed on 2014-05-02 (1283 days ago)
+ InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
+ Package: ibus 1.5.14-2ubuntu1
+ PackageArchitecture: amd64
+ ProcVersionSignature: Ubuntu 4.13.0-16.19-lowlatency 4.13.4
+ Tags:  wayland-session artful
+ Uname: Linux 4.13.0-16-lowlatency x86_64
+ UpgradeStatus: No upgrade log present (probably fresh install)
+ UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo www-data
+ _MarkForUpload: True
+ modified.conffile..etc.dconf.db.ibus.d.00-upstream-settings: [deleted]
+ modified.conffile..etc.dconf.profile.ibus: [deleted]

** Attachment added: "Dependencies.txt"

[Desktop-packages] [Bug 1727174] JournalErrors.txt

apport information

** Attachment added: "JournalErrors.txt"
   
https://bugs.launchpad.net/bugs/1727174/+attachment/5004418/+files/JournalErrors.txt

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

Title:
  ibus not working, Error: traps: ibus-ui-gtk3[4578] general protection
  ip:7fb85293d253 sp:7ffeecf73800 error:0 in
  libX11.so.6.3.0[7fb8528a+134000]

Status in ibus package in Ubuntu:
  Incomplete

Bug description:
  uname -a
  Linux Danny-Yoga 4.13.0-16-lowlatency #19-Ubuntu SMP PREEMPT Wed Oct 11 
19:51:52 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux

  
  lsb_release -a
  LSB Version:  
core-9.20160110ubuntu5-amd64:core-9.20160110ubuntu5-noarch:security-9.20160110ubuntu5-amd64:security-9.20160110ubuntu5-noarch
  Distributor ID:   Ubuntu
  Description:  Ubuntu 17.10
  Release:  17.10
  Codename: artful

  read-config
  SCHEMA: org.freedesktop.ibus.general
dconf-preserve-name-prefixes: ['/desktop/ibus/engine/pinyin', 
'/desktop/ibus/engine/bopomofo', '/desktop/ibus/engine/hangul']
use-system-keyboard-layout: true
embed-preedit-text: true
enable-by-default: false
use-global-engine: false
use-xmodmap: true
switcher-delay-time: 400
version: '1.5.14'
engines-order: ['libpinyin']
preload-engines: ['libpinyin', 'xkb:us::eng']
xkb-latin-layouts: ['ara', 'bg', 'cz', 'dev', 'gr', 'gur', 'in', 
'jp(kana)', 'mal', 'mkd', 'ru', 'ua']
  SCHEMA: org.freedesktop.ibus.general.hotkey
next-engine: ['Alt+Shift_L']
disable-unconditional: @as []
enable-unconditional: @as []
trigger: ['Control+space', 'Zenkaku_Hankaku', 'Alt+Kanji', 'Alt+grave', 
'Hangul', 'Alt+Release+Alt_R']
previous-engine: @as []
prev-engine: @as []
next-engine-in-menu: ['Alt+Shift_L']
triggers: ['space']
  SCHEMA: org.freedesktop.ibus.panel
x: -1
property-icon-delay-time: 500
y: -1
lookup-table-orientation: 1
show: 2
xkb-icon-rgba: '#415099'
auto-hide-timeout: 1
show-im-name: false
follow-input-cursor-when-always-shown: false
custom-font: 'Sans 10'
show-icon-on-systray: true
use-custom-font: false

  ibus engine
  xkb:us::eng

  ps -ef|grep ibus
  gdm   1969  1647  0 12:42 tty1 00:00:00 ibus-daemon --xim --panel 
disable
  gdm   1972  1969  0 12:42 tty1 00:00:00 /usr/lib/ibus/ibus-dconf
  gdm   1975 1  0 12:42 tty1 00:00:00 /usr/lib/ibus/ibus-x11 
--kill-daemon
  gdm   2046  1969  0 12:42 tty1 00:00:00 
/usr/lib/ibus/ibus-engine-simple
  hdzhong   2516  2433  0 12:42 tty2 00:00:02 ibus-daemon --xim --panel 
disable
  hdzhong   3966  2516  0 12:53 tty2 00:00:00 /usr/lib/ibus/ibus-dconf
  hdzhong   3968 1  0 12:53 tty2 00:00:00 /usr/lib/ibus/ibus-x11 
--kill-daemon
  hdzhong   3984  2516  0 12:53 tty2 00:00:00 
/usr/lib/ibus/ibus-engine-simple
  hdzhong   4198  3939  0 12:58 pts/100:00:00 grep --color=auto ibus

  dpkg:

  ii  ibus 1.5.14-2ubuntu1  amd64
Intelligent Input Bus - core
  ii  ibus-anthy   1.5.9-2  amd64anthy 
engine for IBus
  ii  ibus-clutter:amd64   0.0+git20090728.a936bacf-5.1 amd64ibus 
input method framework for clutter
  ii  ibus-gtk:amd64   1.5.14-2ubuntu1  amd64
Intelligent Input Bus - GTK+2 support
  ii  ibus-gtk3:amd64  1.5.14-2ubuntu1  amd64
Intelligent Input Bus - GTK+3 support
  ii  ibus-libpinyin   1.7.3-2  amd64
Intelligent Pinyin engine based on libpinyin for IBus
  ii  ibus-qt4 1.3.3-1  amd64
qt-immodule for ibus (QT4) (plugin)
  ii  ibus-sunpinyin   2.0.3-5build3amd64
sunpinyin engine for ibus
  ii  ibus-table   1.9.14-3 all  table 
engine for IBus
  ii  ibus-table-wubi  1.8.2-2  all  
ibus-table input method: Wubi
  ii  ibus-wayland 1.5.14-2ubuntu1  amd64
Intelligent Input Bus - Wayland support
  ii  libibus-1.0-5:amd64   1.5.14-2ubuntu1 amd64Intelligent Input Bus 
- shared library
  ii  libibus-1.0-dev:amd64 1.5.14-2ubuntu1 amd64Intelligent Input Bus 
- development file
  ii  libibus-qt1   1.3.3-1 amd64qt-immodule for ibus 
(QT4) (library)

  
  execute command: "ibus-daemon -rdx" won't fixed the issue.

  and no system tray in the topbar.
  --- 
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 17.10
  InstallationDate: Installed on 2014-05-02 (1283 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  Package: ibus 1.5.14-2ubuntu1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu

[Desktop-packages] [Bug 1720820] Re: Totem with gstreamer1.0-vaapi and Wayland is just a black screen, then crashes on AMD/radeon graphics

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

** Changed in: gstreamer-vaapi (Ubuntu)
   Status: New => Confirmed

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

Title:
  Totem with gstreamer1.0-vaapi and Wayland is just a black screen, then
  crashes on AMD/radeon graphics

Status in gstreamer-vaapi package in Ubuntu:
  Confirmed
Status in totem package in Ubuntu:
  Confirmed

Bug description:
  Totem with gstreamer1.0-vaapi and Wayland crashes on my machine with
  AMD Fury graphics card and open source drivers. Video output is just a
  black frame and crash happens within just a few seconds after video
  playback starts.

  Could not reproduce bug on two older Intel laptops with iGPU's where
  hardware acceleration seemed to work fine under Wayland.

  Issue is only present on Wayland, not x.

  I can get hardware accelerated video playback working on Wayland with
  'mpv --hwdec=vaapi-copy --opengl-backend=wayland' but this is the only
  way I have found so far. Even in mpv, no other option than vaapi-copy
  works.

  gst-play-1.0 outputs the following error:
  ERROR Internal error: could not render surface for file:///***
  ERROR debug information: ../../../gst/vaapi/gstvaapisink.c(1483): 
gst_vaapisink_show_frame_unlocked (): 
/GstPlayBin:playbin/GstPlaySink:playsink/GstBin:vbin/GstVaapiSink:vaapisink0


  
  lsb_release -rd
  Description:  Ubuntu Artful Aardvark (development branch)
  Release:  17.10

  totem   3.25.90.1-0ubuntu3
  gstreamer1.0-vaapi:amd641.12.3-1ubuntu1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gstreamer-vaapi/+bug/1720820/+subscriptions

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

[Desktop-packages] [Bug 1720820] Re: Totem with gstreamer1.0-vaapi and Wayland is just a black screen, then crashes on AMD/radeon graphics

** Summary changed:

- Totem with gstreamer1.0-vaapi and Wayland crashes on AMD graphics
+ Totem with gstreamer1.0-vaapi and Wayland is just a black screen, then 
crashes on AMD/radeon graphics

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

Title:
  Totem with gstreamer1.0-vaapi and Wayland is just a black screen, then
  crashes on AMD/radeon graphics

Status in gstreamer-vaapi package in Ubuntu:
  Confirmed
Status in totem package in Ubuntu:
  Confirmed

Bug description:
  Totem with gstreamer1.0-vaapi and Wayland crashes on my machine with
  AMD Fury graphics card and open source drivers. Video output is just a
  black frame and crash happens within just a few seconds after video
  playback starts.

  Could not reproduce bug on two older Intel laptops with iGPU's where
  hardware acceleration seemed to work fine under Wayland.

  Issue is only present on Wayland, not x.

  I can get hardware accelerated video playback working on Wayland with
  'mpv --hwdec=vaapi-copy --opengl-backend=wayland' but this is the only
  way I have found so far. Even in mpv, no other option than vaapi-copy
  works.

  gst-play-1.0 outputs the following error:
  ERROR Internal error: could not render surface for file:///***
  ERROR debug information: ../../../gst/vaapi/gstvaapisink.c(1483): 
gst_vaapisink_show_frame_unlocked (): 
/GstPlayBin:playbin/GstPlaySink:playsink/GstBin:vbin/GstVaapiSink:vaapisink0


  
  lsb_release -rd
  Description:  Ubuntu Artful Aardvark (development branch)
  Release:  17.10

  totem   3.25.90.1-0ubuntu3
  gstreamer1.0-vaapi:amd641.12.3-1ubuntu1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gstreamer-vaapi/+bug/1720820/+subscriptions

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

[Desktop-packages] [Bug 1720820] Re: Totem with gstreamer1.0-vaapi and Wayland is just a black screen, then crashes on AMD/radeon graphics

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

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

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

Title:
  Totem with gstreamer1.0-vaapi and Wayland is just a black screen, then
  crashes on AMD/radeon graphics

Status in gstreamer-vaapi package in Ubuntu:
  Confirmed
Status in totem package in Ubuntu:
  Confirmed

Bug description:
  Totem with gstreamer1.0-vaapi and Wayland crashes on my machine with
  AMD Fury graphics card and open source drivers. Video output is just a
  black frame and crash happens within just a few seconds after video
  playback starts.

  Could not reproduce bug on two older Intel laptops with iGPU's where
  hardware acceleration seemed to work fine under Wayland.

  Issue is only present on Wayland, not x.

  I can get hardware accelerated video playback working on Wayland with
  'mpv --hwdec=vaapi-copy --opengl-backend=wayland' but this is the only
  way I have found so far. Even in mpv, no other option than vaapi-copy
  works.

  gst-play-1.0 outputs the following error:
  ERROR Internal error: could not render surface for file:///***
  ERROR debug information: ../../../gst/vaapi/gstvaapisink.c(1483): 
gst_vaapisink_show_frame_unlocked (): 
/GstPlayBin:playbin/GstPlaySink:playsink/GstBin:vbin/GstVaapiSink:vaapisink0


  
  lsb_release -rd
  Description:  Ubuntu Artful Aardvark (development branch)
  Release:  17.10

  totem   3.25.90.1-0ubuntu3
  gstreamer1.0-vaapi:amd641.12.3-1ubuntu1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gstreamer-vaapi/+bug/1720820/+subscriptions

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

[Desktop-packages] [Bug 1727210] Re: Totem locks up with 17.10 on AMD® E1-6010 apu with amd radeon r2 graphics × 2 (Lenovo)

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

I'm going to group this with bug 1720820 just to keep us organized and
on the same page.

If a fix for bug 1720820 arrives and this bug is not resolved then we
can un-duplicate this one.

** This bug has been marked a duplicate of bug 1720820
   Totem with gstreamer1.0-vaapi and Wayland is just a black screen, then 
crashes on AMD/radeon graphics

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

Title:
  Totem locks up with 17.10 on AMD® E1-6010 apu with amd radeon r2
  graphics × 2 (Lenovo)

Status in gstreamer-vaapi package in Ubuntu:
  New
Status in totem package in Ubuntu:
  Invalid

Bug description:
  when trying to play videos in Totum on AMD® E1-6010 apu with amd
  radeon r2 graphics × 2 (Lenovo), the timer shows it's playing but
  there is no video. After about 10 seconds I get the "Video is not
  responding" "what do you want to do" "wait/force close" window. the
  only way to close it is to force it closed. Same result with MP4 and
  FLV videos.

  totum version= 3.26.0-0ubuntu1

  Ubuntu 17.10

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gstreamer-vaapi/+bug/1727210/+subscriptions

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

[Desktop-packages] [Bug 1729998] Re: totem only shows black screen but no video

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

I'm going to group this with bug 1720820 just to keep us organized and
on the same page.

If a fix for bug 1720820 arrives and this bug is not resolved then we
can un-duplicate this one.

** This bug has been marked a duplicate of bug 1720820
   Totem with gstreamer1.0-vaapi and Wayland is just a black screen, then 
crashes on AMD/radeon graphics

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

Title:
  totem only shows black screen but no video

Status in totem package in Ubuntu:
  Incomplete

Bug description:
  After installing a fresh Ubuntu 17.10 I can't display videos with totem any 
more.
  If I double-click on an mpeg file the window is opened, sound starts but 
window stays black.

  (totem:22883): Gdk-WARNING **: Native Windows taller than 65535 pixels are 
not supported
  0:00:00.151576109 22883 0x557a6396a950 WARN basesrc 
gstbasesrc.c:3480:gst_base_src_start_complete: pad not activated yet
  0:00:00.151845987 22883 0x557a6396a950 WARN basesrc 
gstbasesrc.c:3480:gst_base_src_start_complete: pad not activated yet
  0:00:00.164796657 22883 0x557a645a2f70 WARN qtdemux 
qtdemux.c:3008:qtdemux_parse_trex: failed to find fragment defaults 
for stream 1
  0:00:00.164970079 22883 0x557a645a2f70 WARN qtdemux 
qtdemux.c:3008:qtdemux_parse_trex: failed to find fragment defaults 
for stream 2
  0:00:00.165140814 22883 0x557a645a2f70 WARN basesrc 
gstbasesrc.c:2389:gst_base_src_update_length: processing at or past EOS
  mesa: for the -simplifycfg-sink-common option: may only occur zero or one 
times!
  0:00:00.226782448 22883 0x557a645a2f70 WARNvaapidisplay 
gstvaapidisplay_wayland.c:202:gst_vaapi_display_wayland_bind_display: wayland: 
get display name
  0:00:00.467088487 22883 0x557a6396a950 WARN   totem 
bacon-video-widget.c:2074:bvw_update_tags: Pipeline sent video tags update with 
no changes

  (totem:22883): Gtk-WARNING **: Drawing a gadget with negative dimensions. Did 
you forget to allocate a size? (node slider owner GtkScale)
  0:00:00.470669545 22883 0x557a645a2ca0 ERROR  vaapi 
gstvaapitexture_egl.c:160:create_objects: failed to create VA surface from 2D 
texture 8
  0:00:00.470705390 22883 0x557a6396a950 WARNcluttervideosink 
clutter-gst-video-sink.c:1371:clutter_gst_rgb32_upload_gl:
 GL texture upload failed
  0:00:00.470714239 22883 0x557a6396a950 WARNcluttervideosink 
clutter-gst-video-sink.c:2089:clutter_gst_source_dispatch:
 Failed to upload buffer
  0:00:12.410952966 22883 0x557a63f6cb00 WARN   pulse 
pulsesink.c:702:gst_pulsering_stream_underflow_cb:
 Got underflow

  lshw -c video
*-display 
 Beschreibung: VGA compatible controller
 Produkt: Baffin [Radeon RX 460]
 Hersteller: Advanced Micro Devices, Inc. [AMD/ATI]
 Physische ID: 0
 Bus-Informationen: pci@:01:00.0
 Version: cf
 Breite: 64 bits
 Takt: 33MHz
 Fähigkeiten: pm pciexpress msi vga_controller bus_master cap_list rom
 Konfiguration: driver=amdgpu latency=0
 Ressourcen: irq:31 memory:d000-dfff memory:e000-e01f 
ioport:e000(Größe=256) memory:ef20-ef23 memory:c-d

  
  I also have issues with VLC, which I could solve by disabling the VA-API via 
DRM. 

  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/radeonsi_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: mesa gallium vaapi
  vainfo: Supported profile and entrypoints
VAProfileMPEG2Simple:   VAEntrypointVLD
VAProfileMPEG2Main  :   VAEntrypointVLD
VAProfileVC1Simple  :   VAEntrypointVLD
VAProfileVC1Main:   VAEntrypointVLD
VAProfileVC1Advanced:   VAEntrypointVLD
VAProfileH264ConstrainedBaseline:   VAEntrypointVLD
VAProfileH264ConstrainedBaseline:   VAEntrypointEncSlice
VAProfileH264Main   :   VAEntrypointVLD
VAProfileH264Main   :   VAEntrypointEncSlice
VAProfileH264High   :   VAEntrypointVLD
VAProfileH264High   :   VAEntrypointEncSlice
VAProfileHEVCMain   :   VAEntrypointVLD
VAProfileHEVCMain10 :   VAEntrypointVLD
VAProfileNone   :   VAEntrypointVideoProc

To manage notifications about this bug go to:

[Desktop-packages] [Bug 1729998] Re: totem only shows black screen but no video

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

Thanks. Please try this as a workaround for totem:

  sudo apt remove gstreamer1.0-vaapi

or this as a workaround for all players:

  sudo apt remove mesa-va-drivers

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

** Tags added: radeon

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

Title:
  totem only shows black screen but no video

Status in totem package in Ubuntu:
  Incomplete

Bug description:
  After installing a fresh Ubuntu 17.10 I can't display videos with totem any 
more.
  If I double-click on an mpeg file the window is opened, sound starts but 
window stays black.

  (totem:22883): Gdk-WARNING **: Native Windows taller than 65535 pixels are 
not supported
  0:00:00.151576109 22883 0x557a6396a950 WARN basesrc 
gstbasesrc.c:3480:gst_base_src_start_complete: pad not activated yet
  0:00:00.151845987 22883 0x557a6396a950 WARN basesrc 
gstbasesrc.c:3480:gst_base_src_start_complete: pad not activated yet
  0:00:00.164796657 22883 0x557a645a2f70 WARN qtdemux 
qtdemux.c:3008:qtdemux_parse_trex: failed to find fragment defaults 
for stream 1
  0:00:00.164970079 22883 0x557a645a2f70 WARN qtdemux 
qtdemux.c:3008:qtdemux_parse_trex: failed to find fragment defaults 
for stream 2
  0:00:00.165140814 22883 0x557a645a2f70 WARN basesrc 
gstbasesrc.c:2389:gst_base_src_update_length: processing at or past EOS
  mesa: for the -simplifycfg-sink-common option: may only occur zero or one 
times!
  0:00:00.226782448 22883 0x557a645a2f70 WARNvaapidisplay 
gstvaapidisplay_wayland.c:202:gst_vaapi_display_wayland_bind_display: wayland: 
get display name
  0:00:00.467088487 22883 0x557a6396a950 WARN   totem 
bacon-video-widget.c:2074:bvw_update_tags: Pipeline sent video tags update with 
no changes

  (totem:22883): Gtk-WARNING **: Drawing a gadget with negative dimensions. Did 
you forget to allocate a size? (node slider owner GtkScale)
  0:00:00.470669545 22883 0x557a645a2ca0 ERROR  vaapi 
gstvaapitexture_egl.c:160:create_objects: failed to create VA surface from 2D 
texture 8
  0:00:00.470705390 22883 0x557a6396a950 WARNcluttervideosink 
clutter-gst-video-sink.c:1371:clutter_gst_rgb32_upload_gl:
 GL texture upload failed
  0:00:00.470714239 22883 0x557a6396a950 WARNcluttervideosink 
clutter-gst-video-sink.c:2089:clutter_gst_source_dispatch:
 Failed to upload buffer
  0:00:12.410952966 22883 0x557a63f6cb00 WARN   pulse 
pulsesink.c:702:gst_pulsering_stream_underflow_cb:
 Got underflow

  lshw -c video
*-display 
 Beschreibung: VGA compatible controller
 Produkt: Baffin [Radeon RX 460]
 Hersteller: Advanced Micro Devices, Inc. [AMD/ATI]
 Physische ID: 0
 Bus-Informationen: pci@:01:00.0
 Version: cf
 Breite: 64 bits
 Takt: 33MHz
 Fähigkeiten: pm pciexpress msi vga_controller bus_master cap_list rom
 Konfiguration: driver=amdgpu latency=0
 Ressourcen: irq:31 memory:d000-dfff memory:e000-e01f 
ioport:e000(Größe=256) memory:ef20-ef23 memory:c-d

  
  I also have issues with VLC, which I could solve by disabling the VA-API via 
DRM. 

  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/radeonsi_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: mesa gallium vaapi
  vainfo: Supported profile and entrypoints
VAProfileMPEG2Simple:   VAEntrypointVLD
VAProfileMPEG2Main  :   VAEntrypointVLD
VAProfileVC1Simple  :   VAEntrypointVLD
VAProfileVC1Main:   VAEntrypointVLD
VAProfileVC1Advanced:   VAEntrypointVLD
VAProfileH264ConstrainedBaseline:   VAEntrypointVLD
VAProfileH264ConstrainedBaseline:   VAEntrypointEncSlice
VAProfileH264Main   :   VAEntrypointVLD
VAProfileH264Main   :   VAEntrypointEncSlice
VAProfileH264High   :   VAEntrypointVLD
VAProfileH264High   :   VAEntrypointEncSlice
VAProfileHEVCMain   :   VAEntrypointVLD
VAProfileHEVCMain10 :   VAEntrypointVLD
VAProfileNone   :   VAEntrypointVideoProc

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

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

[Desktop-packages] [Bug 1723130] Re: totem crashed with SIGSEGV in wl_proxy_add_listener()

Tracking also in:
https://errors.ubuntu.com/problem/bc6e28a2367ba53b9714f5982d0034dbd45a1fd7

** Description changed:

+ https://errors.ubuntu.com/problem/bc6e28a2367ba53b9714f5982d0034dbd45a1fd7
+ 
+ ---
+ 
  I just opened the video from nautilus with double click
  
  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: totem 3.26.0-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-0ubuntu3
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Oct 12 16:06:22 2017
  ExecutablePath: /usr/bin/totem
  InstallationDate: Installed on 2017-09-17 (24 days ago)
  InstallationMedia: It
  ProcCmdline: /usr/bin/totem --gapplication-service
  ProcEnviron:
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
   PATH=(custom, no user)
   LANG=es_ES.UTF-8
  SegvAnalysis:
   Segfault happened at: 0x7f368b77c77c : testb  
$0x4,0x28(%rdi)
   PC (0x7f368b77c77c) ok
   source "$0x4" ok
   destination "0x28(%rdi)" (0x0028) not located in a known VMA region 
(needed writable region)!
  SegvReason: writing NULL VMA
  Signal: 11
  SourcePackage: totem
  StacktraceTop:
   wl_proxy_add_listener () from 
/usr/lib/x86_64-linux-gnu/libwayland-client.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/mesa-egl/libEGL.so.1
   eglSwapBuffers () from /usr/lib/x86_64-linux-gnu/mesa-egl/libEGL.so.1
   ?? () from /usr/lib/x86_64-linux-gnu/libcogl.so.20
   cogl_onscreen_swap_buffers_with_damage () from 
/usr/lib/x86_64-linux-gnu/libcogl.so.20
  Title: totem crashed with SIGSEGV in wl_proxy_add_listener()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  XorgLog: Error: [Errno 2] No existe el archivo o el directorio: 
'/var/log/Xorg.0.log'

** Summary changed:

- totem crashed with SIGSEGV in wl_proxy_add_listener()
+ totem crashed with SIGSEGV in wl_proxy_add_listener() from 
wl_buffer_add_listener() from dri2_wl_swap_buffers_with_damage() from 
eglSwapBuffers() from _cogl_winsys_onscreen_swap_buffers_with_damage()

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

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

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

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

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

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

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

Title:
  totem crashed with SIGSEGV in wl_proxy_add_listener() from
  wl_buffer_add_listener() from dri2_wl_swap_buffers_with_damage() from
  eglSwapBuffers() from _cogl_winsys_onscreen_swap_buffers_with_damage()

Status in mesa package in Ubuntu:
  Confirmed
Status in totem package in Ubuntu:
  Confirmed
Status in wayland package in Ubuntu:
  Confirmed

Bug description:
  https://errors.ubuntu.com/problem/bc6e28a2367ba53b9714f5982d0034dbd45a1fd7

  ---

  I just opened the video from nautilus with double click

  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: totem 3.26.0-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-0ubuntu3
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Oct 12 16:06:22 2017
  ExecutablePath: /usr/bin/totem
  InstallationDate: Installed on 2017-09-17 (24 days ago)
  InstallationMedia: It
  ProcCmdline: /usr/bin/totem --gapplication-service
  ProcEnviron:
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
   PATH=(custom, no user)
   LANG=es_ES.UTF-8
  SegvAnalysis:
   Segfault happened at: 0x7f368b77c77c : testb  
$0x4,0x28(%rdi)
   PC (0x7f368b77c77c) ok
   source "$0x4" ok
   destination "0x28(%rdi)" (0x0028) not located in a known VMA region 
(needed writable region)!
  SegvReason: writing NULL VMA
  Signal: 11
  SourcePackage: totem
  StacktraceTop:
   wl_proxy_add_listener () from 
/usr/lib/x86_64-linux-gnu/libwayland-client.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/mesa-egl/libEGL.so.1
   eglSwapBuffers () from /usr/lib/x86_64-linux-gnu/mesa-egl/libEGL.so.1
   ?? () from /usr/lib/x86_64-linux-gnu/libcogl.so.20
   cogl_onscreen_swap_buffers_with_damage () from 
/usr/lib/x86_64-linux-gnu/libcogl.so.20
  Title: totem crashed with SIGSEGV in wl_proxy_add_listener()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  XorgLog: Error: [Errno 2] No existe el archivo o el directorio: 
'/var/log/Xorg.0.log'

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

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

[Desktop-packages] [Bug 1707352] Re: the change from libsane to libsane1 broke many (all?) 3rd party plug-ins for sane

2017-11-05 Thread derlybyn

@staedtler-przyborski

Thanks a lot.  This worked for my Epson Perfection V10 on Ubuntu Mate
17.10, upgraded from 17.04.

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

Title:
  the change from libsane to libsane1 broke many (all?) 3rd party plug-
  ins for sane

Status in sane-backends package in Ubuntu:
  Fix Released
Status in sane-backends source package in Artful:
  Fix Committed
Status in sane-backends package in Debian:
  New

Bug description:
  Note to SRU Team
  
  The first proposed fix (1.0.27-1~experimental2ubuntu2) failed because it 
needed to be a versioned Provides, not just a Provides.

  Impact
  ==

  1) The Debian maintainer renamed libsane to libsane1-experimental "to
  match with the soname". This apparently fixes a Lintian warning, but
  makes installing 3rd-party plug-ins hard, as they typically depend on
  "libsane", not on "libsane1". The first try to add a "Provides:
  libsane" to libsane1 (which created a virtual package) didn't make
  drivers installable that claim to depend on a minimum version of
  libsane as virtual packages are ignored in this case.

  2) The soname change might be justified by the new version breaking
  (several? most?) 3rd party plug-ins even if the library version number
  doesn't indicate any bigger change than any ordinary new version of
  the library - which might indicate that this phenomenon might be an
  upstream bug.

  libsane 1.0.25 in zesty includes libsane.so.1.25
  libsane1 1.0.27 in artful includes libsane.so.1.27

  It is to note that depending on the manufacturer for many old scanners
  there won't be new versions of the plug-ins that are recompiled like
  this.

  Test Case
  =
  Visit http://support.epson.net/linux/en/iscan_c.html
  Download the amd64 deb .tar.gz
  Unzip it.
  Install the iscan .deb from the core folder.

  It won't install before this SRU because it Depends: libsane

  Regression Potential
  
  The fix here was proposed to the Debian maintainer in July but there's been 
virtually zero response on it. In the meantime the workaround that was proposed 
initially has started to result in automatically uninstalling gtk - which makes 
the system basically useless.

  It doesn't seem like adding the Provides will make things any worse
  for third-party drivers but it has a goodme chance of making things
  better for some.

  Original Bug Report
  ===
  I don't know if that can be prevented in the long run. But both brscan (for 
my brother scanner) and iscan (for my epson scanners) have been broken by the 
change from libsane to libsane1. For iscan I have unpackaged the debian 
package, changed the dependency it contains from libsane to libsane1 and 
installed the changed package. But even then my epson scanners no more work 
leaving me without any scanner => Reporting a bug.

  Impossibility of workarounds
  
  Just installing an old version of libsane is impossible as it uninstalls 
libgtk (which depends on libsane1 which conflicts with libsane) making the 
system basically useless.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: libsane1 1.0.27-1~experimental1ubuntu2
  Uname: Linux 4.13.0-041300rc2-lowlatency x86_64
  ApportVersion: 2.20.6-0ubuntu4
  Architecture: amd64
  Date: Sat Jul 29 08:38:15 2017
  EcryptfsInUse: Yes
  SourcePackage: sane-backends
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1729887] Re: Drag-and-drop to desktop not possible without copying the file under wayland

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

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

Title:
  Drag-and-drop to desktop not possible without copying the file under
  wayland

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  since my upgrade to Ubuntu Desktop 17.10 all files moved with drag-
  and-drop from any folder to my desktop are copied but not moved.

  Using strg+x and strg+v works. When i open the desktop as a folder
  usual drag-and-drop from different folders do work without copying the
  files.

  This is wayland related. Ubuntu Desktop 17.10 with Xorg performs like
  before and allows normal drag-and-drop from folders to the desktop.

  
  (I reported the issue before at https://askubuntu.com/questions/972533/)

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

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

[Desktop-packages] [Bug 1729942] Re: /usr/bin/totem:11:_cogl_buffer_initialize:_cogl_pixel_buffer_new:cogl_pixel_buffer_new:cogl_bitmap_new_with_size:clutter_canvas_emit_draw

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

** This bug has been marked a duplicate of bug 1724255
   totem crashed with SIGSEGV in _cogl_buffer_initialize()

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

Title:
  
/usr/bin/totem:11:_cogl_buffer_initialize:_cogl_pixel_buffer_new:cogl_pixel_buffer_new:cogl_bitmap_new_with_size:clutter_canvas_emit_draw

Status in totem package in Ubuntu:
  New

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
totem.  This problem was most recently seen with package version 
3.26.0-0ubuntu1, the problem page at 
https://errors.ubuntu.com/problem/a0a2f89e4e2b7f369a7e64e26d496ce56625415d 
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/totem/+bug/1729942/+subscriptions

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

[Desktop-packages] [Bug 1724255] Re: totem crashed with SIGSEGV in _cogl_buffer_initialize()

Tracking here also:
https://errors.ubuntu.com/problem/a0a2f89e4e2b7f369a7e64e26d496ce56625415d

** Description changed:

+ https://errors.ubuntu.com/problem/a0a2f89e4e2b7f369a7e64e26d496ce56625415d
+ 
+ ---
+ 
  played 4k movie
  
  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: totem 3.26.0-0ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  NonfreeKernelModules: wl nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Oct 17 15:41:48 2017
  EcryptfsInUse: Yes
  ExecutablePath: /usr/bin/totem
  InstallationDate: Installed on 2017-09-13 (33 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170815)
  ProcCmdline: /usr/bin/totem --gapplication-service
  ProcEnviron:
-  SHELL=/bin/bash
-  XDG_RUNTIME_DIR=
-  PATH=(custom, no user)
-  LANG=sv_SE.UTF-8
+  SHELL=/bin/bash
+  XDG_RUNTIME_DIR=
+  PATH=(custom, no user)
+  LANG=sv_SE.UTF-8
  SegvAnalysis:
-  Segfault happened at: 0x7faf266e7c60:testb  $0x10,0xc0(%rsi)
-  PC (0x7faf266e7c60) ok
-  source "$0x10" ok
-  destination "0xc0(%rsi)" (0x00c0) not located in a known VMA region 
(needed writable region)!
+  Segfault happened at: 0x7faf266e7c60:testb  $0x10,0xc0(%rsi)
+  PC (0x7faf266e7c60) ok
+  source "$0x10" ok
+  destination "0xc0(%rsi)" (0x00c0) not located in a known VMA region 
(needed writable region)!
  SegvReason: writing NULL VMA
  Signal: 11
  SourcePackage: totem
  StacktraceTop:
-  ?? () from /usr/lib/x86_64-linux-gnu/libcogl.so.20
-  cogl_pixel_buffer_new () from /usr/lib/x86_64-linux-gnu/libcogl.so.20
-  cogl_bitmap_new_with_size () from /usr/lib/x86_64-linux-gnu/libcogl.so.20
-  ?? () from /usr/lib/x86_64-linux-gnu/libclutter-1.0.so.0
-  clutter_content_invalidate () from 
/usr/lib/x86_64-linux-gnu/libclutter-1.0.so.0
+  ?? () from /usr/lib/x86_64-linux-gnu/libcogl.so.20
+  cogl_pixel_buffer_new () from /usr/lib/x86_64-linux-gnu/libcogl.so.20
+  cogl_bitmap_new_with_size () from /usr/lib/x86_64-linux-gnu/libcogl.so.20
+  ?? () from /usr/lib/x86_64-linux-gnu/libclutter-1.0.so.0
+  clutter_content_invalidate () from 
/usr/lib/x86_64-linux-gnu/libclutter-1.0.so.0
  Title: totem crashed with SIGSEGV in cogl_pixel_buffer_new()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

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

Title:
  totem crashed with SIGSEGV in _cogl_buffer_initialize()

Status in totem package in Ubuntu:
  Confirmed

Bug description:
  https://errors.ubuntu.com/problem/a0a2f89e4e2b7f369a7e64e26d496ce56625415d

  ---

  played 4k movie

  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: totem 3.26.0-0ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  NonfreeKernelModules: wl nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Oct 17 15:41:48 2017
  EcryptfsInUse: Yes
  ExecutablePath: /usr/bin/totem
  InstallationDate: Installed on 2017-09-13 (33 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170815)
  ProcCmdline: /usr/bin/totem --gapplication-service
  ProcEnviron:
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
   PATH=(custom, no user)
   LANG=sv_SE.UTF-8
  SegvAnalysis:
   Segfault happened at: 0x7faf266e7c60:testb  $0x10,0xc0(%rsi)
   PC (0x7faf266e7c60) ok
   source "$0x10" ok
   destination "0xc0(%rsi)" (0x00c0) not located in a known VMA region 
(needed writable region)!
  SegvReason: writing NULL VMA
  Signal: 11
  SourcePackage: totem
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/libcogl.so.20
   cogl_pixel_buffer_new () from /usr/lib/x86_64-linux-gnu/libcogl.so.20
   cogl_bitmap_new_with_size () from /usr/lib/x86_64-linux-gnu/libcogl.so.20
   ?? () from /usr/lib/x86_64-linux-gnu/libclutter-1.0.so.0
   clutter_content_invalidate () from 
/usr/lib/x86_64-linux-gnu/libclutter-1.0.so.0
  Title: totem crashed with SIGSEGV in cogl_pixel_buffer_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/totem/+bug/1724255/+subscriptions

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

[Desktop-packages] [Bug 1729974] Re: totem crashed with SIGSEGV in wl_proxy_add_listener() from wl_buffer_add_listener() from dri2_wl_swap_buffers_with_damage() from eglSwapBuffers() from _cogl_winsys

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

** Summary changed:

- 
/usr/bin/totem:11:wl_proxy_add_listener:wl_buffer_add_listener:dri2_wl_swap_buffers_with_damage:eglSwapBuffers:_cogl_winsys_onscreen_swap_buffers_with_damage
+ totem crashed with SIGSEGV in wl_proxy_add_listener() from 
wl_buffer_add_listener() from dri2_wl_swap_buffers_with_damage() from 
eglSwapBuffers() from _cogl_winsys_onscreen_swap_buffers_with_damage()

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

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

** This bug has been marked a duplicate of bug 1723130
   totem crashed with SIGSEGV in wl_proxy_add_listener()

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

Title:
  totem crashed with SIGSEGV in wl_proxy_add_listener() from
  wl_buffer_add_listener() from dri2_wl_swap_buffers_with_damage() from
  eglSwapBuffers() from _cogl_winsys_onscreen_swap_buffers_with_damage()

Status in mesa package in Ubuntu:
  New
Status in totem package in Ubuntu:
  New
Status in wayland package in Ubuntu:
  New

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
totem.  This problem was most recently seen with package version 
3.26.0-0ubuntu1, the problem page at 
https://errors.ubuntu.com/problem/bc6e28a2367ba53b9714f5982d0034dbd45a1fd7 
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/mesa/+bug/1729974/+subscriptions

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

[Desktop-packages] [Bug 1729441] Re: changing display mode after login terminates session

You might find links to relevant crash reports from your system by
running this command in a terminal:

xdg-open "https://errors.ubuntu.com/user/"`sudo cat /var/lib/whoopsie
/whoopsie-id`

If there is a recent entry listed there for your system then please tell
us the link.

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

Title:
  changing display mode after login terminates session

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  When I login, I type the password on the laptop screen. (Maybe it's
  important.) After a while, while I'm waiting to get logged in, Ubuntu
  changes the display mode. Both monitor goes black, laptop screen
  becomes the secondary and my external monitor becomes the primary
  display. Because of Ubuntu is unable to remember to the previously set
  display mode, I usually change it a bit after I have logged in.
  However, if I (would like to) do this too quickly, say... less than
  4-5 seconds after I can see my desktop, my session gets terminated and
  I'm returned to the login screen. You can repeat it indefinitely, it
  always worked for me.

  I thought it's because of one of my extensions but I could reproduce it after 
I have disabled them.
  I haven't found any useful log entries.

  
  UPDATE 1:
  While I was writing this, I thought it has something to do with theme loading 
or something like this, so I continued to test with startup applications.
  I just rarely managed to reproduce this bug when I didn't execute the 
following script (as a file) at login:
  ```
  #!/bin/bash
  sleep 1s; firefox &
  sleep 1s; thunderbird &
  ```

  I also noticed that after I have some faulty logins and then I login
  without changing display mode, I >sometimes< have no desktop, no
  startup applications and when I click power off/logout buttons nothing
  happens, but that's sure I will being logged out randomly in the near
  future - even if I don't touch my computer (I'm talking about
  minutes).

  Plus, I can see the desktop and the top bar (so it's the primary
  screen) with two wide black bars on the two sides of my laptop monitor
  for a moment before I get logged out. (However, I don't see any
  resolution changes so I guess it's not 640x480, or 800x600, etc.)

  
  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.26.1-0ubuntu5
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  NonfreeKernelModules: vtsspp sep4_1 socperf2_0 pax
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Wed Nov  1 21:00:45 2017
  DisplayManager: gdm3
  InstallationDate: Installed on 2017-08-08 (85 days ago)
  InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412)
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to artful on 2017-10-21 (10 days ago)

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

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

[Desktop-packages] [Bug 1730116] Re: gstreamer's flac encoder creates corrupt files with sound-juicer

2017-11-05 Thread Bug Watch Updater

** Changed in: gst-plugins-good
   Status: Unknown => Confirmed

** Changed in: gst-plugins-good
   Importance: Unknown => Critical

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

Title:
  gstreamer's flac encoder creates corrupt files with sound-juicer

Status in gst-plugins-good:
  Confirmed
Status in gst-plugins-good1.0 package in Ubuntu:
  New

Bug description:
  When ripping a CD to the FLAC format with Sound Juicer (and based on
  the upstream bug also Rhythmbox, and maybe also affects other
  applications), it creates corrupted files (e.g. when you test them
  with "flac -t").

To manage notifications about this bug go to:
https://bugs.launchpad.net/gst-plugins-good/+bug/1730116/+subscriptions

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

[Desktop-packages] [Bug 1729028] Re: gnome-shell crashes after period of inactivity

Echo: Please don't attach crash files to bugs. You can upload them
securely and in a way we can process by running 'ubuntu-bug
/var/crash/_my_crash_report.crash'. That will also create a new bug for
you.

** Attachment removed: "Apport .crash file"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1729028/+attachment/5004296/+files/_usr_bin_gnome-shell.1000.crash

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

Title:
  gnome-shell crashes after period of inactivity

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  Gnome shell crashes reliably and only after a period of inactivity
  (15+ minutes). I have not seen it crash while using the desktop - even
  for hours at a time. I suspect it has something to do with locking the
  screen or turning off the monitor. However even after attempting to
  disable both lockscreen and blank screen it still happens.

  After a crash dmesg shows [ 3726.608957] gnome-shell[2666]: segfault
  at 38 ip 7fc6a7330c30 sp 7fff0d12fe78 error 4 in
  libmutter-1.so.0.0.0[7fc6a72de000+141000]

  When the crash happens it goes back to the login screen. Logging in
  works fine.

  It happens pretty reliably but will sometimes successfully lock and
  blank the screen. I would say it happens 90% of the time I leave the
  computer alone for awhile.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.26.1-0ubuntu5
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Oct 31 11:34:11 2017
  DisplayManager: gdm3
  GsettingsChanges:
   b'org.gnome.shell' b'favorite-apps' b"['org.gnome.Nautilus.desktop', 
'google-chrome.desktop', 'firefox.desktop', 'code.desktop', 
'org.gnome.Terminal.desktop', 'libreoffice-writer.desktop', 
'libreoffice-calc.desktop', 'libreoffice-impress.desktop', 
'org.gnome.Software.desktop', 'gnome-control-center.desktop']"
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
   b'org.gnome.desktop.interface' b'clock-format' b"'12h'"
   b'org.gnome.desktop.interface' b'text-scaling-factor' b'1.25'
  InstallationDate: Installed on 2017-07-18 (105 days ago)
  InstallationMedia: Ubuntu 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-shell
  UpgradeStatus: Upgraded to artful on 2017-10-18 (12 days ago)

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

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

[Desktop-packages] [Bug 1728778] Re: Touchpad not working after resuming from suspend

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

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

Title:
  Touchpad not working after resuming from suspend

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

Bug description:
  I am using ubuntu 17.10 (intel i3, 16gb ram ). my mouse doesn't works
  once I have suspended the pc when i close the lid and reopens it

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

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

[Desktop-packages] [Bug 1728455] Re: Inputting in Chrome URL Bar Triggering UI Freeze, pegged CPU and Major Memory Leak

** Changed in: gnome-shell (Ubuntu)
   Importance: Undecided => 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/1728455

Title:
  Inputting in Chrome URL Bar Triggering UI Freeze, pegged CPU and Major
  Memory Leak

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

Bug description:
  OS: Ubuntu 17.10 (Linux weilong-Ubuntu 4.13.0-16-generic #19-Ubuntu
  SMP Wed Oct 11 18:35:14 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux)

  GNOME version: GNOME Shell 3.26.1
  Chrome version: Version 62.0.3202.75 (Official Build) (64-bit)

  Description:

  This may very likely have something to do with my Chinese input method
  (iBus). I encounter this consistently while the system input method is
  Chinese (WubiHaifeng86) but the mode within the input method is
  English.

  Inputting in Chrome URL bar is triggering UI freeze and major memory
  meak. The whole UI freezes and won't respond to either mouse or
  keyboard. Can't switch to console by Ctrl+Alt+Fx. Was able to ssh in
  from another machine and gather information.

  Reproduce Steps:

  1. Switch system input method to Chinese (WubiHaifeng86)
  2. Switch to English inputting mode (while system input method is still 
Chinese).
  3. Open Chrome
  4. Input some characters in URL bar and the bug should occur. If not, use 
Backspace to delete some and input some more.

  (Sometimes swapping step 2 and 3 might help reproduce the issue.)

  Some info:

  top:

  top - 11:35:02 up 23 min,  3 users,  load average: 2.70, 2.10, 1.20
  Tasks: 221 total,   4 running, 217 sleeping,   0 stopped,   0 zombie
  %Cpu(s): 59.1 us,  2.9 sy,  0.0 ni, 37.9 id,  0.0 wa,  0.0 hi,  0.1 si,  0.0 
st
  KiB Mem :  8161428 total,  1386928 free,  5591952 used,  1182548 buff/cache
  KiB Swap:   472404 total,   472404 free,0 used.  2244372 avail Mem 

PID USER  PR  NIVIRTRESSHR S  %CPU %MEM TIME+ COMMAND   

870 weilong   20   0 7634048 3.726g 100292 R 116.9 47.9   6:50.39 
gnome-shell 
  
   1376 weilong   20   0  399472  40320   8032 R  91.0  0.5   4:19.32 
ibus-daemon 
  
   1591 weilong   20   0  273556  32908  14976 S  26.2  0.4   1:18.30 python3   

   1805 weilong   20   0 1513112 260204 119888 S  10.6  3.2   1:35.11 chrome

256 root  20   0   88024  13660  12756 S   1.3  0.2   0:05.23 
systemd-journal 
  
922 weilong   20   0  732384  66480  53788 S   1.3  0.8   0:21.74 Xwayland  

   2211 weilong   20   0 1316096 169220  58552 S   1.0  2.1   0:13.77 chrome

   2078 weilong   20   0 1164120  99948  59080 S   0.7  1.2   0:06.08 chrome

 35 root  20   0   0  0  0 S   0.3  0.0   0:02.60 
kworker/2:1

  syslogs:

  Oct 29 12:58:59 weilong-Ubuntu google-chrome.desktop[10633]: Created new 
window in existing browser session.
  Oct 29 12:59:21 weilong-Ubuntu org.gnome.Shell.desktop[5354]: Key repeat 
discarded, Wayland compositor doesn't seem to be processing events fast enough!
  Oct 29 12:59:24 weilong-Ubuntu org.gnome.Shell.desktop[5354]: message 
repeated 105 times: [ Key repeat discarded, Wayland compositor doesn't seem to 
be processing events fast enough!]
  Oct 29 12:59:24 weilong-Ubuntu org.gnome.Shell.desktop[5354]: Key repeat 
discarded, Wayland compositor doesn't seem to be processing events fast enough!
  ^C

  This bug is also reported to
  https://bugzilla.gnome.org/show_bug.cgi?id=789634

  A screenshot seconds before the issue occurs is attached. Notice at
  the right top corner, the system input method is Chinese but in
  English inputting mode (showing a "英" character to indicate English
  inputting mode with Chinese Input method selected)

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.26.1-0ubuntu5
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Oct 29 14:45:33 2017
  DisplayManager: gdm3
  GsettingsChanges:
   b'org.gnome.shell' b'command-history' b"['ubuntu-bug gnome', 'ubuntu-bug 
gnome-shell']"
   b'org.gnome.shell' b'app-picker-view' b'uint32 1'
   b'org.gnome.shell'

[Desktop-packages] [Bug 1719322] Re: Remove patch to remove headerbar

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

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

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

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

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

Title:
  Remove patch to remove headerbar

Status in eog package in Ubuntu:
  Triaged
Status in epiphany-browser package in Ubuntu:
  Fix Released
Status in evince package in Ubuntu:
  Triaged
Status in file-roller package in Ubuntu:
  Triaged
Status in gnome-contacts package in Ubuntu:
  Fix Released
Status in totem package in Ubuntu:
  In Progress

Bug description:
  As of Artful, it seems that there are still patches against various
  apps that remove/replace the Gtk.HeaderBar with a Gtk.Toolbar.

  Now that GNOME Shell is default in Ubuntu and there is better support
  for client-side decorations, these patches can probably go away

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

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

[Desktop-packages] [Bug 1727958] Re: In Ubuntu 17.10 Libreoffice writer / calc etc show as white icon in launcher when opened

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

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

Title:
  In Ubuntu 17.10 Libreoffice writer / calc etc show as white icon in
  launcher when opened

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

Bug description:
  Running Liboreoffice 5.4.2.2 in Ubuntu 17.10, there is an issue with
  the application's icons. The individual icons show up in the list of
  programs, and can be docked in the launcher - but a generic white
  libreoffice icon also shows up in the program list, and if any of the
  docked, correct, icons are clicked, a new, white icon appears that is
  generic across all libreoffice windows (e.g. if I have open writer and
  calc, the white icon gets two red dots and to access either the writer
  or calc window I have to click on the generic icon). This is annoying
  but not crippling, and not solved by a purge and reinstall.

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

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

[Desktop-packages] [Bug 1728188] Re: Don't build pulseaudio with trust-store support

Sounds good.

I am working on releasing 11.1 first (since I have ported the trust
store work over now, it's building and not a blocker). Then expect other
changes like this one can be patched soon after.

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

Title:
  Don't build pulseaudio with trust-store support

Status in pulseaudio package in Ubuntu:
  Triaged

Bug description:
  Please check whether we still need to build pulseaudio with trust-
  store support or if we can drop it and remove trust-store from Ubuntu.

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

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

[Desktop-packages] [Bug 1718654] Re: Touchpad input doesn't work after longer suspend.

Jonathan, that confirms you have a kernel issue.

The direction of this bug however depends on what saviq says...

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

Title:
  Touchpad input doesn't work after longer suspend.

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  When I resume my laptop from a longer (not sure what the threshold is
  yet) suspend, I don't get input from the touchpad, a short suspend
  cycle fixes it.

  Touchscreen works all the time.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.26.0-0ubuntu1
  ProcVersionSignature: Ubuntu 4.12.0-13.14-generic 4.12.10
  Uname: Linux 4.12.0-13-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Sep 21 14:20:56 2017
  DisplayManager: gdm3
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1722479] Re: Dock and panel are different opacity/transparency/colour

Thanks but your screenshot shows the problem is now reversed (lighter
panel and darker dock :).

Close, but still not quite right. We may need to change the actual
colour too/instead.

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

Title:
  Dock and panel are different opacity/transparency/colour

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

Bug description:
  Dock and panel are different opacity/transparency/colour

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell-extension-ubuntu-dock 0.7
  ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3
  Uname: Linux 4.13.0-12-generic x86_64
  ApportVersion: 2.20.7-0ubuntu2
  Architecture: amd64
  Date: Tue Oct 10 16:27:07 2017
  InstallationDate: Installed on 2017-05-03 (160 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170502)
  PackageArchitecture: all
  SourcePackage: gnome-shell-extension-ubuntu-dock
  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/1722479/+subscriptions

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

[Desktop-packages] [Bug 1709994] Re: gnome-shell crashes often on unlock / resume from suspend

Stefan, please open a new bug for yourself. There are many root causes
of such crashes and it would be wrong to assume you have the exact same
bug based on the short title of this bug.

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

Title:
  gnome-shell crashes often on unlock / resume from suspend

Status in gnome-shell package in Ubuntu:
  Expired

Bug description:
  It happens very frequently that, after resuming from suspend, as soon
  as I enter my password into GDM, gnome-shell crashes.  I initially see
  my windows appear for a moment (with titlebars, etc.), then gnome-
  shell crashes, the titlebars disappear, and I am unable to do interact
  with any windows.  Eventually gnome-shell restarts itself and the
  titlebars and functionality are restored.

  This doesn't happen 100% of the time, and I have not been able to find
  any correlation.  In my syslog, I see lines like:

  Aug 10 14:30:49 hermes org.gnome.Shell.desktop[5325]: Window manager warning: 
Failed to set power save mode for output VGA-1: Permission denied
  Aug 10 14:30:49 hermes org.gnome.Shell.desktop[5325]: Window manager warning: 
Failed to set power save mode for output eDP-1: Permission denied
  Aug 10 14:30:58 hermes gnome-session[6503]: gnome-session-binary[6503]: 
WARNING: Application 'org.gnome.Shell.desktop' killed by signal 6
  Aug 10 14:30:58 hermes gnome-session-binary[6503]: WARNING: Application 
'org.gnome.Shell.desktop' killed by signal 6

  
  This is on Ubuntu 17.04, gnome-shell 3.24.2-0ubuntu0.1, under Xorg with Intel 
HD 4600 graphics.  I experience the same crashes under Wayland, making it 
*completely* unusable.  At least under X I can still recover my session.

  This is particularly annoying because whenever gnome-shell dies, it
  triggers a separate issue that kills all active Firefox content
  processes, requiring me to restart Firefox as well.

  If there's a way to get some better debugging info for this, please
  let me know.

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

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

Re: [Desktop-packages] [Bug 1709708] Re: [Intel Broxton HDMI, Digital Out, HDMI] Pulseaudio detects output but produces no sound on an HDMI TV until power cycled.

2017-11-05 Thread Kai-Heng Feng

> On 4 Nov 2017, at 7:29 PM, Rael Gugelmin Cunha  wrote:
> 
> I'm using the X-Swat PPA
> (https://launchpad.net/~ubuntu-x-swat/+archive/ubuntu/updates) with mesa
> 17.2.3-0ubuntu0~16.04.0. Should I purge it in order to receive the fix?

This fix comes from kernel side, so downgrade Mesa or not should not affect it.
> 
> -- 
> You received this bug notification because you are subscribed to linux
> in Ubuntu.
> https://bugs.launchpad.net/bugs/1709708
> 
> Title:
>  [Intel Broxton HDMI, Digital Out, HDMI] Pulseaudio detects output but
>  produces no sound on an HDMI TV until power cycled.
> 
> Status in DRI:
>  Fix Released
> Status in linux package in Ubuntu:
>  Triaged
> Status in pulseaudio package in Ubuntu:
>  Invalid
> 
> Bug description:
>  Upon bootup, the HDMI output connected to a Samsung TV shows up as an
>  output. If this output is selected and a sound test run (either using
>  the GUI or using aplay /user/share/sounds/alsa/Front_Center.wav) no
>  sound is heard. Pavumeter does however show sound coming through.
> 
>  I found that sound can be fixed by allowing the display to sleep,
>  waking it up, and then restarting pulseaudio (pulseaudio -k). After
>  that sound output through HDMI to the TV will work until rebooted.
> 
>  The fix can be succesfully scripted as follows:
> 
>  xset dpms force off
>  sleep 1
>  pulseaudio -k
> 
>  The machine is an Intel NUC6CAYH, connected to a not particularly new
>  Samsung 42" TV using an HDMI cable, running a fresh install of Ubuntu
>  16.04.
> 
>  In earlier attempts at fixing the issue I set pulseaudio to never let
>  the sound device sleep (commented out load-module module-suspend-on-
>  idle in /etc/pulse/default.pa), and also set the default sampling rate
>  to 48000 (default-sample-rate = 48000 in /etc/pulse/daemon.conf). Not
>  sure if these settings contributed to the fix, but they are not
>  sufficient on their own.
> 
>  ProblemType: Bug
>  DistroRelease: Ubuntu 16.04
>  Package: pulseaudio 1:8.0-0ubuntu3.3
>  ProcVersionSignature: Ubuntu 4.10.0-30.34~16.04.1-generic 4.10.17
>  Uname: Linux 4.10.0-30-generic x86_64
>  ApportVersion: 2.20.1-0ubuntu2.10
>  Architecture: amd64
>  Date: Wed Aug  9 21:48:39 2017
>  InstallationDate: Installed on 2017-08-06 (2 days ago)
>  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
> (20170801)
>  SourcePackage: pulseaudio
>  Symptom: audio
>  Symptom_Card: HDA-Intel - HDA Intel PCH
>  Symptom_Jack: Digital Out, HDMI
>  Title: [, Intel Broxton HDMI, Digital Out, HDMI] Pulseaudio fails to detect 
> card
>  UpgradeStatus: No upgrade log present (probably fresh install)
>  dmi.bios.date: 11/24/2016
>  dmi.bios.vendor: Intel Corp.
>  dmi.bios.version: AYAPLCEL.86A.0029.2016.1124.1625
>  dmi.board.name: NUC6CAYB
>  dmi.board.vendor: Intel Corporation
>  dmi.board.version: J23203-402
>  dmi.chassis.type: 3
>  dmi.modalias: 
> dmi:bvnIntelCorp.:bvrAYAPLCEL.86A.0029.2016.1124.1625:bd11/24/2016:svn:pn:pvr:rvnIntelCorporation:rnNUC6CAYB:rvrJ23203-402:cvn:ct3:cvr:
>  modified.conffile..etc.pulse.daemon.conf: [modified]
>  modified.conffile..etc.pulse.default.pa: [modified]
>  mtime.conffile..etc.pulse.daemon.conf: 2017-08-06T22:55:35.510382
>  mtime.conffile..etc.pulse.default.pa: 2017-08-06T22:51:49.639085
> 
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/dri/+bug/1709708/+subscriptions

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

Title:
  [Intel Broxton HDMI, Digital Out, HDMI] Pulseaudio detects output but
  produces no sound on an HDMI TV until power cycled.

Status in DRI:
  Fix Released
Status in linux package in Ubuntu:
  Triaged
Status in pulseaudio package in Ubuntu:
  Invalid

Bug description:
  Upon bootup, the HDMI output connected to a Samsung TV shows up as an
  output. If this output is selected and a sound test run (either using
  the GUI or using aplay /user/share/sounds/alsa/Front_Center.wav) no
  sound is heard. Pavumeter does however show sound coming through.

  I found that sound can be fixed by allowing the display to sleep,
  waking it up, and then restarting pulseaudio (pulseaudio -k). After
  that sound output through HDMI to the TV will work until rebooted.

  The fix can be succesfully scripted as follows:

  xset dpms force off
  sleep 1
  pulseaudio -k

  The machine is an Intel NUC6CAYH, connected to a not particularly new
  Samsung 42" TV using an HDMI cable, running a fresh install of Ubuntu
  16.04.

  In earlier attempts at fixing the issue I set pulseaudio to never let
  the sound device sleep (commented out load-module module-suspend-on-
  idle in /etc/pulse/default.pa), and also set the default sampling rate
  to 48000 (default-sample-rate = 48000 in /etc/pulse/daemon.conf). Not
  sure if these settings contributed to the fix, but they are not
  sufficient on their own.

  ProblemType: Bug

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

2017-11-05 Thread luca.mg

Hi staedtler-przyborski, I created the /etc/udev/rules.d/79-udev-
brother.rules file as suggested, no joy. I have written to Brother
support, asking if they're planning the release of drivers libsane1
compliant; I've had an automatic reply suggesting to install the non
working driver... hope I'll get a proper answer anytime soon, I fear
they won't support legacy hardware, but they should indeed support
recent products.

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

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

Status in sane-backends package in Ubuntu:
  Confirmed

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

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

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

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

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

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

[Desktop-packages] [Bug 1551385] Re: No sound on ASUS Xonar DGX Soundcard (16.04)

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

** Tags added: xenial

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

Title:
  No sound on ASUS Xonar DGX Soundcard (16.04)

Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  Hello,
  On Ubuntu 16.04 LTS (Alpha), with the latest package updates (28/02/2015), 
Linux 4.4 and PulseAudio 8.0, I can't play any sound on my ASUS Xonar DGX. 
Tested with the app to test speakers, Firefox, VLC, and checked with 
pavucontrol, the progress bar indicate that a sound is played on the card, but 
no sound on the speakers.

  I report this bug because it works on the same version with the
  integrated card of my motherboard. (ASUS H87-PLUS)

  On Ubuntu 14.04 (PulseAudio 4.0), the sound work correctly (with all
  defaults params)

  The speakers connected are the Logitech Z9600 (by 3 jacks), and I
  precise that they are correctly plugged in, etc..., it works when I
  connect it to the integrated sound card of my motherboard (and if I
  use Ubuntu 14.04 LTS)

  I don't know if it's a normal development bug, but in doubt I report it.
  Thank you,
  Valentin Crône

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

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

[Desktop-packages] [Bug 1574667] Re: Mouse pointer occasionally jumps to the bottom-left corner

2017-11-05 Thread ChrisC

#32 seems to be the best work around. Thanks Juan! Mint 18.2 (New
Build).

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

Title:
  Mouse pointer occasionally jumps to the bottom-left corner

Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  Sometimes the mouse pointer jumps directly to the bottom-left corner
  of the screen, which results in opening the trash window when
  clicking.

  This seems to be related: https://ubuntu-mate.community/t/mouse-
  pointer-jumps-on-clicking-touchpad/2932.

  Thanks,
  MZ

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  BootLog: /dev/sda6: clean, 276587/40779776 files, 15261626/163117056 blocks
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Mon Apr 25 15:55:54 2016
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  EcryptfsInUse: Yes
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation Sky Lake Integrated Graphics [8086:1916] (rev 07) (prog-if 
00 [VGA controller])
 Subsystem: Dell Skylake Integrated Graphics [1028:06b2]
  InstallationDate: Installed on 2016-04-23 (2 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 8087:07dc Intel Corp. 
   Bus 001 Device 003: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card 
Reader Controller
   Bus 001 Device 002: ID 064e:920b Suyin Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Inspiron 5559
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-21-generic.efi.signed 
root=UUID=c5bc0a1d-3fe9-4ae5-81e9-de7d141b419c ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/21/2015
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.1.5
  dmi.board.name: 06CMH7
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.1.5:bd12/21/2015:svnDellInc.:pnInspiron5559:pvr:rvnDellInc.:rn06CMH7:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: Inspiron 5559
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.12.2+16.04.20160415-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.67-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Mon Apr 25 13:43:44 2016
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id1156 
   vendor LGD
  xserver.version: 2:1.18.3-1ubuntu2

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

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

[Desktop-packages] [Bug 1730196] Re: system slowness, delayed response, mouse stuttered movement

2017-11-05 Thread Gustavo Silva

If that is the case, I propose changing the affecting package to Polari
and not Firefox.

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

Title:
  system slowness, delayed response, mouse stuttered movement

Status in firefox package in Ubuntu:
  New

Bug description:
  After leaving Ubuntu 17.10 on and running on my Asus laptop for over 24 hours 
I found the whole system performing poorly.
  The only applications I have left running are FireFox, Terminal, and Polari. 
Skype might be running in the background.

  The system is slow and delayed in it's response, the mouse stutters as
  it moves across the desktop.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: firefox 56.0+build6-0ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  AddonCompatCheckDisabled: False
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  mptz991 F pulseaudio
   /dev/snd/controlC0:  mptz991 F pulseaudio
  BuildID: 20171003222101
  Channel: Unavailable
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Nov  5 09:31:21 2017
  ExecutablePath: /usr/lib/firefox/firefox
  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-10-29 (7 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  IpRoute:
   default via 192.168.0.1 dev wlp3s0 proto static metric 600 
   169.254.0.0/16 dev wlp3s0 scope link metric 1000 
   192.168.0.0/24 dev wlp3s0 proto kernel scope link src 192.168.0.106 metric 
600
  Locales: extensions.sqlite corrupt or missing
  PrefSources: prefs.js
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  Profiles: Profile0 (Default) - LastVersion=56.0/20171003222101 (In use)
  RunningIncompatibleAddons: False
  SourcePackage: firefox
  Themes: extensions.sqlite corrupt or missing
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/16/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: Q550LF.215
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: Q550LF
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrQ550LF.215:bd06/16/2014:svnASUSTeKCOMPUTERINC.:pnQ550LF:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnQ550LF:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: Q
  dmi.product.name: Q550LF
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

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

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

[Desktop-packages] [Bug 1730254] [NEW] Gnome Shell or X disappears with last log message _st_paint_shadow_with_opacity: assertion 'shadow_pipeline != NULL' failed

2017-11-05 Thread Michal Pasniewski

Public bug reported:

gnome-shell or X is disappearing (crashing?), with frequency of roughly 1 time 
per 2 days.  This last time it happened when my partner was switching users (we 
have 2 users on this box "Beast").  This is a new Ubuntu 17.10 setup on 
i7700/NVidia 1060 with 3 monitors plugged to 1060.  The symptom is black screen 
with lines like 
[   OK   ] Started User Manager for UID 121
and unresponsive keyboard.  

Hard drive was blinking so I tried and I was able to SSH into the
machine and run ubuntu-bug.

The log (tail -c4000 syslog) is:

Nov  5 18:19:19 Beast gnome-shell[2285]: message repeated 551 times: [ 
[AppIndicatorSupport-WARN] Attempting to re-register 
:1.55/org/ayatana/NotificationItem/multiload; resetting instead]
Nov  5 18:19:19 Beast gnome-software[2521]: no app for changed 
sensory-percept...@harlemsquirrel.github.io
Nov  5 18:19:19 Beast gnome-software[2521]: no app for changed 
ubuntu-appindicat...@ubuntu.com
Nov  5 18:19:19 Beast gnome-shell[2285]: ../../../../gobject/gsignal.c:2641: 
instance '0x55c34fa62bb0' has no handler with id '3872875'
Nov  5 18:19:19 Beast gnome-shell[2285]: ../../../../gobject/gsignal.c:2641: 
instance '0x55c34fa62bb0' has no handler with id '3872876'
Nov  5 18:19:19 Beast gnome-software[2521]: no app for changed 
ubuntu-d...@ubuntu.com
Nov  5 18:19:19 Beast /usr/lib/gdm3/gdm-x-session[2134]: (**) Option "fd" "73"
Nov  5 18:19:19 Beast /usr/lib/gdm3/gdm-x-session[2134]: (II) event2  - (II) 
Power Button: (II) device removed
Nov  5 18:19:19 Beast /usr/lib/gdm3/gdm-x-session[2134]: (**) Option "fd" "43"
Nov  5 18:19:19 Beast /usr/lib/gdm3/gdm-x-session[2134]: (II) event0  - (II) 
Sleep Button: (II) device removed
Nov  5 18:19:19 Beast /usr/lib/gdm3/gdm-x-session[2134]: (**) Option "fd" "42"
Nov  5 18:19:19 Beast /usr/lib/gdm3/gdm-x-session[2134]: (II) event1  - (II) 
Power Button: (II) device removed
Nov  5 18:19:19 Beast /usr/lib/gdm3/gdm-x-session[2134]: (**) Option "fd" "45"
Nov  5 18:19:19 Beast /usr/lib/gdm3/gdm-x-session[2134]: (II) event4  - (II) 
Logitech Logitech G710 Keyboard: (II) device removed
Nov  5 18:19:19 Beast /usr/lib/gdm3/gdm-x-session[2134]: (**) Option "fd" "46"
Nov  5 18:19:19 Beast /usr/lib/gdm3/gdm-x-session[2134]: (II) event5  - (II) 
Logitech M570: (II) device removed
Nov  5 18:19:19 Beast /usr/lib/gdm3/gdm-x-session[2134]: (**) Option "fd" "44"
Nov  5 18:19:19 Beast /usr/lib/gdm3/gdm-x-session[2134]: (II) event3  - (II) 
Logitech Logitech G710 Keyboard: (II) device removed
Nov  5 18:19:19 Beast /usr/lib/gdm3/gdm-x-session[2134]: (**) Option "fd" "74"
Nov  5 18:19:19 Beast /usr/lib/gdm3/gdm-x-session[2134]: (II) event18 - (II) 
Media Center Ed. eHome Infrared Remote Transceiver (0471:2093): (II) device 
removed
Nov  5 18:19:21 Beast gsd-rfkill[2407]: g_object_notify: object class 
'CcRfkillGlib' has no property named 'kernel-noinput'
Nov  5 18:19:21 Beast kernel: [45693.199078] rfkill: input handler enabled
Nov  5 18:19:21 Beast /usr/lib/gdm3/gdm-x-session[2134]: (II) systemd-logind: 
got pause for 13:66
Nov  5 18:19:21 Beast /usr/lib/gdm3/gdm-x-session[2134]: (II) systemd-logind: 
got pause for 13:65
Nov  5 18:19:21 Beast /usr/lib/gdm3/gdm-x-session[2134]: (II) systemd-logind: 
got pause for 13:64
Nov  5 18:19:21 Beast /usr/lib/gdm3/gdm-x-session[2134]: (II) systemd-logind: 
got pause for 13:67
Nov  5 18:19:21 Beast /usr/lib/gdm3/gdm-x-session[2134]: (II) systemd-logind: 
got pause for 13:69
Nov  5 18:19:21 Beast /usr/lib/gdm3/gdm-x-session[2134]: (II) systemd-logind: 
got pause for 13:68
Nov  5 18:19:21 Beast /usr/lib/gdm3/gdm-x-session[2134]: (II) systemd-logind: 
got pause for 13:82
Nov  5 18:19:22 Beast acpid: client 2136[0:0] has disconnected
Nov  5 18:19:25 Beast gnome-shell[2285]: _st_paint_shadow_with_opacity: 
assertion 'shadow_pipeline != NULL' failed
Nov  5 18:19:44 Beast gnome-shell[2285]: message repeated 380 times: [ 
_st_paint_shadow_with_opacity: assertion 'shadow_pipeline != NULL' failed]

The Infrared Remote is not relevant as it was crashing before I plugged
it in (just today).

I tried to run

   ls -ltr /var/crash/

but it gives me no crash files as of today.

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: gnome-shell 3.26.1-0ubuntu5
ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
Uname: Linux 4.13.0-16-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
ApportVersion: 2.20.7-0ubuntu3.1
Architecture: amd64
Date: Sun Nov  5 18:41:51 2017
DisplayManager: gdm3
InstallationDate: Installed on 2017-10-27 (9 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
ProcEnviron:
 TERM=xterm
 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)

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


** Tags: amd64 apport-bug artful

** Attachment added: "WIN_20171105_185759.JPG"

[Desktop-packages] [Bug 1685035] Re: GDM login doesn't scale on Hi-DPI display

2017-11-05 Thread PJSingh5000

For me, the GDM screen is scaling the icons and text correctly.

However, the pointer is very tiny.

This tiny pointer is also briefly visible on the Plymouth screen just
before GDM appears.

Once I click on the user name, and hover over the password text box, the
cursor scales up to the correct size.

It seems as if the pointer retains its original size (from Plymouth),
until it encounters a text area.  Then it seems to read the gsettings
value and resize itself.


GDM 3.26.1

GNOME Shell 3.26.1

Distributor ID: Ubuntu
Description:Ubuntu 17.10
Release:17.10
Codename:   artful

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

Title:
  GDM login doesn't scale on Hi-DPI display

Status in GNOME Settings Daemon:
  Fix Released
Status in Ubuntu GNOME:
  Triaged
Status in gnome-settings-daemon package in Ubuntu:
  Fix Released
Status in gnome-settings-daemon source package in Zesty:
  Fix Released

Bug description:
  Impact
  --
  GDM's login screen was being start with no gnome-settings-daemons plugins. In 
particular, this broke Hi-DPI support in the login screen

  Test Case
  -
  - Install the update on a computer running Ubuntu GNOME 17.04 with a Hi-DPI 
display (ideally one that worked well with Ubuntu GNOME 16.10).
  - Restart your computer.
  - The login screen should automatically show at the right scale.

  Regression Potential
  
  See the other 3.24.2 bugs but this commit is a simple typo fix.

  Original Bug Report
  ---
  Ubuntu gnome 17.04, gnome 3.24. On high resolution display, 3200x1800, login 
screen is too tiny to read. GDM login screen doesn't reflect changes to 
org.gnome.desktop.interface scaling-factor or text-scaling-factor.

  Eg:
  xhost +SI:localuser:gdm
  sudo su gdm -s /bin/bash
  gsettings set org.gnome.desktop.interface scaling-factor 2
  gsettings set org.gnome.desktop.interface text-scaling-factor 2.0

  no effect.

  Creating a gdm user under /etc/dconf and running dconf update has no
  effect either. Scaling-factor seems to scale the mouse cursor, but
  nothing else.

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

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

[Desktop-packages] [Bug 1718552] Re: gnome-shell uses lots of memory

2017-11-05 Thread Charles Green

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

I'd be willing to do memory profiling - I don't know how, and would need
some assistance in getting it done.  I have noticed that if gnome-shell
is running for a couple of days, I run up towards 400 MB of memory used,
and the system starts to feel sluggish.  Logging out and back in, or
restarting the gnome-shell reduce RAM usage to 67 MB, and restore system
performance.

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

Title:
  gnome-shell uses lots of memory

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  On Ubuntu 17.10 (daily build, VirtualBox), gnome-shell uses lots of
  memory, even more after opening and closing just a few apps
  (LibreOffice Writer, Chromium, Nautilus.) More than 640 mb.

  Also,the CPU usage is quite high too, even if nothing is running in
  the foreground.

  See screen captures.

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

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

[Desktop-packages] [Bug 1640180] Re: gnome-todo doesn't load CalDav task list from EDS

2017-11-05 Thread François

Hi, yeah, still happening on 17.10 with gnome-todo 2.26.1

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

Title:
  gnome-todo doesn't load CalDav task list from EDS

Status in GNOME To Do:
  Confirmed
Status in Ubuntu GNOME:
  New
Status in evolution-data-server package in Ubuntu:
  Incomplete
Status in gnome-todo package in Ubuntu:
  Triaged

Bug description:
  Since the upgrade to Yakkety Gnome-TODO doesn't show my remote CalDav
  task list that were set through evolution. The list are still
  available in working in Evolution.

  I tried to set them up again but they didn't appear. 
  I tried upgrading to version available in various gnome3-ppa (still 3.20.* 
though) and it didn't help.

  The bug seems to have been handled in Fedora :
  https://bugzilla.redhat.com/show_bug.cgi?format=multiple=1363848
  and https://bodhi.fedoraproject.org/updates/FEDORA-2016-db729be3e1 (I
  found those while searching the web for a solution).

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

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

[Desktop-packages] [Bug 1730213] Re: Mouse cursor flickers with box when external Display Link monitor is connected

2017-11-05 Thread Christopher M. Penalver

Travis Brace, thank you for reporting this and helping make Ubuntu
better. To clarify:

1) Could you please cross post this to DisplayLink following their
instructions via:
http://support.displaylink.com/knowledgebase/articles/757047-how-can-i
-report-ubuntu-issues-to-displaylink

2) Could you please provide the full manufacturer and model of your
device (ex. StarTech USB3SDOCKDD). Please note DisplayLink is not the
manufacturer or model.

3) Could you please advise to the full manufacturer and model of your
monitor(s)?

4) How does your DisplayLink device connect to the monitor(s)? For
example, one external monitor connects via HDMI.

5) If the version of the driver advertised by the device manufacturer is
older than that from DisplayLink's website, please advise to the results
of testing both the device manufacturer's version, and the latest driver
version from DisplayLink.

6) To rule out a regression in the DisplayLink driver, could you please
advise on what happens when testing the earliest version of the driver
compatible with your Ubuntu release?

7) Could you please post a picture of the issue via a camera,
screenshot, or screencast?

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

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

** Tags added: bios-outdated-f22a

** Tags added: potential-workaround

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

Title:
  Mouse cursor flickers  with box when external Display Link monitor is
  connected

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  I'm having the same issue as well. With three screens the mouse has a
  glitch where it's like part of the screen makes a box around it. It
  almost seems to happen on interactions.. It's very noticable moving
  over tabs on a browser window.

  I'm not sure if the same effect would happen with two video cards two
  monitors share the 1050ti with the Nvidia drivers installed. I did get
  the latest display link drivers installed.

  Thanks again for the help

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: xorg 1:7.7+16ubuntu3
  ProcVersionSignature: Ubuntu 4.10.0-39.43-generic 4.10.17
  Uname: Linux 4.10.0-39-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  384.90  Tue Sep 19 19:17:35 
PDT 2017
   GCC version:  gcc version 6.3.0 20170406 (Ubuntu 6.3.0-12ubuntu2)
  .proc.driver.nvidia.warnings.fbdev:
   Your system is not currently configured to drive a VGA console
   on the primary VGA device. The NVIDIA Linux graphics driver
   requires the use of a text-mode VGA console. Use of other console
   drivers including, but not limited to, vesafb, may result in
   corruption and stability problems, and is not supported.
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.4-0ubuntu4.5
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity:Unity7
  Date: Sun Nov  5 11:30:06 2017
  DistUpgraded: 2017-11-05 00:25:16,311 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process 
"./xorg_fix_proprietary.py" (No such file or directory) (8))
  DistroCodename: zesty
  DistroVariant: ubuntu
  DkmsStatus:
   bbswitch, 0.8, 4.10.0-28-generic, x86_64: installedError! Could not locate 
dkms.conf file.
   File:  does not exist.
   
   bbswitch, 0.8, 4.10.0-38-generic, x86_64: installed
   bbswitch, 0.8, 4.10.0-39-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   NVIDIA Corporation GP107 [GeForce GTX 1050 Ti] [10de:1c82] (rev a1) (prog-if 
00 [VGA controller])
 Subsystem: eVga.com. Corp. GP107 [GeForce GTX 1050 Ti] [3842:6253]
  InstallationDate: Installed on 2017-11-04 (0 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  MachineType: Gigabyte Technology Co., Ltd. H110M-M.2
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-39-generic 
root=UUID=8718e5d2-d2a9-4711-9619-505cb18367c9 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: Upgraded to zesty on 2017-11-05 (0 days ago)
  dmi.bios.date: 02/22/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F21
  dmi.board.asset.tag: Default string
  dmi.board.name: H110M-M2-CF
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3

[Desktop-packages] [Bug 1730250] Re: Location Services settings change doesn't reflect immediately

2017-11-05 Thread Logan Rosen

** Bug watch added: GNOME Bug Tracker #785891
   https://bugzilla.gnome.org/show_bug.cgi?id=785891

** Also affects: gnome-control-center via
   https://bugzilla.gnome.org/show_bug.cgi?id=785891
   Importance: Unknown
   Status: Unknown

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

Title:
  Location Services settings change doesn't reflect immediately

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

Bug description:
  In Privacy -> Location Services, clicking the toggle to either On or
  Off and then closing the dialog doesn't cause it to show a different
  value in the Privacy pane. You have to click a different pane and then
  go back to Privacy to reflect the change.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-control-center 1:3.26.1-0ubuntu5
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Nov  5 14:42:35 2017
  InstallationDate: Installed on 2017-06-20 (138 days ago)
  InstallationMedia: Ubuntu 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-control-center
  UpgradeStatus: Upgraded to artful on 2017-11-05 (0 days ago)

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

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

[Desktop-packages] [Bug 1730250] [NEW] Location Services settings change doesn't reflect immediately

2017-11-05 Thread Logan Rosen

Public bug reported:

In Privacy -> Location Services, clicking the toggle to either On or Off
and then closing the dialog doesn't cause it to show a different value
in the Privacy pane. You have to click a different pane and then go back
to Privacy to reflect the change.

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: gnome-control-center 1:3.26.1-0ubuntu5
ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
Uname: Linux 4.13.0-16-generic x86_64
ApportVersion: 2.20.7-0ubuntu3.1
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Sun Nov  5 14:42:35 2017
InstallationDate: Installed on 2017-06-20 (138 days ago)
InstallationMedia: Ubuntu 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-control-center
UpgradeStatus: Upgraded to artful on 2017-11-05 (0 days ago)

** Affects: gnome-control-center
 Importance: Unknown
 Status: Unknown

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


** Tags: amd64 apport-bug artful wayland-session

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

Title:
  Location Services settings change doesn't reflect immediately

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

Bug description:
  In Privacy -> Location Services, clicking the toggle to either On or
  Off and then closing the dialog doesn't cause it to show a different
  value in the Privacy pane. You have to click a different pane and then
  go back to Privacy to reflect the change.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-control-center 1:3.26.1-0ubuntu5
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Nov  5 14:42:35 2017
  InstallationDate: Installed on 2017-06-20 (138 days ago)
  InstallationMedia: Ubuntu 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-control-center
  UpgradeStatus: Upgraded to artful on 2017-11-05 (0 days ago)

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

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

[Desktop-packages] [Bug 1730251] [NEW] video crash

2017-11-05 Thread Gianluca Autullo

Public bug reported:

when i play a video with vlc media player, it freeze after 20/30 seconds
but the sound still going

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
NonfreeKernelModules: wl
ApportVersion: 2.20.7-0ubuntu3.1
Architecture: amd64
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Sun Nov  5 23:44:35 2017
DistUpgraded: Fresh install
DistroCodename: artful
DistroVariant: ubuntu
DkmsStatus: bcmwl, 6.30.223.271+bdcom, 4.13.0-16-generic, x86_64: installed
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0106] (rev 09) (prog-if 00 [VGA controller])
   Subsystem: Lenovo 2nd Generation Core Processor Family Integrated Graphics 
Controller [17aa:5011]
InstallationDate: Installed on 2017-11-04 (1 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
MachineType: LENOVO 37612DG
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=it_IT.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic 
root=UUID=6dd77dcc-21a1-4be0-9bb6-dff778f4c29d ro quiet splash vt.handoff=7
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 08/06/2015
dmi.bios.vendor: LENOVO
dmi.bios.version: H9ET92WW(1.29)
dmi.board.asset.tag: Not Available
dmi.board.name: 37612DG
dmi.board.vendor: LENOVO
dmi.board.version: Win8 STD MM DPK IPG
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Not Available
dmi.modalias: 
dmi:bvnLENOVO:bvrH9ET92WW(1.29):bd08/06/2015:svnLENOVO:pn37612DG:pvrLenovoB590:rvnLENOVO:rn37612DG:rvrWin8STDMMDPKIPG:cvnLENOVO:ct10:cvrNotAvailable:
dmi.product.family: Lenovo B590
dmi.product.name: 37612DG
dmi.product.version: Lenovo B590
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

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


** Tags: amd64 apport-bug artful ubuntu wayland-session

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

Title:
  video crash

Status in xorg package in Ubuntu:
  New

Bug description:
  when i play a video with vlc media player, it freeze after 20/30
  seconds but the sound still going

  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
  NonfreeKernelModules: wl
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Nov  5 23:44:35 2017
  DistUpgraded: Fresh install
  DistroCodename: artful
  DistroVariant: ubuntu
  DkmsStatus: bcmwl, 6.30.223.271+bdcom, 4.13.0-16-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0106] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: Lenovo 2nd Generation Core Processor Family Integrated Graphics 
Controller [17aa:5011]
  InstallationDate: Installed on 2017-11-04 (1 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  MachineType: LENOVO 37612DG
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=it_IT.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic 
root=UUID=6dd77dcc-21a1-4be0-9bb6-dff778f4c29d ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/06/2015
  dmi.bios.vendor: LENOVO
  dmi.bios.version: H9ET92WW(1.29)
  dmi.board.asset.tag: Not Available
  dmi.board.name: 37612DG
  dmi.board.vendor: LENOVO
  dmi.board.version: Win8 STD MM DPK IPG
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrH9ET92WW(1.29):bd08/06/2015:svnLENOVO:pn37612DG:pvrLenovoB590:rvnLENOVO:rn37612DG:rvrWin8STDMMDPKIPG:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.family: Lenovo B590
  dmi.product.name: 37612DG
  dmi.product.version: Lenovo B590

[Desktop-packages] [Bug 1652110] Re: Chromium 55+ doesn't support Widevine library

2017-11-05 Thread Vuk

Debian contains /debian/patches/fixes/widevine-revision.patch, similar patch 
exists in Arch also, but not in Ubuntu.
Also fix_building_widevinecdm_with_chromium.patch is probably not needed 
anymore. There isn't similar patch in Arch nor Debian.
Maybe replacing fix_building_widevinecdm_with_chromium.patch with 
widevine-revision.patch will help

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

Title:
  Chromium 55+ doesn't support Widevine library

Status in chromium-browser package in Ubuntu:
  Confirmed

Bug description:
  Since the update to version 55, Amazon Prime Video and Magine TV no longer 
work. I thought the fix solves this problem, apparently I was wrong. It seems 
also Widevine DRM since version 55 no longer work. This affects Chromium, Opera 
and Vivaldi because they use all chromium-codecs-ffmpeg-extra.
  A downgrade to version 53 restores the function.

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

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

[Desktop-packages] [Bug 1683990] Re: [Precision 3510, Realtek ALC3235, Speaker, Internal] No sound at all

2017-11-05 Thread Clare

This is a bug, but I am not sure if the cause is software, driver, or
hardware

** Description changed:

- I have had no sound since original (fairly recent) purchase. I purchased
- online from Dell.
+ Edit 05-Nov-2017
+ wondering if my issue could be same as bug 1681679 
+ note that when I run pulseaudio (verbose) at the command line it says that 
the daemon is running but that pa_pid_file_create() failed
+ 
+ and when I ran gnome-control-center at the command line recently I saw:
+ 
+ 
+ (gnome-control-center:8955): sound-cc-panel-WARNING **: No devices in the 
tree, so cannot set the active output
+ 
+ (gnome-control-center:8955): Gvc-WARNING **: Couldn't match the portless
+ stream (with card) - 'Built-in Audio Analog Stereo' is it an input ? ->
+ 1, streams card id -> 0
+ 
+ (gnome-control-center:8955): Gvc-CRITICAL **:
+ gvc_mixer_ui_device_get_id: assertion 'GVC_IS_MIXER_UI_DEVICE (device)'
+ failed
+ 
+ (gnome-control-center:8955): sound-cc-panel-WARNING **:
+ on_control_active_input_update - tried to fetch an input of id 0 but got
+ nothing
+ 
+ -original text of bug--
+ 
+ 
+ I have had no sound since original (fairly recent) purchase. I purchased 
online from Dell.
  
  Sound preferences were originally showing in upper right hand corner of
  the screen, but the sliders for changing volume were grayed out, and
  choosing sound test had no audible or visual result.
  
  Now sound preferences are not showing in upper right corner at all, and
  system preferences --> sound no longer shows 'sound test' as an option.
  
  I tried to fix original problem myself by killing then re-starting pulseaudio
- No effect. Also I tried commands 
+ No effect. Also I tried commands
  
- apt-get purge pulseaudio 
- and then later 
+ apt-get purge pulseaudio
+ and then later
  apt-get install pulseaudio
  
  it seemed to be after that when the sound preferences stopped showing in
  upper right corner, but I also did a general ubuntu update at the same
  time (and there is still a restart required for update for 'Latitude
  E5X60 System Update' 68614)
  
  Release: Ubuntu 16.04.2 LTS
  Package: N: Unable to locate package pkgname
  
  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.4.0-72.93-generic 4.4.49
  Uname: Linux 4.4.0-72-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  AudioDevicesInUse:
-  USERPID ACCESS COMMAND
-  /dev/snd/controlC0:  clare  2105 F pulseaudio
+  USERPID ACCESS COMMAND
+  /dev/snd/controlC0:  clare  2105 F pulseaudio
  CurrentDesktop: Unity
  Date: Tue Apr 18 22:44:33 2017
  DistributionChannelDescriptor:
-  # This is a distribution channel descriptor
-  # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
-  canonical-oem-somerville-trusty-amd64-osp1-20150720-0
+  # This is a distribution channel descriptor
+  # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
+  canonical-oem-somerville-trusty-amd64-osp1-20150720-0
  InstallationDate: Installed on 2017-01-05 (104 days ago)
  InstallationMedia: Ubuntu 14.04 "Trusty" - Build amd64 LIVE Binary 
20150720-04:06
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_DevicesInUse:
-  USERPID ACCESS COMMAND
-  /dev/snd/controlC0:  clare  2105 F pulseaudio
+  USERPID ACCESS COMMAND
+  /dev/snd/controlC0:  clare  2105 F pulseaudio
  Symptom_Jack: Speaker, Internal
  Symptom_Type: No sound at all
  Title: [Precision 3510, Realtek ALC3235, Speaker, Internal] No sound at all
  UpgradeStatus: Upgraded to xenial on 2017-02-10 (67 days ago)
  dmi.bios.date: 08/26/2016
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.9.4
  dmi.board.name: 0FFPFD
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.9.4:bd08/26/2016:svnDellInc.:pnPrecision3510:pvr:rvnDellInc.:rn0FFPFD:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: Precision 3510
  dmi.sys.vendor: Dell Inc.

** Changed in: alsa-driver (Ubuntu)
   Status: New => Invalid

** Converted to question:
   https://answers.launchpad.net/ubuntu/+source/alsa-driver/+question/660384

** Description changed:

  Edit 05-Nov-2017
- wondering if my issue could be same as bug 1681679 
+ wondering if my issue could be same as bug 1616079
  note that when I run pulseaudio (verbose) at the command line it says that 
the daemon is running but that pa_pid_file_create() failed
  
  and when I ran gnome-control-center at the command line recently I saw:
  
- 
- (gnome-control-center:8955): sound-cc-panel-WARNING **: No devices in the 
tree, so cannot set the active output
+ (gnome-control-center:8955): sound-cc-panel-WARNING **: No devices in
+ the

[Desktop-packages] [Bug 1730241] Re: Evolution segfaults when NVidia driver is installed but not used

** Summary changed:

- Evolution segfaults when NVidia driver is install but not used
+ Evolution segfaults when NVidia driver is installed but not used

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

Title:
  Evolution segfaults when NVidia driver is installed but not used

Status in evolution package in Ubuntu:
  New

Bug description:
  To use CUDA I have installed the NVidia driver but disabled the card
  in the BIOS and set the main output to the onboard GPU.  I also edited
  the xorg.conf accordingly.  Now I can no longer start evolution.  It
  crashes with a segfault.  I cannot reproduce the segfault with other
  clutter apps.

  Attached is a backtrace of the crash, my xorg.conf, and the Xorg log.

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

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

[Desktop-packages] [Bug 1652110] Re: Chromium 55+ doesn't support Widevine library

2017-11-05 Thread Vuk

Issue still present in Chromium 62.0.3202.75. Spotify won't work. 
Is there any workaround?

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

Title:
  Chromium 55+ doesn't support Widevine library

Status in chromium-browser package in Ubuntu:
  Confirmed

Bug description:
  Since the update to version 55, Amazon Prime Video and Magine TV no longer 
work. I thought the fix solves this problem, apparently I was wrong. It seems 
also Widevine DRM since version 55 no longer work. This affects Chromium, Opera 
and Vivaldi because they use all chromium-codecs-ffmpeg-extra.
  A downgrade to version 53 restores the function.

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

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

[Desktop-packages] [Bug 1615734] Re: Multiple monitors broken

2017-11-05 Thread chessplayer

So, I finally had the time to test Xubuntu with the dock and indeed, it
works the way I want it to. Almost, that is, since when I resume work
after a suspend, 4 identical windows open offering display settings. So
I have to close these, but I can live with that.

Seeing that my absolute must have, namely a searchable menu, is now
provided by Xubuntu by means of the whisker menu, I guess I will stick
to it.

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

Title:
  Multiple monitors broken

Status in nvidia-graphics-drivers-361 package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-367 package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-375 package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-384 package in Ubuntu:
  New

Bug description:
  I have a Lenovo P50 with Nvidia Optimus (Quadro M1000M), installed with 
Ubuntu 16.04 and the recommended Nvidia drivers (361.42). 
  I added two external monitors connected to DP sockets in the docking station. 
I would like to have display shift to those two monitors when the laptop is 
docked. One monitor has native resolution of 1680x1050 and the other is 
1920x1080. The laptop native resolution is 1920x1080.

  Expected result: 
  laptop monitor shut off, two external monitors running in native resolution, 
display shared on both monitors (not mirrored).

  Process:
  I configured the display using the "Displays" applet in the unity control 
center. However, pressing "Apply" when changing a specific display setting 
(such as resolution, location of screen relative to others, turning on/off), 
results in a long period of darkness, usually followed by display falling back 
to mirroring of all 3 monitors, using a similar-size screen (either low on all 
or high on all with the low-res monitor using panning). The applet remains 
frozen for some time, with the dialog "Is the display ok" open but 
unresponsive. Later I realized this is because there is another dialog of 
"Cannot set screen CRTCXXX" hidden under the two above windows, which needs to 
by ok-ed first.

  Extra:
  I also tried setting the display manually with 'xrandr', which lead to a 
similar result as above - with the "cannot set screen" dialog, and falling back 
to mirroring. This convinced me that the problem is probably with the nvidia 
driver and not the higher plumbing.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: nvidia-361 361.42-0ubuntu2
  ProcVersionSignature: Ubuntu 4.4.0-34.53-generic 4.4.15
  Uname: Linux 4.4.0-34-generic x86_64
  NonfreeKernelModules: symap_custom_dkms_x86_64 nvidia_uvm nvidia_modeset 
nvidia
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Mon Aug 22 19:14:55 2016
  InstallationDate: Installed on 2016-07-17 (36 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  SourcePackage: nvidia-graphics-drivers-361
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1730063] Re: [USB-Audio - Audioengine HD3, playback] fails after a while

2017-11-05 Thread Arach Hirmanpour

I'm adding a few corrections/details.

Actually sound does not work readily at boot (playing a tune in
rhythmbox would not produce any sound).

To 'activate' sound I have to go to settings and click on Test Speakers.
After that the speakers would work normally for any period of time as
long as there is no playing interruption.

If on the other hand I leave the speakers unused for a few minutes, then
they won't produce any sound any more unless I reboot and click on test
speakers again. When they are in that silent state, pavucontrol shows
the signal that is supposed to be sent to the speakers.

Other things that I have checked : The speakers work normally under
Windows on the same device (dual boot). They can be used over bluetooth
by another device whatever the situation (playing not playing) with
ubuntu.

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

Title:
  [USB-Audio - Audioengine HD3, playback] fails after a while

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  The speakers are connected to USB.

  "Digital Output (S/PDIF) - Audioengine HD3" appears in Sound settings.

  At first try, testing speakers (in sound settings) produced sound, but
  there was no sound in other applications (like Chromium or Rhythmbox).

  I had to add "install snd_hda_intel /bin/false" to /etc/modprobe.d
  /alsa-base.conf to get sound to work in other applications (presumably
  s/pdif was not directed to default sound card).

  But then, after a few minutes there is no sound any more (even speaker
  testing in settings does not produce any sound any more). Turning off
  the speakers and then back on doesn't help. Nor does disconnecting and
  reconnecting usb cord. So far, only rebooting restores sound for a
  while.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC1D0p:   arach  2475 F...m pulseaudio
   /dev/snd/controlC1:  arach  2475 F pulseaudio
  CurrentDesktop: Budgie:GNOME
  Date: Sat Nov  4 11:17:43 2017
  InstallationDate: Installed on 2017-09-24 (40 days ago)
  InstallationMedia: Ubuntu-Budgie 17.04 "Zesty Zapus" - Release amd64 
(20170412)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_Card: Audioengine HD3 - Audioengine HD3
  Symptom_Type: Sound works for a while, then breaks
  Title: [USB-Audio - Audioengine HD3, playback] fails after a while
  UpgradeStatus: Upgraded to artful on 2017-10-19 (15 days ago)
  dmi.bios.date: 10/17/2016
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: J61 v03.91
  dmi.board.asset.tag: CZC3195C9B
  dmi.board.name: 158A
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 0.00
  dmi.chassis.asset.tag: CZC3195C9B
  dmi.chassis.type: 6
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrJ61v03.91:bd10/17/2016:svnHewlett-Packard:pnHPZ620Workstation:pvr:rvnHewlett-Packard:rn158A:rvr0.00:cvnHewlett-Packard:ct6:cvr:
  dmi.product.family: 103C_53335X G=D
  dmi.product.name: HP Z620 Workstation
  dmi.sys.vendor: Hewlett-Packard
  mtime.conffile..etc.modprobe.d.alsa-base.conf: 2017-11-04T10:57:25.798374

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

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

[Desktop-packages] [Bug 1730242] [NEW] My system will not recover from suspend

2017-11-05 Thread Robert McCarter

Public bug reported:

I have ubuntu installed on a dell vostro 200 desktop. I think this
problem began with version 12 upgrade. Prior to that it would recover
from auto suspends.

Thanks in advance for any advice to correct the problem.

Best,

Bob

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg 1:7.7+13ubuntu3
Uname: Linux 4.13.11-041311-generic i686
.tmp.unity_support_test.1:
 
ApportVersion: 2.20.1-0ubuntu2.10
Architecture: i386
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
Date: Sun Nov  5 16:57:10 2017
DistUpgraded: Fresh install
DistroCodename: xenial
DistroVariant: ubuntu
DkmsStatus:
 bbswitch, 0.8, 4.13.11-041311-generic, i686: installed
 bbswitch, 0.8, 4.4.0-100-generic, i686: installed
 nvidia-304, 304.135, 4.4.0-100-generic, i686: installed
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 NVIDIA Corporation GF119 [GeForce GT 620 OEM] [10de:1049] (rev a1) (prog-if 00 
[VGA controller])
   Subsystem: NVIDIA Corporation GF119 [GeForce GT 620 OEM] [10de:0977]
InstallationDate: Installed on 2012-08-05 (1917 days ago)
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release i386 (20120423)
ProcEnviron:
 LANGUAGE=en_US
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.11-041311-generic 
root=UUID=c8f2cac1-e3af-4e51-8a89-726ef2282d44 ro drm.debug=0xe plymouth:debug
Renderer: Software
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.vendor: Dell Inc.
dmi.board.vendor: Dell Inc.
version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
version.libdrm2: libdrm2 2.4.76-1~ubuntu16.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.7-0ubuntu0.16.04.2
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.7-0ubuntu0.16.04.2
version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.7
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1.2
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2
xserver.bootTime: Sun Nov  5 16:53:35 2017
xserver.configfile: default
xserver.devices:
 inputPower Button KEYBOARD, id 6
 inputPower Button KEYBOARD, id 7
 inputDell Dell KM632 Wireless Keyboard and Mouse KEYBOARD, id 8
 inputDell Dell KM632 Wireless Keyboard and Mouse KEYBOARD, id 9
 inputDell Dell KM632 Wireless Keyboard and Mouse MOUSE, id 10
xserver.logfile: /var/log/Xorg.0.log
xserver.version: 2:1.18.4-0ubuntu0.7

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


** Tags: apport-bug compiz-0.9 i386 ubuntu xenial

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

Title:
  My system will not recover from suspend

Status in xorg package in Ubuntu:
  New

Bug description:
  I have ubuntu installed on a dell vostro 200 desktop. I think this
  problem began with version 12 upgrade. Prior to that it would recover
  from auto suspends.

  Thanks in advance for any advice to correct the problem.

  Best,

  Bob

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  Uname: Linux 4.13.11-041311-generic i686
  .tmp.unity_support_test.1:
   
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: i386
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Sun Nov  5 16:57:10 2017
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  DkmsStatus:
   bbswitch, 0.8, 4.13.11-041311-generic, i686: installed
   bbswitch, 0.8, 4.4.0-100-generic, i686: installed
   nvidia-304, 304.135, 4.4.0-100-generic, i686: installed
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   NVIDIA Corporation GF119 [GeForce GT 620 OEM] [10de:1049] (rev a1) (prog-if 
00 [VGA controller])
 Subsystem: NVIDIA Corporation GF119 [GeForce GT 620 OEM] [10de:0977]
  InstallationDate: Installed on 2012-08-05 (1917 days ago)
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release i386 
(20120423)
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.11-041311-generic 
root=UUID=c8f2cac1-e3af-4e51-8a89-726ef2282d44 ro drm.debug=0xe plymouth:debug
  Renderer: Software
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)

[Desktop-packages] [Bug 1730241] Re: Evolution segfaults when NVidia driver is install but not used

** Attachment added: "xorg.conf"
   
https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/1730241/+attachment/5004302/+files/xorg.conf

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

Title:
  Evolution segfaults when NVidia driver is install but not used

Status in evolution package in Ubuntu:
  New

Bug description:
  To use CUDA I have installed the NVidia driver but disabled the card
  in the BIOS and set the main output to the onboard GPU.  I also edited
  the xorg.conf accordingly.  Now I can no longer start evolution.  It
  crashes with a segfault.  I cannot reproduce the segfault with other
  clutter apps.

  Attached is a backtrace of the crash, my xorg.conf, and the Xorg log.

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

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

[Desktop-packages] [Bug 1730241] Re: Evolution segfaults when NVidia driver is install but not used

** Attachment added: "Xorg.0.log"

https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/1730241/+attachment/5004303/+files/Xorg.0.log

** Description changed:

To use CUDA I have installed the NVidia driver but disabled the card in
the BIOS and set the main output to the onboard GPU. I also edited the
xorg.conf accordingly. Now I can no longer start evolution. It crashes
with a segfault. I cannot reproduce the segfault with other clutter
apps.

- Attached is a backtrace of the crash.
+ Attached is a backtrace of the crash, my xorg.conf, and the Xorg log.

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

Title:
Evolution segfaults when NVidia driver is install but not used

Status in evolution package in Ubuntu:
New

Bug description:
To use CUDA I have installed the NVidia driver but disabled the card
in the BIOS and set the main output to the onboard GPU. I also edited
the xorg.conf accordingly. Now I can no longer start evolution. It
crashes with a segfault. I cannot reproduce the segfault with other
clutter apps.

Attached is a backtrace of the crash, my xorg.conf, and the Xorg log.

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

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

[Desktop-packages] [Bug 1730241] [NEW] Evolution segfaults when NVidia driver is install but not used