Confirming what Rober Neve said, 6.8.0 works fine for me.
In case you folks need a full journald output, I have it collected.
kernel boot message + following loading of the desktop created messages.
PS: Can login-now. Apparently I had 2 accounts at UbuntuOne which locked
my account. After they mer
Ok - last test.
While connected to the alpine car device, and disconnecting the Bluetooth on
the phone manually, I can avoid the repetitive 1 bug showing up.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/b
I actually did some more tests.
While paired with the Car unit, everything is fine (Note that I pair the phone
Handsfree and audio capability). When I power off the car unit and didn't
previously disable the pairing manually (Means the phone thinks it is still
paired), that behavior starts.
All
I can confirm that I didn't have to compile the kernel/driver for it to
recognize that network chip.
So yes - the OOB provided driver works for me - version 3.8.0-22.33 - see below.
smurphy@Pandora:~$ uname -a
Linux Pandora 3.8.0-22-generic #33-Ubuntu SMP Thu May 16 15:17:14 UTC 2013
x
The grub will not answer to an held down shift-key as the keyboard mode is
changed.
You have to shutdown the mac mini, and restart it. warm-boot won't work.
Note that I am using the plain KUbuntu 13.04 image. Not the amd64+mac
image.
--
You received this bug notification because you are a membe
Confirmed - 3.8.0-22.33 boots and detects the 57766 chip out of the box. No
recompile required.
Guess you can close this bug.
Thx.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1182868
Title:
tg3 d
Just checked the 3.8.0-22 source, and according to the
linux_3.8.0-22.33.diff.gz file, the tg3.c is patched to support the
57766 chip.
--- linux-3.8.0.orig/drivers/net/ethernet/broadcom/tg3.c
+++ linux-3.8.0/drivers/net/ethernet/broadcom/tg3.c
@@ -330,6 +330,7 @@
{PCI_DEVICE(PCI_VENDOR_ID_
If you tell me where to get 3.8.0-20 directly, I can.
It is not in the repositories. However, I definitely confirm that the driver of
3.8.0-21 does not recognize the NetXtreme BCM57766 gigabit ethernet chip on my
mac mini.
--
You received this bug notification because you are a member of Ubuntu
apport information
** Attachment added: "UdevLog.txt"
https://bugs.launchpad.net/bugs/1182868/+attachment/3683902/+files/UdevLog.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1182868
Title:
apport information
** Attachment added: "WifiSyslog.txt"
https://bugs.launchpad.net/bugs/1182868/+attachment/3683903/+files/WifiSyslog.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1182868
Ti
apport information
** Attachment added: "UdevDb.txt"
https://bugs.launchpad.net/bugs/1182868/+attachment/3683901/+files/UdevDb.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1182868
Title:
tg
apport information
** Attachment added: "RfKill.txt"
https://bugs.launchpad.net/bugs/1182868/+attachment/3683900/+files/RfKill.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1182868
Title:
tg
apport information
** Attachment added: "PulseList.txt"
https://bugs.launchpad.net/bugs/1182868/+attachment/3683899/+files/PulseList.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1182868
Titl
apport information
** Attachment added: "ProcModules.txt"
https://bugs.launchpad.net/bugs/1182868/+attachment/3683898/+files/ProcModules.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1182868
apport information
** Attachment added: "ProcInterrupts.txt"
https://bugs.launchpad.net/bugs/1182868/+attachment/3683897/+files/ProcInterrupts.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/118
apport information
** Attachment added: "ProcEnviron.txt"
https://bugs.launchpad.net/bugs/1182868/+attachment/3683896/+files/ProcEnviron.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1182868
apport information
** Attachment added: "CRDA.txt"
https://bugs.launchpad.net/bugs/1182868/+attachment/3683889/+files/CRDA.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1182868
Title:
tg3 dr
apport information
** Attachment added: "Lsusb.txt"
https://bugs.launchpad.net/bugs/1182868/+attachment/3683894/+files/Lsusb.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1182868
Title:
tg3
apport information
** Attachment added: "ProcCpuinfo.txt"
https://bugs.launchpad.net/bugs/1182868/+attachment/3683895/+files/ProcCpuinfo.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1182868
apport information
** Attachment added: "HookError_cloud_archive.txt"
https://bugs.launchpad.net/bugs/1182868/+attachment/3683891/+files/HookError_cloud_archive.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.laun
apport information
** Attachment added: "Lspci.txt"
https://bugs.launchpad.net/bugs/1182868/+attachment/3683893/+files/Lspci.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1182868
Title:
tg3
apport information
** Attachment added: "BootDmesg.txt"
https://bugs.launchpad.net/bugs/1182868/+attachment/3683888/+files/BootDmesg.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1182868
Titl
apport information
** Attachment added: "IwConfig.txt"
https://bugs.launchpad.net/bugs/1182868/+attachment/3683892/+files/IwConfig.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1182868
Title:
apport information
** Attachment added: "CurrentDmesg.txt"
https://bugs.launchpad.net/bugs/1182868/+attachment/3683890/+files/CurrentDmesg.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1182868
+ Architecture: amd64
+ AudioDevicesInUse:
+ USERPID ACCESS COMMAND
+ /dev/snd/controlC1: smurphy2218 F pulseaudio
+ /dev/snd/controlC0: smurphy2218 F pulseaudio
+ /dev/snd/pcmC0D0p: smurphy2218 F...m pulseaudio
+ DistroRelease: Ubuntu 13.04
+ MachineType: Apple
Here the entire patch snippet:
--- linux-source-3.8.0/drivers/net/ethernet/broadcom/tg3.c 2013-05-02
04:35:43.0 +1200
+++ tg3-3.128x/src/tg3.c2013-05-06 10:30:07.542039601 +1200
@@ -330,6 +330,9 @@
{PCI_DEVICE(PCI_VENDOR_ID_BROADCOM, TG3PCI_DEVICE_TIGON3_5719)},
{PCI_DEVICE(P
Public bug reported:
Since 13.04 came out officially, the NetXtreme BCM57766 gigabit ethernet chip
is not recognized by the tg3 driver.
Have to recompile the kernel and apply a simple patch over and over again.
A fix exists - which consists adding the vendor identification, but it has not
made i
For those having this issue, replacing the btusb module fixed it for me.
Check out this link:
https://help.ubuntu.com/community/MacBookPro6-2/Maverick#Bluetooth
--
bluez fails to discover mx5000 keyboard and mouse
https://bugs.launchpad.net/bugs/550288
You received this bug notification because
Forgot to add the lsbusb output - it shows the difference between using the
Logitech Bluetooth dongle:
smur...@pandora:~$ lsusb
Bus 004 Device 006: ID 05ac:8218 Apple, Inc.
Bus 004 Device 005: ID 05ac:820b Apple, Inc.
Bus 004 Device 004: ID 05ac:820a Apple, Inc.
Bus 004 Device 003: ID 0a5c:450
Last addition.
When adding the Bluetooth Dongle provided by Logitech, all keys and extra stuff
of the leyboard works (except the LCD screen - but that's not a requirement).
So - any chance in getting the Kernel to recognize the MX5500 MX Revolution
with Mouse MX Revolution, without the logitech
Another addition. Using xev to try to localize all the supplementary
buttons won't work. xev won't show anything if pushing any of the other
buttons on the mouse.
C'mon folks - I can't be the only one having this issue
Ther Mac Mini is the perfect computer, and has bluetooth integrated. Why
What I just wanted to add here. It seems, that the HID Devices are recognized,
however not as Logitech devices.
Any way to get a workaround here, so the logitech drivers are loaded correctly
? HID 05ac:820b/HID 05ac:820a ?
--
bluez fails to discover mx5000 keyboard and mouse
https://bugs.launch
Having the same issue. Only that mine may be a little bit more complex.
Running a Mac Mini 4,1 (last one available) with KUbuntu. And - because I
didn't want to use any more USB Ports, I also got the MX5500 Keyboard/Mouse
combination.
So - setup is simple: Mac Mini builtin bluetooth communicatio
** Attachment added: "Dependencies.txt"
http://launchpadlibrarian.net/35569877/Dependencies.txt
** Attachment added: "ProcMaps.txt"
http://launchpadlibrarian.net/35569878/ProcMaps.txt
** Attachment added: "ProcStatus.txt"
http://launchpadlibrarian.net/35569879/ProcStatus.txt
--
Use ex
Public bug reported:
Binary package hint: kdebase-workspace
a very nice way to switch desktops is to use the extra Mouse Buttons
(e.g. Mouse button 4 to switch to the desktop on the left, and 5 to
Switch over to the Desktop on the right). This is very handy as you
don't have to take your hand off
Using KUbuntu 9.10 - functionality came back with my Cordless Desktop
MX700 (Keyboard and Mouse).
--
Regression: Multimedia keys on LX710 stopped working
https://bugs.launchpad.net/bugs/321740
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubunt
Answers:
1. the minimum Step to encounter the problem: Install KUbuntu
2. I expected the Extra keys (Audio Up/Down, next/previous song etc. to work).
3. The actual behavior isn't existent. All extra keys on that keyboard are not
recognized under X. xev/showkey don't return anything on the CLI and
Answers:
1. the minimum Step to encounter the problem: Install KUbuntu
2. I expected the Extra keys (Audio Up/Down, next/previous song etc. to work).
3. The actual behavior isn't existent. All extra keys on that keyboard are not
recognized under X. xev doesn't return anything on the CLI and under
** Attachment added: "lshal output"
http://launchpadlibrarian.net/29002868/lshal.debug
--
Multimedia keys on Cordless Desktop Optical not working
https://bugs.launchpad.net/bugs/399173
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Attachment added: "udev log"
http://launchpadlibrarian.net/29002860/udev.log
--
Multimedia keys on Cordless Desktop Optical not working
https://bugs.launchpad.net/bugs/399173
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubu
** Attachment added: "lsusb output"
http://launchpadlibrarian.net/29002864/lsusb.debug
--
Multimedia keys on Cordless Desktop Optical not working
https://bugs.launchpad.net/bugs/399173
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Attachment added: "XOrg Log File."
http://launchpadlibrarian.net/29002845/Xorg.0.log
--
Multimedia keys on Cordless Desktop Optical not working
https://bugs.launchpad.net/bugs/399173
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
Since upgrading to KUbuntu 8.10, 9.04 and 9.10betas (all instances), the
MX700 Logitech Cordless Desktop worked less and less. In KUbuntu 8.10 I
was still able to configure the Multimedia Keys using a manual method
(Check http://stargate.solsys.org/mod.php?mod=faq&op=view&faq_
Same issue here - using Nvidia proprietary Drivers on a T61p with KUbuntu 4.2.2
and 4.2.3 in 64bit mode.
If deeper details are required, let me know.
--
Kubuntu 9.04 alpha6 panel corruption
https://bugs.launchpad.net/bugs/345076
You received this bug notification because you are a member of Ubun
OK - I don't have any more issues - and I have redone the entire X stuff - by
removing and reinstallation all the X stuff.
My xorg.conf looks like this:
Section "Device"
Identifier "Configured Video Device"
EndSection
Section "Monitor"
Identifier "Configured Monitor"
En
Just saw the following on the pages of http://keytouch.sourceforge.net/ :
When your keyboard is connected via USB you may have noticed that some extra
function keys don't work. Note that most keyboard files in keyTouch are for a
PS/2 connection and if a keyboard file is for a USB connection th
** Attachment added: "lsusb output"
http://launchpadlibrarian.net/21795983/lsusb.txt
--
Intrepid - MX700 Cordless Desktop - Multimedia Key functionality not detected
https://bugs.launchpad.net/bugs/323066
You received this bug notification because you are a member of Ubuntu
Bugs, which is sub
Note that I have replugged the cordless desktop receiver several times
in tests - so the unplug/repluging is seen at the end.
** Attachment added: "dmesg output"
http://launchpadlibrarian.net/21795991/dmesg.txt
--
Intrepid - MX700 Cordless Desktop - Multimedia Key functionality not detected
h
** Attachment added: "lspci output"
http://launchpadlibrarian.net/21795976/lspci.txt
--
Intrepid - MX700 Cordless Desktop - Multimedia Key functionality not detected
https://bugs.launchpad.net/bugs/323066
You received this bug notification because you are a member of Ubuntu
Bugs, which is sub
** Attachment added: "Xorg.0.log"
http://launchpadlibrarian.net/21795969/Xorg.0.log
--
Intrepid - MX700 Cordless Desktop - Multimedia Key functionality not detected
https://bugs.launchpad.net/bugs/323066
You received this bug notification because you are a member of Ubuntu
Bugs, which is subs
Public bug reported:
Using a Logitech Cordless Desktop MX700. All Multimedia Function keys are
ignored, e.g. not detected.
In hardy - it still worked if under X (KDE 3.5.x) I did not use the evdev
driver. In intrepid, even if not using the evdev driver, it doesn't.
The Mouse is working OK in fa
Just saw the following on the pages of http://keytouch.sourceforge.net/ :
When your keyboard is connected via USB you may have noticed that some extra
function keys don't work. Note that most keyboard files in keyTouch are for a
PS/2 connection and if a keyboard file is for a USB connection the
I did actually subscribe to Bug #281993 and tried all they have proposed. Even
the solution which works with the Microsoft Keyboards. It does not work with my
MX700 - so it's not the same bug.
It rather looks like this one: Bug 321740
where I also have uploaded some details and informations in th
BTW - on the mainpage of keytouch:
When your keyboard is connected via USB you may have noticed that some extra
function keys don't work. Note that most keyboard files in keyTouch are for a
PS/2 connection and if a keyboard file is for a USB connection the name of the
keyboard file will contai
These 2 Bugs are not similar (Bug #182704 and Bug #182165) as they are
using the old Drivers, kdb/Corepointer etc. and not evdev. If I
configure my System to use the old Drivers - everything works as
expected. The Bug however here is directly related to evdev - as it does
not recognize the real ca
IT is IMHO the same bug which affects both keyboards, as the same functionality
is affected.
I could of course open a new Bug - but I don't think it is different.
** Attachment added: "Logitech Navigator MX700"
http://launchpadlibrarian.net/21705229/logitech_internetnavigator.jpg
--
Regressi
You want this to be done before or after replugging the Cordless Receiver ?
I'll do it before replugging - as that's where it doesn't work. also - I use
kubuntu - anything I should killt here before doing it ?
gnome-settings-daemon is not used here.
With xev - all Multimedia keys, _ALL_ are not w
I can confirm this Bug. Having the same issue with a Cordless Desktop MX700.
The Mouse is working OK, but almost all Multimedia Keys are working only after
I unplug and Replug the Cordless Receiver.
I attached the xorg.0.log file, with the content of informations during the
unplugging and replugg
I can confirm that the Logitech MX700 Cordless Desktop is not a Microsoft Like
Keyboard.
This kernel has not fixed it. Guess I'll open a new Bug for it - if I don't
find an open one.
I can use most of the Multimedia Keys though by just unplugging and re-plugging
the Cordless Desktop receiver aft
Just for the notes. I noticed, that when unplugging the Cordless receiver while
running under X - waiting 2 Secs, and replugging it, the system detects all
keys etc. as required, and the multimedia keys work.
So - this seems to be a workaround for the Cordless desktop MX700 and
eventually shows
Here mine - Logitech MX700 Cordless Desktop (Mouse & Keyboard).
** Attachment added: "lsusb_vvv as root"
http://launchpadlibrarian.net/21050452/lsubs_vvv.txt
--
[intrepid] REGRESSION: multimedia keys no longer working
https://bugs.launchpad.net/bugs/281993
You received this bug notification b
Have tried whatever was proposed by clement ...
Using a Logitech Cordless Desktop MX 700 combination here. All Keys got screwed
as soon as I upgraded to Intrepid too.
Tried reverting all automations by Disabling hal in the /etc/X11/xorg.conf
file, recompiled the kernel modules (from the usbhid di
You folks,
try adding this:
Section "Device"
Identifier "Configured Video Device"
Option "ForceEnablePipeA" "true"
EndSection
to the device section. Seems this does something ?
--
lockup on mac mini 945GM [8086:27a2]
https://bugs.launchpad.net/bugs/218334
You received this
As we have many people here without knowledge on how doing this - could
you post exactly which steps you did - to perform the change ? Like a
Mini-Howto ?
--
lockup on mac mini 945GM [8086:27a2]
https://bugs.launchpad.net/bugs/218334
You received this bug notification because you are a member of
The only thing that helped me is to disable all Powersaving stuff to
Screen and CPU.
--
lockup on mac mini 945GM [8086:27a2]
https://bugs.launchpad.net/bugs/218334
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing l
Yes. The console did Hang - I followed the also the part specifically dedicated
to remote connections through ssh, but it did hang too.
BTW - in debugging mode - as soon as you start openoffice - and open a Menu in
OO - X takes 100% CPU Time and the system becomes unresponsive too :} Was
reprodu
OK - I tried again - as I was able to reset the screen so it flickers again.
Problem - as soon as I attach gdb from the Command-line on the same machine -
the X-Server becomes unresponsive.
If I do it from a remote machine through ssh - using the keeptty and dumbSched
options, the X-Server stops.
Here the backtrace.
Note - that this time - no flickering - the X system just froze.
Ctrl_C didn't work - so I actually had to send a SIG-Stop to the Xorg process.
Don't know if it helps though ...
** Attachment added: "Backtrace Mac-Mini."
http://launchpadlibrarian.net/15541910/Xorg_mac-mini_b
This is tipical ...
As soon as the entire gdb stuff is loaded, and attached to the xorg process -
nothing flickers anymore ... *pt*
Will leave it running until something crashes...
--
lockup on mac mini 945GM [8086:27a2]
https://bugs.launchpad.net/bugs/218334
You received this bug notificati
Started the entire backtrace process... Now waiting for the crash to occure ...
At least - it flickers from time to time ...
Ah - it helped watching some movies - to speed it up :) the crash I mean.
--
lockup on mac mini 945GM [8086:27a2]
https://bugs.launchpad.net/bugs/218334
You received this
I did actually made what you suggested - but I have a mac-mini, edition late
2006 (December).
Let's see if it's a pipe-issue ;) Would be nice :D
--
lockup on mac mini 945GM [8086:27a2]
https://bugs.launchpad.net/bugs/218334
You received this bug notification because you are a member of Ubuntu
Bu
Hia mate.
Sorry - but it didn't work over here. If I activate Power-Management, it takes
roughly 5minutes until I get a Grey-Screen ...
With Powermanagement disabled, it works though.
--
lockup on mac mini 945GM [8086:27a2]
https://bugs.launchpad.net/bugs/218334
You received this bug notificati
Public bug reported:
Binary package hint: linux-ubuntu-modules-2.6.24-16-generic
when inserting the Vodaphone Cardbus Card into the cardbus slot - the system
locks hard immediatly.
The last you see in the console is how it loads the nozomi driver.
Note that when booting the latest gutsy kernel i
Good one ...
I manage to get it to run without patching - just disabling Powermanagement
entirely for the chip - and not starting any Screen-Lock/Saver
--
lockup on mac mini 945GM [8086:27a2]
https://bugs.launchpad.net/bugs/218334
You received this bug notification because you are a member of Ub
Nope - we like your personal Diary
Guess most don't have time to go after it in detail - but your Input is highly
appreciated :) by us all :)
--
lockup on mac mini 945GM [8086:27a2]
https://bugs.launchpad.net/bugs/218334
You received this bug notification because you are a member of Ubuntu
This seems to be limited to the mac-mini systems...
Anyone having no mac-mini with that issue in here ?
--
lockup on mac mini 945GM [8086:27a2]
https://bugs.launchpad.net/bugs/218334
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ub
Happens if I´m working or I'm away. No Difference here.
--
lockup on mac mini 945GM [8086:27a2]
https://bugs.launchpad.net/bugs/218334
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.
as Dmitry pointed out - you can almost eliminate these effects by:
a. Disable Display power Management completely. Do this as Administrator AND
User.
b. Completely disable kpowersaved
Disabling a just as user didn't stop these effects to happen. Since I
also disabled it as Administrator - I barel
*** This bug is a duplicate of bug 210153 ***
https://bugs.launchpad.net/bugs/210153
I had seen that Bug - but the fact here is that the Windows and Linux
Version differe. I though the Internal Engine of OpenOffice was the same
- and not linked to OS/System libraries. Bug 210153 referred to t
I personally think that both version (Linux/Windows) should behave the
same way on these files.
--
calc: sum show err:529
https://bugs.launchpad.net/bugs/228143
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
Public bug reported:
Binary package hint: openoffice.org2
I know the handling of empty cells has changed - however OpenOffice 2.4
should beheave the same under Ubuntu/Gutsy and Windows right ?
Well - not so - check attached screenshots.
** Affects: openoffice.org (Ubuntu)
Importance: Undec
** Attachment added: "Paze opened with linux shows the Error"
http://launchpadlibrarian.net/14359814/OOPaze_Linux.png
--
calc: sum show err:529
https://bugs.launchpad.net/bugs/228143
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
OpenOffice 2.4 Windows Opening of the same file.
** Attachment added: "Paze opened under windows"
http://launchpadlibrarian.net/14359826/OOPaze_Windows.png
--
calc: sum show err:529
https://bugs.launchpad.net/bugs/228143
You received this bug notification because you are a member of Ubuntu
Bu
I can confirm this bug. My workaround is to have the max bandwidth
limited to 10MBit. This works.
Same system - 1 Year old Mac-Mini, Core 2 Duo CPU (Self upgraded), 2 GB Ram and
an upgraded 200GB Harddisk running a Kubuntu 8.04 (Update from Kubuntu 7.10
which was updated from Kubuntu 7.04)...
On
*** This bug is a duplicate of bug 218334 ***
https://bugs.launchpad.net/bugs/218334
Just for the correctness :) The output of the lspci -v on the Graphic
chip.
00:02.0 VGA compatible controller: Intel Corporation Mobile 945GM/GMS,
943/940GML Express Integrated Graphics Controller (rev 03) (
*** This bug is a duplicate of bug 218334 ***
https://bugs.launchpad.net/bugs/218334
Hi There ...
having a mac-mini too here - 1 Year old. I have the exact same beheaviour !
Also - Updated from a KUbuntu 7.10 to a KUbuntu 8.04 Adept Upgrade Tool.
--
[hardy] Mac mini. Intel 945GM. Random scr
*** This bug is a duplicate of bug 218334 ***
https://bugs.launchpad.net/bugs/218334
Sorry - forgot to add one thing. I have a Samsung SyncMaster 214T (1600x1200)
Panel.
The Screen Flickers randomly - and sometimes - suddenly becomes Black. Can't
recover except go to console and initiate a r
Happens here too...
The first run after system start without parameters seems to work - e.g. gives
me a help - all following executions core-dump
--
knocker invalid pointer
https://bugs.launchpad.net/bugs/77084
You received this bug notification because you are a member of Ubuntu
Bugs, which is
You guys Think we could start a petition ? or a Vote ? to get this issue
addressed ?
Of - who can we send an E-Mail to try to get that done ... to try to discuss
this matter ?
Anyone knows how to retrieve a list of applications that are dependent
on this ?
All we need then is to validate these
If there is anything specific I can do - let me know.
Can play around with the Mac mini (Without screwing the OS) to check what is
going on.
But I need direction ... Long time I did some deep kernel debugging ...
--
keyboard.c floods syslog
https://launchpad.net/bugs/94160
--
ubuntu-bugs maili
Well - from the standard/stable-view prespective - yes. However - just testing
both setups - version 0.90 catches about 1 virus more out of 10 - which for me
- is a valid reason to use the new version.
I don't care for myself - as I have the knowledge to build myself new packages
- how about the
Sorry folks...
I was too fast ...
It stopped flooding syslog - however /var/log/messages get's it all now ...
So - even with 2.6.20-12.20 we still have the flooding.
--
keyboard.c floods syslog
https://launchpad.net/bugs/94160
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://li
Seems that has been fixed with the latest kernel.
Running 2.6.20-12.20 here - and no more syslog flooding ...
Ah yes - this is the guy with the mac-mini ...
Thx folks :)
--
keyboard.c floods syslog
https://launchpad.net/bugs/94160
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https:/
Another question - anyone made some ubuntu packages ???
or has a repository that can be used ?
It is IMHO (coming from me - 14 Years in Internet Security Business) a very
critical issue. I don't mind having that system in place... cause I know my
systems.
But loads of People rely on us (Ubuntu) t
Rebootet into 2.6.20.3 - and didn't have that beheaviour ...
So it seems a bug in 2.6.20-12-generic
Confirmed.
Please note that I can't test with other keyboards - as I only have 2 ;)
--
keyboard.c floods syslog
https://launchpad.net/bugs/94160
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.
Got a Mac-Mini 1.66GHz, 1GB Ram showing the same beheaviour.
Disconnected the actual keyboard (Logitech MX700 Keboard & Mouse) and
connected another one. Didn't make a difference.
Even rebooting...
Linux deimos.solsys.org 2.6.20-12-generic #2 SMP Sun Mar 18 03:07:14 UTC 2007
i686 GNU/Linux
Not
Just to notify - kernel 2.6.20-12-generic boots the Mac-mini (intel) fine ...
Thx for fixing this ...
Cheers
--
ATA: abnormal status 0xXX on port 0x
https://launchpad.net/bugs/92757
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bu
I have added a dmesg output of a kernel that did actually boot the
system - which is my self recompiled 2.6.20.3 version...
The ubuntu feisty kernel does not boot the system with the error I did
put into the first tab, notably: 2.6.20-11-generic, 2.6.20-10-generic
So - yes this is a Bug - and thi
But - what do we do about that then ?
Secutiry is definitly a concern on production systems - and as I remember -
dapper is also used for 6.06.1 LTS - which tells Long time support. This also
means - that all systems out there building up on that version will have
restricted security if the Admi
Public bug reported:
Binary package hint: clamav
Hi Folks,
coming from the security side - I know how Important it is to update the Engine
in security products.
The issue is - that viruses tend to change the algorythm's they use to attack
systems. These force the anti-virus-software writers to
1 - 100 of 102 matches
Mail list logo
