[Bug 1968588] [NEW] Cannot create or add VPN in connection editor

[Nicholas Hagen]

Public bug reported:

In 22.04 I am unable to create a new VPN in network manager and nm-
connection-editor. After filing in the entire form the save button
remains disabled!

watching the terminal provides this error:
Cannot save connection due to error: Invalid setting General: 
connection.interface-name: '': interface name must not be empty

Seems like the form validator is not looking at the right field!

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: network-manager-gnome 1.24.0-1ubuntu3
ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30
Uname: Linux 5.15.0-25-generic x86_64
ApportVersion: 2.20.11-0ubuntu80
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Mon Apr 11 10:49:34 2022
ExecutablePath: /usr/bin/nm-connection-editor
InstallationDate: Installed on 2022-04-09 (1 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Beta amd64 (20220329.1)
IpRoute:
 default via 10.0.2.2 dev enp0s3 proto dhcp metric 100 
 10.0.2.0/24 dev enp0s3 proto kernel scope link src 10.0.2.15 metric 100 
 169.254.0.0/16 dev enp0s3 scope link metric 1000
IwConfig:
 lono wireless extensions.
 
 enp0s3no wireless extensions.
ProcEnviron:
 SHELL=/bin/bash
 LANG=en_US.UTF-8
 TERM=xterm-256color
 XDG_RUNTIME_DIR=
 PATH=(custom, no user)
RfKill:
 
SourcePackage: network-manager-applet
UpgradeStatus: No upgrade log present (probably fresh install)
nmcli-con:
 NAMEUUID  TYPE  TIMESTAMP  
 TIMESTAMP-REAL   AUTOCONNECT  AUTOCONNECT-PRIORITY  READONLY  
DBUS-PATH   ACTIVE  DEVICE  STATE  
ACTIVE-PATH SLAVE  FILENAME 
  
 Wired connection 1  31e61843-ef5f-31e8-96a2-cf86d47e015c  ethernet  1649688323 
 Mon 11 Apr 2022 10:45:23 AM EDT  yes  -999  no
/org/freedesktop/NetworkManager/Settings/1  yes enp0s3  activated  
/org/freedesktop/NetworkManager/ActiveConnection/1  -- 
/run/NetworkManager/system-connections/Wired connection 1.nmconnection
nmcli-dev:
 DEVICE  TYPE  STATE  IP4-CONNECTIVITY  IP6-CONNECTIVITY  DBUS-PATH 
 CONNECTION  CON-UUID   
   CON-PATH   
 enp0s3  ethernet  connected  full  limited   
/org/freedesktop/NetworkManager/Devices/2  Wired connection 1  
31e61843-ef5f-31e8-96a2-cf86d47e015c  
/org/freedesktop/NetworkManager/ActiveConnection/1 
 lo  loopback  unmanaged  unknown   unknown   
/org/freedesktop/NetworkManager/Devices/1  --  --   
 --
nmcli-nm:
 RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  WIFI  
   WWAN-HW  WWAN
 running  1.36.4   connected  started  full  enabled enabled  
enabled  enabled  enabled

** Affects: network-manager-applet (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug jammy wayland-session

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1968588

Title:
  Cannot create or add VPN in connection editor

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager-applet/+bug/1968588/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1968588] Re: Cannot create or add VPN in connection editor

[Nicholas Hagen]

This also affects the UI connection manager! I merely provided the nm-
connection-editor error as you get no error in the UI, the Apply button
just remains disabled.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1968588

Title:
  Cannot create or add VPN in connection editor

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager-applet/+bug/1968588/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1879633] Re: Killer 500s (QCA6390) WLAN/BT [17cb:1101] unavailable

[Lucas Hagen]

@vicamo, thank you very much for the instructions. I'm on groovy
actually, so that's probably why it didn't work the last time, I didn't
try to install the focal packages. I install the focal packages and
everything seems to be working well.

I already noticed the freeze on start problem is no longer happening.

If you need any help testing, please feel free to contact me.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1879633

Title:
  Killer 500s (QCA6390) WLAN/BT [17cb:1101] unavailable

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1879633/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1879633] Re: Killer 500s (QCA6390) WLAN/BT [17cb:1101] unavailable

[Lucas Hagen]

I'm sorry for my inexperience. I have a XPS with the AX500 board, could
you provide some instructions for me to test it, @vicamo?

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1879633

Title:
  Killer 500s (QCA6390) WLAN/BT [17cb:1101] unavailable

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1879633/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1902350] [NEW] sa-exim not compatible with localscan

[Hasse Hagen Johansen]

Public bug reported:

After upgrading to Ubuntu 20.10 there are problems with sa-exim

While upgrading sa-exim would be uninstalled. It seems there is a
conflict somehow with a dependency of exim4-daemon-heavy which makes it
want to uninstall sa-exim

After upgrading I installed sa-exim and exim4-daemon-heavy was removed
and exim4-daemon-light was installed

Looking in the logs I now got an error that sa-exim and localscan wasn't
compatible:

2020-10-31 00:15:13.296 [31577] 1kYdc0-0008DJ-VD local_scan() has an 
incompatible majorversion number, you need to recompile your module for this 
versionof exim (The module was compiled for version 3.1 and this exim 
providesABI version 4.1) 2020-10-31 00:15:13.296 [31577] 1kYdc0-0008DJ-VD 
local_scan() has an incompatible majorversion number, you need to recompile 
your module for this versionof exim (The module was compiled for version 3.1 
and this exim providesABI version 4.1)
2020-10-31 00:15:13.297 [31577] 1kYdc0-0008DJ-VD local_scan() function crashed 
with signal 11 - message temporarily rejected (size 22707)

I hav now stopped using sa-exim as it is not the first time there is
this problem on a new release and it is not an especially popular method
to do spamscanning in the wider exim community

ProblemType: Bug
DistroRelease: Ubuntu 20.10
Package: sa-exim (not installed)
ProcVersionSignature: Ubuntu 5.8.0-26.27-generic 5.8.14
Uname: Linux 5.8.0-26-generic x86_64
ApportVersion: 2.20.11-0ubuntu50
Architecture: amd64
CasperMD5CheckResult: skip
Date: Sat Oct 31 10:44:01 2020
SourcePackage: sa-exim
UpgradeStatus: Upgraded to groovy on 2020-10-30 (0 days ago)
modified.conffile..etc.exim4.sa-exim.conf: [modified]
mtime.conffile..etc.exim4.sa-exim.conf: 2019-05-17T15:21:43

** Affects: sa-exim (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug apport-hook-error groovy

** Description changed:

  After upgrading to Ubuntu 20.10 there are problems with sa-exim
  
  While upgrading sa-exim would be uninstalled. It seems there is a
  conflict somehow with a dependency of exim4-daemon-heavy which makes it
  want to uninstall sa-exim
  
  After upgrading I installed sa-exim and exim4-daemon-heavy was removed
  and exim4-daemon-light was installed
  
  Looking in the logs I now got an error that sa-exim and localscan wasn't
  compatible:
  
  2020-10-31 00:15:13.296 [31577] 1kYdc0-0008DJ-VD local_scan() has an 
incompatible majorversion number, you need to recompile your module for this 
versionof exim (The module was compiled for version 3.1 and this exim 
providesABI version 4.1) 2020-10-31 00:15:13.296 [31577] 1kYdc0-0008DJ-VD 
local_scan() has an incompatible majorversion number, you need to recompile 
your module for this versionof exim (The module was compiled for version 3.1 
and this exim providesABI version 4.1)
  2020-10-31 00:15:13.297 [31577] 1kYdc0-0008DJ-VD local_scan() function 
crashed with signal 11 - message temporarily rejected (size 22707)
  
+ I hav now stopped using sa-exim as it is not the first time there is
+ this problem on a new release and it is not an especially popular method
+ to do spamscanning in the wider exim community
+ 
  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: sa-exim (not installed)
  ProcVersionSignature: Ubuntu 5.8.0-26.27-generic 5.8.14
  Uname: Linux 5.8.0-26-generic x86_64
  ApportVersion: 2.20.11-0ubuntu50
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Sat Oct 31 10:44:01 2020
  SourcePackage: sa-exim
  UpgradeStatus: Upgraded to groovy on 2020-10-30 (0 days ago)
  modified.conffile..etc.exim4.sa-exim.conf: [modified]
  mtime.conffile..etc.exim4.sa-exim.conf: 2019-05-17T15:21:43

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1902350

Title:
  sa-exim not compatible with localscan

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/sa-exim/+bug/1902350/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1848782] [NEW] package sddm 0.17.0-1ubuntu7 failed to install/upgrade: Unterprozess installiertes sddm-Skript des Paketes post-installation gab den Fehler-Ausgangsstatus 1 zurück

[Hagen von Eitzen]

Public bug reported:

$ lsb_release 
Display all 420 possibilities? (y or n)
hagen@samba2:~$ lsb_release -rd
Description:Ubuntu 18.04.3 LTS
Release:18.04

(Error occurred during do-release-upgrade from Xenial)


What I expected to happen:  Smooth release upgrade
What happened instead:  Problems with sddm were reported

ProblemType: Package
DistroRelease: Ubuntu 18.04
Package: sddm 0.17.0-1ubuntu7
ProcVersionSignature: Ubuntu 4.4.0-165.193-generic 4.4.189
Uname: Linux 4.4.0-165-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.7
Architecture: amd64
Date: Fri Oct 18 20:26:23 2019
ErrorMessage: Unterprozess installiertes sddm-Skript des Paketes 
post-installation gab den Fehler-Ausgangsstatus 1 zurück
InstallationDate: Installed on 2010-04-25 (3462 days ago)
InstallationMedia: Kubuntu 9.10 "Karmic Koala" - Release amd64 (20091027)
Python3Details: /usr/bin/python3.6, Python 3.6.8, python3-minimal, 3.6.7-1~18.04
PythonDetails: /usr/bin/python2.7, Python 2.7.15+, python-minimal, 2.7.15~rc1-1
RelatedPackageVersions:
 dpkg 1.19.0.5ubuntu2.3
 apt  1.6.12
SourcePackage: sddm
Title: package sddm 0.17.0-1ubuntu7 failed to install/upgrade: Unterprozess 
installiertes sddm-Skript des Paketes post-installation gab den 
Fehler-Ausgangsstatus 1 zurück
UpgradeStatus: Upgraded to bionic on 2019-10-18 (0 days ago)

** Affects: sddm (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package bionic

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1848782

Title:
  package sddm 0.17.0-1ubuntu7 failed to install/upgrade: Unterprozess
  installiertes sddm-Skript des Paketes post-installation gab den
  Fehler-Ausgangsstatus 1 zurück

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/sddm/+bug/1848782/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1829292] Re: exim4 doesn't run the local_scan function after upgrade to 19.04

[Hasse Hagen Johansen]

exim4-daemon-heavy version 4.92-4ubuntu1.1 seems to have fixed the
problem

Thank you!

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1829292

Title:
  exim4 doesn't run the local_scan function after upgrade to 19.04

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/exim4/+bug/1829292/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1829611] Re: tomcat cannot create the index directory for solr on startup

[Hasse Hagen Johansen]

Mohonri:

I have tested it. For it to work you have to tell systemd to reload its
units so to fix i for now doing this will solve it:

sudo systemctl stop tomcat9
sudo mv /etc/systemd/system/tomcat9.d /etc/systemd/system/tomcat9.service.d
sudo systemctl daemon-reload
sudo systemctl start tomcat9

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1829611

Title:
  tomcat cannot create the index directory for solr on startup

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lucene-solr/+bug/1829611/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1829611] Re: tomcat cannot create the index directory for solr on startup

[Hasse Hagen Johansen]

I found the error the systemd override snippet the solr-tomcat package
provides is placed in a wrongly named directory
/etc/systemd/system/tomcat9.d it should be in
/etc/systemd/system/tomcat9.service.d for systemd to pick it up

so

/etc/systemd/system/tomcat9.d/solr-permissions.conf should be

/etc/systemd/system/tomcat9.service.d/solr-permissions.conf

I have provided a patch to the source package(hope it is the right way
or please tell me)

** Patch added: "patch tomcat-solr.install"
   
https://bugs.launchpad.net/ubuntu/+source/lucene-solr/+bug/1829611/+attachment/5264684/+files/solr-tomcat.patch

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1829611

Title:
  tomcat cannot create the index directory for solr on startup

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lucene-solr/+bug/1829611/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1829611] Re: tomcat cannot create the index directory for solr on startup

[Hasse Hagen Johansen]

I have found out that it has something to do with ProtectSystem=strict
in the tomcat9 systemd unit. I will debug some more. setting
ProtectSystem=full worked one time(and then something else went wrong
and tomcat never got properly started)

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1829611

Title:
  tomcat cannot create the index directory for solr on startup

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lucene-solr/+bug/1829611/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1829611] [NEW] tomcat cannot create the index directory for solr on startup

[Hasse Hagen Johansen]

Public bug reported:

After upgrading to 19.04 tomcat cannot create solr's index directory
/var/lib/solr/data/index as seen by the catalina log like this:

18-May-2019 14:06:54.627 WARNING [main] org.apache.solr.core.SolrCore.initIndex 
[] Solr index directory '/var/lib/solr/data/index' doesn't exist. Creating new 
index...
18-May-2019 14:06:54.679 SEVERE [main] org.apache.solr.common.SolrException.log 
java.lang.RuntimeException: java.io.IOException: Cannot create directory: 
/var/lib/solr/data/index
at org.apache.solr.core.SolrCore.initIndex(SolrCore.java:403)
at org.apache.solr.core.SolrCore.(SolrCore.java:552)
at org.apache.solr.core.CoreContainer.create(CoreContainer.java:480)
at org.apache.solr.core.CoreContainer.load(CoreContainer.java:332)
at org.apache.solr.core.CoreContainer.load(CoreContainer.java:216)
at 
org.apache.solr.core.CoreContainer$Initializer.initialize(CoreContainer.java:161)
at 
org.apache.solr.servlet.SolrDispatchFilter.init(SolrDispatchFilter.java:96)
at 
org.apache.catalina.core.ApplicationFilterConfig.initFilter(ApplicationFilterConfig.java:270)
at 
org.apache.catalina.core.ApplicationFilterConfig.getFilter(ApplicationFilterConfig.java:251)
at 
org.apache.catalina.core.ApplicationFilterConfig.(ApplicationFilterConfig.java:102)
at 
org.apache.catalina.core.StandardContext.filterStart(StandardContext.java:4516)
at 
org.apache.catalina.core.StandardContext.startInternal(StandardContext.java:5162)
at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:183)
at 
org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:713)
at 
org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:690)
at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:695)
at 
org.apache.catalina.startup.HostConfig.deployDescriptor(HostConfig.java:631)
at 
org.apache.catalina.startup.HostConfig$DeployDescriptor.run(HostConfig.java:1832)
at 
java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:515)
at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264)
at 
org.apache.tomcat.util.threads.InlineExecutorService.execute(InlineExecutorService.java:75)
at 
java.base/java.util.concurrent.AbstractExecutorService.submit(AbstractExecutorService.java:118)
at 
org.apache.catalina.startup.HostConfig.deployDescriptors(HostConfig.java:526)
at 
org.apache.catalina.startup.HostConfig.deployApps(HostConfig.java:425)
at org.apache.catalina.startup.HostConfig.start(HostConfig.java:1577)
at 
org.apache.catalina.startup.HostConfig.lifecycleEvent(HostConfig.java:309)
at 
org.apache.catalina.util.LifecycleBase.fireLifecycleEvent(LifecycleBase.java:123)
at 
org.apache.catalina.util.LifecycleBase.setStateInternal(LifecycleBase.java:424)
at 
org.apache.catalina.util.LifecycleBase.setState(LifecycleBase.java:367)
at 
org.apache.catalina.core.ContainerBase.startInternal(ContainerBase.java:929)
at 
org.apache.catalina.core.StandardHost.startInternal(StandardHost.java:831)
at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:183)
at 
org.apache.catalina.core.ContainerBase$StartChild.call(ContainerBase.java:1377)
at 
org.apache.catalina.core.ContainerBase$StartChild.call(ContainerBase.java:1367)
at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264)
at 
org.apache.tomcat.util.threads.InlineExecutorService.execute(InlineExecutorService.java:75)
at 
java.base/java.util.concurrent.AbstractExecutorService.submit(AbstractExecutorService.java:140)
at 
org.apache.catalina.core.ContainerBase.startInternal(ContainerBase.java:902)
at 
org.apache.catalina.core.StandardEngine.startInternal(StandardEngine.java:262)
at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:183)
at 
org.apache.catalina.core.StandardService.startInternal(StandardService.java:423)
at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:183)
at 
org.apache.catalina.core.StandardServer.startInternal(StandardServer.java:928)
at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:183)
at org.apache.catalina.startup.Catalina.start(Catalina.java:638)
at 
java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at 
java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at 
java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.base/java.lang.reflect.Method.invoke(Method.java:566)
at org.apache.catalina.startup.Bootstrap.start(Bootstrap.java:350)
at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:496)

[Bug 1829292] [NEW] exim4 doesn't run the local_scan function after upgrade to 19.04

[Hasse Hagen Johansen]

Public bug reported:

It seems like after upgrade to 19.04 that exim is not running the
local_scan function (in my case the sa-exim /usr/lib/exim4/local_scan
/sa-exim.so)

So I now don't have the spam-scan I am used to(I have enabled scanning
by the way of an RCPT_ACL for now)

Hope this can fixed despite sa-exim being very old

Description:Ubuntu 19.04
Release:19.04

exim4-daemon-heavy:
  Installed: 4.92-4ubuntu1
  Candidate: 4.92-4ubuntu1
  Version table:
 *** 4.92-4ubuntu1 500
500 http://dk.archive.ubuntu.com/ubuntu disco/main amd64 Packages
100 /var/lib/dpkg/status

I expect to see in /var/log/exim4/mainlog lines like this as I saw before:
2019-05-12 20:01:54 1hPsnJ-000285-Jj SA: Debug: check succeeded, running spamc
2019-05-12 20:02:01 1hPsnJ-000285-Jj SA: Action: scanned but message isn't 
spam: score=2.5 required=5.0 (scanned in 7/7 secs | Message-Id: 
duxufv23y44bfkuepz1f4naeoavbh7xtz_es_rsbndc.erur4y-b0k2tn61ykllctsv6z3yzr3hqkm9umv94...@devotestream.icu).
 From  (host=NULL [185.254.236.42]) for 

I don't see that after upgrading to 19.04 this saturday

** Affects: exim4 (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: 19.04

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1829292

Title:
  exim4 doesn't run the local_scan function after upgrade to 19.04

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/exim4/+bug/1829292/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1727288] Re: SHA256SUMS mismatch with ubuntu-17.10-server-amd64.iso

[Hagen Kuehn]

The download from http://releases.ubuntu.com/17.10/ubuntu-17.10-server-
amd64.iso works (i.e the sha256 checksum is correct). However I continue
to get a different checksum every time I download it from
http://uk.releases.ubuntu.com/17.10/ubuntu-17.10-server-amd64.iso.

@ Brian Murray - As it's working for you and no one else appears to have
this problem, I am closing this bug now.

** Changed in: ubuntu
   Status: New => Invalid

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1727288

Title:
  SHA256SUMS mismatch with ubuntu-17.10-server-amd64.iso

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+bug/1727288/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1727288] Re: SHA256SUMS mismatch with ubuntu-17.10-server-amd64.iso

[Hagen Kuehn]

@Brian Murray - Thanks for checking.

Given that no one else seems to have this problem, I can only guess that
my ISP's proxy sends me an old cached version or someone indeed does the
unbelievable.

I will investigate and report back.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1727288

Title:
  SHA256SUMS mismatch with ubuntu-17.10-server-amd64.iso

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+bug/1727288/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1727288] Re: SHA256SUMS mismatch with ubuntu-17.10-server-amd64.iso

[Hagen Kuehn]

@bot As it currently stand I don't suspect a bug in a particular
package. All it seams to me that some or all web servers that provide
the Ubuntu 17.10 "ubuntu-17.10-server-amd64.iso", are not up to date and
therefore the sha256sums results do not match the ones provided with
http://uk.releases.ubuntu.com//17.10/SHA256SUMS

Steps to reproduce

1. Download http://uk.releases.ubuntu.com/17.10/ubuntu-17.10-server-amd64.iso
2. Get SHA256 sum
$ sha256sum ubuntu-17.10-server-amd64.iso
3. Compare with checksums provided with 
http://uk.releases.ubuntu.com/17.10/SHA256SUMS

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1727288

Title:
  SHA256SUMS mismatch with ubuntu-17.10-server-amd64.iso

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+bug/1727288/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1727288] Re: SHA256SUMS mismatch with ubuntu-17.10-server-amd64.iso

[Hagen Kuehn]

Could it be that the mirror is not up to date? It shows that the ISO was
updated on 17/10/2017 whereas I do find it likely that it should be at
least 19/10/2017?

ubuntu-17.10-server-amd64.iso  2017-10-17 20:46  745M  Server
install image for 64-bit PC (AMD64) computers (standard download)

Please see attached screenshot for details.

** Attachment added: "Screenshot of uk.releases.ubuntu.com that show date of 
last changes"
   
https://bugs.launchpad.net/ubuntu/+bug/1727288/+attachment/4994141/+files/uk.releases.ubuntu.com.png

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1727288

Title:
  SHA256SUMS mismatch with ubuntu-17.10-server-amd64.iso

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+bug/1727288/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1727288] [NEW] SHA256SUMS mismatch with ubuntu-17.10-server-amd64.iso

[Hagen Kuehn]

Public bug reported:

Current Time is 12:10 BST

When I download the "ubuntu-17.10-server-amd64.iso" from

http://uk.releases.ubuntu.com//17.10/ubuntu-17.10-server-amd64.iso

the sha256sum published at
http://uk.releases.ubuntu.com//17.10/SHA256SUMS does not match the
sha256sum of the ISO downloaded.


--
$ sha256sum ubuntu-17.10-server-amd64.iso 
04021044a7726a1de0fed6ac539864a1f311266bd49156e11a7bbee13e53ee0d  
ubuntu-17.10-server-amd64.iso
--

--
http://uk.releases.ubuntu.com//17.10/SHA256SUMS
--
aaf4ba1809e08f6108f1e410174ebcbd49af5cc4f6493ab3d98d0683289bbc6e 
*ubuntu-17.10-desktop-amd64.iso
af913c00296eb0cfece99b8a02ae6db035ae173ed240241e780c8d7db96914b1 
*ubuntu-17.10-server-amd64.img
af913c00296eb0cfece99b8a02ae6db035ae173ed240241e780c8d7db96914b1 
*ubuntu-17.10-server-amd64.iso
d8fc9cea7eadeec39253fe62c215111314c582ef9ec10b6a70959265bac73cc4 
*ubuntu-17.10-server-i386.img
d8fc9cea7eadeec39253fe62c215111314c582ef9ec10b6a70959265bac73cc4 
*ubuntu-17.10-server-i386.iso
--

The odd thing is, no one else seems to report this problem, although I
believe quite a few people would have tried Ubuntu 17.10 Server by now.
I suppose it's unlikely that someone is feeding me with a hacked version
of this ISO.

Do you have the same problem somewhere else too?

** Affects: ubuntu
 Importance: Undecided
 Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1727288

Title:
  SHA256SUMS mismatch with ubuntu-17.10-server-amd64.iso

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+bug/1727288/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1610944] Re: GNOME Online Accounts breaks if you log out (until you reboot)

[Hagen Kuehn]

I believe I encounter this issue with Ubuntu 17.10, which uses "gnome-
session 3.26.1-0ubuntu5".

The story, I installed Ubuntu 17.04 back in September 2017 and been
using Online Accounts for three Gmail accounts. The email client
Evolution was working fine. I then upgraded to Ubuntu 17.10 a couple of
days ago. After upgrade, Evolution continued to work by using the
configured accounts within Online Accounts. So far so good.

I then realised that Thunderbird was installed during this OS upgrade
too. So I uninstalled Thunderbird with "sudo apt purge thunderbird".
After that I had this problem that Online Accounts stopped working. The
symptom was that all online accounts showed that the login had expired,
despite me having re-logged in a couple of times. I then found this bug
report and I followed the instructions provided with
https://bugs.launchpad.net/ubuntu/+source/gnome-online-
accounts/+bug/1610944/comments/3, which allowed me to get it working
again.

In the light of this, I believe this problem is still present with
"gnome-session 3.26.1-0ubuntu5".

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1610944

Title:
  GNOME Online Accounts breaks if you log out (until you reboot)

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-online-accounts/+bug/1610944/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1697556] Re: Computer freezes after login - 4.10.0-22-generic

[Hagen Kuehn]

This is a re-write of my previous response, as I should have reviewed it
before submitting. I have simply been too excited! ;-)

@Kai-Heng Feng and @Anmar Queja

I have upgraded to Ubuntu 17.10 and used the suggested nouveau.modeset=0
kernel boot option.

It works perfectly. I can indeed see many improvements. Most and
foremost Wayland is working as far as I can see!

The only hiccup I had was with the laptop suspending right after a
successful login, when the laptop lid was closed while being connected
to the Dell Thunderbolt dock – TB16. In contrast to previous Ubuntu
version there is no way of configuring the laptop lid closed behaviour
by using the GUI (via Power configuration).

Below setting made the trick.
vim ~/etc/systemd/logind.conf
---
HandleLidSwitchDocked=ignore
---

In the light of this I believe this bug is addressed by upgrading to
17.10 and therefore this bug can be closed.

@Marco Scavazzon I believe you should create a new bug and reference
this bug in order to get kernel 4.13.0-16 ported to Ubuntu 16.04 LTS.

@All Ubuntu kernel developer
A great thank you to you all for your efforts of making Ubuntu 17.04 so nicely 
work with Wayland and with Dell XPS 15 (9560)!!

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1697556

Title:
  Computer freezes after login - 4.10.0-22-generic

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1697556/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1697556] Re: Computer freezes after login - 4.10.0-22-generic

[Hagen Kuehn]

@Kai-Heng Feng and @Anmar Queja

I have upgraded to Ubuntu 17.10 and used the suggested nouveau.modeset=0 kernel
boot option.

It works perfectly. I can indeed see many improvement. Most and foremost
Wayland is working as far as I can see!

The only hiccup I had was with the laptop suspending right after the
successful login, when the laptop lid was closed while being connected
to the Dell Thunderbolt dock – TB16. In contrast to previous Ubuntu
version there is no way of configuring the laptop lid behaviour by using
the GUI (via Power configuration).

Below setting made the trick.
vim ~/etc/systemd/logind.conf
---
HandleLidSwitchDocked=ignore
---

In the light of this I believe this addressed by upgrading to 17.10 and
thus can be closed.

@Marco Scavazzon I believe you should create a new bug and reference
this bug in order to get kernel 4.13.0-16 ported to Ubuntu 16.04 LTS.

@All Ubuntu kernel develops
A great thank you to you all of you for making Ubuntu 17.04 so nicely work with 
Wayland and with Dell XPS 15 (9560)!!

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1697556

Title:
  Computer freezes after login - 4.10.0-22-generic

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1697556/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1697556] Re: Computer freezes after login - 4.10.0-22-generic

[Hagen Kuehn]

I have tested with provided kernel at 
http://people.canonical.com/~khfeng/lp1697556/3/
The test setup was the same as previously.

Short answer: It does not work.

Long answer: I can see the icon circling for a while. While this happens
I cannot toggle between the boot text output and the circling icon, by
using the ESC button. After a while (guess a minute or so), the screen
turns black and displays:

BusyBox v1.22.1 (Ubuntu 1:1.22.0-19ubuntu2) built-in shell (ash)
Enter 'help' for a list of built-in commands.

(initramfs)_

Also note that I was not able to find any logs concerning this attempted
boot. The kern.log file didn't have a single line concerning this boot
attempt.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1697556

Title:
  Computer freezes after login - 4.10.0-22-generic

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1697556/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1697556] Re: Computer freezes after login - 4.10.0-22-generic

[Hagen Kuehn]

I have tested with kernel 4.10.0-lp1697556
http://people.canonical.com/~khfeng/lp1697556/2/ with the default kernel
parameters and with the same hardware setup as previously.

Short answer: It works.

Long answer: The login screen is displayed on built in monitor, while
the laptop is closed. The login works. I am actually writing this
response while using this kernel.

Please see attached 4.10.0-lp1697556.kern.log file for details. The
nouveau section of the log is pasted below.

Oct  4 17:19:09 quatlap002 kernel: [3.165635] nouveau: detected PR support, 
will not use DSM
Oct  4 17:19:09 quatlap002 kernel: [3.165648] nouveau :01:00.0: 
enabling device (0006 -> 0007)
Oct  4 17:19:09 quatlap002 kernel: [3.165704] nouveau :01:00.0: unknown 
chipset (137000a1)
Oct  4 17:19:09 quatlap002 kernel: [3.165723] nouveau: probe of 
:01:00.0 failed with error -12

** Attachment added: "4.10.0-lp1697556.kern.log"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1697556/+attachment/4962155/+files/4.10.0-lp1697556.kern.log

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1697556

Title:
  Computer freezes after login - 4.10.0-22-generic

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1697556/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1697556] Re: Computer freezes after login - 4.10.0-22-generic

[Hagen Kuehn]

I have tested with kernel 4.11.0-rc1-lp1697556 with the default kernel
with the same hardware setup as previously.

Short answer: It works.

Long answer: The login screen is displayed on built in monitor, while
the laptop is closed. The login works. Network issues but they are not
relevant to this bug.

Please see attached the "4.11.0-rc1-lp1697556.kern.log" kernel log for
details. The relevant nouveau section is copied below.

Oct  3 14:48:49 computername kernel: [3.175682] nouveau: detected PR 
support, will not use DSM
Oct  3 14:48:49 computername kernel: [3.175693] nouveau :01:00.0: 
enabling device (0006 -> 0007)
Oct  3 14:48:49 computername kernel: [3.175746] nouveau :01:00.0: 
unknown chipset (137000a1)
Oct  3 14:48:49 computername kernel: [3.175764] nouveau: probe of 
:01:00.0 failed with error -12

** Attachment added: "4.11.0-rc1-lp1697556.kern.log"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1697556/+attachment/4961442/+files/4.11.0-rc1-lp1697556.kern.log

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1697556

Title:
  Computer freezes after login - 4.10.0-22-generic

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1697556/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1697556] Re: Computer freezes after login - 4.10.0-22-generic

[Hagen Kuehn]

Your question:
"so what's the result on v4.12-rc1, without "nomodeset"?"

Short answer: It does not freeze.

Detailed answer:
With v4.12-rc1, by using the default kernel arguments (i.e. without 
"nomodeset"), it does not freeze. It shows the login screen on the closed 
laptop, which you pointed out is related to i915.

The kern.log shows following nouveau related output.

Sep 27 09:37:15 computername kernel: [3.239682] nouveau: detected PR 
support, will not use DSM
Sep 27 09:37:15 computername kernel: [3.239698] nouveau :01:00.0: 
enabling device (0006 -> 0007)
Sep 27 09:37:15 computername kernel: [3.239831] nouveau :01:00.0: 
NVIDIA GP107 (137000a1)
Sep 27 09:37:15 computername kernel: [3.245638] i915 :00:02.0: vgaarb: 
changed VGA decodes: olddecodes=io+mem,decodes=io+mem:owns=io+mem
Sep 27 09:37:15 computername kernel: [3.248707] [drm] Finished loading DMC 
firmware i915/kbl_dmc_ver1_01.bin (v1.1)
Sep 27 09:37:15 computername kernel: [3.269575] nouveau :01:00.0: bios: 
version 86.07.3e.00.1c
Sep 27 09:37:15 computername kernel: [3.269993] nouveau :01:00.0: 
Direct firmware load for nvidia/gp107/gr/sw_nonctx.bin failed with error -2
Sep 27 09:37:15 computername kernel: [3.269995] nouveau :01:00.0: gr: 
failed to load gr/sw_nonctx
Sep 27 09:37:15 computername kernel: [3.26] nouveau :01:00.0: gr 
ctor failed, -2
Sep 27 09:37:15 computername kernel: [3.270003] nouveau: probe of 
:01:00.0 failed with error -2

Please see attached "kernel.log.4.12-rc1WithDefaultKernelArguments.log"
for details.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1697556

Title:
  Computer freezes after login - 4.10.0-22-generic

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1697556/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1697556] Re: Computer freezes after login - 4.10.0-22-generic

[Hagen Kuehn]

** Attachment added: "Kernel 4.12-rc1 log using default kernel argument"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1697556/+attachment/4957550/+files/kernel.log.4.12-rc1WithDefaultKernelArguments.log

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1697556

Title:
  Computer freezes after login - 4.10.0-22-generic

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1697556/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1697556] Re: Computer freezes after login - 4.10.0-22-generic

[Hagen Kuehn]

** Attachment added: "Kernel 4.11.12 log using nomodeset argument"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1697556/+attachment/4957291/+files/kernel.log.4.11.12.nomodeset.log

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1697556

Title:
  Computer freezes after login - 4.10.0-22-generic

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1697556/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1697556] Re: Computer freezes after login - 4.10.0-22-generic

[Hagen Kuehn]

** Attachment added: "Kernel 4.11.12 log when using blacklist nouveau arguments"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1697556/+attachment/4957292/+files/kernel.log.4.11.12.blacklist.nouveau.log

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1697556

Title:
  Computer freezes after login - 4.10.0-22-generic

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1697556/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1697556] Re: Computer freezes after login - 4.10.0-22-generic

[Hagen Kuehn]

@Kai-Heng

In answer to your question "Can you confirm v4.11 freezes but v4.12-rc1
doesn't?", I can confirm that 4.11.12 freezes. Kernel log shows "NMI
watchdog: BUG: soft lockup - CPU#3 stuck for 23s! [kworker/3:1:70]".

Below are the test details along with the corresponding kernel log
output.

Kernel version used during this test:
http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.11.12/
linux-headers-4.11.12-041112_4.11.12-041112.201707210350_all.deb
linux-headers-4.11.12-041112-generic_4.11.12-041112.201707210350_amd64.deb
linux-image-4.11.12-041112-generic_4.11.12-041112.201707210350_amd64.deb

Detailed answer:
v4.11.12 -> default kernel settings -> Progress icon rotates endlessly. When 
toggling to the ttl output I see "NMI watchdog: BUG: soft lockup - CPU#3 stuck 
for 23s! [kworker/3:1:70]" and many more.
-> See attached file kernel.log.4.11.12.WithDefaultKernelArguments.log

v4.11.12 -> NOMODESET -> Progress icon was displayed and rotated for a while 
but then the entire computer turned off. -> Not frozen but dead.
-> See attached file kernel.log.4.11.12.nomodeset.log

v4.11.12 -> "blacklist=nouveau modprobe.blacklist=nouveau" -> I could login 
without problems and the desktop appears to be displayed and working as I would 
expect.
-> See attached file kernel.log.4.11.12.blacklist.nouveau.log

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1697556

Title:
  Computer freezes after login - 4.10.0-22-generic

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1697556/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1697556] Re: Computer freezes after login - 4.10.0-22-generic

[Hagen Kuehn]

** Attachment added: "Kernel 4.11.12 log using default kernel arguments"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1697556/+attachment/4957290/+files/kernel.log.4.11.12.WithDefaultKernelArguments.log

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1697556

Title:
  Computer freezes after login - 4.10.0-22-generic

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1697556/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1697556] Re: Computer freezes after login - 4.10.0-22-generic

[Hagen Kuehn]

@Kai-Heng

Concerning your question:
v4.12-rc1 with NOMODESET -> Successfully logged in.
v4.12-rc2 with NOMODESET -> Successfully logged in.
v4.12-rc5 without NOMODESET-> Successfully logged in.
Can I say that -rc2 has freeze but -rc5 doesn't freeze?

I would say that neither of those two kernels freeze. However they
behave differently depending whether NOMODESET is configured. For
example, -rc5 shows a wired behaviour when NOMODESET is used. This is
explained further below.

In the light of your question I have run the tests again, but this time
without modifying the kernel parameters so they are the ones that come
with it by default. (i.e. only "quiet splash").

Short answer (vanilla - no additional kernel parameters set):
v4.12-rc1 -> Successfully logged in but login screen on built in monitor.
v4.12-rc2 -> Successfully logged in but login screen on built in monitor.
v4.12-rc5 -> Successfully logged in as I would expect it to work.
4.10.0-35-generic -> No login possible due to login screen never being shown.


Long answer:
v4.12-rc1 -> Same as v4.12-rc2
v4.12-rc2 -> Booting the laptop with lid closed. It does not show the login 
screen on the external monitor but found the login screen on the built in 
monitor after opening the lid. I then successfully logged in by using the 
external keyboard. After the login the built in monitor got disabled (no user 
intervention from my side) while the laptop lid was still open. The external 
monitor is active and displays the desktop with correct resolution. The 
external keyboard continued to be working after login.
v4.12-rc5 -> Successfully logged in. It correctly used the external monitor 
only and the keyboard continued to work after login.
4.10.0-35-generic -> The login screen is never displayed. I can see the 
progress icon circling endlessly. Note, the icon itself continuous to move all 
the time but nothing else beyond that happens. Furthermore, both screens are 
active and show the progress icon.


Furthermore, I have then tested v4.12-rc5 with NOMODESET again, with flowing 
outcome.

v4.12-rc5 with NOMODESET -> Booting laptop with lid closed. The login
screen gets displayed on the external screen correctly. I then logged in
by using the external keyboard, which was then followed by a black
screen (i.e. monitor reported no signal) on the external monitor (note,
the laptop was still closed). The laptop does not appear to react to any
keystrokes. As of my testing, this black screen would remain there until
the laptop lid was opened once. At least in two out of three tests this
was the case, whereas with one test I was not able to get to the desktop
at all. I have tested it three times by waiting differently long periods
and it appears that opening the laptop lid causes the external screen to
eventually show the desktop (after 20 to 30 seconds) in two of the three
test cases. Note, the built in laptop screen remains black all the way.
Furthermore, after the login, the external keyboard stopped working.
This might explain that the laptop did not react to my keystrokes since
the laptop lid was closed during this period and thus the built in
keyboard was not available to me. Another observation is, which is
probably i915 related too, that the external keyboard only worked after
the USB dongle was removed and re-connected to the docking station.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1697556

Title:
  Computer freezes after login - 4.10.0-22-generic

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1697556/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1697556] Re: Computer freezes after login - 4.10.0-22-generic

[Hagen Kuehn]

@Kai-Heng

Here are the test results when starting the kernel with "blacklist=nouveau 
modprobe.blacklist=nouveau".
The Dell XPS 9560 is connected to Dell Thunderbolt Dock TB16 with the external 
monitor and the external keyboard being connected to the docking station.

Short answer:
v4.12-rc1 -> Successfully logged in.
v4.12-rc2 -> Successfully logged in.
v4.12-rc5 -> Successfully logged in. (This is the only one without negative 
side effects as explained with the long answer below.)
4.10.0-35-generic -> Successfully logged in.

Long answer:
The side effects observed are likely not all related to this particular bug but 
I mention them here for completeness.

v4.12-rc1 -> Login scree is displayed on the laptop screen but not on
the external screen. Note, up to this point of booting, the laptop was
closed. After opening the laptop I can see the login screen. Regardless
whether the laptop is closed I can use the external keyboard to
successfully login. However from this point onwards (after login) the
external keyboard stops working (while connected to the docking
station). I can then only use the laptop's built in keyboard.
Furthermore, the screen resolution on both screens is very low (i.e.
1600x900) whereas it should be 3840x2160 as configured on my laptop.


v4.12-rc2 -> Same behaviour as with v4.12-rc1 and 4.10.0-35-generic

v4.12-rc5 -> As far as I can tell everything works fine with my setup.
The login screen is displayed on the external monitor and has not
activated the built in monitor while the laptop is closed. It is using
the correct screen resolution of 3840x2160 and the external keyboard
continuous to work after login.

4.10.0-35-generic -> Same behaviour as with v4.12-rc1, v4.12-rc2

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1697556

Title:
  Computer freezes after login - 4.10.0-22-generic

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1697556/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1697556] Re: Computer freezes after login - 4.10.0-22-generic

[Hagen Kuehn]

@Kai-Heng Feng (kaihengfeng)

Based on your suggestion I have tested with the below mainline kernels as well 
as the current 17.04 kernel.
http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.12-rc1/
http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.12-rc2/
http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.12-rc5/

Short answer:
v4.12-rc1 with NOMODESET -> Successfully logged in.
v4.12-rc2 with NOMODESET -> Successfully logged in.
v4.12-rc5 without NOMODESET-> Successfully logged in.
4.10.0-35-generic with NOMODESET -> Successfully logged in.

Though, there have been slight different behaviours observed, which I
believe are noteworthy.

Long answer:
I am using the Dell XPS 15 9560 with a Dell Thunderbolt dock – tb16. The laptop 
itself is closed and thus only using the external monitor. To turn the laptop 
on, I use the power button on the docking station.

Scenario 1: v4.12-rc1 without NOMODESET -> The external screen
eventually shows the login screen background and I can move the mouse.
Due to the way the mouse was moving out the display area I then got the
impression that it might render the login dialog on the laptop screen
instead. This was confirmed by opening my laptop.

Scenario 2: v4.12-rc1 with NOMODESET -> The external screen correctly
shows the login screen and I can successfully login.

Note, kernel v4.12-rc1 and v4.12-rc2 behave identical.

Scenario 3: v4.12-rc5 without NOMODESET -> The external screen correctly
shows the login screen and I can successfully login.

Scenario 4: v4.12-rc5 with NOMODESET -> Eventually shows a black screen.
No response to key strokes.

Scenario 5: 4.10.0-35-generic without NOMODESET -> The Ubuntu splash
screen is displayed (i.e. with the circling progress icon). It never
shows the login screen and appears to be stuck in an endless loop. I
have observed this for about 10 minute and then turned the computer off.

Scenario 6: 4.10.0-35-generic with NOMODESET -> The external screen
correctly shows the login screen and I can successfully login. Note,
this is the currently latest kernel that ships with Ubuntu 17.04. This
is how I currently use Ubuntu 17.04 on Dell XPS 9560.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1697556

Title:
  Computer freezes after login - 4.10.0-22-generic

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1697556/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1697556] Re: Computer freezes after login - 4.10.0-22-generic

[Hagen Kuehn]

@dani_bs(sdaniele78)

I trust you commented and changed the state of the bug with good intent.
Please accept my apology for being so direct... it was a complete fail.

Both links referenced do not provide any solution. One link mentions to
alter the "acpi_osi kernel parameters" without details what should be
changed. The second link generically talks about installing the latest
OS and Nvidia updates, which is manly only a suggestion by someone to
assist someone to troubleshoot a similar problem. It's no way a
solution, just an attempt by someone to assist someone. Therefore both
of your references do not yield any relevance to this bug.

Furthermore, when referencing other sources in the internet, you should
cite the information provided there in addition to the link. This is
there to ensure that the key information is never lost, since those
third party websites may make articles unavailable.

I understand that you "involuntarily" changed the bug status to "Fix
Released". However, wouldn't it not been better if you would have
voluntarily changed it back to "Confirmed" right away?

I have changed the bug back to "Confirmed" now!

BTW, the current workaround is to use the "nomodeset" kernel boot
argument. Adding the nomodeset parameter instructs the kernel to not
load video drivers and use BIOS modes instead until X is loaded.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1697556

Title:
  Computer freezes after login - 4.10.0-22-generic

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1697556/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1697556] Re: Computer freezes after login - 4.10.0-22-generic

[Hagen Kuehn]

** Changed in: linux (Ubuntu)
   Status: Fix Released => Confirmed

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1697556

Title:
  Computer freezes after login - 4.10.0-22-generic

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1697556/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1697556] Re: Computer freezes after login - 4.10.0-22-generic

[Hagen Kuehn]

I have reviewed the kernel source code that was committed between the
Ubuntu-4.10.0-21.23 and Ubuntu-4.10.0-22.24 and I believe commit
b93843fcde501b9264ac5dbe2c980eb0b479 introduced bug #1697556.

Commit b93843fcde501b9264ac5dbe2c980eb0b479 corresponds to
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1687045

In the light of this I believe that Thierry Reding 
and Stefan Bader  would be the best people
to look into this.

BTW, as it was not mentioned so far, Dell XPS 15 (9560) uses Intel HD
630 NVidia GeForce GTX 1050 with 4GB GDDR5.

** Attachment added: "Suspected commit that causes bug #1697556"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1697556/+attachment/4946672/+files/ubuntu-zesty-kernel-commit-b93843fcde501b9264ac5dbe2c980eb0b479.txt

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1697556

Title:
  Computer freezes after login - 4.10.0-22-generic

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1697556/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1697556] Re: Computer freezes after login - 4.10.0-22-generic

[Hagen Kuehn]

In line with comment
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1697556/comments/11,
the workarounds suggested with
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1697556/comments/9
do not work with kernel 4.10.0-28 either. The computer freezes just
before the login screen appears. Note, no key strokes are recognised and
it's not possible to switch to another TTY (same as with originally
reported problem).

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1697556

Title:
  Computer freezes after login - 4.10.0-22-generic

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1697556/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1697556] Re: Computer freezes after login - 4.10.0-22-generic

[Hagen Kuehn]

I have tested the suggested workarounds that were given with comment
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1697556/comments/9
in conjunction with kernel 4.10.0-24. Those two workarounds basically
suggest not to use the nouveau driver but instead the Nvidia drivers.

Those workarounds do not work. When the Nvidia driver is configured and
the machine booted by using kernel 4.10.0-24, the computer freezer just
before the login window.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1697556

Title:
  Computer freezes after login - 4.10.0-22-generic

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1697556/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1697556] Re: Computer freezes after login - 4.10.0-22-generic

[Hagen Kuehn]

In answer to your question
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1697556/comments/6

I have tested with Kernel 4.12.0, and DID NOT ENCOUNTER this problem.

linux-headers-4.12.0-041200rc5_4.12.0-041200rc5.201706112031_all.deb
linux-headers-4.12.0-041200rc5-generic_4.12.0-041200rc5.201706112031_amd64.deb
linux-image-4.12.0-041200rc5-generic_4.12.0-041200rc5.201706112031_amd64.deb

Note, while installing Kernel 4.12.0, I got below stdout.

$ sudo dpkg -i linux-*
Selecting previously unselected package linux-headers-4.12.0-041200rc5.
(Reading database ... 182643 files and directories currently installed.)
Preparing to unpack 
linux-headers-4.12.0-041200rc5_4.12.0-041200rc5.201706112031_all.deb ...
Unpacking linux-headers-4.12.0-041200rc5 (4.12.0-041200rc5.201706112031) ...
Selecting previously unselected package linux-headers-4.12.0-041200rc5-generic.
Preparing to unpack 
linux-headers-4.12.0-041200rc5-generic_4.12.0-041200rc5.201706112031_amd64.deb 
...
Unpacking linux-headers-4.12.0-041200rc5-generic 
(4.12.0-041200rc5.201706112031) ...
Selecting previously unselected package linux-image-4.12.0-041200rc5-generic.
Preparing to unpack 
linux-image-4.12.0-041200rc5-generic_4.12.0-041200rc5.201706112031_amd64.deb ...
Examining /etc/kernel/preinst.d/
run-parts: executing /etc/kernel/preinst.d/intel-microcode 
4.12.0-041200rc5-generic /boot/vmlinuz-4.12.0-041200rc5-generic
Done.
Unpacking linux-image-4.12.0-041200rc5-generic (4.12.0-041200rc5.201706112031) 
...
Setting up linux-headers-4.12.0-041200rc5 (4.12.0-041200rc5.201706112031) ...
Setting up linux-headers-4.12.0-041200rc5-generic 
(4.12.0-041200rc5.201706112031) ...
Examining /etc/kernel/header_postinst.d.
run-parts: executing /etc/kernel/header_postinst.d/dkms 
4.12.0-041200rc5-generic /boot/vmlinuz-4.12.0-041200rc5-generic
Setting up linux-image-4.12.0-041200rc5-generic (4.12.0-041200rc5.201706112031) 
...
Running depmod.
update-initramfs: deferring update (hook will be called later)
Examining /etc/kernel/postinst.d.
run-parts: executing /etc/kernel/postinst.d/apt-auto-removal 
4.12.0-041200rc5-generic /boot/vmlinuz-4.12.0-041200rc5-generic
run-parts: executing /etc/kernel/postinst.d/dkms 4.12.0-041200rc5-generic 
/boot/vmlinuz-4.12.0-041200rc5-generic
run-parts: executing /etc/kernel/postinst.d/initramfs-tools 
4.12.0-041200rc5-generic /boot/vmlinuz-4.12.0-041200rc5-generic
update-initramfs: Generating /boot/initrd.img-4.12.0-041200rc5-generic
W: Possible missing firmware /lib/firmware/i915/kbl_huc_ver02_00_1810.bin for 
module i915
W: Possible missing firmware /lib/firmware/i915/bxt_huc_ver01_07_1398.bin for 
module i915
W: Possible missing firmware /lib/firmware/i915/skl_huc_ver01_07_1398.bin for 
module i915
W: Possible missing firmware /lib/firmware/nvidia/gm20b/pmu/sig.bin for module 
nouveau
W: Possible missing firmware /lib/firmware/nvidia/gm20b/pmu/image.bin for 
module nouveau
W: Possible missing firmware /lib/firmware/nvidia/gm20b/pmu/desc.bin for module 
nouveau
W: Possible missing firmware /lib/firmware/nvidia/gp107/sec2/sig.bin for module 
nouveau
W: Possible missing firmware /lib/firmware/nvidia/gp107/sec2/image.bin for 
module nouveau
W: Possible missing firmware /lib/firmware/nvidia/gp107/sec2/desc.bin for 
module nouveau
W: Possible missing firmware /lib/firmware/nvidia/gp107/nvdec/scrubber.bin for 
module nouveau
W: Possible missing firmware /lib/firmware/nvidia/gp107/gr/sw_method_init.bin 
for module nouveau
W: Possible missing firmware /lib/firmware/nvidia/gp107/gr/sw_bundle_init.bin 
for module nouveau
W: Possible missing firmware /lib/firmware/nvidia/gp107/gr/sw_nonctx.bin for 
module nouveau
W: Possible missing firmware /lib/firmware/nvidia/gp107/gr/sw_ctx.bin for 
module nouveau
W: Possible missing firmware /lib/firmware/nvidia/gp107/gr/gpccs_sig.bin for 
module nouveau
W: Possible missing firmware /lib/firmware/nvidia/gp107/gr/gpccs_data.bin for 
module nouveau
W: Possible missing firmware /lib/firmware/nvidia/gp107/gr/gpccs_inst.bin for 
module nouveau
W: Possible missing firmware /lib/firmware/nvidia/gp107/gr/gpccs_bl.bin for 
module nouveau
W: Possible missing firmware /lib/firmware/nvidia/gp107/gr/fecs_sig.bin for 
module nouveau
W: Possible missing firmware /lib/firmware/nvidia/gp107/gr/fecs_data.bin for 
module nouveau
W: Possible missing firmware /lib/firmware/nvidia/gp107/gr/fecs_inst.bin for 
module nouveau
W: Possible missing firmware /lib/firmware/nvidia/gp107/gr/fecs_bl.bin for 
module nouveau
W: Possible missing firmware /lib/firmware/nvidia/gp107/acr/ucode_unload.bin 
for module nouveau
W: Possible missing firmware /lib/firmware/nvidia/gp107/acr/ucode_load.bin for 
module nouveau
W: Possible missing firmware /lib/firmware/nvidia/gp107/acr/unload_bl.bin for 
module nouveau
W: Possible missing firmware /lib/firmware/nvidia/gp107/acr/bl.bin for module 
nouveau
W: Possible missing firmware /lib/firmware/nvidia/gp106/sec2/sig.bin for module 
nouveau
W: Possible missing firmware 

[Bug 1697556] Re: Computer freezes after login - 4.10.0-22-generic

[Hagen Kuehn]

In answer to your qeustion
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1697556/comments/3

* Yes, the problem is NOT encountered when using Kernel linux-
image-4.10.0-21-generic 4.10.0-21.23.

* The problem is encountered when using 4.10.0-22-generic

In response to your request
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1697556/comments/4

I have tested with upstream kernel 4.10.17

linux-headers-4.10.17-041017_4.10.17-041017.201705201051_all.deb
linux-headers-4.10.17-041017-generic_4.10.17-041017.201705201051_amd64.deb
linux-image-4.10.17-041017-generic_4.10.17-041017.201705201051_amd64.deb

and equally encountered the problem. I therefore added the tag: 'kernel-
bug-exists-upstream'.


** Changed in: linux (Ubuntu)
   Status: Incomplete => Confirmed

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1697556

Title:
  Computer freezes after login - 4.10.0-22-generic

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1697556/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1697556] Re: Computer freezes after login - 4.10.0-22-generic

[Hagen Kuehn]

** Tags added: kernel-bug-exists-upstream

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1697556

Title:
  Computer freezes after login - 4.10.0-22-generic

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1697556/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1697556] [NEW] Computer freezes after login - 4.10.0-22-generic

[Hagen Kuehn]

Public bug reported:

I have got a new Ubuntu 17.04 install on a Dell XPS 15 (Intel(R)
Core(TM) i7-7700HQ CPU @ 2.80GHz) that was installed a couple of days
ago. Login worked fine too.

A couple of days later I installed the suggested kernel update
"4.10.0-22-generic". With kernel 4.10.0-22-generic, the computer freezes
right after login (i.e. after pressing enter, the background image with
the mouse is shown, no responses to any key strokes).

Syslog excerpt:

Jun 12 22:12:48 computername kernel: [   47.603358] NMI watchdog: BUG: soft 
lockup - CPU#1 stuck for 23s! [Xorg.wrap:1672]
Jun 12 22:12:48 computername kernel: [   47.603360] Modules linked in: ccm msr 
arc4 cmac rfcomm uvcvideo videobuf2_vmalloc videobuf2_memops videobuf2_v4l2 
videobuf2_core videodev media btusb btrtl bnep hid_multitouch nls_iso8859_1 
i2c_designware_platform i2c_designware_core snd_hda_codec_hdmi dell_wmi 
dell_led dell_smbios snd_hda_codec_realtek snd_hda_codec_generic snd_hda_intel 
dcdbas ath10k_pci snd_hda_codec ath10k_core intel_rapl snd_hda_core ath 
x86_pkg_temp_thermal snd_hwdep intel_powerclamp mac80211 snd_pcm coretemp 
snd_seq_midi snd_seq_midi_event cfg80211 snd_rawmidi rtsx_pci_ms kvm_intel 
memstick kvm irqbypass crct10dif_pclmul joydev crc32_pclmul snd_seq 
ghash_clmulni_intel snd_seq_device input_leds snd_timer serio_raw snd soundcore 
idma64 virt_dma mei_me mei shpchp processor_thermal_device intel_soc_dts_iosf 
intel_lpss_pci intel_pch_thermal
Jun 12 22:12:48 computername kernel: [   47.603422]  hci_uart btbcm btqca 
btintel bluetooth dell_smo8800 intel_hid intel_lpss_acpi sparse_keymap 
intel_lpss tpm_crb int3403_thermal int3400_thermal acpi_als 
int340x_thermal_zone acpi_thermal_rel acpi_pad kfifo_buf industrialio mac_hid 
pcbc aesni_intel crypto_simd glue_helper cryptd aes_x86_64 dm_crypt parport_pc 
ppdev lp parport ip_tables x_tables autofs4 nouveau rtsx_pci_sdmmc i915 ttm 
i2c_algo_bit drm_kms_helper syscopyarea mxm_wmi sysfillrect psmouse sysimgblt 
fb_sys_fops nvme drm nvme_core rtsx_pci ahci libahci i2c_hid hid 
pinctrl_sunrisepoint video wmi pinctrl_intel fjes
Jun 12 22:12:48 computername kernel: [   47.603453] CPU: 1 PID: 1672 Comm: 
Xorg.wrap Not tainted 4.10.0-22-generic #24-Ubuntu
Jun 12 22:12:48 computername kernel: [   47.603453] Hardware name: Dell Inc. 
XPS 15 9560/05FFDN, BIOS 1.3.3 05/08/2017


Note, this problem is observed with kernel 4.10.0-22-generic whereas it's not 
observed with 4.10.0-21-generic. As I was not able to login to my computer I am 
writing this bug report while it runs on kernel 4.10.0-21-generic. Therefore 
the information attached through the "ubuntu-bug linux" command here, are 
referring to the kernel that is actually working. I decided to nonetheless 
include that information as it might contain other kernel unrelated information 
that would help you troubleshooting.

Please see attached file "syslog-4.10.0-22-generic-freeze-after-
login.log" for the full syslog.

ProblemType: Bug
DistroRelease: Ubuntu 17.04
Package: linux-image-4.10.0-21-generic 4.10.0-21.23
ProcVersionSignature: Ubuntu 4.10.0-21.23-generic 4.10.11
Uname: Linux 4.10.0-21-generic x86_64
ApportVersion: 2.20.4-0ubuntu4.1
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  hkuehn 1796 F pulseaudio
CurrentDesktop: GNOME
Date: Mon Jun 12 23:17:08 2017
EcryptfsInUse: Yes
InstallationDate: Installed on 2017-05-30 (13 days ago)
InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412)
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 003: ID 138a:0091 Validity Sensors, Inc. 
 Bus 001 Device 002: ID 0cf3:e300 Atheros Communications, Inc. 
 Bus 001 Device 004: ID 0c45:6713 Microdia 
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: Dell Inc. XPS 15 9560
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.10.0-21-generic.efi.signed 
root=UUID=e0800d30-3eff-46ac-a6af-38e3bcf99b58 ro quiet splash vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-4.10.0-21-generic N/A
 linux-backports-modules-4.10.0-21-generic  N/A
 linux-firmware 1.164.1
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 05/08/2017
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.3.3
dmi.board.name: 05FFDN
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 10
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvr1.3.3:bd05/08/2017:svnDellInc.:pnXPS159560:pvr:rvnDellInc.:rn05FFDN:rvrA00:cvnDellInc.:ct10:cvr:
dmi.product.name: XPS 15 9560
dmi.sys.vendor: Dell Inc.

** Affects: linux (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug zesty

** Attachment added: "Relevant section of the syslog"
   
https://bugs.launchpad.net/bugs/1697556/+attachment/4894866/+files/syslog-4.10.0-22-generic-freeze-after-login.log

-- 
You received this bug notification 

[Bug 1631137] [NEW] dove-lda apparmor profile prevents lda indexing from working

[Hasse Hagen Johansen]

Public bug reported:

Hi

I had the the full text indexing failing with(every time I received a
mail):

Oct  6 21:31:02 pris dovecot: lda(hhj): Error:
net_connect_unix(/var/run/dovecot/indexer) failed: Permission denied


It seems he profile doesn't allow connecting to the unix socket 
/var/run/dovecot/indexer

/etc/apparmor.d/usr.lib.dovecot.dovecot-lda

Disabling apparmor for dovecot-lda seems to have fixed the problem. Like
this:

aa-disable /usr/lib/dovecot/dovecot-lda

I will change the profile locally on my machine (a little crude to just
disable it) to allow for connecting to the indexing socket, but maybe
that should also be fixed in the apparor-profiles package

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: apparmor-profiles 2.10.95-0ubuntu2.2
ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19
Uname: Linux 4.4.0-38-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
Date: Thu Oct  6 22:01:15 2016
InstallationDate: Installed on 2011-06-24 (1930 days ago)
InstallationMedia: Ubuntu-Server 11.04 "Natty Narwhal" - Release amd64 
(20110426)
PackageArchitecture: all
ProcKernelCmdline: BOOT_IMAGE=/boot/vmlinuz-4.4.0-38-generic 
root=/dev/mapper/miyagi-root ro quiet splash vt.handoff=7
SourcePackage: apparmor
Syslog:
 
UpgradeStatus: Upgraded to xenial on 2016-04-29 (160 days ago)

** Affects: apparmor (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug third-party-packages xenial

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1631137

Title:
  dove-lda apparmor profile prevents lda indexing from working

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1631137/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1452202] Re: ubuntu preseed install fails to set a hostname

[Ben Hagen]

** Bug watch added: Debian Bug tracker #755848
   http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=755848

** Also affects: netcfg via
   http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=755848
   Importance: Unknown
   Status: Unknown

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1452202

Title:
  ubuntu preseed install fails to set a hostname

To manage notifications about this bug go to:
https://bugs.launchpad.net/netcfg/+bug/1452202/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1609544] [NEW] package texlive-latex-base-doc 2015.20160320-1 failed to install/upgrade: Versuch, »/usr/share/doc/texlive-doc/latex/url/url.tex.gz« zu überschreiben, welches auch in Paket texlive

[Hagen von Eitzen]

Public bug reported:

had to get rid of this during do-release-upgrade 14.04 -> 16.04, but am
still trying to recover

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: texlive-latex-base-doc 2015.20160320-1
ProcVersionSignature: Ubuntu 3.13.0-86.131-generic 3.13.11-ckt39
Uname: Linux 3.13.0-86-generic x86_64
ApportVersion: 2.14.1-0ubuntu3.21
Architecture: amd64
Date: Wed Aug  3 20:39:15 2016
DpkgTerminalLog:
 Vorbereitung zum Entpacken von 
.../texlive-latex-base-doc_2015.20160320-1_all.deb ...
 Entpacken von texlive-latex-base-doc (2015.20160320-1) über (2013.20140215-1) 
...
 dpkg: Fehler beim Bearbeiten des Archivs 
/var/cache/apt/archives/texlive-latex-base-doc_2015.20160320-1_all.deb 
(--unpack):
  Versuch, »/usr/share/doc/texlive-doc/latex/url/url.tex.gz« zu überschreiben, 
welches auch in Paket texlive-latex-recommended-doc 2013.20140215-1 ist
DuplicateSignature: package:texlive-latex-base-doc:2015.20160320-1:Versuch, 
»/usr/share/doc/texlive-doc/latex/url/url.tex.gz« zu überschreiben, welches 
auch in Paket texlive-latex-recommended-doc 2013.20140215-1 ist
ErrorMessage: Versuch, »/usr/share/doc/texlive-doc/latex/url/url.tex.gz« zu 
überschreiben, welches auch in Paket texlive-latex-recommended-doc 
2013.20140215-1 ist
InstallationDate: Installed on 2012-06-02 (1523 days ago)
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 
(20120425)
PackageArchitecture: all
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.1
 apt  1.2.12~ubuntu16.04.1
SourcePackage: texlive-base
Title: package texlive-latex-base-doc 2015.20160320-1 failed to 
install/upgrade: Versuch, »/usr/share/doc/texlive-doc/latex/url/url.tex.gz« zu 
überschreiben, welches auch in Paket texlive-latex-recommended-doc 
2013.20140215-1 ist
UpgradeStatus: Upgraded to xenial on 2016-08-03 (0 days ago)

** Affects: texlive-base (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package third-party-packages xenial

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1609544

Title:
  package texlive-latex-base-doc 2015.20160320-1 failed to
  install/upgrade: Versuch, »/usr/share/doc/texlive-
  doc/latex/url/url.tex.gz« zu überschreiben, welches auch in Paket
  texlive-latex-recommended-doc 2013.20140215-1 ist

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/texlive-base/+bug/1609544/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1609503] [NEW] package ppp 2.4.5-5.1ubuntu2.2 failed to install/upgrade: Unterprozess neues pre-installation-Skript gab den Fehlerwert 1 zurück

[Hagen von Eitzen]

Public bug reported:

happended during do-release-upgrade

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: ppp 2.4.5-5.1ubuntu2.2
ProcVersionSignature: Ubuntu 3.13.0-92.139-generic 3.13.11-ckt39
Uname: Linux 3.13.0-92-generic x86_64
ApportVersion: 2.14.1-0ubuntu3.21
Architecture: amd64
Date: Wed Aug  3 19:29:42 2016
DuplicateSignature: package:ppp:2.4.5-5.1ubuntu2.2:Unterprozess neues 
pre-installation-Skript gab den Fehlerwert 1 zurück
ErrorMessage: Unterprozess neues pre-installation-Skript gab den Fehlerwert 1 
zurück
InstallationDate: Installed on 2012-06-02 (1523 days ago)
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 
(20120425)
RelatedPackageVersions:
 dpkg 1.17.5ubuntu5.7
 apt  1.0.1ubuntu2.14
SourcePackage: ppp
Title: package ppp 2.4.5-5.1ubuntu2.2 failed to install/upgrade: Unterprozess 
neues pre-installation-Skript gab den Fehlerwert 1 zurück
UpgradeStatus: Upgraded to xenial on 2016-08-03 (0 days ago)

** Affects: ppp (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package third-party-packages xenial

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1609503

Title:
  package ppp 2.4.5-5.1ubuntu2.2 failed to install/upgrade: Unterprozess
  neues pre-installation-Skript gab den Fehlerwert 1 zurück

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ppp/+bug/1609503/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1609423] Re: systemd: Puppet agent starts before network-online.target is reached

[Ben Hagen]

Also see this upstream bugreport:
https://tickets.puppetlabs.com/browse/PUP-5402

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1609423

Title:
  systemd: Puppet agent starts before network-online.target is reached

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/puppet/+bug/1609423/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1609423] [NEW] systemd: Puppet agent starts before network-online.target is reached

[Ben Hagen]

Public bug reported:

This leads to puppet failing the first run after boot on slower network
connections.

Adding

Wants=network-online.target
After=network-online.target

to the Unit section of the puppet.service file does fix this.

** Affects: puppet (Ubuntu)
 Importance: Undecided
 Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1609423

Title:
  systemd: Puppet agent starts before network-online.target is reached

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/puppet/+bug/1609423/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1582163] [NEW] DHClient Not Acquiring New Lease After Disconnecting and Reconnecting Ethernet cable

[Hagen Kuehn]

Public bug reported:

isc-dhclient-4.3.3 does not acquire a new DHCP lease when the Ethernet
cable was disconnected and reconnected.

This problem is observed with Ubuntu 16.04 whereas it's working with
Ubuntu 14.04 (i.e. isc-dhclient-4.2.4).

The Problem:
When using Virtualbox 5.0.20 and Vagrant 1.8.1, SSH connection fails after the 
Ubuntu 16.04 VM was suspended and then started again from the saved state.

As of this Virtualbox bug https://www.virtualbox.org/ticket/15412 it
appears from Virtualbox 5.0.20 onwards, Virtualbox disconnects the
Ethernet cable for 5 seconds in order to trigger a DHCP lease request.
Since this is not the case with isc-dhclient-4.3.3 on Ubuntu 16.04 any
more, Virtualbox is waiting for network traffic endlessly in order to
infer the IP address of the VM, which is in turn required for Virtualbox
NAT Forwarding to work.

External associated bugs:
https://www.virtualbox.org/ticket/15412
https://github.com/mitchellh/vagrant/issues/7306

** Affects: isc-dhcp (Ubuntu)
 Importance: Undecided
 Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1582163

Title:
  DHClient Not Acquiring New Lease After Disconnecting and Reconnecting
  Ethernet cable

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1582163/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1533568] [NEW] package fonts-tlwg-kinnari-ttf (not installed) failed to install/upgrade: trying to overwrite '/usr/share/fonts/truetype/tlwg/Kinnari-Bold.ttf', which is also in package fonts-tlwg

[Hagen Kuehn]

*** This bug is a duplicate of bug 1533458 ***
https://bugs.launchpad.net/bugs/1533458

Public bug reported:

The error was encountered when I run the Ubuntu Software Updater now
(13/01/2016 - 09:00 GMT).

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: fonts-tlwg-kinnari-ttf (not installed)
ProcVersionSignature: Ubuntu 4.3.0-5.16-generic 4.3.3
Uname: Linux 4.3.0-5-generic x86_64
ApportVersion: 2.19.3-0ubuntu3
Architecture: amd64
Date: Wed Jan 13 09:05:20 2016
DuplicateSignature:
 Unpacking fonts-tlwg-garuda-ttf (1:0.6.2-2) ...
 dpkg: error processing archive 
/var/cache/apt/archives/fonts-tlwg-garuda-ttf_1%3a0.6.2-2_all.deb (--unpack):
  trying to overwrite '/usr/share/fonts/truetype/tlwg/Garuda.ttf', which is 
also in package fonts-tlwg-garuda 1:0.6.2-1
ErrorMessage: trying to overwrite 
'/usr/share/fonts/truetype/tlwg/Kinnari-Bold.ttf', which is also in package 
fonts-tlwg-kinnari 1:0.6.2-1
InstallationDate: Installed on 2015-01-21 (356 days ago)
InstallationMedia: Ubuntu-GNOME 14.10 "Utopic Unicorn" - Release amd64 
(20141022.1)
RelatedPackageVersions:
 dpkg 1.18.3ubuntu1
 apt  1.1.10
SourcePackage: fonts-tlwg
Title: package fonts-tlwg-kinnari-ttf (not installed) failed to 
install/upgrade: trying to overwrite 
'/usr/share/fonts/truetype/tlwg/Kinnari-Bold.ttf', which is also in package 
fonts-tlwg-kinnari 1:0.6.2-1
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: fonts-tlwg (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package package-conflict xenial

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1533568

Title:
  package fonts-tlwg-kinnari-ttf (not installed) failed to
  install/upgrade: trying to overwrite '/usr/share/fonts/truetype/tlwg
  /Kinnari-Bold.ttf', which is also in package fonts-tlwg-kinnari
  1:0.6.2-1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/fonts-tlwg/+bug/1533568/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1532364] Re: Shutter silently fails

[Hagen Kuehn]

I am running 16.04 and installing
"shutter_0.93.1-ppa1-ubuntu16.04.1_all.deb" resolved this problem for me
too.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1532364

Title:
  Shutter silently fails

To manage notifications about this bug go to:
https://bugs.launchpad.net/shutter/+bug/1532364/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1518023] Re: pip3 installs under python3.5

[John Hagen]

For users that want to use Python 3.5, now that this has been changed,
what is the supported way to install pip for Python 3.5?

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1518023

Title:
  pip3 installs under python3.5

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python-pip/+bug/1518023/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1528822] Re: Installation hangs at password prompt

[Jonas Hagen]

Yes, this was it. Thanks a lot!

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1528822

Title:
  Installation hangs at password prompt

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/postgresql-common/+bug/1528822/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1528822] Re: Configuration hangs at password change

[Jonas Hagen]

** Description changed:

- The configuration of postresql-common hangs after "Password:" promt. The
- password can be entered, but is visible and after hitting enter, nothing
- happens. Can be aborted by Ctrl+C. System: Ubuntu 15.10
+ 1) sudo apt-get install postgresql (on a fresh install of Ubuntu 15.10)
+ 2) Give Password as requested for the configuration of postgresql-common 
package. (Entered password is visible.)
+ 3) Hit Enter -> process hangs (Ctrl+C or +D do not work either).
+ 4) Only option to exit apt-get is to kill it and delete lock files manually.
  
-   $ sudo dpkg --configure -a
-   Setting up postgresql-common (169git1) ...
-   Password: hallo
-   ^CPassword change aborted.
-   dpkg: error processing package postgresql-common (--configure):
-subprocess installed post-installation script was interrupted
-   dpkg: dependency problems prevent configuration of postgresql-9.4:
-postgresql-9.4 depends on postgresql-common (>= 142~); however:
- Package postgresql-common is not configured yet.
+ The configuration via dpkg of postresql-common hangs after "Password:"
+ prompt. The password can be entered, but is visible and after hitting
+ enter, nothing happens. Can be aborted by Ctrl+C. System: Ubuntu 15.10
+ 
+   $ sudo dpkg --configure -a
+   Setting up postgresql-common (169git1) ...
+   Password: hallo
+   ^CPassword change aborted.
+   dpkg: error processing package postgresql-common (--configure):
+    subprocess installed post-installation script was interrupted
+   dpkg: dependency problems prevent configuration of postgresql-9.4:
+    postgresql-9.4 depends on postgresql-common (>= 142~); however:
+ Package postgresql-common is not configured yet.
+ 
+ 
+ System: Ubuntu 15.10
+ Package: postgresql-common
+ Version: 169git1

** Description changed:

  1) sudo apt-get install postgresql (on a fresh install of Ubuntu 15.10)
  2) Give Password as requested for the configuration of postgresql-common 
package. (Entered password is visible.)
  3) Hit Enter -> process hangs (Ctrl+C or +D do not work either).
  4) Only option to exit apt-get is to kill it and delete lock files manually.
  
- The configuration via dpkg of postresql-common hangs after "Password:"
+ The configuration via dpkg of postgresql-common hangs after "Password:"
  prompt. The password can be entered, but is visible and after hitting
  enter, nothing happens. Can be aborted by Ctrl+C. System: Ubuntu 15.10
  
    $ sudo dpkg --configure -a
    Setting up postgresql-common (169git1) ...
    Password: hallo
    ^CPassword change aborted.
    dpkg: error processing package postgresql-common (--configure):
     subprocess installed post-installation script was interrupted
    dpkg: dependency problems prevent configuration of postgresql-9.4:
     postgresql-9.4 depends on postgresql-common (>= 142~); however:
  Package postgresql-common is not configured yet.
  
- 
  System: Ubuntu 15.10
  Package: postgresql-common
  Version: 169git1

** Description changed:

  1) sudo apt-get install postgresql (on a fresh install of Ubuntu 15.10)
  2) Give Password as requested for the configuration of postgresql-common 
package. (Entered password is visible.)
  3) Hit Enter -> process hangs (Ctrl+C or +D do not work either).
  4) Only option to exit apt-get is to kill it and delete lock files manually.
  
  The configuration via dpkg of postgresql-common hangs after "Password:"
  prompt. The password can be entered, but is visible and after hitting
- enter, nothing happens. Can be aborted by Ctrl+C. System: Ubuntu 15.10
+ enter, nothing happens. Can be aborted by Ctrl+C.
  
    $ sudo dpkg --configure -a
    Setting up postgresql-common (169git1) ...
    Password: hallo
    ^CPassword change aborted.
    dpkg: error processing package postgresql-common (--configure):
     subprocess installed post-installation script was interrupted
    dpkg: dependency problems prevent configuration of postgresql-9.4:
     postgresql-9.4 depends on postgresql-common (>= 142~); however:
  Package postgresql-common is not configured yet.
  
  System: Ubuntu 15.10
  Package: postgresql-common
  Version: 169git1

** Description changed:

  1) sudo apt-get install postgresql (on a fresh install of Ubuntu 15.10)
  2) Give Password as requested for the configuration of postgresql-common 
package. (Entered password is visible.)
  3) Hit Enter -> process hangs (Ctrl+C or +D do not work either).
  4) Only option to exit apt-get is to kill it and delete lock files manually.
  
- The configuration via dpkg of postgresql-common hangs after "Password:"
- prompt. The password can be entered, but is visible and after hitting
- enter, nothing happens. Can be aborted by Ctrl+C.
+ The configuration via dpkg of postgresql-common also hangs after
+ "Password:" prompt. The password can be entered, but is visible and
+ after hitting enter, nothing happens. Can be aborted by Ctrl+C.
  
    $ sudo dpkg --configure -a
    Setting up postgresql-common (169git1) 

[Bug 1528822] Re: Configuration hangs at password change

[Jonas Hagen]

** Description changed:

  1) sudo apt-get install postgresql (on a fresh install of Ubuntu 15.10)
  2) Give Password as requested for the configuration of postgresql-common 
package. (Entered password is visible.)
  3) Hit Enter -> process hangs (Ctrl+C or +D do not work either).
  4) Only option to exit apt-get is to kill it and delete lock files manually.
  
- The configuration via dpkg of postgresql-common also hangs after
- "Password:" prompt. The password can be entered, but is visible and
- after hitting enter, nothing happens. Can be aborted by Ctrl+C.
+ Full output of apt-get:
+   ...@...:...$ sudo apt-get install postgresql-9.4
+   Reading package lists... Done
+   Building dependency tree   
+   Reading state information... Done
+   The following extra packages will be installed:
+ postgresql-common postgresql-contrib-9.4
+   Suggested packages:
+ oidentd ident-server locales-all libdbd-pg-perl
+   The following NEW packages will be installed:
+ postgresql-9.4 postgresql-common postgresql-contrib-9.4
+   0 upgraded, 3 newly installed, 0 to remove and 0 not upgraded.
+   Need to get 0 B/3'433 kB of archives.
+   After this operation, 14.8 MB of additional disk space will be used.
+   Do you want to continue? [Y/n] y
+   Preconfiguring packages ...
+   Selecting previously unselected package postgresql-common.
+   (Reading database ... 321682 files and directories currently installed.)
+   Preparing to unpack .../postgresql-common_169git1_all.deb ...
+   Adding 'diversion of /usr/bin/pg_config to /usr/bin/pg_config.libpq-dev by 
postgresql-common'
+   Unpacking postgresql-common (169git1) ...
+   Selecting previously unselected package postgresql-9.4.
+   Preparing to unpack .../postgresql-9.4_9.4.5-1_amd64.deb ...
+   Unpacking postgresql-9.4 (9.4.5-1) ...
+   Selecting previously unselected package postgresql-contrib-9.4.
+   Preparing to unpack .../postgresql-contrib-9.4_9.4.5-1_amd64.deb ...
+   Unpacking postgresql-contrib-9.4 (9.4.5-1) ...
+   Processing triggers for man-db (2.7.4-1) ...
+   Processing triggers for ureadahead (0.100.0-19) ...
+   Processing triggers for systemd (225-1ubuntu9) ...
+   Setting up postgresql-common (169git1) ...
+   Password:
+ 
+ 
+ The configuration via dpkg of postgresql-common also hangs after "Password:" 
prompt. The password can be entered, but is visible and after hitting enter, 
nothing happens. Can be aborted by Ctrl+C.
  
    $ sudo dpkg --configure -a
    Setting up postgresql-common (169git1) ...
    Password: hallo
    ^CPassword change aborted.
    dpkg: error processing package postgresql-common (--configure):
     subprocess installed post-installation script was interrupted
    dpkg: dependency problems prevent configuration of postgresql-9.4:
     postgresql-9.4 depends on postgresql-common (>= 142~); however:
  Package postgresql-common is not configured yet.
  
  System: Ubuntu 15.10
  Package: postgresql-common
  Version: 169git1

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1528822

Title:
  Configuration hangs at password change

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/postgresql-common/+bug/1528822/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1528822] Re: Configuration hangs at password prompt

[Jonas Hagen]

** Summary changed:

- Configuration hangs at password change
+ Configuration hangs at password prompt

** Summary changed:

- Configuration hangs at password prompt
+ Installation hangs at password prompt

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1528822

Title:
  Installation hangs at password prompt

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/postgresql-common/+bug/1528822/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1528822] [NEW] Configuration hangs at password change

[Jonas Hagen]

Public bug reported:

The configuration of postresql-common hangs after "Password:" promt. The
password can be entered, but is visible and after hitting enter, nothing
happens. Can be aborted by Ctrl+C. System: Ubuntu 15.10

  $ sudo dpkg --configure -a
  Setting up postgresql-common (169git1) ...
  Password: hallo
  ^CPassword change aborted.
  dpkg: error processing package postgresql-common (--configure):
   subprocess installed post-installation script was interrupted
  dpkg: dependency problems prevent configuration of postgresql-9.4:
   postgresql-9.4 depends on postgresql-common (>= 142~); however:
Package postgresql-common is not configured yet.

** Affects: postgresql-common (Ubuntu)
 Importance: Undecided
 Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1528822

Title:
  Configuration hangs at password change

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/postgresql-common/+bug/1528822/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1459235] Re: Google Address book: Unable to open address book

[Hagen Kuehn]

I am having the same problem too. Since so many different Evolution
versions are affected, I get the impression that this problem is induced
by Google...

Ubuntu 15.04 64-bit
Evolution 3.12.11

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1459235

Title:
  Google Address book: Unable to open address book

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/1459235/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1458323] [NEW] Asterisk crashes with default install because of pjsip

[Hasse Hagen Johansen]

Public bug reported:

Hi

I have just upgraded to Ubuntu 15.04 where I got a new Asterisk. First I
thought I neede to convert my sip.conf to pjsip.conf. But troubles
persist - even after making af copy of my configuration and reinstalling
asterisk,asterisk-modules,asterisk-config etc (making sure /etc/asterisk
was empty before reinstalling). So a clean install also fails and
asterisk is quite unuseable right now

Is seems after starting asterisk(with systemctl start asterisk) and then
doing an asterisk -r i get this:

Connected to Asterisk 13.1.0~dfsg-1ubuntu2 currently running on pris (pid = 
0)
SIP channel loading...
[May 24 14:18:14] ERROR[0]: astobj2.c:116 INTERNAL_OBJ: user_data is NULL
[May 24 14:18:14] ERROR[0]: astobj2.c:116 INTERNAL_OBJ: user_data is NULL
[May 24 14:18:14] ERROR[0]: astobj2.c:116 INTERNAL_OBJ: user_data is NULL
[May 24 14:18:14] ERROR[0]: res_pjsip_sdp_rtp.c:1329 load_module: Unable to 
register SDP handler for audio stream type
[May 24 14:18:14] ERROR[0]: astobj2.c:116 INTERNAL_OBJ: user_data is NULL
[May 24 14:18:14] ERROR[0]: astobj2.c:116 INTERNAL_OBJ: user_data is NULL
pris*CLI
Disconnected from Asterisk server
Asterisk cleanly ending (0).
Executing last minute cleanups

blacklisting res_pjsip.so in /etc/asterisk/modules.conf makes asterisk
not crash

Description:Ubuntu 15.04
Release:15.04
asterisk:
  Installed: 1:13.1.0~dfsg-1ubuntu2
  Candidate: 1:13.1.0~dfsg-1ubuntu2
  Version table:
 *** 1:13.1.0~dfsg-1ubuntu2 0
500 http://dk.archive.ubuntu.com/ubuntu/ vivid/universe amd64 Packages
100 /var/lib/dpkg/status

ProblemType: Bug
DistroRelease: Ubuntu 15.04
Package: asterisk 1:13.1.0~dfsg-1ubuntu2
ProcVersionSignature: Ubuntu 3.19.0-18.18-generic 3.19.6
Uname: Linux 3.19.0-18-generic x86_64
ApportVersion: 2.17.2-0ubuntu1.1
Architecture: amd64
Date: Sun May 24 14:23:26 2015
InstallationDate: Installed on 2011-06-24 (1429 days ago)
InstallationMedia: Ubuntu-Server 11.04 Natty Narwhal - Release amd64 
(20110426)
SourcePackage: asterisk
UpgradeStatus: Upgraded to vivid on 2015-05-23 (0 days ago)

** Affects: asterisk (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug vivid

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to asterisk in Ubuntu.
https://bugs.launchpad.net/bugs/1458323

Title:
  Asterisk crashes with default install because of pjsip

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/asterisk/+bug/1458323/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1458323] [NEW] Asterisk crashes with default install because of pjsip

[Hasse Hagen Johansen]

Public bug reported:

Hi

I have just upgraded to Ubuntu 15.04 where I got a new Asterisk. First I
thought I neede to convert my sip.conf to pjsip.conf. But troubles
persist - even after making af copy of my configuration and reinstalling
asterisk,asterisk-modules,asterisk-config etc (making sure /etc/asterisk
was empty before reinstalling). So a clean install also fails and
asterisk is quite unuseable right now

Is seems after starting asterisk(with systemctl start asterisk) and then
doing an asterisk -r i get this:

Connected to Asterisk 13.1.0~dfsg-1ubuntu2 currently running on pris (pid = 
0)
SIP channel loading...
[May 24 14:18:14] ERROR[0]: astobj2.c:116 INTERNAL_OBJ: user_data is NULL
[May 24 14:18:14] ERROR[0]: astobj2.c:116 INTERNAL_OBJ: user_data is NULL
[May 24 14:18:14] ERROR[0]: astobj2.c:116 INTERNAL_OBJ: user_data is NULL
[May 24 14:18:14] ERROR[0]: res_pjsip_sdp_rtp.c:1329 load_module: Unable to 
register SDP handler for audio stream type
[May 24 14:18:14] ERROR[0]: astobj2.c:116 INTERNAL_OBJ: user_data is NULL
[May 24 14:18:14] ERROR[0]: astobj2.c:116 INTERNAL_OBJ: user_data is NULL
pris*CLI
Disconnected from Asterisk server
Asterisk cleanly ending (0).
Executing last minute cleanups

blacklisting res_pjsip.so in /etc/asterisk/modules.conf makes asterisk
not crash

Description:Ubuntu 15.04
Release:15.04
asterisk:
  Installed: 1:13.1.0~dfsg-1ubuntu2
  Candidate: 1:13.1.0~dfsg-1ubuntu2
  Version table:
 *** 1:13.1.0~dfsg-1ubuntu2 0
500 http://dk.archive.ubuntu.com/ubuntu/ vivid/universe amd64 Packages
100 /var/lib/dpkg/status

ProblemType: Bug
DistroRelease: Ubuntu 15.04
Package: asterisk 1:13.1.0~dfsg-1ubuntu2
ProcVersionSignature: Ubuntu 3.19.0-18.18-generic 3.19.6
Uname: Linux 3.19.0-18-generic x86_64
ApportVersion: 2.17.2-0ubuntu1.1
Architecture: amd64
Date: Sun May 24 14:23:26 2015
InstallationDate: Installed on 2011-06-24 (1429 days ago)
InstallationMedia: Ubuntu-Server 11.04 Natty Narwhal - Release amd64 
(20110426)
SourcePackage: asterisk
UpgradeStatus: Upgraded to vivid on 2015-05-23 (0 days ago)

** Affects: asterisk (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug vivid

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1458323

Title:
  Asterisk crashes with default install because of pjsip

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/asterisk/+bug/1458323/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1391673] Re: error creating new machine with Fedora20+ profile

[Hagen Kuehn]

I think I got to the bottom of it.

Short version:
If the .treeinfo file is missing from the repository, the error ERROR
global name 'fetcher' is not defined is encountered.

Long version:
I had used wget to download the Centos 7 packages from a website mirror to keep 
them on my local HTTP server. What it didn't copy were the hidden files.

When I encountered this error I found this bug report and could
successfully work around/ solve this problem by applying the above
virt-manager-urlfetcher.patch patch.

Later then I realized that the PXE installer reports a 404 error for the
.treeinfo file. I then downloaded the .treeinfo from the repository
and also reverted the urlfetcher.py to its original code line. Now the
error was not encountered anymore.

In the light of this, I presume that there is the possiblity that the
others encountered this error because of the the missing .treeinfo
file.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1391673

Title:
  error creating new machine with Fedora20+ profile

To manage notifications about this bug go to:
https://bugs.launchpad.net/hundredpapercuts/+bug/1391673/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1391829] [NEW] package syslinux-themes-debian (not installed) failed to install/upgrade: Paket syslinux-themes-debian ist nicht bereit zur Konfiguration kann nicht konfiguriert werden (momentane

[Hagen]

Public bug reported:

This issue occurs every start up, but only once.

ProblemType: Package
DistroRelease: Ubuntu 14.10
Package: syslinux-themes-debian (not installed)
ProcVersionSignature: Ubuntu 3.16.0-24.32-generic 3.16.4
Uname: Linux 3.16.0-24-generic x86_64
ApportVersion: 2.14.7-0ubuntu8
AptOrdering: syslinux-themes-debian: Configure
Architecture: amd64
Date: Tue Nov 11 23:07:54 2014
DpkgTerminalLog:
 dpkg: Fehler beim Bearbeiten des Paketes syslinux-themes-debian (--configure):
  Paket syslinux-themes-debian ist nicht bereit zur Konfiguration
  kann nicht konfiguriert werden (momentaner Status »half-installed«)
DuplicateSignature: package:syslinux-themes-debian:(not installed):Paket 
syslinux-themes-debian ist nicht bereit zur Konfiguration  kann nicht 
konfiguriert werden (momentaner Status »half-installed«)
ErrorMessage: Paket syslinux-themes-debian ist nicht bereit zur Konfiguration  
kann nicht konfiguriert werden (momentaner Status »half-installed«)
InstallationDate: Installed on 2014-05-27 (169 days ago)
InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417)
SourcePackage: syslinux-themes-debian
Title: package syslinux-themes-debian (not installed) failed to 
install/upgrade: Paket syslinux-themes-debian ist nicht bereit zur 
Konfiguration  kann nicht konfiguriert werden (momentaner Status 
»half-installed«)
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: syslinux-themes-debian (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package utopic

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1391829

Title:
  package syslinux-themes-debian (not installed) failed to
  install/upgrade: Paket syslinux-themes-debian ist nicht bereit zur
  Konfiguration  kann nicht konfiguriert werden (momentaner Status
  »half-installed«)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/syslinux-themes-debian/+bug/1391829/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 997269] Re: dovecot imap broken by apparmor policy

[Hasse Hagen Johansen]

For me it has been fixed by 14.04 and can now run with the different
dovecot apparmor profiles swithed on

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to dovecot in Ubuntu.
https://bugs.launchpad.net/bugs/997269

Title:
  dovecot imap broken by apparmor policy

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/997269/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 997269] Re: dovecot imap broken by apparmor policy

[Hasse Hagen Johansen]

For me it has been fixed by 14.04 and can now run with the different
dovecot apparmor profiles swithed on

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/997269

Title:
  dovecot imap broken by apparmor policy

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/997269/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1277018] Re: Backuppc claims to configure apache2, but doesn't

[Ben Hagen]

*** This bug is a duplicate of bug 1243476 ***
https://bugs.launchpad.net/bugs/1243476

** This bug has been marked a duplicate of bug 1243476
   Apache 2.4 transition broke the web interface

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to backuppc in Ubuntu.
https://bugs.launchpad.net/bugs/1277018

Title:
  Backuppc claims to configure apache2, but doesn't

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/backuppc/+bug/1277018/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1277018] Re: Backuppc claims to configure apache2, but doesn't

[Ben Hagen]

*** This bug is a duplicate of bug 1243476 ***
https://bugs.launchpad.net/bugs/1243476

** This bug has been marked a duplicate of bug 1243476
   Apache 2.4 transition broke the web interface

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1277018

Title:
  Backuppc claims to configure apache2, but doesn't

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/backuppc/+bug/1277018/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1310569] Re: puppet does not correctly handle unusually encoded filenames in a file resource

[Ben Hagen]

Not sure what you mean by unusually encoded but the following line
will trigger the bug:

mkdir -p /tmp/src; touch /tmp/ö.txt; puppet apply --exec 'file {
/tmp/dst:ensure = directory, recurse = true, source = /tmp/src }'

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to puppet in Ubuntu.
https://bugs.launchpad.net/bugs/1310569

Title:
  puppet does not correctly handle unusually encoded filenames in a file
  resource

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/puppet/+bug/1310569/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1310569] Re: puppet does not correctly handle unusually encoded filenames in a file resource

[Ben Hagen]

Not sure what you mean by unusually encoded but the following line
will trigger the bug:

mkdir -p /tmp/src; touch /tmp/ö.txt; puppet apply --exec 'file {
/tmp/dst:ensure = directory, recurse = true, source = /tmp/src }'

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1310569

Title:
  puppet does not correctly handle unusually encoded filenames in a file
  resource

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/puppet/+bug/1310569/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1267824] Re: arecord didn't found soundcards

[Hagen H.]

Hi Raymond!

i've done alsa-info.sh taday (Post #2)

The results are located here: http://www.alsa-
project.org/db/?f=faaa002a54d579e6e829a15f06b7c9af96ae70da

regarding to Post #3:

fyi: i don't need an output. i only want to record from line in!

i didn't find the information you asked for in the windows *.inf files.

i've uploaded all *.inf files.
launchpad don't accept my attachment. here is the dropbox-link: 
https://dl.dropboxusercontent.com/s/5rwzcf3pzknv92c/HDA.zip?dl=1token_hash=AAEi_Oc_HGHc-ahzSO2x1TCEXotlzyEQK26t3g0dLPxTog

Thanks for all!!!

cu
Hagen

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1267824

Title:
  arecord didn't found soundcards

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1267824/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1267824] Re: arecord didn't found soundcards

[Hagen H.]

sorry: the correct link:
https://www.dropbox.com/s/5rwzcf3pzknv92c/HDA.zip

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1267824

Title:
  arecord didn't found soundcards

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1267824/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1267824] Re: arecord didn't found soundcards

[Hagen H.]

the board only has one stereo line-in !! this is the port i want to use!

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1267824

Title:
  arecord didn't found soundcards

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1267824/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1267824] [NEW] arecord didn't found soundcards

[Hagen H.]

Public bug reported:

Mainboard Advantech PCM-3356

Onboard-Soundcard with two codecs: card0 ATI R6xx HDMI and card1
Realtek ALC892

arecord and aplay didin't find any soundcards. i want to record from
card1

cu
Hagen

ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: alsa-base 1.0.25+dfsg-0ubuntu1.1
ProcVersionSignature: Ubuntu 3.5.0-40.62~precise1-generic 3.5.7.20
Uname: Linux 3.5.0-40-generic i686
AlsaVersion:
 Advanced Linux Sound Architecture Driver Version 1.0.2x-130606-v5.18.
 Compiled on Jan 10 2014 for kernel 3.5.0-40-generic (SMP).
AplayDevices: aplay: device_list:252: no soundcards found...
ApportVersion: 2.0.1-0ubuntu17.6
Architecture: i386
ArecordDevices: arecord: device_list:252: no soundcards found...
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/controlC1', '/dev/snd/hwC1D0', '/dev/snd/controlC0', 
'/dev/snd/hwC0D0', '/dev/snd/pcmC0D3p', '/dev/snd/seq', '/dev/snd/timer', 
'/dev/sequencer2', '/dev/sequencer'] failed with exit code 1:
CurrentDmesg:
 
Date: Fri Jan 10 13:07:57 2014
InstallationMedia: Ubuntu-Server 12.04.2 LTS Precise Pangolin - Release i386 
(20130214)
MarkForUpload: True
PackageArchitecture: all
ProcEnviron:
 TERM=linux
 PATH=(custom, no user)
 LANG=de_DE.UTF-8
 SHELL=/bin/bash
SourcePackage: alsa-driver
Symptom: audio
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 08/22/2013
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 4.6.5
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: Inagua CRB
dmi.board.vendor: AMD Corporation
dmi.board.version: To be filled by O.E.M.
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: To Be Filled By O.E.M.
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd08/22/2013:svnTobefilledbyO.E.M.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnAMDCorporation:rnInaguaCRB:rvrTobefilledbyO.E.M.:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
dmi.product.name: To be filled by O.E.M.
dmi.product.version: To be filled by O.E.M.
dmi.sys.vendor: To be filled by O.E.M.
mtime.conffile..etc.modprobe.d.alsa.base.conf: 2014-01-10T12:14:38.534061

** Affects: alsa-driver (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: apport-bug i386 precise

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1267824

Title:
  arecord didn't found soundcards

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1267824/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1051947] Re: Acer TravelMate 6293 - no s/pdif (iec958) anymore since Ubuntu 12.04 LTS

[Hagen]

Yes, a patch has been created:

https://git.kernel.org/cgit/linux/kernel/git/tiwai/sound.git/commit/?id=24eff328f65c8ef352c90b6adb7c2f39eb94205d

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1051947

Title:
  Acer TravelMate 6293 - no s/pdif (iec958) anymore since Ubuntu 12.04
  LTS

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1051947/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1051947] Re: Acer TravelMate 6293 - no s/pdif (iec958) anymore since Ubuntu 12.04 LTS

[Hagen]

# sudo dmidecode -s bios-version  sudo dmidecode -s bios-release-date
V1.41
05/26/10

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1051947

Title:
  Acer TravelMate 6293 - no s/pdif (iec958) anymore since Ubuntu 12.04
  LTS

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1051947/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1051947] Re: Acer TravelMate 6293 - no s/pdif (iec958) anymore since Ubuntu 12.04 LTS

[Hagen]

I installed hda-jack-retask as suggested and got it working with the
default kernel (3.2.0-55-generic), finally! The created files have been
slightly modified (cleaned up), so the workaround looks as follows:

$ cat /etc/modprobe.d/hda-jack-retask.conf 
# This file was added by the program 'hda-jack-retask'.
# If you want to revert the changes made by this program, you can simply erase 
this file and reboot your computer.
options snd-hda-intel patch=hda-jack-retask.fw

$ cat /lib/firmware/hda-jack-retask.fw 
[codec]
0x10ec0268 0x10250139 0

[pincfg]
0x1e 0x014b1180

With that config, pin 0x1e will be connected to S/PDIF out - et voilà.
Thanks a lot for pointing this out, Raymond!

I also wrote a mail to the author to have it fixed in a future kernel
release.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1051947

Title:
  Acer TravelMate 6293 - no s/pdif (iec958) anymore since Ubuntu 12.04
  LTS

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1051947/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1246292] Re: Launcher and top panel missing after interrupted upgrade to Saucy

[thomas michael hagen]

When I log in as guest, the launcher and top panel are there.

When I press Ctrl-Alt-F1, Ctrl-Alt-F2, etc., I am taken to the various
terminals (ttys). From in there, there does not seem to be anything else
wrong with the machine. Note - NOT Alt-F2 as previously stated.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1246292

Title:
  Launcher and top panel missing after interrupted upgrade to Saucy

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/1246292/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1246292] [NEW] Launcher and top panel missing after interrupted upgrade to Saucy

[thomas michael hagen]

Public bug reported:

My first attempt to upgrade from 13.04 to 13.10 halted midway. I shut
down the computer using the shut down command, and started it again some
time later.

I launched update-manager again, and it told me that it could only do an
incomplete upgrade, because it had previously been interrupted.

The upgrade finished, and I restarted the computer as instructed. It
turned back on, and I can now see my background image, but the launcher
and the top panel are gone. Thus, I can't use the computer for anything.

I've tried starting terminal by pressing Alt-F2, but nothing happens.

I can move the mouse around the screen, and right-click brings up the
right-click menu.

I am, of course, writing this bug report from another system, as my
system is now non-functional.

** Affects: update-manager (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: launcher saucy upgrade

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1246292

Title:
  Launcher and top panel missing after interrupted upgrade to Saucy

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/1246292/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1051947] Re: Acer TravelMate 6293 - no s/pdif (iec958) anymore since Ubuntu 12.04 LTS

[Hagen]

** Changed in: linux (Ubuntu)
   Status: Expired = Confirmed

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1051947

Title:
  Acer TravelMate 6293 - no s/pdif (iec958) anymore since Ubuntu 12.04
  LTS

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1051947/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1242365] Re: dovecot imapd process crashes using dovecot-solr

[Hasse Hagen Johansen]

** Changed in: dovecot (Ubuntu)
   Status: Invalid = New

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to dovecot in Ubuntu.
https://bugs.launchpad.net/bugs/1242365

Title:
  dovecot imapd process crashes using dovecot-solr

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dovecot/+bug/1242365/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1242365] Re: dovecot imapd process crashes using dovecot-solr

[Hasse Hagen Johansen]

Ok. I lookedsome more into this bug. The imap process is not coredumping
anymore when accessing the mailbox via imap (for some reason I cannot
quite understand)

But I cannot update the text index anymore. I have found what seems the
exact same bug reported in debians bugtracker http://bugs.debian.org
/cgi-bin/bugreport.cgi?bug=719666

I have checked the versions of the debian bugreport against the versions
installed on my Ubuntu system. They are the same for dovecot-solr and
libvurl3.

I can also reproduce it on a newly installed Ubuntu 13.10 in a virtual
machine. By installing dove-solr,solr and configuring it. Then sending a
couple of mails to the user and then try to do a /usr/bin/doveadm index
-u user INBOX

So it seems that dovecot fultext search with solr is broken :(

Sorry for my original confusing bugreport

** Bug watch added: Debian Bug tracker #719666
   http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=719666

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to dovecot in Ubuntu.
https://bugs.launchpad.net/bugs/1242365

Title:
  dovecot imapd process crashes using dovecot-solr

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dovecot/+bug/1242365/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1242365] Re: dovecot imapd process crashes using dovecot-solr

[Hasse Hagen Johansen]

** Changed in: dovecot (Ubuntu)
   Status: Invalid = New

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1242365

Title:
  dovecot imapd process crashes using dovecot-solr

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dovecot/+bug/1242365/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1242365] Re: dovecot imapd process crashes using dovecot-solr

[Hasse Hagen Johansen]

Ok. I lookedsome more into this bug. The imap process is not coredumping
anymore when accessing the mailbox via imap (for some reason I cannot
quite understand)

But I cannot update the text index anymore. I have found what seems the
exact same bug reported in debians bugtracker http://bugs.debian.org
/cgi-bin/bugreport.cgi?bug=719666

I have checked the versions of the debian bugreport against the versions
installed on my Ubuntu system. They are the same for dovecot-solr and
libvurl3.

I can also reproduce it on a newly installed Ubuntu 13.10 in a virtual
machine. By installing dove-solr,solr and configuring it. Then sending a
couple of mails to the user and then try to do a /usr/bin/doveadm index
-u user INBOX

So it seems that dovecot fultext search with solr is broken :(

Sorry for my original confusing bugreport

** Bug watch added: Debian Bug tracker #719666
   http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=719666

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1242365

Title:
  dovecot imapd process crashes using dovecot-solr

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dovecot/+bug/1242365/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1242365] [NEW] dovecot imapd process crashes using dovecot-solr

[Hasse Hagen Johansen]

Public bug reported:

I had my dovecot successfully configured for using solr for fulltext
search with dovecot on my ubuntu 13.04. Now I have upgraded to 13.10 and
I now see this in the log crashing the imapd process(and I don't quite
understand why maxfd can less than zero. I Did try disable apparmor but
it didn't help):

Oct 20 16:38:11 pris dovecot: imap(hhj): Panic: file solr-connection.c: line 
545 (solr_connection_post_more): assertion failed: (maxfd = 0)
Oct 20 16:38:11 pris dovecot: imap(hhj): Error: Raw backtrace: 
/usr/lib/dovecot/libdovecot.so.0(+0x3b297) [0x7fdab6a1e297] - 
/usr/lib/dovecot/libdovecot.so.0(+0x3b35e) [0x7fdab6a1e35e] - 
/usr/lib/dovecot/libdovecot.so.0(i_fatal+0) [0x7fdab69f6763] - 
/usr/lib/dovecot/modules/lib21_fts_solr_plugin.so(solr_connection_post_more+0x259)
 [0x7fdab53891b9] - 
/usr/lib/dovecot/modules/lib21_fts_solr_plugin.so(solr_connection_post+0x27) 
[0x7fdab5389377] - /usr/lib/dovecot/modules/lib21_fts_solr_plugin.so(+0x415f) 
[0x7fdab538615f] - /usr/lib/dovecot/libdovecot-storage.so.0(+0x41d3c) 
[0x7fdab6caad3c] - /usr/lib/dovecot/libdovecot-storage.so.0(+0x46ca0) 
[0x7fdab6cafca0] - 
/usr/lib/dovecot/libdovecot-storage.so.0(maildir_file_do+0x3d) [0x7fdab6cb00dd] 
- /usr/lib/dovecot/libdovecot-storage.so.0(maildir_sync_index+0x2d1) 
[0x7fdab6cab361] - /usr/lib/dovecot/libdovecot-storage.so.0(+0x41028) 
[0x7fdab6caa028] - 
/usr/lib/dovecot/libdovecot-storage.so.0(maildir_storage_sync_init+0xdd) 
[0x7fdab6c
 aa74d] - /usr/lib/dovecot/libdovecot-storage.so.0(mailbox_sync_init+0x29) 
[0x7fdab6cd7309] - /usr/lib/dovecot/libdovecot-storage.so.0(mailbox_sync+0x27) 
[0x7fdab6cd7417] - dovecot/imap(cmd_select_full+0x137) [0x7fdab7195407] - 
dovecot/imap(command_exec+0x3c) [0x7fdab719905c] - dovecot/imap(+0x1107b) 
[0x7fdab719807b] - dovecot/imap(+0x1112d) [0x7fdab719812d] - 
dovecot/imap(client_handle_input+0x12d) [0x7fdab71983dd] - 
dovecot/imap(client_input+0x65) [0x7fdab7198ba5] - 
/usr/lib/dovecot/libdovecot.so.0(io_loop_call_io+0x27) [0x7fdab6a2a9f7] - 
/usr/lib/dovecot/libdovecot.so.0(io_loop_handler_run+0xa7) [0x7fdab6a2b6e7] - 
/usr/lib/dovecot/libdovecot.so.0(io_loop_run+0x28) [0x7fdab6a2a5f8] - 
/usr/lib/dovecot/libdovecot.so.0(master_service_run+0x13) [0x7fdab6a17ae3] - 
dovecot/imap(main+0x2ba) [0x7fdab719084a] - 
/lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf5) [0x7fdab663cde5] - 
dovecot/imap(+0x99b4) [0x7fdab71909b4]
Oct 20 16:38:11 pris dovecot: imap(hhj): Fatal: master: service(imap): child 
4788 killed with signal 6 (core dumped)

ProblemType: Bug
DistroRelease: Ubuntu 13.10
Package: dovecot-solr 1:2.1.7-7ubuntu3
ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3
Uname: Linux 3.11.0-12-generic x86_64
ApportVersion: 2.12.5-0ubuntu2
Architecture: amd64
Date: Sun Oct 20 16:46:40 2013
InstallationDate: Installed on 2011-06-24 (848 days ago)
InstallationMedia: Ubuntu-Server 11.04 Natty Narwhal - Release amd64 
(20110426)
MarkForUpload: True
SourcePackage: dovecot
UpgradeStatus: Upgraded to saucy on 2013-10-20 (0 days ago)

** Affects: dovecot (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug saucy

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to dovecot in Ubuntu.
https://bugs.launchpad.net/bugs/1242365

Title:
  dovecot imapd process crashes using dovecot-solr

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dovecot/+bug/1242365/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1242365] Re: dovecot imapd process crashes using dovecot-solr

[Hasse Hagen Johansen]

Sorry. I think this bug can be closed. It works now. I think it just
needed to be reindexed

** Changed in: dovecot (Ubuntu)
   Status: New = Invalid

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to dovecot in Ubuntu.
https://bugs.launchpad.net/bugs/1242365

Title:
  dovecot imapd process crashes using dovecot-solr

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dovecot/+bug/1242365/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1242365] [NEW] dovecot imapd process crashes using dovecot-solr

[Hasse Hagen Johansen]

Public bug reported:

I had my dovecot successfully configured for using solr for fulltext
search with dovecot on my ubuntu 13.04. Now I have upgraded to 13.10 and
I now see this in the log crashing the imapd process(and I don't quite
understand why maxfd can less than zero. I Did try disable apparmor but
it didn't help):

Oct 20 16:38:11 pris dovecot: imap(hhj): Panic: file solr-connection.c: line 
545 (solr_connection_post_more): assertion failed: (maxfd = 0)
Oct 20 16:38:11 pris dovecot: imap(hhj): Error: Raw backtrace: 
/usr/lib/dovecot/libdovecot.so.0(+0x3b297) [0x7fdab6a1e297] - 
/usr/lib/dovecot/libdovecot.so.0(+0x3b35e) [0x7fdab6a1e35e] - 
/usr/lib/dovecot/libdovecot.so.0(i_fatal+0) [0x7fdab69f6763] - 
/usr/lib/dovecot/modules/lib21_fts_solr_plugin.so(solr_connection_post_more+0x259)
 [0x7fdab53891b9] - 
/usr/lib/dovecot/modules/lib21_fts_solr_plugin.so(solr_connection_post+0x27) 
[0x7fdab5389377] - /usr/lib/dovecot/modules/lib21_fts_solr_plugin.so(+0x415f) 
[0x7fdab538615f] - /usr/lib/dovecot/libdovecot-storage.so.0(+0x41d3c) 
[0x7fdab6caad3c] - /usr/lib/dovecot/libdovecot-storage.so.0(+0x46ca0) 
[0x7fdab6cafca0] - 
/usr/lib/dovecot/libdovecot-storage.so.0(maildir_file_do+0x3d) [0x7fdab6cb00dd] 
- /usr/lib/dovecot/libdovecot-storage.so.0(maildir_sync_index+0x2d1) 
[0x7fdab6cab361] - /usr/lib/dovecot/libdovecot-storage.so.0(+0x41028) 
[0x7fdab6caa028] - 
/usr/lib/dovecot/libdovecot-storage.so.0(maildir_storage_sync_init+0xdd) 
[0x7fdab6c
 aa74d] - /usr/lib/dovecot/libdovecot-storage.so.0(mailbox_sync_init+0x29) 
[0x7fdab6cd7309] - /usr/lib/dovecot/libdovecot-storage.so.0(mailbox_sync+0x27) 
[0x7fdab6cd7417] - dovecot/imap(cmd_select_full+0x137) [0x7fdab7195407] - 
dovecot/imap(command_exec+0x3c) [0x7fdab719905c] - dovecot/imap(+0x1107b) 
[0x7fdab719807b] - dovecot/imap(+0x1112d) [0x7fdab719812d] - 
dovecot/imap(client_handle_input+0x12d) [0x7fdab71983dd] - 
dovecot/imap(client_input+0x65) [0x7fdab7198ba5] - 
/usr/lib/dovecot/libdovecot.so.0(io_loop_call_io+0x27) [0x7fdab6a2a9f7] - 
/usr/lib/dovecot/libdovecot.so.0(io_loop_handler_run+0xa7) [0x7fdab6a2b6e7] - 
/usr/lib/dovecot/libdovecot.so.0(io_loop_run+0x28) [0x7fdab6a2a5f8] - 
/usr/lib/dovecot/libdovecot.so.0(master_service_run+0x13) [0x7fdab6a17ae3] - 
dovecot/imap(main+0x2ba) [0x7fdab719084a] - 
/lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf5) [0x7fdab663cde5] - 
dovecot/imap(+0x99b4) [0x7fdab71909b4]
Oct 20 16:38:11 pris dovecot: imap(hhj): Fatal: master: service(imap): child 
4788 killed with signal 6 (core dumped)

ProblemType: Bug
DistroRelease: Ubuntu 13.10
Package: dovecot-solr 1:2.1.7-7ubuntu3
ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3
Uname: Linux 3.11.0-12-generic x86_64
ApportVersion: 2.12.5-0ubuntu2
Architecture: amd64
Date: Sun Oct 20 16:46:40 2013
InstallationDate: Installed on 2011-06-24 (848 days ago)
InstallationMedia: Ubuntu-Server 11.04 Natty Narwhal - Release amd64 
(20110426)
MarkForUpload: True
SourcePackage: dovecot
UpgradeStatus: Upgraded to saucy on 2013-10-20 (0 days ago)

** Affects: dovecot (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug saucy

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1242365

Title:
  dovecot imapd process crashes using dovecot-solr

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dovecot/+bug/1242365/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1242365] Re: dovecot imapd process crashes using dovecot-solr

[Hasse Hagen Johansen]

Sorry. I think this bug can be closed. It works now. I think it just
needed to be reindexed

** Changed in: dovecot (Ubuntu)
   Status: New = Invalid

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1242365

Title:
  dovecot imapd process crashes using dovecot-solr

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dovecot/+bug/1242365/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1241109] Re: evolution is no longer translated

[Hagen Malessa]

workaround for this:

strace shows:
open(/usr/share/locale-langpack/de/LC_MESSAGES/evolution-3.8.mo, O_RDONLY) = 
-1 ENOENT (No such file or directory)

cd /usr/share/locale-langpack/de/LC_MESSAGES 
ls  evolution-* shows:
evolution-3.6.mo
evolution-data-server-3.6.mo

simply create symlinks:
sudo ln -s evolution-3.6.mo evolution-3.8.mo
sudo ln -s evolution-data-server-3.6.mo evolution-data-server-3.8.mo

thats it

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1241109

Title:
  evolution is no longer translated

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/1241109/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1051947] CRDA.txt

[Hagen]

apport information

** Attachment added: CRDA.txt
   https://bugs.launchpad.net/bugs/1051947/+attachment/3794707/+files/CRDA.txt

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1051947

Title:
  Acer TravelMate 6293 - no s/pdif (iec958) anymore since Ubuntu 12.04
  LTS

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1051947/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1051947] IwConfig.txt

[Hagen]

apport information

** Attachment added: IwConfig.txt
   
https://bugs.launchpad.net/bugs/1051947/+attachment/3794709/+files/IwConfig.txt

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1051947

Title:
  Acer TravelMate 6293 - no s/pdif (iec958) anymore since Ubuntu 12.04
  LTS

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1051947/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1051947] BootDmesg.txt

[Hagen]

apport information

** Attachment added: BootDmesg.txt
   
https://bugs.launchpad.net/bugs/1051947/+attachment/3794706/+files/BootDmesg.txt

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1051947

Title:
  Acer TravelMate 6293 - no s/pdif (iec958) anymore since Ubuntu 12.04
  LTS

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1051947/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1051947] CurrentDmesg.txt

[Hagen]

apport information

** Attachment added: CurrentDmesg.txt
   
https://bugs.launchpad.net/bugs/1051947/+attachment/3794708/+files/CurrentDmesg.txt

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1051947

Title:
  Acer TravelMate 6293 - no s/pdif (iec958) anymore since Ubuntu 12.04
  LTS

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1051947/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1051947] Re: Acer TravelMate 6293 - no s/pdif (iec958) anymore since Ubuntu 12.04 LTS

[Hagen]

apport information

** Tags added: apport-collected saucy

** Description changed:

- Since upgrading to Precise the IEC958 setting is missing when opening
- 'alsamixer', resulting in no S/PDIF output signal at all. Prior to that,
- it was possible to add the ALC267/268 module option snd-hda-intel
- model=zepto to forcible activate the S/PDIF support, but this parameter
- has been vanished with kernel version 3.2.x. When installing a 3.0.x
- kernel (from Ubuntu 11.10) it works again.
+ Since upgrading to Precise the IEC958 setting is missing when opening 
'alsamixer', resulting in no S/PDIF output signal at all. Prior to that, it was 
possible to add the ALC267/268 module option snd-hda-intel model=zepto to 
forcible activate the S/PDIF support, but this parameter has been vanished with 
kernel version 3.2.x. When installing a 3.0.x kernel (from Ubuntu 11.10) it 
works again.
+ --- 
+ ApportVersion: 2.12.1-0ubuntu2
+ Architecture: i386
+ AudioDevicesInUse:
+  USERPID ACCESS COMMAND
+  /dev/snd/controlC0:  ubuntu 2704 F pulseaudio
+   ubuntu 4506 F pulseaudio
+ CasperVersion: 1.336
+ DistroRelease: Ubuntu 13.10
+ LiveMediaBuild: Ubuntu 13.10 Saucy Salamander - Alpha i386 (20130829)
+ MachineType: Acer TravelMate 6293
+ MarkForUpload: True
+ Package: linux (not installed)
+ PccardctlIdent:
+  Socket 0:
+no product info available
+ PccardctlStatus:
+  Socket 0:
+no card
+ ProcEnviron:
+  LANGUAGE=de_DE
+  TERM=xterm
+  PATH=(custom, no user)
+  LANG=de_DE.UTF-8
+  SHELL=/bin/bash
+ ProcFB: 0 inteldrmfb
+ ProcKernelCmdLine: noprompt cdrom-detect/try-usb=true 
file=/cdrom/preseed/hostname.seed boot=casper initrd=/casper/initrd.lz quiet 
splash -- maybe-ubiquity
+ ProcVersionSignature: Ubuntu 3.11.0-4.9-generic 3.11.0-rc7
+ PulseList:
+  Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
+  No PulseAudio daemon running, or not running as session daemon.
+ RelatedPackageVersions:
+  linux-restricted-modules-3.11.0-4-generic N/A
+  linux-backports-modules-3.11.0-4-generic  N/A
+  linux-firmware1.113
+ Tags:  saucy
+ Uname: Linux 3.11.0-4-generic i686
+ UpgradeStatus: No upgrade log present (probably fresh install)
+ UserGroups:
+  
+ dmi.bios.date: 04/02/09
+ dmi.bios.vendor: Acer
+ dmi.bios.version: V1.25
+ dmi.board.asset.tag: Tag 12345
+ dmi.board.name: TravelMate 6293
+ dmi.board.vendor: Acer
+ dmi.board.version: Not Applicable
+ dmi.chassis.type: 10
+ dmi.chassis.vendor: Acer
+ dmi.chassis.version: N/A
+ dmi.modalias: 
dmi:bvnAcer:bvrV1.25:bd04/02/09:svnAcer:pnTravelMate6293:pvr03:rvnAcer:rnTravelMate6293:rvrNotApplicable:cvnAcer:ct10:cvrN/A:
+ dmi.product.name: TravelMate 6293
+ dmi.product.version: 03
+ dmi.sys.vendor: Acer

** Attachment added: AlsaInfo.txt
   
https://bugs.launchpad.net/bugs/1051947/+attachment/3794705/+files/AlsaInfo.txt

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1051947

Title:
  Acer TravelMate 6293 - no s/pdif (iec958) anymore since Ubuntu 12.04
  LTS

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1051947/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1051947] WifiSyslog.txt

[Hagen]

apport information

** Attachment added: WifiSyslog.txt
   
https://bugs.launchpad.net/bugs/1051947/+attachment/3794718/+files/WifiSyslog.txt

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1051947

Title:
  Acer TravelMate 6293 - no s/pdif (iec958) anymore since Ubuntu 12.04
  LTS

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1051947/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1051947] ProcCpuinfo.txt

[Hagen]

apport information

** Attachment added: ProcCpuinfo.txt
   
https://bugs.launchpad.net/bugs/1051947/+attachment/3794712/+files/ProcCpuinfo.txt

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1051947

Title:
  Acer TravelMate 6293 - no s/pdif (iec958) anymore since Ubuntu 12.04
  LTS

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1051947/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1051947] ProcModules.txt

[Hagen]

apport information

** Attachment added: ProcModules.txt
   
https://bugs.launchpad.net/bugs/1051947/+attachment/3794714/+files/ProcModules.txt

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1051947

Title:
  Acer TravelMate 6293 - no s/pdif (iec958) anymore since Ubuntu 12.04
  LTS

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1051947/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1051947] Lsusb.txt

[Hagen]

apport information

** Attachment added: Lsusb.txt
   https://bugs.launchpad.net/bugs/1051947/+attachment/3794711/+files/Lsusb.txt

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1051947

Title:
  Acer TravelMate 6293 - no s/pdif (iec958) anymore since Ubuntu 12.04
  LTS

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1051947/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1051947] ProcInterrupts.txt

[Hagen]

apport information

** Attachment added: ProcInterrupts.txt
   
https://bugs.launchpad.net/bugs/1051947/+attachment/3794713/+files/ProcInterrupts.txt

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1051947

Title:
  Acer TravelMate 6293 - no s/pdif (iec958) anymore since Ubuntu 12.04
  LTS

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1051947/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1051947] RfKill.txt

[Hagen]

apport information

** Attachment added: RfKill.txt
   https://bugs.launchpad.net/bugs/1051947/+attachment/3794715/+files/RfKill.txt

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1051947

Title:
  Acer TravelMate 6293 - no s/pdif (iec958) anymore since Ubuntu 12.04
  LTS

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1051947/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1051947] Lspci.txt

[Hagen]

apport information

** Attachment added: Lspci.txt
   https://bugs.launchpad.net/bugs/1051947/+attachment/3794710/+files/Lspci.txt

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1051947

Title:
  Acer TravelMate 6293 - no s/pdif (iec958) anymore since Ubuntu 12.04
  LTS

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1051947/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1051947] UdevDb.txt

[Hagen]

apport information

** Attachment added: UdevDb.txt
   https://bugs.launchpad.net/bugs/1051947/+attachment/3794716/+files/UdevDb.txt

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1051947

Title:
  Acer TravelMate 6293 - no s/pdif (iec958) anymore since Ubuntu 12.04
  LTS

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1051947/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1051947] UdevLog.txt

[Hagen]

apport information

** Attachment added: UdevLog.txt
   
https://bugs.launchpad.net/bugs/1051947/+attachment/3794717/+files/UdevLog.txt

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1051947

Title:
  Acer TravelMate 6293 - no s/pdif (iec958) anymore since Ubuntu 12.04
  LTS

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1051947/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs