[Bug 605603] Re: brasero can't use cdrdao to burn cd
The problem seems to be that the version of cdrdao (in Maverick at least) is too old. The available cdrdao is version 1:1.2.2-18.2ubuntu1 but cdrdao 1.2.3 is required for brasero. cdrdao 1.2.3 is already uploaded in Debian testing so we should be able to simply resync it again to fix this issue. The current cdrdao package in Ubuntu has a very small change compared to Debian. The only remaining change seems to be Add armv7l target. How does this process work, do we first request sync and then applies the diff? As a workaround it is possible to create an image file in brasero and then write the resulting CUE file to disc from the command line with cdrdao with something like: $ cdrdao write brasero.cue -- brasero can't use cdrdao to burn cd https://bugs.launchpad.net/bugs/605603 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to brasero in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 508890] Re: Nautilus crashes when there are multiple XScreens
Which version of xserver-xorg-core do you refer to? My system is fully updated right now but the issue still exists for me with version 2:1.7.3.902-1ubuntu12. -- Nautilus crashes when there are multiple XScreens https://bugs.launchpad.net/bugs/508890 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 508890] Re: Nautilus crashes with Seperate X-Screen (nvidia-current)
My Monitor: k...@amd:0 nautilus ** (nautilus:1545): WARNING **: No marshaller for signature of signal 'UploadFinished' ** (nautilus:1545): WARNING **: No marshaller for signature of signal 'DownloadFinished' ** (nautilus:1545): WARNING **: No marshaller for signature of signal 'ShareCreateError' Initializing nautilus-gdu extension Creating native window for 0x2136c80 (screen: 1) attributes-colormap: 0x1e36820 (1), parent: 0x1e368a0, system: 0x1e368a0 attributes-visual: 0x1e32c00 (1), parent: 0x1e35c00, system: 0x1e35c00 Gdk-ERROR **: The program 'nautilus' received an X Window System error. This probably reflects a bug in the program. The error was 'BadMatch (invalid parameter attributes)'. (Details: serial 1127 error_code 8 request_code 1 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.) aborting... [1]1545 trace trap (core dumped) nautilus My TV: k...@amd:133 nautilus ** (nautilus:1591): WARNING **: No marshaller for signature of signal 'UploadFinished' ** (nautilus:1591): WARNING **: No marshaller for signature of signal 'DownloadFinished' ** (nautilus:1591): WARNING **: No marshaller for signature of signal 'ShareCreateError' Initializing nautilus-gdu extension Creating native window for 0x1142a00 (screen: 0) attributes-colormap: 0xf628a0 (1), parent: 0xf62820, system: 0xf62820 attributes-visual: 0xf61c00 (1), parent: 0xf5ec00, system: 0xf5ec00 Gdk-ERROR **: The program 'nautilus' received an X Window System error. This probably reflects a bug in the program. The error was 'BadMatch (invalid parameter attributes)'. (Details: serial 674 error_code 8 request_code 1 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.) aborting... [1]1591 trace trap (core dumped) nautilus -- Nautilus crashes with Seperate X-Screen (nvidia-current) https://bugs.launchpad.net/bugs/508890 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 508890] Re: Nautilus crashes with Seperate X-Screen (nvidia-current)
Different visuals here too: Primary screen: xwininfo: Window id: 0x2e5 Terminal Absolute upper-left X: 622 Absolute upper-left Y: 237 Relative upper-left X: 3 Relative upper-left Y: 23 Width: 988 Height: 694 Depth: 24 Visual: 0x21 Visual Class: TrueColor Border width: 0 Class: InputOutput Colormap: 0x20 (installed) Bit Gravity State: NorthWestGravity Window Gravity State: NorthWestGravity Backing Store State: NotUseful Save Under State: no Map State: IsViewable Override Redirect State: no Corners: +622+237 -70+237 -70-119 +622-119 -geometry 97x35-67+214 Secondary screen: xwininfo: Window id: 0x325 Terminal Absolute upper-left X: 502 Absolute upper-left Y: 203 Relative upper-left X: 3 Relative upper-left Y: 23 Width: 818 Height: 485 Depth: 24 Visual: 0x1aa Visual Class: TrueColor Border width: 0 Class: InputOutput Colormap: 0x1a9 (installed) Bit Gravity State: NorthWestGravity Window Gravity State: NorthWestGravity Backing Store State: NotUseful Save Under State: no Map State: IsViewable Override Redirect State: no Corners: +502+203 -600+203 -600-392 +502-392 -geometry 80x24+499+180 -- Nautilus crashes with Seperate X-Screen (nvidia-current) https://bugs.launchpad.net/bugs/508890 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 508936] Re: nautilus crash
Stack trace with more debug symbols installed and break on gdk_x_error. ** Attachment added: nautilus-stack-trace_2.txt http://launchpadlibrarian.net/38050588/nautilus-stack-trace_2.txt -- nautilus crash https://bugs.launchpad.net/bugs/508936 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 508936] Re: nautilus crash
I had a theory yesterday when I posted this bug and I just verified it. This crash only occurs when running multiple desktops. I have an NVIDIA card and have my computer attached to the TV. I run two separate X screens configured with nvidia-settings. With this setup nautilus crashes all the time. If just use one screen and disable the TV (hence I only use the monitor) nautilus starts just fine. I haven't tested with TwinView, I can do that too. -- nautilus crash https://bugs.launchpad.net/bugs/508936 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 508936] Re: nautilus crash
Ok, tested with TwinView and it works. So same two screens and same resolution (1680x1050, 1920x1080) on both configurations - separate X screens crashes nautilus while TwinView doesn't. Please let me know if I can provide any more informations. And btw, I'm a programmer so I don't have any problems applying a patch and rebuilding nautilus. It's just the combination of lack of knowledge/experience about the Gnome/GDK/GTK/X11 stack and lack of time that prevents myself from digging into the code. -- nautilus crash https://bugs.launchpad.net/bugs/508936 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 508936] [NEW] nautilus crash
Public bug reported: Binary package hint: nautilus stack trace to come ProblemType: Bug Architecture: amd64 Date: Mon Jan 18 00:16:45 2010 DistroRelease: Ubuntu 10.04 InstallationMedia: Ubuntu 9.10 Karmic Koala - Release Candidate amd64 (20091020.3) NonfreeKernelModules: nvidia Package: nautilus 1:2.29.1-0ubuntu2 ProcEnviron: LC_TIME=sv_SE.utf8 LANGUAGE=en_US.utf8 PATH=(custom, user) LANG=en_US.utf8 SHELL=/usr/bin/zsh ProcVersionSignature: Ubuntu 2.6.32-10.14-generic SourcePackage: nautilus Tags: lucid Uname: Linux 2.6.32-10-generic x86_64 ** Affects: nautilus (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug lucid -- nautilus crash https://bugs.launchpad.net/bugs/508936 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 508936] Re: nautilus crash
** Attachment added: Dependencies.txt http://launchpadlibrarian.net/38011352/Dependencies.txt ** Attachment added: usr_lib_nautilus.txt http://launchpadlibrarian.net/38011354/usr_lib_nautilus.txt -- nautilus crash https://bugs.launchpad.net/bugs/508936 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 508936] Re: nautilus crash
Stack trace for nautilus. You want me to install libglib symbols too? ** Attachment added: nautilus-stack-trace.txt http://launchpadlibrarian.net/38011421/nautilus-stack-trace.txt -- nautilus crash https://bugs.launchpad.net/bugs/508936 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 508936] Re: nautilus crash
This started to happen after updating to nvidia-current, i.e. Nvidia 190.53, well at least I think to. I held back Xorg 7.5 a long time since I knew the Nvidia drivers wasn't updated in Lucid yet. So when I saw that Alberto Milone started to work on updating Nvidia for Lucid I updated Xorg. So most likely because of new Xorg and Nvidia driver. -- nautilus crash https://bugs.launchpad.net/bugs/508936 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 208548] Re: en_SE locale needed to get correct weekdays in Sweden
I confirm that this is an issue. English desktop but Swedish locale settings are indeed common here. I have always been setting LC_TIME for my session for achieving this but that is of course hard for a new user to know. I always creates a file like this. $ cat .gnomerc export LC_TIME=sv_SE.UTF-8 But keep the rest as en_US.UTF-8 as I can't work with Swedish translated desktop :) But if it would be possible to select English (Sweden) in the Language Support application it would really help many users. And the weekday does indeed start at Monday in Sweden. -- en_SE locale needed to get correct weekdays in Sweden https://bugs.launchpad.net/bugs/208548 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-panel in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 88516] gnome-terminal crashes when creating a new tab
Public bug reported: Binary package hint: gnome-terminal In the latest version of gnome-terminal (2.17.92-0ubuntu1, that is in Feisty) it crashes each time a new tab is opened if the window is maximized and just one tab exists earlier. In other words: * Start a new gnome-terminal * Maximize window * Ctrl-t to open a new tab * Crash This only happens if no tab was added before. Which means that a new item is added to the gnome-terminal window when a new tab is created, the list of tabs (which isn't visible with just one tab). It works to open a new tab if the window isn't maximized and it also works to add new tabs when at least two tabs are in the gnome-terminal window. Worked in the previous version. Might also be because of Xorg 7.2 since xorg-server was updated to 2:1.2.0-3ubuntu1 at the same time, but don't think so. Also tried without composite disabled no difference. ** Affects: gnome-terminal (Ubuntu) Importance: Undecided Status: Unconfirmed -- gnome-terminal crashes when creating a new tab https://launchpad.net/bugs/88516 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 88516] Re: gnome-terminal crashes when creating a new tab
Just tried with version 2.17.91-0ubuntu1 of gnome-terminal instead. Crashed with that version also. So is because of something else. -- gnome-terminal crashes when creating a new tab https://launchpad.net/bugs/88516 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 88516] Re: gnome-terminal crashes when creating a new tab
Ok, found the faulty package. Was vte. Installed libvte9_0.15.3-0ubuntu3_i386.deb libvte-common_0.15.3-0ubuntu3_all.deb python-vte_0.15.3-0ubuntu3_i386.deb Instead of the version 0.15.4-0ubuntu1 published today. With 0.15.3-0ubuntu3 is works. Attaching a backtrace with libvte9-dbgsym. ** Attachment added: gnome-terminal-libvte9-dbgsym http://librarian.launchpad.net/6563753/gnome-terminal-libvte9-dbgsym.txt -- gnome-terminal crashes when creating a new tab https://launchpad.net/bugs/88516 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
