synapse 0.2.99.4 builds with vala 0.40.3. Thank you.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1756803
Title:
0.2.99.3 won't build with vala 0.40.0
To manage notifications about this bug go
I don't have tried this application, I just came across this bug, but I
guess this is due to structure change written in ./module/gtk3privates.h
(yes, this is originally "private" header in gtk3, so the structures may
change in gtk3).
For example, with gtk+ 3.20, struct _GtkMenuPrivate has more
James, if you can please report this (feature request) to the upstream,
which may bring more possibility that your request would be included into
xscreensaver code.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Thank you for confirming. I asked the upstream to enable double
buffering on Linux again.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1390304
Title:
Noof does not preview or run
To manage
If you can compile xscreensaver by yourself, can you try below?
Edit hacks/glx/noof.c as below:
Around the line 448:
ENTRYPOINT void
init_noof (ModeInfo *mi)
{
int i;
noof_configuration *bp;
#ifdef HAVE_JWZGLES == REMOVE THIS LINE
dbuf_p = 1;
#endif == REMOVE THIS LINE
--
You
** Changed in: xscreensaver (Ubuntu)
Status: Invalid = New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/103975
Title:
[amd64] bumps crashed with SIGSEGV in __libc_start_main()
This issue is fixed in 5.22.
ref:
https://bugzilla.redhat.com/show_bug.cgi?id=911007
http://pkgs.fedoraproject.org/cgit/xscreensaver.git/commit/?id=df2bf76a86058ead6baba8d025449ba4fbf60fa3
README in xscreensaver 5.22:
* Fix for `bumps' in 64 bit.
** Bug watch added: Red Hat Bugzilla #911007
(As I wrote in the previous comment, this issue is really 64 bit
specific, does not happen on 32 bit)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/103975
Title:
[amd64] bumps crashed with SIGSEGV
This is that xscreensaver is not included in live iso, and not a problem on
xscreensaver.
http://cdimage.ubuntu.com/lubuntu/daily-live/current/saucy-desktop-i386.manifest
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Your patch is included in 5.22.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1196251
Title:
pacman crashed with SIGSEGV in is_bonus_dot()
To manage notifications about this bug go to:
This is fixed in 5.16.
ref:
http://pkgs.fedoraproject.org/cgit/xscreensaver.git/commit/?id=60149f5b6a8c8b18e20b0056046849b9c9080149
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1116006
Title:
gcc developer says gcc 4.8 does this type of aggressive optimization
when loop contains undefined behavior, ref:
http://gcc.gnu.org/gcc-4.8/porting_to.html
https://lists.fedoraproject.org/pipermail/devel/2013-January/175876.html
i.e. loop may be optimized into endless loop.
By the way, I have
(and the above patch contains some mistakes:
http://pkgs.fedoraproject.org/cgit/xscreensaver.git/commit/?id=60fa5b4c75d354d808a219c52a7a648f9b22cfb1
http://pkgs.fedoraproject.org/cgit/xscreensaver.git/commit/?id=888fb0d80b39f060f658cbf5670edae0cbaeeb4c
)
--
You received this bug notification
All the above 3 patches were already included in 5.16, i.e.
* xscreensaver-demo does truncate http:// into http:/
* xscreensaver-demo now uses memmove instead of strcpy when source and
destination overlaps, which will _perhaps_ fix some strange about degraeve
into degraee and so on.
For
xscreensaver-demo does truncate http:// into http:/
This is xscreensaver-demo does NOT truncate http:// into http:/ (from 5.16)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1116006
Title:
Step to reproduce:
* Launch with firefox -ProfileManager , create new profile, and launch
firefox with that (new) profile
* Go Preferences - Advanced - Network - Connection - Settings
* Once choose Manual proxy configuration, set random http proxy, change port
(like HTTP Proxy: aa Port:
(In reply to Mamoru TASAKA from comment #40)
Step to reproduce:
* Launch with firefox -ProfileManager , create new profile, and launch
firefox with that (new) profile
* Go Preferences - Advanced - Network - Connection - Settings
* Once choose Manual proxy configuration, set random http
Note that with xscreensaver 5.21, AC_SYS_LARGEFILE is added to
configure.in, so _FILE_OFFSET_BITS will be set to 64 in config.h{,in} if
needed with doing configure, and modifying CFLAGS is no longer needed.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
I guess this is the key line in the log file:
xscreensaver: 21:17:14: LOCK ClientMessage received; activating and locking.
Presumably something, such as ACPI, is asking xscreensaver to lock
rather than activate?
Probably, from looking at the log.
--
You received this bug notification
If you can still reproduce this bug, would you try lauching xscreensaver
with
$ xscreensaver -verbose -log output_log_name
and attach the contents of output_log_name ?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I discussed this with the upstream developer and we agreed to add
-D_FILE_OFFSET_BITS=64 to compiler flags when building whole
xscreensaver source. He is now thinking where to write this on
configure.in.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Reproducible even with xscreensaver 5.18 on my i686 machine (client).
It seems that stat() on the line 1256 in get_filename_1() in
xscreensaver-getimage.c returns -1 with errno 75 = EOVERFLOW. stat(2)
says that this can happen when such application was not compiled with
-D_FILE_OFFSET_BITS=64 and
photopile.diff
While the comment changes in this photopile.diff was not applied, the
changes in hacks/glx/photopile.c is already included in xscreensaver
5.16.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Perhaps this:
https://bugzilla.redhat.com/show_bug.cgi?id=746847
Fixed in xscreensaver 5.16 .
** Bug watch added: Red Hat Bugzilla #746847
https://bugzilla.redhat.com/show_bug.cgi?id=746847
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
The attached patch changes
It is highly appreciated if you would send your patch to the upstream
developer.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1007862
Title:
Xscreensaver photopile
I use ASCII characters only and currently I cannot check this. However
do some people know some evidence that XLookupString checks LC_CTYPE?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/671923
So something like attached is needed?
** Patch added: Trial patch
https://bugs.launchpad.net/ubuntu/+source/xscreensaver/+bug/671923/+attachment/2199597/+files/xscreensaver-5.14-XLookupString-need-locale.patch
--
You received this bug notification because you are a member of Ubuntu
Bugs,
If I use `LANG=ja_JP.UTF-8 xscreensaver`, only the date is scrambled,
but not the word Password.
Well, if I comment out #undef ENABLE_NLS in xscreensaver.c around line
1410, I still see garbage messages on both date and Password in
LANG=ja_JP.UTF-8 (note that you can see the name tasaka1 in the
This issue is known on 5.12 and should be fixed in 5.13 (see comments
around line 1405 in on xscreensaver-5.14/driver/xscreensaver.c)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/793344
Title:
Did someone try xscreensaver 5.14 for this issue?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/671923
Title:
In XScreensaver unlock screen it is not possible to insert € sign
To manage
** Changed in: alexandria (Ubuntu)
Status: Invalid = New
--
Alexandria crashes on start-up
https://bugs.launchpad.net/bugs/239403
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
From other posts and dump.txt attached on commeit 1,
I guess Alperen is trying to use alexandria in Turkish locale
(i.e. in LANG=tr_TR.UTF-8).
If so, this is due to bugs in both ruby-gnome2 and alexandria.
For ruby-gnome2 side, this was fixed in rev 2857 [1][2]
For alexandria side, this was
I am Fedora user and I am not familiar with ubuntu, however from
this report it seems that José is using karmic branch (right?).
If so, this is due to the change in gnome-settings-daemon 2.27.4
From NEWS file in g-s-d:
--
-
I guess the attached patch should fix this issue. I would appreciate
it if you would apply my patch (by the way I will send my patch to Ubuntu
members
later)
Regards,
Mamoru Tasaka
** Attachment added: Proposal patch to fix this issue
http
I guess this is the same as
https://bugzilla.novell.com/show_bug.cgi?id=242602
https://bugzilla.redhat.com/show_bug.cgi?id=428195
Patch available from Novell bugzilla.
--
Search results invisible in amd64 version
https://bugs.launchpad.net/bugs/174407
You received this bug notification because
35 matches
Mail list logo
