[Bug 2062042] Re: "No valid sources.list entry found" and "An upgrade might not succeed" when running "sudo do-dist-upgrade -d" on Ubuntu 23.10

[Paul Smith]

This fixed the problem.  Thanks!  Although, I wonder if this will affect
others who try to upgrade to 24.04 when it releases tomorrow?  That's
part of the reason that I went ahead and posted the bug rather than just
waiting for the release date.

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

Title:
  "No valid sources.list entry found" and "An upgrade might not succeed"
  when running "sudo do-dist-upgrade -d" on Ubuntu 23.10

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/2062042/+subscriptions


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

[Bug 2062042] Re: "No valid sources.list entry found" and "An upgrade might not succeed" when running "sudo do-dist-upgrade -d" on Ubuntu 23.10

[Paul Smith]

No problem.  Let me know if you need anything else.

** Attachment added: "sources.list.d.tar.gz"
   
https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/2062042/+attachment/5766910/+files/sources.list.d.tar.gz

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

Title:
  "No valid sources.list entry found" and "An upgrade might not succeed"
  when running "sudo do-dist-upgrade -d" on Ubuntu 23.10

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/2062042/+subscriptions


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

[Bug 2062042] [NEW] "No valid sources.list entry found" and "An upgrade might not succeed" when running "sudo do-dist-upgrade -d" on Ubuntu 23.10

[Paul Smith]

Public bug reported:

I receive the message following message when performing a "sudo do-
release-upgrade -d" on both my Ubuntu 23.10 system(s):

Fetched 23.8 kB in 0s (0 B/s)  
Reading package lists... Done
Building dependency tree... Done 
Reading state information... Done
Fetched 0 B in 0s (0 B/s)  

Updating repository information

No valid sources.list entry found

While scanning your repository information no entry about mantic 
could be found. 

An upgrade might not succeed.

Do you want to continue anyway?

Continue [yN]

The message "An upgrade might not succeed" is of concern, so obviously I
can't proceed with the upgrade.

My sources.list.d directory looks like this:

cvpsmith@tars:/etc/apt/sources.list.d$ ls
cubic-wizard-ubuntu-release-mantic.sources  slack.list
google-chrome.sources   spotify.sources
jonaski-ubuntu-strawberry-lunar.sources teams.list
mozillateam-ubuntu-ppa-mantic.sources   ubuntu.sources
nvhpc.list

And here are the contents of "ubuntu.sources":

Types: deb
URIs: http://archive.ubuntu.com/ubuntu
Suites: mantic mantic-updates mantic-security mantic-backports
Components: main restricted universe multiverse
Signed-By: /usr/share/keyrings/ubuntu-archive-keyring.gpg

As is evident, removing "vscode.list" from sources.list.d/ has no
effect.

lsb_release -rd
No LSB modules are available.
Description:Ubuntu 23.10
Release:23.10

** Affects: ubuntu-release-upgrader (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/2062042

Title:
  "No valid sources.list entry found" and "An upgrade might not succeed"
  when running "sudo do-dist-upgrade -d" on Ubuntu 23.10

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/2062042/+subscriptions


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

[Bug 2047447] Re: No valid source.list found while upgrading from mantic to noble

[Paul Smith]

Will do, thanks!

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

Title:
  No valid source.list found while upgrading from mantic to noble

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


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

[Bug 2047447] Re: No valid source.list found while upgrading from mantic to noble

[Paul Smith]

I can confirm that I have the same issue on two separate 23.10-based
systems, but removing vscode.list from /etc/apt/sources.list.d/ has no
effect.  I get the following warning with "sudo do-release-upgrade -d":

Updating repository information

No valid sources.list entry found

While scanning your repository information no entry about mantic 
could be found. 

An upgrade might not succeed.

Do you want to continue anyway?

Obviously, I don't want to attempt the upgrade if it may bork the
system.  Any ideas on when this might see a fix?

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

Title:
  No valid source.list found while upgrading from mantic to noble

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


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

[Bug 1926634] [NEW] openjdk 1.8.0_292 fails with unrecognized algorithm name: PBEWithSHA1AndDESede

[Paul Smith]

Public bug reported:

After upgrading my Ubuntu 20.04 systems to the latest updates, which
installed openjdk-8-jdk-headless version 1.8.0_292, I'm getting
exceptions thrown in a variety of my code:

Caused by: java.security.KeyStoreException: Key protection  algorithm not 
found: java.security.UnrecoverableKeyException: Encrypt Private Key failed: 
unrecognized algorithm name: PBEWithSHA1AndDESede
at 
sun.security.pkcs12.PKCS12KeyStore.setKeyEntry(PKCS12KeyStore.java:677)
at 
sun.security.pkcs12.PKCS12KeyStore.engineSetKeyEntry(PKCS12KeyStore.java:577)
at java.security.KeyStore.setKeyEntry(KeyStore.java:1140)
... 43 more
Caused by: java.security.UnrecoverableKeyException: Encrypt Private Key failed: 
unrecognized algorithm name: PBEWithSHA1AndDESede
at 
sun.security.pkcs12.PKCS12KeyStore.encryptPrivateKey(PKCS12KeyStore.java:921)
at 
sun.security.pkcs12.PKCS12KeyStore.setKeyEntry(PKCS12KeyStore.java:614)
... 45 more
Caused by: java.security.NoSuchAlgorithmException: unrecognized algorithm name: 
PBEWithSHA1AndDESede
at sun.security.x509.AlgorithmId.get(AlgorithmId.java:448)
at 
sun.security.pkcs12.PKCS12KeyStore.mapPBEAlgorithmToOID(PKCS12KeyStore.java:938)
at 
sun.security.pkcs12.PKCS12KeyStore.encryptPrivateKey(PKCS12KeyStore.java:895)
... 46 more

This code worked fine with all previous versions.

It looks like this is a bug in this version of OpenJDK; see
https://bugs.openjdk.java.net/browse/JDK-8266261 and related bugs
reported to OpenJDK.  There are at least 3 bugs already filed against
OpenJDK about this.

Can/should we downgrade openjdk-8 from this version until upstream can
fix this bug?

Info:

$ apt-cache policy openjdk-8-jdk-headless
openjdk-8-jdk-headless:
  Installed: 8u292-b10-0ubuntu1~20.04
  Candidate: 8u292-b10-0ubuntu1~20.04
  Version table:
 *** 8u292-b10-0ubuntu1~20.04 500
500 http://archive.ubuntu.com:80/ubuntu focal-updates/universe amd64 
Packages
500 http://security.ubuntu.com/ubuntu focal-security/universe amd64 
Packages
100 /var/lib/dpkg/status
 8u252-b09-1ubuntu1 500
500 http://archive.ubuntu.com:80/ubuntu focal/universe amd64 Packages

** Affects: openjdk-8 (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/1926634

Title:
  openjdk 1.8.0_292 fails with unrecognized algorithm name:
  PBEWithSHA1AndDESede

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openjdk-8/+bug/1926634/+subscriptions

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

[Bug 1876322] Re: kazam on Focal: No audio recorded

[Paul Smith]

The kazam 1.4.5-3ubuntu0.1 fixes this bug for me. Thanks!

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

Title:
  kazam on Focal: No audio recorded

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

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

[Bug 1883980] Re: Upgrade corrupted due to "sh: 1: pager: not found"

[Paul Smith]

OK I found out that I had adwaita-icon-theme installed but not adwaita-
icon-theme-full.  After installing the latter all my Evolution icons now
exist.

I'm still not sure what other packages I might be missing...

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

Title:
  Upgrade corrupted due to "sh: 1: pager: not found"

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

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

[Bug 1883980] Re: Upgrade corrupted due to "sh: 1: pager: not found"

[Paul Smith]

Also if anyone has any ideas about how to fix my system, other than
reinstalling from scratch, I'm definitely interested...

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

Title:
  Upgrade corrupted due to "sh: 1: pager: not found"

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

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

[Bug 1883980] [NEW] Upgrade corrupted due to "sh: 1: pager: not found"

[Paul Smith]

Public bug reported:

Description:Ubuntu 20.04 LTS
Release:20.04

dpkg:
  Installed: 1.19.7ubuntu3
  Candidate: 1.19.7ubuntu3
  Version table:
 *** 1.19.7ubuntu3 500
500 http://us.archive.ubuntu.com/ubuntu focal/main amd64 Packages
100 /var/lib/dpkg/status


This past weekend I performed an upgrade of Ubuntu 18.04 LTS to Ubuntu
20.04 LTS.  I fully updated my 18.04 system and rebooted, then I ran do-
release-upgrade -d to start the upgrade.

During the upgrade process for the mime-support package it asked me
about changes to /etc/mime.types file:

Configuration file '/etc/mime.types'
 ==> Modified (by you or by a script) since installation.
 ==> Package distributor has shipped an updated version.
   What would you like to do about it ?  Your options are:
Y or I  : install the package maintainer's version
N or O  : keep your currently-installed version
  D : show the differences between the versions
  Z : start a shell to examine the situation
 The default action is to keep your current version.
*** mime.types (Y/I/N/O/D/Z) [default=N] ?

I wanted to see the difference so I typed "d" here.  Then I got this
error:

*** mime.types (Y/I/N/O/D/Z) [default=N] ? d
sh: 1: pager: not found
diff: standard output: Broken pipe
dpkg: error processing package mime-support (--configure):
 conffile difference visualizer subprocess returned error exit status 127

After this, many, MANY packages were failing because mime-support was
not configured:

dpkg: dependency problems prevent configuration of python2.7:
 python2.7 depends on mime-support; however:
  Package mime-support is not configured yet.

dpkg: error processing package python2.7 (--configure):
 dependency problems - leaving unconfigured

etc. etc.  Eventually it just bailed:

dpkg: too many errors, stopping
Errors were encountered while processing:
 mime-support
 python2.7
   ...
Processing was halted because there were too many errors.


Now my system is in a weird state where it is upgraded and mostly works but I'm 
missing a bunch of icons, I can't seem to properly select different 
"Appearance" values from the Settings dialog, etc.  I've tried to run "apt 
dist-upgrade" and "dpkg --configure -a" and neither of those has any impact: 
they both had no work to do.

I think that breaking the entire install is an overreaction to not being
able to run a pager to display a diff: dpkg should handle this error
much better and simply say that diffs are not available at this time,
but not fail the package configuration!

Of course it would be good to know why "pager" was not available at this
point in the upgrade, as well.

** Affects: dpkg (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/1883980

Title:
  Upgrade corrupted due to "sh: 1: pager: not found"

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

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

[Bug 1881381] [NEW] blender and inkscape should not be recommended packages

[Paul Smith]

Public bug reported:

Package Dependency Information:
openshot-qt
  Depends: libjs-jquery
  Depends: python3-openshot
  Depends: python3-pyqt5
  Depends: python3-pyqt5.qtsvg
  Depends: python3-pyqt5.qtwebkit
  Depends: python3-zmq
  Depends: 
python3:i386
python3
  Breaks: openshot
  Recommends: blender
  Recommends: inkscape
  Suggests: openshot-qt-doc

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: openshot-qt 2.4.1-2build2
ProcVersionSignature: Ubuntu 5.3.0-53.47~18.04.1-generic 5.3.18
Uname: Linux 5.3.0-53-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.9-0ubuntu7.15
Architecture: amd64
Date: Fri May 29 22:55:35 2020
InstallationDate: Installed on 2019-08-31 (272 days ago)
InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805)
PackageArchitecture: all
ProcEnviron:
 TERM=screen.xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: openshot-qt
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: openshot-qt (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug bionic

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

Title:
  blender and inkscape should not be recommended packages

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openshot-qt/+bug/1881381/+subscriptions

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

[Bug 1797734] Re: slow calculator startup

[Paul Smith]

Hey, if my assertion incentivizes someone to figure out how to do that,
I'm more than willing to admit I was wrong :).

The thing is, IMO "fast enough" for a desktop calculator is pretty darn
fast.  In my opinion the current integrated DEB version is already slow
enough to be frustrating, so there's plenty of work in this area without
even considering the issue of snaps.  People just don't expect to have
to wait for a calculator on their computer: isn't calculating the thing
that computers were built for and are best at?!

I'm not suggesting we should do something like waste users' memory by
preloading the calculator app just so it can be ready to display a
window quickly, though.  In reality probably not enough people use the
app often enough to justify that.

Cheers!

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

Title:
  slow calculator startup

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-calculator/+bug/1797734/+subscriptions

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

[Bug 1797734] Re: slow calculator startup

[Paul Smith]

It is not physically possible to ever get a snap to start as fast as a
native application.  The entire purpose of a snap is that it uses its
own set of dependencies, which means that by definition it cannot share
those dependencies with other applications on the system, which means
that they must be loaded separately, which will take longer, use more
system resources, etc.

snaps should be used for applications which (a) are difficult to
package, and/or (b) want to be used across multiple versions where
prerequisites might change, and/or (c) snaps downsides are not as
relevant (for example, they are left running for longer periods of time
and are large enough that they aren't expected to start quickly, to
amortize the increased start time and resource usage).

None of those criteria hold true for a desktop calculator utility.  We
need to get to the point where I can hit the calculator button on the
keyboard and a calculator window appears virtually instantaneously.
gnome-calculator was always too slow to start, but now it's far slower:
it's moving in exactly the wrong direction.  Using it as a way to
experiment with snaps just gives both snaps and gnome-calculator a bad
reputation.

This bug is not trying to say "we must improve snap startup times".

This bug is trying to say "gnome-calculator is not an appropriate
application to be snapped and should be changed back to a native
application".

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

Title:
  slow calculator startup

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-calculator/+bug/1797734/+subscriptions

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

[Bug 1797734] Re: slow calculator startup

[Paul Smith]

I'm not sure why the "is 2s too slow to start" is the question being
asked.  Who starts and stops their calculator multiple times in a row?
That's not a realistic use-case for the vast majority.

Most people need a calculator once a day or every few days, and a
desktop calculator is not an application people tend to leave running
for long periods like a browser or word processor.  They need to do a
quick bit of computation so they open the app, work in it for a few
minutes, then close it again.  Startup speed is, after correctness,
probably THE most important aspect of a utility like this.

The interesting number for gnome-calculator is the FIRST number: how
long it takes to be able to use the application from a cold start.  15s
is much closer to what I see, EVERY TIME I start gnome-calculator.

That's just... close to unusable.

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

Title:
  slow calculator startup

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-calculator/+bug/1797734/+subscriptions

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

[Bug 1754671] Re: Full-tunnel VPN DNS leakage regression

[Paul Smith]

Is this going to be fixed in disco?

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

Title:
  Full-tunnel VPN DNS leakage regression

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

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

[Bug 1778946] Re: No dns resolution after closing a vpn/pptp connection

[Paul Smith]

Although this problem is easy to fix once you know what to do, I don't
know if it should be only "Medium" importance because the impact is
massive: no DNS is available.  If you're not technically inclined enough
to know to go poking around /etc/resolv.conf if DNS breaks, you would
never be able to figure out what was wrong with your system and you
can't search the internet to find a solution...

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

Title:
  No dns resolution after closing a vpn/pptp connection

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

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

[Bug 1793427] Re: network-manager-fortisslvpn breaks mode of /run/systemd/resolv/stub-resolv.conf

[Paul Smith]

I've had this happen to me with Ubuntu 18.10 as well.

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

Title:
  network-manager-fortisslvpn breaks mode of /run/systemd/resolv/stub-
  resolv.conf

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

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

[Bug 1729028] Re: gnome-shell crashes when monitor sleeps or is turned off

[Paul Smith]

I wasn't having any problems with Ubuntu 18.04 but ever since I upgraded
to Ubuntu 18.10 gnome-shell seems to crash two out of every three times
the screensaver starts.

I used ubuntu-bug on a /var/crash file but I have no idea what happened
to it: it showed me the info in a window and I said go ahead and send
it, then it disappeared and I got no email or anything.

FYI, I have an older system with an old NVidia card, no 4k monitor
although I do use two monitors.  I use Xg not wayland.

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

Title:
  gnome-shell crashes when monitor sleeps or is turned off

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1729028/+subscriptions

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

[Bug 1812593] Re: gnome-shell[3159]: JS ERROR: Exception in callback for signal: activate: Error: Error invoking IBus.set_global_engine_async: Expected function for callback argument callback, got und

[Paul Smith]

I was seeing this same warning.  The only overlap of extensions with the
list above and my list (I only use 3 extensions) is 'system-
moni...@paradoxxx.zero.gmail.com'.

I realized I had installed that extension from source rather than
through the extensions website since it needed to be built from source
for a while due to prerequisites, and I hadn't updated it.  I
uninstalled and re-installed it from the Extensions web site.  So far I
haven't seen this warning come back.  I'll continue to check if I see it
again.

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

Title:
  gnome-shell[3159]: JS ERROR: Exception in callback for signal:
  activate: Error: Error invoking IBus.set_global_engine_async: Expected
  function for callback argument callback, got undefined

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1812593/+subscriptions

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

[Bug 1080978] Re: apport forcefully overrides sysctl kernel.core_pattern from values set in /etc/sysctl.*

[Paul Smith]

This is quite frustrating.  I wish it would be addressed... somehow...
(still getting this problem on 18.04 LTS).

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

Title:
  apport forcefully overrides sysctl kernel.core_pattern from values set
  in /etc/sysctl.*

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

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

[Bug 1730241] Re: Evolution segfaults when NVidia driver is installed but not used

[Paul Smith]

Aha, looking at issue #109 then checking journalctl I see:

Oct 09 09:34:34 homebase kernel: NVRM: API mismatch: the client has the version 
340.107, but
 NVRM: this kernel module has the version 
340.106.  Please
 NVRM: make sure that this kernel module and 
all NVIDIA driver
 NVRM: components have the same version.
Oct 09 09:34:34 homebase kernel: NVRM: nvidia_frontend_ioctl: minor 255, 
module->ioctl failed, error -22

I suspect that maybe an "apt update" ran which installed a new nvidia
driver but I haven't rebooted so the old one is still active?  I'll try
rebooting to see if that helps.

I think it would be very helpful if libcogl could be enhanced to report
some sort of error rather than just dumping core...

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

Title:
  Evolution segfaults when NVidia driver is installed but not used

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/clutter-gtk/+bug/1730241/+subscriptions

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

[Bug 1730241] Re: Evolution segfaults when NVidia driver is installed but not used

[Paul Smith]

Seems like it might be related to this:
https://gitlab.gnome.org/GNOME/cogl/issues/1 which similarly was
reported here: https://gitlab.gnome.org/GNOME/gnome-control-
center/issues/109

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

Title:
  Evolution segfaults when NVidia driver is installed but not used

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/clutter-gtk/+bug/1730241/+subscriptions

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

[Bug 1730241] Re: Evolution segfaults when NVidia driver is installed but not used

[Paul Smith]

** Attachment added: "GDB backtrace for crash in libcogl"
   
https://bugs.launchpad.net/ubuntu/+source/cogl/+bug/1730241/+attachment/5199322/+files/libcogl-crash.log

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

Title:
  Evolution segfaults when NVidia driver is installed but not used

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/clutter-gtk/+bug/1730241/+subscriptions

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

[Bug 1730241] Re: Evolution segfaults when NVidia driver is installed but not used

[Paul Smith]

I just restarted Evolution (but did not reboot my system or make any
other changes) and now Evolution is crashing for me in the identical way
described here.  I literally just quit Evolution, it was running fine,
and restarted it and now it just crashes with the same stacktrace shown
above, a null pointer passed to g_ascii_strtoull() (will add it as an
attachment) after this error:

  (evolution:14770): GLib-CRITICAL **: 19:35:04.237: g_strsplit:
assertion 'string != NULL' failed

I'm now a little afraid to restart my system in case more things start
to fail.

FYI, glxinfo shows:

$ glxinfo
name of display: :1
X Error of failed request:  BadValue (integer parameter out of range for 
operation)
  Major opcode of failed request:  154 (GLX)
  Minor opcode of failed request:  24 (X_GLXCreateNewContext)
  Value in failed request:  0x0
  Serial number of failed request:  93
  Current serial number in output stream:  94

I think if nothing else, a bug should be filed with libcogl asking them
to be more defensive in their programming here and handle badly
formatted GPU version string.  For example in my backtrace I can clearly
see that the strings being taken from the context are all null, and that
_cogl_gpu_info_parse_version_string() simply passes this to
g_ascii_strtoull() without checking.


I have Ubuntu 18.04.1 with:

ii  evolution 3.28.5-0ubuntu0.18.04.1
ii  evolution-common  3.28.5-0ubuntu0.18.04.1
ii  evolution-data-server 3.28.5-0ubuntu0.18.04.1
ii  evolution-data-server-common  3.28.5-0ubuntu0.18.04.1
ii  evolution-plugin-bogofilter   3.28.5-0ubuntu0.18.04.1
ii  evolution-plugin-pstimport3.28.5-0ubuntu0.18.04.1
ii  evolution-plugins 3.28.5-0ubuntu0.18.04.1
ii  libclutter-1.0-0:amd641.26.2+dfsg-4
ii  libclutter-1.0-0-dbgsym:amd64 1.26.2+dfsg-4
ii  libclutter-1.0-common 1.26.2+dfsg-4
ii  libclutter-gst-3.0-0:amd643.0.26-1
ii  libclutter-gtk-1.0-0:amd641.8.4-3
ii  libclutter-gtk-1.0-0-dbgsym:amd64 1.8.4-3
ii  libcogl-common1.22.2-3
ii  libcogl-pango20:amd64 1.22.2-3
ii  libcogl-path20:amd64  1.22.2-3
ii  libcogl20:amd64   1.22.2-3
ii  libcogl20-dbgsym:amd641.22.2-3
ii  libglib2.0-0:amd642.56.2-0ubuntu0.18.04.2
ii  libglib2.0-0-dbgsym:amd64 2.56.2-0ubuntu0.18.04.2
ii  libglib2.0-bin2.56.2-0ubuntu0.18.04.2
ii  libglib2.0-data   2.56.2-0ubuntu0.18.04.2
ii  libglib2.0-dev:amd64  2.56.2-0ubuntu0.18.04.2
ii  libglib2.0-dev-bin2.56.2-0ubuntu0.18.04.2

I'm running with NVidia proprietary drivers with my old crusty NVidia
GeForce 8400 GS with the proprietary driver version 340.107 that I've
been using, and has worked fine, for years.

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

Title:
  Evolution segfaults when NVidia driver is installed but not used

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/clutter-gtk/+bug/1730241/+subscriptions

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

[Bug 1793427] [NEW] network-manager-fortisslvpn breaks mode of /run/systemd/resolv/stub-resolv.conf

[Paul Smith]

Public bug reported:

(I'm not able to use ubuntu-bug as it fails with a 503 error trying to
connect to the crash server)

I'm using Ubuntu 18.04.1 on 64bit Intel with:

network-manager1.10.6-2ubuntu1
network-manager-fortisslvpn1.2.8-1build1
network-manager-fortisslvpn-gnome  1.2.8-1build1
network-manager-gnome  1.8.10-2ubuntu1

systemd237-3ubuntu10.3

When I connect then disconnect from my VPN using the network-manager-
fortisslvpn VPN interface, it will break the permissions on
/run/systemd/resolv/stub-resolv.conf such that I can't use DNS anymore
until I fix the permissions.

On my system I see:

$ ls -al /etc/resolv.conf
lrwxrwxrwx 1 root root 39 Oct 22  2017 /etc/resolv.conf -> 
../run/systemd/resolve/stub-resolv.conf

When there's no VPN connection, I see:

$ ls -al /run/systemd/resolve/
total 8
drwxr-xr-x  3 systemd-resolve systemd-resolve 100 Sep 19 23:05 ./
drwxr-xr-x 21 rootroot480 Sep 15 14:19 ../
drwx--  2 systemd-resolve systemd-resolve  60 Sep 19 23:05 netif/
-rw-r--r--  1 systemd-resolve systemd-resolve 714 Sep 19 23:05 resolv.conf
-rw-r--r--  1 systemd-resolve systemd-resolve 783 Sep 19 19:31 stub-resolv.conf

Now I start the fortisslvpn VPN:

$ ls -al /run/systemd/resolve/
total 16
drwxr-xr-x  3 systemd-resolve systemd-resolve 140 Sep 19 23:06 ./
drwxr-xr-x 21 rootroot480 Sep 15 14:19 ../
drwx--  2 systemd-resolve systemd-resolve  80 Sep 19 23:06 netif/
-rw-r--r--  1 systemd-resolve systemd-resolve 714 Sep 19 23:06 resolv.conf
-rw-r--r--  1 systemd-resolve systemd-resolve 783 Sep 19 23:06 stub-resolv.conf
-rw---  1 rootroot783 Sep 19 19:31 
stub-resolv.conf.pppd-backup.ppp0
-rw-r--r--  1 rootroot805 Sep 19 23:06 
stub-resolv.conf.tmp

Note how the stub-resolv.conf.pppd-backup-ppp0 has 0600 file
permissions.

Now I stop the fortisslvpn VPN:

$ ls -al /run/systemd/resolve/
total 12
drwxr-xr-x  3 systemd-resolve systemd-resolve 120 Sep 19 23:06 ./
drwxr-xr-x 21 rootroot480 Sep 15 14:19 ../
drwx--  2 systemd-resolve systemd-resolve  60 Sep 19 23:06 netif/
-rw-r--r--  1 systemd-resolve systemd-resolve 714 Sep 19 23:06 resolv.conf
-rw---  1 rootroot783 Sep 19 19:31 stub-resolv.conf
-rw-r--r--  1 rootroot805 Sep 19 23:06 
stub-resolv.conf.tmp

Now the stub-resolv.conf file hs 0600 permissions and my DNS is broken.

** Affects: network-manager-fortisslvpn (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/1793427

Title:
  network-manager-fortisslvpn breaks mode of /run/systemd/resolv/stub-
  resolv.conf

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

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

[Bug 1791996] [NEW] Connection failed: Failed to create file due to missing directory

[Paul Smith]

Public bug reported:

I'm using Ubuntu 18.04.1 LTS with network-manager-fortisslvpn
1.2.8-1build1 installed.

To do this I simply ran "sudo apt install network-manager-fortisslvpn-
gnome".

After setting up a VPN interface using this plugin, attempting to
connect fails immediately and using journalctl I can see this error
message:

Sep 11 14:05:06 homebase NetworkManager[900]:   [1536689106.6238]
vpn-connection[,,"VPN1",0]: VPN connection: failed to connect:
'Failed to create file “/var/lib/NetworkManager-
fortisslvpn/.config.”: No such file or directory'

After running "sudo mkdir /var/lib/NetworkManager-fortisslvpn" by hand,
then I was able to get past this error.

** Affects: network-manager-fortisslvpn (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/1791996

Title:
  Connection failed: Failed to create file due to missing directory

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

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

[Bug 1678510] Re: gprof: get empty output

[Paul Smith]

Oops, this problem still occurs with glibc 2.27, my mistake.

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

Title:
  gprof: get empty output

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gcc-5/+bug/1678510/+subscriptions

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

[Bug 1678510] Re: gprof: get empty output

[Paul Smith]

Looks like this is fixed in glibc 2.27. 
https://sourceware.org/bugzilla/show_bug.cgi?id=22284

** Bug watch added: Sourceware.org Bugzilla #22284
   https://sourceware.org/bugzilla/show_bug.cgi?id=22284

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

Title:
  gprof: get empty output

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gcc-5/+bug/1678510/+subscriptions

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

[Bug 1678510] Re: gprof: get empty output

[Paul Smith]

** Also affects: gcc-7 (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/1678510

Title:
  gprof: get empty output

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gcc-5/+bug/1678510/+subscriptions

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

[Bug 1773481] [NEW] beta build warning on Anki

[Paul Smith]

Public bug reported:

Anki prints the following warning to stdout on startup:

This is an BETA build - please do not package it up for Linux
distributions

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: anki 2.1.0+dfsg~b36-1
ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
Uname: Linux 4.15.0-20-generic x86_64
ApportVersion: 2.20.9-0ubuntu7
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Fri May 25 23:11:26 2018
EcryptfsInUse: Yes
InstallationDate: Installed on 2018-01-06 (139 days ago)
InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412)
PackageArchitecture: all
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: anki
UpgradeStatus: Upgraded to bionic on 2018-05-09 (17 days ago)

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


** Tags: amd64 apport-bug bionic

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

Title:
  beta build warning on Anki

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

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

[Bug 1754726] Re: anki could not be installed because of unmet dependencies

[Paul Smith]

Sorry it took me so long to respond.

I still see this problem in Ubuntu 17.10. The problem does not occur in
Ubuntu 18.04.

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

Title:
  anki could not be installed because of unmet dependencies

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

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

[Bug 1754726] [NEW] anki could not be installed because of unmet dependencies

[Paul Smith]

Public bug reported:

sudo apt install anki
Reading package lists... Done
Building dependency tree   
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
 anki : Depends: python3-pyqt5.qtwebengine but it is not going to be installed
Depends: python3-pyqt5.qtwebchannel but it is not going to be installed
E: Unable to correct problems, you have held broken packages.

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: anki (not installed)
ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
Uname: Linux 4.13.0-32-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
ApportVersion: 2.20.7-0ubuntu3.7
Architecture: amd64
CurrentDesktop: X-Cinnamon
Date: Fri Mar  9 12:38:44 2018
InstallationDate: Installed on 2016-03-03 (735 days ago)
InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
SourcePackage: anki
UpgradeStatus: Upgraded to artful on 2017-12-31 (67 days ago)

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


** Tags: amd64 apport-bug artful

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

Title:
  anki could not be installed because of unmet dependencies

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

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

[Bug 1726124] Re: DNS domain search paths not updated when VPN started

[Paul Smith]

I'm not sure why it's being asserted that these two uses are mutually
incompatible, especially since I've been using them in a coordinated way
forever and can still do so (at the expense of junking systemd-resolve
and going back to using dnsmasq and a custom configuration, which is
obviously a big pain).  I've even, in the past, used MULTIPLE VPNs, even
at the same time, and it still just works.

If the resolver library (e.g., gethostbyname etc.) gets an unqualified
hostname, it uses the search path just as it always has including ndots
and all that stuff, to generate FQ hostnames.  No change there.

When the local resolver caching service (dnsmasq, systemd-resolv) gets a
FQ hostname it looks through the extensions provided by the VPN DHCP
information and if the hostname matches that extension it forwards the
lookup to the DNS server for that VPN.  If it doesn't match, it doesn't
forward the request.  If it doesn't match any of the VPN search paths,
it forwards the request to the default DNS servers.

I honestly don't understand why we're considering these uses
incompatible.  They seem to me to be exactly compatible and exactly what
you want to do, at least the vast majority of the time.

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

Title:
  DNS domain search paths not updated when VPN started

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

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

[Bug 1726124] Re: DNS domain search paths not updated when VPN started

[Paul Smith]

Andreas: unfortunately disallowing short name lookups is not acceptable:
many environments use short names in embedded URLs all over the place,
and without domain search paths the entire environment is rendered
completely unusable (e.g., URLs are simply https://tools/foo or
https://wiki/foo or whatever; this means no cross-links work).

Connecting to an untrusted VPN is a tiny sliver of a minority of the
usage of VPN; 99.99% of the time when someone connects to a VPN they're
trying to create a secure link to another trusted network (e.g., working
remotely).

If you want to provide support for both modes of handling short names
with some kind of checkbox to select between them that's fine with me,
but the current behavior is a serious loss of functionality from
previous solutions.

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

Title:
  DNS domain search paths not updated when VPN started

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

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

[Bug 1726124] Re: DNS domain search paths not updated when VPN started

[Paul Smith]

Hi Sebastien, thanks for your interest.  This issue is causing me
extreme pain.  I believe I'm going to have to reconfigure N-M to use the
old-style dnsmasq setup and throw out systemd-resolve pretty soon.

It's not clear to me whether this is an N-M bug vs. a systemd bug, but
I'm happy to file more bugs.  Did you want me to file a bug with N-M?

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

Title:
  DNS domain search paths not updated when VPN started

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

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

[Bug 1728450] [NEW] Details are not visible by default and hide important configuration

[Paul Smith]

Public bug reported:

When I open the gnome-control-center, I see the following menu items
down the left side: Wi-Fi, Bluetooth, Background, Notifications, Search,
Region & Language, Universal Access, Online Accounts, Privacy, Sharing,
Sound, Power, Network, Devices (with a sub-menu).  Screenshot attached.

If I happen to move my mouse into the menu area I _may_ notice a very
thin "scroll area" show up briefly before it disappears again, or I
_may_ notice very subtle dotted lines at the bottom of the menu, and I
_may_ notice that there is actually another menu item at the bottom that
I have to scroll down to see: Details.

And if I happen to find that and click on that sub-menu, I will find
critically important items in there such as Date & Time configuration
(what I was looking for to get an AM/PM clock, and couldn't find at
all), Users configuration (couldn't find that either so had to add users
by hand from the CLI), and Default Applications (also important so I can
change the default mail client etc.)

What does "Details" even mean?  This menu might as well be named
"Miscellaneous".  Really that would be MORE helpful: at least it would
be clear that there's a bunch of random stuff below that menu, which is
the reality.  The only thing in "Details" that feels appropriate to the
name is the "About" menu.

I really like the format change of gnome-control-center from the "rows
of icons" to the left-side menu: it looks nice and avoiding the "go back
and select something else" by just clicking along the left side is a
very pleasant experience.  But the menu organization here is really
confusing and hard to use, and needs serious attention.

There needs to be enough top-level menus to be sure everything fits on
the screen without scrolling.

The About menu item should be on the top-level menu at the bottom of the
list... people think it's not important but it's actually REALLY
important, so inexperienced people can easily obtain critical system
details when asking for help.

And the grouping of these menus needs love: for example, why is "Wi-Fi"
a separate menu item from "Network"?  I would think that Wi-Fi, Network,
Online Accounts and Sharing could all be combined into one sub-menu like
"Internet" or similar.  Actually I don't have a Wi-Fi adapter in my
system so I don't know what shows up there: maybe "Wi-Fi" is more about
the hardware, and belongs under "Devices"?  Either way.

Also I think "Region & Language", "Universal Access", and possibly "Date
& Time" could be grouped together.

And "Background", "Privacy", and "Notifications" could be grouped under
some sort of "desktop" menu.  Or maybe "Region & Language" would stay a
top-level item and "Universal Access" and "Date & Time" would be added
to "Desktop".

Anyway.  I realize there are lots of ways to chop these items up and
people will have disagreements, but the current situation is really very
not good: the control center needs to avoid the need for scrolling to
see all the options and if things are moved into sub-menus the names of
those menus HAVE to be evocative and clear.

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: gnome-control-center 1:3.26.1-0ubuntu4
ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
Uname: Linux 4.13.0-16-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia
ApportVersion: 2.20.7-0ubuntu3.1
Architecture: amd64
CurrentDesktop: GNOME
Date: Sun Oct 29 15:18:20 2017
InstallationDate: Installed on 2017-10-21 (8 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
SourcePackage: gnome-control-center
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: gnome-control-center (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug artful

** Attachment added: "control center screenshot"
   
https://bugs.launchpad.net/bugs/1728450/+attachment/4999656/+files/Screenshot%20from%202017-10-29%2015-44-45.png

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

Title:
  Details are not visible by default and hide important configuration

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1728450/+subscriptions

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

[Bug 1726124] Re: DNS domain search paths not updated when VPN started

[Paul Smith]

I'm not sure I understand what you mean.  In a typical configuration you
never send "foo" to the nameservice, there's always a search domain and
those lookups are always tried first (because the default value for the
ndots is 1).  This is handled by the libc resolver linked into every
program, it's not handled by a central service.

I don't have any idea how systemd-resolve works.  But, my understanding
of how it used to work with dnsmasq using split tunneling was that the
nameservice mapped domains to DNS servers, and the resolver would only
forward requests to the DNS server that matched the domain for the host
being requested.

If you have a VPN interface that adds "mycorp.com" to the search domain
that appears in /etc/resolv.conf search, so it contains "mycorp.com
localdomain" for example.  Then when someone tries to resolve "myhost",
the libc resolver sees that there are no dots here and so it starts
appending search paths to the hostname, in order, and sending them to
the DNS service to look up.  So first it will send "myhost.mycorp.com"
to the resolver.  The resolver sees that the hostname ends in
"mycorp.com" and it knows that the VPN DNS servers "own" that domain, so
it forwards that request to those servers for lookup.

If that doesn't match, then the libc resolver will try to look up
"myhost.localdomain".  That does NOT match the VPN domain, so it will
not try to forward that to the DNS servers for the VPN connection and
instead use a different resolver.

I don't think there's any information leakage here.

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

Title:
  DNS domain search paths not updated when VPN started

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

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

[Bug 1726143] [NEW] Automatic installation of samba fails with "could not find package libpam-smbpass"

[Paul Smith]

Public bug reported:

I actually have no idea if this is really a Nautilus issue but didn't
know where else to file it.

I have a fresh install of ubuntu 17.10.  I start nautilus (using File).
I right-click on a folder and select "Local Network Share".  When I
select "Share this folder" it says the sharing service is not installed,
so I select "Install Service" and it offers to install samba for me.

I click "install" and it proceeds, then throws up an error dialog:

Could not find package 'libpam-smbpass'

I can see that Samba packages are already installed at this point.

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: nautilus 1:3.26.0-0ubuntu1
ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
Uname: Linux 4.13.0-16-generic x86_64
ApportVersion: 2.20.7-0ubuntu3
Architecture: amd64
CurrentDesktop: GNOME
Date: Sun Oct 22 15:43:28 2017
InstallationDate: Installed on 2017-10-21 (1 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
SourcePackage: nautilus
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug artful

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

Title:
  Automatic installation of samba fails with "could not find package
  libpam-smbpass"

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

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

[Bug 1726124] Re: DNS domain search paths not updated when VPN started

[Paul Smith]

To be clear, they are NOT updated in /etc/resolv.conf.  They ARE updated
in /run/NetworkManager/resolv.conf, but that has no effect since we're
not using that for resolution: instead we're using systemd-resolve.

And as I noted above, it does appear that systemd-resolve is notified
about the search domains, because "systemd-resolve --status" does show
them associated with the openvpn tun0 device.

However, those search domains are never manifested in the
/run/systemd/resolve/stub-resolv.conf which is what /etc/resolv.conf is
pointing to, so they never take effect.

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

Title:
  DNS domain search paths not updated when VPN started

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

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

[Bug 1726124] [NEW] DNS domain search paths not updated when VPN started

[Paul Smith]

Public bug reported:

I connect to work with openvpn through network-manager-openvpn.  I'm
selecting automatic (DHCP) to get an IP address, and "Use this
connection only for resources on its network" to support split
tunneling.

In the last few versions of Ubuntu I used, this all worked fine.  In
Ubuntu 17.10 (fresh install, not upgrade) I can access hosts on both my
VPN network and the internet, BUT I have to use FQDN for my VPN network
hosts: the updates to the DNS search path provided by my VPN DHCP server
are never being applied.

Investigating the system I see that /etc/resolv.conf is pointing to
/run/systemd/resolve/stub-resolv.conf and that resolv.conf does not have
any of the VPN's search path settings in it:

  # This file is managed by man:systemd-resolved(8). Do not edit.
  #
  # 127.0.0.53 is the systemd-resolved stub resolver.
  # run "systemd-resolve --status" to see details about the actual nameservers.
  nameserver 127.0.0.53

  search home

In previous versions of Ubuntu, where NetworkManager controlled the
resolver not systemd, /etc/resolv.conf pointed to
/run/NetworkManager/resolv.conf and there was a local dnsmasq instance
that managed all the complexity.  In Ubuntu 17.10 when I look in
/run/NetworkManager/resolv.conf file, I see that the search paths ARE
properly updated there:

  $ cat /run/NetworkManager/resolv.conf 
  # Generated by NetworkManager
  search internal.mycorp.com other.mycorp.com home
  nameserver 127.0.1.1

However this file isn't being used, and also there's no dnsmasq running
on the system so if I switch my /etc/resolv.conf to point to this file
instead, then all lookups fail.

Strangely, if I look at the systemd-resolv status I see that in theory
systemd-resolve does seem to know about the proper search paths:

  $ systemd-resolve --status
 ...
  Link 3 (tun0)
Current Scopes: DNS LLMNR/IPv4 LLMNR/IPv6
 LLMNR setting: yes
  MulticastDNS setting: no
DNSSEC setting: no
  DNSSEC supported: no
   DNS Servers: 10.3.0.10
10.8.42.2
DNS Domain: ~internal.mycorp.com
~other.mycorp.com

but for whatever reason the search domains are not getting put into the
resolv.conf file:

  $ host mydesk
  ;; connection timed out; no servers could be reached

  $ host mydesk.internal.mycorp.com
  mydesk.internal.mycorp.com has address 10.8.37.74

(BTW, the timeout in the failed attempt above takes 10s: it is SUPER
frustrating when all your host lookups are taking that long just to
fail).

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: systemd 234-2ubuntu12
ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
Uname: Linux 4.13.0-16-generic x86_64
ApportVersion: 2.20.7-0ubuntu3
Architecture: amd64
CurrentDesktop: GNOME
Date: Sun Oct 22 15:08:57 2017
InstallationDate: Installed on 2017-10-21 (1 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
MachineType: System manufacturer System Product Name
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-16-generic 
root=UUID=4384306c-5fed-4b48-97a6-a6d594c4f72b ro quiet splash vt.handoff=7
SourcePackage: systemd
SystemdDelta:
 [EXTENDED]   /lib/systemd/system/rc-local.service → 
/lib/systemd/system/rc-local.service.d/debian.conf
 [EXTENDED]   /lib/systemd/system/user@.service → 
/lib/systemd/system/user@.service.d/timeout.conf
 
 2 overridden configuration files found.
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 12/02/2014
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 2101
dmi.board.asset.tag: To Be Filled By O.E.M.
dmi.board.name: M5A78L-M/USB3
dmi.board.vendor: ASUSTeK Computer INC.
dmi.board.version: Rev X.0x
dmi.chassis.asset.tag: Asset-1234567890
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.version: Chassis Version
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2101:bd12/02/2014:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM5A78L-M/USB3:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
dmi.product.family: To Be Filled By O.E.M.
dmi.product.name: System Product Name
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer

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


** Tags: amd64 apport-bug artful

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

Title:
  DNS domain search paths not updated when VPN started

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

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

[Bug 1639776] Re: name resolution (dnsmasq) fails to send queries out after suspend/resume reconnects the interface

[Paul Smith]

Yes, that version is OK (I'm on 16.10 so mine is a bit newer).  If you
check /usr/share/doc/dnsmasq-base/changelog.Debian.gz on your system you
should see info related to this bug in that changelog.

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

Title:
  name resolution (dnsmasq) fails to send queries out after
  suspend/resume reconnects the interface

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

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

[Bug 1639776] Re: name resolution (dnsmasq) fails to send queries out after suspend/resume reconnects the interface

[Paul Smith]

Shawn B it sounds like your issue might be related to this one, since
it's fixed by restarting dnsmasq.  Do you have the newer dnsmasq version
(you need dnsmasq-base 2.76-4ubuntu0.1 or better)?

Just to note: it's definitely true that this bug will impact VPN users;
that's how I ran into it.  Basically, anything that causes changes to
DNS configuration will hit this: so starting / stopping VPN and also
suspend / resume.

However, if your problem is solved by switching versions of
NetworkManager then it's not this bug.  Also if the problem is NOT
solved by restarting dnsmasq then it's not this bug.

In general, the above version of dnsmasq definitely fixes _this_ bug, so
if you have that version and you're still seeing problems then it's not
_this_ bug.  You should file a new issue in Launchpad, with all the
details you can obtain.

Feel free to add a comment here with a link to the bug you create so
people can follow it if they come here first.

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

Title:
  name resolution (dnsmasq) fails to send queries out after
  suspend/resume reconnects the interface

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

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

[Bug 1639776] Re: name resolution (dnsmasq) fails to send queries out after suspend/resume reconnects the interface

[Paul Smith]

It sounds like a different bug to me, if changing networkmanager fixes
it without changing dnsmasq.  I would file a new Launchpad bug with all
the details you can provide.  You can add a comment to this issue with a
link.

In particular, please specify:
* If you're using IPv4 vs. IPv6
* If you have checked or unchecked the "Use this connection only for resources 
on its network"
* If you have this checked, try unchecking it and see if that makes a difference
* When you say "DNS lookups" please be clear about whether the hostnames being 
looked up are public (e.g., www.google.com or whatever), on your local LAN, or 
in the network accessed via the VPN.  Does it make a difference which one you 
choose?
* Are you using fully-qualified hostnames, or relying on the DNS domain search 
path?  Does it make a difference if you do it differently?

FYI, if you choose "Use this connection only for resources on its
network" then different DNS lookups going to different servers is
expected: the decision is made based on the DNS domain name; lookups for
hosts with domains that are served via the VPN (as determined by
information obtained from the DHCP response when you got an IP address
over the VPN) will be sent to DNS servers in the VPN (again, based on
DHCP).  Lookups for hosts with domains that are not registered by the
VPN will not be sent to the VPN's DNS server.

I assume (but have not tried) that if you don't check that box then all
DNS lookups would go to the VPN DNS servers.  However, this does mean
that no local LAN hostnames can be resolved since your local DNS server
will not be consulted.  It also means if you have multiple VPN
connections going, only one of them will have DNS available.

If you either use fully-qualified hostnames, and/or you ensure that the
VPN's DNS domains come first in the search path, then I don't think
there should be a security issue (unless you don't trust your normal DNS
server, but that's an entirely different situation).

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

Title:
  name resolution (dnsmasq) fails to send queries out after
  suspend/resume reconnects the interface

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

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

[Bug 1639776] Re: name resolution (dnsmasq) fails to send queries out after suspend/resume reconnects the interface

[Paul Smith]

I think the problems being reported by NJ and Lukas at least, are
different issues and you should file a new report about them.  I can't
say about GammaPoint because the description there ("DNS leaks") is not
understandable to me.

This issue has the following characteristics: DNS lookups fail, often
with an error of REFUSED.  Restarting dnsmasq and/or "pkill -HUP
NetworkManager" fixes the problem.

If your issue doesn't meet those characteristics (particularly if it
isn't fixed by restarting dnsmasq or sending SIGHUP to NetworkManager to
restart it) then it's probably not this bug and you should open a new
bug.

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

Title:
  name resolution (dnsmasq) fails to send queries out after
  suspend/resume reconnects the interface

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

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

[Bug 1639776] Re: name resolution (dnsmasq) fails to send queries out after suspend/resume reconnects the interface

[Paul Smith]

Just curious if there's more work needed here before this fix moves out
of proposed and into standard updates for xenial / yakkety, or if not
then is there a timeline when that transition is normally expected?

I'm currently recommending to users that they reset NetworkManager by
hand when they have a DNS error: once this package makes it into the
normal update queue then I can just tell them to update their systems.

Thanks!

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

Title:
  name resolution (dnsmasq) fails to send queries out after
  suspend/resume reconnects the interface

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

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

[Bug 1639776] Re: dnsmasq fails to send queries out after suspend disconnects the interface

[Paul Smith]

Just to add a note: this issue also occurs when using VPNs: I use
NetworkManager OpenVPN and when I start up the connection I can't
resolve DNS hosts from the VPN DNS server until I run "sudo killall -HUP
NetworkManager" or similar.  This has to be done every time the VPN goes
down / comes back up.

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

Title:
  dnsmasq fails to send queries out after suspend disconnects the
  interface

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

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

[Bug 1676597] [NEW] dnsmasq doesn't manage destruction/recreation of tun interface

[Paul Smith]

Public bug reported:

This issue happens in Ubuntu 16.04 LTS as well.

When I connect via tun to an OpenVPN server, my DNS lookups do not
succeed even though the OpenVPN service is started correctly and does
provide the correct information.  If I force NetworkManager to load its
configuration via "killall -HUP NetworkManager" then it works.


  $ host git.my.domain.com
  Host git.my.domain.com not found: 5(REFUSED)

  $ sudo killall -HUP NetworkManager

  $ host git
  git.my.domain.com has address 192.168.1.7

Looking around I see that this appears to be an instance of this bug, in
dnsmasq:

https://bugzilla.redhat.com/show_bug.cgi?id=1367772

There are TWO patches (already applied to the dnsmasq source and queued
for the next release, which is not out yet) needed to fix this problem,
both mentioned in the above bug:

http://thekelleys.org.uk/gitweb/?p=dnsmasq.git;a=commitdiff;h=2675f2061525bc954be14988d64384b74aa7bf8b
http://thekelleys.org.uk/gitweb/?p=dnsmasq.git;a=commitdiff;h=16800ea072dd0cdf14d951c4bb8d2808b3dfe53d

ProblemType: Bug
DistroRelease: Ubuntu 16.10
Package: dnsmasq-base 2.76-4
ProcVersionSignature: Ubuntu 4.8.0-41.44-generic 4.8.17
Uname: Linux 4.8.0-41-generic x86_64
ApportVersion: 2.20.3-0ubuntu8.2
Architecture: amd64
CurrentDesktop: GNOME
Date: Mon Mar 27 16:00:03 2017
InstallationDate: Installed on 2014-04-28 (1064 days ago)
InstallationMedia: Ubuntu-GNOME 14.04 LTS "Trusty Tahr" - Release amd64 
(20140416.2)
SourcePackage: dnsmasq
UpgradeStatus: Upgraded to yakkety on 2017-03-25 (1 days ago)

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


** Tags: amd64 apport-bug yakkety

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

Title:
  dnsmasq doesn't manage destruction/recreation of tun interface

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

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

[Bug 1658921] Re: NetworkManager does not manage wired connection

[Paul Smith]

Just want to point out that "chroot installs" or netboot installs are
NOT the only places this breaks.  I did a a straightforward upgrade (via
do-release-upgrade) from Ubuntu GNOME 16.04.n (latest packages
installed) to Ubuntu GNOME 16.10, on a standard desktop system where the
wired network was managed by NM before.

After the upgrade, no wired interface was available.

Luckily my desktop also has a wireless interface (which I never used
before); that still worked so I could continue to search for help: it
took two days on and off but I finally found this bug (I was searching
NetworkManager documentation and looking through nmcli output,
journalctl output, etc. but there is nothing shown anywhere about this;
most likely NM should be modified so that it prints something useful to
the logs if it skips interfaces due to the unmanaged-devices setting).

The solution above (replacing with an empty file) then running "sudo
killall -HUP NetworkManager" caused my wired connection to immediately
reappear and connect.

In any event, this change is kind of a disaster; regardless of the
intentions behind it the results are far too disruptive and the reasons
for the problem and the solution are far too obscure and difficult for
the average desktop user to be expected to figure out.

This change should be reverted until some alternative solution that is
more carefully targeted to only impact the correct set of systems can be
devised and implemented.

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

Title:
  NetworkManager does not manage wired connection

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

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

[Bug 1568277] Re: nemo crashed with SIGSEGV in g_closure_invoke() when opening new tab

[Paul Smith]

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

In order to recreate this bug I had to do the following:
1. Open nemo
2. Navigate away from the default location, for example to $HOME/Pictures
3. Open a new tab
4. Close the new tab
5. Open a new tab again

I noticed some directories seem to never cause this problem if the
directory name is short. For example $HOME/help  does not cause the
crash.

Just wondering, how are we supposed to comment on this bug if we aren't
supposed to comment here but we cannot see the private bug to comment on
that?

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

Title:
  nemo crashed with SIGSEGV in g_closure_invoke() when opening new tab

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

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

[Bug 1603692] Re: java-update-alternatives doesn't recognize jdkhl label

[Paul Smith]

Note that there's a more comprehensive patch already available in the
linked Debian bug report (see the remote bug watches box to the right).

My hope would be someone would go even further and update the script to
show some kind of warning, at least, if unknown tags are seen so that
future updates to the set of tags are not silently ignored (I can do
that myself if someone is interested).

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

Title:
  java-update-alternatives doesn't recognize jdkhl label

To manage notifications about this bug go to:
https://bugs.launchpad.net/java-common/+bug/1603692/+subscriptions

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

[Bug 1603692] [NEW] java-update-alternatives doesn't recognize jdkhl label

[Paul Smith]

Public bug reported:

java-common  0.56ubuntu2
openjdk-8-jre-headless:amd64 8u91-b14-0ubuntu4~16.04.1

Newer versions of openjdk-8-jre-headless provide a .jinfo file that uses
a new tag "jdkhl" (for JDK headless).  Since update-java-alternatives
doesn't know anything about that tag, it ignores all those entries and
leaves them set to Java 7.

I spend about 45 massively frustrating minutes trying to figure out what
was going on before I realized that my javac was actually still Java 7
not Java 8 :(.

In addition to recognizing the new tag, I think that java-update-
alternatives should be modified to at least generate warning messages
for any tags that it doesn't recognize rather than failing silently and
leaving one believing that one's Java version has been changed
appropriately when it hasn't.

** Affects: java-common
 Importance: Unknown
 Status: Unknown

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

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

** Also affects: java-common via
   http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=825987
   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/1603692

Title:
  java-update-alternatives doesn't recognize jdkhl label

To manage notifications about this bug go to:
https://bugs.launchpad.net/java-common/+bug/1603692/+subscriptions

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

[Bug 1593261] Re: Using "splash" Linux boot option causes IPMI console view to blank

[Paul Smith]

** Tags added: kernel-fixed-upstream

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

Title:
  Using "splash" Linux boot option causes IPMI console view to blank

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

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

[Bug 1593261] Re: Using "splash" Linux boot option causes IPMI console view to blank

[Paul Smith]

** 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/1593261

Title:
  Using "splash" Linux boot option causes IPMI console view to blank

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

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

[Bug 1593261] Re: Using "splash" Linux boot option causes IPMI console view to blank

[Paul Smith]

I've tested with 4.7-rc3.  I first booted with this kernel without the
"splash" to make sure it booted, then I added back the "splash" and re-
ran update-grub, and booted that.  That also worked.  I verified by
examining dmesg that the vt.handoff=7 WAS present on the kernel command
line when it worked.

So it appears this issue is resolved in this newest kernel.

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

Title:
  Using "splash" Linux boot option causes IPMI console view to blank

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

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

[Bug 1593261] Re: Using "splash" Linux boot option causes IPMI console view to blank

[Paul Smith]

This is a blade server install and getting enough packages installed to
run apport-collect is difficult.  I've attached the results of running
dmesg when I see the error (dmesg-bad.out) and when I don't see the
error (dmesg-good.out).

While doing this I discovered the REAL cause of the problem, it's not
the splash setting, at least not directly.

The real problem is the "vt.handoff=7" option which gets added to the
kernel command line.  This is only added if splash is part of the
settings (at least insofar as my experiments go).  When that value is
present, then the IPMI console viewer breaks.  If I leave splash in the
command line but edit the grub.cfg file directly to remove the
vt.handoff=7 setting then reboot, the IPMI console viewer works again.

** Attachment added: "dmesg output for "bad" boot"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1593261/+attachment/4685027/+files/dmesg-bad.out

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

Title:
  Using "splash" Linux boot option causes IPMI console view to blank

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

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

[Bug 1593261] Re: Using "splash" Linux boot option causes IPMI console view to blank

[Paul Smith]

** Attachment added: "dmesg output for "good" boot"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1593261/+attachment/4685028/+files/dmesg-good.out

** 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/1593261

Title:
  Using "splash" Linux boot option causes IPMI console view to blank

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

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

[Bug 1593261] [NEW] Using "splash" Linux boot option causes IPMI console view to blank

[Paul Smith]

Public bug reported:

I'm using a set of blade servers with SuperMicro BIOS and IPMI console
viewing capabilities.  I use the Ubuntu netboot options with a PXE
server to install.

I've installed Ubuntu 12.04 and 14.04 on these systems, and everything
works great.

However, when I install Ubuntu 16.04 (and this is true both if I upgrade
from Ubuntu 14.04 with do-release-upgrade AND when I install a fresh
copy directly via the Ubuntu 16.04 netboot image via PXE), then the
install works but when I reboot the IPMI console is completely blank: no
cursor, no text, no typing shows anything.

I can still SSH to the system (except of course the default netboot
install doesn't include sshd for some bizarre reason so I had to play
some tricks and rerun the install multiple times :-/).

After a lot of experimentation I discovered that if I edit the
/etc/default/grub file and remove the "splash" setting from
GRUB_CMDLINE_LINUX_DEFAULT variable and re-run update-grub, then things
worked fine and I was able to boot properly without losing access to the
IPMI console.

One more note: this is definitely a kernel issue because when I choose
the older 14.04 kernel (3.13 or similar) from the boot menu on the
system I upgraded from 14.04 to 16.04, with the "splash" setting still
in the grub config and no other changes (so userspace is still all
16.04), I had no problems with the IPMI console viewer.

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

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

Title:
  Using "splash" Linux boot option causes IPMI console view to blank

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

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

[Bug 1526042] Re: WARNING Couldn't connect to accessibility bus Failed to connect to socket /tmp/dbus* starting sound-juicer

[Paul Smith]

Looks the same as this bug: https://bugzilla.redhat.com/show_bug.cgi?id=1056820
I tried the suggested workaround of adding "export NO_AT_BRIDGE=1"   to .bashrc 
and that made the warning message go away. 

It looks like the version of ibus that red hat switched to might have
some bug fixes over the Ubuntu one based on the version number shown in
that bug report where it was reported as fixed, just guessing though.


** Bug watch added: Red Hat Bugzilla #1056820
   https://bugzilla.redhat.com/show_bug.cgi?id=1056820

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

Title:
  WARNING Couldn't connect to accessibility bus Failed to connect to
  socket /tmp/dbus* starting sound-juicer

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/sound-juicer/+bug/1526042/+subscriptions

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

[Bug 1526042] Re: WARNING Couldn't connect to accessibility bus Failed to connect to socket /tmp/dbus* starting sound-juicer

[Paul Smith]

I see this error when starting gedit or nemo from the command line.

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

Title:
  WARNING Couldn't connect to accessibility bus Failed to connect to
  socket /tmp/dbus* starting sound-juicer

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/sound-juicer/+bug/1526042/+subscriptions

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

[Bug 1479715] Re: Crash due to fd leak when playing sounds in pidgin

[Paul Smith]

A fix for this has been sitting in wily-proposed for about 3 weeks now.
I have no idea what it takes to get through that into a regular update.
It's been handled as Bug #1529445 so look there for more details.  Maybe
someone knows how to move it forward through the process?

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

Title:
  Crash due to fd leak when playing sounds in pidgin

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

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

[Bug 1528313] [NEW] Pidgin crashing somewhat regularly in 15.10

[Paul Smith]

Public bug reported:

I've been using Pidgin since forever and it's been very stable, but ever
since I've updated to 15.10 I'm getting semi-regular (once or twice a
week) crashes.

Ubuntu GNOME 15.10
Pidgin 1:2.10.11-0ubuntu4

Here's a stack trace from my latest crash a few minutes ago, after I
installed the pidgin-dbg package:

$ gdb -c core.pidgin.3643.1450721666 /usr/bin/pidgin
GNU gdb (Ubuntu 7.10-1ubuntu2) 7.10
Copyright (C) 2015 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later 
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "x86_64-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
.
Find the GDB manual and other documentation resources online at:
.
For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from /usr/bin/pidgin...Reading symbols from 
/usr/lib/debug//usr/bin/pidgin...done.
done.
[New LWP 3643]
[New LWP 3707]
[New LWP 3706]
[New LWP 3651]
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
Core was generated by `pidgin'.
Program terminated with signal SIGSEGV, Segmentation fault.
#0  g_source_attach (source=0x0, context=0x0) at 
/build/glib2.0-MuyBSS/glib2.0-2.46.2/./glib/gmain.c:1163
1163/build/glib2.0-MuyBSS/glib2.0-2.46.2/./glib/gmain.c: No such file or 
directory.
[Current thread is 1 (Thread 0x7fda0a301a80 (LWP 3643))]
(gdb) thr a a bt

Thread 4 (Thread 0x7fd9f33a2700 (LWP 3651)):
#0  0x7fda06d99743 in select () at ../sysdeps/unix/syscall-template.S:81
#1  0x7fd9f3a5a530 in  () at /usr/lib/x86_64-linux-gnu/libtcl8.6.so
#2  0x7fda0706d6aa in start_thread (arg=0x7fd9f33a2700) at 
pthread_create.c:333
#3  0x7fda06da2eed in clone () at 
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 3 (Thread 0x7fd9ee9dd700 (LWP 3706)):
#0  0x7fda06d978dd in poll () at ../sysdeps/unix/syscall-template.S:81
#1  0x7fda079111ec in g_main_context_iterate (priority=2147483647, n_fds=2, 
fds=0x7fd9e80008e0, timeout=, context=0x561e1a8cf110) at 
/build/glib2.0-MuyBSS/glib2.0-2.46.2/./glib/gmain.c:4135
#2  0x7fda079111ec in g_main_context_iterate 
(context=context@entry=0x561e1a8cf110, block=block@entry=1, 
dispatch=dispatch@entry=1, self=) at 
/build/glib2.0-MuyBSS/glib2.0-2.46.2/./glib/gmain.c:3835
#3  0x7fda079112fc in g_main_context_iteration (context=0x561e1a8cf110, 
may_block=may_block@entry=1) at 
/build/glib2.0-MuyBSS/glib2.0-2.46.2/./glib/gmain.c:3901
#4  0x7fda07911339 in glib_worker_main (data=) at 
/build/glib2.0-MuyBSS/glib2.0-2.46.2/./glib/gmain.c:5672
#5  0x7fda07937965 in g_thread_proxy (data=0x561e1a82e9e0) at 
/build/glib2.0-MuyBSS/glib2.0-2.46.2/./glib/gthread.c:778
#6  0x7fda0706d6aa in start_thread (arg=0x7fd9ee9dd700) at 
pthread_create.c:333
#7  0x7fda06da2eed in clone () at 
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 2 (Thread 0x7fd9ee1dc700 (LWP 3707)):
#0  0x7fda06d978dd in poll () at ../sysdeps/unix/syscall-template.S:81
#1  0x7fda079111ec in g_main_context_iterate (priority=2147483647, n_fds=3, 
fds=0x7fd9e00010c0, timeout=, context=0x561e1a8cb710) at 
/build/glib2.0-MuyBSS/glib2.0-2.46.2/./glib/gmain.c:4135
#2  0x7fda079111ec in g_main_context_iterate (context=0x561e1a8cb710, 
block=block@entry=1, dispatch=dispatch@entry=1, self=) at 
/build/glib2.0-MuyBSS/glib2.0-2.46.2/./glib/gmain.c:3835
#3  0x7fda07911572 in g_main_loop_run (loop=0x561e1a8cfa00) at 
/build/glib2.0-MuyBSS/glib2.0-2.46.2/./glib/gmain.c:4034
#4  0x7fda057944a6 in gdbus_shared_thread_func (user_data=0x561e1a8cfa40) 
at /build/glib2.0-MuyBSS/glib2.0-2.46.2/./gio/gdbusprivate.c:246
#5  0x7fda07937965 in g_thread_proxy (data=0x561e1a82ea30) at 
/build/glib2.0-MuyBSS/glib2.0-2.46.2/./glib/gthread.c:778
#6  0x7fda0706d6aa in start_thread (arg=0x7fd9ee1dc700) at 
pthread_create.c:333
#7  0x7fda06da2eed in clone () at 
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 1 (Thread 0x7fda0a301a80 (LWP 3643)):
#0  0x7fda0790eb24 in g_source_attach (source=0x0, context=0x0) at 
/build/glib2.0-MuyBSS/glib2.0-2.46.2/./glib/gmain.c:1163
#1  0x7fda09c798b8 in  () at /usr/lib/x86_64-linux-gnu/libgstreamer-1.0.so.0
#2  0x7fda09c799e0 in gst_bus_add_watch_full () at 
/usr/lib/x86_64-linux-gnu/libgstreamer-1.0.so.0
#3  0x561e1a014b3a in pidgin_sound_play_file (filename=) at 
/build/pidgin-hiYwOJ/pidgin-2.10.11/./pidgin/gtksound.c:543
#4  0x561e1a014927 in pidgin_sound_play_event 
(event=PURPLE_SOUND_BUDDY_ARRIVE) at 
/build/pidgin-hiYwOJ/pidgin-2.10.11/./pidgin/gtksound.c:616
#5  0x7fda0761b9f2 in purple_signal_emit_vargs (instance=, 

[Bug 1528313] Re: Pidgin crashing somewhat regularly in 15.10

[Paul Smith]

** Description changed:

  I've been using Pidgin since forever and it's been very stable, but ever
  since I've updated to 15.10 I'm getting semi-regular (once or twice a
  week) crashes.
  
  Ubuntu GNOME 15.10
  Pidgin 1:2.10.11-0ubuntu4
  
  Here's a stack trace from my latest crash a few minutes ago, after I
  installed the pidgin-dbg package:
  
  $ gdb -c core.pidgin.3643.1450721666 /usr/bin/pidgin
  GNU gdb (Ubuntu 7.10-1ubuntu2) 7.10
  Copyright (C) 2015 Free Software Foundation, Inc.
  License GPLv3+: GNU GPL version 3 or later 
  This is free software: you are free to change and redistribute it.
  There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
  and "show warranty" for details.
  This GDB was configured as "x86_64-linux-gnu".
  Type "show configuration" for configuration details.
  For bug reporting instructions, please see:
  .
  Find the GDB manual and other documentation resources online at:
  .
  For help, type "help".
  Type "apropos word" to search for commands related to "word"...
  Reading symbols from /usr/bin/pidgin...Reading symbols from 
/usr/lib/debug//usr/bin/pidgin...done.
  done.
  [New LWP 3643]
  [New LWP 3707]
  [New LWP 3706]
  [New LWP 3651]
  [Thread debugging using libthread_db enabled]
  Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
  Core was generated by `pidgin'.
  Program terminated with signal SIGSEGV, Segmentation fault.
  #0  g_source_attach (source=0x0, context=0x0) at 
/build/glib2.0-MuyBSS/glib2.0-2.46.2/./glib/gmain.c:1163
  1163/build/glib2.0-MuyBSS/glib2.0-2.46.2/./glib/gmain.c: No such file or 
directory.
  [Current thread is 1 (Thread 0x7fda0a301a80 (LWP 3643))]
  (gdb) thr a a bt
  
  Thread 4 (Thread 0x7fd9f33a2700 (LWP 3651)):
  #0  0x7fda06d99743 in select () at ../sysdeps/unix/syscall-template.S:81
  #1  0x7fd9f3a5a530 in  () at /usr/lib/x86_64-linux-gnu/libtcl8.6.so
  #2  0x7fda0706d6aa in start_thread (arg=0x7fd9f33a2700) at 
pthread_create.c:333
  #3  0x7fda06da2eed in clone () at 
../sysdeps/unix/sysv/linux/x86_64/clone.S:109
  
  Thread 3 (Thread 0x7fd9ee9dd700 (LWP 3706)):
  #0  0x7fda06d978dd in poll () at ../sysdeps/unix/syscall-template.S:81
  #1  0x7fda079111ec in g_main_context_iterate (priority=2147483647, 
n_fds=2, fds=0x7fd9e80008e0, timeout=, context=0x561e1a8cf110) 
at /build/glib2.0-MuyBSS/glib2.0-2.46.2/./glib/gmain.c:4135
  #2  0x7fda079111ec in g_main_context_iterate 
(context=context@entry=0x561e1a8cf110, block=block@entry=1, 
dispatch=dispatch@entry=1, self=) at 
/build/glib2.0-MuyBSS/glib2.0-2.46.2/./glib/gmain.c:3835
  #3  0x7fda079112fc in g_main_context_iteration (context=0x561e1a8cf110, 
may_block=may_block@entry=1) at 
/build/glib2.0-MuyBSS/glib2.0-2.46.2/./glib/gmain.c:3901
  #4  0x7fda07911339 in glib_worker_main (data=) at 
/build/glib2.0-MuyBSS/glib2.0-2.46.2/./glib/gmain.c:5672
  #5  0x7fda07937965 in g_thread_proxy (data=0x561e1a82e9e0) at 
/build/glib2.0-MuyBSS/glib2.0-2.46.2/./glib/gthread.c:778
  #6  0x7fda0706d6aa in start_thread (arg=0x7fd9ee9dd700) at 
pthread_create.c:333
  #7  0x7fda06da2eed in clone () at 
../sysdeps/unix/sysv/linux/x86_64/clone.S:109
  
  Thread 2 (Thread 0x7fd9ee1dc700 (LWP 3707)):
  #0  0x7fda06d978dd in poll () at ../sysdeps/unix/syscall-template.S:81
  #1  0x7fda079111ec in g_main_context_iterate (priority=2147483647, 
n_fds=3, fds=0x7fd9e00010c0, timeout=, context=0x561e1a8cb710) 
at /build/glib2.0-MuyBSS/glib2.0-2.46.2/./glib/gmain.c:4135
  #2  0x7fda079111ec in g_main_context_iterate (context=0x561e1a8cb710, 
block=block@entry=1, dispatch=dispatch@entry=1, self=) at 
/build/glib2.0-MuyBSS/glib2.0-2.46.2/./glib/gmain.c:3835
  #3  0x7fda07911572 in g_main_loop_run (loop=0x561e1a8cfa00) at 
/build/glib2.0-MuyBSS/glib2.0-2.46.2/./glib/gmain.c:4034
  #4  0x7fda057944a6 in gdbus_shared_thread_func (user_data=0x561e1a8cfa40) 
at /build/glib2.0-MuyBSS/glib2.0-2.46.2/./gio/gdbusprivate.c:246
  #5  0x7fda07937965 in g_thread_proxy (data=0x561e1a82ea30) at 
/build/glib2.0-MuyBSS/glib2.0-2.46.2/./glib/gthread.c:778
  #6  0x7fda0706d6aa in start_thread (arg=0x7fd9ee1dc700) at 
pthread_create.c:333
  #7  0x7fda06da2eed in clone () at 
../sysdeps/unix/sysv/linux/x86_64/clone.S:109
  
  Thread 1 (Thread 0x7fda0a301a80 (LWP 3643)):
  #0  0x7fda0790eb24 in g_source_attach (source=0x0, context=0x0) at 
/build/glib2.0-MuyBSS/glib2.0-2.46.2/./glib/gmain.c:1163
  #1  0x7fda09c798b8 in  () at 
/usr/lib/x86_64-linux-gnu/libgstreamer-1.0.so.0
  #2  0x7fda09c799e0 in gst_bus_add_watch_full () at 
/usr/lib/x86_64-linux-gnu/libgstreamer-1.0.so.0
  #3  0x561e1a014b3a in pidgin_sound_play_file (filename=) 
at /build/pidgin-hiYwOJ/pidgin-2.10.11/./pidgin/gtksound.c:543
  #4  0x561e1a014927 in pidgin_sound_play_event 

[Bug 1518988] Re: Switching from "Plain Text" to "HTML" mode in Evolution composer keeps fixed width font

[Paul Smith]

I tested evolution 3.16.5-1ubuntu3.1 and the problem has been resolved.
Thanks!

** Tags removed: verification-needed
** Tags added: verification-done

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

Title:
  Switching from "Plain Text" to "HTML" mode in Evolution composer keeps
  fixed width font

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

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

[Bug 1476702] Re: Xorg crash when using Spotify client

[Paul Smith]

Updating the BIOS seems to have fixed it: no crashes since then.  Thanks
for the support!

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

Title:
  Xorg crash when using Spotify client

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

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

[Bug 1518988] [NEW] Switching from "Plain Text" to "HTML" mode in Evolution composer keeps fixed width font

[Paul Smith]

Public bug reported:

I'm using Evolution 3.16.5-1ubuntu3 in Ubuntu GNOME 15.10, latest
packages.

My email starts by default in Plain Text mode.  However sometimes I want
to switch to "HTML" mode.  When I do this, I get HTML-formatted email
HOWEVER no matter what I do my font is still always fixed-width and
never proportional.  I can change the size, the slant, etc. but it's
always fixed-width.

After discussing this on the Evolution mailing lists
https://mail.gnome.org/archives/evolution-
list/2015-November/msg00112.html it appears this is a bug that was fixed
in 3.18.  However, the fix looks simple to backport: please consider
pulling this into Ubuntu 15.10 version of Evolution to fix this
extremely annoying problem:

https://bugzilla.gnome.org/show_bug.cgi?id=753702

Fixed with this commit:

https://git.gnome.org/browse/evolution/commit/?id=8aa930e0634b22afa38753816be824d7b1622140

** Affects: evolution
 Importance: Unknown
 Status: Unknown

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

** Bug watch added: GNOME Bug Tracker #753702
   https://bugzilla.gnome.org/show_bug.cgi?id=753702

** Also affects: evolution via
   https://bugzilla.gnome.org/show_bug.cgi?id=753702
   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/1518988

Title:
  Switching from "Plain Text" to "HTML" mode in Evolution composer keeps
  fixed width font

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

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

[Bug 1476702] Re: Xorg crash when using Spotify client

[Paul Smith]

OK I've updated my bios:

$ sudo dmidecode -s bios-version && sudo dmidecode -s bios-release-date
0708
12/25/2012

I used to get crashes just by semi-vigorous scrolling in the Spotify
window but a session of clicking and scrolling so far hasn't reproduced
the crash.  I'll keep trying for a while.

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

Title:
  Xorg crash when using Spotify client

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

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

[Bug 1476702] [NEW] Xorg crash when using Spotify client

[Paul Smith]

Public bug reported:

Ever since I upgraded from Ubuntu GNOME 14.04 to Ubuntu GNOME 15.04,
I've had my entire desktop crash relatively quickly when using Spotify,
if I mess around with the client much.  Just starting the client is no
problem, and it plays songs OK, but for a while whenever I clicked one
of my playlists it would immediately crash.  I stopped using the client
for a while, but last week started using again and it was working for
these simple cases.

Today I started the client, picked a playlist, and grabbed the scrollbar
and dragged it all the way to the top; as I was dragging my desktop
crashed.  In my home directory I see a gnome-shell core:

(gdb) thr a a bt

Thread 2 (Thread 0x7f3da0ebd700 (LWP 16545)):
#0  0x7f3db4d3b8dd in poll () at ../sysdeps/unix/syscall-template.S:81
#1  0x7f3db5271ebc in g_main_context_iterate (priority=2147483647, n_fds=1, 
fds=0x7f3d9c0008e0, timeout=-1, context=0x1363e20) at 
/build/buildd/glib2.0-2.44.1/./glib/gmain.c:4103
#2  0x7f3db5271ebc in g_main_context_iterate 
(context=context@entry=0x1363e20, block=block@entry=1, 
dispatch=dispatch@entry=1, self=optimized out) at 
/build/buildd/glib2.0-2.44.1/./glib/gmain.c:3803
#3  0x7f3db5271fcc in g_main_context_iteration (context=0x1363e20, 
may_block=may_block@entry=1) at /build/buildd/glib2.0-2.44.1/./glib/gmain.c:3869
#4  0x7f3db5272009 in glib_worker_main (data=optimized out) at 
/build/buildd/glib2.0-2.44.1/./glib/gmain.c:5618
#5  0x7f3db5298955 in g_thread_proxy (data=0x1364000) at 
/build/buildd/glib2.0-2.44.1/./glib/gthread.c:764
#6  0x7f3db50116aa in start_thread (arg=0x7f3da0ebd700) at 
pthread_create.c:333
#7  0x7f3db4d46eed in clone () at 
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 1 (Thread 0x7f3db81a4a40 (LWP 16538)):
#0  0x7f3db5278d00 in g_logv (log_domain=0x7f3db6bfc260 mutter, 
log_level=G_LOG_LEVEL_ERROR, format=optimized out, 
args=args@entry=0x7ffd6e47ad40) at 
/build/buildd/glib2.0-2.44.1/./glib/gmessages.c:1046
#1  0x7f3db5278f3f in g_log (log_domain=log_domain@entry=0x7f3db6bfc260 
mutter, log_level=log_level@entry=G_LOG_LEVEL_ERROR, 
format=format@entry=0x7f3db6bf4838 Unable to initialize Clutter.\n) at 
/build/buildd/glib2.0-2.44.1/./glib/gmessages.c:1079
#2  0x7f3db6b71a7e in meta_clutter_init () at backends/meta-backend.c:469
#3  0x7f3db6ba1072 in meta_init () at core/main.c:358
#4  0x00401ddb in main (argc=1, argv=0x7ffd6e47b1b8) at main.c:429

but I think this is just a symptom of the X server crashing; in my X
session log file (Xorg.0.log.old probably attached below) I see:

[939562.032] (EE)
[939562.064] (EE) Backtrace:
[939562.212] (EE) 0: /usr/bin/X (xorg_backtrace+0x56) [0x7f5a10ef6556]
[939562.212] (EE) 1: /usr/bin/X (0x7f5a10d43000+0x1b7749) [0x7f5a10efa749]
[939562.212] (EE) 2: /lib/x86_64-linux-gnu/libc.so.6 (0x7f5a0ea09000+0x352f0) 
[0x7f5a0ea3e2f0]
[939562.212] (EE) 3: /usr/lib/xorg/modules/drivers/intel_drv.so 
(0x7f5a0afe8000+0xfa6c3) [0x7f5a0b0e26c3]
[939562.213] (EE) 4: /usr/lib/xorg/modules/drivers/intel_drv.so 
(0x7f5a0afe8000+0x10cf60) [0x7f5a0b0f4f60]
[939562.213] (EE) 5: /usr/lib/xorg/modules/drivers/intel_drv.so 
(0x7f5a0afe8000+0x10e3ac) [0x7f5a0b0f63ac]
[939562.213] (EE) 6: /usr/lib/xorg/modules/drivers/intel_drv.so 
(0x7f5a0afe8000+0x10f343) [0x7f5a0b0f7343]
[939562.213] (EE) 7: /usr/bin/X (DRI2SwapBuffers+0x1d0) [0x7f5a10ec9100]
[939562.213] (EE) 8: /usr/bin/X (0x7f5a10d43000+0x187a7c) [0x7f5a10ecaa7c]
[939562.213] (EE) 9: /usr/bin/X (0x7f5a10d43000+0x580a7) [0x7f5a10d9b0a7]
[939562.213] (EE) 10: /usr/bin/X (0x7f5a10d43000+0x5c29b) [0x7f5a10d9f29b]
[939562.213] (EE) 11: /lib/x86_64-linux-gnu/libc.so.6 (__libc_start_main+0xf0) 
[0x7f5a0ea29a40]
[939562.213] (EE) 12: /usr/bin/X (0x7f5a10d43000+0x4662e) [0x7f5a10d8962e]
[939562.213] (EE)
[939562.215] (EE) Segmentation fault at address 0x7f5a1119b004
[939562.215] (EE)
Fatal server error:
[939562.215] (EE) Caught signal 11 (Segmentation fault). Server aborting

So maybe an issue with the Intel display driver?

ProblemType: Bug
DistroRelease: Ubuntu 15.04
Package: xorg 1:7.7+7ubuntu4
ProcVersionSignature: Ubuntu 3.19.0-22.22-generic 3.19.8-ckt1
Uname: Linux 3.19.0-22-generic x86_64
.tmp.unity.support.test.0:
 
ApportVersion: 2.17.2-0ubuntu1.1
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
CurrentDesktop: GNOME
Date: Tue Jul 21 10:25:08 2015
DistUpgraded: 2015-04-27 12:05:00,462 DEBUG enabling apt cron job
DistroCodename: vivid
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GraphicsCard:
 Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller 
[8086:0162] (rev 09) (prog-if 00 [VGA controller])
   Subsystem: ASUSTeK Computer Inc. P8 series motherboard [1043:84ca]
InstallationDate: Installed on 2014-04-28 (449 days ago)
InstallationMedia: Ubuntu-GNOME 14.04 LTS Trusty Tahr - Release amd64 
(20140416.2)
MachineType: ASUSTeK COMPUTER INC. CM6870

[Bug 1448882] Re: Resume on Macbook Pro doesn't restart wireless connection

[Paul Smith]

The problem with testing the mainline kernel is that the failure is with
the wireless device, and that uses a proprietary broadcom driver on the
macbook (bcmwl).  I'm not sure how to get a copy of that driver that
will work with a newer kernel.  However I'll investigate and see what I
can do.

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

Title:
  Resume on Macbook Pro doesn't restart wireless connection

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

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

[Bug 1448882] Re: Resume on Macbook Pro doesn't restart wireless connection

[Paul Smith]

I'm not able to compile bmcwl-kernel-source for the latest mainline
kernel (linux-
headers-4.1.0-040100rc4-generic_4.1.0-040100rc4.201505181436_amd64) as
the compilation fails:

/var/lib/dkms/bcmwl/6.30.223.248+bdcom/build/src/wl/sys/wl_cfg80211_hybrid.c: I
n function ‘wl_cfg80211_get_station’:
/var/lib/dkms/bcmwl/6.30.223.248+bdcom/build/src/wl/sys/wl_cfg80211_hybrid.c:14
44:20: error: ‘STATION_INFO_TX_BITRATE’ undeclared (first use in this function)
   sinfo-filled |= STATION_INFO_TX_BITRATE;
^
/var/lib/dkms/bcmwl/6.30.223.248+bdcom/build/src/wl/sys/wl_cfg80211_hybrid.c:14
44:20: note: each undeclared identifier is reported only once for each function 
it appears in
/var/lib/dkms/bcmwl/6.30.223.248+bdcom/build/src/wl/sys/wl_cfg80211_hybrid.c:1457:20:
 error: ‘STATION_INFO_SIGNAL’ undeclared (first use in this function)
   sinfo-filled |= STATION_INFO_SIGNAL;
^


** Tags added: kernel-unable-to-test-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/1448882

Title:
  Resume on Macbook Pro doesn't restart wireless connection

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

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

[Bug 1448882] Re: Resume on Macbook Pro doesn't restart wireless connection

[Paul Smith]

apport information

** Tags added: apport-collected vivid

** Description changed:

  I've just installed Ubuntu GNOME 15.04 64bit on my Macbook Pro, and
  everything seems to work great including suspend/resume, EXCEPT that
  after I resume my wireless network does not start.  When the system
  first wakes up I very briefly see a ? icon for the wireless, then it
  disappears and nothing is shown.  If I click the system menu it says
  Wifi Not Connected.
  
  If I run killall wpa_supplicant (which I found in the answer to this
  question in askubuntu: http://askubuntu.com/questions/456644/wireless-
  doesnt-reconnect-after-resuming-on-after-the-upgrade-to-ubuntu-14-04-o )
  then wpa_supplicant is restarted automatically and when that happens my
  wifi comes back again.
  
  Info:
  $ cat /proc/version_signature
  Ubuntu 3.19.0-15.15-generic 3.19.3
  
  Wifi:
  02:00.0 Network controller [0280]: Broadcom Corporation BCM4331 802.11a/b/g/n 
[14e4:4331] (rev 02)
  
  lsmod:
  bcm5974
  
  wpasupplicant version 2.1-0ubuntu7.1
  network-manager version 0.9.10.0-4ubuntu15
+ --- 
+ ApportVersion: 2.17.2-0ubuntu1.1
+ Architecture: amd64
+ AudioDevicesInUse:
+  USERPID ACCESS COMMAND
+  /dev/snd/controlC0:  psmith 1311 F pulseaudio
+ CurrentDesktop: GNOME
+ DistroRelease: Ubuntu 15.04
+ HibernationDevice: RESUME=UUID=0886834d-a55b-48fc-be4e-21b43e537ffe
+ InstallationDate: Installed on 2015-04-25 (29 days ago)
+ InstallationMedia: Ubuntu-GNOME 15.04 Vivid Vervet - Release amd64 
(20150422)
+ MachineType: Apple Inc. MacBookPro9,2
+ NonfreeKernelModules: wl
+ Package: linux (not installed)
+ ProcEnviron:
+  TERM=xterm
+  PATH=(custom, no user)
+  XDG_RUNTIME_DIR=set
+  LANG=en_US.UTF-8
+  SHELL=/bin/bash
+ ProcFB: 0 inteldrmfb
+ ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-18-generic.efi.signed 
root=UUID=7cc4dfee-335f-4a7f-ae50-59276f346587 ro quiet splash vt.handoff=7
+ ProcVersionSignature: Ubuntu 3.19.0-18.18-generic 3.19.6
+ RelatedPackageVersions:
+  linux-restricted-modules-3.19.0-18-generic N/A
+  linux-backports-modules-3.19.0-18-generic  N/A
+  linux-firmware 1.143.1
+ Tags:  vivid
+ UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
+ Uname: Linux 3.19.0-18-generic x86_64
+ UpgradeStatus: No upgrade log present (probably fresh install)
+ UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
+ _MarkForUpload: True
+ dmi.bios.date: 08/08/2012
+ dmi.bios.vendor: Apple Inc.
+ dmi.bios.version: MBP91.88Z.00D3.B08.1208081132
+ dmi.board.asset.tag: Base Board Asset Tag#
+ dmi.board.name: Mac-6F01561E16C75D06
+ dmi.board.vendor: Apple Inc.
+ dmi.board.version: MacBookPro9,2
+ dmi.chassis.type: 10
+ dmi.chassis.vendor: Apple Inc.
+ dmi.chassis.version: Mac-6F01561E16C75D06
+ dmi.modalias: 
dmi:bvnAppleInc.:bvrMBP91.88Z.00D3.B08.1208081132:bd08/08/2012:svnAppleInc.:pnMacBookPro9,2:pvr1.0:rvnAppleInc.:rnMac-6F01561E16C75D06:rvrMacBookPro9,2:cvnAppleInc.:ct10:cvrMac-6F01561E16C75D06:
+ dmi.product.name: MacBookPro9,2
+ dmi.product.version: 1.0
+ dmi.sys.vendor: Apple Inc.

** Attachment added: AlsaInfo.txt
   
https://bugs.launchpad.net/bugs/1448882/+attachment/4403522/+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/1448882

Title:
  Resume on Macbook Pro doesn't restart wireless connection

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

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

[Bug 1448882] CRDA.txt

[Paul Smith]

apport information

** Attachment added: CRDA.txt
   https://bugs.launchpad.net/bugs/1448882/+attachment/4403523/+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/1448882

Title:
  Resume on Macbook Pro doesn't restart wireless connection

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

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

[Bug 1448882] IwConfig.txt

[Paul Smith]

apport information

** Attachment added: IwConfig.txt
   
https://bugs.launchpad.net/bugs/1448882/+attachment/4403525/+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/1448882

Title:
  Resume on Macbook Pro doesn't restart wireless connection

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

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

[Bug 1448882] JournalErrors.txt

[Paul Smith]

apport information

** Attachment added: JournalErrors.txt
   
https://bugs.launchpad.net/bugs/1448882/+attachment/4403526/+files/JournalErrors.txt

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

Title:
  Resume on Macbook Pro doesn't restart wireless connection

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

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

[Bug 1448882] CurrentDmesg.txt

[Paul Smith]

apport information

** Attachment added: CurrentDmesg.txt
   
https://bugs.launchpad.net/bugs/1448882/+attachment/4403524/+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/1448882

Title:
  Resume on Macbook Pro doesn't restart wireless connection

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

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

[Bug 1448882] UdevDb.txt

[Paul Smith]

apport information

** Attachment added: UdevDb.txt
   https://bugs.launchpad.net/bugs/1448882/+attachment/4403534/+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/1448882

Title:
  Resume on Macbook Pro doesn't restart wireless connection

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

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

[Bug 1448882] PulseList.txt

[Paul Smith]

apport information

** Attachment added: PulseList.txt
   
https://bugs.launchpad.net/bugs/1448882/+attachment/4403532/+files/PulseList.txt

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

Title:
  Resume on Macbook Pro doesn't restart wireless connection

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

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

[Bug 1448882] ProcModules.txt

[Paul Smith]

apport information

** Attachment added: ProcModules.txt
   
https://bugs.launchpad.net/bugs/1448882/+attachment/4403531/+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/1448882

Title:
  Resume on Macbook Pro doesn't restart wireless connection

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

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

[Bug 1448882] ProcInterrupts.txt

[Paul Smith]

apport information

** Attachment added: ProcInterrupts.txt
   
https://bugs.launchpad.net/bugs/1448882/+attachment/4403530/+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/1448882

Title:
  Resume on Macbook Pro doesn't restart wireless connection

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

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

[Bug 1448882] Lsusb.txt

[Paul Smith]

apport information

** Attachment added: Lsusb.txt
   https://bugs.launchpad.net/bugs/1448882/+attachment/4403528/+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/1448882

Title:
  Resume on Macbook Pro doesn't restart wireless connection

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

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

[Bug 1448882] Lspci.txt

[Paul Smith]

apport information

** Attachment added: Lspci.txt
   https://bugs.launchpad.net/bugs/1448882/+attachment/4403527/+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/1448882

Title:
  Resume on Macbook Pro doesn't restart wireless connection

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

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

[Bug 1448882] WifiSyslog.txt

[Paul Smith]

apport information

** Attachment added: WifiSyslog.txt
   
https://bugs.launchpad.net/bugs/1448882/+attachment/4403535/+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/1448882

Title:
  Resume on Macbook Pro doesn't restart wireless connection

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

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

[Bug 1448882] RfKill.txt

[Paul Smith]

apport information

** Attachment added: RfKill.txt
   https://bugs.launchpad.net/bugs/1448882/+attachment/4403533/+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/1448882

Title:
  Resume on Macbook Pro doesn't restart wireless connection

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

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

[Bug 1448882] ProcCpuinfo.txt

[Paul Smith]

apport information

** Attachment added: ProcCpuinfo.txt
   
https://bugs.launchpad.net/bugs/1448882/+attachment/4403529/+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/1448882

Title:
  Resume on Macbook Pro doesn't restart wireless connection

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

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

[Bug 1448882] Re: Resume on Macbook Pro doesn't restart wireless connection

[Paul Smith]

My macbook is at work but I'll bring it home this weekend and see if I
can do more investigation.

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

Title:
  Resume on Macbook Pro doesn't restart wireless connection

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

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

[Bug 1448882] [NEW] Resume on Macbook Pro doesn't restart wireless connection

[Paul Smith]

Public bug reported:

I've just installed Ubuntu GNOME 15.04 64bit on my Macbook Pro, and
everything seems to work great including suspend/resume, EXCEPT that
after I resume my wireless network does not start.  When the system
first wakes up I very briefly see a ? icon for the wireless, then it
disappears and nothing is shown.  If I click the system menu it says
Wifi Not Connected.

If I run killall wpa_supplicant (which I found in the answer to this
question in askubuntu: http://askubuntu.com/questions/456644/wireless-
doesnt-reconnect-after-resuming-on-after-the-upgrade-to-ubuntu-14-04-o )
then wpa_supplicant is restarted automatically and when that happens my
wifi comes back again.

Info:
$ cat /proc/version_signature
Ubuntu 3.19.0-15.15-generic 3.19.3

Wifi:
02:00.0 Network controller [0280]: Broadcom Corporation BCM4331 802.11a/b/g/n 
[14e4:4331] (rev 02)

lsmod:
bcm5974

wpasupplicant version 2.1-0ubuntu7.1
network-manager version 0.9.10.0-4ubuntu15

** Affects: linux (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/1448882

Title:
  Resume on Macbook Pro doesn't restart wireless connection

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

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

[Bug 1247366] Re: Evolution is missing bogofilter integration

[Paul Smith]

Thank you Iain!  Is there any possibility this can get backported to
14.04?  As an LTS release, it would be REALLY nice to have this fix
there too... I think this patch applies cleanly to 3.11 as well as 3.12.

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

Title:
  Evolution is missing bogofilter integration

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

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

[Bug 1247366] Re: Evolution is missing bogofilter integration

[Paul Smith]

If you know of another way, than filing a bug like this one, I urge you
to pursue it...

** Tags added: patch

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

Title:
  Evolution is missing bogofilter integration

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

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

[Bug 1247366] Re: Evolution is missing bogofilter integration

[Paul Smith]

Just for completeness I'm adding the patch used to fix this issue
upstream.

** Patch added: Patch for Gnome bug 1247366
   
https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/1247366/+attachment/4331521/+files/bug-1247366.patch

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

Title:
  Evolution is missing bogofilter integration

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

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

[Bug 1247366] Re: Evolution is missing bogofilter integration

[Paul Smith]

Well, first it has to get fixed in Ubuntu, in any version: currently
there's no fix even in the upcoming 15.04.

Once that happens we can talk about whether it's possible to backport
it.

** Tags removed: patch

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

Title:
  Evolution is missing bogofilter integration

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

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

[Bug 1247366] Re: Evolution is missing bogofilter integration

[Paul Smith]

Milan Crha has posted a fix for the next release of Evolution, which may
or may not be straightforward to cherry-pick back to the current
release.

See: https://bugzilla.gnome.org/show_bug.cgi?id=743109

and: https://git.gnome.org/browse/evolution/commit/?id=0b91d60

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

Title:
  Evolution is missing bogofilter integration

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

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

[Bug 1247366] Re: Evolution is missing bogofilter integration

[Paul Smith]

Hm.  It seems that newer versions of Evolution have completely removed
support for runtime detection of the underlying spam filtering facility
in the plugin, so my simple patch in comment #18 is not sufficient and
more work is needed.

See https://bugzilla.gnome.org/show_bug.cgi?id=743109 for more
information.

** Bug watch added: GNOME Bug Tracker #743109
   https://bugzilla.gnome.org/show_bug.cgi?id=743109

** Also affects: evolution via
   https://bugzilla.gnome.org/show_bug.cgi?id=743109
   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/1247366

Title:
  Evolution is missing bogofilter integration

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

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

[Bug 1247366] Re: Evolution is missing bogofilter integration

[Paul Smith]

I believe this can be fixed with a simple patch to the rules file in the
Evolution Ubuntu package: if we set the BOGOFILTER environment variable
before we run configure then whatever value it has will be used during
the build without checking, and at runtime if the program exists the
plugin will be enabled (and if not it won't be).

** Patch added: Enable bogofilter plugin for Evolution
   
https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/1247366/+attachment/4298600/+files/evo-bogofilter.patch

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

Title:
  Evolution is missing bogofilter integration

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

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

[Bug 1386869] Re: -host in auto.master not mounting nfs exports

[Paul Smith]

Is there a reason we can't just go get the patches that Ian Kent already
provided for Fedora (see my link to the Red Hat bugzilla entry, which
contains references to RPM versions that fix the problem) and apply them
here and/or in Debian since the bug exists there as well?

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

Title:
  -host in auto.master not mounting nfs exports

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/autofs/+bug/1386869/+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 1386869] Re: -host in auto.master not mounting nfs exports

[Paul Smith]

Is there a reason we can't just go get the patches that Ian Kent already
provided for Fedora (see my link to the Red Hat bugzilla entry, which
contains references to RPM versions that fix the problem) and apply them
here and/or in Debian since the bug exists there as well?

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

Title:
  -host in auto.master not mounting nfs exports

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

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

[Bug 1387459] Re: autofs stops working after upgrade to 14.10

[Paul Smith]

I believe this is a duplicate of Bug #1386869

There's a workaround in the comments of that bug.  HTH!

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

Title:
  autofs stops working after upgrade to 14.10

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/autofs/+bug/1387459/+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 1386869] Re: -host in auto.master not mounting nfs exports

[Paul Smith]

This appears to be a bug in the version of autofs that Ubuntu is
shipping.  See this report from ArchLinux:
https://bugs.archlinux.org/task/38379

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

Title:
  -host in auto.master not mounting nfs exports

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/autofs/+bug/1386869/+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 1386869] Re: -host in auto.master not mounting nfs exports

[Paul Smith]

Also there's a problem reported in Fedora against 5.0.7, but apparently
still present for 5.0.8:
https://bugzilla.redhat.com/show_bug.cgi?id=1038356

** Bug watch added: Red Hat Bugzilla #1038356
   https://bugzilla.redhat.com/show_bug.cgi?id=1038356

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

Title:
  -host in auto.master not mounting nfs exports

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/autofs/+bug/1386869/+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 1387459] Re: autofs stops working after upgrade to 14.10

[Paul Smith]

I believe this is a duplicate of Bug #1386869

There's a workaround in the comments of that bug.  HTH!

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

Title:
  autofs stops working after upgrade to 14.10

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

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

[Bug 1386869] Re: -host in auto.master not mounting nfs exports

[Paul Smith]

This appears to be a bug in the version of autofs that Ubuntu is
shipping.  See this report from ArchLinux:
https://bugs.archlinux.org/task/38379

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

Title:
  -host in auto.master not mounting nfs exports

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

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

[Bug 1386869] Re: -host in auto.master not mounting nfs exports

[Paul Smith]

Also there's a problem reported in Fedora against 5.0.7, but apparently
still present for 5.0.8:
https://bugzilla.redhat.com/show_bug.cgi?id=1038356

** Bug watch added: Red Hat Bugzilla #1038356
   https://bugzilla.redhat.com/show_bug.cgi?id=1038356

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

Title:
  -host in auto.master not mounting nfs exports

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

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