Bug#817059: vagrant: domain_name gem not found
Package: vagrant Version: 1.8.1+dfsg-1 Severity: grave Justification: renders package unusable -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Dear Maintainer, Until #817011 on ruby-domain-name is fixed by the maintainer, vagrant does not work without a manual fix (gemspec file) available in the bts report.[1] See below. I'm reporting this against your package for the benefit of others, especially those using virtualbox from sid. Guy Hughes [1]: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=817011 $ vagrant Vagrant experienced a version conflict with some installed plugins! This usually happens if you recently upgraded Vagrant. As part of the upgrade process, some existing plugins are no longer compatible with this version of Vagrant. The recommended way to fix this is to remove your existing plugins and reinstall them one-by-one. To remove all plugins: rm -r ~/.vagrant.d/plugins.json ~/.vagrant.d/gems Note if you have an alternate VAGRANT_HOME environmental variable set, the folders above will be in that directory rather than your user's home directory. The error message is shown below: Bundler could not find compatible versions for gem "domain_name": In Gemfile: vagrant (= 1.8.1) was resolved to 1.8.1, which depends on rest-client (< 2.0, >= 1.6.0) was resolved to 1.8.0, which depends on http-cookie (< 2.0, >= 1.0.2) was resolved to 1.0.2, which depends on domain_name (~> 0.5) Could not find gem 'domain_name (~> 0.5)', which is required by gem 'http-cookie (< 2.0, >= 1.0.2)', in any of the sources. -BEGIN PGP SIGNATURE- iQIcBAEBCgAGBQJW3bWUAAoJEP5VHtX/6ko8rYIP/1IsuCxSQUi5ifmyxaxxhN3j Hk+fa73j/nAWXPI/in4lky+heiWwbstvgvoir5zK9fftQAv58q6h/d1ExIvsqHei ZfNdVJKFE0DYSCxjJYS6a33xof7/WhuhoE33kThuvbuinwnMOh4i5XN+x3Pr9KPx mD7zBUDhbiEsbLYFguo1rpz6b05bkJD+NLbhgVSQ0z1G54AQPze9ZUfAqRmtgkWW wU6p67zDWSn0E1NyRUPDOo8al7bXaqZ++D6B70Psk+7yxxaZF3HzqjSZUDRcgjMK 8f+4e4lQHccFJSAvdz0RRXMWUm+egVDpRSex71he4Z14g6MDoPUsodU3gvI4ns5M sLrL2+q8r/UeDaVNEsJSQY1Igot+jQt0e8P1gsOxbaCM//SoW+1dqa9Hfza9HfQX 2D4TAXAamdxWvzBdViKCp4+8Dj4MfFBMrtyT3vWaJ/C80X5GyEQDNb9TEL2Owvvv zxbG4i4D/bqLMFrEBB59q4u3V9XCFjh069fIMHVkgU60Lu3kVIZFQyhNUVlRtmfL SOHoJfp1OQJEBH+ZPY/wx06BgR0xDKmz2cSf2C8heHkMberBrOvKrawHhIa4gqB+ iBhPAoMMzpaUThZkBMPAD8XvdhkkA1mxnB5zNbVLT+O/tBk7xF5YqlV5QYqLJBsj PO0cwls0qMxPJftBuOr1 =7KLp -END PGP SIGNATURE-
Bug#813706: trash-cli: restore-trash v. trash-restore, manpages
Package: trash-cli
Version: 0.12.9.14-2
Severity: minor
Tags: upstream
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Dear Maintainers,
I noticed that the manpage refers to 'trash-restore (1)' where it ought
to refer to 'restore-trash (1)'. I noticed debian/trash-cli.links[1],
however:
$ man -w trash-restore
No manual entry for trash-restore
$ man -w restore-trash
/usr/share/man/man1/restore-trash.1.gz
The same conflict occurs with the command.
$ trash-restore
bash: trash-restore: command not found
$ restore-trash
No files trashed from current dir ('/share/share/man/man1')
Meanwhile, upstream has moved to `trash-restore` [2].
Is it possible to provide both or at least update the documentation?
Thank you for your work,
Guy Hughes
[1]:
https://anonscm.debian.org/cgit/collab-maint/trash-cli.git/tree/debian/trash-cli.links
[2]: https://github.com/andreafrancia/trash-cli/issues/20
-BEGIN PGP SIGNATURE-
iQIcBAEBCgAGBQJWs2q1AAoJEP5VHtX/6ko8txsQAIgmk2KWs6nLLAECLOKSDIUM
ejbxfD3x9Jv9zH8B/s4lkDxpgiMHGpRuSrrMIIql9XX5chzk4vhH2JVTEl3GGcmL
r8N3rBBszCxPLh5F8oXjNevE4ucdCxvxonSWFewO1PRz1RoYnbvL1IsCRV5cV3qM
lI4COYIh8V6oSGzWbZI/SfcUQCx9cwKPmOlVOIg9Sv4upmHLm6vOUbyjRsimFXvY
rlJ47xxZrVscRBDJxNLZkzFYel2fCQB+Q1BUQUxsIOVPxnqcojG+sIMe/g/iggQi
G8K3yfP04dSCtIU+G411a0P+KMirjNqQRyl52JxkvmF9GYZquNRk6u3rO6dZHfjU
36iOofE9wuVpetgR++x3xKiywnAIuy9kTCTGcJK6R70JZJHjiU+DfFcMzcwBntAY
L+fZCAGCZOTnUG6wfyspEREOashLquzvK+o/55b9ozIMVg5S/t31YMe33VT39qlB
W4TQBjwBwP+jm8O7Hq+2w4f/oVlzp46KX9HyevbJ/Czn6/TEHEtgSqDMApUe+d8O
PTgcNReHmAeypAUrvpsEubkttNromhFCz0LWLq3xlcdjxZGKHM5QC8xJLtVoT8ND
jZ5cK2fAzU+MscBNjGTEW+tq+TOHI/EV6fVj+4WpTFxRikSbUFTzw4PfXsTI9udf
Z+/fHy3pt+VJOsuHdEWo
=GrwH
-END PGP SIGNATURE-
-- System Information:
Debian Release: sid
Architecture: amd64 (x86_64)
Versions of packages trash-cli depends on:
ii python2.7.11-1
ii python-pkg-resources 18.8-1
trash-cli recommends no packages.
trash-cli suggests no packages.
-- no debconf information
Bug#808187: lastpass-cli: new upstream version packaged
Package: lastpass-cli Version: 0.7.0 Severity: normal Tags: patch -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Hi Troy, Upstream tagged 0.7.0 in November and I have packaged it for debian using gbp. [1] The tags are signed. And I have added a watch file. Lintian reports clear. I'd be happy to support any effort to get this new version accepted into the Debian archive. Regards, Guy Hughes [1]: https://github.com/guyhughes/lastpass-cli-debian -BEGIN PGP SIGNATURE- iQIcBAEBCgAGBQJWcejdAAoJEP5VHtX/6ko8rxMP/29xMBpK7TnXDoV2XDZEoNlf kWSjwb1uzpn4EkJd5h7z9+6wP3IlEbnay/2MhtXduMJ+QkIr99xKk3wdmz/X/VUd mc2wpStDMnZeaQrik1RhAlxfic9ILi1XPplfdzApBAn375HosVlzWW4Yx7BrcQFM AEFpyExPhWvFvRGoTkGhjnMqGIZe71oEDRv3eob3bQZu+NzwgcovTGWgyQcJSmIz nG6JwPs6HR39vwUb99U1JTEOT1bFyATVp5H7dngiOEOZTxHf+91hQrkcY5Mf+N3g /QkEyTSIG4HDGwhLtIssLJLqzGX/y07PURaPSEf5gFUdLDYm6oGLg0HRuW24IvAI kZIUQMKmYW+RyYqk+xEFVJvKkzPO+UkFhWYdk6r8zZTCbTqpwTXLlusQWYIUoOzN HlgToXl74GTlCunn3N9aaMPs3OzTmp49QwKwpmi2iXhzFQkn8+r50jg6QawVEQBC HhMTuqMoPvaT4CVZX/n44Wmqdomw1kkoiqEltj3Z3L9PE/lSPj8gCE4oSoKzy9j8 Se4hW33P8xEQaYWHVJsC4sfKcPcn/eGLIdgSTY61CoGg2RsLp3moBBxhoxBMUkAs T8E52DEmSUKE/S5wXl7Z5K6wMzR8rwPLDmazv0f9HSEGMPKtoxkZVtJXpDq1GKCH jUzMnG7il5La3I/CA8Hn =+cY1 -END PGP SIGNATURE-
Bug#807510: tmuxinator: Upstream fix packaging available
Package: tmuxinator Followup-For: Bug #807510 -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 NotDashEscaped: You need GnuPG to verify this message Dear Maintainer, I've packaged the upstream fixes from upstream/master/HEAD 57ef604245d5c9add490b872fc17d8d0cb1918c9. https://github.com/guyhughes/tmuxinator/tree/guy/0.7.0a-0.1 I've tested and this does resolve the bug in 0.7.0. Guy Hughes -- System Information: Debian Release: stretch/sid APT prefers testing APT policy: (550, 'testing'), (502, 'testing'), (502, 'stable'), (500, 'stable-updates'), (500, 'stable'), (99, 'unstable'), (10, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.2.0-1-amd64 (SMP w/4 CPU cores) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages tmuxinator depends on: ii ruby1:2.2.3 ii ruby-erubis 2.7.0-3 ii ruby-thor 0.19.1-2 ii ruby2.1 [ruby-interpreter] 2.1.5-4 ii ruby2.2 [ruby-interpreter] 2.2.3-2 ii tmux2.1-3 tmuxinator recommends no packages. tmuxinator suggests no packages. -- no debconf information -BEGIN PGP SIGNATURE- iQIcBAEBCgAGBQJWamSyAAoJEP5VHtX/6ko8RLQQAMyx83jSaox4UCQy7Sk/CC9Y M5zdMYYCmWvDK513DkPQorggW6lFHVDYrQSP1EUn+8h5DeS50BtftV8CZJ/kV3oj 0lx6ZzSnw30/V9CJNLeRJVo8LPT/jYgRzGBhhkT7Goi/UjtBpPz0lcjGbTxGuzJ9 zpf3/7I5Vh9ECnyVfpHtTvc206ZMxpx1ySUVBlwYX8cVdkyKUiFU2WUHtDoopLHk uFqjv03B/xy86F1xB3yTyyElhXhQIveaJRFowHyxW3rcjBsOt0s8a39gcijot9DL nLUGcRNPdZeh0SUBbfq2cuSSDlpoPu1kXczUycvSHjRKAVw4A5no/yNO3cJtwwvG pEvCf0owXCNbYbIknHSuH5xad+zcTXWQFnNPCpDiqUVGZh2JMcasNTTbMKcXeY7n vHBjNDVJuCbYxPV1W9aL1/zztFwTz15WJpFhjzHbBi4u0L7ik/7LfF2uyCJTvKGQ oOqgpW6EU4b19FzfILnt8nmyneQ23/Xtrz9ifY2vrDbLLmTEOtHg/SZU/rb3SU+1 tAdZ3hsnnnm6b+dyIs/ag/ZytEyO7X1eyC63hcX1ewkpcCobZ3znVw2JPQj/Zi8J D4YG8LXWXors8oSP75mH3V4NzmzgrNud/GsbgN0HPE79WyiT021bn/FuZiRjOJ9V n8533nWRKSOHFSeq8QVn =2Iwn -END PGP SIGNATURE-
Bug#807510: tmuxinator: Upstream fix packaging available
Package: tmuxinator Followup-For: Bug #807510 -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 NotDashEscaped: You need GnuPG to verify this message Dear Maintainer, I've packaged the upstream fixes from upstream/master/HEAD 57ef604245d5c9add490b872fc17d8d0cb1918c9. https://github.com/guyhughes/tmuxinator/tree/guy/0.7.0a-0.1 I've tested and this does resolve the issue. Guy Hughes -- System Information: Debian Release: stretch/sid APT prefers testing APT policy: (550, 'testing'), (502, 'testing'), (502, 'stable'), (500, 'stable-updates'), (500, 'stable'), (99, 'unstable'), (10, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.2.0-1-amd64 (SMP w/4 CPU cores) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages tmuxinator depends on: ii ruby1:2.2.3 ii ruby-erubis 2.7.0-3 ii ruby-thor 0.19.1-2 ii ruby2.1 [ruby-interpreter] 2.1.5-4 ii ruby2.2 [ruby-interpreter] 2.2.3-2 ii tmux2.1-3 tmuxinator recommends no packages. tmuxinator suggests no packages. -- no debconf information -BEGIN PGP SIGNATURE- iQIcBAEBCgAGBQJWamXhAAoJEP5VHtX/6ko8Qp0QANBJeFMo2dxeo+TPp1AVcbNt oaenthdVYuI3A/dZr9GxJQg6dfg7VvJOLldhVD6gPc5JTDzU9+6pZh/+OwFlDhoH VSuMOgXyHwbVwjQOsBtzKILoF7PpNIrGJILTprcFuSkQEwM4XdELyeh+qVerXsRU nSrk226w+NB2iPtsn4QCwxIchA8wJms7xcrt6Gwjo54TJ5lXt4xeVmyHRWeGBQLx haN4DkciGpd1BmnOLnemj56TIKWZloqO1xtLI7v6RQC67zpKUx7f11tl1apCGblt Qu9tN9odaOm0ZFyONqlpTfkPkVuL6JblIHuTdtDIOOjh5AcEhNqAyWidw1Y3VzoJ c/11Sv4e9gaEAO98Dgi72ecV5SEU9AKmCkfH+/fio32WjMzu1JjReEsyOy4hhUy6 tB9LUOLappmVGnA8xqalHgSoYMwJxWWeeot0QoAjGp/ZObxQ1VaoABoXVtWaOHp2 fCEchEPANGfCR5uK9Y6h8hjt3SY6mRr3YiGSbfX9KvRmpvW6Z2ryesCJTmUA6Dfc oAwOyMl2TlBKjm1dGCU3xkXkpyo2FbDSQYq8gHAIceQQLbPG2GZ5XexETfrZSi2Z qvD4qTESiAYVkIh0pezwjY1RtPTrFmFHl5mhBAiB5oaWoEZruJnrFxrSdSskdCcL yczvb9P1AJYy/M3kUt86 =g1y1 -END PGP SIGNATURE-
Bug#807510: tmuxinator: Open deletes project, upstream #358
Package: tmuxinator Version: 0.7.0-1 Severity: important Tags: upstream Dear Maintainer, When I packaged 0.7.0, I did not realize that the release was affected by upstream #358 [1]. `tmuxinator open projectx` recreates the project file, resetting it as if `tmuxinator new projectx` was executed. An upstream fix is available and I will package it today and send it to Youhei Sasaki for consideration. NB: 0.7.0 is still the latest upstream tagged release. Guy Hughes [1]: https://github.com/tmuxinator/tmuxinator/pull/358 -- System Information: Debian Release: stretch/sid APT prefers testing APT policy: (550, 'testing'), (502, 'testing'), (502, 'stable'), (500, 'stable-updates'), (500, 'stable'), (99, 'unstable'), (10, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.2.0-1-amd64 (SMP w/4 CPU cores) Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages tmuxinator depends on: ii ruby1:2.2.3 ii ruby-erubis 2.7.0-3 ii ruby-thor 0.19.1-2 ii ruby2.1 [ruby-interpreter] 2.1.5-4 ii ruby2.2 [ruby-interpreter] 2.2.3-2 ii tmux2.1-3 tmuxinator recommends no packages. tmuxinator suggests no packages. -- no debconf information
Bug#803994: rofi: segfaults on -show window (upstream#256)
Package: rofi Version: 0.15.10-1 Severity: grave Tags: upstream Justification: renders package unusable -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 NotDashEscaped: You need GnuPG to verify this message Dear Maintainer, It may be of note that upstream release 0.15.10 has serious bugs: * https://github.com/DaveDavenport/rofi/issues/256 (confirmed) * https://github.com/DaveDavenport/rofi/issues/258 (possible duplicate) A complete upstream patch is not available. * What led up to the situation? `rofi -show window` or `rofi -key-run alt+r` * What was the outcome of this action? (process:30936): GLib-CRITICAL **: g_strchug: assertion 'string != NULL' failed (process:30936): GLib-CRITICAL **: g_strchomp: assertion 'string != NULL' failed zsh: segmentation fault (core dumped) rofi -show window Thanks, Guy Hughes -- System Information: Debian Release: stretch/sid APT prefers testing APT policy: (550, 'testing'), (502, 'testing'), (502, 'stable'), (500, 'stable-updates'), (500, 'stable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.2.0-1-amd64 (SMP w/4 CPU cores) Locale: LANG=en_CA.UTF-8, LC_CTYPE=en_CA.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages rofi depends on: ii libc6 2.19-22 ii libcairo2 1.14.2-2 ii libglib2.0-0 2.46.1-1 ii libpango-1.0-01.38.1-1 ii libpangocairo-1.0-0 1.38.1-1 ii libstartup-notification0 0.12-4 ii libx11-6 2:1.6.3-1 ii libxinerama1 2:1.1.3-1+b1 rofi recommends no packages. rofi suggests no packages. -- no debconf information -BEGIN PGP SIGNATURE- iQIcBAEBCgAGBQJWOWURAAoJEP5VHtX/6ko8i0cP/RIM17SswYExfvQrT6IYRlBi 1qPZUeoK5SuPUeXKB8KtTJn7mr3DHEO/m46RuTe+hcytzakXoUAQ9DD0IHSisJDz wxo+VZeL7ZCtj5cR9N6SdpzJ+vbafnx3awFXT9nZAqG86A9VqQdl8SrVsTMIVRlv +oNyCj3huEtqYItp8O3X0e/RVTvUELUTrwDdhSraH+imUKSyaQji7hyObjI/MUcn lHD60VYIGuYDtFXmc5RgvCVe82KBhvCp6bYSFiXzGydRSXpvBK1OQ21L1gwZRAmO gBCkX3bh44n9uVtz5IhSOzryO52wM0C43QmJXiogL4gGFpOf93f7wGAfcsElMZp0 quHY0NROBumj6wLxo92SKhXlzY/+ckbOlGjPnoD/eGr7DtPgJLX18Rl0YOlqhhR3 We7IagMiJLnVVoPm3Jmcb1tT4ROEDpVCCi5c2Mp5+10ZSRzb3GKdNR0XKvFYEeDg vAoJn8l5gFaXciYOzig1JJ/8qsEj6DvjsIomrfufhhiFgRSdOtDi1/3P/+YZ9XCd StPKGM6gF7yN83lknActJnp6LGlSWxi799/7LyC5MILPqQrC/lfYm4RSoCHYkJFS C8sBN9m61gWPwfBNLH7VtPteGWcJKT0zjhuO5cJF65nLF4dGFY6VhIhtm4kSuw9N 9Lu76j093bPXQmWjSJ0n =+88R -END PGP SIGNATURE-
Bug#803994: rofi: segfaults on -show window (upstream#256)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
NotDashEscaped: You need GnuPG to verify this message
Hello, wow, you're fast.
On Tue, Nov 03, 2015 at 09:38:04PM -0500, Jason Pleau wrote:
> Hi,
>
> Do you have any rofi settings in $HOME/.Xresources you can provide in
> this bug report?
`rofi -dump-xresources` also segfaults, so:
$ xrdb -query | grep rofi
rofi.bg: #00
rofi.bw: 0
rofi.eh: 2
rofi.fixed-num-lines: true
rofi.font:Cousine 10
rofi.hide-scrollbar: true
rofi.hlbg:#00
rofi.hlfg:#ffb96a
rofi.lines: 3
rofi.opacity: 85
rofi.padding: 700
rofi.terminal:urxvtcd
rofi.width: 100
> What desktop environment and/or window manager are you running rofi with ?
I run bspwm https://github.com/baskerville/bspwm compiled with defaults.
(https://github.com/guyhughes/dots -- includes full .Xresources).
>
> I cannot reproduce #256, but can easily reproduce #258 (with a high
> enough 'padding' in arguments or in .Xresources)
>
> It looks like a patch that attempts to fix #256 was commited:
> https://github.com/DaveDavenport/rofi/commit/f9e7bc0775724a348e14c32437eeaffc255a6ffd
>
> But I cannot test whether or not it fixes the problem since I can't
> reproduce it =/
>
> Are you able to test if the above commit fixes the issue for you ? I can
> provide a temporary patched package if you cannot build rofi yourself.
Sad news. This is the latest commit, failing. Including debugging
symbols.
$ git rev-parse HEAD
d01afc53032b52c07bdf0f77701534305eea
$ which rofi
/usr/local/bin/rofi
$ rofi -show window
(process:1632): GLib-CRITICAL **: g_strchug: assertion 'string != NULL' failed
(process:1632): GLib-CRITICAL **: g_strchomp: assertion 'string != NULL' failed
zsh: segmentation fault rofi -show window
$ ulimit -c unlimited; rofi -show window; echo "thread apply all bt"|gdb rofi
core
(process:7321): GLib-CRITICAL **: g_strchug: assertion 'string != NULL' failed
(process:7321): GLib-CRITICAL **: g_strchomp: assertion 'string != NULL' failed
zsh: segmentation fault (core dumped) rofi -show window
GNU gdb (Debian 7.10-1) 7.10
Copyright (C) 2015 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law. Type "show copying"
and "show warranty" for details.
This GDB was configured as "x86_64-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
<http://www.gnu.org/software/gdb/bugs/>.
Find the GDB manual and other documentation resources online at:
<http://www.gnu.org/software/gdb/documentation/>.
For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from rofi...done.
[New LWP 7321]
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
Core was generated by `rofi -show window'.
Program terminated with signal SIGSEGV, Segmentation fault.
#0 0x0040e53f in color_get (display=display@entry=0x25f69d0,
name=,
defn=defn@entry=0x4136f8 "white") at ../source/x11-helper.c:527
527 if ( strncmp ( cname, "argb:", 5 ) == 0 ) {
(gdb)
Thread 1 (Thread 0x7f5c90fad880 (LWP 7321)):
#0 0x0040e53f in color_get (display=display@entry=0x25f69d0,
name=,
defn=defn@entry=0x4136f8 "white") at ../source/x11-helper.c:527
#1 0x0040a99e in parse_color (display=display@entry=0x25f69d0,
bg=,
col=col@entry=0x61a740 <colors+64>) at ../source/textbox.c:586
#2 0x0040bc19 in textbox_setup (display=0x25f69d0) at
../source/textbox.c:634
#3 0x004072f0 in setup () at ../source/rofi.c:1564
#4 0x00409561 in show_error_message (
---Type to continue, or q to quit---msg=0x26058f0
"The configuration failed to
validate:\n\tconfig.padding+config.menu_bw=700 is to big for
the minimum size of the monitor: 1080.\nPlease update your configuration.",
markup=markup@entry=1)
at ../source/rofi.c:1667
#5 0x0040a877 in config_sanity_check (display=0x25f69d0) at
../source/helper.c:610
#6 0x0040523c in main (argc=, argv=0x7ffdc7cf4388) at
../source/rofi.c:2201
(gdb) quit
>
> As for #258 I have ran a git bisect and updated the bug upstream, I'm
> sure it will help the developer fix it :)
Wow. ♥
>
>
> Thanks for bringing this up !
>
> --
> Jason Pleau
Thanks again,
Guy Hughes
-BEGIN PGP SIGNATURE-
iQIcBAEBCgAGBQJWOXirAAoJEP5VHtX/6ko8XBsQAI53w5EuSBohKD8gA9LgkhcS
0/reDRCoUX2sO+G5EoENpeihGh2fzY4hSJFR32uidl5xIqWLx/YcTh47VLmfLRbZ
HYS6zB27E80/uexAc48RZMbnoyiguxN
