[Bug 1792544] Re: demotion of pcre3 (8.x) a.k.a pcre (without the 3) in favor of pcre2 (10.x)
** Bug watch added: Debian Bug tracker #18 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=18 ** Also affects: zsh (Debian) via https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=18 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1792544 Title: demotion of pcre3 (8.x) a.k.a pcre (without the 3) in favor of pcre2 (10.x) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/aide/+bug/1792544/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1792544] Re: demotion of pcre3 (8.x) a.k.a pcre (without the 3) in favor of pcre2 (10.x)
zsh is not really fixed. Please see the changelog entry of 5.6.2-3 which states: * [92175749] Revert "Switch from the deprecated libpcre3 to the newer (!) libpcre2." libpcre2 is not a drop-in replacement and not detected by zsh's configure script. (Closes: #909084, reopens LP#1792544) -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1792544 Title: demotion of pcre3 (8.x) a.k.a pcre (without the 3) in favor of pcre2 (10.x) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/aide/+bug/1792544/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1792544] Re: demotion of pcre3 in favor of pcre2
Hi, Andreas Hasenack wrote: > I've seen the wget debian change, but just switching builddeps from pcre3-dev > to pcre2-dev and rebuilding isn't enough. The package ends up not finding > pcre and doesn't enable it: > checking for PCRE... no > checking pcre.h usability... no > checking pcre.h presence... no > checking for pcre.h... no > ... > Libs: -luuid -lidn2 -lnettle -lgnutls -lz -lpsl > > So while the package builds, it's not using pcre. > > I tried to switch apache, and while I could make it find pcre2-config and use > it, pcre2 has different libraries than pcre3: > pcre3-config --libs: -lpcre > pcre2-config --libs: no such parameter > > In pcre2, we have --libs8, --libs-posix, --libs32 and --libs16, but no > --libs. Is this a bug in pcre2-config? Indeed, same for zsh: checking for pcre-config... no checking pcre.h usability... no checking pcre.h presence... no checking for pcre.h... no checking for pcre_compile... no checking for pcre_study... no checking for pcre_exec... no [...] ../../Test/V07pcre.ztst: starting. ../../Test/V07pcre.ztst: skipped (the zsh/pcre module is not available) → Back to Incomplete. I'll revert that commit from the recent 5.6.2-2 upload. Regards, Axel -- ,''`. | Axel Beckert , https://people.debian.org/~abe/ : :' : | Debian Developer, ftp.ch.debian.org Admin `. `' | 4096R: 2517 B724 C5F6 CA99 5329 6E61 2FF9 CD59 6126 16B5 `-| 1024D: F067 EA27 26B9 C3FC 1486 202E C09E 1D89 9593 0EDE ** Changed in: zsh (Ubuntu) Status: Triaged => Incomplete -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1792544 Title: demotion of pcre3 in favor of pcre2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/aide/+bug/1792544/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1792544] Re: demotion of pcre3 in favor of pcre2
zsh in Debian Unstable (5.6.2-1) seems to build fine if I exchange libpcre3-dev by libpcre2-dev in Build-Depends and Build-Using (via debian/rules). -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1792544 Title: demotion of pcre3 in favor of pcre2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/aide/+bug/1792544/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
Re: [Bug 1726826] Re: screen 256 colour TERM setting breaks logging into older hosts
Hi Paul, Paul Gortmaker wrote: > So, something that used to work and now does not -- the boilerplate > definition of a regression, No, it's no regression in this case: Screen's behaviour hasn't changed at all. But it's long-standing behaviour relies a lot on which termcap definitions are available, and that depends on ncurses-term being installed or not on the remote (and partially also on the local) side as well as which termcap definitions are in ncurses-base and which are in ncurses-term. And that changes over time. See the README "that nobody reads". IMHO this is neither a regression nor an issue with screen's code nor can it be fixed without causing _real_ regressions, which I'd like to avoid. It might be an issue with the logic implemented in screen since many, many years if not decades. But I surely won't change such a long-standing behaviour as a distribution-only patch. Regards, Axel -- ,''`. | Axel Beckert <a...@debian.org>, https://people.debian.org/~abe/ : :' : | Debian Developer, ftp.ch.debian.org Admin `. `' | 4096R: 2517 B724 C5F6 CA99 5329 6E61 2FF9 CD59 6126 16B5 `-| 1024D: F067 EA27 26B9 C3FC 1486 202E C09E 1D89 9593 0EDE -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-terminal in Ubuntu. https://bugs.launchpad.net/bugs/1726826 Title: screen 256 colour TERM setting breaks logging into older hosts To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1726826/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1726826] Re: screen 256 colour TERM setting breaks logging into older hosts
I do not want to add any further patches to Debian's screen package which makes it differ from upstream behaviour more than it already does. (Of course, it's a different thing if issues are caused by existing patches.) And IMHO workarounds for issues in other packages do not belong into shell startup files either. (Saying this with my Debian Zsh Team hat on.) Additionally, after the long and thorough discussion in the Debian bug report (and additional discussions on the ncurses-term topic on IRC), I'm convinced that there is no perfect solution. If you change something to make screen usable in scenario X, it will make people using screen in scenario Y unhappy and vice versa. Even moving definitions from ncurses-term to ncurses-base doesn't make things better by default: It may help to SSH from older systems with ncurses-term to newer systems with just ncurses-base installed. But it will also cause issues for people SSHing from newer systems with just ncurses-base installed to older systems with an older version of ncurses-base installed. (Not having ncurses-term at all and all definitions in ncurses-base might look like a solution, but then it will which definitions are in that package at which version...) So yes, IMHO the best thing we can do is document the issue. (And improvements for the documentation are always welcome. :-) If you really think a behavioural change is needed in screen, then please make according suggestions upstream and submit patches there. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-terminal in Ubuntu. https://bugs.launchpad.net/bugs/1726826 Title: screen 256 colour TERM setting breaks logging into older hosts To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1726826/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1726826] Re: screen 256 colour TERM setting breaks logging into older hosts
Please see this new section in README.Debian, which will be published with the next upload of Debian's screen package to Debian Unstable: https://anonscm.debian.org/cgit/collab- maint/screen.git/tree/debian/README.Debian#n142 I don't see any other feasible solution to this problem from the side of the screen package. ** Changed in: screen (Ubuntu) Status: New => In Progress ** Changed in: screen (Ubuntu) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-terminal in Ubuntu. https://bugs.launchpad.net/bugs/1726826 Title: screen 256 colour TERM setting breaks logging into older hosts To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1726826/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1726826] Re: screen 256 colour TERM setting breaks logging into older hosts
** Bug watch added: Debian Bug tracker #854414 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=854414 ** Also affects: screen (Debian) via https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=854414 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-terminal in Ubuntu. https://bugs.launchpad.net/bugs/1726826 Title: screen 256 colour TERM setting breaks logging into older hosts To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1726826/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1020244] Re: gvfsd-http loops requesting the same page
Ehm, precise is still supported until April 2017. And that bug is still present in precise. So reopening... ** Changed in: gvfs (Ubuntu) Status: Invalid => Confirmed -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gvfs in Ubuntu. https://bugs.launchpad.net/bugs/1020244 Title: gvfsd-http loops requesting the same page To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1020244/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
Re: [Bug 1020244] Re: gvfsd-http loops requesting the same page
Hi,
dino99 wrote:
> but there are only two users afected since 2012;
Probably because it occurs rather seldom, but if it does, it can cause
quite some issues.
> none reported against newer version than 'precise',
Indeed. We only ran into it once. At least there was only once such
incident at our department I'm aware of.
> meaning that problem is not met and so 'fixed' as it is not a
> 'security' problem,
It's not a security problem on the machine, but it caused an security
incident here, because an e-journal provider filed an abuse complaint
at our department and I had to take the affected machine offline until
it was clear that this is "just" a bug and not a malicious (read
"DoS") attack.
So this bug can definitely cause effects that look like a DoS attack
to others.
> swith to 'incomplete' .
"Incomplete" is ok-ish IMHO. Nevertheless, I'd prefer to keep that bug
open at least until precise is gone, too.
Regards, Axel
--
,''`. | Axel Beckert <a...@debian.org>, http://people.debian.org/~abe/
: :' : | Debian Developer, ftp.ch.debian.org Admin
`. `' | 4096R: 2517 B724 C5F6 CA99 5329 6E61 2FF9 CD59 6126 16B5
`-| 1024D: F067 EA27 26B9 C3FC 1486 202E C09E 1D89 9593 0EDE
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gvfs in Ubuntu.
https://bugs.launchpad.net/bugs/1020244
Title:
gvfsd-http loops requesting the same page
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1020244/+subscriptions
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1448259] Re: Systemd does not send SIGTERM first on shutdown
** Bug watch added: Debian Bug tracker #784720 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=784720 ** Also affects: systemd (Debian) via http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=784720 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1448259 Title: Systemd does not send SIGTERM first on shutdown To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1448259/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1020244] Re: gvfsd-http loops requesting the same page
We just ran into an issue with symptoms as described here on Ubuntu 12.04.5 LTS Precise with gvfs-backends 1.12.1-0ubuntu1.2. gvfsd-http seems to have been started by evince. ** Tags added: precise -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gvfs in Ubuntu. https://bugs.launchpad.net/bugs/1020244 Title: gvfsd-http loops requesting the same page To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1020244/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1390537] Re: gdm depends on evolution-data-server-common
** Package changed: aptitude (Ubuntu) = gdm (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gdm in Ubuntu. https://bugs.launchpad.net/bugs/1390537 Title: gdm depends on evolution-data-server-common To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm/+bug/1390537/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1030022] Re: Port from legacy Xlib to to modern XCB
flwm does not use xlib directly but through FLTK. Hence flwm is the wrong place to file such a bug report. ** Changed in: flwm (Ubuntu) Status: New = Invalid -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to metacity in Ubuntu. https://bugs.launchpad.net/bugs/1030022 Title: Port from legacy Xlib to to modern XCB To manage notifications about this bug go to: https://bugs.launchpad.net/compiz/+bug/1030022/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
Re: [Bug 888662] Re: Web browsers should share the cache
Hi Fred,
Fred wrote:
Oh sorry, I just thought it was a really good idea.
It actually is a good _idea_, just not a very realistic one. :-(
Even all the Mozilla based browsers aren't sharing their caches
despite the file format is the same. And it seems as if this wanted by
Mozilla for some reason.
Because I thought it was so dumb that all web browsers use cache and
they all fetch the same stuff, but store it in different places.
You basically just asked at the wrong place: No Linux distribution has
the power to convince all the browser makers, especially Mozilla and
Google (who both care a shit about distributions IMHO), to do such a
thing. And it's the browser makers where this should start. Maybe the
W3C (World Wide Web Consortium) is a better place to dump/plant this
wish/idea.
Regards, Axel (with his links{,2}, dillo and conkeror maintainer hat on)
--
,''`. | Axel Beckert a...@debian.org, http://people.debian.org/~abe/
: :' : | Debian Developer, ftp.ch.debian.org Admin
`. `' | 1024D: F067 EA27 26B9 C3FC 1486 202E C09E 1D89 9593 0EDE
`-| 4096R: 2517 B724 C5F6 CA99 5329 6E61 2FF9 CD59 6126 16B5
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to epiphany-browser in Ubuntu.
https://bugs.launchpad.net/bugs/888662
Title:
Web browsers should share the cache
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/amaya/+bug/888662/+subscriptions
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 862911] Re: Can not set turn screen off to never (resets to 1 minute)
*** This bug is a duplicate of bug 862154 *** https://bugs.launchpad.net/bugs/862154 ** Package changed: screen (Ubuntu) = gnome-control-center (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/862911 Title: Can not set turn screen off to never (resets to 1 minute) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/862911/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 3923] Re: Cannot change default character encoding
Seems to be more or less the same issue as http://bugs.debian.org/cgi- bin/bugreport.cgi?bug=512497 ** Bug watch added: Debian Bug tracker #512497 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=512497 -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug assignee. https://bugs.launchpad.net/bugs/3923 Title: Cannot change default character encoding To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-terminal/+bug/3923/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 568839] Re: New Headline: message sent to my contacts when log in
Now also getting such messages from someone using Gajim on Karmic. I have two Jabber accounts, one which is used on my N900 (uses telepathy below IIRC), and one which is a Bitlbee IM to IRC gateway. Both connect to a jabberd 1.4 running on Debian Lenny, but running on different hosts. In Bitlbee I do get these annoying messages, but not on the N900 despite I have some of the contact which cause that problem on both accounts (e.g. the Pidgin user on Gentoo). So I do not expect empathy being the problem. I also do not suspect jabberd 1.4 to be the problem but maybe Bitlbee. Omer: Do the contacts which receive such messages from you, use Bitlbee, too? The screenshots you send look like irssi being connected to a Bitlbee. I usually always get these messages in a set of three. It looks like this for me: 14:29:48 [Bitlbee] [nickname(u...@jabber.example.org)] Headline: 14:29:48 [Bitlbee] [nickname(u...@jabber.example.org)] Headline: 14:29:49 [Bitlbee] [nickname(u...@jabber.example.org)] Headline: The differences are that I do receive Jabber messages as private message instead of in the Bitlbee IRC channel, that I do have seconds in the timestamp and the IRC network. Without these settings it would look like this: 14:29 nickname Headline: 14:29 nickname Headline: 14:29 nickname Headline: … which looks exactly what Omer's contacts seem to have provided as screenshot. -- New Headline: message sent to my contacts when log in https://bugs.launchpad.net/bugs/568839 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to empathy in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 568839] Re: New Headline: message sent to my contacts when log in
Sorry, the quoted messages were of course in Aleksanders original report, not from Omer. He just asked for how the messages I received look like. -- New Headline: message sent to my contacts when log in https://bugs.launchpad.net/bugs/568839 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to empathy in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 568839] Re: New Headline: message sent to my contacts when log in
With the N900 user we managed to reproduce those messages: He logged off and when he logged on, those messages popped up immediately in my client. -- New Headline: message sent to my contacts when log in https://bugs.launchpad.net/bugs/568839 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to empathy in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 568839] Re: New Headline: message sent to my contacts when log in
Ok, mystery solved: Those are (for whatever reason empty) broadcast messages newer clients send. Bitlbee up to version 1.2.5 displays them, Bitlbee from 1.2.6 on suppresses them. See http://code.bitlbee.org/lh/bitlbee/revision/525 for the corresponding commit and thanks to Wilmer van der Gaast (Bitlbee author) for solving that mystery. ** Changed in: empathy (Ubuntu) Status: Incomplete = Invalid -- New Headline: message sent to my contacts when log in https://bugs.launchpad.net/bugs/568839 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to empathy in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 568839] Re: New Headline: message sent to my contacts when log in
This is very annoying as recipient of such messages. I get such messages from at least 5 of my Ubuntu using contacts. 4 of the use Lucid, 1 of them uses Karmic. -- New Headline: message sent to my contacts when log in https://bugs.launchpad.net/bugs/568839 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to empathy in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 568839] Re: New Headline: message sent to my contacts when log in
Ok, this seems not only an Empathy issue. I also got this messages from one contact who uses Pidgin on Gentoo. Very strange. I use Bitlbee on Debian Unstable as client btw. in case it's a client issue (i.e. it should suppress that messages), but the Bitlbee bug tracker doesn't have an item with headline in the subject. -- New Headline: message sent to my contacts when log in https://bugs.launchpad.net/bugs/568839 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to empathy in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
