Inkscape 0.92 with this bug, combined with the dog's breakfast it makes of
text from earlier versions of inkscape [1], makes me wonder if we should allow
0.92 to make it out to stable (given that the freeze has just begun).
As far as I know a patched version, 0.92.1 will come out with a half-baked
Ahh, I see now, kind of, but it looks more like a repackaging of lxsession
caused this, as a package contents search on jessie shows lxlock as appearing
as part of the lxsession package, and indeed, lxlock still builds out of the
lxsession source in testing/unstable.
My pleasure for reporting, ju
I have just upgraded lxpanel:amd64 0.8.2-1 -> 0.9.1-1 and can confirm this bug.
I hope that helps.
$ df
Filesystem 1K-blocks Used Available Use% Mounted on
udev 1958288 0 1958288 0% /dev
tmpfs 393692 6296387396 2% /run
/dev/sda820025212 14023532 4961400 74% /
tmpfs 196844884 1968364
Thanks Pino,
A few comments/questions...
root/debian/changelog
This contains only the line for this package, this seems a bit odd to ditch the
changelog from before. While Krita technically goes in to debian as a new
package,
it just replaces the older krita package, and I do not presume that u
Hi,
> My guess is that most of these bugs will fix themselves once 2.9 is
> packaged. I think there were some attempts to fix these before, but the
> package was rejected by the ftpmasters on copyright grounds - so they'll
> need to be some work to sort that out.
Yes, pretty much my philosophy
Just found out about Krita, and thinking about giving it a try...
Does the fact that the latest stable version of Krita upstream (3.x) has now
split from Calligra have any bearing
on this bug?
I.e. instead of trying to fix these issues, we should just start from a clean
slate with Calligra?
B
I don't this bug should have been closed just yet. The original reporter
obviously had a
difficult time figuring out where the problem lay, and no doubt countless
others will too.
At the very least a message needs to go out in apt-get upgrade telling people
that they
should and cite that pauvc
Actually I find this problem even more serious then that because it does this
even though I have Skype installed.
For pidgin not to crash I have to run Skype and login first, otherwsie this
happens:1. Pidgin runs Skype.2. Wait for a bit (whether logging in to Skype or
not)3. Pidgin crashes.4. Re
Hi Andrej,
Thanks for your reply. In answer to your questions, the menu item has
the active (compared with ``Delete This Panel'' which has the inactive
greyed out look'').
I get no error message (neither from the GUI, or from lxterminal after I run:
$ killall lxpanel
$ lxpanel
Since filing this
I have this problem too, I have done a bit more testing and I get a
Segmentation Fault for
obconf --tab n
where n >= 2 and n = a number
I have tried with negative numbers, floats (e.g. 1.9 and 2.1), and strings. It
either opens the 1st tab, or
Seg Faults (under the conditions I give above).
-
Subject: lxpanel: Cannot access "Desktop Pager" Settings from panel
Package: lxpanel
Version: 0.7.0-1
Severity: normal
Dear Maintainer,
* What led up to the situation?
1. Right clicked on pager area in panel
2. Left clicked on ``"Desktop Pager" Settings''
* What was the outcome
severity 756450 important
--
Looking at https://www.debian.org/Bugs/Developer#severities they define critical
(and grave) as ``*introduces* a security hole'', so I agree with you of the
importance
of this bug, but I see this as an inherent security flaw that needs to get
addressed,
rather then a
13 matches
Mail list logo
