** 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:
*** 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,
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.
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
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
Nothing new comes out in the crash report.
When I visit
https://errors.ubuntu.com/user/1d81a00d35531ca846cc8b470c853c9c4cc299c3a0a42040e68da92210168a3d96818f5de95d8f7d85e66516d77e481a6259123145189d1685f6d22ac584114a
the most recent report is:
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
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
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
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-
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:
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
I got another automated crash prompt to come up. This generated
+bug1791278 (which is marked as private right now, but I shall try to
change that when appropriate).
I had tried running octave as root to see if that changed the
unavailable resource mentions in the strace. I now see SIGABRT in
Further diagnostic suggestions were to try:
$ octave --norc
octave exited with signal 6
$ octave --no-gui-libs
GNU Octave, version 4.2.2
$ octave-cli
GNU Octave, version 4.2.2
So the problem seems to be related to the GUI libraries for me. I am
not much help at diagnosing more than that. I
Public bug reported:
Before my update to Ubuntu 18.04 I was using Octave under 16.04. I am
not a frequent Octave user (once every few months). I updated to 18.04
a couple of months ago and tried running octave today only to find that
it would not start from my command line. Instead, I see:
$
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
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
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.
$
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
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
$ 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
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
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
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
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
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
--
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
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.
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
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
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
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
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
*** 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
*** 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
Happened again today. Raised #1760792 this morning to see if the trace
will work. If it does not I shall try adding more -dev packages to see
if the backtrace can be brought about.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
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
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
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
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,
** Bug watch added: Debian Bug tracker #825101
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=825101
** Also affects: clang (Debian) via
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=825101
Importance: Unknown
Status: Unknown
--
You received this bug notification because
** Also affects: clang (Debian) via
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=825101
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/1578803
Seems simple enough to recreate this each time I restart the machine.
--
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
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
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
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:
I have now raised a bug with Google / Android tools at
https://issuetracker.google.com/issues/68131667
The Debian package maintainers suggested this was the bug tracker I should
probably be using
http://lists.alioth.debian.org/pipermail/android-tools-devel/2017q4/002864.html
--
You received
Public bug reported:
I have written a manifest XML file for repo (or git-repo depending on
how you like to name it). To help check my syntax, I attempted to
generate a Document Type Definition (DTD) file to go with it based on
the repo Manifest Format text document. When I include a line in my
I am doing OK at being taken to this page every few months.
--
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
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.
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
Eyeballed the attachments and cannot see anything sensitive in them.
Making this public instead of private.
** 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.
Make that 8 years ago.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/376859
Title:
crashed on AMD64
To manage notifications about this bug go to:
Eyeballed the attachments. Looks safe to make public.
** 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/1702879
Title:
crashed with SIGABRT in
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
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:
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
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'
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
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
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
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
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
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
To finish off my confirmation of the fix, I did not see any email
notifications overnight. When I look at the relevant log files I can
see the rotation is progressing:
$ ls -l /var/log/apt-cacher-ng/apt-cacher.err*
-rw-r--r-- 1 apt-cacher-ng apt-cacher-ng 0 Apr 5 06:28
The proposed change added under https://launchpad.net/~ci-train-ppa-
service/+archive/ubuntu/2623 seems to have resolved my issue.
Before the change I received an email stating:
/etc/cron.daily/logrotate:
error: error creating output file /var/log/apt-cacher-ng/apt-cacher.err.1.gz:
File exists
Is bug #1663453 also a duplicate of this bug? I raised two bugs
yesterday that I thought were probably the same but one got marked as a
duplicate of this bug and the other was marked as a duplicate of bug
#1663453. My two bugs were bug #1678877 and bug #1679233.
--
You received this bug
*** This bug is a duplicate of bug 1565332 ***
https://bugs.launchpad.net/bugs/1565332
Interesting. I expected this bug to be a duplicate of bug #1678877 that
I reported earlier in the day but it did not get identified as a
duplicate of bug #1663453 so it must be a different one.
--
You
*** This bug is a duplicate of bug 1663453 ***
https://bugs.launchpad.net/bugs/1663453
Oh good. Another bug that has been marked as a duplicate of a private
bug so I cannot tell if it should or should not be a duplicate of it.
This bug is not marked as private any more. Please can someone
Installing for 16.04 xenial on a machine that has just reproduced the
issue on its own. If I do not see the error message emailed out to me
tonight then it is likely that the fix has succeeded. I shall try to
post an update promptly, sorry for the delay.
--
You received this bug notification
*** This bug is a duplicate of bug 910566 ***
https://bugs.launchpad.net/bugs/910566
Public bug reported:
Having installed munin-plugins-core, a LAMP stack and the other packages
to run a Munin node I have discovered that the mysql_ plugin will not
run as a library file it requires is
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
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
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
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
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
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
@jarnos mentions having generated a script to remove extra kernels.
There is already a purge-old-kernels command line tool lingering in the
bikeshed package.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
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:
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
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
Thank you Joseph, the upstream kernel from months ago was the cause of
the issue. I had completely forgotten about it being there and did not
recognise the change in version numbering as significant.
I followed the steps outlined in http://askubuntu.com/a/594484/109072 to
remove the kernel and a
Seen in an email this morning from a 16.04 system:
/etc/cron.daily/apt:
MarkUpgrade() called on a non-upgrable pkg: 'linux-image-4.4.0-59-generic'
MarkUpgrade() called on a non-upgrable pkg: 'linux-tools-3.13.0-107-generic'
MarkUpgrade() called on a non-upgrable pkg: 'linux-tools-3.13.0-107'
I expect I got the kernel the same way I get most of my kernels, though
an `apt-get upgrade`. Although I did try and compile a kernel a while
ago... I wonder if that got left around as an install option and it was
so long since I last rebooted I forgot about it!
Now isn't that a silly thing to
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:
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
apport information
** Attachment added: "CurrentDmesg.txt"
https://bugs.launchpad.net/bugs/1653636/+attachment/4799329/+files/CurrentDmesg.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
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.
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:
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
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
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.
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:
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
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,
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
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:
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
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"
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
1 - 100 of 303 matches
Mail list logo
