Manjaro-Deepin ISO 18.0.4-rc2 (testing branch) - the next try ;)

community-edition
deepin
#1

DLOSDN
direct | sig | sha1 | sha256 | torrent

Linuxdeepin is still proving to be a rather bumpy road for rolling release distributions but we are giving it another try... :sunglasses:
We have kept annoying Deepin devs with our bug-reports and suggestions and they have been really cooperative and trying hard to keep the Deepin experience going also on Arch-based systems.
So here comes another test-build, attempting to finally become our Manjaro-Deepin 18.0.4 edition :wink:
Adaptations since 18.0.2:

  • replaced gedit with deepin-editor
  • added deepin-voice-recorder, deepin-screensaver, deepin-turbo :sunglasses: and
  • added timeshift (full edition only)

I am providing a minimal build here. Will follow up with a full package profile probably tonight or after some initial feedback.
still to-do: I am aware that packaging of Deepin-wallpapers needs some re-organization... I will come up with a plan these days and then push some package updates...

Thank you for your input and feedback as always.

20 Likes
Manjaro-Deepin 18.0.4-rc (testing branch)
Linux Desktop Environment Survey
#2

there doesnt seem to a way to avoid mutter and only use kwin.
deepin-mutter is dependancie of many deepin packages

#3

Will test it soon, thx for new build! :slightly_smiling_face:

@Librewish
Like i've said in another thread - it will have to wait for now, this is WIP and have too many bugs to be publicly released yet.

So we'll have to stick with deepin-mutter for now, otherwise it will be very unstable and :poop:-storm of bug reports will come to Manjaro support...Not really what we'd want :laughing:

For now best option to avoid mutter bugs (for those of us who have it), is compiz, have few visual quirks, but prove to be pretty stable.

1 Like
#4

My understanding is that deepin-kwin development is still not final. However in general Linuxdeepin is kind of notoriously famous for cooking a mixture of all sorts of different ingredients ... :stuck_out_tongue_winking_eye:
It still needs to be seen where exactly all of this is going...

2 Likes
#5

@oberon

Here's my first look in VirtualBox VM:

  1. Very serious issue is dock and control-center constant crashes:

    1. On boot, for example reported here
    2. On changing settings, reported here
    3. Just navigating through settings here

    This is sure as hell known by far (and most likely caused by gradually moving toward deepin-kwin codebase), started ~6 days ago from now on Arch Deepin (hope it'll help to figure out where to roll-back for now), i could take a guess it's again work of our mutual friend electricface :crazy_face:

    Today i've catched it with this .iso multiple time on reboot (dock just crash -> reopen again in sequence constantly) and also while changing locale in settings both control-center and dock crashed and relaunched, here's coredump:

apr 16 14:11:26 x133-pc systemd-coredump[1355]: Process 644 (dde-dock) of user 1000 dumped core.

Stack trace of thread 644:
#0  0x00007efe8fa39bd0 _ZN19IndicatorTrayWidget7setTextERK7QString (libtray.so)
#1  0x00007efe8fa328c2 n/a (libtray.so)
#2  0x00007efe8fa32b67 _ZN13IndicatorTray19textPropertyChangedERK12QDBusMessage (libtray.so)
#3  0x00007efe8fa17e93 _ZN13IndicatorTray11qt_metacallEN11QMetaObject4CallEiPPv (libtray.so)
#4  0x00007efeb8f179ef n/a (libQt5DBus.so.5)
#5  0x00007efeb86a4102 _ZN7QObject5eventEP6QEvent (libQt5Core.so.5)
#6  0x00007efeb90e9e24 _ZN19QApplicationPrivate13notify_helperEP7QObjectP6QEvent (libQt5Widgets.so.5)
#7  0x00007efeb90f15f1 _ZN12QApplication6notifyEP7QObjectP6QEvent (libQt5Widgets.so.5)
#8  0x00007efeb97e8219 _ZN3Dtk6Widget12DApplication6notifyEP7QObjectP6QEvent (libdtkwidget.so.2)
#9  0x00007efeb8678df9 _ZN16QCoreApplication15notifyInternal2EP7QObjectP6QEvent (libQt5Core.so.5)
#10 0x00007efeb867bee8 _ZN23QCoreApplicationPrivate16sendPostedEventsEP7QObjectiP11QThreadData (libQt5Core.so.5)
#11 0x00007efeb86cf6c4 n/a (libQt5Core.so.5)
#12 0x00007efeb7a247bf g_main_context_dispatch (libglib-2.0.so.0)
#13 0x00007efeb7a26739 n/a (libglib-2.0.so.0)
#14 0x00007efeb7a2677e g_main_context_iteration (libglib-2.0.so.0)
#15 0x00007efeb86cec99 _ZN20QEventDispatcherGlib13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE (libQt5Core.so.5)
#16 0x00007efeb8677a8c _ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE (libQt5Core.so.5)
#17 0x00007efeb867fde6 _ZN16QCoreApplication4execEv (libQt5Core.so.5)
#18 0x0000561db96299d1 main (dde-dock)
#19 0x00007efeb80b3223 __libc_start_main (libc.so.6)
#20 0x0000561db9629dbe n/a (dde-dock)

Stack trace of thread 654:
#0  0x00007efeb817fc21 __poll (libc.so.6)
#1  0x00007efeb8071630 n/a (libxcb.so.1)
#2  0x00007efeb80732db xcb_wait_for_event (libxcb.so.1)
#3  0x00007efeb281d989 n/a (libQt5XcbQpa.so.5)
#4  0x00007efeb84bc96c n/a (libQt5Core.so.5)
#5  0x00007efeb71a8a9d start_thread (libpthread.so.0)
#6  0x00007efeb818ab23 __clone (libc.so.6)

Stack trace of thread 655:
#0  0x00007efeb817fc21 __poll (libc.so.6)
#1  0x00007efeb7a26690 n/a (libglib-2.0.so.0)
#2  0x00007efeb7a2677e g_main_context_iteration (libglib-2.0.so.0)
#3  0x00007efeb7a267d2 n/a (libglib-2.0.so.0)
#4  0x00007efeb7a01c21 n/a (libglib-2.0.so.0)
#5  0x00007efeb71a8a9d start_thread (libpthread.so.0)
#6  0x00007efeb818ab23 __clone (libc.so.6)

Stack trace of thread 657:
#0  0x00007efeb817fc21 __poll (libc.so.6)
#1  0x00007efeb7a26690 n/a (libglib-2.0.so.0)
#2  0x00007efeb7a2677e g_main_context_iteration (libglib-2.0.so.0)
#3  0x00007efeb9effbde n/a (libdconfsettings.so)
#4  0x00007efeb7a01c21 n/a (libglib-2.0.so.0)
#5  0x00007efeb71a8a9d start_thread (libpthread.so.0)
#6  0x00007efeb818ab23 __clone (libc.so.6)

Stack trace of thread 656:
#0  0x00007efeb817fc21 __poll (libc.so.6)
#1  0x00007efeb7a26690 n/a (libglib-2.0.so.0)
#2  0x00007efeb7a276d2 g_main_loop_run (libglib-2.0.so.0)
#3  0x00007efeb6feb568 n/a (libgio-2.0.so.0)
#4  0x00007efeb7a01c21 n/a (libglib-2.0.so.0)
#5  0x00007efeb71a8a9d start_thread (libpthread.so.0)
#6  0x00007efeb818ab23 __clone (libc.so.6)

Stack trace of thread 787:
#0  0x00007efeb817fc21 __poll (libc.so.6)
#1  0x00007efeb7a26690 n/a (libglib-2.0.so.0)
#2  0x00007efeb7a2677e g_main_context_iteration (libglib-2.0.so.0)
#3  0x00007efeb86cec99 _ZN20QEventDispatcherGlib13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE (libQt5Core.so.5)
#4  0x00007efeb8677a8c _ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE (libQt5Core.so.5)
#5  0x00007efeb84bb569 _ZN7QThread4execEv (libQt5Core.so.5)
#6  0x00007efeb84bc96c n/a (libQt5Core.so.5)
#7  0x00007efeb71a8a9d start_thread (libpthread.so.0)
#8  0x00007efeb818ab23 __clone (libc.so.6)

Stack trace of thread 785:
#0  0x00007efeb817fc21 __poll (libc.so.6)
#1  0x00007efeb7a26690 n/a (libglib-2.0.so.0)
#2  0x00007efeb7a2677e g_main_context_iteration (libglib-2.0.so.0)
#3  0x00007efeb86cec99 _ZN20QEventDispatcherGlib13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE (libQt5Core.so.5)
#4  0x00007efeb8677a8c _ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE (libQt5Core.so.5)
#5  0x00007efeb84bb569 _ZN7QThread4execEv (libQt5Core.so.5)
#6  0x00007efeb84bc96c n/a (libQt5Core.so.5)
#7  0x00007efeb71a8a9d start_thread (libpthread.so.0)
#8  0x00007efeb818ab23 __clone (libc.so.6)

Stack trace of thread 658:
#0  0x00007efeb817fc21 __poll (libc.so.6)
#1  0x00007efeb7a26690 n/a (libglib-2.0.so.0)
#2  0x00007efeb7a2677e g_main_context_iteration (libglib-2.0.so.0)
#3  0x00007efeb86cec99 _ZN20QEventDispatcherGlib13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE (libQt5Core.so.5)
#4  0x00007efeb8677a8c _ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE (libQt5Core.so.5)
#5  0x00007efeb84bb569 _ZN7QThread4execEv (libQt5Core.so.5)
#6  0x00007efeb8f0bba6 n/a (libQt5DBus.so.5)
#7  0x00007efeb84bc96c n/a (libQt5Core.so.5)
#8  0x00007efeb71a8a9d start_thread (libpthread.so.0)
#9  0x00007efeb818ab23 __clone (libc.so.6)


apr 16 14:12:40 x133-pc systemd-coredump[1395]: Process 790 (dde-control-cen) of user 1000 dumped core.

Stack trace of thread 790:
#0  0x00007f2375774d7f raise (libc.so.6)
#1  0x00007f237575f672 abort (libc.so.6)
#2  0x00007f23779de3db n/a (libdtkcore.so.2)
#3  0x00007f23779fcf14 _ZN3Dtk4Core6Logger5writeERK9QDateTimeNS1_8LogLevelEPKciS7_S7_RK7QString (libdtkcore.so.2)
#4  0x00007f23779fcf8b _ZN3Dtk4Core6Logger5writeENS1_8LogLevelEPKciS4_S4_RK7QString (libdtkcore.so.2)
#5  0x00007f23779fd094 n/a (libdtkcore.so.2)
#6  0x00007f2375ce6446 n/a (libQt5Core.so.5)
#7  0x00007f2375ce6809 n/a (libQt5Core.so.5)
#8  0x00007f2375cb57e2 _ZNK14QMessageLogger5fatalEPKcz (libQt5Core.so.5)
#9  0x00007f2375cb6055 n/a (libQt5Core.so.5)
#10 0x00007f2375ced6fa _ZN7QThreadD0Ev (libQt5Core.so.5)
#11 0x00007f2375ed475b _ZN14QObjectPrivate14deleteChildrenEv (libQt5Core.so.5)
#12 0x00007f2375edd7d5 _ZN7QObjectD2Ev (libQt5Core.so.5)
#13 0x00007f2377153f8a _ZN3dde7network12NetworkModelD0Ev (libdde-network-utils.so.1)
#14 0x00007f2375ed7121 _ZN7QObject5eventEP6QEvent (libQt5Core.so.5)
#15 0x00007f23774ade24 _ZN19QApplicationPrivate13notify_helperEP7QObjectP6QEvent (libQt5Widgets.so.5)
#16 0x00007f23774b55f1 _ZN12QApplication6notifyEP7QObjectP6QEvent (libQt5Widgets.so.5)
#17 0x00007f2377bac219 _ZN3Dtk6Widget12DApplication6notifyEP7QObjectP6QEvent (libdtkwidget.so.2)
#18 0x00007f2375eabdf9 _ZN16QCoreApplication15notifyInternal2EP7QObjectP6QEvent (libQt5Core.so.5)
#19 0x00007f2375eaeee8 _ZN23QCoreApplicationPrivate16sendPostedEventsEP7QObjectiP11QThreadData (libQt5Core.so.5)
#20 0x00007f2375f026c4 n/a (libQt5Core.so.5)
#21 0x00007f2376c2b7bf g_main_context_dispatch (libglib-2.0.so.0)
#22 0x00007f2376c2d739 n/a (libglib-2.0.so.0)
#23 0x00007f2376c2d77e g_main_context_iteration (libglib-2.0.so.0)
#24 0x00007f2375f01c99 _ZN20QEventDispatcherGlib13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE (libQt5Core.so.5)
#25 0x00007f2375eaaa8c _ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE (libQt5Core.so.5)
#26 0x00007f2375eb2de6 _ZN16QCoreApplication4execEv (libQt5Core.so.5)
#27 0x0000555f93d89e3c main (dde-control-center)
#28 0x00007f2375761223 __libc_start_main (libc.so.6)
#29 0x0000555f93d2f33e n/a (dde-control-center)

Stack trace of thread 797:
#0  0x00007f237582dc21 __poll (libc.so.6)
#1  0x00007f2376c2d690 n/a (libglib-2.0.so.0)
#2  0x00007f2376c2d77e g_main_context_iteration (libglib-2.0.so.0)
#3  0x00007f2375f01c99 _ZN20QEventDispatcherGlib13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE (libQt5Core.so.5)
#4  0x00007f2375eaaa8c _ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE (libQt5Core.so.5)
#5  0x00007f2375cee569 _ZN7QThread4execEv (libQt5Core.so.5)
#6  0x00007f23772c8ba6 n/a (libQt5DBus.so.5)
#7  0x00007f2375cef96c n/a (libQt5Core.so.5)
#8  0x00007f2374e61a9d start_thread (libpthread.so.0)
#9  0x00007f2375838b23 __clone (libc.so.6)

Stack trace of thread 815:
#0  0x00007f237582dc21 __poll (libc.so.6)
#1  0x00007f2376c2d690 n/a (libglib-2.0.so.0)
#2  0x00007f2376c2d77e g_main_context_iteration (libglib-2.0.so.0)
#3  0x00007f2375f01c99 _ZN20QEventDispatcherGlib13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE (libQt5Core.so.5)
#4  0x00007f2375eaaa8c _ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE (libQt5Core.so.5)
#5  0x00007f2375cee569 _ZN7QThread4execEv (libQt5Core.so.5)
#6  0x00007f2375cef96c n/a (libQt5Core.so.5)
#7  0x00007f2374e61a9d start_thread (libpthread.so.0)
#8  0x00007f2375838b23 __clone (libc.so.6)

Stack trace of thread 816:
#0  0x00007f237582dc21 __poll (libc.so.6)
#1  0x00007f2376c2d690 n/a (libglib-2.0.so.0)
#2  0x00007f2376c2d77e g_main_context_iteration (libglib-2.0.so.0)
#3  0x00007f2375f01c99 _ZN20QEventDispatcherGlib13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE (libQt5Core.so.5)
#4  0x00007f2375eaaa8c _ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE (libQt5Core.so.5)
#5  0x00007f2375cee569 _ZN7QThread4execEv (libQt5Core.so.5)
#6  0x00007f2375cef96c n/a (libQt5Core.so.5)
#7  0x00007f2374e61a9d start_thread (libpthread.so.0)
#8  0x00007f2375838b23 __clone (libc.so.6)

Stack trace of thread 794:
#0  0x00007f237582dc21 __poll (libc.so.6)
#1  0x00007f2376c2d690 n/a (libglib-2.0.so.0)
#2  0x00007f2376c2d77e g_main_context_iteration (libglib-2.0.so.0)
#3  0x00007f2376c2d7d2 n/a (libglib-2.0.so.0)
#4  0x00007f2376c08c21 n/a (libglib-2.0.so.0)
#5  0x00007f2374e61a9d start_thread (libpthread.so.0)
#6  0x00007f2375838b23 __clone (libc.so.6)

Stack trace of thread 793:
#0  0x00007f237582dc21 __poll (libc.so.6)
#1  0x00007f23780cd630 n/a (libxcb.so.1)
#2  0x00007f23780cf2db xcb_wait_for_event (libxcb.so.1)
#3  0x00007f237049b989 n/a (libQt5XcbQpa.so.5)
#4  0x00007f2375cef96c n/a (libQt5Core.so.5)
#5  0x00007f2374e61a9d start_thread (libpthread.so.0)
#6  0x00007f2375838b23 __clone (libc.so.6)

Stack trace of thread 795:
#0  0x00007f237582dc21 __poll (libc.so.6)
#1  0x00007f2376c2d690 n/a (libglib-2.0.so.0)
#2  0x00007f2376c2e6d2 g_main_loop_run (libglib-2.0.so.0)
#3  0x00007f2376da1568 n/a (libgio-2.0.so.0)
#4  0x00007f2376c08c21 n/a (libglib-2.0.so.0)
#5  0x00007f2374e61a9d start_thread (libpthread.so.0)
#6  0x00007f2375838b23 __clone (libc.so.6)

Stack trace of thread 796:
#0  0x00007f237582dc21 __poll (libc.so.6)
#1  0x00007f2376c2d690 n/a (libglib-2.0.so.0)
#2  0x00007f2376c2d77e g_main_context_iteration (libglib-2.0.so.0)
#3  0x00007f237833ebde n/a (libdconfsettings.so)
#4  0x00007f2376c08c21 n/a (libglib-2.0.so.0)
#5  0x00007f2374e61a9d start_thread (libpthread.so.0)
#6  0x00007f2375838b23 __clone (libc.so.6)

  1. Also you still can't use deepin-editor as root, so for now still having gedit is a good idea. As BLumia have stated he's really full on his schedule, so if someone could figure out difference between deepin-editor version before 13 February and figure out what caused it with update somewhere around 13 February - pull requests are very welcome!

  2. You need to roll-back deepin-wm a little again, since last update shows desktop itself as program entity (also caused by process of moving to kwin btw):

  3. Root programs have some monospace fonts and weird default settings (theme in root deepin-terminal is kinda off), not sure maybe it's caused by not having some packages as it is minimal .iso, but i'm sure that it doesn't happen on Arch, so please check it.

  4. Obviously still have this like you did, but that's not a big deal anyway.

#6

I've pretty much stopped reporting bugs at the deepin developer center, reporting any bugs at this point is futile, once kwin has been implemented I will continue bug reports.

I have also delayed my archdeepin.iso until kwin has been implemented, their are far to many bugs at the moment and a lot of bugs from way back have not even been fixed, a good indication that the bugs will not be fixed until kwin has been implemented.

I will work round them for now but unless something major happens, soon, I may have to switch to a different DE :wink:

1 Like
#7

At this point it no longer seams reasonable to constantly keep re-packaging older versions of Deepin packages while upstream apparently more or less blindly pushes updates. Either Linuxdeepin or Archlinux packager need to get their s**t together testing their packages. I can no longer take care of this downstream. It is simply too unreliable and consumes too much unnecessary energy on this level.
I will for now no longer release any new ISOs until the situation starts to look different...
Sorry guys!

7 Likes
#8

No worries, we all feel the same here, as @ant stated it's just waste of time until this deepin-kwin situation will change.

I'm constantly tracking Arch Deepin / upstream / internal discussion, so when situation will change i'll make sure to let you know :wink:

P.S. Actually there's another way, as they pretty much release their own Linux Deepin with only tagged milestones (like 15.9.3 / 15.10 etc), which seems to be relatively stable. On Arch they push just some untested stuff, which breaks a lot really.

1 Like
#9

@oberon @ant
I figured you guys should add your 5 cents here:

#10

I just arrived to Manjaro Deepin after 6 years of Ubuntu(Unity),Kubuntu,and Manjaro KDE use. I have a spare machine for testing. This may not be the appropriate place but is there a need/room for another Manjaro Deepin tester?

#11

Installed it as VM, looks great, works surprisingly nice considering previous opinions with only two major issues:

  1. the panel likes to crash from time to time
  2. I have no idea how the deepin DE works, but it is my fault mostly

maybe if I start using it on more daily basis it will have more issues, but for now it was quite nice (and aesthetically pleasing) experience
great work, cheers

1 Like
#12

@dbyentzen1
Sure, why not - we always value testers :slight_smile:

You can use either VM or real machine to test, in Manjaro just switch to unstable or testing branch, then:

  1. If you encounter some clearly Deepin related bug report it directly to upstream
  2. If you encounter Manjaro or other software bugs, report them accordingly either to Manjaro unstable / testing threads, and/or software devs directly

You can also do pretty much same on stable branch, but if you seriously aimed for testing it's better if you switch branch :slight_smile:

1 Like
#13

This is due dbus > 1.12.10-1

1 Like
#14

Thanks. I have a spare machine so I'll install the testing branch and start learning how to report bugs. I'm a non tech user so I think this is the best way for me to contribute back to the Manjaro community.

2 Likes
#15

We are also planning to make our project more developer-friendly with online documentation and dev supports, so maybe there can be more developer join the development to help the community build a better DDE.

(c) BLumia github

#16

Current process described:

#17

The problem is that if I decide that Kwin is stable enough for me, I can't uninstall Mutter, even though Mutter is not running on my system in any way, shape, or form.

So make it an optional dependency in pamac or something?

#18

(post withdrawn by author, will be automatically deleted in 24 hours unless flagged)

1 Like
#19

Thank you for the feedback! I will build a new image these days, then we can see better how the current state is :wink:

2 Likes
#20

(post withdrawn by author, will be automatically deleted in 24 hours unless flagged)