Public bug reported:
Binary package hint: flashplugin-nonfree
flashplugin-nonfree 9.0.48.0.0ubuntu4 does not install properly in Gutsy
x86_64.
I get this error message: install: target `/usr/lib/flashplugin-nonfree/' is
not a directory: No such file or directory
** Affects:
This problem is still present in Gutsy
** Tags added: condensed dejavu qt
--
No Dejavu Sans Condensed font in KDE Feisty Fawn
https://bugs.launchpad.net/bugs/93155
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs
Public bug reported:
I have no sound in Gutsy x86_64. In Feisty, sound worked fine.
My laptop is a Dell Latitude D830.
** Affects: Ubuntu
Importance: Undecided
Status: New
--
No sound in Gutsy
https://bugs.launchpad.net/bugs/131133
You received this bug notification because you
** Attachment added: tail -2 /proc/asound/oss/sndstat
http://launchpadlibrarian.net/8738435/sndstat
--
No sound in Gutsy
https://bugs.launchpad.net/bugs/131133
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs
** Attachment added: amixer
http://launchpadlibrarian.net/8738436/amixer
--
No sound in Gutsy
https://bugs.launchpad.net/bugs/131133
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
** Attachment added: asoundconf list
http://launchpadlibrarian.net/8738437/asoundconf
--
No sound in Gutsy
https://bugs.launchpad.net/bugs/131133
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
** Attachment added: dmesg
http://launchpadlibrarian.net/8738439/dmesg
--
No sound in Gutsy
https://bugs.launchpad.net/bugs/131133
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
** Attachment added: /proc/interrupts
http://launchpadlibrarian.net/8738440/interrupts
--
No sound in Gutsy
https://bugs.launchpad.net/bugs/131133
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
** Attachment added: lspci -nv
http://launchpadlibrarian.net/8738441/lspci
** Description changed:
I have no sound in Gutsy x86_64. In Feisty, sound worked fine.
+
+ My laptop is a Dell Latitude D830.
--
No sound in Gutsy
https://bugs.launchpad.net/bugs/131133
You received this bug
I have also this problem running Kubuntu 6.10.
It is very annoying especially in combination with knetworkmanager that keeps
asking for a password every time I reboot.
Is someone working on this? Do I have to post some debugging
information?
--
kwalletmanager do not rememeber passwords after
Is this patch added in kde-guidance-powermanager-0.8.0-0ubuntu4? If so,
I think it has introduced a problem for me: When running on batttery,
the power manager wrongly indicates it is fully charged and it never
changes to discharging. On ac adapter, everything seems fine. I have
this behavior
I'm using a Dell Latitude D800 notebook. I have made the change you
suggested and then, the battery monitor works correctly again. Thanks
for your help and your work on guidance-powermananger!
** Attachment added: lshal output in powered mode
http://librarian.launchpad.net/7243204/ac
--
** Attachment added: lshal output in battery mode
http://librarian.launchpad.net/7243206/battery
--
guidance-power-manager shows dischanging if battery full
https://bugs.launchpad.net/bugs/104794
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug
Public bug reported:
Binary package hint: powermanagement-interface
I was unable to upgrade to the new version (0.3.15) of
powermanagement-interface. I'm running Kubuntu Feisty Fawn.
This is the error message I got:
Setting up powermanagement-interface (0.3.15) ...
Can't call method description
After todays updates, the problem seems to be resolved. I don't know which
package exactly has resolved my problem.
Somebody may close this bug for me.
--
nvidia driver corrupts usplash with feisty beta since kernel 2.6.20-13
https://bugs.launchpad.net/bugs/96889
You received this bug
I think it wasn't a real bug. After searching a bit on google, I found
it was a corrupt debconf database (don't know what could cause this).
After running /usr/share/debconf/fix_db.pl I could install the package
properly.
--
error while installinge powermanagement-interface (0.3.15)
Added console output from the powermanager when it should suspend. I
have the time set to 1 minute.
** Attachment added: console output
http://librarian.launchpad.net/7121048/guidance-powermanager
--
Suspend when the system is idle for more than n minutes
Public bug reported:
Binary package hint: kde-guidance-powermanager
Suspend/hibernate/shutdown when the system is idle for more than n
minutes in guidance-powermanager doesn't seem to work. Nothing happens
after the the n minutes have passed.
Manually suspending or hibernating works.
I'm
I'm just using English as language. I don't know if it matters, but I
have configured Belgium as country.
I have applied the your patch and tested suspending and hibernating
after 1 minute. It works fine know.
I have noticed a rather cosmetic thing: the popup when suspending or
hibernating does
I just started to learn python and after some trial and error I think you have
to replace %s with %1 and %2 in your patch. Then, everything seems to
work correctly.
I don't know if it would possible to handle plural also (for example 1 minuTE -
10 minuTES)
--
Suspend when the system is idle
Public bug reported:
If I shutdown, usplash is expanded over the whole screen (1680x1050) and the
ubuntu logo looks ugly. Video expansion is disabled in the bios. If I start up,
everything is fine, but after starting X, the framebuffer consoles and usplash
are expanded over the whole screen. I
** Description changed:
- If I shutdown, usplash is expanded over the whole screen (1680x1050) and the
ubuntu logo looks ugly. Video expansion is disabled in the bios. If I start up,
everything is fine, but after starting X, the framebuffer consoles and usplash
are expanded over the whole
I only get this problem when I switch back from X to vt.
(added xorg log)
** Attachment added: Xorg log
http://librarian.launchpad.net/6996439/Xorg.0.log
--
nvidia driver corrupts usplash with feisty beta since kernel 2.6.20-13
https://launchpad.net/bugs/96889
--
ubuntu-bugs mailing list
I can confirm this problem. I'm running a new installed system (kubuntu feisty
beta + latest updates). When I want to log off, all I get is a black screen.
Switching to a terminal is impossible.
I have a nvidia geforce fx 5200 go card with nv driver.
--
feisty logout crash
After the latest upgrade I've done everything is ok again. I can log out
properly.
There were a couple of kde packages to upgrade. I don't know which one has
resolved my problem.
--
feisty logout crash
https://launchpad.net/bugs/86615
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
I am also having this bug. I have installed Kubuntu Feisty Fawn Herd 5
and upgraded to the latest available packages, and the Dejavu Condensed
fonts are missing in KDE. But they are in /usr/share/fonts/truetype/ttf-
dejavu/
--
No Dejavu Sans Condensed font in KDE Feisty Fawn
** Tags added: font kde kubuntu
--
No Dejavu Sans Condensed font in KDE Feisty Fawn
https://launchpad.net/bugs/93155
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
This bug is very sneaky in that way that i totally neglected is untill i
read a thread on the ubuntu forums about it and noticed my laptop HD was
doing it all the time while running on the battery.
Since it's killing my hard disk and i sometimes forget to manually input
the line in terminal i
@Jan
I to can comfirm your solution did the trick, replaced the lines in
hdparm.conf and rebooted, clicking is gone!!!
Thx
--
[Lucid] hdparm.conf change doesn't have effect
https://bugs.launchpad.net/bugs/568120
You received this bug notification because you are a member of Ubuntu
Bugs, which
This bug seems to be back in Ubuntu 16.04
# dig +sigchase
Invalid option: +sigchase
Usage: dig [@global-server] [domain] [q-type] [q-class] {q-opt}
{global-d-opt} host [@local-server] {local-d-opt}
[ host [@local-server] {local-d-opt} [...]]
Use "dig -h" (or "dig -h |
ok; "success" - the problem is solved when installing libseccomp 2.4.3.
Unfortunately, that version is not available on Ubuntu versions < 20.03
(https://packages.ubuntu.com/search?keywords=libseccomp2).
So for debugging, I installed the package from the ubuntu 20.03
repository.
What it comes
Some further discussion in https://github.com/moby/moby/issues/40734.
Possibly one of the new syscalls (added in Linux 5.4) are now being
used, but not whitelisted in docker's seccomp profile;
https://github.com/moby/moby/issues/40734
** Bug watch added: github.com/moby/moby/issues #40734
We ran into the same issue in the containerd packaging scripts
(https://github.com/docker/containerd-packaging/pull/151), and it looks
like the `Cannot utime: Operation not permitted` is caused by seccomp
blocking something.
Now the question is if the default seccomp profile is blocking something
201 - 233 of 233 matches
Mail list logo
