On 24/07/19 22:14, Mathieu Parent wrote:
> Le mer. 24 juil. 2019 à 00:27, Dark Penguin a écrit :
>>
>> On 24/07/19 00:15, Mathieu Parent wrote:
>>> Version: 2:4.9.5+dfsg-5
>>>
>>> I'm closing this bug with the version in buster.
>>>
>&
probe those
interfaces if it wants to bind to all of them, but a negative probing
result is expected, and is not a high-level error.
On 15/07/19 16:36, Mathieu Parent wrote:
> Le dim. 14 juil. 2019 à 14:51, Dark Penguin a écrit :
>>
>> This issue is still present in Buster.
&
te:
> Le dim. 14 juil. 2019 à 15:09, Dark Penguin a écrit :
>>
>> This particular case could be less of a problem (at least to me) if
>> adding "bind interfaces only = yes" was not the only way to disable IPv6
>> in samba.
>>
>> Would it make sense to
This particular case could be less of a problem (at least to me) if
adding "bind interfaces only = yes" was not the only way to disable IPv6
in samba.
Would it make sense to change the priority of an error message on
startup about missing IPv6 support? If samba sees that IPv6 is not
supported on t
This issue is still present in Buster.
Changing the interface name to its IP address in smb.conf does not make
sense because we're talking about a situation when your IP address is
managed by DHCP.
Tweaking the systemd service files does not help according to the OP,
and even if it did, this is n
Package: bilibop-lockfs
Version: 0.5.6
In lockfs mode, if there are any vfat mounts to be protected, they are
ignored and simply mounted as read-write. Everything else is properly
protected with overlayfs.
Isn't it kind of dangerous?.. The user is expecting everything to be safe!
If it is not po
Package: bilibop-lockfs
Version: 0.5.6
Steps to reproduce:
# apt-get install bilibop --no-install-recommends
Now, add a single line to the bottom of /etc/bilibop/bilibop.conf :
BILIBOP_LOCKFS_WHITELIST=/anything
It does not matter if this directory exists or not. Now do an
"update-initramfs -
Package: bilibop-rules
Version: 0.5.6
After installing bilibop, even without enabling lockfs, I see this error
message during the boot process:
---
Begin: Running /scripts/local-bottom ... Warning: bilibop-lockfs:
Nothing to do.
ls: /root/etc/udev/rules.d/70-persistent-cd.rules: No such file or d
Package: bilibop-rules
Version: 0.5.6
During installation AND uninstallation, I see the following error message:
---
Setting up bilibop-rules (0.5.6) ...
dpkg: error: --compare-versions takes three arguments:
Type dpkg --help for help about installing and deinstalling packages [*];
Use 'apt'
Yes, this was a bug in 1.1.2, which was buggy. So I moved to 1.2.0,
which was not in the repo at the time, but without this bug.
--
darkpenguin
The easiest fix for this is changing #!/bin/sh to #!/bin/bash in that
file. And I believe it's the "correct" fix, because the shebang line is
invented specifically to tell you which interpreter to use, so it you
write a script for Bash, you should put Bash there, not Dash or whatever
sh could b
Just came here to ask for better Remmina support. Use it every day, and
use Wheezy and Devuan exclusively. What's the hold up, biggest blocker /
barrier? How can I help?
Apparently, it's just the number of issues in FreeRDP 2.0. Actually, I
understand the reasoning, but I think this is an ex
Have you actually tried either of them? I don't know how many bugs are
in Remmina 1.1.2 and how many in Remmina 1.2.0, but my actual experience
(I use Remmina a lot every day) shows that Remmina 1.1.2 is utterly
broken and barely usable, while 1.2.0 works just fine.
Actually, I notice this kin
I've asked on the systemd mailing lists whether it's possible with
systemd. Maybe this thread could be helpful...
https://lists.freedesktop.org/archives/systemd-devel/2016-September/037447.html
--
darkpenguin
Package: nut
Version: 2.7.2-4
Severity: important
The POWEROFF_WAIT option in nut.conf does not work (has no effect).
I have a suspicion that it has something to do with systemd handling
system shutdowns nowadays, though it's too complex for me to investigate
further and find any proof (other
Package: nut
Version: 2.7.2-4
Severity: important
After an emergency shutdown due to power loss, the command to kill the
power is never sent to the UPS. And since all the machines are powered
down, the load is zero, so this will continue for a pretty long time,
during which power is very like
Package: systemd
Version: 215-17+deb8u4
Severity: normal
I am trying to set up a service shutdown sequence in a way that the
service is asked nicely to quit, and if it doesn't, then it's killed
after a timeout. Sounds very simple - this is very basic.
According to man systemd.service,
Timeo
I did some research. I totally mis-diagnosed the problem earlier; seems
like it's a problem with key translation (or how is it called properly?).
First of all, I've confirmed that this is indeed a problem with upstream
x11vnc. It's present in Linux Mint 18 Cinnamon, it doesn't matter which
VNC
This is one of two bugs with Remmina that really annoy me; after a
while, I've gathered more data and now I think have the simplest way to
reproduce the problem. Also, this time all the machines are running
Debian Jessie with MATE.
- I connect over VNC to one machine with a 1024x768 screen. A
Package: x11vnc
Version: 0.9.13-1.2+b2
Severity: normal
When the local layout is non-English, capital letters (and also "Shift-"
keys) come out lower-case (or "without Shift").
Example:
- I connect to a Debian Jessie machine running x11vnc over MATE (I've
also tried x11vnc on LMDE2 with Cin
I've tried it with relatively recent versions of x11vnc and
tightvncserver on Debian Jessie and Linux Mint. It works. Apparently, it
doesn't work with older versions of various VNC servers on various
operating systems... but I don't think this is something that really
needs to be fixed.
I thi
I've tried it with relatively recent versions of x11vnc and
tightvncserver on Debian Jessie and Linux Mint. It works. Apparently, it
doesn't work with older versions of various VNC servers on various
operating systems - upon closer inspection, it seems that the Alt key
tends to get "stuck" if y
First of all, I mistyped about LMDE: I mean, I'm using MATE on Jessie,
of course.
Now, I've tried to gather more data.
- Click the Remmina tray icon, then quickly (within the double-click
timeout) click one of the items in the context menu: the item is
activated, but the main Remmina window a
Package: remmina
Version: 1.1.1-2
I switch my keyboard layout with Alt+Shift on all my computers. I use
Remmina on MATE on Debian Jessie to connect to other computers - an old
version of tightvncserver on Windows XP, Vino on Debian Squeeze, and
tightvncserver on Debian Wheezy (I'm not sure if
Hi,
you can use reportbug for reporting a bug. Reportbug collect some very
useful informations for the maintainer.
Please run 'reportbug remmina -N 816779' to give me this infos.
And on which operating system and which VNC Server has the error
occurred?
I'm running the client on MATE on Debi
> Hi,
>
> you can use reportbug for reporting a bug. Reportbug collect some very
> useful informations for the maintainer.
>
> Please run 'reportbug remmina -N 816874' to give me this infos.
>
> And on which desktop environment has the error occurred?
I'm using LMDE2 on Debian Jessie.
Here is t
> you can use reportbug for reporting a bug. Reportbug collect some very
> useful informations for the maintainer.
>
> Please run 'reportbug remmina -N 816779' to give me this infos.
>
> And on which operating system and which VNC Server has the error
> occurred?
Hello,
Sorry for the delay - I'
Package: remmina
Version: 1.1.1-2
I have Remmina autostart when I log in, so the Remmina icon sits in the
tray. Whenever I want to connect to some host, I click the tray icon and
the I choose an item from the list of saved hosts.
Now, I only have very few hosts, so those two clicks happen in
Package: remmina
Version: 1.1.1-2
In a VNC connection, Shift+Tab combination just does not get across to
the remote desktop. It does not have any result at all, with or without
"Grab Keyboard" enabled.
Shift+Tab is one of the very basic shortcuts for people who mostly use
keyboard and not mo
I think this situation is a disaster. Not having periodical checks on
your arrays, or rather, having them fail quietly without even notifying
the admin, can lead to grave consequences. (People tend to underestimate
how critical it is to have periodical consistency checks, especially in
RAID5's)
Package: remmina
Version: 1.1.1-2
Even if the "Maintain scale ratio" button is enabled, and this is saved
in the connection, Remmina does not always honor it. This happens in
some cases on window size change, and sometimes even right after connecting.
How to reproduce:
- Connect via VNC to
The next problem is to find the bugtracker for MATE. Unsurprisingly,
googling "bugs mate" yield unwanted and graphic results. %)
--
darkpenguin
And, no, it's not only up to the developers to figure what causes the
bug. Both Mate and Debian are community-driven, so if you find a bug
you would like to get fixed as a user, you should help developers
with some testing which helps locate the issue.
The more information you provide, the faster
When renaming files in Caja, pressing Shift+Del does not "cut the name";
instead, it works as if you wanted to "permanently delete" the file.
Ctrl+X works as expected, however.
Meh, you people are really nitpicky. I would have expected that
Shift+Del will actually delete the file, not cut the te
Package: caja
Version: 1.8.2-3+deb8u1
Severity: normal
Dear Maintainer,
When renaming files in Caja, pressing Shift+Del does not "cut the name";
instead, it works as if you wanted to "permanently delete" the file.
Ctrl+X works as expected, however.
To reproduce:
- Press F2 on any file to ren
35 matches
Mail list logo
