On Fri, 02 Sep 2022 05:50:06 +0800
Paul Wise wrote:
> On Thu, 2022-09-01 at 11:26 +0200, B wrote:
>
> > I followed this HOWTO to the letter, however I meet a compilation
> > error, it seems it is the dbus part of the backport that conflict
> > with the regular installation (? my interpretatio
On Thu, 2022-09-01 at 11:26 +0200, B wrote:
> I followed this HOWTO to the letter, however I meet a compilation error,
> it seems it is the dbus part of the backport that conflict with the
> regular installation (? my interpretation, I'm not tough enough to be
> sure about that).
Looks like t
On Wed, 2022-08-31 at 14:05 +0200, B wrote:
> my bad, I did not remember that the sound comes at the exact alarm time
> (my parm: open alarm window 1 minute before its triggering time), sounds
> came right at the good time.
>
> So, everything's ferpect.
Sounds like we can probably close this
On Mon, 08 Aug 2022 10:04:28 +0800
Paul Wise wrote:
CORRECTION
==
Hi again Paul,
my bad, I did not remember that the sound comes at the exact alarm time
(my parm: open alarm window 1 minute before its triggering time), sounds
came right at the good time.
So, everything's ferpect.
BTW
On Mon, 08 Aug 2022 10:04:28 +0800
Paul Wise wrote:
> On Sun, 09 Feb 2020 12:12:06 + Jiff wrote:
>
> > - a click on the orage clock opens the calendar window for ~500ms
> >(just the frame, no text) and it closes at once.
>
> orage 4.16.0-1 has been reintroduced into Debian unstable.
>
> P
On Sun, 09 Feb 2020 12:12:06 + Jiff wrote:
> - a click on the orage clock opens the calendar window for ~500ms
>(just the frame, no text) and it closes at once.
orage 4.16.0-1 has been reintroduced into Debian unstable.
Please try it and see if the crash has been fixed.
If the crash has
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On Mon, 2020-02-10 at 11:21 +0100, B wrote:
> I'm sorry for the noise and your wasted time, but thanks for your help ;
> may be a warning about not re-using old xfce4 configuration files when
> upgrading would be of some help for others.
Well, t
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On Sun, 2020-02-09 at 19:01 +, B wrote:
> > Ok. Can you run it throught gdb and when it crashes, run bt full and
> > copy the output?
>
> I don't know how to do that, could you explain it?
Try to follow those instructions: https://wiki.xfce
On Sun, 09 Feb 2020 18:21:11 +0100
Yves-Alexis Perez wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA256
>
> On Sun, 2020-02-09 at 16:57 +, B wrote:
> > > I tried on my own Buster installation but I can't reproduce your
> > > problem. I installed Orage and it worked just fine here
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On Sun, 2020-02-09 at 16:57 +, B wrote:
> > I tried on my own Buster installation but I can't reproduce your
> > problem. I installed Orage and it worked just fine here (either the
> > plugin or running from command line).
>
> Ra ! :/
>
On Sun, 09 Feb 2020 17:36:54 +0100
Yves-Alexis Perez wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA256
>
> control: tag -1 moreinfo unreproducible
>
> On Sun, 2020-02-09 at 12:12 +, Jiff wrote:
> > Package: orage
> > Version: 4.12.1-6
> > Severity: important
> >
> > Hi Dear Maintaine
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
control: tag -1 moreinfo unreproducible
On Sun, 2020-02-09 at 12:12 +, Jiff wrote:
> Package: orage
> Version: 4.12.1-6
> Severity: important
>
> Hi Dear Maintainer,
>
>* What led up to the situation?
>
> Yesterday buster large update to
Package: orage
Version: 4.12.1-6
Severity: important
Hi Dear Maintainer,
* What led up to the situation?
Yesterday buster large update to 10.3.
* What exactly did you do (or not do) that was effective (or
ineffective)?
Yesterday, I did:
- apt update
- apt upgrade
- finished what
13 matches
Mail list logo
