[Bug 2000862] [NEW] Nautilus search start tracker-miner-fs everytime
Public bug reported: Everytime I enter a text in Nautilus to start a search, tracker-miner-fs starts, crawling the filesystem for 10-15 mins. No search results are shown before the process finish. However, if I start a search from the command line using tracker3 it works as expected, if I start a search from gnome-shell it works as expected, and with the nightly version of nautilus (flatpak) it works as expected as well. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: nautilus 1:43.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.19.0-26.27-generic 5.19.7 Uname: Linux 5.19.0-26-generic x86_64 ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Mon Jan 2 11:38:22 2023 GsettingsChanges: b'org.gnome.nautilus.list-view' b'default-zoom-level' b"'small'" b'org.gnome.nautilus.preferences' b'default-folder-viewer' b"'list-view'" b'org.gnome.nautilus.window-state' b'initial-size' b'(1248, 638)' InstallationDate: Installed on 2022-02-25 (310 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) SourcePackage: nautilus UpgradeStatus: Upgraded to kinetic on 2022-10-09 (84 days ago) usr_lib_nautilus: file-roller 43.0-1 nautilus-extension-gnome-terminal 3.46.2-1ubuntu1 nautilus-share0.7.5-0.1 ** Affects: nautilus (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug kinetic wayland-session -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/2000862 Title: Nautilus search start tracker-miner-fs everytime To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/2000862/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1869881] Re: html file detected as unknown application/octet-stream
As far as I remember, yes it used to work (after having an application manually set for the file extension). -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1869881 Title: html file detected as unknown application/octet-stream To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1869881/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1869881] Re: html file detected as unknown application/octet-stream
Same issue here with text-like files. The .txt files are now correctly recognized as text files and are open with a text editor by default, but the other configuration files which are not .txt ending, like in my case .parset file, show the issue described by chicoff. Also I set manually an application to open this kind of file, and the application appears in the right-click menu, it does not launch when I select it / press enter / double click on it on the icon. I have to go to "Open with other application" and select the app so that finally I can open the file. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1869881 Title: html file detected as unknown application/octet-stream To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1869881/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1870517] [NEW] Unknown type error when opening sftp text file with nautlus
Public bug reported: On Ubuntu 20.04 freshly installed, double clicking on a text file which does not have a .txt extension return a "The file is of an unknown type" error message. This used to open the file with the text editor. I believe this is due to Nautilus bug #1425: https://gitlab.gnome.org/GNOME/nautilus/-/issues/1425 ** Affects: nautilus Importance: Unknown Status: Unknown ** Affects: nautilus (Ubuntu) Importance: Undecided Status: New ** Bug watch added: gitlab.gnome.org/GNOME/nautilus/-/issues #1425 https://gitlab.gnome.org/GNOME/nautilus/-/issues/1425 ** Also affects: nautilus via https://gitlab.gnome.org/GNOME/nautilus/-/issues/1425 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1870517 Title: Unknown type error when opening sftp text file with nautlus To manage notifications about this bug go to: https://bugs.launchpad.net/nautilus/+bug/1870517/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1064549] [NEW] rhythmbox crashed with SIGSEGV in dmap_container_record_get_entries()
Public bug reported: Crashed while trying to connect to DACP via iRemote android app ProblemType: Crash DistroRelease: Ubuntu 12.10 Package: rhythmbox 2.97-1ubuntu5 ProcVersionSignature: Ubuntu 3.5.0-17.27-generic 3.5.5 Uname: Linux 3.5.0-17-generic x86_64 ApportVersion: 2.6.1-0ubuntu1 Architecture: amd64 Date: Tue Oct 9 19:18:42 2012 ExecutablePath: /usr/bin/rhythmbox InstallationMedia: Ubuntu 11.04 Natty Narwhal - Release amd64 (20110426) ProcCmdline: rhythmbox SegvAnalysis: Segfault happened at: 0x7fce21559cc9 dmap_container_record_get_entries+9: mov(%rbx),%rdi PC (0x7fce21559cc9) ok source (%rbx) (0x) not located in a known VMA region (needed readable region)! destination %rdi ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: rhythmbox StacktraceTop: dmap_container_record_get_entries () from /usr/lib/libdmapsharing-3.0.so.2 _dmap_share_databases () from /usr/lib/libdmapsharing-3.0.so.2 ?? () from /usr/lib/x86_64-linux-gnu/libsoup-2.4.so.1 g_closure_invoke () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 Title: rhythmbox crashed with SIGSEGV in dmap_container_record_get_entries() UpgradeStatus: Upgraded to quantal on 2012-09-04 (34 days ago) UserGroups: adm admin audio bluetooth cdrom dialout dip fax floppy fuse lpadmin plugdev powerdev pulse pulse-access rtkit sambashare tape vboxusers video ** Affects: rhythmbox (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-crash need-amd64-retrace quantal running-unity ** Visibility changed to: Public -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to rhythmbox in Ubuntu. https://bugs.launchpad.net/bugs/1064549 Title: rhythmbox crashed with SIGSEGV in dmap_container_record_get_entries() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rhythmbox/+bug/1064549/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1063006] Re: nautilus crashed with SIGABRT in raise()
** Visibility changed to: Public -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1063006 Title: nautilus crashed with SIGABRT in raise() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1063006/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1063018] Re: gnome-control-center crashed with SIGSEGV in ffi_call_unix64()
** Visibility changed to: Public -- 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/1063018 Title: gnome-control-center crashed with SIGSEGV in ffi_call_unix64() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1063018/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1061862] Re: nautilus crashed with SIGSEGV
** Visibility changed to: Public -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1061862 Title: nautilus crashed with SIGSEGV To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1061862/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 872044] Re: Bluetooth 'Send files' returns permission denied error
Same problem with my Samsung i5800. ** Attachment added: Syslog https://bugs.launchpad.net/ubuntu/+source/gnome-bluetooth/+bug/872044/+attachment/2574835/+files/syslog ** Changed in: gnome-bluetooth (Ubuntu) Status: Incomplete = Confirmed -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-bluetooth in Ubuntu. https://bugs.launchpad.net/bugs/872044 Title: Bluetooth 'Send files' returns permission denied error To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-bluetooth/+bug/872044/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 610358] Re: Cannot start graphical session when disk is full (and Ubuntu does not warn/explain)
** Changed in: disk-manager Status: New = Invalid -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-disk-utility in ubuntu. https://bugs.launchpad.net/bugs/610358 Title: Cannot start graphical session when disk is full (and Ubuntu does not warn/explain) -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 549896] Re: swell-foop doesn't start
*** This bug is a duplicate of bug 561734 *** https://bugs.launchpad.net/bugs/561734 ** This bug has been marked a duplicate of bug 561734 quadrapassel doesn't start: Failed to initialise clutter: Unable to select the newly created GLX context -- swell-foop doesn't start https://bugs.launchpad.net/bugs/549896 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-games in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 561734] Re: quadrapassel doesn't start: Failed to initialise clutter: Unable to select the newly created GLX context
Clutter require 3D capability that some graphic driver can't offer. Same problem for people using VirtualBox or KVM. The main problem i see is that you get no feedback of why the game didn't start. You should get a dialog explaining that you can play this game in a environement that is 3D capable. -- quadrapassel doesn't start: Failed to initialise clutter: Unable to select the newly created GLX context https://bugs.launchpad.net/bugs/561734 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-games in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 395470] Re: nautilus does not recognize music cd
I forgot to say that : Drive connected: 'CD/DVD Drive' appear after i ejected the disc. -- nautilus does not recognize music cd https://bugs.launchpad.net/bugs/395470 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gvfs in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 395470] Re: nautilus does not recognize music cd
I just got this problem with an audio CD. Exact same beahviour : [Before inserting the dic] f...@flo-laptop:~$ gvfs-mount -li Drive(0): 60 GB Hard Disk Type: GProxyDrive (GProxyVolumeMonitorGdu) ids: unix-device: '/dev/sda' themed icons: [drive-harddisk-ata] [drive-harddisk] [drive] is_media_removable=0 has_media=1 is_media_check_automatic=0 can_poll_for_media=0 can_eject=0 can_start=0 can_stop=0 start_stop_type=unknown Volume(0): 66 MB Filesystem Type: GProxyVolume (GProxyVolumeMonitorGdu) ids: uuid: '6ee62768-822d-43d7-8525-737950a49256' unix-device: '/dev/sda1' themed icons: [drive-harddisk-ata] [drive-harddisk] [drive] can_mount=1 can_eject=0 should_automount=0 Volume(1): 15 GB Filesystem Type: GProxyVolume (GProxyVolumeMonitorGdu) ids: uuid: 'ead9c39f-c83f-4f93-a740-da192c932853' unix-device: '/dev/sda2' themed icons: [drive-harddisk-ata] [drive-harddisk] [drive] can_mount=1 can_eject=0 should_automount=0 Mount(0): 15 GB Filesystem - file:///media/disk-2 Type: GProxyMount (GProxyVolumeMonitorGdu) default_location=file:///media/disk-2 themed icons: [drive-harddisk-ata] [drive-harddisk] [drive] can_unmount=1 can_eject=0 is_shadowed=0 Volume(2): MUSIQUE Type: GProxyVolume (GProxyVolumeMonitorGdu) ids: uuid: '43C0-343B' unix-device: '/dev/sda4' label: 'MUSIQUE' themed icons: [drive-harddisk-ata] [drive-harddisk] [drive] can_mount=1 can_eject=0 should_automount=0 Mount(0): MUSIQUE - file:///media/documents Type: GProxyMount (GProxyVolumeMonitorGdu) default_location=file:///media/documents themed icons: [drive-harddisk-ata] [drive-harddisk] [drive] can_unmount=1 can_eject=0 is_shadowed=0 Drive(1): CD/DVD Drive Type: GProxyDrive (GProxyVolumeMonitorGdu) ids: unix-device: '/dev/sr0' themed icons: [drive-optical] [drive] is_media_removable=1 has_media=0 is_media_check_automatic=1 can_poll_for_media=1 can_eject=0 can_start=0 can_stop=0 start_stop_type=unknown f...@flo-laptop:~$ gvfs-mount -o Monitoring events. Press Ctrl+C to quit. [I insert the disc] Drive changed: '_NEC DVD+-RW ND-6500A' Drive disconnected: '_NEC DVD+-RW ND-6500A' Drive connected:'CD/DVD Drive' ** Changed in: gvfs (Ubuntu) Status: Fix Released = Confirmed -- nautilus does not recognize music cd https://bugs.launchpad.net/bugs/395470 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gvfs in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 437638] Re: Totem stop playing when I try to call in skype
** Also affects: gnome-media (Ubuntu) Importance: Undecided Status: New -- Totem stop playing when I try to call in skype https://bugs.launchpad.net/bugs/437638 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-media in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 273142] Re: screensaver won't release with mouse movement
Confirming the bug with 'Floating ubuntu'. I also confirm that it works ok with GLSlideshow. -- screensaver won't release with mouse movement https://bugs.launchpad.net/bugs/273142 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-screensaver in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 24630] Re: Evince crashes when zooming PDF-File to 400%
** Description changed: -- Evince crashes when zooming PDF-File to 400% https://bugs.launchpad.net/bugs/24630 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a direct subscriber. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 157585] Re: Copyng a file to a NTFS drive change the date and the time of the file
*** This bug is a duplicate of bug 215499 *** https://bugs.launchpad.net/bugs/215499 ** This bug is no longer a duplicate of bug 157396 Copyng a file to a NTFS drive change the date and the time of the file ** This bug has been marked a duplicate of bug 215499 Nautilus not preserving timestamps -- Copyng a file to a NTFS drive change the date and the time of the file https://bugs.launchpad.net/bugs/157585 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 157396] Re: Copyng a file to a NTFS drive change the date and the time of the file
*** This bug is a duplicate of bug 215499 *** https://bugs.launchpad.net/bugs/215499 ** Changed in: ntfs-config Status: New = Invalid ** Changed in: ntfs-3g (Ubuntu) Status: New = Invalid ** This bug has been marked a duplicate of bug 215499 Nautilus not preserving timestamps -- Copyng a file to a NTFS drive change the date and the time of the file https://bugs.launchpad.net/bugs/157396 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 223023] [NEW] No way to cancel a CD extraction
Public bug reported: Binary package hint: rhythmbox When starting a CD extraction, there is no way to cancel it without quitting rhthmbox. Sugestions : - A cancel button in the status bar, near the progress bar. - A cancel button near the extract CD button - An extract button which is keept clicked when extracting so that unclicking it pause the extraction, just like how the play/pause buton behave. ProblemType: Bug Architecture: i386 Date: Sun Apr 27 13:42:57 2008 DistroRelease: Ubuntu 8.04 ExecutablePath: /usr/bin/rhythmbox Package: rhythmbox 0.11.5-0ubuntu6 PackageArchitecture: i386 ProcEnviron: PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/bin/X11:/usr/games LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: rhythmbox Uname: Linux 2.6.24-16-generic i686 ** Affects: rhythmbox (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug -- No way to cancel a CD extraction https://bugs.launchpad.net/bugs/223023 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 223023] Re: No way to cancel a CD extraction
** Attachment added: Dependencies.txt http://launchpadlibrarian.net/13960766/Dependencies.txt ** Attachment added: ProcMaps.txt http://launchpadlibrarian.net/13960767/ProcMaps.txt ** Attachment added: ProcStatus.txt http://launchpadlibrarian.net/13960768/ProcStatus.txt -- No way to cancel a CD extraction https://bugs.launchpad.net/bugs/223023 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 223027] [NEW] Clicking by error 2 times on the Extract CD button make rhythmbox extracting 2 time the CD
Public bug reported: Binary package hint: rhythmbox Clicking several time on the the exctract CD button queue again and again the same tracks for extraction. And since there is no way to cancel an exraction (bug #223023) this make the CD extraction experience not really user friendly. It should at least check that the same track is not already in the queue before adding it. I think that this should be a candidate for 8.04.1 ** Affects: rhythmbox (Ubuntu) Importance: Undecided Status: New -- Clicking by error 2 times on the Extract CD button make rhythmbox extracting 2 time the CD https://bugs.launchpad.net/bugs/223027 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 223027] Re: Clicking by error 2 times on the Extract CD button make rhythmbox extracting 2 time the CD
** Bug watch added: GNOME Bug Tracker #530189 http://bugzilla.gnome.org/show_bug.cgi?id=530189 ** Also affects: rhythmbox via http://bugzilla.gnome.org/show_bug.cgi?id=530189 Importance: Unknown Status: Unknown -- Clicking by error 2 times on the Extract CD button make rhythmbox extracting 2 time the CD https://bugs.launchpad.net/bugs/223027 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 223023] Re: No way to cancel a CD extraction
** Bug watch added: GNOME Bug Tracker #365306 http://bugzilla.gnome.org/show_bug.cgi?id=365306 ** Also affects: rhythmbox via http://bugzilla.gnome.org/show_bug.cgi?id=365306 Importance: Unknown Status: Unknown -- No way to cancel a CD extraction https://bugs.launchpad.net/bugs/223023 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 25931] Re: Failed to initalize HAL.
Please follow Martin Pitt comment if you really want to tackle down the problem. Without proper debug information, we can't really now why hal failed to start. -- Failed to initalize HAL. https://bugs.launchpad.net/bugs/25931 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a direct subscriber. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
Re: [Bug 25931] Re: Failed to initalize HAL.
Leeuw a écrit : In my case it's the, only recently surfaced, connection Philips Tv-card. I read through this whole thread, noting down dif'rent fixes that didn't seem to make much sense, So these means that your bug is different than the original one. This bug report is really old and was cause by something simple : hal was started too late. It was fix a long time ago and it seams your bug is different. So you really should follow martin comment : open a new bug and please FOLLOW https://wiki.ubuntu.com/DebuggingHal TO GET REAL DEBUG INFORMATION. Thanks. And stop commenting on this fixed bug, you will not get the visibility you deserve. -- Failed to initalize HAL. https://bugs.launchpad.net/bugs/25931 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a direct subscriber. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 199496] Re: Tomboy.exe crashed with SIGSEGV in exit()
Did it crash on exit ? If not please open a new bug. Thanks. -- Tomboy.exe crashed with SIGSEGV in exit() https://bugs.launchpad.net/bugs/199496 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a direct subscriber. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 194552] Re: [Hardy] GDM starts with wrong display resolution
Wrong resolution in gnome after restart was fixed by #191878. Wrong resolution in GDM is not a bug because gnome-display-properties only set resolution for gnome. If you want to change it, you'll have to change it manually in xorg.conf. ** Changed in: libxrandr (Ubuntu) Status: New = Invalid -- [Hardy] GDM starts with wrong display resolution https://bugs.launchpad.net/bugs/194552 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 197673] Re: gnome-display-properties should revert change automatically if not acknowledged
Florent, cool, I'll take a look at your patch tomorrow. Do as you want. With the actual code i don't see better way to do it. For now you can't pass objects to g-s-d so you'll always need to store new config in a test file. BTW, i wonder why they call configuration_apply_stored() via g-s-d and don't call it directly, that would have been easier to deal with. looking at the gnome-desktop changes, they seem to leak file in the case where false is returned in configuration_apply_stored() Bryce, you might want to use get_filename() in configuration_apply_stored() too. This avoid hard coding 2 times the name of the conf file, and you get the benefice of idle_free. -- gnome-display-properties should revert change automatically if not acknowledged https://bugs.launchpad.net/bugs/197673 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-control-center in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 197673] Re: gnome-display-properties should revert change automatically if not acknowledged
Attached is an updated patch for gnome-control-center It re enable translation. The *.pot file is correctly updated during build but not the *.po. This need some `make update-po` magic, and i don't now how to do that cleanly. ** Attachment added: PATCH 2/3 http://launchpadlibrarian.net/13076671/110_cc-randr12-revert-dialog.patch -- gnome-display-properties should revert change automatically if not acknowledged https://bugs.launchpad.net/bugs/197673 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-control-center in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 208535] Re: Hardy beta: gnome-display-properties allows switching off the only monitor
** Tags added: new-xrandr-capplet -- Hardy beta: gnome-display-properties allows switching off the only monitor https://bugs.launchpad.net/bugs/208535 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-control-center in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 207534] Re: Dual monitor disconnect doesn't reset resolution
Bryce, do you think that the gtk.patch in the upstream source tree might help one that ? Anyway, affect to gnome-control-center for now, even if it has nothing to do here... ** Changed in: gnome-control-center (Ubuntu) Sourcepackagename: None = gnome-control-center -- Dual monitor disconnect doesn't reset resolution https://bugs.launchpad.net/bugs/207534 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-control-center in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 197673] Re: gnome-display-properties should revert change automatically if not acknowledged
** Tags added: new-xrandr-capplet -- gnome-display-properties should revert change automatically if not acknowledged https://bugs.launchpad.net/bugs/197673 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-control-center in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 194552] Re: [Hardy] GDM starts with wrong display resolution
Is it only GDM that start with the wrong resolution or even gnome ? If it's only GDM, gnome-display-properties will not help (at least for now) as it only set the resolution for gnome. ** Tags added: new-xrandr-capplet -- [Hardy] GDM starts with wrong display resolution https://bugs.launchpad.net/bugs/194552 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 197673] Re: gnome-display-properties should revert change automatically if not acknowledged
Finaly the gnome-control-center patch that make use of the above. ** Attachment added: PATCH 3/3 http://launchpadlibrarian.net/13039184/110_cc-randr12-revert-dialog.patch -- gnome-display-properties should revert change automatically if not acknowledged https://bugs.launchpad.net/bugs/197673 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-control-center in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 197673] Re: gnome-display-properties should revert change automatically if not acknowledged
Then the gnome-setting-daemon patch that make it react to _GNOME_RANDR_TEST_ATOM xevent by calling configuration_apply_test. ** Attachment added: PATCH 2/3 http://launchpadlibrarian.net/13039173/93_gsd-randr12-revert-dialog.patch -- gnome-display-properties should revert change automatically if not acknowledged https://bugs.launchpad.net/bugs/197673 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-control-center in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 197673] Re: gnome-display-properties should revert change automatically if not acknowledged
Hi all, Here we go. First the gnome-desktop patch that implement : configuration_save_test configuration_apply_test ** Attachment added: Patch 1/3 http://launchpadlibrarian.net/13039165/104_gd-xrandr-revert-dialog.patch -- gnome-display-properties should revert change automatically if not acknowledged https://bugs.launchpad.net/bugs/197673 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-control-center in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 197673] Re: gnome-display-properties should revert change automatically if not acknowledged
Humm, why did it set mime-type to text/html ??? Anyway, this is a first shoot so some tests are required, but overall this seams to works ok. No gettext for now but that might be a futur patch. Not the most urgent. Now i'll take some rest ;) Cheers -- gnome-display-properties should revert change automatically if not acknowledged https://bugs.launchpad.net/bugs/197673 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-control-center in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 203125] Re: gnome-panel workspace switcher segfaults when switching workspaces
*** This bug is a duplicate of bug 207693 *** https://bugs.launchpad.net/bugs/207693 ** This bug is no longer a duplicate of bug 199380 gnome-panel crashed with SIGSEGV in g_object_get() ** This bug has been marked a duplicate of bug 207693 gnome-panel crashed with SIGSEGV -- gnome-panel workspace switcher segfaults when switching workspaces https://bugs.launchpad.net/bugs/203125 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 200629] Re: Panel crash when switching viewports
*** This bug is a duplicate of bug 207693 *** https://bugs.launchpad.net/bugs/207693 ** This bug is no longer a duplicate of bug 199380 gnome-panel crashed with SIGSEGV in g_object_get() ** This bug has been marked a duplicate of bug 207693 gnome-panel crashed with SIGSEGV -- Panel crash when switching viewports https://bugs.launchpad.net/bugs/200629 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to libwnck in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 199380] Re: gnome-panel crashed with SIGSEGV in g_object_get()
*** This bug is a duplicate of bug 207693 *** https://bugs.launchpad.net/bugs/207693 ** This bug has been marked a duplicate of bug 207693 gnome-panel crashed with SIGSEGV -- gnome-panel crashed with SIGSEGV in g_object_get() https://bugs.launchpad.net/bugs/199380 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to libwnck in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 207693] Re: gnome-panel crashed with SIGSEGV
https://bugs.edge.launchpad.net/ubuntu/+source/libwnck/+bug/199380 is the same bug and contains a valgrind showing the issue : ==27419== Invalid read of size 4 ==27419==at 0x44B87D1: gtk_tooltip_start_delay (gtktooltip.c:1015) ==27419==by 0x44B93DF: _gtk_tooltip_handle_event (gtktooltip.c:1298) ==27419==by 0x43DBCF9: gtk_main_do_event (gtkmain.c:1608) ==27419==by 0x464FA99: gdk_event_dispatch (gdkevents-x11.c:2351) ==27419==by 0x4858D15: g_main_context_dispatch (gmain.c:2003) ==27419==by 0x485C0D2: g_main_context_iterate (gmain.c:2636) ==27419==by 0x485C68D: g_main_context_iteration (gmain.c:2699) ==27419==by 0x751BDF3: processEvents (gconf.c:1886) ==27419==by 0x757B13D: ccsProcessEvents (main.c:1729) ==27419==by 0x7544549: wnck_pager_query_tooltip (in /usr/lib/libwnck-1.so.22.3.6) ==27419==by 0x43E09A3: _gtk_marshal_BOOLEAN__INT_INT_BOOLEAN_OBJECT (gtkmarshalers.c:835) ==27419==by 0x47EE078: g_type_class_meta_marshal (gclosure.c:567) ==27419==by 0x47EF82E: g_closure_invoke (gclosure.c:490) ==27419==by 0x4804119: signal_emit_unlocked_R (gsignal.c:2478) ==27419==by 0x4805946: g_signal_emit_valist (gsignal.c:2209) ==27419==by 0x4805EDF: g_signal_emit_by_name (gsignal.c:2267) ==27419==by 0x44B9275: gtk_tooltip_run_requery (gtktooltip.c:747) ==27419==by 0x44B9485: _gtk_tooltip_handle_event (gtktooltip.c:1256) ==27419==by 0x43DBCF9: gtk_main_do_event (gtkmain.c:1608) ==27419==by 0x464FA99: gdk_event_dispatch (gdkevents-x11.c:2351) ==27419==by 0x4858D15: g_main_context_dispatch (gmain.c:2003) ==27419==by 0x485C0D2: g_main_context_iterate (gmain.c:2636) ==27419==by 0x485C68D: g_main_context_iteration (gmain.c:2699) ==27419==by 0x751BDF3: processEvents (gconf.c:1886) ==27419==by 0x757B13D: ccsProcessEvents (main.c:1729) ==27419==by 0x7544549: wnck_pager_query_tooltip (in /usr/lib/libwnck-1.so.22.3.6) ==27419==by 0x43E09A3: _gtk_marshal_BOOLEAN__INT_INT_BOOLEAN_OBJECT (gtkmarshalers.c:835) ==27419==by 0x47EE078: g_type_class_meta_marshal (gclosure.c:567) ==27419==by 0x47EF82E: g_closure_invoke (gclosure.c:490) ==27419==by 0x4804119: signal_emit_unlocked_R (gsignal.c:2478) ==27419==by 0x4805946: g_signal_emit_valist (gsignal.c:2209) ==27419==by 0x4805EDF: g_signal_emit_by_name (gsignal.c:2267) ==27419==by 0x44B9275: gtk_tooltip_run_requery (gtktooltip.c:747) ==27419==by 0x44B9485: _gtk_tooltip_handle_event (gtktooltip.c:1256) ==27419==by 0x43DBCF9: gtk_main_do_event (gtkmain.c:1608) ==27419==by 0x464FA99: gdk_event_dispatch (gdkevents-x11.c:2351) ==27419==by 0x4858D15: g_main_context_dispatch (gmain.c:2003) ==27419==by 0x485C0D2: g_main_context_iterate (gmain.c:2636) ==27419==by 0x485C68D: g_main_context_iteration (gmain.c:2699) ==27419==by 0x751BDF3: processEvents (gconf.c:1886) ==27419== Address 0x48 is not stack'd, malloc'd or (recently) free'd -- gnome-panel crashed with SIGSEGV https://bugs.launchpad.net/bugs/207693 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to libwnck in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 197673] Re: gnome-display-properties should revert change automatically if not acknowledged
Hi bryce, gd_randr12_revert_support.patch : doesn't apply cleanly (as 104_gd_randr12_revert_support.patch) cc_randr12_revert_dialog.patch : fail to build. You probably should add at least (most obvious): #define REVERT_COUNT 40 Also gettext is quite broken. Another implementation idea would be to make apply_stored_configuration (in g-s-d) configuration file independant, like : apply_configuration (RWScreen *screen, gchar *file) so apply would be something like that : configurations_write(app-all_configurations, get_test_filename(), NULL) apply_configuration (app-screen, get_test_filename()); run_revert_dialog () configurations_write(app-all_configurations, get_filename(), NULL) apply_configuration (app-screen, get_filename()); In side not, i saw that upstream is implementing clone support right now. Do you think that this may land in ubuntu, but i understand that this is not the priority ;) -- gnome-display-properties should revert change automatically if not acknowledged https://bugs.launchpad.net/bugs/197673 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-control-center in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 197673] Re: gnome-display-properties should revert change automatically if not acknowledged
Ok, forget my previous implementation idea, i was confused by the big mess of the upstream tree. There is of course no apply_configuration in g-s-d, it's a running daemon (damn i'm stupid). So xrandr_capplet talk to it with Xevents. So i have an other implementation idea. Why not create an xevent for testing purpose.We would call it _GNOME_RANDR_ATOM_TEST for exemple. It would call a configuration_apply_stored_test (or configuration_apply_stored(screen, testfile) as you want) that would apply a test file. so apply() in xrandr_capplet would work like that : configuration_save(,,testfile) XsendEvent - _GNOME_RANDR_ATOM_TEST message run_revert_dialog configuration_save(,,file) Might be a bit confusion. I may hack a bit on it tomorrow night to see what i can do with it. -- gnome-display-properties should revert change automatically if not acknowledged https://bugs.launchpad.net/bugs/197673 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-control-center in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 207911] Re: gvfsd-gphoto2 crashed with SIGSEGV in pthread_mutex_lock()
*** This bug is a duplicate of bug 202304 *** https://bugs.launchpad.net/bugs/202304 ** Tags added: need-i386-retrace ** Tags removed: apport-failed-retrace -- gvfsd-gphoto2 crashed with SIGSEGV in pthread_mutex_lock() https://bugs.launchpad.net/bugs/207911 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gvfs in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 202304] Re: gvfsd-gphoto2 crashed with SIGSEGV in pthread_mutex_lock()
I can confirm this bug. I also can confirm that 'gphoto2 -L' works, so this has nothing to do with the sansa issue. I also found that when mounting with right-click-mount it works. Can somebody try that ? ** Changed in: gvfs (Ubuntu) Status: Incomplete = Confirmed -- gvfsd-gphoto2 crashed with SIGSEGV in pthread_mutex_lock() https://bugs.launchpad.net/bugs/202304 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is the registrant for gvfs. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 200629] Re: Panel crash when switching viewports
*** This bug is a duplicate of bug 199380 *** https://bugs.launchpad.net/bugs/199380 ** This bug has been marked a duplicate of bug 199380 gnome-panel crashed with SIGSEGV in g_object_get() -- Panel crash when switching viewports https://bugs.launchpad.net/bugs/200629 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to libwnck in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 197153] Re: gnome-settings-daemon crashed with SIGSEGV
Longsleep, this is a different bug. please see Bug #199960 Thanks -- gnome-settings-daemon crashed with SIGSEGV https://bugs.launchpad.net/bugs/197153 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-control-center in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 195153] Re: Yelp take a lot of ressource
It seams to not be a problem for me anymore. Bernard, feel free to reopen it if it's still an issue for you. ** Changed in: yelp (Ubuntu) Status: Incomplete = Fix Released -- Yelp take a lot of ressource https://bugs.launchpad.net/bugs/195153 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to yelp in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 199380] Re: gnome-panel crashed with SIGSEGV in g_object_get()
I think i can also reproduce this crash. It's have to do with the new tooltip. My way to reproduce it is : 1. enable compiz 2. move the mouse over the workspace switcher 3. as soon as the tooltip appears, click on a workspace (different than your current one, of course) 4. repeat with different delay until it crash The tooltip is created by libwnck22. If i rebuild this package without the patch that add this tooltip (02_expose_wm_keybindings.patch) it don't crash anymore. ** Also affects: libwnck (Ubuntu) Importance: Undecided Status: New -- gnome-panel crashed with SIGSEGV in g_object_get() https://bugs.launchpad.net/bugs/199380 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 199380] Re: gnome-panel crashed with SIGSEGV in g_object_get()
** Attachment added: A BIG backtrace of the crash http://launchpadlibrarian.net/12755790/big_bactrace -- gnome-panel crashed with SIGSEGV in g_object_get() https://bugs.launchpad.net/bugs/199380 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 199380] Re: gnome-panel crashed with SIGSEGV in g_object_get()
** Attachment added: A valgrind log http://launchpadlibrarian.net/12755792/valgrind.log -- gnome-panel crashed with SIGSEGV in g_object_get() https://bugs.launchpad.net/bugs/199380 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 203125] Re: gnome-panel workspace switcher segfaults when switching workspaces
*** This bug is a duplicate of bug 199380 *** https://bugs.launchpad.net/bugs/199380 ** This bug has been marked a duplicate of bug 199380 gnome-panel crashed with SIGSEGV in g_object_get() -- gnome-panel workspace switcher segfaults when switching workspaces https://bugs.launchpad.net/bugs/203125 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 198951] Re: gnome-display-properties crashed with SIGSEGV in screen_info_new() - i855, fglrx, radeonhd
Sebastien you are my hero ! -- gnome-display-properties crashed with SIGSEGV in screen_info_new() - i855, fglrx, radeonhd https://bugs.launchpad.net/bugs/198951 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-desktop in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 198951] Re: gnome-display-properties crashed with SIGSEGV in screen_info_new() - i855, fglrx, radeonhd
Hi Bryce, X.Org X Server 1.4.0.90 Release Date: 5 September 2007 X Protocol Version 11, Revision 0 Build Operating System: Linux Ubuntu (xorg-server 2:1.4.1~git20080131-1ubuntu5~b wh1) Current Operating System: Linux flo-laptop 2.6.24-12-generic #1 SMP Mon Mar 10 1 5:32:00 UTC 2008 i686 Build Date: 10 March 2008 11:54:37PM With intel 855GM, no change. Crashing at the exact same point. -- gnome-display-properties crashed with SIGSEGV in screen_info_new() - i855, fglrx, radeonhd https://bugs.launchpad.net/bugs/198951 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 198951] [NEW] [intel 855GM] gnome-display-properties crashed with SIGSEGV in screen_info_new()
Public bug reported: Binary package hint: gnome-control-center Starting gnome-display-properties crash at startup. I got this from standart output : Resource Timestamp: 39771 Resource Configuration Timestamp: 39771 CRTC 49 Timestamp: 39771 CRTC 4a Timestamp: 39771 Output 4b Timestamp: 39771 I should add that xrandr 1.2 is running correctly from the terminal. I can change my resolution without problems : [EMAIL PROTECTED]:~$ xrandr Screen 0: minimum 320 x 200, current 1024 x 768, maximum 1024 x 768 VGA disconnected (normal left inverted right x axis y axis) LVDS connected 1024x768+0+0 (normal left inverted right x axis y axis) 304mm x 228mm 1024x768 60.0*+ 800x60060.3 640x48059.9 TMDS disconnected (normal left inverted right x axis y axis) [EMAIL PROTECTED]:~$ xrandr --output LVDS --mode 800x600 [EMAIL PROTECTED]:~$ xrandr --output LVDS --auto [EMAIL PROTECTED]:~$ Laptop : Dell 510m Graphic card: intel 855GM ProblemType: Crash Architecture: i386 CrashCounter: 1 Date: Thu Mar 6 01:29:30 2008 DistroRelease: Ubuntu 8.04 ExecutablePath: /usr/bin/gnome-display-properties NonfreeKernelModules: cdrom Package: gnome-control-center 1:2.21.92-0ubuntu2 PackageArchitecture: i386 ProcCmdline: gnome-display-properties ProcEnviron: SHELL=/bin/bash PATH=/home/username/.bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/bin/X11:/usr/games LANG=fr_FR.UTF-8 Signal: 11 SourcePackage: gnome-control-center StacktraceTop: screen_info_new (screen=value optimized out) rw_screen_new (gdk_screen=0x80710b0, main () Title: gnome-display-properties crashed with SIGSEGV in screen_info_new() Uname: Linux 2.6.24-11-generic i686 UserGroups: adm admin audio cdrom dialout dip fax usernameppy fuse lpadmin mythtv plugdev sambashare scanner tape ** Affects: gnome-control-center (Ubuntu) Importance: Medium Status: New ** Affects: xserver-xorg-video-intel (Ubuntu) Importance: Undecided Status: New ** Tags: apport-crash -- [intel 855GM] gnome-display-properties crashed with SIGSEGV in screen_info_new() https://bugs.launchpad.net/bugs/198951 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-control-center in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 198951] Re: [intel 855GM] gnome-display-properties crashed with SIGSEGV in screen_info_new()
** Attachment added: CoreDump.gz http://launchpadlibrarian.net/12452737/CoreDump.gz ** Attachment added: Dependencies.txt http://launchpadlibrarian.net/12452738/Dependencies.txt ** Attachment added: Disassembly.txt http://launchpadlibrarian.net/12452739/Disassembly.txt ** Attachment added: ProcMaps.txt http://launchpadlibrarian.net/12452740/ProcMaps.txt ** Attachment added: ProcStatus.txt http://launchpadlibrarian.net/12452741/ProcStatus.txt ** Attachment added: Registers.txt http://launchpadlibrarian.net/12452742/Registers.txt ** Attachment added: Stacktrace.txt http://launchpadlibrarian.net/12452743/Stacktrace.txt ** Attachment added: ThreadStacktrace.txt http://launchpadlibrarian.net/12452744/ThreadStacktrace.txt ** Also affects: xserver-xorg-video-intel (Ubuntu) Importance: Undecided Status: New ** Visibility changed to: Public -- [intel 855GM] gnome-display-properties crashed with SIGSEGV in screen_info_new() https://bugs.launchpad.net/bugs/198951 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-control-center in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
Re: [Bug 197153] Re: gnome-settings-daemon crashed with SIGSEGV
Bryce Harrington a écrit : @Florent and rbmorse: Thanks for confirming that the crash is gone on 855, that's a relief. So technically this bug is solved - system start up is no longer prevented. I'm dropping the priority and milestone. For the separate gnome-display-properties crash, unfortunately that means this tool is not going to function on your system for now. I will add an error dialog so it errors out gracefully rather than gives a crash in these cases, but we need to explore that in more detail - please open new bugs (against the specific graphic driver) that gnome- display-properties does not run on your hardware? (This bug is getting rather long, so if/when we upstream the bug, it'll be clearer if it's focused on this one specific issue.) I opened a new one for intel 855GM : #198951 Thanks -- gnome-settings-daemon crashed with SIGSEGV https://bugs.launchpad.net/bugs/197153 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-control-center in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 197153] Re: gnome-settings-daemon crashed with SIGSEGV
Some results with an intel 855 GM : With gnome-settings-daemon 2.21.91-0ubuntu6 and gnome-desktop 2:21.92-ubuntu3 gnome-settings-daemon don't crash anymore at startup. However, gnome-display-properties still crash with a sligthly different backtrace : #0 rw_output_by_id (info=0x1af28, id=77) at randrwrap.c:122 output = value optimized out #1 0xb7ef7970 in screen_info_new (screen=value optimized out) at randrwrap.c:606 info = (ScreenInfo *) 0x81d2f90 #2 0xb7ef7f0b in rw_screen_new (gdk_screen=0x80710b0, callback=0x804cdb0 [EMAIL PROTECTED], data=0x8077128) at randrwrap.c:391 screen = (RWScreen *) 0x81d2f00 dpy = (Display *) 0x8065578 event_base = 98 ignore = 173 #3 0x0804cfea in main () -- gnome-settings-daemon crashed with SIGSEGV https://bugs.launchpad.net/bugs/197153 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-desktop in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
Re: [Bug 197153] Re: gnome-settings-daemon crashed with SIGSEGV
2008/3/3, Bryce Harrington [EMAIL PROTECTED]: From the confirmations, it sounds like all the reporters are using drivers or hardware without proper xrandr 1.2 support. I would imagine fglrx users would have the same problem. Do you mean that the intel driver with an intel 855 card is not enough for proper xrandr 1.2 support ? -- gnome-settings-daemon crashed with SIGSEGV https://bugs.launchpad.net/bugs/197153 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-desktop in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
Re: [Bug 197153] Re: gnome-settings-daemon crashed with SIGSEGV
Those packages don't seem to exist under hardy. Use this repo : deb http://ddebs.ubuntu.com hardy main universe -- gnome-settings-daemon crashed with SIGSEGV https://bugs.launchpad.net/bugs/197153 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-desktop in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 197153] Re: gnome-settings-daemon crashed with SIGSEGV
A backtrace : --- stack trace --- #0 rw_output_by_id (info=0x0, id=77) at randrwrap.c:122 output = value optimized out #1 0xb6dc9990 in screen_info_new (screen=value optimized out) at randrwrap.c:606 info = (ScreenInfo *) 0x80a4e50 #2 0xb6dc9f3b in rw_screen_new (gdk_screen=0x806e0b0, callback=0xb6e05340 on_randr_event, data=0x0) at randrwrap.c:391 screen = (RWScreen *) 0x80a4c10 dpy = (Display *) 0x8062878 event_base = 98 ignore = 173 #3 0xb6e05410 in gsd_xrandr_manager_start (manager=0x8078080, error=0xbf901500) at gsd-xrandr-manager.c:114 rw_screen = value optimized out #4 0xb6e0520f in impl_activate (plugin=0x80892c8) at gsd-xrandr-plugin.c:78 res = value optimized out error = (GError *) 0x0 #5 0x0804b86e in gnome_settings_plugins_engine_activate_plugin (info=0x8087688) at gnome-settings-plugins-engine.c:533 __PRETTY_FUNCTION__ = gnome_settings_plugins_engine_activate_plugin #6 0x0804bb98 in activate_plugin (info=0x8087688, user_data=0x0) at gnome-settings-plugins-engine.c:244 res = value optimized out #7 0xb76af041 in IA__g_slist_foreach (list=0x8080fd0, func=0x804bb80 activate_plugin, user_data=0x0) at /build/buildd/glib2.0-2.15.6/glib/gslist.c:468 next = (GSList *) 0x8080fe0 #8 0x0804beba in gnome_settings_plugins_engine_init (gconf_prefix=0x8082820 /apps/gnome_settings_daemon/plugins) at gnome-settings-plugins-engine.c:346 __PRETTY_FUNCTION__ = gnome_settings_plugins_engine_init #9 0x0804acd3 in gnome_settings_manager_start (manager=0x8077f48, error=0xbf901634) at gnome-settings-manager.c:106 No locals. #10 0x0804aa5a in main (argc=134712472, argv=0x2) at main.c:221 manager = (GnomeSettingsManager *) 0x8077f48 program = (GnomeProgram *) 0x80732b8 res = value optimized out error = (GError *) 0x0 --- thread stack trace --- . Thread 2 (process 19530): #0 0xb7fc6410 in __kernel_vsyscall () #1 0xb764d99b in read () from /lib/tls/i686/cmov/libpthread.so.0 #2 0xb7691cba in child_watch_helper_thread (data=0x0) at /build/buildd/glib2.0-2.15.6/glib/gmain.c:3910 b = \n\236d�(s��*\017u�\001\000\000\000\230K\b\b list = (GSList *) 0x8084b98 #3 0xb76b8fef in g_thread_create_proxy (data=0x8084b98) at /build/buildd/glib2.0-2.15.6/glib/gthread.c:635 __PRETTY_FUNCTION__ = g_thread_create_proxy #4 0xb76464fb in start_thread () from /lib/tls/i686/cmov/libpthread.so.0 #5 0xb75c88ee in clone () from /lib/tls/i686/cmov/libc.so.6 . Thread 1 (process 19528): #0 rw_output_by_id (info=0x0, id=77) at randrwrap.c:122 output = value optimized out #1 0xb6dc9990 in screen_info_new (screen=value optimized out) at randrwrap.c:606 info = (ScreenInfo *) 0x80a4e50 #2 0xb6dc9f3b in rw_screen_new (gdk_screen=0x806e0b0, callback=0xb6e05340 on_randr_event, data=0x0) at randrwrap.c:391 screen = (RWScreen *) 0x80a4c10 dpy = (Display *) 0x8062878 event_base = 98 ignore = 173 #3 0xb6e05410 in gsd_xrandr_manager_start (manager=0x8078080, error=0xbf901500) at gsd-xrandr-manager.c:114 rw_screen = value optimized out #4 0xb6e0520f in impl_activate (plugin=0x80892c8) at gsd-xrandr-plugin.c:78 res = value optimized out error = (GError *) 0x0 #5 0x0804b86e in gnome_settings_plugins_engine_activate_plugin (info=0x8087688) at gnome-settings-plugins-engine.c:533 __PRETTY_FUNCTION__ = gnome_settings_plugins_engine_activate_plugin #6 0x0804bb98 in activate_plugin (info=0x8087688, user_data=0x0) at gnome-settings-plugins-engine.c:244 res = value optimized out #7 0xb76af041 in IA__g_slist_foreach (list=0x8080fd0, func=0x804bb80 activate_plugin, user_data=0x0) at /build/buildd/glib2.0-2.15.6/glib/gslist.c:468 next = (GSList *) 0x8080fe0 #8 0x0804beba in gnome_settings_plugins_engine_init (gconf_prefix=0x8082820 /apps/gnome_settings_daemon/plugins) at gnome-settings-plugins-engine.c:346 __PRETTY_FUNCTION__ = gnome_settings_plugins_engine_init #9 0x0804acd3 in gnome_settings_manager_start (manager=0x8077f48, error=0xbf901634) at gnome-settings-manager.c:106 No locals. #10 0x0804aa5a in main (argc=134712472, argv=0x2) at main.c:221 manager = (GnomeSettingsManager *) 0x8077f48 program = (GnomeProgram *) 0x80732b8 res = value optimized out error = (GError *) 0x0 It seams the problem is in gnome-desktop ** Also affects: gnome-desktop (Ubuntu) Importance: Undecided Status: New -- gnome-settings-daemon crashed with SIGSEGV https://bugs.launchpad.net/bugs/197153 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-desktop in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 197153] Re: gnome-settings-daemon crashed with SIGSEGV
graphic card : intel 855 GM Attached is my xorg.conf ** Attachment added: xorg.conf http://launchpadlibrarian.net/12341101/xorg.conf -- gnome-settings-daemon crashed with SIGSEGV https://bugs.launchpad.net/bugs/197153 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-desktop in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 197153] Re: gnome-settings-daemon crashed with SIGSEGV
No problem with the i810 driver, but i guess it's because it don't support randr 1.2 -- gnome-settings-daemon crashed with SIGSEGV https://bugs.launchpad.net/bugs/197153 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-desktop in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 195153] Re: Yelp take a lot of ressource
Here is a screenshot showing yelp acting strangely. As you can, yelp is using 90% of my CPU and 6% of my memory while it is *idle*. In fact it consume less CPU if i actually use it. My system : Intel centrino 1600MHz - 1024 Mo RAM I don't know what else i can provide to help you. Tell me. ** Attachment added: Yelp_acting_strangely http://launchpadlibrarian.net/12241680/Capture.png -- Yelp take a lot of ressource https://bugs.launchpad.net/bugs/195153 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to yelp in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 195153] Re: Yelp take a lot of ressource
Hum, forgot to answer your question : ubuntu version : Hardy yelp version : 2.21.90 -- Yelp take a lot of ressource https://bugs.launchpad.net/bugs/195153 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to yelp in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 189448] Re: Nibbles is buggy
I can't reproduce it myself. I'll reopen it if i can't. Thanks for your time. ** Changed in: gnome-games (Ubuntu) Status: Incomplete = Invalid -- Nibbles is buggy https://bugs.launchpad.net/bugs/189448 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 195150] [NEW] Some nroff macros are not recognised by yelp
Public bug reported: Binary package hint: yelp Yelp fail to format certain unix man page correctly, probably because it fail to recognize certain nroff macros. Step to reproduce (this is an exemple that require mplayer.) : 1. Open yelp 2. Manual page - application - mplayer The INTERACTIVE CONTROL-keybord control paragraphe is not formated correctly. 3. Look at 'man mplayer' to see what it should look like. ProblemType: Bug Architecture: i386 Date: Sun Feb 24 19:42:32 2008 DistroRelease: Ubuntu 8.04 ExecutablePath: /usr/bin/yelp Package: yelp 2.21.90-0ubuntu2 PackageArchitecture: i386 ProcCwd: /home/flo ProcEnviron: PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/bin/X11:/usr/games LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: yelp Uname: Linux flo-laptop 2.6.24-8-generic #1 SMP Thu Feb 14 20:40:45 UTC 2008 i686 GNU/Linux ** Affects: yelp (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug -- Some nroff macros are not recognised by yelp https://bugs.launchpad.net/bugs/195150 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to yelp in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 195150] Re: Some nroff macros are not recognised by yelp
** Attachment added: Dependencies.txt http://launchpadlibrarian.net/12174561/Dependencies.txt ** Attachment added: ProcMaps.txt http://launchpadlibrarian.net/12174562/ProcMaps.txt ** Attachment added: ProcStatus.txt http://launchpadlibrarian.net/12174563/ProcStatus.txt -- Some nroff macros are not recognised by yelp https://bugs.launchpad.net/bugs/195150 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to yelp in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 195153] [NEW] Yelp take a lot of ressource
Public bug reported: Binary package hint: yelp Yelp just take a lot of resource for nothing. Steps to reproduce : 1. Just open yelp 2. Start 'top' and see yelp consuming 80% of your cpu (hardware dependant) There is something wrong there. ** Affects: yelp (Ubuntu) Importance: Undecided Status: New -- Yelp take a lot of ressource https://bugs.launchpad.net/bugs/195153 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to yelp in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 189448] [NEW] Nibbles is buggy
Public bug reported: Binary package hint: gnome-games Just unplayable. Step to reproduce : - start any game at any level - go into a wall. =You'll lose all your points, while you should lose only one and restart = You'll continue to play, and you'll be able to cross all walls and users as you want. ProblemType: Bug Architecture: i386 Date: Wed Feb 6 01:41:49 2008 DistroRelease: Ubuntu 8.04 Package: gnome-games 1:2.21.90-0ubuntu1 PackageArchitecture: i386 SourcePackage: gnome-games Uname: Linux flo-laptop 2.6.24-5-generic #1 SMP Thu Jan 24 19:45:21 UTC 2008 i686 GNU/Linux ** Affects: gnome-games (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug -- Nibbles is buggy https://bugs.launchpad.net/bugs/189448 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug contact for gnome-games in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 189448] Re: Nibbles is buggy
** Attachment added: Dependencies.txt http://launchpadlibrarian.net/11784278/Dependencies.txt -- Nibbles is buggy https://bugs.launchpad.net/bugs/189448 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug contact for gnome-games in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 132357] Re: files with unusual character sets are sometimes completely invisible to the driver : locale not set correctly
miraks, palbarra , what the result of : $cat /etc/default/locale Make sure that you have the locale installed for your language (in SystemAdministrationLanguage Support) and set to default. Vangelis Tasoulas, does it works if you set greek as default in SystemAdministrationLanguage Support ? -- files with unusual character sets are sometimes completely invisible to the driver : locale not set correctly https://bugs.launchpad.net/bugs/132357 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug contact for gnome-panel in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 131475] Re: brasero fails to lock cd writer
** Also affects: sound-juicer (Ubuntu) Importance: Undecided Status: New -- brasero fails to lock cd writer https://bugs.launchpad.net/bugs/131475 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug contact for sound-juicer in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 131475] Re: Sound-juicer don't unlock drive on exit : brasero fails to lock cd writer
** Summary changed: - brasero fails to lock cd writer + Sound-juicer don't unlock drive on exit : brasero fails to lock cd writer ** Description changed: - Binary package hint: brasero + Binary package hint: sound-juicer + + sound-juicer lock drive at startup via hal , but it only unlock it when ejecting the drive, + and so when you exit normally, the drive is still locked. + A consequence is that applications that respect this lock, like brasero, refuse to go ahead. + + Original report : Brasero keeps moaning that the cd writer is locked and refuses to write. Other tools like k3b and gnomes build in cd burner works. ** Summary changed: - Sound-juicer don't unlock drive on exit : brasero fails to lock cd writer + Sound-juicer don't unlock drive on exit : brasero fails to burn -- Sound-juicer don't unlock drive on exit : brasero fails to burn https://bugs.launchpad.net/bugs/131475 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug contact for sound-juicer in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 131475] Re: Sound-juicer don't unlock drive on exit : brasero fails to burn
** Description changed: Binary package hint: sound-juicer sound-juicer lock drive at startup via hal , but it only unlock it when ejecting the drive, and so when you exit normally, the drive is still locked. A consequence is that applications that respect this lock, like brasero, refuse to go ahead. + Step to reproduce : + + - Start sound-juicer (even if you don't have a CD on your drive) + - Exit it normaly. + - Insert a blank CD in your drive + - Normaly you should have a dialog that ask you if you want to burn an audio + CD or a data CD, but here you have nothing : the drive is locked (you can also check that with hal-device-manager). + - Start brasero or burn:/// and try to burn something : it will fail. + Serpentine will work, but it's only because it don't respect the lock state. + Original report : Brasero keeps moaning that the cd writer is locked and refuses to write. Other tools like k3b and gnomes build in cd burner works. -- Sound-juicer don't unlock drive on exit : brasero fails to burn https://bugs.launchpad.net/bugs/131475 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug contact for sound-juicer in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 131475] Re: Sound-juicer don't unlock drive on exit : brasero fails to burn
Attach is a patch that remove the lock feature from sound-juicer. At this state of Gutsy, it's might be too intrusive to create a patch that make sure that the drive is unlocked whatever sound-juicer is exited normally or crash. For now, it's better to make sure that the drive is not locked at all by sound-juicer. Anyway, this is not something that useful. It's quite uncommon to burn a CD while extracting music from it. And since the default audio CD burner application Serpentine don't respect this lock state, this is not useful at all. ** Attachment added: 03-dont_lock_drive.patch http://launchpadlibrarian.net/9860618/03-dont_lock_drive.patch -- Sound-juicer don't unlock drive on exit : brasero fails to burn https://bugs.launchpad.net/bugs/131475 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug contact for sound-juicer in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 131475] Re: Sound-juicer don't unlock drive on exit : brasero fails to burn
** Bug watch added: GNOME Bug Tracker #484535 http://bugzilla.gnome.org/show_bug.cgi?id=484535 ** Also affects: sound-juicer via http://bugzilla.gnome.org/show_bug.cgi?id=484535 Importance: Unknown Status: Unknown -- Sound-juicer don't unlock drive on exit : brasero fails to burn https://bugs.launchpad.net/bugs/131475 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug contact for sound-juicer in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 92099] Re: Mounted Drives do not appear in Desktop or Disk Mounter
*** This bug is a duplicate of bug 73227 *** ** This bug has been marked a duplicate of bug 73227 [feisty] some partitions do not appear in Places menu -- Mounted Drives do not appear in Desktop or Disk Mounter https://launchpad.net/bugs/92099 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 73227] Re: [feisty] some partitions do not appear in Places menu
Martin, is there any plan to change that in feisty, or do you want to keep the current behaviour ? -- [feisty] some partitions do not appear in Places menu https://launchpad.net/bugs/73227 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 85795] Re: Internal error failed to inialize HAL !
This bug might be https://launchpad.net/ubuntu/+source/update- notifier/+bug/81670 Try to logout/login, and see if you still get the error. Thanks. -- Internal error failed to inialize HAL ! https://launchpad.net/bugs/85795 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 85125] Re: ntfs drive not appearing on gnome
*** This bug is a duplicate of bug 73227 *** I believe that this is an other duplicate of 73227. Tell me if you think that this is an other problem. Thanks ** This bug has been marked a duplicate of bug 73227 [feisty] some partitions do not appear in Places menu -- ntfs drive not appearing on gnome https://launchpad.net/bugs/85125 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 81670] Re: failed to initialize HAL : gdm init script priority should be at least equal to dbus one
Hum, misread your comment, but anyway, sudo /etc/init.d/dbus restart should be taken with caution. It's always better to restart gnome in that case. -- failed to initialize HAL : gdm init script priority should be at least equal to dbus one https://launchpad.net/bugs/81670 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 81670] Re: failed to initialize HAL : gdm init script priority should be at least equal to dbus one
Restarting the all dbus init scripts during a gnome session, could stop support for some working service (like avahi in your case). The minimal should be to restart hal : sudo /etc/dbus-1/events.d/20hal restart The best is to simply restart gnome. -- failed to initialize HAL : gdm init script priority should be at least equal to dbus one https://launchpad.net/bugs/81670 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 83035] Re: Disk-Mounter applet does not show all partitions
*** This bug is a duplicate of bug 73227 *** ** This bug has been marked a duplicate of bug 73227 [feisty] some partitions do not appear in Places menu -- Disk-Mounter applet does not show all partitions https://launchpad.net/bugs/83035 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 76936] Re: [Feisty] Fails to display some mounted local partitions
*** This bug is a duplicate of bug 73227 *** ** This bug has been marked a duplicate of bug 73227 [feisty] some partitions do not appear in Places menu -- [Feisty] Fails to display some mounted local partitions https://launchpad.net/bugs/76936 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 73227] Re: [feisty] some partitions do not appear in Places menu
** Description changed: In feisty, volumes that are mounted from fstab with the options defaults and/or auto are ignored and in consequence don't show up in place and in computer:// This is a different behavior from dapper or edgy, where all partitions, mounted or not, where present in computer://. People were used to that and it was IMO a good behavior. I also don't see why we should ignore those volumes. And if there is a reason, the rule is wrong cause a volume could be mounted with or without the defaults option with no change for the user, but with a different behavior in the desktop. - I suggest to revert the ignored volume policy to the one before 0.5.8.1-3ubuntu6 : + I suggest to revert the ignored volume policy to the one before + 0.5.8.1-3ubuntu6, with some modification, to not show only fixed + partitions which are not mounted in /media : + In the ignored_volume patch, replace : !-- Ignore fixed partitions which are automatically mounted from fstab -- match key=linux.fstab.mountpoint exists=true merge key=volume.ignore type=boolfalse/merge match key=linux.fstab.options contains=defaults merge key=volume.ignore type=booltrue/merge /match match key=linux.fstab.options contains=auto merge key=volume.ignore type=booltrue/merge /match match key=linux.fstab.options contains=noauto merge key=volume.ignore type=boolfalse/merge /match /match by : !-- Ignore fixed partitions which are not mounted in /media -- match key=@block.storage_device:storage.hotpluggable bool=false match key=@block.storage_device:storage.removable bool=false match key=volume.is_mounted bool=true merge key=volume.ignore type=booltrue/merge !-- Show /media/ drives -- match key=volume.mount_point compare_gt=/media match key=volume.mount_point copare_lt=/media0 merge key=volume.ignore type=boolfalse/merge /match /match /match /match /match -- [feisty] some partitions do not appear in Places menu https://launchpad.net/bugs/73227 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 73227] Re: [feisty] some partitions do not appear in Places menu
** Description changed: In feisty, volumes that are mounted from fstab with the options defaults and/or auto are ignored and in consequence don't show up in place and in computer:// This is a different behavior from dapper or edgy, where all partitions, mounted or not, where present in computer://. People were used to that and it was IMO a good behavior. I also don't see why we should ignore those volumes. And if there is a reason, the rule is wrong cause a volume could be mounted with or without the defaults option with no change for the user, but with a different behavior in the desktop. - I suggest that we remove those bits from the ignored_volume patch : + I suggest to revert the ignored volume policy to the one before 0.5.8.1-3ubuntu6 : + In the ignored_volume patch, replace : + !-- Ignore fixed partitions which are automatically mounted from fstab -- match key=linux.fstab.mountpoint exists=true merge key=volume.ignore type=boolfalse/merge match key=linux.fstab.options contains=defaults merge key=volume.ignore type=booltrue/merge /match match key=linux.fstab.options contains=auto merge key=volume.ignore type=booltrue/merge /match match key=linux.fstab.options contains=noauto merge key=volume.ignore type=boolfalse/merge /match /match + + by : + + match key=@block.storage_device:storage.hotpluggable bool=false + match key=@block.storage_device:storage.removable bool=false + merge key=volume.ignore type=booltrue/merge + + match key=volume.is_mounted bool=true + !-- Show /media/ drives -- + match key=volume.mount_point compare_gt=/media + match key=volume.mount_point compare_lt=/media0 + merge key=volume.ignore type=boolfalse/merge + /match + /match + /match -- [feisty] some partitions do not appear in Places menu https://launchpad.net/bugs/73227 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 73227] Re: [feisty] some partitions do not appear in Places menu
** Description changed: In feisty, volumes that are mounted from fstab with the options defaults and/or auto are ignored and in consequence don't show up in place and in computer:// This is a different behavior from dapper or edgy, where all partitions, mounted or not, where present in computer://. People were used to that and it was IMO a good behavior. I also don't see why we should ignore those volumes. And if there is a reason, the rule is wrong cause a volume could be mounted with or without the defaults option with no change for the user, but with a different behavior in the desktop. I suggest to revert the ignored volume policy to the one before 0.5.8.1-3ubuntu6 : In the ignored_volume patch, replace : !-- Ignore fixed partitions which are automatically mounted from fstab -- match key=linux.fstab.mountpoint exists=true merge key=volume.ignore type=boolfalse/merge match key=linux.fstab.options contains=defaults merge key=volume.ignore type=booltrue/merge /match match key=linux.fstab.options contains=auto merge key=volume.ignore type=booltrue/merge /match match key=linux.fstab.options contains=noauto merge key=volume.ignore type=boolfalse/merge /match /match by : - + !-- Ignore fixed partitions which are not mounted in /media -- match key=@block.storage_device:storage.hotpluggable bool=false match key=@block.storage_device:storage.removable bool=false - merge key=volume.ignore type=booltrue/merge - - match key=volume.is_mounted bool=true - !-- Show /media/ drives -- + match key=volume.is_mounted bool=true + merge key=volume.ignore type=booltrue/merge + !-- Show /media/ drives -- match key=volume.mount_point compare_gt=/media - match key=volume.mount_point compare_lt=/media0 - merge key=volume.ignore type=boolfalse/merge - /match - /match + match key=volume.mount_point copare_lt=/media0 + merge key=volume.ignore type=boolfalse/merge + /match + /match /match + /match + /match -- [feisty] some partitions do not appear in Places menu https://launchpad.net/bugs/73227 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 57626] Re: Network Monitor icons are horizontally stretched
Please give me the output of : apt-cache madison gnome-netstatus-applet remove and readd the applet and confirm that it works or not. If it don't work, install http://flomertens.keo.in/debian/gnome-netstatus-applet_false_i386.deb remove and readd the applet and confirm that it works or not. Thanks -- Network Monitor icons are horizontally stretched https://launchpad.net/bugs/57626 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 57626] Re: Network Monitor icons are horizontally stretched
Be sure that you have 2.12.1-0ubuntu2 it should fix it -- Network Monitor icons are horizontally stretched https://launchpad.net/bugs/57626 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 57626] Re: Network Monitor icons are horizontally stretched
It seams that this bug come back today with the new gnome-netstatus ** Changed in: gnome-netstatus (Ubuntu) Status: Fix Released = Unconfirmed -- Network Monitor icons are horizontally stretched https://launchpad.net/bugs/57626 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 57626] Re: Network Monitor icons are horizontally stretched
Ok, so it appears that the fix was dropped because it wasn't in a patch. enable frank patch fix the issue. I provide a debdiff in case : ** Attachment added: debdiff_ubuntu1-ubuntu2 http://librarian.launchpad.net/6424726/debdiff_ubuntu1-ubuntu2 -- Network Monitor icons are horizontally stretched https://launchpad.net/bugs/57626 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 81670] Re: failed to initialize HAL with automated login
I don't see any reason why it should be update-notifier fault : There is a real problem if hal is started after gnome, what seams to be the case ** Changed in: update-notifier (Ubuntu) Status: Unconfirmed = Rejected -- failed to initialize HAL with automated login https://launchpad.net/bugs/81670 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 81670] Re: failed to initialize HAL with automated login
I think this bug is due to a problem in the init script priority : - gdm start with S13 - dbus (and so hal) start with S20 In the majority of the case there is no problem. But if you use automated login and if there a script between the 2 that take some time, it might fail. I suggest that priority of gdm should be at least the same as dbus (20) or, to be more safe, greeter (21 or something) ** Changed in: hal (Ubuntu) Sourcepackagename: hal = gdm -- failed to initialize HAL : gdm init script priority should be at least equal to dbus one https://launchpad.net/bugs/81670 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 69160] Re: hal failed to initialize
RGilbert, this bug might be a duplicate of 81670. Do you have the same problem when logout/login (no restart) ? -- hal failed to initialize https://launchpad.net/bugs/69160 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 81670] Re: failed to initialize HAL : gdm init script priority should be at least equal to dbus one
** Summary changed: - failed to initialize HAL with automated login + failed to initialize HAL : gdm init script priority should be at least equal to dbus one -- failed to initialize HAL : gdm init script priority should be at least equal to dbus one https://launchpad.net/bugs/81670 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 81670] Re: failed to initialize HAL : gdm init script priority should be at least equal to dbus one
Hal is use by a lot different pieces in the desktop, so if it isn't update-notifier that shows up this message, it will be show by something else. So what is important is not to improve the update-notifier message, but to make hal running properly before gnome start. -- failed to initialize HAL : gdm init script priority should be at least equal to dbus one https://launchpad.net/bugs/81670 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 84642] Wrong usage for the init script
Public bug reported:
Binary package hint: hal
This is a little issue but still annoying.
Using a wrong argument or no argument to the hal init script,
give you the following argument :
* Usage: /etc/init.d/hald {start|stop|restart|force-reload}
which is wrong and should be :
* Usage: /etc/dbus-1/event.d/20hal {start|stop|restart|force-reload}
** Affects: hal (Ubuntu)
Importance: Undecided
Status: Unconfirmed
--
Wrong usage for the init script
https://launchpad.net/bugs/84642
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 73227] Re: [feisty] some partitions do not appear in Places menu
This issue is due to : hal-0.5.8.1/fdi/policy/10osvendor/20-storage-methods.fdi : [...] !-- Ignore fixed partitions which are automatically mounted from fstab -- match key=linux.fstab.mountpoint exists=true merge key=volume.ignore type=boolfalse/merge match key=linux.fstab.options contains=defaults merge key=volume.ignore type=booltrue/merge /match match key=linux.fstab.options contains=auto merge key=volume.ignore type=booltrue/merge /match match key=linux.fstab.options contains=noauto merge key=volume.ignore type=boolfalse/merge /match /match [...] Volume mounted in fstab with defaults and/or auto option are ignored which is something wrong in my opinion. People are used to see their devies (mounted or not) in computer:// and i don't see any reason why we should ignore those drives. -- [feisty] some partitions do not appear in Places menu https://launchpad.net/bugs/73227 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
