Viestialustana vianhallintajärjestelmät

Is gtk-update-icon-cache now a hard dependency?

17. helmikuuta 2017 klo 20.46
Sijainti: Vianhallintajärjestelmät: Github
Avainsanat: Gnome

Was there a regression or is gtk-update-icon-cache now a hard dependency? I’m getting this in Ubuntu 16.04 (when using the PPA).

The following packages have unmet dependencies:
 gnome-gmail : Depends: gtk-update-icon-cache but it is not installable

Vastaa viestiin sen kontekstissa (Github)

Poorly worded output

12. marraskuuta 2016 klo 17.38
Sijainti: Vianhallintajärjestelmät: kieli
Avainsanat: zync

$ zsync http://cdimage.ubuntu.com/ubuntu-server/daily/current/zesty-server-amd64.iso.zsync
#################### 100.0% 144.7 kBps DONE     

No relevent local data found - I will be downloading the whole file. If that's not what you want, CTRL-C out. You should specify the local file is the old version of the file to download with -i (you might have to decompress it with gzip -d first). Or perhaps you just have no data that helps download the file

What I *think* it’s trying to say is something like: ”No relevant local data was found, and therefore the entire file will be downloaded. If that’s not what you want, use Ctrl-C to abort. If you do have local data, you should specify the location with -i. If the local data is compressed, decompress it first.”

Also, the ”verifying download…checksum matches OK” message (after downloading is finished) could do with capitalization and whitespace: ”Verifying download… Checksum matches OK.”

Vastaa viestiin sen kontekstissa (kieli)

Cannot override Timeout directives in included configuration

29. heinäkuuta 2016 klo 20.30
Sijainti: Vianhallintajärjestelmät: Launchpad
Avainsanat: Proftpd

Redefining TimeoutIdle or TimeoutNoTransfer in a configuration file inside /etc/proftpd/conf.d/, after they’ve already been defined in /etc/proftpd/proftpd.conf, fails to change those values for the daemon — that is, after restarting the daemon, the values for those parameters remain as those set in /etc/proftpd/proftpd.conf.

At least TimeoutIdle or TimeoutNoTransfer are affected. TimeoutSession and TimeoutLogin, which (in stock 16.04) haven’t been defined in the master configuration file can be set effectively, but setting them first in the master file, then again to different values inside conf.d reveals them to be equally affected.

On the other hand, (at least) ServerName *can* be overridden in the custom configuration file, so the handling of different configuration knobs in this regard seems to be inconsistent.

Steps to reproduce:
1. Create a /etc/proftpd/conf.d/proftpd.conf with the following lines:
TimeoutIdle 10
TimeoutNoTransfer 10
2. Restart proftpd
3. Log into the server, wait 11 seconds

What I expect to happen:
To get kicked out of the server.

What happens instead:
I’m allowed to linger on the server, presumably for the 600 seconds defined for TimeoutNoTransfer in /etc/proftpd/proftpd.conf.

Vastaa viestiin sen kontekstissa (Launchpad)

Including a configuration directory includes all files, not just *.conf files

29. heinäkuuta 2016 klo 20.03
Sijainti: Vianhallintajärjestelmät: Launchpad
Avainsanat: Proftpd, Vim

The Include directive, when given a directory as parameter (such as /etc/proftpd/conf.d/, as in the stock /etc/proftpd/proftpd.conf), causes all files in said directory to be read, not just ones ending in .conf. This causes problems if, for instance, I’m using vim to edit a file in the included directory while the proftpd service is being (re)started: vim stores a .swp file in the same directory, and proftpd may fail to start with ”fatal: unknown configuration directive” when it tries to parse the .swp file.

Vastaa viestiin sen kontekstissa (Launchpad)

It’s looking for plymouth and plymouthd in the initrd /bin and /sbin directories

24. heinäkuuta 2016 klo 17.53
Sijainti: Vianhallintajärjestelmät: Launchpad
Avainsanat: Plymouth

Those scripts are ran from the initrd, so it’s looking for plymouth and plymouthd in the initrd /bin and /sbin directories, and those are probably missing the said files just as the error message says.

/usr/share/initramfs-tools/hooks/plymouth is responsible for copying the plymouth executables onto the initrd, so to see why it fails to copy the files, I added `set -x` to it and then ran `update-initramfs -v -u`.

In my case (I’m running Kodibuntu, I recently upgraded the underlying system from 14.04 to 16.04) the issue was that the hook failed to find Kodibuntu theme files for Plymouth, because it was looking for them in /usr/share/plymouth/themes (which apparently is the standard place), whereas the files actually resided in /lib/plymouth/themes for some (legacy?) reason. The hook therefore determined that I have no working Plymouth theme and thus don’t need the executables.

After moving the theme files to /usr/share/plymouth/themes (and some manual labor updating references in the files themselves as well as Plymouth’s alternatives) the hook now correctly finds those files and then proceeds to copy the Plymouth executables onto the initrd.

Vastaa viestiin sen kontekstissa (Launchpad)

Haven’t seen this once since upgrading to 16.04

22. heinäkuuta 2016 klo 16.23
Sijainti: Vianhallintajärjestelmät: Launchpad

Haven’t seen this once since upgrading to 16.04 back in April, so I’m pretty sure the issue has been fixed. Yay!

Vastaa viestiin sen kontekstissa (Launchpad)

Downloading is done via browser

14. huhtikuuta 2016 klo 11.37
Sijainti: Vianhallintajärjestelmät: Github
Avainsanat: saavutettavuus, Slack

Steps to reproduce:
Select to download a file uploaded to a channel.

What happens:

A browser window/tab opens with a Slack redirect URL pointing to the file, and asks me to log in to Slack.

What I expect to happen:

I’d prefer it if Scudcloud just directly prompted me with the file saving dialogue, without having to log in to Slack again in the browser.

Other info:

I’m using version 1.22-2 from the PPA on Ubuntu 14.04. I have 2FV set up for the Slack team in question in case it matters.

Vastaa viestiin sen kontekstissa (Github)

Confusing, unnecessary ”Do you want to close it” dialog

30. tammikuuta 2016 klo 11.17
Sijainti: Vianhallintajärjestelmät: Launchpad
Avainsanat: saavutettavuus

Steps to reproduce:

0. Have two projects, A and B
1. Open project A in Geany, make no changes
2. Select Project > Recent Projects > Project B

(Reproduced on an up-to-date Xenial installation today.)

What happens:
A dialog pops up saying the previous project is open, and asks if I want to close it before proceeding.

What I expect to happen instead:
For Project B to open without the dialog. I’ve not made any changes to Project A so the dialog is blocking the switch unnecessarily. If I *had* made changes, I’d expect them to be saved implicitly at this point, or, failing that, to be prompted to *save* the changes before switching; not whether I want to close Project A (which I do).

Perhaps unrelatedly, the prompt title (”The ’Project A’ project is open.”) seems to be missing from Launchpad translations; only the question (”Do you want to close it before proceeding?”) is translatable.

Vastaa viestiin sen kontekstissa (Launchpad)

That indeed fixes it

28. tammikuuta 2016 klo 9.39
Sijainti: Vianhallintajärjestelmät: Github
Avainsanat: ownCloud

Thanks @VicDeo, that indeed fixes it.

I’d argue that the comment above the setting in the sample makes this less than apparent — at least I would have been unlikely to have dared to set it to false on my own, and it still seems to me that in making this change I lose ”a crucial security check” for .htaccess. But that’s perhaps subject for another bug.

Vastaa viestiin sen kontekstissa (Github)

Broken links in _textarea.inc.php

15. marraskuuta 2015 klo 13.34
Sijainti: Vianhallintajärjestelmät: The Bug Genie

modules/main/templates/_textarea.inc.php has two links pointing to URLs under issues.thebuggenie.com without preceding http:// protocol, resulting in non-working links.

$ grep 'href="issues' core/modules/main/templates/_textarea.inc.php 
                 'MarkdownFormatting')); ?>
                 'MarkdownFormatting')); ?>
  1. Open a text area, for example to report a new issue
  2. Have Markdown as Selected syntax
  3. Have the ”See more formatting tips in MarkdownFormatting” tip appear (I don’t know the exact steps to trigger this)
    4. Try to open the MarkdownFormatting link

Vastaa viestiin sen kontekstissa (The Bug Genie)

« Uudempia - Vanhempia »