I confirm this error still occurs using libsecret from the Debian
package version 0.18.5-3.1
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1221955
Title:
GNOME_KEYRING_RESULT_IO_ERROR from
Is there any versioning information of this libsecret?
Not having a test suite is hard to tell.
I'm running 0.18.5-3.1 from devuan ascii and will try to replicate.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Upstream developer here, who managed the release of this fix back in summer
2013.
It is ridiculous how Debian and Ubuntu are ignoring our software.
I can only recommend to change distribution.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Hi again.
This bug affects every software using gnome-keyring and as such
represents a serious security issue which should be examined with
attention, to avoid future surprises.
The gnome-keyring is the gateway keeper to all passwords saved on gnome
desktops, used via dbus which may also be a
I'm stumbling into this bug now and then, using standard C code to query
gnome-keyring via gnome_keyring_find_password_sync()
Works most of the time, but returns the error with an approximated ratio
of 2% of the times it is called. In some implementation this may lead in
a dialog asking a
Ping. 10 months later...
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1313787
Title:
Multistrap is broken in 14.04
To manage notifications about this bug go to:
It is not an unuseful comment, is UX feedback, which should be valued
the most. When I initially reacted to this bug, I was reporting my
experience helping users update and observing their struggle with layers
of fixes on their desktop, often scripts made by friends to help execute
tasks.
A LEAN
On Wed, 29 Jan 2014, Mantas Kriaučiūnas wrote:
It's simple to return back old behavior - set dconf setting value:
org.gnome.nautilus.preferences executable-text-activation
to 'ask'
simple? most ubuntu users are afraid to open a Terminal.
however, thanks for the info, but this discussion
Thanks for the references to the upstream process.
Not just the executable bit, but also the file magic (shell script or
ELF) could be parsed to sort out problems.
However, I guess this is not the place for discussing this.
--
You received this bug notification because you are a member of
We should pay attention to this indeed.
This is a radical change for many users acquainted to execute shell scripts or
having them written by friends to fix things.
Believe me, this happens *all the time*.
Changing this behavior without any notice is irresponsible, a very
conservative step that
Again: this was fixed upstream.
There are more updated packages on the ppa:jaromil/freej (1.0-RC)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/668947
Title:
Corrupt JPEG data: premature end of
This bug was not solved, by closing it you imply there was no bug in the
first place, but people disagree to that. I for one report the bug is
there, .5 seconds is a too short delay and there is no way to change it.
Meanwhile a patch was also released, see:
** Branch unlinked: lp:frei0r
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/459940
Title:
Launching totem when frei0r-plugins is installed shows: Could not load
classifier cascade
To manage
Sunab already kindly provides compiled packaged of frei0r here
https://launchpad.net/~sunab/+archive/kdenlive-release
** Also affects: kdenlive
Importance: Undecided
Status: New
** Also affects: frei0r
Importance: Undecided
Status: New
--
You received this bug notification
Hi there. Guys, I'm not sure what is wrong in your process, but this bug
was fixed by an upload of release 1.3 already YEARS ago.
Frei0r 1.3 It was never incorporated in Ubuntu despite this bug being
open here.
Meanwhile after years we released version 1.4 and it is a rather useful
package for
BTW, FWIW this ppa has 1.4 ppa:sunab/kdenlive-release
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/459940
Title:
Launching totem when frei0r-plugins is installed shows: Could not load
classifier
and stability fixes. Yet, there was never an update
of the package and now not even in the new LTS.
I'm publishing frei0r packages on my ppa
https://launchpad.net/~jaromil/+archive/frei0r
Now I've asked this question many times, ended up subscribing to
mailinglists like the MOTU etc. just to discover
Committed = Triaged
what does this means?
** Changed in: frei0r (Ubuntu)
Assignee: jaromil (jaromil) = (unassigned)
why de-assign it?
I've fixed the bug already since long time.
I don't understand what is the workflow, who has the power to upload
and how that can be transferred. providing
the gdmsetup privilege escalation problem is only related to the awesome
window manager, not the default gnome or unity.
using gnome as desktop i could set the default session of my user.
so i guess i should put the candle back where it was and mark this bug
as expired.
ciao
** Changed in:
This same bug occurs in a freshly installed ubuntu 11.04.
GDM doesn't asks if the default should be changed and gdmsetup stays
grey, the unlock button does nothing, no access to the selection.
** Changed in: gdm (Ubuntu)
Status: Expired = New
--
You received this bug notification
Further testing shows this bug occurs if gdmsetup is called from another
windowmanager (i'm using awesome here, still freedesktop compliant): the
privilege escalation program doesn't gets called to unlock the widget.
once unlocked gdm lets one change the default system-wide (for all
users), but
/+source/hasciicam
so i'll close the bug.
** Changed in: hasciicam (Ubuntu)
Assignee: (unassigned) = jaromil (jaromil)
** Changed in: hasciicam (Ubuntu)
Status: New = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu
** Changed in: hasciicam (Ubuntu)
Status: Triaged = Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/749100
Title:
hasciicam version 1.0-1 failed to build on i386
--
ubuntu-bugs
:
freej
freej-dbg
freej-doc
libfreej-dev
libfreej0
libfreej0-dbg
python-freej
python-freej-dbg
** Changed in: freej (Ubuntu)
Assignee: (unassigned) = jaromil (jaromil)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https
Upstream is 1.1.1 and has already moved to V4L2 API.
for your convenience, packages are ready to test on my
ppa:jaromil/rastasoft
ciao
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/749100
Title:
it's on ppa:jaromil/frei0r
if problems arise and you can fix them youself i'm happy to incorporate
contributed patches upstream (either in master or ubuntu0 branch) just
please format them with 'git format-patch'
ciao
--
You received this bug notification because you are a member of Ubuntu
i'm sorry but the ppa is not accepting it. i don't know what's wrong:
ultimately its just a matter of changing a debian/changelog name, yet it seems
there is more to do and i can't do it alone.
i guess there is someone that has more experience with launchpad here? below
the error i get:
BTW the ubuntu0 branch is in our GIT upstream
http://code.dyne.org/index.cgi?url=frei0r/tree/h=ubuntu0
i guess already imported in your bzr, should be easy to add a target for build,
no?
how?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
i suggest for the future to take the source repository and the GPG
signed message by upstream maintainers as authoritative source for a new
release. thanks for your attention to details!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
packages ready on ppa:jaromil/frei0r
** Changed in: frei0r (Ubuntu)
Status: Confirmed = Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/459940
Title:
Launching totem when
upstream 1.1.1 is out, try it on ppa:jaromil/rastasoft
** Changed in: hasciicam (Ubuntu)
Assignee: (unassigned) = jaromil (jaromil)
** Changed in: hasciicam (Ubuntu)
Status: New = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
** Branch linked: lp:~jaromil/frei0r/master
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/459940
Title:
Launching totem when frei0r-plugins is installed shows: Could not load
classifier cascade
upstream frei0r 1.3 release now fixes this bug.
i'm now uploading a new .deb package on ppa:jaromil/frei0r
** Changed in: frei0r (Ubuntu)
Assignee: (unassigned) = jaromil (jaromil)
** Changed in: frei0r (Ubuntu)
Status: Confirmed = Fix Released
--
You received this bug
frei0r 1.3 it is a stable development release.
i'm just done compiling and uploading other packages, cross-compiling for
different platforms and then also updating the webpage on freshmeat. it all
just takes some time.. will be up on freshmeat within 24h.
thanks for reacting so fast!
--
You
upstream before our next 1.3
release.
- once done upload a new version on my ppa.
ciao
--
jaromil, upstream maintainer of frei0r-plugins
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/459940
Title
new upstream version should have solved this issue long ago
we are at 1.1.1 now, see http://ftp.dyne.org/hasciicam
.dsc and debian packages available on http://apt.dyne.org
soon will update my ppa
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
i second your analysis and conclusions, thanks Brian.
should we move this bug to libmozjs-dev and fix the deps of that
package?
BTW, why libmozjs.so is duplicated in two packages? this is so
confusing.
--
installing libmozjs-dev will remove ... firefox ubuntu-desktop ubuntu-docs
This bug is embarassing: it blocks all users from compiling new
applications that link the javascript interpreter
(and a lot of bleeding edge development is going on libmozjs and
xulrunner)
also the versioning libmozjs0d -1d -2d is confusing: it doesn't reflects
upstream versioning
--
not only the naming scheme is a problem.
apps will fail to link libmozjs since the library is compiled without
-DJS_THREADSAFE
and to the contrary the .pc file xulrunner-js adopts -DJS_THREADSAFE in the
CFLAGS
this will generate such an error:
undefined reference to
39 matches
Mail list logo
