Ahh.. That's what it checks. No need. My problem then is I haven't been
using do-release-upgrade to do updates for a long time.
I have a ton of complicated dependencies that always seem to fail on
upgrade, so I've been manually replacing the codename in
/etc/apt/sources.list for each upgrade.
So
Public bug reported:
For whatever reason, when I run apport-bug or apport-cli, the crash file that
is generated/submitted contains the line:
UpgradeStatus: Upgraded to bionic on 2014-12-03 (1344 days ago)
Obviously this is wildly incorrect, and I'm not even sure how this value
was obtained. (I
FYI, this is fixed in Bionic running the latest NVidia drivers and KDE
version.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1756997
Title:
plasmashell leaks memory uncontrollably
To manage
Console output from apport-valgrind attached,
NB: I invoked it with:
/usr/bin/apport-valgrind -l valgrind.$$.log -C ./cache -v /usr/bin/plasmashell
< /dev/null &> apport-valgrind.$$.log &
** Attachment added: "Console output from apport-valgrind"
Public bug reported:
I'm not sure if this is a problem with the plasmashell executable
itself, or the the nvidia libraries, or perhaps plasmashell not
interacting with the nvidia libraries correctly, but for the past
several months I've noticed that the memory usage of plasmashell creeps
slowly
Out of curiosity, can you link me to the upstream git repo for
http://kernsec.org/pipermail/linux-security-module-
archive/2017-December/004638.html? I want to be sure I'm looking at the
right place.
Interestingly, it looks like someone replied to your patch saying they
would incorporate it in
Thanks!
Should I mark this bug as a duplicate then?
Also, what is the process/timeline for that patch you linked being
applied downstream into Artful?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Okay, the bug still exists in 4.13.0-21-generic, but went away in
4.13.0-25-generic once I removed 'apparmor=0'. So I think Tetsuo may be
on to something.
Could this be a duplicate of this[0] bug? This would make sense
considering the message of one the problematic commits is "add stacking
Okay, I tested it with 4.15.0-041500rc7-generic and the issue
disappeared. Thanks!
Does that provide any insight into what exactly the error is and/or a
possible workaround?
Unfortunately I'm unable to use this kernel in the interim as I rely on
the Nvidia kernel modules, which aren't compiling
Public bug reported:
Last night, in an attempt to secure my system against Meltdown/Spectre,
I upgraded from Zesty to Artful. Upon booting into the latest kernel, my
system would immediately hang and fail to respond (including to SysRq
commands).
Both this (my primary) system and an Intel NUC
Please note that I ran 'ubuntu-bug' from my most recent working kernel
(from Zesty): 4.10.0-42-generic, so some of this log output may be
inaccurate as a result.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
Crash also occurs (every time) when selecting any of the following:
- Media -> Open Multiple Files
- Media -> Open Disc
- Media -> Open Network Stream
- Media -> Open Media Device
- Media -> Convert / Save
- Media -> Stream
Each time, the console output is:
ASSERT failure in
Disregard this bug report. It is missing my core dump.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1587573
Title:
VLC Crashes on Media -> Open Media Device
To manage notifications about this bug
Disregard this bug. It is missing the core dump.
** Changed in: vlc (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1587574
Title:
VLC Crashes on Media Menu
** Changed in: vlc (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1587573
Title:
VLC Crashes on Media -> Open Media Device
To manage notifications about this
Public bug reported:
Crash also occurs (every time) when selecting any of the following:
- Media -> Open Multiple Files
- Media -> Open Disc
- Media -> Open Network Stream
- Media -> Convert / Save
- Media -> Stream
Each time, the console output is:
ASSERT failure in QList::operator[]: "index
I'm experiencing the same behavior as LStranger. My IP aliases are
coming up, but they're just not reflected anywhere as online (in either
ifconfig or ip).
I can do the following and see the actual commands being run to bring up
the interfaces, which as far as I can tell are working correctly
** Attachment added: pidgin-backtrace5.log
https://bugs.launchpad.net/ubuntu/+source/orc/+bug/675054/+attachment/1732668/+files/pidgin-backtrace5.log
--
liborc causes segfault in pidgin when playing sound
https://bugs.launchpad.net/bugs/675054
You received this bug notification because you
Public bug reported:
This will happen when I get an IM that triggers a sound alert, or even
when I go into preferences and preview a sound.
Expected Result: Sound plays and segfault does not occur.
Actual Result: Sound does not play, segfault occurs.
Backtrace attached.
Please let me know if I
--
liborc causes segfault in pidgin when playing sound
https://bugs.launchpad.net/bugs/675054
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
** Bug watch added: Pidgin Trac #12880
http://developer.pidgin.im/ticket/12880
** Also affects: pidgin via
http://developer.pidgin.im/ticket/12880
Importance: Unknown
Status: Unknown
--
liborc causes segfault in pidgin when playing sound
https://bugs.launchpad.net/bugs/675054
21 matches
Mail list logo
