Package: dnsmasq
Version: 2.78-1
Severity: grave
Tags: upstream
After upgrading from systemd 236-3+b1 to 237-1, the service cannot be started
anymore getting following error in syslog (Tested on multiple (sid) machines):
Feb 03 10:47:35 pcname systemd[1]: Starting dnsmasq - A lightweight DHCP and
Package: guake
Version: 3.0.0.b2-1
Severity: grave
Tags: upstream
When compositor is off, guake does not start at all.
(When turned on guake starts normally)
Regards
Error message:
INFO Logging configuration complete
DEBUGDebug mode enabled
DEBUGDBus not running, starting it
INFO
Package: xul-ext-noscript
Version: 5.1.3-1
Followup-For: Bug #878695
I can confirm that the plugin does not work with an existing profile:
- No NoScript icon in the toolbar
- No Preferences button in Add-Ons for NoScript
I also tried the version in experimental (5.1.4~rc1-1) but it has the same
p
Hi
I tried this new version, and it didn't work.
Then i tried with the mac randomization 'off', and it works.
I tried also the previous version (2.6-2, where the bug first happened),
and with randomization on 'off', it works as well.
Regards
On Thu, Jan 26, 2017 at 6:36 PM, Andrew Shadura wrote
rguments (1 given)
> I had to install older reportbug version and python-reportbug (both
6.6.6) to be able to
file this report.
Regards
-- Package-specific info:
** Environment settings:
INTERFACE="gtk2"
** /home/jb/.reportbugrc:
reportbug_version "6.6.6"
mode expert
ui gtk2
re
Package: wpasupplicant
Version: 2.5-2+v2.4-3+b1
Severity: grave
Tags: upstream
Me too, i have also that problem.
When installing 2.6-2, i cant see even the device anywhere (ifconfig nor
network-manager), downgrading to 2.5-2+v2.4-3+b1 works again.
I'm building the driver module (8188eu) also mys
Package: libcurl4-openssl-dev
Version: 7.51.0-1
Severity: serious
Tags: upstream
On a amd64 system with "libcurl4-openssl-dev:amd64" already installed, trying
to install "libcurl4-openssl-dev:i386"
gives following error:
Unpacking libcurl4-openssl-dev:i386 (7.51.0-1) ...
dpkg: error processing a
Package: network-manager-openvpn
Version: 1.2.6-2
Severity: grave
Tags: upstream
When trying to build the connection (with 1.2.6-2) the log says:
"VPN connection: did not receive valid IP config information"
while a successful connection (with 1.2.4-1) would continue with:
"VPN connection: (IP Co
Package: auditd
Version: 1:2.6.3-1
Followup-For: Bug #830244
Addition:
I noticed that today the service suddenly started, but only with the standard
rules file.
As soon as i add anythign to it or use my own separate rules file, the service
wont start anymore.
But i found out that when using "log_
Package: auditd
Version: 1:2.6.3-1
Followup-For: Bug #830244
I can confirm the error is present as i have it on multiple machines.
What is more interesting and maybe helps to narrow down the problem is that i
get
the error after installing libc* >2.22-13 and *gcc* >6.1.1-7 (reproducible as
when i
10 matches
Mail list logo
