Bug#873240: redshift-gtk: redshift doesn't launch either when launching in the console or at start of computer
Package: redshift-gtk Version: 1.11-1 Followup-For: Bug #873240 -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 I've upgraded my packages on Buster, including GLib, and I'm now unable to reproduce this issue. Redshift's GTK+ interface as well as Blueman's is now working well for me. Unless someone is still able to reproduce, we may finally be able to close this bug, though I'm sure the cause will forever remain a mystery. - -- System Information: Debian Release: buster/sid APT prefers testing-debug APT policy: (500, 'testing-debug'), (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 4.15.0-2-amd64 (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages redshift-gtk depends on: ii gir1.2-appindicator3-0.1 0.4.92-5 ii python3 3.6.4-1 ii python3-gi3.26.1-2 ii python3-xdg 0.25-4 ii redshift 1.11-1 Versions of packages redshift-gtk recommends: ii at-spi2-core 2.28.0-1 redshift-gtk suggests no packages. - -- no debconf information -BEGIN PGP SIGNATURE- iQFGBAEBCgAwFiEEJwCMxdBfG24Y2trvfWFEpid5MHIFAlq6weASHGpzY290dEBw b3N0ZW8ubmV0AAoJEH1hRKYneTBy3sgIAJCPjPKQtsjsFLOV1g+091wM7VDTlHQr XR+vHgYFanEmoCu3T7WQKBL+uem4HfKplBu9WQwtyFK0hv4/zHJoc+2k3BFLgFvZ CxXNdQrnPWA+N3IARsuFMKmjOxWP+EicONqZGPgM2G/CRX8OCU9dUQdy6r44fbpC F6iJytcLpz/Wa/CkGXih0QZr29qlKUvGbRviMz49MRdjwj0pgE5deOCD3UzzpA4u 0ENctDYZsHxhYs1h4SHtyOlmVsGsdVMJCmL2pc+CHiXe9mU7hWD26rXVgUNyrEzH QpbnzvwSGr9um4V6ODc7Q9A18I7iYR572jEUrKnNuv2h8Z/TW+aZmz0= =7eKU -END PGP SIGNATURE-
Bug#873240: redshift-gtk: redshift doesn't launch either when launching in the console or at start of computer
On Sun, 2018-02-25 at 18:14 -0500, John Scott wrote: > I don't use the Redshift service, but here is what it says: > > ● redshift.service - Redshift display colour temperature adjustment >Loaded: loaded (/usr/lib/systemd/user/redshift.service; disabled; > vendor preset: enabled) >Active: inactive (dead) > Docs: http://jonls.dk/redshift/ > > Running `redshift` in the terminal works fine for me. > Good to know that redshift is working for you. > You said that you are not experiencing this bug, but are you on > Debian Jessie? No. I tried it on Debian Sid. > I should have > mentioned in my last message that I think this bug is not a bug in > Redshift, but in a dependency, > specific to Sid and Buster. I'm more certain of it now than ever, but > I think the issues I found > with python3-xdg are unrelated. > I am not sure whom this bug should be reassigned to then. > In addition to redshift-gtk, I also have Blueman installed, which > also doesn't show its icon. In > hindsight, I should have thought that the issues might be related > sooner. They are both written in > Python 3 and use gir1.2-appindicator3-0.1. > > In fact, I just ran both Redshift and Blueman through gdb, and I > noticed that a thread crashes > when it tries to display the icon. I'm including my Redshift > backtrace. -- Ritesh Raj Sarraf | http://people.debian.org/~rrs Debian - The Universal Operating System signature.asc Description: This is a digitally signed message part
Bug#873240: redshift-gtk: redshift doesn't launch either when launching in the console or at start of computer
Package: redshift-gtk Version: 1.11-1 Followup-For: Bug #873240 -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 I don't use the Redshift service, but here is what it says: ● redshift.service - Redshift display colour temperature adjustment Loaded: loaded (/usr/lib/systemd/user/redshift.service; disabled; vendor preset: enabled) Active: inactive (dead) Docs: http://jonls.dk/redshift/ Running `redshift` in the terminal works fine for me. You said that you are not experiencing this bug, but are you on Debian Jessie? I should have mentioned in my last message that I think this bug is not a bug in Redshift, but in a dependency, specific to Sid and Buster. I'm more certain of it now than ever, but I think the issues I found with python3-xdg are unrelated. In addition to redshift-gtk, I also have Blueman installed, which also doesn't show its icon. In hindsight, I should have thought that the issues might be related sooner. They are both written in Python 3 and use gir1.2-appindicator3-0.1. In fact, I just ran both Redshift and Blueman through gdb, and I noticed that a thread crashes when it tries to display the icon. I'm including my Redshift backtrace. - -- System Information: Debian Release: buster/sid APT prefers testing-debug APT policy: (500, 'testing-debug'), (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 4.14.0-3-amd64 (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages redshift-gtk depends on: ii gir1.2-appindicator3-0.1 0.4.92-5 ii python3 3.6.4-1 ii python3-gi3.26.1-2 ii python3-xdg 0.25-4 ii redshift 1.11-1 Versions of packages redshift-gtk recommends: ii at-spi2-core 2.26.2-2 redshift-gtk suggests no packages. - -- no debconf information *** /home/john/redshift/backtrace.txt #0 0x76d50e6b in __GI___poll (fds=0xe75950, nfds=5, timeout=14506) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x75f4b119 in g_main_context_poll (priority=, n_fds=5, fds=0xe75950, timeout=, context=0xca7c10) at ../../../../glib/gmain.c:4169 #2 0x75f4b119 in g_main_context_iterate (context=0xca7c10, block=block@entry=1, dispatch=dispatch@entry=1, self=) at ../../../../glib/gmain.c:3863 #3 0x75f4b4b2 in g_main_loop_run (loop=0xbde6e0) at ../../../../glib/gmain.c:4064 #4 0x7fffeedcbff5 in gtk_main () at ../../../../gtk/gtkmain.c:1323 #5 0x75cfcfce in ffi_call_unix64 () at ../src/x86/unix64.S:76 #6 0x75cfc93f in ffi_call (cif=cif@entry=0xe9c738, fn=, rvalue=, rvalue@entry=0x7fffd898, avalue=) at ../src/x86/ffi64.c:525 #7 0x766fadda in pygi_invoke_c_callable (function_cache=0xe9c690, state=, py_args=, py_kwargs=) at ../../gi/pygi-invoke.c:682 #8 0x766fc9b8 in pygi_function_cache_invoke (function_cache=, py_args=, py_kwargs=) at ../../gi/pygi-cache.c:863 #9 0x0045a0d3 in _PyObject_FastCallDict (func=, args=0xacc680, nargs=0, kwargs=0x0) at ../Objects/abstract.c:2331 #10 0x0054fc17 in call_function (pp_stack=pp_stack@entry=0x7fffda88, oparg=, kwnames=kwnames@entry=0x0) at ../Python/ceval.c:4848 #11 0x005545af in _PyEval_EvalFrameDefault (f=, throwflag=) at ../Python/ceval.c:3322 #12 0x0054fac1 in PyEval_EvalFrameEx (throwflag=0, f=Frame 0xacc4e8, for file /usr/lib/python3/dist-packages/redshift_gtk/statusicon.py, line 524, in run (terminate_child=, s=, _error_buffer= , _errors="Trying location provider `geoclue2'...\n") at remote 0x7fffeacb5bd0>, indicator=, status_menu=, toggle_item=, info_dialog=, status_label=, location_label=, temperature_label=, period_label=, suspend_timer=None) at remote 0x7fffeac95f98>)) at ../Python/ceval.c:753 #13 0x0054fac1 in _PyEval_EvalCodeWithName (_co=, globals=globals@entry={'__name__': 'redshift_gtk.statusicon', '__doc__': "GUI status icon for Redshift.\n\nThe run method will try to start an appindicator for Redshift. If the\nappindicator module isn't present it will fall back to a GTK status icon.\n", '__package__': 'redshift_gtk', '__loader__': , '__spec__': , origin='/usr/lib/python3/dist-packages/redshift_gtk/statusicon.py', loader_state=None, submodule_search_locations=None, _set_fileattr=True,
Bug#873240: redshift-gtk: redshift doesn't launch either when launching in the console or at start of computer
I just tried out redshift on my GNOME box and it is working fine. Lately, the way redshift works has changed slightly. What is the output of: systemctl --user status redshift rrs@chutzpah:~$ systemctl --user status redshift ● redshift.service - Redshift display colour temperature adjustment Loaded: loaded (/usr/lib/systemd/user/redshift.service; enabled; vendor preset: enab Active: active (running) since Sun 2018-02-25 10:49:56 IST; 3min 47s ago Docs: http://jonls.dk/redshift/ Main PID: 18964 (redshift) CGroup: /user.slice/user-1000.slice/user@1000.service/redshift.service └─18964 /usr/bin/redshift Feb 25 10:49:56 chutzpah systemd[13641]: Started Redshift display colour temperature ad Feb 25 10:49:56 chutzpah redshift[18964]: Trying location provider `geoclue2'... Feb 25 10:49:56 chutzpah redshift[18964]: Using provider `geoclue2'. Feb 25 10:50:02 chutzpah redshift[18964]: Using method `randr'. The gtk icon doesn't show up in GNOME but that is a different issue altogether. You should be able to see the icon on other desktops that use LibAppIndicator. Please keep in mind that redshift needs geoclue2 support. Without it, it wouldn't function properly unless you explicitly provide the location details to it. rrs@chutzpah:/usr/share/doc/redshift$ redshift -l list Available location providers: geoclue2 manual Specify colon-separated options with`-l PROVIDER:OPTIONS'. Try `-l PROVIDER:help' for help. 10:57 ♒♒♒ ☺ On Sat, 2018-02-24 at 10:06 -0500, John Scott wrote: > Package: redshift-gtk > Version: 1.11-1 > Followup-For: Bug #873240 > > I felt that it was justified since redshift-gtk is unusable, though I > respect > your decision going forward. I don't think this is specific to any > particular desktop environment. I am having the same issue on MATE, > and the > submitter of the bug I merged into this one said that this bug also > applied to > Xfce. I concede that I don't know a lot about Python packaging, but I > had > thought that the Python errors could have explained the issue. This > is > displayed when it tries to import some modules from python3-xdg: > > import 'xdg.BaseDirectory' # > <_frozen_importlib_external.SourceFileLoader object at > 0x7f697d5abda0> > # code object from /usr/lib/python3/dist-packages/xdg/DesktopEntry.py > # could not create '/usr/lib/python3/dist-packages/xdg/__pycache__': > PermissionError(13, 'Permission denied') > > I attempted to run redshift-gtk as root (I know it's not a good > idea), and > running it as root in MATE does work and show in the tray. That is > why I thought > escalating this issue was justified, since I thought this seemed like > an > issue not specific to a desktop environment, but to Python or > Redshift, like above. > > For me, most packages in /usr/lib/python3/dist-packages/ do have a > __pycache__ > directory, but xdg seems to be an exception. pyxdg hasn't been built > since 2014, so > could it be that it just needs to be rebuilt? > > I tried to rebuild it to investigate it further, but one of the tests > in pyxdg, > test_validate_icon_theme, fails, with "Invalid key: Scale", which > keeps me from > building the package. > > Sorry for the trouble and confusion I caused earlier. > > > -- System Information: > Debian Release: buster/sid > APT prefers testing-debug > APT policy: (500, 'testing-debug'), (500, 'testing') > Architecture: amd64 (x86_64) > > Kernel: Linux 4.14.0-3-amd64 (SMP w/2 CPU cores) > Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), > LANGUAGE=en_US.UTF-8 (charmap=UTF-8) > Shell: /bin/sh linked to /bin/dash > Init: systemd (via /run/systemd/system) > LSM: AppArmor: enabled > > Versions of packages redshift-gtk depends on: > ii gir1.2-appindicator3-0.1 0.4.92-5 > ii python3 3.6.4-1 > ii python3-gi3.26.1-2 > ii python3-xdg 0.25-4 > ii redshift 1.11-1 > > Versions of packages redshift-gtk recommends: > ii at-spi2-core 2.26.2-2 > > redshift-gtk suggests no packages. > > -- no debconf information > -- Ritesh Raj Sarraf | http://people.debian.org/~rrs Debian - The Universal Operating System signature.asc Description: This is a digitally signed message part
Bug#873240: redshift-gtk: redshift doesn't launch either when launching in the console or at start of computer
Package: redshift-gtk Version: 1.11-1 Followup-For: Bug #873240 -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 I felt that it was justified since redshift-gtk is unusable, though I respect your decision going forward. I don't think this is specific to any particular desktop environment. I am having the same issue on MATE, and the submitter of the bug I merged into this one said that this bug also applied to Xfce. I concede that I don't know a lot about Python packaging, but I had thought that the Python errors could have explained the issue. This is displayed when it tries to import some modules from python3-xdg: import 'xdg.BaseDirectory' # <_frozen_importlib_external.SourceFileLoader object at 0x7f697d5abda0> # code object from /usr/lib/python3/dist-packages/xdg/DesktopEntry.py # could not create '/usr/lib/python3/dist-packages/xdg/__pycache__': PermissionError(13, 'Permission denied') I attempted to run redshift-gtk as root (I know it's not a good idea), and running it as root in MATE does work and show in the tray. That is why I thought escalating this issue was justified, since I thought this seemed like an issue not specific to a desktop environment, but to Python or Redshift, like above. For me, most packages in /usr/lib/python3/dist-packages/ do have a __pycache__ directory, but xdg seems to be an exception. pyxdg hasn't been built since 2014, so could it be that it just needs to be rebuilt? I tried to rebuild it to investigate it further, but one of the tests in pyxdg, test_validate_icon_theme, fails, with "Invalid key: Scale", which keeps me from building the package. Sorry for the trouble and confusion I caused earlier. - -- System Information: Debian Release: buster/sid APT prefers testing-debug APT policy: (500, 'testing-debug'), (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 4.14.0-3-amd64 (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages redshift-gtk depends on: ii gir1.2-appindicator3-0.1 0.4.92-5 ii python3 3.6.4-1 ii python3-gi3.26.1-2 ii python3-xdg 0.25-4 ii redshift 1.11-1 Versions of packages redshift-gtk recommends: ii at-spi2-core 2.26.2-2 redshift-gtk suggests no packages. - -- no debconf information -BEGIN PGP SIGNATURE- iQFGBAEBCgAwFiEEJwCMxdBfG24Y2trvfWFEpid5MHIFAlqRf4USHGpzY290dEBw b3N0ZW8ubmV0AAoJEH1hRKYneTByd3QH/2M3jfkTY6XbBr2bBNMRy0I+wjX9XvSL 3ArWh5wEH9ricbN8wVUjBkLBIpuXVlFWY/GthHDkH6FEkYw/IWNfn7rJyi/+Gb55 JeEJ96k+ALvTSCM4lii95lTHXoOF51fL6KwcdEhTmSWL3rqdJWyw/4tWT7/HRAct wE+8ePlnfgcHh6n0JDqMnDu03PCM6MYkprtwkrHPcGD95slWTQt938Q7DNDYcKy8 qsu3h/kWTmFXpoH3/e7Ul3gZFjs7J9SVc4Y/soIzvBPt1ineI9CaRdQZlZ4Qx5M8 2kX0DhFOu39qZ1stGI0QtUzM4m8IQk+aI2lK1FA4AbySBMdQE37uhHw= =Mvbc -END PGP SIGNATURE-
Bug#873240: redshift-gtk: redshift doesn't launch either when launching in the console or at start of computer
Package: redshift-gtk Version: 1.11-1 Followup-For: Bug #873240 Hi Paul, Are you running Gnome on wayland? You can check with echo $XDG_SESSION_TYPE Currently, redshift (using xrandr) does not work on wayland. As a workaround, you can can either choose ‘Gnome on X.org’ in GDM or you give Gnome Night Light a try, which is available in Gnome 3.24. Best, Marcel
Bug#873240: redshift-gtk: redshift doesn't launch either when launching in the console or at start of computer
Package: redshift-gtk Version: 1.11-1 Severity: important Dear Maintainer, *** Reporter, please consider answering these questions, where appropriate *** * What led up to the situation? just installing the package and try to launch it * What exactly did you do (or not do) that was effective (or ineffective)? try to launch it in th terminal * What was the outcome of this action? The redshift command was just executing without doing nothing * What outcome did you expect instead? Launching of redshift program *** End of the template - remove these template lines *** -- System Information: Debian Release: buster/sid APT prefers testing APT policy: (500, 'testing'), (500, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.12.0-1-amd64 (SMP w/4 CPU cores) Locale: LANG=fr_FR.utf8, LC_CTYPE=fr_FR.utf8 (charmap=UTF-8), LANGUAGE=fr_FR.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages redshift-gtk depends on: pn gir1.2-appindicator3-0.1 ii python3 3.5.3-3 ii python3-gi3.22.0-2+b1 ii python3-xdg 0.25-4 ii redshift 1.11-1 Versions of packages redshift-gtk recommends: ii at-spi2-core 2.24.1-1 redshift-gtk suggests no packages.