Public bug reported:
The code that detects universal-ctags,
does this:
`echo | ctags -L - -f /dev/null`
On Focal this fails with:
`sort: /dev/null: error truncating: Invalid argument`
It works properly on any more recent distros.
I think this upstream fix should be applied to Focal:
Public bug reported:
This bug was recently fixed in llvm upstream:
https://github.com/llvm/llvm-project/pull/84290
But now it sneaked into ubuntu-Noble, and
breaks my LP builds:
** Bug watch added: github.com/dosemu2/dosemu2/issues #1500
https://github.com/dosemu2/dosemu2/issues/1500
** Also affects: dosemu2 via
https://github.com/dosemu2/dosemu2/issues/1500
Importance: Unknown
Status: Unknown
** Changed in: dosemu2
Importance: Unknown => Medium
--
So I am that moron who makes typos in commands. :(
Thank you.
** Changed in: xfonts-utils (Ubuntu)
Status: Incomplete => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1920052
Title:
Public bug reported:
$ pdftopcf
Command 'pdftopcf' not found, did you mean:
command 'bdftopcf' from deb xfonts-utils (1:7.7+6)
Try: sudo apt install
$ $ dpkg-query -s xfonts-utils
Package: xfonts-utils
Status: install ok installed
Priority: optional
Section: x11
Installed-Size: 416
** Package changed: ubuntu => linux (Ubuntu)
** Bug watch added: github.com/dosemu2/dosemu2/issues #1404
https://github.com/dosemu2/dosemu2/issues/1404
** Also affects: linux via
https://github.com/dosemu2/dosemu2/issues/1404
Importance: Unknown
Status: Unknown
** Project
But are you sure the API was changed
rather than extended? Are there any
evidences that the transition will be
needed?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1863148
Title:
RFE: update
In fact, x11vnc just inserts the fake
KeyRelease for Shift, before sending Fx.
It is likely because it searches for a
possible combinations to generate the
same keycode on a target system, and
uses the first match, instead of trying
the best match with identical modifiers.
--
You received this
Public bug reported:
Shift-Fx (x is a number) is treated as just Fx.
Very easy to test.
Open terminal locally and run "cat".
Press Shift-F1.
You will see ^[[1;2P
Press Shift-F1 on a desktop shared via x11vnc
You will see ^[OP which is plain F1.
After many hours of investigations (I started
from
Public bug reported:
All versions of libjson-c-dev prior to 0.13
lack the json_pointer API. As the result, libjson-c-dev
is only useful since Eoan, which is very disappointing.
Please update json-c to 0.13 on every supported distro
prior to Eoan (Disco, Bionic, Xenial etc).
** Affects: json-c
Public bug reported:
libfliudsynth provides an API to locate the default
soundfonts. Its like below:
ret = fluid_settings_dupstr(settings, "synth.default-soundfont", );
if (ret == 0 || access(sfont, R_OK) != 0) {
ret = fluid_synth_sfload(synth, sfont, TRUE);
}
Under ubuntu it returns
But why not to have the unpatched new upstream
version that already contains the fix? Or is
xenial in a freeze mode and updated packages
are not accepted?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Feel free to remove the patched package.
The fix was applied 2 years ago.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1679573
Title:
[SRU]full-screen switching is broken
To manage notifications
I don't think I did, at least definitely
not willingly. I only did do_release_upgrade.
But this setup can no longer be replicated,
so if this problem only affected me, there is
probably no reason to keep it opened.
--
You received this bug notification because you are a member of Ubuntu
Bugs,
Exceptionally annoying bug.
Fortunately I've found about Win-L from
this thread, so maybe if it works for me,
at least I won't have to reboot after every
attempt of locking the screen...
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Well its definitely in 2.0.6.
It was released in 17 Sep 2017:
https://discourse.libsdl.org/t/sdl-2-0-6-released/23109
and the fix was committed at 2017-04-03.
So my suggestion is to just mark this as fixed.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
So I have 2.0.6+dfsg1-3ubuntu1 already installed,
and there seem to be no bug. But I have not used
the -proposed repo for this.
So is it possible that the fixed packages are
already in the main Artful repo and we don't have
to care?
--
You received this bug notification because you are a member
Isn't it just a packaging of a more recent SDL?
Should I indeed test it explicitly so that it
not to be removed?
I tested this fix directly from SDL repository
before reporting the problem here.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Public bug reported:
It is not possible to disable NLS in
proftpd. Tried:
LangEngine off
UseEncoding off
But it still replies with the native language
strings. Maybe this is fine in some countries,
but in Russia there are several incompatible
charsets used, so the inability the select one
or
Public bug reported:
$ fbset 768x576-75
ioctl FBIOPUT_VSCREENINFO: Invalid argument
And the same happens with all other modes
defined in /etc/fb.modes
The problem seems to be that KMS fbcon does
not accept the pixclock parameter, which is
the first parameter in a "timings" string.
Changing it
Public bug reported:
After upgrading to 17.04, nautilus stops
opening the inserted flash drives. It gives:
Unable to open a folder for DRIVENAME
No application is registered as handling this file
The fix was found here:
affects: libsdl via
http://bugzilla.libsdl.org/show_bug.cgi?id=1859
Importance: Unknown
Status: Unknown
** Bug watch added: github.com/stsp/dosemu2/issues #350
https://github.com/stsp/dosemu2/issues/350
** Also affects: dosemu2 via
https://github.com/stsp/dosemu2/issues/350
OK, sorry then.
I just have the same problem and didn't want
to create a duplicate ticket...
Will do now.
** No longer affects: libsdl
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1671954
Title:
The fix was just applied to sdl mainline:
https://hg.libsdl.org/SDL/rev/f931db466859
Would be very nice if ubuntu can take this
up as this is a real show-stopper for the
full-screen apps.
** Also affects: libsdl via
http://bugzilla.libsdl.org/show_bug.cgi?id=1859
Importance: Unknown
Fullscreen switching in sdl2 is currently broken:
https://bugzilla.libsdl.org/show_bug.cgi?id=1859
This ticket has the patch that fixes it:
https://bugzilla-attachments.libsdl.org/attachment.cgi?id=1715
I tested the patch and it works for me.
Would be nice if ubuntu can apply it, as
it seems sdl
Public bug reported:
$ lsb_release -rd
Description:Ubuntu 16.04 LTS
Release:16.04
$ tightvncpasswd
Using password file /home/pa/.vnc/passwd
Password:
Verify:
Would you like to enter a view-only password (y/n)? n
*** buffer overflow detected ***: tightvncpasswd terminated
===
Please consider integrating also the fix for
bug #1389811 to make the testing easier and
more sensible.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1547060
Title:
cant use -d switch
To manage
What was the fix?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1551730
Title:
error deleting node
To manage notifications about this bug go to:
Public bug reported:
Version: 1.10.0+bzr4578-0ubuntu2
When deleting the node, I get this crash:
2016-03-01 16:16:19 [-] Error on request (257) node.action:
node-4b22834e-d1a3-11e5-b0b9-005043000be0
Traceback (most recent call last):
File "/usr/lib/python3.5/threading.py",
Public bug reported:
Version: 1.10.0+bzr4578-0ubuntu2
When deleting the node, I get this crash:
2016-03-01 16:16:19 [-] Error on request (257) node.action:
node-4b22834e-d1a3-11e5-b0b9-005043000be0
Traceback (most recent call last):
File "/usr/lib/python3.5/threading.py",
Public bug reported:
maas 1.10.0+bzr4578-0ubuntu2
After commissioning the node, I've replaced its HDD.
Now commission fails with this error:
b'{"__all__": ["Block device with this Node and Name already exists."]}'
This happens when uploading 00-maas-07-block-devices.out.
** Affects: maas
Public bug reported:
maas 1.10.0+bzr4578-0ubuntu2
After commissioning the node, I've replaced its HDD.
Now commission fails with this error:
b'{"__all__": ["Block device with this Node and Name already exists."]}'
This happens when uploading 00-maas-07-block-devices.out.
** Affects: maas
Public bug reported:
tgt-1:1.0.62-1ubuntu2
# ./tgtd -d 1
-d argument value '1' invalid
Try `tgtd --help' for more information.
The following change should fix the problem:
--- util.h.old 2015-12-02 03:27:15.0 +0300
+++ util.h 2016-02-18 18:04:08.749932076 +0300
@@ -148,7 +148,7
Public bug reported:
tgt-1:1.0.62-1ubuntu2
# ./tgtd -d 1
-d argument value '1' invalid
Try `tgtd --help' for more information.
The following change should fix the problem:
--- util.h.old 2015-12-02 03:27:15.0 +0300
+++ util.h 2016-02-18 18:04:08.749932076 +0300
@@ -148,7 +148,7
What fix is mentioned here?
I am getting this when trying to upgrade from trusty to xenial.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1281758
Title:
re-installing maas-region-controller fails
What fix is mentioned here?
I am getting this when trying to upgrade from trusty to xenial.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to maas in Ubuntu.
https://bugs.launchpad.net/bugs/1281758
Title:
re-installing
This is a problem in Trusty too, if
BUSYBOX=n
in /etc/initramfs-tools/initramfs.conf.
Neither grep nor egrep seems to be added, so
the same error message appears.
** Changed in: initramfs-tools (Ubuntu Trusty)
Status: Invalid => Confirmed
--
You received this bug notification because you
37 matches
Mail list logo
