[Bug 587644] Re: You can't bind the SuperS keyboard shortcut to anything in lucid lynx
Sorry for doing this again, but the bug is back! So the long series of updates I did to Ubuntu packages did not solve this. -- You can't bind the SuperS keyboard shortcut to anything in lucid lynx https://bugs.launchpad.net/bugs/587644 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 587644] Re: You can't bind the SuperS keyboard shortcut to anything in lucid lynx
I want to inform you that the problem has disappeared for me. I can no longer reproduce it. It is a fresh installation of Ubuntu that I have, and I observed that bug before the long list of initial updates you do. Thanks for your help anyway. -- You can't bind the SuperS keyboard shortcut to anything in lucid lynx https://bugs.launchpad.net/bugs/587644 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 587644] [NEW] You can't bind the SuperS keyboard shortcut to anything in lucid lynx
Public bug reported: I can't bind the Supers keyboard shortcut to anything. This isn't doable through SystemPreferencesKeyboard Shortcuts nor trough CompizConfig Settings Manager. When I press this combination I get a menu at the top right of Ubuntu's screen that shows various options for ending the current session (logout, shutdown, restart, etc.). To reproduce the bug: 1. Enter SystemPreferencesKeyboard Shortcuts. 2. Bind Supers (or Mod4+s as it sometime is referred to) to any command that you like. 3. Observe that Supers does not do what you intend it to do. ** Affects: gnome-desktop (Ubuntu) Importance: Undecided Status: New -- You can't bind the SuperS keyboard shortcut to anything in lucid lynx https://bugs.launchpad.net/bugs/587644 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 103187] Re: System startup failed. Commandline was presented. Required manual file system check of the root filesystem. This was not possible to do.
Hello. I know you didn't read it but if you did you would realize that this ain't some bug that you can easily reproduce. Also, it happened a long time ago and I don't have hardy anymore. Well, sorry for writing that much but it was my first report and this was a NASTY bug! -- System startup failed. Commandline was presented. Required manual file system check of the root filesystem. This was not possible to do. https://bugs.launchpad.net/bugs/103187 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 183674] Can not control level of bass through volume control. Bass is too high and unchangeable.
Public bug reported: In ubuntu gusty 7.10, one can not control the level of bass through the volume-control which you access by clicking on the speaker icon on the top right of the screen. Changing the the bass slider has no effect. The VERY BIG problem is that the level of bass is set to a unchangeable value which is way too high. I have a z-680 speaker system. My bass level is set to the lowest level. My room trembles and the roof vibrates when I try to watch a movie. This does not happen in Windows. I have a 5.1 spekaer setting. My sound card is SoundBlaster Audigy. Instructions to encounter the bug: First, you need a speaker system with a subwoofer. 1. Turn on the subwoofer. 2. Start some playback that has bass, such as a DVD movie. 3. Open the volume-control by double clicking the speaker icon to the top right of your screen. 4. Change the slider that controls the amount of bass. You will notice no change. I'm guessing that this has something to do with ALSA. ** Affects: ubuntu Importance: Undecided Status: New -- Can not control level of bass through volume control. Bass is too high and unchangeable. https://bugs.launchpad.net/bugs/183674 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 154104] Re: glxinfo: 'Direct rendering: no' on 915GM video chipset on Gutsy
I really don't think this is a bug it isn't hard to fix neither. Just add Option DRI true in the device section that deals with your graphic card drivers. Yeah, I'm talking about xorg.conf Also, you must add Load dri in your module section. Seriously, doing this is far much better than just copy-paste some other guys xorg.conf! If you ask me that is just crazy! xorg.conf does like hundreds and hundreds of things. If you get luckily and it works, then it is only a matter of time when you get some other problems! Well atleast this worked out fine for me! -- glxinfo: 'Direct rendering: no' on 915GM video chipset on Gutsy https://bugs.launchpad.net/bugs/154104 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 154104] Re: glxinfo: 'Direct rendering: no' on 915GM video chipset on Gutsy
Also, I'm pretty sure that your compiz problem has its roots in something else! Cause my glxinfo also said that direct rendering was not enabled. But I was still able to get compiz running under aiglx. But I must say something else too. I am using ATI 9800, so maybe we are not dealing with the same kind of issue. Sorry if that is true. But I suspect that I'm right since I can't find Option DRI true In Ralph Bonnells xorg.con -- glxinfo: 'Direct rendering: no' on 915GM video chipset on Gutsy https://bugs.launchpad.net/bugs/154104 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 66051] Re: [users-admin] Adding a previously existing user fails silently
Are you rally sure this time? :-) -- [users-admin] Adding a previously existing user fails silently https://bugs.launchpad.net/bugs/66051 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 178621] Re: [7.10 8.04alpha-2 users groups] Can not remove a user and create a new one with the same username as the deleted one. No error message is presented. (Administrative user cannot admini
*** This bug is a duplicate of bug 66051 *** https://bugs.launchpad.net/bugs/66051 I will respond to Stanley Sokolow's comments in bug #66051. -- [7.10 8.04alpha-2 users groups] Can not remove a user and create a new one with the same username as the deleted one. No error message is presented. (Administrative user cannot administer users and groups from System menu.) https://bugs.launchpad.net/bugs/178621 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 66051] Re: [users-admin] Adding a previously existing user fails silently
Respond to Stanley Sokolow's questions. You can read his questions in bug #178621 I looked in /etc/group and /etc/passwd. The user had been deleted from both of them. But the group UbuntuFun (our fictional user account) was still in place. I do not if it is supposed to be deleted or not, but a workaround is to first delete the user account, then delete the group with the same name as the account, and then create a new account with the same username as the deleted one. Tell me if you want to know anything else, but I suspect that this bug appears in any Gutsy and not only on my system. -- [users-admin] Adding a previously existing user fails silently https://bugs.launchpad.net/bugs/66051 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 178621] Can not remove a user and create a new one with the same username as the deleted one. No error message is presented.
Public bug reported: I use Ubuntu 7.10 Gutsy Gibbon. Say that you have a user with username UbuntuFun. First, you delete the user. Then you create a new user with the same username, namely UbuntuFun. You will not be able to do this. You will not receive a proper error message. Reproduce: 1. Go to System-Administration-Users and Groups 2. Mark the (fictional) user with username UbuntuFun in the list, and choose Delete. 3. Confirm your choice. Assumed Intermediate Result: User with username UbuntuFun does no longer exist in the list. 4. Create a new user, by choosing Add User. 5. Choose UbuntuFun as Username. 6. Chose a Real name. 7. Choose a User password. 8. Confirm your choice by typing it once more in Confirm. 9. Confirm your choice of new user by choosing OK. Result: Your new user does not appear in the list of users. You will not receive any error message. Final note: Restarting the application Users and Groups after deleting the old user and before trying to add the new user will not help. A workaround will now be presented. WARNING! KNOW WHAT YOU ARE DOING IF YOU FOLLOW THIS WORKAROUND! Workaround: Do this AFTER you have deleted the old user and BEFORE you try to add the new user. CREATE A BACKUP OF /etc/group IN CASE SOMETHING GOES WRONG. AFTER THAT, Open /etc/group. Remove all rows that declare UbuntuFun as a group. Save your changes. I will try to remember to keep an eye on this report. But please, feel free to terrorize me with e-mails at [EMAIL PROTECTED] in order to catch my attention. I did look through existing bug reports as careful as I could. I found no bug report that mentioned this. I apologize if this has already been reported. ** Affects: ubuntu Importance: Undecided Status: New -- Can not remove a user and create a new one with the same username as the deleted one. No error message is presented. https://bugs.launchpad.net/bugs/178621 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 103187] System startup failed. Commandline was presented. Required manual file system check of the root filesystem. This was not possible to do.
Public bug reported: I have a computer with CPU 3GHz, 512 MB Ram, ATI Radeon PRO 128 MB, HP harddrive. The partitions on the harddrive are /dev/hda1 (FTA32 compact- recovery partition. The size of it is 3.64 GB), /dev/hda2 (NTFS partition running Windows XP. The size of it is 94.4 GB), /dev/hda3 (EXT3 partition running Ubuntu. The size of it is 49.9 GB) and /dev/hda4 (SWAP partition. The size of it is 1 GB). These were also my exact partitions when the bug occurred. I shall now describe what kind of bug it was and how it occurred. I was running Ubuntu Edgy Eft 6.10. I can not remember exactly what programs where running, but it was nothing out of the ordinary. I can recall Mozilla Firefox and Gaim of them. I decided I want to install digiKam. I started the GUI-version of the package manager of Ubuntu. I have forgotten its name. I am referring to the one that does exactly what apt does but provides a GUI. I selected digiKam and confirmed my choice to start the installation. The installation finnished. The package manager stated this and brought it to my attention by the soft silver-orange blinking at the bar at the bottom. I switched to it in order to confirm that the installation was finnished by clicking OK. Once I clicked OK (or shortly after that I clicked OK) the basr at the top and at the bottom of the screen froze. I am referring to the bar at the bottom with all active programs, small thumbnails of running desktops, etc.. I am also referring to the bar at the top with the clock, the menus, the volume-button, etc.. I could not click on their features; they did not respond. The only exception was the Gaim icon at the top right. Clicking on it showed me my running instance of Gaim as it was supposed to. But nothing else (the menus, the desktop-buttons, etc..) responded. Ubuntu was however running. I could still use Firefox, Gaim, etc.. I was even able to start digiKam through a commandline. After a while, I decided that maybe a reboot of the computer would restore the bars at the top and the bottom. I could not use the menu to restart the computer. I pushed the powerbutton on my computer once. The Quit-windows appeared. I chose Restart. The system did not respond. I pushed the power-button again. The Quit-windows appeared again. I once more chose Restart. The system did not respond this time either. I pushed the power-button and kept it pushed for five seconds. The power of the computer went of. I started up the computer. The bot-screen that allows me to choose which partition I want to start up from showed up. I chose my Ubuntu-partition. After a while, the startup-screen showed up. I am referring to the screen that shows the Ubuntu-mark, has the name of Ubuntu on it and shows a progress bar that reflects how much of the startup-process has been accomplished. The progress bar went on filling itself until it reached roughly speaking 20-25%. It then stopped progressing. The startup-screen was completely replaced with text. I have written down parts of this text. I shall now present it here. - - * Checking root file system... /etc/rcS.d/S20checkroot.sh: 407 logsave: not found * An automatic file system check (fsck) of the root file system failed. A manual fsck must be performed in maintenance mode with the root filesystem mounted in read-only mode. - - I did not write down the rest of the text. I shall now try to recall it to the best of my abilities. + I was told that it was required of me to run a fsck manually from a maintenance mode. I was told that I would now enter som sort of maintenance mode. + I was told to press Ctrl+D when I was done. + The system (referring to the thing that was presenting this error and running the computer at the time) was trying to enter some kind of maintenance mode. However, this utterly failed. It tried to execute fuor commands. They both returned a response stating that the command was unavailable, except the first one. The first one stated something like that batch jobs were not available or could not be started. + A commandline, awaiting my input, was presented. I typed fsck and hit enter. The system stated that there was no such command. I also tried typing fsck.ext2 and fsck.ext3. The system stated that there was no such command. I tried these in combination with sudo. The system still gave the same response. Finally, I tried typing sudo fsck.ext3 /dev/hda3. The system gave the very same response. I rebooted the computer by pressing Ctrl+D. The system said something like entering maintenance mode failed. I started the computer from the liveCD that I used to install ubuntu. From the instance of Ubuntu that was running from the CD, i mounted /dev/hda3 and entered it. I entered
[Bug 103187] Re: System startup failed. Commandline was presented. Required manual file system check of the root filesystem. This was not possible to do.
I am the one who wrote this bugreport. I would like to say that in the beginning of the bugreport, I meant to write FAT32 Compaq-recovery partition about my /dev/hda1 partition. I apologize for this misstake, and hope no one got confused. -- System startup failed. Commandline was presented. Required manual file system check of the root filesystem. This was not possible to do. https://bugs.launchpad.net/bugs/103187 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
