raring startup applications don't work after latest update

Bug #1084045 reported by jerrylamos
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
gnome-session (Ubuntu)
Invalid
Low
Unassigned

Bug Description

Before updates this week startup application commands were working now they are never issued. I do them manually after boot they work fine. Example:
 sudo iwconfig wlan0 essid LAUREL
xrandr --newmode "1366x768_60.00" 85.25 1366 1440 1576 1784 768 771 781 798 -hsync +vsync
which used to work.
One of them uses sudo the other doesn't. Last week they were working fine then apt-get update, apt-get dist-upgrade they are never issued by unity startup applications.

ProblemType: Bug
DistroRelease: Ubuntu 13.04
Package: unity 6.12.0-0ubuntu4
ProcVersionSignature: Ubuntu 3.7.0-3.9-generic 3.7.0-rc6
Uname: Linux 3.7.0-3-generic i686
.tmp.unity.support.test.0:

ApportVersion: 2.6.2-0ubuntu5
Architecture: i386
CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
Date: Wed Nov 28 07:00:00 2012
DistUpgraded: Fresh install
DistroCodename: raring
DistroVariant: ubuntu
GraphicsCard:
 Intel Corporation Atom Processor D4xx/D5xx/N4xx/N5xx Integrated Graphics Controller [8086:a011] (prog-if 00 [VGA controller])
   Subsystem: Acer Incorporated [ALI] Device [1025:0349]
   Subsystem: Acer Incorporated [ALI] Device [1025:0349]
InstallationDate: Installed on 2012-11-27 (1 days ago)
InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Alpha i386 (20121127)
MachineType: Acer AOD255E
MarkForUpload: True
ProcEnviron:
 TERM=xterm
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.7.0-3-generic root=UUID=ce422c9d-4d8e-4311-8b95-0b4733e8142f ro quiet splash vt.handoff=7
SourcePackage: unity
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 12/16/2010
dmi.bios.vendor: Acer
dmi.bios.version: V3.12(DDR3)
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: JE02_PT
dmi.board.vendor: Acer
dmi.board.version: V3.12(DDR3)
dmi.chassis.type: 10
dmi.chassis.vendor: Acer
dmi.chassis.version: V3.12(DDR3)
dmi.modalias: dmi:bvnAcer:bvrV3.12(DDR3):bd12/16/2010:svnAcer:pnAOD255E:pvrV3.12(DDR3):rvnAcer:rnJE02_PT:rvrV3.12(DDR3):cvnAcer:ct10:cvrV3.12(DDR3):
dmi.product.name: AOD255E
dmi.product.version: V3.12(DDR3)
dmi.sys.vendor: Acer
version.compiz: compiz 1:0.9.8.4+bzr3412-0ubuntu1
version.libdrm2: libdrm2 2.4.40-1
version.libgl1-mesa-dri: libgl1-mesa-dri 9.0.1-0ubuntu1
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 9.0.1-0ubuntu1
version.xserver-xorg-core: xserver-xorg-core 2:1.13.0-0ubuntu8
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu2
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.0.0-0ubuntu1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.20.13-0ubuntu1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.4-0ubuntu1
xserver.bootTime: Wed Nov 28 06:56:39 2012
xserver.configfile: default
xserver.errors:

xserver.logfile: /var/log/Xorg.0.log
xserver.version: 2:1.13.0-0ubuntu8
xserver.video_driver: intel

Revision history for this message
jerrylamos (jerrylamos) wrote :
affects: unity (Ubuntu) → gnome-session (Ubuntu)
Revision history for this message
Sebastien Bacher (seb128) wrote :

Thank you for your bug report, what did you upgrade? gnome-session didn't change recently...

Changed in gnome-session (Ubuntu):
importance: Undecided → Low
status: New → Incomplete
Revision history for this message
jerrylamos (jerrylamos) wrote :

Apt-get update, apt-get dist-upgrade is getting tons of stuff every day on Raring. Even the kernel. Any way to tell if startup applications is even getting activated?

Revision history for this message
Sebastien Bacher (seb128) wrote :

try looking in .xsession-errors for error, how did you add those commands?

Revision history for this message
jerrylamos (jerrylamos) wrote :

Thanks for looking at this bug. I did edit by copy and paste from an exec that works to add the commands for example
sudo iwconfig wlan0 essid LAUREL
which works fine from the xterminal and did work from startup applications. The reason for this command is the automatic connection on raring automatically disconnects hidden wireless WPA which is another bug #1017738. Hardware works fine on 12.04.1 both 12.10 and 13.04 have nm problem connecting to hidden wireless on boot.
Since it didn't work from startup I issue it from terminal and works fine.

Now that iwconfig works fine from terminal and did work from startup applications. I've verified the entry several times. Is there any way to verify that the startup applications are ever issued?

The other startup command entered by edit by copy and paste from an exec that works into startup commands:
xrandr --newmode "1366x768_60.00" 85.25 1366 1440 1576 1784 768 771 781 798 -hsync +vsync
the reason for this is the vga external monitor where there's no way for ubuntu to know what the resolution should be. Again this was working from startup on raring until the latest updates.
Since it didn't work from startup I issue it from terminal and works fine.

Attached is xsession-errors. Some usual unity complaints no failures.

Revision history for this message
Sebastien Bacher (seb128) wrote :

dunno, gnome-session didn't change so there is no reason those job should stop working... letting to somebody who wants to debug

Changed in gnome-session (Ubuntu):
status: Incomplete → New
Revision history for this message
Rob Harvey (jackcorbae-gmail) wrote :

I was using e17 with Ubuntu 12.10.

After upgrading to 13.04 last week I switched back to Unity.

Startup applications start randomly or not at all.

Nothing fancy, just trying to start xscreensaver, Chrome, Pidgin and VirtualBox ... sometime Pidgin will start. xscreensaver, Chrome and VirtualBox haven't started successfully since the upgrade.

I had problems getting xscreensaver to start with everything except e17.

Revision history for this message
Daniel van Vugt (vanvugt) wrote :

Thank you for reporting this bug to Ubuntu.
Ubuntu 13.04 (raring) reached end-of-life on January 27, 2014.

See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases

We appreciate that this bug may be old and you might not be interested in discussing it any more. But if you are then please upgrade to the latest Ubuntu version and re-test. If you then find the bug is still present in the newer Ubuntu version, please add a comment here telling us which new version it is in and change the bug status to Confirmed.

Changed in gnome-session (Ubuntu):
status: New → Won't Fix
status: Won't Fix → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.