On Sun, Jan 18, 2015 at 6:18 PM, Shai Berger wrote:
>> Both grave and critical refer to actual data loss. Using the term
>> serious isn't particularly useful since that falls outside those two
>> categories anyway.
>>
>
> Again, you're being tautological, repeating your terms rather than defining
On Sun, Jan 18, 2015 at 5:44 PM, Shai Berger wrote:
> I am asking about "serious" vs. "non-serious" because those are the terms used
> by reportbug ("non-serious data loss" is a reason to mark a bug "grave").
Both grave and critical refer to actual data loss. Using the term
serious isn't particul
On Sun, Jan 18, 2015 at 4:14 PM, Shai Berger wrote:
>> > So, the bits marking messages as "read" or "unread" are not data? What,
>> > pray tell, are they?
>>
>> Easily recreatable bit flags.
>>
>
> So data isn't lost if it is "easily recreatable"? Really?
No.
> By that argument, there really sho
On Fri, Jan 16, 2015 at 8:07 AM, Shai Berger wrote:
> On Friday 16 January 2015 01:45:53 Michael Gilbert wrote:
>> > However, the problem reported here is not a usability problem. If a mail
>> > client losing record of which mails have been read and which haven't
>>
> However, the problem reported here is not a usability problem. If a mail
> client losing record of which mails have been read and which haven't isn't
> "non-serious data loss", I can't tell what is.
Actual data loss.
Best wishes,
Mike
--
To UNSUBSCRIBE, email to debian-qt-kde-requ...@lists.d
control: severity -1 important
> It may sound cynical, but my advice would be that if you're hit with this,
> change mail clients :/
>
> In the context of freeze/release, I'd suggest to tag this jessie-ignore, or
> even forever-ignore.
This is a usability problem, so it doesn't really qualify a
control: tag -1 patch, pending
Hi,
I've uploaded an nmu fixing this issue to delayed/5. Please see attached patch.
Best wishes,
Mike
kdeadmin.patch
Description: Binary data
>> The best way to see whether an issue is fixed is to make it available
>> to the people experiencing the problem. If you're afraid of causing
>> problems in unstable, you can use experimental first.
>
> Not the case here Michael :-)
>
> My worry is that this seems more like a hack than a proper
> Pending an upload, whenever some of us has the time to do it.
>
> On the other hand, I'm still not quite sure that this can be viewed as a fix.
> I'm removing the patch tag, because the approiate tag would be pending, but as
> I said before, I'm still not sure of this.
The best way to see whethe
> Thanks for caring about Qt4. Sadly, buildds running out of space is
> something that happens often and filing bugs about this issue is not
> useful given there is nothing that can be done from the maintainers.
this build failure is holding up migration of a security fix to
testing. the maintain
package: qt4-x11
version: 4:4.6.3-2
severity: grave
https://buildd.debian.org/fetch.cgi?&pkg=qt4-x11&ver=4:4.6.3-2&arch=s390&stamp=1283800739&file=log
--
To UNSUBSCRIBE, email to debian-qt-kde-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.or
severity 561762 important
thanks
even though kde4libs really needs to be checked against these webkit
issues, it isn't a reason to hold up the release.
mike
--
To UNSUBSCRIBE, email to debian-qt-kde-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.de
Package: kde4libs
Version: 4:4.3.4-1
Severity: serious
Tags: security
Hi,
The following CVE (Common Vulnerabilities & Exposures) ids were
published for webkit. webkit was forked from khtml, so these
issues very like apply to this package as well. Since there are so
many problems, I have not had
Package: kdelibs
Version: 4:3.5.10.dfsg.1-2.1
Severity: serious
Tags: security
Hi,
The following CVE (Common Vulnerabilities & Exposures) ids were
published for webkit. webkit was forked from khtml, so these
issues very like apply to this package as well. Since there are so
many problems, I hav
Package: qt4-x11
Version: 4:4.5.3-4
Severity: grave
Tags: security
Hi,
The following CVE (Common Vulnerabilities & Exposures) ids were
published for webkit. qt4-x11 embeds webkit, so most of these issues
are likely applicable to this package. Since there are so many
problems, I have not had tim
package: kde4libs
version: 4:4.3.4-1
severity: important
tags: security
hello,
it has been discovered that all of the major web browsers use a
predictable pseudo-random number generator (PRNG), which has at a
minimum the consequences described in [0]. please check whether this
package is affected
package: kdelibs
version: 4:3.5.10.dfsg.1-2.1
severity: important
tags: security
hello,
it has been discovered that all of the major web browsers use a
predictable pseudo-random number generator (PRNG), which has at a
minimum the consequences described in [0]. please check whether this
package is
package: qt4-x11
version: 4:4.5.3-4
severity: important
tags: security
hello,
it has been discovered that all of the major web browsers use a
predictable pseudo-random number generator (PRNG), which has at a
minimum the consequences described in [0]. please check whether this
package is affected.
package: kde4libs
version: 4:4.3.4-1
severity: important
tags: security
hi,
it has been disclosed that it is possible for any website to query the
user's site viewing history via css. please see [0]. i have not
personally checked whether this package is vulnerable, but it seems to
be a general
package: qt4-x11
version: 4:4.5.3-4
severity: important
tags: security
hi,
it has been disclosed that it is possible for any website to query the
user's site viewing history via css. please see [0]. i have not
personally checked whether this package is vulnerable, but it seems to
be a general
package: kdelibs
version: 4:3.5.10.dfsg.1-2.1
severity: important
tags: security
hi,
it has been disclosed that it is possible for any website to query the
user's site viewing history via css. please see [0]. i have not
personally checked whether this package is vulnerable, but it seems to
be a
Package: kdelibs
Severity: grave
Tags: security
Hi,
The following CVE (Common Vulnerabilities & Exposures) id was
published for libtool. I have determined that this package embeds a
vulnerable copy of the libtool source code. However, since this is a
mass bug filing (due to so many packages emb
Package: arts
Severity: grave
Tags: security
Hi,
The following CVE (Common Vulnerabilities & Exposures) id was
published for libtool. I have determined that this package embeds a
vulnerable copy of the libtool source code. However, since this is a
mass bug filing (due to so many packages embedd
package: kdegraphics
version: 4:3.5.5-3
severity: serious
tags: security
hi,
it has been disclosed that xpdf is vulnerable to multiple new
vulnerabilities [0]. kdegraphics embeds xpdf in both stable and
oldstable, so please coordinate with the security team to release
patched versions. kdegraphi
reopen 366342
retitle 366342 libasound2: no /dev/snd/seq for AC97 alsa driver
reassign 366342 libasound2
thank you
this was a bug thought to apply only to kmid, but it appears that it
is specific to the AC97 alsa driver. it appears that ths driver does
not provide a /dev/snd/seq device, which lea
reopen 366342
thank you
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
> Then your problem is not with kmid. Seems to be with your audio setup. I'm
> closing this bug.
wouldn't it make more sense to reassign the bug to the appropriate
package? it hasn't been fixed yet. which package would this apply
to?
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subje
> Do you have timidity installed? If so, check that /etc/default/timidity
> has TIM_ALSASEQ=true uncommented.
no, timidity had not previously been installed on my system. if you
look at kmid's dependencies, you will find that timidity is not one of
them. should that be fixed?
i installed timid
found 366342 4:3.5.9-1
thank you
> We are sorry if nobody responded when you filed the bug, KDE has
> gotten more bugs in the past years than the maintainers could handle.
> The team is trying to fix this now, but we need your help. So please
> respond to this mail and tell us if:
>
> - you are st
Package: qt4-x11
Version: 4.4.0~rc1-5
Severity: important
qt4-xll should use the already-packaged libwebkit-1.0 library, rather than
repackaging webkit separately.
this has a couple major advantages. it reduces duplicated data (on the
debian archives, on the user's system, and in memory). also,
On 5/6/08, Michael Gilbert wrote:
> i believe that this is actually an issue with webkit itself, not the
> libqt4-webkit package (which uses webkit as a library). CVE-2008-1025
> seems to indicate that the issue is wholely within webkit (there is no
> mention of qt).
i am mistaken, i
i believe that this is actually an issue with webkit itself, not the
libqt4-webkit package (which uses webkit as a library). CVE-2008-1025
seems to indicate that the issue is wholely within webkit (there is no
mention of qt).
submitter, do you have further details that would confirm that the
prob
Package: konqueror
Version: 4:3.5.8.dfsg.1-6
Severity: wishlist
it would be very nice if konqueror had a quick search toolbar (like the
one in firefox). this could even be a way for kde to make some money
(via google).
thank you for your consideration.
-- System Information:
Debian Release: len
Package: konqueror
Version: 4:3.5.8.dfsg.1-6
Severity: normal
the konqueror home button takes the user to their home directory, rather
than their home page (even when it is in the "Web Browsing" profile
mode). this is just very unintuitive, especially when the user has been
conditioned to expect
Package: libqt4-dev
Version: 4.3.3-2
Severity: normal
since there are currently security issues with a couple of the mysql
packages in sid, i would like to remove them. however, doing so would
remove libqt4-dev as well since there is a dependency on libqt4-sql
(which depends on the mysql packag
reopen 460753
thank you
> Not really. /usr/lib/kde4/phonon_xine.so, the xine backend of phonon
> links against it. This dependency can't be removed and was added
> automatically added by dpjg-shlibs (and is completely correct).
i understand that this is how things currently work, but it isn't
nec
Package: kdebase-runtime
Version: 4:4.0.0-1
Severity: normal
if one tries to remove libxine1, most of kde 4.0 will also be removed
(because kdebase-runtime has a dependency on libxine1). this is a very
undesirable effect.
it seems like the dependency should be more of a recommendation because
t
37 matches
Mail list logo
