[Touch-packages] [Bug 1825963] Re: Abysmal memory leak on tracker-extract
The bug is still present in Ubuntu 19.10. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to tracker in Ubuntu. https://bugs.launchpad.net/bugs/1825963 Title: Abysmal memory leak on tracker-extract Status in tracker package in Ubuntu: Confirmed Bug description: After upgrading from 18.10 to 19.04 my Ubuntu desktop started lagging madly. It became very difficult to use and I discovered the problem to be tracker-extract running and very rapidly leaking memory up to 100% and breaching into swap memory. I tried killing it several times but Tracker appears to relaunch it every time, so I deleted it from /usr/lib/tracker entirely. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: tracker 2.1.8-2 ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 Uname: Linux 5.0.0-13-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Apr 23 13:02:25 2019 InstallationDate: Installed on 2019-03-11 (42 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) SourcePackage: tracker UpgradeStatus: Upgraded to disco on 2019-04-23 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tracker/+bug/1825963/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1825963] Re: Abysmal memory leak on tracker-extract
In the directory there are 10666 files, total size 735,5 MB. There are 723 .dds files with a total size of 248.2 MB >Could you run `tracker extract *` inside the problematic directory and see what happens There are various sub-directories with .dds files, running tracker inside them gives very similar outputs. Two outputs here https://pastebin.com/NTzha2Ww and here https://pastebin.com/MEiTzZPq It however doesn't loop forever, it just gives one error message for every single dds file and then exists properly. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to tracker in Ubuntu. https://bugs.launchpad.net/bugs/1825963 Title: Abysmal memory leak on tracker-extract Status in tracker package in Ubuntu: Confirmed Bug description: After upgrading from 18.10 to 19.04 my Ubuntu desktop started lagging madly. It became very difficult to use and I discovered the problem to be tracker-extract running and very rapidly leaking memory up to 100% and breaching into swap memory. I tried killing it several times but Tracker appears to relaunch it every time, so I deleted it from /usr/lib/tracker entirely. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: tracker 2.1.8-2 ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 Uname: Linux 5.0.0-13-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Apr 23 13:02:25 2019 InstallationDate: Installed on 2019-03-11 (42 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) SourcePackage: tracker UpgradeStatus: Upgraded to disco on 2019-04-23 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tracker/+bug/1825963/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1825963] Re: Abysmal memory leak on tracker-extract
After removing the folder with those .dds files, the memory leak of tracker-extract doesn't occur. However IMO this can't be regarded as anything as a temporary workaround. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to tracker in Ubuntu. https://bugs.launchpad.net/bugs/1825963 Title: Abysmal memory leak on tracker-extract Status in tracker package in Ubuntu: New Bug description: After upgrading from 18.10 to 19.04 my Ubuntu desktop started lagging madly. It became very difficult to use and I discovered the problem to be tracker-extract running and very rapidly leaking memory up to 100% and breaching into swap memory. I tried killing it several times but Tracker appears to relaunch it every time, so I deleted it from /usr/lib/tracker entirely. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: tracker 2.1.8-2 ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 Uname: Linux 5.0.0-13-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Apr 23 13:02:25 2019 InstallationDate: Installed on 2019-03-11 (42 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) SourcePackage: tracker UpgradeStatus: Upgraded to disco on 2019-04-23 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tracker/+bug/1825963/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1825963] Re: Abysmal memory leak on tracker-extract
Here you go. Those are texture files from a mod for the game "Crusader Kings 2". >does it stop doing that if you remove those? Can I exclude the folder from being indexed by tracker? I'll try that (or removing the files) tomorrow. ** Attachment added: "minimap_area.dds" https://bugs.launchpad.net/ubuntu/+source/tracker/+bug/1825963/+attachment/5258276/+files/minimap_area.dds -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to tracker in Ubuntu. https://bugs.launchpad.net/bugs/1825963 Title: Abysmal memory leak on tracker-extract Status in tracker package in Ubuntu: Incomplete Bug description: After upgrading from 18.10 to 19.04 my Ubuntu desktop started lagging madly. It became very difficult to use and I discovered the problem to be tracker-extract running and very rapidly leaking memory up to 100% and breaching into swap memory. I tried killing it several times but Tracker appears to relaunch it every time, so I deleted it from /usr/lib/tracker entirely. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: tracker 2.1.8-2 ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 Uname: Linux 5.0.0-13-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Apr 23 13:02:25 2019 InstallationDate: Installed on 2019-03-11 (42 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) SourcePackage: tracker UpgradeStatus: Upgraded to disco on 2019-04-23 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tracker/+bug/1825963/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1825963] Re: Abysmal memory leak on tracker-extract
I have the exact same issue as gert7. Tracker-extract fills my entire memory until kernel kills the process, after which tracker-extract gets started again with the same situation after a few seconds. The only way to make the system usable again is to forcibly kill all tracker processes. While clogging up the memory, tracker-extract also gives some errors to journalctl like this, on two specific .dds files. >Apr 23 17:04:27 apfelgriebs-desktop tracker-extract[3527]: Call to gst_discoverer_discover_uri(file:///[...]/[...].dds) failed: Internal data stream error. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to tracker in Ubuntu. https://bugs.launchpad.net/bugs/1825963 Title: Abysmal memory leak on tracker-extract Status in tracker package in Ubuntu: Incomplete Bug description: After upgrading from 18.10 to 19.04 my Ubuntu desktop started lagging madly. It became very difficult to use and I discovered the problem to be tracker-extract running and very rapidly leaking memory up to 100% and breaching into swap memory. I tried killing it several times but Tracker appears to relaunch it every time, so I deleted it from /usr/lib/tracker entirely. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: tracker 2.1.8-2 ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 Uname: Linux 5.0.0-13-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Apr 23 13:02:25 2019 InstallationDate: Installed on 2019-03-11 (42 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) SourcePackage: tracker UpgradeStatus: Upgraded to disco on 2019-04-23 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tracker/+bug/1825963/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 46586] Re: Logitech Media Keyboard Elite not fully supported
Still affected by this bug in 15.04
The media keys work fine as far as I can see, however the following keys
produce no keycode (checked with xinput), meaning that can't be used at
all.
No keycode:
Reset zoom
Zoom in
Zoom out
Word key
Excel key
Launch A
Launch B
Launch C
Launch D
Messenger
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xkeyboard-config in
Ubuntu.
https://bugs.launchpad.net/bugs/46586
Title:
Logitech Media Keyboard Elite not fully supported
Status in xkeyboard-config package in Ubuntu:
Confirmed
Bug description:
The media keys on the Logitech Media Keyboard Elite are not supported
properly - the layout appears to be different than the others already
included and the kernel does not recognise many of the media/extra
keys. Currently I have the keyboard hooked up through the USB port.
I have made the following changes to my system to attempt to support
this keyboard. Caution: Pressing the key I have mapped as XF86LaunchC
(F11 with the F-mode light off) will reliably crash and reboot the
system - I have no idea why.
At boot time, the following script is run to map the scancodes to the
console level codes. I assume that this keyboard really requires
fixes in the kernel code to recognise this keyboard without the use of
extra scan codes.
# Kernel level keycode mappings for the Logitech Media Keyboard Elite USB
# 6a 190 Zoom In
# e004 191 Zoom Out
# 6b 192 Zoom Reset
# e011 193 Messenger
# e05a 194 Mode F (switch function keys)
# e03b 195 (F1 )Help
# e03c 196 (F2 )Word
# e03d 197 (F3 )Excel
# e03e 198 (F4 )Powerpoint
# e03f 199 (F5 )Undo
# e040 200 (F6 )Redo
# e041 201 (F7 )Print
# e042 202 (F8 )Save
# e043 203 (F9 )Box A
# e044 204 (F10)Box B
# e057 205 (F11)Box C
# e058 206 (F12)Box D
setkeycodes \
6a 190 \
e004 191 \
6b 192 \
e011 193 \
e05a 194 \
e03b 195 \
e03c 196 \
e03d 197 \
e03e 198 \
e03f 199 \
e040 200 \
e041 201 \
e042 202 \
e043 203 \
e044 204 \
e057 205 \
e058 206
# ---
I also made the following alterations to the symbols in
/etc/X11/xkb/symbols/inet:
--- inet.20060516 2006-05-16 20:44:30.0 -0400
+++ inet2006-05-16 20:59:41.0 -0400
@@ -1244,6 +1244,39 @@
key { [ XF86AudioRaiseVolume ] };
};
+// Logitech Media Keyboard Elite
+partial alphanumeric_keys
+xkb_symbols "logimedelite" {
+include "inet(logitech_base)"
+
+key { [ XF86ZoomIn] };
+key { [ XF86ZoomOut ] };
+key { [ XF86Clear ] };
+key { [ XF86AudioPlay, XF86AudioPause ] };
+key { [ XF86AudioStop ] };
+key { [ XF86AudioNext ] };
+key { [ XF86Messenger ] };
+key { [ XF86Calculator] };
+key { [ XF86ModeLock ] };
+
+key { [ XF86Help ] };
+key { [ XF86Word ] };
+key { [ XF86Excel ] };
+key { [ XF86Finance ] };
+
+key { [ XF86Back ] };
+key { [ XF86Forward ] };
+key { [ XF86Book ] };
+key { [ XF86Save ] };
+
+key { [ XF86LaunchA ] };
+key { [ XF86LaunchB ] };
+key { [ XF86LaunchC ] };
+key { [ XF86LaunchD ] };
+
+};
+
+
partial alphanumeric_keys
xkb_symbols "logiultrax" {
include "inet(logitech_base)"
Then the three rules files in /etc/X11/xkb/rules were updated as follows:
toby@nexus:/etc/X11/xkb/rules$ diff -Naur base.20060516 base
--- base.20060516 2006-05-16 21:00:45.0 -0400
+++ base2006-05-16 21:01:43.0 -0400
@@ -38,7 +38,7 @@
honeywell_euroboard \
rapidaccess rapidaccess2 rapidaccess2a \
ltcd logiaccess logicdp logicdpa logicdit logicink logiciink \
- logiinkse logiinkseusb logiitc logiik itouch logiultrax \
+ logiinkse logiinkseusb logiitc logiik itouch logimedelite
logiultrax \
mx1998 mx2500 mx2750 \
microsoftinet microsoftpro microsoftprousb microsoftprooem
microsoftprose \
microsoftoffice microsoftmult \
toby@
