[Bug 272970] Re: Floppy drive doesn't work from file manager
I can confirm this bug with 9.10 with a floppy drive, with a pre-release version as of 8th July 2009. The floppy issue is not related to bug #255651 as it persists if floppy is added to /etc/modules. Steps to replicate: Boot machine. Floppy Drive isn't shown in nautilus. lsmod | grep floppy shows no results. try mount /media/floppy Gives result: either mount: can't find /media/floppy in /etc/fstab or /etc/mtab OR mount: special device /dev/fd0 doesn't exist. So to overcome these scenarios, add line to fstab: /dev/fd0 /media/floppy0 auto rw,user,noauto 0 0 add line to /etc/modules: floppy reboot the above is related to bug #255651 However, the following is unrelated to that bug: Now that we have a module installed in the kernel and an appropriate fstab line, we can issue the command mount /media/floppy the floppy contents will appear when floppy is clicked in nautilus. Click the unmoiunt icon in Nautilus, the floppy unmounts. There is no way to mount the floppy in nautilus. Clicking on floppy drive will not cause the disc to mount. Unless the user reverts to the command line and issues a mount command, the user will not be able to use the floppy disc with nautilus. The user can unmount the floppy within nautilus. I expect nautilus would have a method to issue a system mount command for the floppy as the user. ** Summary changed: - Floppy drive doesn't work from file manager + Nautilus will not mount floppy 9.10 ** Package changed: ubuntu = nautilus (Ubuntu) ** Changed in: nautilus (Ubuntu) Status: Incomplete = Confirmed -- Nautilus will not mount floppy 9.10 https://bugs.launchpad.net/bugs/272970 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 137247] Re: libpam-keyring broken on autologins
On a fresh install of 9.04, I set up a wireless network. Set my account to auto-login. Whenever I start machine, I get a dialog that nm-applet wants access to keyring, enter password. I want the machine to start up, take me to the desktop, and connect to the network without troubling me for passwords. There were no obvious ways to make the machine behave as I wanted. I had to go to Launchpad, search for bugs, read several bug reports until I found a method of working around the default behaviour by following the steps Doug Holton followed, above. The default behaviour is certainly buggy to me. I expect to set up a wireless network connection and have it auto- connect without asking for a password, whether or not I have auto-login enabled. And if it doesn't auto-connect, it should be simple and intuitive for the user to make it auto-connect. -- libpam-keyring broken on autologins https://bugs.launchpad.net/bugs/137247 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gdm in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 128934] evolution outlook web access only works on port 80
Public bug reported: Binary package hint: evolution I have found it necessary to run exchange / outlook web access (OWA) on port 81 so that port 80 may be redirected to a web server. There may also be instances where connections to multiple exchange servers are required through the same IP address. This will require port re-mapping for OWA/Exchange. Outlook and OWA web services are usable when assigned to port 81, and presumably other random port numbers. Evolution does not appear to function when pointed to OWA on ports other than 80. Steps to reproduce bug: 1) Determine evolution works correctly with default setup; Configure Exchange to listen to port 80. Create account on Evolution, pointing to outlook web access url. Verify Evolution connects to OWA services. 2) Verify bug: Delete previously created account from Evolution. Set exchange server to listen to port 81. Create account on Evolution, pointing to outlook web access url eg http://myexchangeserver.com:81/exchange Click verify, enter password. Verification appears to complete OK. When Evolution attempts to connect to exchange server, a dialog box appears saying Error while Scanning folders in /servver/var/spool/mail/nick/. Could not scan folder `/servver/var/spool/mail/nick': No such file or directory 3) Verify exchange is working properly. by a) Pointing a web browser to the port 81 URL, check web access functions. Point outlook to exchange URL. Verify outlook functions. It appears the backend to evolution connecting to exchange is hard-wired to connect to port 80. The back end should connect to whatever port is specified in the OWA URL. ** Affects: evolution (Ubuntu) Importance: Undecided Status: New -- evolution outlook web access only works on port 80 https://bugs.launchpad.net/bugs/128934 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug contact for evolution in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 118745] Re: Font sizes in Gutsy are vulnerable to bad X.org DPI detection
Hello Andreas Presumably your fonts scaled to 75dpi but displayed on your 96dpi screen. They were therefore not displayed as an 11pt font but instead displayed as an 8.5pt font. Now the dpi is presumably detected correctly, it is displayed, as set, at 11pt. As you rightly say, there is a matter of taste how big you would like to see your fonts on screen. But having the system set up so that it does not know the resolution of your screen is not a good way to achieve the desired result. Putting it another way, if your screen were really 75dpi, you would probably again find the fonts too big. Once screen dpi is correctly detected and set on the majority of systems, if users find the fonts are then too big, bugs can be filed against Gnome/KDE for more appropriate default font sizes. In the meantime, you can adjust your menu font sizes to your preferred size in the control panel. -- Font sizes in Gutsy are vulnerable to bad X.org DPI detection https://bugs.launchpad.net/bugs/118745 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 118745] Re: Font sizes in Gutsy are vulnerable to bad X.org DPI detection
Hello Patrice How did you sett he DPI for your system? For my 17 TFT monitor, I set screen size and hence DPI in xorg.conf like: Section Monitor Identifier Generic Monitor Option DPMS HorizSync 30-65 VertRefresh 50-75 DisplaySize 340 270 EndSection However, Bryce Harrington has been making excellent progress with bullet proof X, which should autodetect all relevant settings, which could ultimately eliminate the need for xorg.conf on most machines. I installed Ubuntu Gutsy T2 on a 2.5 hard drive, deleted xorg.conf then swapped it between 8 very different laptops. On all systems, I had a screen which was potentially usable to at least install the system and manually configure the resolution etc (once the front end will accommodate higher than fall-back settings in fall-back situations). I have logged info from these laptops including lspci -v, xorg.0.log, /proc/bus, dmesg, lsmod. If anyone knows how this information can best be used, please let me know! -- Font sizes in Gutsy are vulnerable to bad X.org DPI detection https://bugs.launchpad.net/bugs/118745 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 118745] Re: Font sizes in Gutsy are vulnerable to bad X.org DPI detection
As an update to my suggestion to have the DPI settable in a Gnome interface, I suggest replacing the DPI drop-down box that I previously suggested, with a screen size drop-down box. And add two fields for width and height. If anything other than user defined is selected, the width and height boxes are greyed/inactive and display the current auto-detected width and height, or the width and height associated with the option manually selected. If User Defined is selected, the width and height boxes are black, activated and editable. User can change those values to any sensible value. I'd suggest AutoDetect 12 14 14 widescreen 15 15 widescreen 17 17 widescreen 19 19 widescreen User Defined How do we handle situations where the user has not selected either a resolution or screen size, and no detection information is available? Normally, we would want to assume the user is using the most common screen size of the day which is 17”. We need to consider whether this would work when a user is trying to install a system using a 'fall-back' resolution such as 640x480 or 800x600 whether or not screen size info is available. We are faced with several competing factors: 1)Will the font sizes be readable with default settings? 2)Will the system be installable with default settings? 3)Will the screen be set to the “correct” size? I suggest that when we are set to a fall-back resolution, 3 doesn't matter. Readability and installability are the prime factors. The user can set his or her preferences later, once installed. We also need to ensure the ubiquity installer is usable with fall-back resolutions, at least, 800x600. I therefore suggest that if the screen resolution detected via DDC is 800x600 or less, we should ignore the screen size reported by DDC if less than 14” and assume 14”. (We don't want high DPI values at 800x600 resolution as this will often lead to the ubiquity application window growing too large for the screen, and other applications growing ungainly). I have made a flowchart which demonstrates logical steps to end up with a resolution, refresh rate and screen size from xorg.conf, gnome settings and DDC as outlined above. ** Attachment added: screen_res_flowchart.png http://launchpadlibrarian.net/8329646/screen_res_flowchart.png -- Font sizes in Gutsy are vulnerable to bad X.org DPI detection https://bugs.launchpad.net/bugs/118745 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 118745] Re: Font sizes in Gutsy are vulnerable to bad X.org DPI detection
I have a switch box. The switch box doesn't appear to send DDC signals through, whether or not the monitor is live when X starts. If I start X with the monitor connected directly to the computer, X sets DPI at 95, 96 . If the monitor is not connected, it sets the DPI at 75. At 75dpi, the fonts are usually intolerably small. The most common screen resolutions/sizes tend to be (appx) : Diagonal Width Height ResolutionWxH DPI 14.1 11.28 8.46 1024X768 90.5 90.5 15 12 9 1024x768 85 85 17 13.25 10.65 1280x1024 97 96 19 14.8 11.85 1280x1024 86 86 The most common resolution today is probably 17 1280x1024. for desktops, and something close to 14.1 1024x768 for laptops. The weighted average is probably around 92dpi. We must assume that it is not always possible to determine the monitor's characteristics - any of them. Screen size, H/V sync, max resolution, DPI. Where no information is available, we need to set sensible defaults so that the user can at least get something on screen to make initial changes.. If the user has not set preferences (ie all fields are on autodetect in the attached example) and we have no DDC information whatsoever, AND no settings have been put in xorg.conf, then 800x600,60Hz75dpi is a sensible default. However, if a resolution has been set and a DPI has not been set, I suggest we have an automatic DPI mapping based on the highest resolution axis as follows: 700 56dpi(eg 640x480) 950 75dpi(eg 800x600) 1200 85dpi(eg 1024x768) 1400 95dpi(eg 1280x1024) 1400 100dpi.(eg 1440x1024) Whenever display settings changes are made within Gnome, I suggest we also store the mtime for file /etc/X11/xorg.conf. If xorg.conf exists, and the time stamp differs, then all settings in Gnome should be re-set to Autodetect / default. Otherwise, Gnome settings should take precedence. This way, if the user does dpkg-reconfigure xserver-xorg, the settings will take precedence. If the user then logs into Gnome then changes settings, they then take precedence. So we have an order of precedence for each parameter Res, Freq, DPI: Resoution 1) The most recently changed of Gnome or xorg.conf 2) DDC 3) 800x600 Frequency (refresh rate) 1) The most recently changed of Gnome or xorg.conf 2) DDC 3) 60Hz DPI: 1) The setting in Gnome 2) DDC 3) 700 56dpi(eg 640x480) 950 75dpi(eg 800x600) 1200 85dpi(eg 1024x768) 1400 95dpi(eg 1280x1024) 1400 100dpi.(eg 1440x1024) ** Attachment added: Image of example resolution/DPI/Frequency box http://launchpadlibrarian.net/8281386/resolutionexample.png -- Font sizes in Gutsy are vulnerable to bad X.org DPI detection https://bugs.launchpad.net/bugs/118745 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 32126] Re: sleep shortcut belongs to gnome-power-manager
It is a bug for the desktop infrastructure to handle keyboard events for suspend and hibernate. Users of all desktops and users of console will want consistent power saving keyboard shortcuts. The desktop environment should just write the settings to a config file and let a script make changes to the system on boot-up or on settings change. -- sleep shortcut belongs to gnome-power-manager https://launchpad.net/bugs/32126 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 32126] Need key combo for sleep WAS: sleep shortcut belongs to gnome-power-manager
As part of an energy (environment) saving drive, I have migrated to Ubuntu dapper from sarge on my main machine mainly because there is better support for suspend and hibernate. Sadly, the (newer) unbranded keyboards which feature power keys are of poor quality; I can't get on with them. Many newer keyboards also still lack power buttons. Given that BIOSes often allow an alias to the wake-up button (ctrl+Fx), there is no need for the power buttons so long as the OS can respond to some other key combination to put the machine in a user-configurable power saving state. In gnome power management-general, the sleep button can be configured to suspend the machine. I need to be able to set some other key combination as an alias for the sleep button. Perhaps configure ctrl+Fx to put the machine into suspend mode. -- sleep shortcut belongs to gnome-power-manager https://launchpad.net/bugs/32126 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
