Public bug reported:
EDS generates instances for recurring events starting at midnight with
an UNTIL date incorrectly. Specifically, using
e_cal_client_generate_instances() or
e_cal_recur_generate_instances_sync() generates an instance one day
after the UNTIL date. This bug was introduced with th
(In reply to comment #15)
> (In reply to comment #14)
> > Fixed in Factory.
>
> it's back again in 12.3-RC1 (or never got fixed?) !
>
> I'm using 12.3-RC1 plus updates and run XFCE4.
>
> /usr/bin/gnome-keyring-daemon --daemonize --login
>
> gets started and it's loading offering all my ssh-
Please read comment 37, comment 65 and comment 69. The problem has been
completely triaged, the MSI Wind handles brightness through the BIOS BUT
each change of brightness levels also emits a keypress event which is
then handled by gnome-power-manager, powerdevil, or xfce4-power-manager.
There are t
A workaround is per defintion not a solution to the underlying problem
which I and others have described a couple of times.
However, with kernel modesetting disabled I have not been able to
reproduce the second issue that I mentioned in comment #80. Can you
please describe how to reproduce the fli
Disabling KMS just makes the problem appear less often. This is
ultimately a bug in the MSI BIOS, if it chooses to handle the brightness
keys in hardware it shouldn't emit keypress events. The power managers
such as g-p-m, powerdevel, and xfce4-power-manager need to be told to
work around this. For
*** This bug is a duplicate of bug 415023 ***
https://bugs.launchpad.net/bugs/415023
** This bug has been marked a duplicate of bug 415023
brightness is broken on MSI WIND U100
--
[Karmic] [i945] Screen flickers due to constantly changing brightness level
https://bugs.launchpad.net/bugs/4
*** This bug is a duplicate of bug 415023 ***
https://bugs.launchpad.net/bugs/415023
** This bug has been marked a duplicate of bug 415023
brightness is broken on MSI WIND U100
--
LCD brightness fluctuates on Gnome login
https://bugs.launchpad.net/bugs/426010
You received this bug notific
Looking into this problem I just found four more duplicates of this bug
and have counted about 45 people confirming this bug. This issue should
at the very least be mentioned in the release notes, given the
popularity of the MSI Wind U90, U120, U123, U100 models (as well as the
various OEM versions
*** This bug is a duplicate of bug 415023 ***
https://bugs.launchpad.net/bugs/415023
** This bug has been marked a duplicate of bug 415023
brightness is broken on MSI WIND U100
--
Brightness is reset continuously
https://bugs.launchpad.net/bugs/441761
You received this bug notification be
** Bug watch added: GNOME Bug Tracker #599112
https://bugzilla.gnome.org/show_bug.cgi?id=599112
** Also affects: gnome-power via
https://bugzilla.gnome.org/show_bug.cgi?id=599112
Importance: Unknown
Status: Unknown
--
brightness is broken on MSI WIND U100
https://bugs.launchpad.n
A possible workaround to avoid the flicker (at least in my case) is to
disable kernel modesetting, that way g-p-m does not seem to get out of
sync, although it is still buggy in that each brightness keypress is
handeled twice, that is both by g-p-m and in hardware.
The main problem is making g-p-m
Once again, you do not need to press a key, if you adjust the brightness
in software the hardware emits a keypress.
The main issue is that brightness adjustments need to be either handled
in hardware or in software, i.e. by g-p-m, powerdevil etc, and that
right now it is handled by both. This is b
12 matches
Mail list logo
