Activity Not Available
59
I Use This!

News

Analyzed 3 months ago. based on code collected 3 months ago.
Posted 10 days ago by andyhot
Η επιλογή σήμερα της Κατερίνας ήταν αυτό: Ούτε που θυμόμουν ότι είχα Rising High αλλά χτυπηθήκαμε άνετα με το Ruthless Compassion Θα’ταν δε θα’ταν 1992 όταν αγόραζα το LP αυτό (η 12η αγορά από “techno” όπως φαίνεται και στη φώτο και μάλλον και η πιο dark). Λογικά από Discobole στην Ιπποκράτους (τότε ήταν κατεβαίνοντας δεξιά) […]
Posted about 1 year ago by Howard Lewis Shiphttps://plus.google.com/11787526736733...@blogger.com
Posted about 1 year ago by Howard Lewis Ship
Posted about 1 year ago by nore...@blogger.com (Fanf)
Seems some time, I have, sometime, a really annoying behaviour with Enlightenent (E19). It happens on Archlinux (e0.19.5.1 at the time of writting), but I think it is not related with the distribution.At the same time, it happens that new screen ... [More] detection goes wrong, so it may be due to some bad driver. I'm using Intel driver (i915).So, when it happens, the symptoms are: from the login page (I'm using lightdm, but again, not sure it plays any role), I try to log the E19 loading screen seems to want to appear, but nothing happen if I switch on tty 1, ps aux | grep enligh gives  /usr/bin/enlightenment_start and /usr/bin/enlightenment I can kill /usr/bin/enlightenment_start but the other need a kill -9 if I try  env DISPLAY=:0 enlightenment_remote -restart , the command hangs env DISPLAY=:0 xrandr gives strange "current value" for screen 0: my screen is 1600x900, and when the bug happens, I get things like "3520x994"  I get the same value on .xsession-errors, first line: zone 0x31cdfc0: 0 0   3520x994  And until now, the only solution I had to make it start again was to remove my E19 profile (~/.e) - quite frustrating.So, it happens that the problem is with "e_randr" module, the Enlightenment module in charge to manage xrandr for E. Somehow it's configuration get corrupted, and completely block any new sessions.The solution is to simply remove e_randr cache files in .e/e/config when no enlightenment process runs (so kill them before if needed): rm .e/e/config/standard/e_randr.* rm .e/e/config/default/e_randr.* The name "default" or "standard" may vary (for example, I remember that when I used to use BodhiLinux, it was bodhi or something alike). And that's all ! Hope it helps other and my future me when I'll forget how to get out of that situation. [Less]
Posted about 1 year ago by nore...@blogger.com (Fanf)
Seems some time, I have, sometime, a really annoying behaviour with Enlightenent (E19). It happens on Archlinux (e0.19.5.1 at the time of writting), but I think it is not related with the distribution.At the same time, it happens that new screen ... [More] detection goes wrong, so it may be due to some bad driver. I'm using Intel driver (i915).So, when it happens, the symptoms are:from the login page (I'm using lightdm, but again, not sure it plays any role), I try to logthe E19 loading screen seems to want to appear, but nothing happenif I switch on tty 1, ps aux | grep enligh gives  /usr/bin/enlightenment_start and /usr/bin/enlightenmentI can kill /usr/bin/enlightenment_start but the other need a kill -9if I try  env DISPLAY=:0 enlightenment_remote -restart , the command hangsenv DISPLAY=:0 xrandr gives strange "current value" for screen 0: my screen is 1600x900, and when the bug happens, I get things like "3520x994" I get the same value on .xsession-errors, first line: zone 0x31cdfc0: 0 0   3520x994 And until now, the only solution I had to make it start again was to remove my E19 profile (~/.e) - quite frustrating.So, it happens that the problem is with "e_randr" module, the Enlightenment module in charge to manage xrandr for E. Somehow it's configuration get corrupted, and completely block any new sessions.The solution is to simply remove e_randr cache files in .e/e/config when no enlightenment process runs (so kill them before if needed):rm .e/e/config/standard/e_randr.*rm .e/e/config/default/e_randr.*The name "default" or "standard" may vary (for example, I remember that when I used to use BodhiLinux, it was bodhi or something alike). And that's all ! Hope it helps other and my future me when I'll forget how to get out of that situation. [Less]
Posted almost 2 years ago by Howard Lewis Shiphttps://plus.google.com/11787526736733...@blogger.com
Posted almost 2 years ago by Howard Lewis Ship
Posted about 2 years ago by nore...@blogger.com (Fanf)
This last weed-end, I tried to upgrade my old Bodhi Linux 2.4 based on Ubuntu 12.04 LTS to Bodhi 3.0 based on Ubuntu 14.04 LTS.At some point something goes wrong with the update of the 1500 or so packages. I'm not sure about what happenned, but I ... [More] started to see stranges errors, especially when trying to install/remove/correct package, but also in other part, for example when running some Python3 scripts.Finally, everything was looking like working, but just almost working. Google fails on me on that, and I spend quite some time this week-end trying to go to the bottom of that problem, so I let a testimonial here, if it can help other people.SymptomsSegmentation fault (core dumped) with apt-get and python3 related scriptsThis appears especially when trying to install/install -f "update-notifier-common" software, for example (sorry for the French):% sudo apt-get install -fLecture des listes de paquets... FaitConstruction de l'arbre des dépendances       Lecture des informations d'état... Fait0 mis à jour, 0 nouvellement installés, 0 à enlever et 0 non mis à jour.1 partiellement installés ou enlevés.Après cette opération, 0 o d'espace disque supplémentaires seront utilisés.Paramétrage de update-notifier-common (0.154.1) ...Segmentation fault (core dumped)dpkg: error processing package update-notifier-common (--configure): le sous-processus script post-installation installé a retourné une erreur de sortie d'état 139Des erreurs ont été rencontrées pendant l'exécution : update-notifier-commonError: Timeout was reachedE: Sub-process /usr/bin/dpkg returned an error code (1)The other aspect of that problem was that any Python3 related errors lead to a stack trace like that:% python3Python 3.4.0 (default, Apr 11 2014, 13:05:11) [GCC 4.8.2] on linuxType "help", "copyright", "credits" or "license" for more information.>>> foo                                                                                                                                                                                                      Traceback (most recent call last):  File "", line 1, in NameError: name 'foo' is not definedError in sys.excepthook:Traceback (most recent call last):  File "/usr/lib/python3/dist-packages/apport_python_hook.py", line 63, in apport_excepthook    from apport.fileutils import likely_packaged, get_recent_crashes  File "/usr/lib/python3/dist-packages/apport/__init__.py", line 5, in     from apport.report import Report  File "/usr/lib/python3/dist-packages/apport/report.py", line 30, in     import apport.fileutils  File "/usr/lib/python3/dist-packages/apport/fileutils.py", line 23, in     from apport.packaging_impl import impl as packaging  File "/usr/lib/python3/dist-packages/apport/packaging_impl.py", line 20, in     import apt  File "/usr/lib/python3/dist-packages/apt/__init__.py", line 23, in     import apt_pkgImportError: /usr/lib/python3/dist-packages/apt_pkg.cpython-34m-x86_64-linux-gnu.so: undefined symbol: _ZN13pkgTagSectionC1EvOriginal exception was:Traceback (most recent call last):  File "", line 1, in NameError: name 'foo' is not definedError: Timeout was reachedThe second main symptom was that when using apt-* tools, I was getting an error message "Error: Timeout was reached" just at the end of the process. Nonetheless, everything seemed to be correctly installed/removed/etc. Bug tracking, short versionThat led me to some bug about a timeout to short for packagekit:/usr/bin/test -e /usr/share/dbus-1/system-services/org.freedesktop.PackageKit.service && /usr/bin/test -S /var/run/dbus/system_bus_socket && /usr/bin/gdbus call --system --dest org.freedesktop.PackageKit --object-path /org/freedesktop/PackageKit --timeout 4 --method org.freedesktop.PackageKit.StateHasChanged cache-updateSo I tested with a really big number, and got:/usr/bin/gdbus call --system --dest org.freedesktop.PackageKit --object-path /org/freedesktop/PackageKit --timeout 300 --method org.freedesktop.PackageKit.StateHasChanged cache-updateError: GDBus.Error:org.freedesktop.DBus.Error.TimedOut: Activation of org.freedesktop.PackageKit timed outWhat lead to testing packagkit itself:% sudo /usr/lib/packagekit/packagekitd --verbose11:12:57        PackageKit          Verbose debugging enabled (on console 1)11:12:57        PackageKit          keep_environment: 011:12:57        PackageKit          using config file '/etc/PackageKit/PackageKit.conf'11:12:57        PackageKit          syslog fucntionality disabled11:12:57        PackageKit          Log all transactions: 111:12:57        PackageKit          daemon shutdown set to 300 seconds11:12:57        PackageKit          clearing download cache at /var/cache/PackageKit/downloads11:12:57        PackageKit          destination eth0 is valid11:12:57        PackageKit          setting config file watch on /etc/PackageKit/PackageKit.conf11:12:57        PackageKit          ProxyHTTP read error: Key file does not have key 'ProxyHTTP'11:12:57        PackageKit          searching for plugins in /usr/lib/x86_64-linux-gnu/packagekit-plugins11:12:57        PackageKit          opened plugin /usr/lib/x86_64-linux-gnu/packagekit-plugins/libpk_plugin-systemd-updates.so: A plugin to write the prepared-updates file11:12:57        PackageKit          opened plugin /usr/lib/x86_64-linux-gnu/packagekit-plugins/libpk_plugin-clear-firmware-requests.so: Clears firmware requests11:12:57        PackageKit          opened plugin /usr/lib/x86_64-linux-gnu/packagekit-plugins/libpk_plugin-check-shared-libraries-in-use.so: checks for any shared libraries in use after a security update11:12:57        PackageKit          opened plugin /usr/lib/x86_64-linux-gnu/packagekit-plugins/libpk_plugin-scan-desktop-files.so: Scans desktop files on refresh and adds them to a database11:12:57        PackageKit          opened plugin /usr/lib/x86_64-linux-gnu/packagekit-plugins/libpk_plugin-update-check-processes.so: Checks for running processes during update for session restarts11:12:57        PackageKit          opened plugin /usr/lib/x86_64-linux-gnu/packagekit-plugins/libpk_plugin-no-update-process.so: Updates the package lists after refresh11:12:57        PackageKit          opened plugin /usr/lib/x86_64-linux-gnu/packagekit-plugins/libpk_plugin-update-package-cache.so: Maintains a database of all packages for fast read-only access to package information11:12:57        PackageKit          opened plugin /usr/lib/x86_64-linux-gnu/packagekit-plugins/libpk_plugin_scripts.so: Runs external scrips11:12:57        PackageKit          opened plugin /usr/lib/x86_64-linux-gnu/packagekit-plugins/libpk_plugin-require-restart.so: A dummy plugin that doesn't do anything11:12:57        PackageKit          run pk_plugin_initialize on /usr/lib/x86_64-linux-gnu/packagekit-plugins/libpk_plugin-check-shared-libraries-in-use.so11:12:57        PackageKit          finished pk_plugin_initialize11:12:57        PackageKit          run pk_plugin_initialize on /usr/lib/x86_64-linux-gnu/packagekit-plugins/libpk_plugin-scan-desktop-files.so11:12:57        PackageKit          finished pk_plugin_initialize11:12:57        PackageKit          run pk_plugin_initialize on /usr/lib/x86_64-linux-gnu/packagekit-plugins/libpk_plugin-update-check-processes.so11:12:57        PackageKit          finished pk_plugin_initialize11:12:57        PackageKit          run pk_plugin_initialize on /usr/lib/x86_64-linux-gnu/packagekit-plugins/libpk_plugin-no-update-process.so11:12:57        PackageKit          finished pk_plugin_initialize11:12:57        PackageKit          run pk_plugin_initialize on /usr/lib/x86_64-linux-gnu/packagekit-plugins/libpk_plugin-update-package-cache.so11:12:57        PackageKit          finished pk_plugin_initialize11:12:57        PackageKit          run pk_plugin_initialize on /usr/lib/x86_64-linux-gnu/packagekit-plugins/libpk_plugin-require-restart.so11:12:57        PackageKit          finished pk_plugin_initialize11:12:57        PackageKit          Trying to load : aptcc11:12:57        PackageKit          dlopening '/usr/lib/x86_64-linux-gnu/packagekit-backend/libpk_backend_aptcc.so'Failed to load the backend: opening module aptcc failed : /usr/lib/x86_64-linux-gnu/packagekit-backend/libpk_backend_aptcc.so: undefined symbol: _ZN13pkgTagSectionC1Ev11:12:57 PackageKit          run pk_plugin_destroy on /usr/lib/x86_64-linux-gnu/packagekit-plugins/libpk_plugin-check-shared-libraries-in-use.so11:12:57        PackageKit          finished pk_plugin_destroy11:12:57        PackageKit          run pk_plugin_destroy on /usr/lib/x86_64-linux-gnu/packagekit-plugins/libpk_plugin-scan-desktop-files.so11:12:57        PackageKit          finished pk_plugin_destroy11:12:57        PackageKit          run pk_plugin_destroy on /usr/lib/x86_64-linux-gnu/packagekit-plugins/libpk_plugin-update-check-processes.so11:12:57        PackageKit          finished pk_plugin_destroy11:12:57        PackageKit          run pk_plugin_destroy on /usr/lib/x86_64-linux-gnu/packagekit-plugins/libpk_plugin-no-update-process.so11:12:57        PackageKit          finished pk_plugin_destroy11:12:57        PackageKit          run pk_plugin_destroy on /usr/lib/x86_64-linux-gnu/packagekit-plugins/libpk_plugin-update-package-cache.so11:12:57        PackageKit          finished pk_plugin_destroy11:12:57        PackageKit          run pk_plugin_destroy on /usr/lib/x86_64-linux-gnu/packagekit-plugins/libpk_plugin-require-restart.so11:12:57        PackageKit          finished pk_plugin_destroy11:12:57        PackageKit          already closed (nonfatal)11:12:57        PackageKit          parent_class->finalizeHooooOOoo... What about Aptitude ?% aptitudeaptitude: symbol lookup error: aptitude: undefined symbol: _ZN3APT11CacheFilter39PackageArchitectureMatchesSpecificationC1ERKSsbSolution The problem was that somehow, I get a bad version of libapt-pkg4.12. So anything related to apt in some way had a chance to end badly.Reinstalling the correct version of them (the one provided with my distribution) corrected all the problems:sudo apt-get install libapt-pkg4.12=1.1.1bodhi1 apt=1.1.1bodhi1 apt-transport-https=1.1.1bodhi1 apt-utils=1.1.1bodhi1Hope it helps ! [Less]
Posted about 2 years ago by nore...@blogger.com (Fanf)
This last weed-end, I tried to upgrade my old Bodhi Linux 2.4 based on Ubuntu 12.04 LTS to Bodhi 3.0 based on Ubuntu 14.04 LTS.At some point something goes wrong with the update of the 1500 or so packages. I'm not sure about what happenned, but I ... [More] started to see stranges errors, especially when trying to install/remove/correct package, but also in other part, for example when running some Python3 scripts.Finally, everything was looking like working, but just almost working. Google fails on me on that, and I spend quite some time this week-end trying to go to the bottom of that problem, so I let a testimonial here, if it can help other people.SymptomsSegmentation fault (core dumped) with apt-get and python3 related scriptsThis appears especially when trying to install/install -f "update-notifier-common" software, for example (sorry for the French):% sudo apt-get install -fLecture des listes de paquets... FaitConstruction de l'arbre des dépendances       Lecture des informations d'état... Fait0 mis à jour, 0 nouvellement installés, 0 à enlever et 0 non mis à jour.1 partiellement installés ou enlevés.Après cette opération, 0 o d'espace disque supplémentaires seront utilisés.Paramétrage de update-notifier-common (0.154.1) ...Segmentation fault (core dumped)dpkg: error processing package update-notifier-common (--configure): le sous-processus script post-installation installé a retourné une erreur de sortie d'état 139Des erreurs ont été rencontrées pendant l'exécution : update-notifier-commonError: Timeout was reachedE: Sub-process /usr/bin/dpkg returned an error code (1)The other aspect of that problem was that any Python3 related errors lead to a stack trace like that:% python3Python 3.4.0 (default, Apr 11 2014, 13:05:11) [GCC 4.8.2] on linuxType "help", "copyright", "credits" or "license" for more information.>>> foo                                                                                                                                                                                                      Traceback (most recent call last):  File "Error: Timeout was reachedThe second main symptom was that when using apt-* tools, I was getting an error message "Error: Timeout was reached" just at the end of the process. Nonetheless, everything seemed to be correctly installed/removed/etc. Bug tracking, short versionThat led me to some bug about a timeout to short for packagekit:/usr/bin/test -e /usr/share/dbus-1/system-services/org.freedesktop.PackageKit.service && /usr/bin/test -S /var/run/dbus/system_bus_socket && /usr/bin/gdbus call --system --dest org.freedesktop.PackageKit --object-path /org/freedesktop/PackageKit --timeout 4 --method org.freedesktop.PackageKit.StateHasChanged cache-updateSo I tested with a really big number, and got:/usr/bin/gdbus call --system --dest org.freedesktop.PackageKit --object-path /org/freedesktop/PackageKit --timeout 300 --method org.freedesktop.PackageKit.StateHasChanged cache-updateError: GDBus.Error:org.freedesktop.DBus.Error.TimedOut: Activation of org.freedesktop.PackageKit timed outWhat lead to testing packagkit itself:% sudo /usr/lib/packagekit/packagekitd --verbose11:12:57        PackageKit          Verbose debugging enabled (on console 1)11:12:57        PackageKit          keep_environment: 011:12:57        PackageKit          using config file '/etc/PackageKit/PackageKit.conf'11:12:57        PackageKit          syslog fucntionality disabled11:12:57        PackageKit          Log all transactions: 111:12:57        PackageKit          daemon shutdown set to 300 seconds11:12:57        PackageKit          clearing download cache at /var/cache/PackageKit/downloads11:12:57        PackageKit          destination eth0 is valid11:12:57        PackageKit          setting config file watch on /etc/PackageKit/PackageKit.conf11:12:57        PackageKit          ProxyHTTP read error: Key file does not have key 'ProxyHTTP'11:12:57        PackageKit          searching for plugins in /usr/lib/x86_64-linux-gnu/packagekit-plugins11:12:57        PackageKit          opened plugin /usr/lib/x86_64-linux-gnu/packagekit-plugins/libpk_plugin-systemd-updates.so: A plugin to write the prepared-updates file11:12:57        PackageKit          opened plugin /usr/lib/x86_64-linux-gnu/packagekit-plugins/libpk_plugin-clear-firmware-requests.so: Clears firmware requests11:12:57        PackageKit          opened plugin /usr/lib/x86_64-linux-gnu/packagekit-plugins/libpk_plugin-check-shared-libraries-in-use.so: checks for any shared libraries in use after a security update11:12:57        PackageKit          opened plugin /usr/lib/x86_64-linux-gnu/packagekit-plugins/libpk_plugin-scan-desktop-files.so: Scans desktop files on refresh and adds them to a database11:12:57        PackageKit          opened plugin /usr/lib/x86_64-linux-gnu/packagekit-plugins/libpk_plugin-update-check-processes.so: Checks for running processes during update for session restarts11:12:57        PackageKit          opened plugin /usr/lib/x86_64-linux-gnu/packagekit-plugins/libpk_plugin-no-update-process.so: Updates the package lists after refresh11:12:57        PackageKit          opened plugin /usr/lib/x86_64-linux-gnu/packagekit-plugins/libpk_plugin-update-package-cache.so: Maintains a database of all packages for fast read-only access to package information11:12:57        PackageKit          opened plugin /usr/lib/x86_64-linux-gnu/packagekit-plugins/libpk_plugin_scripts.so: Runs external scrips11:12:57        PackageKit          opened plugin /usr/lib/x86_64-linux-gnu/packagekit-plugins/libpk_plugin-require-restart.so: A dummy plugin that doesn't do anything11:12:57        PackageKit          run pk_plugin_initialize on /usr/lib/x86_64-linux-gnu/packagekit-plugins/libpk_plugin-check-shared-libraries-in-use.so11:12:57        PackageKit          finished pk_plugin_initialize11:12:57        PackageKit          run pk_plugin_initialize on /usr/lib/x86_64-linux-gnu/packagekit-plugins/libpk_plugin-scan-desktop-files.so11:12:57        PackageKit          finished pk_plugin_initialize11:12:57        PackageKit          run pk_plugin_initialize on /usr/lib/x86_64-linux-gnu/packagekit-plugins/libpk_plugin-update-check-processes.so11:12:57        PackageKit          finished pk_plugin_initialize11:12:57        PackageKit          run pk_plugin_initialize on /usr/lib/x86_64-linux-gnu/packagekit-plugins/libpk_plugin-no-update-process.so11:12:57        PackageKit          finished pk_plugin_initialize11:12:57        PackageKit          run pk_plugin_initialize on /usr/lib/x86_64-linux-gnu/packagekit-plugins/libpk_plugin-update-package-cache.so11:12:57        PackageKit          finished pk_plugin_initialize11:12:57        PackageKit          run pk_plugin_initialize on /usr/lib/x86_64-linux-gnu/packagekit-plugins/libpk_plugin-require-restart.so11:12:57        PackageKit          finished pk_plugin_initialize11:12:57        PackageKit          Trying to load : aptcc11:12:57        PackageKit          dlopening '/usr/lib/x86_64-linux-gnu/packagekit-backend/libpk_backend_aptcc.so'Failed to load the backend: opening module aptcc failed : /usr/lib/x86_64-linux-gnu/packagekit-backend/libpk_backend_aptcc.so: undefined symbol: _ZN13pkgTagSectionC1Ev11:12:57 PackageKit          run pk_plugin_destroy on /usr/lib/x86_64-linux-gnu/packagekit-plugins/libpk_plugin-check-shared-libraries-in-use.so11:12:57        PackageKit          finished pk_plugin_destroy11:12:57        PackageKit          run pk_plugin_destroy on /usr/lib/x86_64-linux-gnu/packagekit-plugins/libpk_plugin-scan-desktop-files.so11:12:57        PackageKit          finished pk_plugin_destroy11:12:57        PackageKit          run pk_plugin_destroy on /usr/lib/x86_64-linux-gnu/packagekit-plugins/libpk_plugin-update-check-processes.so11:12:57        PackageKit          finished pk_plugin_destroy11:12:57        PackageKit          run pk_plugin_destroy on /usr/lib/x86_64-linux-gnu/packagekit-plugins/libpk_plugin-no-update-process.so11:12:57        PackageKit          finished pk_plugin_destroy11:12:57        PackageKit          run pk_plugin_destroy on /usr/lib/x86_64-linux-gnu/packagekit-plugins/libpk_plugin-update-package-cache.so11:12:57        PackageKit          finished pk_plugin_destroy11:12:57        PackageKit          run pk_plugin_destroy on /usr/lib/x86_64-linux-gnu/packagekit-plugins/libpk_plugin-require-restart.so11:12:57        PackageKit          finished pk_plugin_destroy11:12:57        PackageKit          already closed (nonfatal)11:12:57        PackageKit          parent_class->finalizeHooooOOoo... What about Aptitude ?% aptitudeaptitude: symbol lookup error: aptitude: undefined symbol: _ZN3APT11CacheFilter39PackageArchitectureMatchesSpecificationC1ERKSsbSolution The problem was that somehow, I get a bad version of libapt-pkg4.12. So anything related to apt in some way had a chance to end badly.Reinstalling the correct version of them (the one provided with my distribution) corrected all the problems:sudo apt-get install libapt-pkg4.12=1.1.1bodhi1 apt=1.1.1bodhi1 apt-transport-https=1.1.1bodhi1 apt-utils=1.1.1bodhi1Hope it helps ! [Less]
Posted about 2 years ago by Howard Lewis Ship