Your message dated Fri, 02 Sep 2022 07:00:34 +0800 with message-id <d34bf7b469973d344f266a7d0ff2c0134a27257c.camel@debian.org> and subject line Re: orage: calendar window doesn't work anymore has caused the Debian Bug report #950993, regarding orage: calendar window doesn't work anymore to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact owner@bugs.debian.org immediately.) -- 950993: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=950993 Debian Bug Tracking System Contact owner@bugs.debian.org with problems
--- Begin Message ---
- To: Debian Bug Tracking System <submit@bugs.debian.org>
- Subject: orage: calendar window doesn't work anymore
- From: Jiff <lazyvirus@gmx.com>
- Date: Sun, 09 Feb 2020 12:12:06 +0000
- Message-id: <158125032692.7601.10844852213069388876.reportbug@msi.defcon1.lan>
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 I had to do and stopped the computer - this morning, the calendar icon is missing from the taskbar. - a click on the orage clock opens the calendar window for ~500ms (just the frame, no text) and it closes at once. - ps aux|grep orage shows each time I try to launch the calendar, it creates <defunct> lines: user 4373 0.3 0.2 224964 35992 ? Sl 11:30 0:04 /usr/lib/x86_64-linux-gnu/xfce4/panel/wrapper-1.0 /usr/lib/x86_64-linux- gnu/xfce4/panel/plugins/liborageclock.so 18 16786110 xfce4-orageclock-plugin Orage Panel Clock Show time and date? user 4864 0.0 0.0 0 0 ? Z 11:35 0:00 [orage] <defunct> user 4870 0.0 0.0 0 0 ? Z 11:35 0:00 [orage] <defunct> user 6448 0.0 0.0 0 0 ? Z 11:45 0:00 [orage] <defunct> user 7560 10.5 0.0 0 0 ? Z 11:54 0:00 [orage] <defunct> - trying to launch it from the command line has the same result as above. * What was the outcome of this action? I'm unable to get any of my alarms, which is a real concern as all of them are managed through orage and I have some importants this week. In case it was a configuration file issue, I rename the original to oragerc_OLD, logged out (and even stop/start lightdm) but the issue still persists. * What outcome did you expect instead? Orage to work as usual. -- System Information: Debian Release: 10.3 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 4.19.0-8-amd64 (SMP w/4 CPU cores) Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=fr_FR.utf8, LC_CTYPE=fr_FR.utf8 (charmap=UTF-8), LANGUAGE=fr_FR.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages orage depends on: ii libatk1.0-0 2.30.0-2 ii libc6 2.28-10 ii libcairo2 1.16.0-4 ii libfontconfig1 2.13.1-2 ii libfreetype6 2.9.1-3+deb10u1 ii libgdk-pixbuf2.0-0 2.38.1+dfsg-1 ii libglib2.0-0 2.58.3-2+deb10u2 ii libgtk2.0-0 2.24.32-3 ii libical3 3.0.4-3 ii libnotify4 0.7.7-4 ii libpango-1.0-0 1.42.4-7~deb10u1 ii libpangocairo-1.0-0 1.42.4-7~deb10u1 ii libpangoft2-1.0-0 1.42.4-7~deb10u1 ii libpopt0 1.16-12 ii libx11-6 2:1.6.7-1 ii libxfce4util7 4.12.1-3 ii orage-data 4.12.1-6 ii xfce4-panel 4.12.2-1 Versions of packages orage recommends: ii dbus-user-session [default-dbus-session-bus] 1.12.16-1 ii dbus-x11 [dbus-session-bus] 1.12.16-1 Versions of packages orage suggests: ii sox 14.4.2+git20190427-1 -- no debconf information
--- End Message ---
--- Begin Message ---
- To: Bzzzz <lazyvirus@gmx.com>
- Cc: 950993-done@bugs.debian.org
- Subject: Re: orage: calendar window doesn't work anymore
- From: Paul Wise <pabs@debian.org>
- Date: Fri, 02 Sep 2022 07:00:34 +0800
- Message-id: <d34bf7b469973d344f266a7d0ff2c0134a27257c.camel@debian.org>
- In-reply-to: <[🔎] 20220902004410.5b412dbc@msi.defcon1.lan>
- References: <158125032692.7601.10844852213069388876.reportbug@msi.defcon1.lan> <a2cb2b7406e32361b50b2a5988ec7d58aa8d040e.camel@debian.org> <20220831140502.0da0e498@msi.defcon1.lan> <[🔎] 9cd562286b75939dd26d37ba58d252fac01ac869.camel@debian.org> <[🔎] 20220901112644.4f39ff04@msi.defcon1.lan> <[🔎] 30dc874ceeab68482bd92d0322f60e2df54f2853.camel@debian.org> <[🔎] 20220902004410.5b412dbc@msi.defcon1.lan>
Version: 4.16.0-1 On Fri, 2022-09-02 at 00:44 +0200, Bzzzz wrote: > Worked like a charm :) Great, thanks for confirming! I'm closing the bug with this mail then. -- bye, pabs https://wiki.debian.org/PaulWiseAttachment: signature.asc
Description: This is a digitally signed message part
--- End Message ---