[Bug 672563] [NEW] System Monitor displayed info

2010-11-08 Thread Dijon442
Public bug reported: Binary package hint: gnome-system-monitor System Monitor should display the Installed Architecture many users would hunt a long time to find that information. Regards... dlp ProblemType: Bug Architecture: i386 CheckboxSubmission: ae14f75495244f2b39306f57a72c125f

[Bug 672563] Re: System Monitor displayed info

2010-11-08 Thread Dijon442
-- System Monitor displayed info https://bugs.launchpad.net/bugs/672563 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Re: [Bug 348368] Re: lm-sensors blocks PS2 mouse

2009-09-01 Thread Dijon442
Without other reports I would not consider this a bug. I think it was other hardware issues on my end, and the lm-sensors connection was most likely coincidental. Thanks for the follow-up. David Dimitrios Symeonidis wrote: dijon442, have you managed to resolve/identify this issue? thanks

[Bug 348368] [NEW] lm-sensors blocks PS2 mouse

2009-03-25 Thread Dijon442
Public bug reported: Binary package hint: lm-sensors After installing lm-sensors the Logitech PS2 stopped operating. Removing the package re-enabled the mouse. ProblemType: Bug Architecture: amd64 Date: Wed Mar 25 07:39:36 2009 DistroRelease: Ubuntu 8.04 ExecutablePath: /usr/sbin/synaptic

[Bug 348368] Re: lm-sensors blocks PS2 mouse

2009-03-25 Thread Dijon442
** Attachment added: Dependencies.txt http://launchpadlibrarian.net/24327783/Dependencies.txt ** Attachment added: ProcMaps.txt http://launchpadlibrarian.net/24327784/ProcMaps.txt ** Attachment added: ProcStatus.txt http://launchpadlibrarian.net/24327785/ProcStatus.txt -- lm-sensors

[Bug 348368] Re: lm-sensors blocks PS2 mouse

2009-03-25 Thread Dijon442
** Description changed: Binary package hint: lm-sensors After installing lm-sensors the Logitech PS2 stopped operating. Removing the package re-enabled the mouse. + + This is likely not correct... while the mouse was re-enabled + immediately, I'm starting to suspect other hardware