Bug#461820: iceweasel: Crashes with BadAlloc on www.howtoforge.com
The problem is with this image: www.howtoforge.com/themes/htf_glass/images/bg_header_bottom_left15.png It is 10.000 pixels wide (very ugly hack). It is a bug in the page (I'll try to report it to howtoforge), but gecko shouldn't have any problem displaing it (less than a megapixel). And I think it _is_ a security risk, as it could lend to a DoS as reported above. -- Rubén Rodríguez GNU no es UNIX! http://es.gnu.org
Bug#441830: package is empty
Package: squashfs-modules-2.6.22-2-686 Version: 2.6.22+3.2r2-1 The package (in sid by now) don't actually include the module: http://packages.debian.org/sid/squashfs-modules-2.6.22-2-686/i386/filelist live-initramfs and live-cd's may fail too -- Rubén Rodríguez Pérez -- GNU España http://es.gnu.org -- Este mensaje ha sido analizado por MailScanner en busca de virus y otros contenidos peligrosos, y se considera que está limpio.
Bug#354582: Nautilus does not list fstab devices in computer:///
El Martes, 28 de Febrero de 2006 08:43, Josselin Mouette escribió:
Le mardi 28 février 2006 à 00:09 +0100, Rubén Rodríguez Pérez a écrit :
sda6 is a fixed sata drive. the results are the same with hda* and hdb*
(my fstab is quite long so I send you only a line as example).
I'm working in a live cd, so users can mount disks by hand. However,
removing the flag, or changing the mount point to /media don't work.
GNOME only lists mounts handled by HAL, not all mounts, in the
computer:/// location. That's purely intentional, because you can't tell
whether /foobar is a user-specific drive or not.
You mean internal drives are not visible in desktop? That's really a new (and
strange) behavior!
If I force downgrade the package (ONLY this package), and left all the rest
exactly like it is now, then I can see both removables and internal drives in
the desktop, nautilus and apps, and I dont even have to reboot, restart hald,
or even restart gnome. Thats what I (and I think _all_ users) I whant.
I think you are not getting me. If I list computer:/// with gnomevfs-ls then I
only see removable devices, network and filesystem, like this example
[EMAIL PROTECTED]:/# gnomevfs-ls computer:///
Filesystem.desktop (Regular, application/x-desktop)size 0
mode 0444
Network.desktop (Regular, application/x-desktop)size 0 mode
0444
Disquetera.drive(Regular, application/x-desktop)size 0
mode 0444
Unidade%20CD-RW%2FDVD%C2%B1R.drive (Regular,
application/x-desktop)size 0 mode 0444
I can see removables, but not my hd* and sd*
And it _only_ happens if hald is not running. If hald is NOT runing then I
have this output:
[EMAIL PROTECTED]:/# gnomevfs-ls computer:///
Filesystem.desktop (Regular, application/x-desktop)size 0
mode 0444
Network.desktop (Regular, application/x-desktop)size 0 mode
0444
sda6.drive (Regular, application/x-desktop)size 0 mode
0444
So, I cannot see my fixed drives, only removables. Yes, I can go to /mnt using
nautilus, but it is not the way it should work: fixed drives should be in
computer:///location, and I cannot get it working!
For what you are trying to achieve, you can either:
* remove the noauto and user options for your partition, and mount
it with a specific umask and gid, adding users that can access
it to that group;
In the examples, drive sda6 is mounted with this fstab line
/dev/sda6 /mnt/sda6 ext3 auto,gid=1000,umask=000 0 0
* write a specific udev rule to make /dev/sda6 belong to hal.
That's almost so stupid as adding hal to disk group.
Using lshal I get this about sda6:
udi =
'/org/freedesktop/Hal/devices/volume_uuid_40f86157_3921_440d_8f8f_b82622404c6e'
volume.unmount.valid_options = {'lazy'} (string list)
volume.mount.valid_other_fs = {'subfs'} (string list)
volume.mount.valid_options = {'ro', 'sync', 'dirsync', 'noatime',
'nodiratime', 'noexec', 'quiet'} (string list)
org.freedesktop.Hal.Device.Volume.method_execpaths =
{'hal-system-storage-mount', 'hal-system-storage-unmount',
'hal-system-storage-eject'} (string list)
org.freedesktop.Hal.Device.Volume.method_signatures = {'ssas', 'as', 'as'}
(string list)
org.freedesktop.Hal.Device.Volume.method_names = {'Mount', 'Unmount',
'Eject'} (string list)
info.interfaces = {'org.freedesktop.Hal.Device.Volume'} (string list)
volume.ignore = false (bool)
volume.policy.desired_mount_point = 'scsidisk' (string)
volume.policy.mount_filesystem = 'ext3' (string)
volume.policy.should_mount = true (bool)
info.udi =
'/org/freedesktop/Hal/devices/volume_uuid_40f86157_3921_440d_8f8f_b82622404c6e'
(string)
volume.partition.msdos_part_table_type = 131 (0x83) (int)
info.product = 'Volume (ext3)' (string)
volume.size = 190061512704 (0x2c408c8800) (uint64)
volume.num_blocks = 371213892 (0x16204644) (int)
volume.block_size = 512 (0x200) (int)
volume.partition.number = 6 (0x6) (int)
info.capabilities = {'volume', 'block'} (string list)
info.category = 'volume' (string)
volume.is_partition = true (bool)
volume.is_disc = false (bool)
volume.is_mounted = true (bool)
volume.mount_point = '/mnt/sda6' (string)
volume.label = '' (string)
volume.uuid = '40f86157-3921-440d-8f8f-b82622404c6e' (string)
volume.fsversion = '1.0' (string)
volume.fsusage = 'filesystem' (string)
volume.fstype = 'ext3' (string)
storage.model = '' (string)
block.storage_device =
'/org/freedesktop/Hal/devices/storage_serial_L59AR23G' (string)
block.is_volume = true (bool)
block.minor = 6 (0x6) (int)
block.major = 8 (0x8) (int)
block.device = '/dev/sda6' (string)
linux.hotplug_type = 3 (0x3) (int)
info.parent =
'/org/freedesktop/Hal/devices/storage_serial_L59AR23G' (string)
linux.sysfs_path_device = '/sys/block/sda/sda6' (string)
linux.sysfs_path = '/sys/block/sda/sda6
Bug#354582: Nautilus does not list fstab devices in computer:///
I think I've found the error. /schemas/system/storage/display_internal_hard_drives is set to default=false in schemas/system_storage.schemas /schemas/system/storage/display_scsi_drives is set to false too. That way users have to open gconf-editor and modify the config by hand. Both should be set to true. Regards. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#354582: Nautilus does not list fstab devices in computer:///
That's why a lot of users are switching to gnome: easy usability. You know... Nobody want to see they drives in a place named computer, that is confusing. What users want (specially newbies from windows) is going to /etc/fstab, look in a manual what's the difference between sda and hdb and all that crap, look the mountpoints, and go to that place using nautilus. Nautilus is crap anyway. we should replace it with bash. I am packaging a live debian distro, a thing that tries to improve usability of debian for newbies. It gererates the fstab, and configurates all the system. But I will have to put a red advertence in the box YOUR DISKS LIVE IN /MNT; YOU WINDOWS MORON. That will help. Regards -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#354582: Nautilus does not list fstab devices in computer:///
Package: libgnomevfs2-common Version: 2.12.2-6 Severity: grave When hald is running, you cannot see fstab devices in computer:/// (you cannot see the icons in the desktop or nautilus, or list the devices with gnomevfs-ls), but you can see, mount and umount hotplug devices. If you kill hald, then you can see fstab devices, but not the hotplug ones. Downgrading the package (forced, downgrading _only_ this package) to 2.10 fixes the problem, so it is not a misconfiguraion in hald or gconf. Examples: Runing hald [EMAIL PROTECTED]:/tmp# gnomevfs-ls computer:/// Filesystem.desktop (Regular, application/x-desktop) size 0 mode 0444 Network.desktop (Regular, application/x-desktop)size 0 mode 0444 Disquetera.drive(Regular, application/x-desktop) size 0 mode 0444 Unidad%20CD-RW%2FDVD%C2%B1R.drive (Regular, application/x-desktop)size 0 mode 0444 -- Not running hald [EMAIL PROTECTED]:/tmp# gnomevfs-ls computer:/// Filesystem.desktop (Regular, application/x-desktop) size 0 mode 0444 Network.desktop (Regular, application/x-desktop)size 0 mode 0444 sda6.drive (Regular, application/x-desktop)size 0 mode 0444 hdc.volume (Regular, application/x-desktop)size 0 mode 0444 -- It don't matter if the devices are mounted or not, and I've tried to add hal to group disks. Hal-device-manager info is ok. Restarting dbus (consecuently restarting hald) in a started gnome session results in devices showing up in nautilus and desktop. my fstab looks like this: /dev/sda6 /mnt/sda6 ext3 noauto,user 0 0 don't matter if I change the opts to auto or remove the user flag -- System Information: Debian Release: testing/unstable APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 'experimental') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.15trisquel Locale: LANG=es_ES, LC_CTYPE=es_ES (charmap=ISO-8859-1) Versions of packages libgnomevfs2-common depends on: ii gconf22.12.1-9 GNOME configuration database syste ii gnome-mime-data 2.4.2-1base MIME and Application database ii shared-mime-info 0.16-3 FreeDesktop.org shared MIME databa libgnomevfs2-common recommends no packages. -- no debconf information I'm using latest dbus, hal, gnome and gnomevfs from unstable hal 0.5.6-4 dbus0.60-6 capplets-data 2.12.3-2 file-roller 2.12.2-2 gconf2 2.12.1-9 gconf2-common 2.12.1-9 gnome-about 2.12.2-2 gnome-applets 2.12.3-1 gnome-applets-data 2.12.3-1 gnome-control-center2.12.3-2 gnome-core 2.12.2.2 gnome-desktop-data 2.12.2-2 gnome-games 2.12.3-1 gnome-games-data2.12.3-1 gnome-icon-theme2.12.1-2 gnome-keyring-manager 2.12.0-1 gnome-media 2.12.0-3 gnome-netstatus-applet 2.12.0-5 gnome-panel 2.12.3-1 gnome-panel-data2.12.3-1 gnome-session 2.12.0-4 gnome-terminal 2.12.0-2 gnome-terminal-data 2.12.0-2 gnome-themes2.12.3-1 gnome-utils 2.12.2-3 libeel2-2 2.12.2-3 libgconf2-4 2.12.1-9 libgnome2-0 2.12.0.1-5 libgnome2-common2.12.0.1-5 libgnome2.0-cil 2.8.0-1 libgnomeprint2.2-0 2.12.1-3 libgnomeprint2.2-data 2.12.1-3 libgnomeprintui2.2-02.12.1-2 libgnomeprintui2.2-common 2.12.1-2 libgnomeui-02.12.1-1 libgnomeui-common 2.12.1-1 libgnomevfs2-0 2.12.2-6 libgnomevfs2-bin2.12.2-6 libgnomevfs2-common 2.12.2-6 libgnomevfs2-extra 2.12.2-6 libpanel-applet2-0 2.12.3-1 nautilus2.12.2-2 python-gnome2 2.12.3-2 python-gnome2-extras2.12.1-2.1 python2.3-gnome22.12.3-2 python2.3-gnome2-extras 2.12.1-2.1 python2.4-gnome22.12.3-2 sound-juicer2.12.3-3 vino2.12.0-1 yelp2.12.2-2 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#354582: Nautilus does not list fstab devices in computer:///
O lun, 27-02-2006 ás 18:17 +0100, Josselin Mouette escribiu: severity 354582 normal thanks Le lundi 27 février 2006 à 15:08 +0100, Rubén Rodríguez Pérez a écrit : When hald is running, you cannot see fstab devices in computer:/// (you cannot see the icons in the desktop or nautilus, or list the devices with gnomevfs-ls), but you can see, mount and umount hotplug devices. If you kill hald, then you can see fstab devices, but not the hotplug ones. Removable drives are still seen anyway, as you can see for your CD drive. Thats what I mean with hotplug devices. You can rename the bug to Nautilus does not list non-removable devices in computer:/// My cd drive is not listed in the fstab. It don't matter if the devices are mounted or not, and I've tried to add hal to group disks. That's pretty stupid. You shouldn't give anything access to the disk group. If it is stupid, don't write it in the README.debian Anyway that file is outdated since --retain-privileges is not used anymore. Hal-device-manager info is ok. Restarting dbus (consecuently restarting hald) in a started gnome session results in devices showing up in nautilus and desktop. What do you mean? sda6 appears in this case? Exactly that. sda* and hda* appears in the desktop, but removables dissapear. I think killing hald cuts the comunnication with gnome-vfs-daemon. If I kill that process it starts again. Then fixed discs disappear and removables returns as when the gnome session was started. my fstab looks like this: /dev/sda6 /mnt/sda6 ext3 noauto,user 0 0 don't matter if I change the opts to auto or remove the user flag What is sda6 exactly? Is it a removable drive? If it is a removable drive, this is an issue in the kernel or udev. If it isn't, why are you making it user-mountable? sda6 is a fixed sata drive. the results are the same with hda* and hdb* (my fstab is quite long so I send you only a line as example). I'm working in a live cd, so users can mount disks by hand. However, removing the flag, or changing the mount point to /media don't work. with this fstab of mt other computer, it didn't work: /dev/hda1 /media/hda1 ntfs auto,exec,ro,umask=000 0 0 /dev/hda5 /mnt/hda5 xfs auto,exec 0 0 /dev/hda7 /mnt/hda7 reiserfs auto,exec 0 0 /dev/hda8 /mnt/hda8 vfat auto,user,umask=000 0 0 By the way, what is your udev version? Latest unstable. All versions used was listed in the first mail. Regards, Best Regards.
