[Bug 459322] Re: gnome-display-properties/xrandr crashes X server when loading after pluging an external display
** Attachment added: "Dependencies.txt" http://launchpadlibrarian.net/34277642/Dependencies.txt ** Attachment added: "ProcMaps.txt" http://launchpadlibrarian.net/34277643/ProcMaps.txt ** Attachment added: "ProcStatus.txt" http://launchpadlibrarian.net/34277644/ProcStatus.txt ** Attachment added: "XsessionErrors.txt" http://launchpadlibrarian.net/34277645/XsessionErrors.txt -- gnome-display-properties/xrandr crashes X server when loading after pluging an external display https://bugs.launchpad.net/bugs/459322 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 459322] [NEW] gnome-display-properties/xrandr crashes X server when loading after pluging an external display
Public bug reported: Binary package hint: gnome-control-center release: ubuntu 9.10 package: gnome-control-center 1:2.28.1-0ubuntu1 related information: 00:02.0 VGA compatible controller: Intel Corporation Mobile 945GME Express Integrated Graphics Controller (rev 03) 00:02.1 Display controller: Intel Corporation Mobile 945GM/GMS/GME, 943/940GML Express Integrated Graphics Controller (rev 03) xserver-xorg: 1:7.4+3ubuntu7 xserver-xorg-video-intel: 2:2.9.0-1ubuntu2 libxrandr2: 2:1.3.0-2 How to reproduce the bug: start your computer (laptop) without any external display plugged in. Let your Gnome session starts. plug the VGA cable in. launch gnome-display-properties. What's happening: X crashes (freeze). relevant Xorg.0.log entries: (at the end of the file) "" (II) intel(0): Allocate new frame buffer 2704x1050 stride 4096 "" What strikes me is that the intel driver is told to allocate a 2704*1050 FB whereas specs available at http://www.intel.com/design/mobile/specupdt/309220.htm page 375 state that maximum resolution is 2048x1536. What's expected: Well, the gnome-display-properties window is expected. More information: -Starting X with the external display already plugged in works, ie: I can launch gnome-display-properties. -if you reproduce the bug process and change the call to gnome-display-properties by a call to xrandr, same bug occurs ProblemType: Bug Architecture: i386 Date: Fri Oct 23 20:22:07 2009 DistroRelease: Ubuntu 9.10 ExecutablePath: /usr/bin/gnome-display-properties Package: gnome-control-center 1:2.28.1-0ubuntu1 ProcEnviron: LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 2.6.31-14.48-generic SourcePackage: gnome-control-center Uname: Linux 2.6.31-14-generic i686 ** Affects: gnome-control-center (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 -- gnome-display-properties/xrandr crashes X server when loading after pluging an external display https://bugs.launchpad.net/bugs/459322 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 321041] Re: gnome-settings-daemon crashed with signal 5 in xkl_process_error()
Well, I could reproduce the bug with Karmic alpha 4 (i386) as my host OS (outside of VirtualBox). I don't think that VirtualBox is a good trail, but it's just my 2cents. Regards, Quentin 2009/8/26 Nikolaj Sheller > Running under Karmic alpha 4 AMD64 in a Virtualbox with compositing > enabled I also get bug 185785. Perhaps there is a relation? > > -- > gnome-settings-daemon crashed with signal 5 in xkl_process_error() > https://bugs.launchpad.net/bugs/321041 > You received this bug notification because you are a direct subscriber > of a duplicate bug. > > Status in Gnome Settings Daemon: New > Status in “gnome-settings-daemon” package in Ubuntu: Incomplete > > Bug description: > Binary package hint: gnome-settings-daemon > > Just crashed out of nowhere... Was running terminal when it crashed. > Running Ubuntu jaunty 9.04 > > ProblemType: Crash > Architecture: amd64 > DistroRelease: Ubuntu 9.04 > ExecutablePath: /usr/lib/gnome-settings-daemon/gnome-settings-daemon > NonfreeKernelModules: nvidia > Package: gnome-settings-daemon 2.25.3-0ubuntu1 > ProcCmdline: /usr/lib/gnome-settings-daemon/gnome-settings-daemon > ProcEnviron: > LANG=en_US.UTF-8 > SHELL=/bin/bash > Signal: 5 > SourcePackage: gnome-settings-daemon > StacktraceTop: > ?? () from /usr/lib/libgdk-x11-2.0.so.0 > xkl_process_error () from /usr/lib/libxklavier.so.12 > _XError () from /usr/lib/libX11.so.6 > _XReply () from /usr/lib/libX11.so.6 > XGetWindowProperty () from /usr/lib/libX11.so.6 > Title: gnome-settings-daemon crashed with signal 5 in xkl_process_error() > Uname: Linux 2.6.28-5-generic x86_64 > UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare > -- Quentin Lampin 06 70 55 41 34 Département Télécommunications Insa de Lyon -- gnome-settings-daemon crashed with signal 5 in xkl_process_error() https://bugs.launchpad.net/bugs/321041 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 338957] Re: python 2.5 -> 2.6 import module pymsn
I found a solution for this bug: First make sure that /usr/bin.python is a symlink pointing to /usr/bin/python2.6 then sudo dpkg-reconfigure python-msn -- python 2.5 -> 2.6 import module pymsn https://bugs.launchpad.net/bugs/338957 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 338957] Re: python 2.5 -> 2.6 import module pymsn
Just make sure that python-msn has been configured against python 2.6 ** Changed in: telepathy-butterfly (Ubuntu) Status: Incomplete => Fix Committed -- python 2.5 -> 2.6 import module pymsn https://bugs.launchpad.net/bugs/338957 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 338957] Re: python 2.5 -> 2.6 import module pymsn
My bad, the package is python-msn (and it's installed). Anyway, the problem seems to affect the migration of python modules version 2.5 to 2.6. As I stated above, switching from 2.6 to 2.5 solved the problem. I don't know what it means, perhaps is it necessary to port python-msn to python 2.6 or to make python 2.5 modules available in 2.6. by the way, here is the correct apt-cache policy output: quen...@quentin-laptop-eee:~$ apt-cache policy python-msn python-msn: Installé : 0.3.3-0ubuntu2 Candidat : 0.3.3-0ubuntu2 Table de version : *** 0.3.3-0ubuntu2 0 500 http://fr.archive.ubuntu.com jaunty/universe Packages 100 /var/lib/dpkg/status -- python 2.5 -> 2.6 import module pymsn https://bugs.launchpad.net/bugs/338957 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 338957] [NEW] python 2.5 -> 2.6 import module pymsn
Public bug reported: Empathy cannot connect to msn accounts. launching telepathy-butterfly after setting $BUTTERFLY_PERSIST to 1 and $BUTTERFLY_DEBUG=all, we get some useful informations. telepathy-butterfly is trying to import the module pymsn. The problem is that it's using python 2.6 and that the pymsn module is in the python2.5 modules directories as shown by: quen...@quentin-laptop-eee:~$ find /usr/lib/ -name pymsn* /usr/lib/python2.5/site-packages/pymsn-0.3.3.egg-info /usr/lib/python2.5/site-packages/pymsn Switching back to python2.5 solves the issue but it's a temporary fix. quen...@quentin-laptop-eee:~$ apt-cache policy pymsnt pymsnt: Installé : 0.11.3-4 Candidat : 0.11.3-4 Table de version : *** 0.11.3-4 0 500 http://fr.archive.ubuntu.com jaunty/universe Packages 100 /var/lib/dpkg/status quen...@quentin-laptop-eee:~$ lsb_release -rd Description:Ubuntu jaunty (development branch) Release:9.04 ** Affects: telepathy-butterfly (Ubuntu) Importance: Undecided Status: New ** Description changed: Empathy cannot connect to msn accounts. launching telepathy-butterfly after setting $BUTTERFLY_PERSIST to 1 and $BUTTERFLY_DEBUG=all, we get some useful informations. telepathy-butterfly is trying to import the module pymsn. The problem is that it's using python 2.6 and that the pymsn module is in the python2.5 modules directories as shown by: quen...@quentin-laptop-eee:~$ find /usr/lib/ -name pymsn* /usr/lib/python2.5/site-packages/pymsn-0.3.3.egg-info /usr/lib/python2.5/site-packages/pymsn - Switching back python2.5 solves the issue but it's a temporary fix. + Switching back to python2.5 solves the issue but it's a temporary fix. quen...@quentin-laptop-eee:~$ apt-cache policy pymsnt pymsnt: Installé : 0.11.3-4 Candidat : 0.11.3-4 Table de version : *** 0.11.3-4 0 500 http://fr.archive.ubuntu.com jaunty/universe Packages 100 /var/lib/dpkg/status quen...@quentin-laptop-eee:~$ lsb_release -rd Description: Ubuntu jaunty (development branch) Release: 9.04 -- python 2.5 -> 2.6 import module pymsn https://bugs.launchpad.net/bugs/338957 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 296168] [NEW] ark archive content update
Public bug reported: Binary package hint: kdeutils simple example to illustrate the bug: #create a new directory mkdir ark_bug #create 3 dummy files touch file1 file2 file3 #fill them so they are not empty echo foo > file1 echo bar > file2 echo foobar > file3 #navigate with dolphin to the ark_bug directory. #right click on file1 then actions/compress/GZipped Tar Archive #it should create an archive called file1.tar.gz #rename it to archive.tar.gz mv file1.tar.gz archive.tar.gz #recreate archive.tar.gz, including all the files with the command line. tar -czf archive.tar.gz file* #re-open the archive with ark #it should show you file1 only. That's the bug. ##general information tar --version : tar (GNU tar) 1.19 ark --version : Qt: 3.3.8b KDE: 3.5.10 Ark: 2.6.4 lsb_release -rd : Description:Ubuntu 8.04.1 Release:8.04 ** Affects: kdeutils (Ubuntu) Importance: Undecided Status: New -- ark archive content update https://bugs.launchpad.net/bugs/296168 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
