[Touch-packages] [Bug 346912] Re: Tracker index corruption (was Tracker does not stop indexing)
have not seen this one jet in newer version. -- 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/346912 Title: Tracker index corruption (was Tracker does not stop indexing) Status in Tracker: Expired Status in tracker package in Ubuntu: Incomplete Status in tracker source package in Jaunty: Won't Fix Bug description: I recently realized that tracker does not always give me the search results I expected, meaning that it does not find documents containing certain words. A quick look through the indexer preferences, I doubled the "maximal amount of text to index" and "maximum number of unique words to index". After doing so, the tracker does not stop indexing. The information message when I hover over the tracker icons says: Tracker: Indexing Done: 883 of 22296 Estimated: 33 minutes ... Elapsed: 01 minute ... This message hasn't changed for about a day, and the indexing continues. One of my log files is continuously flooded with the following messages: nasko@serre:~/.local/share/tracker$ tail -n20 tracker-indexer.log 22 Mar 2009, 15:11:17: Tracker-Warning **: Could not store word 'previous': with fatal error 22 Mar 2009, 15:11:17: Tracker-Warning **: Could not store word 'troubl': with fatal error 22 Mar 2009, 15:11:17: Tracker-Warning **: Could not store word 'preprocessor': with fatal error 22 Mar 2009, 15:11:17: Tracker-Warning **: Could not store word 'ac_abs_top_builddir': with fatal error 22 Mar 2009, 15:11:17: Tracker-Warning **: Could not store word 'detail': with fatal error 22 Mar 2009, 15:11:17: Tracker-Warning **: Could not store word 'call': with fatal error 22 Mar 2009, 15:11:17: Tracker-Warning **: Could not store word 'paramet': with fatal error 22 Mar 2009, 15:11:17: Tracker-Warning **: Could not store word 'offshoot': with fatal error 22 Mar 2009, 15:11:17: Tracker-Warning **: Could not store word 'with_gcc': with fatal error 22 Mar 2009, 15:11:17: Tracker-Warning **: Could not store word 'honor': with fatal error I would like to have tracker index my files more fully, and yet have it do that in a normal manner. Is there a way to prevent this problem? To manage notifications about this bug go to: https://bugs.launchpad.net/tracker/+bug/346912/+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 1608646] Re: ip4 static routes added in NetworkManager UI fail and prevent connection
For me it works when I enter no Gateway -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1608646 Title: ip4 static routes added in NetworkManager UI fail and prevent connection Status in network-manager package in Ubuntu: Confirmed Bug description: lsb_release -rd: Description: Ubuntu 16.04.1 LTS Release: 16.04 Network Settings package version in Software Center: 15.04.0+16.04.20160705-0ubuntu1 Prior to upgrading to 16.04 LTS I was running 14.04 LTS. Using the "Edit Connections..." menu option I had created a custom Ethernet connection that had some custom routes added. These routes are required for me to connect to certain resources on a local network while using Wifi for basic internet. (Physical network locked down, no Internet access available) I've attached a screenshot showing the routes. These routes were working great in 14.04 (And prior releases of Ubuntu). However, upon upgrading to 16.04, I noticed this connection would no longer "connect". It would just silently fail. I noticed that if I deleted my custom routes, it would work, but I need those in order to connect to my required network services. When I try to connect with the routes in place, the connection silently fails in the NetworkManager UI (I get no error message in the UI) but I took a look at syslog and found these: Aug 1 08:15:19 jeremy-ThinkPad-X1-Carbon-4th NetworkManager[2868]: [1470057319.7268] platform-linux: do-add-ip4-route[2: 10.104.0.0/16 0]: failure 101 (Network is unreachable) Aug 1 08:15:19 jeremy-ThinkPad-X1-Carbon-4th NetworkManager[2868]: [1470057319.7271] platform-linux: do-add-ip4-route[2: 10.105.0.0/16 0]: failure 101 (Network is unreachable) Aug 1 08:15:19 jeremy-ThinkPad-X1-Carbon-4th NetworkManager[2868]: [1470057319.7272] platform-linux: do-add-ip4-route[2: 10.51.35.0/24 0]: failure 101 (Network is unreachable) Aug 1 08:15:19 jeremy-ThinkPad-X1-Carbon-4th NetworkManager[2868]: [1470057319.7273] platform-linux: do-add-ip4-route[2: 10.140.76.0/24 0]: failure 101 (Network is unreachable) Aug 1 08:15:19 jeremy-ThinkPad-X1-Carbon-4th NetworkManager[2868]: [1470057319.7281] device (enp0s31f6): state change: ip-config -> failed (reason 'config-failed') [70 120 4] Aug 1 08:15:19 jeremy-ThinkPad-X1-Carbon-4th NetworkManager[2868]: [1470057319.7289] device (enp0s31f6): Activation: failed for connection 'Windstream' Aug 1 08:15:19 jeremy-ThinkPad-X1-Carbon-4th NetworkManager[2868]: [1470057319.7309] device (enp0s31f6): state change: failed -> disconnected (reason 'none') [120 30 0] Now, if I remove the custom routes from the UI, then I can connect. I them manually add the routes using the "ip" command: sudo /sbin/ip route add 10.104.0.0/16 dev enp0s31f6 sudo /sbin/ip route add 10.105.0.0/16 dev enp0s31f6 sudo /sbin/ip route add 10.51.35.0/24 dev enp0s31f6 sudo /sbin/ip route add 10.140.76.0/24 dev enp0s31f6 This is able to add the routes successfully. So there has to be some problem in the new implementation of NetworkManager in 16.04, because these routes worked in 14.04 and they still work in 16.04 if I just manually add them from the command line. For now I can work around this issue by manually adding these routes from the command line every time I connect. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1608646/+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 264144] Re: NetworkManager VPN configuration export does not work
I confirm this issue in 16.04 x64 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/264144 Title: NetworkManager VPN configuration export does not work Status in NetworkManager: Invalid Status in NetworkManager-OpenVPN: Fix Released Status in network-manager package in Ubuntu: Invalid Status in network-manager-openvpn package in Ubuntu: Fix Released Status in network-manager-pptp package in Ubuntu: Triaged Bug description: Intrepid, network-manager: 0.7~~svn20080818t061112+eni0-0ubuntu1 Subject says it. To reproduce: 1. Configure VPN connection 2. Try to Export it to a file As a result I got cryptic error message dialog: === Cannot export VPN connection The VPN connection 'vpn_test' could not be exported to vpn_test (pptp).conf. Error: unknown error. === Expected behavior: Configuration saved to a file. = WORKAROUND The configuration is saved in a file in /etc/NetworkManager/system-connections/ that has the same name as the connection. This file can be examined with a text editor and/or copied around to other machines. source: https://bugs.launchpad.net/ubuntu/+source/network-manager-openvpn/+bug/264144/comments/27 WORKAROUND = To manage notifications about this bug go to: https://bugs.launchpad.net/network-manager/+bug/264144/+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
