[Bug 968383] Re: gnome-power-statistics shows info on first time launched from indicator-power, but not subsequent times
I noticed that when I close gnome-power-statistics pressing Esc on the keyboard, or just clicking the Close icon in the window decoration, window closes but the process remains running. On the other hand, when using the Close button at bottom-right in the window, gnome-power-statistics window closes and process finishes as well. So gnome-power-statistics is only happy when closing it through its very own Close button, sigh. Using ubuntu 12.04 beta 2 now, fully updated. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-power-manager in Ubuntu. https://bugs.launchpad.net/bugs/968383 Title: gnome-power-statistics shows info on first time launched from indicator-power, but not subsequent times To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-power-manager/+bug/968383/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 968383] Re: gnome-power-statistics shows info on first time launched from indicator-power, but not subsequent times
Thanks mfisch for the clarification. Didn't know it was gnome-power- statistics. About a crash, I don't see any crash file in /var/crash for gnome-power- statistics. Should I look in other places? -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-power-manager in Ubuntu. https://bugs.launchpad.net/bugs/968383 Title: gnome-power-statistics shows info on first time launched from indicator-power, but not subsequent times To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-power-manager/+bug/968383/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 968383] Re: gnome-power-statistics shows info on first time launched from indicator-power, but not subsequent times
Oh, I have run gnome-power-statistics from a terminal (window shows info normally), but when closing the power statistics window the terminal does not return to the prompt, as if gnome-power-statistics were still running. I opened System Monitor and the process is there indeed. Also, while the process is running, a second call to the program (through indicator-power, for example) shows the window with no content. After killing the process (e.g. with Ctrl+C in the terminal, or in System Monitor), calling again gnome-power-statistics shows its window with the usual content, not empty. So seems gnome-power-statistics does not finish normally after its window is closed, affecting all subsequent runs (not showing any info) until finished manually. (this is using gnome-power-manager 3.4.0-0ubuntu1; didn't find version of gnome-power-statistics) -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-power-manager in Ubuntu. https://bugs.launchpad.net/bugs/968383 Title: gnome-power-statistics shows info on first time launched from indicator-power, but not subsequent times To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-power-manager/+bug/968383/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 848340] Re: Brasero can't select DVD drive to burn image
It works for me. Now the combo box for selecting the destination disk is filled, not empty. Writing the alpha-2 image to a DVD-R works. Ok, after all is well and finished brasero process stays around, but this is another bug I suppose. Using ubuntu 11.10 Oneiric (i386) and brasero - 3.2.0-0ubuntu1.1 from oneiric-proposed. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to brasero in Ubuntu. https://bugs.launchpad.net/bugs/848340 Title: Brasero can't select DVD drive to burn image To manage notifications about this bug go to: https://bugs.launchpad.net/brasero/+bug/848340/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 463376] Re: can't catch $USER in /etc/gdm/PostLogin/Default
Hi, the fix for Lucid has been backported to Karmic thanks to Artur Rona. You can test the fix by following the instructions in comment #8 of bug #574262. It works for me (tested on two machines running Karmic, one upgraded from Jaunty, another with a fresh Karmic install). -- can't catch $USER in /etc/gdm/PostLogin/Default https://bugs.launchpad.net/bugs/463376 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug assignee. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 506972] Re: Environment passed to /etc/gdm/PostLogin/Default script does not contain useful information
Hi Manuel, the fix for Lucid has been nicely backported to Karmic by Artur Rona. If you want to test the fix in Karmic, please follow the instructions in comment #8 of bug #574262. The fix works for me on two different machines (one upgraded from Jaunty to Karmic, the other with a fresh Karmic install). -- Environment passed to /etc/gdm/PostLogin/Default script does not contain useful information https://bugs.launchpad.net/bugs/506972 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug assignee. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 574262] Re: [SRU] Please backport to Karmic GDM fix for bug #463376
Also tested the new gdm package in one of school's computers, and it works too. In an unrelated note, would it be ok if I add a comment in the other bugs (#463376, #506972) so that the other persons who reported the bug against Karmic know it's now fixed? I did add a comment there before opening this bug, but seems no mail was generated. What do you think? (Oh and did I say you definitly rock guys? :-)) -- [SRU] Please backport to Karmic GDM fix for bug #463376 https://bugs.launchpad.net/bugs/574262 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gdm in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 574262] Re: [SRU] Please backport to Karmic GDM fix for bug #463376
I've just tested the new gdm package in my home's computer (running Ubuntu 9.10 Karmic) and it works! (i.e. everything is ok plus now you get proper values from env. vars. $HOME, $USER, $USERNAME, $LOGNAME inside script /etc/gdm/PostLogin/Default) I'll test tomorrow morning at work (when classes end). Oh and many thanks Artur, Martin and everyone! You rock guys! -- [SRU] Please backport to Karmic GDM fix for bug #463376 https://bugs.launchpad.net/bugs/574262 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gdm in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 574262] Re: Please backport to Karmic GDM fix for bug #463376
Sure, I can test it at work (though in around 8 hours, after work hours) and at home. -- Please backport to Karmic GDM fix for bug #463376 https://bugs.launchpad.net/bugs/574262 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gdm in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 574262] [NEW] Please backport to Karmic GDM fix for bug #463376
Public bug reported: Binary package hint: gdm Hi, when time permits, could you please backport from Lucid to Karmic GDM's patch for bug #463376? The bug is about GDM's PostLogin/Default script. In Ubuntu 9.04 (Jaunty) when you log in as, say, somename, you get proper values inside /etc/PostLogin/Default for these vars.: $USERNAME -- somename $LOGNAME -- somename $HOME -- /home/somename But in Ubuntu 9.10 (Karmic) you get instead these values: $USERNAME -- gdm $LOGNAME -- gdm $HOME -- /var/lib/gdm It seems that this is fixed in Ubuntu 10.04 too, but I haven't tested it yet. Having these vars. and others set up correctly for using them in the script /etc/PostSession/Default is badly needed for admins that want to clear $HOME upon login, for example in a shool computer lab (as is our case here). Bug #463376 is where the patch for Lucid was posted; bug #506972 is where the request to backport to Karmic was originally done by Manuel Iglesias. ** Affects: gdm (Ubuntu) Importance: Undecided Status: New -- Please backport to Karmic GDM fix for bug #463376 https://bugs.launchpad.net/bugs/574262 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gdm in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 574262] Re: Please backport to Karmic GDM fix for bug #463376
Thanks for your promptly reply Sebastien. I see that now that Lucid fixes this bug, it makes sense a Karmic -- Lucid upgrade. I'll try tomorrow evening after work hours to update one of our lab's computers to Lucid and see if env vars work properly inside /etc/PostLogin/Default (not now because I'm outside work). I was trying to avoid the upgrade because we use several scripts in our computer's classroom that must be tested separately for each new Ubuntu version. Anyway, who said a part-time sysadmin's work would be easy :-) -- Please backport to Karmic GDM fix for bug #463376 https://bugs.launchpad.net/bugs/574262 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gdm in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 574262] Re: Please backport to Karmic GDM fix for bug #463376
(Erm, I meant a Jaunty -- Karmic upgrade, then a Karmic -- Lucid upgrade. Though it sems too many upgrades, maybe I'll try a fresh Lucid install too.) -- Please backport to Karmic GDM fix for bug #463376 https://bugs.launchpad.net/bugs/574262 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gdm in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 463376] Re: can't catch $USER in /etc/gdm/PostLogin/Default
Err, this bug still happens in Karmic, though it's been fixed for Lucid. It was a regression from Intrepid, where things worked fine. It would be awesome if you could backport the fix to Karmic (I know time is tight now with Lucid being near release time, maybe after release). (Don't know if it's appropiate to comment in a fix-commited bug though, sorry for any inconveniences.) -- can't catch $USER in /etc/gdm/PostLogin/Default https://bugs.launchpad.net/bugs/463376 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug assignee. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 506972] Re: Environment passed to /etc/gdm/PostLogin/Default script does not contain useful information
Hi, this bug affects me too in Karmic (and 18 PCs in our school's computer lab, which I upgraded from Ubuntu 9.04 to 9.10). Fix for Lucid is in bug #463376, but is not backported to Karmic. Oh, the bug is about GDM's /etc/gdm/PostLogin/Default script where you no longer get the user name that's login in through any of $USER, $USERNAME or $LOGNAME (they all now contain gdm). It worked before Karmic, but not with new GDM 2.28.x. Bug https://bugs.launchpad.net/gdm/+bug/463376 seems to have resolved the issue for Lucid, but the fix is still not in Karmic. Please could you backport the fix in bug 463376 from Lucid to Karmic? This way us poor school sysadmins could stop pulling out our hair because of this :-) Many people rely on these vars set properly to perform tasks like cleaning the student's home directory at login and setting predefined defaults for the desktop. -- Environment passed to /etc/gdm/PostLogin/Default script does not contain useful information https://bugs.launchpad.net/bugs/506972 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug assignee. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 332554] Re: gvfsd-trash crashed with SIGSEGV in g_type_check_instance_is_a()
Thank you for your promptly effort. If I can help in testing the fix or whatever, just say so. -- gvfsd-trash crashed with SIGSEGV in g_type_check_instance_is_a() https://bugs.launchpad.net/bugs/332554 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gvfs in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 145704] Re: Same tooltip on both workspaces when using Compiz
Hi, sorry for not responding in a few days, lots of work in day job now. Yes, problem still exists here with 9.04 alpha 4, in fresh install and after today's updates. Tooltip is the same on both workspaces: Área de trabajo actual: Escritorio 1 (in English Current workspace: workspace 1) same as what Stephen Gornick says in the previous post. What a stubborn tooltip! :-) -- Same tooltip on both workspaces when using Compiz https://bugs.launchpad.net/bugs/145704 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug assignee. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 332554] Re: gvfsd-trash crashed with SIGSEGV in g_type_check_instance_is_a()
** Attachment added: CoreDump.gz http://launchpadlibrarian.net/22948078/CoreDump.gz ** Attachment added: Dependencies.txt http://launchpadlibrarian.net/22948079/Dependencies.txt ** Attachment added: Disassembly.txt http://launchpadlibrarian.net/22948080/Disassembly.txt ** Attachment added: ProcMaps.txt http://launchpadlibrarian.net/22948081/ProcMaps.txt ** Attachment added: ProcStatus.txt http://launchpadlibrarian.net/22948082/ProcStatus.txt ** Attachment added: Registers.txt http://launchpadlibrarian.net/22948083/Registers.txt ** Attachment added: Stacktrace.txt http://launchpadlibrarian.net/22948084/Stacktrace.txt ** Attachment added: ThreadStacktrace.txt http://launchpadlibrarian.net/22948085/ThreadStacktrace.txt ** Visibility changed to: Public -- gvfsd-trash crashed with SIGSEGV in g_type_check_instance_is_a() https://bugs.launchpad.net/bugs/332554 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gvfs in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 211409] Re: gnome-display-properties shows incorrect monitor size
Ok, wishlist seems good to me. I also think tricking those diagonals to report marketing data is not the best solution. By the way, we have lots of CRT monitors at work because it's a high school, which means we keep using very old computers (like PIII in departments) along newer ones in classrooms. Maybe adding a text disclaimer in the dialog about CRT monitor sizes could be done, something like: 'Tube monitors usually report a screen size smaller than what they have; e.g. 15 for a 17 monitor, or 13 for a 15' This might be a bad idea, though, as more research should be done (and I think string freeze is on). Also would be good to detect if the monitor is CRT or LCD, but I haven't any LCD at hand to try things (I'll try the one at the library, if the librarian allows me :-) Anyway I believe that Windows reports correct monitor sizes when one installs the .inf that comes with the monitor, so it's not much smarter than Linux or Xorg. -- gnome-display-properties shows incorrect monitor size https://bugs.launchpad.net/bugs/211409 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-control-center in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 211409] Re: gnome-display-properties shows incorrect monitor size
(sorry for delay in answering, Internet broke at home). Yes, I have these lines: $ cat /var/log/Xorg.0.log | grep Max H-Image (II) RADEON(0): Max H-Image Size [cm]: horiz.: 31 vert.: 23 [...] (II) RADEON(0): Max H-Image Size [cm]: horiz.: 31 vert.: 23 (same line is there 12 times). I did the math you said: diagonal D = sqrt(31² + 23²) / 2.54 = sqrt(961 + 529) / 2.54 = sqrt(1490) / 2.54 = 38.60 /2.54 = 15.19 inches so you're right, my monitor is 15! But it's really a 17 model (or so I believed all these years :-) No, seriously I was starting to disbelieve Pithagoras, so I directly measured the screen diagonal with a ruler. Measuring just the visible image in the tube (there are unused black borders around it), diagonal is 39,5 cm = 15,55 inches; measuring the whole of the glass (including those black borders), diagonal is 40,5 cm = 15,94 inches. So yeah, again 15.something. I also measured a 15 Phillips 105S CRT monitor to know if it really has 15, and its diagonal (again the whole of the glass) is 35,2 cm = 13,86 inches. Another 15, a Samsung SyncMaster 550s CRT monitor has a diagonal of 34,7 cm = 13,66 inches. Hmm, maybe vendors are (were) selling CRT monitor a bit smaller than what they advertised? A trick I noticed in all these diagonal values (in inches) is that truncating them (say turning 15,19 into 15) and adding 2 yields the (supposedly) correct value (in this case 15 + 2 = 17 inches). The same seems to work for those 15 inchers: 13.something -- 13, plus 2 = 15 inches. Don't know if this trick can be useful for showing more-or-less correct diagonals (at least for CRTs); surely TFT monitors are another world in this regard. Sorry for this long comment, just my discoveries -- gnome-display-properties shows incorrect monitor size https://bugs.launchpad.net/bugs/211409 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-control-center in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 211409] Re: gnome-display-properties shows incorrect monitor size
** Attachment added: Monitor_Resolution_Settings.png http://launchpadlibrarian.net/13096578/Monitor_Resolution_Settings.png -- gnome-display-properties shows incorrect monitor size https://bugs.launchpad.net/bugs/211409 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-control-center in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 211409] [NEW] gnome-display-properties shows incorrect monitor size
Public bug reported: In Hardy beta, gnome-display-properties (I think, it's the new Xrandr GUI) shows an incorrect monitor size in the screen miniature: it says 'Samsung 15' but should say 'Samsung 17'. See screenshot attached. My monitor is a 17 Samsung SyncMaster 793DF, a CRT one (the '7' in the model means 17 in case it helps). It's not a very important bug I think, but showing the correct monitor size would give a better impression for users of this tool. If you need more info just tell me. ** Affects: gnome-control-center (Ubuntu) Importance: Undecided Status: New -- gnome-display-properties shows incorrect monitor size https://bugs.launchpad.net/bugs/211409 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-control-center in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 211409] Re: gnome-display-properties shows incorrect monitor size
Oh, I forgot to say the monitor has a VGA connector, plugged into the PC to the VGA one. PC is a desktop with an ATI 9600 XT graphics card, AGP. The card has VGA, DVI and TV-out connectors, I just use the VGA one. Output from lspci -vvnn | grep ATI: [EMAIL PROTECTED]:~$ lspci -vvnn | grep ATI 02:00.0 VGA compatible controller [0300]: ATI Technologies Inc M10 NQ [Radeon Mobility 9600] [1002:4e51] (prog-if 00 [VGA controller]) 02:00.1 Display controller [0380]: ATI Technologies Inc M10 NQ [Radeon Mobility 9600] (Secondary) [1002:4e71] (the two lines are for VGA and DVI connections I think). -- gnome-display-properties shows incorrect monitor size https://bugs.launchpad.net/bugs/211409 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-control-center in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 204362] Re: Filesystem-properties in Nautilus in continuous loop
Happens here as well but just on the ext3 partition (the one named File System in Places | Computer). CPU usage goes to 100% while count goes forever. Using Hardy Beta downloaded and installed this morning, with no updates. Does not happen neither in the windows XP partition (NTFS, 3.4 GB) nor in USB key I have mounted (FAT16, 2.1 GB). In both the properties window counts correctly the number of elements and reports a reasonable Total. So I suppose I'm using NTFS-3G, but seems to work well. Version installed is 1:1.2216-1ubuntu1. Like Juksu reported above, processes gvfsd, gvfsd-burn, gvfsd-computer and gvfsd-trash are running but sleeping. Also there is gnome-vfs-daemon running and sleeping. By the way, the properties window that counts forever does not show the nice colored graph about free and used space. Screenshot attached (no window decoration, Compiz in use). Computer is an old PIII 1GHz, 512 MB RAM, ATI 9600XT, 10 GB IDE hard disk, just 3 partitions (ntfs, swap and ext3, in /dev/sda1, /dev/sda2, /dev/sda5). ** Attachment added: properties_filesystem_ext3.png http://launchpadlibrarian.net/12827527/properties_filesystem_ext3.png -- Filesystem-properties in Nautilus in continuous loop https://bugs.launchpad.net/bugs/204362 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug assignee. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 204362] Re: Filesystem-properties in Nautilus in continuous loop
Thank you, sorry for posting after the bug fix. I'll be patient :-) We appreciate very much your promptly work, as well as that of upstream. it's the persons what count. -- Filesystem-properties in Nautilus in continuous loop https://bugs.launchpad.net/bugs/204362 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug assignee. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 150106] Re: Eye of Gnome doesn't display fullscreen
*** This bug is a duplicate of bug 149615 *** https://bugs.launchpad.net/bugs/149615 Same here too, using ATI 9600XT with -ati free driver and Compiz. Only happens with Compiz (i.e. using Normal or Extra effects). Without effects, EOG in full screen and slideshow modes does not flashes and works ok. The flashing starts when EOG is in full screen and attempts to hide its top menu bar; it disappears briefly, then reappears, then disappears, etc., all with flashing, as Mart said. The flashing looks like a lot of redraws of the screen (and rectangular portions of it) while EOG is trying to hide the menu bar. Seems as if the window manager (Compiz) and EOG where contending for the screen. I think it didn't happen in Gutsy alphas, with or without Compiz. Might be related to compiz 0.6? (just wondering, don't know for sure). Compiz works ok here, either with normal or extra effects. -- Eye of Gnome doesn't display fullscreen https://bugs.launchpad.net/bugs/150106 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug assignee. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 149615] Re: screen starts flickering in EOG when fullscreen
(I reported this in bug #150106, didn't notice it was a duplicate of this) Same here too, using ATI 9600XT with -ati free driver and Compiz (which works ok). Only happens with Compiz (i.e. using Normal or Extra effects). Without effects, EOG in full screen and slideshow modes does not flashes and works ok. The flashing looks like a lot of redraws of the screen (and rectangular portions of it) while EOG is trying to hide the menu bar. Seems as if the window manager (Compiz) and EOG where contending for the screen. I think it didn't happen in Gutsy alphas, with or without Compiz. -- screen starts flickering in EOG when fullscreen https://bugs.launchpad.net/bugs/149615 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug assignee. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 149615] Re: screen starts flickering in EOG when fullscreen
Just noticed that after opening a .doc document with OO.o Writer, the flashing of EOG in fullscreen does not happen and all is well. After closing Writer the flashing stills not happens. If I reboot and use EOG in fullscreen, the flashing is back. Curious! Also I forgot to say I'm running Gutsy beta fully up to date. -- screen starts flickering in EOG when fullscreen https://bugs.launchpad.net/bugs/149615 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug assignee. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 149615] Re: screen starts flickering in EOG when fullscreen
Just a crazy idea. Could this be related to bug #147943? There the bottom panel gets hidden by Compiz, here the menu bar gets hidden by EOG, then shown by Compiz, then hidden again by EOG... and thus the flashing. Hmm, no, it would stay hidden. Must be other thing. Anyway, who knows. -- screen starts flickering in EOG when fullscreen https://bugs.launchpad.net/bugs/149615 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug assignee. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 147070] Re: bottom panel not visible when desktop starts
The Compiz devels seem aware of this bug. I saw this post by Danny Baumann on Compiz's mailing list this evening (post at http://lists.freedesktop.org/archives/compiz/2007-October/002697.html): (quote) (...) Unfortunately I noticed today that release 0.6.0 contains a bad problem that allows e.g. desktop windows being stacked over normal windows when they are mapped. This results in normal windows and/or panels not being visible when compiz is launched with the Gnome or KDE session until the desktop window is restacked once (e.g. by clicking on it if the Raise on click option is enabled). I will release a 0.6.2 ASAP that fixes that problem, but until then, please either apply this commit to the release tarball: http://gitweb.freedesktop.org/?p=xorg/app/compiz.git;a=commit;h=b6c6acc70261d0942977441914c23e7a1c99215e or continue to use the compiz-0.6 branch. (...) (end of quote) Hope this helps. -- bottom panel not visible when desktop starts https://bugs.launchpad.net/bugs/147070 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug contact for gnome-panel in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 147070] Re: bottom panel not visible when desktop starts
*** This bug is a duplicate of bug 147943 *** https://bugs.launchpad.net/bugs/147943 Ah, all is well. Thank you for your info, I just saw that post and thought would be interesting to all. And many thanks also for your efforts, your work is very well regarded. -- bottom panel not visible when desktop starts https://bugs.launchpad.net/bugs/147070 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug contact for gnome-panel in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 147070] Re: bottom panel not visible when desktop starts
Erm, another rectification: the nautilus window is not shown when login after a fresh boot. Subsequent times (e.g. logout and then login) it's usually shown. What a nuissance! -- bottom panel not visible when desktop starts https://bugs.launchpad.net/bugs/147070 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug contact for gnome-panel in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 147070] Re: bottom panel not visible when desktop starts
I can confirm this too; just happens with Compiz, not with Metacity. Just click anywhere in the desktop and the bottom panel comes from the void. Also, it's not just the bottom panel that's not visible; I have session restore set, and when I login, a Nautilus window I left opened at previous logout is usually not visible. Just click anywhere in the desktop and both the nautilus window (and bottom panel) are finally shown. To set/unset session restore go to System | Preferences | Sessions, tab Session options, check box Automatically remember running apps when closing session (I'm translating from Spanish). -- bottom panel not visible when desktop starts https://bugs.launchpad.net/bugs/147070 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug contact for gnome-panel in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 147070] Re: bottom panel not visible when desktop starts
I should rectify the second paragraph in my previous comment: after today's update (October 1, 2007) the nautilus window is always shown after login (using Compiz). Many thanks for the fix, you rock hard! -- bottom panel not visible when desktop starts https://bugs.launchpad.net/bugs/147070 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug contact for gnome-panel in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 145704] Re: Same tooltip on both workspaces when using Compiz
Still happens as of 28/09/2007, after updating Gutsy (it's up to date, so it should be Gutsy beta now). Switcher and gnome-applets are same versions as before the update (switcher 2.20.0.1, gnome-applets 2.20.0-0ubuntu1). Just gnome-panel has new version: gnome-panel 2.20.0.1-0ubuntu4. -- Same tooltip on both workspaces when using Compiz https://bugs.launchpad.net/bugs/145704 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug assignee. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 145704] Re: Same tooltip on both workspaces when using Compiz
Oh! I thought it was Compiz messing with the tooltip's text for each workspace, as it just happens with Compiz. Should I fill a bug in Gnome's bugzilla? Maybe they can come up with a solution (though things involving Compiz seem not easy). -- Same tooltip on both workspaces when using Compiz https://bugs.launchpad.net/bugs/145704 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug contact for gnome-panel in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 145704] Re: Same tooltip on both workspaces when using Compiz
Using Gutsy alpha, updated as of 26/09/2007. Still not using the beta just released, I'll try to update to it today after work. I'm using Gnome 2.20.0 with normal effects now, and to switch workspaces just click on one of the two thumbnails in the switcher (at right in screen's bottom panel). Using Super+e also works, and very smoothly. Tooltips about windows in a workspace are correct, but when placing the mouse in an unused area of the workspace thumbnail bot workspaces show the same text in the tooltip, Current Workspace: Workspace 1 (as if they were the same, but they are 2 different workspaces, I can switch to first one -has windows- or second one -has no windows-). The switcher is 2.20.0.1 (from context menu, About). Gnome applets is 2.20.0-0ubuntu1, gnome-panel is 2.20.0.1-0ubuntu2 I'm using the free -ati driver with a Radeon 9600XT AGP card (256MB, VGA, DVI, TV-out, just using the VGA) and almost everything is smooth in Compiz (only issues aside from these tooltips are the video playing + switching workspaces and the flicker in animation used to bring windows to the front). -- Same tooltip on both workspaces when using Compiz https://bugs.launchpad.net/bugs/145704 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug assignee. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 18735] Re: [gutsy] rhythmbox doesn't automatically start after selecting audio file with Nautilus
Still happens in Gutsy (Ubuntu 7.10 alpha 5) using: rhythmbox 0.11.2-0ubuntu2 nautilus 1:2.19.91-0ubuntu1 To reproduce the bug: in Nautilus go to a directory with an .ogg file, double click on it, and an error message pops up [screenshot 1] saying: (name of song) cannot be opened No application suitable for automatic installation is available for handling this kind of file. It seems Nautilus doesn't know about the file association between .ogg files and Rhythmbox, even when it is set in System - Preferences - Preferred applications [screenshot 2]. To try it in another way: right-click same file in Nautilus, the context menu has as first entry Open (without saying which app to open with), and next entry says Open with Rhythmbox [screenshot 3]. Selecting this second option opens up Rhythmbox, but the song doesn't play [screenshot 4]. The only way to listen the .ogg file is (inside Rhythmbox) going to Music - Import file... and importing the song [screenshot 5]. Very frustrating, hearing a song should not require this amount of work. Ps: All screenshots, with comments, are combined in attached image. ** Attachment added: screenshots_combined.jpg http://launchpadlibrarian.net/9050039/screenshots_combined.jpg -- [breezy] rhythmbox doesn't automatically start after selecting audio file with Nautilus https://bugs.launchpad.net/bugs/18735 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a direct subscriber. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 77110] [Possibly solved] deskbar-applet does not use new theme background until relogin
Hi, I have noticed that all issues in this bug report seem to be resolved now (in Ubuntu 7.10 tribe 5). This is after updating last night to deskbar-applet 2.19.91-0ubuntu1 (version found using 'dpkg -l deskbar-applet', thanks bmurray and BugSquad's FAQ for showing how). Things specifically solved: * Changes in background color now take effect immediately. No need to log out/log in or reload the applet for the change to happen. * Changing theme to Glider, deskbar uses new panel's background color. * Using other themes also works (tried Glider, Human, Clearlooks, Glossy and (ugh!) Inverse high contrast). * Background for the history drop-down also uses the current theme color. Another thing solved (it isn't in this bug, but I was looking for this when found this bug and could be possibly related): * Icon now seems to have a transparent background, good (not in tribe 4 and tribe 5 before the update to deskbar-applet 2.19.91-0ubuntu1). If someone can try the above things and get the same results, maybe this bug could be closed now. -- does not use new theme background until relogin https://bugs.launchpad.net/bugs/77110 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is the registrant for deskbar-applet. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 135346] Re: missing button
Hi phirestalker. From what I see in my Sound Juicer, there are just 2 buttons in the main window: Play and Extract. They seem adequate to perform the tasks Sound Juicer does, namely play those CD tracks marked in the list and extract the tracks marked into ogg files (or some other format). Did you see a Next track button in a previous Sound Juicer version? If so, maybe its authors have rearranged the GUI and decided to remove that button. Sound Juicer is an app that does just a few things (but does them well, you know :-) Anyway I attach a screenshot of my Sound Juicer to let you see it. I'm now using now sound-juicer 2.19.3-0ubuntu1 (Ubuntu 7.10 tribe 5). (translating from spanish to english, maybe the english label for Play is Reproduce or something...) ** Attachment added: Screenshot of current Sound Juicer http://launchpadlibrarian.net/9034787/screenshot-Sound%20Juicer.png -- missing button https://bugs.launchpad.net/bugs/135346 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug assignee. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
