[Bug 2059847] Re: Input lag or freezes on Nvidia desktops with X11
Probably not related, but "nvidia-driver-535" was mentioned above in a post. I'm now using ppa:vanvugt/mutter and it seems to be fine, but apt also upgraded nvidia driver from 525 to 535 (maybe not related at all just the new nvidia driver was presented now?). Since then I have hard lock-ups on my system what I've never seen before (no keyboard and mouse works). After forced power-off I see this in the kernel log file: Apr 5 15:42:57 rygel kernel: [ 3282.354685] NVRM: GPU at PCI::01:00: GPU-78091d7e-2007-c450-19a1-f764cae07b00 Apr 5 15:42:57 rygel kernel: [ 3282.354689] NVRM: Xid (PCI::01:00): 79, pid='', name=, GPU has fallen off the bus. Apr 5 15:42:57 rygel kernel: [ 3282.354691] NVRM: GPU :01:00.0: GPU has fallen off the bus. Apr 5 15:42:57 rygel kernel: [ 3282.354730] NVRM: A GPU crash dump has been created. If possible, please run Apr 5 15:42:57 rygel kernel: [ 3282.354730] NVRM: nvidia-bug-report.sh as root to collect this data before Apr 5 15:42:57 rygel kernel: [ 3282.354730] NVRM: the NVIDIA kernel module is unloaded. Apr 5 15:43:02 rygel kernel: [ 3287.474709] NVRM: Error in service of callback Apr 5 15:48:05 rygel kernel: [ 3590.071558] Asynchronous wait on fence NVIDIA:nvidia.prime:11cbb timed out (hint:intel_atomic_commit_ready [i915]) I've never seen anything similar before, though I have this very system/install with nvidia's driver since more than a year or so. Since it's probably a totally different issue (though I am not 100% sure), I've reported here: https://bugs.launchpad.net/ubuntu/+source/nvidia- graphics-drivers-535/+bug/2060303 It seems now this hard lock up occurs several times per day :( Though the terminal slowness/keyboard input lag/etc is gone, which is good, of course! -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/2059847 Title: Input lag or freezes on Nvidia desktops with X11 To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/2059847/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2059847] Re: Input lag in native terminal on Nvidia desktops with X11
I've fetched some older versions (again, I am running 22.04.4) of packages gir1.2-mutter-10 libmutter-10-0 and mutter-common and made them into hold status. After a very ugly and dangerous move, namely editing /var/lib/dpkg/status by hand (to comply the dependencies of gnome-shell which was broken by forcing older versions of packages ... maybe I should have simply installed also older version of gnome-shell, hmm ...), now everything works perfectly again. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/2059847 Title: Input lag in native terminal on Nvidia desktops with X11 To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/2059847/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2059847] Re: Input lag in native terminal on Nvidia desktops with X11
I have similar problem. I'm currently using Ubuntu 22.04.4 LTS (x86_64). Since some days (maybe three?) I see very odd behaviour from programs running in gnome-terminal (or xfce4-terminal if it does not matter, I guess the problem is not the terminal itself but VTE probably or similar? - no problem when using KDE's Konsole for example!). I also have nvidia's driver. Some programs "only" have very significant input delay, sometimes like 1 sec or so. However interestingly some programs (most notably neomutt) has "infinite" delay, ie, it lags behind exactly one key. For example if I move upwards in the email list, then pressing down still moves up once. And so on, it seems to be true for all keys. Other applications running in terminal seems to "only" have more significant delay, but it's not always consistent. Especially ssh'ing to a remote machine is a very bad experience now, but even on the local host, without any ssh involved just the shell, it's very notable. $ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 22.04.4 LTS Release:22.04 Codename: jammy $ dpkg -l | grep mutter ii gir1.2-mutter-10:amd6442.9-0ubuntu7 amd64GObject introspection data for Mutter ii libmutter-10-0:amd64 42.9-0ubuntu7 amd64window manager library from the Mutter window manager ii mutter-common 42.9-0ubuntu7 all shared files for the Mutter window manager -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/2059847 Title: Input lag in native terminal on Nvidia desktops with X11 To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/2059847/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1288655] Re: Terminal height shrinks - repeatedly restored shorter than the previous height
22.04 fresh install, even worse, the window shrunk by 3 lines each time :-O And now even shrinks by 3 rows ... I use toggle full screen back and forth, since this is what I really use a lot, not the maximize. But maximize has the same effect, just checked. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-terminal in Ubuntu. https://bugs.launchpad.net/bugs/1288655 Title: Terminal height shrinks - repeatedly restored shorter than the previous height To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-terminal/+bug/1288655/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1288655] Re: Terminal height shrinks - repeatedly restored shorter than the previous height
I'm using 20.04.2 LTS (focal), I can also confirm the problem exists there with Xorg and gnome-shell (no idea about 20.10 and/or Wayland though). -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-terminal in Ubuntu. https://bugs.launchpad.net/bugs/1288655 Title: Terminal height shrinks - repeatedly restored shorter than the previous height To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-terminal/+bug/1288655/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1881038] [NEW] when trying to lock my screen I always get: gnome-shell crashed with SIGSEGV in _st_theme_node_ensure_background()
Public bug reported: When I try to lock the screen, gnome-shell seems to crash, always since two days or so (I update daily basis). crash file is attached. x86_64 Ubuntu 20.04 LTS ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.2-1ubuntu1~20.04.1 ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34 Uname: Linux 5.4.0-31-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu May 28 01:38:46 2020 DisplayManager: gdm3 InstallationDate: Installed on 2020-03-06 (82 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200304) RelatedPackageVersions: mutter-common 3.36.2-1ubuntu1~20.04.1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ** Attachment added: "crash file" https://bugs.launchpad.net/bugs/1881038/+attachment/5377584/+files/_usr_bin_gnome-shell.1000.crash -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1881038 Title: when trying to lock my screen I always get: gnome-shell crashed with SIGSEGV in _st_theme_node_ensure_background() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1881038/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1825559] [NEW] Upgrading 18.10 to 19.04: cannot leave overview mode, computer needs to be restarted
Public bug reported: I've upgraded my Ubuntu 18.10 to 19.04. Everything looked okey, however if I enter gnome shell "overview mode" I cannot leave it anymore, I can't select any window, type to search etc, and all my windows are in the foreground, covering the search bar etc, but not possible to select them. Simply I can't do anything. I can launch applications from the dock but cannot see and access them anymore. So basically I stuck in overview mode which does not work too much. What I can do, is to use the top panel to log out. If I do that, and login again, I only get a black screen and nothing more. I have to press the power button at that point to shut the computer off, so I can turn on again. It seems everything works, just entering into that "overview mode" kills everything then and only reboot helps from that point. Sorry, I am not sure what the official name of the gnome3 shell "overview mode" possibly I used the wrong terminology. Also, my bad English cannot help either to express the problem well enough, I guess. ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1825559 Title: Upgrading 18.10 to 19.04: cannot leave overview mode, computer needs to be restarted To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1825559/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 965921] Re: gnome-shell most keyboard shortcuts not working
Still happens time to time, even with fresh 18.10 install. It's a "miracle" that it's such an old bug, but still hits us :( -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/965921 Title: gnome-shell most keyboard shortcuts not working To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/965921/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1706008] Re: gnome-terminal window becomes one line shorter after every fullscreen/windowed cycle
*** This bug is a duplicate of bug 1288655 *** https://bugs.launchpad.net/bugs/1288655 So, as thinking on this, I must say, maybe this is my mis-interpretation of the problem. Maybe not the colour prompt causes this, but if I use a newer (or ssh into a newer) ubuntu box versus ssh into an older version (in both cases ssh in the window only changes the situation of "shrinking" if the window title is modified to reflect this, ie like username@machine1:~ changes into username@machine2:~ because of the ssh). I really feel bad not to be able to express this in a sane way, but it's kind of odd issue for me at least. Just changing PS1 does not change the situation for me either. Ok, now it's even more odd, just trying to test it ... Now window shrinks by TWO lines not only one, and the behaviour I tried to describe above seems not to apply at all :-O I don't know what I can say, maybe this is a more complex issue and my assumption was only true for the given case when I last tested it ...Sorry about that. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-terminal in Ubuntu. https://bugs.launchpad.net/bugs/1706008 Title: gnome-terminal window becomes one line shorter after every fullscreen/windowed cycle To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1706008/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1706008] Re: gnome-terminal window becomes one line shorter after every fullscreen/windowed cycle
*** This bug is a duplicate of bug 1288655 *** https://bugs.launchpad.net/bugs/1288655 I don't know how to tell, but it seems the bug happens when the prompt has effect on the title of the window. What I mean here: opening a gnome-terminal with a colourful PS1 causes this. However if I ssh into another machine which does update the title of the window and the prompt does not use colour, the shrinking stops if I try fullscreen/back cycles again ... If I ssh into a machine which does have this "new" colour prompt then it continues ... If I ssh into a machine which does not effect the title bar, it does not effect the strange behaviour though. So, what I can think about there is some connection about the window bar title updating by the prompt (???) sorry, I have really no idea hot it happens :-O -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-terminal in Ubuntu. https://bugs.launchpad.net/bugs/1706008 Title: gnome-terminal window becomes one line shorter after every fullscreen/windowed cycle To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1706008/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 965921] Re: gnome-shell most keyboard shortcuts not working
This bug still affects me now, upgraded to the to-be-released 17.10 (artful). I was a die hard text only user of Linux systems for a while, so I still configure system to "emulate" something like this, ie ALT+F1...F8 to switch between workspaces. However, ALT-F5 does not _always_ works. Sometimes it does sometimes it doesn't and even it changes behaviour from time to time without reboot, logout or anything, which is strange. I can't find how I tell that alt-f5 is _my_ shortcut. It's very annoying that system randomly 'forgets' it, and then somehow remembers it again after some time :-O -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/965921 Title: gnome-shell most keyboard shortcuts not working To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/965921/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 965921] Re: gnome-shell most keyboard shortcuts not working
Oh, by the way, it's often happens after locking then unlocking the screen though! It often fixes the problem too (if it was before). But not always ... -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/965921 Title: gnome-shell most keyboard shortcuts not working To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/965921/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1706008] Re: gnome-terminal window becomes one line shorter after every fullscreen/windowed cycle
I've just noticed: it seems it only happens if the shell prompt is colourfull. if it's not, there is no shrinking of the gnome-terminal window height when cycling between fullscreen and windowed mode ... Interesting!! -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-terminal in Ubuntu. https://bugs.launchpad.net/bugs/1706008 Title: gnome-terminal window becomes one line shorter after every fullscreen/windowed cycle To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1706008/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1706008] [NEW] gnome-terminal window becomes one line shorter after every fullscreen/windowed cycle
Public bug reported: It's 17.04 64 bit Ubuntu, wayland+gnome-shell. I have key F11 configured to toggle between fullscreen and windowed mode. Just noticed, that every time I press F11 to get full screen, then F11 to get back windowed mode, the window becomes one line shorter ... Continuing this I can hit the situation to have only a one line tall window. It's kinda annoying, since during my work I use tons of terminal windows, and I often use full screen / windowed mode switching. Now, I have to resize the window again and again before it becomes too shallow ... ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: gnome-terminal 3.20.2-1ubuntu8 ProcVersionSignature: Ubuntu 4.10.0-28.32-generic 4.10.17 Uname: Linux 4.10.0-28-generic x86_64 ApportVersion: 2.20.4-0ubuntu4.5 Architecture: amd64 CurrentDesktop: GNOME Date: Mon Jul 24 11:14:01 2017 InstallationDate: Installed on 2015-07-10 (744 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release i386 (20150422) SourcePackage: gnome-terminal UpgradeStatus: Upgraded to zesty on 2017-06-20 (33 days ago) ** Affects: gnome-terminal (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug wayland-session zesty -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-terminal in Ubuntu. https://bugs.launchpad.net/bugs/1706008 Title: gnome-terminal window becomes one line shorter after every fullscreen/windowed cycle To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1706008/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1704360] Re: Cannot resize gnome-terminal window in gnome wayland session with mouse
Nice to hear, that is fixed in 17.10 already. Well, I've just read many discussion on this topic. For example MPV issue: https://github.com/mpv- player/mpv/issues/139 windows has no border. It seems for me, projects like mpv waiting for some server side window decoration to be done, instead of implementing in client side for every possible application (and for being realistic, I feel it's a better option anyway, or well "more realistic"), thus the issue is "wontfix". Surely, gnome-terminal may be different being a gtk3 app, may be handled at gtk3 level for this issue? As far as I know at least, wayland makes it possible to provide 'server side decorations' more like the classic X11 window manager scenario. And the last comment on that issue is funny: "In two years, every compositor will be able to draw server-side decorations." (so "wontfix" ...). Ok, I was kinda off-topic now, sorry about that. Now I am more involved with gnome-terminal at least ... Thanks for the info, that 17.10 seems to solve this issue at least! ** Bug watch added: github.com/mpv-player/mpv/issues #139 https://github.com/mpv-player/mpv/issues/139 -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1704360 Title: Cannot resize gnome-terminal window in gnome wayland session with mouse To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1704360/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1704360] [NEW] Cannot resize window in gnome wayland session with mouse
Public bug reported: Running gnome-shell + wayland on ubuntu 17.04 here. If I have a "legacy" (X11) application, like firefox or xterm (running with Xwayland, I guess) I can resize its window normally, ie mouse shape changes into resize-signaling shape near the window borders and I can do the job. However pure-wayland clients, like gnome-terminal it simply does not work, which is very annoying no need to say. I can do the resize with eg ALT+right click and select "resize" but it's kinda more work to do a very simple task (and also it seems there is only horizontal OR vertical resize, not the both what I used to if I move the mouse near to the corner of the window). ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: gnome-shell 3.24.2-0ubuntu0.1 ProcVersionSignature: Ubuntu 4.10.0-28.32-generic 4.10.17 Uname: Linux 4.10.0-28-generic x86_64 ApportVersion: 2.20.4-0ubuntu4.4 Architecture: amd64 CurrentDesktop: GNOME Date: Fri Jul 14 11:43:52 2017 DisplayManager: gdm3 InstallationDate: Installed on 2015-07-10 (734 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release i386 (20150422) SourcePackage: gnome-shell UpgradeStatus: Upgraded to zesty on 2017-06-20 (23 days ago) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug wayland-session zesty -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1704360 Title: Cannot resize window in gnome wayland session with mouse To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1704360/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1700465] Re: gnome-shell --replace does not work: Can't initialize KMS backend: Could not get session ID: No such file or directory
I don't know anything about gnome internals, but with trying to strace, I see this: getpeername(2, 0x7ffec62742e0, 0x7ffec62742dc) = -1 ENOTSOCK (Socket operation on non-socket) which is odd, since stderr is not a socket usually, indeed ... Other than that, the mentioned error message can be found here, after trying to "apt source" some gnome specific packages: mutter-3.24.1/src/backends/native/meta-launcher.c in function get_session_proxy() Though for sure, I have exactly zero knowledge about these :-/ -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1700465 Title: gnome-shell --replace does not work: Can't initialize KMS backend: Could not get session ID: No such file or directory To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1700465/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1700465] [NEW] gnome-shell --replace does not work: Can't initialize KMS backend: Could not get session ID: No such file or directory
Public bug reported: gnome-shell --replace does not work and reports: (gnome-shell:15848): mutter-WARNING **: Can't initialize KMS backend: Could not get session ID: No such file or directory (gnome-shell:16495): mutter-WARNING **: Can't initialize KMS backend: Could not get session ID: No such file or directory (gnome-shell:4910): mutter-WARNING **: Can't initialize KMS backend: Could not get session ID: No such file or directory ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: gnome-shell 3.24.2-0ubuntu0.1 ProcVersionSignature: Ubuntu 4.10.0-25.29-generic 4.10.17 Uname: Linux 4.10.0-25-generic x86_64 ApportVersion: 2.20.4-0ubuntu4.2 Architecture: amd64 CurrentDesktop: GNOME Date: Mon Jun 26 09:03:06 2017 DisplayManager: gdm3 InstallationDate: Installed on 2015-07-10 (716 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release i386 (20150422) SourcePackage: gnome-shell UpgradeStatus: Upgraded to zesty on 2017-06-20 (5 days ago) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug wayland-session zesty -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1700465 Title: gnome-shell --replace does not work: Can't initialize KMS backend: Could not get session ID: No such file or directory To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1700465/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1573563] Re: Toggling full screen mode does not work well after upgrading to Ubuntu 16.04 from 15.10
I've attached some screen shots, if it's more understandable than my not-so-perfect English, sorry about that. Moreover, I had the suspect that it can be a generic window manager issue more, rather than gnome-terminal specific problem, but starting the KDE console (konsole) its fullscreen toggle functionality seems to be OK, just I have problem with the gnome-terminal, it seems. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-terminal in Ubuntu. https://bugs.launchpad.net/bugs/1573563 Title: Toggling full screen mode does not work well after upgrading to Ubuntu 16.04 from 15.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1573563/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1573563] [NEW] Toggling full screen mode does not work well after upgrading to Ubuntu 16.04 from 15.10
Public bug reported: I use tons of terminal windows (gnome-terminal) all the time for various tasks. Thus, it's important for me to be able to go into full screen mode (F11) - if I need more attention or space and switch back later. I haven't got any problem with this in previous Ubuntu versions, after "switching back" from fullscreen mode, I got the terminal window at its original place and size. However, after upgrading to Ubuntu 16.04 recently, if I press F11 to switch back, the terminal window is enlarged to cover almost the full desktop, it's not "full screen" anymore (that's OK), ie I can see panel, borders, etc, but still it's not the original size and position of the window. So I have to manually resize the window all the time. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: gnome-terminal 3.18.3-1ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic i686 ApportVersion: 2.20.1-0ubuntu2 Architecture: i386 CurrentDesktop: Unity Date: Fri Apr 22 13:48:12 2016 InstallationDate: Installed on 2014-05-08 (715 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release i386 (20140417) SourcePackage: gnome-terminal UpgradeStatus: Upgraded to xenial on 2015-10-08 (196 days ago) ** Affects: gnome-terminal (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 xenial ** Attachment added: "Screenshot before pressing F11" https://bugs.launchpad.net/bugs/1573563/+attachment/4642820/+files/Screenshot%20from%202016-04-22%2014-09-39.png -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-terminal in Ubuntu. https://bugs.launchpad.net/bugs/1573563 Title: Toggling full screen mode does not work well after upgrading to Ubuntu 16.04 from 15.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1573563/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1573563] Re: Toggling full screen mode does not work well after upgrading to Ubuntu 16.04 from 15.10
** Attachment added: "Screenshot after pressing F11 (fullscreen, OK)" https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1573563/+attachment/4642824/+files/Screenshot%20from%202016-04-22%2014-09-59.png -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-terminal in Ubuntu. https://bugs.launchpad.net/bugs/1573563 Title: Toggling full screen mode does not work well after upgrading to Ubuntu 16.04 from 15.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1573563/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1573563] Re: Toggling full screen mode does not work well after upgrading to Ubuntu 16.04 from 15.10
** Attachment added: "Screenshot after pressing F11 again, not OK!" https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1573563/+attachment/4642825/+files/Screenshot%20from%202016-04-22%2014-10-13.png -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-terminal in Ubuntu. https://bugs.launchpad.net/bugs/1573563 Title: Toggling full screen mode does not work well after upgrading to Ubuntu 16.04 from 15.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1573563/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1501250] Re: double clicking on a URL drops the protocol from the URL
Quite ugly "bug" :( I had the habit "since ages" (ehhh) to work in terminal windows, and copy URLs etc. It worked nicely with a quick double click on the URL which does not work anymore after upgrade to Wily :( I understand that it was not meant to select URLs anyway (and not a perfect solution either), but in practice it worked reasonably well. I've just wanted to write a bug report about this, however launchpad was intelligent enough to find me a similar already existing bug report, this one ;) -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-terminal in Ubuntu. https://bugs.launchpad.net/bugs/1501250 Title: double clicking on a URL drops the protocol from the URL To manage notifications about this bug go to: https://bugs.launchpad.net/vte/+bug/1501250/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1292209] Re: Locking screen does not work in case of fullscreen gnome-terminal
It happened again now (up-to-date 14.04 LTS now): screen started to fade out after pressing CTRL-ALT-L, then it stuck in the middle of process, I can move the mouse, but I can't do anything neither with mouse or keyboard. What helped: switching to text console (CTRL-ALT-F1) login, then killing gnome-terminal. After that, I can switch back to X.org (ALT-F7) and I see the unlock screen now. However of course this is not an ideal solution, and I lost all of my (tons of ...) gnome-terminal windows. Again: it seems it happens sometimes, if I press CTRL-ALT-L when I have a fullscreen (not maximized, but full screen) gnome-terminal on the current workspace. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-screensaver in Ubuntu. https://bugs.launchpad.net/bugs/1292209 Title: Locking screen does not work in case of fullscreen gnome-terminal To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-screensaver/+bug/1292209/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1292965] [NEW] Unlocking screensaver needs two redundant steps
Public bug reported: Up-to-date 32 bit 14.04 on Lenovo L520 notebook. After locking the screen eg with CTRL-ALT-L I want to unlock it, so I give my password. It works, but sometimes after some seconds of unlocked state (I already working, ie typing etc) the screen fades out again and I have to give my password again to unlock. It's even more interesting with my wife's account (on the same machine/OS though): she must type her password two times, and the second password prompt follows immediately, not the very same case as mine. It's another issue and I am not sure if it's related at all: after locking the screen never turns off, which was the behaviour before upgraded to 14.04 and I guess the normal behaviour, as it's not so useful to waste power to show the screen for hours, it should goes of after locking till some keypress and/or mouse movement, I think. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: gnome-screensaver 3.6.1-0ubuntu11 ProcVersionSignature: Ubuntu 3.13.0-17.37-generic 3.13.6 Uname: Linux 3.13.0-17-generic i686 ApportVersion: 2.13.3-0ubuntu1 Architecture: i386 CurrentDesktop: Unity Date: Sat Mar 15 20:55:00 2014 GnomeSessionIdleInhibited: No GnomeSessionInhibitors: None GsettingsGnomeSession: org.gnome.desktop.session session-name 'gnome' org.gnome.desktop.session idle-delay uint32 3600 InstallationDate: Installed on 2012-03-03 (742 days ago) InstallationMedia: Ubuntu 11.04 Natty Narwhal - Release i386 (20110427.1) SourcePackage: gnome-screensaver UpgradeStatus: Upgraded to trusty on 2013-10-18 (148 days ago) ** Affects: gnome-screensaver (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 trusty -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-screensaver in Ubuntu. https://bugs.launchpad.net/bugs/1292965 Title: Unlocking screensaver needs two redundant steps To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-screensaver/+bug/1292965/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1292209] Re: Locking screen does not work in case of fullscreen gnome-terminal
Btw, the other even more odd workaround: switch to text console, kill gnome-terminal and switch back to the VT used by X, and you can unlock then. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-screensaver in Ubuntu. https://bugs.launchpad.net/bugs/1292209 Title: Locking screen does not work in case of fullscreen gnome-terminal To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-screensaver/+bug/1292209/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1292209] [NEW] Locking screen does not work in case of fullscreen gnome-terminal
Public bug reported: Somewhat odd situation. If I use CTRL-ALT-L to lock my session, it normally works as expected. However if there is a fullscreen gnome- terminal (F11) was on the screen, CTRL-ALT-L does something interesting: it begins fade the screen but it's left in a middle state, no way to unlock but also it's not locked visually though I can't type anymore. More interestingly: it seems the screen IS locked, since if I type my password blindly (I still see the half faded session ...) I get back my desktop in a usable state! Interesting. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: gnome-screensaver 3.6.1-0ubuntu11 ProcVersionSignature: Ubuntu 3.13.0-17.37-generic 3.13.6 Uname: Linux 3.13.0-17-generic i686 ApportVersion: 2.13.3-0ubuntu1 Architecture: i386 CurrentDesktop: Unity Date: Thu Mar 13 21:25:10 2014 GnomeSessionIdleInhibited: No GnomeSessionInhibitors: None GsettingsGnomeSession: org.gnome.desktop.session session-name 'gnome' org.gnome.desktop.session idle-delay uint32 3600 InstallationDate: Installed on 2012-03-03 (740 days ago) InstallationMedia: Ubuntu 11.04 Natty Narwhal - Release i386 (20110427.1) SourcePackage: gnome-screensaver UpgradeStatus: Upgraded to trusty on 2013-10-18 (146 days ago) ** Affects: gnome-screensaver (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 trusty -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-screensaver in Ubuntu. https://bugs.launchpad.net/bugs/1292209 Title: Locking screen does not work in case of fullscreen gnome-terminal To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-screensaver/+bug/1292209/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1290904] [NEW] System behaviour does not follow user settings in some cases
Public bug reported: First of all, sorry, I am not sure what kind of package should I specify with this report. Upgraded to trusty, and some of the user settings are not used (or only temporary) anymore: * I use F12 to open a terminal since ages (I depends most on terminals in my work). Setting that works, but after next login, it's forgotten and must be set again. * Whatever I set up for action in case of closing lid of the notebook it always goes into sleep mode, however I _don't_ want that. I'm not sure if there is common problem of these bugs however, just I think it can be common settings problem ... It's daily updated 32bit system on a Lenovo L520 notebook. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: gnome-settings-daemon 3.8.6.1-0ubuntu9 ProcVersionSignature: Ubuntu 3.13.0-17.37-generic 3.13.6 Uname: Linux 3.13.0-17-generic i686 ApportVersion: 2.13.3-0ubuntu1 Architecture: i386 CurrentDesktop: Unity Date: Tue Mar 11 16:16:11 2014 InstallationDate: Installed on 2012-03-03 (738 days ago) InstallationMedia: Ubuntu 11.04 Natty Narwhal - Release i386 (20110427.1) SourcePackage: gnome-settings-daemon UpgradeStatus: Upgraded to trusty on 2013-10-18 (143 days ago) ** Affects: gnome-settings-daemon (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 trusty -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1290904 Title: System behaviour does not follow user settings in some cases To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1290904/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1011594] Re: Dragging of tabs does not work with chrome and firefox
-- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to metacity in Ubuntu. https://bugs.launchpad.net/bugs/1011594 Title: Dragging of tabs does not work with chrome and firefox To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/metacity/+bug/1011594/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1011594] [NEW] Dragging of tabs does not work with chrome and firefox
Public bug reported: I'm using Unity-2D (so metacity), up-to-date precise, 32 bit. Since a while (I can't tell the exact point, since I've just noticed it) I can't drag tabs in chrome and firefox (to re-order tabs) anymore. I am sure in one thing: it works in oneiric at least, since I have a machine running oneiric. If I try to drag a tab in firefox (version 13, not from ubuntu but installed manually). The twist: I use firefox from another machine (running hardy) but via ssh X11 redirection. However, chrome is running on the local machine. In firefox if I drag a tab, nothing happens: I can see the translucent image of the page and I can drag it, I can't dock it between the tabs, if I release the mouse button, the image just jumps back. With chrome, again: I can see the translucent image, and I can drag it, but again, I can't dock it, if I release the mouse button it creates a new window instead of docking among the already existing tabs in the already existing window at the desired position. It seems that locally launched firefox 13 (from ubuntu repo!) works however. Also tab re-arraning eg in geany seems to be OK. Btw, composite effects are enabled via gconf in metacity. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: metacity 1:2.34.1-1ubuntu11 ProcVersionSignature: Ubuntu 3.2.0-24.38-generic-pae 3.2.16 Uname: Linux 3.2.0-24-generic-pae i686 ApportVersion: 2.0.1-0ubuntu9 Architecture: i386 Date: Mon Jun 11 14:25:45 2012 InstallationMedia: Ubuntu-Server 10.04.1 LTS Lucid Lynx - Release i386 (20100816.2) SourcePackage: metacity UpgradeStatus: Upgraded to precise on 2012-03-01 (101 days ago) ** Affects: metacity (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 precise -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to metacity in Ubuntu. https://bugs.launchpad.net/bugs/1011594 Title: Dragging of tabs does not work with chrome and firefox To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/metacity/+bug/1011594/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 985449] [NEW] unity-2d launcher behind a full screen window
Public bug reported: Not exactly a show-stopper bug ... I have a terminal window, not maximazed, but full screen. I'm using Unity-2D+metacity, with composite support is switched on. The terminal window is semi-transparent. Now, if I move the mouse to the left side of the screen, I can see (through the semi transparent window) that Unity-2D's launcher is shown (it's configured for auto-hide). I guess it's a problem, since in case of a full screen window, I wouldn't except that anything other is activated if I move the mouse through the screen, as the screen is filled with a full screen window, so no other thing should be involved. The only problem I have with this: if I switch workspace then, unity-2d's launcher is still shown, so I have to move the mouse pointer on it, and then remove so it can be hidden, which is a bit annoying to do all the time, as I would like auto-hide ... Maybe it's not a metacity but an unity-2d problem? ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: metacity 1:2.34.1-1ubuntu11 ProcVersionSignature: Ubuntu 3.2.0-23.36-generic-pae 3.2.14 Uname: Linux 3.2.0-23-generic-pae i686 ApportVersion: 2.0.1-0ubuntu5 Architecture: i386 Date: Thu Apr 19 09:34:33 2012 InstallationMedia: Ubuntu-Server 10.04.1 LTS Lucid Lynx - Release i386 (20100816.2) SourcePackage: metacity UpgradeStatus: Upgraded to precise on 2012-03-01 (48 days ago) ** Affects: metacity (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 precise -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to metacity in Ubuntu. https://bugs.launchpad.net/bugs/985449 Title: unity-2d launcher behind a full screen window To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/metacity/+bug/985449/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 985449] Re: unity-2d launcher behind a full screen window
-- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to metacity in Ubuntu. https://bugs.launchpad.net/bugs/985449 Title: unity-2d launcher behind a full screen window To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/metacity/+bug/985449/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 980013] [NEW] moving icons on the desktop leaves some garbage
Public bug reported: I'm using Unity-2D with metacity (composite effects are on). I also switched on icons on the desktop (computer, home, mounted filesystems), but I have custom ones too. If I want to move an icon by dragging it, ugly garbage is left on the screen where I move that icon. The garbage disappears if I click onto some of the unused part of the desktop though. For sure, it's not a show-stopper bug, but looks quite ugly. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: metacity 1:2.34.1-1ubuntu11 ProcVersionSignature: Ubuntu 3.2.0-21.34-generic-pae 3.2.13 Uname: Linux 3.2.0-21-generic-pae i686 ApportVersion: 2.0.1-0ubuntu2 Architecture: i386 Date: Thu Apr 12 17:54:13 2012 InstallationMedia: Ubuntu-Server 10.04.1 LTS Lucid Lynx - Release i386 (20100816.2) SourcePackage: metacity UpgradeStatus: Upgraded to precise on 2012-03-01 (41 days ago) ** Affects: metacity (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 precise -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to metacity in Ubuntu. https://bugs.launchpad.net/bugs/980013 Title: moving icons on the desktop leaves some garbage To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/metacity/+bug/980013/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 980013] Re: moving icons on the desktop leaves some garbage
-- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to metacity in Ubuntu. https://bugs.launchpad.net/bugs/980013 Title: moving icons on the desktop leaves some garbage To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/metacity/+bug/980013/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 971322] [NEW] Unity-2D/metacity window placement/move problems in precise
Public bug reported: I've upgraded oneiric to precise (32 bit). One annoying problem is the window placement/moving policy now. In oneiric this worked (I am using Unity-2D, so metacity, composing manager/effects are enabled) very well. If I open a new window, it will be placed stacked on existing window (eg if I open a new terminal (usually I have to open more of them), even if there is lots of free space on the workspace. So, I think metacity in oneiric tries to use available 'free' screen space, which is not true for oneiric. Another annoying thing is the window border resistance. In oneiric, if I move a window, there is need for a little push more action to be able to move window when border is at another window's border. It's a great help to align windows in a nice way. In precise, this does not work, or at least it behaves oddly: if I move a window towards another horizontally this _is_ this effect, however not at the border but _before_ it! There is a huge space, probably the same size as the Unity launcher bar, is it possible, that positions are miscalculated? I am using auto hide for Unity. There is similar problem vertically however the gap is smaller, and I have no idea if there is some relation of the size of the gap and any other thing. It's about half of the height of the top panel, for example. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: metacity 1:2.34.1-1ubuntu9 ProcVersionSignature: Ubuntu 3.2.0-21.34-generic-pae 3.2.13 Uname: Linux 3.2.0-21-generic-pae i686 ApportVersion: 2.0-0ubuntu2 Architecture: i386 Date: Mon Apr 2 09:05:42 2012 InstallationMedia: Ubuntu-Server 10.04.1 LTS Lucid Lynx - Release i386 (20100816.2) SourcePackage: metacity UpgradeStatus: Upgraded to precise on 2012-03-01 (31 days ago) ** Affects: metacity (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 precise -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to metacity in Ubuntu. https://bugs.launchpad.net/bugs/971322 Title: Unity-2D/metacity window placement/move problems in precise To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/metacity/+bug/971322/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 971322] Re: Unity-2D/metacity window placement/move problems in precise
-- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to metacity in Ubuntu. https://bugs.launchpad.net/bugs/971322 Title: Unity-2D/metacity window placement/move problems in precise To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/metacity/+bug/971322/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 971322] Re: Unity-2D/metacity window placement/move problems in precise
Also it seems workspace switcher does not support wrapping: ie if I am at the first workspace, using switch to workspace at the left would cause (in oneiric it works) to the last one and vice versa. This behaviour _is_ enabled, I've just checked gconf settings, but it does not work anyway. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to metacity in Ubuntu. https://bugs.launchpad.net/bugs/971322 Title: Unity-2D/metacity window placement/move problems in precise To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/metacity/+bug/971322/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 852485] Re: [oneiric] cannot login, failed to load session
Is it possible that it's not the bug of gnome-session (I was reported as)? Maybe it should be moved to the right package, at least deletion of /etc/X11/Xsession.d/20desktop-profiles_activateDesktopProfiles helped, and that file is part of pacakge desktop-profiles and rdepends on edubuntu-menueditor according to apt-cache. But that package exited in natty too before I upgraded (and I still has it on other natty systems without problem), so it should be some kind of regression. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-session in Ubuntu. https://bugs.launchpad.net/bugs/852485 Title: [oneiric] cannot login, failed to load session To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/852485/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 852485] Re: [oneiric] cannot login, failed to load session
Still some minor issues left, like missing icons (firefox etc), maybe that's the problem of bad XDG_DATA_DIRS. I wonder if I made misstake to always install meta packages for kubuntu, edubuntu, xubuntu, etc too, since as far as I can recall, that file you suggested to remove is part of edubuntu package, or something like that ... -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-session in Ubuntu. https://bugs.launchpad.net/bugs/852485 Title: [oneiric] cannot login, failed to load session To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/852485/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 852485] Re: [oneiric] cannot login, failed to load session
I would be surprised, if a specific bug like this is caused by a hardware failure, especially because I am using that notebook since months without a single problem (with previous versions of Ubuntu, too). Also, other DEs, like KDE seems to work nicely, with many resource hungry tasks (which usually triggers bugs like ones with disk I/O, memory or CPU). I've also tried to re-install packages you've mentioned but it did not help. Anyway, just to be sure, I will check it with memcheck at this evening. Also I am thinking to try to reinstall the system (it was an upgrade from natty) to see if it helps, if there is no further ideas to cure the problem; just I thought it can be useful to track this bug if others may have it too ... -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-session in Ubuntu. https://bugs.launchpad.net/bugs/852485 Title: [oneiric] cannot login, failed to load session To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/852485/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 852485] Re: [oneiric] cannot login, failed to load session
I've removed sabayon (dpkg --purge sabayon). I have even done a reboot then. However the problem remains. I've attached the whole .xsession- errors file (I've tested with a totally new and clean user). I've tested memory with memtest for a while at least, as I thought; no problem has been found. However there is one thing, I don't know if related or note, but here it is: I often see during package install/upgrade/etc: Processing triggers for man-db ... Processing triggers for hicolor-icon-theme ... Processing triggers for libglib2.0-0 ... Processing triggers for gconf2 ... Processing triggers for gnome-menus ... Processing triggers for bamfdaemon ... Rebuilding /usr/share/applications/bamf.index... Processing triggers for desktop-file-utils ... Processing triggers for shared-mime-info ... Unknown media type in type 'all/all' Unknown media type in type 'all/allfiles' Unknown media type in type 'uri/mms' Unknown media type in type 'uri/mmst' Unknown media type in type 'uri/mmsu' Unknown media type in type 'uri/pnm' Unknown media type in type 'uri/rtspt' Unknown media type in type 'uri/rtspu' Unknown media type in type 'interface/x-winamp-skin' Note that '/usr/share' is not in the search path set by the XDG_DATA_HOME and XDG_DATA_DIRS environment variables, so applications may not be able to find it until you set them. The directories currently searched are: - /root/.local/share - /usr/share/kde-plasma - - ** Attachment added: .xsession-errors https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/852485/+attachment/2535316/+files/.xsession-errors -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-session in Ubuntu. https://bugs.launchpad.net/bugs/852485 Title: [oneiric] cannot login, failed to load session To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/852485/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 852485] Re: [oneiric] cannot login, failed to load session
By the way, by google'ing a bit, I found something which seems to be a bit similar to my problem at least: http://bugs.debian.org/cgi- bin/bugreport.cgi?bug=633851 Also there was an article mentioning that all your gconf schemas have been unregistered for some reason and suggesting this: cd /usr/share/gconf/schemas/ sudo /usr/sbin/gconf-schemas --register *.schemas However this was a quite old post so I doubt it's my case (and btw, it hasn't worked anyway ...) ** Bug watch added: Debian Bug tracker #633851 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=633851 -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-session in Ubuntu. https://bugs.launchpad.net/bugs/852485 Title: [oneiric] cannot login, failed to load session To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/852485/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 852485] Re: [oneiric] cannot login, failed to load session
Just one thing (I don't know if it's a problem or not): on a natty system there is file: /usr/share/gconf/schemas/gnome-session.schemas However on my promlematic oneiric notebook is does not exist. However since they are different ubuntugnme releases, maybe it's not even a problem. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-session in Ubuntu. https://bugs.launchpad.net/bugs/852485 Title: [oneiric] cannot login, failed to load session To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/852485/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 852485] Re: [oneiric] cannot login, failed to load session
Command gsettings get org.gnome.desktop.session session says: No such schema 'org.gnome.desktop.session'. Setting envvar XDG_DATA_DIRS to /usr/share does not seem to help. The output of grep (with also the -n option) is attached. ** Attachment added: grep.output https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/852485/+attachment/2535512/+files/grep.output -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-session in Ubuntu. https://bugs.launchpad.net/bugs/852485 Title: [oneiric] cannot login, failed to load session To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/852485/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 852485] Re: [oneiric] cannot login, failed to load session
Wow! Yes. With removing (well, moving away to have a backup) I could log in. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-session in Ubuntu. https://bugs.launchpad.net/bugs/852485 Title: [oneiric] cannot login, failed to load session To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/852485/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 852485] Re: [oneiric] cannot login, failed to load session
@Anakin: hmm, but does it mean that oneiric will be released as stable that I can't even log in to the system? It sounds quite painfull -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-session in Ubuntu. https://bugs.launchpad.net/bugs/852485 Title: [oneiric] cannot login, failed to load session To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/852485/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 852485] Re: [oneiric] cannot login, failed to load session
I've reinstall the mentioned packages (apt-get --reinstall install ...) but still no success. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-session in Ubuntu. https://bugs.launchpad.net/bugs/852485 Title: [oneiric] cannot login, failed to load session To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/852485/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 852485] Re: [oneiric] cannot login, failed to load session
@Sebastien: thanks for your answer! gnome-session-bin: 3.2.0-0ubuntu2 gconf2: 3.2.0-0ubuntu1 libglib2 is not installed, not even an installable package exists with that name (according to apt-get install) Similar package name seems to be libglib2.0-0 , it's installed, and version is: 2.30.0-0ubuntu3 -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-session in Ubuntu. https://bugs.launchpad.net/bugs/852485 Title: [oneiric] cannot login, failed to load session To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/852485/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 852485] Re: [oneiric] cannot login, failed to load session
Sorry for the huge amount of comments from me, but I think this bug is simply a show-stopper, since system can't be used at all (well of course, if someone can run another kind of session than gnome ...). I try almost every day to upgrade the system and check the situation with oneiric, but still, the result is the same :( If there is some problem with my bug report (so you can't work with it too much) please note, and I try to help more to identify the problem. Thanks! -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-session in Ubuntu. https://bugs.launchpad.net/bugs/852485 Title: [oneiric] cannot login, failed to load session To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/852485/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 852485] Re: [oneiric] cannot login, failed to load session
If I try to run gnome-session by hand: lgb@orion:~$ gnome-session gnome-session[6343]: GLib-GIO-CRITICAL: Settings schema 'org.gnome.SessionManager' is not installed gnome-session[6343]: GLib-GIO-CRITICAL: Settings schema 'org.gnome.desktop.session' is not installed gnome-session[6343]: GLib-GIO-CRITICAL: Settings schema 'org.gnome.desktop.screensaver' is not installed gnome-session[6343]: GLib-GIO-CRITICAL: Settings schema 'org.gnome.desktop.lockdown' is not installed gnome-session[6343]: GLib-GIO-CRITICAL: g_settings_get_key_info: assertion `settings-priv-schema != NULL' failed gnome-session[6343]: GLib-GIO-CRITICAL: g_settings_get_key_info: assertion `settings-priv-schema != NULL' failed gnome-session[6343]: GLib-CRITICAL: g_variant_get_string: assertion `value != NULL' failed Segmentation fault (core dumped) -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-session in Ubuntu. https://bugs.launchpad.net/bugs/852485 Title: [oneiric] cannot login, failed to load session To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/852485/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 852485] Re: [oneiric] cannot login, failed to load session
lgb@orion:~$ gnome-session --version gnome-session 3.2.0 lgb@orion:~$ dpkg -S `which gnome-session` gnome-session-bin: /usr/bin/gnome-session lgb@orion:~$ dpkg -s gnome-session-bin Package: gnome-session-bin Status: install ok installed Priority: optional Section: gnome Installed-Size: 576 Maintainer: Ubuntu Developers ubuntu-devel-disc...@lists.ubuntu.com Architecture: i386 Source: gnome-session Version: 3.2.0-0ubuntu1 [...] -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-session in Ubuntu. https://bugs.launchpad.net/bugs/852485 Title: [oneiric] cannot login, failed to load session To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/852485/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 852485] Re: [oneiric] cannot login, failed to load session
Btw, Failed to summon the GConf demon. Is word demon is demon by will? Or should I interpret is as daemon? -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-session in Ubuntu. https://bugs.launchpad.net/bugs/852485 Title: [oneiric] cannot login, failed to load session To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/852485/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 852485] [NEW] [oneiric] cannot login, failed to load session
Public bug reported: I've upgraded to oneiric to test the new not-yet-ready version of ubuntu. However since then I cannot log in at the lightdm (btw I tried to use gdm too, the result is the same) screen. A window (without borders) appear that failed to load session ubuntu. The result is the same, if I try to use alternative options like Ubuntu 2D, Gnome, Gnome classic, Gnome without ubuntu specific, etc etc etc. Just the message is different (the session name in the message). Now I am writing from fluxbox WM, since it was able to load at least. If I try to launch eg gnome-terminal from a terminal in fluxbox, I get: lgb@orion:~$ gnome-terminal Failed to summon the GConf demon; exiting. Failed to activate configuration server: The name org.gnome.GConf was not provided by any .service files .xsession-errors file is attached. ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: gnome-session 3.1.91-0ubuntu2 ProcVersionSignature: Ubuntu 3.0.0-11.18-generic-pae 3.0.4 Uname: Linux 3.0.0-11-generic-pae i686 ApportVersion: 1.23-0ubuntu1 Architecture: i386 Date: Sat Sep 17 12:09:17 2011 InstallationMedia: Ubuntu 10.10 Maverick Meerkat - Release i386 (20101007) PackageArchitecture: all ProcEnviron: PATH=(custom, user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-session UpgradeStatus: Upgraded to oneiric on 2011-09-06 (10 days ago) ** Affects: gnome-session (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 oneiric -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-session in Ubuntu. https://bugs.launchpad.net/bugs/852485 Title: [oneiric] cannot login, failed to load session To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/852485/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 852485] Re: [oneiric] cannot login, failed to load session
** Attachment added: .xsession-erros file https://bugs.launchpad.net/bugs/852485/+attachment/2416290/+files/.xsession-errors -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-session in Ubuntu. https://bugs.launchpad.net/bugs/852485 Title: [oneiric] cannot login, failed to load session To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/852485/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 852485] Re: [oneiric] cannot login, failed to load session
Btw, I also created a new user, and tested with that, to be sure that no user config files etc can cause problems, but the result was the same. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-session in Ubuntu. https://bugs.launchpad.net/bugs/852485 Title: [oneiric] cannot login, failed to load session To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/852485/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 852485] Re: [oneiric] cannot login, failed to load session
Interesting: running X (with another DE/WM) I got this: lgb@orion:~$ gconftool --dump / gconfentryfile entrylist base=/ Failure listing entries in `/': Failed to activate configuration server: The name org.gnome.GConf was not provided by any .service files /entrylist /gconfentryfile The odd thing: if I type this very same command into a shell running on console (so without X) it gives normal result - as far as I see that a big XML structure is good :) -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-session in Ubuntu. https://bugs.launchpad.net/bugs/852485 Title: [oneiric] cannot login, failed to load session To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/852485/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 665548] Re: changing workspaces is very slow in case of big terminal windows
Yes, I have the issue with natty too. However, it's not always the case (as it was not before either), usually it does not happen after reboot and then it starts to happen after a while. It's annoying since a big terminal window I often use (btw: it can be a case with more terminal windows on the same workspace as well: it seems somehow the sum of the surface counts??) it can be 4-5 seconds to switch workspace. I am not using unity/compiz/desktop effects etc all, but classic desktop (without compiz) but metacity's internal composite support is enabled though! -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to vte in Ubuntu. https://bugs.launchpad.net/bugs/665548 Title: changing workspaces is very slow in case of big terminal windows To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/vte/+bug/665548/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 639913] Re: gnome-settings-daemon random crash at session start (xorg badmatch error)
I have this problem too (bug 696455 now it's a duplicate of this bug) but I often meet this one not only at session start, but even randomly sometimes. It's quite frequent issue for me, if I kill indicator applet by the way (just I noticed it can trigger this problem more frequently, I got this otherwise too!). Starting gnome-appearance-properties fixes the problem, because it restarts gnome-settings-daemon (afaik). In .xession-errors The program 'gnome-settings-daemon' received an X Window System error. This probably reflects a bug in the program. The error was 'BadMatch (invalid parameter attributes)'. (Details: serial 1365 error_code 8 request_code 3 minor_code 0) (Note to programmers: normally, X errors are reported asynchronously; that is, you will receive the error a while after causing it. To debug your program, run it with the --sync command line option to change this behavior. You can then get a meaningful backtrace from your debugger if you break on the gdk_x_error() function.) In kernel log: [1206298.610775] gnome-settings-[2102]: segfault at 535f4d57 ip 00bc5f4b sp bfbd90a0 error 4 in libgtk-x11-2.0.so.0.2200.0[ad1000+3c8000] I have this problem in three different machines, one of them is fresh install, the others are upgraded since several ubuntu releases. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-settings-daemon in ubuntu. https://bugs.launchpad.net/bugs/639913 Title: gnome-settings-daemon random crash at session start (xorg badmatch error) -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 696455] Re: GTK/gnome applications/desktop loses the GTK theme sometime
Also in kernel log: [1206298.610775] gnome-settings-[2102]: segfault at 535f4d57 ip 00bc5f4b sp bfbd90a0 error 4 in libgtk-x11-2.0.so.0.2200.0[ad1000+3c8000] -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-settings-daemon in ubuntu. https://bugs.launchpad.net/bugs/696455 Title: GTK/gnome applications/desktop loses the GTK theme sometime -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 696455] [NEW] GTK/gnome applications/desktop loses the GTK theme sometime
Public bug reported: First of all, I am sorry that I may send this bug report against the wrong package. With Ubuntu 10.10 (actually on two different machines: one of them is a notebook with fresh install, the other is upgraded since the stone age but it is also a 10.10 32 bit version now) sometimes I have the experience that gtk/gnome apps loses the theme. It means that things appears in a default themeless GTK way. On the notebook (the new install) let's say 2 startups from 10 (in average) results the themeless appearance after logging in (including the gnome panel). On the other machine, if some application which used the panel exists (or killed) there is a chance that theme switches back to the themeless state without my will. In both cases, if I start application gnome- appearance-properties, everything returns into the correct themed appearance even without doing anything in gnome-appearance-properties just starting it, and CTRL-C before its window appears (I run it from terminal window) helps. I have no idea what can cause this really annoying bug. Thanks in advance, if you have any advice to avoid this. ProblemType: Bug DistroRelease: Ubuntu 10.10 Package: libgtk2.0-0 2.22.0-0ubuntu1 ProcVersionSignature: Ubuntu 2.6.35-24.42-generic-pae 2.6.35.8 Uname: Linux 2.6.35-24-generic-pae i686 NonfreeKernelModules: fglrx Architecture: i386 Date: Sun Jan 2 12:22:08 2011 InstallationMedia: Ubuntu 10.10 Maverick Meerkat - Release i386 (20101007) ProcEnviron: PATH=(custom, user) LANG=en_US.utf8 SHELL=/bin/bash SourcePackage: gtk+2.0 ** Affects: gnome-settings-daemon (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 maverick -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gtk+2.0 in ubuntu. https://bugs.launchpad.net/bugs/696455 Title: GTK/gnome applications/desktop loses the GTK theme sometime -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 696455] Re: GTK/gnome applications/desktop loses the GTK theme sometime
-- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gtk+2.0 in ubuntu. https://bugs.launchpad.net/bugs/696455 Title: GTK/gnome applications/desktop loses the GTK theme sometime -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 696455] Re: GTK/gnome applications/desktop loses the GTK theme sometime
Hmm, I found this in .xsession-erros file: ** Message: applet now embedded in the notification area The program 'gnome-settings-daemon' received an X Window System error. This probably reflects a bug in the program. The error was 'BadMatch (invalid parameter attributes)'. (Details: serial 1365 error_code 8 request_code 3 minor_code 0) (Note to programmers: normally, X errors are reported asynchronously; that is, you will receive the error a while after causing it. To debug your program, run it with the --sync command line option to change this behavior. You can then get a meaningful backtrace from your debugger if you break on the gdk_x_error() function.) Can it cause the problem? Is it a gnome-setting-daemon bug then? ** Package changed: gtk+2.0 (Ubuntu) = gnome-settings-daemon (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-settings-daemon in ubuntu. https://bugs.launchpad.net/bugs/696455 Title: GTK/gnome applications/desktop loses the GTK theme sometime -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 665548] [NEW] changing workspaces is very slow in case of big terminal windows
Public bug reported: First, sorry if this bug is not vte related, maybe it's more gtk than vte? I can only reproduce this problem with gnome-terminal and xfce4-terminal but not with xterm for example. The common thing between xfce4-terminal and gnome-terminal is using libvte as well, that's the reason I try to bugreport here. If I was wrong, please move my report to the right place, thanks! The bug now: I'm using multiple workspaces (desktops) under gnome/metacity with Ubuntu maverick 32bit OS. I have this problem on two machines, but it's hard to tell when, it seems if the problem begins it remains, but I don't know what can cause the beginning of the problem. If I change workspaces, and I switch onto a workspace which have a large enough terminal window (not a standard 80x24 but a larger, like 130x90 or even full screen) the change is _very_ slow, sometimes my X session is frozen for 4-5 seconds! Within that time I see the old workspace (but as frozen, though I can move the mouse cursor) before the new appears. It seems I can have even dozens of terminal windows without a problem, if none of them is large enough window to trigger the problem. This is a very annoying problem for me, because I'm using terminals and multiple workspaces quite heavily, but that delay is awful especially if I only want a quick look at a terminal then I would switch back to another one on another workspace. As I've already told, it seems xterm is not affected only gtk/vte based terminals. I am not using compiz at all (though I've activated the internal compositing support of metacity wia gconf). The problem exists even with semi transparent and non- transparent (static black) background configured for gnome-terminal. ProblemType: Bug DistroRelease: Ubuntu 10.10 Package: libvte9 1:0.26.0-0ubuntu2 ProcVersionSignature: Ubuntu 2.6.35-22.35-generic 2.6.35.4 Uname: Linux 2.6.35-22-generic i686 NonfreeKernelModules: nvidia Architecture: i386 Date: Sat Oct 23 14:48:51 2010 EcryptfsInUse: Yes ProcEnviron: LANGUAGE=en_US:en PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: vte ** Affects: vte (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 maverick ubuntu-une -- changing workspaces is very slow in case of big terminal windows https://bugs.launchpad.net/bugs/665548 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to vte in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 665548] Re: changing workspaces is very slow in case of big terminal windows
-- changing workspaces is very slow in case of big terminal windows https://bugs.launchpad.net/bugs/665548 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to vte in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 625793] Re: Regression: Multiple Keyboard Layouts unusable: continuously changes layout + 100% CPU usage [updated]
@yurik81: I always had that option unchecked. I've never used my system with that option. Still I have got the bug! So it's not even a workaround for me, since I have the bug with that option unchecked you mentioned ... -- Regression: Multiple Keyboard Layouts unusable: continuously changes layout + 100% CPU usage [updated] https://bugs.launchpad.net/bugs/625793 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-settings-daemon in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 625793] Re: Keyboard layout automatically changes + 100% CPU usage [updated]
@Marat Dyatko: Hmmm, well I am not an expert about Xorg and kbd handling etc, but this was my first guess when I met this bug, since as I've commented according to output of command xev I got non-stopping output of key events even if I don't touch the kbd/mouse or anything (during the bug I mean). I had the idea that the problem that kbd layer (whatever it is, or how it should be called) reports I am pressing scroll-lock (the layout changer key for me), so does the system switches it for me then. The problem that I don't press the scoll-lock for real (only once) just it is stucked for some reason. If my guess is true, then bugs like this with other keys (even shift, and not related the layouts as all!) is about the key stucking problem, and not depend strictly on the layout problem. So is it possible that we try to find the solution of the bug behind the layout changes etc, when the real problem is a more general one about the kbd handling in some way? Btw, as I've commented, xev reports endless messages during the triggered bug like: PropertyNotify event, serial 30, synthetic NO, window 0x601, atom 0x174 (XKLAVIER_STATE), time 11886812, state PropertyNewValue -- Keyboard layout automatically changes + 100% CPU usage [updated] https://bugs.launchpad.net/bugs/625793 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-settings-daemon in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 625793] Re: Keyboard layout automatically changes + 100% CPU usage [updated]
And btw it's very easy to trigger for me, only one keypress of scroll lock (configured to switch between my four kbd layouts) and it begins ... -- Keyboard layout automatically changes + 100% CPU usage [updated] https://bugs.launchpad.net/bugs/625793 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-settings-daemon in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 625793] Re: Keyboard layout automatically changes + 100% CPU usage [updated]
@Karl Lattimer: I haven't got this bug at the GDM screen, but later when I'm using (typically web browser, like chromium) to write mail in a non- English language which requires one of my non-US layouts. Usually then if I press scroll lock (it's configured to switch layout) the problem occures: layouts switches automatically like crazy, scroll lock led flashes rapidly (it's configured to show the non-primary layout is active, I have four btw), and if I press a key it produces random character each time, I guess based on the fact which was the actual layout at the very moment when I press it. So even pressing the same key for long, produces an odd sequence of different characters. But, please note that the kbd indicator applet itself does _NOT_ change, ie it says I am using US layout even if it's not true! Killing g-s-d seems to fix the problem though ... -- Keyboard layout automatically changes + 100% CPU usage [updated] https://bugs.launchpad.net/bugs/625793 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-settings-daemon in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 625793] Re: Keyboard layout automatically changes + 100% CPU usage [updated]
Doesn't it help what I have commented? That even xev outputs a huge amount of flood of PropertyNotify event, serial 30, synthetic NO, window 0x601, atom 0x174 (XKLAVIER_STATE), time 11886812, state PropertyNewValue lines, even if I don't touch keyboard, mouse or anything. -- Keyboard layout automatically changes + 100% CPU usage [updated] https://bugs.launchpad.net/bugs/625793 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-settings-daemon in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 625793] Re: Keyboard layout automatically changes + 100% CPU usage [updated]
@Sergey Klimov: Not just cyrillic ... I am using US layout as primary but also layout for my native language (Hungarian), and two languages I am learning (Finnish,Norwegian). I think it's not depend on cyrillic or not, but simply the fact that you have any layouts configured other than only one, so you can switch between them. ALSO I am not sure if it's the problem but some developer may have check out the problem I've reported with xev that it can help the source of the problem for example. Again the output of xev in case of problem (endless loop of these): PropertyNotify event, serial 30, synthetic NO, window 0x601, atom 0x174 (XKLAVIER_STATE), time 11886756, state PropertyNewValue Can someone else to run xev in a terminal window too at the time when the problem occures? Maybe it can be useful to find the problem, maybe not :) -- Keyboard layout automatically changes + 100% CPU usage [updated] https://bugs.launchpad.net/bugs/625793 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-settings-daemon in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 625793] Re: Keyboard layout automatically changes + 100% CPU usage [updated]
I can agree, just checked it out: killing process /usr/lib/gnome- settings-daemon/gnome-settings-daemon fixes the issue, cycling of layouts stops, xev output stops (no more XKLAVIER_STATE messages without end just other events like my mouse movements etc). After relaunching g-s-d by hand everything is normal. And what is odd: it seems (at least now) that the bug is no longer exists after killing-relaunching g-s-d. (until the next reboot or logout/login, etc). -- Keyboard layout automatically changes + 100% CPU usage [updated] https://bugs.launchpad.net/bugs/625793 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-settings-daemon in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 625793] Re: Keyboard layout automatically changes + 100% CPU usage [updated]
I have/had Use different layouts for different windows disabled since years, even now. Anyway I still have the problem! I have never used any system with different layouts for different windows, it's confusing in my opinion. -- Keyboard layout automatically changes + 100% CPU usage [updated] https://bugs.launchpad.net/bugs/625793 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-settings-daemon in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 625793] Re: Keyboard layout automatically changes + 100% CPU usage [updated]
@Joe_Bishop I agree, this bug renders ubuntu deskop simply unusable for anyone who has more than one kbd layout. -- Keyboard layout automatically changes + 100% CPU usage [updated] https://bugs.launchpad.net/bugs/625793 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-settings-daemon in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 625793] Re: Keyboard layout automatically changes
As I've reported in bug #636619 It happens for me too. It's still there, I've just checked. It's triggered by switching layout. After that, it goes crazy and layouts are switched cycling between my previously configured ones rapidly. Scroll lock led flashes as well (it's configured to show the non-primary layout). I can't even type since pressing the same key generates random character based on the fact which layout was active at the moment when I pressed the key. xev reports things like this without stopping (even without toucing the keyboard or the mouse after I managed to launch xev in a terminal window): PropertyNotify event, serial 30, synthetic NO, window 0x601, atom 0x174 (XKLAVIER_STATE), time 11886504, state PropertyNewValue PropertyNotify event, serial 30, synthetic NO, window 0x601, atom 0x174 (XKLAVIER_STATE), time 11886505, state PropertyNewValue PropertyNotify event, serial 30, synthetic NO, window 0x601, atom 0x174 (XKLAVIER_STATE), time 11886562, state PropertyNewValue PropertyNotify event, serial 30, synthetic NO, window 0x601, atom 0x174 (XKLAVIER_STATE), time 11886634, state PropertyNewValue PropertyNotify event, serial 30, synthetic NO, window 0x601, atom 0x174 (XKLAVIER_STATE), time 11886635, state PropertyNewValue PropertyNotify event, serial 30, synthetic NO, window 0x601, atom 0x174 (XKLAVIER_STATE), time 11886694, state PropertyNewValue PropertyNotify event, serial 30, synthetic NO, window 0x601, atom 0x174 (XKLAVIER_STATE), time 11886695, state PropertyNewValue PropertyNotify event, serial 30, synthetic NO, window 0x601, atom 0x174 (XKLAVIER_STATE), time 11886756, state PropertyNewValue PropertyNotify event, serial 30, synthetic NO, window 0x601, atom 0x174 (XKLAVIER_STATE), time 11886811, state PropertyNewValue PropertyNotify event, serial 30, synthetic NO, window 0x601, atom 0x174 (XKLAVIER_STATE), time 11886812, state PropertyNewValue My system was upgraded from the previous version of Ubuntu (lucid lynx) I am wondering if it can cause the problem and it works with a 'clean' install (ie: new home directory with gnome/etc settings created by the current development version of ubuntu). I have four layouts configured, one of them (USA) is the primary, the others are configured to be signaled by the scoll lock led, and I switch layouts by key scroll lock. -- Keyboard layout automatically changes https://bugs.launchpad.net/bugs/625793 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-settings-daemon in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 424435] Re: Cannot be logged in to gnome desktop after upgrading to karmic alpha5
Now I have this problem with fresh lucid install (installed from beta iso image from ubuntu.com). After the installation everything worked. After another reboot logging in at the gdm screen I got only a background, no panel, etc, whatsoever. From text console I've issued xhost + command and then DISPLAY=:0 xterm so I got an xterm window at least after change VT back to the X. Then I managed to launch gnome- panel and metacity for myself, however nautilus exits, maybe that caused the problem, that gnome login process hangs and I can't get anything but some background when gnome session is about launching nautilus? -- Cannot be logged in to gnome desktop after upgrading to karmic alpha5 https://bugs.launchpad.net/bugs/424435 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-session in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 551124] Re: python-gnome2-extras not installable
It affects me too. miro (from the site directly) requires this package but cannot be installed: r...@oxygene:~# apt-get install python-gnome2-extras Reading package lists... Done Building dependency tree Reading state information... Done Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: python-gnome2-extras: Depends: python-gtkhtml2 (= 2.25.3-3ubuntu1) but 2.25.3-4.1ubuntu1 is to be installed Depends: python-gtkmozembed (= 2.25.3-3ubuntu1) but 2.25.3-4.1ubuntu3 is to be installed Depends: python-eggtrayicon (= 2.25.3-3ubuntu1) but 2.25.3-4.1ubuntu3 is to be installed Depends: python-gtkspell (= 2.25.3-3ubuntu1) but 2.25.3-4.1ubuntu3 is to be installed Depends: python-gksu2 (= 2.25.3-3ubuntu1) but 2.25.3-4.1ubuntu3 is to be installed Depends: python-gdl (= 2.25.3-3ubuntu1) but 2.25.3-4.1ubuntu3 is to be installed Depends: python-gda (= 2.25.3-3ubuntu1) but 2.25.3-4.1ubuntu3 is to be installed E: Broken packages r...@oxygene:~# apt-cache show python-gnome2-extras Package: python-gnome2-extras Priority: optional Section: universe/python Installed-Size: 296 Maintainer: Ubuntu Desktop Team ubuntu-desk...@lists.ubuntu.com Original-Maintainer: Sebastien Bacher seb...@debian.org Architecture: i386 Source: gnome-python-extras Version: 2.25.3-3ubuntu1 Replaces: python2.2-gnome2 ( 1.99.16-5), python2.3-gnome2 ( 2.9.1), python2.3-gnome2-extras, python2.4-gnome2-extras Depends: libart-2.0-2 (= 2.3.18), libatk1.0-0 (= 1.20.0), libbonobo2-0 (= 2.15.0), libbonoboui2-0 (= 2.15.1), libc6 (= 2.4), libcairo2 (= 1.2.4), libfontconfig1 (= 2.4.0), libfreetype6 (= 2.2.1), libgconf2-4 (= 2.23.2), libglib2.0-0 (= 2.16.0), libgnome2-0 (= 2.17.3), libgnomecanvas2-0 (= 2.11.1), libgnomeui-0 (= 2.22.0), libgnomevfs2-0 (= 1:2.17.90), libgtk2.0-0 (= 2.8.0), libice6 (= 1:1.0.0), liborbit2 (= 1:2.14.10), libpango1.0-0 (= 1.14.0), libpopt0 (= 1.14), libsm6, zlib1g (= 1:1.1.4), python ( 2.7), python (= 2.5), python-support (= 0.90.0), python-gtk2, python-pyorbit, python-gtkhtml2 (= 2.25.3-3ubuntu1), python-gtkmozembed (= 2.25.3-3ubuntu1), python-eggtrayicon (= 2.25.3-3ubuntu1), python-gtkspell (= 2.25.3-3ubuntu1), python-gksu2 (= 2.25.3-3ubuntu1), python-gdl (= 2.25.3-3ubuntu1), python-gda (= 2.25.3-3ubuntu1) Conflicts: python2.2-gnome2 ( 1.99.16-5), python2.3-gnome2 ( 2.9.1), python2.3-gnome2-extras, python2.4-gnome2-extras Filename: pool/universe/g/gnome-python-extras/python-gnome2-extras_2.25.3-3ubuntu1_i386.deb Size: 90770 MD5sum: e2f1a9e6eab0dba2e3f3004782b61d22 SHA1: babb5fecbc90e9ceb039784b299b4cdf1e024110 SHA256: a3037083be8ce7ddcf47c3b7757cf69b81b7d45d94e5b566aea7d10eb4478e4c Description: Extra Python bindings for the GNOME desktop environment This package contains bindings for GNOME libraries that are not part of the official GNOME release. They will help writing programs in Python using these libraries. . This package is now mostly empty, and programs using these bindings should depend on the individual packages instead. You can safely remove it from your system. Homepage: http://www.pygtk.org/ Python-Version: 2.5, 2.6 Bugs: https://bugs.launchpad.net/ubuntu/+filebug Origin: Ubuntu r...@oxygene:~# lsb_release -a LSB Version: core-2.0-ia32:core-2.0-noarch:core-3.0-ia32:core-3.0-noarch:core-3.1-ia32:core-3.1-noarch:core-3.2-ia32:core-3.2-noarch:core-4.0-ia32:core-4.0-noarch:cxx-3.0-ia32:cxx-3.0-noarch:cxx-3.1-ia32:cxx-3.1-noarch:cxx-3.2-ia32:cxx-3.2-noarch:cxx-4.0-ia32:cxx-4.0-noarch:desktop-3.1-ia32:desktop-3.1-noarch:desktop-3.2-ia32:desktop-3.2-noarch:desktop-4.0-ia32:desktop-4.0-noarch:graphics-2.0-ia32:graphics-2.0-noarch:graphics-3.0-ia32:graphics-3.0-noarch:graphics-3.1-ia32:graphics-3.1-noarch:graphics-3.2-ia32:graphics-3.2-noarch:graphics-4.0-ia32:graphics-4.0-noarch:languages-3.2-ia32:languages-3.2-noarch:languages-4.0-ia32:languages-4.0-noarch:multimedia-3.2-ia32:multimedia-3.2-noarch:multimedia-4.0-ia32:multimedia-4.0-noarch:printing-3.2-ia32:printing-3.2-noarch:printing-4.0-ia32:printing-4.0-noarch:qt4-3.1-ia32:qt4-3.1-noarch Distributor ID: Ubuntu Description:Ubuntu lucid (development branch) Release:10.04 Codename: lucid r...@oxygene:~# uname -a Linux oxygene 2.6.32-19-generic #28-Ubuntu SMP Wed Mar 31 17:46:20 UTC 2010 i686 GNU/Linux ** Changed in: gnome-python-extras (Ubuntu) Status: New = Confirmed -- python-gnome2-extras not installable https://bugs.launchpad.net/bugs/551124 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-python-extras in ubuntu.
[Bug 513346] Re: MSN connection does not work: Network error
Information: I've just upgraded to lucid, and it seems it is not affected. But I had problems with karmic and even karmic with the PPA you've suggested to try. -- MSN connection does not work: Network error https://bugs.launchpad.net/bugs/513346 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 513346] Re: MSN connection does not work: Network error
I reported it here: https://bugzilla.gnome.org/show_bug.cgi?id=608418 ** Bug watch added: GNOME Bug Tracker #608418 https://bugzilla.gnome.org/show_bug.cgi?id=608418 -- MSN connection does not work: Network error https://bugs.launchpad.net/bugs/513346 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 513346] Re: MSN connection does not work: Network error
Is there an easy way to do it without messing up my karmic? I mean, I can compile empathy 2.29.6 for sure, if it compiles without too much dependency problems (I have karmic) and no other stuffs like telepathy and another 1000 packages needed to install and/or compile :) Or is it ok to test from a live cd for example using an alpha release of lucid? -- MSN connection does not work: Network error https://bugs.launchpad.net/bugs/513346 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 513346] Re: MSN connection does not work: Network error
Aaaa, PPA, ok thanks. I've tried, the result is same, just as I can see, the UI is a bit redesigned :) But it says the same: network error. If I open the account settings dialog, I see a red area saying: Disconnected - Network Error. What is a bit odd, that in settings (advanced) I see: Server: messenger.hotmail.com Port: 0 Port 0 sounds a bit odd for me, but it seems it's the default, since I've even tried to re-create the MSN account inside empathy now. And it seems I can't even edit it, well I can (I've tried 1863, afaik it should be the right port number), but after closing the window it says port 0 again. Or is it normal, just some UI glitch? Anyway I've still the same problem even the 2.29.x stuff from the ppa, it seems. -- MSN connection does not work: Network error https://bugs.launchpad.net/bugs/513346 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 513346] Re: MSN connection does not work: Network error
I would try, but how? That's the point I wanted to tell: if I modify the port to 1863, the change on UI seems not to be used at all, network error again, and if I reopen the account window I can see that port number is set to zero again. So it seems I can't modify it (well at least I can, but it isn't used or even stored it seems, since zero is displayed again if I reopen the account window or moving to another account and then back to the MSN's). -- MSN connection does not work: Network error https://bugs.launchpad.net/bugs/513346 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 513346] [NEW] MSN connection does not work: Network error
Public bug reported: Binary package hint: empathy Using MSN with empathy is almost impossible since most of the time it reports Network error. Please note, that I have no problem with other IM clients using the same user. Also, there can't be major network problem: I am using 1Gbit LAN connection to the ISP's backbone network, also as I've mentioned, no problem with other clients. Also it's a bit misleading to show edit contact window, since user can't edit any setting which can solve this problem, I think :) It's up-to-date ubuntu karmic running on 32 bit x86 platform. ProblemType: Bug Architecture: i386 Date: Wed Jan 27 17:32:02 2010 DistroRelease: Ubuntu 9.10 NonfreeKernelModules: nvidia Package: empathy 2.28.1.1-0ubuntu1 ProcEnviron: LANGUAGE=en_US.UTF-8 PATH=(custom, user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 2.6.31-16.52-generic SourcePackage: empathy Uname: Linux 2.6.31-16-generic i686 ** Affects: empathy (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 -- MSN connection does not work: Network error https://bugs.launchpad.net/bugs/513346 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to empathy in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 513346] Re: MSN connection does not work: Network error
** Attachment added: Dependencies.txt http://launchpadlibrarian.net/38453596/Dependencies.txt ** Attachment added: XsessionErrors.txt http://launchpadlibrarian.net/38453597/XsessionErrors.txt -- MSN connection does not work: Network error https://bugs.launchpad.net/bugs/513346 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to empathy in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 467972] Re: metacity assert failure: metacity:ERROR:core/bell.c:211:bell_flash_window_frame: assertion failed: (window-frame != NULL)
The same for me! I'm using chromium, not chrome, but the problem is very similar, I can see that assert message in .xsession-errors too. It happens almost every day once or more. I'm using Ubuntu 9.10 on 32 bit. I think bug 434389 is quite similar to this one, though. metacity: Installed: 1:2.28.0-0ubuntu1 Candidate: 1:2.28.0-0ubuntu1 Version table: *** 1:2.28.0-0ubuntu1 0 500 http://archive.ubuntu.com karmic/main Packages 100 /var/lib/dpkg/status chromium-browser: Installed: 4.0.246.0~svn20091112r31785-0ubuntu1~ucd1 Candidate: 4.0.246.0~svn20091112r31785-0ubuntu1~ucd1 Version table: *** 4.0.246.0~svn20091112r31785-0ubuntu1~ucd1 0 500 http://ppa.launchpad.net karmic/main Packages 100 /var/lib/dpkg/status -- metacity assert failure: metacity:ERROR:core/bell.c:211:bell_flash_window_frame: assertion failed: (window-frame != NULL) https://bugs.launchpad.net/bugs/467972 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to metacity in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 434389] Re: metacity assert failure: metacity:ERROR:core/bell.c:211:bell_flash_window_frame: assertion failed: (window-frame != NULL)
I also have this problem when using chromium, and I found another similar report: bug 467972 where I also commented the situation with more information included! -- metacity assert failure: metacity:ERROR:core/bell.c:211:bell_flash_window_frame: assertion failed: (window-frame != NULL) https://bugs.launchpad.net/bugs/434389 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to metacity in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 467972] Re: metacity assert failure: metacity:ERROR:core/bell.c:211:bell_flash_window_frame: assertion failed: (window-frame != NULL)
Maybe the problem, that Chromium (and also Chrome) does not have window border/decoration (by window manager) by default? :) ** Changed in: metacity (Ubuntu) Status: New = Confirmed -- metacity assert failure: metacity:ERROR:core/bell.c:211:bell_flash_window_frame: assertion failed: (window-frame != NULL) https://bugs.launchpad.net/bugs/467972 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to metacity in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 467972] Re: metacity assert failure: metacity:ERROR:core/bell.c:211:bell_flash_window_frame: assertion failed: (window-frame != NULL)
http://code.google.com/p/chromium/issues/detail?id=27654 chrome:3337): Gdk-WARNING **: XID collision, trouble ahead However I don't know it's chromium or metacity bug then, metacity shouldn't crash by a client though, at least imho. ** Bug watch added: code.google.com/p/chromium/issues #27654 http://code.google.com/p/chromium/issues/detail?id=27654 -- metacity assert failure: metacity:ERROR:core/bell.c:211:bell_flash_window_frame: assertion failed: (window-frame != NULL) https://bugs.launchpad.net/bugs/467972 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to metacity in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 290204] Re: Annoying beep on shutdown using System - Shut down...
Nice, but I want to use my PC speaker to beep (like from scripts, to make some alarm even without soundcard), so blacklisting the kernel module about pc speaker is not so nice idea for me. I only want not to have beep on shutdown, because it's a useless idea: if I want to shut the machine down, of course I know it will happen, completly pointless to generate beeps. Also note, that sometimes not even one beep but multiple ones are generated on shutdown (maybe this is not a problem anymore, I haven't noticed it since a while, I have to admit ...). -- Annoying beep on shutdown using System - Shut down... https://bugs.launchpad.net/bugs/290204 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-session in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 438046] Re: Showing binary data in gnome-terminal makes it crash
** Attachment added: _usr_bin_gnome-terminal.1000.crash.gz http://launchpadlibrarian.net/32591310/_usr_bin_gnome-terminal.1000.crash.gz -- Showing binary data in gnome-terminal makes it crash https://bugs.launchpad.net/bugs/438046 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-terminal in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 438046] [NEW] Showing binary data in gnome-terminal makes it crash
Public bug reported: Binary package hint: gnome-terminal If I make something in gnome-terminal to display binary data (by coincidence), all the gnome-terminal windows disappears, which is quite annoying because of the work in other windows. I know that it's not nice to try to display binary data as text, but gnome-terminal should not crash at least (and it did not before). A simple cat /bin/ls seems to be able to reproduce the problem. _usr_bin_gnome-terminal.1000.crash is attached in gzip'ped form from directory /var/crash gnome-terminal: Installed: 2.28.0-0ubuntu1 Candidate: 2.28.0-0ubuntu1 Version table: *** 2.28.0-0ubuntu1 0 500 http://archive.ubuntu.com karmic/main Packages 100 /var/lib/dpkg/status ** Affects: gnome-terminal (Ubuntu) Importance: Undecided Status: New -- Showing binary data in gnome-terminal makes it crash https://bugs.launchpad.net/bugs/438046 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-terminal in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 435367] Re: gnome-terminal assert failure: Vte:ERROR:/build/buildd/vte-0.22.0/./src/vtestream-file.h:30:_xread: assertion failed: (fd || !len)
I can reproduce it too. Cat'ting for example /bin/ls by mistake make all gnome-terminal windows disappears which caused major problem for me, since I have dozens of terminals open usually ... It seems some random binary 'garbage' makes gnome-terminal to crash ... For me, cat /bin/ls can trigger the bug all the time. -- gnome-terminal assert failure: Vte:ERROR:/build/buildd/vte-0.22.0/./src/vtestream-file.h:30:_xread: assertion failed: (fd || !len) https://bugs.launchpad.net/bugs/435367 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-terminal in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 424435] Re: Cannot be logged in to gnome desktop after upgrading to karmic alpha5
Sorry, I was not at the machine for a while, now I updated to the system to the latest, and it seems thsi bug does not affect me any more, so I couldn't reproduce it. I guess some upgrade has solved the problem. Thanks for the patience! -- Cannot be logged in to gnome desktop after upgrading to karmic alpha5 https://bugs.launchpad.net/bugs/424435 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-session in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 429231] Re: Pidgin does not start, problem with /usr/lib/gstreamer-0.10/libgstlibvisual.so
The new gstreamer0.10-plugins-base (or the new pidgin package??) seems to solve the problem. pidgin: Installed: 1:2.6.2-1ubuntu3 Candidate: 1:2.6.2-1ubuntu3 Version table: *** 1:2.6.2-1ubuntu3 0 500 http://archive.ubuntu.com karmic/main Packages 100 /var/lib/dpkg/status 1:2.6.1-1ubuntu0~pidgin1.9.10 0 500 http://ppa.launchpad.net karmic/main Packages gstreamer0.10-plugins-base: Installed: 0.10.24.2-2 Candidate: 0.10.24.2-2 Version table: *** 0.10.24.2-2 0 500 http://archive.ubuntu.com karmic/main Packages 100 /var/lib/dpkg/status -- Pidgin does not start, problem with /usr/lib/gstreamer-0.10/libgstlibvisual.so https://bugs.launchpad.net/bugs/429231 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gst-plugins-base0.10 in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 425736] Re: nautilus segfaults
I commented it at gnome bugzilla. As I wrote there too, the interesting part, that nautilus behaves differently every time, this directory not icon view model does not happen always (each time I try to execute nautilus). Also it does not crash using valgrind it seems. Also sometimes I got other messages too, like these: nautilus:25733): GLib-CRITICAL **: g_thread_join: assertion `thread' failed (nautilus:25733): Eel-WARNING **: nautilus-directory.c: directories hash table still has 6 elements at quit time -- nautilus segfaults https://bugs.launchpad.net/bugs/425736 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 424435] Re: Cannot be logged in to gnome desktop after upgrading to karmic alpha5
I managed to start gnome components manually from an xterm (gnome- session, gnome-panel, metacity, nautilus) so it seems it works this way (just gnome-session is not enough, maybe it stucks somewhere and that's the reason it does not work?), but nautilus segfaults every time (but maybe it's another bug). -- Cannot be logged in to gnome desktop after upgrading to karmic alpha5 https://bugs.launchpad.net/bugs/424435 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-session in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 425736] [NEW] [karmic alpha 5] nautilus segfaults
Public bug reported: Binary package hint: nautilus Upgraded system from jaunty to karmic alpha 5. Gnome does not work anymore (no panel, etc shows up just my custom background), I've reported this bug as bug #424435 but I managed to launch gnome-panel, metacity, etc by hand from an xterm. However nautilus segfaults all the time just after I start it: Initializing nautilus-open-terminal extension ** Message: Initializing gksu extension... ** (nautilus:15448): WARNING **: No marshaller for signature of signal 'UploadFinished' ** (nautilus:15448): WARNING **: No marshaller for signature of signal 'DownloadFinished' Initializing nautilus-gdu extension Initializing nautilus-image-converter extension Sense key: 0x70 0x00 0x02 0x00 0x00 0x00 0x00 0x0a 0x00 0x00 0x00 0x00 0x3a 0x00 0x00 0x00 0x00 0x00 0x00 *** glibc detected *** nautilus: double free or corruption (fasttop): 0x0a23ce70 *** === Backtrace: = /lib/tls/i686/cmov/libc.so.6[0x365f091] /lib/tls/i686/cmov/libc.so.6[0x3660792] /lib/tls/i686/cmov/libc.so.6(cfree+0x6d)[0x366383d] /usr/lib/libglib-2.0.so.0(g_free+0x36)[0x63a0c6] /usr/lib/libglib-2.0.so.0[0x65c94a] /lib/tls/i686/cmov/libpthread.so.0[0x13f2ef] /lib/tls/i686/cmov/libpthread.so.0[0x13f81c] /lib/tls/i686/cmov/libc.so.6(clone+0x5e)[0x36c081e] === Memory map: 0011-0012e000 r-xp 08:03 404362 /usr/lib/libdbus-glib-1.so.2.1.0 0012e000-0012f000 r--p 0001e000 08:03 404362 /usr/lib/libdbus-glib-1.so.2.1.0 0012f000-0013 rw-p 0001f000 08:03 404362 /usr/lib/libdbus-glib-1.so.2.1.0 0013-00138000 r-xp 08:03 9396 /usr/lib/libXrender.so.1.3.0 00138000-00139000 r--p 7000 08:03 9396 /usr/lib/libXrender.so.1.3.0 00139000-0013a000 rw-p 8000 08:03 9396 /usr/lib/libXrender.so.1.3.0 0013a000-0015 r-xp 08:03 8027 /lib/tls/i686/cmov/libpthread-2.10.1.so 0015-00151000 r--p 00015000 08:03 8027 /lib/tls/i686/cmov/libpthread-2.10.1.so 00151000-00152000 rw-p 00016000 08:03 8027 /lib/tls/i686/cmov/libpthread-2.10.1.so 00152000-00154000 rw-p 00:00 0 00154000-0016e000 r-xp 08:03 397806 /usr/lib/libgdk_pixbuf-2.0.so.0.1710.0 0016e000-0016f000 r--p 0001a000 08:03 397806 /usr/lib/libgdk_pixbuf-2.0.so.0.1710.0 0016f000-0017 rw-p 0001b000 08:03 397806 /usr/lib/libgdk_pixbuf-2.0.so.0.1710.0 0017-00173000 r-xp 08:03 77036 /lib/libuuid.so.1.3.0 00173000-00174000 r--p 3000 08:03 77036 /lib/libuuid.so.1.3.0 00174000-00175000 rw-p 4000 08:03 77036 /lib/libuuid.so.1.3.0 00175000-0017c000 r-xp 08:03 66639 /usr/lib/libXrandr.so.2.2.0 0017c000-0017d000 r--p 6000 08:03 66639 /usr/lib/libXrandr.so.2.2.0 0017d000-0017e000 rw-p 7000 08:03 66639 /usr/lib/libXrandr.so.2.2.0 0017e000-00186000 r-xp 08:03 398598 /usr/lib/libstartup-notification-1.so.0.0.0 00186000-00187000 r--p 8000 08:03 398598 /usr/lib/libstartup-notification-1.so.0.0.0 00187000-00188000 rw-p 9000 08:03 398598 /usr/lib/libstartup-notification-1.so.0.0.0 00188000-0018a000 r-xp 08:03 9384 /usr/lib/libXinerama.so.1.0.0 0018a000-0018b000 rw-p 1000 08:03 9384 /usr/lib/libXinerama.so.1.0.0 0018b000-0018d000 r-xp 08:03 9571 /usr/lib/libXcomposite.so.1.0.0 0018d000-0018e000 r--p 1000 08:03 9571 /usr/lib/libXcomposite.so.1.0.0 0018e000-0018f000 rw-p 2000 08:03 9571 /usr/lib/libXcomposite.so.1.0.0 0018f000-001b5000 r-xp 08:03 398665 /usr/lib/libgnome-desktop-2.so.11.4.0 001b5000-001b6000 r--p 00025000 08:03 398665 /usr/lib/libgnome-desktop-2.so.11.4.0 001b6000-001b7000 rw-p 00026000 08:03 398665 /usr/lib/libgnome-desktop-2.so.11.4.0 001b7000-00262000 r-xp 08:03 397805 /usr/lib/libgdk-x11-2.0.so.0.1710.0 00262000-00264000 r--p 000ab000 08:03 397805 /usr/lib/libgdk-x11-2.0.so.0.1710.0 00264000-00265000 rw-p 000ad000 08:03 397805 /usr/lib/libgdk-x11-2.0.so.0.1710.0 00265000-002a9000 r-xp 08:03 36938 /usr/lib/libgobject-2.0.so.0.2105.0 002a9000-002aa000 r--p 00044000 08:03 36938 /usr/lib/libgobject-2.0.so.0.2105.0 002aa000-002ab000 rw-p 00045000 08:03 36938 /usr/lib/libgobject-2.0.so.0.2105.0 002ab000-002bf000 r-xp 08:03 11570 /lib/libz.so.1.2.3.3 002bf000-002c r--p 00013000 08:03 11570 /lib/libz.so.1.2.3.3 002c-002c1000 rw-p 00014000 08:03 11570 /lib/libz.so.1.2.3.3 002c1000-002c3000 r-xp 08:03 9370 /usr/lib/libXdamage.so.1.1.0 002c3000-002c4000 rw-p 1000 08:03 9370 /usr/lib/libXdamage.so.1.1.0 002c5000-002c6000 r-xp 00:00 0 [vdso] 002c6000-0034a000 r-xp 08:03 83382 /usr/lib/libcairo.so.2.10800.8 0034a000-0034c000 r--p 00083000 08:03 83382 /usr/lib/libcairo.so.2.10800.8 0034c000-0034d000 rw-p 00085000 08:03 83382 /usr/lib/libcairo.so.2.10800.8 0034d000-00354000 r-xp 08:03 8029
[Bug 425736] Re: [karmic alpha 5] nautilus segfaults
** Attachment added: strace output http://launchpadlibrarian.net/31443123/nautilus.log -- [karmic alpha 5] nautilus segfaults https://bugs.launchpad.net/bugs/425736 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to nautilus in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 425736] Re: [karmic alpha 5] nautilus segfaults
Sorry, I forgot this: nautilus: Installed: 1:2.27.91-0ubuntu3 Candidate: 1:2.27.91-0ubuntu3 Version table: *** 1:2.27.91-0ubuntu3 0 500 http://archive.ubuntu.com karmic/main Packages 100 /var/lib/dpkg/status -- [karmic alpha 5] nautilus segfaults https://bugs.launchpad.net/bugs/425736 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to nautilus in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 425736] Re: nautilus segfaults
Using valgrind makes nautilus at least stable (it doesn't crashed, however it always crashing if I run just alone) so I made the log with issuing nautilus -q inside a terminal to make it quit after a while. Anyway I'm attaching the result. Also I saw lots of things like this: ** (nautilus:25318): WARNING **: fm_icon_view_remove_file() - directory not ** icon view model, shouldn't happen. file: 0xc1b6628:file:///home/lgb/.Xauthority, dir: 0x54d5d00:file:///home/lgb, model: 0x6ee5820:file:///tmp, view loading: 1 If you see this, please add this info to http://bugzilla.gnome.org/show_bug.cgi?id=368178 I don't know it's important or not, though. ** Bug watch added: GNOME Bug Tracker #368178 http://bugzilla.gnome.org/show_bug.cgi?id=368178 ** Attachment added: valgrind-logs-nautilus.tar.gz http://launchpadlibrarian.net/31445794/valgrind-logs-nautilus.tar.gz -- nautilus segfaults https://bugs.launchpad.net/bugs/425736 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 424435] [NEW] Cannot be logged in to gnome desktop after upgrading to karmic alpha5
Public bug reported: Just tried the new karmic alpha 5 on 32 bit x86 with upgrading a stable system on a test machine. After upgrading I can't log in into the gnome environment, all I can see is my background picture and the mouse cursor. According to the output of command ps launched from text console, many gnome processes are running, but neither the nautilus nor the metacity process. I tried to use an empty home too (if it has problems with the old gnome settings), but the result is the same. I also tried KDE (after installing kubuntu-desktop meta package and its dependencies), no problem there. What can I do, how can I help to solve this problem? Thanks a lot in advance, and sorry if I report against the bad package. ** Affects: gnome-session (Ubuntu) Importance: Undecided Status: New -- Cannot be logged in to gnome desktop after upgrading to karmic alpha5 https://bugs.launchpad.net/bugs/424435 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-session in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
