+1 from me.
I sopped cups via systemctl, then the plasmashell and the taskbar came
up again. I disabled the printer status notification in system settings,
now plasmashell and printing is working (but without notifiy).
--
You received this bug notification because you are a member of Ubuntu
Public bug reported:
Hello,
the package is missing in Bionic, so we can't get more than 640x480 in Bionic!
Please provide it.
rgds,
j
** Affects: xserver-xorg-video-mga (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of
This just happend to me when upgrading vom 4.7.8 to 4.8.4. Kernel is
self-compiled, but with the kernel config taken from Ubuntu Mainline
PPA.
I run a Macbook 11,3, so it's very similar to what at wvengen's setup
happens.
--
You received this bug notification because you are a member of Ubuntu
@ldc:
- I did observe multiple times now, that killing the wpa_supplicant +
reconnecting to the wifi solved the no traffic issue.
- I can reproduce it quite good in the company by changing the floor (and
thus, getting a different access point with the same ssid)
- Does that workaround work
Hi,
Yesterday I ran into a no traffic situation, which was not resolveable by
unloading the wl module:
tcpdump on the wlan0 interface showed me only:
00:21:21.575404 EAPOL key (3) v2, len 117
00:21:21.865239 EAPOL key (3) v2, len 117
00:21:22.385278 EAPOL key (3) v2, len 11
...
At the same I
Hello,
yes, it supports 5 GHz and 2.4GHz and it's a hidden SSID. With your two
accesspoint setup, did you try to associate with one AP and turn that off or
force the AP desaccociate the client?
About my chipset: I run a Macbook Pro (rMBP) with the following
broadcom chipset (which is NOT
Hello,
I build the module with your patch. Thanks for that patch!
I work in a an environment with a cisco-based corporate Wi-Fi solution
which leads to a situation that I roam often. My observation is, that I
suspend, change the building and resume, the no traffic effect occurs.
In difference to
Hello,
the same occurs here after dist-upgrading Gutsy to version of yesterday night.
With the old version it more or less worked, but sometimes I needed to click on
the network 2-3 times ... then the connection became ready (100%). I am using a
kernel from vanilla sources + madwifi + whoopie
*** This bug is a duplicate of bug 150680 ***
https://bugs.launchpad.net/bugs/150680
Public bug reported:
/usr/share/gconf/schemas/update-notifier.schemas is not wellformed in
version 0.60. Line defaultfalse/default lacks a . Change into
defaultfalse/default.
Or dpkg will not install the
hm,
without digging deeper into the theme, I assume you cannot nice or
schedule the KVM machine, as it is implemented in the kernel. So I would
add a CPU-consumption DoS, as kernel-mode execution has high prio.
And, as things like scanner and audio have own groups, it makes sense to
give a
Hello Scott,
then why did you change the bug report to invalid? The only thing that
needs to be corrected is, replaung the patch with a own udev rule file.
Everything else discussed here, is absolutely correct.
The title of the bugs reads: access to /dev/kvm should have a
different
Well,
this bug ( #127704 ) is a bug filed to the kvm package, not the udev
package. So it's still the right place. Only the patch is invalid, which
is no problem: As one of the foreposters noted, there already was such a
udev rule file, provided by the kvm package. So we should simply look
wasnt aware that deb
format supports udev rules natively.
I hope, this will be accepted again.
rgds,
Andreas
Andreas John schrieb:
Well,
this bug ( #127704 ) is a bug filed to the kvm package, not the udev
package. So it's still the right place. Only the patch is invalid, which
Gabriel Ambuehl schrieb:
On Monday 24 September 2007 16:09:55 Andreas John wrote:
I hope, this will be accepted again.
Couldnt one simply create a /etc/udev/rules.d/XX-kvm-rules
I already mailed the diff, that is needed to create a udev rule within
the kvm package.
Scott please re-confirm
hm,
why can't I find a compiled kernel linux-image-2.6.22-.*-xen in the
repository with $ARCH amd64?
Is that upload still pending?
Best regards,
Andreas
--
compile fails: Xen on amd64 architecture
https://bugs.launchpad.net/bugs/133986
You received this bug notification because you are a
Hi Christoph,
thanks for the hint, I also spent quite a lot of time to search for the
sluggishness of my X.
I have:
00:02.0 VGA compatible controller: Intel Corporation Mobile 945GM/GMS/940GML
Express Integrated Graphics Controller (rev 03)
00:02.1 Display controller: Intel Corporation Mobile
Hi,
I still can confirm, that my Thinkpad X60s can be supended (via klaptop) and
woken up via FN-Moon, unless the kvm module is loaded. As workaround you can
blacklist the modues in /etc/default/acpi-support, but this doesnt help if a
kvm machine is up and running: The modules cannot be
hm,
as stated in the thread mention by Snah Nosrovlah, the upstream version has
fixed the bug. I droped-in their cvs and rebuilded the package. kino starts now
(but at least one file overlaps with kinoplus).
Please consider using cvs from upstream.
rgds,
Andreas
--
[Gutsy] Kino freezes when
Public bug reported:
The description says:
An example config file for this kernel and documentation on how
to build it can be found in the xen-docs package
But:
[EMAIL PROTECTED]:/usr/share/doc# apt-get install xen-docs
Paketlisten werden gelesen... Fertig
Abhängigkeitsbaum wird
Public bug reported:
Binary package hint: kvm
Hello,
I am not sure where to file this wish. udev or kvm? I'll try on kvm first. I
found that bug/wish on feisty/tribe 2.
The device /dev/kvm belongs to root:root which renders it unusable from
ordinary users. I recommend to give it
Public bug reported:
Binary package hint: airport-utils
airport-config dies silently. My Java alternative points to the Sun
Java 6 JVM. Running AirportBaseStationConfig.jar manually with Java 5
is a workaround. I bet it's an upstream bug, but please fix the wrapper
script with blacklisting Java
21 matches
Mail list logo
