[Bug 354678] [NEW] Error while saving screenshot in absolute path
Public bug reported: Binary package hint: totem When attempting to save a screenshot using an absolute path, the following error dialog appears: Error while saving screenshot Impossible to save the screenshot to file:///home/ubuntu/Desktop/%2Ftmp%2Ftotem.png To reproduce the problem, simply press the PrtSc key and select an absolute path. This bug applies to jaunty beta. ** Affects: totem (Ubuntu) Importance: Undecided Status: New -- Error while saving screenshot in absolute path https://bugs.launchpad.net/bugs/354678 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to totem in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 354681] [NEW] Totem takes more space than available on Eee 701SD
Public bug reported: Binary package hint: totem Totem is unusable on a Eee 701SD which supports a resolution of 800 x 480 (16:10) by default. The window takes too much vertical space and maximizing doesn't workaround the problem. I have attached a screenshot for your convenience. ** Affects: totem (Ubuntu) Importance: Undecided Status: New -- Totem takes more space than available on Eee 701SD https://bugs.launchpad.net/bugs/354681 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to totem in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 354681] Re: Totem takes more space than available on Eee 701SD
** Attachment added: Totem screenshot http://launchpadlibrarian.net/24764699/totem.png -- Totem takes more space than available on Eee 701SD https://bugs.launchpad.net/bugs/354681 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to totem in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 354683] [NEW] Rhythmbox takes more space than available on Eee 701SD
Public bug reported: Binary package hint: rhythmbox Rhythmbox is almost usable on a Eee 701SD which supports a resolution of 800 x 480 (16:10) by default. The window takes too much vertical space and maximizing doesn't workaround the problem. I have attached a screenshot for your convenience. ** Affects: rhythmbox (Ubuntu) Importance: Undecided Status: New -- Rhythmbox takes more space than available on Eee 701SD https://bugs.launchpad.net/bugs/354683 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to rhythmbox in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 354683] Re: Rhythmbox takes more space than available on Eee 701SD
** Attachment added: Rhythmbox screenshot http://launchpadlibrarian.net/24764794/rhythmbox.png -- Rhythmbox takes more space than available on Eee 701SD https://bugs.launchpad.net/bugs/354683 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to rhythmbox in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 354685] [NEW] Volume hotkeys take a long time to react with Rhythmbox
Public bug reported: Binary package hint: rhythmbox When using the volume hotkeys with rhythmbox, it takes a long time for the application to first become gray and then the notifcation to appear. This can be confirmed on a Eee 701SD and a 900. Also note this doesn't happen in other application such as Totem, so this bug is being assigned to the rhythmbox package. ** Affects: rhythmbox (Ubuntu) Importance: Undecided Status: New -- Volume hotkeys take a long time to react with Rhythmbox https://bugs.launchpad.net/bugs/354685 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to rhythmbox in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 354687] [NEW] Evolution setup assistant takes more space than available on Eee 701SD
Public bug reported: Binary package hint: evolution Evolution setup assistant is difficult to use on a Eee 701SD which supports a resolution of 800 x 480 (16:10) by default. The window takes too much vertical and horizontal space, and maximizing doesn't workaround the problem. I have attached a screenshot for your convenience. ** Affects: evolution (Ubuntu) Importance: Undecided Status: New -- Evolution setup assistant takes more space than available on Eee 701SD https://bugs.launchpad.net/bugs/354687 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to evolution in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 354687] Re: Evolution setup assistant takes more space than available on Eee 701SD
** Attachment added: Evolution screenshot http://launchpadlibrarian.net/24765033/evolution.png -- Evolution setup assistant takes more space than available on Eee 701SD https://bugs.launchpad.net/bugs/354687 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to evolution in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 354687] Re: [Jaunty] Evolution setup assistant takes more space than available on Eee 701SD
** Summary changed: - Evolution setup assistant takes more space than available on Eee 701SD + [Jaunty] Evolution setup assistant takes more space than available on Eee 701SD -- [Jaunty] Evolution setup assistant takes more space than available on Eee 701SD https://bugs.launchpad.net/bugs/354687 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to evolution in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 354683] Re: [Jaunty] Rhythmbox takes more space than available on Eee 701SD
** Summary changed: - Rhythmbox takes more space than available on Eee 701SD + [Jaunty] Rhythmbox takes more space than available on Eee 701SD -- [Jaunty] Rhythmbox takes more space than available on Eee 701SD https://bugs.launchpad.net/bugs/354683 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to rhythmbox in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 354678] Re: [Jaunty] Error while saving screenshot in absolute path
** Summary changed: - Error while saving screenshot in absolute path + [Jaunty] Error while saving screenshot in absolute path -- [Jaunty] Error while saving screenshot in absolute path https://bugs.launchpad.net/bugs/354678 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to totem in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 290506] Re: cheese doesn't show v4l2 video output and disables output on gstreamer-based apps ran afterwards
The attached file shows the output of cheese -v. The interesting line might be: v4l2src name=video_source device=/dev/video0 ! capsfilter name=capsfilter caps=video/x-raw- rgb,width=640,height=480,framerate=30/1;video/x-raw- yuv,width=640,height=480,framerate=30/1 ! identity ** Attachment added: cheese -v http://launchpadlibrarian.net/19056940/cheese.txt -- cheese doesn't show v4l2 video output and disables output on gstreamer-based apps ran afterwards https://bugs.launchpad.net/bugs/290506 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gstreamer0.10 in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 290506] Re: cheese doesn't show v4l2 video output and disables output on gstreamer-based apps ran afterwards
Here is the lsbusb -v output on a Dell XPS M1330 where the webcam uses the uvcvideo kernel module, and where cheese doesn't work. ** Attachment added: lsusb -v http://launchpadlibrarian.net/19056953/lsusb.txt -- cheese doesn't show v4l2 video output and disables output on gstreamer-based apps ran afterwards https://bugs.launchpad.net/bugs/290506 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gstreamer0.10 in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 290506] Re: cheese doesn't show v4l2 video output and disables output on gstreamer-based apps ran afterwards
And here is the lsusb -v output on a Toshiba Tecra M8 where the webcam also uses the uvcvideo kernel module, but where cheese works. ** Attachment added: lsusb -v http://launchpadlibrarian.net/19056971/lsusb.txt -- cheese doesn't show v4l2 video output and disables output on gstreamer-based apps ran afterwards https://bugs.launchpad.net/bugs/290506 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gstreamer0.10 in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 290506] Re: cheese doesn't show v4l2 video output and disables output on gstreamer-based apps ran afterwards
From the above comment, it should be noted that the following gstreamer pipeline works just fine on laptops where cheese doesn't work: # gst-launch v4l2src name=video_source device=/dev/video0 ! capsfilter name=capsfilter 'caps=video/x-raw- rgb,width=640,height=480,framerate=30/1;video/x-raw- yuv,width=640,height=480,framerate=30/1' ! gconfvideosink Note how identity was changed for gconfvideosink, which doesn't quite reproduce the problem accurately. -- cheese doesn't show v4l2 video output and disables output on gstreamer-based apps ran afterwards https://bugs.launchpad.net/bugs/290506 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gstreamer0.10 in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 138981] makefile.mk overwrites LDFLAGS defined in Makefile
Public bug reported: I have a Makefile containing the following lines: LDFLAGS := -nostdlibs -Linitramfs/data/lib -Linitramfs/data/usr/lib -export-dynamic -lc -ldl `pkg-config --libs glib-2.0` -lnewt -lslang biostest: $(LIBS) biostest.h .depend $(LIBC) gcc $(LIBS) $(LDFLAGS) -o biostest I also have a debian/rules file with the following line: include /usr/share/cdbs/1/class/makefile.mk When I run debuild, I get the following output when compiling the biostest rule above: gcc dmesg.o main.o tests.o plugins.o ui.o uri.o dumpxml.o usb.o serial.o lib.o acpitable.o dsdt.o e820.o ssh.o -o biostest Notice how all the LDFLAGS are stripped. So, when I look higher in the debuild output, I also see: /usr/bin/make -C . CFLAGS=-g -Wall -O2 CXXFLAGS=-g -Wall -O2 CPPFLAGS= LDFLAGS= The problem here is that the LDFLAGS variables seems to be overwritten by regardless of what has been defined in the Makefile. The source of the problem seems to be in /usr/share/cdbs/1/class/makefile-vars.mk: DEB_MAKE_INVOKE = $(DEB_MAKE_ENVVARS) $(MAKE) $(if $(DEB_MAKE_MAKEFILE), -f $(DEB_MAKE_MAKEFILE),) -C $(DEB_BUILDDIR) CFLAGS=$(if $(CFLAGS_$(cdbs_curpkg)),$(CFLAGS_$(cdbs_curpkg)),$(CFLAGS)) CXXFLAGS=$(if $(CXXFLAGS_$(cdbs_curpkg)),$(CXXFLAGS_$(cdbs_curpkg)),$(CXXFLAGS)) CPPFLAGS=$(if $(CPPFLAGS_$(cdbs_curpkg)),$(CPPFLAGS_$(cdbs_curpkg)),$(CPPFLAGS)) LDFLAGS=$(if $(LDFLAGS_$(cdbs_curpkg)),$(LDFLAGS_$(cdbs_curpkg)),$(LDFLAGS)) So, whether LDFLAGS is not defined at all or defined to be empty, it is always being set to . ** Affects: cdbs (Ubuntu) Importance: Undecided Status: New -- makefile.mk overwrites LDFLAGS defined in Makefile https://bugs.launchpad.net/bugs/138981 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug contact for cdbs in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 123080] [gutsy] booting after hibernation doesn't prompt for a password
You have been subscribed to a public bug: Steps to reproduce: 1. Select System - Quit, then Hibernate 2. Wait for the machine to power off 3. Power on the machine Expected behavior: The user should be prompted for the password of the user previously logged in. Actual behavior: The user is immediately logged into the previous user's session. ** Affects: Ubuntu Importance: Medium Assignee: Ubuntu Desktop Bugs Status: Confirmed ** Tags: hwct -- [gutsy] booting after hibernation doesn't prompt for a password https://bugs.launchpad.net/bugs/123080 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 123078] System - Quit takes a long time to appear
You have been subscribed to a public bug: Immediately after logging in, selecting System - Quit takes more than a minute for the window to appear. If waiting a few minutes after logging in, then selecting System - Quit is much more responsive. Also, when having to wait more than a minute for the window to appear, the options available aren't all available. For example, the suspend and hibernation options are simply not there. However, after waiting a few minutes, those options are available again. ** Affects: gnome-session (Ubuntu) Importance: Undecided Status: New ** Tags: hwct -- System - Quit takes a long time to appear https://bugs.launchpad.net/bugs/123078 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 119326] No hibernate nor sleep button in the quite menu of Gutsy Tribe-1
*** This bug is a duplicate of bug 118537 *** https://bugs.launchpad.net/bugs/118537 Public bug reported: After installing Gutsy Tribe-1 for i386 from the alternate CD on several laptops and desktops, it seems that the quit menu no longer has hibernate nor sleep buttons. ** Affects: Ubuntu Importance: Undecided Status: Unconfirmed ** Changed in: Ubuntu Target: None = ubuntu-7.10-beta ** Summary changed: - No hibernate nor sleep button in the quite menu of Gutsy Tribe-1 + No hibernate nor sleep button in the quit menu of Gutsy Tribe-1 -- No hibernate nor sleep button in the quit menu of Gutsy Tribe-1 https://bugs.launchpad.net/bugs/119326 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug contact for gnome-session in ubuntu (via bug 118537). -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 119326] Re: No hibernate nor sleep button in the quit menu of Gutsy Tribe-1
*** This bug is a duplicate of bug 118537 *** https://bugs.launchpad.net/bugs/118537 Also, for your information, these machines all had the hibernate button in the quit menu with Feisty. -- No hibernate nor sleep button in the quit menu of Gutsy Tribe-1 https://bugs.launchpad.net/bugs/119326 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug contact for gnome-session in ubuntu (via bug 118537). -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 119326] Re: No hibernate nor sleep button in the quit menu of Gutsy Tribe-1
*** This bug is a duplicate of bug 118537 *** https://bugs.launchpad.net/bugs/118537 # lshal | grep can_suspend power_management.can_suspend = true (bool) power_management.can_suspend_hybrid = false (bool) power_management.can_suspend_to_disk = true (bool) power_management.can_suspend_to_ram = true (bool) -- No hibernate nor sleep button in the quit menu of Gutsy Tribe-1 https://bugs.launchpad.net/bugs/119326 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug contact for gnome-session in ubuntu (via bug 118537). -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 119326] Re: No hibernate nor sleep button in the quit menu of Gutsy Tribe-1
*** This bug is a duplicate of bug 118537 *** https://bugs.launchpad.net/bugs/118537 After running apt-get-update and apt-get upgrade, the hibernate and suspend button appear in the quit menu. So, this bug seems to have been fixed since the release of Tribe-1. -- No hibernate nor sleep button in the quit menu of Gutsy Tribe-1 https://bugs.launchpad.net/bugs/119326 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug contact for gnome-session in ubuntu (via bug 118537). -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 103349] gconfd does not cleanup empty directories under /tmp
Public bug reported: When a user logins, gconfd creates a new session and creates a temporary directory for the user under /tmp. For a user named cr3, gconfd creates the directory /tmp/gconfd-cr3. While the user is logged in, this directory is used for storing miscellaneous files. For example, gconfd creates a lock subdirectory. When a user logouts, gconfd cleans everything in the temporary directory except the directory itself. In the above example, the directory /tmp /gconfd-cr3 remains and is completely empty. The expected behavior is that gconfd should cleanup everything for users under /tmp when they logout. ** Affects: gconf2 (Ubuntu) Importance: Undecided Status: Unconfirmed ** Changed in: gconf2 (Ubuntu) Target: None = ubuntu-6.10 ** Summary changed: - gconfd does not cleanup empty directories under /tmp + gconfd-2 does not cleanup empty directories under /tmp -- gconfd-2 does not cleanup empty directories under /tmp https://bugs.launchpad.net/bugs/103349 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug contact for gconf2 in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 96064] Re: [apport] gnome-panel crashed with SIGSEGV in strlen()
** Attachment added: CoreDump.gz http://librarian.launchpad.net/6934137/CoreDump.gz ** Attachment added: Dependencies.txt http://librarian.launchpad.net/6934138/Dependencies.txt ** Attachment added: Disassembly.txt http://librarian.launchpad.net/6934139/Disassembly.txt ** Attachment added: ProcMaps.txt http://librarian.launchpad.net/6934140/ProcMaps.txt ** Attachment added: ProcStatus.txt http://librarian.launchpad.net/6934141/ProcStatus.txt ** Attachment added: Registers.txt http://librarian.launchpad.net/6934142/Registers.txt ** Attachment added: Stacktrace.txt http://librarian.launchpad.net/6934143/Stacktrace.txt ** Attachment added: ThreadStacktrace.txt http://librarian.launchpad.net/6934144/ThreadStacktrace.txt -- [apport] gnome-panel crashed with SIGSEGV in strlen() https://launchpad.net/bugs/96064 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 96064] [apport] gnome-panel crashed with SIGSEGV in strlen()
Public bug reported: Binary package hint: gnome-panel See bug #94433 ProblemType: Crash Architecture: i386 CrashCounter: 1 Date: Sun Mar 25 15:23:06 2007 DistroRelease: Ubuntu 7.04 ExecutablePath: /usr/bin/gnome-panel Package: gnome-panel 2.18.0-0ubuntu2 ProcCmdline: gnome-panel --sm-client-id default1 ProcCwd: /home/ubuntu ProcEnviron: PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games LANG=en_US.UTF-8 SHELL=/bin/bash Signal: 11 SourcePackage: gnome-panel StacktraceTop: strlen () from /lib/tls/i686/cmov/libc.so.6 g_strdup () from /usr/lib/libglib-2.0.so.0 panel_run_dialog_screen_changed (widget=0x83fe690, g_cclosure_marshal_VOID__OBJECT () g_closure_invoke () from /usr/lib/libgobject-2.0.so.0 Uname: Linux ubuntu 2.6.20-9-generic #2 SMP Mon Feb 26 03:01:44 UTC 2007 i686 GNU/Linux UserGroups: adm admin audio cdrom dialout dip floppy lpadmin netdev plugdev powerdev scanner video ** Affects: gnome-panel (Ubuntu) Importance: Undecided Status: Unconfirmed -- [apport] gnome-panel crashed with SIGSEGV in strlen() https://launchpad.net/bugs/96064 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 94433] Re: Run Application on 20070319.1 seems to refresh Gnome
I did not notice apport ever appearing when gnome-panel was running. However, after installing gnome-panel-dbgsym, apport appeared when I attempted to reproduce the problem. So, you will find the generated information in bug #96064: https://bugs.launchpad.net/ubuntu/+source/gnome-panel/+bug/96064 -- Run Application on 20070319.1 seems to refresh Gnome https://launchpad.net/bugs/94433 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 94433] Run Application on 20070319.1 seems to refresh Gnome
Public bug reported: I'm running 20070319.1 on a System76 Z62F laptop. When pressing Alt-F2 to Run Application, pressing the Run... button seems to refresh Gnome. One of the side effects is that the battery applet disappears from the toolbar and appears in a little window of its own. Reproduction steps: 1. Press Alt-F2 2. Enter gedit 3. Press Run... Expected result: The gedit application should appear. Actual result: The whole window manager flashes, as if it was refreshing itself. Then, the battery applet from the toolbar disappears and reappears in its own window. ** Affects: gnome-panel (Ubuntu) Importance: Medium Assignee: Ubuntu Desktop Bugs Status: Needs Info -- Run Application on 20070319.1 seems to refresh Gnome https://beta.launchpad.net/bugs/94433 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 94433] Re: Run Application on 20070319.1 seems to refresh Gnome
Yes, it seems to be gnome-panel crashing. Here is what I did: 1. Look at the current pid of gnome-panel 2. Pressed the Run... button to reproduce the problem 3. Looked at the pid of gnome-panel again The pids before and after the problem were indeed different. -- Run Application on 20070319.1 seems to refresh Gnome https://launchpad.net/bugs/94433 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
