date:20171001

Public bug reported:

Release: Artful Aardvark 17.10
Package version: 1.0.28-4

The current version of libsndfile1-dev is not able to be marked Multi-
Arch: same, because the examples it provides includes an autoheader (?)
generated config.h file, which has architecture-specific defines like
SIZEOF_INT. However, as far as I can tell, this header, as well as
common.h and sfconfig.h aren't actually used in any of the examples,
despite being included sometimes. So if they were removed, it should be
possible to mark the dev package as Multi-Arch: same. I was able to
install both amd64 and i386 versions of libsndfile1-dev after removing
the examples.

For a more long-term solution, the header includes in
debian/libsndfile1-dev.examples can probably be removed once those extra
includes are removed. A change on the github repo for libsndfile was
recently merged to get rid of the extra includes, as it's also probably
a bad idea to (unnecessarily) include internal header files in example
code.

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

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

Title:
  Enable multiarch in libsndfile1-dev

Status in libsndfile package in Ubuntu:
  New

Bug description:
  Release: Artful Aardvark 17.10
  Package version: 1.0.28-4

  The current version of libsndfile1-dev is not able to be marked Multi-
  Arch: same, because the examples it provides includes an autoheader
  (?) generated config.h file, which has architecture-specific defines
  like SIZEOF_INT. However, as far as I can tell, this header, as well
  as common.h and sfconfig.h aren't actually used in any of the
  examples, despite being included sometimes. So if they were removed,
  it should be possible to mark the dev package as Multi-Arch: same. I
  was able to install both amd64 and i386 versions of libsndfile1-dev
  after removing the examples.

  For a more long-term solution, the header includes in
  debian/libsndfile1-dev.examples can probably be removed once those
  extra includes are removed. A change on the github repo for libsndfile
  was recently merged to get rid of the extra includes, as it's also
  probably a bad idea to (unnecessarily) include internal header files
  in example code.

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

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

[Desktop-packages] [Bug 1707487] Re: Bluetooth speaker only plays as mono

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

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

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

Title:
  Bluetooth speaker only plays as mono

Status in pulseaudio package in Ubuntu:
  Expired

Bug description:
  When I connect my Sony SRS-X1 Bluetooth speaker to Ubuntu, it only
  plays back as "mono" and refuses to use "hi fidelity".

  I have Windows 10 installed on the same laptop and when I've used the
  Bluetooth speaker in Ubuntu, Windows will "forget" the speaker on its
  Bluetooth list. I have to hold in the "reset" button on the speaker
  itself and re-add the speaker to Windows 10. This ONLY HAPPENS if I
  try using this speaker in Ubuntu, which suggests that Ubuntu is
  forcing the speaker into "mono" mode and Windows then sees it as a
  different device?

  Please help.
  I will post all needed outputs as instructed.

  Cheers!
  --- 
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0c:   david  3626 F...m pulseaudio
   /dev/snd/controlC0:  david  3626 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.04
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2016-07-28 (367 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  Package: pulseaudio 1:8.0-0ubuntu3.3
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.4.0-87.110-generic 4.4.73
  Tags:  xenial
  Uname: Linux 4.4.0-87-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 12/16/2013
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V2.21
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: VA50_HC_CR
  dmi.board.vendor: Acer
  dmi.board.version: Type2 - Board Version
  dmi.chassis.type: 10
  dmi.chassis.vendor: Insyde Corp.
  dmi.chassis.version: V2.21
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV2.21:bd12/16/2013:svnAcer:pnAspireV3-571:pvrV2.21:rvnAcer:rnVA50_HC_CR:rvrType2-BoardVersion:cvnInsydeCorp.:ct10:cvrV2.21:
  dmi.product.name: Aspire V3-571
  dmi.product.version: V2.21
  dmi.sys.vendor: Acer
  modified.conffile..etc.xdg.autostart.pulseaudio.desktop: [modified]
  mtime.conffile..etc.xdg.autostart.pulseaudio.desktop: 
2016-07-29T10:08:04.428983

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

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

[Desktop-packages] [Bug 1707611] Re: Sound does not automatically play on new audio device

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

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

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

Title:
  Sound does not automatically play on new audio device

Status in pulseaudio package in Ubuntu:
  Expired

Bug description:
  When connecting a HDMI cable or other audio device, the user must
  manually click on the "sound volume" in the top-right and switch to
  the newly connected device.

  Example: you connect a HDMI cable to the television, but then you must
  manually choose the HDMI sound option; it does not get selected
  automatically.

  Often times e.g. when the HDMI cable is disconnected, the user must
  then manually click on the "speakers" or "line out" setting - EVEN IF
  IT'S ALREADY SELECTED, it must be clicked on again for the sound to
  work through the computer's speakers.

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

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

[Desktop-packages] [Bug 1720723] [NEW] Add multiarch metadata to gir1.2-gstreamer-1.0

Public bug reported:

Release: Artful Aardvark 17.10
Package version: 1.12.3-1

I modified the debian/gir1.2-gstreamer-1.0.install file to put its
girepository-1.0 files under the architecture-dependent directory, by
removing the target specifier (usr/lib). As far as I can tell, the non-
architecture specific files are just doc files, and should be the same
on other architectures. I then successfully installed the modified
package and imported Gst using python3-gi. Changing the install
directory plus adding Multi-Arch: same to gir1.2-gstreamer-1.0 should
make it multiarch-compatible.

It's also likely that libgstreamer1.0-dev could also be Multi-Arch: same
if it weren't for the binaries in the package, although I don't know an
easy solution to that - for instance gst-codec-info-1.0 loads plugins
dynamically, which fails (with an accurate warning message) if used on
the wrong architecture. Renaming it/giving it an architecture-dependent
path (e.g. x86_64-linux-gnu-gcc) would probably break backwards
compatibility, and there are about 20 rdepends for libgstreamer1.0-dev,
which as gst-codec-info-1.0 and dh_gstscancodecs seem designed for use
by packagers are probably the only places to check for usage.

** Affects: gstreamer1.0 (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  Add multiarch metadata to gir1.2-gstreamer-1.0

Status in gstreamer1.0 package in Ubuntu:
  New

Bug description:
  Release: Artful Aardvark 17.10
  Package version: 1.12.3-1

  I modified the debian/gir1.2-gstreamer-1.0.install file to put its
  girepository-1.0 files under the architecture-dependent directory, by
  removing the target specifier (usr/lib). As far as I can tell, the
  non-architecture specific files are just doc files, and should be the
  same on other architectures. I then successfully installed the
  modified package and imported Gst using python3-gi. Changing the
  install directory plus adding Multi-Arch: same to gir1.2-gstreamer-1.0
  should make it multiarch-compatible.

  It's also likely that libgstreamer1.0-dev could also be Multi-Arch:
  same if it weren't for the binaries in the package, although I don't
  know an easy solution to that - for instance gst-codec-info-1.0 loads
  plugins dynamically, which fails (with an accurate warning message) if
  used on the wrong architecture. Renaming it/giving it an architecture-
  dependent path (e.g. x86_64-linux-gnu-gcc) would probably break
  backwards compatibility, and there are about 20 rdepends for
  libgstreamer1.0-dev, which as gst-codec-info-1.0 and dh_gstscancodecs
  seem designed for use by packagers are probably the only places to
  check for usage.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gstreamer1.0/+bug/1720723/+subscriptions

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

[Desktop-packages] [Bug 1720184] Re: Please merge im-config 0.32-1 (main) from Debian unstable (main)

This bug was fixed in the package im-config - 0.32-1ubuntu1

---
im-config (0.32-1ubuntu1) artful; urgency=medium

  * Merge with Debian unstable (LP: #1720184), remaining changes:
- d/im-config.user-session.upstart, d/im-config.links, d/rules:
  - Install upstart user session job.
- d/user/im-config.override, d/user/im-config.service, d/rules:
  - Install systemd user session job.
- debian/menu
- debian/patches/01-ubuntu-default-mode.patch
- debian/patches/use-distinguishable-abstract-address.patch
  * debian/patches/use-distinguishable-abstract-address.patch:
- Refreshed.
  * debian/patches/03-not-always-require-zenity.patch:
- Dropped; applied upstream.

 -- Gunnar Hjalmarsson   Fri, 29 Sep 2017 00:13:00
+0200

** Changed in: im-config (Ubuntu)
   Status: Fix Committed => Fix Released

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

Title:
  Please merge im-config 0.32-1 (main) from Debian unstable (main)

Status in im-config package in Ubuntu:
  Fix Released

Bug description:
  Please merge im-config 0.32-1 (main) from Debian unstable (main)

  Changelogs from ubuntu package:

  im-config (0.32-1) unstable; urgency=medium

[ HIGUCHI Daisuke (VDR dai) ]
* Disable uim-toolbar-gtk{,3}-systray due to outdated.   
  - They are outdated, buggy and have alternatives (uim-toolbar-gtk{,3}).   

* Use uim-toolbar-qt5 instead of uim-toolbar-qt (nonexistent).   
* Wait a sec before starting uim-toolbar.
  - uim-toolbar's spawning is too faster than desktop environment's 
starting.   

   -- Osamu Aoki   Wed, 27 Sep 2017 21:15:24 +0900

  im-config (0.31-1) unstable; urgency=medium

[ Osamu Aoki ]   
* Start ibus with IBUS_ENABLE_SYNC_MODE=0.  Closes: #812826, #838318, 
#876794   
* Add Czech language strings to the desktop file.  Closes: #868036 
* im-config -l doesn't need GUI.  Closes: #804067
* Update PO with trivial unfuzzy. 

[ Boyuan Yang ]
* Refresh debian/copyright file as machine-readable format.

   -- Osamu Aoki   Tue, 26 Sep 2017 22:41:36 +0900

  im-config (0.30-1) unstable; urgency=medium

* New upstream release acknowledging all NMU patches.

   -- Osamu Aoki   Wed, 07 Dec 2016 22:00:16 +0900

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/im-config/+bug/1720184/+subscriptions

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

[Desktop-packages] [Bug 1720703] Re: Broken graphics on Ubuntu mate 17.10 on EeePC 901X

2017-10-01 Thread Steve Langasek

This screenshot shows an X session, so is definitely not a Plymouth bug.

** Package changed: plymouth (Ubuntu) => xorg-server (Ubuntu)

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

Title:
  Broken graphics on Ubuntu mate 17.10 on EeePC 901X

Status in xorg-server package in Ubuntu:
  New

Bug description:
  I have upgraded 17.04 to 17.10 Ubuntu Mate.

  The graphic is broken as shown below.

  https://imgur.com/a/t0y9L
  https://imgur.com/gallery/o8I7F

  Partial screen (1/6 right) working correctly.

  recovery mode is working fine.

  I found 4.13.0-12-generic and 4.13.0-11-generic kernel has broken
  graphics.

  In recovery mode, I could select 800x600 only.

  The correct resolution is 1024x600 for my EeePC, but this resolution
  is broken.

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

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

[Desktop-packages] [Bug 1720703] [NEW] Broken graphics on Ubuntu mate 17.10 on EeePC 901X

You have been subscribed to a public bug:

I have upgraded 17.04 to 17.10 Ubuntu Mate.

The graphic is broken as shown below.

https://imgur.com/a/t0y9L
https://imgur.com/gallery/o8I7F

Partial screen (1/6 right) working correctly.

recovery mode is working fine.

I found 4.13.0-12-generic and 4.13.0-11-generic kernel has broken
graphics.

In recovery mode, I could select 800x600 only.

The correct resolution is 1024x600 for my EeePC, but this resolution is
broken.

** Affects: xorg-server (Ubuntu)
 Importance: Undecided
 Assignee: inugami (inugami-mamoru)
 Status: New


** Tags: bot-comment
-- 
Broken graphics on Ubuntu mate 17.10 on EeePC 901X
https://bugs.launchpad.net/bugs/1720703
You received this bug notification because you are a member of Desktop 
Packages, which is subscribed to xorg-server in Ubuntu.

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

[Desktop-packages] [Bug 1689033] Re: A few missing icons in version 2.4.3

2017-10-01 Thread Amr Ibrahim

** Changed in: easytag (Ubuntu)
   Status: Confirmed => Invalid

** Changed in: gtk+3.0 (Ubuntu)
   Status: Fix Committed => Fix Released

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

Title:
  A few missing icons in version 2.4.3

Status in gdk-pixbuf:
  Invalid
Status in GTK+:
  Fix Released
Status in easytag package in Ubuntu:
  Invalid
Status in gdk-pixbuf package in Ubuntu:
  Invalid
Status in gtk+3.0 package in Ubuntu:
  Fix Released

Bug description:
  A few icons are missing in version 2.4.3 for zesty (and probably
  artful), see https://i.imgur.com/Cl4o36Sr.png

To manage notifications about this bug go to:
https://bugs.launchpad.net/gdk-pixbuf/+bug/1689033/+subscriptions

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

[Desktop-packages] [Bug 1720713] [NEW] [E205SA, Realtek ALC255, Speaker, Internal] No sound at all

2017-10-01 Thread Chris Meyer

Public bug reported:

New installation of Ubuntu 17.04 no sound whatsoever. tried all the
troubleshooting tips, even tried installing realtek driver, searched the
web and no solution

ProblemType: Bug
DistroRelease: Ubuntu 17.04
Package: alsa-base 1.0.25+dfsg-0ubuntu5
ProcVersionSignature: Ubuntu 4.10.0-35.39-generic 4.10.17
Uname: Linux 4.10.0-35-generic x86_64
ApportVersion: 2.20.4-0ubuntu4.5
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  chris  1657 F pulseaudio
CurrentDesktop: Unity:Unity7
Date: Mon Oct  2 12:37:39 2017
InstallationDate: Installed on 2017-10-01 (0 days ago)
InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
PackageArchitecture: all
ProcEnviron:
 LANGUAGE=en_AU:en
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_AU.UTF-8
 SHELL=/bin/bash
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:  chris  1657 F pulseaudio
Symptom_Jack: Speaker, Internal
Symptom_Type: No sound at all
Title: [E205SA, Realtek ALC255, Speaker, Internal] No sound at all
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 09/04/2015
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: E205SA.206
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: E205SA
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.:bvrE205SA.206:bd09/04/2015:svnASUSTeKCOMPUTERINC.:pnE205SA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnE205SA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
dmi.product.name: E205SA
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK COMPUTER INC.

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


** Tags: amd64 apport-bug zesty

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

Title:
  [E205SA, Realtek ALC255, Speaker, Internal] No sound at all

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  New installation of Ubuntu 17.04 no sound whatsoever. tried all the
  troubleshooting tips, even tried installing realtek driver, searched
  the web and no solution

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.10.0-35.39-generic 4.10.17
  Uname: Linux 4.10.0-35-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  chris  1657 F pulseaudio
  CurrentDesktop: Unity:Unity7
  Date: Mon Oct  2 12:37:39 2017
  InstallationDate: Installed on 2017-10-01 (0 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  PackageArchitecture: all
  ProcEnviron:
   LANGUAGE=en_AU:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_AU.UTF-8
   SHELL=/bin/bash
  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:  chris  1657 F pulseaudio
  Symptom_Jack: Speaker, Internal
  Symptom_Type: No sound at all
  Title: [E205SA, Realtek ALC255, Speaker, Internal] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/04/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: E205SA.206
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: E205SA
  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.:bvrE205SA.206:bd09/04/2015:svnASUSTeKCOMPUTERINC.:pnE205SA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnE205SA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: E205SA
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

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

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

[Desktop-packages] [Bug 1720651] Re: Scrollbar drawing broken on wayland sesssion

** Tags added: ui

** Tags added: artful

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

Title:
  Scrollbar drawing broken on wayland sesssion

Status in gnome-terminal package in Ubuntu:
  New

Bug description:
  Scrollbar drawing broken, with light theme variant on wayland session.
  See attached screenshot (white line right of scrollbar). To fix this
  you should remove some unity-compatible patch.

  Ubuntu 17.10, gnome-terminal-3.24.2-0ubuntu4

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

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

[Desktop-packages] [Bug 1720649] Re: broken gnome expirience caused by unity-compatible patch

** Tags added: ui

** Tags added: artful

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

Title:
  broken gnome expirience caused by unity-compatible patch

Status in rhythmbox package in Ubuntu:
  New

Bug description:
  Standard gnome behavior doesn't allow to draw rhythmbox menubar,
  because all the controls are available through the "settings (gear)
  button". Ubuntu 17.10 draws menu, because of unity-compatible patch,
  you should remove it, to provide true gnome expirience. Menubar is
  bloatware.

  Problem occurs if you disable top bar application menu in Gnome
  Tweaks, and start Rhythmbox after that. See attached screenshot.
  Please, remove menubar patch.

  Ubuntu 17.10, rhythmbox-3.4.1-2ubuntu5.

  You should also check other Gnome apps!!! AFAIK, Totem, default video
  player also has some patch like this, and you even cant hide menubar
  in fullscreen mode (!). I'm using mpv, so i dont care.

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

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

[Desktop-packages] [Bug 1720654] Re: Totem menu is totally broken

** Tags added: ui

** Tags added: artful

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

Title:
  Totem menu is totally broken

Status in totem package in Ubuntu:
  New

Bug description:
  Open Totem with disabled "top bar application menu" option in Gnome
  Tweaks. See this (screenshot). Menu is coming from unity-compatible
  patch, original gnome behavior - menu should go to button with totem
  icon left of the "+" button. Worst thing - MENU IS ALWAYS VISIBLE,
  EVEN IN FULLSCREEN MODE WITH MOVIE PLAYING!!! (Ubuntu 17.10)

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

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

[Desktop-packages] [Bug 735496] I'm so worked up about it

2017-10-01 Thread Robert Cotterman

Hello friend,

Just  check out the  stuff  I  just found, I'm so fired up, take  a look
at http://www.alsafe.in/premium.php?UE83MzU0OTZAYnVncy5sYXVuY2hwYWQubmV0


Warmest regards, Chad Cordero


-

Reproduction is prohibited other than in accordance with the copyright
notice, which forms part of these terms and conditions. All trade marks
reproduced in this website which are not the property of, or licensed
to, the operator are acknowledged on the website. Unauthorised use of
this website may give rise to a claim for damages and/or be a criminal
offence.

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

Title:
  package monodoc-webkit-manual 0.3-2 failed to install/upgrade:
  subprocess installed post-installation script returned error exit
  status 1

Status in webkit-sharp package in Ubuntu:
  New

Bug description:
  i don't know anything about this, the machine just asked me to file
  this report

  ProblemType: Package
  DistroRelease: Ubuntu 10.04
  Package: monodoc-webkit-manual 0.3-2
  ProcVersionSignature: Ubuntu 2.6.32-29.58-generic-pae 2.6.32.28+drm33.13
  Uname: Linux 2.6.32-29-generic-pae i686
  NonfreeKernelModules: nvidia
  Architecture: i386
  Date: Mon Mar 14 20:23:04 2011
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  InstallationMedia: Xubuntu 10.04 "Lucid Lynx" - Release i386 (20100429)
  PackageArchitecture: all
  SourcePackage: webkit-sharp
  Title: package monodoc-webkit-manual 0.3-2 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/webkit-sharp/+bug/735496/+subscriptions

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

[Desktop-packages] [Bug 1706052] Re: cupsd crashes with SIGSEGV on ubuntu 17.04 on start

2017-10-01 Thread HuaiDan

Ubuntu 17.04 4.10.0-35-generic amd64 (upgraded from
Wiley->Xenial->Zesty)


gbd output:

(gdb) bt
#0  __strcasecmp_l_avx () at ../sysdeps/x86_64/multiarch/strcmp-sse42.S:165
#1  0x7f699c907fe5 in lsp_initialize ()
   from /lib/lib/x86_64-linux-gnu/liblsp.so
#2  0x7f699cb1b9ca in call_init (l=, argc=argc@entry=1, 
argv=argv@entry=0x7fffc1969d68, env=env@entry=0x7fffc1969d78)
at dl-init.c:72
#3  0x7f699cb1badb in call_init (env=0x7fffc1969d78, argv=0x7fffc1969d68, 
argc=1, l=) at dl-init.c:30
#4  _dl_init (main_map=0x7f699cd32168, argc=1, argv=0x7fffc1969d68, 
env=0x7fffc1969d78) at dl-init.c:120
#5  0x7f699cb0bc5a in _dl_start_user () from /lib64/ld-linux-x86-64.so.2
#6  0x0001 in ?? ()
#7  0x7fffc196a27f in ?? ()
#8  0x in ?? ()
(gdb) quit


I've been sending the reports from the crash notifications whenever prompted.

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

Title:
  cupsd crashes with SIGSEGV on ubuntu 17.04 on start

Status in cups package in Ubuntu:
  Confirmed

Bug description:
  Hey,
  I upgraded to Ubuntu 17.04, but CUPS crashes on boot, and when I run cupsd it 
segfaults. Attaching strace ouput.
  --- 
  ApportVersion: 2.20.4-0ubuntu4.4
  Architecture: amd64
  CupsErrorLog:
   
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 17.04
  InstallationDate: Installed on 2012-12-20 (1698 days ago)
  InstallationMedia: Kubuntu 12.10 "Quantal Quetzal" - Release amd64 
(20121017.1)
  Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: Bad 
file descriptor
  MachineType: ASUSTeK COMPUTER INC. UX303LB
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  Package: cups 2.2.2-1ubuntu1
  PackageArchitecture: amd64
  Papersize: letter
  ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-4.10.0-28-generic 
root=UUID=a8690ccc-4675-4e21-896f-eadcc45159f4 ro quiet splash vga=791 
pcie_aspm=force drm.vblankoffdelay=1
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-28-generic 
root=UUID=a8690ccc-4675-4e21-896f-eadcc45159f4 ro quiet splash vga=791 
pcie_aspm=force drm.vblankoffdelay=1
  ProcVersionSignature: Ubuntu 4.10.0-28.32-generic 4.10.17
  Tags:  zesty
  Uname: Linux 4.10.0-28-generic x86_64
  UpgradeStatus: Upgraded to zesty on 2017-04-19 (117 days ago)
  UserGroups: adm bluetooth bumblebee cdrom dialout dip lp lpadmin netdev 
nvidia-persistenced plugdev sambashare sudo usrp
  _MarkForUpload: True
  dmi.bios.date: 03/17/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX303LB.203
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX303LB
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: ATN12345678901234567
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrUX303LB.203:bd03/17/2015:svnASUSTeKCOMPUTERINC.:pnUX303LB:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX303LB:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: UX303LB
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  mtime.conffile..etc.cups.cupsd.conf: 2015-10-21T13:38:49.740915

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

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

[Desktop-packages] [Bug 1706052] Re: cupsd crashes with SIGSEGV on ubuntu 17.04 on start

2017-10-01 Thread HuaiDan

>From /var/crash

** Attachment added: "CUPSD crash report"
   
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1706052/+attachment/4960158/+files/_usr_sbin_cupsd.0.crash

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

Title:
  cupsd crashes with SIGSEGV on ubuntu 17.04 on start

Status in cups package in Ubuntu:
  Confirmed

Bug description:
  Hey,
  I upgraded to Ubuntu 17.04, but CUPS crashes on boot, and when I run cupsd it 
segfaults. Attaching strace ouput.
  --- 
  ApportVersion: 2.20.4-0ubuntu4.4
  Architecture: amd64
  CupsErrorLog:
   
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 17.04
  InstallationDate: Installed on 2012-12-20 (1698 days ago)
  InstallationMedia: Kubuntu 12.10 "Quantal Quetzal" - Release amd64 
(20121017.1)
  Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: Bad 
file descriptor
  MachineType: ASUSTeK COMPUTER INC. UX303LB
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  Package: cups 2.2.2-1ubuntu1
  PackageArchitecture: amd64
  Papersize: letter
  ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-4.10.0-28-generic 
root=UUID=a8690ccc-4675-4e21-896f-eadcc45159f4 ro quiet splash vga=791 
pcie_aspm=force drm.vblankoffdelay=1
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-28-generic 
root=UUID=a8690ccc-4675-4e21-896f-eadcc45159f4 ro quiet splash vga=791 
pcie_aspm=force drm.vblankoffdelay=1
  ProcVersionSignature: Ubuntu 4.10.0-28.32-generic 4.10.17
  Tags:  zesty
  Uname: Linux 4.10.0-28-generic x86_64
  UpgradeStatus: Upgraded to zesty on 2017-04-19 (117 days ago)
  UserGroups: adm bluetooth bumblebee cdrom dialout dip lp lpadmin netdev 
nvidia-persistenced plugdev sambashare sudo usrp
  _MarkForUpload: True
  dmi.bios.date: 03/17/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX303LB.203
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX303LB
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: ATN12345678901234567
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrUX303LB.203:bd03/17/2015:svnASUSTeKCOMPUTERINC.:pnUX303LB:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX303LB:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: UX303LB
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  mtime.conffile..etc.cups.cupsd.conf: 2015-10-21T13:38:49.740915

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

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

[Desktop-packages] [Bug 1720250] Re: im-config configuration ignored with gdm3

2017-10-01 Thread Gunnar Hjalmarsson

On 2017-10-02 00:00, Jeremy Bicha wrote:> Gunnar, upstart has been removed from 
Debian 9 "Stretch" and from
> Ubuntu 17.10.
Ah, had missed that.

> You should drop the debian/menu too.
I just uploaded a new version to the PPA with those changes.

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

Title:
  im-config configuration ignored with gdm3

Status in gdm3 package in Ubuntu:
  Confirmed
Status in im-config package in Ubuntu:
  Confirmed

Bug description:
  After having logged in via gdm3, the IM related environment variables
  are always set like this:

  $ env | grep -E '_IM|XMOD'
  QT_IM_MODULE=ibus
  XMODIFIERS=@im=ibus

  Changing ~/.xinputrc to e.g. xim makes no difference, so gdm3 prevents
  all other IM frameworks but IBus from working.

  This problem seems to be similar to bug #1594681 (which was fixed).

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

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

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

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

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

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

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

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

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

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

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

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

** This bug has been marked a duplicate of bug 1505409
   gnome-shell crashed with SIGTRAP in x_io_error() from _XIOError() from 
_XEventsQueued() from XPending() from gdk_check_xpending() ["Connection to 
xwayland lost"]

** Information type changed from Private to Public

** Tags removed: need-amd64-retrace

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

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

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  This error occurred for no apparent reason.

  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.26.0-0ubuntu2
  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
  CurrentDesktop: GNOME-Greeter:GNOME
  Date: Sun Oct  1 17:50:32 2017
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  GsettingsChanges:
   
  InstallationDate: Installed on 2017-06-08 (114 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170608)
  ProcCmdline: /usr/bin/gnome-shell
  Signal: 5
  SourcePackage: gnome-shell
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/libmutter-1.so.0
   _XIOError () from /usr/lib/x86_64-linux-gnu/libX11.so.6
   _XEventsQueued () from /usr/lib/x86_64-linux-gnu/libX11.so.6
   XPending () from /usr/lib/x86_64-linux-gnu/libX11.so.6
   ?? () from /usr/lib/x86_64-linux-gnu/libgdk-3.so.0
  Title: gnome-shell crashed with signal 5 in _XIOError()
  UpgradeStatus: 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/1720705/+subscriptions

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

[Desktop-packages] [Bug 1720701] [NEW] Add multiarch metadata to libpixman-1-dev

Public bug reported:

Release: Artful Aardvark 17.10
Package version: 0.34.0-1

After modifying libpixman-1-dev to be Multi-Arch: same, and checking
that it installs architecture-specific files appropriately, and
successfully building and installing both the amd64 and i386 versions
simultaneously, it seems like libpixman-1-dev can be upgraded to get
multiarch support fairly easily.

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

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

Title:
  Add multiarch metadata to libpixman-1-dev

Status in pixman package in Ubuntu:
  New

Bug description:
  Release: Artful Aardvark 17.10
  Package version: 0.34.0-1

  After modifying libpixman-1-dev to be Multi-Arch: same, and checking
  that it installs architecture-specific files appropriately, and
  successfully building and installing both the amd64 and i386 versions
  simultaneously, it seems like libpixman-1-dev can be upgraded to get
  multiarch support fairly easily.

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

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

[Desktop-packages] [Bug 1720552] Re: appstreamcli crashed with SIGSEGV in gvs_tuple_needed_size()

2017-10-01 Thread Matthias Klumpp

This doesn't look like it is a bug in appstreamcli... I am not sure what
exactly went wrong there, because the GLib side looks fine as well.

** Information type changed from Private to Public

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

Title:
  appstreamcli crashed with SIGSEGV in gvs_tuple_needed_size()

Status in appstream package in Ubuntu:
  New

Bug description:
  Crashed, reset my screen but kept all documents open I had

  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: appstream 0.11.3-1
  ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3
  Uname: Linux 4.13.0-12-generic i686
  NonfreeKernelModules: nvidia
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: i386
  Date: Sat Sep 30 16:27:55 2017
  ExecutablePath: /usr/bin/appstreamcli
  InstallationDate: Installed on 2017-07-25 (67 days ago)
  InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release i386 (20170412)
  ProcCmdline: appstreamcli refresh-cache
  ProcEnviron:
   LANGUAGE=en_GB:en
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  SegvAnalysis:
   Segfault happened at: 0xb7e0e0ba : 
pushl  (%eax)
   PC (0xb7e0e0ba) ok
   source "(%eax)" (0x) not located in a known VMA region (needed 
readable region)!
   destination "(%esp)" (0xbfaca794) ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: appstream
  StacktraceTop:
   g_variant_serialiser_needed_size () from /lib/i386-linux-gnu/libglib-2.0.so.0
   ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0
   ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0
   g_variant_serialiser_needed_size () from /lib/i386-linux-gnu/libglib-2.0.so.0
   ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0
  Title: appstreamcli crashed with SIGSEGV in g_variant_serialiser_needed_size()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

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

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

[Desktop-packages] [Bug 1720184] Re: Please merge im-config 0.32-1 (main) from Debian unstable (main)

Since this has been uploaded (although still waiting for manual
approval), I am unsubscribing ubuntu-sponsors. Feel free to re-subscribe
if you have something else that needs sponsoring.

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

Title:
  Please merge im-config 0.32-1 (main) from Debian unstable (main)

Status in im-config package in Ubuntu:
  Fix Committed

Bug description:
  Please merge im-config 0.32-1 (main) from Debian unstable (main)

  Changelogs from ubuntu package:

  im-config (0.32-1) unstable; urgency=medium

[ HIGUCHI Daisuke (VDR dai) ]
* Disable uim-toolbar-gtk{,3}-systray due to outdated.   
  - They are outdated, buggy and have alternatives (uim-toolbar-gtk{,3}).   

* Use uim-toolbar-qt5 instead of uim-toolbar-qt (nonexistent).   
* Wait a sec before starting uim-toolbar.
  - uim-toolbar's spawning is too faster than desktop environment's 
starting.   

   -- Osamu Aoki   Wed, 27 Sep 2017 21:15:24 +0900

  im-config (0.31-1) unstable; urgency=medium

[ Osamu Aoki ]   
* Start ibus with IBUS_ENABLE_SYNC_MODE=0.  Closes: #812826, #838318, 
#876794   
* Add Czech language strings to the desktop file.  Closes: #868036 
* im-config -l doesn't need GUI.  Closes: #804067
* Update PO with trivial unfuzzy. 

[ Boyuan Yang ]
* Refresh debian/copyright file as machine-readable format.

   -- Osamu Aoki   Tue, 26 Sep 2017 22:41:36 +0900

  im-config (0.30-1) unstable; urgency=medium

* New upstream release acknowledging all NMU patches.

   -- Osamu Aoki   Wed, 07 Dec 2016 22:00:16 +0900

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/im-config/+bug/1720184/+subscriptions

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

[Desktop-packages] [Bug 1720630] Re: Amazon S3 storage location missing from Deja Dup 36.1-0ubuntu1

2017-10-01 Thread Michael Terry

I assume your testing was on a fresh system, not an upgrade?

We have intentionally hidden several cloud providers by default. See this wiki 
page for the explanation and how to unhide them:
https://wiki.gnome.org/Apps/DejaDup/Clouds

But on upgrades, your old settings shouldn’t be affected. If that’s the
case, this is a new bug. Otherwise, I’ll mark this bug closed as
intentional behavior.

(You also shouldn’t have to manually install python-boto and such
anymore. If you have S3 set up in deja-dup, we’ll prompt you to install
what we need now.)

** Changed in: deja-dup
   Status: New => Invalid

** Package changed: ubuntu => deja-dup (Ubuntu)

** Changed in: deja-dup (Ubuntu)
   Status: New => Invalid

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

Title:
  Amazon S3 storage location missing from Deja Dup 36.1-0ubuntu1

Status in Déjà Dup:
  Invalid
Status in deja-dup package in Ubuntu:
  Invalid

Bug description:
  I am currently testing out Ubuntu 17.10 and I noticed that Deja Dup
  (version 36.1-0ubuntu1) no longer supports S3 backups. I have already
  installed the packages python-boto python-cloudfiles but the "Amazon
  S3" option is missing from the Storage location tab.

  Using dconfig editor, I can see the S3 records created under
  /org/gnome/deja-dup/s3. The same installation works fine on Ubuntu
  16.04. Any thoughts?

  
  lsb_release -d
  Description:  Ubuntu Artful Aardvark (development branch)

  dpkg-query -W deja-dup duplicity
  deja-dup  36.1-0ubuntu1
  duplicity 

  gsettings list-recursively org.gnome.DejaDup
  org.gnome.DejaDup last-restore ''
  org.gnome.DejaDup periodic false
  org.gnome.DejaDup periodic-period 7
  org.gnome.DejaDup full-backup-period 90
  org.gnome.DejaDup backend 'remote'
  org.gnome.DejaDup last-run ''
  org.gnome.DejaDup nag-check ''
  org.gnome.DejaDup prompt-check '2017-10-01T10:29:53.542958Z'
  org.gnome.DejaDup root-prompt true
  org.gnome.DejaDup include-list ['$HOME']
  org.gnome.DejaDup exclude-list ['$TRASH', '$DOWNLOAD']
  org.gnome.DejaDup last-backup ''
  org.gnome.DejaDup allow-metered false
  org.gnome.DejaDup delete-after 0
  org.gnome.DejaDup.Rackspace username ''
  org.gnome.DejaDup.Rackspace container 'ubuntu'
  org.gnome.DejaDup.S3 id ''
  org.gnome.DejaDup.S3 bucket ''
  org.gnome.DejaDup.S3 folder 'ubuntu'
  org.gnome.DejaDup.OpenStack authurl ''
  org.gnome.DejaDup.OpenStack tenant ''
  org.gnome.DejaDup.OpenStack username ''
  org.gnome.DejaDup.OpenStack container 'ubuntu'
  org.gnome.DejaDup.GCS id ''
  org.gnome.DejaDup.GCS bucket ''
  org.gnome.DejaDup.GCS folder 'ubuntu'
  org.gnome.DejaDup.Local folder 'ubuntu'
  org.gnome.DejaDup.Remote uri ''
  org.gnome.DejaDup.Remote folder 'ubuntu'
  org.gnome.DejaDup.Drive uuid ''
  org.gnome.DejaDup.Drive icon ''
  org.gnome.DejaDup.Drive folder '$HOSTNAME'
  org.gnome.DejaDup.Drive name ''
  org.gnome.DejaDup.GOA id ''
  org.gnome.DejaDup.GOA folder 'ubuntu'
  org.gnome.DejaDup.GOA type 'owncloud'
  org.gnome.DejaDup.File short-name ''
  org.gnome.DejaDup.File type 'normal'
  org.gnome.DejaDup.File migrated true
  org.gnome.DejaDup.File name ''
  org.gnome.DejaDup.File path ''
  org.gnome.DejaDup.File uuid ''
  org.gnome.DejaDup.File icon ''
  org.gnome.DejaDup.File relpath @ay []

To manage notifications about this bug go to:
https://bugs.launchpad.net/deja-dup/+bug/1720630/+subscriptions

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

[Desktop-packages] [Bug 1720692] Re: Add multiarch metadata to libxkbcommon*dev packages

** Description changed:

  Release: Artful Aardvark 17.10
  Package Version: 0.7.1-2
  
  As far as I can tell (after creating a local patch and building and
  installing them as Multi-Arch: same) libxkbcommon-dev and
  libxkbcommon-x11-dev can be safely marked as Multi-Arch: same with no
  additional changes. Note that in order to cross-build the package, I
  also patched the build dependency x11-xkb-utils as Multi-Arch: allowed,
  and then used an :any dep. The use of :any as a dep is possibly
  appropriate, as I successfully built the package this way, I think only
  the tests depend on it, and they seem to call the binaries at runtime
  rather than compiling against them.
+ 
+ Also, tests/x11comp is actually deactivated, and seems to be the only
+ place that uses one of the x11-xkb-utils binaries, so maybe this
+ dependency can just be removed?

** Description changed:

  Release: Artful Aardvark 17.10
  Package Version: 0.7.1-2
  
  As far as I can tell (after creating a local patch and building and
  installing them as Multi-Arch: same) libxkbcommon-dev and
  libxkbcommon-x11-dev can be safely marked as Multi-Arch: same with no
  additional changes. Note that in order to cross-build the package, I
  also patched the build dependency x11-xkb-utils as Multi-Arch: allowed,
  and then used an :any dep. The use of :any as a dep is possibly
  appropriate, as I successfully built the package this way, I think only
  the tests depend on it, and they seem to call the binaries at runtime
  rather than compiling against them.
  
- Also, tests/x11comp is actually deactivated, and seems to be the only
- place that uses one of the x11-xkb-utils binaries, so maybe this
- dependency can just be removed?
+ Also, tests/x11comp is actually deactivated (since Mar 13, 2016
+ upstream), and seems to be the only place that uses one of the x11-xkb-
+ utils binaries, so maybe this dependency can just be removed?

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

Title:
  Add multiarch metadata to libxkbcommon*dev packages

Status in libxkbcommon package in Ubuntu:
  New

Bug description:
  Release: Artful Aardvark 17.10
  Package Version: 0.7.1-2

  As far as I can tell (after creating a local patch and building and
  installing them as Multi-Arch: same) libxkbcommon-dev and
  libxkbcommon-x11-dev can be safely marked as Multi-Arch: same with no
  additional changes. Note that in order to cross-build the package, I
  also patched the build dependency x11-xkb-utils as Multi-Arch:
  allowed, and then used an :any dep. The use of :any as a dep is
  possibly appropriate, as I successfully built the package this way, I
  think only the tests depend on it, and they seem to call the binaries
  at runtime rather than compiling against them.

  Also, tests/x11comp is actually deactivated (since Mar 13, 2016
  upstream), and seems to be the only place that uses one of the x11
  -xkb-utils binaries, so maybe this dependency can just be removed?

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

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

[Desktop-packages] [Bug 1720630] [NEW] Amazon S3 storage location missing from Deja Dup 36.1-0ubuntu1

You have been subscribed to a public bug:

I am currently testing out Ubuntu 17.10 and I noticed that Deja Dup
(version 36.1-0ubuntu1) no longer supports S3 backups. I have already
installed the packages python-boto python-cloudfiles but the "Amazon S3"
option is missing from the Storage location tab.

Using dconfig editor, I can see the S3 records created under /org/gnome
/deja-dup/s3. The same installation works fine on Ubuntu 16.04. Any
thoughts?


lsb_release -d
Description:Ubuntu Artful Aardvark (development branch)

dpkg-query -W deja-dup duplicity
deja-dup36.1-0ubuntu1
duplicity   

gsettings list-recursively org.gnome.DejaDup
org.gnome.DejaDup last-restore ''
org.gnome.DejaDup periodic false
org.gnome.DejaDup periodic-period 7
org.gnome.DejaDup full-backup-period 90
org.gnome.DejaDup backend 'remote'
org.gnome.DejaDup last-run ''
org.gnome.DejaDup nag-check ''
org.gnome.DejaDup prompt-check '2017-10-01T10:29:53.542958Z'
org.gnome.DejaDup root-prompt true
org.gnome.DejaDup include-list ['$HOME']
org.gnome.DejaDup exclude-list ['$TRASH', '$DOWNLOAD']
org.gnome.DejaDup last-backup ''
org.gnome.DejaDup allow-metered false
org.gnome.DejaDup delete-after 0
org.gnome.DejaDup.Rackspace username ''
org.gnome.DejaDup.Rackspace container 'ubuntu'
org.gnome.DejaDup.S3 id ''
org.gnome.DejaDup.S3 bucket ''
org.gnome.DejaDup.S3 folder 'ubuntu'
org.gnome.DejaDup.OpenStack authurl ''
org.gnome.DejaDup.OpenStack tenant ''
org.gnome.DejaDup.OpenStack username ''
org.gnome.DejaDup.OpenStack container 'ubuntu'
org.gnome.DejaDup.GCS id ''
org.gnome.DejaDup.GCS bucket ''
org.gnome.DejaDup.GCS folder 'ubuntu'
org.gnome.DejaDup.Local folder 'ubuntu'
org.gnome.DejaDup.Remote uri ''
org.gnome.DejaDup.Remote folder 'ubuntu'
org.gnome.DejaDup.Drive uuid ''
org.gnome.DejaDup.Drive icon ''
org.gnome.DejaDup.Drive folder '$HOSTNAME'
org.gnome.DejaDup.Drive name ''
org.gnome.DejaDup.GOA id ''
org.gnome.DejaDup.GOA folder 'ubuntu'
org.gnome.DejaDup.GOA type 'owncloud'
org.gnome.DejaDup.File short-name ''
org.gnome.DejaDup.File type 'normal'
org.gnome.DejaDup.File migrated true
org.gnome.DejaDup.File name ''
org.gnome.DejaDup.File path ''
org.gnome.DejaDup.File uuid ''
org.gnome.DejaDup.File icon ''
org.gnome.DejaDup.File relpath @ay []

** Affects: deja-dup
 Importance: Undecided
 Status: Invalid

** Affects: deja-dup (Ubuntu)
 Importance: Undecided
 Status: Invalid


** Tags: artful
-- 
Amazon S3 storage location missing from Deja Dup 36.1-0ubuntu1
https://bugs.launchpad.net/bugs/1720630
You received this bug notification because you are a member of Desktop 
Packages, which is subscribed to deja-dup in Ubuntu.

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

[Desktop-packages] [Bug 1706052] Re: cupsd crashes with SIGSEGV on ubuntu 17.04 on start

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

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

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

Title:
  cupsd crashes with SIGSEGV on ubuntu 17.04 on start

Status in cups package in Ubuntu:
  Confirmed

Bug description:
  Hey,
  I upgraded to Ubuntu 17.04, but CUPS crashes on boot, and when I run cupsd it 
segfaults. Attaching strace ouput.
  --- 
  ApportVersion: 2.20.4-0ubuntu4.4
  Architecture: amd64
  CupsErrorLog:
   
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 17.04
  InstallationDate: Installed on 2012-12-20 (1698 days ago)
  InstallationMedia: Kubuntu 12.10 "Quantal Quetzal" - Release amd64 
(20121017.1)
  Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: Bad 
file descriptor
  MachineType: ASUSTeK COMPUTER INC. UX303LB
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  Package: cups 2.2.2-1ubuntu1
  PackageArchitecture: amd64
  Papersize: letter
  ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-4.10.0-28-generic 
root=UUID=a8690ccc-4675-4e21-896f-eadcc45159f4 ro quiet splash vga=791 
pcie_aspm=force drm.vblankoffdelay=1
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-28-generic 
root=UUID=a8690ccc-4675-4e21-896f-eadcc45159f4 ro quiet splash vga=791 
pcie_aspm=force drm.vblankoffdelay=1
  ProcVersionSignature: Ubuntu 4.10.0-28.32-generic 4.10.17
  Tags:  zesty
  Uname: Linux 4.10.0-28-generic x86_64
  UpgradeStatus: Upgraded to zesty on 2017-04-19 (117 days ago)
  UserGroups: adm bluetooth bumblebee cdrom dialout dip lp lpadmin netdev 
nvidia-persistenced plugdev sambashare sudo usrp
  _MarkForUpload: True
  dmi.bios.date: 03/17/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX303LB.203
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX303LB
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: ATN12345678901234567
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrUX303LB.203:bd03/17/2015:svnASUSTeKCOMPUTERINC.:pnUX303LB:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX303LB:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: UX303LB
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  mtime.conffile..etc.cups.cupsd.conf: 2015-10-21T13:38:49.740915

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

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

[Desktop-packages] [Bug 1720582] Re: gvfs-backends not installed with GIMP

2017-10-01 Thread Bug Watch Updater

** Changed in: gimp (Debian)
   Status: Unknown => New

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

Title:
  gvfs-backends not installed with GIMP

Status in gimp package in Ubuntu:
  Confirmed
Status in gimp package in Debian:
  New

Bug description:
  I am running Kubuntu 17.04.
  I installed the GIMP.
  I tried to use the menu item "Open from location", but it did not work.
  After searching on the Internet, I found out that the GIMP needs a GVFS 
backend in order to fetch an image from the web. I installed gvfs-backends. Now 
the menu item "Open from location" works.

  Problem: A feature from the GIMP does not work by default.
  How to solve: install an additional package.
  Ideal use case: user only needs to install the GIMP.

  Could it be possible to add gvfs-backends as a hard dependency of the
  GIMP?

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: gimp 2.8.20-1
  ProcVersionSignature: Ubuntu 4.10.0-35.39-generic 4.10.17
  Uname: Linux 4.10.0-35-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4.5
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Sat Sep 30 23:21:25 2017
  InstallationDate: Installed on 2015-07-31 (792 days ago)
  InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 
(20150218.1)
  SourcePackage: gimp
  UpgradeStatus: Upgraded to zesty on 2017-05-02 (151 days ago)

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

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

[Desktop-packages] [Bug 1720250] Re: im-config configuration ignored with gdm3

Gunnar, upstart has been removed from Debian 9 "Stretch" and from Ubuntu
17.10.

You should drop the debian/menu too.
https://lintian.debian.org/tags/command-in-menu-file-and-desktop-file.html

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

Title:
  im-config configuration ignored with gdm3

Status in gdm3 package in Ubuntu:
  Confirmed
Status in im-config package in Ubuntu:
  Confirmed

Bug description:
  After having logged in via gdm3, the IM related environment variables
  are always set like this:

  $ env | grep -E '_IM|XMOD'
  QT_IM_MODULE=ibus
  XMODIFIERS=@im=ibus

  Changing ~/.xinputrc to e.g. xim makes no difference, so gdm3 prevents
  all other IM frameworks but IBus from working.

  This problem seems to be similar to bug #1594681 (which was fixed).

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

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

[Desktop-packages] [Bug 1038578] Re: vlc crash

2017-10-01 Thread Sebastian Ramacher

** Changed in: libproxy (Ubuntu)
   Status: Confirmed => Incomplete

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

Title:
  vlc crash

Status in libproxy package in Ubuntu:
  Incomplete
Status in vlc package in Ubuntu:
  Incomplete

Bug description:
  1

  ProblemType: Crash
  DistroRelease: Ubuntu 12.10
  Package: vlc-nox 2.0.3-1
  ProcVersionSignature: Ubuntu 3.5.0-6.6-generic 3.5.0
  Uname: Linux 3.5.0-6-generic i686
  ApportVersion: 2.4-0ubuntu8
  Architecture: i386
  Date: Sun Aug 19 08:05:28 2012
  ExecutablePath: /usr/bin/vlc
  InstallationMedia: Lubuntu 11.04 "Natty Narwhal" - i386 (20101203)
  ProcCmdline: /usr/bin/vlc file://[...]/video.avi
  Signal: 6
  SourcePackage: vlc
  UpgradeStatus: Upgraded to quantal on 2012-07-30 (20 days ago)
  UserGroups: adm admin cdrom dialout lpadmin netdev plugdev sambashare

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

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

[Desktop-packages] [Bug 1720692] [NEW] Add multiarch metadata to libxkbcommon*dev packages

Public bug reported:

Release: Artful Aardvark 17.10
Package Version: 0.7.1-2

As far as I can tell (after creating a local patch and building and
installing them as Multi-Arch: same) libxkbcommon-dev and
libxkbcommon-x11-dev can be safely marked as Multi-Arch: same with no
additional changes. Note that in order to cross-build the package, I
also patched the build dependency x11-xkb-utils as Multi-Arch: allowed,
and then used an :any dep. The use of :any as a dep is possibly
appropriate, as I successfully built the package this way, I think only
the tests depend on it, and they seem to call the binaries at runtime
rather than compiling against them.

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

** Description changed:

+ Release: Artful Aardvark 17.10
+ Package Version: 0.7.1-2
+ 
  As far as I can tell (after creating a local patch and building and
  installing them as Multi-Arch: same) libxkbcommon-dev and
  libxkbcommon-x11-dev can be safely marked as Multi-Arch: same with no
  additional changes. Note that in order to cross-build the package, I
  also patched the build dependency x11-xkb-utils as Multi-Arch: allowed,
  and then used an :any dep. The use of :any as a dep is possibly
  appropriate, as I successfully built the package this way, I think only
  the tests depend on it, and they seem to call the binaries at runtime
  rather than compiling against them.

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

Title:
  Add multiarch metadata to libxkbcommon*dev packages

Status in libxkbcommon package in Ubuntu:
  New

Bug description:
  Release: Artful Aardvark 17.10
  Package Version: 0.7.1-2

  As far as I can tell (after creating a local patch and building and
  installing them as Multi-Arch: same) libxkbcommon-dev and
  libxkbcommon-x11-dev can be safely marked as Multi-Arch: same with no
  additional changes. Note that in order to cross-build the package, I
  also patched the build dependency x11-xkb-utils as Multi-Arch:
  allowed, and then used an :any dep. The use of :any as a dep is
  possibly appropriate, as I successfully built the package this way, I
  think only the tests depend on it, and they seem to call the binaries
  at runtime rather than compiling against them.

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

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

[Desktop-packages] [Bug 1720693] [NEW] [10MVCTO1WW, Realtek ALC294, Black Headphone Out, Front] No sound at all

2017-10-01 Thread Daley Guo

Public bug reported:

There is no sound from the front jack.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: alsa-base 1.0.25+dfsg-0ubuntu5
ProcVersionSignature: Ubuntu 4.10.0-35.39~16.04.1-generic 4.10.17
Uname: Linux 4.10.0-35-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.10
Architecture: amd64
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/hwC0D2', 
'/dev/snd/hwC0D0', '/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', 
'/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D2c', '/dev/snd/pcmC0D0c', 
'/dev/snd/by-path', '/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
CurrentDesktop: Unity
Date: Sun Oct  1 17:49:29 2017
InstallationDate: Installed on 2017-06-08 (115 days ago)
InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
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: Error: command ['pkexec', 'fuser', '-v', 
'/dev/snd/hwC0D2', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', 
'/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D2c', '/dev/snd/pcmC0D0c', 
'/dev/snd/by-path', '/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
Symptom_Jack: Black Headphone Out, Front
Symptom_Type: No sound at all
Symptom_amixerStderr: a m i x e r :   M i x e r   h w : P C H   l o a d   e r r 
o r :   I n v a l i d   a r g u m e n t
Title: [10MVCTO1WW, Realtek ALC294, Black Headphone Out, Front] No sound at all
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 04/13/2017
dmi.bios.vendor: LENOVO
dmi.bios.version: M1AKT17A
dmi.board.name: 310B
dmi.board.vendor: LENOVO
dmi.board.version: SDK0J40709 WIN 3259612472445
dmi.chassis.type: 3
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.modalias: 
dmi:bvnLENOVO:bvrM1AKT17A:bd04/13/2017:svnLENOVO:pn10MVCTO1WW:pvrThinkCentreM910q:rvnLENOVO:rn310B:rvrSDK0J40709WIN3259612472445:cvnLENOVO:ct3:cvrNone:
dmi.product.name: 10MVCTO1WW
dmi.product.version: ThinkCentre M910q
dmi.sys.vendor: LENOVO

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


** Tags: amd64 apport-bug xenial

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

Title:
  [10MVCTO1WW, Realtek ALC294, Black Headphone Out, Front] No sound at
  all

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  There is no sound from the front jack.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.10.0-35.39~16.04.1-generic 4.10.17
  Uname: Linux 4.10.0-35-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/hwC0D2', 
'/dev/snd/hwC0D0', '/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', 
'/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D2c', '/dev/snd/pcmC0D0c', 
'/dev/snd/by-path', '/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CurrentDesktop: Unity
  Date: Sun Oct  1 17:49:29 2017
  InstallationDate: Installed on 2017-06-08 (115 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  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: Error: command ['pkexec', 'fuser', '-v', 
'/dev/snd/hwC0D2', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', 
'/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D2c', '/dev/snd/pcmC0D0c', 
'/dev/snd/by-path', '/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  Symptom_Jack: Black Headphone Out, Front
  Symptom_Type: No sound at all
  Symptom_amixerStderr: a m i x e r :   M i x e r   h w : P C H   l o a d   e r 
r o r :   I n v a l i d   a r g u m e n t
  Title: [10MVCTO1WW, Realtek ALC294, Black Headphone Out, Front] No sound at 
all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/13/2017
  dmi.bios.vendor: LENOVO
  dmi.bios.version: M1AKT17A
  dmi.board.name: 310B
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40709 WIN 3259612472445
  dmi.chassis.type: 3
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrM1AKT17A:bd04/13/2017:svnLENOVO:pn10MVCTO1WW:pvrThinkCentreM910q:rvnLENOVO:rn310B:rvrSDK0J40709WIN3259612472445:cvnLENOVO:ct3:cvrNone:
  dmi.product.name: 10MVCTO1WW
  dmi.product.version: ThinkCentre M910q
  dmi.sys.vendor: LENOVO

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

-- 
Mailing list:

[Desktop-packages] [Bug 1720438] Re: brightness control broken nvidia

2017-10-01 Thread Brinstar

also did you do the update-grub part? but I do think this bug needs a
proper fix

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

Title:
  brightness control broken nvidia

Status in gnome-power-manager package in Ubuntu:
  New

Bug description:
  Ubuntu 17.10 beta 2 
  Nvidia 310M, 340.x official driver installed with Additional Drivers program

  The brightness control built into the laptop (Dell Vostro 3300) isn't 
changing the brightness. Normally I can use Fn + Up/Down arrow keys to change 
the brightness.
  The brightness control works fine in Ubuntu 16.04 with the same driver series.

  I don't know if this is a GNOME 3.26 bug but it's likely as I'm having
  the exact same problem with Fedora 26 on this laptop.

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

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

[Desktop-packages] [Bug 1720438] Re: brightness control broken nvidia

2017-10-01 Thread Brinstar

remember to click the 'This bug affects you' link near the top

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

Title:
  brightness control broken nvidia

Status in gnome-power-manager package in Ubuntu:
  New

Bug description:
  Ubuntu 17.10 beta 2 
  Nvidia 310M, 340.x official driver installed with Additional Drivers program

  The brightness control built into the laptop (Dell Vostro 3300) isn't 
changing the brightness. Normally I can use Fn + Up/Down arrow keys to change 
the brightness.
  The brightness control works fine in Ubuntu 16.04 with the same driver series.

  I don't know if this is a GNOME 3.26 bug but it's likely as I'm having
  the exact same problem with Fedora 26 on this laptop.

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

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

[Desktop-packages] [Bug 1720539] Re: network-manager-openvpn-gnome cannot be installed using GNOME Software

This bug was fixed in the package network-manager-openvpn -
1.2.10-0ubuntu2

---
network-manager-openvpn (1.2.10-0ubuntu2) artful; urgency=medium

  * debian/network-manager-openvpn-gnome.install:
- Install appstream metadata (LP: #1720539)

 -- Jeremy Bicha   Sun, 01 Oct 2017 08:48:53 -0400

** Changed in: network-manager-openvpn (Ubuntu)
   Status: Fix Committed => Fix Released

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

Title:
  network-manager-openvpn-gnome cannot be installed using GNOME Software

Status in network-manager-openvpn package in Ubuntu:
  Fix Released

Bug description:
  The network-manager-openvpn-gnome package cannot be installed using
  GNOME Software as GNOME Control Center add-on because it is missing
  the necessary AppStream metadata.

  Steps to reproduce:
  1. Run GNOME Software.
  2. Search for "Control Center" and select "GNOME Control Center".
  3. See available add-ons at the bottom of the page.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager-openvpn/+bug/1720539/+subscriptions

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

[Desktop-packages] [Bug 1720438] Re: brightness control broken nvidia

2017-10-01 Thread Simone Bordet

Same problem here.

Ubuntu 17.10 beta 2
NVIDIA Corporation GM204M [GeForce GTX 970M]
Driver NVIDIA binary 375.82

Changing the brightness via Fn keys or via Settings/Power does not work.
Adding acpi_osi=Linux does nothing for me, the problem remains.

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

Title:
  brightness control broken nvidia

Status in gnome-power-manager package in Ubuntu:
  New

Bug description:
  Ubuntu 17.10 beta 2 
  Nvidia 310M, 340.x official driver installed with Additional Drivers program

  The brightness control built into the laptop (Dell Vostro 3300) isn't 
changing the brightness. Normally I can use Fn + Up/Down arrow keys to change 
the brightness.
  The brightness control works fine in Ubuntu 16.04 with the same driver series.

  I don't know if this is a GNOME 3.26 bug but it's likely as I'm having
  the exact same problem with Fedora 26 on this laptop.

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

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

[Desktop-packages] [Bug 1720687] [NEW] package python-gi 3.20.0-0ubuntu1 failed to install/upgrade: 子进程已安装 post-installation 脚本返回错误状态 1

2017-10-01 Thread shen maoyuan

Public bug reported:

pinyin can not use

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: python-gi 3.20.0-0ubuntu1
ProcVersionSignature: Ubuntu 4.4.0-70.91-generic 4.4.49
Uname: Linux 4.4.0-70-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.10
Architecture: amd64
Date: Mon Oct  2 04:46:58 2017
DpkgHistoryLog:
 Start-Date: 2017-10-02  04:46:49
 Commandline: apt install ibus-pinyin
 Requested-By: prometheus (1000)
 Install: libpyzy-1.0-0v5:amd64 (1.0.1-4.1, automatic), python-xdg:amd64 
(0.25-4, automatic), libopencc1:amd64 (0.4.3-2build1, automatic), 
python-gi:amd64 (3.20.0-0ubuntu1, automatic), ibus-pinyin:amd64 (1.5.0-3ubuntu3)
ErrorMessage: 子进程 已安装 post-installation 脚本 返回错误状态 1
InstallationDate: Installed on 2017-03-17 (198 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.2
 apt  1.2.24
SourcePackage: pygobject
Title: package python-gi 3.20.0-0ubuntu1 failed to install/upgrade: 子进程 已安装 
post-installation 脚本 返回错误状态 1
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-package xenial

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

Title:
  package python-gi 3.20.0-0ubuntu1 failed to install/upgrade: 子进程 已安装
  post-installation 脚本 返回错误状态 1

Status in pygobject package in Ubuntu:
  New

Bug description:
  pinyin can not use

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: python-gi 3.20.0-0ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-70.91-generic 4.4.49
  Uname: Linux 4.4.0-70-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  Date: Mon Oct  2 04:46:58 2017
  DpkgHistoryLog:
   Start-Date: 2017-10-02  04:46:49
   Commandline: apt install ibus-pinyin
   Requested-By: prometheus (1000)
   Install: libpyzy-1.0-0v5:amd64 (1.0.1-4.1, automatic), python-xdg:amd64 
(0.25-4, automatic), libopencc1:amd64 (0.4.3-2build1, automatic), 
python-gi:amd64 (3.20.0-0ubuntu1, automatic), ibus-pinyin:amd64 (1.5.0-3ubuntu3)
  ErrorMessage: 子进程 已安装 post-installation 脚本 返回错误状态 1
  InstallationDate: Installed on 2017-03-17 (198 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.24
  SourcePackage: pygobject
  Title: package python-gi 3.20.0-0ubuntu1 failed to install/upgrade: 子进程 已安装 
post-installation 脚本 返回错误状态 1
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1502978] Re: fglrx-core 2:15.201-0ubuntu1: fglrx-core kernel module failed to build against kernel 4.3 [firegl_public.c:... error: void value not ignored as it ought to be ...

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

** Changed in: fglrx-installer-updates (Ubuntu Trusty)
   Status: New => Confirmed

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

Title:
  fglrx-core 2:15.201-0ubuntu1: fglrx-core kernel module failed to build
  against kernel 4.3 [firegl_public.c:... error: void value not ignored
  as it ought to be ... seq_printf]

Status in fglrx-installer package in Ubuntu:
  Invalid
Status in fglrx-installer-updates package in Ubuntu:
  Invalid
Status in software-properties package in Ubuntu:
  Invalid
Status in fglrx-installer source package in Trusty:
  Confirmed
Status in fglrx-installer-updates source package in Trusty:
  Confirmed
Status in software-properties source package in Trusty:
  Triaged

Bug description:
  Probably fglrx-installer. 
  However I am not using fglrx , I am using xserver-xorg-video-ati and 
xserver-xorg-video-amdgpu.
  This happened when I installed kernel 4.3.0-040300rc4 in Ubuntu Wily Werewolf.
  Graphic card Radeon R9 380

  ProblemType: Package
  DistroRelease: Ubuntu 15.10
  Package: fglrx-core 2:15.201-0ubuntu1
  Uname: Linux 4.3.0-040300rc4-generic x86_64
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.19-0ubuntu1
  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
  DKMSKernelVersion: 4.3.0-040300rc4-generic
  Date: Mon Oct  5 18:33:50 2015
  DistUpgraded: Fresh install
  DistroCodename: wily
  DistroVariant: ubuntu
  DkmsStatus: fglrx-core, 15.201, 4.2.0-14-generic, x86_64: installed
  DuplicateSignature: 
dkms:fglrx-core:2:15.201-0ubuntu1:/var/lib/dkms/fglrx-core/15.201/build/2.6.x/firegl_public.c:639:9:
 error: void value not ignored as it ought to be
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Tonga PRO [Radeon R9 285/380] 
[1002:6939] (rev f1) (prog-if 00 [VGA controller])
 Subsystem: Micro-Star International Co., Ltd. [MSI] Device [1462:2015]
  InstallationDate: Installed on 2015-02-01 (246 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Alpha amd64 (20150130)
  MachineType: Gigabyte Technology Co., Ltd. GA-MA770-UD3
  PackageVersion: 2:15.201-0ubuntu1
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.3.0-040300rc4-generic 
root=UUID=494a814f-1825-4bfc-941f-1d7ee79111d1 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   dpkg 1.18.2ubuntu4
   apt  1.0.9.10ubuntu7
  SourcePackage: fglrx-installer
  Title: fglrx-core 2:15.201-0ubuntu1: fglrx-core kernel module failed to build
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/09/2009
  dmi.bios.vendor: Award Software International, Inc.
  dmi.bios.version: FA
  dmi.board.name: GA-MA770-UD3
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrFA:bd04/09/2009:svnGigabyteTechnologyCo.,Ltd.:pnGA-MA770-UD3:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-MA770-UD3:rvr:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
  dmi.product.name: GA-MA770-UD3
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  version.compiz: compiz 1:0.9.12.2+15.10.20151002-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.64-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.0.0-1ubuntu1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.0.0-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.17.2-1ubuntu9
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.2-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 
1:7.5.0+git20150819-0ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20150808-0ubuntu2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.11-1ubuntu3
  xserver.bootTime: Mon Oct  5 18:37:05 2015
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.17.2-1ubuntu9
  xserver.video_driver: amdgpu

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/fglrx-installer/+bug/1502978/+subscriptions

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

[Desktop-packages] [Bug 1502978] Re: fglrx-core 2:15.201-0ubuntu1: fglrx-core kernel module failed to build against kernel 4.3 [firegl_public.c:... error: void value not ignored as it ought to be ...

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

** Changed in: fglrx-installer (Ubuntu Trusty)
   Status: New => Confirmed

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

Title:
  fglrx-core 2:15.201-0ubuntu1: fglrx-core kernel module failed to build
  against kernel 4.3 [firegl_public.c:... error: void value not ignored
  as it ought to be ... seq_printf]

Status in fglrx-installer package in Ubuntu:
  Invalid
Status in fglrx-installer-updates package in Ubuntu:
  Invalid
Status in software-properties package in Ubuntu:
  Invalid
Status in fglrx-installer source package in Trusty:
  Confirmed
Status in fglrx-installer-updates source package in Trusty:
  Confirmed
Status in software-properties source package in Trusty:
  Triaged

Bug description:
  Probably fglrx-installer. 
  However I am not using fglrx , I am using xserver-xorg-video-ati and 
xserver-xorg-video-amdgpu.
  This happened when I installed kernel 4.3.0-040300rc4 in Ubuntu Wily Werewolf.
  Graphic card Radeon R9 380

  ProblemType: Package
  DistroRelease: Ubuntu 15.10
  Package: fglrx-core 2:15.201-0ubuntu1
  Uname: Linux 4.3.0-040300rc4-generic x86_64
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.19-0ubuntu1
  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
  DKMSKernelVersion: 4.3.0-040300rc4-generic
  Date: Mon Oct  5 18:33:50 2015
  DistUpgraded: Fresh install
  DistroCodename: wily
  DistroVariant: ubuntu
  DkmsStatus: fglrx-core, 15.201, 4.2.0-14-generic, x86_64: installed
  DuplicateSignature: 
dkms:fglrx-core:2:15.201-0ubuntu1:/var/lib/dkms/fglrx-core/15.201/build/2.6.x/firegl_public.c:639:9:
 error: void value not ignored as it ought to be
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Tonga PRO [Radeon R9 285/380] 
[1002:6939] (rev f1) (prog-if 00 [VGA controller])
 Subsystem: Micro-Star International Co., Ltd. [MSI] Device [1462:2015]
  InstallationDate: Installed on 2015-02-01 (246 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Alpha amd64 (20150130)
  MachineType: Gigabyte Technology Co., Ltd. GA-MA770-UD3
  PackageVersion: 2:15.201-0ubuntu1
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.3.0-040300rc4-generic 
root=UUID=494a814f-1825-4bfc-941f-1d7ee79111d1 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   dpkg 1.18.2ubuntu4
   apt  1.0.9.10ubuntu7
  SourcePackage: fglrx-installer
  Title: fglrx-core 2:15.201-0ubuntu1: fglrx-core kernel module failed to build
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/09/2009
  dmi.bios.vendor: Award Software International, Inc.
  dmi.bios.version: FA
  dmi.board.name: GA-MA770-UD3
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrFA:bd04/09/2009:svnGigabyteTechnologyCo.,Ltd.:pnGA-MA770-UD3:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-MA770-UD3:rvr:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
  dmi.product.name: GA-MA770-UD3
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  version.compiz: compiz 1:0.9.12.2+15.10.20151002-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.64-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.0.0-1ubuntu1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.0.0-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.17.2-1ubuntu9
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.2-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 
1:7.5.0+git20150819-0ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20150808-0ubuntu2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.11-1ubuntu3
  xserver.bootTime: Mon Oct  5 18:37:05 2015
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.17.2-1ubuntu9
  xserver.video_driver: amdgpu

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/fglrx-installer/+bug/1502978/+subscriptions

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

[Desktop-packages] [Bug 1720442] Re: Software (gnome-software) crashes after several seconds. Entirely unusable.

2017-10-01 Thread Dan Bright

While looking through the backtrace, I noticed the references to
libgs_plugin_snap.so. That reminded me, I was messing around with
snapcraft a couple of weeks ago, trying to snap an app of mine (it
didn't end well).

I'm wondering if I inadvertently broke something, possibly removing a
critical snap related file in error (I didn't intentionally remove or
change anything outwith my own created snap files, but wouldn't rule out
having done so erroneously as a possibility).

Either way, in that scenario a resultant gnome-software crash probably
wouldn't be a desired/expected outcome, so I'd imagine the bug would
nevertheless stand, but this is some additional context in case it's
useful.

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

Title:
  Software (gnome-software) crashes after several seconds. Entirely
  unusable.

Status in gnome-software package in Ubuntu:
  Incomplete

Bug description:
  Ubuntu version: Ubuntu Artful Aardvark (development branch), Release: 17.10
  gnome-software package version: 3.26.0-0ubuntu2

  Expected: To be able to use the application.

  What happened instead: The application crashes after several seconds.
  Bug replicated every time the application is opened, rending it
  entirely unusable.

  Journald shows a segfault, as per attached snippet.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-software 3.26.0-0ubuntu2
  ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3
  Uname: Linux 4.13.0-12-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Sep 29 21:01:06 2017
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2017-09-14 (15 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170912)
  InstalledPlugins:
   gnome-software-plugin-flatpak N/A
   gnome-software-plugin-limba   N/A
   gnome-software-plugin-snap3.26.0-0ubuntu2
  SourcePackage: gnome-software
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1714245] Re: 'Add to Favourites' should say 'Lock to Dock' or similar

I added a gnome-shell task since this string comes from gnome-shell.

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

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

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

Title:
  'Add to Favourites' should say 'Lock to Dock' or similar

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

Bug description:
  I was watching Popescu Sorin's video of the Ubuntu session as it was
  two weeks ago ( https://youtu.be/ure54RKSsMM?t=1m27s ) and noticed
  that when right-clicking on a Dock item it says 'Add to Favorites' to
  lock it to the Launcher. Ubuntu users may not know what this
  does...would it be better to change that text to 'Lock to Dock' or
  similar (even though it adds it to favorites too) or should we leave
  it as it is to hopefully familiarize Ubuntu users with how GNOME
  works? Feel free to close as Won't Fix, it's  just a thought.

  Also I checked the ubuntu-dock commits and I can't see any commit that
  fixes this issue so I assume this is still current behavior.

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

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

[Desktop-packages] [Bug 1720250] Re: im-config configuration ignored with gdm3

2017-10-01 Thread Gunnar Hjalmarsson

Thanks, Mitsuya, for valuable input!

As regards the upstart stuff, it was introduced before Unity8, and since
I don't know if all the flavors have switched to systemd for user
session, I'm disinclined to drop it at this time.

I uploaded a test version of im-config here:

https://launchpad.net/~gunnarhj/+archive/ubuntu/im-config

The difference compared to the version in the queue is that I made use
of your im-config.service script and changed the related symlink
accordingly.

Even if the variables seem to be properly set, I made this observation:

$ systemctl --user list-unit-files | grep im-config
im-config.service   disabled

Can't tell if that is of any significance.

Anyway, I'll try to make some experienced developer review this
solution. It looks promising to me.

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

Title:
  im-config configuration ignored with gdm3

Status in gdm3 package in Ubuntu:
  Confirmed
Status in im-config package in Ubuntu:
  Confirmed

Bug description:
  After having logged in via gdm3, the IM related environment variables
  are always set like this:

  $ env | grep -E '_IM|XMOD'
  QT_IM_MODULE=ibus
  XMODIFIERS=@im=ibus

  Changing ~/.xinputrc to e.g. xim makes no difference, so gdm3 prevents
  all other IM frameworks but IBus from working.

  This problem seems to be similar to bug #1594681 (which was fixed).

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

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

[Desktop-packages] [Bug 1720149] Re: gnome-shell segv on wake from display or system sleep

2017-10-01 Thread Rachel Greenham

ok, same symptoms occurred with the default theme. So after all it looks
like the shell theme has nothing to do with it.

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

Title:
  gnome-shell segv on wake from display or system sleep

Status in gnome-shell package in Ubuntu:
  Confirmed

Bug description:
  The observable symptom is that if I go away and let the computer go
  either to display sleep or suspend, when I come back and try to wake
  it up again, I find myself, after sliding up the lock screen, at the
  gdm login screen. I'm logged out, and logging in gives me a fresh new
  session. Anything I had open in the previous session is lost. (I'm
  getting used to saving stuff before I step away from the computer!)

  The only trace I've been able to find is that in /var/log/syslog I see
  a line like:

  Sep 28 14:38:44 fleetfoot kernel: [10621.432586] gnome-shell[1863]:
  segfault at 2c ip 7f6200e82434 sp 7ffc46f981c8 error 4 in
  libmutter-1.so.0.0.0[7f6200de4000+14]

  This happens at the time of attempted wake, not the time of going to
  sleep. It's preceded by a lot of activity from gdm-x-session that I'm
  not sure is indicating any error, just the process of waking up. I
  will attach a portion of syslog surrounding the whole event in the
  hope it helps. (In fact attaching the whole current syslog file - it
  has two such events occuring in it, first display sleep/wake at 09:02
  this morning, and secondly (because I was experimenting) a suspend-
  wake at 14:38 this afternoon.

  This is only affecting Xorg sessions, and may possibly only be
  affecting where nvidia is in use, I'm not sure about that. But the
  fact it occurs on display wake alone, not needing the system itself to
  have suspended (I was trying suspend to see if it *avoided* the
  problem, which it doesn't), does point the finger in that direction I
  guess. But ultimately I'm guessing it's gnome-shell itself segfaulting
  that's causing the login session to end?

  Not observed on my Wayland system.

  This is not new as of the current version of gnome-shell but I think
  it is relatively recent. Now my hackintosh partition is wrecked by a
  failed upgrade to High Sierra I'm using my Linux system more in
  earnest than before, so I'm hitting this often enough for it to
  provoke a bug report (and much of the time, to just turn all auto
  suspend/display-sleep off and instead shut down the computer when I'm
  leaving it for any length of time).

  The ubuntu bug reporter is not picking this up by itself, so I presume
  a crash report of the sort that uses is not being saved.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.26.0-0ubuntu2
  ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3
  Uname: Linux 4.13.0-12-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Thu Sep 28 14:41:07 2017
  DisplayManager: gdm3
  InstallationDate: Installed on 2017-07-30 (59 days ago)
  InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412)
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to artful on 2017-08-22 (37 days ago)

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

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

[Desktop-packages] [Bug 1720442] Re: Software (gnome-software) crashes after several seconds. Entirely unusable.

2017-10-01 Thread Dan Bright

My pleasure Sebastien, very happy to help. 
Please don't hesitate to get back to me if you require any further details or 
testing.

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

Title:
  Software (gnome-software) crashes after several seconds. Entirely
  unusable.

Status in gnome-software package in Ubuntu:
  Incomplete

Bug description:
  Ubuntu version: Ubuntu Artful Aardvark (development branch), Release: 17.10
  gnome-software package version: 3.26.0-0ubuntu2

  Expected: To be able to use the application.

  What happened instead: The application crashes after several seconds.
  Bug replicated every time the application is opened, rending it
  entirely unusable.

  Journald shows a segfault, as per attached snippet.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-software 3.26.0-0ubuntu2
  ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3
  Uname: Linux 4.13.0-12-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Sep 29 21:01:06 2017
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2017-09-14 (15 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170912)
  InstalledPlugins:
   gnome-software-plugin-flatpak N/A
   gnome-software-plugin-limba   N/A
   gnome-software-plugin-snap3.26.0-0ubuntu2
  SourcePackage: gnome-software
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1720442] Re: Software (gnome-software) crashes after several seconds. Entirely unusable.

2017-10-01 Thread Dan Bright

** Attachment added: "backtrace"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1720442/+attachment/4960053/+files/gdb-gnome-software.txt

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

Title:
  Software (gnome-software) crashes after several seconds. Entirely
  unusable.

Status in gnome-software package in Ubuntu:
  Incomplete

Bug description:
  Ubuntu version: Ubuntu Artful Aardvark (development branch), Release: 17.10
  gnome-software package version: 3.26.0-0ubuntu2

  Expected: To be able to use the application.

  What happened instead: The application crashes after several seconds.
  Bug replicated every time the application is opened, rending it
  entirely unusable.

  Journald shows a segfault, as per attached snippet.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-software 3.26.0-0ubuntu2
  ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3
  Uname: Linux 4.13.0-12-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Sep 29 21:01:06 2017
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2017-09-14 (15 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170912)
  InstalledPlugins:
   gnome-software-plugin-flatpak N/A
   gnome-software-plugin-limba   N/A
   gnome-software-plugin-snap3.26.0-0ubuntu2
  SourcePackage: gnome-software
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1707451] Re: udisksd crashed with SIGSEGV in g_mutex_lock()

2017-10-01 Thread Bernard Banko

Don't know if this is related, but I had phone plugged in usb and than
set it to charge only.

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

Title:
  udisksd crashed with SIGSEGV in g_mutex_lock()

Status in udisks2 package in Ubuntu:
  Confirmed

Bug description:
  Showed up after login

  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: udisks2 2.6.5-2ubuntu1
  ProcVersionSignature: Ubuntu 4.11.0-10.15-generic 4.11.8
  Uname: Linux 4.11.0-10-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.6-0ubuntu4
  Architecture: amd64
  Date: Sun Jul 30 00:35:31 2017
  ExecutablePath: /usr/lib/udisks2/udisksd
  InstallationDate: Installed on 2017-06-22 (37 days ago)
  InstallationMedia: Ubuntu-GNOME 17.10 "Artful Aardvark" - Alpha amd64 
(20170622)
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  ProcCmdline: /usr/lib/udisks2/udisksd
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.11.0-10-generic.efi.signed 
root=UUID=44b31662-d2ab-443b-9546-86d022d8de0d ro quiet splash vt.handoff=7
  SegvAnalysis:
   Segfault happened at: 0x7f4900fb5c65 :   lock xadd 
%eax,(%rdi)
   PC (0x7f4900fb5c65) ok
   source "%eax" ok
   destination "(%rdi)" (0x3a9d80e262617474) not located in a known VMA region 
(needed writable region)!
  SegvReason: writing unknown VMA
  Signal: 11
  SourcePackage: udisks2
  StacktraceTop:
   g_mutex_lock () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   main ()
  Title: udisksd crashed with SIGSEGV in g_mutex_lock()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  dmi.bios.date: 04/12/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P3.40
  dmi.board.name: Z87 Extreme4
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP3.40:bd04/12/2016:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnZ87Extreme4:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.

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

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

[Desktop-packages] [Bug 1720675] Re: nautilus crashed with SIGABRT in raise()

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

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

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

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

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

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

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

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

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

** This bug has been marked a duplicate of private bug 1676799

** Information type changed from Private to Public

** Tags removed: need-amd64-retrace

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

Title:
  nautilus crashed with SIGABRT in raise()

Status in nautilus package in Ubuntu:
  New

Bug description:
  Dont know whether duplicate. Didn't bother checking.

  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: nautilus 1:3.26.0-0ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3
  Uname: Linux 4.12.0-13-generic x86_64
  ApportVersion: 2.20.7-0ubuntu2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Oct  1 20:29:36 2017
  ExecutablePath: /usr/bin/nautilus
  ProcCmdline: /usr/bin/nautilus --gapplication-service
  Signal: 6
  SourcePackage: nautilus
  StacktraceTop:
   raise () from /lib/x86_64-linux-gnu/libc.so.6
   abort () from /lib/x86_64-linux-gnu/libc.so.6
   g_assertion_message () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_assertion_message_expr () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
  Title: nautilus crashed with SIGABRT in raise()
  UpgradeStatus: Upgraded to artful on 2017-08-29 (33 days ago)
  UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo

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

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

[Desktop-packages] [Bug 1720149] Re: gnome-shell segv on wake from display or system sleep

2017-10-01 Thread Rachel Greenham

well I spoke too soon. Crash occurred with the locally 'built' arc
theme. Slightly different though in that this time it *did* hang the
system. But it started with the same segv message logged. So back to the
default+Ambiance theme to test that for longer.

Problem with trying to prove a negative. You can only say "Well it
hasn't crashed *yet*" until it does. Damn, I liked that theme. :-(

(Of course, now to try to prove the same negative about the default
theme... I kind of hope it fails too now so it's not my favourite
theme's fault.)

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

Title:
  gnome-shell segv on wake from display or system sleep

Status in gnome-shell package in Ubuntu:
  Confirmed

Bug description:
  The observable symptom is that if I go away and let the computer go
  either to display sleep or suspend, when I come back and try to wake
  it up again, I find myself, after sliding up the lock screen, at the
  gdm login screen. I'm logged out, and logging in gives me a fresh new
  session. Anything I had open in the previous session is lost. (I'm
  getting used to saving stuff before I step away from the computer!)

  The only trace I've been able to find is that in /var/log/syslog I see
  a line like:

  Sep 28 14:38:44 fleetfoot kernel: [10621.432586] gnome-shell[1863]:
  segfault at 2c ip 7f6200e82434 sp 7ffc46f981c8 error 4 in
  libmutter-1.so.0.0.0[7f6200de4000+14]

  This happens at the time of attempted wake, not the time of going to
  sleep. It's preceded by a lot of activity from gdm-x-session that I'm
  not sure is indicating any error, just the process of waking up. I
  will attach a portion of syslog surrounding the whole event in the
  hope it helps. (In fact attaching the whole current syslog file - it
  has two such events occuring in it, first display sleep/wake at 09:02
  this morning, and secondly (because I was experimenting) a suspend-
  wake at 14:38 this afternoon.

  This is only affecting Xorg sessions, and may possibly only be
  affecting where nvidia is in use, I'm not sure about that. But the
  fact it occurs on display wake alone, not needing the system itself to
  have suspended (I was trying suspend to see if it *avoided* the
  problem, which it doesn't), does point the finger in that direction I
  guess. But ultimately I'm guessing it's gnome-shell itself segfaulting
  that's causing the login session to end?

  Not observed on my Wayland system.

  This is not new as of the current version of gnome-shell but I think
  it is relatively recent. Now my hackintosh partition is wrecked by a
  failed upgrade to High Sierra I'm using my Linux system more in
  earnest than before, so I'm hitting this often enough for it to
  provoke a bug report (and much of the time, to just turn all auto
  suspend/display-sleep off and instead shut down the computer when I'm
  leaving it for any length of time).

  The ubuntu bug reporter is not picking this up by itself, so I presume
  a crash report of the sort that uses is not being saved.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.26.0-0ubuntu2
  ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3
  Uname: Linux 4.13.0-12-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Thu Sep 28 14:41:07 2017
  DisplayManager: gdm3
  InstallationDate: Installed on 2017-07-30 (59 days ago)
  InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412)
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to artful on 2017-08-22 (37 days ago)

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

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

[Desktop-packages] [Bug 1720671] [NEW] meow

2017-10-01 Thread Beth

Public bug reported:

I don't know

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg 1:7.7+13ubuntu3
ProcVersionSignature: Ubuntu 4.10.0-28.32~16.04.2-generic 4.10.17
Uname: Linux 4.10.0-28-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: None
Date: Sun Oct  1 20:47:08 2017
DistUpgraded: Fresh install
DistroCodename: xenial
DistroVariant: ubuntu
GraphicsCard:
 NVIDIA Corporation G84 [GeForce 8600 GT] [10de:0402] (rev a1) (prog-if 00 [VGA 
controller])
   Subsystem: eVga.com. Corp. G84 [GeForce 8600 GT] [3842:c795]
InstallationDate: Installed on 2017-10-01 (0 days ago)
InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801)
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-28-generic 
root=UUID=7a5959d8-5b1c-457d-b654-05ac59e53525 ro quiet splash vt.handoff=7
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 02/18/2008
dmi.bios.vendor: Intel Corp.
dmi.bios.version: DPP3510J.86A.0407.2008.0218.0923
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: DP35DP
dmi.board.vendor: Intel Corporation
dmi.board.version: AAD81073-208
dmi.chassis.type: 3
dmi.modalias: 
dmi:bvnIntelCorp.:bvrDPP3510J.86A.0407.2008.0218.0923:bd02/18/2008:svn:pn:pvr:rvnIntelCorporation:rnDP35DP:rvrAAD81073-208:cvn:ct3:cvr:
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 17.0.7-0ubuntu0.16.04.1
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.7-0ubuntu0.16.04.1
version.xserver-xorg-core: xserver-xorg-core N/A
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
xserver.bootTime: Sun Oct  1 18:57:52 2017
xserver.configfile: default
xserver.devices:
 inputPower Button KEYBOARD, id 6
 inputSleep Button KEYBOARD, id 7
 inputGenius Optical Mouse MOUSE, id 8
 inputSIGMACHIP USB Keyboard KEYBOARD, id 9
 inputSIGMACHIP USB Keyboard KEYBOARD, id 10
xserver.errors:
 Failed to load module "nvidia" (module does not exist, 0)
 Failed to load module "nvidia" (module does not exist, 0)
xserver.logfile: /var/log/Xorg.0.log
xserver.version: 2:1.19.3-1ubuntu1~16.04.2
xserver.video_driver: nouveau

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


** Tags: amd64 apport-bug 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/1720671

Title:
  meow

Status in xorg package in Ubuntu:
  New

Bug description:
  I don't know

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.10.0-28.32~16.04.2-generic 4.10.17
  Uname: Linux 4.10.0-28-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: None
  Date: Sun Oct  1 20:47:08 2017
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  GraphicsCard:
   NVIDIA Corporation G84 [GeForce 8600 GT] [10de:0402] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: eVga.com. Corp. G84 [GeForce 8600 GT] [3842:c795]
  InstallationDate: Installed on 2017-10-01 (0 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-28-generic 
root=UUID=7a5959d8-5b1c-457d-b654-05ac59e53525 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/18/2008
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: DPP3510J.86A.0407.2008.0218.0923
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: DP35DP
  dmi.board.vendor: Intel Corporation
  dmi.board.version: AAD81073-208
  dmi.chassis.type: 3
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrDPP3510J.86A.0407.2008.0218.0923:bd02/18/2008:svn:pn:pvr:rvnIntelCorporation:rnDP35DP:rvrAAD81073-208:cvn:ct3:cvr:
  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 17.0.7-0ubuntu0.16.04.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.7-0ubuntu0.16.04.1
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev

[Desktop-packages] [Bug 1720668] [NEW] Graphics glitches on top of screen (Intel HD 4400)

2017-10-01 Thread Egor Khromov

Public bug reported:

There are graphics glitches near right top corner of the screen in every Linux 
distro and FreeBSD. Glitches appear every 0.2-5 seconds constantly.
Screen resolution: 1600x900
GPU: Intel HD 4400 (integrated in Intel Core i5 4200u).
There is no such issue in Windows.
You can download video with this bug there https://yadi.sk/i/5qeZ12Z_3NNUep

ProblemType: Bug
DistroRelease: Ubuntu 17.04
Package: libgl1-mesa-dri 17.0.7-0ubuntu0.17.04.1
ProcVersionSignature: Ubuntu 4.10.0-35.39-generic 4.10.17
Uname: Linux 4.10.0-35-generic x86_64
ApportVersion: 2.20.4-0ubuntu4.5
Architecture: amd64
CurrentDesktop: XFCE
Date: Sun Oct  1 19:18:16 2017
InstallationDate: Installed on 2017-09-14 (16 days ago)
InstallationMedia: Xubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
SourcePackage: mesa
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug zesty

** Description changed:

- There are graphics glitches near right top corner of the screen in every 
Linux distro and FreeBSD. Glitches appear constantly every 0.2-5 seconds 
constantly.
+ There are graphics glitches near right top corner of the screen in every 
Linux distro and FreeBSD. Glitches appear every 0.2-5 seconds constantly.
  Screen resolution: 1600x900
  GPU: Intel HD 4400 (integrated in Intel Core i5 4200u).
  There is no such issue in Windows.
  You can download video with this bug there https://yadi.sk/i/5qeZ12Z_3NNUep
  
  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: libgl1-mesa-dri 17.0.7-0ubuntu0.17.04.1
  ProcVersionSignature: Ubuntu 4.10.0-35.39-generic 4.10.17
  Uname: Linux 4.10.0-35-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4.5
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Sun Oct  1 19:18:16 2017
  InstallationDate: Installed on 2017-09-14 (16 days ago)
  InstallationMedia: Xubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  SourcePackage: mesa
  UpgradeStatus: No upgrade log present (probably fresh install)

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

Title:
  Graphics glitches on top of screen (Intel HD 4400)

Status in mesa package in Ubuntu:
  New

Bug description:
  There are graphics glitches near right top corner of the screen in every 
Linux distro and FreeBSD. Glitches appear every 0.2-5 seconds constantly.
  Screen resolution: 1600x900
  GPU: Intel HD 4400 (integrated in Intel Core i5 4200u).
  There is no such issue in Windows.
  You can download video with this bug there https://yadi.sk/i/5qeZ12Z_3NNUep

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: libgl1-mesa-dri 17.0.7-0ubuntu0.17.04.1
  ProcVersionSignature: Ubuntu 4.10.0-35.39-generic 4.10.17
  Uname: Linux 4.10.0-35-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4.5
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Sun Oct  1 19:18:16 2017
  InstallationDate: Installed on 2017-09-14 (16 days ago)
  InstallationMedia: Xubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  SourcePackage: mesa
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1720649] Re: broken gnome expirience caused by unity-compatible patch

** Description changed:

  Standard gnome behavior doesn't allow to draw rhythmbox menubar, because
  all the controls are available through the "settings (gear) button".
  Ubuntu 17.10 draws menu, because of unity-compatible patch, you should
  remove it, to provide true gnome expirience. Menubar is bloatware.
  
  Problem occurs if you disable top bar application menu in Gnome Tweaks,
  and start Rhythmbox after that. See attached screenshot. Please, remove
  menubar patch.
  
+ Ubuntu 17.10, rhythmbox-3.4.1-2ubuntu5.
+ 
  You should also check other Gnome apps!!! AFAIK, Totem, default video
  player also has some patch like this, and you even cant hide menubar in
  fullscreen mode (!). I'm using mpv, so i dont care.

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

Title:
  broken gnome expirience caused by unity-compatible patch

Status in rhythmbox package in Ubuntu:
  New

Bug description:
  Standard gnome behavior doesn't allow to draw rhythmbox menubar,
  because all the controls are available through the "settings (gear)
  button". Ubuntu 17.10 draws menu, because of unity-compatible patch,
  you should remove it, to provide true gnome expirience. Menubar is
  bloatware.

  Problem occurs if you disable top bar application menu in Gnome
  Tweaks, and start Rhythmbox after that. See attached screenshot.
  Please, remove menubar patch.

  Ubuntu 17.10, rhythmbox-3.4.1-2ubuntu5.

  You should also check other Gnome apps!!! AFAIK, Totem, default video
  player also has some patch like this, and you even cant hide menubar
  in fullscreen mode (!). I'm using mpv, so i dont care.

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

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

[Desktop-packages] [Bug 1720651] Re: Scrollbar drawing broken on wayland sesssion

** Description changed:

  Scrollbar drawing broken, with light theme variant on wayland session.
  See attached screenshot (white line right of scrollbar). To fix this you
  should remove some unity-compatible patch.
+ 
+ Ubuntu 17.10, gnome-terminal-3.24.2-0ubuntu4

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

Title:
  Scrollbar drawing broken on wayland sesssion

Status in gnome-terminal package in Ubuntu:
  New

Bug description:
  Scrollbar drawing broken, with light theme variant on wayland session.
  See attached screenshot (white line right of scrollbar). To fix this
  you should remove some unity-compatible patch.

  Ubuntu 17.10, gnome-terminal-3.24.2-0ubuntu4

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

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

[Desktop-packages] [Bug 1661098] Re: NetworkManager-openvpn mishandles the comp-lzo option, thereby breaking the ovpn config and causing AUTH_FAILED

2017-10-01 Thread Amr Ibrahim

** Changed in: network-manager-openvpn (Ubuntu)
   Status: Fix Committed => Fix Released

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

Title:
  NetworkManager-openvpn mishandles the comp-lzo option, thereby
  breaking the ovpn config and causing AUTH_FAILED

Status in NetworkManager-OpenVPN:
  Fix Released
Status in network-manager-openvpn package in Ubuntu:
  Fix Released

Bug description:
  Attempting to establish an OpenVPN session via network-manager-openvpn
  fails with a password authentication error, even though the username
  and password I entered are correct.  The following messages in syslog:

  Feb  1 12:44:54 computer nm-openvpn[21582]: NOTE: the current 
--script-security setting may allow this configuration to call user-defined 
scripts
  Feb  1 12:44:54 computer nm-openvpn[21582]: UDPv4 link local: [undef]
  Feb  1 12:44:54 computer nm-openvpn[21582]: UDPv4 link remote: 
[AF_INET]209.148.113.36:1194
  Feb  1 12:44:54 computer nm-openvpn[21582]: WARNING: 'link-mtu' is used 
inconsistently, local='link-mtu 1557', remote='link-mtu 1558'
  Feb  1 12:44:54 computer nm-openvpn[21582]: WARNING: 'comp-lzo' is 
present in remote config but missing in local config, remote='comp-lzo'
  Feb  1 12:44:54 computer nm-openvpn[21582]: [OpenVPN Server] Peer 
Connection Initiated with [AF_INET]209.148.113.36:1194
  Feb  1 12:44:56 computer nm-openvpn[21582]: AUTH: Received control 
message: AUTH_FAILED
  Feb  1 12:44:56 computer nm-openvpn[21582]: SIGUSR1[soft,auth-failure] 
received, process restarting
  Feb  1 12:44:56 computer NetworkManager[1322]: nm-openvpn[21574]   
Password verification failed

  I am able to establish the session by manually running openvpn from
  the command line, using the same username, password, and the ovpn file
  from which NetworkManager imported the setttings.

  I'm running Xubuntu 16.10 (yakkety).
  I did not have this problem in Ubuntu 16.04 (xenial).

To manage notifications about this bug go to:
https://bugs.launchpad.net/network-manager-openvpn/+bug/1661098/+subscriptions

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

[Desktop-packages] [Bug 1720654] Re: Totem menu is totally broken

** Description changed:

  Open Totem with disabled "top bar application menu" option in Gnome
  Tweaks. See this (screenshot). Menu is coming from unity-compatible
  patch, original gnome behavior - menu should go to button with totem
  icon left of the "+" button. Worst thing - MENU IS ALWAYS VISIBLE, EVEN
- IN FULLSCREEN MODE WITH MOVIE PLAYING!!!
+ IN FULLSCREEN MODE WITH MOVIE PLAYING!!! (Ubuntu 17.10)

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

Title:
  Totem menu is totally broken

Status in totem package in Ubuntu:
  New

Bug description:
  Open Totem with disabled "top bar application menu" option in Gnome
  Tweaks. See this (screenshot). Menu is coming from unity-compatible
  patch, original gnome behavior - menu should go to button with totem
  icon left of the "+" button. Worst thing - MENU IS ALWAYS VISIBLE,
  EVEN IN FULLSCREEN MODE WITH MOVIE PLAYING!!! (Ubuntu 17.10)

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

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

[Desktop-packages] [Bug 1720649] Re: broken gnome expirience caused by unity-compatible patch

Actuall, i also checked and reported totem bug
https://bugs.launchpad.net/ubuntu/+source/totem/+bug/1720654 , but
please, consider to check all of gtk3-applications which were patched
for unity de.

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

Title:
  broken gnome expirience caused by unity-compatible patch

Status in rhythmbox package in Ubuntu:
  New

Bug description:
  Standard gnome behavior doesn't allow to draw rhythmbox menubar,
  because all the controls are available through the "settings (gear)
  button". Ubuntu 17.10 draws menu, because of unity-compatible patch,
  you should remove it, to provide true gnome expirience. Menubar is
  bloatware.

  Problem occurs if you disable top bar application menu in Gnome
  Tweaks, and start Rhythmbox after that. See attached screenshot.
  Please, remove menubar patch.

  You should also check other Gnome apps!!! AFAIK, Totem, default video
  player also has some patch like this, and you even cant hide menubar
  in fullscreen mode (!). I'm using mpv, so i dont care.

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

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

[Desktop-packages] [Bug 1720654] Re: Totem menu is totally broken

Found correct menu look, flat button in top left corner:

https://doc.opensuse.org/documentation/leap/gnomeuser/html/book.gnomeuser/images/totem_a.png

** Description changed:

Open Totem with disabled "top bar application menu" option in Gnome
Tweaks. See this (screenshot). Menu is coming from unity-compatible
patch, original gnome behavior - menu should go to button with totem
- icon right of the "+" button. Worst thing - MENU IS ALWAYS VISIBLE, EVEN
+ icon left of the "+" button. Worst thing - MENU IS ALWAYS VISIBLE, EVEN
IN FULLSCREEN MODE WITH MOVIE PLAYING!!!

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

Title:
Totem menu is totally broken

Status in totem package in Ubuntu:
New

Bug description:
Open Totem with disabled "top bar application menu" option in Gnome
Tweaks. See this (screenshot). Menu is coming from unity-compatible
patch, original gnome behavior - menu should go to button with totem
icon left of the "+" button. Worst thing - MENU IS ALWAYS VISIBLE,
EVEN IN FULLSCREEN MODE WITH MOVIE PLAYING!!!

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

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

[Desktop-packages] [Bug 1720654] [NEW] Totem menu is totally broken

Public bug reported:

Open Totem with disabled "top bar application menu" option in Gnome
Tweaks. See this (screenshot). Menu is coming from unity-compatible
patch, original gnome behavior - menu should go to button with totem
icon right of the "+" button. Worst thing - MENU IS ALWAYS VISIBLE, EVEN
IN FULLSCREEN MODE WITH MOVIE PLAYING!!!

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

** Attachment added: "screenshot"
   
https://bugs.launchpad.net/bugs/1720654/+attachment/4959888/+files/bugrep-totem.png

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

Title:
  Totem menu is totally broken

Status in totem package in Ubuntu:
  New

Bug description:
  Open Totem with disabled "top bar application menu" option in Gnome
  Tweaks. See this (screenshot). Menu is coming from unity-compatible
  patch, original gnome behavior - menu should go to button with totem
  icon right of the "+" button. Worst thing - MENU IS ALWAYS VISIBLE,
  EVEN IN FULLSCREEN MODE WITH MOVIE PLAYING!!!

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

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

[Desktop-packages] [Bug 1720653] Re: package gconf2 3.2.6-3ubuntu7 failed to install/upgrade: dependency problems - leaving triggers unprocessed

** Tags removed: need-duplicate-check

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

Title:
  package gconf2 3.2.6-3ubuntu7 failed to install/upgrade: dependency
  problems - leaving triggers unprocessed

Status in gconf package in Ubuntu:
  New

Bug description:
  2 to 5 times diff bugs popped up

  ProblemType: Package
  DistroRelease: Ubuntu 17.04
  Package: gconf2 3.2.6-3ubuntu7
  ProcVersionSignature: Ubuntu 4.4.0-96.119-generic 4.4.83
  Uname: Linux 4.4.0-96-generic x86_64
  NonfreeKernelModules: vboxpci vboxnetadp vboxnetflt vboxdrv wl
  ApportVersion: 2.20.4-0ubuntu4.5
  Architecture: amd64
  Date: Sun Oct  1 18:54:49 2017
  ErrorMessage: dependency problems - leaving triggers unprocessed
  InstallationDate: Installed on 2017-05-22 (132 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu2
   apt  1.4.6~17.04.1
  SourcePackage: gconf
  Title: package gconf2 3.2.6-3ubuntu7 failed to install/upgrade: dependency 
problems - leaving triggers unprocessed
  UpgradeStatus: Upgraded to zesty on 2017-10-01 (0 days ago)

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

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

[Desktop-packages] [Bug 1720653] [NEW] package gconf2 3.2.6-3ubuntu7 failed to install/upgrade: dependency problems - leaving triggers unprocessed

2017-10-01 Thread shubham

Public bug reported:

2 to 5 times diff bugs popped up

ProblemType: Package
DistroRelease: Ubuntu 17.04
Package: gconf2 3.2.6-3ubuntu7
ProcVersionSignature: Ubuntu 4.4.0-96.119-generic 4.4.83
Uname: Linux 4.4.0-96-generic x86_64
NonfreeKernelModules: vboxpci vboxnetadp vboxnetflt vboxdrv wl
ApportVersion: 2.20.4-0ubuntu4.5
Architecture: amd64
Date: Sun Oct  1 18:54:49 2017
ErrorMessage: dependency problems - leaving triggers unprocessed
InstallationDate: Installed on 2017-05-22 (132 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
RelatedPackageVersions:
 dpkg 1.18.10ubuntu2
 apt  1.4.6~17.04.1
SourcePackage: gconf
Title: package gconf2 3.2.6-3ubuntu7 failed to install/upgrade: dependency 
problems - leaving triggers unprocessed
UpgradeStatus: Upgraded to zesty on 2017-10-01 (0 days ago)

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


** Tags: amd64 apport-package zesty

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

Title:
  package gconf2 3.2.6-3ubuntu7 failed to install/upgrade: dependency
  problems - leaving triggers unprocessed

Status in gconf package in Ubuntu:
  New

Bug description:
  2 to 5 times diff bugs popped up

  ProblemType: Package
  DistroRelease: Ubuntu 17.04
  Package: gconf2 3.2.6-3ubuntu7
  ProcVersionSignature: Ubuntu 4.4.0-96.119-generic 4.4.83
  Uname: Linux 4.4.0-96-generic x86_64
  NonfreeKernelModules: vboxpci vboxnetadp vboxnetflt vboxdrv wl
  ApportVersion: 2.20.4-0ubuntu4.5
  Architecture: amd64
  Date: Sun Oct  1 18:54:49 2017
  ErrorMessage: dependency problems - leaving triggers unprocessed
  InstallationDate: Installed on 2017-05-22 (132 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu2
   apt  1.4.6~17.04.1
  SourcePackage: gconf
  Title: package gconf2 3.2.6-3ubuntu7 failed to install/upgrade: dependency 
problems - leaving triggers unprocessed
  UpgradeStatus: Upgraded to zesty on 2017-10-01 (0 days ago)

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

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

[Desktop-packages] [Bug 1720651] [NEW] Scrollbar drawing broken on wayland sesssion

Public bug reported:

Scrollbar drawing broken, with light theme variant on wayland session.
See attached screenshot (white line right of scrollbar). To fix this you
should remove some unity-compatible patch.

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

** Attachment added: "screenshot"
   
https://bugs.launchpad.net/bugs/1720651/+attachment/4959869/+files/bugrep-terminal.png

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

Title:
  Scrollbar drawing broken on wayland sesssion

Status in gnome-terminal package in Ubuntu:
  New

Bug description:
  Scrollbar drawing broken, with light theme variant on wayland session.
  See attached screenshot (white line right of scrollbar). To fix this
  you should remove some unity-compatible patch.

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

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

[Desktop-packages] [Bug 1720582] Re: gvfs-backends not installed with GIMP

2017-10-01 Thread Ross Gammon

Gvfs-backends is "suggested" by Gimp. I have asked on the Debian bug
that it is moved to Depends (Or at least Recommends).

Thanks for reporting!

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

Title:
  gvfs-backends not installed with GIMP

Status in gimp package in Ubuntu:
  Confirmed
Status in gimp package in Debian:
  Unknown

Bug description:
  I am running Kubuntu 17.04.
  I installed the GIMP.
  I tried to use the menu item "Open from location", but it did not work.
  After searching on the Internet, I found out that the GIMP needs a GVFS 
backend in order to fetch an image from the web. I installed gvfs-backends. Now 
the menu item "Open from location" works.

  Problem: A feature from the GIMP does not work by default.
  How to solve: install an additional package.
  Ideal use case: user only needs to install the GIMP.

  Could it be possible to add gvfs-backends as a hard dependency of the
  GIMP?

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: gimp 2.8.20-1
  ProcVersionSignature: Ubuntu 4.10.0-35.39-generic 4.10.17
  Uname: Linux 4.10.0-35-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4.5
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Sat Sep 30 23:21:25 2017
  InstallationDate: Installed on 2015-07-31 (792 days ago)
  InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 
(20150218.1)
  SourcePackage: gimp
  UpgradeStatus: Upgraded to zesty on 2017-05-02 (151 days ago)

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

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

[Desktop-packages] [Bug 1720582] Re: gvfs-backends not installed with GIMP

2017-10-01 Thread Ross Gammon

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

** Bug watch added: Debian Bug tracker #520915
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=520915

** Also affects: gimp (Debian) via
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=520915
   Importance: Unknown
   Status: Unknown

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

Title:
  gvfs-backends not installed with GIMP

Status in gimp package in Ubuntu:
  Confirmed
Status in gimp package in Debian:
  Unknown

Bug description:
  I am running Kubuntu 17.04.
  I installed the GIMP.
  I tried to use the menu item "Open from location", but it did not work.
  After searching on the Internet, I found out that the GIMP needs a GVFS 
backend in order to fetch an image from the web. I installed gvfs-backends. Now 
the menu item "Open from location" works.

  Problem: A feature from the GIMP does not work by default.
  How to solve: install an additional package.
  Ideal use case: user only needs to install the GIMP.

  Could it be possible to add gvfs-backends as a hard dependency of the
  GIMP?

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: gimp 2.8.20-1
  ProcVersionSignature: Ubuntu 4.10.0-35.39-generic 4.10.17
  Uname: Linux 4.10.0-35-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4.5
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Sat Sep 30 23:21:25 2017
  InstallationDate: Installed on 2015-07-31 (792 days ago)
  InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 
(20150218.1)
  SourcePackage: gimp
  UpgradeStatus: Upgraded to zesty on 2017-05-02 (151 days ago)

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

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

[Desktop-packages] [Bug 1720649] [NEW] broken gnome expirience caused by unity-compatible patch

Public bug reported:

Standard gnome behavior doesn't allow to draw rhythmbox menubar, because
all the controls are available through the "settings (gear) button".
Ubuntu 17.10 draws menu, because of unity-compatible patch, you should
remove it, to provide true gnome expirience. Menubar is bloatware.

Problem occurs if you disable top bar application menu in Gnome Tweaks,
and start Rhythmbox after that. See attached screenshot. Please, remove
menubar patch.

You should also check other Gnome apps!!! AFAIK, Totem, default video
player also has some patch like this, and you even cant hide menubar in
fullscreen mode (!). I'm using mpv, so i dont care.

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

** Attachment added: "screenshot"
   
https://bugs.launchpad.net/bugs/1720649/+attachment/4959868/+files/bugrep-rh.png

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

Title:
  broken gnome expirience caused by unity-compatible patch

Status in rhythmbox package in Ubuntu:
  New

Bug description:
  Standard gnome behavior doesn't allow to draw rhythmbox menubar,
  because all the controls are available through the "settings (gear)
  button". Ubuntu 17.10 draws menu, because of unity-compatible patch,
  you should remove it, to provide true gnome expirience. Menubar is
  bloatware.

  Problem occurs if you disable top bar application menu in Gnome
  Tweaks, and start Rhythmbox after that. See attached screenshot.
  Please, remove menubar patch.

  You should also check other Gnome apps!!! AFAIK, Totem, default video
  player also has some patch like this, and you even cant hide menubar
  in fullscreen mode (!). I'm using mpv, so i dont care.

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

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

[Desktop-packages] [Bug 1720648] [NEW] Apturl not working out of the box in Firefox on Ubuntu 17.10 Artful

2017-10-01 Thread Alessandro Viprati

Public bug reported:

Installed yesterday Ubuntu 17.10 Artful, now up to date. 
It seems that AptUrl is not working out-of-the-box in Firefox, even if apturl 
is pre-installed.

= How to reproduce =
 1. with Firefox, open this wiki page: https://help.ubuntu.com/community/TheGIMP
 2. click on the "gimp" link in the "Standard" chapter, which should start the 
procedure to install gimp. 

Expected: a window opens telling you if you want to install the "gimp" package.
What happen: Firefox tells you that the url can not be interpreted.

Hope you can fix this problem

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: firefox 55.0.2+build1-0ubuntu4
ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3
Uname: Linux 4.13.0-12-generic x86_64
NonfreeKernelModules: wl
AddonCompatCheckDisabled: False
ApportVersion: 2.20.7-0ubuntu2
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  alessandro   1219 F pulseaudio
BuildID: 20170919185010
Channel: Unavailable
CurrentDesktop: ubuntu:GNOME
Date: Sun Oct  1 16:38:17 2017
Extensions: extensions.sqlite corrupt or missing
ForcedLayersAccel: False
IfupdownConfig:
 # interfaces(5) file used by ifup(8) and ifdown(8)
 auto lo
 iface lo inet loopback
IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini 
or extensions.sqlite)
InstallationDate: Installed on 2017-09-30 (0 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926)
IpRoute:
 default via 192.168.1.254 dev wlp9s0 proto static metric 600 
 169.254.0.0/16 dev wlp9s0 scope link metric 1000 
 192.168.1.0/24 dev wlp9s0 proto kernel scope link src 192.168.1.73 metric 600
Locales: extensions.sqlite corrupt or missing
PrefSources: prefs.js
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=it_IT.UTF-8
 SHELL=/bin/bash
Profiles: Profile0 (Default) - LastVersion=55.0.2/20170919185010 (In use)
RunningIncompatibleAddons: False
SourcePackage: firefox
Themes: extensions.sqlite corrupt or missing
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 03/23/2012
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A04
dmi.board.name: 01HXXJ
dmi.board.vendor: Dell Inc.
dmi.board.version: A04
dmi.chassis.type: 8
dmi.chassis.vendor: Dell Inc.
dmi.chassis.version: Not Specified
dmi.modalias: 
dmi:bvnDellInc.:bvrA04:bd03/23/2012:svnDellInc.:pnInspironN5050:pvrNotSpecified:rvnDellInc.:rn01HXXJ:rvrA04:cvnDellInc.:ct8:cvrNotSpecified:
dmi.product.name: Inspiron N5050
dmi.product.version: Not Specified
dmi.sys.vendor: Dell Inc.

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

Title:
  Apturl not working out of the box in Firefox on Ubuntu 17.10 Artful

Status in firefox package in Ubuntu:
  New

Bug description:
  Installed yesterday Ubuntu 17.10 Artful, now up to date. 
  It seems that AptUrl is not working out-of-the-box in Firefox, even if apturl 
is pre-installed.

  = How to reproduce =
   1. with Firefox, open this wiki page: 
https://help.ubuntu.com/community/TheGIMP
   2. click on the "gimp" link in the "Standard" chapter, which should start 
the procedure to install gimp. 

  Expected: a window opens telling you if you want to install the "gimp" 
package.
  What happen: Firefox tells you that the url can not be interpreted.

  Hope you can fix this problem

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: firefox 55.0.2+build1-0ubuntu4
  ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3
  Uname: Linux 4.13.0-12-generic x86_64
  NonfreeKernelModules: wl
  AddonCompatCheckDisabled: False
  ApportVersion: 2.20.7-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  alessandro   1219 F pulseaudio
  BuildID: 20170919185010
  Channel: Unavailable
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Oct  1 16:38:17 2017
  Extensions: extensions.sqlite corrupt or missing
  ForcedLayersAccel: False
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  IncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
  InstallationDate: Installed on 2017-09-30 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926)
  IpRoute:
   default via 192.168.1.254 dev wlp9s0 proto static metric 600 
   169.254.0.0/16 dev wlp9s0 scope link metric 1000 
   192.168.1.0/24 dev wlp9s0 proto kernel scope link src 192.168.1.73 metric 600
  Locales: extensions.sqlite corrupt or missing
  PrefSources: prefs.js
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=it_IT.UTF-8
   SHELL=/bin/bash
  Profiles: Profile0 (Default) -

[Desktop-packages] [Bug 1716068] Re: Gnome Shell crashes randomly

2017-10-01 Thread John Steeves

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

Thanks Daniel! Please let me know if there's anything I can do to help
accelerate the bug fixing process.

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

Title:
  Gnome Shell crashes randomly

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  When using Ubuntu Gnome 16.04, it is common for gnome-shell to crash
  unexpectedly, especially when performing intensive tasks.

  
  I've found that I was able to replicate the error by following these steps:
  Download and install a copy of Ubuntu Gnome 16.04.2 in VirtualBox.
  Open a screen displaying App icons in a menu, such as the app grid in the 
Gnome Shell overlay or the Arc Menu Gnome Shell extension 
(https://extensions.gnome.org/extension/1228/arc-menu/).
  Install all the latest software updates from the Software Updater or Synaptic.
  Upgrading all the packages between 16.04.2 to 16.04.3 seems to over-load 
Gnome Shell and cause the crash in the middle of the installation process.
  This crash always seems to occur after opening a screen with app icons and 
I'm not sure why.

  
  I've attached my .crash file updated with a symbolic stack trace.I hope this 
info and my attachment proves helpful in fixing the issue.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: gnome-shell 3.18.5-0ubuntu0.3
  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
  CurrentDesktop: GNOME
  Date: Fri Sep  8 19:24:22 2017
  DisplayManager: gdm3
  GsettingsChanges:
   b'org.gnome.shell' b'enabled-extensions' b"['arc-m...@linxgem33.com']"
   b'org.gnome.shell' b'favorite-apps' b"['ubiquity.desktop', 
'firefox.desktop', 'evolution.desktop', 'empathy.desktop', 'rhythmbox.desktop', 
'org.gnome.Photos.desktop', 'libreoffice-writer.desktop', 
'org.gnome.Nautilus.desktop', 'yelp.desktop']"
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
  InstallationDate: Installed on 2017-09-08 (0 days ago)
  InstallationMedia: Ubuntu-GNOME 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215)
  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/1716068/+subscriptions

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

[Desktop-packages] [Bug 1720149] Re: gnome-shell segv on wake from display or system sleep

2017-10-01 Thread Steven Harms

Of interest, I can reproduce this on Ubuntu 17.10 beta, however it
doesn't occur on Debian Stretch.  However I didn't test theme settings,
and was running Pop_OS! themes at the time.   Next I will see if it
occurs with stock themes.

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

Title:
  gnome-shell segv on wake from display or system sleep

Status in gnome-shell package in Ubuntu:
  Confirmed

Bug description:
  The observable symptom is that if I go away and let the computer go
  either to display sleep or suspend, when I come back and try to wake
  it up again, I find myself, after sliding up the lock screen, at the
  gdm login screen. I'm logged out, and logging in gives me a fresh new
  session. Anything I had open in the previous session is lost. (I'm
  getting used to saving stuff before I step away from the computer!)

  The only trace I've been able to find is that in /var/log/syslog I see
  a line like:

  Sep 28 14:38:44 fleetfoot kernel: [10621.432586] gnome-shell[1863]:
  segfault at 2c ip 7f6200e82434 sp 7ffc46f981c8 error 4 in
  libmutter-1.so.0.0.0[7f6200de4000+14]

  This happens at the time of attempted wake, not the time of going to
  sleep. It's preceded by a lot of activity from gdm-x-session that I'm
  not sure is indicating any error, just the process of waking up. I
  will attach a portion of syslog surrounding the whole event in the
  hope it helps. (In fact attaching the whole current syslog file - it
  has two such events occuring in it, first display sleep/wake at 09:02
  this morning, and secondly (because I was experimenting) a suspend-
  wake at 14:38 this afternoon.

  This is only affecting Xorg sessions, and may possibly only be
  affecting where nvidia is in use, I'm not sure about that. But the
  fact it occurs on display wake alone, not needing the system itself to
  have suspended (I was trying suspend to see if it *avoided* the
  problem, which it doesn't), does point the finger in that direction I
  guess. But ultimately I'm guessing it's gnome-shell itself segfaulting
  that's causing the login session to end?

  Not observed on my Wayland system.

  This is not new as of the current version of gnome-shell but I think
  it is relatively recent. Now my hackintosh partition is wrecked by a
  failed upgrade to High Sierra I'm using my Linux system more in
  earnest than before, so I'm hitting this often enough for it to
  provoke a bug report (and much of the time, to just turn all auto
  suspend/display-sleep off and instead shut down the computer when I'm
  leaving it for any length of time).

  The ubuntu bug reporter is not picking this up by itself, so I presume
  a crash report of the sort that uses is not being saved.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.26.0-0ubuntu2
  ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3
  Uname: Linux 4.13.0-12-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Thu Sep 28 14:41:07 2017
  DisplayManager: gdm3
  InstallationDate: Installed on 2017-07-30 (59 days ago)
  InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412)
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to artful on 2017-08-22 (37 days ago)

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

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

[Desktop-packages] [Bug 1720250] Re: im-config configuration ignored with gdm3

2017-10-01 Thread Mitsuya Shibata

Fist of all, I don't know details about history of upstart/unity
and user session system. There is no conclusion, just my research.

---

For Unity8/Mir, upstart script of im-config was added LP #1433831
This Ubuntu only script should be removed from im-config package.

Since switching user session from upstart to systemd, above upstart script
is convert to systemd unit on 0.29-1ubuntu14.

However this unit file uses initctl command, then this unit work on both of
systemd and upstart installed system only.

Legacy (Xorg) system will launches /etc/X11/Xsession.d/70im-config_launch
and set STARTUP variable to exec /usr/bin/im-launch.
All environment variables are set, no problem.

Wayland system doesn't exec /etc/X11/Xsession.d, i.e. any mechanism to
set environment variables is needed as like on Unity8/Mir.

(old) systemd unit doesn't work by two reasons.

1. use initctl command of upstart
2. bind to graphical-session.target which is not launched on ubuntu

If I understand correctly, graphical-session.target and
graphical-session-pre.target
will be launched for unity8 system and others.
At artful, this target are not depended by any target and service.

/usr/lib/gnome-session/run-systemd-session will stop these targets,
but this script will be executed from unity.desktop only.

How about use basic.target instead of graphical-session.target?
I attach sample im-config.service.

sudo cp im-config.service /usr/lib/systemd/user/
systemctl --user daemon-reload
systemctl --user enable im-config.service
(and restart session by logout and login)

This service file will work about environment variables.

$ env | grep -E '_IM|XMOD'
CLUTTER_IM_MODULE=xim
QT4_IM_MODULE=xim
QT_IM_MODULE=ibus
XMODIFIERS=@im=ibus
GTK_IM_MODULE=ibus

However suggestion window will be displayed on top left of display,
not near cursor on gedit and gnome-termial. The reason isn't known.

** Attachment added: "im-config.service"

https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1720250/+attachment/4959803/+files/im-config.service

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

Title:
im-config configuration ignored with gdm3

Status in gdm3 package in Ubuntu:
Confirmed
Status in im-config package in Ubuntu:
Confirmed

Bug description:
After having logged in via gdm3, the IM related environment variables
are always set like this:

$ env | grep -E '_IM|XMOD'
QT_IM_MODULE=ibus
XMODIFIERS=@im=ibus

Changing ~/.xinputrc to e.g. xim makes no difference, so gdm3 prevents
all other IM frameworks but IBus from working.

This problem seems to be similar to bug #1594681 (which was fixed).

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

[Desktop-packages] [Bug 1718653] Re: Windows buttons gone on specific programs

Graphics is a bit older ATI X800:

lotuspsychje@ArtfullBOX:~$ sudo lshw -C video
[sudo] wachtwoord voor lotuspsychje: 
  *-display:0   
   description: VGA compatible controller
   product: R420 [Radeon X800 PRO/GTO AGP]
   vendor: Advanced Micro Devices, Inc. [AMD/ATI]
   physical id: 0
   bus info: pci@:01:00.0
   version: 00
   width: 32 bits
   clock: 66MHz
   capabilities: agp agp-3.0 pm vga_controller bus_master cap_list rom
   configuration: driver=radeon latency=32 mingnt=8
   resources: irq:16 memory:d800-dfff ioport:9000(size=256) 
memory:e900-e900 memory:c-d
  *-display:1 UNCLAIMED
   description: Display controller
   product: R420 [Radeon X800 PRO/GTO] (Secondary)
   vendor: Advanced Micro Devices, Inc. [AMD/ATI]
   physical id: 0.1
   bus info: pci@:01:00.1
   version: 00
   width: 32 bits
   clock: 66MHz
   capabilities: pm cap_list
   configuration: latency=32 mingnt=8
   resources: memory:e000-e7ff memory:e901-e901

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

Title:
  Windows buttons gone on specific programs

Status in gnome-shell package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu 17.10 64bit Development version up to date @ 21/9/2017 on
  Xwayland

  kernel: Linux ArtfullBOX 4.13.0-11-generic #12-Ubuntu SMP Tue Sep 12
  16:03:57 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux

  Windows buttons are gone for specific programs like Firefox, hexchat, 
photoprint,chromium
  (maybe more that i havent tested)
  on a black window header with disformed white letters as window title

  other programs have working buttons

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.26.0-0ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-11.12-generic 4.13.1
  Uname: Linux 4.13.0-11-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Sep 21 14:17:17 2017
  DisplayManager: gdm3
  InstallationDate: Installed on 2017-08-31 (21 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170830)
  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/1718653/+subscriptions

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

[Desktop-packages] [Bug 1720539] Re: network-manager-openvpn-gnome cannot be installed using GNOME Software

** Changed in: network-manager-openvpn (Ubuntu)
   Status: New => Fix Committed

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

Title:
  network-manager-openvpn-gnome cannot be installed using GNOME Software

Status in network-manager-openvpn package in Ubuntu:
  Fix Committed

Bug description:
  The network-manager-openvpn-gnome package cannot be installed using
  GNOME Software as GNOME Control Center add-on because it is missing
  the necessary AppStream metadata.

  Steps to reproduce:
  1. Run GNOME Software.
  2. Search for "Control Center" and select "GNOME Control Center".
  3. See available add-ons at the bottom of the page.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager-openvpn/+bug/1720539/+subscriptions

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

[Desktop-packages] [Bug 1718653] Re: Windows buttons gone on specific programs

theme is ambiance by default, tryed other themes but still the same
issue

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

Title:
  Windows buttons gone on specific programs

Status in gnome-shell package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu 17.10 64bit Development version up to date @ 21/9/2017 on
  Xwayland

  kernel: Linux ArtfullBOX 4.13.0-11-generic #12-Ubuntu SMP Tue Sep 12
  16:03:57 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux

  Windows buttons are gone for specific programs like Firefox, hexchat, 
photoprint,chromium
  (maybe more that i havent tested)
  on a black window header with disformed white letters as window title

  other programs have working buttons

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.26.0-0ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-11.12-generic 4.13.1
  Uname: Linux 4.13.0-11-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Sep 21 14:17:17 2017
  DisplayManager: gdm3
  InstallationDate: Installed on 2017-08-31 (21 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170830)
  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/1718653/+subscriptions

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

[Desktop-packages] [Bug 1718653] Re: Windows buttons gone on specific programs

i think the overall lags in system,mouse and animations are related to
this bug:

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

** Bug watch added: GNOME Bug Tracker #745032
   https://bugzilla.gnome.org/show_bug.cgi?id=745032

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

Title:
  Windows buttons gone on specific programs

Status in gnome-shell package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu 17.10 64bit Development version up to date @ 21/9/2017 on
  Xwayland

  kernel: Linux ArtfullBOX 4.13.0-11-generic #12-Ubuntu SMP Tue Sep 12
  16:03:57 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux

  Windows buttons are gone for specific programs like Firefox, hexchat, 
photoprint,chromium
  (maybe more that i havent tested)
  on a black window header with disformed white letters as window title

  other programs have working buttons

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.26.0-0ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-11.12-generic 4.13.1
  Uname: Linux 4.13.0-11-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Sep 21 14:17:17 2017
  DisplayManager: gdm3
  InstallationDate: Installed on 2017-08-31 (21 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170830)
  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/1718653/+subscriptions

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

[Desktop-packages] [Bug 1712188] Re: Ubuntu 17.10: Cannot use shelltile extension in Ubuntu Session while it works fine in Gnome Session

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

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

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

Title:
  Ubuntu 17.10: Cannot use shelltile extension in Ubuntu Session while
  it works fine in Gnome Session

Status in gnome-shell package in Ubuntu:
  Confirmed

Bug description:
  On Ubuntu 17.10 with artful-proposed enabled, I cannot use the
  shelltile extension in Ubuntu session. If you see the screenshot, it
  seems like both shelltile and gnome's built in tile feature work at
  the same time and the gnome's one is preferred (enabling shelltile
  from gnome-tweak should disable the built in functionality). However,
  shelltile works properly on Gnome session.

  I don't know if I should file this bug against gnome-shell or gnome-
  session (if I've understood correctly ubuntu-session is a sub package
  of gnome-session).

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.24.3-0ubuntu5
  ProcVersionSignature: Ubuntu 4.12.0-12.13-generic 4.12.8
  Uname: Linux 4.12.0-12-generic x86_64
  ApportVersion: 2.20.6-0ubuntu6
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Aug 21 22:57:51 2017
  DisplayManager: gdm3
  InstallationDate: Installed on 2017-08-21 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170820)
  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/1712188/+subscriptions

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

[Desktop-packages] [Bug 1720149] Re: gnome-shell segv on wake from display or system sleep

2017-10-01 Thread Rachel Greenham

arc-theme package uninstalled and instead arc gtk & shell themes
installed manually as directed in its github page via autogen. This
appears not to be triggering the crash. even though the autogen doesn't
know any gnome > 3.22.  It may be that similarly rebuilding the
arc-theme package for a gnome 3.26 environment would fix it, but I still
don't really have a theory as to why it should break, let alone only on
nvidia. There's no binaries in it afaik.

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

Title:
  gnome-shell segv on wake from display or system sleep

Status in gnome-shell package in Ubuntu:
  Confirmed

Bug description:
  The observable symptom is that if I go away and let the computer go
  either to display sleep or suspend, when I come back and try to wake
  it up again, I find myself, after sliding up the lock screen, at the
  gdm login screen. I'm logged out, and logging in gives me a fresh new
  session. Anything I had open in the previous session is lost. (I'm
  getting used to saving stuff before I step away from the computer!)

  The only trace I've been able to find is that in /var/log/syslog I see
  a line like:

  Sep 28 14:38:44 fleetfoot kernel: [10621.432586] gnome-shell[1863]:
  segfault at 2c ip 7f6200e82434 sp 7ffc46f981c8 error 4 in
  libmutter-1.so.0.0.0[7f6200de4000+14]

  This happens at the time of attempted wake, not the time of going to
  sleep. It's preceded by a lot of activity from gdm-x-session that I'm
  not sure is indicating any error, just the process of waking up. I
  will attach a portion of syslog surrounding the whole event in the
  hope it helps. (In fact attaching the whole current syslog file - it
  has two such events occuring in it, first display sleep/wake at 09:02
  this morning, and secondly (because I was experimenting) a suspend-
  wake at 14:38 this afternoon.

  This is only affecting Xorg sessions, and may possibly only be
  affecting where nvidia is in use, I'm not sure about that. But the
  fact it occurs on display wake alone, not needing the system itself to
  have suspended (I was trying suspend to see if it *avoided* the
  problem, which it doesn't), does point the finger in that direction I
  guess. But ultimately I'm guessing it's gnome-shell itself segfaulting
  that's causing the login session to end?

  Not observed on my Wayland system.

  This is not new as of the current version of gnome-shell but I think
  it is relatively recent. Now my hackintosh partition is wrecked by a
  failed upgrade to High Sierra I'm using my Linux system more in
  earnest than before, so I'm hitting this often enough for it to
  provoke a bug report (and much of the time, to just turn all auto
  suspend/display-sleep off and instead shut down the computer when I'm
  leaving it for any length of time).

  The ubuntu bug reporter is not picking this up by itself, so I presume
  a crash report of the sort that uses is not being saved.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.26.0-0ubuntu2
  ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3
  Uname: Linux 4.13.0-12-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Thu Sep 28 14:41:07 2017
  DisplayManager: gdm3
  InstallationDate: Installed on 2017-07-30 (59 days ago)
  InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412)
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to artful on 2017-08-22 (37 days ago)

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

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

[Desktop-packages] [Bug 1720628] [NEW] Display freezes/unresponsive after locking screen for a while

2017-10-01 Thread Rafael

Public bug reported:

Everyday, I lock the screen when I'm away from the computer and,
everyday, if I am more than two hours away, the bloody computer freezes
its graphical interface: not the laptop itself, still running, but to no
avail.

Workaround - Emergency Sync + Emergency Umount + Reboot with the laptop
keyboard, as the external mouse and keyboard and the monitors are
unresponsive. The machine is connected and could be accessed via ssh, if
I had another computer at home.

1) Release:

$ lsb_release -rd
Description:Ubuntu 17.04
Release:17.04

2) Version
$ apt-cache policy xorg
xorg:
  Installed: 1:7.7+16ubuntu3
  Candidate: 1:7.7+16ubuntu3
  Version table:
 *** 1:7.7+16ubuntu3 500
500 http://br.archive.ubuntu.com/ubuntu zesty/main amd64 Packages
100 /var/lib/dpkg/status
 
-- Rafael

ProblemType: Bug
DistroRelease: Ubuntu 17.04
Package: xorg 1:7.7+16ubuntu3
ProcVersionSignature: Ubuntu 4.10.0-35.39-generic 4.10.17
Uname: Linux 4.10.0-35-generic x86_64
.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: None
Date: Sun Oct  1 08:25:16 2017
DistUpgraded: Fresh install
DistroCodename: zesty
DistroVariant: ubuntu
DpkgLog:
 
ExtraDebuggingInterest: Yes
GraphicsCard:
 Intel Corporation HD Graphics 520 [8086:1916] (rev 07) (prog-if 00 [VGA 
controller])
   Subsystem: Acer Incorporated [ALI] HD Graphics 520 [1025:100c]
InstallationDate: Installed on 2017-04-16 (167 days ago)
InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719)
MachineType: Acer Aspire E5-574G
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-35-generic 
root=UUID=4d4e9fdd-82f0-489b-8cee-66717d903185 ro nouveau.modeset=0 splash quiet
Renderer: Software
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 03/04/2016
dmi.bios.vendor: Insyde Corp.
dmi.bios.version: V1.14
dmi.board.asset.tag: Type2 - Board Asset Tag
dmi.board.name: Zoro_SL
dmi.board.vendor: Acer
dmi.board.version: V1.14
dmi.chassis.type: 10
dmi.chassis.vendor: Chassis Manufacturer
dmi.chassis.version: Chassis Version
dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.14:bd03/04/2016:svnAcer:pnAspireE5-574G:pvrV1.14:rvnAcer:rnZoro_SL:rvrV1.14:cvnChassisManufacturer:ct10:cvrChassisVersion:
dmi.product.name: Aspire E5-574G
dmi.product.version: V1.14
dmi.sys.vendor: Acer
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.7-0ubuntu0.17.04.1
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.7-0ubuntu0.17.04.1
version.xserver-xorg-core: xserver-xorg-core 2:1.19.3-1ubuntu1.1
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: Thu Aug 31 18:00:16 2017
xserver.configfile: default
xserver.devices: inputETPS/2 Elantech Touchpad TOUCHPAD, id 6
xserver.errors:
 Failed to load module "nvidia" (module does not exist, 0)
 Failed to load module "nvidia" (module does not exist, 0)
 [drm] Failed to open DRM device for (null): -22
 Screen 0 deleted because of no matching config section.
 AIGLX: reverting to software rendering
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 
xserver.version: 2:1.19.3-1ubuntu1.1

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


** Tags: amd64 apport-bug ubuntu zesty

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

Title:
  Display freezes/unresponsive after locking screen for a while

Status in xorg package in Ubuntu:
  New

Bug description:
  Everyday, I lock the screen when I'm away from the computer and,
  everyday, if I am more than two hours away, the bloody computer
  freezes its graphical interface: not the laptop itself, still running,
  but to no avail.

  Workaround - Emergency Sync + Emergency Umount + Reboot with the
  laptop keyboard, as the external mouse and keyboard and the monitors
  are unresponsive. The machine is connected and could be accessed via
  ssh, if I had another computer at home.

  1) Release:

  $ lsb_release -rd
  Description:  Ubuntu 17.04
  Release:  17.04

  2) Version
  $ apt-cache policy xorg
  xorg:
Installed: 1:7.7+16ubuntu3
Candidate: 1:7.7+16ubuntu3
Version table:
   *** 1:7.7+16ubuntu3 500
  500 http://br.archive.ubuntu.com/ubuntu zesty/main amd64 Packages
  100 /var/lib/dpkg/status
   
  -- Rafael

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: xorg

[Desktop-packages] [Bug 1718653] Re: Windows buttons gone on specific programs

theme is ambient

syslog: https://hastebin.com/vonexazane.sql

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

Title:
  Windows buttons gone on specific programs

Status in gnome-shell package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu 17.10 64bit Development version up to date @ 21/9/2017 on
  Xwayland

  kernel: Linux ArtfullBOX 4.13.0-11-generic #12-Ubuntu SMP Tue Sep 12
  16:03:57 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux

  Windows buttons are gone for specific programs like Firefox, hexchat, 
photoprint,chromium
  (maybe more that i havent tested)
  on a black window header with disformed white letters as window title

  other programs have working buttons

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.26.0-0ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-11.12-generic 4.13.1
  Uname: Linux 4.13.0-11-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Sep 21 14:17:17 2017
  DisplayManager: gdm3
  InstallationDate: Installed on 2017-08-31 (21 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170830)
  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/1718653/+subscriptions

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

[Desktop-packages] [Bug 1720539] Re: network-manager-openvpn-gnome cannot be installed using GNOME Software

2017-10-01 Thread AsciiWolf

I don't think this is an upstream issue. OpenVPN is available as add-on
in Fedora and there is an AppStream metainfo file in the upstream
repository[1].

[1] https://git.gnome.org/browse/network-manager-openvpn/tree/appdata
/network-manager-openvpn.metainfo.xml.in

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

Title:
  network-manager-openvpn-gnome cannot be installed using GNOME Software

Status in network-manager-openvpn package in Ubuntu:
  New

Bug description:
  The network-manager-openvpn-gnome package cannot be installed using
  GNOME Software as GNOME Control Center add-on because it is missing
  the necessary AppStream metadata.

  Steps to reproduce:
  1. Run GNOME Software.
  2. Search for "Control Center" and select "GNOME Control Center".
  3. See available add-ons at the bottom of the page.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager-openvpn/+bug/1720539/+subscriptions

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

[Desktop-packages] [Bug 1720616] [NEW] Wrong colors when making a window screenshot

2017-10-01 Thread Hadrien

Public bug reported:

This is on Ubuntu 17.10 (development branch) and gnome-screenshot 3.25.0

Open a Gnome terminal
Make a screenshot by calling gnome-screenshot -w
Open the created png

Expected result: the png shows the Gnome terminal window with colors matching 
the ones displayed
Actual result: the orange close button looks blue instead of orange. Maybe the 
red and blue channels are inverted.

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: gnome-screenshot 3.25.0-0ubuntu1
ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3
Uname: Linux 4.13.0-12-generic x86_64
ApportVersion: 2.20.7-0ubuntu1
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Sun Oct  1 11:47:27 2017
EcryptfsInUse: Yes
InstallationDate: Installed on 2017-01-03 (270 days ago)
InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=fr_FR.UTF-8
 SHELL=/bin/bash
SourcePackage: gnome-screenshot
UpgradeStatus: Upgraded to artful on 2017-09-30 (1 days ago)

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


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

** Attachment added: "Created png"
   
https://bugs.launchpad.net/bugs/1720616/+attachment/4959701/+files/Capture%20du%202017-10-01%2011-48-02.png

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

Title:
  Wrong colors when making a window screenshot

Status in gnome-screenshot package in Ubuntu:
  New

Bug description:
  This is on Ubuntu 17.10 (development branch) and gnome-screenshot
  3.25.0

  Open a Gnome terminal
  Make a screenshot by calling gnome-screenshot -w
  Open the created png

  Expected result: the png shows the Gnome terminal window with colors matching 
the ones displayed
  Actual result: the orange close button looks blue instead of orange. Maybe 
the red and blue channels are inverted.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-screenshot 3.25.0-0ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3
  Uname: Linux 4.13.0-12-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Oct  1 11:47:27 2017
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2017-01-03 (270 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-screenshot
  UpgradeStatus: Upgraded to artful on 2017-09-30 (1 days ago)

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

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

[Desktop-packages] [Bug 1720611] [NEW] firefox "eats" too much CPU while downloads files (not an unkown file size)

2017-10-01 Thread Dima

Public bug reported:

1) Ubuntu Artful Aardvark (development branch) 17.10
2) firefox 55.0.2+build1-0ubuntu4
3) <10% of Athlon II x2 2000
4) 45-50% of Athlon II x2 2000

I had this in Ubuntu 16.04.3 also

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: firefox 55.0.2+build1-0ubuntu4
ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3
Uname: Linux 4.13.0-12-generic x86_64
AddonCompatCheckDisabled: False
AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k4.13.0-12-generic.
ApportVersion: 2.20.7-0ubuntu1
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  user   1071 F pulseaudio
 /dev/snd/controlC1:  user   1071 F pulseaudio
BuildID: 20170919185010
Card0.Amixer.info:
 Card hw:0 'SB'/'HDA ATI SB at 0xfe024000 irq 16'
   Mixer name   : 'Realtek ALC892'
   Components   : 'HDA:10ec0892,1458a102,00100302'
   Controls  : 55
   Simple ctrls  : 22
Card1.Amixer.info:
 Card hw:1 'HDMI'/'HDA ATI HDMI at 0xfdffc000 irq 19'
   Mixer name   : 'ATI RS690/780 HDMI'
   Components   : 'HDA:1002791a,00791a00,0010'
   Controls  : 7
   Simple ctrls  : 1
Card1.Amixer.values:
 Simple mixer control 'IEC958',0
   Capabilities: pswitch pswitch-joined
   Playback channels: Mono
   Mono: Playback [on]
Channel: Unavailable
CurrentDesktop: LXDE
Date: Sun Oct  1 10:09:30 2017
Extensions: extensions.sqlite corrupt or missing
ForcedLayersAccel: False
IfupdownConfig:
 # interfaces(5) file used by ifup(8) and ifdown(8)
 auto lo
 iface lo inet loopback
IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini 
or extensions.sqlite)
InstallationDate: Installed on 2017-09-29 (1 days ago)
InstallationMedia: Lubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926)
IpRoute:
 default via 192.168.1.1 dev enp2s0 proto static metric 100 
 192.168.1.0/24 dev enp2s0 proto kernel scope link src 192.168.1.2 metric 100
IwConfig:
 enp2s0no wireless extensions.
 
 lono wireless extensions.
Locales: extensions.sqlite corrupt or missing
Plugins: Shockwave Flash - /usr/lib/adobe-flashplugin/libflashplayer.so 
(adobe-flashplugin)
PrefSources: prefs.js
Profiles: Profile0 (Default) - LastVersion=55.0.2/20170919185010 (In use)
RelatedPackageVersions: adobe-flashplugin 1:20170912.1-0ubuntu1
RfKill:
 
RunningIncompatibleAddons: False
SourcePackage: firefox
Themes: extensions.sqlite corrupt or missing
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 10/11/2010
dmi.bios.vendor: Award Software International, Inc.
dmi.bios.version: F8
dmi.board.name: GA-880GM-UD2H
dmi.board.vendor: Gigabyte Technology Co., Ltd.
dmi.chassis.type: 3
dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrF8:bd10/11/2010:svnGigabyteTechnologyCo.,Ltd.:pnGA-880GM-UD2H:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-880GM-UD2H:rvr:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
dmi.product.name: GA-880GM-UD2H
dmi.sys.vendor: Gigabyte Technology Co., Ltd.

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


** Tags: amd64 apport-bug artful

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

Title:
  firefox "eats" too much CPU while downloads files (not an unkown file
  size)

Status in firefox package in Ubuntu:
  New

Bug description:
  1) Ubuntu Artful Aardvark (development branch) 17.10
  2) firefox 55.0.2+build1-0ubuntu4
  3) <10% of Athlon II x2 2000
  4) 45-50% of Athlon II x2 2000

  I had this in Ubuntu 16.04.3 also

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: firefox 55.0.2+build1-0ubuntu4
  ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3
  Uname: Linux 4.13.0-12-generic x86_64
  AddonCompatCheckDisabled: False
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k4.13.0-12-generic.
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  user   1071 F pulseaudio
   /dev/snd/controlC1:  user   1071 F pulseaudio
  BuildID: 20170919185010
  Card0.Amixer.info:
   Card hw:0 'SB'/'HDA ATI SB at 0xfe024000 irq 16'
 Mixer name : 'Realtek ALC892'
 Components : 'HDA:10ec0892,1458a102,00100302'
 Controls  : 55
 Simple ctrls  : 22
  Card1.Amixer.info:
   Card hw:1 'HDMI'/'HDA ATI HDMI at 0xfdffc000 irq 19'
 Mixer name : 'ATI RS690/780 HDMI'
 Components : 'HDA:1002791a,00791a00,0010'
 Controls  : 7
 Simple ctrls  : 1
  Card1.Amixer.values:
   Simple mixer control 'IEC958',0
 Capabilities: pswitch pswitch-joined
 Playback channels: Mono
 Mono: Playback [on]
  Channel: Unavailable
  CurrentDesktop: LXDE
  Date: Sun Oct  1 10:09:30 2017
  Extensions: extensions.sqlite corrupt or missing
  ForcedLayersAccel: False
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto

[Desktop-packages] [Bug 405294] Re: A2DP Bluetooth audio skips terribly ["Skipping NNN us (= MMM bytes) in audio stream"]

2017-10-01 Thread GPratique

@Daniel, please understand that this is not personal, and I know this is
not the right place for such a discussion, but where else ?

This problem is really annoying in 2017, 8 years after the bug was first
reported, in a world where bluetooth speakers are of everyday use.

I know this bug has been reported here but also under various Linux
subsystem. Googling it returns a massive amount of results each one
slightly different from the other, some with workaround, including from
the pulseaudio documentation (yes, I read it, tried, made things worse).

Basically this means that the root cause may not have been found yet.

Asking end users to report again and again the same bug in different
ways just makes it more difficult for the developers to understand and
ultimately correct.

I am fairly sure that 100 people declaring here to be affected by this
bug, means that a lot more are too. Maybe only 1 user out of 10 knows
how to report it. So the real amount is probably way higher.

@Daniel if you have any influence in this, please try to forward this
problem to whomever is able to fix it, it would be very much
appreciated.

Best regards,

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

Title:
  A2DP Bluetooth audio skips terribly ["Skipping NNN us (= MMM bytes) in
  audio stream"]

Status in PulseAudio:
  Confirmed
Status in bluez package in Ubuntu:
  Confirmed
Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  As I upgraded to the Karmic alpha, bluetooth audio (via a2dp) stopped
  working properly. It was working fine in Jaunty.

  My headphones are detected and configured by pulse, but the audio
  skips as if it's spending half of each second paused. Music is
  buffered so that after I click stop on rhythmbox (or whatever--it
  happens with whatever player I use) the audio continues until it's
  caught up.

  syslog is full of the following lines:
  Jul 27 08:55:45 carlin1 pulseaudio[3218]: alsa-source.c: Increasing minimal 
latency to 1.00 ms
  Jul 27 08:55:46 carlin1 pulseaudio[3218]: module-bluetooth-device.c: Skipping 
15128 us (= 2668 bytes) in audio stream
  Jul 27 08:55:46 carlin1 pulseaudio[3218]: module-bluetooth-device.c: Skipping 
36586 us (= 6452 bytes) in audio stream
  Jul 27 08:55:46 carlin1 pulseaudio[3218]: module-bluetooth-device.c: Skipping 
35593 us (= 6276 bytes) in audio stream
  Jul 27 08:55:46 carlin1 pulseaudio[3218]: module-bluetooth-device.c: Skipping 
36597 us (= 6452 bytes) in audio stream
  Jul 27 08:55:46 carlin1 pulseaudio[3218]: module-bluetooth-device.c: Skipping 
32601 us (= 5748 bytes) in audio stream
  Jul 27 08:55:46 carlin1 pulseaudio[3218]: module-bluetooth-device.c: Skipping 
32589 us (= 5748 bytes) in audio stream

  This is with
  bluez 4.45-0ubuntu4
  pulseaudio1:0.9.15-4ubuntu2 0

  pulseaudio version 1:0.9.16~test2-0ubuntu1~ppa3 from ubuntu-audio-dev
  didn't help.

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

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

[Desktop-packages] [Bug 1718719] Re: qemu can't capture keys properly under wayland

2017-10-01 Thread Timo Aaltonen

Actually, this bug would affect current 1.19-branch too since the
patches are backported there as well. You can test
ppa:canonical-x/x-staging to verify, which has xorg-server from current
stable branch.

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

Title:
  qemu can't capture keys properly under wayland

Status in QEMU:
  New
Status in XServer:
  Incomplete
Status in qemu package in Ubuntu:
  New
Status in xorg-server package in Ubuntu:
  Triaged

Bug description:
  This appears to be different than the previous similar bugs; patches
  do look to be applied to use libinput in the wayland case. Still:

  unknown keycodes `(unnamed)', please report to qemu-de...@nongnu.org

  I am using qemu-system-x86   1:2.10+dfsg-0ubuntu1
  on artful.

  Many key inputs work correctly, but at boot the system will not
  properly catch the arrow keys, the above error shows up immediately
  after hitting Esc (for instance) to get to the boot menu. Booting from
  CD onto a daily Ubuntu desktop image, I can't navigate the splash
  menu.

  The same works correctly through virt-manager (which uses spice
  AFAICT, but wayland tends to crash when running virt-manager), and
  things work if I switch my session to Xorg rather than wayland.

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

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

[Desktop-packages] [Bug 1720133] Re: USB 3.0 displays are black on Ubuntu after x.org update to 1.18.3 or newer

2017-10-01 Thread Timo Aaltonen

I've proposed to add the patch to  upstream 1.19 branch, 1.19.4 is about
to be released.

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

** Changed in: xorg-server (Ubuntu)
   Importance: Undecided => High

** Changed in: xorg-server (Ubuntu)
   Status: Confirmed => Triaged

** Changed in: xorg-server (Ubuntu)
 Assignee: (unassigned) => Timo Aaltonen (tjaalton)

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

Title:
  USB 3.0 displays are black on Ubuntu after x.org update to 1.18.3 or
  newer

Status in xorg-server package in Ubuntu:
  Triaged

Bug description:
  [Impact]

   * This impacts all Ubuntu releases which received an update of x.org
  to 1.18.3 or newer, i.e. Ubuntu 16.04, 16.10, 17.04 & 17.10

   * End users are unable to use their USB displays unless they
  workaround the problem which currently involves disabling pageflip for
  modesetting in x.org.conf file

   * The fix which has been submitted to x.org extends blacklisting
  mechanism so the EVDI kernel module which is essential for DisplayLink
  USB 3.0 devices to work is correctly recognised by x.org. Then the
  PRIME sync is disabled in such case; The patch can be found here:
  
https://cgit.freedesktop.org/xorg/xserver/commit/?id=fbd80b2c8ebe9fd41229dc5438524d107c071ff1

  [Test Case]

  1. On a PC device with Ubuntu install DisplayLink SW for Ubuntu v1.3.54 
downloaded from http://www.displaylink.com/downloads/ubuntu. Detailed 
requirements and instructions can be found here:  
  2. Plug in a DisplayLink USB 3.0 compatible device, e.g. Dell D3100 docking 
station
  3. Plug in an external monitor (HDMI or DisplayPort) to the docking station

  Expected result: 
  The external monitor should light up and show the desktop

  Actual result: 
  The monitor remains black or shows frozen desktop.

  [Regression Potential]

   * The patchset extends number of modules for which x.org changes its
  functionality. It checks if "evdi" string is in the syspath so it is
  quite unlikely there would be any impact on anything else then USB 3.0
  displays which use EVDI module.

  [Other Info]
   
   * The patch has been applied to Ubuntu x.org source code built and tested.

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

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

[Desktop-packages] [Bug 1720606] Re: gnome-disks crashed with SIGSEGV in g_dbus_object_get_interface()