[Touch-packages] [Bug 1346355] Re: 14.04 power-cog does not turn red when restart is needed
Matthew Paul Thomas said: The red icon dates from the era when the rightmost menu was a device menu, trying to cover everything from attached printers to external displays to software updates to screen locking, which was absurd. Nowadays everything to do with software updates is integrated into Software Updater, including the restart notification. It will sometimes be true that the alert appears when it's not a good time to restart; but you can leave it open (even minimized) until you're ready. Your explanation makes no sense, Matthew. The power-cog is where users go to shutdown/restart their computer. If a RESTART is needed, this is the perfect place to advertise it. The user does not know that it needs to update. The user knows a RESTART is needed, for whatever reason. As far as the user is concerned, the update process is over/done. Users that update in the background (like my parents) don't understand the process. The only thing they understand was that when it was red (and red lettering appears in the Power-Cog, you restart. They never restart their computer anymore since I moved them to 14.04. Which means they aren't getting kernel updates. Your rationalization that everything Update-Related be kept away from the Power-Cog is misguided and flawed because the update is DONE, it's been set. The only step that remains is to perform a procedure that the user needs to go to the Power-Cog to accomplish. That is, the user is not UPDATING, they are RESTARTING. The decision to change the red icon was a poor choice and per your explanation the logic surrounding the decision is not in accordance with good design principle nor user-use patterns. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity in Ubuntu. https://bugs.launchpad.net/bugs/1346355 Title: 14.04 power-cog does not turn red when restart is needed Status in The Session Menu: Invalid Status in “unity” package in Ubuntu: Invalid Bug description: In ubuntu 12.04 the power-cog turned red when a reboot/restart was needed. This was a helpful feature because it informed users that they needed to restart the computer. But this helpful indicator is gone in 14.04 and it has resulted in me never remembering to restart my computer because there is no helpful feedback from ubuntu that a restart is needed. In 14.04, I will perform an update and a popup tells me a Restart is needed but I usually select to restart-later because I am in the middle of working. By the the time I am done working I have forgotten that a restart is needed. Later when I am working again a popup occurs informing me that a restart is needed (but again I am in the middle of working so I don't restart). Bottom line: when the power-cog turned red, it reminded me that I needed to restart the computer. When I finished my work I look up and see the red power-cog and Oh yeah, I need to restart. Now is a good time. In 14.04 this doesn't happen. Instead I'm perpetually bugged by a popup (which is useless because it's never a good time to restart when it pops up). The red power-cog was a much BETTER design choice. The removal of the power-cog turning red has negatively affected the management of ubuntu updates and it should be fixed so that it behaves like 12.04. To manage notifications about this bug go to: https://bugs.launchpad.net/indicator-session/+bug/1346355/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1346355] Re: 14.04 power-cog does not turn red when restart is needed
Thanks for the reply, Matthew. 1) closing and opening the lid to cause sleep is unrelated to this matter. Regardless of Suspend use, if a user intends to shutdown/restart the computer, the power-cog is where the GUI user is going to go. If a user never shuts down or restarts unless explicitly prompted, that does NOT change the fact that the power-cog is the GUI area where this is accomplished. It is not meaningless to them to futz with the cog icon. It makes perfect sense as this is the location that restart/shutdown is accomplished. 2) it is a poor design decision to use popups to communicate that a restart is needed. It is not done in the normal Ubuntu method of communicating information (i.e., displaying a rectangular box in the upper right corner of the screen). Instead the popup is reminiscent of popups from the world wide web. Something few people appreciate. And if the popup box is closed (whether on purpose or by mistake), where does the user have to go to restart? The cog icon. Both my parents did not understand that the popup icon demanding restart was from Ubuntu. Both my parents did (intuitively) understand however that the red cog icon was a communication from Ubuntu telling them something. And when they clicked the red icon they saw in red lettering what was needed from them. MUCH BETTER DESIGN. Canonical/Ubuntu is overall very good at design choices. But this popup choice for restart is a regression. Hopefully you guys can/will reconsider it? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity in Ubuntu. https://bugs.launchpad.net/bugs/1346355 Title: 14.04 power-cog does not turn red when restart is needed Status in The Session Menu: Invalid Status in “unity” package in Ubuntu: Invalid Bug description: In ubuntu 12.04 the power-cog turned red when a reboot/restart was needed. This was a helpful feature because it informed users that they needed to restart the computer. But this helpful indicator is gone in 14.04 and it has resulted in me never remembering to restart my computer because there is no helpful feedback from ubuntu that a restart is needed. In 14.04, I will perform an update and a popup tells me a Restart is needed but I usually select to restart-later because I am in the middle of working. By the the time I am done working I have forgotten that a restart is needed. Later when I am working again a popup occurs informing me that a restart is needed (but again I am in the middle of working so I don't restart). Bottom line: when the power-cog turned red, it reminded me that I needed to restart the computer. When I finished my work I look up and see the red power-cog and Oh yeah, I need to restart. Now is a good time. In 14.04 this doesn't happen. Instead I'm perpetually bugged by a popup (which is useless because it's never a good time to restart when it pops up). The red power-cog was a much BETTER design choice. The removal of the power-cog turning red has negatively affected the management of ubuntu updates and it should be fixed so that it behaves like 12.04. To manage notifications about this bug go to: https://bugs.launchpad.net/indicator-session/+bug/1346355/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1346355] Re: 14.04 power-cog does not turn red when restart is needed
** Description changed: + Bug = the restart-popup-dialog that sometimes occurs after a system- + update should only run once. If the user declines to reboot from the + popup, then the power-cog should turn red until reboot occurs. Repeated + popups asking to reboot should not occur. + In ubuntu 12.04 the power-cog turned red when a reboot/restart was needed. This was a helpful feature because it informed users that they needed to restart the computer. But this helpful indicator is gone in 14.04 and it has resulted in me never remembering to restart my computer because there is no helpful feedback from ubuntu that a restart is needed. In 14.04, I will perform an update and a popup tells me a Restart is needed but I usually select to restart-later because I am in the middle of working. By the the time I am done working I have forgotten that a restart is needed. Later when I am working again a popup occurs informing me that a restart is needed (but again I am in the middle of working so I don't restart). Bottom line: when the power-cog turned red, it reminded me that I needed to restart the computer. When I finished my work I look up and see the red power-cog and Oh yeah, I need to restart. Now is a good time. In 14.04 this doesn't happen. Instead I'm perpetually bugged by a popup (which is useless because it's never a good time to restart when it pops up). The red power-cog was a much BETTER design choice. The removal of the power-cog turning red has negatively affected the management of ubuntu updates and it should be fixed so that it behaves like 12.04. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity in Ubuntu. https://bugs.launchpad.net/bugs/1346355 Title: 14.04 power-cog does not turn red when restart is needed Status in The Session Menu: Invalid Status in “unity” package in Ubuntu: Invalid Bug description: Bug = the restart-popup-dialog that sometimes occurs after a system- update should only run once. If the user declines to reboot from the popup, then the power-cog should turn red until reboot occurs. Repeated popups asking to reboot should not occur. In ubuntu 12.04 the power-cog turned red when a reboot/restart was needed. This was a helpful feature because it informed users that they needed to restart the computer. But this helpful indicator is gone in 14.04 and it has resulted in me never remembering to restart my computer because there is no helpful feedback from ubuntu that a restart is needed. In 14.04, I will perform an update and a popup tells me a Restart is needed but I usually select to restart-later because I am in the middle of working. By the the time I am done working I have forgotten that a restart is needed. Later when I am working again a popup occurs informing me that a restart is needed (but again I am in the middle of working so I don't restart). Bottom line: when the power-cog turned red, it reminded me that I needed to restart the computer. When I finished my work I look up and see the red power-cog and Oh yeah, I need to restart. Now is a good time. In 14.04 this doesn't happen. Instead I'm perpetually bugged by a popup (which is useless because it's never a good time to restart when it pops up). The red power-cog was a much BETTER design choice. The removal of the power-cog turning red has negatively affected the management of ubuntu updates and it should be fixed so that it behaves like 12.04. To manage notifications about this bug go to: https://bugs.launchpad.net/indicator-session/+bug/1346355/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1346355] Re: 14.04 power-cog does not turn red when restart is needed
Let me first draw attention to the edit I made to my initial Bug Description: I have expanded the Bug scope to the fact that the popup- dialog repeats itself AND the power-cog icon does not turn red. After a system updates, only one restart-popup should present (it serves informational purposes while offering the user with an immediate way to reboot, should they want to). If the user declines this popup, then the power-cog should turn red and no further popups asking for restart should present at any time. Matthew, many of the examples you use do not bolster the case for a repeating popup-dialog. When a battery is getting moderately low, the battery status icon goes red. This is as it should be. When the battery is critically low (and your computer is going to turn itself off or change its runlevel state), you get a dialog. This is as it should be. When you update your system and a restart is needed (but your computer is not going to change its runlevel state if you fail to interact with the dialog) the dialog is purely informational and offering a choice. If the user declines to reboot, the appropriate response is to give a red icon indicating the need to address the issue at a later time, like when the battery is moderately low. Likewise, when I am connected to Wi-Fi, the icon changes, as it should. When I need to enter a Wi-Fi password, it is because I am trying to connect to Wi-Fi. That intention cannot happen unless I enter a password. Hence a dialog. The analogy here is that after a system is updated, one can argue that the update cannot fully happen unless the user reboots. But this is not true in the sense that the reboot has to happen at that very moment. The system will finish the update whenever the system is next rebooted; hence, the important thing is the user be made aware of the need to reboot. With respect to the Wi-Fi password, the user cannot access Wi-Fi unless they enter the Wi-Fi password. It's something that has to happen at that very moment. Many of your arguments appear to gloss over or ignore an important principle in Unity design. Of course if someone never shuts down or restarts unless explicitly prompted, shutdown and restart will never occur at the power-cog. But this is a moot point. For someone who only shuts down and restarts from the power-cog, the only place the events occur is at the power-cog. The point is in the conformity to the overall design of Unity. The indicators in the right-corner of the top panel (along with NotifyOSD) is the informational hub in Unity for system- related matters. This is basic Unity design principle. This is where system-related messages SHOULD present. You seem to be arguing that how one particular user may choose to use the system warrants ignoring this design criteria/principle of Unity. If the system needs to be rebooted to accomplish something, this longterm state should to be communicated to users via the established Unity design principle of a red system- indicator. Many people hate popups when Google Docs use them. And they hate them when advertisements use them. And they hate them when they land at a website and the screen grays and there's some stupid popup telling them to Like them on Facebook (forcing them to click an X to get rid of the popup). Popups should only present when input is REQUIRED to prevent a change in runlevel or to complete a REQUIRED objective to achieve said state (i.e., something that will disrupt what the user is trying to accomplish at that moment). Other popups are nothing more than nuisances and serve mostly as an interruption. A popup announcing that a reboot is needed may be a permissible exception because it is informational while simultaneously serving as a shortcut to accomplish the act. If the user chooses not to reboot, however, repeating the popup-dialog is introducing a nuisance and needlessly interrupting the work of Ubuntu users while simultaneously failing to utilize the proper communication channels that Unity Design Principles stipulate. The power-cog turning red is the appropriate way to handle the communication of the system's state in this regard. ** Description changed: - Bug = the restart-popup-dialog that sometimes occurs after a system- - update should only run once. If the user declines to reboot from the - popup, then the power-cog should turn red until reboot occurs. Repeated - popups asking to reboot should not occur. + Bug = a popup-dialog asking the user to reboot the system after an + update should not repeat (popup again) at a later time if the user + chooses not to reboot. Instead, the power-cog should turn the color red + and no further popup-dialogs should present at any time. In ubuntu 12.04 the power-cog turned red when a reboot/restart was needed. This was a helpful feature because it informed users that they needed to restart the computer. But this helpful indicator is gone in 14.04 and it has resulted in me never remembering to restart my computer
[Touch-packages] [Bug 1425991] Re: Networks I have never connected to should be confined to the More Networks folder
as Shahbaz points out, most of the time, Ubuntu will connect automatically to one of the networks you have connected to before. So most of the time, if you open the menu to connect to a Wi-Fi network, it is to connect to a network that you have *not* connected to before. It would be counterproductive, then, to show by default only networks that you *have* connected to before. No, this is not accurate. 1) there are lots of users who do not want networks connecting automatically, so they manually select the network they want. 2) even if Ubuntu is set to automatically connect to networks, if there are more than one network in range that a user regularly connects to, he/she HAS to manually select the network because Ubuntu does not know which network to automatically connect to. Except the way Ubuntu currently works, the user is forced to wade through unknown networks to single out the network/s they have previously connected to in the past. 3) there are other reasons to access the network-indicator besides connecting to a network. And having NEVER-USED, NEVER-WILL-USE networks taking up space in the drop-down is not a smart design choice 4) there is no good reason NOT to confine networks you have never connected to the More networks folder or an Unknown networks folder. Demarcating networks like this makes it easier on the user because it helps identify to the user which networks they have and have-not connected to in the past. And it allows simplified presentation of the network-indicator menu; it also aides user memory of what networks they have connected to in the past without forcing them to visit the Edit Connections section of the network-indicator menu. Networks are already demarcated into the More networks folder. But there is little logic to why they are put in the folder. Add some logic and understanding to the placement of networks in this folder, logic that the User immediately understands. Where you have previously connected to more than one of the networks in range, the menu prioritizes showing these ones, ahead of showing networks that you have not connected to before. After that, it prioritizes the strongest other networks, minimizing the probability that the network you want isn't at the top level. https://wiki.ubuntu.com/Networking#wi-fi-menu No, this is untrue. I regularly have to fish out the network I want at the bottom of the network-indicator dropdown list because other networks are placed above it in the list (networks I have never connected to and never will connect to). for example, you may not remember whether you used the Wi-Fi the last time you were at this particular cafe/airport/etc, so you may not remember whether the network is known or not. And having two lists of networks, separated by other functional items, would be rather inelegant. What? You do not understand what I am reporting as the bug. If you fix the bug I am reporting, the user would immediately know whether he/she used the network in the past because Ubuntu would display it in the network-indicator dropdown. The network was connected to before, so it would show up in the network-indicator list. If the network has NEVER been connected to before, it will only show in the More networks folder or the Unknown networks folder. Having networks list in the network-indicator list that the user will NEVER connect to and has NEVER connected to in the past is what is inelegant and screws with the user's memory. In my proposal, the user does not have to remember whether the network is known or not. Ubuntu tells the user the network is known (or connected to before) because it is not listing it in the Unknown networks folder. Let me restate what you need to do to fix this problem: Networks that have never been connected to in the past should not directly display in the network-indicator drop-down. Instead, they should be confined to a folder that says Unknown Networks. If a connection has been made to the network in the past, then the network should directly display in the network-indicator drop-down. Part of adapting the phone Wi-Fi settings to the PC will, I hope, be introducing the ability to arrange previous networks in order of preference. Once that is done, I don't think there will be any point in also letting you confine/blacklist networks. This bug reports the inelegant and inefficient organziation and handling of wifi networks that currently exists in Ubuntu. It should be fixed as soon as possible. Currently, every time a user wants to connect to a network, he/she has to hunt through a list of networks that perpetually show but that the user will NEVER EVER connect to. What sense does this make to force this on Ubuntu users? Every user on earth will immediately understand to look in the More Networks folder or a folder called Unknown Networks for networks that they have not connected to in the past. And then once the user has connected to a network that network will display in the
[Touch-packages] [Bug 1425991] Re: Networks I have never connected to should be confined to an Unknown Networks folder
** Description changed: When a user clicks the network manager indicator, a dropdown appears and lists wifi networks. This menu should NOT display networks that the user has never connected to. Networks the user has never connected to should - only display in the More networks folder. At a mininum, the user - should be given the ability to confine unwanted networks in the More - networks folder. + only display in a folder called Unknown Networks. At a mininum, the + user should be given the ability to prevent networks from cluttering up + the indicator menu. It is an unproductive design choice to force users to have to wade through networks they have never connected to (networks they will never - connect to) in their menu. Numerous reasons exist why a user will not - use the Auto-Connect setting for wireless networks. So it makes sense - and is more efficient to have the menu only display the networks the - user makes active use of and no more. + connect to) in their menu. Even if a user makes use of the Auto-Connect + setting for wireless networks, only displaying known networks in the + indicator dropdown allows a visual reference of available networks the + user can connect to. If the user is interested in connecting to an + unknown (or never before connected-to network), the user can explore a + folder that contains such networks. It makes sense and is more efficient + to have the menu only display the networks the user makes active use of + and no more. When I click on the Network Manager Indicator and select Edit Connections and then look under the Wifi heading, only a couple networks appear. So why do 5 or more networks (networks I have never connected to, networks I never will connect to) perpetually show in the Network Indicator menu? They should not be displayed like they are. They - should be confined to the More networks folder. Alternatively, there - should be a way to manually confine/sandbox unwanted networks to this - folder so they no longer display in the dropdown menu. + should be confined to a folder called Unknown Networks. In the interest of providing a visual example of what I am talking about, here is a picture of some networks I would like to hide/remove from my Network Indicator menu. http://a.pomf.se/fdqlnn.png ** Description changed: When a user clicks the network manager indicator, a dropdown appears and lists wifi networks. This menu should NOT display networks that the user has never connected to. Networks the user has never connected to should only display in a folder called Unknown Networks. At a mininum, the user should be given the ability to prevent networks from cluttering up the indicator menu. It is an unproductive design choice to force users to have to wade through networks they have never connected to (networks they will never connect to) in their menu. Even if a user makes use of the Auto-Connect setting for wireless networks, only displaying known networks in the indicator dropdown allows a visual reference of available networks the - user can connect to. If the user is interested in connecting to an - unknown (or never before connected-to network), the user can explore a - folder that contains such networks. It makes sense and is more efficient - to have the menu only display the networks the user makes active use of - and no more. + user can connect to. If the user is in the vicinity of a free network or + at a friend's house and has the password to a network he/she has never + connected to before, this network would be unknown (because it has never + been connected to before). So the user would browse the Unknown + Networks folder to identify the SSID. Once connected to, from then on + the network would directly display in the Network-Indicator dropdown + list. It makes sense and is more efficient to have the menu only display + the networks the user makes active use of and no more. When I click on the Network Manager Indicator and select Edit Connections and then look under the Wifi heading, only a couple networks appear. So why do 5 or more networks (networks I have never connected to, networks I never will connect to) perpetually show in the Network Indicator menu? They should not be displayed like they are. They should be confined to a folder called Unknown Networks. In the interest of providing a visual example of what I am talking about, here is a picture of some networks I would like to hide/remove from my Network Indicator menu. http://a.pomf.se/fdqlnn.png -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-network in Ubuntu. https://bugs.launchpad.net/bugs/1425991 Title: Networks I have never connected to should be confined to an Unknown Networks folder Status in indicator-network package in Ubuntu: New Bug description: When a user clicks the network manager indicator, a
[Touch-packages] [Bug 1425991] Re: Networks I have never connected to should be confined to an Unknown Networks folder
@ James Anslow, no because it's not signal strength that defines the significance of the network to the user. The user is making connection decisions based on the identity of the network. Even in a context where a user is trying to select between several free networks, signal strength may or may not be an important consideration. Personally, I value my appraisal of the trust worthiness of the network over signal strength. And signal strength is a non-factor in a trusted context, for example your home. The neighbors may be blasting their WAP at max strength and you have reduced your WAP's strength because you are in a small apartment or something. So your network would appear at the bottom of the list, being crowded out by the stronger signals. Yet you have never connected to your neighbors' networks and you likely never will. So why should these networks display perpetually in a regular-use area of your menu? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-network in Ubuntu. https://bugs.launchpad.net/bugs/1425991 Title: Networks I have never connected to should be confined to an Unknown Networks folder Status in indicator-network package in Ubuntu: New Bug description: When a user clicks the network manager indicator, a dropdown appears and lists wifi networks. This menu should NOT display networks that the user has never connected to. Networks the user has never connected to should only display in a folder called Unknown Networks. At a mininum, the user should be given the ability to prevent networks from cluttering up the indicator menu. It is an unproductive design choice to force users to have to wade through networks they have never connected to (networks they will never connect to) in their menu. Even if a user makes use of the Auto- Connect setting for wireless networks, only displaying known networks in the indicator dropdown allows a visual reference of available networks the user can connect to. If the user is in the vicinity of a free network or at a friend's house and has the password to a network he/she has never connected to before, this network would be unknown (because it has never been connected to before). So the user would browse the Unknown Networks folder to identify the SSID. Once connected to, from then on the network would directly display in the Network-Indicator dropdown list. It makes sense and is more efficient to have the menu only display the networks the user makes active use of and no more. When I click on the Network Manager Indicator and select Edit Connections and then look under the Wifi heading, only a couple networks appear. So why do 5 or more networks (networks I have never connected to, networks I never will connect to) perpetually show in the Network Indicator menu? They should not be displayed like they are. They should be confined to a folder called Unknown Networks. In the interest of providing a visual example of what I am talking about, here is a picture of some networks I would like to hide/remove from my Network Indicator menu. http://a.pomf.se/fdqlnn.png To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-network/+bug/1425991/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1425991] Re: Networks I have never connected to should be confined to an Unknown Networks folder
** Summary changed: - Networks I have never connected to should be confined to the More Networks folder + Networks I have never connected to should be confined to an Unknown Networks folder -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-network in Ubuntu. https://bugs.launchpad.net/bugs/1425991 Title: Networks I have never connected to should be confined to an Unknown Networks folder Status in indicator-network package in Ubuntu: New Bug description: When a user clicks the network manager indicator, a dropdown appears and lists wifi networks. This menu should NOT display networks that the user has never connected to. Networks the user has never connected to should only display in the More networks folder. At a mininum, the user should be given the ability to confine unwanted networks in the More networks folder. It is an unproductive design choice to force users to have to wade through networks they have never connected to (networks they will never connect to) in their menu. Numerous reasons exist why a user will not use the Auto-Connect setting for wireless networks. So it makes sense and is more efficient to have the menu only display the networks the user makes active use of and no more. When I click on the Network Manager Indicator and select Edit Connections and then look under the Wifi heading, only a couple networks appear. So why do 5 or more networks (networks I have never connected to, networks I never will connect to) perpetually show in the Network Indicator menu? They should not be displayed like they are. They should be confined to the More networks folder. Alternatively, there should be a way to manually confine/sandbox unwanted networks to this folder so they no longer display in the dropdown menu. In the interest of providing a visual example of what I am talking about, here is a picture of some networks I would like to hide/remove from my Network Indicator menu. http://a.pomf.se/fdqlnn.png To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-network/+bug/1425991/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1346355] Re: 14.04 power-cog does not turn red when restart is needed
System-related communications should present in the upper-right corner at the indicators. The indicators exist as an interface layer between the System and the User. Application-related communications should present at the Launcher. The requirement that the computer be rebooted is a System-related event; therefore, the communication that this event is needed needs to present at the indicators--not the Launcher, and not some ephemeral popup. If an Application needs to be restarted, then the appropriate communication location would be at the Launcher or within the Application itself. The ONLY instance where a popup should be used is in situations where an IMMEDIATE response is needed to proceed: for example, the user is trying to access something that requires a password. A prompt pops up to allow entering the password. ** Changed in: unity (Ubuntu) Status: Invalid = New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity in Ubuntu. https://bugs.launchpad.net/bugs/1346355 Title: 14.04 power-cog does not turn red when restart is needed Status in The Session Menu: Invalid Status in unity package in Ubuntu: New Bug description: Bug = a popup-dialog asking the user to reboot the system after an update should not repeat (popup again) at a later time if the user chooses not to reboot. Instead, the power-cog should turn the color red and no further popup-dialogs should present at any time. In ubuntu 12.04 the power-cog turned red when a reboot/restart was needed. This was a helpful feature because it informed users that they needed to restart the computer. But this helpful indicator is gone in 14.04 and it has resulted in me never remembering to restart my computer because there is no helpful feedback from ubuntu that a restart is needed. In 14.04, I will perform an update and a popup tells me a Restart is needed but I usually select to restart-later because I am in the middle of working. By the the time I am done working I have forgotten that a restart is needed. Later when I am working again a popup occurs informing me that a restart is needed (but again I am in the middle of working so I don't restart). Bottom line: when the power-cog turned red, it reminded me that I needed to restart the computer. When I finished my work I look up and see the red power-cog and Oh yeah, I need to restart. Now is a good time. In 14.04 this doesn't happen. Instead I'm perpetually bugged by a popup (which is useless because it's never a good time to restart when it pops up). The red power-cog was a much BETTER design choice. The removal of the power-cog turning red has negatively affected the management of ubuntu updates and it should be fixed so that it behaves like 12.04. To manage notifications about this bug go to: https://bugs.launchpad.net/indicator-session/+bug/1346355/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1425991] [NEW] Networks I have never connected to should be confined to the More Networks folder
Public bug reported: When a user clicks the network manager indicator, a dropdown appears and lists wifi networks. This menu should NOT display networks that the user has never connected to. Networks the user has never connected to should only display in the More networks folder. At a mininum, the user should be given the ability to confine unwanted networks in the More networks folder. It is an unproductive design choice to force users to have to wade through networks they have never connected to (networks they will never connect to) in their menu. Numerous reasons exist why a user will not use the Auto-Connect setting for wireless networks. So it makes sense and is more efficient to have the menu only display the networks the user makes active use of and no more. When I click on the Network Manager Indicator and select Edit Connections and then look under the Wifi heading, only a couple networks appear. So why do 5 or more networks (networks I have never connected to, networks I never will connect to) perpetually show in the Network Indicator menu? They should not be displayed like they are. They should be confined to the More networks folder. Alternatively, there should be a way to manually confine/sandbox unwanted networks to this folder so they no longer display in the dropdown menu. In the interest of providing a visual example of what I am talking about, here is a picture of some networks I would like to hide/remove from my Network Indicator menu. http://a.pomf.se/fdqlnn.png ** Affects: indicator-network (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-network in Ubuntu. https://bugs.launchpad.net/bugs/1425991 Title: Networks I have never connected to should be confined to the More Networks folder Status in indicator-network package in Ubuntu: New Bug description: When a user clicks the network manager indicator, a dropdown appears and lists wifi networks. This menu should NOT display networks that the user has never connected to. Networks the user has never connected to should only display in the More networks folder. At a mininum, the user should be given the ability to confine unwanted networks in the More networks folder. It is an unproductive design choice to force users to have to wade through networks they have never connected to (networks they will never connect to) in their menu. Numerous reasons exist why a user will not use the Auto-Connect setting for wireless networks. So it makes sense and is more efficient to have the menu only display the networks the user makes active use of and no more. When I click on the Network Manager Indicator and select Edit Connections and then look under the Wifi heading, only a couple networks appear. So why do 5 or more networks (networks I have never connected to, networks I never will connect to) perpetually show in the Network Indicator menu? They should not be displayed like they are. They should be confined to the More networks folder. Alternatively, there should be a way to manually confine/sandbox unwanted networks to this folder so they no longer display in the dropdown menu. In the interest of providing a visual example of what I am talking about, here is a picture of some networks I would like to hide/remove from my Network Indicator menu. http://a.pomf.se/fdqlnn.png To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-network/+bug/1425991/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1425991] Re: Networks I have never connected to should be confined to the More Networks folder
Well there are several problems with your argument concerning people are too dumb/lazy to read stuff. First, most of the networks already appear in the More networks folder because there are so many. 5 or 6 get shuffled into the visible space from the dozens that live in the More networks folder. So there is a very good chance that the network the person who doesn't read stuff is looking for is going to be listed in the More networks folder anyways. Second, I don't think you give most users enough credit to recognize that the network they are looking for might be in the More networks folder. It makes intuitive sense that Networks they have already connected to will be listed in the visible space. And that a network they have never connected to before would be listed in the More networks folder. Third, none of these arguments explain why there is not a manual way to organize where networks appear. There should be a way to confine unused networks to the More networks folder or blacklist them from the Network indicator menu all together. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-network in Ubuntu. https://bugs.launchpad.net/bugs/1425991 Title: Networks I have never connected to should be confined to the More Networks folder Status in indicator-network package in Ubuntu: Confirmed Bug description: When a user clicks the network manager indicator, a dropdown appears and lists wifi networks. This menu should NOT display networks that the user has never connected to. Networks the user has never connected to should only display in the More networks folder. At a mininum, the user should be given the ability to confine unwanted networks in the More networks folder. It is an unproductive design choice to force users to have to wade through networks they have never connected to (networks they will never connect to) in their menu. Numerous reasons exist why a user will not use the Auto-Connect setting for wireless networks. So it makes sense and is more efficient to have the menu only display the networks the user makes active use of and no more. When I click on the Network Manager Indicator and select Edit Connections and then look under the Wifi heading, only a couple networks appear. So why do 5 or more networks (networks I have never connected to, networks I never will connect to) perpetually show in the Network Indicator menu? They should not be displayed like they are. They should be confined to the More networks folder. Alternatively, there should be a way to manually confine/sandbox unwanted networks to this folder so they no longer display in the dropdown menu. In the interest of providing a visual example of what I am talking about, here is a picture of some networks I would like to hide/remove from my Network Indicator menu. http://a.pomf.se/fdqlnn.png To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-network/+bug/1425991/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1441111] Re: Clicking the nautilus icon for focusing a window of an external device opens a new window instead
This bug also exists in ubuntu 15.04 (Vivid Vervet). -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity in Ubuntu. https://bugs.launchpad.net/bugs/144 Title: Clicking the nautilus icon for focusing a window of an external device opens a new window instead Status in Nautilus: New Status in Unity: New Status in unity package in Ubuntu: Confirmed Bug description: The Launcher icon for Nautilus (whether clicking on the icon or using the shortcut 'Super+1') does not work properly in Ubuntu 14.04 when an external Device is attached to the computer [i.e., when an item appears under the Devices heading in Nautilus' Sidebar (e.g., USB drive).] With all applications except Nautilus, clicking a Launcher icon results in this behavior: 1) if the application is not open, the application is opened. 2) if the application is opened, focus is given to the already opened window. Yet Nautilus does NOT behave this way when an external device is attached to the computer and Nautilus is viewing the contents of that device. For example, if a USB thumb drive is attached to the computer and user is viewing the contents, pressing Super+1 (or clicking the Nautilus icon) to bring focus to an already opened Nautilus window results in a new window being opened so there are a total of 2 Nautilus windows. Some side-effects of this include making it IMPOSSIBLE to close the Nautilus application by clicking the X in the upper left corner of the window unless the user makes use of Alt+Tab to get to the already opened Nautilus window. To illustrate this, do the following: 1) Attach a USB thumb drive to the computer. (I have Never start programs on media insertion enabled so no windows automatically open on my computer). 2) To access the USB drive I just attached, I open Nautilus by clicking the icon in the Launcher. My HOME folder opens. I click on the USB device (that lists under DEVICES in Nautilus' Sidebar) to see what is on the USB drive. 3) I open Firefox by clicking on the Firefox icon in the Launcher. 4) I want to return to the Nautilus window I previously opened, so I click on the Nautilus icon in the Launcher. A NEW NAUTILUS WINDOW OPENS. The correct behavior here is for Ubuntu to give focus to the already opened Nautilus window. 5) If I then click the X in the upper left corner of the window to close nautilus, the window closes but Nautilus is still open. If I click the Nautilus icon to give focus to the open Nautilus Window, IT OPENS A NEW NAUTILUS WINDOW. Clicking the X in this window puts me back where I started. A second window of an application should only be opened 1) if user right-clicks the Launcher icon and selects Open a New Window or 2) if user makes use of the Super+Shift+# shortcut. New windows should NOT be opened from standard left-clicks on the icon. I am reporting this bug on a fully up to date version of Ubuntu 14.04. To manage notifications about this bug go to: https://bugs.launchpad.net/nautilus/+bug/144/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1508468] [NEW] Users are forced to wade through unknown networks to single out the network/s they have previously connected to in the past
Public bug reported: The summary pretty much tells the tale: users are forced to wade through unknown networks to single out the network/s they have previously connected to in the past. I go to a location. Twenty some networks are available. Most of them appear in the "More Networks" folder. Five networks appear outside the "More Networks" folder. Despite the fact that I ONLY EVER connect maybe two networks, other networks that I never ever connect to are always displayed. Why are networks that I have never connected to (and never will connect to) ALWAYS displayed in the menu? Why aren't they confined to the "More Networks" folder until connected to at least one time. Previously, I proposed a solution: confine networks that have NEVER been connected to in the "More Networks" folder. Once a connection has been established, move it out of the "More Networks" folder. I'm told most users allow automatic wifi connections: so users only have to look ONE TIME, the first time they connect to a foreign (never before seen) network. the current system presents two usability problems. If automatic connection is turned on and more than one network has been connected to in the past, the system does not know which network the user wants THIS TIME. And yet the user has to wade through networks they have never connected to and will never connect to to locate the networks they have to connected to in the past (there has to be a better way to organize this). Second, if the user does not allow automatic connections for security/privacy/battery reasons, the user is forced to wade through networks he/she has never connected to and will never connect every time he/she wants to make a wifi connection. Since my previous proposal was shot down, can ubuntu engineers please come up with a solution to this usability problem (as Matthew Paul Thomas has you are more capable of doing). Matthew Paul Thomas has invalidated my "simple" solution that would inconvenience no one: https://bugs.launchpad.net/ubuntu/+source/indicator-network/+bug/1425991 I'm told most users autoconnect. So they want to see the networks right away, but this is nonsense. There are often so many networks, they HAVE to look in "More Networks" anyways. ** Affects: indicator-network (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-network in Ubuntu. https://bugs.launchpad.net/bugs/1508468 Title: Users are forced to wade through unknown networks to single out the network/s they have previously connected to in the past Status in indicator-network package in Ubuntu: New Bug description: The summary pretty much tells the tale: users are forced to wade through unknown networks to single out the network/s they have previously connected to in the past. I go to a location. Twenty some networks are available. Most of them appear in the "More Networks" folder. Five networks appear outside the "More Networks" folder. Despite the fact that I ONLY EVER connect maybe two networks, other networks that I never ever connect to are always displayed. Why are networks that I have never connected to (and never will connect to) ALWAYS displayed in the menu? Why aren't they confined to the "More Networks" folder until connected to at least one time. Previously, I proposed a solution: confine networks that have NEVER been connected to in the "More Networks" folder. Once a connection has been established, move it out of the "More Networks" folder. I'm told most users allow automatic wifi connections: so users only have to look ONE TIME, the first time they connect to a foreign (never before seen) network. the current system presents two usability problems. If automatic connection is turned on and more than one network has been connected to in the past, the system does not know which network the user wants THIS TIME. And yet the user has to wade through networks they have never connected to and will never connect to to locate the networks they have to connected to in the past (there has to be a better way to organize this). Second, if the user does not allow automatic connections for security/privacy/battery reasons, the user is forced to wade through networks he/she has never connected to and will never connect every time he/she wants to make a wifi connection. Since my previous proposal was shot down, can ubuntu engineers please come up with a solution to this usability problem (as Matthew Paul Thomas has you are more capable of doing). Matthew Paul Thomas has invalidated my "simple" solution that would inconvenience no one: https://bugs.launchpad.net/ubuntu/+source/indicator- network/+bug/1425991 I'm told most users autoconnect. So they want to see the networks right away, but this is nonsense. There are often so many networks, they HAVE to look in "More
[Touch-packages] [Bug 1508468] Re: Users are forced to wade through unknown networks to single out the network/s they have previously connected to in the past
This would be a much more efficient and clean network-indicator design arrangement: Wi-Fi Networks -currently connected network Disconnect -previously connected network -previously connected network More Networks -never before connected network -never before connected network -never before connected network -never before connected network -never before connected network -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-network in Ubuntu. https://bugs.launchpad.net/bugs/1508468 Title: Users are forced to wade through unknown networks to single out the network/s they have previously connected to in the past Status in indicator-network package in Ubuntu: New Bug description: The summary pretty much tells the tale: users are forced to wade through unknown networks to single out the network/s they have previously connected to in the past. I go to a location. Twenty some networks are available. Most of them appear in the "More Networks" folder. Five networks appear outside the "More Networks" folder. Despite the fact that I ONLY EVER connect maybe two networks, other networks that I never ever connect to are always displayed. Why are networks that I have never connected to (and never will connect to) ALWAYS displayed in the menu? Why aren't they confined to the "More Networks" folder until connected to at least one time. Previously, I proposed a solution: confine networks that have NEVER been connected to in the "More Networks" folder. Once a connection has been established, move it out of the "More Networks" folder. I'm told most users allow automatic wifi connections: so users only have to look ONE TIME, the first time they connect to a foreign (never before seen) network. the current system presents two usability problems. If automatic connection is turned on and more than one network has been connected to in the past, the system does not know which network the user wants THIS TIME. And yet the user has to wade through networks they have never connected to and will never connect to to locate the networks they have to connected to in the past (there has to be a better way to organize this). Second, if the user does not allow automatic connections for security/privacy/battery reasons, the user is forced to wade through networks he/she has never connected to and will never connect every time he/she wants to make a wifi connection. Since my previous proposal was shot down, can ubuntu engineers please come up with a solution to this usability problem (as Matthew Paul Thomas has you are more capable of doing). Matthew Paul Thomas has invalidated my "simple" solution that would inconvenience no one: https://bugs.launchpad.net/ubuntu/+source/indicator- network/+bug/1425991 I'm told most users autoconnect. So they want to see the networks right away, but this is nonsense. There are often so many networks, they HAVE to look in "More Networks" anyways. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-network/+bug/1508468/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1564135] [NEW] Ubuntu Touch cannot connect to access point that has long wifi password
Public bug reported: There are some wifi access points that I have to connect to for work. They have 63 digit passwords with special characters. Ubuntu Desktop has no problem connecting. But Ubuntu Touch is unable to connect at all. At home, I configured a router with a similar password and Ubuntu cannot connect. If I make the password something like 12 digits, it connects fine. Considering long passwords aid security, this bug should receive higher priority. ** Affects: network-manager (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1564135 Title: Ubuntu Touch cannot connect to access point that has long wifi password Status in network-manager package in Ubuntu: New Bug description: There are some wifi access points that I have to connect to for work. They have 63 digit passwords with special characters. Ubuntu Desktop has no problem connecting. But Ubuntu Touch is unable to connect at all. At home, I configured a router with a similar password and Ubuntu cannot connect. If I make the password something like 12 digits, it connects fine. Considering long passwords aid security, this bug should receive higher priority. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1564135/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1564135] Re: Ubuntu Touch cannot connect to access point that has long wifi password
This bug can be deleted. It appears the problem is the phone cannot connect to 5GHz networks. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1564135 Title: Ubuntu Touch cannot connect to access point that has long wifi password Status in network-manager package in Ubuntu: New Bug description: There are some wifi access points that I have to connect to for work. They have 63 digit passwords with special characters. Ubuntu Desktop has no problem connecting. But Ubuntu Touch is unable to connect at all. At home, I configured a router with a similar password and Ubuntu cannot connect. If I make the password something like 12 digits, it connects fine. Considering long passwords aid security, this bug should receive higher priority. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1564135/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1564135] Re: Ubuntu Touch cannot connect to access point that has long wifi password
This bug is valid after all. It appears that Ubuntu Touch is unable to connect to network that have long passwords. I'm tired of trying but a 16 digit password works. 17-19 I don't know about. If the password is 20 digits or longer, the OS is totally unable to use the Access Point. A major issue as it cannot even connect to a perfectly good network simply because the access point is using a long password. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1564135 Title: Ubuntu Touch cannot connect to access point that has long wifi password Status in network-manager package in Ubuntu: New Bug description: There are some wifi access points that I have to connect to for work. They have 63 digit passwords with special characters. Ubuntu Desktop has no problem connecting. But Ubuntu Touch is unable to connect at all. At home, I configured a router with a similar password and Ubuntu cannot connect. If I make the password something like 12 digits, it connects fine. Considering long passwords aid security, this bug should receive higher priority. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1564135/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
