On Sun, May 31, 2020, at 10:17 AM, thom...@fastmail.cn wrote:
> Package: netcfg
> Version: 1.166
>
> I appologize in advance if I reported this against the wrong package.
> When running the netinst Sid daily firmware image, if I try to connect
> to my wireless network that uses WpA 2 from
Package: upower
Version: 0.99.11-2
I propose setting the critical battery action to hibernate rather than hybrid
sleep in /etc/UPower/UPower.conf
Reasons:
1. Windows does this by default. By doing what Widnows does in this situation,
you are more likely to get expected behavior. FWIW: Windows
package: mate-power-manager
Version: 1.24.1-1
Steps to reproduce:
1. Use Debian Mate with a laptop with a low battery.
2. Mate sends the message that the battery is low and it is about to hibernate.
3. The machine actually enters Hybrid Sleep.
This commit gives a clue:
Package: netcfg
Version: 1.166
I appologize in advance if I reported this against the wrong package. When
running the netinst Sid daily firmware image, if I try to connect to my
wireless network that uses WpA 2 from the installer, selecting the network via
the menu always causes a timeout,
I did some more testing on this bug this afternoon because I discovered that
powertop can generate an HTML report that I can view after assistive tech is
re-enabled. What I found is that for some reason, speech dispatcher is
preventing the package from entering low power savings like pc2
I bisected this. After I see what the change was, its hard to imagine how
accessibility could have anything to do with this since its i915 related. The
person I had read the screen in powertop is not really a computer user so maybe
they accidentally read the wrong numbers to me or I did
I built some kernels from mainline to narrow this down exactly. I don't
reproduce in 5.3.10. I reproduce in 5.3.11. Not sure if something was fixed in
the kernel that exposed an Orca/Speech Dispatcher bug or if this is a kernel
regression. Hopefully narrowing this down helps some. 5.3.10 to
I have to appologize for an error I made when reporting this. It can actually
be reproduced in both Arch and Debian. The difference was that I didn't have
pulseaudio installed on my Arch system. I am blind and use Orca. If I have Orca
playing through pulse, the pc states are not entered in both
package: src:linux
1. run powertop --auto-tune to ensure settings are optimal for power saving.
This may require a laptop.
2. Run powertop, press tab, and notice that the values in pc2 through pc10 are
not incrementing.
Reproduced on Broadwell and Whiskey Lake. The first version of 5.3 posted to
I'll add a final bit of information. I discovered that the thing that I did
while troubleshooting that caused my problem was installing xfce4 but I am not
sure which dependency causes the problem. One of the dependencies causes the
mate screensaver to start misbehaving. With xfce4 installed,
Please disreguard the message I just sent. I did a fresh install of Debian and
the screen is locking again even with the patch applied from Martin to Mate
Session Manager. I did all sorts of installing and setting changing when trying
to troubleshoot the bug with the long pause and
On Tue, Oct 8, 2019, at 10:07 AM, thom...@fastmail.cn wrote:
>
>
> On Mon, Sep 2, 2019, at 11:08 AM, Mike Gabriel wrote:
> > Hi,
> >
> > On Mi 21 Aug 2019 21:22:51 CEST, thomasw wrote:
> >
> > > Just wonder if anyone was able to reproduce this. This
On Mon, Sep 2, 2019, at 11:08 AM, Mike Gabriel wrote:
> Hi,
>
> On Mi 21 Aug 2019 21:22:51 CEST, thomasw wrote:
>
> > Just wonder if anyone was able to reproduce this. This patch is
> > adding good functionality (locking the screen before suspend) so
> >
Just wonder if anyone was able to reproduce this. This patch is adding good
functionality (locking the screen before suspend) so reverting is not the
correct solution. Before I start investigating this, I would like to know if it
works correctly for some people. I have a few friends that run
Also related:
# CONFIG_SURFACE_3_BUTTON is not set
# CONFIG_INTEL_BXTWC_PMIC_TMU is not set
package: mate-screensaver
version: 1.22.1-2
I see this in the journal
Aug 17 08:35:13 debian-laptop systemd-logind[813]: Delay lock is active (UID
1000/bw, PID 3508/mate-screensave) but inhibitor timeout is reached.
Going back to 1.22.1-1 solves the problem for me.
package: orca
When running reportbug from a terminal in debian, Orca becomes unresponsive for
a long while. More specifically, I am using the mate-terminal. Eventually, it
starts reading but it is after almost a minute. I am using the text interface.
Also, this was reproduced in the initial
On Tue, Aug 6, 2019, at 5:38 PM, Ben Hutchings wrote:
> Control: severity -1 wishlist
>
> On Tue, 2019-08-06 at 17:21 -0400, thom...@fastmail.cn wrote:
> > package: src:linux
> > I think less running code when possible and a smaller linux image is
> > always a good thing, therefore, I propose
package: network-manager
Network manager now offers its own internal dhcp client. I have been testing
this with dhcp=internal in its configuration file. Setting this by default
would offer us some advantages since this client is faster than dhclient. I
have been using it on my laptops on all
package: src:linux
Keyboards, leds, remote controls etc.
CONFIG_HID_BIGBEN_FF
CONFIG_HID_GFRM
CONFIG_HID_GT683R
CONFIG_HID_MACALLY
CONFIG_HID_VIEWSONIC
CONFIG_HID_MALTRON
CONFIG_HID_U2FZERO
package: src:linux
I think less running code when possible and a smaller linux image is always a
good thing, therefore, I propose these as modules instead of built-in.
CONFIG_PINCTRL_AMD
CONFIG_PINCTRL_CHERRYVIEW
CONFIG_PINCTRL_INTEL
CONFIG_PINCTRL_CANNONLAKE
CONFIG_PINCTRL_CEDARFORK
package: linux
CONFIG_RTW88=m and related options should be set or a bunch of laptops are
going to lose wifi support.
CONFIG_RTW88_PCI=m
CONFIG_RTW88_8822BE=y
CONFIG_RTW88_8822CE=y
Hi,
Git cherry-pick a2cdef is the solution. I built 1.22.1 with this and things
worked fine. Also see my post on the Debian mate mailing list.
Package: Orca
Sometimes when shutting down the machine with Orca running, it takes a long
time to shut down with a countdown about a stop job running. I think the
problem is that at-spi registry daemon is killed before Orca which prevents
Orca from responding to the signal to stop running but
package: linux-image-amd64
Was looking at the config and noticed these missing. Guess this also applies to
32 bit.
# CONFIG_SURFACE3_WMI is not set
# CONFIG_ACER_WIRELESS is not set
# CONFIG_INTEL_WMI_THUNDERBOLT is not set
I have some info that I think could help narrow this down and feel like I now
at least have a trail to pursue. The SD card reader works in Fedora 30 Rawhide
but not in the 29 iso. This means that between kernel 4.18 and 5.0 the
maintainers in Fedora made a change to their config that made this
package: linux-image-amd64
The card reader is device 8086:9df5 and seems to use the sdhci_pci module. I
tested with Buster which is kernel 4.19 at the time of testing. The following
message is printed multiple times in dmesg but the card reader does not start.
[ 194.701899] sdhci-pci
27 matches
Mail list logo
