[Bug 1278350] Re: Request: show downloadrate
Not sure what you mean with touch images. I was refering to the grafical update-manager, which hardly gives any feedback about the download of package information. In case the network connection is lost the update-manager does not give any feedback about the package information not being updated. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1278350 Title: Request: show downloadrate To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/1278350/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1047384] Re: System Encryption Password set before setting keyboard locale
Ubuntu (gnome) 14.04 beta1 is still affected by this bug, making full disk encryption unuseable for everyone except us keyboard users. (Debian does not seem to have this issue. What do they do different?) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1047384 Title: System Encryption Password set before setting keyboard locale To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1047384/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1278373] Re: keyboard does not work at login
The Issue is still present in the current development version of Ubuntu 14.04 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1278373 Title: keyboard does not work at login To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1278373/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1278359] Re: ntpdate call frequency
Regarding the choice between ntp and ntpdate, I suspect that ntpdate is a smaller package then ntp. Even if configurable as client, ntp still also is a server package. I do not know for sure but this might be the reason behind the use of ntpdate. To raise the sync frequency to several times a day does not seem like a good Idea to me, nor does it really seem necessary as most systems will only suffer minor time fluctuations. If you or anyone needs to sync more often then once per network up I think you should use an individual configuration that applies to your needs. The number of systems that will suffer major time differences is probably very small, even a raspberry pi which does not even have a hardware clock, keeps an acurate time for weeks. Considering that most desktop systems will be booted once a day or every few days, this seems a good configuration as it is. To solve this issue for more individual needs, it might be a good idea to create an option in the ntp (or ntpdate) configuration file, that defines to sync frequency. As far as I know this is not yet the case. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to ntp in Ubuntu. https://bugs.launchpad.net/bugs/1278359 Title: ntpdate call frequency To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ntp/+bug/1278359/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 844317] Re: Killing all remaining processes... [failed]
Workaround: change the wait time from 10 seconds to 5 seconds: /etc/init.d/sendsigs [...] # Kill all processes. log_action_begin_msg Asking all remaining processes to terminate killall5 -15 $OMITPIDS # SIGTERM log_action_end_msg 0 alldead= OMITPIDS0=$OMITPIDS for seq in 1 2 3 4 5 ; do OMITPIDS=$OMITPIDS0 [...] Notice: do not change the time to a lower time, as this might cause more problems -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to rpcbind in Ubuntu. https://bugs.launchpad.net/bugs/844317 Title: Killing all remaining processes... [failed] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rpcbind/+bug/844317/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1278359] Re: ntpdate call frequency
Regarding the choice between ntp and ntpdate, I suspect that ntpdate is a smaller package then ntp. Even if configurable as client, ntp still also is a server package. I do not know for sure but this might be the reason behind the use of ntpdate. To raise the sync frequency to several times a day does not seem like a good Idea to me, nor does it really seem necessary as most systems will only suffer minor time fluctuations. If you or anyone needs to sync more often then once per network up I think you should use an individual configuration that applies to your needs. The number of systems that will suffer major time differences is probably very small, even a raspberry pi which does not even have a hardware clock, keeps an acurate time for weeks. Considering that most desktop systems will be booted once a day or every few days, this seems a good configuration as it is. To solve this issue for more individual needs, it might be a good idea to create an option in the ntp (or ntpdate) configuration file, that defines to sync frequency. As far as I know this is not yet the case. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1278359 Title: ntpdate call frequency To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ntp/+bug/1278359/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 844317] Re: Killing all remaining processes... [failed]
Workaround: change the wait time from 10 seconds to 5 seconds: /etc/init.d/sendsigs [...] # Kill all processes. log_action_begin_msg Asking all remaining processes to terminate killall5 -15 $OMITPIDS # SIGTERM log_action_end_msg 0 alldead= OMITPIDS0=$OMITPIDS for seq in 1 2 3 4 5 ; do OMITPIDS=$OMITPIDS0 [...] Notice: do not change the time to a lower time, as this might cause more problems -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/844317 Title: Killing all remaining processes... [failed] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rpcbind/+bug/844317/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1278365] Re: ntpdate target server
I aggree this issue might be appropriate to be discussed at the mailing list. Also for this reason setting the but to incomplete ** Changed in: ntp (Ubuntu) Status: Invalid = Incomplete -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to ntp in Ubuntu. https://bugs.launchpad.net/bugs/1278365 Title: ntpdate target server To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ntp/+bug/1278365/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1278365] Re: ntpdate target server
Quote: 1. Where are you find a privacy issue? Please read the docu at The issue is based in the name and origin of the target server. Calling ntp.ubuntu cleary tells what kind of OS you are using. This is an increasing issue today 2. The use of ntp.ubuntu.com is IMHO the availability of the ntp - service. Ubuntu can not guarantee the availability of other service providers over the entire term. I did not intent to propose the use of usual public ntp servers. Ubuntu should use a canonical server, but ths server should maybe be used by other clients to to prevent identivication of the System. 3. It is easy to change the ntp server eg via dhcp This does not change that most Systems will still have this issue. Therefore it should be solved by changing the defult behavior. We already point people at the NTP pool: $ cat /etc/ntp.conf ... server 0.ubuntu.pool.ntp.org server 1.ubuntu.pool.ntp.org server 2.ubuntu.pool.ntp.org server 3.ubuntu.pool.ntp.org ... Yes that is correct, but it still contains a pool of ntp servers only used by Ubuntu correct? The Issue might be rendered irrelevant if there are non Ubuntu systems using the ubuntu ntp pool as well. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to ntp in Ubuntu. https://bugs.launchpad.net/bugs/1278365 Title: ntpdate target server To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ntp/+bug/1278365/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1278359] Re: ntpdate call frequency
I agree. Regarding the aspect that most systems will be booted only once a day or less it will probably affect only a few people as it is. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to ntp in Ubuntu. https://bugs.launchpad.net/bugs/1278359 Title: ntpdate call frequency To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ntp/+bug/1278359/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1278387] Re: Private key generation does not work at all
Yes this is a upstream issue. However the seahorse project seems barely active, so if you want to have a working version of seahorse in the next Ubuntu release, you (Ubuntu developer) will need to fix some of those bugs yourself. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1278387 Title: Private key generation does not work at all To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/seahorse/+bug/1278387/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1278392] Re: multiple option settings for lock screen
** Description changed: - The option to set the time bevore activating screen lock is abviable to + The option to set the time before activating screen lock is aviable to be set in the tab privacy and security as well als in brightness - lock leving an inconsistent interface + lock leaving an inconsistent interface also in Security and Pivacy the time options to determin when to lock the sceen after it turned black should contain a 5 and/or 10 second option, as it now only contains the choice between 1 second and 30 Seconds, leaving a big gap. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1278392 Title: multiple option settings for lock screen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/activity-log-manager/+bug/1278392/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1278386] Re: seahorse can only generate pgp keys up to 4096 bit
Correction: since this is rather a functionality request my former post is not correct. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1278386 Title: seahorse can only generate pgp keys up to 4096 bit To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/seahorse/+bug/1278386/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1278386] Re: seahorse can only generate pgp keys up to 4096 bit
Yes this is a upstream issue. However the seahorse project seems barely active, so if you want to have a working version of seahorse in the next Ubuntu release, you (Ubuntu developer) will need to fix some of those bugs yourself. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1278386 Title: seahorse can only generate pgp keys up to 4096 bit To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/seahorse/+bug/1278386/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1278365] Re: ntpdate target server
Quote: 1. Where are you find a privacy issue? Please read the docu at The issue is based in the name and origin of the target server. Calling ntp.ubuntu cleary tells what kind of OS you are using. This is an increasing issue today 2. The use of ntp.ubuntu.com is IMHO the availability of the ntp - service. Ubuntu can not guarantee the availability of other service providers over the entire term. I did not intent to propose the use of usual public ntp servers. Ubuntu should use a canonical server, but ths server should maybe be used by other clients to to prevent identivication of the System. 3. It is easy to change the ntp server eg via dhcp This does not change that most Systems will still have this issue. Therefore it should be solved by changing the defult behavior. We already point people at the NTP pool: $ cat /etc/ntp.conf ... server 0.ubuntu.pool.ntp.org server 1.ubuntu.pool.ntp.org server 2.ubuntu.pool.ntp.org server 3.ubuntu.pool.ntp.org ... Yes that is correct, but it still contains a pool of ntp servers only used by Ubuntu correct? The Issue might be rendered irrelevant if there are non Ubuntu systems using the ubuntu ntp pool as well. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1278365 Title: ntpdate target server To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ntp/+bug/1278365/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1278365] Re: ntpdate target server
I aggree this issue might be appropriate to be discussed at the mailing list. Also for this reason setting the but to incomplete ** Changed in: ntp (Ubuntu) Status: Invalid = Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1278365 Title: ntpdate target server To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ntp/+bug/1278365/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1278359] Re: ntpdate call frequency
I agree. Regarding the aspect that most systems will be booted only once a day or less it will probably affect only a few people as it is. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1278359 Title: ntpdate call frequency To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ntp/+bug/1278359/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1278359] [NEW] ntpdate call frequency
Public bug reported: Currently ntpdate is started every time the network interface changes to up. On systems that have a hardware clock this is not nessesary, causeing unnessesary traffic and load on ntp servers. If easily possible ntpdate shold rather be called daily or weekly via cron, if there is a hardware clock present. (affects all Ubuntu versions) ** Affects: ntp (Ubuntu) Importance: Undecided Status: New ** Description changed: Currently ntpdate is started every time the network interface changes to up. - On systems that have a hardware clock this is not nessesary, causeing unnessesary traffic and load on ntp servers. + On systems that have a hardware clock this is not nessesary, causeing unnessesary traffic and load on ntp servers. If easily possible ntpdate shold rather be called daily or weekly via cron, if there is a hardware clock present. - - (Valid on all Ubuntu versions and ntpdate versions) + (Valid on all Ubuntu versions) ** Description changed: Currently ntpdate is started every time the network interface changes to up. On systems that have a hardware clock this is not nessesary, causeing unnessesary traffic and load on ntp servers. If easily possible ntpdate shold rather be called daily or weekly via cron, if there is a hardware clock present. - (Valid on all Ubuntu versions) + (affects all Ubuntu versions) -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to ntp in Ubuntu. https://bugs.launchpad.net/bugs/1278359 Title: ntpdate call frequency To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ntp/+bug/1278359/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1278365] [NEW] ntpdate target server
Public bug reported: ntpdate calls a ubuntu specific ntp server on network-interface startup. This causes some slight but unnessesary privacy issues as it identifies the client software to anyone listening on the network. This issue can be solved easily by adding the ubuntu/canonical ntp server to a public ntp pool and (maybe) using a more common server name (ntp.canonical instead of ntp.ubuntu) This way there is no privacy issue regaring network traffic and it is a public service by helping public ntp pools ** Affects: ntp (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to ntp in Ubuntu. https://bugs.launchpad.net/bugs/1278365 Title: ntpdate target server To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ntp/+bug/1278365/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1278350] [NEW] Request: show downloadrate
Public bug reported: The new update-manager in Ubuntu 14.04 does not give any feedback about the updating process. It would be very helpfull to have at least something like the downloadrate showing in the main window, to show that the updating process is working. Right now it is not possible to see whether the update is working or not. ** Affects: update-manager (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1278350 Title: Request: show downloadrate To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/1278350/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1278359] [NEW] ntpdate call frequency
Public bug reported: Currently ntpdate is started every time the network interface changes to up. On systems that have a hardware clock this is not nessesary, causeing unnessesary traffic and load on ntp servers. If easily possible ntpdate shold rather be called daily or weekly via cron, if there is a hardware clock present. (affects all Ubuntu versions) ** Affects: ntp (Ubuntu) Importance: Undecided Status: New ** Description changed: Currently ntpdate is started every time the network interface changes to up. - On systems that have a hardware clock this is not nessesary, causeing unnessesary traffic and load on ntp servers. + On systems that have a hardware clock this is not nessesary, causeing unnessesary traffic and load on ntp servers. If easily possible ntpdate shold rather be called daily or weekly via cron, if there is a hardware clock present. - - (Valid on all Ubuntu versions and ntpdate versions) + (Valid on all Ubuntu versions) ** Description changed: Currently ntpdate is started every time the network interface changes to up. On systems that have a hardware clock this is not nessesary, causeing unnessesary traffic and load on ntp servers. If easily possible ntpdate shold rather be called daily or weekly via cron, if there is a hardware clock present. - (Valid on all Ubuntu versions) + (affects all Ubuntu versions) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1278359 Title: ntpdate call frequency To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ntp/+bug/1278359/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1278365] [NEW] ntpdate target server
Public bug reported: ntpdate calls a ubuntu specific ntp server on network-interface startup. This causes some slight but unnessesary privacy issues as it identifies the client software to anyone listening on the network. This issue can be solved easily by adding the ubuntu/canonical ntp server to a public ntp pool and (maybe) using a more common server name (ntp.canonical instead of ntp.ubuntu) This way there is no privacy issue regaring network traffic and it is a public service by helping public ntp pools ** Affects: ntp (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1278365 Title: ntpdate target server To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ntp/+bug/1278365/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1278373] [NEW] keyboard does not work at login
Public bug reported: In Ubuntu 14.04 daily (current versions today) there repeatently appears a bug that makes it impossible to enter a password on login. It is still possible to select another user by mouse but not to enter something in the password field. Rebooting does not help. A workaround is to select and login to guest session and logout again, afterwards it is possible to enter a password again. The but occurs almost everytime after bootup. (lightdm version 1.9.7) ** Affects: lightdm (Ubuntu) Importance: Undecided Status: New ** Description changed: - In Ubuntu 14.04 daily (8.1.) and current versions (today) there - repeatently appears a but that makes it impossible to enter a password - on login. + In Ubuntu 14.04 daily (current versions today) there repeatently appears + a bug that makes it impossible to enter a password on login. It is still possible to select another user by mouse but not to enter something in the password field. Rebooting does not help. A workaround is to select and login to guest session and logout again, afterwards it is possible to enter a password again. The but occurs almost everytime after bootup. ** Description changed: In Ubuntu 14.04 daily (current versions today) there repeatently appears a bug that makes it impossible to enter a password on login. It is still possible to select another user by mouse but not to enter something in the password field. Rebooting does not help. A workaround is to select and login to guest session and logout again, afterwards it is possible to enter a password again. The but occurs almost everytime after bootup. + + (lightdm version 1.9.7) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1278373 Title: keyboard does not work at login To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1278373/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1278381] [NEW] pgp key generation window not present
Public bug reported: In the current version (today) of ubuntu 14.04: seahorse does not show a key generation window when creating a new pgp key, therefore giving no feedback at all about key generation. There also should be a process indicator showing how much of the can has been generated, as it takes several minutes leving unexperienced users to think it might have crased. seahorse version 3.10.2 gpg version 1.4.15 ** Affects: seahorse (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1278381 Title: pgp key generation window not present To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/seahorse/+bug/1278381/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1278386] [NEW] seahorse can only generate pgp keys up to 4096 bit
Public bug reported: The current version of seahorse in Ubuntu 14.04 does not show an option to generate pgp keys larger then 4096 bit. This should be raised to allow key sizes up to 8192 (at least) as is the case when generating ssh keys ** Affects: seahorse (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1278386 Title: seahorse can only generate pgp keys up to 4096 bit To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/seahorse/+bug/1278386/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1278387] [NEW] Private key generation does not work at all
Public bug reported: The current version of seahorse in Ubuntu 14.04 shows an option to generate a private key. It is neither obvious what kind of key this is nor does the option work at all, leaving fields for key type empty and not offering the possibility to active the Create button, leaving this option completely pointless. Additionally, when setting the key size, the value is not limeted by anything other then the size of int ** Affects: seahorse (Ubuntu) Importance: Undecided Status: New ** Description changed: The current version of seahorse in Ubuntu 14.04 shows an option to generate a private key. It is neither obvious what kind of key this is nor does the option work at all, leaving fields for key type empty and not offering the possibility to active the Create button, leaving this option completely pointless. + + Additionally, when setting the key size, the value is not limeted by + anything other then the size of int -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1278387 Title: Private key generation does not work at all To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/seahorse/+bug/1278387/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1047384] Re: System Encryption Password set before setting keyboard locale
This is still a issue in Ubuntu 14.04, causing a lot of trouble for anyone with a non english keyboardlayout. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1047384 Title: System Encryption Password set before setting keyboard locale To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1047384/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1278390] [NEW] diagnostic tab lock button
Public bug reported: On Ubuntu 14.04 the tab privacy and security show a lock button that does not have any function anymore. Clicking the button does not have any effect at all, neither locking nor unlocking the setting for sending error reports and stuff. ** Affects: gnome-control-center (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1278390 Title: diagnostic tab lock button To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1278390/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1278392] [NEW] multiple option settings for lock screen
Public bug reported: The option to set the time bevore activating screen lock is abviable to be set in the tab privacy and security as well als in brightness lock leving an inconsistent interface also in Security and Pivacy the time options to determin when to lock the sceen after it turned black should contain a 5 and/or 10 second option, as it now only contains the choice between 1 second and 30 Seconds, leaving a big gap. ** Affects: gnome-control-center (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1278392 Title: multiple option settings for lock screen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1278392/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1257939] Re: Does not show fingerprint in key import dialog
https://bugzilla.gnome.org/show_bug.cgi?id=719872 ** Bug watch added: GNOME Bug Tracker #719872 https://bugzilla.gnome.org/show_bug.cgi?id=719872 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1257939 Title: Does not show fingerprint in key import dialog To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/seahorse/+bug/1257939/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1257939] Re: Does not show fingerprint in key import dialog
Perhaps 'fingerprint=on' isn't an option on all keyservers? Or perhaps they are using a more meager search mechanism that doesn't expose this information cheaply. The fingerprint was not shown using several different servers. It might be a simple bug like the key ID Variable used where the fingerprint variable should be. I did not find the specific section of the code yet. https://github.com/GNOME/seahorse -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1257939 Title: Does not show fingerprint in key import dialog To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/seahorse/+bug/1257939/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 760344] Re: gvfsd-http not closing tcp connections
Still affecting Ubuntu 12.04.3 Will there be a backport available? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/760344 Title: gvfsd-http not closing tcp connections To manage notifications about this bug go to: https://bugs.launchpad.net/libsoup/+bug/760344/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1257939] [NEW] Does not show fingerprint in key import dialog
*** This bug is a security vulnerability *** Public security bug reported: Using the seahorse option to find and import remote public keys, the properties dialog does not show the correct fingerprint but the key ID instead. to reproduce: go to remote, find remote keys, enter a valid search term, select a key from the results and select properties in the context menu of the selected key. bug was confirmed using the following versions: 3.10.1 (using ArchLinux) 3.2.2 (Using Ubuntu 12.04.3) ** Affects: seahorse (Ubuntu) Importance: Undecided Status: New ** Information type changed from Private Security to Public Security -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1257939 Title: Does not show fingerprint in key import dialog To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/seahorse/+bug/1257939/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
