You are not logged in.

#1526 2013-01-17 18:32:45

kladd
Member
Registered: 2012-09-18
Posts: 7

Re: Progress on Unity under Arch Linux!

I'm having trouble getting the screen to lock both with the shortcut and through the menu. Is this a known issue I missed?

Offline

#1527 2013-01-17 18:55:53

chenxiaolong
Member
From: /home/chenxiaolong
Registered: 2010-11-03
Posts: 784

Re: Progress on Unity under Arch Linux!

kladd wrote:

I'm having trouble getting the screen to lock both with the shortcut and through the menu. Is this a known issue I missed?

Could you see if gnome-screensaver is running?

ps aux | grep gnome-screensaver

Offline

#1528 2013-01-17 19:31:54

kladd
Member
Registered: 2012-09-18
Posts: 7

Re: Progress on Unity under Arch Linux!

chenxiaolong wrote:
kladd wrote:

I'm having trouble getting the screen to lock both with the shortcut and through the menu. Is this a known issue I missed?

Could you see if gnome-screensaver is running?

ps aux | grep gnome-screensaver

It is running, yes.

Offline

#1529 2013-01-17 19:42:43

divansantana
Member
Registered: 2011-01-21
Posts: 117

Re: Progress on Unity under Arch Linux!

@oi_wtf:

* The Files&Folders lens seems not to be working. Doesn't find anything. Does this work for you guys? What am I missing?
- maybe zeitgeist, afaik packages are named zeitgeist and zeitgeist-datahub, they should be in [community] if I remember correctly
So far have this installed and not working(yet):
libqzeitgeist 0.8.0-2
libzeitgeist 0.3.18-3
zeitgeist 0.9.5-1
zeitgeist-datahub 0.9.5-2

Following processes are running but not using any IO
zeitgeist-datahub
/usr/bin/zeitgeist-daemon
/usr/lib/zeitgeist/zeitgeist-fts

* indicator-multiload package is not available in Repo's/aur etc. Not a big deal can be packaged
- multiload indicator is broken, no more support for unity since... er... a long time...
Ok nice to know won't bother then.

* diodon (best clipboard for unity) is in AUR but outdated and doesn't have the great unity integration. Minor can be updated.
- I don't know anything about that one.

Real nice clipboard app you should try it. I'll try get it updated.

Otherwise the other things I've noticed:
* Most applications aren't patched for unity, so missing HUD integration, unity scrollbars, don't hide menubar etc incl KDE etc. Gentoo+Unity would possibly solve this nicely because you could build all your application with this patched/supported(?). Perhaps this can be worked around by rebuilding these applications via ABS, anyone tried this? I'll try give this a go.
* One can't click/right click on background. So can't add folders there etc. Minor.

Seems to be coming along really nicely! Very impressed.

Offline

#1530 2013-01-17 20:03:22

chenxiaolong
Member
From: /home/chenxiaolong
Registered: 2010-11-03
Posts: 784

Re: Progress on Unity under Arch Linux!

kladd wrote:
chenxiaolong wrote:
kladd wrote:

I'm having trouble getting the screen to lock both with the shortcut and through the menu. Is this a known issue I missed?

Could you see if gnome-screensaver is running?

ps aux | grep gnome-screensaver

It is running, yes.

In that case, are you able to lock from the command line?

gnome-screensaver-command -l

Offline

#1531 2013-01-17 20:04:31

chenxiaolong
Member
From: /home/chenxiaolong
Registered: 2010-11-03
Posts: 784

Re: Progress on Unity under Arch Linux!

divansantana wrote:

* One can't click/right click on background. So can't add folders there etc. Minor.

Seems to be coming along really nicely! Very impressed.

For this, you'll need to enable the nautilus desktop in gnome tweak-tool.

Offline

#1532 2013-01-17 22:37:54

kladd
Member
Registered: 2012-09-18
Posts: 7

Re: Progress on Unity under Arch Linux!

chenxiaolong wrote:
kladd wrote:
chenxiaolong wrote:

Could you see if gnome-screensaver is running?

ps aux | grep gnome-screensaver

It is running, yes.

In that case, are you able to lock from the command line?

gnome-screensaver-command -l

Not locking from the cli either. Are there any logs that might have error messages for this?

Offline

#1533 2013-01-18 00:42:28

oi_wtf
Member
From: /home/wtf
Registered: 2012-03-11
Posts: 191

Re: Progress on Unity under Arch Linux!

divansantana wrote:

Otherwise the other things I've noticed:
* Most applications aren't patched for unity, so missing HUD integration, unity scrollbars, don't hide menubar etc

- this sounds as if appmenu and scrollbar related packages aren't installed... did you install the 'overlay-scrollbar'-packages? ...the appmenu-gtk{2,3}, libappindicator, gtk{2,3}-ubuntu, indicator-appmenu, etc...  packages?

Last edited by oi_wtf (2013-01-18 00:43:06)


Laptop:   Arch Linux (x86_64) and Win10 (x86_64);  Intel Core i7-3630QM @ 2.40GHz, 8 GiB RAM, NViDiA GeForce GT 650M w/ 2 GiB
Desktop: Arch Linux (x86_64) and Win10 (x86_64);  Intel Core i7-4771  @ 3.50GHz, 32 GiB RAM, AMD Radeon RX 480 w/ 8 GiB

Offline

#1534 2013-01-18 01:24:29

chenxiaolong
Member
From: /home/chenxiaolong
Registered: 2010-11-03
Posts: 784

Re: Progress on Unity under Arch Linux!

kladd wrote:
chenxiaolong wrote:
kladd wrote:

It is running, yes.

In that case, are you able to lock from the command line?

ps aux | grep gnome-screensaver

Not locking from the cli either. Are there any logs that might have error messages for this?

That is so strange. You have 'gnome-screensaver' installed and not 'gnome-screensaver-ubuntu' right?

Try doing this to get a log:

# Kill the gnome-screensaver process
killall gnome-screensaver
# Run gnome-screensaver in debug mode and send the output to a file
gnome-screensaver --debug --no-daemon &>not_locking.log

Now try to lock the screen and then please upload the log somewhere, so I can take a look smile

Last edited by chenxiaolong (2013-01-18 01:25:03)

Offline

#1535 2013-01-18 07:00:47

shiznix
Member
Registered: 2012-10-04
Posts: 24

Re: Progress on Unity under Arch Linux!

I'm guessing you guys are running vanilla gnome-screensaver.

Unity expects to communicate with the gnome-screensaver daemon via dbus (not the old 'gnome-screensaver-command' way).
This is a special patch implemented by Ubuntu (05_dbus_service.patch)

You'll need to apply that patch to your own packaged version of gnome-screensaver to get screen locking working.
Specifically it provides /usr/share/dbus-1/services/org.gnome.ScreenSaver.service

Hope that helps wink

Offline

#1536 2013-01-18 09:06:33

qiuwei
Member
Registered: 2009-12-18
Posts: 245

Re: Progress on Unity under Arch Linux!

divansantana wrote:

@oi_wtf:

* The Files&Folders lens seems not to be working. Doesn't find anything. Does this work for you guys? What am I missing?
- maybe zeitgeist, afaik packages are named zeitgeist and zeitgeist-datahub, they should be in [community] if I remember correctly
So far have this installed and not working(yet):
libqzeitgeist 0.8.0-2
libzeitgeist 0.3.18-3
zeitgeist 0.9.5-1
zeitgeist-datahub 0.9.5-2

Following processes are running but not using any IO
zeitgeist-datahub
/usr/bin/zeitgeist-daemon
/usr/lib/zeitgeist/zeitgeist-fts

* indicator-multiload package is not available in Repo's/aur etc. Not a big deal can be packaged
- multiload indicator is broken, no more support for unity since... er... a long time...
Ok nice to know won't bother then.

* diodon (best clipboard for unity) is in AUR but outdated and doesn't have the great unity integration. Minor can be updated.
- I don't know anything about that one.

Real nice clipboard app you should try it. I'll try get it updated.

Otherwise the other things I've noticed:
* Most applications aren't patched for unity, so missing HUD integration, unity scrollbars, don't hide menubar etc incl KDE etc. Gentoo+Unity would possibly solve this nicely because you could build all your application with this patched/supported(?). Perhaps this can be worked around by rebuilding these applications via ABS, anyone tried this? I'll try give this a go.
* One can't click/right click on background. So can't add folders there etc. Minor.

Seems to be coming along really nicely! Very impressed.

Did you strictly follow the install guidelines on unity.xe-xe.org?
You need to install all packages from unity repo not only unity itself.

Last edited by qiuwei (2013-01-18 09:06:43)

Offline

#1537 2013-01-18 16:14:48

divansantana
Member
Registered: 2011-01-21
Posts: 117

Re: Progress on Unity under Arch Linux!

qiuwei wrote:

Did you strictly follow the install guidelines on unity.xe-xe.org?
You need to install all packages from unity repo not only unity itself.

Absolutely it's very basic instructions.
Except that I installed from http://unity.humbug.in/

Same instrcutions different repository though.

Can you confirm that the files lens is working for you??

Offline

#1538 2013-01-18 16:28:14

chenxiaolong
Member
From: /home/chenxiaolong
Registered: 2010-11-03
Posts: 784

Re: Progress on Unity under Arch Linux!

shiznix wrote:

I'm guessing you guys are running vanilla gnome-screensaver.

Unity expects to communicate with the gnome-screensaver daemon via dbus (not the old 'gnome-screensaver-command' way).
This is a special patch implemented by Ubuntu (05_dbus_service.patch)

You'll need to apply that patch to your own packaged version of gnome-screensaver to get screen locking working.
Specifically it provides /usr/share/dbus-1/services/org.gnome.ScreenSaver.service

Hope that helps wink

Thanks! Looks like I'll need to add gnome-screensaver-ubuntu back.

EDIT: The dbus service:

[D-BUS Service]
Name=org.gnome.ScreenSaver
Exec=/usr/bin/gnome-screensaver --no-daemon

as far as I know, only starts the gnome-screensaver daemon. I don't see any patch that allows communication via org.gnome.ScreenSaver. I think the vanilla gnome-screensaver should work properly.

EDIT2: indicator-session does not call gnome-screensaver at all. It locks the screen through ConsoleKit:

    <method name="Lock">
      <annotation name="org.freedesktop.DBus.GLib.Async" value=""/>
      <doc:doc>
        <doc:description>
          <doc:para>This will cause a <doc:ref type="signal" to="Session::Lock">Lock</doc:ref>
          signal to be emitted for this session.
          </doc:para>
        </doc:description>
        <doc:permission>This method is restricted to privileged users by D-Bus policy.</doc:permission>
        <doc:seealso><doc:ref type="signal" to="Session::Lock">Lock signal</doc:ref></doc:seealso>
      </doc:doc>
    </method>

I may need to write a patch for systemd-logind.

EDIT: For those who have gnome-screensaver working, you are all using LightDM as the display manager, right?

Last edited by chenxiaolong (2013-01-18 16:48:12)

Offline

#1539 2013-01-18 17:06:51

kuglee
Member
Registered: 2011-09-02
Posts: 61

Re: Progress on Unity under Arch Linux!

It seems that the default autostart file that comes with gnome-screensaver doesn't start the screensaver. I've added it manually (command: gnome-screensaver). It's the vanilla gnome-screensaver. Now it's working properly.

Offline

#1540 2013-01-18 19:10:48

qiuwei
Member
Registered: 2009-12-18
Posts: 245

Re: Progress on Unity under Arch Linux!

EDIT: For those who have gnome-screensaver working, you are all using LightDM as the display manager, right?

Yes , I can confirm that it works for me and I'm using LightDM.

Offline

#1541 2013-01-18 19:15:42

qiuwei
Member
Registered: 2009-12-18
Posts: 245

Re: Progress on Unity under Arch Linux!

divansantana wrote:
qiuwei wrote:

Did you strictly follow the install guidelines on unity.xe-xe.org?
You need to install all packages from unity repo not only unity itself.

Absolutely it's very basic instructions.
Except that I installed from http://unity.humbug.in/

Same instrcutions different repository though.

Can you confirm that the files lens is working for you??

I can confirm that all qt-applications are well integrated, and also all gtk2 and gtk3 applications.
I'm not sure my file lenses are working properly or not, but it's showing some files but not all of the files on my disk. It doesn't bother me too much because I never use it:)

Offline

#1542 2013-01-18 19:27:59

oi_wtf
Member
From: /home/wtf
Registered: 2012-03-11
Posts: 191

Re: Progress on Unity under Arch Linux!

files lens uses zeitgeist, so only files tracked by it, will show... but I don't use it much, too...
I also can confirm all qt or gtk applications well integrated in both Hud and global menu...


Laptop:   Arch Linux (x86_64) and Win10 (x86_64);  Intel Core i7-3630QM @ 2.40GHz, 8 GiB RAM, NViDiA GeForce GT 650M w/ 2 GiB
Desktop: Arch Linux (x86_64) and Win10 (x86_64);  Intel Core i7-4771  @ 3.50GHz, 32 GiB RAM, AMD Radeon RX 480 w/ 8 GiB

Offline

#1543 2013-01-18 20:55:44

divansantana
Member
Registered: 2011-01-21
Posts: 117

Re: Progress on Unity under Arch Linux!

Thanks for the feedback guys. Maybe I will try rather install from http://unity.xe-xe.org/ or from source and re-do everything.
I also want to do it on bare metal annd be full time on arch and not just a VM can't wait smile Arch rocks.

Offline

#1544 2013-01-18 21:09:08

kuglee
Member
Registered: 2011-09-02
Posts: 61

Re: Progress on Unity under Arch Linux!

Zeitgeist settings can be edited with activity-log-manager.

Offline

#1545 2013-01-18 22:20:15

shiznix
Member
Registered: 2012-10-04
Posts: 24

Re: Progress on Unity under Arch Linux!

@chenxialong - Oops yes you're right, sorry for the noise neutral

Offline

#1546 2013-01-18 22:27:28

chenxiaolong
Member
From: /home/chenxiaolong
Registered: 2010-11-03
Posts: 784

Re: Progress on Unity under Arch Linux!

shiznix wrote:

@chenxialong - Oops yes you're right, sorry for the noise neutral

No need to apologize smile Your post brought up an important issue where screen locking probably won't work with gdm.

Offline

#1547 2013-01-19 12:23:27

illusionmist
Member
Registered: 2012-05-14
Posts: 32

Re: Progress on Unity under Arch Linux!

A minor annoyance: when I select "Change Desktop Background" from the desktop context menu, it opens System Settings, but not straight into the Appearance panel.
Does this happen to everyone?

Offline

#1548 2013-01-19 12:58:57

qiuwei
Member
Registered: 2009-12-18
Posts: 245

Re: Progress on Unity under Arch Linux!

illusionmist wrote:

A minor annoyance: when I select "Change Desktop Background" from the desktop context menu, it opens System Settings, but not straight into the Appearance panel.
Does this happen to everyone?

Yes, it's a new bug introduced in the latest update.
And also for the online accounts which is already there for quite long time.

Offline

#1549 2013-01-19 16:57:58

chenxiaolong
Member
From: /home/chenxiaolong
Registered: 2010-11-03
Posts: 784

Re: Progress on Unity under Arch Linux!

illusionmist wrote:

A minor annoyance: when I select "Change Desktop Background" from the desktop context menu, it opens System Settings, but not straight into the Appearance panel.
Does this happen to everyone?

qiuwei wrote:
illusionmist wrote:

A minor annoyance: when I select "Change Desktop Background" from the desktop context menu, it opens System Settings, but not straight into the Appearance panel.
Does this happen to everyone?

Yes, it's a new bug introduced in the latest update.
And also for the online accounts which is already there for quite long time.

Do both of you have gnome-control-center-unity installed? The online accounts should work with my version of credentials-preferences in the git repo.

Offline

#1550 2013-01-20 01:59:34

chenxiaolong
Member
From: /home/chenxiaolong
Registered: 2010-11-03
Posts: 784

Re: Progress on Unity under Arch Linux!

Some info about the disappearing launcher icon issue

A few days ago, most of my programs I use daily were updated, causing my launcher to end up blank sad I wrote this program to give me an idea of exactly what is happening behind the scenes when packages are upgraded on Arch compared to Ubuntu:

/* Written by: Xiao-Long Chen <chenxiaolong@cxl.epac.to> */

/* This program will monitory any directory for file for changes */

/* Compile with (gcc|clang) dirwatcher.c -o dirwatcher */

#include <limits.h>
#include <stdio.h>
#include <stdlib.h>
#include <string.h>
#include <sys/inotify.h>
#include <unistd.h>

/* Allow the buffer to hold 10 events */
#define BUF_LEN (10 * (sizeof(struct inotify_event) + NAME_MAX + 1))

static void print_event(struct inotify_event *event) {
  if (event->mask & IN_ACCESS)
    printf("%s: File was accessed\n",                           event->name);
  if (event->mask & IN_ATTRIB)
    printf("%s: Metadata was changed\n",                        event->name);
  if (event->mask & IN_CLOSE_WRITE)
    printf("%s: File opened for writing was closed\n",          event->name);
  if (event->mask & IN_CLOSE_NOWRITE)
    printf("%s: File not opened for writing was closed\n",      event->name);
  if (event->mask & IN_CREATE)
    printf("%s: File/directory was created\n",                  event->name);
  if (event->mask & IN_DELETE)
    printf("%s: File/directory was deleted\n",                  event->name);
  if (event->mask & IN_DELETE_SELF)
    printf("%s: Watched file/directory was deleted\n",          event->name);
  if (event->mask & IN_MODIFY)
    printf("%s: File was modified\n",                           event->name);
  if (event->mask & IN_MOVE_SELF)
    printf("%s: Watched file/directory was moved\n",            event->name);
  if (event->mask & IN_MOVED_FROM)
    printf("%s: File was moved out of the watched directory\n", event->name);
  if (event->mask & IN_MOVED_TO)
    printf("%s: File was moved into the watched directory\n",   event->name);
  if (event->mask & IN_OPEN)
    printf("%s: File was opened\n",                             event->name);
}

int main(int argc, char *argv[]) {
  char *path;

  if (argc < 2) {
    fprintf(stderr, "No arguments provided!\n");
    exit(1);
  }

  if (strcmp(argv[1], "-v") == 0) {
    if (argc < 3) {
      fprintf(stderr, "No path provided!\n");
      exit(1);
    }
    path = argv[2];
  }
  else {
    path = argv[1];
  }

  int fd = inotify_init();
  if (fd < 0) {
    fprintf(stderr, "inotify_init() failed!\n");
    exit(1);
  }

  int options = IN_ATTRIB |
                IN_CREATE |
                IN_DELETE |
                IN_MODIFY |
                IN_MOVED_TO |
                IN_MOVED_FROM;
  if (strcmp(argv[1], "-v") == 0) {
    options = options |
              IN_ACCESS |
              IN_CLOSE_WRITE |
              IN_CLOSE_NOWRITE |
              IN_DELETE_SELF |
              IN_MOVE_SELF |
              IN_OPEN;
  }

  int wd = inotify_add_watch(fd, path, options);

  if (wd < 0) {
    fprintf(stderr, "inotify_add_watch() failed!\n");
    exit(1);
  }

  char buf[BUF_LEN];

  while (1) {
    int length = read(fd, buf, BUF_LEN);
    if (length <= 0) {
      fprintf(stderr, "read() from inotify file descriptor returned %i!\n", length);
      exit(1);
    }

    int i = 0;
    while (i < length) {
      struct inotify_event *event = (struct inotify_event *)&buf[i];
      print_event(event);
      i += sizeof(struct inotify_event) + event->len;
    }
  }
}

On Ubuntu, this is what an upgrade looks like:

chenxiaolong@cxl-4270cto:~$ ./dirwatcher /usr/share/applications/
xdiagnose.desktop.dpkg-new: File/directory was created
xdiagnose.desktop.dpkg-new: File was modified
xdiagnose.desktop.dpkg-new: Metadata was changed
xdiagnose.desktop.dpkg-new: Metadata was changed
xdiagnose.desktop.dpkg-tmp: File/directory was created
xdiagnose.desktop.dpkg-new: File was moved out of the watched directory
xdiagnose.desktop: File was moved into the watched directory
xdiagnose.desktop.dpkg-tmp: File/directory was deleted
bamf.index: File/directory was deleted
bamf.index.new: File/directory was created
bamf.index.new: File was modified
bamf.index.new: File was moved out of the watched directory
bamf.index: File was moved into the watched directory
.mimeinfo.cache.DW78QW: File/directory was created
.mimeinfo.cache.DW78QW: Metadata was changed
.mimeinfo.cache.DW78QW: File was modified
.mimeinfo.cache.DW78QW: File was modified
.mimeinfo.cache.DW78QW: File was modified
.mimeinfo.cache.DW78QW: File was modified
.mimeinfo.cache.DW78QW: File was modified
.mimeinfo.cache.DW78QW: File was modified
.mimeinfo.cache.DW78QW: File was moved out of the watched directory
mimeinfo.cache: File was moved into the watched directory

On Arch, this is what an upgrade looks like:

chenxiaolong@cxl-4270cto:~$ ./dirwatcher /usr/share/applications/
nautilus.desktop: File/directory was deleted
nautilus-home.desktop: File/directory was deleted
nautilus-folder-handler.desktop: File/directory was deleted
nautilus-connect-server.desktop: File/directory was deleted
nautilus-autorun-software.desktop: File/directory was deleted
mount-archive.desktop: File/directory was deleted
nautilus-folder-handler.desktop: File/directory was created
nautilus-folder-handler.desktop: File was modified
nautilus-folder-handler.desktop: Metadata was changed
nautilus-folder-handler.desktop: Metadata was changed
nautilus-folder-handler.desktop: Metadata was changed
nautilus.desktop: File/directory was created
nautilus.desktop: File was modified
nautilus.desktop: Metadata was changed
nautilus.desktop: Metadata was changed
nautilus.desktop: Metadata was changed
nautilus-home.desktop: File/directory was created
nautilus-home.desktop: File was modified
nautilus-home.desktop: Metadata was changed
nautilus-home.desktop: Metadata was changed
mount-archive.desktop: File/directory was created
mount-archive.desktop: File was modified
mount-archive.desktop: Metadata was changed
mount-archive.desktop: Metadata was changed
mount-archive.desktop: Metadata was changed
nautilus-connect-server.desktop: File/directory was created
nautilus-connect-server.desktop: File was modified
nautilus-connect-server.desktop: Metadata was changed
nautilus-connect-server.desktop: Metadata was changed
nautilus-connect-server.desktop: Metadata was changed
nautilus-autorun-software.desktop: File/directory was created
nautilus-autorun-software.desktop: File was modified
nautilus-autorun-software.desktop: Metadata was changed
nautilus-autorun-software.desktop: Metadata was changed
.mimeinfo.cache.4ALTQW: File/directory was created
.mimeinfo.cache.4ALTQW: Metadata was changed
.mimeinfo.cache.4ALTQW: File was modified
.mimeinfo.cache.4ALTQW: File was modified
.mimeinfo.cache.4ALTQW: File was modified
.mimeinfo.cache.4ALTQW: File was modified
.mimeinfo.cache.4ALTQW: File was modified
.mimeinfo.cache.4ALTQW: File was moved out of the watched directory
mimeinfo.cache: File was moved into the watched directory

Notice how in Ubuntu, no files are ever deleted on upgrades. dpkg copies the new desktop file to program/.desktop.dpkg-new and then moves it onto the old program/.desktop

Now take a look at the output for Arch. Arch deletes all of the files belonging to the old version and then installs the new version. The behavior is similar to "pacman -Syu nautilus" is similar to "pacman -Rdd nautilus && pacman -Sy nautilus". It's no wonder that the icons disappear from the launcher.

At this point, I have no idea how to fix the issue. How can I tell Unity that a package is being upgraded if the upgrade process involves removing the old package and then installing the new one?

Last edited by chenxiaolong (2013-01-20 02:00:07)

Offline

Board footer

Powered by FluxBB