[Dx-packages] [Bug 1315352] Re: vim.gnome "d$" doesn't delete

2014-07-04 Thread Yavor Nikolov
I haven't faced the problem since a while (perhaps it has gone after
applying some updates).

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

Title:
  vim.gnome "d$" doesn't delete

Status in “unity-gtk-module” package in Ubuntu:
  New

Bug description:
  I have a problem with gvim (linked to vim.gnome) in Ubuntu 14.04. I managed 
to reproduce it with following 1-line file (test.txt):
  asdf asdf

  1) gvim test.txt
  2) I go to the second (it doesn't really 2-nd or other) character (s) and I 
press keys:
  d$

  * The observed behaviour is:
  My cursor is moved to the end of file (not deleting anything)

  * What is expected is:
  The text from current position to the end of line to be deleted.

  ---
  * The problem didn't exist until recently (I recently upgraded from 13.10 to 
14.04 so I suspect 14.04 may have introduced this regression)
  * Same operation works fine with plain vim and vim.gtk.
  * I have moved away my ~/.vimrc file (to make sure that none of my 
customizations is interfering)
  * I tried wit "gvim -U NONE -u NONE": the problem still persists
  * I managed to reproduce the problem with both 32-bit and 64-bit Ubuntu setups

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity-gtk-module/+bug/1315352/+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 1319283] Re: unity screensaver lockup/crash

2014-07-04 Thread Anton Piatek
Do those linked instructions even work??

$ sudo apt-get install compiz-core-dbgsym compiz-plugins-dbgsym 
compiz-fusion-plugins-main-dbgsym compiz-fusion-plugins-extra-dbgsym 
compizconfig-backend-gconf-dbgsym libcompizconfig0-dbgsym compiz-gnome-dbgsym
Reading package lists... Done
Building dependency tree   
Reading state information... Done
E: Unable to locate package compiz-core-dbgsym
E: Unable to locate package compiz-plugins-dbgsym
E: Unable to locate package compiz-fusion-plugins-main-dbgsym
E: Unable to locate package compiz-fusion-plugins-extra-dbgsym
E: Unable to locate package compizconfig-backend-gconf-dbgsym
E: Unable to locate package libcompizconfig0-dbgsym
E: Unable to locate package compiz-gnome-dbgsym

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

Title:
  unity screensaver lockup/crash

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

Bug description:
  I have seen several instances where resuming from suspend results in a 
slightly corrupted unity screensaver/lockscreen. Login is impossible. 
  Sometimes it crashes after a few minutes and restarts and all is ok. Other 
times it crashes after a few minutes and simply unlocks the screen, though this 
is often accompanies by no unity windowmanager running in the desktop

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: unity 7.2.0+14.04.20140423-0ubuntu1.2
  ProcVersionSignature: Ubuntu 3.11.0-17.31-generic 3.11.10.3
  Uname: Linux 3.11.0-17-generic x86_64
  NonfreeKernelModules: symap_custom_dkms_x86_64 nvidia
  .proc.driver.nvidia.gpus.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  331.38  Wed Jan  8 19:32:30 
PST 2014
   GCC version:  gcc version 4.8.2 (Ubuntu 4.8.2-19ubuntu1)
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.14.1-0ubuntu3
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: Unity
  Date: Tue May 13 21:01:18 2014
  DistUpgraded: 2014-04-17 13:16:06,322 DEBUG enabling apt cron job
  DistroCodename: trusty
  DistroVariant: ubuntu
  GraphicsCard:
   NVIDIA Corporation GK107GLM [Quadro K1000M] [10de:0ffc] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: Lenovo Device [17aa:21f6]
  InstallationDate: Installed on 2013-07-05 (311 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  MachineType: LENOVO 24491D1
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.11.0-17-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash nox2apic
  SourcePackage: unity
  UpgradeStatus: Upgraded to trusty on 2014-04-17 (26 days ago)
  dmi.bios.date: 11/27/2013
  dmi.bios.vendor: LENOVO
  dmi.bios.version: G5ET96WW (2.56 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 24491D1
  dmi.board.vendor: LENOVO
  dmi.board.version: Win8 Pro DPK TPG
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrG5ET96WW(2.56):bd11/27/2013:svnLENOVO:pn24491D1:pvrThinkPadW530:rvnLENOVO:rn24491D1:rvrWin8ProDPKTPG:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 24491D1
  dmi.product.version: ThinkPad W530
  dmi.sys.vendor: LENOVO
  version.compiz: compiz 1:0.9.11+14.04.20140423-0ubuntu1
  version.ia32-libs: ia32-libs 20090808ubuntu36
  version.libdrm2: libdrm2 2.4.52-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.0-4ubuntu5
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.0-4ubuntu5
  version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.10-1ubuntu2
  xserver.bootTime: Thu May  8 19:16:07 2014
  xserver.configfile: default
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   
  xserver.version: 2:1.15.1-0ubuntu2

To manage notifications about this bug go to:
https://bugs.launchpad.net/unity/+bug/1319283/+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 1319283] Re: unity screensaver lockup/crash

2014-07-04 Thread Anton Piatek
apport uploads a crash report each time - is there anyway to find those?

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

Title:
  unity screensaver lockup/crash

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

Bug description:
  I have seen several instances where resuming from suspend results in a 
slightly corrupted unity screensaver/lockscreen. Login is impossible. 
  Sometimes it crashes after a few minutes and restarts and all is ok. Other 
times it crashes after a few minutes and simply unlocks the screen, though this 
is often accompanies by no unity windowmanager running in the desktop

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: unity 7.2.0+14.04.20140423-0ubuntu1.2
  ProcVersionSignature: Ubuntu 3.11.0-17.31-generic 3.11.10.3
  Uname: Linux 3.11.0-17-generic x86_64
  NonfreeKernelModules: symap_custom_dkms_x86_64 nvidia
  .proc.driver.nvidia.gpus.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  331.38  Wed Jan  8 19:32:30 
PST 2014
   GCC version:  gcc version 4.8.2 (Ubuntu 4.8.2-19ubuntu1)
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.14.1-0ubuntu3
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: Unity
  Date: Tue May 13 21:01:18 2014
  DistUpgraded: 2014-04-17 13:16:06,322 DEBUG enabling apt cron job
  DistroCodename: trusty
  DistroVariant: ubuntu
  GraphicsCard:
   NVIDIA Corporation GK107GLM [Quadro K1000M] [10de:0ffc] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: Lenovo Device [17aa:21f6]
  InstallationDate: Installed on 2013-07-05 (311 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  MachineType: LENOVO 24491D1
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.11.0-17-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash nox2apic
  SourcePackage: unity
  UpgradeStatus: Upgraded to trusty on 2014-04-17 (26 days ago)
  dmi.bios.date: 11/27/2013
  dmi.bios.vendor: LENOVO
  dmi.bios.version: G5ET96WW (2.56 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 24491D1
  dmi.board.vendor: LENOVO
  dmi.board.version: Win8 Pro DPK TPG
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrG5ET96WW(2.56):bd11/27/2013:svnLENOVO:pn24491D1:pvrThinkPadW530:rvnLENOVO:rn24491D1:rvrWin8ProDPKTPG:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 24491D1
  dmi.product.version: ThinkPad W530
  dmi.sys.vendor: LENOVO
  version.compiz: compiz 1:0.9.11+14.04.20140423-0ubuntu1
  version.ia32-libs: ia32-libs 20090808ubuntu36
  version.libdrm2: libdrm2 2.4.52-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.0-4ubuntu5
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.0-4ubuntu5
  version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.10-1ubuntu2
  xserver.bootTime: Thu May  8 19:16:07 2014
  xserver.configfile: default
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   
  xserver.version: 2:1.15.1-0ubuntu2

To manage notifications about this bug go to:
https://bugs.launchpad.net/unity/+bug/1319283/+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 1337942] [NEW] unity doesn't remember scaling factor (text, menu, titlebar)

2014-07-04 Thread Amit Kucheria
Public bug reported:

Please find attached a screenshot of the "ideal" scaling factor requiity
red for my HiDPI laptop screen to be useable.

In the Displays, setting I've set menu and titlebars to be scaled by 1.75 to 
get large enough buttons.
In the Ubuntu-Tweak-Tool, I've set the text scaling factor to 1.2 to make 
application menu fonts readable.

Unity seems to forget these and uses some random values after a restart.

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: unity 7.2.1+14.04.20140513-0ubuntu2
ProcVersionSignature: Ubuntu 3.13.0-30.54-generic 3.13.11.2
Uname: Linux 3.13.0-30-generic x86_64
.tmp.unity.support.test.0:
 
ApportVersion: 2.14.1-0ubuntu3.2
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
CurrentDesktop: Unity
Date: Fri Jul  4 23:40:41 2014
DistUpgraded: Fresh install
DistroCodename: trusty
DistroVariant: ubuntu
EcryptfsInUse: Yes
GraphicsCard:
 Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 
09) (prog-if 00 [VGA controller])
   Subsystem: Samsung Electronics Co Ltd Device [144d:c0ef]
InstallationDate: Installed on 2014-06-06 (27 days ago)
InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64+mac (20140417)
MachineType: SAMSUNG ELECTRONICS CO., LTD. 940X3G/930X3G
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-30-generic 
root=UUID=735955f7-9d94-4ef3-a17d-7e84999c4b76 ro persistent quiet splash 
vt.handoff=7
SourcePackage: unity
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 04/11/2014
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: P04ACJ.125.140411.dg
dmi.board.asset.tag: No Asset Tag
dmi.board.name: NP940X3G-K04US
dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
dmi.board.version: SAMSUNG_SW_REVISION_1234567890ABCD
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 9
dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
dmi.chassis.version: N/A
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP04ACJ.125.140411.dg:bd04/11/2014:svnSAMSUNGELECTRONICSCO.,LTD.:pn940X3G/930X3G:pvrP04ACJ:rvnSAMSUNGELECTRONICSCO.,LTD.:rnNP940X3G-K04US:rvrSAMSUNG_SW_REVISION_1234567890ABCD:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvrN/A:
dmi.product.name: 940X3G/930X3G
dmi.product.version: P04ACJ
dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.
version.compiz: compiz 1:0.9.11+14.04.20140423-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.52-1
version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.1
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.1
version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3.1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2
xserver.bootTime: Fri Jul  4 23:32:30 2014
xserver.configfile: default
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 product id   16970 
 vendor SDC
xserver.version: 2:1.15.1-0ubuntu2

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


** Tags: amd64 apport-bug compiz-0.9 trusty ubuntu

** Attachment added: "HiDPI-settings-displays-tweak-tool.png"
   
https://bugs.launchpad.net/bugs/1337942/+attachment/4145688/+files/HiDPI-settings-displays-tweak-tool.png

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

Title:
  unity doesn't remember scaling factor (text, menu, titlebar)

Status in “unity” package in Ubuntu:
  New

Bug description:
  Please find attached a screenshot of the "ideal" scaling factor
  requiity red for my HiDPI laptop screen to be useable.

  In the Displays, setting I've set menu and titlebars to be scaled by 1.75 to 
get large enough buttons.
  In the Ubuntu-Tweak-Tool, I've set the text scaling factor to 1.2 to make 
application menu fonts readable.

  Unity seems to forget these and uses some random values after a
  restart.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: unity 7.2.1+14.04.20140513-0ubuntu2
  ProcVersionSignature: Ubuntu 3.13.0-30.54-generic 3.13.11.2
  Uname: Linux 3.13.0-30-generic x86_64
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.14.1-0ubuntu3.2
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Fri

[Dx-packages] [Bug 1273014] Re: notification-daemon crashed with signal 5 in g_source_remove()

2014-07-04 Thread Apport retracing service
** Tags added: utopic

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

Title:
  notification-daemon crashed with signal 5 in g_source_remove()

Status in “notification-daemon” package in Ubuntu:
  Confirmed

Bug description:
  Login to LXDE - Ubuntu 14.04

  ProblemType: Crash
  DistroRelease: Ubuntu 14.04
  Package: notification-daemon 0.7.6-1
  Uname: Linux 3.13.0-031300-generic x86_64
  ApportVersion: 2.13.1-0ubuntu2
  Architecture: amd64
  CurrentDesktop: LXDE
  Date: Sun Jan 26 20:20:56 2014
  ExecutablePath: /usr/lib/notification-daemon/notification-daemon
  InstallationDate: Installed on 2014-01-26 (0 days ago)
  InstallationMedia: Kubuntu 12.04.3 LTS "Precise Pangolin" - Release amd64 
(20130822)
  ProcCmdline: /usr/lib/notification-daemon/notification-daemon
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  Signal: 5
  SourcePackage: notification-daemon
  StacktraceTop:
   g_source_remove () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? ()
   g_closure_invoke () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   g_signal_emit_valist () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
  Title: notification-daemon crashed with signal 5 in g_source_remove()
  UpgradeStatus: Upgraded to trusty on 2014-01-26 (0 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev root sambashare sudo vboxusers

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/notification-daemon/+bug/1273014/+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 1337939] Re: notification-daemon crashed with signal 5 in g_source_remove()

2014-07-04 Thread Apport retracing service
*** This bug is a duplicate of bug 1273014 ***
https://bugs.launchpad.net/bugs/1273014

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 #1273014, 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/1337939/+attachment/4145670/+files/CoreDump.gz

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

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

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

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

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

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

** This bug has been marked a duplicate of bug 1273014
   notification-daemon crashed with signal 5 in g_source_remove()

** Information type changed from Private to Public

** Tags removed: need-amd64-retrace

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

Title:
  notification-daemon crashed with signal 5 in g_source_remove()

Status in “notification-daemon” package in Ubuntu:
  New

Bug description:
  Weather Applet

  ProblemType: Crash
  DistroRelease: Ubuntu 14.10
  Package: notification-daemon 0.7.6-1
  Uname: Linux 3.16.0-031600rc2-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.14.4-0ubuntu1
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: LXDE
  Date: Fri Jul  4 13:43:36 2014
  ExecutablePath: /usr/lib/notification-daemon/notification-daemon
  InstallationDate: Installed on 2014-06-17 (16 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  ProcCmdline: /usr/lib/notification-daemon/notification-daemon
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  Signal: 5
  SourcePackage: notification-daemon
  StacktraceTop:
   g_source_remove () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? ()
   g_closure_invoke () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   g_signal_emit_valist () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
  Title: notification-daemon crashed with signal 5 in g_source_remove()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/notification-daemon/+bug/1337939/+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 1337926] Re: Switching workspaces: launcher stays grey & panel does not update

2014-07-04 Thread Aibara Iduas
I forgot to add that when selecting a workspace with no open window
(i.e. it's just the desktop) the panel sometimes has color but the words
"Ubuntu Desktop" are offset and gray. ?field.comment=I forgot to add
that when selecting a workspace with no open window (i.e. it's just the
desktop) the panel sometimes has color but the words "Ubuntu Desktop"
are offset and gray.

** Attachment added: "gray.png"
   
https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1337926/+attachment/4145649/+files/gray.png

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

Title:
  Switching workspaces: launcher stays grey & panel does not update

Status in “unity” package in Ubuntu:
  New

Bug description:
  When switching workspaces, occasionally (1 out of 10 times, sometimes
  more frequently) the launcher and panel do not update. This means that
  although a worskpace is opened with a focused window, the panel still
  reads "Ubuntu Desktop" and the launcher is gray (as it is when
  selecting workspaces). The launcher is still functional and can bring
  other windows forward, but it stays gray and the panel still says
  "Ubuntu Desktop." They only update properly whenl the user either
  switches desktops again or activates a window spread.

  See the attached screenshot. In it, Firefox is actually focused, so
  the panel should read "New Tab - Mozilla Firefox". And, of course, the
  launcher should not be gray.

  I wonder if it is related to showing menus in the window's title bar
  setting, since I can't seem to reproduce it with the old global menu.
  Not sure about that though.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: unity 7.2.1+14.04.20140513-0ubuntu2
  ProcVersionSignature: Ubuntu 3.13.0-30.54-generic 3.13.11.2
  Uname: Linux 3.13.0-30-generic i686
  ApportVersion: 2.14.1-0ubuntu3.2
  Architecture: i386
  CompizPlugins: 
[core,composite,opengl,compiztoolbox,decor,move,mousepoll,text,regex,place,resize,vpswitch,animation,imgpng,wall,gnomecompat,fade,unitymtgrabhandles,grid,session,expo,workarounds,scale,scaleaddon,ezoom,unityshell]
  CurrentDesktop: Unity
  Date: Fri Jul  4 12:35:26 2014
  InstallationDate: Installed on 2014-03-10 (116 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release i386 (20131016.1)
  SourcePackage: unity
  UpgradeStatus: Upgraded to trusty on 2014-04-18 (76 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1337926/+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 1337926] [NEW] Switching workspaces: launcher stays grey & panel does not update

2014-07-04 Thread Aibara Iduas
Public bug reported:

When switching workspaces, occasionally (1 out of 10 times, sometimes
more frequently) the launcher and panel do not update. This means that
although a worskpace is opened with a focused window, the panel still
reads "Ubuntu Desktop" and the launcher is gray (as it is when selecting
workspaces). The launcher is still functional and can bring other
windows forward, but it stays gray and the panel still says "Ubuntu
Desktop." They only update properly whenl the user either switches
desktops again or activates a window spread.

See the attached screenshot. In it, Firefox is actually focused, so the
panel should read "New Tab - Mozilla Firefox". And, of course, the
launcher should not be gray.

I wonder if it is related to showing menus in the window's title bar
setting, since I can't seem to reproduce it with the old global menu.
Not sure about that though.

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: unity 7.2.1+14.04.20140513-0ubuntu2
ProcVersionSignature: Ubuntu 3.13.0-30.54-generic 3.13.11.2
Uname: Linux 3.13.0-30-generic i686
ApportVersion: 2.14.1-0ubuntu3.2
Architecture: i386
CompizPlugins: 
[core,composite,opengl,compiztoolbox,decor,move,mousepoll,text,regex,place,resize,vpswitch,animation,imgpng,wall,gnomecompat,fade,unitymtgrabhandles,grid,session,expo,workarounds,scale,scaleaddon,ezoom,unityshell]
CurrentDesktop: Unity
Date: Fri Jul  4 12:35:26 2014
InstallationDate: Installed on 2014-03-10 (116 days ago)
InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release i386 (20131016.1)
SourcePackage: unity
UpgradeStatus: Upgraded to trusty on 2014-04-18 (76 days ago)

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


** Tags: apport-bug i386 trusty

** Attachment added: "Firefox is focused; panel incorrect and launcher gray"
   
https://bugs.launchpad.net/bugs/1337926/+attachment/4145639/+files/screenshot.png

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

Title:
  Switching workspaces: launcher stays grey & panel does not update

Status in “unity” package in Ubuntu:
  New

Bug description:
  When switching workspaces, occasionally (1 out of 10 times, sometimes
  more frequently) the launcher and panel do not update. This means that
  although a worskpace is opened with a focused window, the panel still
  reads "Ubuntu Desktop" and the launcher is gray (as it is when
  selecting workspaces). The launcher is still functional and can bring
  other windows forward, but it stays gray and the panel still says
  "Ubuntu Desktop." They only update properly whenl the user either
  switches desktops again or activates a window spread.

  See the attached screenshot. In it, Firefox is actually focused, so
  the panel should read "New Tab - Mozilla Firefox". And, of course, the
  launcher should not be gray.

  I wonder if it is related to showing menus in the window's title bar
  setting, since I can't seem to reproduce it with the old global menu.
  Not sure about that though.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: unity 7.2.1+14.04.20140513-0ubuntu2
  ProcVersionSignature: Ubuntu 3.13.0-30.54-generic 3.13.11.2
  Uname: Linux 3.13.0-30-generic i686
  ApportVersion: 2.14.1-0ubuntu3.2
  Architecture: i386
  CompizPlugins: 
[core,composite,opengl,compiztoolbox,decor,move,mousepoll,text,regex,place,resize,vpswitch,animation,imgpng,wall,gnomecompat,fade,unitymtgrabhandles,grid,session,expo,workarounds,scale,scaleaddon,ezoom,unityshell]
  CurrentDesktop: Unity
  Date: Fri Jul  4 12:35:26 2014
  InstallationDate: Installed on 2014-03-10 (116 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release i386 (20131016.1)
  SourcePackage: unity
  UpgradeStatus: Upgraded to trusty on 2014-04-18 (76 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1337926/+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 1283065] Re: Use the existing audio stack to play event sounds

2014-07-04 Thread Charles Kerr
Not a total fix in the sense of using the Media API, but a step in the
right direction:

https://code.launchpad.net/~charlesk/indicator-datetime/lp-1337348-use-
gstreamer-api, written for bug #1337348, uses GStreamer directly and so
drops the libcanberra packaging requirement.

** Branch linked: lp:~charlesk/indicator-datetime/lp-1337348-use-
gstreamer-api

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

Title:
  Use the existing audio stack to play event sounds

Status in “indicator-datetime” package in Ubuntu:
  Triaged

Bug description:
  This merge introduced several new packages in order to produce sounds on 
calendar events
  https://code.launchpad.net/~charlesk/indicator-datetime/alarms/+merge/204420

  We should rather use existing APIs in QtMultimedia or go directly to the 
media service in the platform api. 
  - reduce number of packages supported
  - allow coordination for audio playback from multiple sources
  - support multiple encoding formats

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1283065/+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 1337794] [NEW] [whishlist] Missing pause button in copy window

2014-07-04 Thread obibann
Public bug reported:

Ubuntu teams should include a "pause" button on copy windows.

Thank you !

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: unity 7.2.1+14.04.20140513-0ubuntu2
ProcVersionSignature: Ubuntu 3.13.0-24.47-generic 3.13.9
Uname: Linux 3.13.0-24-generic x86_64
.tmp.unity.support.test.0:
 
ApportVersion: 2.14.1-0ubuntu3.2
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
CurrentDesktop: Unity
Date: Fri Jul  4 12:44:06 2014
DistUpgraded: Fresh install
DistroCodename: trusty
DistroVariant: ubuntu
DkmsStatus:
 virtualbox, 4.3.10, 3.13.0-24-generic, x86_64: installed
 virtualbox, 4.3.10, 3.13.0-27-generic, x86_64: installed
 virtualbox, 4.3.10, 3.13.0-29-generic, x86_64: installed
 virtualbox, 4.3.10, 3.13.0-30-generic, x86_64: installed
GraphicsCard:
 Advanced Micro Devices, Inc. [AMD/ATI] Robson CE [Radeon HD 6370M/7370M] 
[1002:68e4] (prog-if 00 [VGA controller])
   Subsystem: ASUSTeK Computer Inc. Radeon HD 6370M [1043:1c92]
InstallationDate: Installed on 2014-04-20 (75 days ago)
InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
MachineType: ASUSTeK Computer Inc. K52JT
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-24-generic 
root=UUID=20c42177-7d37-49ef-a5b2-c8d00012a18d ro quiet splash acpi_osi=Linux 
vt.handoff=7
SourcePackage: unity
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 01/25/2011
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: K52JT.206
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: K52JT
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.:bvrK52JT.206:bd01/25/2011:svnASUSTeKComputerInc.:pnK52JT:pvr1.0:rvnASUSTeKComputerInc.:rnK52JT:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr1.0:
dmi.product.name: K52JT
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK Computer Inc.
version.compiz: compiz 1:0.9.11+14.04.20140423-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.52-1
version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.1
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.1
version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3.1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2
xserver.bootTime: Fri Jul  4 12:06:03 2014
xserver.configfile: /etc/X11/xorg.conf
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs: Output  HDMI-0LVDS 
  VGA-0
xserver.version: 2:1.15.1-0ubuntu2
xserver.video_driver: radeon

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


** Tags: amd64 apport-bug compiz-0.9 trusty ubuntu

** Summary changed:

- Missing pause button in copy window
+ [whishlist] Missing pause button in copy window

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

Title:
  [whishlist] Missing pause button in copy window

Status in “unity” package in Ubuntu:
  New

Bug description:
  Ubuntu teams should include a "pause" button on copy windows.

  Thank you !

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: unity 7.2.1+14.04.20140513-0ubuntu2
  ProcVersionSignature: Ubuntu 3.13.0-24.47-generic 3.13.9
  Uname: Linux 3.13.0-24-generic x86_64
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.14.1-0ubuntu3.2
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Fri Jul  4 12:44:06 2014
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox, 4.3.10, 3.13.0-24-generic, x86_64: installed
   virtualbox, 4.3.10, 3.13.0-27-generic, x86_64: installed
   virtualbox, 4.3.10, 3.13.0-29-generic, x86_64: installed
   virtualbox, 4.3.10, 3.13.0-30-generic, x86_64: installed
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Robson CE [Radeon HD 6370M/7370M] 
[1002:68e4] (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. Radeon HD 6370M [1043:1c92]
  InstallationDate: Installed on 2014-04-20 (75 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr

[Dx-packages] [Bug 1337244] Re: compiz crashed with SIGSEGV in nux::WindowThread::ComputeQueuedLayout()

2014-07-04 Thread Margarita Manterola
This keeps happening over and over.  Looking at the resolution of the
other bug, I expect the code that needs to be fixed is not here, but in
the handling of some element in this queue.  I suspect some element is
getting deleted and the memory reused without it being removed from the
queue.

Here's the latest stacktrace:
#0  0x in ?? ()
#1  0x7fdd0a32c75d in nux::WindowThread::ComputeQueuedLayout 
(this=this@entry=0x2319f40) at ./WindowThread.cpp:318
#2  0x7fdd0a32db28 in nux::WindowThread::RenderInterfaceFromForeignCmd 
(this=0x2319f40, clip=...) at ./WindowThread.cpp:1627
#3  0x7fdd0ba61389 in unity::UnityScreen::paintDisplay() () from 
/usr/lib/compiz/libunityshell.so
#4  0x7fdd0ba61748 in unity::UnityScreen::glPaintOutput(GLScreenPaintAttrib 
const&, GLMatrix const&, CompRegion const&, CompOutput*, unsigned int) () from 
/usr/lib/compiz/libunityshell.so
#5  0x7fdd1b3da272 in GLScreen::glPaintOutput(GLScreenPaintAttrib const&, 
GLMatrix const&, CompRegion const&, CompOutput*, unsigned int) ()
  from /usr/lib/compiz/libopengl.so
#6  0x7fdd1b3daed4 in PrivateGLScreen::paintOutputs(std::list >&, unsigned int, CompRegion const&) ()
  from /usr/lib/compiz/libopengl.so
#7  0x7fdd203e144f in CompositeScreen::paint(std::list >&, unsigned int) ()
  from /usr/lib/compiz/libcomposite.so
#8  0x7fdd203e4af2 in CompositeScreen::handlePaintTimeout() () from 
/usr/lib/compiz/libcomposite.so
#9  0x7fdd2cc6b53d in CompTimer::triggerCallback() () from 
/usr/lib/libcompiz_core.so.ABI-20140123
#10 0x7fdd2cc6b5ef in CompTimeoutSource::callback() () from 
/usr/lib/libcompiz_core.so.ABI-20140123
#11 0x7fdd2cc6ab4d in CompTimeoutSource::dispatch(sigc::slot_base*) () from 
/usr/lib/libcompiz_core.so.ABI-20140123
#12 0x7fdd2b15735f in Glib::Source::dispatch_vfunc(_GSource*, int 
(*)(void*), void*) () from /usr/lib/x86_64-linux-gnu/libglibmm-2.4.so.1
#13 0x7fdd2ac49ce5 in g_main_context_dispatch () from 
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#14 0x7fdd2ac4a048 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#15 0x7fdd2ac4a30a in g_main_loop_run () from 
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#16 0x7fdd2cc260eb in 
compiz::private_screen::EventManager::startEventLoop(_XDisplay*) () from 
/usr/lib/libcompiz_core.so.ABI-20140123
#17 0x00401971 in main ()

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

Title:
  compiz crashed with SIGSEGV in
  nux::WindowThread::ComputeQueuedLayout()

Status in “unity” package in Ubuntu:
  New

Bug description:
  Hi, this is basically the same bug as
  https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1298202, but that
  bug is marked as Fix Released with Unity 7.2.0, and I'm still seeing
  this bug on trusty, with the latest Unity version (unity
  7.2.1+14.04.20140513-0ubuntu2).  I already mentioned in that bug that
  I was still seeing it quite a while ago, but got no reply to that.

  Crashes are being experienced in multiple machines, while unlocking
  the screen.  The stacktraces vary, but they always fail in the same
  function and same line.

  First stacktrace:
  #0  0x0410 in ?? ()
  #1  0x7fd4bf4eb75d in nux::WindowThread::ComputeQueuedLayout 
(this=this@entry=0x22c1990) at ./WindowThread.cpp:318
  #2  0x7fd4bf4ecb28 in nux::WindowThread::RenderInterfaceFromForeignCmd 
(this=0x22c1990, clip=...) at ./WindowThread.cpp:1627
  #3  0x7fd4c0c20389 in unity::UnityScreen::paintDisplay() () from 
/usr/lib/compiz/libunityshell.so
  #4  0x7fd4c0c20748 in 
unity::UnityScreen::glPaintOutput(GLScreenPaintAttrib const&, GLMatrix const&, 
CompRegion const&, CompOutput*, unsigned int)
 () from /usr/lib/compiz/libunityshell.so
  #5  0x7fd4d4f2e272 in GLScreen::glPaintOutput(GLScreenPaintAttrib const&, 
GLMatrix const&, CompRegion const&, CompOutput*, unsigned int) ()
from /usr/lib/compiz/libopengl.so
  #6  0x7fd4d4f2eed4 in 
PrivateGLScreen::paintOutputs(std::list >&, unsigned int, CompRegion const&) ()
from /usr/lib/compiz/libopengl.so
  #7  0x7fd4d556944f in CompositeScreen::paint(std::list >&, unsigned int) ()
from /usr/lib/compiz/libcomposite.so
  #8  0x7fd4d556caf2 in CompositeScreen::handlePaintTimeout() () from 
/usr/lib/compiz/libcomposite.so
  #9  0x7fd4e12c053d in CompTimer::triggerCallback() () from 
/usr/lib/libcompiz_core.so.ABI-20140123
  #10 0x7fd4e12c05ef in CompTimeoutSource::callback() () from 
/usr/lib/libcompiz_core.so.ABI-20140123
  #11 0x7fd4e12bfb4d in CompTimeoutSource::dispatch(sigc::slot_base*) () 
from /usr/lib/libcompiz_core.so.ABI-20140123
  #12 0x7fd4df7ac35f in Glib::Source::dispatch_vfunc(_GSource*, int 
(*)(void*), void*) () from /usr/lib/x86_64-linux-gnu/libglibmm-2.4.so.1
  #13 0x7fd4df29ece5 in g_main_context_dispatch () from 
/lib/x86_64-linux-gnu/lib

[Dx-packages] [Bug 1319352] Re: indicator-application does not work in MATE 1.8

2014-07-04 Thread Monsta
I've compiled indicator-application-gtk2 from source and found out
there's indicator-application-service executable which doesn't make it
to the package. It can be found only in the src subdir after the
compilation.

If I run it manually, I get this:

$ ./indicator-application-service

(process:16085): libindicator-WARNING **: No watchers, service timing
out.

(process:16085): GLib-CRITICAL **: Source ID 20 was not found when
attempting to remove it


Then it exits.

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

Title:
  indicator-application does not work in MATE 1.8

Status in “indicator-application” package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu version: Xubuntu 14.04 LTS
  indicator-application version: 12.10.1+14.04.20140407-0ubuntu1
  indicator-application-gtk2 version: 12.10.0.1-0ubuntu2

  
  Steps to reproduce:

  1. Install Xubuntu 14.04
  2. Install MATE 1.8 following the instructions at 
http://www.webupd8.org/2014/03/how-to-install-mate-18-in-ubuntu.html
  3. Install mate-indicator-applet (a container for the indicators) and add it 
to MATE panel
  4. Install indicator-application and indicator-application-gtk2

  
  What expected to happen:

  Working indicator-application, displaying the network manager icon in 
mate-indicator-applet area.
  At the same time, the network manager icon should disappear from the 
notification area.

  
  What happened instead:

  The indicator-application apparently does not run.
  No network manager icon is displayed in mate-indicator-applet area.
  The network manager icon is still displayed in the notification area.

  
  Additional info:

  1. All the steps above worked fine before in Ubuntu 13.10.

  2. If I manually run 
/usr/lib/x86_64-linux-gnu/indicator-application/indicator-application-service 
from the terminal,
  the network manager icon disappears from the notification area, but it still 
doesn't appear in mate-indicator-applet area.
  At the same time, a message is displayed in the terminal:

  initctl: UPSTART_SESSION isn't set in the environment. Unable to
  locate the Upstart instance.

  3. On the contrary, indicator-sound/indicator-sound-gtk2 work in MATE just 
fine. The volume icon is properly displayed
  in mate-indicator-applet area.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-application/+bug/1319352/+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