[Bug 1096354] Re: hybrid-detect only checks for amd64, not i386 (unreachable code)
Hello Brian, I'm using 64bit Ubuntu so I can't easily test this, but I think the code should work now (assuming it already worked on amd64 before). I just saw the copy-paste-error while looking for information on what this program does. On a 32bit Ubuntu system (not mine, no hybrid graphics): $ dpkg --print-architecture i386 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1096354 Title: hybrid-detect only checks for amd64, not i386 (unreachable code) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-common/+bug/1096354/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1096363] [NEW] Add '--help' to hybrid-detect
Public bug reported:
When looking at /etc/init/hybrid-gfx.conf or hybrid-detect one could
maybe guess its use, but there is no description in the upstart job, no
manpage, no 'hybrid-detect --help' or similar.
I propose adding an '--help' option to hybrid-detect with an output like
this:
printf("Usage: %s\n", argv[0]);
printf("Detect if the available GPUs were changed (e.g. by BIOS settings) since
the last run using %s.\n", FILENAME);
printf("In this case detect which GPU in a hybrid graphics configuration should
be used.\n");
** Affects: ubuntu-drivers-common (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1096363
Title:
Add '--help' to hybrid-detect
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-common/+bug/1096363/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1096354] [NEW] hybrid-detect only checks for amd64, not i386 (unreachable code)
Public bug reported:
There seems to be a copy-paste-error in /share/hybrid/hybrid-detect.c, line 187
ff.:
> char *arch = NULL;
> arch = get_output("dpkg --print-architecture");
> if (strcmp(arch, "amd64") == 0) {
> arch_path = "x86_64-linux-gnu";
> }
> else if (strcmp(arch, "amd64") == 0) {
> arch_path = "i386-linux-gnu";
> }
> else {
Both "if"s check for "amd64", but the second one should probably check
for "i386". I didn't test it, but at the moment "arch_path = "i386
-linux-gnu";" is unreachable.
Same in quantal-updates and raring-proposed branch of ubuntu-drivers-
common.
** Affects: ubuntu-drivers-common (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1096354
Title:
hybrid-detect only checks for amd64, not i386 (unreachable code)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-common/+bug/1096354/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 984785] Re: .goutputstream files polluting $HOME
pidybi: > I have the some and can't make > > rm .goutputstream-* -v > > every day :( Just put this command into autorun (in system menu top left on screen): sh -c "rm ~/.goutputstream-*" -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/984785 Title: .goutputstream files polluting $HOME To manage notifications about this bug go to: https://bugs.launchpad.net/glib/+bug/984785/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 811166] Re: update manager no longer asking for password in 11.10
*** This bug is a duplicate of bug 814331 *** https://bugs.launchpad.net/bugs/814331 This is expected behavior for admin users. See comment 9 in duplicate bug #814331 ** Changed in: update-manager (Ubuntu) Status: Confirmed => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/811166 Title: update manager no longer asking for password in 11.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/811166/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1021474] Re: update-apt-xapian-index crashes with Unpickling Error in init() invalid load key
Happy to hear it works again. > sudo update-apt-xapian-index --verbose --force --batch-mode &> uaxi.output > > leaves a blank console... The command directs all output to the file "uaxi.output". So you can find the output in that file. (Slightly different from usual output because of "--batch-mode") In bash "&> file" equals "> file 2>&1". More information in the uu.de wiki (German): http://wiki.ubuntuusers.de/Shell/Umleitungen I'm not sure about what the status of this bug should be now. It's not really "Fix Commited / Released". I'll leave it as "Confirmed", as deleting the corrupt file is only a workaround, not a fix. cheers Dennis -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1021474 Title: update-apt-xapian-index crashes with Unpickling Error in init() invalid load key To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt-xapian-index/+bug/1021474/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1021474] Re: update-apt-xapian-index crashes with Unpickling Error in init() invalid load key
OK, the only error is this one (printed three times): opera.desktop: parsing X-AppInstall-Popcon: invalid literal for int() with base 10: '' But I think that's unrelated to your issue. Seems like it worked. Just run the command again to see if it crashes again because of the new /var/lib/apt-xapian-index/cataloged_times.p: $ sudo update-apt-xapian-index --force If it does not crash: I don't know, what originally produced the error, but it seems to be gone. If it does crash: Run this command and attach uaxi.outupt: $ sudo update-apt-xapian-index --verbose --force --batch-mode &> uaxi.output (If you want to, you can also leave out the command I mentioned first and only use the second. Then you have to inspect the file to see if there was an error.) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1021474 Title: update-apt-xapian-index crashes with Unpickling Error in init() invalid load key To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt-xapian-index/+bug/1021474/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1021474] Re: update-apt-xapian-index crashes with Unpickling Error in init() invalid load key
The file contains non-printable / corrupted characters in the entry for 'libcommons-javaflow-java-doc': $ grep -vEC 1 '^[[:print:]]*$' SickofSociety_cataloged_times.p p20573 �1336418�58.2340701 sS'l�bcommon�-javafl�w-java-doc' p20574 $ grep -C 1 'common.*-java.*java-doc' /var/lib/apt-xapian-index/cataloged_times.p# example for valid entry F1336421894.408062 sS'libcommons-javaflow-java-doc' p20179 Try deleting the file and then running update-apt-xapian-index again: $ sudo rm /var/lib/apt-xapian-index/cataloged_times.p $ sudo update-apt-xapian-index --verbose --force Note: Because of '--verbose' there will be more messages than usual. Please show us the commands' output. ** Changed in: apt-xapian-index (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1021474 Title: update-apt-xapian-index crashes with Unpickling Error in init() invalid load key To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt-xapian-index/+bug/1021474/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 989978] Re: Firefox spell check does not work
Problem solved, but not actually a bug. ** Changed in: firefox (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/989978 Title: Firefox spell check does not work To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/989978/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 989978] Re: Firefox spell check does not work
I'm not sure, if you understood me / I understood you. I meant this: Right click in a text input box -> "Languages" -> make sure an entry is chosen (should have a dot in front of it). You can choose a language by simply clicking on it in this submenu. "Extras -> Add-ons -> Languages" was only for checking, if a desired language pack is installed and _activated_ or not. See also https://support.mozilla.org/en-US/kb/how-do-i-use-firefox- spell-checker -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/989978 Title: Firefox spell check does not work To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/989978/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 989978] Re: Firefox spell check does not work
Did you also choose a language (below "Check Spelling")? Afaik this setting is not remembered with some modified privacy settings. Also check "Extras -> Add-ons -> Languages". -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/989978 Title: Firefox spell check does not work To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/989978/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 878872] Re: powertop doesn't display frequency statistics
Confirmed for 12.04. Also note, that not all frequencies are displayed. For me, "turbo mode" and "2.21 GHz" to "1300 MHz" are displayed, but the cpu is running at 800 MHz, which is the lowest one available. Thus, the percentages which _are_ displayed are probably correct. See also #911387 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/878872 Title: powertop doesn't display frequency statistics To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/powertop/+bug/878872/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 974141] Re: [apparmor profile] allow /proc/$$/net/wireless
I got the firefox update (version 12 -> 13) today. It _allows_ reading
the files @{PROC}/[0-9]*/net/dev and wireless, but the changelog says:
> adjust apparmor profile to deny reads to @{PROC}/[0-9]*/net/dev.
(same for wireless)
This is just a kind of typo in the changelog, isn't it?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/974141
Title:
[apparmor profile] allow /proc/$$/net/wireless
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/974141/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 984785] Re: .goutputstream files polluting $HOME
> what is your lightdm version? mine 1.2.1
Mine too, but that's no surprise. All users of (X|K|L)Ubuntu 12.04 should have
LightDM 1.2.1 (unless manually changed). See
http://packages.ubuntu.com/search?keywords=lightdm
> ps -ef | grep lightdm
Mine is similar:
root 980 1 0 13:33 ?00:00:00 lightdm
root 1018 980 1 13:33 tty7 00:01:23 /usr/bin/X :0 -auth
/var/run/lightdm/root/:0 -nolisten tcp vt7 -novtswitch -background none
root 1345 980 0 13:33 ?00:00:00 lightdm --session-child 12 19
root 9934 9743 0 14:46 pts/200:00:00 grep --color=auto lightdm
> lightdm --session-child INPUTFD OUTPUTFD
> ... "from_deamon_output" "to_deamon_output"
> ... "Failed to get D-Bus connection"
When using a tty there is usually no connection to D-Bus in the environment.
There is an session bus set up at login for interprocess communication of
desktop applications as well as an systemwide bus started by init / Upstart.
(https://en.wikipedia.org/wiki/D-Bus, `man dbus-daemon`)
These INPUTFD and OUTPUTFD (fd = file descriptor) arguments could be the
fds to use for communication with D-Bus.
> ps -ejH
See attachment. (Launchpad seems to merge all spaces and tabs into one space in
comments.)
- LightDM starts Xorg
- LightDM starts another lightdm child (the `--session-child` one)
- this child starts the desktop session; here: invokes gnome-session
- all processes (more or less) necessary for the desktop session are started,
including (see manpages for more information):
- shells (/bin/sh -> /bin/dash, /bin/bash), used to start further processes
and in terminal windows (like gnome-terminal)
- ssh-agent for ssh-key management
- screensaver process
- many more
> parent pgid
You mean "parent pid" = "parent process id"? Wrong interpretation. See `man
ps`: "PGID" = "process group ID"
> kill -9
9 SIGKILL terminates the process immediately (poor process: no chance for
cleanup or other actions).
The process doesn't really receive this signal to react, but instead the
kernel just kills / deletes / terminates the process.
15 SIGTERM tells the process to terminate. ("Hey you: Stop yourself or I will
stop you (using SIGKILL)!" ;) ) -> chance for cleanup
SIGKILL is usually only used if SIGTERM doesn't work.
> killing lightdm doesn't do anything besides hanging the pc
When you kill lightdm (using SIGKILL), it has no chance for any reaction
(including creating a .goutputstream-* file).
> killing Xorg creates the file!
Probably this happens:
Xorg gone without cleanup -> LightDM wants to quit -> LightDM creates
.goutputstream-* file.
I tried sending SIGTERMs (all commands entered in a tty; before each 'kill'
logged in into the session on tty7 using LightDM):
sudo kill # login screen shown
sudo kill
# no login screen or other GUI on tty7
restarting by pressing Ctrl+Alt+Del
sudo kill # login screen shown
I repeated this procedure a second time. None of them created a
.goutputstream-* file.
Also note: Sometimes there was no .goutputstream-* file created when I
shutdown / restarted from a running session. I saw this while trying to
find out which process is creating these files.
I think, it's a bug in LightDM, not Xorg. See the lsof (= list open files)
output in / attached to my last post (#45).
> lightdm 1348 a 9w REG 8,6 46 304928 /home/a/.goutputstream-YJRHEW
** Attachment added: "ps-ejH.part"
https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/984785/+attachment/3161042/+files/ps-ejH.part
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/984785
Title:
.goutputstream files polluting $HOME
To manage notifications about this bug go to:
https://bugs.launchpad.net/lightdm/+bug/984785/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 984785] Re: .goutputstream files polluting $HOME
> oh yes! checked the code and then again lost my memory :). No problem. Happens :) In short: I'm pretty sure now, that lightdm is creating these files. In long: I modified my ps-log.sh a bit, ran it several times and saw, that lightdm sometimes appeared in the log right before the file was created and sometimes right after it. This implies, that lightdm creates the file very fast after starting. Also tried starting lightdm. Didn't work (maybe would have, if I had tried with --test-mode from a tty): $ lightdm Only root can run Light Display Manager. To run as a regular user for testing run with the --test-mode flag. $ lightdm --test-mode Running inside an X server requires Xephyr to be installed but it cannot be found. Please install it or update your PATH environment variable. Logged whole command line of lightdm as started on shutdown: lightdm --session-child 12 19 --session-child is not documented in the man page. Tried this command in a running session, but no .goutputstream-* file was created (neither in current working directory, nor in ~): $ lightdm --session-child 12 19 Error reading from daemon: Bad file descriptor Error reading from daemon: Bad file descriptor Error reading from daemon: Bad file descriptor Error reading from daemon: Bad file descriptor Error reading from daemon: Bad file descriptor Error reading from daemon: Bad file descriptor Error reading from daemon: Bad file descriptor Error reading from daemon: Bad file descriptor Error reading from daemon: Bad file descriptor Error reading from daemon: Bad file descriptor Failed to start PAM: System error Then I tried logging with inotifywait and lsof (again, but modified script). This is a part of the log file: lightdm 1348a9w REG8,6 46 304928 /home/a/.goutputstream-YJRHEW -> It's really lightdm. 2 scripts + logfiles attached. ** Attachment added: "lightdm-logging.tar.gz" https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/984785/+attachment/3159336/+files/lightdm-logging.tar.gz -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/984785 Title: .goutputstream files polluting $HOME To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/984785/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 781931] Re: New windows are moved to front but don't take focus
Doug McMahon (mc3man): > I'll say that andyrock's fix works just fine here on 12.04 to fix the issue Sorry, I overlooked that branch. Thank you, andyrock! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/781931 Title: New windows are moved to front but don't take focus To manage notifications about this bug go to: https://bugs.launchpad.net/compiz/+bug/781931/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 984785] Re: .goutputstream files polluting $HOME
> Notice, how lightdm was not present on Dennis machine when file created, then > it comes up and dissapears. Maybe lightdm was actually running. This would be possible: - ps logs running processes (started by my script) - lightdm starts and creates .goutputstream* - next run of ps But it could also be possible, that lightdm was started later. I will repeat this test and comment later again. > How do you know it runs with userid 1000? How to check it on my computer? In my script: > ps -o comm -U 1000 -u 1000 >> ps-log.out man ps > -U userlist Select by real user ID (RUID) or name. > -u userlist Select by effective user ID (EUID) or name. So this command only logs processes running with real or effective UID 1000. That is the UID of the user created at installation. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/984785 Title: .goutputstream files polluting $HOME To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/984785/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 781931] Re: New windows are moved to front but don't take focus
This bug affects (and annoys) me too. Also if I open Nautilus and then try to focus it with Alt+Tab, its at the end of the list, so I have to press Tab about 3 times. When I read https://bugs.launchpad.net/unity/+bug/864233/comments/4 I tried changing that property: CompizConfig Settings Manager -> General Options -> Focus & Raise Behavior -> Focus Prevention Level -> "Off" to "Very High" (default: "Low") - "Off": Nautilus gets focus - "Low" to "Very High": Nautilus doesn't get focus Sometimes also with "Low" Nautilus gets focus, when I click the title bar of another window right before. I assume using "Off" wouldn't be very good, too. It would fix the problem with Nautilus (and maybe other applications), but if for example the update-manager pops up it would probably steal focus from the application I'm working with. Maybe the code behind this (especially for the "Low" preference) should be corrected. If somebody already looked at this: Thank you and never mind. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/781931 Title: New windows are moved to front but don't take focus To manage notifications about this bug go to: https://bugs.launchpad.net/compiz/+bug/781931/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 945812] Re: nautilus windows often open without focus if a terminal window is open, focus remains on terminal
*** This bug is a duplicate of bug 781931 *** https://bugs.launchpad.net/bugs/781931 ** This bug has been marked a duplicate of bug 781931 New windows are moved to front but don't take focus -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/945812 Title: nautilus windows often open without focus if a terminal window is open, focus remains on terminal To manage notifications about this bug go to: https://bugs.launchpad.net/unity-2d/+bug/945812/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 970829] Re: Nautilus isnt active when pops up- only shows taskbar its active
*** This bug is a duplicate of bug 781931 *** https://bugs.launchpad.net/bugs/781931 ** This bug is no longer a duplicate of bug 945812 nautilus windows often open without focus if a terminal window is open, focus remains on terminal ** This bug has been marked a duplicate of bug 781931 New windows are moved to front but don't take focus -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/970829 Title: Nautilus isnt active when pops up- only shows taskbar its active To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/970829/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 984785] Re: .goutputstream files polluting $HOME
Thank you Karolis! I downloaded your file and merged the duplicate blocks (search + replace). It's 330 lines now, instead of 3900. Here are the diffs: $ diff PART1 PART2 2c2 < sh --- > lightdm # LightDM start $ diff PART2 PART3 # "FILE CREATED!!!" is between these two (empty diff) $ diff PART3 PART4 2d1 < lightdm # LightDM end $ diff PART4 PART5 5d4 < xfconfd 11d9 < xfsettingsd 14d11 < gvfsd $ diff PART5 PART6 7d6 < xfwm4 # ... and so on (only processes quitting or becoming "" and then quitting) When I ran my script lightdm appeared right after "FILE CREATED!!!", but it probably spawned a bit earlier, i.e. right before .goutputstream-* is created. It was also the first process to quit after the creation of .goutputstream-*. Now, in a Xfce session, we have lightdm spawning right before .goutputstream-* is created and quitting afterwards again. It's not a proof, but an indication. And I have no clue why it is started (by user 1000!) at all ... Anybody else? ** Attachment added: "Shortened version of Karolis's log" https://bugs.launchpad.net/lightdm/+bug/984785/+attachment/3156579/+files/ps-log.out.xfce.shortened -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/984785 Title: .goutputstream files polluting $HOME To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/984785/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 386953] Re: Focus is moved from desktop to window
> This issue seems to be gone in Karmic. Can anyone confirm? I found this bug while searching for another one. It's not a problem for me, but in Ubuntu 12.04 (Unity) I experience almost the same behaviour as specified in the description. The only difference is, that a file / folder is focused in Nautilus only when I manually focused one before (between steps 2 and 3). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/386953 Title: Focus is moved from desktop to window To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/386953/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 984785] Re: .goutputstream files polluting $HOME
> is that specific to one of the lightdm greeters? I don't know if it's specific to unity-greeter. Maybe an Xfce / LXDE user can try the script I attached. There are also some Xubuntu users which commented on this bug. For those who want to try my script: You should start it only just before requesting shutdown or restart. It produces a lot of output into the logfile (more time -> more output). > do you mean that it happens at logout? It happened on shutdown. It seems that makes a difference here (between logout and shutdown I mean; see comment #29). I did this: - rm ~/.goutputstream-* - start ps-log.sh: sudo -b nice -n -19 sh ./ps-log.sh - start gnome-session-quit --power-off and click on "Shutdown" (This should be the same as top-right button in Unity -> Shutdown -> Shutdown.) After restarting my computer I looked into ps-log.out: ... COMMAND gnome-session ... FILE CREATED!!! <-- This is the point where my script first sees an ~/.goutputstream-* file. COMMAND lightdm ... -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/984785 Title: .goutputstream files polluting $HOME To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/984785/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 984785] Re: .goutputstream files polluting $HOME
** Attachment added: "ps-log.out.shortened" https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/984785/+attachment/3155848/+files/ps-log.out.shortened ** Also affects: lightdm Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/984785 Title: .goutputstream files polluting $HOME To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/984785/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 984785] Re: .goutputstream files polluting $HOME
Summary of previous comments: - blank files (#25, #31) or partial copies of .Xauthority (#11, #15, #26 / #28, mine too) - in Ubuntu and Xubuntu (files shown by Nautilus, Thunar and ls; no file manager problem) - created on direct shutdown (but not logout -> shutdown) Workaround: put 'sh -c "rm ~/.goutputstream-*"' (without the single quotes) into autorun My Software: - Ubuntu 12.04 amd64 (up-to-date) - file-roller installed but usually not running (also not running on shutdown: see below) - No gtk-recordmydesktop, Dropbox or UbuntuOne. I tried to find out which software is creating these files. I used (e.g.) inotifywait (package inotify-tools) and lsof, but it didn't work out. Probably the .goutputstream-* files are open only very short (too short for my script to catch it although run with niceness -19). Then I simply logged all processes running with my UID (1000) in an endless loop (i.e. until the script was terminated because of shutdown). I'll attach the script and its shortened output (removed duplicate blocks with no changes in process list and many blocks at the beginning). The output also contains a line stating "FILE CREATED!!!" when the ~/.goutputstream-* file is created. Just before / after this gnome- session quits and lightdm is started by UID 1000 (not root as usual). I don't know, why it is started, but it is also the next process which quits. lightdm also uses the ~/.Xauthority file. See strings `which lightdm` | grep -iE 'output|xauth' and the source code of lightdm: grep -ri xauthority /path/to/source/of/lightdm-1.2.1/src/ lightdm is used by Ubuntu and Xubuntu, but not Kubuntu. This fits to the previous comments. Maybe also related: GIO (part of glib) http://developer.gnome.org/gio/2.30/GOutputStream.html Get own processes using this: ps -o comm= -U 1000 -u 1000 | while read cmd; do file=$(which "$cmd") || file=$(locate -b "$cmd*"); strings -af $file | grep -E ': g.*output.*stream'; done > search.out I assume it's a problem with lightdm, but I can't fix it. I hope my information helps. ** Attachment added: "ps-log.sh" https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/984785/+attachment/3155847/+files/ps-log.sh -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/984785 Title: .goutputstream files polluting $HOME To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/984785/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
