from:"Thomas A. F. Thorne"

Would +bug1756835 work better as a link?

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

Title:
  window-stack-bridge crashed with SIGABRT in QMessageLogger::fatal()

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

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

[Bug 1753393] Re: window-stack-bridge crashed with SIGABRT in QMessageLogger::fatal()

The problem happened again this morning.

As requested above I have filed a new report at #1756835.  Hopefully
this will include more useful diagnostic information.

** Information type changed from Private to Public

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

Title:
  window-stack-bridge crashed with SIGABRT in QMessageLogger::fatal()

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

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

[Bug 1753393] Re: window-stack-bridge crashed with SIGABRT in QMessageLogger::fatal()

Changing report to Public so that others can see it.

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

Title:
  window-stack-bridge crashed with SIGABRT in QMessageLogger::fatal()

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

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

[Bug 1748844] Re: hud-service crash with qmessageLogger::fatal() reported at login

Occurred again today.  New report raised at +bug1756839

I raised a new report as this bug seems to happen as a pair with another
bug.  The original pair that went with this bug (+bug1753393) asked me
to raise a new bug to see if better diagnostics were included.  I have
done so and created +bug1756835.  +bug1756839 is the new copy of this
bug, created from the same login as +bug1756835

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

Title:
  hud-service crash with qmessageLogger::fatal() reported at login

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

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

[Bug 1651130] Re: gvfsd-smb-browse crashed with SIGABRT in talloc_abort()

2019-08-07 Thread Thomas A. F. Thorne

Marking as non-private as it has been long enough I am comfortable that
anything stored is no longer sensative.  I do not think there is
anything sensitive in there anyway.

I am back here now as I have just raised bug 1839247 however that only
looks related by attributed package and nothing more.  I know I am not
running on the same hardware.

** Information type changed from Private to Public

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

Title:
  gvfsd-smb-browse crashed with SIGABRT in talloc_abort()

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

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

[Bug 1839247] Re: gvfsd-smb-browse crashed with SIGABRT

2019-08-07 Thread Thomas A. F. Thorne

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

Apport is once again suggesting this is a duplicate of a private bug.
If I am mean to check whether this is a duplicate or not I cannot do so.

If apport is comfortable to strip this bug of its Private tag, why can
it not do the same for the one being referenced?

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

Title:
  gvfsd-smb-browse crashed with SIGABRT

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

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

[Bug 1837071] Re: xfsettingsd crashed with SIGSEGV

2019-08-08 Thread Thomas A. F. Thorne

** Information type changed from Private to Public

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

Title:
  xfsettingsd crashed with SIGSEGV

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xfce4-settings/+bug/1837071/+subscriptions

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

[Bug 1810743] [NEW] keepassxc fails to start with could not find or load the Qt platform plugin "xcb" in "".

2019-01-07 Thread Thomas A. F. Thorne

Public bug reported:

I recently installed keepassxc and attempted to launch it both from the
activities menu and from the command line without success.  When I try
to run the application from the command line I see:


$ keepassxc --help
This application failed to start because it could not find or load the Qt 
platform plugin "xcb"
in "".

Available platform plugins are: eglfs, linuxfb, minimal, minimalegl,
offscreen, vnc, wayland-egl, wayland, wayland-xcomposite-egl, wayland-
xcomposite-glx, xcb.

Reinstalling the application may fix this problem.
Aborted


Trying to find what is wrong with the xcb plugin I ran again with 
QT_DEBUG_PLUGINS sete to 1.


$ QT_DEBUG_PLUGINS=1 keepassxc --help
QFactoryLoader::QFactoryLoader() checking directory path "/usr/bin/platforms" 
...
QFactoryLoader::QFactoryLoader() looking at "/usr/bin/platforms/libqeglfs.so"
Found metadata in lib 
/usr/lib/x86_64-linux-gnu/qt5/plugins/platforms/libqeglfs.so, metadata=
{
"IID": "org.qt-project.Qt.QPA.QPlatformIntegrationFactoryInterface.5.3",
"MetaData": {
"Keys": [
"eglfs"
]
},
"className": "QEglFSIntegrationPlugin",
"debug": false,
"version": 329989
}


Got keys from plugin meta data ("eglfs")
QFactoryLoader::QFactoryLoader() looking at "/usr/bin/platforms/libqlinuxfb.so"
Found metadata in lib 
/usr/lib/x86_64-linux-gnu/qt5/plugins/platforms/libqlinuxfb.so, metadata=
{
"IID": "org.qt-project.Qt.QPA.QPlatformIntegrationFactoryInterface.5.3",
"MetaData": {
"Keys": [
"linuxfb"
]
},
"className": "QLinuxFbIntegrationPlugin",
"debug": false,
"version": 329989
}


Got keys from plugin meta data ("linuxfb")
QFactoryLoader::QFactoryLoader() looking at "/usr/bin/platforms/libqminimal.so"
Found metadata in lib 
/usr/lib/x86_64-linux-gnu/qt5/plugins/platforms/libqminimal.so, metadata=
{
"IID": "org.qt-project.Qt.QPA.QPlatformIntegrationFactoryInterface.5.3",
"MetaData": {
"Keys": [
"minimal"
]
},
"className": "QMinimalIntegrationPlugin",
"debug": false,
"version": 329989
}


Got keys from plugin meta data ("minimal")
QFactoryLoader::QFactoryLoader() looking at 
"/usr/bin/platforms/libqminimalegl.so"
Found metadata in lib 
/usr/lib/x86_64-linux-gnu/qt5/plugins/platforms/libqminimalegl.so, metadata=
{
"IID": "org.qt-project.Qt.QPA.QPlatformIntegrationFactoryInterface.5.3",
"MetaData": {
"Keys": [
"minimalegl"
]
},
"className": "QMinimalEglIntegrationPlugin",
"debug": false,
"version": 329989
}


Got keys from plugin meta data ("minimalegl")
QFactoryLoader::QFactoryLoader() looking at 
"/usr/bin/platforms/libqoffscreen.so"
Found metadata in lib 
/usr/lib/x86_64-linux-gnu/qt5/plugins/platforms/libqoffscreen.so, metadata=
{
"IID": "org.qt-project.Qt.QPA.QPlatformIntegrationFactoryInterface.5.3",
"MetaData": {
"Keys": [
"offscreen"
]
},
"className": "QOffscreenIntegrationPlugin",
"debug": false,
"version": 329989
}


Got keys from plugin meta data ("offscreen")
QFactoryLoader::QFactoryLoader() looking at "/usr/bin/platforms/libqvnc.so"
Found metadata in lib 
/usr/lib/x86_64-linux-gnu/qt5/plugins/platforms/libqvnc.so, metadata=
{
"IID": "org.qt-project.Qt.QPA.QPlatformIntegrationFactoryInterface.5.3",
"MetaData": {
"Keys": [
"vnc"
]
},
"className": "QVncIntegrationPlugin",
"debug": false,
"version": 329989
}


Got keys from plugin meta data ("vnc")
QFactoryLoader::QFactoryLoader() looking at 
"/usr/bin/platforms/libqwayland-egl.so"
Found metadata in lib 
/usr/lib/x86_64-linux-gnu/qt5/plugins/platforms/libqwayland-egl.so, metadata=
{
"IID": "org.qt-project.Qt.QPA.QPlatformIntegrationFactoryInterface.5.3",
"MetaData": {
"Keys": [
"wayland-egl"
]
},
"className": "QWaylandEglPlatformIntegrationPlugin",
"debug": false,
"version": 329989
}


Got keys from plugin meta data ("wayland-egl")
QFactoryLoader::QFactoryLoader() looking at 
"/usr/bin/platforms/libqwayland-generic.so"
Found metadata in lib 
/usr/lib/x86_64-linux-gnu/qt5/plugins/platforms/libqwayland-generic.so, 
metadata=
{
"IID": "org.qt-project.Qt.QPA.QPlatformIntegrationFactoryInterface.5.3",
"MetaData": {
"Keys": [
"wayland"
]
},
"className": "QWaylandIntegrationPlugin",
"debug": false,
"version": 329989
}


Got keys from plugin meta data ("wayland")
QFactoryLoader::QFactoryLoader() looking at 
"/usr/bin/platforms/libqwayland-xcomposite-egl.so"
Found metadata in lib 
/usr/lib/x86_64-linux-gnu/qt5/plugins/platforms/libqwayland-xcomposite-egl.so, 
metadata=
{
"IID": "org.qt-project.Qt.QPA.QPlatformIntegrationFactoryInterface.5.3",
"MetaData": {
"Keys": [
"wayland-xcomposite-egl"
]
},
"className": "QWaylandXCompositeEglPlatformIntegrationPlugin",

[Bug 1820029] [NEW] My Ubuntu 18.04 GUI seems frozen

Public bug reported:

This will possibly be a duplicate of Bug #1820028

I was trying to report a frozen GUI over SSH. This is the second report
that apport-cli generated when I ran it with xdm as the target package.

The symptoms I see are that I started running a go test last night and
my GUI on Ubuntu 18.04 seems to have frozen. I cannot get the wireless
mouse or keyboard to move anything on the display and the time shown on
the clock matches when things froze last night.

Before I made the report I looked for any process using high amounts of
CUP with top and htop but spotted none. I tried to local a SIGTERM the
go test process but that made no difference.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xdm (not installed)
ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18
Uname: Linux 4.15.0-45-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.5
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
Date: Thu Mar 14 09:02:43 2019
DistUpgraded: 2018-07-27 11:19:59,510 DEBUG failed to SystemUnLock() (E:Not 
locked)
DistroCodename: bionic
DistroVariant: ubuntu
GraphicsCard:
 Intel Corporation HD Graphics 630 [8086:5912] (rev 04) (prog-if 00 [VGA 
controller])
   Subsystem: ASUSTeK Computer Inc. HD Graphics 630 [1043:8694]
InstallationDate: Installed on 2017-11-16 (482 days ago)
InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801)
MachineType: System manufacturer System Product Name
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-45-generic 
root=UUID=473dc1b9-3a5c-4f95-8cc0-e3b0f628ca41 ro quiet splash vt.handoff=1
SourcePackage: xdm
UnitySupportTest:
 Error: command ['/usr/lib/nux/unity_support_test', '-p', '-f'] failed with 
exit code 5: PuTTY X11 proxy: unable to connect to forwarded X server: Network 
error: Connection refused
 Error: unable to open display
UpgradeStatus: Upgraded to bionic on 2018-07-27 (229 days ago)
dmi.bios.date: 09/27/2017
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 0811
dmi.board.asset.tag: Default string
dmi.board.name: STRIX H270F GAMING
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: Rev X.0x
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 3
dmi.chassis.vendor: Default string
dmi.chassis.version: Default string
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0811:bd09/27/2017:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnSTRIXH270FGAMING:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:
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
version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
version.libdrm2: libdrm2 2.4.95-1~18.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.2-0ubuntu1~18.04.1
version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.2-0ubuntu1~18.04.1
version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2
xserver.bootTime: Tue Mar 12 13:46:44 2019
xserver.configfile: default
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.version: 2:1.19.6-1ubuntu4.2
xserver.video_driver: modeset

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


** Tags: amd64 apport-bug bionic ubuntu

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

Title:
  My Ubuntu 18.04 GUI seems frozen

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

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

[Bug 1820030] [NEW] My Ubuntu 18.04 GUI seems frozen

Public bug reported:

This will possibly be a duplicate of Bug #1820028 or Bug #1820028

I was trying to report a frozen GUI over SSH. This is the second report
that apport-cli generated when I ran it with lightdm as the target
package.

The symptoms I see are that I started running a go test last night and
my GUI on Ubuntu 18.04 seems to have frozen. I cannot get the wireless
mouse or keyboard to move anything on the display and the time shown on
the clock matches when things froze last night.

Before I made the report I looked for any process using high amounts of
CUP with top and htop but spotted none. I tried to local a SIGTERM the
go test process but that made no difference.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: lightdm 1.26.0-0ubuntu1
ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18
Uname: Linux 4.15.0-45-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.5
Architecture: amd64
Date: Thu Mar 14 09:09:36 2019
InstallationDate: Installed on 2017-11-16 (482 days ago)
InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801)
ProcEnviron:
 LANG=en_GB.UTF-8
 TERM=xterm
 LANGUAGE=en_GB:en
 PATH=(custom, no user)
 SHELL=/bin/bash
SourcePackage: lightdm
UpgradeStatus: Upgraded to bionic on 2018-07-27 (229 days ago)

** Affects: lightdm (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/1820030

Title:
  My Ubuntu 18.04 GUI seems frozen

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

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

[Bug 1820031] [NEW] My Ubuntu 18.04 GUI seems frozen

Public bug reported:

This will possibly be a duplicate of Bug #1820028 or Bug #1820029 or Bug
#1820030

I was trying to report a frozen GUI over SSH. This is the second report
that apport-cli generated when I ran it with xorg as the target package.
I made three four reports to see if different diagnostics were
geneereated as Ihave no way of knowing what is causing the lock up at
present.

The symptoms I see are that I started running a go test last night and
my GUI on Ubuntu 18.04 seems to have frozen. I cannot get the wireless
mouse or keyboard to move anything on the display and the time shown on
the clock matches when things froze last night.

Before I made the report I looked for any process using high amounts of
CUP with top and htop but spotted none. I tried to local a SIGTERM the
go test process but that made no difference.



I shall attempt to restart my desktop service

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xorg 1:7.7+19ubuntu7.1
ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18
Uname: Linux 4.15.0-45-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.5
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
Date: Thu Mar 14 09:12:51 2019
DistUpgraded: 2018-07-27 11:19:59,510 DEBUG failed to SystemUnLock() (E:Not 
locked)
DistroCodename: bionic
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, including running git bisection searches
GraphicsCard:
 Intel Corporation HD Graphics 630 [8086:5912] (rev 04) (prog-if 00 [VGA 
controller])
   Subsystem: ASUSTeK Computer Inc. HD Graphics 630 [1043:8694]
InstallationDate: Installed on 2017-11-16 (482 days ago)
InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801)
MachineType: System manufacturer System Product Name
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-45-generic 
root=UUID=473dc1b9-3a5c-4f95-8cc0-e3b0f628ca41 ro quiet splash vt.handoff=1
SourcePackage: xorg
UnitySupportTest:
 Error: command ['/usr/lib/nux/unity_support_test', '-p', '-f'] failed with 
exit code 5: PuTTY X11 proxy: unable to connect to forwarded X server: Network 
error: Connection refused
 Error: unable to open display
UpgradeStatus: Upgraded to bionic on 2018-07-27 (229 days ago)
dmi.bios.date: 09/27/2017
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 0811
dmi.board.asset.tag: Default string
dmi.board.name: STRIX H270F GAMING
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: Rev X.0x
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 3
dmi.chassis.vendor: Default string
dmi.chassis.version: Default string
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0811:bd09/27/2017:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnSTRIXH270FGAMING:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:
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
version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
version.libdrm2: libdrm2 2.4.95-1~18.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.2-0ubuntu1~18.04.1
version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.2-0ubuntu1~18.04.1
version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2
xserver.bootTime: Tue Mar 12 13:46:44 2019
xserver.configfile: default
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.version: 2:1.19.6-1ubuntu4.2
xserver.video_driver: modeset

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


** Tags: amd64 apport-bug bionic ubuntu

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

Title:
  My Ubuntu 18.04 GUI seems frozen

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

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

[Bug 1820031] Re: My Ubuntu 18.04 GUI seems frozen

Nothing new comes out in the crash report.

When I visit
https://errors.ubuntu.com/user/1d81a00d35531ca846cc8b470c853c9c4cc299c3a0a42040e68da92210168a3d96818f5de95d8f7d85e66516d77e481a6259123145189d1685f6d22ac584114a
the most recent report is:

https://errors.ubuntu.com/oops/0d2b0694-2b7d-11e9-9d81-fa163e102db1

I shall try to apply the work around from
https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/994921 as
suggested in step 3 of the instructions you have linked to.

I do not need to apply it as it is already in place.


So what next... apport-collect perhapse although it seems that enough debug may 
be already posted.  Maybe just a reboot of my system (as I cannot restart a 
service) and move on.

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

Title:
  My Ubuntu 18.04 GUI seems frozen

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

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

[Bug 1038044] Re: munin-node: apt_all does not Grok Ubuntu (possible regression)

2019-04-26 Thread Thomas A. F. Thorne

Thank you for taking the time to get this through Christian.

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

Title:
  munin-node: apt_all does not Grok Ubuntu (possible regression)

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

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

[Bug 1831855] Re: Running wireshark-gtk with lots of virtual devices and it crashed with SIGSEGV

2019-06-06 Thread Thomas A. F. Thorne

Having reviewed the contents of the attachments, I do not consider
anything there sensitive so I am changing this bug from private to
public.

If there is anything I could do to try and recreate the issue or debug
the problem please let me know.

** Information type changed from Private to Public

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

Title:
  Running wireshark-gtk with lots of virtual devices and it crashed with
  SIGSEGV

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

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

[Bug 1785249] Re: git-cola crashed with SIGABRT

2019-01-22 Thread Thomas A. F. Thorne

I had this again today.  I also have it when I try to use Barrier or
Synergy, so something has gone wrong with my Qt environment between
16.04 and 18.04. I have tried to remove the development tools and
runtime environment without success.


After posting to the git-cola project's issue tracker:
https://github.com/git-cola/git-cola/issues/869

I was advised to try the snap packaged/version/conaintered variant of
the application.  This has worked perfectly for me as a work around.

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

Title:
  git-cola crashed with SIGABRT

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/git-cola/+bug/1785249/+subscriptions

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

[Bug 1785249] Re: git-cola crashed with SIGABRT

2019-01-24 Thread Thomas A. F. Thorne

Running with my LD_LIBRARY_PATH setup seems to avoid the problem.

$ LD_LIBRARY_PATH=/usr/lib/x86_64-linux-gnu/:$LD_LIBRARY_PATH git-cola

I was lead to attempting this by post at
https://superuser.com/questions/1397366/what-is-wrong-with-my-qt-
environment-it-reports-could-not-find-or-load-the-qt/1397518#1397518

It was noticed that in my debug of the Qt plugins and dynamic library
use, multiple library paths were being selected:

$ export QT_DEBUG_PLUGINS=1
$ git-cola
QFactoryLoader::QFactoryLoader() checking directory path "/usr/bin/platforms" 
...
QFactoryLoader::QFactoryLoader() looking at "/usr/bin/platforms/libqeglfs.so"
Found metadata in lib 
/usr/lib/x86_64-linux-gnu/qt5/plugins/platforms/libqeglfs.so, metadata=
{
"IID": "org.qt-project.Qt.QPA.QPlatformIntegrationFactoryInterface.5.3",
"MetaData": {
"Keys": [
"eglfs"
]
},
"className": "QEglFSIntegrationPlugin",
"debug": false,
"version": 329989
}


..


Got keys from plugin meta data ("xcb")
Cannot load library /usr/lib/x86_64-linux-gnu/qt5/plugins/platforms/libqxcb.so: 
(/usr/lib/x86_64-linux-gnu/libQt5XcbQpa.so.5: symbol 
_ZNK15QPlatformWindow15safeAreaMarginsEv version Qt_5_PRIVATE_API not defined 
in file libQt5Gui.so.5 with link time reference)
QLibraryPrivate::loadPlugin failed on 
"/usr/lib/x86_64-linux-gnu/qt5/plugins/platforms/libqxcb.so" : "Cannot load 
library /usr/lib/x86_64-linux-gnu/qt5/plugins/platforms/libqxcb.so: 
(/usr/lib/x86_64-linux-gnu/libQt5XcbQpa.so.5: symbol 
_ZNK15QPlatformWindow15safeAreaMarginsEv version Qt_5_PRIVATE_API not defined 
in file libQt5Gui.so.5 with link time reference)"
This application failed to start because it could not find or load the Qt 
platform plugin "xcb"
in "".

Available platform plugins are: eglfs, linuxfb, minimal, minimalegl,
offscreen, vnc, wayland-egl, wayland, wayland-xcomposite-egl, wayland-
xcomposite-glx, xcb.

Reinstalling the application may fix this problem.
Aborted (core dumped)

$ env LANG=C ldd /usr/lib/x86_64-linux-gnu/qt5/plugins/platforms/libqxcb.so
linux-vdso.so.1 (0x7ffc489e3000)
libQt5XcbQpa.so.5 => /usr/lib/x86_64-linux-gnu/libQt5XcbQpa.so.5 
(0x7fd3090c8000)
libQt5Gui.so.5 => /lib/x86_64-linux-gnu/libQt5Gui.so.5 (0x7fd308919000)
libQt5Core.so.5 => /lib/x86_64-linux-gnu/libQt5Core.so.5 
(0x7fd3081de000)
libstdc++.so.6 => /usr/lib/x86_64-linux-gnu/libstdc++.so.6 
(0x7fd307e5)
libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x7fd307a5f000)
libglib-2.0.so.0 => /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 
(0x7fd307749000)
libfontconfig.so.1 => /usr/lib/x86_64-linux-gnu/libfontconfig.so.1 
(0x7fd307504000)
libfreetype.so.6 => /usr/lib/x86_64-linux-gnu/libfreetype.so.6 
(0x7fd30725)
libQt5DBus.so.5 => /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5 
(0x7fd306fc6000)
libpthread.so.0 => /lib/x86_64-linux-gnu/libpthread.so.0 
(0x7fd306da7000)
libX11-xcb.so.1 => /usr/lib/x86_64-linux-gnu/libX11-xcb.so.1 
(0x7fd306ba5000)
libX11.so.6 => /usr/lib/x86_64-linux-gnu/libX11.so.6 (0x7fd30686c000)
libXi.so.6 => /usr/lib/x86_64-linux-gnu/libXi.so.6 (0x7fd30665c000)
libSM.so.6 => /usr/lib/x86_64-linux-gnu/libSM.so.6 (0x7fd306454000)
libICE.so.6 => /usr/lib/x86_64-linux-gnu/libICE.so.6 (0x7fd306239000)
libxcb-xkb.so.1 => /usr/lib/x86_64-linux-gnu/libxcb-xkb.so.1 
(0x7fd30601d000)
libxcb-render-util.so.0 => 
/usr/lib/x86_64-linux-gnu/libxcb-render-util.so.0 (0x7fd305e19000)
libxcb-render.so.0 => /usr/lib/x86_64-linux-gnu/libxcb-render.so.0 
(0x7fd305c0c000)
libxcb-sync.so.1 => /usr/lib/x86_64-linux-gnu/libxcb-sync.so.1 
(0x7fd305a05000)
libxcb-xfixes.so.0 => /usr/lib/x86_64-linux-gnu/libxcb-xfixes.so.0 
(0x7fd3057fd000)
libxcb-xinerama.so.0 => /usr/lib/x86_64-linux-gnu/libxcb-xinerama.so.0 
(0x7fd3055fa000)
libxcb-randr.so.0 => /usr/lib/x86_64-linux-gnu/libxcb-randr.so.0 
(0x7fd3053ea000)
libxcb-image.so.0 => /usr/lib/x86_64-linux-gnu/libxcb-image.so.0 
(0x7fd3051e5000)
libxcb-shm.so.0 => /usr/lib/x86_64-linux-gnu/libxcb-shm.so.0 
(0x7fd304fe2000)
libxcb-keysyms.so.1 => /usr/lib/x86_64-linux-gnu/libxcb-keysyms.so.1 
(0x7fd304ddf000)
libxcb-icccm.so.4 => /usr/lib/x86_64-linux-gnu/libxcb-icccm.so.4 
(0x7fd304bda000)
libxcb.so.1 => /usr/lib/x86_64-linux-gnu/libxcb.so.1 (0x7fd3049b2000)
libxcb-shape.so.0 => /usr/lib/x86_64-linux-gnu/libxcb-shape.so.0 
(0x7fd3047ae000)
libxkbcommon-x11.so.0 => /usr/lib/x86_64-linux-gnu/libxkbcommon-x11.so.0 
(0x7fd3045a6000)
libxkbcommon.so.0 => /usr/lib/x86_64-linux-gnu/libxkbcommon.so.0 
(0x7fd304367000)
libm.so.6 => /lib/x86_64-linux-gnu/libm.so.6 (0x7fd303fc9000)
libgcc_s.so.1 => /lib/x86_64-linux-gnu/libgcc_s.so.1 (0x7fd303db1000)
libGL.so.1 => /usr/lib/x86_64-linux-gnu/libGL.so.1 (0x7fd303b25000)
libz.so.1 => /lib/x86_64-linux-gnu/libz.

[Bug 1765001] Re: memcheck-amd64-linux crashed with SIGILL during valgrind --leak-check of my binary

2018-04-18 Thread Thomas A. F. Thorne

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

Interesting... I installed the valgrind-dbg package and I no longer get
an error report when I attempt to recreate the problem.


Before adding debug this was the output: 

$ ./runmysmoketests.sh "valgrind --leak-check=yes -v ./dmcp-debug"
Begining the smoke tests
nc: Address already in use
==4182== Memcheck, a memory error detector
==4182== Copyright (C) 2002-2015, and GNU GPL'd, by Julian Seward et al.
==4182== Using Valgrind-3.11.0 and LibVEX; rerun with -h for copyright info
==4182== Command: ./dmcp-debug
==4182== 
--4182-- Valgrind options:
--4182----leak-check=yes
--4182---v
--4182-- Contents of /proc/version:
--4182--   Linux version 4.13.0-38-generic (buildd@lgw01-amd64-027) (gcc 
version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.9)) #43~16.04.1-Ubuntu SMP 
Wed Mar 14 17:48:43 UTC 2018
--4182-- 
--4182-- Arch and hwcaps: AMD64, LittleEndian, 
amd64-cx16-lzcnt-rdtscp-sse3-avx-avx2-bmi
--4182-- Page sizes: currently 4096, max supported 4096
--4182-- Valgrind library directory: /usr/lib/valgrind
--4182-- Reading syms from /home/thomas/work/src/dmcp/dmcp-debug
--4182-- Reading syms from /lib/x86_64-linux-gnu/ld-2.23.so
--4182--   Considering /lib/x86_64-linux-gnu/ld-2.23.so ..
--4182--   .. CRC mismatch (computed aa979a42 wanted 9019bbb7)
--4182--   Considering /usr/lib/debug/lib/x86_64-linux-gnu/ld-2.23.so ..
--4182--   .. CRC is valid
--4182-- Reading syms from /usr/lib/valgrind/memcheck-amd64-linux
--4182--   Considering /usr/lib/valgrind/memcheck-amd64-linux ..
--4182--   .. CRC mismatch (computed eea41ea9 wanted 2009db78)
--4182--object doesn't have a symbol table
--4182--object doesn't have a dynamic symbol table
--4182-- Scheduler: using generic scheduler lock implementation.
--4182-- Reading suppressions file: /usr/lib/valgrind/default.supp
==4182== embedded gdbserver: reading from 
/tmp/vgdb-pipe-from-vgdb-to-4182-by-thomas-on-???
==4182== embedded gdbserver: writing to   
/tmp/vgdb-pipe-to-vgdb-from-4182-by-thomas-on-???
==4182== embedded gdbserver: shared mem   
/tmp/vgdb-pipe-shared-mem-vgdb-4182-by-thomas-on-???
==4182== 
==4182== TO CONTROL THIS PROCESS USING vgdb (which you probably
==4182== don't want to do, unless you know exactly what you're doing,
==4182== or are doing some strange experiment):
==4182==   /usr/lib/valgrind/../../bin/vgdb --pid=4182 ...command...
==4182== 
==4182== TO DEBUG THIS PROCESS USING GDB: start GDB like this
==4182==   /path/to/gdb ./dmcp-debug
==4182== and then give GDB the following command
==4182==   target remote | /usr/lib/valgrind/../../bin/vgdb --pid=4182
==4182== --pid is optional if only one valgrind process is running
==4182== 
--4182-- REDIR: 0x401cfd0 (ld-linux-x86-64.so.2:strlen) redirected to 
0x3809e181 (???)
--4182-- Reading syms from /usr/lib/valgrind/vgpreload_core-amd64-linux.so
--4182--   Considering /usr/lib/valgrind/vgpreload_core-amd64-linux.so ..
--4182--   .. CRC mismatch (computed 2567ccf6 wanted 49420590)
--4182--object doesn't have a symbol table
--4182-- Reading syms from /usr/lib/valgrind/vgpreload_memcheck-amd64-linux.so
--4182--   Considering /usr/lib/valgrind/vgpreload_memcheck-amd64-linux.so ..
--4182--   .. CRC mismatch (computed 0e27c9a8 wanted ac585421)
--4182--object doesn't have a symbol table
==4182== WARNING: new redirection conflicts with existing -- ignoring it
--4182-- old: 0x0401cfd0 (strlen  ) R-> (.0) 0x3809e181 ???
--4182-- new: 0x0401cfd0 (strlen  ) R-> (2007.0) 0x04c31020 
strlen
--4182-- REDIR: 0x401b920 (ld-linux-x86-64.so.2:index) redirected to 0x4c30bc0 
(index)
--4182-- REDIR: 0x401bb40 (ld-linux-x86-64.so.2:strcmp) redirected to 0x4c320d0 
(strcmp)
--4182-- REDIR: 0x401dd30 (ld-linux-x86-64.so.2:mempcpy) redirected to 
0x4c35270 (mempcpy)
--4182-- Reading syms from /usr/lib/x86_64-linux-gnu/libstdc++.so.6.0.21
--4182--   Considering /usr/lib/x86_64-linux-gnu/libstdc++.so.6.0.21 ..
--4182--   .. CRC mismatch (computed 9adedc07 wanted 319402e2)
--4182--object doesn't have a symbol table
--4182-- Reading syms from /lib/x86_64-linux-gnu/libm-2.23.so
--4182--   Considering /lib/x86_64-linux-gnu/libm-2.23.so ..
--4182--   .. CRC mismatch (computed e8c3647b wanted c3efddac)
--4182--   Considering /usr/lib/debug/lib/x86_64-linux-gnu/libm-2.23.so ..
--4182--   .. CRC is valid
--4182-- Reading syms from /lib/x86_64-linux-gnu/libgcc_s.so.1
--4182--   Considering /lib/x86_64-linux-gnu/libgcc_s.so.1 ..
--4182--   .. CRC mismatch (computed b9a68419 wanted 29d51b00)
--4182--object doesn't have a symbol table
--4182-- Reading syms from /lib/x86_64-linux-gnu/libpthread-2.23.so
--4182--   Considering 
/usr/lib/debug/.build-id/ce/17e023542265fc11d9bc8f534bb4f070493d30.debug ..
--4182--   .. build-id is valid
--4182-- Reading syms from /lib/x86_64-linux-gnu/libc-2.23.so
--4182--   Considering /lib/x86_64-linux-gnu/libc-2.23.so ..
--4182--   .. CRC mismatch (compute

[Bug 1765001] Re: memcheck-amd64-linux crashed with SIGILL during valgrind --leak-check of my binary

2018-04-18 Thread Thomas A. F. Thorne

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

Closest upstream I came up with was
https://bugs.kde.org/show_bug.cgi?id=387940

I cannot confirm if bug #1301850 is a duplicate or not as I cannot view
the private bug.

** Bug watch added: KDE Bug Tracking System #387940
   https://bugs.kde.org/show_bug.cgi?id=387940

** Also affects: valgrind via
   https://bugs.kde.org/show_bug.cgi?id=387940
   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/1765001

Title:
  memcheck-amd64-linux crashed with SIGILL during valgrind --leak-check
  of my binary

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

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

[Bug 1748787] Re: pitivi crashed with AttributeError in _create_next_thumb(): 'NoneType' object has no attribute 'seek'

2018-08-29 Thread Thomas A. F. Thorne

I was not able to complete a render after this crash.  I did not try
reloading the program and trying again.

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

Title:
  pitivi crashed with AttributeError in _create_next_thumb(): 'NoneType'
  object has no attribute 'seek'

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

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

[Bug 1784358] Re: Eclipse not starting with org.eclipse.equinox.launcher.Main.main java.lang.ClassNotFoundException being issued after updgrade to 18.04

2018-07-31 Thread Thomas A. F. Thorne

I can confirm that downloading the Eclipse installer from the main
website: http://www.eclipse.org/downloads/ executing it as myself and
then selecting the C/C++ option got me a working copy of Eclipse
installed.  That is a successful work around until the packaged version
is fixed.


When I ran the install I did see some errors that I will bring up with the 
Eclipse team, if I can work out how:

:~/Downloads/eclipse/eclipse-inst-linux64/eclipse-installer$ sudo 
./eclipse-inst 
[sudo] password for thomas: 
WARNING: An illegal reflective access operation has occurred
WARNING: Illegal reflective access by org.eclipse.emf.ecore.xmi.impl.XMLHandler 
(file:/home/thomas/Downloads/eclipse/eclipse-inst-linux64/eclipse-installer/plugins/org.eclipse.emf.ecore.xmi_2.13.0.v20170609-0707.jar)
 to method 
com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser$LocatorProxy.getEncoding()
WARNING: Please consider reporting this to the maintainers of 
org.eclipse.emf.ecore.xmi.impl.XMLHandler
WARNING: Use --illegal-access=warn to enable warnings of further illegal 
reflective access operations
WARNING: All illegal access operations will be denied in a future release

(SWT:17278): IBUS-WARNING **: 14:26:33.796: The owner of
/home/thomas/.config/ibus/bus is not root!

(SWT:17278): GLib-CRITICAL **: 14:26:38.153: Source ID 409 was not found when 
attempting to remove it
:~/Downloads/eclipse/eclipse-inst-linux64/eclipse-installer$ ./eclipse-inst 
WARNING: An illegal reflective access operation has occurred
WARNING: Illegal reflective access by org.eclipse.emf.ecore.xmi.impl.XMLHandler 
(file:/home/thomas/Downloads/eclipse/eclipse-inst-linux64/eclipse-installer/plugins/org.eclipse.emf.ecore.xmi_2.13.0.v20170609-0707.jar)
 to method 
com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser$LocatorProxy.getEncoding()
WARNING: Please consider reporting this to the maintainers of 
org.eclipse.emf.ecore.xmi.impl.XMLHandler
WARNING: Use --illegal-access=warn to enable warnings of further illegal 
reflective access operations
WARNING: All illegal access operations will be denied in a future release

(SWT:17498): GLib-CRITICAL **: 14:27:23.976: Source ID 5293 was not
found when attempting to remove it

(SWT:17498): GLib-CRITICAL **: 14:27:24.432: Source ID 5445 was not
found when attempting to remove it

(SWT:17498): GLib-CRITICAL **: 14:27:25.951: Source ID 5614 was not found when 
attempting to remove it
[Fatal Error] :539:7: XML document structures must start and end within the 
same entity.

However despite the above it did seem to install fine.

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

Title:
  Eclipse not starting with org.eclipse.equinox.launcher.Main.main
  java.lang.ClassNotFoundException being issued after updgrade to 18.04

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

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

[Bug 1784358] Re: Eclipse not starting with org.eclipse.equinox.launcher.Main.main java.lang.ClassNotFoundException being issued after updgrade to 18.04

2018-07-31 Thread Thomas A. F. Thorne

I have raised https://bugs.eclipse.org/bugs/show_bug.cgi?id=537526 to
cover the installer issue.  There are similar bugs marked as fixed for
the main Eclipse code, but as this is still visible and relates to the
installer, not the main binary, I raised a new bug.

That is probably all from me for now.  I shall await news of an updated
package to test out or some instructions of other things to try.

** Bug watch added: Eclipse bugs #537526
   https://bugs.eclipse.org/bugs/show_bug.cgi?id=537526

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

Title:
  Eclipse not starting with org.eclipse.equinox.launcher.Main.main
  java.lang.ClassNotFoundException being issued after updgrade to 18.04

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

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

[Bug 1785249] Re: git-cola crashed with SIGABRT

2018-08-06 Thread Thomas A. F. Thorne

I cannot work out how to install those missing debug symbols.  Looking
for -dbg or -debug named packages leads me to a dead end.

More mooching about the internet lead me to the suggestion of setting
export QT_DEBUG_PLUGINS=1

Then running my failing program again to see a more detailed output.

$ export QT_DEBUG_PLUGINS=1
$ git-cola
QFactoryLoader::QFactoryLoader() checking directory path "/usr/bin/platforms" 
...
QFactoryLoader::QFactoryLoader() looking at "/usr/bin/platforms/libqeglfs.so"
Found metadata in lib 
/usr/lib/x86_64-linux-gnu/qt5/plugins/platforms/libqeglfs.so, metadata=
{
"IID": "org.qt-project.Qt.QPA.QPlatformIntegrationFactoryInterface.5.3",
"MetaData": {
"Keys": [
"eglfs"
]
},
"className": "QEglFSIntegrationPlugin",
"debug": false,
"version": 329989
}


..


Got keys from plugin meta data ("xcb")
Cannot load library /usr/lib/x86_64-linux-gnu/qt5/plugins/platforms/libqxcb.so: 
(/usr/lib/x86_64-linux-gnu/libQt5XcbQpa.so.5: symbol 
_ZNK15QPlatformWindow15safeAreaMarginsEv version Qt_5_PRIVATE_API not defined 
in file libQt5Gui.so.5 with link time reference)
QLibraryPrivate::loadPlugin failed on 
"/usr/lib/x86_64-linux-gnu/qt5/plugins/platforms/libqxcb.so" : "Cannot load 
library /usr/lib/x86_64-linux-gnu/qt5/plugins/platforms/libqxcb.so: 
(/usr/lib/x86_64-linux-gnu/libQt5XcbQpa.so.5: symbol 
_ZNK15QPlatformWindow15safeAreaMarginsEv version Qt_5_PRIVATE_API not defined 
in file libQt5Gui.so.5 with link time reference)"
This application failed to start because it could not find or load the Qt 
platform plugin "xcb"
in "".

Available platform plugins are: eglfs, linuxfb, minimal, minimalegl,
offscreen, vnc, wayland-egl, wayland, wayland-xcomposite-egl, wayland-
xcomposite-glx, xcb.

Reinstalling the application may fix this problem.
Aborted (core dumped)


I cannot find any helpful solutions based on that extra output.

I am not certain there is much maintenance of the package done under Ubuntu.  
Some of what I was reading suggested it was to do with the Qt packaging of an 
application (or possible of Qt). 
 Raised a bug on the project page as a result of those statements 
https://github.com/git-cola/git-cola/issues/869

** Bug watch added: github.com/git-cola/git-cola/issues #869
   https://github.com/git-cola/git-cola/issues/869

** Information type changed from Private to Public

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

Title:
  git-cola crashed with SIGABRT

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/git-cola/+bug/1785249/+subscriptions

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

[Bug 1785249] Re: git-cola crashed with SIGABRT

2018-08-06 Thread Thomas A. F. Thorne

Set to public as I did not see anything sensitive in the logs.

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

Title:
  git-cola crashed with SIGABRT

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/git-cola/+bug/1785249/+subscriptions

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

[Bug 1784358] Re: Eclipse not starting with org.eclipse.equinox.launcher.Main.main java.lang.ClassNotFoundException being issued after updgrade to 18.04

Reviewing the Debian equivalent people have suggested that:

$ sudo apt-get install --reinstall libequinox-osgi-java

Could resolve the issue.  Although some people note that it does not
help.  Others have recommended completely removing Eclipse as installed
through apt and instead using the version supplied directly on the
Eclipse CDT webpage https://www.eclipse.org/cdt/

I shall try both solutions this afternoon if there are no alternatives
suggested that people would like me to try.

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

** Also affects: eclipse (Debian) via
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=891956
   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/1784358

Title:
  Eclipse not starting with org.eclipse.equinox.launcher.Main.main
  java.lang.ClassNotFoundException being issued after updgrade to 18.04

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

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

[Bug 1784358] [NEW] Eclipse not starting with org.eclipse.equinox.launcher.Main.main java.lang.ClassNotFoundException being issued after updgrade to 18.04

Public bug reported:

I upgraded from 16.04 to 18.04 on Friday.  Following some reboots and
updates this morning I am now unable to start the Eclipse IDE.  This was
working before the upgrade.

I have the C++ developer support added to Eclipse.  To the best of my
memory (and ability to interrogate apt) it is all installed from the
Ubuntu repositories.

When I click the Eclipse launcher pinned to my side bat I get an error message 
from Eclipse that reads:
An error has occurred.  See the log file
/home/thomas/.eclipse/org.eclipse.platform_3.8_155965261/configuration/1532947738216.log

Viewing the log file I see:
!SESSION Mon Jul 30 11:48:58 BST 2018 --
!ENTRY org.eclipse.equinox.launcher 4 0 2018-07-30 11:48:58.229
!MESSAGE Exception launching the Eclipse Platform:
!STACK
java.lang.ClassNotFoundException: 
org.eclipse.core.runtime.adaptor.EclipseStarter
at java.base/java.net.URLClassLoader.findClass(URLClassLoader.java:466)
at java.base/java.lang.ClassLoader.loadClass(ClassLoader.java:566)
at java.base/java.lang.ClassLoader.loadClass(ClassLoader.java:499)
at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:626)
at org.eclipse.equinox.launcher.Main.basicRun(Main.java:584)
at org.eclipse.equinox.launcher.Main.run(Main.java:1438)
at org.eclipse.equinox.launcher.Main.main(Main.java:1414)

This is easily repeatable.

Some internet searching suggests this problem is present upstream as
there is a Debian bug that looks similar: https://bugs.debian.org/cgi-
bin/bugreport.cgi?bug=891956

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: eclipse 3.8.1-11
ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18
Uname: Linux 4.15.0-29-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.2
Architecture: amd64
Date: Mon Jul 30 11:43:38 2018
InstallationDate: Installed on 2017-11-16 (255 days ago)
InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801)
PackageArchitecture: all
ProcEnviron:
 LANGUAGE=en_GB:en
 TERM=xterm-256color
 PATH=(custom, no user)
 LANG=en_GB.UTF-8
 SHELL=/bin/bash
SourcePackage: eclipse
UpgradeStatus: Upgraded to bionic on 2018-07-27 (3 days ago)

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

** Affects: eclipse (Debian)
 Importance: Unknown
 Status: Unknown


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

Title:
  Eclipse not starting with org.eclipse.equinox.launcher.Main.main
  java.lang.ClassNotFoundException being issued after updgrade to 18.04

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

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

[Bug 1784358] Re: Eclipse not starting with org.eclipse.equinox.launcher.Main.main java.lang.ClassNotFoundException being issued after updgrade to 18.04

Reinstalling Eclipse and Eclipse C/C++ Development Tooling also did not
change the error.

$ sudo apt-get install --reinstall eclipse eclipse-cdt g++
Reading package lists... Done
Building dependency tree   
Reading state information... Done
0 to upgrade, 0 to newly install, 3 reinstalled, 0 to remove and 1 not to 
upgrade.
Need to get 37.5 MB of archives.
After this operation, 0 B of additional disk space will be used.
Get:1 http://gb.archive.ubuntu.com/ubuntu bionic/universe amd64 eclipse all 
3.8.1-11 [16.1 kB]
Get:2 http://gb.archive.ubuntu.com/ubuntu bionic/universe amd64 eclipse-cdt all 
8.6.0-2 [37.5 MB]
Get:3 http://gb.archive.ubuntu.com/ubuntu bionic/main amd64 g++ amd64 
4:7.3.0-3ubuntu2 [1,576 B]   
Fetched 37.5 MB in 6s (5,987 kB/s)  
   
(Reading database ... 344165 files and directories currently installed.)
Preparing to unpack .../eclipse_3.8.1-11_all.deb ...
Unpacking eclipse (3.8.1-11) over (3.8.1-11) ...
Preparing to unpack .../eclipse-cdt_8.6.0-2_all.deb ...
Unpacking eclipse-cdt (8.6.0-2) over (8.6.0-2) ...
Preparing to unpack .../g++_4%3a7.3.0-3ubuntu2_amd64.deb ...
Unpacking g++ (4:7.3.0-3ubuntu2) over (4:7.3.0-3ubuntu2) ...
Processing triggers for man-db (2.8.3-2) ...
Setting up g++ (4:7.3.0-3ubuntu2) ...
Setting up eclipse (3.8.1-11) ...
Setting up eclipse-cdt (8.6.0-2) ...

I shall try removing Eclipse using apt and installing from the website
instread.

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

Title:
  Eclipse not starting with org.eclipse.equinox.launcher.Main.main
  java.lang.ClassNotFoundException being issued after updgrade to 18.04

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

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

[Bug 1784358] Re: Eclipse not starting with org.eclipse.equinox.launcher.Main.main java.lang.ClassNotFoundException being issued after updgrade to 18.04

$ sudo apt-get install --reinstall libequinox-osgi-java

Resulted in no change.  The problem presented as before.

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

Title:
  Eclipse not starting with org.eclipse.equinox.launcher.Main.main
  java.lang.ClassNotFoundException being issued after updgrade to 18.04

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

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

[Bug 1780391] Re: Mouse Begins To Work In Jumpy Horizontal Steps Then Stops Working

That is interesting.  The original USB mouse is working OK now but the
new mouse I added is not.  I shall try swapping over the USB ports to
which they are attached.  Maybe I have a USB port that just failed.

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

Title:
  Mouse Begins To Work In Jumpy Horizontal Steps Then Stops Working

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

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

[Bug 1780391] Re: Mouse Begins To Work In Jumpy Horizontal Steps Then Stops Working

Changing USB port has not got the new non-working mouse to start
working.

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

Title:
  Mouse Begins To Work In Jumpy Horizontal Steps Then Stops Working

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

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

[Bug 1780391] [NEW] Mouse Begins To Work In Jumpy Horizontal Steps Then Stops Working

Public bug reported:

When I logged in to my locked PC this morning the mouse began behaving
strangely.  It would only move to one of several vertical points if I
made a violent motion.  It seemed to move left to right as normal.

To try and solve this I unplugged the USB connection and put it back
into the same slot.  This resulted in the optical USB mouse not working
at all.  I tried to move the USB connection to another slot but it still
would not work.  I fetched a known working USB mouse from another PC and
plugged it in.  That still would not work.

Having got access to another PC I did an internet search for possible
solutions.  I found a post on askubntun.com that suggested the problem
lay in the fwupd package.  Rather than remove and kill that packaged as
suggested in the post; I thought I would try posting a bug report first
to see if any useful diagnostics come up that might resolve this.

I have a meeting starting soon.  If there are any further actions I
could take to diagnose this while the USB mouse is still not working,
please let me know as soon as possible.  When I return from the meeting
I will try the steps suggested on askubuntu.com question 768455 (which
also referes out to bugzilla redhat bug 1322259.


As if by magic I just knocked the mouse and it seems to be working again.  It 
was not working when I started the diagnostic and began typing this all out...

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: fwupd 0.8.3-0ubuntu3
ProcVersionSignature: Ubuntu 4.13.0-45.50~16.04.1-generic 4.13.16
Uname: Linux 4.13.0-45-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.18
Architecture: amd64
Date: Fri Jul  6 08:16:03 2018
InstallationDate: Installed on 2017-11-16 (231 days ago)
InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801)
ProcEnviron:
 LANGUAGE=en_GB:en
 TERM=xterm-256color
 PATH=(custom, no user)
 LANG=en_GB.UTF-8
 SHELL=/bin/bash
SourcePackage: fwupd
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug xenial

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

Title:
  Mouse Begins To Work In Jumpy Horizontal Steps Then Stops Working

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

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

[Bug 1780391] Re: Mouse Begins To Work In Jumpy Horizontal Steps Then Stops Working

It seems that I can click and scroll with the non-working mouse at
present.  I cannot move the pointer.

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

Title:
  Mouse Begins To Work In Jumpy Horizontal Steps Then Stops Working

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

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

[Bug 1780391] Re: Mouse Begins To Work In Jumpy Horizontal Steps Then Stops Working

Attaching dmesg output as dmesg.txt as it is rather long.

** Attachment added: "dmesg output captured after origonal mouse was working 
agian but new mouse still did not work"
   
https://bugs.launchpad.net/ubuntu/+source/fwupd/+bug/1780391/+attachment/5160315/+files/dmesg.txt

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

Title:
  Mouse Begins To Work In Jumpy Horizontal Steps Then Stops Working

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

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

[Bug 1780391] Re: Mouse Begins To Work In Jumpy Horizontal Steps Then Stops Working

More plugging an unplugging mice and now my original mouse is working in
the original USB port again.

In the RedHat bug they as for the output of `lsusb -v` and `dmesg`.  I
shall post those here while I have an easy way to copy and paste and
then move on.


thomas@thorne-ul-dt:~/work/pistache/build$ lsusb -v

Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Couldn't open device, some information will be missing
Device Descriptor:
  bLength18
  bDescriptorType 1
  bcdUSB   3.10
  bDeviceClass9 Hub
  bDeviceSubClass 0 Unused
  bDeviceProtocol 3 
  bMaxPacketSize0 9
  idVendor   0x1d6b Linux Foundation
  idProduct  0x0003 3.0 root hub
  bcdDevice4.13
  iManufacturer   3 
  iProduct2 
  iSerial 1 
  bNumConfigurations  1
  Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength   31
bNumInterfaces  1
bConfigurationValue 1
iConfiguration  0 
bmAttributes 0xe0
  Self Powered
  Remote Wakeup
MaxPower0mA
Interface Descriptor:
  bLength 9
  bDescriptorType 4
  bInterfaceNumber0
  bAlternateSetting   0
  bNumEndpoints   1
  bInterfaceClass 9 Hub
  bInterfaceSubClass  0 Unused
  bInterfaceProtocol  0 Full speed (or root) hub
  iInterface  0 
  Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x81  EP 1 IN
bmAttributes3
  Transfer TypeInterrupt
  Synch Type   None
  Usage Type   Data
wMaxPacketSize 0x0004  1x 4 bytes
bInterval  12
bMaxBurst   0

Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Couldn't open device, some information will be missing
Device Descriptor:
  bLength18
  bDescriptorType 1
  bcdUSB   2.00
  bDeviceClass9 Hub
  bDeviceSubClass 0 Unused
  bDeviceProtocol 1 Single TT
  bMaxPacketSize064
  idVendor   0x1d6b Linux Foundation
  idProduct  0x0002 2.0 root hub
  bcdDevice4.13
  iManufacturer   3 
  iProduct2 
  iSerial 1 
  bNumConfigurations  1
  Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength   25
bNumInterfaces  1
bConfigurationValue 1
iConfiguration  0 
bmAttributes 0xe0
  Self Powered
  Remote Wakeup
MaxPower0mA
Interface Descriptor:
  bLength 9
  bDescriptorType 4
  bInterfaceNumber0
  bAlternateSetting   0
  bNumEndpoints   1
  bInterfaceClass 9 Hub
  bInterfaceSubClass  0 Unused
  bInterfaceProtocol  0 Full speed (or root) hub
  iInterface  0 
  Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x81  EP 1 IN
bmAttributes3
  Transfer TypeInterrupt
  Synch Type   None
  Usage Type   Data
wMaxPacketSize 0x0004  1x 4 bytes
bInterval  12

Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Couldn't open device, some information will be missing
Device Descriptor:
  bLength18
  bDescriptorType 1
  bcdUSB   3.00
  bDeviceClass9 Hub
  bDeviceSubClass 0 Unused
  bDeviceProtocol 3 
  bMaxPacketSize0 9
  idVendor   0x1d6b Linux Foundation
  idProduct  0x0003 3.0 root hub
  bcdDevice4.13
  iManufacturer   3 
  iProduct2 
  iSerial 1 
  bNumConfigurations  1
  Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength   31
bNumInterfaces  1
bConfigurationValue 1
iConfiguration  0 
bmAttributes 0xe0
  Self Powered
  Remote Wakeup
MaxPower0mA
Interface Descriptor:
  bLength 9
  bDescriptorType 4
  bInterfaceNumber0
  bAlternateSetting   0
  bNumEndpoints   1
  bInterfaceClass 9 Hub
  bInterfaceSubClass  0 Unused
  bInterfaceProtocol  0 Full speed (or root) hub
  iInterface  0 
  Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x81  EP 1 IN
bmAttributes3
  T

[Bug 1780391] Re: Mouse Begins To Work In Jumpy Horizontal Steps Then Stops Working

2018-07-09 Thread Thomas A. F. Thorne

As requested I have tried to repeat the problem under Ubuntu 18.04.  I
did see the same behaviour so I logged a new bug report for Ubuntu 18.04
to match this 16.04 one.  The new report is under bug 1780731.  The
requested file is attached to that report.

While writing up that report I checked the hardware against a Windows 10
laptop I have on my desk.  I get the same behaviour so I guess my root
cause was a hardware failure in one of the mice.  If there are any
obvious problems in the logs, they are more likely due to the poor
handling of an error case.

As this is triggered by a hardware fault; I am happy for both this
ticket and bug #1780731 to be closed unless there is work needed to make
the handling of errors more robust.

Many Thanks, Tom

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

Title:
  Mouse Begins To Work In Jumpy Horizontal Steps Then Stops Working

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

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

[Bug 1780731] Re: USB Mouse stopped working. Tried live image of lates Ubuntu on same machine and same result.

2018-07-09 Thread Thomas A. F. Thorne

I was asked to run fwupd in verbose mode and submit the log.

Attached is the result of

sudo systemctl stop fwupd.service
sudo /usr/lib/fwupd/fwupd -v

** Attachment added: "fwupd -v log"
   
https://bugs.launchpad.net/ubuntu/+source/fwupd/+bug/1780731/+attachment/5161271/+files/fwupd-v.txt

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

Title:
  USB Mouse stopped working.  Tried live image of lates Ubuntu on same
  machine and same result.

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

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

[Bug 1780731] [NEW] USB Mouse stopped working. Tried live image of lates Ubuntu on same machine and same result.

2018-07-09 Thread Thomas A. F. Thorne

Public bug reported:

I had already filed bug 1780391 and was asked to try 18.04 instead of
16.04 to see if the problem was repeatable.  I seem to have the same
symptoms as with 16.04.

First thing this morning I logged into Ubuntu 16.04 and noticed that my
mouse worked at the login prompt but not once I had logged in.  As
before I have a R.A.T.7 CYBORG Dynnamic Ergonomics mouse and a more
generic Sum Vision Optical Mouse plugged into my PC.  I then restarted
the PC and noticed while in the BIOS Boot menu that neither mouse worked
there, until I moved one mouse onto a different surface.

It seems that the Sum Vision mouse will not sense movement on my desk
any longer.  When placed on the back of a Black n' Red hard cover note
book the Sum Vision mouse will move the pointer again.  On neither
surface will the RAT 7 work.  Clicking and mouse wheel scrolling seem
fine on both mice.

As already mentioned on bug #1780391 both mouse were working fine before
Friday.  Unless a new cleaning fluid is being used on these office desks
or some hardware has failed, I cannot explain the change in behaviour.
I find it hard to believe that I have two intermittent mice, especially
as the semi-working one is OK on my Windows machine.

Which lead me to realise I could check both mice on the Windows laptop I
have.  I get the same behaviour.  The optical motion sensor on the
CYBORG RAT mouse must have just died.  If it sent some strange messages,
that might be what caused any observed problems with the mouse interafce
software in Ubunut.  It is strange that this failed part way though use
and that I managed to pick up a mouse that does not work on my desk (but
does work on an identical work surface in the next room) but that is the
odds I guess.

Sorry for any confusion.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: fwupd 1.0.6-2
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
CasperVersion: 1.394
Date: Mon Jul  9 07:19:22 2018
LiveMediaBuild: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: fwupd
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: fwupd (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/1780731

Title:
  USB Mouse stopped working.  Tried live image of lates Ubuntu on same
  machine and same result.

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

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

[Bug 1748844] Re: hud-service crash with qmessageLogger::fatal() reported at login

2018-03-05 Thread Thomas A. F. Thorne

Occurred again this morning and an automated bug report brought me back
here.

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

Title:
  hud-service crash with qmessageLogger::fatal() reported at login

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

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

[Bug 1748844] Re: hud-service crash with qmessageLogger::fatal() reported at login

2018-03-05 Thread Thomas A. F. Thorne

This morning the second automated bug report prompted me to create
+bug1753393

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

Title:
  hud-service crash with qmessageLogger::fatal() reported at login

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

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

[Bug 1575248] Re: "AppStream cache update completed, but some metadata was ignored due to errors." on "sudo apt-get update"

I started seeing this message: 
 AppStream cache update completed, but some metadata was ignored due to errors.
on one machine on the 23rd November 2016.  I would expect this to be a seperate 
issue.   I cannot reproduce it right now, if I am able to do so later I will 
try and raise 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/1575248

Title:
  "AppStream cache update completed, but some metadata was ignored due
  to errors." on "sudo apt-get update"

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

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

[Bug 1644498] [NEW] apt-get update returns "AppStream cache update completed, but some metadata was ignored due to errors." periodically

Public bug reported:

Periodically I get emails from a machine with the subject:

Cron  if [ -x /etc/munin/plugins/apt_all ]; then
/etc/munin/plugins/apt_all update 7200 12 >/dev/null; elif [ -x
/etc/munin/plugins/apt ]; then /etc/munin/plugins/apt update 7200 12
>/dev/null; fi

And a body of:

AppStream cache update completed, but some metadata was ignored due to
errors.


I have a machine monitored by Munin.  One of the plugins used on that machine 
is /etc/munin/plugins/apt which periodically counts the number of packets that 
can be upgraded.  This is achieved by a crontab entry installed from the 
package which looks like this:

#
# cron-jobs for munin-node
#

MAILTO=root

# If the APT plugin is enabled, update packages databases approx. once
# an hour (12 invokations an hour, 1 in 12 chance that the update will
# happen), but ensure that there will never be more than two hour (7200
# seconds) interval between updates..
*/5 * * * * root if [ -x /etc/munin/plugins/apt_all ]; then 
/etc/munin/plugins/apt_all update 7200 12 >/dev/null; elif [ -x 
/etc/munin/plugins/apt ]; then /etc/munin/plugins/apt update 7200 12 
>/dev/null; fi


For many months everything has been running smoothly.  On the 23rd November 
2016 I started getting the "AppStream cache update completed, but some metadata 
was ignored due to errors." messages at a rate of about ten a day.  


I did a quick Google search which turned up a handful of bugs from earlier this 
year, such as 
Bug1575248.  That is marked as Fixed Released though, so I am raising this new 
bug.

If there are any further diagnostic details I can provide, please let me
know.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: appstream 0.9.4-1ubuntu1
ProcVersionSignature: Ubuntu 4.4.0-47.68-generic 4.4.24
Uname: Linux 4.4.0-47-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
Date: Thu Nov 24 09:57:18 2016
InstallationDate: Installed on 2013-05-08 (1295 days ago)
InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130508)
JournalErrors:
 -- Logs begin at Wed 2016-11-23 19:25:01 GMT, end at Thu 2016-11-24 09:57:24 
GMT. --
 Nov 24 02:22:17 hostname systemd-tmpfiles[27330]: 
[/usr/lib/tmpfiles.d/var.conf:14] Duplicate line for path "/var/log", ignoring.
ProcEnviron:
 TERM=xterm-256color
 SHELL=/bin/bash
 PATH=(custom, no user)
 LANG=en_GB.UTF-8
 LANGUAGE=en_GB:en
SourcePackage: appstream
UpgradeStatus: Upgraded to xenial on 2016-08-24 (91 days ago)

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


** Tags: amd64 apport-bug xenial

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

Title:
  apt-get update returns "AppStream cache update completed, but some
  metadata was ignored due to errors." periodically

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

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

[Bug 1575248] Re: "AppStream cache update completed, but some metadata was ignored due to errors." on "sudo apt-get update"

The error message popped out again for me just now.  I still cannot get
it to reproduce reliably but I have raised Bugs1644498 to start
diagnosis.

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

Title:
  "AppStream cache update completed, but some metadata was ignored due
  to errors." on "sudo apt-get update"

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

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

[Bug 1644498] Re: apt-get update returns "AppStream cache update completed, but some metadata was ignored due to errors." periodically

Thank you.  I could not figure out which combination of commands to send
appsteamcli. I had tried status and validate without success.  Here is
the requested output:

manager@Jenkins:~$ sudo appstreamcli refresh --verbose --force
[sudo] password for manager: 
** (appstreamcli:32754): DEBUG: Refreshing AppStream cache
** (appstreamcli:32754): DEBUG: Reading: 
/usr/share/app-info/xmls/org.freedesktop.fwupd.xml
** (appstreamcli:32754): DEBUG: Reading: 
/var/lib/app-info/yaml/gb.archive.ubuntu.com_ubuntu_dists_xenial_main_dep11_Components-amd64.yml.gz
** (appstreamcli:32754): DEBUG: Reading: 
/var/lib/app-info/yaml/gb.archive.ubuntu.com_ubuntu_dists_xenial_restricted_dep11_Components-amd64.yml.gz
** (appstreamcli:32754): DEBUG: Reading: 
/var/lib/app-info/yaml/gb.archive.ubuntu.com_ubuntu_dists_xenial_universe_dep11_Components-amd64.yml.gz
** (appstreamcli:32754): DEBUG: Reading: 
/var/lib/app-info/yaml/security.ubuntu.com_ubuntu_dists_xenial-security_main_dep11_Components-amd64.yml.gz
** (appstreamcli:32754): DEBUG: Reading: 
/var/lib/app-info/yaml/security.ubuntu.com_ubuntu_dists_xenial-security_restricted_dep11_Components-amd64.yml.gz
** (appstreamcli:32754): DEBUG: Reading: 
/var/lib/app-info/yaml/security.ubuntu.com_ubuntu_dists_xenial-security_universe_dep11_Components-amd64.yml.gz
** (appstreamcli:32754): DEBUG: Reading: 
/var/lib/app-info/yaml/security.ubuntu.com_ubuntu_dists_xenial-security_multiverse_dep11_Components-amd64.yml.gz
** (appstreamcli:32754): DEBUG: Reading: 
/var/lib/app-info/yaml/gb.archive.ubuntu.com_ubuntu_dists_xenial_multiverse_dep11_Components-amd64.yml.gz
** (appstreamcli:32754): DEBUG: Reading: 
/var/lib/app-info/yaml/gb.archive.ubuntu.com_ubuntu_dists_xenial-updates_main_dep11_Components-amd64.yml.gz
** (appstreamcli:32754): DEBUG: Reading: 
/var/lib/app-info/yaml/gb.archive.ubuntu.com_ubuntu_dists_xenial-updates_restricted_dep11_Components-amd64.yml.gz
** (appstreamcli:32754): DEBUG: Reading: 
/var/lib/app-info/yaml/gb.archive.ubuntu.com_ubuntu_dists_xenial-updates_universe_dep11_Components-amd64.yml.gz
** (appstreamcli:32754): DEBUG: Reading: 
/var/lib/app-info/yaml/gb.archive.ubuntu.com_ubuntu_dists_xenial-updates_multiverse_dep11_Components-amd64.yml.gz
** (appstreamcli:32754): DEBUG: Reading: /var/cache/app-info/xmls/fwupd.xml
** (appstreamcli:32754): DEBUG: Detected colliding ids: plan.desktop was 
already added with the same priority.
** (appstreamcli:32754): DEBUG: Detected colliding ids: flcheckers.desktop was 
already added with the same priority.
** (appstreamcli:32754): DEBUG: Detected colliding ids: flblocks.desktop was 
already added with the same priority.
** (appstreamcli:32754): DEBUG: Detected colliding ids: flsudoku.desktop was 
already added with the same priority.
** (appstreamcli:32754): DEBUG: Replaced 'libreoffice-startcenter.desktop' with 
data of higher priority.
** (appstreamcli:32754): DEBUG: Replaced 'libreoffice-math.desktop' with data 
of higher priority.
** (appstreamcli:32754): DEBUG: Replaced 'eog.desktop' with data of higher 
priority.
** (appstreamcli:32754): DEBUG: Replaced 'display-im6.desktop' with data of 
higher priority.
** (appstreamcli:32754): DEBUG: Replaced 'libreoffice-draw.desktop' with data 
of higher priority.
** (appstreamcli:32754): DEBUG: Replaced 'libreoffice-impress.desktop' with 
data of higher priority.
** (appstreamcli:32754): DEBUG: Replaced 'display-im6.q16.desktop' with data of 
higher priority.
** (appstreamcli:32754): DEBUG: Replaced 'libreoffice-writer.desktop' with data 
of higher priority.
** (appstreamcli:32754): DEBUG: Replaced 'org.gnome.FileRoller.desktop' with 
data of higher priority.
** (appstreamcli:32754): DEBUG: Replaced 'libreoffice-base.desktop' with data 
of higher priority.
** (appstreamcli:32754): DEBUG: Replaced 'libreoffice-calc.desktop' with data 
of higher priority.
** (appstreamcli:32754): DEBUG: Replaced 'gimp.desktop' with data of higher 
priority.
** (appstreamcli:32754): DEBUG: Replaced 'chromium-browser.desktop' with data 
of higher priority.
** (appstreamcli:32754): DEBUG: Replaced 'tracker-preferences.desktop' with 
data of higher priority.
** (appstreamcli:32754): DEBUG: Replaced 'tracker-needle.desktop' with data of 
higher priority.
** (appstreamcli:32754): DEBUG: Detected colliding ids: eog.desktop was already 
added with a higher priority.
** (appstreamcli:32754): DEBUG: Replaced 'update-manager.desktop' with data of 
higher priority.
** (appstreamcli:32754): DEBUG: Replaced 'gnome-session-properties.desktop' 
with data of higher priority.
** (appstreamcli:32754): DEBUG: Replaced 'upstart-monitor.desktop' with data of 
higher priority.
** (appstreamcli:32754): DEBUG: Replaced 'fcitx-configtool.desktop' with data 
of higher priority.
** (appstreamcli:32754): DEBUG: Replaced 'fcitx.desktop' with data of higher 
priority.
** (appstreamcli:32754): DEBUG: Detected colliding ids: 
libreoffice-startcenter.desktop was already added with a higher priority.
** (appstreamcli:32754): DEBUG: Det

[Bug 1644498] Re: apt-get update returns "AppStream cache update completed, but some metadata was ignored due to errors." periodically

2016-11-25 Thread Thomas A. F. Thorne

> I think I found the issue, I'll prepare a patch.

That is great news.  Is there a work around I could try that would
silence the emails for a while?  Let me know if you would like me to try
out the updated binary.

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

Title:
  apt-get update returns "AppStream cache update completed, but some
  metadata was ignored due to errors." periodically

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

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

[Bug 1644498] Re: apt-get update returns "AppStream cache update completed, but some metadata was ignored due to errors." periodically

2016-11-25 Thread Thomas A. F. Thorne

Installing the fixed file is not really a work around but the error
piping would work.  I'll live with the noise for now and try to get the
updated package installed once it reaches xenial-backports.

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

Title:
  apt-get update returns "AppStream cache update completed, but some
  metadata was ignored due to errors." periodically

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

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

[Bug 1694391] [NEW] Following System Restart Trac Issues "Error: Unable to get database connection within 0 seconds" Message

2017-05-30 Thread Thomas A. F. Thorne

Public bug reported:

My Trac server is configured to automatically upgrade and reboot in the
early ours of the morrning.  This morning I found that it started
sending me emails like this:

Error: Unable to get database connection within 0 seconds. (OperationalError: 
could not connect to server: Connection refused
Is the server running on host "localhost" (::1) and accepting
TCP/IP connections on port 5432?
could not connect to server: Connection refused
Is the server running on host "localhost" (127.0.0.1) and accepting
TCP/IP connections on port 5432?
)

These were triggered by an hourly cron job that tries to synchronize changes 
from a git repository. 
 The command used is `/usr/local/bin/trac-admin /srv/trac/projects/gittrac/ 
repository sync  | /usr/bin/logger -t trac-admin_sync` 

Further to this the syslog shows the following error message:
May 30 02:25:06 trac Trac[main] ERROR: Internal Server Error: 
, referrer None#012Traceback (most recent call 
last):#012  File "/usr/local/lib/python2.7/dist-packages/trac/web/main.py", 
line 554, in _dispatch_request#012dispatcher.dispatch(req)#012  File 
"/usr/local/lib/python2.7/dist-packages/trac/web/main.py", line 247, in 
dispatch#012resp = chosen_handler.process_request(req)#012  File 
"/usr/local/lib/python2.7/dist-packages/trac/wiki/web_ui.py", line 131, in 
process_request#012page = WikiPage(self.env, pagename)#012  File 
"/usr/local/lib/python2.7/dist-packages/trac/wiki/model.py", line 49, in 
__init__#012self._fetch(name, version, db)#012  File 
"/usr/local/lib/python2.7/dist-packages/trac/wiki/model.py", line 68, in 
_fetch#012self.env.db_query(sql, args):#012  File 
"/usr/local/lib/python2.7/dist-packages/trac/db/api.py", line 124, in 
execute#012return db.execute(query, params)#012  File 
"/usr/local/lib/python2.7/dist-packages/trac/db/util.py", line 128, in 
execute#012cursor.execute(query, params if params is not None else [])#012  
File "/usr/local/lib/python2.7/dist-packages/trac/db/util.py", line 72, in 
execute#012return self.cursor.execute(sql_escape_percent(sql), 
args)#012OperationalError: terminating connection due to administrator 
command#012server closed the connection unexpectedly#012#011This probably means 
the server terminated abnormally#012#011before or while processing the 
request.#012OperationalError: terminating connection due to administrator 
command#012server closed the connection unexpectedly#012#011This probably means 
the server terminated abnormally#012#011before or while processing the request.
May 30 02:25:06 trac Trac[chrome] WARNING: Error with navigation contributor 
HudsonTracPlugin
May 30 02:25:06 trac Trac[chrome] WARNING: Error with navigation contributor 
RPCWeb
May 30 02:25:06 trac Trac[chrome] WARNING: Error with navigation contributor 
QueryModule
May 30 02:25:06 trac Trac[chrome] WARNING: Error with navigation contributor 
TicketModule
May 30 02:25:06 trac Trac[chrome] WARNING: Error with navigation contributor 
SearchModule
May 30 02:25:06 trac Trac[chrome] WARNING: Error with navigation contributor 
TicketStatsPlugin
May 30 02:25:06 trac Trac[chrome] WARNING: Error with navigation contributor 
AdminModule
May 30 02:25:06 trac Trac[chrome] WARNING: Error with navigation contributor 
ReportModule
May 30 02:25:06 trac Trac[chrome] WARNING: Error with navigation contributor 
RoadmapModule
May 30 02:25:06 trac Trac[chrome] WARNING: Error with navigation contributor 
TimelineModule
May 30 02:25:06 trac Trac[chrome] WARNING: Error with navigation contributor 
WikiModule
May 30 02:25:06 trac Trac[chrome] WARNING: Error with navigation contributor 
PDashboard
May 30 02:25:08 trac Trac[chrome] ERROR: Error during check of EMAIL_VIEW: 
TimeoutError: Unable to get database connection within 0 seconds. 
(OperationalError: could not connect to server: Connection refused#012#011Is 
the server running on host "localhost" (::1) and accepting#012#011TCP/IP 
connections on port 5432?#012could not connect to server: Connection 
refused#012#011Is the server running on host "localhost" (127.0.0.1) and 
accepting#012#011TCP/IP connections on port 5432?#012)
May 30 02:25:08 trac Trac[chrome] ERROR: Error during check of EMAIL_VIEW: 
TimeoutError: Unable to get database connection within 0 seconds. 
(OperationalError: could not connect to server: Connection refused#012#011Is 
the server running on host "localhost" (::1) and accepting#012#011TCP/IP 
connections on port 5432?#012could not connect to server: Connection 
refused#012#011Is the server running on host "localhost" (127.0.0.1) and 
accepting#012#011TCP/IP connections on port 5432?#012)

The above looks very similar to what is presented as a Warning and Trac
error when you try to visit the Trac webpage.


I have a feeling that I have seen this before.  In the past it was restarting 
the database or Trac service that resolved the issue I think.  Yes my notes 
from before say:
"There seems to be a postgresql

[Bug 1694391] Re: Following System Restart Trac Issues "Error: Unable to get database connection within 0 seconds" Message

2017-05-30 Thread Thomas A. F. Thorne

To resolve the issue all I needed to do was:
$ sudo service postgresql start

I guess there is something in the sequencing of service start going
wrong.  I will try and look into it more later.  I am not sure how Trac
is packaged, how this server is setup and as a result how much of all
this is a roll-your-own.  I only raised this bug to keep track on things
if this had all come out of a package upgrade in an odd way.

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

Title:
  Following System Restart Trac Issues "Error: Unable to get database
  connection within 0 seconds" Message

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

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

[Bug 1630516] Re: Logrotate doesn't clean old system logs, allowing them to fill the disk

2017-04-25 Thread Thomas A. F. Thorne

Running through on Xenial.

$ sudo apt-get install logrotate/xenial-proposed
Reading package lists... Done
Building dependency tree   
Reading state information... Done
Selected version '3.8.7-2ubuntu2.16.04.1' (Ubuntu:16.04/xenial-proposed 
[amd64]) for 'logrotate'
The following packages will be upgraded:
  logrotate
1 to upgrade, 0 to newly install, 0 to remove and 22 not to upgrade.
Need to get 37.8 kB of archives.
After this operation, 0 B of additional disk space will be used.
Get:1 http://archive.ubuntu.com/ubuntu xenial-proposed/main amd64 logrotate 
amd64 3.8.7-2ubuntu2.16.04.1 [37.8 kB]
Fetched 37.8 kB in 0s (639 kB/s) 
(Reading database ... 889765 files and directories currently installed.)
Preparing to unpack .../logrotate_3.8.7-2ubuntu2.16.04.1_amd64.deb ...
Unpacking logrotate (3.8.7-2ubuntu2.16.04.1) over (3.8.7-2ubuntu2) ...
Processing triggers for man-db (2.7.5-1) ...
Setting up logrotate (3.8.7-2ubuntu2.16.04.1) ...
$ cd /var/log/
$ sudo touch syslog.2
$ ls -l syslog*
-rw-r- 1 syslog adm  193861 Apr 25 15:48 syslog
-rw-r- 1 syslog adm  586698 Apr 25 07:35 syslog.1
-rw-r--r-- 1 root   root  0 Apr 25 15:48 syslog.2
-rw-r- 1 syslog adm   26955 Apr 24 07:35 syslog.2.gz
-rw-r- 1 syslog adm   26695 Apr 23 07:35 syslog.3.gz
-rw-r- 1 syslog adm   31307 Apr 22 07:35 syslog.4.gz
-rw-r- 1 syslog adm   32909 Apr 21 07:35 syslog.5.gz
-rw-r- 1 syslog adm   39182 Apr 20 07:35 syslog.6.gz
-rw-r- 1 syslog adm   27036 Apr 19 07:35 syslog.7.gz
Either things will fail overnight (well first thing tomorrow morning or all 
will be well.  I shall get back in touch soon.

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

Title:
  Logrotate doesn't clean old system logs, allowing them to fill the
  disk

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

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

[Bug 1630516] Re: Logrotate doesn't clean old system logs, allowing them to fill the disk

Looks to me like everything worked fine overnight.
$ ls -l /var/log/syslog*
-rw-r- 1 syslog adm   587351 Apr 26 12:10 /var/log/syslog
-rw-r- 1 syslog adm  1824727 Apr 26 07:38 /var/log/syslog.1
-rw-r--r-- 1 root   root   0 Apr 25 15:48 /var/log/syslog.2
-rw-r- 1 syslog adm37783 Apr 25 07:35 /var/log/syslog.2.gz
-rw-r- 1 syslog adm26955 Apr 24 07:35 /var/log/syslog.3.gz
-rw-r- 1 syslog adm26695 Apr 23 07:35 /var/log/syslog.4.gz
-rw-r- 1 syslog adm31307 Apr 22 07:35 /var/log/syslog.5.gz
-rw-r- 1 syslog adm32909 Apr 21 07:35 /var/log/syslog.6.gz
-rw-r- 1 syslog adm39182 Apr 20 07:35 /var/log/syslog.7.gz

The presence of the inconveniently named file looks to have been ignored
and the log rotations continued unabated.

> change the tag from verification-needed to verification-done

I have only verified this on Xenia so far.  I think that means I leave
the tags alone for now right?

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

Title:
  Logrotate doesn't clean old system logs, allowing them to fill the
  disk

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

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

[Bug 1245666] Re: Pidgin is creating zombies

Closed down Pidgin.  Waited a few seconds for all the defunct processes
to go away.  Restarted Pidgin.  Probably only a minute later before the
first defunct process has arrived.

I am signed into 4 IRC channels automatically on startup.  I have tried
to send my identify command to the NickServ but other than that I have
not made any chats yet.

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

Title:
  Pidgin is creating zombies

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

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

[Bug 1245666] Re: Pidgin is creating zombies

Well I am seeing something odd in Pidgin.

$ ps -elf | grep defunct | wc -l
121
$ ps -elf | grep defunct | grep pidgin | wc -l
120

(One of the 'defunct' hits is the grep)

$ pidgin --version
Pidgin 2.10.12 (libpurple 2.10.12)

I have IRC, and XMPP to GoogleMail (Hangouts / Talk) configured and
active in Pidgin at the moment.  Someone else mentioned Google Hangouts
and I can easily live without for a few days to see if the problem goes
away.  Account Disabled.

I also have Facebook (XMPP), Skype (D-Bus) and Skype setup with Pidgin
but only the IRC and googlemail chat accounts were enabled when this
error was noticed.  I shall try closing Pidgin to clean up the defuncts.

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

Title:
  Pidgin is creating zombies

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

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

[Bug 1245666] Re: Pidgin is creating zombies

It has been noted on the developer site for Pidgin that 1 defunct is
normal for DNS lookups.
https://developer.pidgin.im/ticket/15617#comment:11

The rest I have seen might come from failed attempts to connect to chat
services.  https://developer.pidgin.im/ticket/15617#comment:13 mentions
you get one for every connect attempt.  I did have a network issue last
night that would have blocked IPv4 access for several hours.  That might
explain what i have seen.  If I get further defunct processes without
any signs of network disruption I will report back, else assume that it
is provoked by network issues.

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

Title:
  Pidgin is creating zombies

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

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

[Bug 1630516] Re: Logrotate doesn't clean old system logs, allowing them to fill the disk

Hi Christian, 
A more careful read through of the instructions you link to and I have spotted 
the required tag.  Now added that as requested.  I'll try to get the other two 
tested using lsc tomorrow.  
Tag now added.  

** Tags added: verification-done-xenial

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

Title:
  Logrotate doesn't clean old system logs, allowing them to fill the
  disk

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

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

[Bug 1688232] [NEW] Clicking 'Restart current capture' button while a capture is running results in 'No interface selected' error message instead of a capture restart

2017-05-04 Thread Thomas A. F. Thorne

Public bug reported:

Clicking 'Restart current capture' button while a capture is running
results in 'No interface selected' error message instead of a capture
restart.  You get a similar looking error message after having stopped a
running capture, then clicking the 'Start capturing packets' button.

This is quite a frustrating issue as hitting that restart button when I
re-run a test is a common part of my workflow.  There is a workaround in
that I can click the 'Capture options' button, setup the capture again
then click the 'Start' button in that new window.

I have a quick look about and this might already have been reported in
Debian under: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=812495
which may have been fixed.

The Wireshark project itself may have had this bug reported for the
Ubuntu platform in this mail thread: https://www.wireshark.org/lists
/wireshark-bugs/201511/msg01072.html which links back to this bug
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=11834 in the project
database.

That could mean all that needs to happen is a pull from upstream.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: wireshark 2.0.2+ga16e22e-1
ProcVersionSignature: Ubuntu 4.4.0-72.93-generic 4.4.49
Uname: Linux 4.4.0-72-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.5
Architecture: amd64
CurrentDesktop: Unity
Date: Thu May  4 12:20:41 2017
InstallationDate: Installed on 2015-03-12 (783 days ago)
InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 (20150218.1)
SourcePackage: wireshark
UpgradeStatus: No upgrade log present (probably fresh install)

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

** Affects: wireshark (Debian)
 Importance: Unknown
 Status: Unknown


** Tags: amd64 apport-bug xenial

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

** Also affects: wireshark (Debian) via
   http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=812495
   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/1688232

Title:
  Clicking 'Restart current capture' button while a capture is running
  results in 'No interface selected' error message instead of a capture
  restart

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

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

[Bug 798414] Re: update-initramfs should produce a more helpful error when there isn't enough free space

2016-09-20 Thread Thomas A. F. Thorne

I hit this today.  `df -h` confirmed my /boot was quite full (15MB
left).  Running `sudo purge-old-kernels` (from the bikeshed package)
cleared out some things and brought the free space on /boot up to 93MB.

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

Title:
  update-initramfs should produce a more helpful error when there isn't
  enough  free space

To manage notifications about this bug go to:
https://bugs.launchpad.net/initramfs-tools/+bug/798414/+subscriptions

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

[Bug 1692829] [NEW] Forgets Port And Baud Rate When Configuring

2017-05-23 Thread Thomas A. F. Thorne

Public bug reported:

GtkTerm always ends up presenting the first port (/dev/ttyS0 for me) and
the minimum port baud rate (9600) when you enter to the Configuration >
Port menu.  The Parity, Bits, Stopbits and Flow control settings are
retained from the current setting.  I feel it would be more intuitive if
either all the port settings were retained or if the default
configuration was loaded every time.

This frequently causes me to set /dev/ttyS0 at a speed of 9600 when I
wanted to make a small adjustment for the port I was already using at
the speed I was using it at.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: gtkterm 0.99.7~rc1-0.2ubuntu1
ProcVersionSignature: Ubuntu 4.4.0-72.93-generic 4.4.49
Uname: Linux 4.4.0-72-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.5
Architecture: amd64
CurrentDesktop: Unity
Date: Tue May 23 08:42:27 2017
InstallationDate: Installed on 2015-03-12 (802 days ago)
InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 (20150218.1)
SourcePackage: gtkterm
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug xenial

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

Title:
  Forgets Port And Baud Rate When Configuring

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

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

[Bug 1713004] [NEW] Temporary files left under /var/tmp by mkinitramfs

2017-08-25 Thread Thomas A. F. Thorne

Public bug reported:

I recently ran out of disk space on my / mount.  While looking for what
consumed the disk I noticed a large number (130) of directories with
names / paths beginning /var/tmp/mkinitramfs.  These directories seem to
be either ~103 MB or ~927 MB in size.  Many of these files are months
old, some are almost a year.

Having had a quick look about for an explanation as to why these files
are here and found Debian Bug #814345.  That explains that temporary
files are left behind by the initramfs-tools if something fails in the
process.  If this is the cause of my files then updating the Ubuntu
package to version 0.123 should resolve this issue.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: initramfs-tools 0.122ubuntu8.8
ProcVersionSignature: Ubuntu 4.4.0-72.93-generic 4.4.49
Uname: Linux 4.4.0-72-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.10
Architecture: amd64
CurrentDesktop: Unity
Date: Fri Aug 25 09:40:41 2017
InstallationDate: Installed on 2015-03-12 (896 days ago)
InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 (20150218.1)
PackageArchitecture: all
SourcePackage: initramfs-tools
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: initramfs-tools (Ubuntu)
 Importance: Undecided
 Status: New

** Affects: initramfs-tools (Debian)
 Importance: Unknown
 Status: Unknown


** Tags: amd64 apport-bug xenial

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

** Also affects: initramfs-tools (Debian) via
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=814345
   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/1713004

Title:
  Temporary files left under /var/tmp by mkinitramfs

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1713004/+subscriptions

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

[Bug 1713004] Re: Temporary files left under /var/tmp by mkinitramfs

2017-08-25 Thread Thomas A. F. Thorne

Looks like this bug is related to bug #1597661 and bug #1515513 although
both of those point the upgrade process being the prompt for a failing
run of the initramfs-tools.

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

Title:
  Temporary files left under /var/tmp by mkinitramfs

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1713004/+subscriptions

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

[Bug 1748844] [NEW] hud-service crash with qmessageLogger::fatal() reported at login

2018-02-12 Thread Thomas A. F. Thorne

Public bug reported:

I start up my Ubuntu 16.04 machine and immediately after loginning in to
the GUI I get a crash report about the hub-service.  Often this is
followed by one or two other reports but not today.

Today I followed the instructions on: 
https://help.ubuntu.com/community/ReportingBugs 
`enabled=1` was already set in /etc/default/apport but I had not set `# 
'problem_types': ['Bug', 'Package'],` in /etc/apport/crashdb.conf until this 
morning.  This had the effect of a bug report appearing to be sent in the 
background but no launchpad page opening.  After setting both of the above I 
did `ubuntu-bug hud` on the command line to generate this report.  

This PC was a fresh install a few months ago.  As far as I can recall it
has been generating the crash report message for most of that time.

It would be nice if I could at least silence the error.  Ideally I would
like to fix the issue.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: hud 14.10+16.04.20160415-0ubuntu1
ProcVersionSignature: Ubuntu 4.13.0-32.35~16.04.1-generic 4.13.13
Uname: Linux 4.13.0-32-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.15
Architecture: amd64
CurrentDesktop: Unity
Date: Mon Feb 12 09:11:35 2018
InstallationDate: Installed on 2017-11-16 (87 days ago)
InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801)
SourcePackage: hud
UpgradeStatus: No upgrade log present (probably fresh install)
upstart.hud.log:
 This application failed to start because it could not find or load the Qt 
platform plugin "minimal"
 in "".
 
 Reinstalling the application may fix this problem.

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


** Tags: amd64 apport-bug xenial

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

Title:
  hud-service crash with qmessageLogger::fatal() reported at login

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

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

[Bug 1630516] [NEW] Logrotate fails repeatedly with /etc/cron.daily/logrotate: error: error creating output file /var/log/... File exists run-parts: /etc/cron.daily/logrotate exited with return code 1

2016-10-05 Thread Thomas A. F. Thorne

Public bug reported:

Good afternoon.  
I have started seeing something very similar to Debian Dug 734688 "Logs are not 
rotated for a month" but in the latest Ubuntu LTS (16.04).  I seem to have 
$ logrotate --version
logrotate 3.8.7
bundled in it.  A few weeks ago I started getting root emails such as this:
> Subject: Cron  test -x /usr/sbin/anacron || ( cd / && run-parts 
> --report /etc/cron.daily )
>
> /etc/cron.daily/logrotate:
> error: error creating output file /var/log/munin/munin-node.log.1: File exists
> run-parts: /etc/cron.daily/logrotate exited with return code 1
When I inspected the area of concern I was able to see that there was an 
existing .1 file.  
manager@warden:/var/log/munin$ ll
total 580
drwxr-xr-x  2 munin adm  4096 Sep 27 06:31 ./
drwxr-xr-x 13 root  syslog   4096 Oct  5 06:26 ../
-rw-r--r--  1 root  root 3440 Sep 26 13:39 munin-node-configure.log
-rw-r--r--  1 root  root   490251 Oct  5 10:25 munin-node.log
-rw-r--r--  1 root  root56598 Sep 21 02:01 munin-node.log.1
-rw-r--r--  1 root  root24576 Aug 31 02:01 munin-node.log.2
-rw-r--r--  1 root  root 1906 Sep 19 06:25 munin-node.log.8.gz
The contents of the munin-node.log file seem to run from the 19th September 
until today.  Unlike other parts of this bug the .1 and .2 files do not seem to 
be already compressed.  

I deleted all but the munin-node.log file to see if it would resolve the 
problem and was going to leave it at that.  Then I noticed that I have had 
another Ubuntu machine which has been sending similar emails for the past week:
> Subject: Cron  test -x /usr/sbin/anacron || ( cd / && run-parts 
> --report /etc/cron.daily )
>
> /etc/cron.daily/logrotate:
> error: error creating output file /var/log/syslog.1.gz: File exists
> run-parts: /etc/cron.daily/logrotate exited with return code 1
Different file, different machine but a very similar error message.  

Checking on the syslog file I can see that it better fits with other reports on 
this bug as my duplicated .1 files has a corresponding .1.gz file.  
manager@trac:/var/log$ ll syslog*
-rw-r- 1 syslog adm 918492 Oct  5 10:30 syslog
-rw-r- 1 syslog adm 125819 Sep 30 06:25 syslog.1
-rw-r- 1 syslog adm  20638 Oct  2 02:01 syslog.1.gz
-rw-r- 1 syslog adm  41989 Sep 30 02:00 syslog.2.gz
-rw-r- 1 syslog adm  18654 Sep 28 02:01 syslog.3.gz
-rw-r- 1 syslog adm  31720 Sep 26 06:40 syslog.4.gz
-rw-r- 1 syslog adm  33151 Sep 25 02:01 syslog.5.gz
-rw-r- 1 syslog adm  17290 Sep 23 02:01 syslog.6.gz
-rw-r- 1 syslog adm  39275 Sep 21 06:35 syslog.7.gz

There has been some speculation that a full or nearly full /var
partition would cause this issue.  I can confirm that /var is part of /
on my systems and that presently both of them have several gigabytes of
space.  I run Munin an Icinga to monitor system state.  Neither of these
show / being completely full in the past month.  They have both had
/boot fill significantly.  Trac had a highest use value of / being
99.28% full in the past year  but warden has only had a peak of 33% in
the past year.

A quick search of the internet suggests a couple of other people reporting 
similar issues: 
https://github.com/gitlabhq/gitlabhq/issues/6894
http://raspberrypi.stackexchange.com/questions/22545/why-are-system-logs-not-rotating
 

I do not believe that I have altered by logrotate configuration files but here 
is a copy of the ones I know about:
$ cat /etc/logrotate.conf 
# see "man logrotate" for details
# rotate log files weekly
weekly

# use the syslog group by default, since this is the owning group
# of /var/log/syslog.
su root syslog

# keep 4 weeks worth of backlogs
rotate 4

# create new (empty) log files after rotating old ones
create

# uncomment this if you want your log files compressed
#compress

# packages drop log rotation information into this directory
include /etc/logrotate.d

# no packages own wtmp, or btmp -- we'll rotate them here
/var/log/wtmp {
missingok
monthly
create 0664 root utmp
rotate 1
}

/var/log/btmp {
missingok
monthly
create 0660 root utmp
rotate 1
}

# system-specific logs may be configured here

$ cat /etc/logrotate.d/rsyslog 
/var/log/syslog
{
rotate 7
daily
missingok
notifempty
delaycompress
compress
postrotate
reload rsyslog >/dev/null 2>&1 || true
endscript
}

/var/log/mail.info
/var/log/mail.warn
/var/log/mail.err
/var/log/mail.log
/var/log/daemon.log
/var/log/kern.log
/var/log/auth.log
/var/log/user.log
/var/log/lpr.log
/var/log/cron.log
/var/log/debug
/var/log/messages
{
rotate 4
weekly
missingok
notifempty
compress
delaycompress
sharedscripts
postrotate
reload rsyslog >/dev/null 2>&1 || true
endscript
}

manager@trac:/var/log$ cat /etc/logrotate.d/munin-node 
/va

[Bug 1631355] [NEW] clamav autonfiguring a Proxy based on Apt settings

2016-10-07 Thread Thomas A. F. Thorne

Public bug reported:

In my syslog I can see messages such as "Update failed. Your network may
be down or none of the mirrors listed in /etc/clamav/freshclam.conf is
working. Check http://www.clamav.net/doc/mirrors-faq.html for possible
reasons." and "WARNING: getpatch: Can't download daily-21693.cdiff from
db.local.clamav.net".  The reason for this seems to be that a machine
named warden.pt.local is being used as general purpose http proxy.

If I check in /etc/clamav/freshclam.conf I can see:
# Check for new database 24 times a day
Checks 24
DatabaseMirror db.local.clamav.net
DatabaseMirror database.clamav.net
# Proxy: http://warden.pt.local:3142/
HTTPProxyServer warden.pt.local
HTTPProxyPort 3142

Which does show that warden is being set up  as an HTTP Proxy Server. I did not 
do this manually though, as the start of said config file suggests with it's 
message of:
# Automatically created by the clamav-freshclam postinst
# Comments will get lost when you reconfigure the clamav-freshclam package


I believe that the automatic configuration of this package is behaving in the 
wrong way.  It should not be selecting warden as a Proxy. 


Warden is set as a proxy for APT on my system.  It has Apt-Cacher NG installed 
for this purpose. In my /etc area, warden is only mentioned in the 
/etc/apt/apt.conf.d/02proxy file and in the automatically generated 
/etc/clamav/freshclam.conf file.  
$ sudo rgrep warden.pt.local /etc/
/etc/clamav/freshclam.conf:# Proxy: http://warden.pt.local:3142/
/etc/clamav/freshclam.conf:HTTPProxyServer warden.pt.local
/etc/apt/apt.conf.d/02proxy:Acquire::http { Proxy 
"http://warden.pt.local:3142";; };


When I check other machines on my network that have a similar setting for apt, 
they also express this error messages about clamav in their syslogs.  As far as 
I can see both 14.04 and 16.04 machines exhibit the same behaviour.  


Syslog sample:
Oct  7 12:34:53 thorne-ul-dt freshclam[25718]: Received signal: wake up
Oct  7 12:34:53 thorne-ul-dt freshclam[25718]: ClamAV update process started at 
Fri Oct  7 12:34:53 2016
Oct  7 12:34:53 thorne-ul-dt freshclam[25718]: Connecting via warden.pt.local
Oct  7 12:34:53 thorne-ul-dt freshclam[25718]: main.cvd is up to date (version: 
57, sigs: 4218790, f-level: 60, builder: amishhammer)
Oct  7 12:34:53 thorne-ul-dt freshclam[25718]: Connecting via warden.pt.local
Oct  7 12:34:58 thorne-ul-dt freshclam[25718]: WARNING: getfile: Unknown 
response from db.local.clamav.net
Oct  7 12:34:58 thorne-ul-dt freshclam[25718]: WARNING: getpatch: Can't 
download daily-21693.cdiff from db.local.clamav.net
Oct  7 12:35:01 thorne-ul-dt CRON[7552]: (munin) CMD (if [ -x 
/usr/bin/munin-cron ]; then /usr/bin/munin-cron; fi)
Oct  7 12:35:01 thorne-ul-dt CRON[7557]: (root) CMD (if [ -x 
/etc/munin/plugins/apt_all ]; then /etc/munin/plugins/apt_all update 7200 12 
>/dev/null; elif [ -x /etc/munin/plugins/apt ]; then /etc/munin/plugins/apt 
update 7200 12 >/dev/null; fi)
Oct  7 12:35:04 thorne-ul-dt freshclam[25718]: WARNING: getfile: Unknown 
response from db.local.clamav.net
Oct  7 12:35:04 thorne-ul-dt freshclam[25718]: WARNING: getpatch: Can't 
download daily-21693.cdiff from db.local.clamav.net
Oct  7 12:35:06 thorne-ul-dt systemd[1]: Started CUPS Scheduler.
Oct  7 12:35:06 thorne-ul-dt colord[1420]: (colord:1420): Cd-WARNING **: failed 
to get session [pid 8204]: No such device or address
Oct  7 12:35:06 thorne-ul-dt colord[1420]: message repeated 3 times: [ 
(colord:1420): Cd-WARNING **: failed to get session [pid 8204]: No such device 
or address]
Oct  7 12:35:09 thorne-ul-dt freshclam[25718]: WARNING: getfile: Unknown 
response from db.local.clamav.net
Oct  7 12:35:09 thorne-ul-dt freshclam[25718]: WARNING: getpatch: Can't 
download daily-21693.cdiff from db.local.clamav.net
Oct  7 12:35:14 thorne-ul-dt freshclam[25718]: WARNING: getfile: Unknown 
response from db.local.clamav.net
Oct  7 12:35:14 thorne-ul-dt freshclam[25718]: WARNING: getpatch: Can't 
download daily-21693.cdiff from db.local.clamav.net
Oct  7 12:35:20 thorne-ul-dt freshclam[25718]: WARNING: getfile: Unknown 
response from db.local.clamav.net
Oct  7 12:35:20 thorne-ul-dt freshclam[25718]: WARNING: getpatch: Can't 
download daily-21693.cdiff from db.local.clamav.net
Oct  7 12:35:20 thorne-ul-dt freshclam[25718]: WARNING: Incremental update 
failed, trying to download daily.cvd
Oct  7 12:35:25 thorne-ul-dt freshclam[25718]: WARNING: getfile: Unknown 
response from db.local.clamav.net
Oct  7 12:35:25 thorne-ul-dt freshclam[25718]: WARNING: Can't download 
daily.cvd from db.local.clamav.net
Oct  7 12:35:25 thorne-ul-dt freshclam[25718]: Trying again in 5 secs...
Oct  7 12:35:30 thorne-ul-dt freshclam[25718]: ClamAV update process started at 
Fri Oct  7 12:35:30 2016
Oct  7 12:35:30 thorne-ul-dt freshclam[25718]: Connecting via warden.pt.local
Oct  7 12:35:30 thorne-ul-dt freshclam[25718]: main.cvd is up to date (version: 
57, sigs: 4218790, f-level: 60, builder: amishhammer)
Oct  7 12:35:30 t

[Bug 1631355] Re: clamav autonfiguring a Proxy based on Apt settings

2016-10-07 Thread Thomas A. F. Thorne

Attaching the log file which seems to relate to clamaav as it was not
automatically attached.  This file was taken from
/var/log/clamav/freshclam.log and seems to show the error extending back
to the beginning of the month.

If I look in the oldest rotated copy of the long on my machine I can see
evidence of the problem extending back to at least the end of July
without my noticing until now.

Sun Jul 31 07:35:53 2016 -> ClamAV update process started at Sun Jul 31 
07:35:53 2016
Sun Jul 31 07:35:53 2016 -> WARNING: Your ClamAV installation is OUTDATED!
Sun Jul 31 07:35:53 2016 -> WARNING: Local version: 0.99 Recommended version: 
0.99.2
Sun Jul 31 07:35:53 2016 -> DON'T PANIC! Read http://www.clamav.net/support/faq
Sun Jul 31 07:35:53 2016 -> Connecting via warden.pt.local
Sun Jul 31 07:35:53 2016 -> main.cvd is up to date (version: 57, sigs: 4218790, 
f-level: 60, builder: amishhammer)
Sun Jul 31 07:35:53 2016 -> Connecting via warden.pt.local
Sun Jul 31 07:35:58 2016 -> WARNING: getfile: Unknown response from remote 
server (IP: 172.16.20.99)
Sun Jul 31 07:35:58 2016 -> WARNING: getpatch: Can't download daily-21693.cdiff 
from db.local.clamav.net
Sun Jul 31 07:36:03 2016 -> WARNING: getfile: Unknown response from remote 
server (IP: 172.16.20.99)
Sun Jul 31 07:36:03 2016 -> WARNING: getpatch: Can't download daily-21693.cdiff 
from db.local.clamav.net
Sun Jul 31 07:36:08 2016 -> WARNING: getfile: Unknown response from remote 
server (IP: 172.16.20.99)
Sun Jul 31 07:36:08 2016 -> WARNING: getpatch: Can't download daily-21693.cdiff 
from db.local.clamav.net
Sun Jul 31 07:36:13 2016 -> WARNING: getfile: Unknown response from remote 
server (IP: 172.16.20.99)
Sun Jul 31 07:36:13 2016 -> WARNING: getpatch: Can't download daily-21693.cdiff 
from db.local.clamav.net
Sun Jul 31 07:36:18 2016 -> WARNING: getfile: Unknown response from remote 
server (IP: 172.16.20.99)
Sun Jul 31 07:36:18 2016 -> WARNING: getpatch: Can't download daily-21693.cdiff 
from db.local.clamav.net
Sun Jul 31 07:36:18 2016 -> WARNING: Incremental update failed, trying to 
download daily.cvd
Sun Jul 31 07:36:23 2016 -> WARNING: getfile: Unknown response from remote 
server (IP: 172.16.20.99)
Sun Jul 31 07:36:23 2016 -> WARNING: Can't download daily.cvd from 
db.local.clamav.net
Sun Jul 31 07:36:23 2016 -> Trying again in 5 secs...
Sun Jul 31 07:36:28 2016 -> ClamAV update process started at Sun Jul 31 
07:36:28 2016
Sun Jul 31 07:36:28 2016 -> WARNING: Your ClamAV installation is OUTDATED!
Sun Jul 31 07:36:28 2016 -> WARNING: Local version: 0.99 Recommended version: 
0.99.2
Sun Jul 31 07:36:28 2016 -> DON'T PANIC! Read http://www.clamav.net/support/faq
Sun Jul 31 07:36:28 2016 -> Connecting via warden.pt.local
Sun Jul 31 07:36:28 2016 -> main.cvd is up to date (version: 57, sigs: 4218790, 
f-level: 60, builder: amishhammer)
Sun Jul 31 07:36:28 2016 -> Connecting via warden.pt.local
Sun Jul 31 07:36:33 2016 -> WARNING: getfile: Unknown response from remote 
server (IP: 172.16.20.99)
Sun Jul 31 07:36:33 2016 -> WARNING: getpatch: Can't download daily-21693.cdiff 
from db.local.clamav.net

** Attachment added: "freshclam.log"
   
https://bugs.launchpad.net/ubuntu/+source/clamav/+bug/1631355/+attachment/4756707/+files/freshclam.log

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

Title:
  clamav autonfiguring a Proxy based on Apt settings

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

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

[Bug 1631355] Re: clamav autonfiguring a Proxy based on Apt settings

2016-10-10 Thread Thomas A. F. Thorne

> Could you report the content of those two environment variables on
your system?

Certainly, here is what I can find on my system: 
thomasthorne@thorne-ul-dt:~$ echo $http_proxy

thomasthorne@thorne-ul-dt:~$ echo $HTTPProxyServer

So nothing set for either variable there is seems:
thomasthorne@thorne-ul-dt:~$ env | grep -i http
NVM_NODEJS_ORG_MIRROR=http://nodejs.org/dist
That does not look like it would be applicable either. 

> I'm curious so I'd really like to know.

Always a good trait in someone helping to fault find.

> So in case the check for these env variables doesn't reveal whatever
was going on, would you then mind filing a bug with Debian please?

I will do so in a few minutes time and then report or link the bug
details here.

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

Title:
  clamav autonfiguring a Proxy based on Apt settings

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

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

[Bug 1631355] Re: clamav autonfiguring a Proxy based on Apt settings

2016-10-10 Thread Thomas A. F. Thorne

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

** Also affects: clamav (Debian) via
   http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=840331
   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/1631355

Title:
  clamav autonfiguring a Proxy based on Apt settings

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

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

[Bug 1630516] Re: Logrotate fails repeatedly with /etc/cron.daily/logrotate: error: error creating output file /var/log/... File exists run-parts: /etc/cron.daily/logrotate exited with return code 1

Still present on 14.04.1. I am seeing this again today.

I wonder if this would count as a papercut? I am not really sure as
https://wiki.ubuntu.com/One%20Hundred%20Papercuts/Mission says "Have the
impression the desktop is rock solid." and this is a log rotation system
that only moans if root mail is setup. On the other hand
https://wiki.ubuntu.com/One%20Hundred%20Papercuts/Triage/Classify%20as%20a%20papercut?highlight=%28CategoryPapercuts%29
says "If a bug is trivial to fix, you shall classify it as a papercut by
marking it as affecting the "hundredpapercuts" project." and this bug
just needs the upstream bug brought in. It would make at least 6 of us
feel like someone is caring too.

Front page of the One Hundred Papercuts says "If any doubt, you can ask
any time." so I shall add papercuts-ninja list to the subscription.
This is a very low traffic bug so someone can unsubscribe them before
this thread generates more than a couple of posts.

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

Title:
Logrotate fails repeatedly with /etc/cron.daily/logrotate: error:
error creating output file /var/log/... File exists run-parts:
/etc/cron.daily/logrotate exited with return code 1

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

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

[Bug 1630516] Re: Logrotate fails repeatedly with /etc/cron.daily/logrotate: error: error creating output file /var/log/... File exists run-parts: /etc/cron.daily/logrotate exited with return code 1

That does sound a bit tenuous but could be easily settled by a policy decision 
on whether: 
 i) Bugs that directly block the installation of security patches are security 
bugs.  
 ii) Bugs that cause disk space to fill which in turn block security patch 
install are security bugs.  

I would have said that i sounds like a possible valid case but ii is
getting a bit drawn out.  Still I expect the situation and suggestion
will have popped up before somewhere.  Looking at
https://wiki.ubuntu.com/DebuggingSecurity#How%20to%20File it does not
mention blocking security patches as a criteria which would thrown the
whole idea of it being a security bug out.

If in doubt ask.  I shall try heading over to IRC and seeing if someone
can answer the question.

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

Title:
  Logrotate fails repeatedly with /etc/cron.daily/logrotate: error:
  error creating output file /var/log/... File exists run-parts:
  /etc/cron.daily/logrotate exited with return code 1

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

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

[Bug 1630516] Re: Logrotate fails repeatedly with /etc/cron.daily/logrotate: error: error creating output file /var/log/... File exists run-parts: /etc/cron.daily/logrotate exited with return code 1

I checked on IRC #ubuntu-hardened (the actual name for the #ubuntu-
security channel) and was told that "we typically only consider bugs to
have a security impact if there's an attacker to the story".  The reason
for that is "else, almost every bug has an indirect security impact"
which I can see the logic to.

So that means this is not a security bug, just a bug.

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

Title:
  Logrotate fails repeatedly with /etc/cron.daily/logrotate: error:
  error creating output file /var/log/... File exists run-parts:
  /etc/cron.daily/logrotate exited with return code 1

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

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

[Bug 1630516] Re: Logrotate fails repeatedly with /etc/cron.daily/logrotate: error: error creating output file /var/log/... File exists run-parts: /etc/cron.daily/logrotate exited with return code 1

The stock not security reply can be found at
https://wiki.ubuntu.com/SecurityTeam/BugTriage#Not_Security which says
"unmarked it as a security issue since this bug does not show evidence
of allowing attackers to cross privilege boundaries nor directly cause
loss of data/privacy."

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

Title:
  Logrotate fails repeatedly with /etc/cron.daily/logrotate: error:
  error creating output file /var/log/... File exists run-parts:
  /etc/cron.daily/logrotate exited with return code 1

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

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

Re: [Bug 1636564] Re: Segfault from libX11.so.6.3.0

2017-03-21 Thread Thomas A. F. Thorne

I don't think I'm using the Nvidia drivers on the machine I reported this
from. That would mean they could not be the route cause.

On Mon, 20 Mar 2017, 17:51 Jan Lachnitt, <1636...@bugs.launchpad.net>
wrote:

> Another report and some thoughts below
>
> HW: Asus Vivobook (touchscreen, Intel graphics), external monitor attached.
> OS: Linux Mint 18 Cinnamon x64.
> State before crash: Running X session using both displays ("big desktop"),
> several applications, Vivaldi browser active.
> My aim: Lock the computer.
> Course of action, the USUAL part: Pressed Ctrl+Alt+L, not locked - Vivaldi
> displayed its menu (to be displayed upon pressing Alt), tapped the
> touchscreen to get rid of the menu and thus actually lock the computer.
> Course of action, the UNUSUAL part: Black screen for a few seconds, then
> login screen, old X session gone.
>
> syslog:
> Mar 20 14:43:20 VivoBook org.a11y.atspi.Registry[1729]: XIO:  fatal IO
> error 11 (Resource temporarily unavailable) on X server ":0"
> Mar 20 14:43:20 VivoBook org.a11y.atspi.Registry[1729]:   after 2925
> requests (2925 known processed) with 0 events remaining.
> Mar 20 14:43:20 VivoBook cinnamon-session[1640]: Gdk-WARNING:
> t+4492,79569s: cinnamon-session: Fatal IO error 11 (Prostředek je dočasně
> nepřístupný) on X server :0.
> Mar 20 14:43:20 VivoBook org.gtk.vfs.Daemon[1711]: A connection to the bus
> can't be made
> Mar 20 14:43:20 VivoBook org.gtk.vfs.Daemon[1711]: A connection to the bus
> can't be made
> Mar 20 14:43:20 VivoBook mdm[1212]: WARNING: mdm_slave_xioerror_handler:
> Kritická chyba X - Restartování :0
> Mar 20 14:43:20 VivoBook kernel: [ 4538.677519] vivaldi-bin[4100]:
> segfault at 968 ip 7f61ac384643 sp 7ffc09f25b50 error 4 in
> libX11.so.6.3.0[7f61ac35c000+135000]
> Mar 20 14:43:20 VivoBook ag[4118]: mdm-superpost Starting...
> Mar 20 14:43:20 VivoBook ag[4122]: mdm-superpost Finished
> Mar 20 14:43:20 VivoBook console-kit-daemon[1566]: (process:4128):
> GLib-CRITICAL **: g_slice_set_config: assertion 'sys_page_size == 0' failed
> Mar 20 14:43:21 VivoBook acpid: client 1219[0:0] has disconnected
> Mar 20 14:43:21 VivoBook acpid: client connected from 4131[0:0]
> Mar 20 14:43:21 VivoBook acpid: 1 client rule loaded
> Mar 20 14:43:22 VivoBook ag[4139]: mdm-superinit Starting...
> Mar 20 14:43:22 VivoBook ag[4140]: mdm-superinit Finished
>
> Xorg.0.log covers the new session, Xorg.0.log.old has no record of the
> event.
>
> The segfault really seems to affect multiple users, especially with
> Chromium-based browsers, e.g.:
> https://bbs.archlinux.org/viewtopic.php?id=131328 - from 2011 already
> https://bbs.archlinux.org/viewtopic.php?id=221888 - solution?
>
> I don't know if syslog preserves the order of events (within a second),
> but if yes, then the segfault is just a consequence of another problem,
> e.g.:
>
> https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers/+bug/999191
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1636564
>
> Title:
>   Segfault from libX11.so.6.3.0
>
> Status in libx11 package in Ubuntu:
>   Confirmed
>
> Bug description:
>   Something went wrong with my Ubuntu 16.04 LTS desktop today.  When I
>   got back to the system Mattermost and a Chrome were indicating that
>   the network was not working.  I started to look about and it seemed
>   that my main ethernet network connection had lost its IPv4 address
>   somehow.  ifconfig and the GUI network manager confirmed this.
>
>   To try and resolve this I physically removed the connector and the
>   plugged it back in.  Shortly after I did this my GUI seemed to die out
>   and I ended up back at the login screen.
>
>   Once everything had calmed down I logged back in.  After some digging
>   about in the logs I noticed the following in /var/log/kern.log
>
>   Oct 25 13:01:09 thorne-ul-dt kernel: [694321.877561] Mattermost[744]:
> segfault at 968 ip 7f8a9e257643 sp 7ffe72a3b510 error 4 in
> libX11.so.6.3.0[7f8a9e22f000+135000]
>   Oct 25 13:01:09 thorne-ul-dt kernel: [694322.029362] chrome[745]:
> segfault at 968 ip 7fd4b5c73643 sp 7fff94f78d90 error 4 in
> libX11.so.6.3.0[7fd4b5c4b000+135000]
>
>   That seemed to be the correct time for the problem I noticed.   What
>   exactly caused it I am not sure.
>
>   ProblemType: Bug
>   DistroRelease: Ubuntu 16.04
>   Package: libx11-6 2:1.6.3-1ubuntu2
>   ProcVersionSignature: Ubuntu 4.4.0-42.62-generic 4.4.21
>   Uname: Linux 4.4.0-42-generic x86_64
>   .tmp.unity_support_test.0:
>
>   ApportVersion: 2.20.1-0ubuntu2.1
>   Architecture: amd64
>   CompizPlugins: No value set for
> `/apps/compiz-1/general/screen0/options/active_plugins'
>   CompositorRunning: compiz
>   CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
>   CompositorUnredirectFSW: true
>   CurrentDesktop: Unity
>   Date: Tue Oct 25 17:07:28 2016
>   DistUpgraded: Fresh install
>   DistroCodename: xenial
>   DistroVariant:

[Bug 1630516] Re: Logrotate doesn't clean old system logs, allowing them to fill the disk

2017-03-22 Thread Thomas A. F. Thorne

SRU Bug Template


[Impact] 

Logrotate fails to rotate a log and then will continue to fail to rotate
it until manual intervention takes place.  If messaging has not been
configured on the system there will be no warning issued to the user.
The log will grow day by day until a user intervenes or the drive that
the log is stored on is full.

Very large log files can make it more difficult to find useful data.
Full drives make the rest of the system fail to operate.  Backporting a
fix would prevent drives filling up on stable releases.

[Test Case]

Go to your logs area (/var/logs) and create a file with a name ending
.2, as would be created part way through the logrotate process.  So if
you have /var/log/syslog, /var/log/syslog.1, /var/log/syslog.2.gz,
/var/log/syslog.3.gz; create a new file named /var/log/syslog.2.  Your
subsequent log rotate runs will fail.

[Regression Potential]



[Other Info]

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

Title:
  Logrotate doesn't clean old system logs, allowing them to fill the
  disk

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

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

[Bug 1660574] [NEW] IPv4 Address Lost 8 Days After Previous DHCP Allocation

2017-01-31 Thread Thomas A. F. Thorne

Public bug reported:

My Ubuntu 16.04 desktop frequently loses the IPv4 address on its wired
ethernet connection to my office's network.  This happened this morning
and previously happened 8 days ago.

The network uses a Windows Small Business Server as its main Active
Domain Domain Controller which includes a DHCP service.  There are
several other Ubuntu 16.04 machines on the network that do not seem to
experience this issue.  This is an IPv4 only network, no IPv6 services
are configures and IPv6 is disabled on most machines.

My PC has two wired network ports.  One connects to the office network
and uses DHCP to get an IPv4 address.  The other connects to a switch on
my desk that has test equipment connected to it and uses a static IPv4
address.

I have the output from: 
 ll /var/lib/NetworkManager
 nmcli -p c
 nmcli -p c show TN\ Wired
Taken; after the renewal of the address eight days ago, this morning before I 
"Disconnect"ed the connection from the drop down menu and after I reconnected 
and an IPv4 address was re-acquired.  If any of this would be helpful, please 
let me know and I shall post it.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: network-manager 1.2.2-0ubuntu0.16.04.3
ProcVersionSignature: Ubuntu 4.4.0-57.78-generic 4.4.35
Uname: Linux 4.4.0-57-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.4
Architecture: amd64
CurrentDesktop: Unity
Date: Tue Jan 31 09:55:10 2017
IfupdownConfig:
 # interfaces(5) file used by ifup(8) and ifdown(8)
 auto lo
 iface lo inet loopback
InstallationDate: Installed on 2015-03-12 (690 days ago)
InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 (20150218.1)
IpRoute:
 default via 172.16.20.21 dev eth0  proto static  metric 100 
 169.254.0.0/16 dev eth1  scope link  metric 1000 
 172.16.20.0/24 dev eth0  proto kernel  scope link  src 172.16.20.67  metric 
100 
 192.168.0.0/24 dev eth1  proto kernel  scope link  src 192.168.0.10  metric 100
IwConfig:
 lono wireless extensions.
 
 eth1  no wireless extensions.
 
 eth0  no wireless extensions.
NetworkManager.state:
 [main]
 NetworkingEnabled=true
 WirelessEnabled=true
 WWANEnabled=true
 WimaxEnabled=true
RfKill:
 
SourcePackage: network-manager
UpgradeStatus: No upgrade log present (probably fresh install)
mtime.conffile..etc.NetworkManager.NetworkManager.conf: 
2016-03-11T09:44:29.848008
nmcli-dev:
 DEVICE  TYPE  STATE  DBUS-PATH  
CONNECTIONCON-UUID  CON-PATH
   
 eth0ethernet  connected  /org/freedesktop/NetworkManager/Devices/2  TN 
Wired  decbd8d4-b045-4214-88c3-904bcabaa386  
/org/freedesktop/NetworkManager/ActiveConnection/2 
 eth1ethernet  connected  /org/freedesktop/NetworkManager/Devices/1  Test 
Network  c2e4c3e8-027e-4201-8486-824d32ee164f  
/org/freedesktop/NetworkManager/ActiveConnection/0 
 lo  loopback  unmanaged  /org/freedesktop/NetworkManager/Devices/0  -- 
   ----
nmcli-nm:
 RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  WIFI  
   WWAN-HW  WWAN
 running  1.2.2connected  started  full  enabled enabled  
enabled  enabled  enabled

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


** Tags: amd64 apport-bug xenial

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

Title:
  IPv4 Address Lost 8 Days After Previous DHCP Allocation

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

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

[Bug 1306436] Re: unity-settings-daemon crashed with signal 5 in _XReply()

2017-02-06 Thread Thomas A. F. Thorne

Occurred again today.

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

Title:
  unity-settings-daemon crashed with signal 5 in _XReply()

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity-settings-daemon/+bug/1306436/+subscriptions

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

[Bug 1642600] [NEW] PC freeze when turning off screen

2016-11-17 Thread Thomas A. F. Thorne

Public bug reported:

I have an ubuntu 16.04 PC which was recently upgraded from 10.something
to 12.04 and then to 16.04 (I think that is how it went, it was a two
day thing with me checking on it now and again to say yes.  Now that it
is running on 16.04 I have noticed that when I left the PC for a while
it locked up.  The display was off, the power light on the tower solidly
on and the keyboard unresponsive.  The Num Lock light was lit but would
not respond to key presses, nor would the Caps Lock or Scroll Lock
lights.  No key presses or short press of a power light would change the
system state.  The only thing I could do while sat at the PC was hold
the power button in to force a power off.

When the PC was powered back on everything seemed to be OK.

I thought it might be a problem with suspending the PC.  I was able to
do that manually though.  The display went off, the tower fans went
quiet and the power light started to blink.  Pressing keyboard keys did
nothing but a short press of the power button brought the system back
online.  The only problem being that the Wi-Fi was lost until I
restarted the system, not ideal but better than frozen.

I attempted to disable the automatic suspend option from the Settings
menu but the system still ended up in the frozen state.  Next to
completely disable suspend by creating a
/etc/polkit-1/localauthority/50-local.d/com.ubuntu.disable-suspend.pkla
file as suggested at http://askubuntu.com/questions/452908/how-to-
disable-suspend-in-14-04 but the system still ended up frozen.

That leaves me to think it was the act of going into the Monitor
Disabled state which caused the issue.  So I started to report an
ubuntu-bug and here I am typing out this description of what I remember
doing.

$ lsb_release -rd
Description:Ubuntu 16.04.1 LTS
Release:16.04

Memory 2.0 GiB
Processor Intel Core 2 Duo CPU E4400 @ 2.00 GHz x 2
Graphics Gallium 0.4 on ATI RV515
OS type 64-bit
Disk 96.6 GB

If there are any further diagnostic steps I can take please let me know.
This is a personal machine so I can do most things to it.  I am a c/c++
software engineer by trade so although I am not great with the GNU
Debugger I can do most things with a bit of instruction.  I do not do
much Ubuntu or Kernel work so links to getting started guides for how to
do anything more specific that git clone or make would be appreciated.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg 1:7.7+13ubuntu3
ProcVersionSignature: Ubuntu 4.4.0-47.68-generic 4.4.24
Uname: Linux 4.4.0-47-generic x86_64
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
CurrentDesktop: Unity
Date: Thu Nov 17 13:29:59 2016
DistUpgraded: 2016-11-16 07:49:36,758 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
DistroCodename: xenial
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GpuHangFrequency: Several times a day
GpuHangReproducibility: Occurs more often under certain circumstances
GpuHangStarted: Immediately after installing this version of Ubuntu
GraphicsCard:
 Advanced Micro Devices, Inc. [AMD/ATI] RV516 [Radeon X1300/X1550 Series] 
[1002:7183] (prog-if 00 [VGA controller])
   Subsystem: Dell RV516 [Radeon X1300/X1550 Series] [1028:0d02]
   Subsystem: Dell RV516 [Radeon X1300/X1550 Series] (Secondary) [1028:0d03]
InstallationDate: Installed on 2014-02-03 (1017 days ago)
InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1)
LightdmGreeterLogOld:
 (lightdm-gtk-greeter:1176): GLib-CRITICAL **: g_shell_parse_argv: assertion 
'command_line != NULL' failed
 
 ** (lightdm-gtk-greeter:1176): WARNING **: Failed to open sessions directory: 
Error opening directory '/usr/share/lightdm/sessions': No such file or directory
 
 ** (lightdm-gtk-greeter:1176): WARNING **: Failed to load user image: Failed 
to open file '/home/thomas/.face': No such file or directory
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-47-generic 
root=UUID=ce39165f-49f5-4875-a74e-2be810fd63c9 ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
Title: Xorg freeze
UpgradeStatus: Upgraded to xenial on 2016-11-16 (1 days ago)
dmi.bios.date: 06/23/2008
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.0.15
dmi.board.name: 0CU409
dmi.board.vendor: Dell Inc.
dmi.chassis.type: 3
dmi.chassis.vendor: Dell Inc.
dmi.chassis.version: OEM
dmi.modalias: 
dmi:bvnDellInc.:bvr1.0.15:bd06/23/2008:svnDellInc.:pnVostro200:pvr:rvnDellInc.:rn0CU409:rvr:cvnDellInc.:ct3:cvrOEM:
dmi.product.name: Vostro 200
dmi.sys.vendor: Dell Inc.
version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.2
version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2.2
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-ex

[Bug 1642600] Re: PC freeze when turning off screen

2016-11-17 Thread Thomas A. F. Thorne

I probably should have put that I have not seen the issue since setting
the turn off screen option to never.  It has only been a couple of hours
since I did that but it is better than before when it would fail within
the ~30 minutes that setting was at before.

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

Title:
  PC freeze when turning off screen

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

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

[Bug 1656405] [NEW] package mariadb-server-10.0 10.0.28-0ubuntu0.16.04.1 failed to install/upgrade: trying to overwrite '/usr/share/man/man1/myisam_ftdump.1.gz', which is also in package mysql-client-

2017-01-13 Thread Thomas A. F. Thorne

Public bug reported:

No Idea.  Fired this machine up after about a year of it not really
working well and got to here.

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: mariadb-server-10.0 10.0.28-0ubuntu0.16.04.1
ProcVersionSignature: Ubuntu 4.4.0-59.80-generic 4.4.35
Uname: Linux 4.4.0-59-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.4
Architecture: amd64
Date: Thu Jan 12 23:52:04 2017
DpkgTerminalLog:
 Preparing to unpack .../mariadb-server-10.0_10.0.28-0ubuntu0.16.04.1_amd64.deb 
...
 /var/lib/mysql: found previous version 5.5
 Unpacking mariadb-server-10.0 (10.0.28-0ubuntu0.16.04.1) ...
 dpkg: error processing archive 
/var/cache/apt/archives/mariadb-server-10.0_10.0.28-0ubuntu0.16.04.1_amd64.deb 
(--unpack):
  trying to overwrite '/usr/share/man/man1/myisam_ftdump.1.gz', which is also 
in package mysql-client-5.7 5.7.16-0ubuntu0.16.04.1
DuplicateSignature:
 package:mariadb-server-10.0:10.0.28-0ubuntu0.16.04.1
 Unpacking mariadb-server-10.0 (10.0.28-0ubuntu0.16.04.1) ...
 dpkg: error processing archive 
/var/cache/apt/archives/mariadb-server-10.0_10.0.28-0ubuntu0.16.04.1_amd64.deb 
(--unpack):
  trying to overwrite '/usr/share/man/man1/myisam_ftdump.1.gz', which is also 
in package mysql-client-5.7 5.7.16-0ubuntu0.16.04.1
ErrorMessage: trying to overwrite '/usr/share/man/man1/myisam_ftdump.1.gz', 
which is also in package mysql-client-5.7 5.7.16-0ubuntu0.16.04.1
InstallationDate: Installed on 2011-06-08 (2045 days ago)
InstallationMedia: Mythbuntu 11.04 "Natty Narwhal" - Release amd64 (20110426)
Logs.var.log.daemon.log:
 
Logs.var.log.mysql.error.log: 
MySQLConf.etc.mysql.conf.d.mysql.cnf: [mysql]
MySQLConf.etc.mysql.conf.d.mysqld_safe_syslog.cnf:
 [mysqld_safe]
 syslog
MySQLConf.etc.mysql.conf.d.mysqldump.cnf:
 [mysqldump]
 quick
 quote-names
 max_allowed_packet = 16M
MySQLConf.etc.mysql.conf.d.mythtv.cnf:
 [mysqld]
 bind-address=::
 max_connections=100
MySQLVarLibDirListing: ['test', 'aria_log.0001', 'aria_log_control', 
'debian-10.0.flag', 'zm', 'multi-master.info', 'ibdata1', 'ib_logfile0', 
'performance_schema', 'ib_logfile1', 'mythconverg', 'mysql', 
'mysql_upgrade_info']
ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-4.4.0-59-generic 
root=UUID=d0ffd2db-ea86-4737-b057-b55193fccad6 ro quiet splash vt.handoff=7
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.1
 apt  1.2.18
SourcePackage: mariadb-10.0
Title: package mariadb-server-10.0 10.0.28-0ubuntu0.16.04.1 failed to 
install/upgrade: trying to overwrite '/usr/share/man/man1/myisam_ftdump.1.gz', 
which is also in package mysql-client-5.7 5.7.16-0ubuntu0.16.04.1
UpgradeStatus: Upgraded to xenial on 2016-08-27 (139 days ago)

** Affects: mariadb-10.0 (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package need-duplicate-check package-conflict xenial

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

Title:
  package mariadb-server-10.0 10.0.28-0ubuntu0.16.04.1 failed to
  install/upgrade: trying to overwrite
  '/usr/share/man/man1/myisam_ftdump.1.gz', which is also in package
  mysql-client-5.7 5.7.16-0ubuntu0.16.04.1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mariadb-10.0/+bug/1656405/+subscriptions

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

[Bug 1653636] Re: Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0, 0)

As an upgrade from one kernel to the other seems to have brought about
this problem I am attaching the recent /var/log/apt/history.log file.

** Attachment added: "history.log.1.gz"
   
https://bugs.launchpad.net/ubuntu/+bug/1653636/+attachment/4799315/+files/history.log.1.gz

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

Title:
  Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-
  block(0,0)

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

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

[Bug 1653636] [NEW] Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0, 0)

Public bug reported:

On powering my PC up after the holiday break I got a welcome back in the
form of a kernel panic. I had completed some upgrades before the
holiday and was seeing a restart to use the newly upgraded packages
message.

When the PC powered on the Caps Lock and Scroll Lock lights on my
keyboard were blinking. After passing through grub and attempting to
boot the kernel the boot message ended with the following message (typed
out by me by hand, please see the attached photograph of the screen for
more details):

Kernel Offset: disabled
---[ end Kernel panic - not syncing: VFS: Unable to mount root fs on
unknown-block(0,0)
[ cut here ]
WARNING: CPU: 0 PID: 1 at arch/x86/kernel/smp.c:125
native_smp_send_reschedule+0x60/0x70(
Modules linked in:
CPU: 0 PID 1: Comm: swapper/0 Not tainted 4.4.21 #1
Hardware name: Gigabyte Technology Cp., Ltd. H81M-DS2V/H81M-DS2V, BIOS F6
08/11/2015
...
Call Trace:
... dump_stack
... warn_slowpath_common
... warn_slowpath_null
... native_smp_send_rescheduale
... trigger_load_balance
... scheduler_tick
... ? tick_sched_handle.isra
... update_process_times
... tick_sched_handle.isra

I can type out more of the message if people want but I think the
chances of my typing it all in correctly are slim.

I tried to boot using the (recovery mode) version of 4.4.21 and the .old
version of 4.4.21 that seemed to have appeared from somewhere. To my eye the
problem looked the same in each version. Once I selected 4.4.0-57-generic I
was able to complete the boot and begin reporting this bug.

If there are any more steps I can take to aid diagnosis please let me
know.

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

** Tags: xenial

** Attachment added: "Photograph of Kernel panic displayed at boot"

https://bugs.launchpad.net/bugs/1653636/+attachment/4799314/+files/Kernel-panic_not_syncing_vfs_unable_to_mount_root_fs_on_unknown-block.png

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

Title:
Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-
block(0,0)

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

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

[Bug 1653636] Re: Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0, 0)

I did not choose the virtualbox package when opening this bug.  I wanted
to choose some kind of kernel or smp related package but did not know
what one to select.

** Package changed: virtualbox (Ubuntu) => ubuntu

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

Title:
  Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-
  block(0,0)

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

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

[Bug 1653636] Re: Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0, 0)

As an upgrade from one kernel to the other seems to have brought about
this problem I am attaching the recent /var/log/apt/term.log file.

The more recent version of the file is blank.  These files relate to the
period of the 16th to power off.

** Attachment added: "term.log.1.gz"
   
https://bugs.launchpad.net/ubuntu/+bug/1653636/+attachment/4799316/+files/term.log.1.gz

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

Title:
  Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-
  block(0,0)

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

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

[Bug 1653636] CRDA.txt

apport information

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

Title:
  Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-
  block(0,0)

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

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

[Bug 1653636] ProcEnviron.txt

apport information

** Attachment added: "ProcEnviron.txt"
   
https://bugs.launchpad.net/bugs/1653636/+attachment/4799334/+files/ProcEnviron.txt

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

Title:
  Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-
  block(0,0)

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

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

[Bug 1653636] ProcModules.txt

apport information

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

Title:
  Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-
  block(0,0)

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

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

[Bug 1653636] WifiSyslog.txt

apport information

** Attachment added: "WifiSyslog.txt"
   
https://bugs.launchpad.net/bugs/1653636/+attachment/4799339/+files/WifiSyslog.txt

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

Title:
  Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-
  block(0,0)

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

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

[Bug 1653636] Lspci.txt

apport information

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

Title:
  Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-
  block(0,0)

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

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

[Bug 1653636] ProcCpuinfo.txt

apport information

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

Title:
  Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-
  block(0,0)

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

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

[Bug 1653636] Re: Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0, 0)

apport information

** Tags added: apport-collected

** Description changed:

  On powering my PC up after the holiday break I got a welcome back in the
  form of a kernel panic.  I had completed some upgrades before the
  holiday and was seeing a restart to use the newly upgraded packages
  message.
  
  When the PC powered on the Caps Lock and Scroll Lock lights on my
  keyboard were blinking.  After passing through grub and attempting to
  boot the kernel the boot message ended with the following message (typed
  out by me by hand, please see the attached photograph of the screen for
  more details):
  
  Kernel Offset: disabled
  ---[ end Kernel panic - not syncing: VFS: Unable to mount root fs on 
unknown-block(0,0)
  [ cut here ]
  WARNING: CPU: 0 PID: 1 at arch/x86/kernel/smp.c:125 
native_smp_send_reschedule+0x60/0x70(
  Modules linked in:
  CPU: 0 PID 1: Comm: swapper/0 Not tainted 4.4.21 #1
  Hardware name: Gigabyte Technology Cp., Ltd. H81M-DS2V/H81M-DS2V, BIOS F6 
08/11/2015
   ...
  Call Trace:
   ... dump_stack
   ... warn_slowpath_common
   ... warn_slowpath_null
   ... native_smp_send_rescheduale
   ... trigger_load_balance
   ... scheduler_tick
   ... ? tick_sched_handle.isra
   ... update_process_times
   ... tick_sched_handle.isra
   
  
  I can type out more of the message if people want but I think the
  chances of my typing it all in correctly are slim.
  
  
  I tried to boot using the (recovery mode) version of 4.4.21 and the .old 
version of 4.4.21 that seemed to have appeared from somewhere.  To my eye the 
problem looked the same in each version.  Once I selected 4.4.0-57-generic I 
was able to complete the boot and begin reporting this bug.  
  
- If there are any more steps I can take to aid diagnosis please let me
- know.
+ If there are any more steps I can take to aid diagnosis please let me know.
+ --- 
+ ApportVersion: 2.20.1-0ubuntu2.4
+ Architecture: amd64
+ AudioDevicesInUse:
+  USERPID ACCESS COMMAND
+  /dev/snd/controlC2:  thomasthorne   4613 F pulseaudio
+  /dev/snd/pcmC1D0p:   thomasthorne   4613 F...m pulseaudio
+  /dev/snd/controlC1:  thomasthorne   4613 F pulseaudio
+  /dev/snd/controlC0:  thomasthorne   4613 F pulseaudio
+ CurrentDesktop: Unity
+ DistroRelease: Ubuntu 16.04
+ HibernationDevice: RESUME=UUID=3c3104a1-5ead-4ebf-b2df-f9397f572dca
+ InstallationDate: Installed on 2015-03-12 (662 days ago)
+ InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 
(20150218.1)
+ IwConfig:
+  lono wireless extensions.
+  
+  eth1  no wireless extensions.
+  
+  eth0  no wireless extensions.
+ MachineType: Gigabyte Technology Co., Ltd. H81M-DS2V
+ Package: linux (not installed)
+ ProcFB: 0 inteldrmfb
+ ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-57-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro quiet splash crashkernel=384M-:128M
+ ProcVersionSignature: Ubuntu 4.4.0-57.78-generic 4.4.35
+ RelatedPackageVersions:
+  linux-restricted-modules-4.4.0-57-generic N/A
+  linux-backports-modules-4.4.0-57-generic  N/A
+  linux-firmware1.157.6
+ RfKill:
+  
+ Tags:  xenial
+ Uname: Linux 4.4.0-57-generic x86_64
+ UpgradeStatus: No upgrade log present (probably fresh install)
+ UserGroups: adm cdrom dialout dip lpadmin mock plugdev sambashare sudo 
wireshark
+ _MarkForUpload: True
+ dmi.bios.date: 08/11/2015
+ dmi.bios.vendor: American Megatrends Inc.
+ dmi.bios.version: F6
+ dmi.board.asset.tag: To be filled by O.E.M.
+ dmi.board.name: H81M-DS2V
+ dmi.board.vendor: Gigabyte Technology Co., Ltd.
+ dmi.board.version: x.x
+ dmi.chassis.asset.tag: To Be Filled By O.E.M.
+ dmi.chassis.type: 3
+ dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
+ dmi.chassis.version: To Be Filled By O.E.M.
+ dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF6:bd08/11/2015:svnGigabyteTechnologyCo.,Ltd.:pnH81M-DS2V:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnH81M-DS2V:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.:
+ dmi.product.name: H81M-DS2V
+ dmi.product.version: To be filled by O.E.M.
+ dmi.sys.vendor: Gigabyte Technology Co., Ltd.

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

Title:
  Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-
  block(0,0)

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

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

[Bug 1653636] Re: Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0, 0)

I have executed the command `apport-collect 1653636` as requested by
brad-figg.  I can see that log files have been added.

Note that this command was performed while running 4.4.0-57-generic not
the 4.4.21 kernel that causes the issue.  It is also worth noting that
as the filesystem could not be mounted the kernel panic trace was not
recorded to disk and as a result is not included in any of the attached
log files.

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

Title:
  Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-
  block(0,0)

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

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

[Bug 1653636] ProcInterrupts.txt

apport information

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

Title:
  Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-
  block(0,0)

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

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

[Bug 1653636] UdevDb.txt

apport information

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

Title:
  Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-
  block(0,0)

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

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

[Bug 1653636] JournalErrors.txt

apport information

** Attachment added: "JournalErrors.txt"
   
https://bugs.launchpad.net/bugs/1653636/+attachment/4799330/+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/1653636

Title:
  Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-
  block(0,0)

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

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

[Bug 1653636] Lsusb.txt

apport information

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

Title:
  Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-
  block(0,0)

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

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

[Bug 1653636] PulseList.txt

apport information

** Attachment added: "PulseList.txt"
   
https://bugs.launchpad.net/bugs/1653636/+attachment/4799337/+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/1653636

Title:
  Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-
  block(0,0)

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

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

[Bug 1653636] CurrentDmesg.txt