[Desktop-packages] [Bug 1245979]

2013-12-19 Thread Andreas Roth
just installed KDE 4.12 on kubuntu 13.10 amd64 and the problem still appears. 
sending SIGTERM to all akonadi processes (incl. mysql) and restarting kontact 
akonadi works again (until restarting the machine).

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

Title:
  After Upgrade to Kubuntu 13.10 akondai fails to register at d-bus
  session, making kde-pim suit unusable

Status in Akonadi - The PIM Storage Service:
  Unknown
Status in “akonadi” package in Ubuntu:
  Confirmed

Bug description:
  Upon opening Kontact akonadi is supposed to be loaded but fails with
  the following error: Akonadi fails to register at d-bus session.

  I safed the self-test protocoll of the akonadi server and attached the
  report.

  I already deleted all my akonadi config files but it did not resolve
  the error.

To manage notifications about this bug go to:
https://bugs.launchpad.net/akonadi/+bug/1245979/+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 1245979]

2013-12-19 Thread Andreas Roth
i've two system with the latest 4.12 installed. on one machine (at work)
the problem occurs on every system start and on the second machine (at
home) the problem does not occur at all.

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

Title:
  After Upgrade to Kubuntu 13.10 akondai fails to register at d-bus
  session, making kde-pim suit unusable

Status in Akonadi - The PIM Storage Service:
  Unknown
Status in “akonadi” package in Ubuntu:
  Confirmed

Bug description:
  Upon opening Kontact akonadi is supposed to be loaded but fails with
  the following error: Akonadi fails to register at d-bus session.

  I safed the self-test protocoll of the akonadi server and attached the
  report.

  I already deleted all my akonadi config files but it did not resolve
  the error.

To manage notifications about this bug go to:
https://bugs.launchpad.net/akonadi/+bug/1245979/+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 1245979] Re: After Upgrade to Kubuntu 13.10 akondai fails to register at d-bus session, making kde-pim suit unusable

2013-12-13 Thread Andreas Roth
** Also affects: akonadi via
   https://bugs.kde.org/show_bug.cgi?id=326480
   Importance: Unknown
   Status: Unknown

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

Title:
  After Upgrade to Kubuntu 13.10 akondai fails to register at d-bus
  session, making kde-pim suit unusable

Status in Akonadi - The PIM Storage Service:
  Unknown
Status in “akonadi” package in Ubuntu:
  Confirmed

Bug description:
  Upon opening Kontact akonadi is supposed to be loaded but fails with
  the following error: Akonadi fails to register at d-bus session.

  I safed the self-test protocoll of the akonadi server and attached the
  report.

  I already deleted all my akonadi config files but it did not resolve
  the error.

To manage notifications about this bug go to:
https://bugs.launchpad.net/akonadi/+bug/1245979/+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 1242801] Re: meld assertion while selecting directory

2013-10-22 Thread Andreas Roth
** Bug watch added: KDE Bug Tracking System #326424
   https://bugs.kde.org/show_bug.cgi?id=326424

** Also affects: gtk2-engines-oxygen via
   https://bugs.kde.org/show_bug.cgi?id=326424
   Importance: Unknown
   Status: Unknown

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

Title:
  meld assertion while selecting directory

Status in Oxygen-gtk:
  Unknown
Status in “gtk2-engines-oxygen” package in Ubuntu:
  Invalid

Bug description:
  I installed saucy with version 1.3.4-0ubuntu1 of gtk2-engines-oxygen and meld 
version 1.8.2 on Kubuntu/KDE.
  - set GTK2 theme to oxygen-gtk in system settings
  - Start meld
  - on start screen (new comparsion) select directory comparison
  - select in either source or destination directory combo box the entry 
'Other...'
  - crash

  in the terminal i could see the callstack of the crash:
  /usr/bin/meld:167: GtkWarning: gtk_tree_model_filter_get_value: assertion 
'GTK_TREE_MODEL_FILTER (model)-priv-stamp == iter-stamp' failed
gtk.main()
  /usr/bin/meld:167: Warning: 
/build/buildd/glib2.0-2.38.0/./gobject/gtype.c:4215: type id '0' is invalid
gtk.main()
  /usr/bin/meld:167: Warning: can't peek value table for type 'invalid' which 
is not currently referenced
gtk.main()
  Segmentation fault

  I also tried with version 1.4.0-0ubuntu1 of gtk2-engines-oxygen with the same 
result. 
  If I select a QtCurve as gtk2 theme the same crash occurs. If i select a 
different theme (e.g. Clearlooks) i get the file dialog and everything is ok.

  Today i tested this issue on a raring machine and i was unable to
  reproduce this issue there.

To manage notifications about this bug go to:
https://bugs.launchpad.net/gtk2-engines-oxygen/+bug/1242801/+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 1242801] [NEW] meld assertion while selecting directory

2013-10-21 Thread Andreas Roth
Public bug reported:

I installed saucy with version 1.3.4-0ubuntu1 of gtk2-engines-oxygen and meld 
version 1.8.2 on Kubuntu/KDE.
- set GTK2 theme to oxygen-gtk in system settings
- Start meld
- on start screen (new comparsion) select directory comparison
- select in either source or destination directory combo box the entry 
'Other...'
- crash

in the terminal i could see the callstack of the crash:
/usr/bin/meld:167: GtkWarning: gtk_tree_model_filter_get_value: assertion 
'GTK_TREE_MODEL_FILTER (model)-priv-stamp == iter-stamp' failed
  gtk.main()
/usr/bin/meld:167: Warning: 
/build/buildd/glib2.0-2.38.0/./gobject/gtype.c:4215: type id '0' is invalid
  gtk.main()
/usr/bin/meld:167: Warning: can't peek value table for type 'invalid' which 
is not currently referenced
  gtk.main()
Segmentation fault

I also tried with version 1.4.0-0ubuntu1 of gtk2-engines-oxygen with the same 
result. 
If I select a QtCurve as gtk2 theme the same crash occurs. If i select a 
different theme (e.g. Clearlooks) i get the file dialog and everything is ok.

Today i tested this issue on a raring machine and i was unable to
reproduce this issue there.

** Affects: gtk2-engines-oxygen (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  meld assertion while selecting directory

Status in “gtk2-engines-oxygen” package in Ubuntu:
  New

Bug description:
  I installed saucy with version 1.3.4-0ubuntu1 of gtk2-engines-oxygen and meld 
version 1.8.2 on Kubuntu/KDE.
  - set GTK2 theme to oxygen-gtk in system settings
  - Start meld
  - on start screen (new comparsion) select directory comparison
  - select in either source or destination directory combo box the entry 
'Other...'
  - crash

  in the terminal i could see the callstack of the crash:
  /usr/bin/meld:167: GtkWarning: gtk_tree_model_filter_get_value: assertion 
'GTK_TREE_MODEL_FILTER (model)-priv-stamp == iter-stamp' failed
gtk.main()
  /usr/bin/meld:167: Warning: 
/build/buildd/glib2.0-2.38.0/./gobject/gtype.c:4215: type id '0' is invalid
gtk.main()
  /usr/bin/meld:167: Warning: can't peek value table for type 'invalid' which 
is not currently referenced
gtk.main()
  Segmentation fault

  I also tried with version 1.4.0-0ubuntu1 of gtk2-engines-oxygen with the same 
result. 
  If I select a QtCurve as gtk2 theme the same crash occurs. If i select a 
different theme (e.g. Clearlooks) i get the file dialog and everything is ok.

  Today i tested this issue on a raring machine and i was unable to
  reproduce this issue there.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gtk2-engines-oxygen/+bug/1242801/+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 1241590] Re: NetworkManager daemon segfaults on start in read_one_ip_address_or_route

2013-10-19 Thread Andreas Roth
Thanks Matthias for the quick solution. It helped on my system as well.

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

Title:
  NetworkManager daemon segfaults on start in
  read_one_ip_address_or_route

Status in “network-manager” package in Ubuntu:
  Confirmed

Bug description:
  After the update to 13.10 my network didn't come back up. After a bit
  of investigation I found the following problem:

  root@Drazi# gdb --args NetworkManager --no-daemon
  (gdb) r
  Starting program: /usr/sbin/NetworkManager --no-daemon
  [Thread debugging using libthread_db enabled]
  Using host libthread_db library /lib/x86_64-linux-gnu/libthread_db.so.1.
  [New Thread 0x72706700 (LWP 11458)]
  NetworkManager[11454]: info NetworkManager (version 0.9.8.0) is starting...
  NetworkManager[11454]: info Read config file 
/etc/NetworkManager/NetworkManager.conf
  NetworkManager[11454]: info WEXT support is enabled
  [New Thread 0x71f05700 (LWP 11459)]
  NetworkManager[11454]: info VPN: loaded org.freedesktop.NetworkManager.pptp
  NetworkManager[11454]: info VPN: loaded 
org.freedesktop.NetworkManager.openvpn
  NetworkManager[11454]: info DNS: loaded plugin dnsmasq
  [New Thread 0x71704700 (LWP 11460)]
  NetworkManager[11454]:SCPlugin-Ifupdown: init!
  NetworkManager[11454]:SCPlugin-Ifupdown: update_system_hostname
  NetworkManager[11454]:SCPluginIfupdown: management mode: unmanaged
  NetworkManager[11454]:SCPlugin-Ifupdown: devices added (path: 
/sys/devices/pci:00/:00:19.0/net/eth0, iface: eth0)
  NetworkManager[11454]:SCPlugin-Ifupdown: device added (path: 
/sys/devices/pci:00/:00:19.0/net/eth0, iface: eth0): no ifupdown 
configuration found.
  NetworkManager[11454]:SCPlugin-Ifupdown: devices added (path: 
/sys/devices/pci:00/:00:1c.3/:04:00.0/net/wlan0, iface: wlan0)
  NetworkManager[11454]:SCPlugin-Ifupdown: device added (path: 
/sys/devices/pci:00/:00:1c.3/:04:00.0/net/wlan0, iface: wlan0): no 
ifupdown configuration found.
  NetworkManager[11454]:SCPlugin-Ifupdown: devices added (path: 
/sys/devices/virtual/net/lo, iface: lo)
  NetworkManager[11454]:SCPlugin-Ifupdown: device added (path: 
/sys/devices/virtual/net/lo, iface: lo): no ifupdown configuration found.
  NetworkManager[11454]:SCPlugin-Ifupdown: end _init.
  NetworkManager[11454]: info Loaded plugin ifupdown: (C) 2008 Canonical Ltd. 
 To report bugs please use the NetworkManager mailing list.
  NetworkManager[11454]: info Loaded plugin keyfile: (c) 2007 - 2010 Red Hat, 
Inc.  To report bugs please use the NetworkManager mailing list.

  (NetworkManager:11454): GLib-GObject-CRITICAL **: Object class
  SCPluginOfono doesn't implement property 'name' from interface
  'NMSystemConfigInterface'

  (NetworkManager:11454): GLib-GObject-CRITICAL **: Object class
  SCPluginOfono doesn't implement property 'info' from interface
  'NMSystemConfigInterface'

  (NetworkManager:11454): GLib-GObject-CRITICAL **: Object class
  SCPluginOfono doesn't implement property 'hostname' from interface
  'NMSystemConfigInterface'

  (NetworkManager:11454): GLib-GObject-CRITICAL **: Object class SCPluginOfono 
doesn't implement property 'capabilities' from interface 
'NMSystemConfigInterface'
  NetworkManager[11454]:SCPlugin-Ofono: Acquired D-Bus service 
com.canonical.NMOfono
  NetworkManager[11454]:SCPlugin-Ofono: init!

  (NetworkManager:11454): GLib-CRITICAL **: g_dir_read_name: assertion 'dir != 
NULL' failed
  NetworkManager[11454]:SCPlugin-Ofono: end _init.

  (NetworkManager:11454): GLib-GObject-WARNING **: g_object_get_valist: object 
class 'SCPluginOfono' has no property named 'name'
  NetworkManager[11454]: info Loaded plugin (null): (null)
  NetworkManager[11454]:Ifupdown: get unmanaged devices count: 0
  NetworkManager[11454]:SCPlugin-Ifupdown: (7663872) ... get_connections.
  NetworkManager[11454]:SCPlugin-Ifupdown: (7663872) ... get_connections 
(managed=false): return empty list.
  NetworkManager[11454]:keyfile: parsing CarreDor ... 
  NetworkManager[11454]:keyfile: read connection 'CarreDor'
  NetworkManager[11454]:keyfile: parsing kyriad chambres ... 
  NetworkManager[11454]: file nm-utils.c: line 2584 (nm_utils_hwaddr_type): 
should not be reached
  NetworkManager[11454]: file nm-utils.c: line 2584 (nm_utils_hwaddr_type): 
should not be reached
  NetworkManager[11454]: read_field: assertion '**current' failed

  Program received signal SIGSEGV, Segmentation fault.
  0x004aec93 in read_one_ip_address_or_route (route=0, ipv6=0, 
key_name=0x76a130 addresses, setting_name=0x76a090 ipv4, file=0x71f5e0) at 
reader.c:293
  293 reader.c: No such file or directory.

  (gdb) bt
  #0  0x004aec93 in read_one_ip_address_or_route (route=0, ipv6=0, 
key_name=0x76a130 addresses, setting_name=0x76a090 ipv4,