[Bug 1385321] Re: memory and file descriptor (zeitgeist/activity.sqlite) leak in empathy
** Summary changed: - memory and file descriptor leak in empathy + memory and file descriptor (zeitgeist/activity.sqlite) leak in empathy -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to empathy in Ubuntu. https://bugs.launchpad.net/bugs/1385321 Title: memory and file descriptor (zeitgeist/activity.sqlite) leak in empathy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/empathy/+bug/1385321/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1385321] [NEW] memory and file descriptor leak in empathy
Public bug reported:
empathy process takes almost 1G of RSS memory, that's way too much and
looks like leak as soon as RSS grows over time.
Another symptom is lots of duplicate open files,
$HOME/.local/share/zeitgeist/activity.sqlite is opened 160 times according to
lsof:
$ lsof -p 3970 | awk '{print $(NF)}' | sort | uniq -c | awk '($1 > 1)'
8 anon_inode
2 /dev/pts/27
160 /home/darkk/.local/share/zeitgeist/activity.sqlite
2 /home/darkk/.local/share/zeitgeist/activity.sqlite-shm
160 /home/darkk/.local/share/zeitgeist/activity.sqlite-wal
2 pipe
6 socket
2 /SYSV
Full lsof output is attached as lsof.txt
ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: empathy 3.8.6-0ubuntu9.1
ProcVersionSignature: Ubuntu 3.13.0-37.64-generic 3.13.11.7
Uname: Linux 3.13.0-37-generic x86_64
ApportVersion: 2.14.1-0ubuntu3.5
Architecture: amd64
CurrentDesktop: Unity
Date: Fri Oct 24 18:44:33 2014
ExecutablePath: /usr/bin/empathy
InstallationDate: Installed on 2011-07-14 (1198 days ago)
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release amd64 (20110426)
SourcePackage: empathy
UpgradeStatus: Upgraded to trusty on 2014-05-12 (165 days ago)
** Affects: empathy (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug trusty
** Attachment added: "lsof -p 3970 >lsof.txt"
https://bugs.launchpad.net/bugs/1385321/+attachment/4243686/+files/lsof.txt
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to empathy in Ubuntu.
https://bugs.launchpad.net/bugs/1385321
Title:
memory and file descriptor leak in empathy
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/empathy/+bug/1385321/+subscriptions
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1058365] Re: Empathy (telepathy-sofiasip) cannot connect to SIP server via VPN
Here is relevant discussion on sofia-sip mailing list: http://sourceforge.net/p/sofia-sip/mailman/message/26158361/ -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to empathy in Ubuntu. https://bugs.launchpad.net/bugs/1058365 Title: Empathy (telepathy-sofiasip) cannot connect to SIP server via VPN To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/empathy/+bug/1058365/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1058365] Re: Empathy (telepathy-sofiasip) cannot connect to SIP server via VPN
It's hard to tell if it's bug in Empathy, telepathy-rakia, sofia-sip or network-manager-openvpn. Here is my case. I have three SIP accounts: one for my company and two for personal usage, all three accounts work in "simple" case with single global IP address without NAT. I have following network setup that kills SIP connection: - my Wi-Fi is in 192.168.1.0/24 network and gives me default gateway and NAT - my VPN gives me _global_ IPv4 and IPv6 addresses, I __don't__ use VPN as default gateway and route only "enterprise" networks via VPN tunnel - my virual 10.0.1.0/24 network connects me with virtualboxes I use for development When VPN is disconnected telepathy selects 192.168... address for outgoing packets and all three SIP accounts work like charm. When VPN is __connected__ telepathy selects VPN IP address as source address. So, kernel routes packets via Wi-Fi network (!), not via VPN for two accounts of three. "company" account still works as it's reachable both via VPN and without it. Packets routed like that may be dropped due to various reasons - NAT, reverse-path filter, etc. The reason does not matter much. Bottomline - there are several ways to fix the issue. 1. add proper source-based routing setup to network-manager. In my case all SIP calls will be routed via VPN with this configuration as sofia-sip library prefers VPN address over everything else. It's not good in terms of latency, but it works. 2. update local-ip-address in SIP settings on network connectiviy change I implemented NetworkManager dispatcher script that sets local-ip-address using IP routing table. It does not look like generic solution, but it works for me: https://github.com/darkk/home/blob/master/bin/nm-sofia-reroute 3. add option to sofia-sip library to disable complex source address selection I've not actually tried it, but the script does alike job. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to empathy in Ubuntu. https://bugs.launchpad.net/bugs/1058365 Title: Empathy (telepathy-sofiasip) cannot connect to SIP server via VPN To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/empathy/+bug/1058365/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1218322] Re: Can't set keyboard layout change to alt+shift, ctrl+shift, etc.
I confirm Vladimir's words. Moreover, sometimes capslock is permanently turned on instead of layout switching: gkjgkjgОлпорпорпролпОПОПОПРОПОРплопрололпJkghkjghjkghjhg ^ I've not touched shift :) -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1218322 Title: Can't set keyboard layout change to alt+shift, ctrl+shift, etc. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-settings-daemon/+bug/1218322/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1235472] Re: New messages do not show
The bug is also reproduced if the person is not in contact list, but some chat history exists. BUG: In this case I see no __new__ messages in the chat tab (only old messages from the tail of the history are displayed). Other symptoms are same. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to empathy in Ubuntu. https://bugs.launchpad.net/bugs/1235472 Title: New messages do not show To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/empathy/+bug/1235472/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1235472] Re: New messages do not show
Alike issue here, here is the test-case: I receive a message from a person not in my contact list via XMPP for the first time (no history exists). telepathy-indicator shows new message. I click a line in the indicator. New chat tab is opened in the empathy-chat with the contact. BUG: No messages are shown in the tab at all — new messages should be shown BUG: window title shows "(-1 unread)" — that's nonsense :) BUG: unread-messages icon does not disappear even in focus is in the tab — that may be another simptom of the bug. If I look at "Previous conversations" at the moment I see new messages. If I close the tab and reopen with Ctrl-Shift-Tab it I see new messages. I have empathy 3.8.4-1ubuntu1 ** Attachment added: "Screenshot of the bug" https://bugs.launchpad.net/ubuntu/+source/empathy/+bug/1235472/+attachment/3900404/+files/empathy-chat%202013-11-05%2012%3A47%3A21.png -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to empathy in Ubuntu. https://bugs.launchpad.net/bugs/1235472 Title: New messages do not show To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/empathy/+bug/1235472/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1218322] Re: Can't set keyboard layout change to alt+shift, ctrl+shift, etc.
> Single keys hotkeys are not working: Alt (opens HUD), Shift, Ctrl, Win (opens > HUD). But IMHO they used very seldom as layout switchers. Ctrl was default layout switcher in linux console (bare TTY) for quite a long time, so there may be significant number of users using Ctrl in X too. But I have no numbers to back my words up. Also, you say that Alt opens HUD. It's not always true due to bug 1237121. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1218322 Title: Can't set keyboard layout change to alt+shift, ctrl+shift, etc. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-settings-daemon/+bug/1218322/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1237121] Re: Keyboard: cannot bind "Alt L" to "Key to show the HUD" => Disabled
Also some key combinations can be set in control center, but do not work properly. I can set Alt+Multikey (Alt + menu), but HUD is not activated with this combination. On the other hand Alt-Z works fine. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1237121 Title: Keyboard: cannot bind "Alt L" to "Key to show the HUD" => Disabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1237121/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1237121] Re: Keyboard: cannot bind "Alt L" to "Key to show the HUD" => Disabled
I suffer from same bug. I use two layouts configured via XKB. I reverted to XKB due to bug in iBus/layout-indicator/smthng-else making layout switching unusable #1218322. Command-line to configure the layout is: $ setxkbmap -layout us,ru -option grp:caps_toggle,grp_led:scroll,compose:menu I'm sure original reporter has different settings :-) -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1237121 Title: Keyboard: cannot bind "Alt L" to "Key to show the HUD" => Disabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1237121/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1103394] Re: [raring] History dialog does not decode UTF-8 (displays за symbols)
What package fixes the issue?
I still observe the bug in the logs and I have folowing '*pathy*' packages
installed
$ dpkg -l | grep pathy | grep ^ii | awk '{printf "%s=%s ", $2, $3}'
empathy=3.6.4-0ubuntu4.1 empathy-common=3.6.4-0ubuntu4.1
libfolks-telepathy22=0.4.2-0ubuntu1 libfolks-telepathy25=0.8.0-1
libmission-control-plugins0=1:5.14.0-0ubuntu2
libtelepathy-farstream3:amd64=0.6.0-1 libtelepathy-glib0:amd64=0.20.2-0ubuntu1
libtelepathy-logger3:amd64=0.8.0-0ubuntu1
nautilus-sendto-empathy=3.6.4-0ubuntu4.1 python-telepathy=0.15.19-2.1build1
telepathy-gabble=0.16.5-0ubuntu1.1 telepathy-haze=0.6.0-1
telepathy-idle=0.1.14-1ubuntu0.1
telepathy-indicator=0.3.1daily13.03.01-0ubuntu1 telepathy-logger=0.8.0-0ubuntu1
telepathy-mission-control-5=1:5.14.0-0ubuntu2 telepathy-rakia=0.7.4-1ubuntu1
telepathy-salut=0.8.1-1 telepathy-sofiasip=0.7.4-1ubuntu1
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to empathy in Ubuntu.
https://bugs.launchpad.net/bugs/1103394
Title:
[raring] History dialog does not decode UTF-8 (displays за symbols)
To manage notifications about this bug go to:
https://bugs.launchpad.net/empathy/+bug/1103394/+subscriptions
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 330437] Re: impossible to clear trash-bin when it contains read-only folders
I don't think I'll be able to install jaunty soon. I can only confirm that 8.04-LTS (with all latest updates) is affected too. Easier steps to reproduce (tested at 8.04): 1. $ mkdir -p foo/bar 2. $ touch foo/bar/baz 3. $ chmod -R u-w foo 4. $ chmod u+w foo 5. delete directory `foo' to trash * try to empty trash — `foo' persists, moreover there is no error message. * try to add `write' permission recursively for folder `foo' that is inside of trash — operation fails without any error message * try to add `write' permission to `foo/bar' that is inside of trash — operation fails with message "the action is not supported by the driver" * try to cut/paste `foo' folder from trash to Desktop — operation fails "during copying file to /home/darkk/Desktop/foo.2/bar" with details "Error occured while deleting file: permission denied" so you have two copies of `foo' tree — one in Trash and another one on Desktop (btw, why the file is copied? IMHO, cut and paste should not copy anything) * there is no way to restore `foo' to it's original place to change permissions there, at least I see no relevant commands in context menu. Error messages MAY be inexact — I had to translate them from Russian back to English. -- impossible to clear trash-bin when it contains read-only folders https://bugs.launchpad.net/bugs/330437 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug assignee. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 330437] [NEW] impossible to clear trash-bin when it contains read-only folders
Public bug reported: Binary package hint: nautilus $ lsb_release -rd Description:Ubuntu 8.10 Release:8.10 I have nautilus-1:2.24.1-0ubuntu2 Steps to reproduce: Copy directory with some subdirectories from CD to home directory and delete it to trash. Try to empty trash — and you'll get message "Error while deleting file: Permission denied". Try to empty trash with gnome applet menu (right-click on the trash icon in the taskbar gives menu and "Empty trash" is one of its items) and it'll show you progress-bar and will finish cleanup without any error but files will be left in the trash. If you try to change permissions for the folder inside of trash, you get error message "the action is not supported by the driver". Possible workaround is to run `chmod -R u+w ~/.local/share/Trash/files/*`. ** Affects: nautilus (Ubuntu) Importance: Undecided Status: New ** Tags: nautilus readonly trash -- impossible to clear trash-bin when it contains read-only folders https://bugs.launchpad.net/bugs/330437 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to nautilus in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
