Title should read 22.04 LTS to version 24.04 LTS
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2083756
Title:
Upgrading Ubuntu 22.04.5 LTS to version 24.04 LTS failed.
To manage notifications about
Public bug reported:
The upgrade died before completing. I have no DNS (no resolved). Every
network access gives "Temporary failure in name resolution." I have
tried suggestions from this forum, but most require an "apt install"
that further need to access us.archive.ubuntu.com (or similar), wh
@mruffell my change has been pulled into the latest stable 5.4 and 5.15
kernel queues:
https://git.kernel.org/pub/scm/linux/kernel/git/stable/stable-
queue.git/tree/queue-5.4/tcp-check-skb-is-non-null-in-
tcp_rto_delta_us.patch
https://git.kernel.org/pub/scm/linux/kernel/git/stable/stable-
queue.
Thanks @mruffell. No, we're not running a custom kernel. We've just
disabled the 2 sysctsl I mentioned, tcp_early_retrans and tcp_recovery,
for now to mitigate the issue. I just checked and it looks like my
change applies cleanly to the HEAD of focal. I think we'd like to see it
applied to both 5.4
My mitigation was accepted upstream:
https://lore.kernel.org/netdev/172708862651.3320223.2618494280244639290.git-
patchwork-not...@kernel.org/
@mruffell I believe this should be picked up by the stable maintainers.
Do you know how long it will take once it lands there until it's in an
official Ubu
following may be more
appropriate:
Author: Josh Hunt
Date: Tue Jul 30 19:45:43 2024 -0400
tcp: check skb is non-NULL before using in tcp_rto_delta_us()
There have been multiple occassions where we have crashed in this path
because
packets_out suggested there were packets
** Attachment added: "uname-a.log"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2077657/+attachment/5808086/+files/uname-a.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2077657
Title:
** Attachment added: "lspci-vnvn.log"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2077657/+attachment/5808087/+files/lspci-vnvn.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2077657
T
a_us() to check that
the skb is non-null b/f trying to read the timestamp. Possibly something
like this:
Author: Josh Hunt
Date: Tue Jul 30 19:45:43 2024 -0400
workaround empty rtx queue
diff --git a/include/net/tcp.h b/include/net/tcp.h
index 2aac11e7e1cc..d1e2ecbce536 100644
--- a/incl
I finally resorted to the uninstall snap workaround. Annoying users and
being intrusive is a solid way to ensure the success of a package you're
responsible for.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.ne
Hey,
I just signed the petition "Julius Jones is innocent. Don't let him be
executed by the state of Oklahoma." and wanted to see if you could help by
adding your name.
Our goal is to reach 7,500,000 signatures and we need more support. You can
read more and sign the petition here:
https://chng.
Public bug reported:
In Impish (canary), when attempting to use the installer with the Orca
screen reader for accessibility, Orca cannot determine the states or
roles of the form controls, and they all appear as 'grayed'. When I
select an item, no feedback is given. To reproduce: start the Orca
Focal as well:
Err:19 http://ddebs.ubuntu.com focal Release.gpg
The following signatures were invalid: EXPKEYSIG C8CAB6595FDFF622 Ubuntu
Debug Symbol Archive Automatic Signing Key (2016)
--
You rece
Probably a bad/currupted hard drive. been having issues with it. still
trying to fix.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1874662
Title:
Corrupted installation medium
To manage notificati
Of note this bug may eventually be overtaken by events. I installed
Lubuntu 19.04, which does not use light-locker and it works fine.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1817922
Title:
lig
After some extensive testing I have further information to report that
may help solve this issue.
I can confirm that the issue exists in Lubuntu 18.04.2, Lubuntu 18.10,
Xubuntu 18.04.2 and Xubuntu 18.10, all of which use light-locker 1.8.0.
Of interest a fresh installation of the original Lubuntu
Same problem seen with light-locker 1.8.0 on Lubuntu 18.04 LTS and
Xubuntu 18.10
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1817922
Title:
light-locker 1.7
To manage notifications about this bug
Thanks for taking a look, Tianon. You're right that Docker appears to be
behaving normally... running journalctl -b I see that the system did in
fact reboot causing the Docker shutdown, and that it came back online at
19:29:45 with multiuser system target being reached at 19:30:04.
So my issue is
Edit to add: the second docker ps resolved the issue at 2018-12-12
21:18:41, and the results of that command showed that all containers had
been restarted at that instant.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.la
** Attachment added: "docker_stack_trace.txt"
https://bugs.launchpad.net/ubuntu/+source/docker.io/+bug/1808266/+attachment/5221826/+files/docker_stack_trace.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad
Public bug reported:
This event ocourred on a single-node Docker.io version
18.06.1-0ubuntu1~18.04.1, Docker version Docker version 18.06.1-ce,
build e68fc7a, Ubuntu version 18.04.1 LTS, kernel Linux
4.15.0-42-generic #45-Ubuntu SMP Thu Nov 15 19:32:57 UTC 2018 x86_64
x86_64 x86_64 GNU/Linux.
At
Reported as https://gitlab.gnome.org/GNOME/gdm/issues/438.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1800277
Title:
"chmod u-w ~/.ICEauthority" breaks login
To manage notifications about this b
apport information
** Tags added: apport-collected bionic
** Description changed:
= Problem =
It is too easy to make a system unusable.
= Examples
The following commands will all cause subsequent graphical logins to
fail:
== User is returned to login screen ==
- chmo
apport info added.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1800277
Title:
"chmod u-w ~/.ICEauthority" breaks login
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubu
apport information
** Attachment added: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/1800277/+attachment/5206696/+files/ProcCpuinfoMinimal.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/
I can do that if really required, but this is not a bug with my system -
it's just the way the system works right now, so I'm suggesting an idea
for how we can make it better :)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://b
Public bug reported:
= Problem =
It is too easy to make a system unusable.
= Examples
The following commands will all cause subsequent graphical logins to
fail:
== User is returned to login screen ==
- chmod 400 ~/.ICEauthority
- rm ~/.ICEauthority
In this scenario, the user is returned to t
I have confirmed that the latest Cosmic development release with this
package version 0.6.1-1 appears to work correctly now. Was able to sign
in to Docker fine on a headless EC2 server over SSH.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Public bug reported:
As of July 19, 2018 the following bug fix was merged in upstream:
https://github.com/docker/docker-credential-helpers/pull/29
The code being shipped by Ubuntu (bionic) now calls the wrong free
function which produces errors on every docker build while this package
is installe
see https://github.com/moby/moby/issues/37916 for the problem caused by
this dependency chain
** Bug watch added: github.com/moby/moby/issues #37916
https://github.com/moby/moby/issues/37916
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Public bug reported:
Not sure why this is a dependency of docker-compose, it isn't mentioned
in upstream install instructions, which just ships a binary:
https://docs.docker.com/compose/install/#install-compose. And it isn't a
dependency on Debian either: https://packages.debian.org/stretch/docker
Of note this seems to be related to a Java update that was recently
rolled out.
Also the LaunchPad feature " This bug affects 1 person. Does this bug
affect you?" seems to be non-functional. It consistently returns
"Timeout error, please try again in a few minutes." Based on the scope,
I suspect t
If this helps, opening jEdit fails in all attempts, across all devices.
When attempting (and failing) to open from a terminal it returns:
2:38:31 PM [main] [error] main: Exception in thread "main"
2:38:31 PM [main] [error] main: java.awt.AWTError: Assistive Technology not
found: org.GNOME.Access
ation of the package asking for latex-
xcolor seemed to be working fine on my system with "texlive-latex-
recommended" installed. But the missing dependency warning is very
annoying.
Yours faithfully
Dylan Hunt
** Affects: texlive-base (Ubuntu)
Importance: Undecided
Status:
Public bug reported:
Expected Behavior:
When starting the mate-tweak application, using orca screen reader for feadback
and navigation, user can move among the tabs, using only the keyboard.
Actual Behavior: Only the 'desktop icons' tab is visible to the screen reader.
** Affects: ubuntu-mate
Public bug reported:
Expected Action:: When moving among the indicator applet menus, using
the cursor keys, orca should speak the name of each menu as cursor lands
on it, E. G. 'network', 'power', ...
Actual Action: Orca speaks the word, "menu", and one must move down the
menu to discover its
Public bug reported:
There is 1 error.
ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: mysql-server-5.7 5.7.22-0ubuntu0.16.04.1
ProcVersionSignature: Ubuntu 4.13.0-39.44~16.04.1-generic 4.13.16
Uname: Linux 4.13.0-39-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.16
Architecture: amd64
D
The patch does not work if you have more than one TPM device in your
machine (I don't know if that is a common thing or not).
sudo systemctl restart trousers.service
Apr 13 13:39:45 CRK-CORP-69 trousers[22117]: Starting Trusted Computing daemon:
tcsd/etc/init.d/trousers: 32: [: /dev/tpm0: unexpec
got this too. but not virtualbox installation. on older hardware.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1752950
Title:
deja-dup-monitor crashed with SIGSEGV in __pthread_once_slow()
To mana
DisplayPort MST seems to work with open-source drivers on Ubuntu 16.04.3
after installing HWE + latest kernel (4.15.2). No kernel parameters
needed, it just works.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.
Public bug reported:
Tried to update and this is the error I recieved
ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: systemd 235-3ubuntu3
ProcVersionSignature: Microsoft 4.4.0-43-Microsoft 4.4.35
Uname: Linux 4.4.0-43-Microsoft x86_64
ApportVersion: 2.20.1-0ubuntu2.15
Architecture: amd
Public bug reported:
Had Ubuntu 8.04 on hp elitebook 8440p , but only for a few days. Wanted to
remove it and install the 16.04.3 because wifi did not work in the 8.04. The
installer could not remove 8.04, so I used the manual partition tool they
offered to give the newer version the maximum ro
Been seeing this sporadically since 17.04 upgrade. I have an NVIDIA
GeForce GT 740 running the proprietary driver, so it isn't nouveau in my
case. Only common activity that sticks in my mind is that it seems to
have occurred for me when (or shortly after) doing something with
VirtualBox - starting
*** This bug is a duplicate of bug 1671273 ***
https://bugs.launchpad.net/bugs/1671273
** This bug has been marked a duplicate of bug 1671273
PulseAudio requirement breaks Firefox on ALSA-only systems
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Note that "ALSA-only systems" particularly affects all Lubuntu users.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1671273
Title:
PulseAudio requirement breaks Firefox on ALSA-only systems
To man
After looking around in my BIOS I found an option for either "advanced"
or "basic" touch pad. If I'm on advanced, the touch pad does not work in
Ubuntu, but it will if I'm in basic mode. I've install Ubuntu alongside
Windows 10, and unfortunately basic mode removes all multi-touch
capabilities for
Public bug reported:
On a fresh install of Ubuntu 16.04.02 the touch pad was never detected.
However, external USB mouse works fine. Reporting this bug after
following instructions at
https://wiki.ubuntu.com/DebuggingTouchpadDetection.
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: linux-i
Public bug reported:
Bash sometimes dies with a SIGABRT on the command
read -N $N < /dev/urandom
where $N represent an integer >=1.
It occurs frequently for high values of N (>2**20).
It occurs rarely for low values of N (<2**20).
It has occurred more than once with a value of N as low as
** Changed in: initramfs-tools (Ubuntu)
Assignee: Peter Hunt (tigerite) => (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1540390
Title:
Backport more recent driver for SKL,
** Changed in: initramfs-tools (Ubuntu)
Assignee: (unassigned) => Peter Hunt (tigerite)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1540390
Title:
Backport more recent driver for SKL,
Public bug reported:
Today is the first day I've used Ubuntu Mate and I was trying to install
software when this bug appeared
ProblemType: Package
DistroRelease: Ubuntu 15.10
Package: libphonon4:i386 4:4.8.3-0ubuntu2
ProcVersionSignature: Ubuntu 4.2.0-27.32-generic 4.2.8-ckt1
Uname: Linux 4.2.0-2
Public bug reported:
Installing LibreCad when problem reported
ProblemType: Package
DistroRelease: Ubuntu 14.10
Package: linux-image-extra-3.19.0-28-generic 3.19.0-28.30~14.04.1
ProcVersionSignature: Ubuntu 3.19.0-28.30~14.04.1-generic 3.19.8-ckt5
Uname: Linux 3.19.0-28-generic x86_64
ApportVersi
Public bug reported:
The touchpad is seen as a generic PS/2 mouse. Clicking, including tap
clicking, works fine. No touchpad-specific options (such as scroll) are
available in the mouse and touchpad settings.
ProblemType: Bug
DistroRelease: Ubuntu 15.04
Package: xserver-xorg-input-synaptics 1.8
Public bug reported:
Kazam screen capture failed to open, resulting in this report
ProblemType: Package
DistroRelease: Ubuntu 15.04
Package: rpm-common 4.11.3-1.1
ProcVersionSignature: Ubuntu 3.19.0-28.30-generic 3.19.8-ckt5
Uname: Linux 3.19.0-28-generic x86_64
ApportVersion: 2.17.2-0ubuntu1.4
A
Sorry I have recently rechecked this and my initial confirmation was in
error, please disregard.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1448528
Title:
freshclam service failure due to missing
Yep - that was handled with lp:~jamesodhunt/goget-ubuntu-touch/add-list-
images-option.
** Changed in: goget-ubuntu-touch (Ubuntu)
Status: Incomplete => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.
Hi Steve - ah, sorry - hadn't registered that you'd already copied the
package into the queue (we now have 2 :-) Could mine be deleted please?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1447756
Tit
** Description changed:
+ = Summary =
+
+ The version of Upstart in vivid is affected by a coule of bugs relating
+ to the flushing data from early-boot jobs to disk which can both result
+ in a crash:
+
+ == Problem 1 ==
+
+ An internal list is mishandled meaning a crash could occur randomly.
** Changed in: upstart (Ubuntu Vivid)
Status: New => In Progress
** Changed in: upstart (Ubuntu Vivid)
Assignee: (unassigned) => James Hunt (jamesodhunt)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Unfortunately, ondra no longer has the failing phones so we may need to
take a decision to just land this if QA are happy the change has not
regressed the behaviour for non-failing phones.
I've tried to raise QA but they are sprinting in the US this week so no
direct response.
I believe that sil2
Thanks for nudging -proposed Steve.
I've silo 021 now includes upstart version 1.13.2-0ubuntu13.1 (which
sil2100 synced from wily).
Basic test plan is here: https://wiki.ubuntu.com/Process/TestPlans
/upstart-bug-1447756
I've tested this as follows:
$ wget http://people.canonical.com/~jhm/baraj
Hi Andy - any progress on this? Although the buildd's are running older
kernels, it seems that the DEP-8 Jenkins environment is running 3.19 and
is thus causing upstart tests to fail. For example:
https://jenkins.qa.ubuntu.com/view/Wily/view/AutoPkgTest/job/wily-adt-
upstart/ARCH=amd64,label=adt/l
Looks like kernel bug 1429756 could block 1.13.2-0ubuntu14 landing for
wily (being a pre-req to getting this fix into vivid and utopic):
https://jenkins.qa.ubuntu.com/view/Wily/view/AutoPkgTest/job/wily-
adt-upstart/ARCH=amd64,label=adt/9/
--
You received this bug notification because you ar
** Also affects: upstart (Ubuntu Utopic)
Importance: Undecided
Status: New
** Also affects: upstart (Ubuntu Wily)
Importance: Critical
Assignee: James Hunt (jamesodhunt)
Status: In Progress
** Also affects: upstart (Ubuntu Vivid)
Importance: Undecided
Status
** Changed in: upstart
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1447756
Title:
segfault in log.c code causes phone reboot loops
To manage notificati
MP raised on lp:upstart to start the trickle-down to the rtm package.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1447756
Title:
segfault in log.c code causes phone reboot loops
To manage notific
Applying the top 2 commits (r1665 and r1666) from
lp:~jamesodhunt/upstart/bug-1447756-the-actual-fix [1] to
https://bugs.launchpad.net/ubuntu-
rtm/+source/upstart/1.13.2-0ubuntu1rtm1 is now working for me.
I've tested this by building on the device itself and also by building
in a ARCH=armhf utopi
lp:~jamesodhunt/upstart/bug-1447756-the-actual-fix contains the fix and
a new test (which correctly fails with the current lp:upstart but passes
with the fix in that branch).
The code has been tested on a failing device and a server system. I am
currently testing on a non-failing krillin device. I
** Changed in: upstart (Ubuntu)
Status: Confirmed => In Progress
** Changed in: upstart
Status: New => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1447756
Title:
segfaul
\o/. Yes, Upstart uses asserts extremely agressively. It's unfortunate
that we've never hit this issue in testing but I'm currently working on
new tests for this slightly unusual scenario.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu
Ondrej - aha! with the debug, this is making more sense now. Yes, since
the ureadahead-touch job spawns a process in the background (ureadahead)
and then the job itself exits, the log associated with the main job
process gets added to the unflushed list. ureadahead then writes output
and the NihIo
Hi Ondrej,
Regarding #15, I'm not sure this is correct. As you say, when the job
process terminates, job_process_terminated() gets called. This calls
log_handle_unflushed() and that function calls log_read_watch(), which
ultimately calls write(2). However, even if the write is successful
before 'i
Hi Ondrej,
Regarding #15, I'm not sure this is correct. As you say, when the job
process terminates, job_process_terminated() gets called. This calls
log_handle_unflushed() and that function calls log_read_watch(), which
ultimately calls write(2). However, even if the write is successful
before 'i
ondra and I have been hammering away at this, but progress is painfully
slow given that:
a) the problem is not seen on every boot.
b) we can only view the end of kmsg log.
c) rebuild times are relatively slow.
>From what ondra says he's seen today, it sounds as though we might be
hitting a stack
I've rebuild the fix in a clean environment and the init binary below
now boots fine for me on a bq aquaris E4.5:
http://people.canonical.com/~jhunt/upstart/bugs/bug-1447756/armhf/
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https
Hi ondra/ogra - Can you comment on my suggestions in #6 and #7? My
device is still bricked so if you have any suggestions on how to perform
a full reset, that'd be great as udf is unable to recover it.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscri
Public bug reported:
Upon selecting Pitivi 0.93-4.2 from the menu on Lubuntu 15.04 AMD-65
bit, nothing happens, will not launch. Upon launching from the command
line gives:
** (pitivi:4584): WARNING **: Error retrieving accessibility bus
address: org.freedesktop.DBus.Error.ServiceUnknown: The nam
I can confirm this bug on clamav 0.98.6 running on Lubuntu 15.04. I get
the same error and clamav definitions cannot be updated. This is new
upon upgrade from Lubuntu 14.10.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.
Something else to try - disable /etc/init/flush-early-job-log.conf on
boot...
$ sudo mount -oremount,rw /
$ echo manual | sudo tee /etc/init/flush-early-job-log.override
$ sudo reboot
... and post-boot do the following:
$ for i in $(seq 17); do sudo initctl notify-disk-writeable; done
As Steve
I've tried the fix on my bq device and it appears to be in a reboot loop
(like the one the fix was supposed to resolve).
As such, I'd recommend testing the binaries only for the session init
initially (/usr/bin/ubuntu-touch-session / /usr/share/lightdm/sessions
/ubuntu-touch.desktop).
Also, for b
Test binaries are available here:
http://people.canonical.com/~jhunt/upstart/bugs/bug-1447756/armhf/
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1447756
Title:
segfault in log.c code causes phone
i386+amd64 are packaged here:
https://launchpad.net/~jamesodhunt/+archive/ubuntu/bug-1447756/+packages
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1447756
Title:
segfault in log.c code causes phon
** Also affects: upstart
Importance: Undecided
Status: New
** Changed in: upstart
Assignee: (unassigned) => James Hunt (jamesodhunt)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/b
Screenshot showing the super-thin divider.
** Attachment added: "scratch.jpg"
https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1368798/+attachment/4382842/+files/scratch.jpg
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
htt
I think I understand what's happening now - it's not the log that isn't
being freed, it's the list entry the log is attached to that is not
freed. The effect is the same though - calling log_clear_unflushed()
multiple times could trigger this issue since the still-valid (but
incorectly so) list ent
** Changed in: upstart (Ubuntu)
Assignee: (unassigned) => James Hunt (jamesodhunt)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1447756
Title:
segfault in log.c code causes phone reboot lo
This issue was resolved on MP
https://code.launchpad.net/~jamesodhunt/snappy/add-transactional-
updates-doc/+merge/255719.
** Changed in: golang-phablet-tools-ubuntu-device-flash (Ubuntu)
Status: Confirmed => Invalid
** Changed in: snappy-ubuntu
Status: Confirmed => Fix Released
--
Hi,
I have this same problem, can anyone help please?
Im running an ATI Radeon Cedar HD5450 graphics card and using the open
source driver, I've tried a fresh install of Unity.
The freeze mainly happens when I'm using Video, so I figured it would
probably be something to do with the Graphics car
Public bug reported:
The s-i archives that u-d-f unpacks specify the contents of /dev.
However, running the following on a snappy system gives unexpected
results:
ubuntu@localhost:~$ ls -l /dev|grep ^-|wc -l
0
ubuntu@localhost:~$ ls -l /dev|egrep "^(b|c)"|wc -l
The inconsistency seems to originate in udf's diskimage/core_uboot.go.
** Also affects: golang-phablet-tools-ubuntu-device-flash (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
http
LKML thread: https://lkml.org/lkml/2015/3/16/474
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1429756
Title:
FTBFS: upstart test_job_process fails in majority of cases / Kernel
returning unexpect
** Package changed: upstart (Ubuntu) => chromium-browser (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1300235
Title:
init (chromium-browser) crashed with SIGSEGV
To manage notifications a
Running with a 3.19.0-8-generic kernel I see:
- The Upstart test_job_process test fail within a few seconds when run in a
loop looking for the errror.
- My test program in #13 also finds the bug within ~30 seconds on my test
system.
Using the kernel in #11, I have run both tests simultaneously
I've written a basic program that surfaces this bug. To recreate:
$ cd /tmp
$ tar xvf bug-1429756.tgz
$ cd bug-1429756
$ make
$ ./bug-1429756.sh
loop 1
loop 2
ERROR: got failure scenario after 2 loops (got=16, count=17,
log=/tmp/tmp.uwZHkHh0mc)
$
** Attachment added: "bug-1429756.tgz"
https
Playing around with strings(1), I've found this:
$ strings /usr/lib/chromium-browser/libs/libcontent.so|egrep "\"
init
The SUID sandbox created a new PID namespace but Zygote is not the init
process. Please, make sure the SUID binary is up to date.
Error creating an init process to reap zombies
F
** Summary changed:
- ubuntu-touch livefs builds kill upstart in host
+ [SRU] ubuntu-touch livefs builds kill upstart in host
** Changed in: upstart (Ubuntu)
Status: Confirmed => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribe
igh
** Changed in: upstart (Ubuntu)
Assignee: (unassigned) => James Hunt (jamesodhunt)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1430403
Title:
ubuntu-touch livefs builds kill upstart i
** Description changed:
= Summary =
The version of Upstart in precise is affected by a bug in the way that
".override" [1] file handling is performed.
If a job has an override file ("/etc/init/*.override") and that override
file is deleted before the corresponding job configuration
** Description changed:
+ = Summary =
+
+ The version of Upstart in precise is affected by a bug in the way that
+ ".override" [1] file handling is performed.
+
+ If a job has an override file ("/etc/init/*.override") and that override
+ file is deleted before the corresponding job configuration
** Also affects: upstart (Ubuntu Precise)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1430403
Title:
ubuntu-touch livefs builds kill upstart in host
To
1 - 100 of 2088 matches
Mail list logo
