Public bug reported:
Hi folks,
As in the summary, if you use --symlink (-y) with the output piped to a
process, it stops building the zip on the first symlink it encounters
with an unhelpful error (as the user is not using -0 intentionally).
Here's the simplest test case I can build:
I managed to track down the package with the debug symbols for
python3-yara, I'm not sure if it's super helpful as my gdb skills leave
a lot to be desired:
Program received signal SIGSEGV, Segmentation fault.
yara_callback (message=2, message_data=0x9fbb20, user_data=) at
yara-python.c:729
Public bug reported:
Ubuntu 20.04 (Focal)
libyara3:amd64 3.9.0-1
python3-yara 3.11.0-1build1
python3.8 3.8.2-1ubuntu1.1
The following is a distilled python program that will crash every time
with a segmentation fault:
##
import yara
rules = """
rule test
{
Public bug reported:
NAME="Ubuntu"
VERSION="16.10 (Yakkety Yak)"
ID=ubuntu
ID_LIKE=debian
PRETTY_NAME="Ubuntu 16.10"
VERSION_ID="16.10"
HOME_URL="http://www.ubuntu.com/;
SUPPORT_URL="http://help.ubuntu.com/;
BUG_REPORT_URL="http://bugs.launchpad.net/ubuntu/;
Under "Screensaver" make sure you have the "Lock screen after" setting
set to 0.
Confirmed works as you describe with command:
> xscreensaver-command -activate
I've noticed various power management tools interfere with the
xscreensaver default xlock. This could be why you're experiencing
XScreenSaverSuspend comes from the X11 Screen Saver extension library,
Package: libxss-dev.
This is naming confusion - XScreenSaverSuspend has nothing to do with
xscreensaver. After speaking with the xscreensaver devs, libxss-dev
package isn't used by the team. They recommend the use of the
This is the functionality you want:
> man xscreensaver-command
-deactivate
This tells xscreensaver to pretend that there has just been
user activity. This means that if the screensaver is active
(the screen is blanked), then this command
xscreensaver has such feature
** Changed in: xscreensaver (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1494454
Title:
Lock screen on wakeup from screensaver
xscreensaver has had this feature for as long as I know.
Under power management settings, configure the following to your
discretion:
Automatically lock the session: "When the screensaver is activated"
Delay locking after screensaver for "5 seconds"
Lock screen when system is going for sleep
Have you tried setting the delay to 1 second? If this still isn't
suitable, you might want to lock your screen manually rather than
waiting for the screen saver?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I'm using lubuntu with xscreensaver; my power management tools (xfce
power manager) does this for me by default, but I can't help but imagine
what might happen if I didn't have such a de installed? Why is this
option disabled by default in xscreensaver?
--
You received this bug notification
MPU-401: https://en.wikipedia.org/wiki/MPU-401
What's your output from 'dmesg | grep -u mpu-401'?
I'm running 3.19.0-28-generic and I have no error. Have you tried
updating your kernel from the upstream?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Public bug reported:
The log shows:
sipe: sip_sec_create_context: type: 1, Single Sign-On: yes, protocol:
SIP
Which is breaking the authentication. This setting was previously
disabled - but is enabled after upgrade. Should it be by default?
** Affects: pidgin-sipe (Ubuntu)
Importance:
13 matches
Mail list logo
