[Stable Update] 2019-01-23 - Kernels, Mesa, Browsers, Nvidia, Deepin, VirtualBox

Calm your horsey, No need to make new replies when you can edit your previous post.

1 Like

sorry. but after removing cups 0.2.6-2 , the update is working. i hope that would finish ok

Thanks to all who read my posts but also to the one who answered that helped me to be able to update the system. everything went well. Thank you

2 Likes

With last update i have error log with tracker-miner-fs in gnome :slight_smile:

Process 1221 (tracker-miner-fs) of user 1000 dumped core.

Stack trace of thread 1221:
#0  0x00007fb89ef81d7f raise (libc.so.6)
#1  0x00007fb89ef6c672 abort (libc.so.6)
#2  0x00007fb89ebc2042 n/a (libglib-2.0.so.0)
#3  0x00007fb89ebef5dc g_assertion_message_expr (libglib-2.0.so.0)
#4  0x00007fb89ef0e2a3 n/a (libtracker-miner-2.0.so.0)
#5  0x00007fb89ef0e982 n/a (libtracker-miner-2.0.so.0)
#6  0x00007fb89ef0aa7e n/a (libtracker-miner-2.0.so.0)
#7  0x00007fb89ef0cbca n/a (libtracker-miner-2.0.so.0)
#8  0x00007fb89eece765 n/a (libtracker-sparql-2.0.so.0)
#9  0x00007fb89eddd2f4 n/a (libgio-2.0.so.0)
#10 0x00007fb89eddfcd7 n/a (libgio-2.0.so.0)
#11 0x00007fb89eed03ef n/a (libtracker-sparql-2.0.so.0)
#12 0x00007fb89eddd2f4 n/a (libgio-2.0.so.0)
#13 0x00007fb89eddd329 n/a (libgio-2.0.so.0)
#14 0x00007fb89ec128d1 g_main_context_dispatch (libglib-2.0.so.0)
#15 0x00007fb89ec145e9 n/a (libglib-2.0.so.0)
#16 0x00007fb89ec155c2 g_main_loop_run (libglib-2.0.so.0)
#17 0x00005611d0acaff5 main (tracker-miner-fs)
#18 0x00007fb89ef6e223 __libc_start_main (libc.so.6)
#19 0x00005611d0acb3ae _start (tracker-miner-fs)


Stack trace of thread 1234:
#0  0x00007fb89f03ac21 __poll (libc.so.6)
#1  0x00007fb89ec14540 n/a (libglib-2.0.so.0)
#2  0x00007fb89ec1462e g_main_context_iteration (libglib-2.0.so.0)
#3  0x00007fb89ec14682 n/a (libglib-2.0.so.0)
#4  0x00007fb89ebef67b n/a (libglib-2.0.so.0)
#5  0x00007fb89f115a9d start_thread (libpthread.so.0)
#6  0x00007fb89f045b23 __clone (libc.so.6)


Stack trace of thread 1278:
#0  0x00007fb89f0404ed syscall (libc.so.6)
#1  0x00007fb89ebc3151 g_cond_wait_until (libglib-2.0.so.0)
#2  0x00007fb89ec412c3 n/a (libglib-2.0.so.0)
#3  0x00007fb89ebe65fb n/a (libglib-2.0.so.0)
#4  0x00007fb89ebef67b n/a (libglib-2.0.so.0)
#5  0x00007fb89f115a9d start_thread (libpthread.so.0)
#6  0x00007fb89f045b23 __clone (libc.so.6)

Stack trace of thread 1239:
#0  0x00007fb89f03ac21 __poll (libc.so.6)
#1  0x00007fb89ec14540 n/a (libglib-2.0.so.0)
#2  0x00007fb89ec1462e g_main_context_iteration (libglib-2.0.so.0)
#3  0x00007fb899106bde n/a (libdconfsettings.so)
#4  0x00007fb89ebef67b n/a (libglib-2.0.so.0)
#5  0x00007fb89f115a9d start_thread (libpthread.so.0)
#6  0x00007fb89f045b23 __clone (libc.so.6)

Stack trace of thread 1235:
#0  0x00007fb89f03ac21 __poll (libc.so.6)
#1  0x00007fb89ec14540 n/a (libglib-2.0.so.0)
#2  0x00007fb89ec155c2 g_main_loop_run (libglib-2.0.so.0)
#3  0x00007fb89ed7acb8 n/a (libgio-2.0.so.0)
#4  0x00007fb89ebef67b n/a (libglib-2.0.so.0)
#5  0x00007fb89f115a9d start_thread (libpthread.so.0)
#6  0x00007fb89f045b23 __clone (libc.so.6)

Stack trace of thread 1486:
#0  0x00007fb89f0404ed syscall (libc.so.6)
#1  0x00007fb89ebc3151 g_cond_wait_until (libglib-2.0.so.0)
#2  0x00007fb89ec412c3 n/a (libglib-2.0.so.0)
#3  0x00007fb89ebe65fb n/a (libglib-2.0.so.0)
#4  0x00007fb89ebef67b n/a (libglib-2.0.so.0)
#5  0x00007fb89f115a9d start_thread (libpthread.so.0)
#6  0x00007fb89f045b23 __clone (libc.so.6)

Stack trace of thread 1268:
#0  0x00007fb89f0404ed syscall (libc.so.6)
#1  0x00007fb89ebc2471 g_cond_wait (libglib-2.0.so.0)
#2  0x00007fb89ec412ec n/a (libglib-2.0.so.0)
#3  0x00007fb89ebe6479 n/a (libglib-2.0.so.0)
#4  0x00007fb89ebef67b n/a (libglib-2.0.so.0)
#5  0x00007fb89f115a9d start_thread (libpthread.so.0)
#6  0x00007fb89f045b23 __clone (libc.so.6)


Le processus 1221 (tracker-miner-fs) a généré un fichier « core »

And when i try to launch manually in terminal tracker-miner-fs (with cmd : /usr/lib/tracker-miner-fs
) i have this :

**
ERROR:../tracker/src/libtracker-miner/tracker-file-system.c:259:file_tree_lookup: assertion failed: (ptr[0] == '/')
Abandon (core dumped)

OK, we found now a proper way without using an epoch. We went for the Debian-way now. Therefore we added now a systemd package called 239.303+really+239.6-1. This will update all systems out there, even with the broken 239.303-1 package out there. We are sorry to not thinking of that simple fix before …

59 Likes

We all are only humans. Thanks for a good news :slight_smile:

1 Like

You’re welcome. :wink:

Also, I need to check my email more regularly. Or, just blame my work for being very busy at the moment.

We are all busy with all the hardware project we currently have. Will send you an email so you are also updated on those we have.

3 Likes

That made me laugh. :grin:

5 Likes

Debian (and Ubuntu) use this approach/hack regularly when there’s an issue with a package and it needs a quick revert without breaking everything else.

Simple but effective.

8 Likes

That’s great news. Planning to install Manjaro on many different machines soon. If it’s handled that way it will ensure I don’t have to fix these machines :wink:

1 Like

Reminds me about different stages of my picture or video project edits (really, final, master, pre, true etc…) lol

2 Likes

This is the funniest version number I’ve ever seen for a package.

Actually, on Arch distros, + is also used, albeit to tell that it has been patched with some commits and isn’t the original version as published by upstream. For example: accountsservice 0.6.54+2+g204a4ab-2

This is a weird solution, but at least it does the job to prevent forcing users to do manual intervention. It should be kept and remembered forever, in case it becomes useful again.

Guess I’m sorry for not suggesting to go outside Arch package versioning standard (epoch is meant for those kind of situation, never though “outside of the box”).

3 Likes

who has to thank me is because your effort we have a spectacular operating system.

Agree

XFCE, 4.19.16-1

Everything went well! At the end of upgrading everything through Pamac, it did warn me of a bunch of conflicting packages (e.g. ncurses, npm, etc), but everything still worked.

Thanks for all the hard work!

Um, I’m assuming systemd at “239.303+really+239.6-1” is really the current version now?

edit: nevermind just caught off gaurd by the version number lol.

AS per philm 's statement above. ^

2 Likes

This is the answer I was looking for, thank you.