Re: Ubuntu Notepad

[Dale Amon]

On Fri, May 06, 2016 at 10:13:28PM +0200, Oliver Grawert wrote:
> the phones (and tablets) actually use a rolling release model, the system
> image gets updated every 6 weeks on a fixed schedule and is still based on
> 15.04 (not the LTS) using a separate archive into which important bits get
> backported from newer releases.

That could cause me problems. I had better stay clear of dselect
(my old familiar tool) entirely since it has a tendency to suck
in more than an apt-get.

I will have to cross my fingers that I can get a full objc, GNUStep
and debian package building tools set without getting into trouble.

Also, I had not noticed it was based on an older version. That
might mean I will need to pull in the GNUstep sources and build
my own as there are release critical (for my needs) bugs that have
only recently been fixed.

Nothing is ever quite as straightforward as one would like with
software. Perhaps that is why AI's will never take over the world.
They'll need to keep us humans around to reboot them.

Dale Amon
Sr. Engineer
XCOR Aerospace


-- 
Ubuntu-devel-discuss mailing list
Ubuntu-devel-discuss@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss

Re: Ubuntu Notepad

[Oliver Grawert]

hi,
Am Freitag, 6. Mai 2016 21:43:07 CEST schrieb Dale Amon :



As to updates... the next LTS is years away. I think we will have
gone through a lot of these lovely little rectangles by then.

the phones (and tablets) actually use a rolling release model, the system 
image gets updated every 6 weeks on a fixed schedule and is still based on 
15.04 (not the LTS) using a separate archive into which important bits get 
backported from newer releases.


if the system is indeed only for toying around and security (and thus 
upgrading) does not matter for you, this is a moot point :)


(note though thaat upgrading using apt will not work either, the system is 
designed for image based upgrades only, an apt based upgrade will 
eventually fail if it hits a package that is bound to this setup)



and as robie said, the ubuntu-phone list [3] is far more appropriate for
the phone and tablet installs where you also will find other users that
have experience with these things.


Thank you for that extra tidbit. I had contacted the list owner to
find out if they covered tablets as well. So the answer is yes.

And so I will, as I will probably need advice on other things.

Now I must get back to work. I've got subversion installed and I am
about to suck in a working set of our toys.


good luck with that :)

ciao
   oli


--
Mit Dekko von meinem Ubuntu-Gerät gesendet

--
Ubuntu-devel-discuss mailing list
Ubuntu-devel-discuss@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss

Re: Ubuntu Notepad

[Dale Amon]

On Fri, May 06, 2016 at 03:51:37PM +0200, Oliver Grawert wrote:
> note that this will likely break as soon as you do the next OTA update
> and long term you will run out of space on the readonly system
> partition ... 
>
> generally it is a very bad idea to make the system writable, either use
> a libertine container in the writable space [1] or if you dont want to
> use any graphical apps, follow [2] 

All of which depends on the goal. Mine is to port and get functioning
an existing inhouse application as quickly and painlessly as possible.
I am not working on general purpose consumer software. I got it purely 
as a single use dedicated aerospace appliance.

Don't get me wrong... it looks like a very nice notepad, but I
acquired it as a platform for our existing software because for
rapid turn around I need to just do to it what I do to any Linux
platform. Before I had no choice except iPad and its walled garden
that forces you to use it the way they want you to use it.

I will be setting it up to compile and build ARM debian packages
for our library and GNUstep front end and I will then install them
and whatever else is needed. My intent is to have it up
and running for our Monday afternoon electrical systems meeting.

Nothing else on the machine matters; we could delete it all if space
became an issue. For safety reasons I might even ended up setting it 
to come up into our program at the end of the start up process.

As to updates... the next LTS is years away. I think we will have
gone through a lot of these lovely little rectangles by then.

> and as robie said, the ubuntu-phone list [3] is far more appropriate for
> the phone and tablet installs where you also will find other users that
> have experience with these things.

Thank you for that extra tidbit. I had contacted the list owner to
find out if they covered tablets as well. So the answer is yes.

And so I will, as I will probably need advice on other things.

Now I must get back to work. I've got subversion installed and I am
about to suck in a working set of our toys.

Dale Amon
Sr. Engineer
XCOR Aerospace

-- 
Ubuntu-devel-discuss mailing list
Ubuntu-devel-discuss@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss

Xenial startup disk creator and custom ISO

[Darren Landoll]

Are there any current issues with creating a custom Ubuntu Install CD
(server install for my particular case) and using Startup Disk Creator in
Ubuntu 16.04 to burn a custom *.iso file to a USB drive?

It claims to finish successfully (does not take as long as I would expect),
but does not result with a bootable USB drive.

I create the *.iso based on instructions here:
https://help.ubuntu.com/community/InstallCDCustomization
-- 
Ubuntu-devel-discuss mailing list
Ubuntu-devel-discuss@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss

Re: installation kubuntu 16.10 (may 1st 2016)

[André Verwijs]

Thank you :) for adding...


André






__
La Ventura (heavy metal band) Tumblr page:
http://laventurafan.tumblr.com

My Twitter Page:
http://twitter.com/OpenSimFan

My Facebook page (be my friend, please )
http://www.facebook.com/andre.verwijs

My Google+ page (follow me please )
André Verwijs - Google+ https://plus.google.com/111310545842863442992


--
Ubuntu-devel-discuss mailing list
Ubuntu-devel-discuss@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss

Re: resolvconf update script failure leads to forgotten device

[corey kasten]

Hi Tobias:

Thank you for your quick and thoughtful response!

On Fri, May 6, 2016 at 6:03 AM, Tobias Brunner 
wrote:

> Hi Corey,
>
> > 1. Call "resolvconf --disable-updates"
> > 2. Call resolvconf the way it is currently in
> > invoke_resolveconf(). This has the effect of installing or
> > deleting the interface without running the update script, and
> > the exit code returned by "pclose()" will tell you whether the
> > resolvconf install succeeded.
> > 3. Call "resolvconf --enable-updates" which will cause the
> > postponed update scripts to be run, and the errors here can be
> > ignored or logged with "DBG1()".
> > 4. Return the pclose() return value from ste
>
> Not sure if that's such a good idea.  Don't failed update scripts
> indicate a serious problem? Actually, resolvconf does not seem to do

much besides some basic checks and writing the passed data to an
> interface file before running the update scripts, of which update.d/libc
> seems to do the main work of actually "installing" the DNS server by
> writing resolv.conf.


Good point. It's not wise to continue as if nothing has gone wrong,
when, as far as we know, it could be the "installing" done within
update.d/libc itself that went wrong, even though, in my case, that
part succeeded, while it was one of the sub-scripts under update-libc.d
which failed. So, it's better and simpler to always return failure.

Also, in order to enhance the debuggability for the case where update
scripts failed, I'd recommend trying to capture stderr of the resolvconf
calls, and sending it to the ike debug log. From my testing, I can see that
the 'run-parts' program (which is called by /sbin/resolvconf in order to run
the update scripts) does a good job of telling you which scripts exited
non-zero, and this would be useful to see in the log alongside the
"[IKE] adding DNS server failed" message, if possible.


>

So perhaps we could just recursively call
> invoke_resolvconf(FALSE) if pclose() indicates the command failed.  That
> way the interface file is at least removed again.
>
>
This seems to be a very good solution. This would definitely fix my case,
where the "install" part in update.d/libc actually succeeded (and the part
that failed was one of the sub-scripts under update-libc.d), since the
follow-up, recursive invoke_resolvconf(FALSE) call would not only delete
the interface file, but also trigger a successful "uninstall" operation
performed
by update.d/libc (even though my failing sub-script in update-libc.d would
still, thereafter, fail, but, if, as mentioned above, stderr is captured,
that would
be easily debugged).


> Regards
> Tobias
>

Let me know if you need help with anything...

Thanks!
Corey
-- 
Ubuntu-devel-discuss mailing list
Ubuntu-devel-discuss@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss

Re: resolvconf update script failure leads to forgotten device

[Tobias Brunner]

Hi Corey,

> 1. Call "resolvconf --disable-updates"
> 2. Call resolvconf the way it is currently in
> invoke_resolveconf(). This has the effect of installing or
> deleting the interface without running the update script, and
> the exit code returned by "pclose()" will tell you whether the
> resolvconf install succeeded.
> 3. Call "resolvconf --enable-updates" which will cause the
> postponed update scripts to be run, and the errors here can be
> ignored or logged with "DBG1()".
> 4. Return the pclose() return value from step 2.

Not sure if that's such a good idea.  Don't failed update scripts
indicate a serious problem?  Actually, resolvconf does not seem to do
much besides some basic checks and writing the passed data to an
interface file before running the update scripts, of which update.d/libc
seems to do the main work of actually "installing" the DNS server by
writing resolv.conf.  So perhaps we could just recursively call
invoke_resolvconf(FALSE) if pclose() indicates the command failed.  That
way the interface file is at least removed again.

Regards,
Tobias


-- 
Ubuntu-devel-discuss mailing list
Ubuntu-devel-discuss@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss

Kubuntu 16.10 - plasma 5 crash after installation nvidia driver....

[André Verwijs]

Kubuntu 16.10

plasma 5 crash after  installation nvidia driver
i've added a backtrace output. No idea where to report (bug.kde.org, 
ubuntu)



André








__
La Ventura (heavy metal band) Tumblr page:
http://laventurafan.tumblr.com

My Twitter Page:
http://twitter.com/OpenSimFan

My Facebook page (be my friend, please )
http://www.facebook.com/andre.verwijs

My Google+ page (follow me please )
André Verwijs - Google+ https://plus.google.com/111310545842863442992


Application: Plasma (plasmashell), signal: Aborted
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f5e4212e8c0 (LWP 1650))]

Thread 7 (Thread 0x7f5e2e32a700 (LWP 1653)):
#0  0x7f5e3c836e8d in poll () at ../sysdeps/unix/syscall-template.S:84
#1  0x7f5e40900c62 in ?? () from /usr/lib/x86_64-linux-gnu/libxcb.so.1
#2  0x7f5e409028d7 in xcb_wait_for_event () from 
/usr/lib/x86_64-linux-gnu/libxcb.so.1
#3  0x7f5e30aaa629 in QXcbEventReader::run (this=0x19f3590) at 
qxcbconnection.cpp:1253
#4  0x7f5e3cf3184e in QThreadPrivate::start (arg=0x19f3590) at 
thread/qthread_unix.cpp:331
#5  0x7f5e3c0196fa in start_thread (arg=0x7f5e2e32a700) at 
pthread_create.c:333
#6  0x7f5e3c842b5d in clone () at 
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 6 (Thread 0x7f5e24a90700 (LWP 1655)):
#0  0x7f5e3c836e8d in poll () at ../sysdeps/unix/syscall-template.S:84
#1  0x7f5e395cb31c in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7f5e395cb42c in g_main_context_iteration () from 
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7f5e3d168a9b in QEventDispatcherGlib::processEvents 
(this=0x7f5e28c0, flags=...) at kernel/qeventdispatcher_glib.cpp:420
#4  0x7f5e3d10fdea in QEventLoop::exec (this=this@entry=0x7f5e24a8fce0, 
flags=..., flags@entry=...) at kernel/qeventloop.cpp:204
#5  0x7f5e3cf2c8a4 in QThread::exec (this=) at 
thread/qthread.cpp:503
#6  0x7f5e3f7d43c5 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5
#7  0x7f5e3cf3184e in QThreadPrivate::start (arg=0x1b21500) at 
thread/qthread_unix.cpp:331
#8  0x7f5e3c0196fa in start_thread (arg=0x7f5e24a90700) at 
pthread_create.c:333
#9  0x7f5e3c842b5d in clone () at 
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 5 (Thread 0x7f5e1ad56700 (LWP 1656)):
#0  0x7f5e3960fa60 in g_mutex_unlock () from 
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#1  0x7f5e395cb1cd in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7f5e395cb42c in g_main_context_iteration () from 
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7f5e3d168a9b in QEventDispatcherGlib::processEvents 
(this=0x7f5e140008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:420
#4  0x7f5e3d10fdea in QEventLoop::exec (this=this@entry=0x7f5e1ad55ce0, 
flags=..., flags@entry=...) at kernel/qeventloop.cpp:204
#5  0x7f5e3cf2c8a4 in QThread::exec (this=) at 
thread/qthread.cpp:503
#6  0x7f5e3f7d43c5 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5
#7  0x7f5e3cf3184e in QThreadPrivate::start (arg=0x1bf6bf0) at 
thread/qthread_unix.cpp:331
#8  0x7f5e3c0196fa in start_thread (arg=0x7f5e1ad56700) at 
pthread_create.c:333
#9  0x7f5e3c842b5d in clone () at 
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 4 (Thread 0x7f5e18cbb700 (LWP 1657)):
#0  0x7f5e395c835f in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#1  0x7f5e395cac7a in g_main_context_check () from 
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7f5e395cb2c0 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7f5e395cb42c in g_main_context_iteration () from 
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#4  0x7f5e3d168a9b in QEventDispatcherGlib::processEvents 
(this=0x7f5e0c0008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:420
#5  0x7f5e3d10fdea in QEventLoop::exec (this=this@entry=0x7f5e18cbace0, 
flags=..., flags@entry=...) at kernel/qeventloop.cpp:204
#6  0x7f5e3cf2c8a4 in QThread::exec (this=) at 
thread/qthread.cpp:503
#7  0x7f5e3f7d43c5 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5
#8  0x7f5e3cf3184e in QThreadPrivate::start (arg=0x1da14d0) at 
thread/qthread_unix.cpp:331
#9  0x7f5e3c0196fa in start_thread (arg=0x7f5e18cbb700) at 
pthread_create.c:333
#10 0x7f5e3c842b5d in clone () at 
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 3 (Thread 0x7f5e131d0700 (LWP 1658)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at 
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7f5e41b79bd4 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Script.so.5
#2  0x7f5e41b79c19 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Script.so.5
#3  0x7f5e3c0196fa in start_thread (arg=0x7f5e131d0700) at 
pthread_create.c:333
#4  0x7f5e3c842b5d in clone () at 
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 2 (Thread 0x7f5d89e10700 (LWP 1660)):
#0  

Re: Ubuntu Notepad

[Oliver Grawert]

hi,
Am Donnerstag, den 05.05.2016, 16:32 -0500 schrieb Dale Amon:
> On Wed, May 04, 2016 at 04:35:11PM +0100, Robie Basak wrote:
> > On Wed, May 04, 2016 at 10:30:52AM -0500, Dale Amon wrote:
> > > And just a question... you are saying phone. This is the new
> > > Ubuntu Notepad, not a phone.
> > 
> > Sorry, I didn't notice that. I believe it should work the same as the
> > phone, but I'm not sure.
> > 
> > There's also a mailing list on https://launchpad.net/~ubuntu-phone that
> > may be relevant to you, even if the name isn't accurate any more. I'm
> > not aware of a more specific list for your needs.
> > 
> > HTH,
> > 
> > Robie
> 
> I've succeeded, although one of the items I did was not in the
> docs I ran across. Once I got the terminal installed and got a
> sudo bash shell, I found that I had to:
> 
>   mount -o remount,rw /


note that this will likely break as soon as you do the next OTA update
and long term you will run out of space on the readonly system
partition ... 

generally it is a very bad idea to make the system writable, either use
a libertine container in the writable space [1] or if you dont want to
use any graphical apps, follow [2] 

and as robie said, the ubuntu-phone list [3] is far more appropriate for
the phone and tablet installs where you also will find other users that
have experience with these things.

ciao
oli

[1]
https://docs.google.com/document/d/1yJepibh68YaQijWO3Z3dWTtTTmzXnMmEE8eswhUXzw4/edit
[2]
http://askubuntu.com/questions/620740/recommended-way-to-install-regularcli-deb-packages-on-ubuntu-phone/623311#623311
[3] https://launchpad.net/~ubuntu-phone


signature.asc
Description: This is a digitally signed message part
-- 
Ubuntu-devel-discuss mailing list
Ubuntu-devel-discuss@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss