Active Topics
-
The N900 is now 15 years old! (7)
to Nokia N900 by Danct12 - 2 days, 22 hrs ago -
Sailfish OS for the Motorola Moto G7 Power (XT1955-5) - (ocean) (4)
to SailfishOS by Maemish - 3 days, 17 hrs ago -
F(x)tec Pro1x (QWERTY) for sale (0)
to Buy & Sell by aln00000 - 6 days, 2 hrs ago - more...
|
2009-02-18
, 20:20
|
|
Posts: 1,950 |
Thanked: 1,174 times |
Joined on Jan 2008
@ Seattle, USA
|
#2
|
Which version of evince? 2.21.1 works for me
__________________
.
. .
Help Save This Forum for N8x0/Diablo Users! Register and Vote for Solution #1 on this Brainstorm. (The Solution will let you see New Posts with any threads you choose -- like the N900 and Maemo5/Fremantle threads -- filtered out.) (To understand the Solution better, see these posts #17, #18, and #19.)
.
. .
Help Save This Forum for N8x0/Diablo Users! Register and Vote for Solution #1 on this Brainstorm. (The Solution will let you see New Posts with any threads you choose -- like the N900 and Maemo5/Fremantle threads -- filtered out.) (To understand the Solution better, see these posts #17, #18, and #19.)
 |
|
2009-02-18
, 21:03
|
|
Posts: 3,220 |
Thanked: 326 times |
Joined on Oct 2005
@ "Almost there!" (Monte Christo, Count of)
|
#3
|
Originally Posted by GeraldKo
The Application mangler says the version is 2.21.1-1.maemo8.
Which version of evince? 2.21.1 works for me
If I run "evince" from a terminal, I get:
evince[3470]: GLIB WARNING ** default - Failed to create directory /home/user/.config/evince: Permission denied
If I run it from a root terminal, I get:
process 3473: D-Bus library appears to be incorrectly set up; failed to read machine uuid: Failed to open "/var/lib/dbus/machine-id": No such file or directory
See the manual page for dbus-uuidgen to correct this issue.
D-Bus not built with -rdynamic so unable to print a backtrace
Aborted
I have no idea what those things mean. I have done nothing with my tablet but install the latest Diablo on it; in fact, it's a brand-spanking new tablet, straight from Nokia's [whereever they keep talbets].
__________________
Watch out Nokia, Pandora's box has opened (sorta)...
I do love explaining cryptic sigs, but for the impatient: http://www.openpandora.org/
Watch out Nokia, Pandora's box has opened (sorta)...
I do love explaining cryptic sigs, but for the impatient: http://www.openpandora.org/
|
|
2009-02-18
, 21:24
|
|
Posts: 1,224 |
Thanked: 1,763 times |
Joined on Jul 2007
|
#4
|
Did you check: that /home/user/.config/ exists and is writeable by user? That /home/user/.config/evince is not an existing regular file or a directory not writeable by user?
 |
|
2009-02-18
, 21:29
|
|
Posts: 903 |
Thanked: 632 times |
Joined on Apr 2008
|
#5
|
Sometimes if you (usually accidentally) run a program as root, it will mangle your permissions:
chown -R user.users /home/user/.config/
(I *think* that's the right command, it may be a lowercase -r).
chown -R user.users /home/user/.config/
(I *think* that's the right command, it may be a lowercase -r).
| The Following User Says Thank You to BrentDC For This Useful Post: | ||
|
|
2009-02-18
, 21:36
|
|
Posts: 3,220 |
Thanked: 326 times |
Joined on Oct 2005
@ "Almost there!" (Monte Christo, Count of)
|
#6
|
Originally Posted by BrentDC
I only ran evince as root after I noticed problems. I didn't even start it from a terminal before I had noticed it wouldn't run at all.
Sometimes if you (usually accidentally) run a program as root, it will mangle your permissions:
chown -R user.users /home/user/.config/
(I *think* that's the right command, it may be a lowercase -r).
So what would have run as root on my tablet to mangle my permissions?
It's -R, but the syntax following, "user.users" is new to me.
__________________
Watch out Nokia, Pandora's box has opened (sorta)...
I do love explaining cryptic sigs, but for the impatient: http://www.openpandora.org/
Watch out Nokia, Pandora's box has opened (sorta)...
I do love explaining cryptic sigs, but for the impatient: http://www.openpandora.org/
|
|
2009-02-18
, 21:41
|
|
Posts: 3,220 |
Thanked: 326 times |
Joined on Oct 2005
@ "Almost there!" (Monte Christo, Count of)
|
#7
|
Originally Posted by Matan
Why should I have to check that? This program is in the repositories, one can reasonably expect it to know how to install itself?
Did you check: that /home/user/.config/ exists and is writeable by user? That /home/user/.config/evince is not an existing regular file or a directory not writeable by user?
In any case, /home/user/.config/ does exist. Whether user can write to it or not is beyond me. I do know that, from ls-ing it, Roxterm at least managed to write its configuration files to it. The "evince" directory however is nowhere to be seen there.
__________________
Watch out Nokia, Pandora's box has opened (sorta)...
I do love explaining cryptic sigs, but for the impatient: http://www.openpandora.org/
Watch out Nokia, Pandora's box has opened (sorta)...
I do love explaining cryptic sigs, but for the impatient: http://www.openpandora.org/
|
|
2009-02-18
, 22:41
|
|
Posts: 903 |
Thanked: 632 times |
Joined on Apr 2008
|
#8
|
Originally Posted by Karel Jansens
Anything that accesses ~/.config/
I only ran evince as root after I noticed problems. I didn't even start it from a terminal before I had noticed it wouldn't run at all.
So what would have run as root on my tablet to mangle my permissions?
It's -R, but the syntax following, "user.users" is new to me.
I would just try that command...
| The Following User Says Thank You to BrentDC For This Useful Post: | ||
|
|
2009-02-19
, 16:32
|
|
Posts: 3,220 |
Thanked: 326 times |
Joined on Oct 2005
@ "Almost there!" (Monte Christo, Count of)
|
#9
|
Originally Posted by BrentDC
Well, it worked, so thanks. I'm still baffled as to what program or process has done stuff with root privileges on my tablet because, "sleeprooting" notwithstanding, it sure wasn't me.
Anything that accesses ~/.config/
The syntax for chown is user[.:]group. Maybe you've seen user:users before?
I would just try that command...
So now I can read the Zombie Survival Guide again.
Because you never know when they'll attack...
__________________
Watch out Nokia, Pandora's box has opened (sorta)...
I do love explaining cryptic sigs, but for the impatient: http://www.openpandora.org/
Watch out Nokia, Pandora's box has opened (sorta)...
I do love explaining cryptic sigs, but for the impatient: http://www.openpandora.org/
|
|
2009-02-19
, 17:33
|
|
Posts: 1,208 |
Thanked: 1,028 times |
Joined on Oct 2007
|
#10
|
Roxterm seems to be at fault here. It has two bugs in it's installation scripts:
1. It writes directly to /home/user directory (it also assumes that user's username is user)
2. It creates /home/user/.config/roxterm.sourceforge.net directory, but it assumes that /home/user/.config directory exists because it only chown's /home/user/.config/roxterm.sourceforge.net directory to user. So if .config directory didn't exist it is owned by root after installing roxterm
1. It writes directly to /home/user directory (it also assumes that user's username is user)
2. It creates /home/user/.config/roxterm.sourceforge.net directory, but it assumes that /home/user/.config directory exists because it only chown's /home/user/.config/roxterm.sourceforge.net directory to user. So if .config directory didn't exist it is owned by root after installing roxterm
| The Following 3 Users Say Thank You to mikkov For This Useful Post: | ||
So what gives?
Watch out Nokia, Pandora's box has opened (sorta)...
I do love explaining cryptic sigs, but for the impatient: http://www.openpandora.org/