[Bug 678421] Re: Error in ~/.profile halts the X startup

2011-07-07 Thread Egon Elbre
For the sed/eval round we can always escape the special characters
beforehand, there should be some function for that.

But I agree with your conclusion. Warning or message is a good enough
solution, even though I would like to see some hand-holding. I agree it
just isn't worth the effort and the only nice way (I can think) of
doing this is to extend dash with such functionality.

** Summary changed:

- Error in ~/.profile halts the X startup
+ Error message for a faulty ~/.profile script

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/678421

Title:
  Error message for a faulty ~/.profile script

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdm/+bug/678421/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 678421] Re: Error in ~/.profile halts the X startup

2011-07-06 Thread Egon Elbre
The idea is simple:

###

VARS=$( # this allows to capture subshell stdout to a variable
 . $HOME/script.sh 1/dev/null   #  this prevents script printing something to 
stdout
set  # this prints all variables to stdout
alias | sed 's/.*/alias \0/' # this prints aliases to stdout and prefixes them 
with alias 
) || ERRCODE=$?

if [ $ERRCODE==0 ]
then
eval $VARS # if everything is ok, we reevaluate the variables and aliases 
in this shell
fi

###
Now the VARS=$(command) || ERRCODE=$?, || prevents the command from exiting 
the script if the next command exits with code 0. We could also use 
VARS=$(command) || true, but then $? would contain the result of command 
true, since ERRCODE=$? also exits with code 0 we can prevent the shell from 
exiting and remember the correct error code.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/678421

Title:
  Error in ~/.profile halts the X startup

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdm/+bug/678421/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 678421] Re: Error in ~/.profile halts the X startup

2011-07-03 Thread Egon Elbre
Right forgot about the variables.

After poking around in dash source I found that $HOME/.profile has
been hardcoded. So the change needs be made in the shell to make
.profile safe.

Also I found a way to keep the variables from subshell

### test.sh ###
ERRCODE=0
TEST=
VARS=$(set -e; . $HOME/script.sh 1/dev/null; set) || ERRCODE=$?
if [ $ERRCODE==0 ]
then
eval $VARS
fi
echo ERRCODE = $ERRCODE
echoTEST = $TEST
### script.sh ###
TEST=something
function AddPath { echo err }
##

This also has one nice thing that when the script fails the environment
stays unchanged. Also there may be some variables that shouldn't be
taken from the subshell, but I have no idea which.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/678421

Title:
  Error in ~/.profile halts the X startup

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdm/+bug/678421/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 678421] Re: Error in ~/.profile halts the X startup

2011-07-02 Thread Egon Elbre
Sorry, I forgot about this due to other duties (work and school).
This is not an active issue for me, but would be a nice touch to Ubuntu.

This still happens in Oneiric (tested in daily). There are some differences, 
it just drops you into the default login screen without any explanation.
Which is quite bad because then you will be puzzled what just happened/went 
wrong.

Also I did some research how to keep the main script running when
sub-script has some syntax errors:

#

set -e
ERRCODE=0
(. $HOME/.profile) || ERRCODE=$?
echo $ERRCODE

#

ERRCODE will be
0 if everything was ok
127 if there was a syntax error
0: there was some other problem with the script

That way we can get the correct error code without terminating the main script
and do graceful handling of the error.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/678421

Title:
  Error in ~/.profile halts the X startup

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdm/+bug/678421/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 678421] Re: Error in ~/.profile halts the X startup

2011-05-19 Thread Egon Elbre
Sure, silently just ignoring is just as bad. I just think that, it's a
mistake that shouldn't prevent you to login and start up everything.

The ~/.profile script can also easily be changed by non-experienced
users (ones who may not know terminal that well). If that user doesn't
get the session running then he'll be forced to use terminal.

The ideal case I think would be: everything starts up and an relevant
error message is displayed.

I'm ok with scripts in /etc/.. preventing xsession to start as that
requires sudo permissions (as sudo implies that caution must be taken).
Essentially my POV is that if modifying a script doesn't require sudo
permissions it should be relatively safe, meaning you should be still
able to fix it from GUI interface. Of course practically it's impossible
to do so, but it's a target to move towards.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/678421

Title:
  Error in ~/.profile halts the X startup

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 656045] Re: [r300] Minecraft crashes, fairly randomly [SIGSEGV (0xb)]

2011-02-28 Thread Egon Elbre
Had the same problem, installed gallium drivers as was suggested in this
discussion
http://getsatisfaction.com/mojang/topics/anything_but_tiny_draw_distance_crashes_minecraft_using_mesa_radeon_drivers_on_x11

How to install:
http://phoronix.com/forums/showthread.php?24195-Help-wanted-instaling-Gallium3D-Ubuntu-10.04-ATI-x1400

Not a fix but a workaround...

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/656045

Title:
  [r300] Minecraft crashes, fairly randomly [SIGSEGV (0xb)]

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 678421] [NEW] Error in ~/.profile halts the X startup

2010-11-22 Thread Egon Elbre
Public bug reported:

Binary package hint: gdm

After adding function AddPath { PATH=$1:$PATH } to $HOME/.profile
made the Xorg startup fail. (At that moment I had already forgotten the
changes made to the .profile). As I had autologin that meant it kept
trying to login and finally showed me the graphics reconfiguration
screen. That sent me to a huge hunt for xorg conf and setup problems.

Anyway finally tracked this down. I had used bash syntax in .profile
file whereas it was run with sh.

This is not a bug per se but I think a user mistake in .profile
shouldn't bring the whole xorg startup to a halt as it does with
autologin. I propose running user .profile and .xprofile scripts so
that Xsession script continues running even if they have errors. I'm not
sure whether this change would have some negative effects as well.

1) Ubuntu Lucid, Linux egon-laptop 2.6.32-25-generic #45-Ubuntu SMP Sat Oct 16 
19:48:22 UTC 2010 i686 GNU/Linux
2) gdm 2.30.2.is.2.30.0-0ubuntu4

** Affects: gdm (Ubuntu)
 Importance: Undecided
 Status: New

-- 
Error in ~/.profile halts the X startup
https://bugs.launchpad.net/bugs/678421
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 677968] Re: Error in $HOME/.profile halts the X startup

2010-11-21 Thread Egon Elbre
Any idea where would be a better place? Is it then just a general ubuntu
problem?

-- 
Error in $HOME/.profile halts the X startup
https://bugs.launchpad.net/bugs/677968
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 677968] [NEW] Error in $HOME/.profile halts the X startup

2010-11-20 Thread Egon Elbre
Public bug reported:

Binary package hint: xorg

After adding  function AddPath { PATH=$1:$PATH } to $HOME/.profile
made the Xorg startup fail. (At that moment I had already forgotten the
changes made to the .profile). As I had autologin that meant it kept
trying to login and finally gave up as it thought something was wrong
was with the graphics setup. That sent me to a huge hunt for xorg conf
or setup problems.

Anyway finally tracked this down. I had used bash syntax in .profile
file whereas it was run with sh.

This is not a bug per se but I think a user mistake in .profile
shouldn't bring the whole xorg startup to a halt as it does with
autologin. I propose running user .profile and .xprofile scripts so
that Xsession script continues running even if they have errors. At this
moment I'm probably biased due to the problem hunting so I'm not sure
whether this change would have some negative effects as well.

1) Ubuntu Lucid, Linux egon-laptop 2.6.32-25-generic #45-Ubuntu SMP Sat Oct 16 
19:48:22 UTC 2010 i686 GNU/Linux
2) xorg 1:7.5+5ubuntu1

** Affects: xorg (Ubuntu)
 Importance: Undecided
 Status: New

-- 
Error in $HOME/.profile halts the X startup
https://bugs.launchpad.net/bugs/677968
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 571846] [NEW] cache folder on ntfs

2010-04-29 Thread Egon Elbre
Public bug reported:

Binary package hint: testdrive

Due to the rsync parameters testdrive cache folder is not working on
ntfs drives.

Changing line 286 in testdrive from:
  run_or_die(rsync -azP %s %s % (ISO_URL, PATH_TO_ISO))
to:
  run_or_die(rsync -rlDzP %s %s % (ISO_URL, PATH_TO_ISO))
fixes the problem.

Whether the change should be done there or should there be special
handling for ntfs I have no idea.

** Affects: testdrive (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: cache ntfs

-- 
cache folder on ntfs
https://bugs.launchpad.net/bugs/571846
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 525302] Re: gwibber-accounts crashed on trying to open it ( crashed with BadArgumentsError in __init__() )

2010-04-29 Thread Egon Elbre
@Kasmus

Version 2.30.0.1 doesn't crash anymore.

-- 
gwibber-accounts crashed on trying to open it ( crashed with BadArgumentsError 
in __init__() )
https://bugs.launchpad.net/bugs/525302
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 525302] Re: gwibber-accounts crashed on trying to open it ( crashed with BadArgumentsError in __init__() )

2010-04-29 Thread Egon Elbre
@Paul, Could you try the gwibber --debug  gwibber-debug.txt . I'm not
able to reproduce the issue.

-- 
gwibber-accounts crashed on trying to open it ( crashed with BadArgumentsError 
in __init__() )
https://bugs.launchpad.net/bugs/525302
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 525302] Re: gwibber-accounts crashed on trying to open it

2010-02-21 Thread Egon Elbre

** Attachment added: Dependencies.txt
   http://launchpadlibrarian.net/39474773/Dependencies.txt

** Attachment added: ProcMaps.txt
   http://launchpadlibrarian.net/39474774/ProcMaps.txt

** Attachment added: ProcStatus.txt
   http://launchpadlibrarian.net/39474775/ProcStatus.txt

** Attachment added: Traceback.txt
   http://launchpadlibrarian.net/39474776/Traceback.txt

** Visibility changed to: Public

-- 
gwibber-accounts crashed on trying to open it
https://bugs.launchpad.net/bugs/525302
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 525321] [NEW] Firefox screen usage

2010-02-21 Thread Egon Elbre
Public bug reported:

Binary package hint: ubuntu-netbook-remix-default-settings

Firefox in default setup uses too much screen space. It uses up about
1/6 of total screen space.

I think the default install should also use minimalistic themes. Disable
bookmarks bar, auto hide status bar and similar (TinyMenu or similar).

A blog post how to make it better:
http://www.blork.org/blorkblog/2009/03/10/optimize-firefox-for-your-netbook/

** Affects: ubuntu-netbook-remix-default-settings (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: firefox netbook usability

-- 
Firefox screen usage
https://bugs.launchpad.net/bugs/525321
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 525321] Re: Firefox screen usage

2010-02-21 Thread Egon Elbre

** Attachment added: FFXScreenUsage.png
   http://launchpadlibrarian.net/39477793/FFXScreenUsage.png

-- 
Firefox screen usage
https://bugs.launchpad.net/bugs/525321
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs