[Touch-packages] [Bug 2057792] Re: Some Games are crashing linked to a vm_max_map_count too low
To complete the list of products: In addition to games, this change is also useful for users of Elasticsearch and/or Opensearch and Apache Lucene/Solr on large clusters. Elasticsearch also suggests raising the value, although not so high: https://www.elastic.co/guide/en/elasticsearch/reference/current/vm-max-map-count.html Opensearch: https://opensearch.org/docs/latest/install-and-configure/install-opensearch/index/#important-settings Apache Solr: https://solr.apache.org/guide/solr/latest/deployment-guide/taking-solr-to-production.html If you e.g. start Elasticsearch without a large enough vm.max_map_count, it will print a log message to raise it and exit. My personal opinion: Actually the game issues described here should better be fixed in Steam's launcher when starting such a game (or in Wine). The downstream software should better ask the user to raise the value upon starting. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to procps in Ubuntu. https://bugs.launchpad.net/bugs/2057792 Title: Some Games are crashing linked to a vm_max_map_count too low Status in gamemode package in Ubuntu: Confirmed Status in linux package in Ubuntu: Won't Fix Status in procps package in Ubuntu: Fix Released Bug description: Hello there, I submit this request to improve the gaming experience in ubuntu for all users. Today, Hogwarts Legacy, Star Citizen and few more games are crashing or just not starting because the vm_max_map_count is locked at 65530. If we change this value to a value > 20, all games are working well and there is no bug linked to maps. Some others distribution like Fedora or Pop OS, have already made the change few month before. It's time to Ubuntu to makes the change also. Thanks in advance for applying this request. How to make this change : One file to modify : /etc/sysctl.conf Add this line : vm.max_map_count=2147483642 Save Reboot and enjoy Best Regards Vinceff To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gamemode/+bug/2057792/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
Re: [Touch-packages] [Bug 1981103] Re: System with DNS server in /etc/network/interfaces has bogus systemd-resolved config after upgrade to 22.04
*This* bug has the full information in the first post including all
needed to fix the problem. Actually there are more problems in the
script regarding syntax, so more issues exist, leading to unwanted
behavior.
Uwe
Am 22. Oktober 2022 22:05:59 MESZ schrieb David Kowis
<1981...@bugs.launchpad.net>:
>https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/1910273
>
>This one seems to have the full patch repair in the bug description.
>None of the other bugs I've found relating to this have the full
>solution.
>
>--
>You received this bug notification because you are subscribed to the bug
>report.
>https://bugs.launchpad.net/bugs/1981103
>
>Title:
> System with DNS server in /etc/network/interfaces has bogus systemd-
> resolved config after upgrade to 22.04
>
>Status in ifupdown package in Ubuntu:
> Triaged
>
>Bug description:
> Description:Ubuntu 22.04 LTS
> Release:22.04
>
> ifupdown:
>Installed: 0.8.36+nmu1ubuntu3
>Candidate: 0.8.36+nmu1ubuntu3
>Version table:
> *** 0.8.36+nmu1ubuntu3 500
> 500 http://de.archive.ubuntu.com/ubuntu jammy/universe amd64 Packages
> 100 /var/lib/dpkg/status
>
> After upgrading a server with classic ifupdown configuration after
> reboot the machine had no valid dns servers anymore.
>
> The problem is that the state file created by ifupdown using
> /etc/network/if-up.d/resolved looks like this:
>
> root@pangaea-pm:~# cat /run/network/ifupdown-inet-ens13
> "DNS"="134.102.20.20 134.102.200.14"
> "DOMAINS"="marum.de"
>
> The script later sources this file and causes the following errors,
> easy to see when you execute this:
>
> root@pangaea-pm:~# ifdown ens13; ifup ens13
> /etc/network/if-down.d/resolved: 12: mystatedir: not found
> /etc/network/if-up.d/resolved: 12: mystatedir: not found
> /etc/network/if-up.d/resolved: 71: DNS: not found
> /etc/network/if-up.d/resolved: 1: /run/network/ifupdown-inet-ens13:
> DNS=134.102.20.20 134.102.200.14: not found
> /etc/network/if-up.d/resolved: 2: /run/network/ifupdown-inet-ens13:
> DOMAINS=marum.de: not found
> Failed to parse DNS server address: DNS
> Failed to set DNS configuration: Invalid argument
>
> This happened to me on three different servers, so this is a serious
> bug and should be fixed before 22.04 upgrades are allowed for
> everybody. Most servers provided by data centers like Hetzner
> (Germany) are configure like that. After a do-release-upgrade you have
> no working DNS anymore, unless you disable systemd-resolved. I don't
> want to use netplan, so changing to this is no option.
>
> The fix is easy - remove the quotes in the script on the left side
> "$DNS" => $DNS; same for DOMAINS:
>
> if [ -n "$NEW_DNS" ]; then
> cat <"$mystatedir/ifupdown-${ADDRFAM}-$interface"
> $DNS="$NEW_DNS"
> EOF
> if [ -n "$NEW_DOMAINS" ]; then
> cat <>"$mystatedir/ifupdown-${ADDRFAM}-$interface"
> $DOMAINS="$NEW_DOMAINS"
> EOF
> fi
> fi
>
>To manage notifications about this bug go to:
>https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/1981103/+subscriptions
>
--
Uwe Schindler
Achterdiek 19, 28357 Bremen
https://www.thetaphi.de
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ifupdown in Ubuntu.
https://bugs.launchpad.net/bugs/1981103
Title:
System with DNS server in /etc/network/interfaces has bogus systemd-
resolved config after upgrade to 22.04
Status in ifupdown package in Ubuntu:
Triaged
Bug description:
Description:Ubuntu 22.04 LTS
Release:22.04
ifupdown:
Installed: 0.8.36+nmu1ubuntu3
Candidate: 0.8.36+nmu1ubuntu3
Version table:
*** 0.8.36+nmu1ubuntu3 500
500 http://de.archive.ubuntu.com/ubuntu jammy/universe amd64 Packages
100 /var/lib/dpkg/status
After upgrading a server with classic ifupdown configuration after
reboot the machine had no valid dns servers anymore.
The problem is that the state file created by ifupdown using
/etc/network/if-up.d/resolved looks like this:
root@pangaea-pm:~# cat /run/network/ifupdown-inet-ens13
"DNS"="134.102.20.20 134.102.200.14"
"DOMAINS"="marum.de"
The script later sources this file and causes the following errors,
easy to see when you execute this:
root@pangaea-pm:~# ifdown ens13; ifup ens13
/etc/network/if-down.d/resolved: 12: mystatedir: not found
/etc/network/if-up.d/resolved: 12: mystatedir: not found
/etc/network/if-up.d/resolved: 71: DNS: not found
/etc/network/if-up.d/resolved
[Touch-packages] [Bug 1981103] Re: System with DNS server in /etc/network/interfaces has bogus systemd-resolved config after upgrade to 22.04
If you changed away from /etc/network/interfaces file to netplan.io
configuration (/etc/netplan/...) then you won't need ifupdown. There is
a configuartion tool, with simple configs it works: See this info how to
convert your network config. But be sure to have physical access to the
machine's console:
https://gist.github.com/mss/7a8e048dd51e5ef928039f1450ba8f31
I did this for my systems and removed and purged ifupdown. For some
configs it may be very complex, especially if you have many tunnels,
bridges or other special stuff in /etc/network/interfaces. But for
simple single ethernet/wifi device it is easy to migrate using the above
GIST.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ifupdown in Ubuntu.
https://bugs.launchpad.net/bugs/1981103
Title:
System with DNS server in /etc/network/interfaces has bogus systemd-
resolved config after upgrade to 22.04
Status in ifupdown package in Ubuntu:
Confirmed
Bug description:
Description:Ubuntu 22.04 LTS
Release:22.04
ifupdown:
Installed: 0.8.36+nmu1ubuntu3
Candidate: 0.8.36+nmu1ubuntu3
Version table:
*** 0.8.36+nmu1ubuntu3 500
500 http://de.archive.ubuntu.com/ubuntu jammy/universe amd64 Packages
100 /var/lib/dpkg/status
After upgrading a server with classic ifupdown configuration after
reboot the machine had no valid dns servers anymore.
The problem is that the state file created by ifupdown using
/etc/network/if-up.d/resolved looks like this:
root@pangaea-pm:~# cat /run/network/ifupdown-inet-ens13
"DNS"="134.102.20.20 134.102.200.14"
"DOMAINS"="marum.de"
The script later sources this file and causes the following errors,
easy to see when you execute this:
root@pangaea-pm:~# ifdown ens13; ifup ens13
/etc/network/if-down.d/resolved: 12: mystatedir: not found
/etc/network/if-up.d/resolved: 12: mystatedir: not found
/etc/network/if-up.d/resolved: 71: DNS: not found
/etc/network/if-up.d/resolved: 1: /run/network/ifupdown-inet-ens13:
DNS=134.102.20.20 134.102.200.14: not found
/etc/network/if-up.d/resolved: 2: /run/network/ifupdown-inet-ens13:
DOMAINS=marum.de: not found
Failed to parse DNS server address: DNS
Failed to set DNS configuration: Invalid argument
This happened to me on three different servers, so this is a serious
bug and should be fixed before 22.04 upgrades are allowed for
everybody. Most servers provided by data centers like Hetzner
(Germany) are configure like that. After a do-release-upgrade you have
no working DNS anymore, unless you disable systemd-resolved. I don't
want to use netplan, so changing to this is no option.
The fix is easy - remove the quotes in the script on the left side
"$DNS" => $DNS; same for DOMAINS:
if [ -n "$NEW_DNS" ]; then
cat <"$mystatedir/ifupdown-${ADDRFAM}-$interface"
$DNS="$NEW_DNS"
EOF
if [ -n "$NEW_DOMAINS" ]; then
cat <>"$mystatedir/ifupdown-${ADDRFAM}-$interface"
$DOMAINS="$NEW_DOMAINS"
EOF
fi
fi
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/1981103/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1981103] Re: System with DNS server in /etc/network/interfaces has bogus systemd-resolved config after upgrade to 22.04
One addition, line 71 in script also looks strange:
if ! cmp --silent "$oldstate" "$newstate" 2>/dev/null; then
DNS DNS6 DOMAINS DOMAINS6 DEFAULT_ROUTE
This causes:
/etc/network/if-up.d/resolved: 71: DNS: not found
If you are on it, please fix this, too.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ifupdown in Ubuntu.
https://bugs.launchpad.net/bugs/1981103
Title:
System with DNS server in /etc/network/interfaces has bogus systemd-
resolved config after upgrade to 22.04
Status in ifupdown package in Ubuntu:
New
Bug description:
Description:Ubuntu 22.04 LTS
Release:22.04
ifupdown:
Installed: 0.8.36+nmu1ubuntu3
Candidate: 0.8.36+nmu1ubuntu3
Version table:
*** 0.8.36+nmu1ubuntu3 500
500 http://de.archive.ubuntu.com/ubuntu jammy/universe amd64 Packages
100 /var/lib/dpkg/status
After upgrading a server with classic ifupdown configuration after
reboot the machine had no valid dns servers anymore.
The problem is that the state file created by ifupdown using
/etc/network/if-up.d/resolved looks like this:
root@pangaea-pm:~# cat /run/network/ifupdown-inet-ens13
"DNS"="134.102.20.20 134.102.200.14"
"DOMAINS"="marum.de"
The script later sources this file and causes the following errors,
easy to see when you execute this:
root@pangaea-pm:~# ifdown ens13; ifup ens13
/etc/network/if-down.d/resolved: 12: mystatedir: not found
/etc/network/if-up.d/resolved: 12: mystatedir: not found
/etc/network/if-up.d/resolved: 71: DNS: not found
/etc/network/if-up.d/resolved: 1: /run/network/ifupdown-inet-ens13:
DNS=134.102.20.20 134.102.200.14: not found
/etc/network/if-up.d/resolved: 2: /run/network/ifupdown-inet-ens13:
DOMAINS=marum.de: not found
Failed to parse DNS server address: DNS
Failed to set DNS configuration: Invalid argument
This happened to me on three different servers, so this is a serious
bug and should be fixed before 22.04 upgrades are allowed for
everybody. Most servers provided by data centers like Hetzner
(Germany) are configure like that. After a do-release-upgrade you have
no working DNS anymore, unless you disable systemd-resolved. I don't
want to use netplan, so changing to this is no option.
The fix is easy - remove the quotes in the script on the left side
"$DNS" => $DNS; same for DOMAINS:
if [ -n "$NEW_DNS" ]; then
cat <"$mystatedir/ifupdown-${ADDRFAM}-$interface"
$DNS="$NEW_DNS"
EOF
if [ -n "$NEW_DOMAINS" ]; then
cat <>"$mystatedir/ifupdown-${ADDRFAM}-$interface"
$DOMAINS="$NEW_DOMAINS"
EOF
fi
fi
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/1981103/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1981103] Re: System with DNS server in /etc/network/interfaces has bogus systemd-resolved config after upgrade to 22.04
I think this should unset the variables, then error goes away and it
makes sense!
if ! cmp --silent "$oldstate" "$newstate" 2>/dev/null; then
unset DNS DNS6 DOMAINS DOMAINS6 DEFAULT_ROUTE
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ifupdown in Ubuntu.
https://bugs.launchpad.net/bugs/1981103
Title:
System with DNS server in /etc/network/interfaces has bogus systemd-
resolved config after upgrade to 22.04
Status in ifupdown package in Ubuntu:
New
Bug description:
Description:Ubuntu 22.04 LTS
Release:22.04
ifupdown:
Installed: 0.8.36+nmu1ubuntu3
Candidate: 0.8.36+nmu1ubuntu3
Version table:
*** 0.8.36+nmu1ubuntu3 500
500 http://de.archive.ubuntu.com/ubuntu jammy/universe amd64 Packages
100 /var/lib/dpkg/status
After upgrading a server with classic ifupdown configuration after
reboot the machine had no valid dns servers anymore.
The problem is that the state file created by ifupdown using
/etc/network/if-up.d/resolved looks like this:
root@pangaea-pm:~# cat /run/network/ifupdown-inet-ens13
"DNS"="134.102.20.20 134.102.200.14"
"DOMAINS"="marum.de"
The script later sources this file and causes the following errors,
easy to see when you execute this:
root@pangaea-pm:~# ifdown ens13; ifup ens13
/etc/network/if-down.d/resolved: 12: mystatedir: not found
/etc/network/if-up.d/resolved: 12: mystatedir: not found
/etc/network/if-up.d/resolved: 71: DNS: not found
/etc/network/if-up.d/resolved: 1: /run/network/ifupdown-inet-ens13:
DNS=134.102.20.20 134.102.200.14: not found
/etc/network/if-up.d/resolved: 2: /run/network/ifupdown-inet-ens13:
DOMAINS=marum.de: not found
Failed to parse DNS server address: DNS
Failed to set DNS configuration: Invalid argument
This happened to me on three different servers, so this is a serious
bug and should be fixed before 22.04 upgrades are allowed for
everybody. Most servers provided by data centers like Hetzner
(Germany) are configure like that. After a do-release-upgrade you have
no working DNS anymore, unless you disable systemd-resolved. I don't
want to use netplan, so changing to this is no option.
The fix is easy - remove the quotes in the script on the left side
"$DNS" => $DNS; same for DOMAINS:
if [ -n "$NEW_DNS" ]; then
cat <"$mystatedir/ifupdown-${ADDRFAM}-$interface"
$DNS="$NEW_DNS"
EOF
if [ -n "$NEW_DOMAINS" ]; then
cat <>"$mystatedir/ifupdown-${ADDRFAM}-$interface"
$DOMAINS="$NEW_DOMAINS"
EOF
fi
fi
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/1981103/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1981103] [NEW] System with DNS server in /etc/network/interfaces has bogus systemd-resolved config after upgrade to 22.04
Public bug reported:
Description:Ubuntu 22.04 LTS
Release:22.04
ifupdown:
Installed: 0.8.36+nmu1ubuntu3
Candidate: 0.8.36+nmu1ubuntu3
Version table:
*** 0.8.36+nmu1ubuntu3 500
500 http://de.archive.ubuntu.com/ubuntu jammy/universe amd64 Packages
100 /var/lib/dpkg/status
After upgrading a server with classic ifupdown configuration after
reboot the machine had no valid dns servers anymore.
The problem is that the state file created by ifupdown using
/etc/network/if-up.d/resolved looks like this:
root@pangaea-pm:~# cat /run/network/ifupdown-inet-ens13
"DNS"="134.102.20.20 134.102.200.14"
"DOMAINS"="marum.de"
The script later sources this file and causes the following errors, easy
to see when you execute this:
root@pangaea-pm:~# ifdown ens13; ifup ens13
/etc/network/if-down.d/resolved: 12: mystatedir: not found
/etc/network/if-up.d/resolved: 12: mystatedir: not found
/etc/network/if-up.d/resolved: 71: DNS: not found
/etc/network/if-up.d/resolved: 1: /run/network/ifupdown-inet-ens13:
DNS=134.102.20.20 134.102.200.14: not found
/etc/network/if-up.d/resolved: 2: /run/network/ifupdown-inet-ens13:
DOMAINS=marum.de: not found
Failed to parse DNS server address: DNS
Failed to set DNS configuration: Invalid argument
This happened to me on three different servers, so this is a serious bug
and should be fixed before 22.04 upgrades are allowed for everybody.
Most servers provided by data centers like Hetzner (Germany) are
configure like that. After a do-release-upgrade you have no working DNS
anymore, unless you disable systemd-resolved. I don't want to use
netplan, so changing to this is no option.
The fix is easy - remove the quotes in the script on the left side
"$DNS" => $DNS; same for DOMAINS:
if [ -n "$NEW_DNS" ]; then
cat <"$mystatedir/ifupdown-${ADDRFAM}-$interface"
$DNS="$NEW_DNS"
EOF
if [ -n "$NEW_DOMAINS" ]; then
cat <>"$mystatedir/ifupdown-${ADDRFAM}-$interface"
$DOMAINS="$NEW_DOMAINS"
EOF
fi
fi
** Affects: ifupdown (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ifupdown in Ubuntu.
https://bugs.launchpad.net/bugs/1981103
Title:
System with DNS server in /etc/network/interfaces has bogus systemd-
resolved config after upgrade to 22.04
Status in ifupdown package in Ubuntu:
New
Bug description:
Description:Ubuntu 22.04 LTS
Release:22.04
ifupdown:
Installed: 0.8.36+nmu1ubuntu3
Candidate: 0.8.36+nmu1ubuntu3
Version table:
*** 0.8.36+nmu1ubuntu3 500
500 http://de.archive.ubuntu.com/ubuntu jammy/universe amd64 Packages
100 /var/lib/dpkg/status
After upgrading a server with classic ifupdown configuration after
reboot the machine had no valid dns servers anymore.
The problem is that the state file created by ifupdown using
/etc/network/if-up.d/resolved looks like this:
root@pangaea-pm:~# cat /run/network/ifupdown-inet-ens13
"DNS"="134.102.20.20 134.102.200.14"
"DOMAINS"="marum.de"
The script later sources this file and causes the following errors,
easy to see when you execute this:
root@pangaea-pm:~# ifdown ens13; ifup ens13
/etc/network/if-down.d/resolved: 12: mystatedir: not found
/etc/network/if-up.d/resolved: 12: mystatedir: not found
/etc/network/if-up.d/resolved: 71: DNS: not found
/etc/network/if-up.d/resolved: 1: /run/network/ifupdown-inet-ens13:
DNS=134.102.20.20 134.102.200.14: not found
/etc/network/if-up.d/resolved: 2: /run/network/ifupdown-inet-ens13:
DOMAINS=marum.de: not found
Failed to parse DNS server address: DNS
Failed to set DNS configuration: Invalid argument
This happened to me on three different servers, so this is a serious
bug and should be fixed before 22.04 upgrades are allowed for
everybody. Most servers provided by data centers like Hetzner
(Germany) are configure like that. After a do-release-upgrade you have
no working DNS anymore, unless you disable systemd-resolved. I don't
want to use netplan, so changing to this is no option.
The fix is easy - remove the quotes in the script on the left side
"$DNS" => $DNS; same for DOMAINS:
if [ -n "$NEW_DNS" ]; then
cat <"$mystatedir/ifupdown-${ADDRFAM}-$interface"
$DNS="$NEW_DNS"
EOF
if [ -n "$NEW_DOMAINS" ]; then
cat <>"$mystatedir/ifupdown-${ADDRFAM}-$interface"
$DOMAINS="$NEW_DOMAINS"
EOF
fi
fi
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/1981103/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1950806] [NEW] package ufw 0.36-6ubuntu1 failed to install/upgrade: installed ufw package post-installation script subprocess returned error exit status 1
Public bug reported: No details ProblemType: Package DistroRelease: Ubuntu 20.04 Package: ufw 0.36-6ubuntu1 ProcVersionSignature: Ubuntu 5.8.0-55.62~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-55-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip Date: Fri Nov 12 15:00:27 2021 DuplicateSignature: package:ufw:0.36-6ubuntu1 Setting up ufw (0.36-6ubuntu1) ... [Errno 5] Input/output error dpkg: error processing package ufw (--configure): installed ufw package post-installation script subprocess returned error exit status 1 ErrorMessage: installed ufw package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2021-06-21 (143 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) PackageArchitecture: all Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.6 SourcePackage: ufw Title: package ufw 0.36-6ubuntu1 failed to install/upgrade: installed ufw package post-installation script subprocess returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: ufw (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package focal need-duplicate-check -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ufw in Ubuntu. https://bugs.launchpad.net/bugs/1950806 Title: package ufw 0.36-6ubuntu1 failed to install/upgrade: installed ufw package post-installation script subprocess returned error exit status 1 Status in ufw package in Ubuntu: New Bug description: No details ProblemType: Package DistroRelease: Ubuntu 20.04 Package: ufw 0.36-6ubuntu1 ProcVersionSignature: Ubuntu 5.8.0-55.62~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-55-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip Date: Fri Nov 12 15:00:27 2021 DuplicateSignature: package:ufw:0.36-6ubuntu1 Setting up ufw (0.36-6ubuntu1) ... [Errno 5] Input/output error dpkg: error processing package ufw (--configure): installed ufw package post-installation script subprocess returned error exit status 1 ErrorMessage: installed ufw package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2021-06-21 (143 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) PackageArchitecture: all Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.6 SourcePackage: ufw Title: package ufw 0.36-6ubuntu1 failed to install/upgrade: installed ufw package post-installation script subprocess returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ufw/+bug/1950806/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1899483] Re: long hang apt install mariadb-server on Ubuntu 20.04 server
After failed installation command 'service mysql start' hangs endless, but mysqlshow and mysql are working. $ ps -f -t pts/4 UID PIDPPID C STIME TTY TIME CMD root 107880 107877 0 12:46 pts/400:00:00 -bash root 125389 107880 0 13:01 pts/400:00:00 systemctl start mysql.service root 125396 125389 0 13:01 pts/400:00:00 /bin/systemd-tty-ask-password-agent --watch $ ps -f -u mysql mysql 125461 1 0 13:01 ?00:00:00 /usr/sbin/mysqld -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1899483 Title: long hang apt install mariadb-server on Ubuntu 20.04 server Status in apt package in Ubuntu: New Bug description: Ubuntu 20.04 server => no graphical user interface MariaDb is functional: mysqlshow works, mysqladmin create xxx works After 10 Minutes - the installation terminates - dbms terminates Oct 12 12:38:19 host systemd[1]: Starting MariaDB 10.3.22 database server... Oct 12 12:38:19 host mysqld[124254]: 2020-10-12 12:38:19 0 [Note] /usr/sbin/mysqld (mysqld 10.3.22-MariaDB-1ubuntu1) starting as process 124254 ... Oct 12 12:53:19 host systemd[1]: mariadb.service: start operation timed out. Terminating. Oct 12 12:53:20 host systemd[1]: mariadb.service: Failed with result 'timeout'. Oct 12 12:53:20 host systemd[1]: Failed to start MariaDB 10.3.22 database server. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: apt 2.0.2ubuntu0.1 ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60 Uname: Linux 5.4.0-48-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.9 Architecture: amd64 CasperMD5CheckResult: skip Date: Mon Oct 12 12:43:49 2020 ExecutablePath: /usr/bin/apt InstallationDate: Installed on 2020-05-11 (154 days ago) InstallationMedia: Ubuntu-Server 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) ProcEnviron: SHELL=/bin/bash LANG=en_US.UTF-8 TERM=xterm-256color PATH=(custom, no user) SourcePackage: apt UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1899483/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1899483] [NEW] long hang apt install mariadb-server on Ubuntu 20.04 server
Public bug reported: Ubuntu 20.04 server => no graphical user interface MariaDb is functional: mysqlshow works, mysqladmin create xxx works After 10 Minutes - the installation terminates - dbms terminates Oct 12 12:38:19 host systemd[1]: Starting MariaDB 10.3.22 database server... Oct 12 12:38:19 host mysqld[124254]: 2020-10-12 12:38:19 0 [Note] /usr/sbin/mysqld (mysqld 10.3.22-MariaDB-1ubuntu1) starting as process 124254 ... Oct 12 12:53:19 host systemd[1]: mariadb.service: start operation timed out. Terminating. Oct 12 12:53:20 host systemd[1]: mariadb.service: Failed with result 'timeout'. Oct 12 12:53:20 host systemd[1]: Failed to start MariaDB 10.3.22 database server. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: apt 2.0.2ubuntu0.1 ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60 Uname: Linux 5.4.0-48-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.9 Architecture: amd64 CasperMD5CheckResult: skip Date: Mon Oct 12 12:43:49 2020 ExecutablePath: /usr/bin/apt InstallationDate: Installed on 2020-05-11 (154 days ago) InstallationMedia: Ubuntu-Server 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) ProcEnviron: SHELL=/bin/bash LANG=en_US.UTF-8 TERM=xterm-256color PATH=(custom, no user) SourcePackage: apt UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: apt (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1899483 Title: long hang apt install mariadb-server on Ubuntu 20.04 server Status in apt package in Ubuntu: New Bug description: Ubuntu 20.04 server => no graphical user interface MariaDb is functional: mysqlshow works, mysqladmin create xxx works After 10 Minutes - the installation terminates - dbms terminates Oct 12 12:38:19 host systemd[1]: Starting MariaDB 10.3.22 database server... Oct 12 12:38:19 host mysqld[124254]: 2020-10-12 12:38:19 0 [Note] /usr/sbin/mysqld (mysqld 10.3.22-MariaDB-1ubuntu1) starting as process 124254 ... Oct 12 12:53:19 host systemd[1]: mariadb.service: start operation timed out. Terminating. Oct 12 12:53:20 host systemd[1]: mariadb.service: Failed with result 'timeout'. Oct 12 12:53:20 host systemd[1]: Failed to start MariaDB 10.3.22 database server. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: apt 2.0.2ubuntu0.1 ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60 Uname: Linux 5.4.0-48-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.9 Architecture: amd64 CasperMD5CheckResult: skip Date: Mon Oct 12 12:43:49 2020 ExecutablePath: /usr/bin/apt InstallationDate: Installed on 2020-05-11 (154 days ago) InstallationMedia: Ubuntu-Server 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) ProcEnviron: SHELL=/bin/bash LANG=en_US.UTF-8 TERM=xterm-256color PATH=(custom, no user) SourcePackage: apt UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1899483/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1864689] Re: openssl in 20.04 can't connect to site that was fine in 19.10 and is fine in Chrome and Firefox
This bug affects me too, with a client certificate that now "magically"
does not match the requirements.
Ironically, the error message says only:
OpenSSL error error:140AB18E:SSL routines:SSL_CTX_use_certificate:ca md
too weak, (no key found, wrong pass phrase, or wrong file format?)
although there was no MD5 signature involved at all. So, even when you
know that with OpenSSL 1.1, an "SSL security level" has been introduced,
and that Ubuntu has set that level to 2, it is hard to find that it
deprecates SHA1 now (see
https://www.openssl.org/docs/manmaster/man3/SSL_CTX_set_security_level.html).
Thus, even for more knowledgable people than me this is a major hassle
to find and/or fix. I wonder why Ubuntu has chosen to raise the level
that high considering that the documentation page contains a clear
warning indication:
"WARNING at this time setting the security level higher than 1 for
general internet use is likely to cause considerable interoperability
issues and is not recommended. This is because the SHA1 algorithm is
very widely used in certificates and will be rejected at levels higher
than 1 because it only offers 80 bits of security."
I think that this is an extremely unwise choice for an OS to make.
That being said, here is the fix (also hard to find):
In /etc/ssl/openssl.cnf, add this line before the start of the file:
openssl_conf = default_conf
At the end of the file, add these lines:
[default_conf]
ssl_conf = ssl_sect
[ssl_sect]
system_default = system_default_sect
[system_default_sect]
CipherString = DEFAULT:@SECLEVEL=1
This will bring down the SSL security level to the former level of 1.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssl in Ubuntu.
https://bugs.launchpad.net/bugs/1864689
Title:
openssl in 20.04 can't connect to site that was fine in 19.10 and is
fine in Chrome and Firefox
Status in OpenSSL:
Unknown
Status in openssl package in Ubuntu:
Confirmed
Bug description:
openssl in Ubuntu 20.04 (focal) refuses to connect to a web site that
openssl in Ubuntu 19.10 (eoan), Chrome, and Firefox are all happy to
connect to.
Reproduce with: `curl -v https://www.toodledo.com/'
or: `openssl s_client -connect www.toodledo.com:443`
or: `python3 -c 'import requests;
requests.get("https://www.toodledo.com/";)'`
or: `wget https://www.toodledo.com/`
These worked in Ubuntu 19.10 and don't work in 20.04.
I've tried all sorts of things to debug this further and I've just run
into walls. I hope someone who understands more about this stuff will
be able to figure it out.
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: openssl 1.1.1d-2ubuntu3
ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18
Uname: Linux 5.4.0-14-generic x86_64
ApportVersion: 2.20.11-0ubuntu18
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Tue Feb 25 13:01:22 2020
InstallationDate: Installed on 2019-08-16 (192 days ago)
InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
SourcePackage: openssl
UpgradeStatus: Upgraded to focal on 2020-01-31 (25 days ago)
To manage notifications about this bug go to:
https://bugs.launchpad.net/openssl/+bug/1864689/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1872443] Re: /etc/securetty missing: dovecot not working
I cannot tell if this is a problem in whatever version of Debian, since I do not use it. Even with Ubuntu being derived from Debian at some point between 18.04 where /etc/securetty was delivered with package login and 20.04 where the whole package is unavailable. I think that is an interdependence between multiple packages, but I am not quite in the position to point at where (or even if) the problem could be fixed in Debian. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to shadow in Ubuntu. https://bugs.launchpad.net/bugs/1872443 Title: /etc/securetty missing: dovecot not working Status in shadow package in Ubuntu: New Bug description: With Ubuntu 20.04 Focal Fossa, /etc/securetty is missing from the "login" package (4.8.1-1ubuntu4). This leads to errors such as in /var/log/mail.log when a dovecot auth is tried: Apr 13 13:08:17 venus dovecot[10588]: imap-login: Login: user=, method=PLAIN, rip=192.168.123.1, lip=192.168.123.188, mpid=12200, TLS, TLSv1.2 with cipher ECDHE-E CDSA-AES256-GCM-SHA384 (256/256 bits) Apr 13 13:08:18 venus auth[12195]: pam_unix(dovecot:auth): Couldn't open /etc/secure tty: No such file or directory Apr 13 13:08:18 venus auth[12195]: pam_unix(dovecot:auth): Couldn't open /etc/secure tty: No such file or directory Apr 13 13:08:18 venus dovecot[10588]: imap-login: Login: user=, method=PLAIN, rip=192.168.123.1, lip=192.168.123.188, mpid=12202, TLS, TLSv1.2 with cipher ECDHE-E CDSA-AES256-GCM-SHA384 (256/256 bits) It seems that pam_unix still needs /etc/securetty, but login no longer provides it. There was a similar bug in debian that seems to be related: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=931899 To my understanding, this is a problem between pam and login packages in 20.04. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/shadow/+bug/1872443/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1872443] Re: /etc/securetty missing: dovecot not working
At least, in 18.04, the file /etc/securetty was in package login... -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to shadow in Ubuntu. https://bugs.launchpad.net/bugs/1872443 Title: /etc/securetty missing: dovecot not working Status in shadow package in Ubuntu: New Bug description: With Ubuntu 20.04 Focal Fossa, /etc/securetty is missing from the "login" package (4.8.1-1ubuntu4). This leads to errors such as in /var/log/mail.log when a dovecot auth is tried: Apr 13 13:08:17 venus dovecot[10588]: imap-login: Login: user=, method=PLAIN, rip=192.168.123.1, lip=192.168.123.188, mpid=12200, TLS, TLSv1.2 with cipher ECDHE-E CDSA-AES256-GCM-SHA384 (256/256 bits) Apr 13 13:08:18 venus auth[12195]: pam_unix(dovecot:auth): Couldn't open /etc/secure tty: No such file or directory Apr 13 13:08:18 venus auth[12195]: pam_unix(dovecot:auth): Couldn't open /etc/secure tty: No such file or directory Apr 13 13:08:18 venus dovecot[10588]: imap-login: Login: user=, method=PLAIN, rip=192.168.123.1, lip=192.168.123.188, mpid=12202, TLS, TLSv1.2 with cipher ECDHE-E CDSA-AES256-GCM-SHA384 (256/256 bits) It seems that pam_unix still needs /etc/securetty, but login no longer provides it. There was a similar bug in debian that seems to be related: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=931899 To my understanding, this is a problem between pam and login packages in 20.04. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/shadow/+bug/1872443/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1872443] [NEW] /etc/securetty missing: dovecot not working
Public bug reported: With Ubuntu 20.04 Focal Fossa, /etc/securetty is missing from the "login" package (4.8.1-1ubuntu4). This leads to errors such as in /var/log/mail.log when a dovecot auth is tried: Apr 13 13:08:17 venus dovecot[10588]: imap-login: Login: user=, method=PLAIN, rip=192.168.123.1, lip=192.168.123.188, mpid=12200, TLS, TLSv1.2 with cipher ECDHE-E CDSA-AES256-GCM-SHA384 (256/256 bits) Apr 13 13:08:18 venus auth[12195]: pam_unix(dovecot:auth): Couldn't open /etc/secure tty: No such file or directory Apr 13 13:08:18 venus auth[12195]: pam_unix(dovecot:auth): Couldn't open /etc/secure tty: No such file or directory Apr 13 13:08:18 venus dovecot[10588]: imap-login: Login: user=, method=PLAIN, rip=192.168.123.1, lip=192.168.123.188, mpid=12202, TLS, TLSv1.2 with cipher ECDHE-E CDSA-AES256-GCM-SHA384 (256/256 bits) It seems that pam_unix still needs /etc/securetty, but login no longer provides it. There was a similar bug in debian that seems to be related: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=931899 To my understanding, this is a problem between pam and login packages in 20.04. ** Affects: shadow (Ubuntu) Importance: Undecided Status: New ** Tags: dovecot login pam securetty -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to shadow in Ubuntu. https://bugs.launchpad.net/bugs/1872443 Title: /etc/securetty missing: dovecot not working Status in shadow package in Ubuntu: New Bug description: With Ubuntu 20.04 Focal Fossa, /etc/securetty is missing from the "login" package (4.8.1-1ubuntu4). This leads to errors such as in /var/log/mail.log when a dovecot auth is tried: Apr 13 13:08:17 venus dovecot[10588]: imap-login: Login: user=, method=PLAIN, rip=192.168.123.1, lip=192.168.123.188, mpid=12200, TLS, TLSv1.2 with cipher ECDHE-E CDSA-AES256-GCM-SHA384 (256/256 bits) Apr 13 13:08:18 venus auth[12195]: pam_unix(dovecot:auth): Couldn't open /etc/secure tty: No such file or directory Apr 13 13:08:18 venus auth[12195]: pam_unix(dovecot:auth): Couldn't open /etc/secure tty: No such file or directory Apr 13 13:08:18 venus dovecot[10588]: imap-login: Login: user=, method=PLAIN, rip=192.168.123.1, lip=192.168.123.188, mpid=12202, TLS, TLSv1.2 with cipher ECDHE-E CDSA-AES256-GCM-SHA384 (256/256 bits) It seems that pam_unix still needs /etc/securetty, but login no longer provides it. There was a similar bug in debian that seems to be related: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=931899 To my understanding, this is a problem between pam and login packages in 20.04. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/shadow/+bug/1872443/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1867784] Re: "systemctl status ..." in Focal does not show any process output
Never mind. My fault. The journal was gone, so nothing could be shown. ** Changed in: systemd (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1867784 Title: "systemctl status ..." in Focal does not show any process output Status in systemd package in Ubuntu: Invalid Bug description: Software versions: # lsb_release -rd Description:Ubuntu Focal Fossa (development branch) Release:20.04 # apt-cache policy systemd systemd: Installed: 244.3-1ubuntu1 Candidate: 244.3-1ubuntu1 Version table: *** 244.3-1ubuntu1 500 500 http://de.archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status When I issue "systemctl status apache2" (or for any other service for that matter) in Focal, the last few lines of output are not shown any more: # systemctl status apache2 ● apache2.service - The Apache HTTP Server Loaded: loaded (/lib/systemd/system/apache2.service; enabled; vendor prese> Drop-In: /etc/systemd/system/apache2.service.d └─override.conf Active: active (running) since Tue 2020-03-17 13:34:42 CET; 1h 43min ago Docs: https://httpd.apache.org/docs/2.4/ Main PID: 283994 (apache2) Tasks: 55 (limit: 9451) Memory: 27.3M CGroup: /system.slice/apache2.service ├─283994 /usr/sbin/apache2 -k start ├─283997 /usr/sbin/apache2 -k start └─283998 /usr/sbin/apache2 -k start # With Bionic (18.04), the last few log lines were shown as described in the systemctl man page: #systemctl status apache2 ● apache2.service - The Apache HTTP Server Loaded: loaded (/lib/systemd/system/apache2.service; enabled; vendor preset: enab Drop-In: /lib/systemd/system/apache2.service.d └─apache2-systemd.conf /etc/systemd/system/apache2.service.d └─override.conf Active: active (running) since Tue 2020-03-03 23:01:13 CET; 1 weeks 6 days ago Process: 1255 ExecReload=/usr/sbin/apachectl graceful (code=exited, status=0/SUCCE Main PID: 11522 (/usr/sbin/apach) Tasks: 15 (limit: 4915) CGroup: /system.slice/apache2.service ├─ 1280 /usr/sbin/apache2 -k start ├─ 6459 /usr/sbin/apache2 -k start └─11522 /usr/sbin/apache2 -k start Mar 13 06:25:27 fatty.xy.de systemd[1]: Reloading The Apache HTTP Server. Mar 13 06:25:27 fatty.xy.de systemd[1]: Reloaded The Apache HTTP Server. Mar 14 06:25:27 fatty.xy.de systemd[1]: Reloading The Apache HTTP Server. Mar 14 06:25:27 fatty.xy.de systemd[1]: Reloaded The Apache HTTP Server. Mar 15 06:25:27 fatty.xy.de systemd[1]: Reloading The Apache HTTP Server. Mar 15 06:25:27 fatty.xy.de systemd[1]: Reloaded The Apache HTTP Server. Mar 16 06:25:28 fatty.xy.de systemd[1]: Reloading The Apache HTTP Server. Mar 16 06:25:28 fatty.xy.de systemd[1]: Reloaded The Apache HTTP Server. Mar 17 06:25:27 fatty.xy.de systemd[1]: Reloading The Apache HTTP Server. Mar 17 06:25:27 fatty.xy.de systemd[1]: Reloaded The Apache HTTP Server. # I do not know if this was an upstream systemd change, however it seems wrong. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1867784/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1867784] [NEW] "systemctl status ..." in Focal does not show any process output
Public bug reported: Software versions: # lsb_release -rd Description:Ubuntu Focal Fossa (development branch) Release:20.04 # apt-cache policy systemd systemd: Installed: 244.3-1ubuntu1 Candidate: 244.3-1ubuntu1 Version table: *** 244.3-1ubuntu1 500 500 http://de.archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status When I issue "systemctl status apache2" (or for any other service for that matter) in Focal, the last few lines of output are not shown any more: # systemctl status apache2 ● apache2.service - The Apache HTTP Server Loaded: loaded (/lib/systemd/system/apache2.service; enabled; vendor prese> Drop-In: /etc/systemd/system/apache2.service.d └─override.conf Active: active (running) since Tue 2020-03-17 13:34:42 CET; 1h 43min ago Docs: https://httpd.apache.org/docs/2.4/ Main PID: 283994 (apache2) Tasks: 55 (limit: 9451) Memory: 27.3M CGroup: /system.slice/apache2.service ├─283994 /usr/sbin/apache2 -k start ├─283997 /usr/sbin/apache2 -k start └─283998 /usr/sbin/apache2 -k start # With Bionic (18.04), the last few log lines were shown as described in the systemctl man page: #systemctl status apache2 ● apache2.service - The Apache HTTP Server Loaded: loaded (/lib/systemd/system/apache2.service; enabled; vendor preset: enab Drop-In: /lib/systemd/system/apache2.service.d └─apache2-systemd.conf /etc/systemd/system/apache2.service.d └─override.conf Active: active (running) since Tue 2020-03-03 23:01:13 CET; 1 weeks 6 days ago Process: 1255 ExecReload=/usr/sbin/apachectl graceful (code=exited, status=0/SUCCE Main PID: 11522 (/usr/sbin/apach) Tasks: 15 (limit: 4915) CGroup: /system.slice/apache2.service ├─ 1280 /usr/sbin/apache2 -k start ├─ 6459 /usr/sbin/apache2 -k start └─11522 /usr/sbin/apache2 -k start Mar 13 06:25:27 fatty.xy.de systemd[1]: Reloading The Apache HTTP Server. Mar 13 06:25:27 fatty.xy.de systemd[1]: Reloaded The Apache HTTP Server. Mar 14 06:25:27 fatty.xy.de systemd[1]: Reloading The Apache HTTP Server. Mar 14 06:25:27 fatty.xy.de systemd[1]: Reloaded The Apache HTTP Server. Mar 15 06:25:27 fatty.xy.de systemd[1]: Reloading The Apache HTTP Server. Mar 15 06:25:27 fatty.xy.de systemd[1]: Reloaded The Apache HTTP Server. Mar 16 06:25:28 fatty.xy.de systemd[1]: Reloading The Apache HTTP Server. Mar 16 06:25:28 fatty.xy.de systemd[1]: Reloaded The Apache HTTP Server. Mar 17 06:25:27 fatty.xy.de systemd[1]: Reloading The Apache HTTP Server. Mar 17 06:25:27 fatty.xy.de systemd[1]: Reloaded The Apache HTTP Server. # I do not know if this was an upstream systemd change, however it seems wrong. ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Tags: focal status systemd -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1867784 Title: "systemctl status ..." in Focal does not show any process output Status in systemd package in Ubuntu: New Bug description: Software versions: # lsb_release -rd Description:Ubuntu Focal Fossa (development branch) Release:20.04 # apt-cache policy systemd systemd: Installed: 244.3-1ubuntu1 Candidate: 244.3-1ubuntu1 Version table: *** 244.3-1ubuntu1 500 500 http://de.archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status When I issue "systemctl status apache2" (or for any other service for that matter) in Focal, the last few lines of output are not shown any more: # systemctl status apache2 ● apache2.service - The Apache HTTP Server Loaded: loaded (/lib/systemd/system/apache2.service; enabled; vendor prese> Drop-In: /etc/systemd/system/apache2.service.d └─override.conf Active: active (running) since Tue 2020-03-17 13:34:42 CET; 1h 43min ago Docs: https://httpd.apache.org/docs/2.4/ Main PID: 283994 (apache2) Tasks: 55 (limit: 9451) Memory: 27.3M CGroup: /system.slice/apache2.service ├─283994 /usr/sbin/apache2 -k start ├─283997 /usr/sbin/apache2 -k start └─283998 /usr/sbin/apache2 -k start # With Bionic (18.04), the last few log lines were shown as described in the systemctl man page: #systemctl status apache2 ● apache2.service - The Apache HTTP Server Loaded: loaded (/lib/systemd/system/apache2.service; enabled; vendor preset: enab Drop-In: /lib/systemd/system/apache2.service.d └─apache2-systemd.conf /etc/systemd/system/apache2.service.d └─override.conf Active: active (running) since Tue 2020-03-03 23:01:13 CET; 1 weeks 6 days ago Process: 1255 ExecReload=/usr/sbin/apachectl graceful (code=exited,
[Touch-packages] [Bug 1865204] Re: Multiple packages broke with openssl 1.1.1 upgrade
** Description changed: While I welcome the adding of security features by upgrading vital packages like openssl, there are at least two packages that I know of which ran fine with libssl 1.1.0 and do not with libssl 1.1.1. This bug has been introduced with the migration from openssl 1.1.0 to 1.1.1 in one of the last point releases. - 1. stunnel4 3:5.44-1ubuntu3 stunnel4 breaks with openssl 1.1.1 (which supports TLS 1.3). I get errors when a Windows stunnel client connects to the stunnel4 daemon: Feb 20 14:10:03 peterpan.neverland stunnel[24427]: LOG3[0]: s_connect: connect ::1:3128 : Connection refused (111) This can be fixed when I manually add "MaxProtocol = TLSv1.2" to /etc/ssl/openssl.conf, showing that TLS 1.3 introduced by openssl 1.1.1 is the culprit. stunnel4 needs an update. At least for stunnel4, another fix would be to specify "sslVersion = TLSv1.2" in its config file. - 2. pure-ftpd 1.0.46-1build1 Same thing here. You cannot connect once you use "tls=2" or higher if openssl 1.1.1 with TLS 1.3 is active. Only fix here I found is to limit - the max protocol. pure-ftpd itself has no means of solving that problem, - at least not in the bionic version. + the max protocol in openssl for all applications. pure-ftpd itself has + no means of controlling the TLS version, at least not in the bionic + version of it. + + I use Ubuntu Server 18.04.04 LTS, BTW and openssl was + 1.1.1-1ubuntu2.1~18.04.5. - I use Ubuntu Server 18.04.04 LTS, BTW and openssl was 1.1.1-1ubuntu2.1~18.04.5. + Both problems could be fixed by backporting stunnel4 and pure-ftpd packages from Focal Fossa. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssl in Ubuntu. https://bugs.launchpad.net/bugs/1865204 Title: Multiple packages broke with openssl 1.1.1 upgrade Status in openssl package in Ubuntu: New Bug description: While I welcome the adding of security features by upgrading vital packages like openssl, there are at least two packages that I know of which ran fine with libssl 1.1.0 and do not with libssl 1.1.1. This bug has been introduced with the migration from openssl 1.1.0 to 1.1.1 in one of the last point releases. 1. stunnel4 3:5.44-1ubuntu3 stunnel4 breaks with openssl 1.1.1 (which supports TLS 1.3). I get errors when a Windows stunnel client connects to the stunnel4 daemon: Feb 20 14:10:03 peterpan.neverland stunnel[24427]: LOG3[0]: s_connect: connect ::1:3128 : Connection refused (111) This can be fixed when I manually add "MaxProtocol = TLSv1.2" to /etc/ssl/openssl.conf, showing that TLS 1.3 introduced by openssl 1.1.1 is the culprit. stunnel4 needs an update. At least for stunnel4, another fix would be to specify "sslVersion = TLSv1.2" in its config file. 2. pure-ftpd 1.0.46-1build1 Same thing here. You cannot connect once you use "tls=2" or higher if openssl 1.1.1 with TLS 1.3 is active. Only fix here I found is to limit the max protocol in openssl for all applications. pure-ftpd itself has no means of controlling the TLS version, at least not in the bionic version of it. I use Ubuntu Server 18.04.04 LTS, BTW and openssl was 1.1.1-1ubuntu2.1~18.04.5. Both problems could be fixed by backporting stunnel4 and pure-ftpd packages from Focal Fossa. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1865204/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1865204] [NEW] Multiple packages broke with openssl 1.1.1 upgrade
Public bug reported: While I welcome the adding of security features by upgrading vital packages like openssl, there are at least two packages that I know of which ran fine with libssl 1.1.0 and do not with libssl 1.1.1. This bug has been introduced with the migration from openssl 1.1.0 to 1.1.1 in one of the last point releases. 1. stunnel4 3:5.44-1ubuntu3 stunnel4 breaks with openssl 1.1.1 (which supports TLS 1.3). I get errors when a Windows stunnel client connects to the stunnel4 daemon: Feb 20 14:10:03 peterpan.neverland stunnel[24427]: LOG3[0]: s_connect: connect ::1:3128 : Connection refused (111) This can be fixed when I manually add "MaxProtocol = TLSv1.2" to /etc/ssl/openssl.conf, showing that TLS 1.3 introduced by openssl 1.1.1 is the culprit. stunnel4 needs an update. At least for stunnel4, another fix would be to specify "sslVersion = TLSv1.2" in its config file. 2. pure-ftpd 1.0.46-1build1 Same thing here. You cannot connect once you use "tls=2" or higher if openssl 1.1.1 with TLS 1.3 is active. Only fix here I found is to limit the max protocol. pure-ftpd itself has no means of solving that problem, at least not in the bionic version. I use Ubuntu Server 18.04.04 LTS, BTW and openssl was 1.1.1-1ubuntu2.1~18.04.5. ** Affects: openssl (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssl in Ubuntu. https://bugs.launchpad.net/bugs/1865204 Title: Multiple packages broke with openssl 1.1.1 upgrade Status in openssl package in Ubuntu: New Bug description: While I welcome the adding of security features by upgrading vital packages like openssl, there are at least two packages that I know of which ran fine with libssl 1.1.0 and do not with libssl 1.1.1. This bug has been introduced with the migration from openssl 1.1.0 to 1.1.1 in one of the last point releases. 1. stunnel4 3:5.44-1ubuntu3 stunnel4 breaks with openssl 1.1.1 (which supports TLS 1.3). I get errors when a Windows stunnel client connects to the stunnel4 daemon: Feb 20 14:10:03 peterpan.neverland stunnel[24427]: LOG3[0]: s_connect: connect ::1:3128 : Connection refused (111) This can be fixed when I manually add "MaxProtocol = TLSv1.2" to /etc/ssl/openssl.conf, showing that TLS 1.3 introduced by openssl 1.1.1 is the culprit. stunnel4 needs an update. At least for stunnel4, another fix would be to specify "sslVersion = TLSv1.2" in its config file. 2. pure-ftpd 1.0.46-1build1 Same thing here. You cannot connect once you use "tls=2" or higher if openssl 1.1.1 with TLS 1.3 is active. Only fix here I found is to limit the max protocol. pure-ftpd itself has no means of solving that problem, at least not in the bionic version. I use Ubuntu Server 18.04.04 LTS, BTW and openssl was 1.1.1-1ubuntu2.1~18.04.5. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1865204/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1850041] [NEW] Susystemd-analyze blame returns "Bootup is not yet finished"
Public bug reported: Every time I run systemd-analyze blame, I get the message: Bootup is not yet finished (org.freedesktop.systemd1.Manager.FinishTimestampMonotonic=0). Please try again later. This, even if my laptop is on for several hours. Running systemctl list-jobs, returns: JOB UNIT TYPE STATE 1 graphical.target start waiting 95 systemd-update-utmp-runlevel.service start waiting 89 system-getty.slice start waiting 87 getty.target start waiting 21 setvtrgb.service start waiting 112 plymouth-quit-wait.service start running 88 getty@tty1.service start waiting 2 multi-user.targetstart waiting Boot time is about 90 seconds, before and after upgrading from 19.04 to 19.10. All applications start and run normally. My system is Ubuntu Budgie 19.10, working on a Dell Inspiron Laptop. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: systemd 242-7ubuntu3 ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1 Uname: Linux 5.3.0-19-generic x86_64 ApportVersion: 2.20.11-0ubuntu8 Architecture: amd64 CurrentDesktop: Budgie:GNOME Date: Sun Oct 27 09:54:26 2019 MachineType: Dell Inc. Inspiron 3421 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-19-generic root=UUID=2b7d5523-743f-465d-a24c-fadc4a3aa0f4 ro quiet splash vt.handoff=7 SourcePackage: systemd SystemdDelta: [EXTENDED] /lib/systemd/system/rc-local.service → /lib/systemd/system/rc-local.service.d/debian.conf [EXTENDED] /lib/systemd/system/systemd-timesyncd.service → /lib/systemd/system/systemd-timesyncd.service.d/disable-with-time-daemon.conf [EXTENDED] /lib/systemd/system/user@.service → /lib/systemd/system/user@.service.d/timeout.conf 3 overridden configuration files found. UpgradeStatus: Upgraded to eoan on 2019-10-23 (3 days ago) dmi.bios.date: 11/30/2012 dmi.bios.vendor: Dell Inc. dmi.bios.version: A02 dmi.board.vendor: Dell Inc. dmi.board.version: A02 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvrA02:bd11/30/2012:svnDellInc.:pnInspiron3421:pvrNotSpecified:rvnDellInc.:rn:rvrA02:cvnDellInc.:ct8:cvrNotSpecified: dmi.product.name: Inspiron 3421 dmi.product.sku: To be filled by O.E.M. dmi.product.version: Not Specified dmi.sys.vendor: Dell Inc. ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug eoan -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1850041 Title: Susystemd-analyze blame returns "Bootup is not yet finished" Status in systemd package in Ubuntu: New Bug description: Every time I run systemd-analyze blame, I get the message: Bootup is not yet finished (org.freedesktop.systemd1.Manager.FinishTimestampMonotonic=0). Please try again later. This, even if my laptop is on for several hours. Running systemctl list-jobs, returns: JOB UNIT TYPE STATE 1 graphical.target start waiting 95 systemd-update-utmp-runlevel.service start waiting 89 system-getty.slice start waiting 87 getty.target start waiting 21 setvtrgb.service start waiting 112 plymouth-quit-wait.service start running 88 getty@tty1.service start waiting 2 multi-user.targetstart waiting Boot time is about 90 seconds, before and after upgrading from 19.04 to 19.10. All applications start and run normally. My system is Ubuntu Budgie 19.10, working on a Dell Inspiron Laptop. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: systemd 242-7ubuntu3 ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1 Uname: Linux 5.3.0-19-generic x86_64 ApportVersion: 2.20.11-0ubuntu8 Architecture: amd64 CurrentDesktop: Budgie:GNOME Date: Sun Oct 27 09:54:26 2019 MachineType: Dell Inc. Inspiron 3421 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-19-generic root=UUID=2b7d5523-743f-465d-a24c-fadc4a3aa0f4 ro quiet splash vt.handoff=7 SourcePackage: systemd SystemdDelta: [EXTENDED] /lib/systemd/system/rc-local.service → /lib/systemd/system/rc-local.service.d/debian.conf [EXTENDED] /lib/systemd/system/systemd-timesyncd.service → /lib/systemd/system/systemd-timesyncd.service.d/disable-with-time-daemon.conf [EXTENDED] /lib/systemd/system/user@.service → /lib/systemd/system/user@.service.d/timeout.conf 3 overridden configuration files found. UpgradeStatus: Upgraded to eoan on 2019-10-23 (3 days ago) dmi.bios.date: 11/30/2012 dmi.bios.vendor: Dell Inc. dmi.bios.version: A02 dmi.board.vendor: Dell Inc. dmi.board.version
[Touch-packages] [Bug 1799647] Re: Patch: Add configuration for german provider winSIM
Submitted upstream: https://gitlab.gnome.org/GNOME/mobile-broadband-provider-info/merge_requests/7 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mobile-broadband-provider- info in Ubuntu. https://bugs.launchpad.net/bugs/1799647 Title: Patch: Add configuration for german provider winSIM Status in mobile-broadband-provider-info package in Ubuntu: New Bug description: I was unable to contribute a patch to the upstream gnome package: https://wiki.gnome.org/Projects/NetworkManager/MobileBroadband/ServiceProviders (They seem to have migrated their git servers away) I still think this little config change adds value to Ubuntu users, hence I am opening this issue. Find the patchfile attached. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mobile-broadband-provider-info/+bug/1799647/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1797386] Re: [SRU] OpenSSL 1.1.1 to 18.04 LTS
Hi, good idea in theory, but I want to add my 2cents: Please coordinate this update with ALL affected packages, like apache2 and nginx. My reason is: I just tried the PPA and found that nginx works with TLS 1.3 after that right out of the box. HOWEVER, there is a problem: openssl 1.1.1 has changed the way the cipher suites are configured - the ones for TLS 1.3 are configured separately, see here: https://github.com/openssl/openssl/commit/f865b08143b453962ad4afccd69e698d13c60f77 Nginx on the other hand has chosen to not support that new configuration at all, see: https://trac.nginx.org/nginx/ticket/1529 That means that the predefined order of TLS 1.3 is: TLS_AES_256_GCM_SHA384:TLS_CHACHA20_POLY1305_SHA256:TLS_AES_128_GCM_SHA256 and cannot be changed - it took me hours to find that out since the Nginx 1.15 documentation does not tell you that the TLS 1.3 ciphers cannot be changed by ssl_ciphers, but are silently ignored. The default set and order of ciphersuites may suit your needs or not - matter-of-fact it makes my SSLLabs score worse because of the AES128 cipher used. I have tried to apply othe defaults in /etc/ssl/openssl.conf but they do not seem to work for nginx. Neither could I just disable TLS 1.3 in order to restore the old behaviour other than to restore OpenSSL 1.1.0 by using "ppa-purge ppa:ci-train-ppa- service/3473". King regards, Uwe ** Bug watch added: trac.nginx.org/nginx/ #1529 http://trac.nginx.org/nginx/ticket/1529 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssl in Ubuntu. https://bugs.launchpad.net/bugs/1797386 Title: [SRU] OpenSSL 1.1.1 to 18.04 LTS Status in openssl package in Ubuntu: In Progress Status in libio-socket-ssl-perl source package in Bionic: New Status in libnet-ssleay-perl source package in Bionic: New Status in nova source package in Bionic: New Status in openssl source package in Bionic: New Status in python-cryptography source package in Bionic: New Status in python2.7 source package in Bionic: New Status in python3.6 source package in Bionic: New Status in python3.7 source package in Bionic: New Status in r-cran-openssl source package in Bionic: Fix Committed Status in ruby-openssl source package in Bionic: Fix Committed Status in ruby2.5 source package in Bionic: New Bug description: [Impact] * OpenSSL 1.1.1 is an LTS release upstream, which will continue to receive security support for much longer than 1.1.0 series will. * OpenSSL 1.1.1 comes with support for TLS v1.3 which is expected to be rapidly adopted due to increased set of supported hashes & algoes, as well as improved handshake [re-]negotiation. * OpenSSL 1.1.1 comes with improved hw-acceleration capabilities. * OpenSSL 1.1.1 is ABI/API compatible with 1.1.0, however some software is sensitive to the negotiation handshake and may either need patches/improvements or clamp-down to maximum v1.2. [Test Case] * Rebuild all reverse dependencies * Execute autopkg tests for all of them * Clamp down to TLS v1.2 software that does not support TLS v1.3 (e.g. mongodb) * Backport TLS v1.3 support patches, where applicable [Regression Potential] * Connectivity interop is the biggest issues which will be unavoidable with introducing TLS v1.3. However, tests on cosmic demonstrate that curl/nginx/google-chrome/mozilla-firefox connect and negotiate TLS v1.3 without issues. * Mitigation of discovered connectivity issues will be possible by clamping down to TLS v1.2 in either server-side or client-side software or by backporting relevant support fixes * Notable changes are listed here https://wiki.openssl.org/index.php/TLS1.3 * Most common connectivity issues so far: - client verifies SNI in TLSv1.3 mode, yet client doesn't set hostname. Solution is client change to set hostname, or to clamp down the client to TLSv1.2. - session negotiation is different in TLSv1.3, existing client code may fail to create/negotiate/resume session. Clients need to learn how to use session callback. * This update bundles python 3.6 and 3.7 point releases [Other Info] * Previous FFe for OpenSSL in 18.10 is at https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1793092 * TLS v1.3 support in NSS is expected to make it to 18.04 via security updates * TLS v1.3 support in GnuTLS is expected to be available in 19.04 * Test OpenSSL is being prepared in https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/3473 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1797386/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1808703] [NEW] Prgram does not run
Public bug reported: it just does nothing: MyTV TorBrowser ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-42.45-generic 4.15.18 Uname: Linux 4.15.0-42-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CompositorRunning: None Date: Sun Dec 16 17:46:25 2018 DistUpgraded: 2018-09-04 18:34:54,728 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py (g-exec-error-quark: Kindprozess »./xorg_fix_proprietary.py« konnte nicht ausgeführt werden (Datei oder Verzeichnis nicht gefunden) (8)) DistroCodename: bionic DistroVariant: ubuntu GraphicsCard: NVIDIA Corporation G96 [GeForce 9400 GT] [10de:0641] (rev a1) (prog-if 00 [VGA controller]) Subsystem: CardExpert Technology G96 [GeForce 9400 GT] [10b0:1401] InstallationDate: Installed on 2017-07-27 (507 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) ProcEnviron: PATH=(custom, no user) LANG=de_DE.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-42-generic root=UUID=b1da7b88-5409-4c35-9eb1-b8d5eccfc1ad ro plymouth:debug drm.debug=0xe quiet splash SourcePackage: xorg UpgradeStatus: Upgraded to bionic on 2018-09-04 (103 days ago) dmi.bios.date: 05/18/2009 dmi.bios.vendor: Intel Corp. dmi.bios.version: PRG3110H.86A.0066.2009.0518.1206 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: DG31PR dmi.board.vendor: Intel Corporation dmi.board.version: AAD97573-306 dmi.chassis.type: 3 dmi.modalias: dmi:bvnIntelCorp.:bvrPRG3110H.86A.0066.2009.0518.1206:bd05/18/2009:svn:pn:pvr:rvnIntelCorporation:rnDG31PR:rvrAAD97573-306:cvn:ct3:cvr: version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 xserver.bootTime: Sat Feb 17 20:02:16 2018 xserver.configfile: default xserver.errors: Failed to load module "nvidia" (module does not exist, 0) Failed to load module "nvidia" (module does not exist, 0) xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.18.4-0ubuntu0.7 xserver.video_driver: nouveau ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic ubuntu -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1808703 Title: Prgram does not run Status in xorg package in Ubuntu: New Bug description: it just does nothing: MyTV TorBrowser ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-42.45-generic 4.15.18 Uname: Linux 4.15.0-42-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CompositorRunning: None Date: Sun Dec 16 17:46:25 2018 DistUpgraded: 2018-09-04 18:34:54,728 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py (g-exec-error-quark: Kindprozess »./xorg_fix_proprietary.py« konnte nicht ausgeführt werden (Datei oder Verzeichnis nicht gefunden) (8)) DistroCodename: bionic DistroVariant: ubuntu GraphicsCard: NVIDIA Corporation G96 [GeForce 9400 GT] [10de:0641] (rev a1) (prog-if 00 [VGA controller]) Subsystem: CardExpert Technology G96 [GeForce 9400 GT] [10b0:1401] InstallationDate: Installed on 2017-07-27 (507 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) ProcEnviron: PATH=(custom, no user) LANG=de_DE.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-42-generic root=UUID=b1da7b88-5409-4c35-9eb1-b8d5eccfc1ad ro plymouth:debug drm.debug=0xe quiet splash SourcePackage: xorg UpgradeStatus: Upgraded to bionic on 2018-09-04 (103 days ago) dmi.bios.date: 05/18/2009 dmi.bios.vendor: Intel Corp. dmi.bios.version: PRG3110H.86A.0066.2009.0518.1206 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: DG31PR dmi.board.vendor: Intel Corporation dmi.board.version: AAD97573-306 dmi.chassis.type: 3 dmi.modalias: dmi:bvnIntelCorp.:bvrPRG3110H.86A.0066.2009.0518.1206:bd05/18/2009:svn:pn:pvr:rvnIntelCorporation:rnDG31PR:rvrAAD97573-306:cvn:ct3:cvr: version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1 version.xserver-xorg-core: xserver-xo
[Touch-packages] [Bug 1808704] [NEW] Prgram does not run
Public bug reported: it just does nothing: MyTV TorBrowser ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-42.45-generic 4.15.18 Uname: Linux 4.15.0-42-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CompositorRunning: None Date: Sun Dec 16 17:46:25 2018 DistUpgraded: 2018-09-04 18:34:54,728 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py (g-exec-error-quark: Kindprozess »./xorg_fix_proprietary.py« konnte nicht ausgeführt werden (Datei oder Verzeichnis nicht gefunden) (8)) DistroCodename: bionic DistroVariant: ubuntu GraphicsCard: NVIDIA Corporation G96 [GeForce 9400 GT] [10de:0641] (rev a1) (prog-if 00 [VGA controller]) Subsystem: CardExpert Technology G96 [GeForce 9400 GT] [10b0:1401] InstallationDate: Installed on 2017-07-27 (507 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) ProcEnviron: PATH=(custom, no user) LANG=de_DE.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-42-generic root=UUID=b1da7b88-5409-4c35-9eb1-b8d5eccfc1ad ro plymouth:debug drm.debug=0xe quiet splash SourcePackage: xorg UpgradeStatus: Upgraded to bionic on 2018-09-04 (103 days ago) dmi.bios.date: 05/18/2009 dmi.bios.vendor: Intel Corp. dmi.bios.version: PRG3110H.86A.0066.2009.0518.1206 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: DG31PR dmi.board.vendor: Intel Corporation dmi.board.version: AAD97573-306 dmi.chassis.type: 3 dmi.modalias: dmi:bvnIntelCorp.:bvrPRG3110H.86A.0066.2009.0518.1206:bd05/18/2009:svn:pn:pvr:rvnIntelCorporation:rnDG31PR:rvrAAD97573-306:cvn:ct3:cvr: version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 xserver.bootTime: Sat Feb 17 20:02:16 2018 xserver.configfile: default xserver.errors: Failed to load module "nvidia" (module does not exist, 0) Failed to load module "nvidia" (module does not exist, 0) xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.18.4-0ubuntu0.7 xserver.video_driver: nouveau ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic ubuntu -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1808704 Title: Prgram does not run Status in xorg package in Ubuntu: New Bug description: it just does nothing: MyTV TorBrowser ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-42.45-generic 4.15.18 Uname: Linux 4.15.0-42-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CompositorRunning: None Date: Sun Dec 16 17:46:25 2018 DistUpgraded: 2018-09-04 18:34:54,728 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py (g-exec-error-quark: Kindprozess »./xorg_fix_proprietary.py« konnte nicht ausgeführt werden (Datei oder Verzeichnis nicht gefunden) (8)) DistroCodename: bionic DistroVariant: ubuntu GraphicsCard: NVIDIA Corporation G96 [GeForce 9400 GT] [10de:0641] (rev a1) (prog-if 00 [VGA controller]) Subsystem: CardExpert Technology G96 [GeForce 9400 GT] [10b0:1401] InstallationDate: Installed on 2017-07-27 (507 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) ProcEnviron: PATH=(custom, no user) LANG=de_DE.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-42-generic root=UUID=b1da7b88-5409-4c35-9eb1-b8d5eccfc1ad ro plymouth:debug drm.debug=0xe quiet splash SourcePackage: xorg UpgradeStatus: Upgraded to bionic on 2018-09-04 (103 days ago) dmi.bios.date: 05/18/2009 dmi.bios.vendor: Intel Corp. dmi.bios.version: PRG3110H.86A.0066.2009.0518.1206 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: DG31PR dmi.board.vendor: Intel Corporation dmi.board.version: AAD97573-306 dmi.chassis.type: 3 dmi.modalias: dmi:bvnIntelCorp.:bvrPRG3110H.86A.0066.2009.0518.1206:bd05/18/2009:svn:pn:pvr:rvnIntelCorporation:rnDG31PR:rvrAAD97573-306:cvn:ct3:cvr: version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1 version.xserver-xorg-core: xserver-xo
[Touch-packages] [Bug 1805000] [NEW] package libwayland-dev 1.16.0-1ubuntu1 failed to install/upgrade: Versuch, »/usr/lib/x86_64-linux-gnu/pkgconfig/wayland-egl.pc« zu überschreiben, welches auch in P
Public bug reported: Sorry, but I cannot provide any further details. ProblemType: Package DistroRelease: Ubuntu 18.10 Package: libwayland-dev 1.16.0-1ubuntu1 ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12 Uname: Linux 4.18.0-11-generic x86_64 ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 CompositorRunning: None Date: Sun Nov 25 11:48:57 2018 DistUpgraded: 2018-11-25 11:29:30,487 DEBUG inhibit gnome-session idle DistroCodename: cosmic DistroVariant: ubuntu ErrorMessage: Versuch, »/usr/lib/x86_64-linux-gnu/pkgconfig/wayland-egl.pc« zu überschreiben, welches auch in Paket libegl1-mesa-dev:amd64 18.0.5-0ubuntu0~18.04.1 ist GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] RV516 [Radeon X1300/X1550 Series] [1002:7183] (prog-if 00 [VGA controller]) Subsystem: Dell RV516 [Radeon X1300/X1550 Series] [1028:0302] Subsystem: Dell RV516 [Radeon X1300/X1550 Series] (Secondary) [1028:0303] InstallationDate: Installed on 2018-11-04 (20 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: Dell Inc. Dell DXP061 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-11-generic root=UUID=6da4486b-e9be-4083-a94e-8dc955713ba7 ro quiet splash vt.handoff=1 Python3Details: /usr/bin/python3.6, Python 3.6.7, python3-minimal, 3.6.7-1~18.10 PythonDetails: /usr/bin/python2.7, Python 2.7.15+, python-minimal, 2.7.15-3 RelatedPackageVersions: dpkg 1.19.0.5ubuntu5 apt 1.7.0 SourcePackage: wayland Title: package libwayland-dev 1.16.0-1ubuntu1 failed to install/upgrade: Versuch, »/usr/lib/x86_64-linux-gnu/pkgconfig/wayland-egl.pc« zu überschreiben, welches auch in Paket libegl1-mesa-dev:amd64 18.0.5-0ubuntu0~18.04.1 ist UpgradeStatus: Upgraded to cosmic on 2018-11-25 (0 days ago) dmi.bios.date: 11/22/2007 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.5.3 dmi.board.name: 0WG855 dmi.board.vendor: Dell Inc. dmi.chassis.type: 7 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.5.3:bd11/22/2007:svnDellInc.:pnDellDXP061:pvr:rvnDellInc.:rn0WG855:rvr:cvnDellInc.:ct7:cvr: dmi.product.name: Dell DXP061 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.95-1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.2-0ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.2-0ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.1-3ubuntu2.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-3 ** Affects: wayland (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package cosmic ubuntu -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to wayland in Ubuntu. https://bugs.launchpad.net/bugs/1805000 Title: package libwayland-dev 1.16.0-1ubuntu1 failed to install/upgrade: Versuch, »/usr/lib/x86_64-linux-gnu/pkgconfig/wayland-egl.pc« zu überschreiben, welches auch in Paket libegl1-mesa-dev:amd64 18.0.5-0ubuntu0~18.04.1 ist Status in wayland package in Ubuntu: New Bug description: Sorry, but I cannot provide any further details. ProblemType: Package DistroRelease: Ubuntu 18.10 Package: libwayland-dev 1.16.0-1ubuntu1 ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12 Uname: Linux 4.18.0-11-generic x86_64 ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 CompositorRunning: None Date: Sun Nov 25 11:48:57 2018 DistUpgraded: 2018-11-25 11:29:30,487 DEBUG inhibit gnome-session idle DistroCodename: cosmic DistroVariant: ubuntu ErrorMessage: Versuch, »/usr/lib/x86_64-linux-gnu/pkgconfig/wayland-egl.pc« zu überschreiben, welches auch in Paket libegl1-mesa-dev:amd64 18.0.5-0ubuntu0~18.04.1 ist GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] RV516 [Radeon X1300/X1550 Series] [1002:7183] (prog-if 00 [VGA controller]) Subsystem: Dell RV516 [Radeon X1300/X1550 Series] [1028:0302] Subsystem: Dell RV516 [Radeon X1300/X1550 Series] (Secondary) [1028:0303] InstallationDate: Installed on 2018-11-04 (20 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: Dell Inc. Dell DXP061 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-11-generic root=UUID=6da4486b-e9be-4083-a94e-8dc955713ba7 ro quiet splash vt.handoff=1 Python3Details: /usr/bin/python3.6, Python 3.6.7, python3-minimal, 3.6.7-1~18.10 PythonDetails: /usr/bin/python2.7, Python 2.7.15+, python-minimal, 2.7.15-3 RelatedPackageVersions: dpkg 1.19.0.5ubuntu5 apt 1.7.0 SourcePackage: wayland Title: package libwayland-dev 1.16.0-1ubuntu1 failed to install/upgrade: Versuch, »/usr/lib/x86_64-linux-gnu/pkgconfig/wayland-egl.pc« zu überschreiben, welches auch in Paket libegl1-mesa-dev:amd64 18.0.5-0ubuntu0~18.04.1 is
[Touch-packages] [Bug 1799647] [NEW] Patch: Add configuration for german provider winSIM
Public bug reported: I was unable to contribute a patch to the upstream gnome package: https://wiki.gnome.org/Projects/NetworkManager/MobileBroadband/ServiceProviders (They seem to have migrated their git servers away) I still think this little config change adds value to Ubuntu users, hence I am opening this issue. Find the patchfile attached. ** Affects: mobile-broadband-provider-info (Ubuntu) Importance: Undecided Status: New ** Tags: patch ** Patch added: "Add configuration for german provider winSIM" https://bugs.launchpad.net/bugs/1799647/+attachment/5204795/+files/patch_Germany_winSIM.patch -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mobile-broadband-provider- info in Ubuntu. https://bugs.launchpad.net/bugs/1799647 Title: Patch: Add configuration for german provider winSIM Status in mobile-broadband-provider-info package in Ubuntu: New Bug description: I was unable to contribute a patch to the upstream gnome package: https://wiki.gnome.org/Projects/NetworkManager/MobileBroadband/ServiceProviders (They seem to have migrated their git servers away) I still think this little config change adds value to Ubuntu users, hence I am opening this issue. Find the patchfile attached. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mobile-broadband-provider-info/+bug/1799647/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1777579] Re: 18.04 Desktop LTS DNS behavior (systemd-resolved)
** Summary changed: - 18.04 Dekstop LTS DNS behavior (systemd-resolved) + 18.04 Desktop LTS DNS behavior (systemd-resolved) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1777579 Title: 18.04 Desktop LTS DNS behavior (systemd-resolved) Status in systemd package in Ubuntu: Expired Bug description: Hi, I am using te latest Ubuntu Mate Desktop 18.04 LTS release and have issues getting local DNS to work. In my network I maintain a central router instance that povides DHCP and DNS successfully over many years. The DHCP assigns a valid address and correct DNS information to my above mentioned network client. However DNS resolution does not work for DNS records maintained in my router for my local network. See here: (local DNS server on .3.1) uho@Asus:~/Schreibtisch$ systemd-resolve --status Global DNSSEC NTA: 10.in-addr.arpa 16.172.in-addr.arpa 168.192.in-addr.arpa 17.172.in-addr.arpa 18.172.in-addr.arpa 19.172.in-addr.arpa 20.172.in-addr.arpa 21.172.in-addr.arpa 22.172.in-addr.arpa 23.172.in-addr.arpa 24.172.in-addr.arpa 25.172.in-addr.arpa 26.172.in-addr.arpa 27.172.in-addr.arpa 28.172.in-addr.arpa 29.172.in-addr.arpa 30.172.in-addr.arpa 31.172.in-addr.arpa corp d.f.ip6.arpa home internal intranet lan local private test Link 2 (wlp2s0) Current Scopes: DNS LLMNR setting: yes MulticastDNS setting: no DNSSEC setting: no DNSSEC supported: no DNS Servers: 192.168.3.1 uho@Asus:~/Schreibtisch$ uho@Asus:~/Schreibtisch$ nslookup filou Server: 127.0.0.53 Address: 127.0.0.53#53 ** server can't find filou: SERVFAIL uho@Asus:~/Schreibtisch$ nslookup filou 192.168.3.1 Server: 192.168.3.1 Address: 192.168.3.1#53 Non-authoritative answer: Name: filou Address: 192.168.3.10 uho@Asus:~/Schreibtisch$ nslookup 192.168.3.10 10.3.168.192.in-addr.arpa name = filou. Authoritative answers can be found from: uho@Asus:~/Schreibtisch$ The example above shows that DNS forward lookup for "filou" does not work, only reverse lookup works. The same behavior with explicit DNS setting in network manager. Any idea what's wrong? To me this looks weirdly broken. BTW: Old school setting in /etc/resolv.conf works like a charm. BR Uwe To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1777579/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1777579] Re: 18.04 Dekstop LTS DNS behavior (systemd-resolved)
I wonder what's going wrong here since this bug is not ranked, not confirmed, just expired. Anyone able to give advice, what is needed to bring focus on it? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1777579 Title: 18.04 Dekstop LTS DNS behavior (systemd-resolved) Status in systemd package in Ubuntu: Expired Bug description: Hi, I am using te latest Ubuntu Mate Desktop 18.04 LTS release and have issues getting local DNS to work. In my network I maintain a central router instance that povides DHCP and DNS successfully over many years. The DHCP assigns a valid address and correct DNS information to my above mentioned network client. However DNS resolution does not work for DNS records maintained in my router for my local network. See here: (local DNS server on .3.1) uho@Asus:~/Schreibtisch$ systemd-resolve --status Global DNSSEC NTA: 10.in-addr.arpa 16.172.in-addr.arpa 168.192.in-addr.arpa 17.172.in-addr.arpa 18.172.in-addr.arpa 19.172.in-addr.arpa 20.172.in-addr.arpa 21.172.in-addr.arpa 22.172.in-addr.arpa 23.172.in-addr.arpa 24.172.in-addr.arpa 25.172.in-addr.arpa 26.172.in-addr.arpa 27.172.in-addr.arpa 28.172.in-addr.arpa 29.172.in-addr.arpa 30.172.in-addr.arpa 31.172.in-addr.arpa corp d.f.ip6.arpa home internal intranet lan local private test Link 2 (wlp2s0) Current Scopes: DNS LLMNR setting: yes MulticastDNS setting: no DNSSEC setting: no DNSSEC supported: no DNS Servers: 192.168.3.1 uho@Asus:~/Schreibtisch$ uho@Asus:~/Schreibtisch$ nslookup filou Server: 127.0.0.53 Address: 127.0.0.53#53 ** server can't find filou: SERVFAIL uho@Asus:~/Schreibtisch$ nslookup filou 192.168.3.1 Server: 192.168.3.1 Address: 192.168.3.1#53 Non-authoritative answer: Name: filou Address: 192.168.3.10 uho@Asus:~/Schreibtisch$ nslookup 192.168.3.10 10.3.168.192.in-addr.arpa name = filou. Authoritative answers can be found from: uho@Asus:~/Schreibtisch$ The example above shows that DNS forward lookup for "filou" does not work, only reverse lookup works. The same behavior with explicit DNS setting in network manager. Any idea what's wrong? To me this looks weirdly broken. BTW: Old school setting in /etc/resolv.conf works like a charm. BR Uwe To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1777579/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1777579] Re: 18.04 Dekstop LTS DNS behavior (systemd-resolved)
For your reference: https://lwn.net/Articles/753079/ https://www.reddit.com/r/linuxquestions/comments/8usld5/ubuntu_1804_dns_not_working/ https://medium.com/@ahmadb/fixing-dns-issues-in-ubuntu-18-04-lts-bd4f9ca56620 https://ubuntuforums.org/showthread.php?t=2358660 https://www.linode.com/community/questions/17081/dns-stops-resolving-on-ubuntu-1804 https://stackoverflow.com/questions/50299241/ubuntu-18-04-server-how-to-check-dns-ip-server-setting-being-used https://www.linuxquestions.org/questions/ubuntu-63/18-04-how-to-force-usage-of-dns-server-assigned-by-dhcp-4175628934/ https://www.techrepublic.com/article/how-to-set-dns-nameservers-in-ubuntu-server-18-04/ -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1777579 Title: 18.04 Dekstop LTS DNS behavior (systemd-resolved) Status in systemd package in Ubuntu: Expired Bug description: Hi, I am using te latest Ubuntu Mate Desktop 18.04 LTS release and have issues getting local DNS to work. In my network I maintain a central router instance that povides DHCP and DNS successfully over many years. The DHCP assigns a valid address and correct DNS information to my above mentioned network client. However DNS resolution does not work for DNS records maintained in my router for my local network. See here: (local DNS server on .3.1) uho@Asus:~/Schreibtisch$ systemd-resolve --status Global DNSSEC NTA: 10.in-addr.arpa 16.172.in-addr.arpa 168.192.in-addr.arpa 17.172.in-addr.arpa 18.172.in-addr.arpa 19.172.in-addr.arpa 20.172.in-addr.arpa 21.172.in-addr.arpa 22.172.in-addr.arpa 23.172.in-addr.arpa 24.172.in-addr.arpa 25.172.in-addr.arpa 26.172.in-addr.arpa 27.172.in-addr.arpa 28.172.in-addr.arpa 29.172.in-addr.arpa 30.172.in-addr.arpa 31.172.in-addr.arpa corp d.f.ip6.arpa home internal intranet lan local private test Link 2 (wlp2s0) Current Scopes: DNS LLMNR setting: yes MulticastDNS setting: no DNSSEC setting: no DNSSEC supported: no DNS Servers: 192.168.3.1 uho@Asus:~/Schreibtisch$ uho@Asus:~/Schreibtisch$ nslookup filou Server: 127.0.0.53 Address: 127.0.0.53#53 ** server can't find filou: SERVFAIL uho@Asus:~/Schreibtisch$ nslookup filou 192.168.3.1 Server: 192.168.3.1 Address: 192.168.3.1#53 Non-authoritative answer: Name: filou Address: 192.168.3.10 uho@Asus:~/Schreibtisch$ nslookup 192.168.3.10 10.3.168.192.in-addr.arpa name = filou. Authoritative answers can be found from: uho@Asus:~/Schreibtisch$ The example above shows that DNS forward lookup for "filou" does not work, only reverse lookup works. The same behavior with explicit DNS setting in network manager. Any idea what's wrong? To me this looks weirdly broken. BTW: Old school setting in /etc/resolv.conf works like a charm. BR Uwe To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1777579/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1777579] Re: 18.04 Dekstop LTS DNS behavior (systemd-resolved)
Hi, this bug is still valid. Out of the box, 18.04.x does not take local DNS into account, leading to massive lookup problems. A lot of discussion and mediocre quality solutions can be found in the wild. Even workarounds with Network Manager config changes are not persistent. My proposal: Revert back to the 16.04 DNS lookup mechanism and test the 18.04 implementation further. 18.04 is barely usable with this DNS implementation... Unfortunately fixing the issue is beyond my own knowledge of the currently used DNS-SEC implementation. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1777579 Title: 18.04 Dekstop LTS DNS behavior (systemd-resolved) Status in systemd package in Ubuntu: Expired Bug description: Hi, I am using te latest Ubuntu Mate Desktop 18.04 LTS release and have issues getting local DNS to work. In my network I maintain a central router instance that povides DHCP and DNS successfully over many years. The DHCP assigns a valid address and correct DNS information to my above mentioned network client. However DNS resolution does not work for DNS records maintained in my router for my local network. See here: (local DNS server on .3.1) uho@Asus:~/Schreibtisch$ systemd-resolve --status Global DNSSEC NTA: 10.in-addr.arpa 16.172.in-addr.arpa 168.192.in-addr.arpa 17.172.in-addr.arpa 18.172.in-addr.arpa 19.172.in-addr.arpa 20.172.in-addr.arpa 21.172.in-addr.arpa 22.172.in-addr.arpa 23.172.in-addr.arpa 24.172.in-addr.arpa 25.172.in-addr.arpa 26.172.in-addr.arpa 27.172.in-addr.arpa 28.172.in-addr.arpa 29.172.in-addr.arpa 30.172.in-addr.arpa 31.172.in-addr.arpa corp d.f.ip6.arpa home internal intranet lan local private test Link 2 (wlp2s0) Current Scopes: DNS LLMNR setting: yes MulticastDNS setting: no DNSSEC setting: no DNSSEC supported: no DNS Servers: 192.168.3.1 uho@Asus:~/Schreibtisch$ uho@Asus:~/Schreibtisch$ nslookup filou Server: 127.0.0.53 Address: 127.0.0.53#53 ** server can't find filou: SERVFAIL uho@Asus:~/Schreibtisch$ nslookup filou 192.168.3.1 Server: 192.168.3.1 Address: 192.168.3.1#53 Non-authoritative answer: Name: filou Address: 192.168.3.10 uho@Asus:~/Schreibtisch$ nslookup 192.168.3.10 10.3.168.192.in-addr.arpa name = filou. Authoritative answers can be found from: uho@Asus:~/Schreibtisch$ The example above shows that DNS forward lookup for "filou" does not work, only reverse lookup works. The same behavior with explicit DNS setting in network manager. Any idea what's wrong? To me this looks weirdly broken. BTW: Old school setting in /etc/resolv.conf works like a charm. BR Uwe To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1777579/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1577042] Re: SIGSEGV in SoundTouch 1.9.2
Why not simply increasing the minimum required version from 1.8.0 to 2.0.0? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to soundtouch in Ubuntu. https://bugs.launchpad.net/bugs/1577042 Title: SIGSEGV in SoundTouch 1.9.2 Status in Mixxx: Confirmed Status in soundtouch package in Ubuntu: Confirmed Bug description: OS: Fedora 23 x86_64 Lib: soundtouch-1.9.2-3.fc23.x86_64 Branch: master (2.1.0-alpha-pre x64) Key Lock enabled Pitch at 0.00 - not moved during the whole session (AutoDJ background music @home) File plays fine after restart - same results - waveform generation is skipped now Warning [AnalyzerQueue 1]: Recoverable MP3 frame decoding error: lost synchronization Debug [AnalyzerQueue 1]: Waveform generation for track 92614 done 6 s Debug [AnalyzerQueue 1]: ReplayGain 2.0 (libebur128) result is -2.78099 dB for "/home/uk/Music/Collection/nico/chelsea girl/01-02 nico these days.mp3" Debug [AnalyzerQueue 1]: Beat Calculation complete Debug [AnalyzerQueue 1]: Key Detection complete Debug [AnalyzerQueue 1]: Key Histogram Debug [AnalyzerQueue 1]: 6 : "F" 7.93267e+06 Debug [AnalyzerQueue 1]: 11 : "B♭" 1.47456e+06 Program received signal SIGSEGV, Segmentation fault. [Switching to Thread 0x7ffee22d2700 (LWP 16845)] 0x77891e90 in soundtouch::TDStretch::overlapStereo(float*, float const*) const () from /usr/lib64/libSoundTouch.so.1 (gdb) bt #0 0x77891e90 in soundtouch::TDStretch::overlapStereo(float*, float const*) const () at /usr/lib64/libSoundTouch.so.1 #1 0x77893037 in soundtouch::TDStretch::processSamples() () at /usr/lib64/libSoundTouch.so.1 #2 0x77891490 in soundtouch::SoundTouch::putSamples(float const*, unsigned int) () at /usr/lib64/libSoundTouch.so.1 #3 0x007cfc82 in EngineBufferScaleST::getScaled(float*, int) (this=0x20a9d00, pOutput=, buf_size=2048) at src/engine/enginebufferscalest.cpp:164 #4 0x007cba11 in EngineBuffer::process(float*, int) (this=0x1fa1be0, pOutput=0x7fffc8792010, iBufferSize=2048) at src/engine/enginebuffer.cpp:983 #5 0x007d1310 in EngineDeck::process(float*, int) (this=0x1f759d0, pOut=0x7fffc8792010, iBufferSize=2048) at src/engine/enginedeck.cpp:98 #6 0x007dff4e in EngineMaster::processChannels(int) (this=this@entry=0x14fe100, iBufferSize=iBufferSize@entry=2048) at src/engine/enginemaster.cpp:318 #7 0x007e8b50 in EngineMaster::process(int) (this=0x14fe100, iBufferSize=iBufferSize@entry=2048) at src/engine/enginemaster.cpp:350 #8 0x00b47d5b in SoundManager::onDeviceOutputCallback(unsigned int) (this=, iFramesPerBuffer=iFramesPerBuffer@entry=1024) at src/soundio/soundmanager.cpp:548 #9 0x00b44a36 in SoundDevicePortAudio::callbackProcessClkRef(unsigned int, float*, float const*, PaStreamCallbackTimeInfo const*, unsigned long) (this=0x1e337c0, framesPerBuffer=1024, out=0x4de4f2a0, in=, timeInfo= to continue, or q to quit--- ptimized out>, statusFlags=) at src/soundio/sounddeviceportaudio.cpp:949 #10 0x77459454 in AdaptingOutputOnlyProcess () at /usr/lib64/libportaudio.so.2 #11 0x7745aded in PaUtil_EndBufferProcessing () at /usr/lib64/libportaudio.so.2 #12 0x7746391b in CallbackThreadFunc () at /usr/lib64/libportaudio.so.2 #13 0x71d1e60a in start_thread () at /usr/lib64/libpthread.so.0 #14 0x7fffeeeb5a4d in clone () at /usr/lib64/libc.so.6 To manage notifications about this bug go to: https://bugs.launchpad.net/mixxx/+bug/1577042/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1603815] Re: after updating to ubuntu 16.04 the network manager is unable to connect me to the wifi network. I can see the network, but once I introduce the password, it asks me
Thanks for your efforts, Fred, but unfortunately, this does not work for Ubuntu 16.04 or Mint 18.2, because the two lines you found does not exist there. The NetworkManger.conf looks exactly the same as on Debian. Hopefully, the error won't exist anymore on the next Ubuntu and Mint version, respectively! ;-) Cheers Uwe -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1603815 Title: after updating to ubuntu 16.04 the network manager is unable to connect me to the wifi network. I can see the network, but once I introduce the password, it asks me for the password after a few seconds and never connects. Status in network-manager package in Ubuntu: Confirmed Bug description: after updating to ubuntu 16.04 the network manager is unable to connect me to the wifi network. I can see the network, but once I introduce the password, it asks me for the password after a few seconds and never connects. I use different devices connected to the same wifi so it is not a problem of writting the wrong password. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: network-manager 1.1.93-0ubuntu4 ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13 Uname: Linux 4.4.0-31-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CurrentDesktop: Unity Date: Sun Jul 17 16:58:17 2016 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2016-07-16 (1 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) IpRoute: default via 192.168.2.1 dev enp2s0 proto static metric 100 169.254.0.0/16 dev enp2s0 scope link metric 1000 192.168.2.0/24 dev enp2s0 proto kernel scope link src 192.168.2.242 metric 100 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-con: NAME UUID TYPE TIMESTAMP TIMESTAMP-REALAUTOCONNECT AUTOCONNECT-PRIORITY READONLY DBUS-PATH ACTIVE DEVICE STATE ACTIVE-PATH Conexión cableada 1 9e376788-1744-46de-a314-eeb07aad8c13 802-3-ethernet 1468789026 dom 17 jul 2016 16:57:06 CDT yes 4294966297no /org/freedesktop/NetworkManager/Settings/2 yes enp2s0 activated /org/freedesktop/NetworkManager/ActiveConnection/1 BELL419 28bd64cc4-181f-449b-95a3-edc74cf2a9a6 802-11-wireless 0 never yes 0 no /org/freedesktop/NetworkManager/Settings/1 no -- -- -- nmcli-dev: DEVICETYPE STATE DBUS-PATH CONNECTION CON-UUID CON-PATH enp2s0ethernet connected /org/freedesktop/NetworkManager/Devices/1 Conexión cableada 1 9e376788-1744-46de-a314-eeb07aad8c13 /org/freedesktop/NetworkManager/ActiveConnection/1 wlp3s0b1 wifi disconnected /org/freedesktop/NetworkManager/Devices/0 -- ---- loloopback unmanaged /org/freedesktop/NetworkManager/Devices/2 -- ---- nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 2: Error: Object 'nm' is unknown, try 'nmcli help'. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1603815/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1729447] Re: No wired connection since upgrade to 17.10
I chose to reinstall the 17.10 version from scratch. All the procedure went without any trouble. I have IP connection over the wire. I presume something went wrong during the upgrade process from 17.04 to 17.10, which I can not reproduce. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1729447 Title: No wired connection since upgrade to 17.10 Status in network-manager package in Ubuntu: New Bug description: 1. Not sending from my pc: 4.13, so far I remember 2. See the file attached 3. Network manager working normally 4. Not connecting over a wired lan. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1729447/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1729447] Re: No wired connection since upgrade to 17.10
** Package changed: ubuntu => network-manager (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1729447 Title: No wired connection since upgrade to 17.10 Status in network-manager package in Ubuntu: New Bug description: 1. Not sending from my pc: 4.13, so far I remember 2. See the file attached 3. Network manager working normally 4. Not connecting over a wired lan. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1729447/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1603815] Re: after updating to ubuntu 16.04 the network manager is unable to connect me to the wifi network. I can see the network, but once I introduce the password, it asks me
I'm experiencing the same problem after I have changed my WiFi router. Each of my device connect flawlessly except a laptop running Ubuntu 16.04. I was only able to connect to my network after disabling the NetworkManager and configuring WiFi using wpa_supplicant. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1603815 Title: after updating to ubuntu 16.04 the network manager is unable to connect me to the wifi network. I can see the network, but once I introduce the password, it asks me for the password after a few seconds and never connects. Status in network-manager package in Ubuntu: Confirmed Bug description: after updating to ubuntu 16.04 the network manager is unable to connect me to the wifi network. I can see the network, but once I introduce the password, it asks me for the password after a few seconds and never connects. I use different devices connected to the same wifi so it is not a problem of writting the wrong password. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: network-manager 1.1.93-0ubuntu4 ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13 Uname: Linux 4.4.0-31-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CurrentDesktop: Unity Date: Sun Jul 17 16:58:17 2016 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2016-07-16 (1 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) IpRoute: default via 192.168.2.1 dev enp2s0 proto static metric 100 169.254.0.0/16 dev enp2s0 scope link metric 1000 192.168.2.0/24 dev enp2s0 proto kernel scope link src 192.168.2.242 metric 100 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-con: NAME UUID TYPE TIMESTAMP TIMESTAMP-REALAUTOCONNECT AUTOCONNECT-PRIORITY READONLY DBUS-PATH ACTIVE DEVICE STATE ACTIVE-PATH Conexión cableada 1 9e376788-1744-46de-a314-eeb07aad8c13 802-3-ethernet 1468789026 dom 17 jul 2016 16:57:06 CDT yes 4294966297no /org/freedesktop/NetworkManager/Settings/2 yes enp2s0 activated /org/freedesktop/NetworkManager/ActiveConnection/1 BELL419 28bd64cc4-181f-449b-95a3-edc74cf2a9a6 802-11-wireless 0 never yes 0 no /org/freedesktop/NetworkManager/Settings/1 no -- -- -- nmcli-dev: DEVICETYPE STATE DBUS-PATH CONNECTION CON-UUID CON-PATH enp2s0ethernet connected /org/freedesktop/NetworkManager/Devices/1 Conexión cableada 1 9e376788-1744-46de-a314-eeb07aad8c13 /org/freedesktop/NetworkManager/ActiveConnection/1 wlp3s0b1 wifi disconnected /org/freedesktop/NetworkManager/Devices/0 -- ---- loloopback unmanaged /org/freedesktop/NetworkManager/Devices/2 -- ---- nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 2: Error: Object 'nm' is unknown, try 'nmcli help'. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1603815/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1577197] Re: Pulseaudio bluez5-util.c: TryAcquire() failed - Operation Not Authorized
I have this problem with my Plantronics BackBeat. Device is connected, but I can't use it at all. a2dp.py does not help. It tells me pulseAudio service does not run. ./a2dp.py Connection MADE Selecting device: 1. 0C:E0:E4:9E:73:7C PLT_BBTSENSE 2. 98:FD:B4:0D:74:E7 ThinkPad Bluetooth Laser Mouse Select device[1]: 1 Device MAC: 0C:E0:E4:9E:73:7C Command: pacmd list-sinks failed with status: 1 stderr: Es läuft kein PulseAudio-Dienst oder nicht als Sessiondienst. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1577197 Title: Pulseaudio bluez5-util.c: TryAcquire() failed - Operation Not Authorized Status in bluez package in Ubuntu: Confirmed Status in indicator-sound package in Ubuntu: Invalid Status in pulseaudio package in Ubuntu: Confirmed Bug description: Pulseaudio outright stops audio via Bluetooth after sleep or prolonged period of time. Only restart fixes the issue. This started early 2016 in 15.10. Issue is discussed here as well http://askubuntu.com/questions/763539/bluetooth-speaker-no-sound-in-ubuntu-16-04 and mentioned in other unrelated bugs. Ubuntu Xenial 16.04 LTS The log below: May 1 17:18:07 jalexoidmobile pulseaudio[2884]: [pulseaudio] module-bluez5-device.c: Default profile not connected, selecting off profile May 1 17:18:07 jalexoidmobile bluetoothd[7349]: /org/bluez/hci0/dev_00_02_3C_05_99_F2/fd4: fd(35) ready May 1 17:18:07 jalexoidmobile rtkit-daemon[1794]: Supervising 3 threads of 1 processes of 1 users. May 1 17:18:07 jalexoidmobile rtkit-daemon[1794]: Successfully made thread 10967 of process 2884 (n/a) owned by '1000' RT at priority 5. May 1 17:18:07 jalexoidmobile rtkit-daemon[1794]: Supervising 4 threads of 1 processes of 1 users. May 1 17:18:07 jalexoidmobile pulseaudio[2884]: [pulseaudio] bluez5-util.c: Transport TryAcquire() failed for transport /org/bluez/hci0/dev_00_02_3C_05_99_F2/fd4 (Operation Not Authorized) May 1 17:18:07 jalexoidmobile kernel: [20583.032442] input: 00:02:3C:05:99:F2 as /devices/virtual/input/input24 May 1 17:18:19 jalexoidmobile pulseaudio[2884]: [pulseaudio] sink-input.c: Failed to create sink input: sink is suspended. Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 006: ID 04f2:b2da Chicony Electronics Co., Ltd thinkpad t430s camera Bus 001 Device 008: ID 0a5c:21e6 Broadcom Corp. BCM20702 Bluetooth 4.0 [ThinkPad] Bus 001 Device 004: ID 147e:2020 Upek TouchChip Fingerprint Coprocessor (WBF advanced mode) Bus 001 Device 003: ID 17ef:1003 Lenovo Integrated Smart Card Reader Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub [20388.983474] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready [20389.070114] usb 1-1.4: New USB device found, idVendor=0a5c, idProduct=21e6 [20389.070120] usb 1-1.4: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [20389.070122] usb 1-1.4: Product: BCM20702A0 [20389.070124] usb 1-1.4: Manufacturer: Broadcom Corp [20389.070126] usb 1-1.4: SerialNumber: 446D578686DD [20389.076232] Bluetooth: hci0: BCM: chip id 63 [20389.092220] Bluetooth: hci0: BCM20702A [20389.093225] Bluetooth: hci0: BCM20702A1 (001.002.014) build [20389.551476] wlan0: authenticate with a0:63:91:2f:3f:ed [20389.554391] wlan0: send auth to a0:63:91:2f:3f:ed (try 1/3) [20389.557790] wlan0: authenticated [20389.558339] wlan0: associate with a0:63:91:2f:3f:ed (try 1/3) [20389.562209] wlan0: RX AssocResp from a0:63:91:2f:3f:ed (capab=0x1411 status=0 aid=2) [20389.581260] wlan0: associated [20389.581369] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready [20389.830185] Bluetooth: hci0: BCM20702A1 (001.002.014) build 1669 [20389.846186] Bluetooth: hci0: Broadcom Bluetooth Device [20418.269466] input: 00:02:3C:05:99:F2 as /devices/virtual/input/input23 [20583.032442] input: 00:02:3C:05:99:F2 as /devices/virtual/input/input24 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1577197/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1650243] [NEW] fonts missing in Ubuntu 16.10
Public bug reported: On Ubuntu 16.10 there is something wrong with dejavu fonts, showing up by trying to use them with scribus or scribus-ng. On Ubuntu 16.04 all worked fine. The fonts aren't loaded into scribus, just one: DejaVu Math TeX Gyre Regular Font packages fonts-dejavu are all installed. I issued this as scribus bug (https://bugs.scribus.net/view.php?id=14475), but the maintainers said it's not a scribus thing. I tried the suggested solution to upgrade libfreetype6, but neither 2.6.5 nor 2.7 worked for me. I also tryed to downgrade libfreetype6 and fonts-dejavu to the working versions on Ubuntu 16.04, but also no success. But using the dejavu fonts in e.g. libreoffice works fine. Ubuntu 16.10 amd64 fonts-dejavu 2.37-1 libfreetype6 2.6.3-3ubuntu1 ** Affects: fonts-dejavu (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to fonts-dejavu in Ubuntu. https://bugs.launchpad.net/bugs/1650243 Title: fonts missing in Ubuntu 16.10 Status in fonts-dejavu package in Ubuntu: New Bug description: On Ubuntu 16.10 there is something wrong with dejavu fonts, showing up by trying to use them with scribus or scribus-ng. On Ubuntu 16.04 all worked fine. The fonts aren't loaded into scribus, just one: DejaVu Math TeX Gyre Regular Font packages fonts-dejavu are all installed. I issued this as scribus bug (https://bugs.scribus.net/view.php?id=14475), but the maintainers said it's not a scribus thing. I tried the suggested solution to upgrade libfreetype6, but neither 2.6.5 nor 2.7 worked for me. I also tryed to downgrade libfreetype6 and fonts-dejavu to the working versions on Ubuntu 16.04, but also no success. But using the dejavu fonts in e.g. libreoffice works fine. Ubuntu 16.10 amd64 fonts-dejavu 2.37-1 libfreetype6 2.6.3-3ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fonts-dejavu/+bug/1650243/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1630309] [NEW] plasma panel auto hide - panel disappears and does not come back
Public bug reported: I have to open plasmashellrc and set planelVisibility to 0 to make it return. Simple reboot doesn't solve the problem. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19 Uname: Linux 4.4.0-38-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: KDE Date: Tue Oct 4 13:33:15 2016 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: kubuntu ExtraDebuggingInterest: I just need to know a workaround GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Dell 3rd Gen Core processor Graphics Controller [1028:0591] InstallationDate: Installed on 2016-07-27 (68 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: Dell Inc. Inspiron 3421 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-38-generic.efi.signed root=UUID=11cb0acd-e2d1-4040-8e64-08167dfa22cf ro quiet splash SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/07/2014 dmi.bios.vendor: Dell Inc. dmi.bios.version: A12 dmi.board.vendor: Dell Inc. dmi.board.version: A12 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvrA12:bd05/07/2014:svnDellInc.:pnInspiron3421:pvrNotSpecified:rvnDellInc.:rn:rvrA12:cvnDellInc.:ct8:cvrNotSpecified: dmi.product.name: Inspiron 3421 dmi.product.version: Not Specified dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2.2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2.2 version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2.3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1.1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 xserver.bootTime: Tue Oct 4 08:52:12 2016 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id5238 vendor CMN xserver.version: 2:1.18.3-1ubuntu2.3 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug kubuntu third-party-packages xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1630309 Title: plasma panel auto hide - panel disappears and does not come back Status in xorg package in Ubuntu: New Bug description: I have to open plasmashellrc and set planelVisibility to 0 to make it return. Simple reboot doesn't solve the problem. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19 Uname: Linux 4.4.0-38-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: KDE Date: Tue Oct 4 13:33:15 2016 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: kubuntu ExtraDebuggingInterest: I just need to know a workaround GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Dell 3rd Gen Core processor Graphics Controller [1028:0591] InstallationDate: Installed on 2016-07-27 (68 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: Dell Inc. Inspiron 3421 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-38-generic.efi.signed root=UUID=11cb0acd-e2d1-4040-8e64-08167dfa22cf ro quiet splash SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/07/2014 dmi.bios.vendor: Dell Inc. dmi.bios.version: A12 dmi.board.vendor: Dell Inc. dmi.board.version: A12 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvrA12:bd05/07/2014:svnDellInc.:pnInspiron3421:pvrNotSpecified:rvnDellInc.:rn:rvrA12:cvnDellInc.:ct8:cvrNotSpecified: dmi.product.name: Inspiron 3421 dmi.product.version: Not Specified dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.12.2
[Touch-packages] [Bug 1574278] Re: AbiWord text cursor starts to flicker after adding some text
I wrote: I can confirm [...] the effectiveness of the work-around "GTK_THEME=adwaita abiword". With some more testing I have to qualify that statement a bit: With the adwaita theme the behaviour is clearly improved compared to the default. I have not seen text flickering so far. But the cursor still flickers a bit and sometimes disappears completely until some new text is entered. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1574278 Title: AbiWord text cursor starts to flicker after adding some text Status in AbiWord: Invalid Status in abiword package in Ubuntu: Invalid Status in gtk+3.0 package in Ubuntu: Fix Released Status in lubuntu-artwork package in Ubuntu: Invalid Status in abiword source package in Xenial: Invalid Status in gtk+3.0 source package in Xenial: Confirmed Status in lubuntu-artwork source package in Xenial: Invalid Bug description: After adding some text in a new document, the entire document (including gray page background, text, text cursor) starts to flicker very fast. The UI above does not flicker. This happens too on a different system in VirtualBox. (Lubuntu 16.04 i386) Workaround == 1. Open the Lubuntu menu. 2. Open Preferences>Customize Look and Feel 3. Change the theme to something other than Lubuntu-default or Lubuntu-dark-panel ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: abiword 3.0.1-6 ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic i686 ApportVersion: 2.20.1-0ubuntu2 Architecture: i386 CurrentDesktop: LXDE Date: Sun Apr 24 16:12:14 2016 ExecutablePath: /usr/bin/abiword InstallationDate: Installed on 2016-04-22 (2 days ago) InstallationMedia: Lubuntu 15.10 "Wily Werewolf" - Release i386 (20151021) ProcEnviron: LANGUAGE=de_DE PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: abiword UpgradeStatus: Upgraded to xenial on 2016-04-22 (2 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/abiword/+bug/1574278/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1574278] Re: AbiWord text cursor starts to flicker after adding some text
Using Xubuntu 16.04 with all updates here. I can confirm both the original flickering and the effectiveness of the work-around "GTK_THEME=adwaita abiword". -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1574278 Title: AbiWord text cursor starts to flicker after adding some text Status in AbiWord: Invalid Status in abiword package in Ubuntu: Invalid Status in gtk+3.0 package in Ubuntu: Fix Released Status in lubuntu-artwork package in Ubuntu: Invalid Status in abiword source package in Xenial: Invalid Status in gtk+3.0 source package in Xenial: Confirmed Status in lubuntu-artwork source package in Xenial: Invalid Bug description: After adding some text in a new document, the entire document (including gray page background, text, text cursor) starts to flicker very fast. The UI above does not flicker. This happens too on a different system in VirtualBox. (Lubuntu 16.04 i386) Workaround == 1. Open the Lubuntu menu. 2. Open Preferences>Customize Look and Feel 3. Change the theme to something other than Lubuntu-default or Lubuntu-dark-panel ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: abiword 3.0.1-6 ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic i686 ApportVersion: 2.20.1-0ubuntu2 Architecture: i386 CurrentDesktop: LXDE Date: Sun Apr 24 16:12:14 2016 ExecutablePath: /usr/bin/abiword InstallationDate: Installed on 2016-04-22 (2 days ago) InstallationMedia: Lubuntu 15.10 "Wily Werewolf" - Release i386 (20151021) ProcEnviron: LANGUAGE=de_DE PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: abiword UpgradeStatus: Upgraded to xenial on 2016-04-22 (2 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/abiword/+bug/1574278/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 10550] Re: DVDs with restrictive permissions are unreadable for normal user
Sorry, is *not* working for me ... -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to util-linux in Ubuntu. https://bugs.launchpad.net/bugs/10550 Title: DVDs with restrictive permissions are unreadable for normal user Status in Linux: Fix Released Status in util-linux package in Ubuntu: Invalid Status in util-linux package in Baltix: New Status in Debian: New Bug description: ever since I upgraded pmount, gnome-volume-manager hasn't been able to deal w/ my DVDs correctly. it mounts the disc as one one would expect, but it can't launch totem. When I do it manually. I get this error from totem when I try to "Play Disc" "Failed to play Audio/Video Disc Error opening directory '/media/cdrom0/' VIDEO_TS': Permission denied." /media/cdrom0 is dr--r--r-- 3 4294967295 4294967295 88 2004-09-03 18:58 /media/cdrom0/ it's mounted as /dev/hdc on /media/cdrom0 type udf (ro,noexec,nosuid,nodev,user=spotter) and an ls of it shows spotter@dent:~ $ ls -l /media/cdrom0/ ls: /media/cdrom0/VIDEO_TS: Permission denied though it works as root root@dent:/home/spotter # ls -l /media/cdrom0/ total 2 dr--r--r-- 2 4294967295 4294967295 508 2004-09-03 18:58 VIDEO_TS root@dent:/home/spotter # ls -l /media/cdrom0/VIDEO_TS/ total 3736860 -r--r--r-- 1 4294967295 4294967295 12288 2004-09-03 18:58 VIDEO_TS.BUP -r--r--r-- 1 4294967295 4294967295 12288 2004-09-03 18:58 VIDEO_TS.IFO -r--r--r-- 1 4294967295 4294967295 47104 2004-09-03 18:58 VIDEO_TS.VOB -r--r--r-- 1 4294967295 4294967295 51200 2004-09-03 18:58 VTS_01_0.BUP -r--r--r-- 1 4294967295 4294967295 51200 2004-09-03 18:58 VTS_01_0.IFO -r--r--r-- 1 4294967295 4294967295 1073170432 2004-09-03 18:58 VTS_01_1.VOB -r--r--r-- 1 4294967295 4294967295 1073170432 2004-09-03 18:58 VTS_01_2.VOB -r--r--r-- 1 4294967295 4294967295 1073170432 2004-09-03 18:58 VTS_01_3.VOB and totem works as root To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/10550/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 10550] Re: DVDs with restrictive permissions are unreadable for normal user
yes, i think the problem still exists in 14.04 ; maybe will also in 16.04 ... but the cd/dvd line is not /etc/fstab ; so even that workaround is working... -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to util-linux in Ubuntu. https://bugs.launchpad.net/bugs/10550 Title: DVDs with restrictive permissions are unreadable for normal user Status in Linux: Fix Released Status in util-linux package in Ubuntu: Invalid Status in util-linux package in Baltix: New Status in Debian: New Bug description: ever since I upgraded pmount, gnome-volume-manager hasn't been able to deal w/ my DVDs correctly. it mounts the disc as one one would expect, but it can't launch totem. When I do it manually. I get this error from totem when I try to "Play Disc" "Failed to play Audio/Video Disc Error opening directory '/media/cdrom0/' VIDEO_TS': Permission denied." /media/cdrom0 is dr--r--r-- 3 4294967295 4294967295 88 2004-09-03 18:58 /media/cdrom0/ it's mounted as /dev/hdc on /media/cdrom0 type udf (ro,noexec,nosuid,nodev,user=spotter) and an ls of it shows spotter@dent:~ $ ls -l /media/cdrom0/ ls: /media/cdrom0/VIDEO_TS: Permission denied though it works as root root@dent:/home/spotter # ls -l /media/cdrom0/ total 2 dr--r--r-- 2 4294967295 4294967295 508 2004-09-03 18:58 VIDEO_TS root@dent:/home/spotter # ls -l /media/cdrom0/VIDEO_TS/ total 3736860 -r--r--r-- 1 4294967295 4294967295 12288 2004-09-03 18:58 VIDEO_TS.BUP -r--r--r-- 1 4294967295 4294967295 12288 2004-09-03 18:58 VIDEO_TS.IFO -r--r--r-- 1 4294967295 4294967295 47104 2004-09-03 18:58 VIDEO_TS.VOB -r--r--r-- 1 4294967295 4294967295 51200 2004-09-03 18:58 VTS_01_0.BUP -r--r--r-- 1 4294967295 4294967295 51200 2004-09-03 18:58 VTS_01_0.IFO -r--r--r-- 1 4294967295 4294967295 1073170432 2004-09-03 18:58 VTS_01_1.VOB -r--r--r-- 1 4294967295 4294967295 1073170432 2004-09-03 18:58 VTS_01_2.VOB -r--r--r-- 1 4294967295 4294967295 1073170432 2004-09-03 18:58 VTS_01_3.VOB and totem works as root To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/10550/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1264364] Re: Glib warnings when running nm-connection-editor and entering Wired Connection options
** Description changed: I am getting GLib warnings in terminal when I run nm-connection-editor and enter Wired Connection options. To reproduce: 1. Run nm-connection-editor in terminal or run gnome-control-center and enter Network. 2. Choose Wired Connection (Ethernet) and click Modify. 3. At this point I get the following GLib warnings in terminal: (nm-connection-editor:10577): GLib-GIO-CRITICAL **: g_settings_new_with_path: assertion 'path_is_valid (path)' failed (nm-connection-editor:10577): GLib-GIO-CRITICAL **: g_settings_get_value: assertion 'G_IS_SETTINGS (settings)' failed (nm-connection-editor:10577): GLib-CRITICAL **: g_variant_get_type: assertion 'value != NULL' failed (nm-connection-editor:10577): GLib-CRITICAL **: g_variant_type_is_subtype_of: assertion 'g_variant_type_check (type)' failed (nm-connection-editor:10577): GLib-CRITICAL **: g_variant_get_boolean: assertion 'g_variant_is_of_type (value, G_VARIANT_TYPE_BOOLEAN)' failed (nm-connection-editor:10577): GLib-CRITICAL **: g_variant_unref: assertion 'value != NULL' failed (nm-connection-editor:10577): GLib-GObject-CRITICAL **: g_object_unref: assertion 'G_IS_OBJECT (object)' failed (nm-connection-editor:10577): GLib-GIO-CRITICAL **: g_settings_new_with_path: assertion 'path_is_valid (path)' failed (nm-connection-editor:10577): GLib-GIO-CRITICAL **: g_settings_get_value: assertion 'G_IS_SETTINGS (settings)' failed (nm-connection-editor:10577): GLib-CRITICAL **: g_variant_get_type: assertion 'value != NULL' failed (nm-connection-editor:10577): GLib-CRITICAL **: g_variant_type_is_subtype_of: assertion 'g_variant_type_check (type)' failed (nm-connection-editor:10577): GLib-CRITICAL **: g_variant_get_boolean: assertion 'g_variant_is_of_type (value, G_VARIANT_TYPE_BOOLEAN)' failed (nm-connection-editor:10577): GLib-CRITICAL **: g_variant_unref: assertion 'value != NULL' failed (nm-connection-editor:10577): GLib-GObject-CRITICAL **: g_object_unref: assertion 'G_IS_OBJECT (object)' failed (nm-connection-editor:10577): GLib-GIO-CRITICAL **: g_settings_new_with_path: assertion 'path_is_valid (path)' failed (nm-connection-editor:10577): GLib-GIO-CRITICAL **: g_settings_get_value: assertion 'G_IS_SETTINGS (settings)' failed (nm-connection-editor:10577): GLib-CRITICAL **: g_variant_get_type: assertion 'value != NULL' failed (nm-connection-editor:10577): GLib-CRITICAL **: g_variant_type_is_subtype_of: assertion 'g_variant_type_check (type)' failed (nm-connection-editor:10577): GLib-CRITICAL **: g_variant_get_boolean: assertion 'g_variant_is_of_type (value, G_VARIANT_TYPE_BOOLEAN)' failed (nm-connection-editor:10577): GLib-CRITICAL **: g_variant_unref: assertion 'value != NULL' failed (nm-connection-editor:10577): GLib-GObject-CRITICAL **: g_object_unref: assertion 'G_IS_OBJECT (object)' failed ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: network-manager 0.9.8.4-0ubuntu3 ProcVersionSignature: Ubuntu 3.12.0-7.15-generic 3.12.4 Uname: Linux 3.12.0-7-generic x86_64 ApportVersion: 2.12.7-0ubuntu3 Architecture: amd64 CurrentDesktop: GNOME Date: Thu Dec 26 20:26:47 2013 IfupdownConfig: - # interfaces(5) file used by ifup(8) and ifdown(8) - auto lo - iface lo inet loopback + # interfaces(5) file used by ifup(8) and ifdown(8) + auto lo + iface lo inet loopback InstallationDate: Installed on 2013-10-15 (71 days ago) InstallationMedia: Ubuntu-GNOME 13.10 "Saucy Salamander" - Release amd64 (20131015) IpRoute: - default via 10.100.10.1 dev eth0 proto static - 10.100.10.0/24 dev eth0 proto kernel scope link src 10.100.10.8 metric 1 - 10.100.10.0/24 dev wlan0 proto kernel scope link src 10.100.10.12 metric 9 + default via 10.100.10.1 dev eth0 proto static + 10.100.10.0/24 dev eth0 proto kernel scope link src 10.100.10.8 metric 1 + 10.100.10.0/24 dev wlan0 proto kernel scope link src 10.100.10.12 metric 9 NetworkManager.state: - [main] - NetworkingEnabled=true - WirelessEnabled=true - WWANEnabled=true - WimaxEnabled=true + [main] + NetworkingEnabled=true + WirelessEnabled=true + WWANEnabled=true + WimaxEnabled=true ProcEnviron: - TERM=xterm - PATH=(custom, no user) - XDG_RUNTIME_DIR= - LANG=pl_PL.UTF-8 - SHELL=/bin/bash + TERM=xterm + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=pl_PL.UTF-8 + SHELL=/bin/bash SourcePackage: network-manager UpgradeStatus: Upgraded to trusty on 2013-11-05 (51 days ago) nmcli-con: - NAME UUID TYPE TIMESTAMPTIMESTAMP-REAL AUTOCONNECT READONLY DBUS-PATH - Połączenie przewodowe 1 8e81b03d-3449-47be-838b-b034b6566876 802-3-ethernet1388085776 czw, 26 gru 2013, 20:22:56 yes no /org/freedesktop/NetworkManag
[Touch-packages] [Bug 1429185] Re: Restart button in Additional Drivers does not restart Xubuntu
Still the same problem on a fully updated xubuntu wily
$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu 15.10
Release:15.10
Codename: wily
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to software-properties in
Ubuntu.
https://bugs.launchpad.net/bugs/1429185
Title:
Restart button in Additional Drivers does not restart Xubuntu
Status in software-properties package in Ubuntu:
Confirmed
Bug description:
After changing a driver in Additional Drivers tab of Software &
Updates, a message tells me a restart ('You need to restart the
computer to complete the driver changes.') is needed and introduces a
button to restart the system. This button does not seem to do anything
in Xubuntu 14.04.2.
Upon running software-properties-gtk through terminal and then
clicking the restart button, these lines are printed:
Traceback (most recent call last):
File
"/usr/lib/python3/dist-packages/softwareproperties/gtk/SoftwarePropertiesGtk.py",
line 1091, in on_driver_restart_clicked
subprocess.call(['gnome-session-quit', '--reboot'])
File "/usr/lib/python3.4/subprocess.py", line 533, in call
with Popen(*popenargs, **kwargs) as p:
File "/usr/lib/python3.4/subprocess.py", line 848, in __init__
restore_signals, start_new_session)
File "/usr/lib/python3.4/subprocess.py", line 1446, in _execute_child
raise child_exception_type(errno_num, err_msg)
FileNotFoundError: [Errno 2] No such file or directory: 'gnome-session-quit'
'gnome-session-quit' does not work on Xubuntu with a fresh install.
ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: software-properties-gtk 0.92.37.3
ProcVersionSignature: Ubuntu 3.16.0-30.40~14.04.1-generic 3.16.7-ckt3
Uname: Linux 3.16.0-30-generic x86_64
ApportVersion: 2.14.1-0ubuntu3.7
Architecture: amd64
CasperVersion: 1.340
CurrentDesktop: XFCE
Date: Fri Mar 6 15:45:48 2015
LiveMediaBuild: Xubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 (20150218.1)
PackageArchitecture: all
ProcEnviron:
TERM=xterm
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=en_US.UTF-8
SHELL=/bin/bash
SourcePackage: software-properties
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1429185/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 140017] Re: tracker doesn't follow symlinks
Old issue, but my favorite search engine seems to find this report more easily than this upstreaam report https://bugzilla.gnome.org/show_bug.cgi?id=726264 ** Bug watch added: GNOME Bug Tracker #726264 https://bugzilla.gnome.org/show_bug.cgi?id=726264 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to tracker in Ubuntu. https://bugs.launchpad.net/bugs/140017 Title: tracker doesn't follow symlinks Status in tracker package in Ubuntu: Won't Fix Bug description: I have several drives in my machine. From each drive, I've symlinked a few folders into my home folder. There seems to be no way to tell trackerd to automatically follow these without manually specifying the files on the drives. This is workable but unfortunate, since from time to time I move the files between drives, and I'm used to other programs being fine with it as long as the symlink is updated. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tracker/+bug/140017/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1254085] Re: ssh fails to connect to VPN host - hangs at 'expecting SSH2_MSG_KEX_ECDH_REPLY'
I've had the same issue on 14.04, using cisco vpn client (horrific) , connecting to a linux machine or freebsd machine, setting MTU to 1200 helped as well. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/1254085 Title: ssh fails to connect to VPN host - hangs at 'expecting SSH2_MSG_KEX_ECDH_REPLY' Status in openssh package in Ubuntu: Confirmed Bug description: ssh -vvv is failing for me where is a VPN system. VPN is configured and connected via network-manager. Last messages from ssh (hangs forever): debug2: kex_parse_kexinit: none,z...@openssh.com debug2: kex_parse_kexinit: none,z...@openssh.com debug2: kex_parse_kexinit: debug2: kex_parse_kexinit: debug2: kex_parse_kexinit: first_kex_follows 0 debug2: kex_parse_kexinit: reserved 0 debug2: mac_setup: found hmac-md5 debug1: kex: server->client aes128-ctr hmac-md5 none debug2: mac_setup: found hmac-md5 debug1: kex: client->server aes128-ctr hmac-md5 none debug1: sending SSH2_MSG_KEX_ECDH_INIT debug1: expecting SSH2_MSG_KEX_ECDH_REPLY = Workaround = $ sudo apt-get install putty $ putty This works perfectly. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: openssh-client 1:6.4p1-1 ProcVersionSignature: Ubuntu 3.12.0-3.8-generic 3.12.0 Uname: Linux 3.12.0-3-generic i686 NonfreeKernelModules: nvidia ApportVersion: 2.12.7-0ubuntu1 Architecture: i386 CurrentDesktop: Unity Date: Fri Nov 22 15:37:18 2013 InstallationDate: Installed on 2010-10-21 (1128 days ago) InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release i386 (20101007) RelatedPackageVersions: ssh-askpass 1:1.2.4.1-9 libpam-sshN/A keychain 2.7.1-1 ssh-askpass-gnome 1:6.4p1-1 SSHClientVersion: OpenSSH_6.4p1 Ubuntu-1, OpenSSL 1.0.1e 11 Feb 2013 SourcePackage: openssh UpgradeStatus: Upgraded to trusty on 2013-11-01 (20 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1254085/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1406712] Re: NetworkManager crashes every few hours with Lubuntu 14.04.1, removing applet from lxpanel.
A friend suggested just to accept the crashes and to restart the application by a trivial loop, so I have some ( while :; do nm-applet iiig_log lost nm-applet ## log entries from my GSM scripts sleep 5## problem high-frequency looping done; ) >> 3g.log 2>&1 & >From the resulting log entries I can present some NM messages around crashing last Monday (they really show "every few hours"): -- ** (nm-applet:28364): CRITICAL **: nm_client_get_manager_running: assertion 'NM_IS_CLIENT (client)' failed ** (nm-applet:28364): CRITICAL **: nm_client_get_state: assertion 'NM_IS_CLIENT (client)' failed ./benno.sh: Zeile 6: 28364 Speicherzugriffsfehler (Speicherabzug geschrieben) nm-applet lost nm-applet -- 09:10:45, Montag connected 09:10:51 nm-applet-Message: using fallback from indicator to GtkStatusIcon -- (nm-applet:3322): GLib-CRITICAL **: Source ID 71 was not found when attempting to remove it (nm-applet:3322): GLib-CRITICAL **: Source ID 1324 was not found when attempting to remove it ./benno.sh: Zeile 6: 3322 Speicherzugriffsfehler (Speicherabzug geschrieben) nm-applet lost nm-applet -- 10:36:04, Montag nm-applet-Message: using fallback from indicator to GtkStatusIcon -- ** (nm-applet:5764): WARNING **: async_got_type: could not read properties for /org/freedesktop/NetworkManager/Devices/4: Method "Get" with signature "ss" on interface "org.freedesktop.DBus.Properties" doesn't exist -- (nm-applet:5764): GLib-CRITICAL **: Source ID 82 was not found when attempting to remove it (nm-applet:5764): GLib-CRITICAL **: Source ID 4456 was not found when attempting to remove it ./benno.sh: Zeile 6: 5764 Speicherzugriffsfehler (Speicherabzug geschrieben) nm-applet lost nm-applet -- 14:33:36, Montag nm-applet-Message: using fallback from indicator to GtkStatusIcon -- (nm-applet:10796): GLib-CRITICAL **: Source ID 82 was not found when attempting to remove it (nm-applet:10796): GLib-CRITICAL **: Source ID 596 was not found when attempting to remove it ./benno.sh: Zeile 6: 10796 Speicherzugriffsfehler (Speicherabzug geschrieben) nm-applet lost nm-applet -- 14:41:57, Montag nm-applet-Message: using fallback from indicator to GtkStatusIcon -- ** (nm-applet:11451): CRITICAL **: nm_client_get_state: assertion 'NM_IS_CLIENT (client)' failed (nm-applet:11451): Gtk-CRITICAL **: gtk_status_icon_set_visible: assertion 'GTK_IS_STATUS_ICON (status_icon)' failed ./benno.sh: Zeile 6: 11451 Speicherzugriffsfehler (Speicherabzug geschrieben) nm-applet lost nm-applet -- 20:38:24, Montag nm-applet-Message: using fallback from indicator to GtkStatusIcon -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1406712 Title: NetworkManager crashes every few hours with Lubuntu 14.04.1, removing applet from lxpanel. Status in network-manager package in Ubuntu: New Bug description: Sometimes I don't find any way to get it back without restarting. (I don't like restarting because then I must re-open at least 5 LXTerminal tabs I use in every session.) Sometimes I even can't use WvDial anymore after certain NetworkManager crashes, "Invalid dial command", maybe related modem key management by NetworkManager and ...!? Yes, I usually connect to the web by UMTS; alternatively sometimes by LAN, rarely by WLAN. I like NetworkManager for its notifications and its icons in the panel. This has happened since I switched to Lubuntu 14.04.1. With Lubuntu 12.10 and Lubuntu 13.04, there only was the "enable mobile broadband" problem for which I had workarounds. Sometimes nm-applet even collapses when it connects successfully. lubuntu@lubuntu:~$ apt-cache policy network-manager network-manager: Installiert: 0.9.8.8-0ubuntu7 Installationskandidat: 0.9.8.8-0ubuntu7 Versionstabelle: *** 0.9.8.8-0ubuntu7 0 500 http://archive.ubuntu.com/ubuntu/ trusty/main i386 Packages 100 /var/lib/dpkg/status (more like this already have been gathered by apport) ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: network-manager 0.9.8.8-0ubuntu7 ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4 Uname: Linux 3.13.0-32-generic i686 ApportVersion: 2.14.1-0ubuntu3.2 Architecture: i386 CRDA: Error: [Errno 2] Datei oder Verzeichnis nicht gefunden: 'iw' CasperVersion: 1.340 CurrentDesktop: LXDE Date: Wed Dec 31 06:49:22 2014 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback IpRoute: default via 10.64.64.64 dev ppp0 proto static 10.64.64.64 dev ppp0 proto kernel scope link src 10.222.214.5 LiveMediaBuild: Lubuntu 14.04.1 LTS "Trusty Tahr" - Release i386 (20140722.2) NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabl
[Touch-packages] [Bug 1423336] [NEW] package libc-bin 2.19-0ubuntu6.5 failed to install/upgrade: el subproceso instalado el script post-installation devolvió el código de salida de error 135
Public bug reported: 1) Description: Ubuntu 14.04.2 LTS Release:14.04 2) libc-bin: Instalados: 2.19-0ubuntu6.5 Candidato: 2.19-0ubuntu6.5 Tabla de versión: *** 2.19-0ubuntu6.5 0 500 http://archive.ubuntu.com/ubuntu/ trusty-updates/main amd64 Packages 100 /var/lib/dpkg/status 2.19-0ubuntu6.4 0 500 http://archive.ubuntu.com/ubuntu/ trusty-security/main amd64 Packages 2.19-0ubuntu6 0 500 http://archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages 3) install the update 4) failed doing so ProblemType: Package DistroRelease: Ubuntu 14.04 Package: libc-bin 2.19-0ubuntu6.5 ProcVersionSignature: Ubuntu 3.13.0-45.74-generic 3.13.11-ckt13 Uname: Linux 3.13.0-45-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.6 Architecture: amd64 Date: Wed Feb 18 17:20:35 2015 Dependencies: gcc-4.9-base 4.9.1-0ubuntu1 libc6 2.19-0ubuntu6.5 libcap2 1:2.24-0ubuntu2 libgcc1 1:4.9.1-0ubuntu1 multiarch-support 2.19-0ubuntu6.5 DuplicateSignature: package:libc-bin:2.19-0ubuntu6.5:el subproceso instalado el script post-installation devolvió el código de salida de error 135 ErrorMessage: el subproceso instalado el script post-installation devolvió el código de salida de error 135 InstallationDate: Installed on 2014-04-15 (308 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Beta amd64 (20140326) SourcePackage: eglibc Title: package libc-bin 2.19-0ubuntu6.5 failed to install/upgrade: el subproceso instalado el script post-installation devolvió el código de salida de error 135 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: eglibc (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package need-duplicate-check trusty -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to eglibc in Ubuntu. https://bugs.launchpad.net/bugs/1423336 Title: package libc-bin 2.19-0ubuntu6.5 failed to install/upgrade: el subproceso instalado el script post-installation devolvió el código de salida de error 135 Status in eglibc package in Ubuntu: New Bug description: 1) Description: Ubuntu 14.04.2 LTS Release: 14.04 2) libc-bin: Instalados: 2.19-0ubuntu6.5 Candidato: 2.19-0ubuntu6.5 Tabla de versión: *** 2.19-0ubuntu6.5 0 500 http://archive.ubuntu.com/ubuntu/ trusty-updates/main amd64 Packages 100 /var/lib/dpkg/status 2.19-0ubuntu6.4 0 500 http://archive.ubuntu.com/ubuntu/ trusty-security/main amd64 Packages 2.19-0ubuntu6 0 500 http://archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages 3) install the update 4) failed doing so ProblemType: Package DistroRelease: Ubuntu 14.04 Package: libc-bin 2.19-0ubuntu6.5 ProcVersionSignature: Ubuntu 3.13.0-45.74-generic 3.13.11-ckt13 Uname: Linux 3.13.0-45-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.6 Architecture: amd64 Date: Wed Feb 18 17:20:35 2015 Dependencies: gcc-4.9-base 4.9.1-0ubuntu1 libc6 2.19-0ubuntu6.5 libcap2 1:2.24-0ubuntu2 libgcc1 1:4.9.1-0ubuntu1 multiarch-support 2.19-0ubuntu6.5 DuplicateSignature: package:libc-bin:2.19-0ubuntu6.5:el subproceso instalado el script post-installation devolvió el código de salida de error 135 ErrorMessage: el subproceso instalado el script post-installation devolvió el código de salida de error 135 InstallationDate: Installed on 2014-04-15 (308 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Beta amd64 (20140326) SourcePackage: eglibc Title: package libc-bin 2.19-0ubuntu6.5 failed to install/upgrade: el subproceso instalado el script post-installation devolvió el código de salida de error 135 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/eglibc/+bug/1423336/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1406712] Re: NetworkManager crashes every few hours with Lubuntu 14.04.1, removing applet from lxpanel.
I believe that
CRDA: Error: [Errno 2] Datei oder Verzeichnis nicht gefunden: 'iw'
('iw' not found) is essential.
Cf. also the "expired" #1387119 with the same error message on a German
installation of Lubuntu 14.10.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1406712
Title:
NetworkManager crashes every few hours with Lubuntu 14.04.1, removing
applet from lxpanel.
Status in network-manager package in Ubuntu:
New
Bug description:
Sometimes I don't find any way to get it back without restarting.
(I don't like restarting because then I must re-open
at least 5 LXTerminal tabs I use in every session.)
Sometimes I even can't use WvDial anymore after certain
NetworkManager crashes, "Invalid dial command", maybe
related modem key management by NetworkManager and ...!?
Yes, I usually connect to the web by UMTS; alternatively sometimes
by LAN, rarely by WLAN. I like NetworkManager for its
notifications and its icons in the panel.
This has happened since I switched to Lubuntu 14.04.1.
With Lubuntu 12.10 and Lubuntu 13.04, there only was
the "enable mobile broadband" problem for which I had
workarounds.
Sometimes nm-applet even collapses when it connects successfully.
lubuntu@lubuntu:~$ apt-cache policy network-manager
network-manager:
Installiert: 0.9.8.8-0ubuntu7
Installationskandidat: 0.9.8.8-0ubuntu7
Versionstabelle:
*** 0.9.8.8-0ubuntu7 0
500 http://archive.ubuntu.com/ubuntu/ trusty/main i386 Packages
100 /var/lib/dpkg/status
(more like this already have been gathered by apport)
ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: network-manager 0.9.8.8-0ubuntu7
ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4
Uname: Linux 3.13.0-32-generic i686
ApportVersion: 2.14.1-0ubuntu3.2
Architecture: i386
CRDA: Error: [Errno 2] Datei oder Verzeichnis nicht gefunden: 'iw'
CasperVersion: 1.340
CurrentDesktop: LXDE
Date: Wed Dec 31 06:49:22 2014
IfupdownConfig:
# interfaces(5) file used by ifup(8) and ifdown(8)
auto lo
iface lo inet loopback
IpRoute:
default via 10.64.64.64 dev ppp0 proto static
10.64.64.64 dev ppp0 proto kernel scope link src 10.222.214.5
LiveMediaBuild: Lubuntu 14.04.1 LTS "Trusty Tahr" - Release i386 (20140722.2)
NetworkManager.state:
[main]
NetworkingEnabled=true
WirelessEnabled=true
WWANEnabled=true
WimaxEnabled=true
SourcePackage: network-manager
UpgradeStatus: No upgrade log present (probably fresh install)
WifiSyslog:
Dec 31 06:19:59 lubuntu kernel: [ 2054.511178] Media[9578]: segfault at 0 ip
(null) sp a46a493c error 14
Dec 31 06:23:09 lubuntu kernel: [ 2244.435972] perf samples too long (2519 >
2500), lowering kernel.perf_event_max_sample_rate to 5
nmcli-con:
NAME UUID TYPE
TIMESTAMPTIMESTAMP-REAL AUTOCONNECT READONLY
DBUS-PATH
Kabelnetzwerkverbindung 1 5b95bb40-4fe3-4710-986e-1d369bbcfb67
802-3-ethernet1420002089 Mi 31 Dez 2014 06:01:29 CETyes
no /org/freedesktop/NetworkManager/Settings/2
E-Plus Vorgabe3147833c-6fae-4422-b031-1fb5439dca8e gsm
1420004801 Mi 31 Dez 2014 06:46:41 CETyes no
/org/freedesktop/NetworkManager/Settings/1
pasing8c214b46-0633-4a14-b287-470ea2f63e01
802-11-wireless 0never yes
no /org/freedesktop/NetworkManager/Settings/0
nmcli-dev:
DEVICE TYPE STATE DBUS-PATH
ttyUSB2gsm connected
/org/freedesktop/NetworkManager/Devices/2
wlan1 802-11-wireless disconnected
/org/freedesktop/NetworkManager/Devices/1
eth1 802-3-ethernetunavailable
/org/freedesktop/NetworkManager/Devices/0
nmcli-nm:
RUNNING VERSIONSTATE NET-ENABLED WIFI-HARDWARE
WIFI WWAN-HARDWARE WWAN
running 0.9.8.8connected enabled enabled
enabledenabled enabled
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1406712/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1406712] Re: NetworkManager crashes every few hours with Lubuntu 14.04.1, removing applet from lxpanel.
A first line saying that I often restart NM by nm-applet & seems to have been removed from my expanded report, below heading. Crashes seem to be accompanied with (nm-applet:6848): GLib-CRITICAL **: Source ID 107 was not found when attempting to remove it as in http://askubuntu.com/questions/506824/nm-applet-does-not-work- ubuntu-14-04. I tried their advice to sudo apt-get install --reinstall network-manager which seemed to change something … not sure, maybe a new strange message appeared instead. I don't want to follow their GNOME-related ideas with Lubuntu, and I think nothing is wrong with the "fallback" message after nm-applet &. Maybe really notable: * occurrs with fragile mobile broadband connection * the installation is live persistent on USB pendrive, with modest upgradings. I have another similar installation heavily upgraded, it behaves similar regarding NetworkManager; I use too rarely to report about it. Another funny circumstance is that I have sudo rfkill block wifi in an autostart script, but after some breakdowns of connection/nm-applet/NM, LC_ALL=C nmcli nm status reports WIFI to be enabled, and the applet displays available WLAN points. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1406712 Title: NetworkManager crashes every few hours with Lubuntu 14.04.1, removing applet from lxpanel. Status in network-manager package in Ubuntu: New Bug description: Sometimes I don't find any way to get it back without restarting. (I don't like restarting because then I must re-open at least 5 LXTerminal tabs I use in every session.) Sometimes I even can't use WvDial anymore after certain NetworkManager crashes, "Invalid dial command", maybe related modem key management by NetworkManager and ...!? Yes, I usually connect to the web by UMTS; alternatively sometimes by LAN, rarely by WLAN. I like NetworkManager for its notifications and its icons in the panel. This has happened since I switched to Lubuntu 14.04.1. With Lubuntu 12.10 and Lubuntu 13.04, there only was the "enable mobile broadband" problem for which I had workarounds. Sometimes nm-applet even collapses when it connects successfully. lubuntu@lubuntu:~$ apt-cache policy network-manager network-manager: Installiert: 0.9.8.8-0ubuntu7 Installationskandidat: 0.9.8.8-0ubuntu7 Versionstabelle: *** 0.9.8.8-0ubuntu7 0 500 http://archive.ubuntu.com/ubuntu/ trusty/main i386 Packages 100 /var/lib/dpkg/status (more like this already have been gathered by apport) ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: network-manager 0.9.8.8-0ubuntu7 ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4 Uname: Linux 3.13.0-32-generic i686 ApportVersion: 2.14.1-0ubuntu3.2 Architecture: i386 CRDA: Error: [Errno 2] Datei oder Verzeichnis nicht gefunden: 'iw' CasperVersion: 1.340 CurrentDesktop: LXDE Date: Wed Dec 31 06:49:22 2014 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback IpRoute: default via 10.64.64.64 dev ppp0 proto static 10.64.64.64 dev ppp0 proto kernel scope link src 10.222.214.5 LiveMediaBuild: Lubuntu 14.04.1 LTS "Trusty Tahr" - Release i386 (20140722.2) NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) WifiSyslog: Dec 31 06:19:59 lubuntu kernel: [ 2054.511178] Media[9578]: segfault at 0 ip (null) sp a46a493c error 14 Dec 31 06:23:09 lubuntu kernel: [ 2244.435972] perf samples too long (2519 > 2500), lowering kernel.perf_event_max_sample_rate to 5 nmcli-con: NAME UUID TYPE TIMESTAMPTIMESTAMP-REAL AUTOCONNECT READONLY DBUS-PATH Kabelnetzwerkverbindung 1 5b95bb40-4fe3-4710-986e-1d369bbcfb67 802-3-ethernet1420002089 Mi 31 Dez 2014 06:01:29 CETyes no /org/freedesktop/NetworkManager/Settings/2 E-Plus Vorgabe3147833c-6fae-4422-b031-1fb5439dca8e gsm 1420004801 Mi 31 Dez 2014 06:46:41 CETyes no /org/freedesktop/NetworkManager/Settings/1 pasing8c214b46-0633-4a14-b287-470ea2f63e01 802-11-wireless 0never yes no /org/freedesktop/NetworkManager/Settings/0 nmcli-dev: DEVICE TYPE STATE DBUS-PATH ttyUSB2gsm connected /org/freedesktop/NetworkManager/Devices/2 wlan1 802-11-wireless disconnected /org/freed
[Touch-packages] [Bug 1406712] [NEW] NetworkManager crashes every few hours with Lubuntu 14.04.1, removing applet from lxpanel.
Public bug reported: Sometimes I don't find any way to get it back without restarting. (I don't like restarting because then I must re-open at least 5 LXTerminal tabs I use in every session.) Sometimes I even can't use WvDial anymore after certain NetworkManager crashes, "Invalid dial command", maybe related modem key management by NetworkManager and ...!? Yes, I usually connect to the web by UMTS; alternatively sometimes by LAN, rarely by WLAN. I like NetworkManager for its notifications and its icons in the panel. This has happened since I switched to Lubuntu 14.04.1. With Lubuntu 12.10 and Lubuntu 13.04, there only was the "enable mobile broadband" problem for which I had workarounds. Sometimes nm-applet even collapses when it connects successfully. lubuntu@lubuntu:~$ apt-cache policy network-manager network-manager: Installiert: 0.9.8.8-0ubuntu7 Installationskandidat: 0.9.8.8-0ubuntu7 Versionstabelle: *** 0.9.8.8-0ubuntu7 0 500 http://archive.ubuntu.com/ubuntu/ trusty/main i386 Packages 100 /var/lib/dpkg/status (more like this already have been gathered by apport) ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: network-manager 0.9.8.8-0ubuntu7 ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4 Uname: Linux 3.13.0-32-generic i686 ApportVersion: 2.14.1-0ubuntu3.2 Architecture: i386 CRDA: Error: [Errno 2] Datei oder Verzeichnis nicht gefunden: 'iw' CasperVersion: 1.340 CurrentDesktop: LXDE Date: Wed Dec 31 06:49:22 2014 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback IpRoute: default via 10.64.64.64 dev ppp0 proto static 10.64.64.64 dev ppp0 proto kernel scope link src 10.222.214.5 LiveMediaBuild: Lubuntu 14.04.1 LTS "Trusty Tahr" - Release i386 (20140722.2) NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) WifiSyslog: Dec 31 06:19:59 lubuntu kernel: [ 2054.511178] Media[9578]: segfault at 0 ip (null) sp a46a493c error 14 Dec 31 06:23:09 lubuntu kernel: [ 2244.435972] perf samples too long (2519 > 2500), lowering kernel.perf_event_max_sample_rate to 5 nmcli-con: NAME UUID TYPE TIMESTAMPTIMESTAMP-REAL AUTOCONNECT READONLY DBUS-PATH Kabelnetzwerkverbindung 1 5b95bb40-4fe3-4710-986e-1d369bbcfb67 802-3-ethernet1420002089 Mi 31 Dez 2014 06:01:29 CETyes no /org/freedesktop/NetworkManager/Settings/2 E-Plus Vorgabe3147833c-6fae-4422-b031-1fb5439dca8e gsm 1420004801 Mi 31 Dez 2014 06:46:41 CETyes no /org/freedesktop/NetworkManager/Settings/1 pasing8c214b46-0633-4a14-b287-470ea2f63e01 802-11-wireless 0never yes no /org/freedesktop/NetworkManager/Settings/0 nmcli-dev: DEVICE TYPE STATE DBUS-PATH ttyUSB2gsm connected /org/freedesktop/NetworkManager/Devices/2 wlan1 802-11-wireless disconnected /org/freedesktop/NetworkManager/Devices/1 eth1 802-3-ethernetunavailable /org/freedesktop/NetworkManager/Devices/0 nmcli-nm: RUNNING VERSIONSTATE NET-ENABLED WIFI-HARDWARE WIFI WWAN-HARDWARE WWAN running 0.9.8.8connected enabled enabled enabledenabled enabled ** Affects: network-manager (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 trusty -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1406712 Title: NetworkManager crashes every few hours with Lubuntu 14.04.1, removing applet from lxpanel. Status in network-manager package in Ubuntu: New Bug description: Sometimes I don't find any way to get it back without restarting. (I don't like restarting because then I must re-open at least 5 LXTerminal tabs I use in every session.) Sometimes I even can't use WvDial anymore after certain NetworkManager crashes, "Invalid dial command", maybe related modem key management by NetworkManager and ...!? Yes, I usually connect to the web by UMTS; alternatively sometimes by LAN, rarely by WLAN. I like NetworkManager for its notifications and its icons in the panel. This has happened since I switched to Lubuntu 14.04.1. With Lubuntu 12.10 and Lubuntu 13.04, there only was the "enable mobile broadband" problem for which I had workarounds. Sometimes nm-applet even collapses when it connects successfully. lubuntu@lubuntu:~$ apt-cache policy netw
[Touch-packages] [Bug 1385537] Re: logrotate does not rotate logs (rsyslog)
Now I have guessed (at bug 1254614) that the developers have disabled
rotating and cron jobs for live sessions *intentionally*. (And I am
sorry and annoyed about all my typos above, still wondering how I could
avoid them without a preview function here.)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to logrotate in Ubuntu.
https://bugs.launchpad.net/bugs/1385537
Title:
logrotate does not rotate logs (rsyslog)
Status in “logrotate” package in Ubuntu:
New
Bug description:
(Expected: auth.log, kern.log, syslog rotated "daily"/"weakly"
according to /etd/..., actually: no rotation even after weeks; and
manual forcing may fail.)
Being concerned about the amount of GBs that a Lubuntu persistent
installation on a USB flash drive may write per day, I observed that
auth.log, kern.log, and syslog grow to many MB. They may get about
1000 entries a day, resulting in many GB load for the USB drive per
day. I learnt about logrotate and rsyslog and modified
/etc/logrotate.conf and /etc/logrotate.d/rsyslog. Yet none had any
effect.
I have kept USB installations of Lubuntu 14.04.1 in parallel and saved
them after some days, so I could report about a number of experiments.
E.g., I started 2014-08-31, and I have a snapshot from 2014-09-22
where I had not changed /etc/logrotate.conf, neither
/etc/logrotate.d/rsyslog ("daily", "weekly"), and the three files
still have the entries from 2014-08-31, although three "weeks" had
passed.
#51879 (2006) and #1278193 (Feb 2014) are very similar, however:
* I observed growing kern.log and syslog to more than 100MB (to "out of
memory" finally) in some installations in summer 2013; in later installations
the same year and before 14.04, the problem vanished (I watched the sizes
manually/regularly – difference to #51879: after 2006, problem recurred,
vanished, recurred).
* With Lubuntu 14.04.1 recently, I changed "weekly" into "daily" in
/etc/logratate.conf and in /etc/logrotate.d/rsyslog, but three days later
auth.log, kern.log, and syslog still had no older copies and still contained
messages from the last three days. Then I did sudo logrotate-f
/etc/logrotate.conf, which works, but still after another three days those
three logs had not been rotated.
Actually I also have tried sudo logrotate -f /etc/logrotate.d/rsyslog,
and the result has been exactly as #1258202 (2013). As opposed to the
latter report and that for #1278193, I am unable to guess from which
changes the problems might have resulted.
ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: logrotate 3.8.7-1ubuntu1
ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4
Uname: Linux 3.13.0-32-generic i686
ApportVersion: 2.14.1-0ubuntu3.2
Architecture: i386
CasperVersion: 1.340
CurrentDesktop: LXDE
Date: Sat Oct 25 01:02:40 2014
LiveMediaBuild: Lubuntu 14.04.1 LTS "Trusty Tahr" - Release i386 (20140722.2)
SourcePackage: logrotate
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/logrotate/+bug/1385537/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1385537] Re: logrotate does not rotate logs (rsyslog)
my (rsyslog) logs *are* rotatated now. I found that /usr/sbin/anacron is
a symbolic link to /bin/true as in bug #1254614 and renamed
/usr/sbin/anacron.distrib found with bug #1254614 into
/usr/sbin/anacron. As opposed to there, this has not been undone so far.
I find the symlink in some saved persistence files/partitions, even
(somewaht opposed to bug #bug #1254614) with Xubuntu 12.10. There is no
anacron symlink in the live iso, but it's there even after a live boot
without persistence.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to logrotate in Ubuntu.
https://bugs.launchpad.net/bugs/1385537
Title:
logrotate does not rotate logs (rsyslog)
Status in “logrotate” package in Ubuntu:
New
Bug description:
(Expected: auth.log, kern.log, syslog rotated "daily"/"weakly"
according to /etd/..., actually: no rotation even after weeks; and
manual forcing may fail.)
Being concerned about the amount of GBs that a Lubuntu persistent
installation on a USB flash drive may write per day, I observed that
auth.log, kern.log, and syslog grow to many MB. They may get about
1000 entries a day, resulting in many GB load for the USB drive per
day. I learnt about logrotate and rsyslog and modified
/etc/logrotate.conf and /etc/logrotate.d/rsyslog. Yet none had any
effect.
I have kept USB installations of Lubuntu 14.04.1 in parallel and saved
them after some days, so I could report about a number of experiments.
E.g., I started 2014-08-31, and I have a snapshot from 2014-09-22
where I had not changed /etc/logrotate.conf, neither
/etc/logrotate.d/rsyslog ("daily", "weekly"), and the three files
still have the entries from 2014-08-31, although three "weeks" had
passed.
#51879 (2006) and #1278193 (Feb 2014) are very similar, however:
* I observed growing kern.log and syslog to more than 100MB (to "out of
memory" finally) in some installations in summer 2013; in later installations
the same year and before 14.04, the problem vanished (I watched the sizes
manually/regularly – difference to #51879: after 2006, problem recurred,
vanished, recurred).
* With Lubuntu 14.04.1 recently, I changed "weekly" into "daily" in
/etc/logratate.conf and in /etc/logrotate.d/rsyslog, but three days later
auth.log, kern.log, and syslog still had no older copies and still contained
messages from the last three days. Then I did sudo logrotate-f
/etc/logrotate.conf, which works, but still after another three days those
three logs had not been rotated.
Actually I also have tried sudo logrotate -f /etc/logrotate.d/rsyslog,
and the result has been exactly as #1258202 (2013). As opposed to the
latter report and that for #1278193, I am unable to guess from which
changes the problems might have resulted.
ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: logrotate 3.8.7-1ubuntu1
ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4
Uname: Linux 3.13.0-32-generic i686
ApportVersion: 2.14.1-0ubuntu3.2
Architecture: i386
CasperVersion: 1.340
CurrentDesktop: LXDE
Date: Sat Oct 25 01:02:40 2014
LiveMediaBuild: Lubuntu 14.04.1 LTS "Trusty Tahr" - Release i386 (20140722.2)
SourcePackage: logrotate
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/logrotate/+bug/1385537/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1385537] Re: logrotate does not rotate logs (rsyslog)
@#5: no, bug #13854564 produces an error on `# logrotate
/etc/logrotate.conf`, while the same command works properly as expected
here.
I have now seen (guessed) that /etc/cron.daily/logrotate is not run
(status file's mtime is from running logrotate manually),
/etc/cron.daily/apport is not run (should remove old crash reports, but
I still have all of them), and /etc/cron.daily/dpkg is not run
(/var/backups/ is empty); and finally, by grepping from syslogs, that
anacron has been "considered" (lines from /etc/cron.*/0anachron), but
never actually been run. So the present problem has little to do with
logrotate, it's only a symptom of an anacron problem. I see in forums
that this sometimes happens in a variety of rather individual, weird
situations, I think I now must track the anachron problem on my own, and
the present report no longer should be considered, sorry.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to logrotate in Ubuntu.
https://bugs.launchpad.net/bugs/1385537
Title:
logrotate does not rotate logs (rsyslog)
Status in “logrotate” package in Ubuntu:
New
Bug description:
(Expected: auth.log, kern.log, syslog rotated "daily"/"weakly"
according to /etd/..., actually: no rotation even after weeks; and
manual forcing may fail.)
Being concerned about the amount of GBs that a Lubuntu persistent
installation on a USB flash drive may write per day, I observed that
auth.log, kern.log, and syslog grow to many MB. They may get about
1000 entries a day, resulting in many GB load for the USB drive per
day. I learnt about logrotate and rsyslog and modified
/etc/logrotate.conf and /etc/logrotate.d/rsyslog. Yet none had any
effect.
I have kept USB installations of Lubuntu 14.04.1 in parallel and saved
them after some days, so I could report about a number of experiments.
E.g., I started 2014-08-31, and I have a snapshot from 2014-09-22
where I had not changed /etc/logrotate.conf, neither
/etc/logrotate.d/rsyslog ("daily", "weekly"), and the three files
still have the entries from 2014-08-31, although three "weeks" had
passed.
#51879 (2006) and #1278193 (Feb 2014) are very similar, however:
* I observed growing kern.log and syslog to more than 100MB (to "out of
memory" finally) in some installations in summer 2013; in later installations
the same year and before 14.04, the problem vanished (I watched the sizes
manually/regularly – difference to #51879: after 2006, problem recurred,
vanished, recurred).
* With Lubuntu 14.04.1 recently, I changed "weekly" into "daily" in
/etc/logratate.conf and in /etc/logrotate.d/rsyslog, but three days later
auth.log, kern.log, and syslog still had no older copies and still contained
messages from the last three days. Then I did sudo logrotate-f
/etc/logrotate.conf, which works, but still after another three days those
three logs had not been rotated.
Actually I also have tried sudo logrotate -f /etc/logrotate.d/rsyslog,
and the result has been exactly as #1258202 (2013). As opposed to the
latter report and that for #1278193, I am unable to guess from which
changes the problems might have resulted.
ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: logrotate 3.8.7-1ubuntu1
ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4
Uname: Linux 3.13.0-32-generic i686
ApportVersion: 2.14.1-0ubuntu3.2
Architecture: i386
CasperVersion: 1.340
CurrentDesktop: LXDE
Date: Sat Oct 25 01:02:40 2014
LiveMediaBuild: Lubuntu 14.04.1 LTS "Trusty Tahr" - Release i386 (20140722.2)
SourcePackage: logrotate
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/logrotate/+bug/1385537/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1385537] Re: logrotate does not rotate logs (rsyslog)
auth.log, kern.log, syslog and their old versions by find / -user/group
are the only files on my system with owning user syslog and owning group
adm. This is what the report is about. Other logs have been rotated.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to logrotate in Ubuntu.
https://bugs.launchpad.net/bugs/1385537
Title:
logrotate does not rotate logs (rsyslog)
Status in “logrotate” package in Ubuntu:
New
Bug description:
(Expected: auth.log, kern.log, syslog rotated "daily"/"weakly"
according to /etd/..., actually: no rotation even after weeks; and
manual forcing may fail.)
Being concerned about the amount of GBs that a Lubuntu persistent
installation on a USB flash drive may write per day, I observed that
auth.log, kern.log, and syslog grow to many MB. They may get about
1000 entries a day, resulting in many GB load for the USB drive per
day. I learnt about logrotate and rsyslog and modified
/etc/logrotate.conf and /etc/logrotate.d/rsyslog. Yet none had any
effect.
I have kept USB installations of Lubuntu 14.04.1 in parallel and saved
them after some days, so I could report about a number of experiments.
E.g., I started 2014-08-31, and I have a snapshot from 2014-09-22
where I had not changed /etc/logrotate.conf, neither
/etc/logrotate.d/rsyslog ("daily", "weekly"), and the three files
still have the entries from 2014-08-31, although three "weeks" had
passed.
#51879 (2006) and #1278193 (Feb 2014) are very similar, however:
* I observed growing kern.log and syslog to more than 100MB (to "out of
memory" finally) in some installations in summer 2013; in later installations
the same year and before 14.04, the problem vanished (I watched the sizes
manually/regularly – difference to #51879: after 2006, problem recurred,
vanished, recurred).
* With Lubuntu 14.04.1 recently, I changed "weekly" into "daily" in
/etc/logratate.conf and in /etc/logrotate.d/rsyslog, but three days later
auth.log, kern.log, and syslog still had no older copies and still contained
messages from the last three days. Then I did sudo logrotate-f
/etc/logrotate.conf, which works, but still after another three days those
three logs had not been rotated.
Actually I also have tried sudo logrotate -f /etc/logrotate.d/rsyslog,
and the result has been exactly as #1258202 (2013). As opposed to the
latter report and that for #1278193, I am unable to guess from which
changes the problems might have resulted.
ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: logrotate 3.8.7-1ubuntu1
ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4
Uname: Linux 3.13.0-32-generic i686
ApportVersion: 2.14.1-0ubuntu3.2
Architecture: i386
CasperVersion: 1.340
CurrentDesktop: LXDE
Date: Sat Oct 25 01:02:40 2014
LiveMediaBuild: Lubuntu 14.04.1 LTS "Trusty Tahr" - Release i386 (20140722.2)
SourcePackage: logrotate
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/logrotate/+bug/1385537/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1278193] Re: logrotate skip the rotation of many files under /var/log due to bad group ownership
@Vinny: I have /etc/logrotate.conf as of 2014-01-22 containing: # use the syslog group by default, since this is the owning group # of /var/log/syslog. su root syslog Yet according to `find / -user syslog' and `find / -group syslog', I have no files with owning group syslog, I have log files with owning user syslog. /var/log/syslog's owning user/group is as posted by Alex Dicianu. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to logrotate in Ubuntu. https://bugs.launchpad.net/bugs/1278193 Title: logrotate skip the rotation of many files under /var/log due to bad group ownership Status in “logrotate” package in Ubuntu: Confirmed Bug description: With the latest update to logrotate (3.8.7-1ubuntu1), the group ownership of /var/log was changed to "syslog" causing this kind of problem: # logrotate -df /etc/logrotate.d/rsyslog reading config file /etc/logrotate.d/rsyslog Handling 2 logs rotating pattern: /var/log/syslog forced from command line (7 rotations) empty log files are not rotated, old logs are removed considering log /var/log/syslog error: skipping "/var/log/syslog" because parent directory has insecure permissions (It's world writable or writable by group which is not "root") Set "su" directive in config file to tell logrotate which user/group should be used for rotation. ... # ls -la /var/ | grep log drwxrwxr-x 17 root syslog 4096 Feb 9 10:58 log $ lsb_release -rd Description: Ubuntu Trusty Tahr (development branch) Release: 14.04 $ apt-cache policy logrotate logrotate: Installed: 3.8.7-1ubuntu1 Candidate: 3.8.7-1ubuntu1 Version table: *** 3.8.7-1ubuntu1 0 500 http://archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: logrotate 3.8.7-1ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-8.27-generic 3.13.2 Uname: Linux 3.13.0-8-generic x86_64 ApportVersion: 2.13.2-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Sun Feb 9 17:19:41 2014 InstallationDate: Installed on 2014-01-26 (14 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140124) SourcePackage: logrotate UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/logrotate/+bug/1278193/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1385537] Re: logrotate does not rotate logs (rsyslog)
cf. #1258202 and #1278193 about owning group, here:
$ ls -ld /var/log
drwxrwxr-x 1 root fuse 4096 Okt 25 02:16 /var/log
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to logrotate in Ubuntu.
https://bugs.launchpad.net/bugs/1385537
Title:
logrotate does not rotate logs (rsyslog)
Status in “logrotate” package in Ubuntu:
New
Bug description:
(Expected: auth.log, kern.log, syslog rotated "daily"/"weakly"
according to /etd/..., actually: no rotation even after weeks; and
manual forcing may fail.)
Being concerned about the amount of GBs that a Lubuntu persistent
installation on a USB flash drive may write per day, I observed that
auth.log, kern.log, and syslog grow to many MB. They may get about
1000 entries a day, resulting in many GB load for the USB drive per
day. I learnt about logrotate and rsyslog and modified
/etc/logrotate.conf and /etc/logrotate.d/rsyslog. Yet none had any
effect.
I have kept USB installations of Lubuntu 14.04.1 in parallel and saved
them after some days, so I could report about a number of experiments.
E.g., I started 2014-08-31, and I have a snapshot from 2014-09-22
where I had not changed /etc/logrotate.conf, neither
/etc/logrotate.d/rsyslog ("daily", "weekly"), and the three files
still have the entries from 2014-08-31, although three "weeks" had
passed.
#51879 (2006) and #1278193 (Feb 2014) are very similar, however:
* I observed growing kern.log and syslog to more than 100MB (to "out of
memory" finally) in some installations in summer 2013; in later installations
the same year and before 14.04, the problem vanished (I watched the sizes
manually/regularly – difference to #51879: after 2006, problem recurred,
vanished, recurred).
* With Lubuntu 14.04.1 recently, I changed "weekly" into "daily" in
/etc/logratate.conf and in /etc/logrotate.d/rsyslog, but three days later
auth.log, kern.log, and syslog still had no older copies and still contained
messages from the last three days. Then I did sudo logrotate-f
/etc/logrotate.conf, which works, but still after another three days those
three logs had not been rotated.
Actually I also have tried sudo logrotate -f /etc/logrotate.d/rsyslog,
and the result has been exactly as #1258202 (2013). As opposed to the
latter report and that for #1278193, I am unable to guess from which
changes the problems might have resulted.
ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: logrotate 3.8.7-1ubuntu1
ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4
Uname: Linux 3.13.0-32-generic i686
ApportVersion: 2.14.1-0ubuntu3.2
Architecture: i386
CasperVersion: 1.340
CurrentDesktop: LXDE
Date: Sat Oct 25 01:02:40 2014
LiveMediaBuild: Lubuntu 14.04.1 LTS "Trusty Tahr" - Release i386 (20140722.2)
SourcePackage: logrotate
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/logrotate/+bug/1385537/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1258202] Re: recent group permissions change on /var/log cause logrotate errors
… and #1278193, sorry -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to logrotate in Ubuntu. https://bugs.launchpad.net/bugs/1258202 Title: recent group permissions change on /var/log cause logrotate errors Status in “logrotate” package in Ubuntu: Fix Released Bug description: The fix for bug #1256695 is causing logrotate to error out with: /etc/cron.daily/logrotate: error: skipping "/var/log/dpkg.log" because parent directory has insecure permissions (It's world writable or writable by group which is not "root") Set "su" directive in config file to tell logrotate which user/group should be used for rotation. error: skipping "/var/log/alternatives.log" because parent directory has insecure permissions (It's world writable or writable by group which is not "root") Set "su" directive in config file to tell logrotate which user/group should be used for rotation. error: skipping "/var/log/pm-suspend.log" because parent directory has insecure permissions (It's world writable or writable by group which is not "root") Set "su" directive in config file to tell logrotate which user/group should be used for rotation. error: skipping "/var/log/pm-powersave.log" because parent directory has insecure permissions (It's world writable or writable by group which is not "root") Set "su" directive in config file to tell logrotate which user/group should be used for rotation. error: skipping "/var/log/ppp-connect-errors" because parent directory has insecure permissions (It's world writable or writable by group which is not "root") Set "su" directive in config file to tell logrotate which user/group should be used for rotation. error: skipping "/var/log/syslog" because parent directory has insecure permissions (It's world writable or writable by group which is not "root") Set "su" directive in config file to tell logrotate which user/group should be used for rotation. error: skipping "/var/log/mail.info" because parent directory has insecure permissions (It's world writable or writable by group which is not "root") Set "su" directive in config file to tell logrotate which user/group should be used for rotation. error: skipping "/var/log/mail.warn" because parent directory has insecure permissions (It's world writable or writable by group which is not "root") Set "su" directive in config file to tell logrotate which user/group should be used for rotation. error: skipping "/var/log/mail.err" because parent directory has insecure permissions (It's world writable or writable by group which is not "root") Set "su" directive in config file to tell logrotate which user/group should be used for rotation. error: skipping "/var/log/mail.log" because parent directory has insecure permissions (It's world writable or writable by group which is not "root") Set "su" directive in config file to tell logrotate which user/group should be used for rotation. error: skipping "/var/log/daemon.log" because parent directory has insecure permissions (It's world writable or writable by group which is not "root") Set "su" directive in config file to tell logrotate which user/group should be used for rotation. error: skipping "/var/log/kern.log" because parent directory has insecure permissions (It's world writable or writable by group which is not "root") Set "su" directive in config file to tell logrotate which user/group should be used for rotation. error: skipping "/var/log/auth.log" because parent directory has insecure permissions (It's world writable or writable by group which is not "root") Set "su" directive in config file to tell logrotate which user/group should be used for rotation. error: skipping "/var/log/user.log" because parent directory has insecure permissions (It's world writable or writable by group which is not "root") Set "su" directive in config file to tell logrotate which user/group should be used for rotation. error: skipping "/var/log/lpr.log" because parent directory has insecure permissions (It's world writable or writable by group which is not "root") Set "su" directive in config file to tell logrotate which user/group should be used for rotation. error: skipping "/var/log/cron.log" because parent directory has insecure permissions (It's world writable or writable by group which is not "root") Set "su" directive in config file to tell logrotate which user/group should be used for rotation. error: skipping "/var/log/debug" because parent directory has insecure permissions (It's world writable or writable by group which is not "root") Set "su" directive in config file to tell logrotate which user/group should be used for rotation. error: skipping "/var/log/messages" because parent directory has insecure permissions (It's world writable or writable by group which is not "root") Set "su" directive in config file to tell logrotate which user/group should be
[Touch-packages] [Bug 1258202] Re: recent group permissions change on /var/log cause logrotate errors
aha, #1385537 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to logrotate in Ubuntu. https://bugs.launchpad.net/bugs/1258202 Title: recent group permissions change on /var/log cause logrotate errors Status in “logrotate” package in Ubuntu: Fix Released Bug description: The fix for bug #1256695 is causing logrotate to error out with: /etc/cron.daily/logrotate: error: skipping "/var/log/dpkg.log" because parent directory has insecure permissions (It's world writable or writable by group which is not "root") Set "su" directive in config file to tell logrotate which user/group should be used for rotation. error: skipping "/var/log/alternatives.log" because parent directory has insecure permissions (It's world writable or writable by group which is not "root") Set "su" directive in config file to tell logrotate which user/group should be used for rotation. error: skipping "/var/log/pm-suspend.log" because parent directory has insecure permissions (It's world writable or writable by group which is not "root") Set "su" directive in config file to tell logrotate which user/group should be used for rotation. error: skipping "/var/log/pm-powersave.log" because parent directory has insecure permissions (It's world writable or writable by group which is not "root") Set "su" directive in config file to tell logrotate which user/group should be used for rotation. error: skipping "/var/log/ppp-connect-errors" because parent directory has insecure permissions (It's world writable or writable by group which is not "root") Set "su" directive in config file to tell logrotate which user/group should be used for rotation. error: skipping "/var/log/syslog" because parent directory has insecure permissions (It's world writable or writable by group which is not "root") Set "su" directive in config file to tell logrotate which user/group should be used for rotation. error: skipping "/var/log/mail.info" because parent directory has insecure permissions (It's world writable or writable by group which is not "root") Set "su" directive in config file to tell logrotate which user/group should be used for rotation. error: skipping "/var/log/mail.warn" because parent directory has insecure permissions (It's world writable or writable by group which is not "root") Set "su" directive in config file to tell logrotate which user/group should be used for rotation. error: skipping "/var/log/mail.err" because parent directory has insecure permissions (It's world writable or writable by group which is not "root") Set "su" directive in config file to tell logrotate which user/group should be used for rotation. error: skipping "/var/log/mail.log" because parent directory has insecure permissions (It's world writable or writable by group which is not "root") Set "su" directive in config file to tell logrotate which user/group should be used for rotation. error: skipping "/var/log/daemon.log" because parent directory has insecure permissions (It's world writable or writable by group which is not "root") Set "su" directive in config file to tell logrotate which user/group should be used for rotation. error: skipping "/var/log/kern.log" because parent directory has insecure permissions (It's world writable or writable by group which is not "root") Set "su" directive in config file to tell logrotate which user/group should be used for rotation. error: skipping "/var/log/auth.log" because parent directory has insecure permissions (It's world writable or writable by group which is not "root") Set "su" directive in config file to tell logrotate which user/group should be used for rotation. error: skipping "/var/log/user.log" because parent directory has insecure permissions (It's world writable or writable by group which is not "root") Set "su" directive in config file to tell logrotate which user/group should be used for rotation. error: skipping "/var/log/lpr.log" because parent directory has insecure permissions (It's world writable or writable by group which is not "root") Set "su" directive in config file to tell logrotate which user/group should be used for rotation. error: skipping "/var/log/cron.log" because parent directory has insecure permissions (It's world writable or writable by group which is not "root") Set "su" directive in config file to tell logrotate which user/group should be used for rotation. error: skipping "/var/log/debug" because parent directory has insecure permissions (It's world writable or writable by group which is not "root") Set "su" directive in config file to tell logrotate which user/group should be used for rotation. error: skipping "/var/log/messages" because parent directory has insecure permissions (It's world writable or writable by group which is not "root") Set "su" directive in config file to tell logrotate which user/group should be used fo
[Touch-packages] [Bug 1385537] Re: logrotate does not rotate logs (rsyslog)
"weekly" indeed supported extremely "weakly"
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to logrotate in Ubuntu.
https://bugs.launchpad.net/bugs/1385537
Title:
logrotate does not rotate logs (rsyslog)
Status in “logrotate” package in Ubuntu:
New
Bug description:
(Expected: auth.log, kern.log, syslog rotated "daily"/"weakly"
according to /etd/..., actually: no rotation even after weeks; and
manual forcing may fail.)
Being concerned about the amount of GBs that a Lubuntu persistent
installation on a USB flash drive may write per day, I observed that
auth.log, kern.log, and syslog grow to many MB. They may get about
1000 entries a day, resulting in many GB load for the USB drive per
day. I learnt about logrotate and rsyslog and modified
/etc/logrotate.conf and /etc/logrotate.d/rsyslog. Yet none had any
effect.
I have kept USB installations of Lubuntu 14.04.1 in parallel and saved
them after some days, so I could report about a number of experiments.
E.g., I started 2014-08-31, and I have a snapshot from 2014-09-22
where I had not changed /etc/logrotate.conf, neither
/etc/logrotate.d/rsyslog ("daily", "weekly"), and the three files
still have the entries from 2014-08-31, although three "weeks" had
passed.
#51879 (2006) and #1278193 (Feb 2014) are very similar, however:
* I observed growing kern.log and syslog to more than 100MB (to "out of
memory" finally) in some installations in summer 2013; in later installations
the same year and before 14.04, the problem vanished (I watched the sizes
manually/regularly – difference to #51879: after 2006, problem recurred,
vanished, recurred).
* With Lubuntu 14.04.1 recently, I changed "weekly" into "daily" in
/etc/logratate.conf and in /etc/logrotate.d/rsyslog, but three days later
auth.log, kern.log, and syslog still had no older copies and still contained
messages from the last three days. Then I did sudo logrotate-f
/etc/logrotate.conf, which works, but still after another three days those
three logs had not been rotated.
Actually I also have tried sudo logrotate -f /etc/logrotate.d/rsyslog,
and the result has been exactly as #1258202 (2013). As opposed to the
latter report and that for #1278193, I am unable to guess from which
changes the problems might have resulted.
ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: logrotate 3.8.7-1ubuntu1
ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4
Uname: Linux 3.13.0-32-generic i686
ApportVersion: 2.14.1-0ubuntu3.2
Architecture: i386
CasperVersion: 1.340
CurrentDesktop: LXDE
Date: Sat Oct 25 01:02:40 2014
LiveMediaBuild: Lubuntu 14.04.1 LTS "Trusty Tahr" - Release i386 (20140722.2)
SourcePackage: logrotate
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/logrotate/+bug/1385537/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1385537] [NEW] logrotate does not rotate logs (rsyslog)
Public bug reported:
(Expected: auth.log, kern.log, syslog rotated "daily"/"weakly" according
to /etd/..., actually: no rotation even after weeks; and manual forcing
may fail.)
Being concerned about the amount of GBs that a Lubuntu persistent
installation on a USB flash drive may write per day, I observed that
auth.log, kern.log, and syslog grow to many MB. They may get about 1000
entries a day, resulting in many GB load for the USB drive per day. I
learnt about logrotate and rsyslog and modified /etc/logrotate.conf and
/etc/logrotate.d/rsyslog. Yet none had any effect.
I have kept USB installations of Lubuntu 14.04.1 in parallel and saved
them after some days, so I could report about a number of experiments.
E.g., I started 2014-08-31, and I have a snapshot from 2014-09-22 where
I had not changed /etc/logrotate.conf, neither /etc/logrotate.d/rsyslog
("daily", "weekly"), and the three files still have the entries from
2014-08-31, although three "weeks" had passed.
#51879 (2006) and #1278193 (Feb 2014) are very similar, however:
* I observed growing kern.log and syslog to more than 100MB (to "out of memory"
finally) in some installations in summer 2013; in later installations the same
year and before 14.04, the problem vanished (I watched the sizes
manually/regularly – difference to #51879: after 2006, problem recurred,
vanished, recurred).
* With Lubuntu 14.04.1 recently, I changed "weekly" into "daily" in
/etc/logratate.conf and in /etc/logrotate.d/rsyslog, but three days later
auth.log, kern.log, and syslog still had no older copies and still contained
messages from the last three days. Then I did sudo logrotate-f
/etc/logrotate.conf, which works, but still after another three days those
three logs had not been rotated.
Actually I also have tried sudo logrotate -f /etc/logrotate.d/rsyslog,
and the result has been exactly as #1258202 (2013). As opposed to the
latter report and that for #1278193, I am unable to guess from which
changes the problems might have resulted.
ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: logrotate 3.8.7-1ubuntu1
ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4
Uname: Linux 3.13.0-32-generic i686
ApportVersion: 2.14.1-0ubuntu3.2
Architecture: i386
CasperVersion: 1.340
CurrentDesktop: LXDE
Date: Sat Oct 25 01:02:40 2014
LiveMediaBuild: Lubuntu 14.04.1 LTS "Trusty Tahr" - Release i386 (20140722.2)
SourcePackage: logrotate
UpgradeStatus: No upgrade log present (probably fresh install)
** Affects: logrotate (Ubuntu)
Importance: Undecided
Status: New
** Tags: apport-bug i386 trusty
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to logrotate in Ubuntu.
https://bugs.launchpad.net/bugs/1385537
Title:
logrotate does not rotate logs (rsyslog)
Status in “logrotate” package in Ubuntu:
New
Bug description:
(Expected: auth.log, kern.log, syslog rotated "daily"/"weakly"
according to /etd/..., actually: no rotation even after weeks; and
manual forcing may fail.)
Being concerned about the amount of GBs that a Lubuntu persistent
installation on a USB flash drive may write per day, I observed that
auth.log, kern.log, and syslog grow to many MB. They may get about
1000 entries a day, resulting in many GB load for the USB drive per
day. I learnt about logrotate and rsyslog and modified
/etc/logrotate.conf and /etc/logrotate.d/rsyslog. Yet none had any
effect.
I have kept USB installations of Lubuntu 14.04.1 in parallel and saved
them after some days, so I could report about a number of experiments.
E.g., I started 2014-08-31, and I have a snapshot from 2014-09-22
where I had not changed /etc/logrotate.conf, neither
/etc/logrotate.d/rsyslog ("daily", "weekly"), and the three files
still have the entries from 2014-08-31, although three "weeks" had
passed.
#51879 (2006) and #1278193 (Feb 2014) are very similar, however:
* I observed growing kern.log and syslog to more than 100MB (to "out of
memory" finally) in some installations in summer 2013; in later installations
the same year and before 14.04, the problem vanished (I watched the sizes
manually/regularly – difference to #51879: after 2006, problem recurred,
vanished, recurred).
* With Lubuntu 14.04.1 recently, I changed "weekly" into "daily" in
/etc/logratate.conf and in /etc/logrotate.d/rsyslog, but three days later
auth.log, kern.log, and syslog still had no older copies and still contained
messages from the last three days. Then I did sudo logrotate-f
/etc/logrotate.conf, which works, but still after another three days those
three logs had not been rotated.
Actually I also have tried sudo logrotate -f /etc/logrotate.d/rsyslog,
and the result has been exactly as #1258202 (2013). As opposed to the
latter report and that for #1278193, I am unable to guess from which
changes the problems might have resulted.
ProblemType: Bug
DistroRelease: Ubuntu 14.04
Packa
[Touch-packages] [Bug 1301015] Re: Networking does not restart
man service suggests that "All scripts should support at least the start
and stop commands. "
indeed this is a change of behavior that is quit crucial, even if
"officially" service restart networking was never a "supported" way of
doing it, it seems to be an intuitive way of doing so; simply because
the script is there ! so intuitive that it is all over ubuntu
documentations, really, a message that is more helpful is needed.
otherwise, the mere existance of that script in the past should be
considered a bug, and continues to be so ... i guess
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ifupdown in Ubuntu.
https://bugs.launchpad.net/bugs/1301015
Title:
Networking does not restart
Status in “ifupdown” package in Ubuntu:
Opinion
Bug description:
In Ubuntu Server 14.04 it appears it is not possible to restart
networking. This is fresh install from ISO.
wirehive@ubuntu:~$ sudo /etc/init.d/networking restart
wirehive@ubuntu:~$ echo $?
1
wirehive@ubuntu:~$ sudo service networking restart
stop: Job failed while stopping
start: Job is already running: networking
wirehive@ubuntu:~$ sudo bash -x /etc/init.d/networking restart
+ PATH=/sbin:/bin
+ RUN_DIR=/run/network
+ IFSTATE=/run/network/ifstate
+ STATEDIR=/run/network/state
+ '[' -x /sbin/ifup ']'
+ '[' -x /sbin/ifdown ']'
+ . /lib/lsb/init-functions
+++ run-parts --lsbsysinit --list /lib/lsb/init-functions.d
++ for hook in '$(run-parts --lsbsysinit --list /lib/lsb/init-functions.d
2>/dev/null)'
++ '[' -r /lib/lsb/init-functions.d/20-left-info-blocks ']'
++ . /lib/lsb/init-functions.d/20-left-info-blocks
++ for hook in '$(run-parts --lsbsysinit --list /lib/lsb/init-functions.d
2>/dev/null)'
++ '[' -r /lib/lsb/init-functions.d/50-ubuntu-logging ']'
++ . /lib/lsb/init-functions.d/50-ubuntu-logging
+++ LOG_DAEMON_MSG=
++ FANCYTTY=
++ '[' -e /etc/lsb-base-logging.sh ']'
++ true
+ CONFIGURE_INTERFACES=yes
+ EXCLUDE_INTERFACES=
+ VERBOSE=no
+ '[' -f /etc/default/networking ']'
+ verbose=
+ '[' no = yes ']'
+ case "$1" in
+ init_is_upstart
+ '[' -x /sbin/initctl ']'
+ /bin/grep -q upstart
+ /sbin/initctl version
+ return 0
+ exit 1
wirehive@ubuntu:~$ sudo bash -x service networking restart
++ basename service
+ VERSION='service ver. 0.91-ubuntu1'
++ basename service
+ USAGE='Usage: service < option > | --status-all | [ service_name [ command
| --full-restart ] ]'
+ SERVICE=
+ ACTION=
+ SERVICEDIR=/etc/init.d
+ OPTIONS=
+ '[' 2 -eq 0 ']'
+ cd /
+ '[' 2 -gt 0 ']'
+ case "${1}" in
+ '[' -z '' -a 2 -eq 1 -a networking = --status-all ']'
+ '[' 2 -eq 2 -a restart = --full-restart ']'
+ '[' -z '' ']'
+ SERVICE=networking
+ shift
+ '[' 1 -gt 0 ']'
+ case "${1}" in
+ '[' -z networking -a 1 -eq 1 -a restart = --status-all ']'
+ '[' 1 -eq 2 -a '' = --full-restart ']'
+ '[' -z networking ']'
+ '[' -z '' ']'
+ ACTION=restart
+ shift
+ '[' 0 -gt 0 ']'
+ '[' -r /etc/init/networking.conf ']'
+ which initctl
+ grep -q upstart
+ initctl version
+ case "${ACTION}" in
+ stop networking
stop: Job failed while stopping
+ :
+ exec start networking
start: Job is already running: networking
wirehive@ubuntu:~$
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/1301015/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
