As comment #19, my issue was apparently with Chrome Remote Desktop.
After uninstalling it, everything seems to be back and working.
* I had no hardware changes prior to my problems
* I'm running on AMD® A10-7800 radeon r7, integrated graphics
* After installing Chrome Remote Desktop, I noticed
** Changed in: software-center (Ubuntu)
Status: Expired = New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/980615
Title:
Can't edit review
To manage notifications about this bug go to:
I'm marking this as new again. I can't edit a review and the log shows
some errors.
** Attachment added: software-center.log
https://bugs.launchpad.net/ubuntu/+source/software-center/+bug/980615/+attachment/3227124/+files/software-center.log
--
You received this bug notification because you
Is this a duplicate of this bug? https://bugs.launchpad.net/indicator-
datetime/+bug/727081
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/750745
Title:
Missing translations for en_GB dates in
Just installed 10.10 on my new computer with an OCZ Vertex 2 60GB SSD,
and I've got the same message. I get this message regardless of SMART is
enabled in BIOS or not.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I've been running Maverick since the release. A quick test just pressing
the buttons and trying to assign them in Keyboard shortcuts says the
problem still exist. I'll try the steps outlined earlier in this thread.
As was concluded in post #10 it's probably a kernel bug. I'm not sure
where Martin
Well, the as far as bug reporting goes it's obviously important to find
out the cause of the problem. But if that's not possible (or not
achieved in a reasonable time frame) then you would obviously want the
problem fixed even without knowing exactly what caused it. And that's
the reason for
As for the rationale behind the Me Menu etc, you can probably find your
answers in this blog post by Mark Shuttleworth:
http://www.markshuttleworth.com/archives/347
--
Make shutdown and user menu separate applets
https://bugs.launchpad.net/bugs/531654
You received this bug notification because
I really don't know how to move on from here. I don't think that you
need to start both compiz and metacity, it's one or the other. Starting
either one with --replace terminates the other if it's running, at least
that's my understanding.
The error in syslog regarding gnome-session might be
I find it strange that you don't have titlebars even when metacity is
set as the window manager. It's probably not a faulty driver then, but
rather some other settings as you say. However, you can see in Hardware
drivers under System - Administration if the latest nvidia driver is
installed. It
The message seems fine, but why the value of windowmanager isn't
changing I don't know. Maybe you could try to manually set it to
metacity with Gconf editor, reboot and see if that works, check to see
if Visual effects says None and from there try again to change to
normal or extra and reboot and
After changing the Desktop Effects, or logging in without title bars, could you
check the setting of /desktop/gnome/session/required_components/windowmanager
with gconf-editor and verify that it shows the same as Desktop Effects:
* It should say metacity if Desktop Effects are set to None
*
Comments #10 and #11 does fix the problem, ie it reverts back to
metacity. However, if I try to activate Visual effects through
Appearance, it hangs on Keep settings and upon log in the problem is
back. Launching gnome-appearance-properties from a terminal gives the
following output when changing
Oh, forgot this: In other words, the problem should go away if users
install compiz and compiz-gnome package (which is a dependency to compiz
so just mark that one for installation).
The bug report should probably be changed to another package, right? I'm
assuming that the fault lies in either
Could you please check this bug report:
https://bugs.launchpad.net/ubuntu/+source/metacity/+bug/559111
See if you have the compiz package installed. If not, install it and see if the
problem goes away (this should allow Compiz to start). If not, try to remove
the mentioned file under ~/-gconf
Could you please check bug #559111 and see if the problem goes away when you:
* install compiz package, or
* remove ~/.gconf/desktop/gnome/session/required_components
Do you know if you have activated Visual effects? In that case the
compiz package needs to be installed since it's probably a
Could you please check bug #559111 and see if the problem goes away when you:
* install compiz package, or
* remove ~/.gconf/desktop/gnome/session/required_components
Do you know if you have activated Visual effects? In that case the
compiz package needs to be installed since it's probably a
Is the file re-created as it was before? Could it possible be because of
the settings in Visual effects? It Visual effects is set to none, I'm
assuming the content of the file should be metacity and not compiz.
--
metacity crashes on login - no window manager
Could you please check bug #559111 and see if the problem goes away when you:
* install compiz package, or
* remove ~/.gconf/desktop/gnome/session/required_components
Do you know if you have activated Visual effects? In that case the
compiz package needs to be installed since it's probably a
Should you encounter any problems, you could try starting the Appearance
properties from a terminal and see if it outputs any error message relating to
the selection of window manager. In other words, run
gnome-appearance-properties
And note any errors you receive while changing from None to
That's normal behavior. I get the same messages sort of. What's
interesting is what gets output when you change the Visual effects
settings, as described in the other bug report. If you get none, then
it's ok I suppose.
I'm guessing this is a duplicate of the other bug, but until the
underlying
Seems likely. Bug #554106 is probably the reason why you can't change
back to metacity in Visual effects, and possibly why some (like me)
didn't have the compiz package installed in the first place. I'm
assuming here that Visual effects takes care of installing the compiz
packages and that the
Well, actually, if you have Visual effects activated you're not running
Metacity anymore, but Compiz. If you want to know which Window Manager
is supposed to be loaded during start up you can check the content of
the gconf setting mentioned earlier. Start gconf-editor and navigate to
the setting
No problem. This is certainly a duplicate of bug #559111 but I'm
reluctant to mark it as such since it will hide it from the search
results. Since this seems to be a fairly new issue users are bound to
search for it, and titlebars seems like a likely keyword for that :)
--
Lucid has no title
Does that character happen to be a 2 or an @? :) There's a related bug
#522554 where that happens, it's marked as a duplicate of this bug.
--
Pressing Enter key causes gdm to restart on first boot
https://bugs.launchpad.net/bugs/522692
You received this bug notification because you are a member
Same here, removing plymouth fixed the problem. I'm leaving it to others
to change package accordingly, mark as duplicate etc. I'm not sure
what's the correct way to do all that :)
--
Logged out when typing 2 or @
https://bugs.launchpad.net/bugs/522554
You received this bug notification because
The numpad issue was a completely different bug, turns out it's Bug
#192508
I've quite recently started using Remote Desktop Viewer which also explains
what I wrote in previous posting:
I have to say that this wasn't the case when 9.10 came out, I would have
noticed since the numpad is used at
Yes, I do. The graphics corruption is present with the open source
nVidia driver, but not with the proprietary driver. The corruption is
present all the time with the open source driver, but in much lesser
degree before the system hangs (it's basically just a couple of black
pixels at the top most
No, you're right, it gets worse all the time while typing. As I
remembered the corruption only worsened when the system froze, but
that's not the case. And also, as you say, it's the 2 key that's the
problem and not the @. I'll change bug title accordingly :)
** Summary changed:
- Logged out
Must be the same, should probably be marked as duplicate but I'm leaving
it as it is for now (that way it has a better chance to show up in
search results).
--
Logged out when typing 2 or @
https://bugs.launchpad.net/bugs/522554
You received this bug notification because you are a member of
@Alex
I've tried both with autologin and without. My description in the bug report is
with autologin enabled, but after your comments I tried without too. It doesn't
matter for me: hitting 2 on the GDM screen restarts the X server. If I reboot,
log in and then hit 2 I get logged out. Same as
Public bug reported:
I'm following the Upgrade Testing test case (
http://testcases.qa.ubuntu.com/Hardware/X/ProprietaryDrivers#Upgrade%20Testing
). Jockey-gtk reports No proprietary drivers are in use on this system as
well as This driver is activated but not in use for the currently
** Attachment added: Dependencies.txt
http://launchpadlibrarian.net/39284344/Dependencies.txt
--
jockey-gtk does not say proprietary drivers are in use
https://bugs.launchpad.net/bugs/522943
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Changed to jockey package
** Package changed: nvidia-graphics-drivers (Ubuntu) = jockey (Ubuntu)
--
jockey-gtk does not say proprietary drivers are in use
https://bugs.launchpad.net/bugs/522943
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Public bug reported:
I get logged out to the GDM screen when typing in the password to my
wireless network. It's always with the same character, namely @. After I
log in again I can successfully enter the password.
ProblemType: Bug
Architecture: amd64
CRDA: Error: [Errno 2] No such file or
** Attachment added: Dependencies.txt
http://launchpadlibrarian.net/39263149/Dependencies.txt
** Attachment added: Gconf.txt
http://launchpadlibrarian.net/39263150/Gconf.txt
** Attachment added: IpAddr.txt
http://launchpadlibrarian.net/39263151/IpAddr.txt
** Attachment added:
I discovered that it doesn't matter where I type the character, so i
choose gnome-desktop as package instead
** Summary changed:
- Logged out when typing @ in password to wireless network
+ Logged out when typing @
** Package changed: network-manager-applet (Ubuntu) = gnome-desktop
(Ubuntu)
--
I tried entering the @ character in the adress bar in Firefox and I got
logged out then as well. Appart from that I'm also having trouble with
this bug, don't know if they are related somehow:
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-
nv/+bug/519505
--
Logged out when typing
Ramon:
Are you sure that it's the same bug? I'm in the same position as you, I'm
testing the proprietary drivers, but for me it's not a timed issue neither is
it with completely random characters. I always get logged out when I'm entering
my password for the wireless network, specifically when
Funny enough the Enter hang bug disappears after I've logged in again.
I've tried logging in, hitting Enter and the desktop hangs. But if I log
in, hit @ and get logged out, then log in again the desktop doesn't seem
to hang when hitting Enter.
--
Logged out when typing @
I'm having the same problem. I also had another problem reported here:
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/522554
Upon logging in again after that, hitting Enter doesn't seem to hang the system
anymore.
--
Pressing Enter or using sudo command with NVidia driver hangs /
I might as well mention another problem that quite recently popped up
regarding this keyboard. I've been using it with Ubuntu 8.10, 9.04 and
now 9.10 without other problems then the above mentioned, However, since
some time ago sometimes the numpad stops working, no matter what the num
lock state
Oh wait... this might be related to mouse keys. Which I thought I had
disabled. I'll look into it a bit more. I turned mouse keys off and the
numpad started working again. Sorry!
(Accessibility features can be toggled... is off too).
--
Logitech Illuminated keyboard: Fn + F5/F6 do not produce
Ok, so I'm troubleshooting from a daily Lucid LiveCD from 31th of
january:
Step 2: Same as before, i.e. no events for Fn+F4-6 but all the other
Fn+Fx works
Step 4: When running /lib/udev/findkeyboards nothing was returned. I instead
checked /dev/input/by-id and found this:
lrwxrwxrwx 1 root
Oh, thanks for the pointer. I forgot about that. /lib/udev/findkeyboards only
listed input/event3. With input/event4 the situation is reversed, normal keys
(like letters) just gets typed in the terminal. Fn+Fx works for all
kombinations except F5 and F6 which outputs nothing. In other words,
Allright. Thanks for the help. Peace of mind is always good :) What
about the kernel bug, should I go about bug reporting it somewhere? On
Launchpad or upstreams? If it isn't already ofcourse. Or is there some
kind of automatic procedure for this?
--
Logitech Illuminated keyboard: Fn + F5/F6 do
I've been using 9.10 64-bit for a couple of weeks now, and the problem
persists. I've followed your suggestion and to no avail. In fact, non of
the Fn+Fx key kombination generates any scan codes, not even the ones
which does launch something (for instance Fn+F7 for the calculator). The
other,
I agree with Ryan's first comment. Maybe the Install icon/option could
be placed under the System menu (after all, it's system related right?)
among the Help and About items. I believe that there's a whole group of
people using LiveCDs for common tasks, and that never intend to install
the system
Regarding inconsistent locale:
As a swede using English as the language of choice for programs, I wish I could
set a different locale for things such as date formats, decimal separator,
currency etc. I have yet to find settings for this in Gnome. I especially find
it annoying that week days
Public bug reported:
Binary package hint: hotkey-setup
I've got a Logitech Illuminated keyboard (
http://www.logitech.com/index.cfm/keyboards/keyboard/devices/4740cl=us,en
), where some of the function keys works flawless and some doesn't work
at all. I'm using Ubuntu 8.10 64-bit.
The keyboard
** Attachment added: xkbcomp.txt
http://launchpadlibrarian.net/23394133/xkbcomp.txt
--
Some Logitech Illuminated keyboard hotkeys doesn't work
https://bugs.launchpad.net/bugs/337461
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
There's a couple of disconnect/connect messages in regards to the
keyboard in the dmesg output. This is due to 1) After a suspend I have
to disconnect and reconnect the keyboard in order for it to work, and 2)
I disconnected the keyboard to try it with my laptop.
** Attachment added: dmesg.log
** Attachment added: xkbmap.txt
http://launchpadlibrarian.net/23394176/xkbmap.txt
--
Some Logitech Illuminated keyboard hotkeys doesn't work
https://bugs.launchpad.net/bugs/337461
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
** Attachment added: lsinput.log
http://launchpadlibrarian.net/23394177/lsinput.log
--
Some Logitech Illuminated keyboard hotkeys doesn't work
https://bugs.launchpad.net/bugs/337461
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
** Attachment added: lshal.log
http://launchpadlibrarian.net/23394181/lshal.log
--
Some Logitech Illuminated keyboard hotkeys doesn't work
https://bugs.launchpad.net/bugs/337461
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
55 matches
Mail list logo
