[Dx-packages] [Bug 1352895] Re: Unity dash doesn't preview PDF if user Home is not in /home

2014-08-23 Thread Yu-Cheng Chou
This bug can be fixed by building the latest version of evince from bzr
branch lp:evince.

** No longer affects: evince

** Changed in: unity (Ubuntu)
 Assignee: Yu-Cheng Chou (ianchou821) = (unassigned)

-- 
You received this bug notification because you are a member of DX
Packages, which is subscribed to unity in Ubuntu.
Matching subscriptions: dx-packages
https://bugs.launchpad.net/bugs/1352895

Title:
  Unity dash doesn't preview PDF if user Home is not in /home

Status in Unity:
  Triaged
Status in “unity” package in Ubuntu:
  Triaged

Bug description:
  Test case
  ===
  1. Not having your Home directory under /home (in my case is under /encrypted)
  2. Preview a PDF for Unity dash
  3. Unity dash can't load the preview
  Screenshot attached.

  If the Home directory is in /home, everything works fine.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: unity 7.2.2+14.04.20140714-0ubuntu1.1
  ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4
  Uname: Linux 3.13.0-32-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.14.1-0ubuntu3.2
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CurrentDesktop: Unity
  Date: Tue Aug  5 15:24:50 2014
  InstallationDate: Installed on 2014-07-28 (8 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 
(20140722.2)
  SourcePackage: unity
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Dx-packages] [Bug 1287041] Re: compiz crashed with SIGSEGV in af_glyph_hints_reload()

2014-08-23 Thread wgroiss
It affected me in 2 situations (i guess, is same bug ...):
When i open dash and type in to find a file on my hdd. But bug not immediately 
starts, there are about 5 - 10 seconds waiting.
When i try the search a 2nd time, it works. When i try another search about 1 
hour later = bug again.

And i have now also problems to force my dell-notebook to go in standby. Screen 
becomes black for 1 or 2 seconds, network-connections stops, after that, 
desktop is here without changes again and network-connection is up again.
But no standbye 

-- 
You received this bug notification because you are a member of DX
Packages, which is subscribed to unity in Ubuntu.
Matching subscriptions: dx-packages
https://bugs.launchpad.net/bugs/1287041

Title:
  compiz crashed with SIGSEGV in af_glyph_hints_reload()

Status in Unity:
  Confirmed
Status in “unity” package in Ubuntu:
  Confirmed

Bug description:
  Unity crashed on opening the dash.

  ProblemType: Crash
  DistroRelease: Ubuntu 14.04
  Package: unity 7.1.2+14.04.20140228-0ubuntu1
  ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3
  Uname: Linux 3.11.0-12-generic x86_64
  NonfreeKernelModules: nvidia wl
  ApportVersion: 2.13.2-0ubuntu5
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Mon Mar  3 09:03:36 2014
  ExecutablePath: /usr/bin/compiz
  ProcCmdline: compiz
  SegvAnalysis:
   Segfault happened at: 0x7fb34b0ed23a:movswl 0x18(%rdx),%r12d
   PC (0x7fb34b0ed23a) ok
   source 0x18(%rdx) (0x0018) not located in a known VMA region (needed 
readable region)!
   destination %r12d ok
   Stack memory exhausted (SP below stack segment)
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: unity
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/libfreetype.so.6
   ?? () from /usr/lib/x86_64-linux-gnu/libfreetype.so.6
   ?? () from /usr/lib/x86_64-linux-gnu/libfreetype.so.6
   ?? () from /usr/lib/x86_64-linux-gnu/libfreetype.so.6
   FT_Load_Glyph () from /usr/lib/x86_64-linux-gnu/libfreetype.so.6
  Title: compiz crashed with SIGSEGV in FT_Load_Glyph()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm autopilot cdrom dip lpadmin plugdev sambashare sbuild sudo 
vboxusers

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

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


[Dx-packages] [Bug 1307657] Re: UBUNTU_MENUPROXY should not be set in Xfce

2014-08-23 Thread Thaddäus Tintenfisch
** Changed in: xfce4-indicator-plugin (Ubuntu)
   Status: Confirmed = Invalid

-- 
You received this bug notification because you are a member of DX
Packages, which is subscribed to unity-gtk-module in Ubuntu.
https://bugs.launchpad.net/bugs/1307657

Title:
  UBUNTU_MENUPROXY should not be set in Xfce

Status in “unity-gtk-module” package in Ubuntu:
  Fix Released
Status in “xfce4-indicator-plugin” package in Ubuntu:
  Invalid

Bug description:
  To reproduce: either start with a fresh Ubuntu install and then
  install xubuntu-desktop, or start with Xubuntu and then install
  ubuntu-desktop - ie have both Xfce and Unity installed on the same
  machine.

  Xfce now has support for gtk3 indicators launched by upstart, but
  indicator-appmenu is totally broken - it will constantly crash the
  panel and applications. Xfce has a mechanism to hide indicators, and
  then the frontend UI will not be loaded in the panel, but it seems
  that UBUNTU_MENUPROXY is still being set in Xfce, which causes menus
  to disappear from applications, even though nothing is available to
  receive them.

  I discussed this with tedg and he suggested that the problem may be to
  do with the upstart service which sets UBUNTU_MENUPROXY, ie
  /usr/share/upstart/sessions/unity-gtk-module.conf

  We may in future get the appmenus working in Xfce, and then we would
  need some way to turn the menuproxy on and off depending on the user
  configuration. But for now, since they are broken anyway, it would be
  easiest to simply blacklist xubuntu desktop completely.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: unity-gtk-module-common 0.0.0+14.04.20140403-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-8.28-generic 3.13.2
  Uname: Linux 3.13.0-8-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.14.1-0ubuntu2
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Mon Apr 14 19:40:36 2014
  InstallationDate: Installed on 2014-02-11 (61 days ago)
  InstallationMedia: Xubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20140210)
  PackageArchitecture: all
  SourcePackage: unity-gtk-module
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity-gtk-module/+bug/1307657/+subscriptions

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


[Dx-packages] [Bug 1252121] Re: missing PrepareForSleep signal after resuming, causing networking to stay disabled

2014-08-23 Thread David Gross
I'm also experiencing this in 14.04 after upgrade from Ubuntu 12; dbus
log shows PrepareForSleep true on suspend, but no corresponding
PrepareForSleep false on awakening.

Putting a script in /etc/pm/sleep.d/ (or in /usr/lib/pm-utils/sleep.d/)
to issue nmcli nm sleep false (a workaround suggested elsewhere)
doesn't work for me (but I can issue sudo nmcli nm sleep false
manually to bring the network back).

Creating a /etc/pm/config.d/config file with the command
SUSPEND_MODULES=brcmsmac (another suggested workaround) also doesn't
do the trick (yes, brcmsmac is my driver, I'm pretty sure anyway).

-- 
You received this bug notification because you are a member of DX
Packages, which is subscribed to systemd-shim in Ubuntu.
https://bugs.launchpad.net/bugs/1252121

Title:
  missing PrepareForSleep signal after resuming, causing networking to
  stay disabled

Status in NetworkManager:
  New
Status in wicd:
  New
Status in “systemd-shim” package in Ubuntu:
  Confirmed
Status in “systemd-shim” source package in Saucy:
  Confirmed
Status in “systemd-shim” source package in Trusty:
  Confirmed

Bug description:
  As per request from bug #1184262, this is a new report, along with
  dbus (to be attached)

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: systemd-services 204-0ubuntu19
  Uname: Linux 3.12.0-custom x86_64
  ApportVersion: 2.12.5-0ubuntu2.1
  Architecture: amd64
  Date: Sun Nov 17 20:24:41 2013
  MarkForUpload: True
  SourcePackage: systemd
  UpgradeStatus: Upgraded to saucy on 2013-10-17 (31 days ago)

  SRU INFORMATION:
  FIX: https://github.com/desrt/systemd-shim/commit/9e1ebe3ab (in trusty 
already)

  Regression potential: Low. Flushing the session bus was introduced in
  version 4 and is obviously bogus as in a system D-BUS service there is
  no session bus. This causes lots of confusing error messages and
  unnecessary overhead like trying to start dbus-launch. Flushing the
  system bus is low-risk, in most cases it's a no-op and it would
  otherwise prevent losing signals after waking up. No known
  regressions.

  TEST CASE: Run several suspend/resume cycles with the lid, session
  indicator menu, and verify that the network comes back up. It is known
  that this fix is necessary but not sufficient, so it is not expected
  to fix all cases. But it should not make things worse, so if network
  now does not come up any more on a machine where it previously worked
  this would count as failure/regression.

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

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


[Dx-packages] [Bug 1252121] Re: missing PrepareForSleep signal after resuming, causing networking to stay disabled

2014-08-23 Thread Yanpas
The same behavior on fresh reinstalled Xubuntu.

-- 
You received this bug notification because you are a member of DX
Packages, which is subscribed to systemd-shim in Ubuntu.
https://bugs.launchpad.net/bugs/1252121

Title:
  missing PrepareForSleep signal after resuming, causing networking to
  stay disabled

Status in NetworkManager:
  New
Status in wicd:
  New
Status in “systemd-shim” package in Ubuntu:
  Confirmed
Status in “systemd-shim” source package in Saucy:
  Confirmed
Status in “systemd-shim” source package in Trusty:
  Confirmed

Bug description:
  As per request from bug #1184262, this is a new report, along with
  dbus (to be attached)

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: systemd-services 204-0ubuntu19
  Uname: Linux 3.12.0-custom x86_64
  ApportVersion: 2.12.5-0ubuntu2.1
  Architecture: amd64
  Date: Sun Nov 17 20:24:41 2013
  MarkForUpload: True
  SourcePackage: systemd
  UpgradeStatus: Upgraded to saucy on 2013-10-17 (31 days ago)

  SRU INFORMATION:
  FIX: https://github.com/desrt/systemd-shim/commit/9e1ebe3ab (in trusty 
already)

  Regression potential: Low. Flushing the session bus was introduced in
  version 4 and is obviously bogus as in a system D-BUS service there is
  no session bus. This causes lots of confusing error messages and
  unnecessary overhead like trying to start dbus-launch. Flushing the
  system bus is low-risk, in most cases it's a no-op and it would
  otherwise prevent losing signals after waking up. No known
  regressions.

  TEST CASE: Run several suspend/resume cycles with the lid, session
  indicator menu, and verify that the network comes back up. It is known
  that this fix is necessary but not sufficient, so it is not expected
  to fix all cases. But it should not make things worse, so if network
  now does not come up any more on a machine where it previously worked
  this would count as failure/regression.

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

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


[Dx-packages] [Bug 1359248] Re: Sound settings no longer works with Gnome Control Center Sound in Xfce

2014-08-23 Thread Roman
Wanted to update that I found a fix, specifically to edit
/usr/share/applications/gnome-sound-panel.desktop and add XFCE to the
OnlyShowIn line.

-- 
You received this bug notification because you are a member of DX
Packages, which is subscribed to indicator-sound in Ubuntu.
Matching subscriptions: dx-packages
https://bugs.launchpad.net/bugs/1359248

Title:
  Sound settings no longer works with Gnome Control Center Sound in Xfce

Status in “indicator-sound” package in Ubuntu:
  New

Bug description:
  In Ubuntu 12.04 I was able to install Gnome Control Center and
  indicator-sound and launch GNOME Control Center's audio options from
  the Sound Settings option in Indicator-Sound, but after upgrading to
  14.04 this is no longer possible - it loads GNOME-Control-Center
  showing only one or two icons, the only workaround being to manually
  launch gksu gnome-control-center sound which is less than ideal.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-sound/+bug/1359248/+subscriptions

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


[Dx-packages] [Bug 1359249] Re: Launching PAVUControl works from Xubuntu, but not from Xfce

2014-08-23 Thread Roman
Wanted to update, this bug is still in effect, the other bug I have
figured out how to solve, will update that thread.

-- 
You received this bug notification because you are a member of DX
Packages, which is subscribed to indicator-sound in Ubuntu.
Matching subscriptions: dx-packages
https://bugs.launchpad.net/bugs/1359249

Title:
  Launching PAVUControl works from Xubuntu, but not from Xfce

Status in “indicator-sound” package in Ubuntu:
  New

Bug description:
  In Xubuntu 14.04 when clicking the sound indicator and choosing Sound
  Settings Pavucontrol is launched, but it does not get launched in the
  same scenario when the session Xfce is launched instead, with the
  same settings. In fact I installed the xfce4 package on top of
  Xubuntu's and launched it. Both xsession files list the same thing to
  start it, so is indicator only choosing to work on whitelisted
  sessions?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-sound/+bug/1359249/+subscriptions

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