(In reply to Paul Webster from comment #21)
(In reply to comment #20)
Is there a way to get RCP to also use setAccelerator whenever it sets
shortcut
labels? That would ensure that menu items work correctly.
RCP and Eclipse SDK use a KeyDown filter to process key shortcuts. We have
(In reply to Paul Webster from comment #21)
(In reply to comment #20)
Is there a way to get RCP to also use setAccelerator whenever it sets
shortcut
labels? That would ensure that menu items work correctly.
RCP and Eclipse SDK use a KeyDown filter to process key shortcuts. We have
This issue is still present in firefox 14:
$ apt-cache policy firefox | head -3
firefox:
Installed: 14.0.1+build1-0ubuntu0.12.04.1
Candidate: 14.0.1+build1-0ubuntu0.12.04.1
** Summary changed:
- print to file fails silently if target directory is not writable
+ print to file defaults to
I upgraded to 12.04, and this issue remains.
$ apt-cache policy firefox | head -3
firefox:
Installed: 13.0+build1-0ubuntu0.12.04.1
Candidate: 13.0+build1-0ubuntu0.12.04.1
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to firefox in
Public bug reported:
Steps to reproduce:
1. Load a web page in firefox and click File-Print. The Print dialog box
appears.
2. Choose Print to File from the list of printers
3. Choose home under Save in folder. (This is always the default selection for
me).
4. Type a name in the filename box,
I changed this to the Unity Apps lens, since this is actually the
culprit here (I am presuming).
** Package changed: software-center (Ubuntu) = unity-lens-applications
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to software-center in
The only solution that worked: fresh install of lubuntu. Nothing else
fixed it and it it got rid of unity which is terrible on a low power
netbook (i.e. the app lens never loads, so you can't access any of your
apps other than through the terminal).
--
You received this bug notification because
@Thilo-Alexander Ginkel (thilo.ginkel) just to confirm, this issue
occurs when the user tries to shutdown normally via the GUI (i.e click
on the cog Shut Down Shut Down), not when issuing terminal commands,
although the issue is still evident when trying to shutdown via the
shutdown -hP command
@Thilo-Alexander Ginkel (thilo.ginkel) just to confirm, this issue
occurs when the user tries to shutdown normally via the GUI (i.e click
on the cog Shut Down Shut Down), not when issuing terminal commands,
although the issue is still evident when trying to shutdown via the
shutdown -hP command
@Thilo-Alexander Ginkel (thilo.ginkel) just to confirm, this issue
occurs when the user tries to shutdown normally via the GUI (i.e click
on the cog Shut Down Shut Down), not when issuing terminal commands,
although the issue is still evident when trying to shutdown via the
shutdown -hP command
@Thilo-Alexander Ginkel (thilo.ginkel) just to confirm, this issue
occurs when the user tries to shutdown normally via the GUI (i.e click
on the cog Shut Down Shut Down), not when issuing terminal commands,
although the issue is still evident when trying to shutdown via the
shutdown -hP command
@Rafael Arroyo (rarroyo) This doesn't fix it for me, I already had
available all users checked
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/882817
Title:
shutdown
Just the same as my route -n:
Kernel IP routing table
Destination Gateway Genmask Flags Metric RefUse Iface
0.0.0.0 192.168.1.1 0.0.0.0 UG0 00 wlan0
169.254.0.0 0.0.0.0 255.255.0.0 U 1000 00 wlan0
*** This bug is a duplicate of bug 882817 ***
https://bugs.launchpad.net/bugs/882817
** Changed in: network-manager (Ubuntu)
Status: Invalid = New
** This bug has been marked a duplicate of bug 882817
shutdown screen stuck after upgrade to Ubuntu 11.10
--
You received this bug
Well, this appears a bug to me, as a number of people are affected as
evidenced by the linked ubuntuforum thread. I am thinking it is either a
fault of network-manager or possibly modem-manager, which also seems to
be killed successfully on the rare occassion when the computer does
shutdown (by
Public bug reported:
Network-Manager appears to be preventing shutdown on some machines, not
sure what the common property is between the people mentioning the
shutdown error here: http://ubuntuforums.org/showthread.php?p=11353570
but I am thinking it is down to Network-Manager, which is
This is on Ubuntu Oneric, upgraded from Natty.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/875959
Title:
network-manager preventing shutdown
Status in “network-manager”
Turns out my initial steps didn't fix the issue. So, I need to know,
how can I debug a shutdown issue if the syslog facility is being killed
before the issue occurs?
** Changed in: network-manager (Ubuntu)
Status: New = Invalid
** Converted to question:
18 matches
Mail list logo
