Public bug reported:
Tjhere's an old, expired bug about the same problem with Jaunty.
** Affects: ubuntu
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I'm running Kubuntu 10.10 and I haven't gotten the notification of the
Natty upgrade. I've tried several alternate ways of getting it, none of
which do anything:
1. sudo apt-get update
sudo apt-get upgrade
2. Synaptic shows no upgrade even after a reload.
3. Neither kpackagekit nor the
I've encountered the same problem with the Maverick - Natty upgrade: no
upgrade notification received and no way to get it from synaptic,
kpackagekit, upgrade manager, apt-get, etc.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Same problem here with a Sansa Clip+, but with a twist. The first time
I did it the mount worked correctly, but after that I got the transport
endpoint error.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I still have this bug.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/703602
Title:
Brightness controls not working
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
I still have this bug. I'll test it in Natty once I have Natty installed.
But as of this very moment the upgrade isn't available.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/703602
Title:
There is a workaround, though not as yet a fix as far as I know. The
workaround is not inconvenient. Put the following into
/usr/local/bin/skype (and mark it executable):
LD_PRELOAD=/usr/lib32/libv4l/v4l1compat.so /usr/bin/skype
Assuming you have the correct version of libv4l, the skype
The recommended magic elixir for this bug is sudo alsactl store 0. It
should work, but unfortunately it doesn't.
The problem has to do with the shutdown procedures. Once the system is
shut down, the damage is already done and the settings are lost.
Logging out, however, does not lose the
And so did I. (also an akonadi error, FWIW).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/710144
Title:
Xsession: unable to launch X session --- not found; falling back
to default session.
Running Natty under VirtualBox, the problem does not occur. I set the
time manually to a different date and time and then did the automatic
setting. It worked. However, the fact that I was running Natty in a
virtual environment might be relevant -- I don't know.
--
You received this bug
I've encountered the same behavior -- KDE panel clock says it can't
contact pool .ntp.org, but I can ping pool.ntp.org. I'm running Kubuntu
Maverick 10.10.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I've run the same thing myself on Natty under Virtual Box. In Natty, it
runs correctly for me. So the situation is clearly version-dependent,
and possibly particular to 10.10. Oddly and confusingly, if you call
keyserver.ubuntu.com over the Net and give it the key that Natty
accepts,
On Thursday, March 17, 2011 07:19:24 pm you wrote:
I just tried to reproduce your problem on 10.04 LTS, but couldn't:
$ sudo apt-key adv --recv-keys --keyserver keyserver.ubuntu.com
A8A515F046D7E7CF Executing: gpg --ignore-time-conflict --no-options
--no-default-keyring --secret-keyring
Public bug reported:
Binary package hint: apt
When gpg is called as the result of a call on apt-key, it gives a
misleading message if the key cannot be found by the keyserver. The
following transcript illustrates this:
pwa@pwa-K60IJ:~$ sudo apt-key adv --recv-keys --keyserver
The problem is worse than I originally realized. The touchpad
disablement is lost when I exit the Input Devices section of System
Settings, not just when I reboot. So in effect there's no way to
disable the touchpad ever, even though there's a provision for it.
What can I do to remove the
Public bug reported:
The 2.32.0-0ubuntu1 version of the package for cheese does not include
an icon. A very good icon can be found at
/usr/lib/openoffice/basis3.2/share/gallery/www-back/cheese.jpg (on my
system at least), but (a) it's a jpg file, which doesn't work as an
icon, and (b) in any
I tried apport-collect -p gnome-control-center 713880 as requested,
but got a whole bunch of errors. I tried to post the transcript here,
but for some mysterious reason the post was rejected, so I sent it to
Fabio personally as a last resort.
Unless there's something odd about my system, it
Public bug reported:
I'm running Skype under Kubuntu Meerkat on an Asus K60IJ laptop -- a
64bit environment. Until a few weeks ago, the video webcam test worked
for me, but now it doesn't.. I can't be sure about the date when it
stopped working, but I did discover that the libv4l package was
Public bug reported:
Binary package hint: synaptic
I added an invalid repository to the list in Other Software. (Of
course I didn't know it was invalid when I added it.) Then when I did a
Reload I got this complaint:
Failed to fetch
additional clarification: after adding the invalid repository to the
list, it didn't show up in the list.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/714235
Title:
Can't get rid of invalid
Fabio --
I tried, but I got this:
pwa@Asus-laptop:~$ apport-collect 713880
The authorization page:
(https://edge.launchpad.net/+authorize-token?oauth_token=Z80lXR0fpqFwXZtcJjLhallow_permission=WRITE_PRIVATE)
should be opening in your browser. After you have authorized
this program to access
Public bug reported:
If I go into System Settings / Input Devices / Touchpad and turn the
touchpad off, the setting is not retained after a reboot.
** Affects: ubuntu
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs,
Environment: Kubuntu 10.10 on an Asus K60IJ laptop, fully updated,
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/713880
Title:
System settings doesn't retain touchpad disablement
--
ubuntu-bugs
What is the best way to install the EnableBrightnessControl fix if
xorg.conf doesn't exist (a common situation now)? I tried creating
xorg.conf as
Section Device
Identifier Configured Video Device
Driver fbdev
Option RegistryDwords EnableBrightnessControl=1
Public bug reported:
Binary package hint: xorg
I first noticed that my screen was too bright and tried to adjust the
brightness with Fn-F5. Nothing happened right away, but after that
something that looked like a brightness control bar would pop up on my
screen every minute or so and then
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/703602
Title:
Brightness controls not working
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
I've determined that the external microphone does work, so the problem
is only with the internal one. On much closer examination I determined
that the internal microphone is actually working but at a near-zero
volume -- certainly nothing usable. The level at max is about 2%.
--
You received
Include me on the list of people with speaker/mike woes on an Asus
laptop. My machine is a K60IJ. I'm running Kubuntu 10.10 with
pulseaudio installed and everything fully updated. The result of lspci
-vv is:
00:1b.0 Audio device: Intel Corporation 82801I (ICH9 Family) HD Audio
Controller (rev
Addendum: I just discovered that the external mike works as Microphone
1. So it's only the internal one that's the problem.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/580183
Title:
asus eeepc
Further discovery: the internal speaker isn't totally muted, but it's
operating at what I would guess is the 5% level. Not enough to be of
any use, though.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
I'm running Kubuntu 10.10 on an Asus K60IJ laptop. I've tried fiddling
with alsamixer, etc., with no success. I've also tried using Sound
Recorder, and the volume meter shows nothing when I tap the mike or
talk. There are quite a few other reports out there about
I spoke a little too quickly. The image is correctly oriented in cheesd
and XawTV -- but not, I just discovered, in Skype. Does anyone know why
the Skype behavior should be different?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Good news! My image is no longer upside down in Meerkat, on an Asus
K60IJ laptop. :=)) Saves me the agony and risk of disassembling my
laptop lid, which might not have solved the problem anyway!!!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
Some observations:
1. After any change, you probably need to start up alsamixer again and
make sure that Front is unmuted and at a good volume. Without that,
nothing else is likely to work.
2. If you start up with headphones plugged in, you probably will get
sound on both headphones and
Public bug reported:
I've been regularly updating the alsa-driver package, and it appears to
be quite unstable. Each update behaves differently than the previous
one, it seems.
Here's what I have now, according to the Synaptic history:
linux-alsa-driver-modules-2.6.35-22-generic
** Attachment added: Snapshot of alsamixer
https://bugs.launchpad.net/bugs/674741/+attachment/1731777/+files/snapshot3.png
--
No sound, kmix indicates dummy output
https://bugs.launchpad.net/bugs/674741
You received this bug notification because you are a member of Ubuntu
Bugs, which is
** Attachment added: The kmix window
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/674741/+attachment/1731786/+files/snapshot4.png
--
No sound, kmix indicates dummy output
https://bugs.launchpad.net/bugs/674741
You received this bug notification because you are a member of
I rebooted and the sound was working for perhaps half an hour, but then
it died. alsamixer was running at the time, and a snapshot of
alsamixer, showing the error messages, might be helpful. The error
message began with Connection to PulseAudio daemon closed.
** Attachment added: snapshot5.png
When trying to start kmix (and not succeeding), I got this:
QMetaObject::invokeMethod: No such method
KMixApp::loadCommandLineOptionsForNewInstance()
QInotifyFileSystemWatcherEngine::addPaths: inotify_add_watch failed: No such
file or directory
QFileSystemWatcher: failed to add paths:
With the latest version of alsabase (1.0.23+dfg-1ubuntu4), the behavior
of alsamixer is peculiar and surprising, but at least not unworkable:
(1) With IHP off, front controls the active output even if that output
is the HP. Unplugging and replugging the HP mutes it, but it can be
unmuted.
(2)
One other oddity I just discovered: with IHP on, muting either the HP or
the front has the effect of muting the front.
--
Headphone jack not working in Asus K60I
https://bugs.launchpad.net/bugs/669224
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
The situation is getting curiouser and curiouser. Early this morning I
installed another large batch of updates. After the installation the
headphones were working and the alsamixer column was no longer greyed
out.
But then I rebooted and disaster struck in the form of a hangup at the
Checking
My experience is not quite the same as Wayne's, possibly because I made
the Lucid - Maverick transition earlier. I had the headphones working
under 10.10; it was the recent update that killed them.
--
Headphone jack not working in Asus K60I
https://bugs.launchpad.net/bugs/669224
You received
** Changed in: alsa-driver (Ubuntu)
Status: Incomplete = Opinion
** Changed in: alsa-driver (Ubuntu)
Status: Opinion = Incomplete
--
Headphone jack not working in Asus K60I
https://bugs.launchpad.net/bugs/669224
You received this bug notification because you are a member of Ubuntu
After today's system update, the sound doesn't work at all. If I call
asound on a .wav file, it hangs.
--
Headphone jack not working in Asus K60I
https://bugs.launchpad.net/bugs/669224
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
I should have mentioned that the troublesome updates have updated linux-
alsa-driver-modules (both server and generic). My current version is
2.6.35-22.201011021600. That module has been updated four times in the
last week (11/3, 11/1, 10/31, 10/30).
--
Headphone jack not working in Asus K60I
I probably could verify that the updates to linux-alsa-driver-modules
are at fault if I could revert to the version before the first update.
Here's what that update installed:
linux-alsa-driver-modules-2.6.35-22-generic (2.6.35-22.201010291600)
linux-alsa-driver-modules-2.6.35-22-server
OK, I succeeded in turning on Independent HP -- but the headphone is
still greyed out, and plugging it in with music playing through the
front speakers has no effect at all. So I don't even get the muting
effect. Because of that greying, I get the impression that the problem
is not really
Well, it did work correctly until my latest update, so it must be
possible to fix it. I'm not sure just what got updated, though -- I did
the regular update that Kubuntu recommends. My guess is that the
problem lies in the latest changes to alsa-base or pulseaudio. If it
helps, I'm guessing
This seems related to, though not the same as, Bug 582234. According to
the reporter's surmise, the greying of the headphone column means that
the headphone is not being detected. So perhaps the issue is hardware-
related after all. But it's still related to the update.
--
Headphone jack not
See also Bug 669224.
--
Main sound mixer mutes automatically every few seconds
https://bugs.launchpad.net/bugs/582234
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
I removed that line and rebooted. No change in behavior that I can
see. The headphone is still greyed out in alsamixer..
--
Headphone jack not working in Asus K60I
https://bugs.launchpad.net/bugs/669224
You received this bug notification because you are a member of Ubuntu
Bugs, which is
I downloaded the script and tried running it. It printed an informative
message about what it was doing and then stopped without producing any
visible diagnostic info. I looked at the help and tried running it with
the option --output alsainfo. This time it uploaded the collected
information to
Here is the output of alsa-info, attached.
** Attachment added: alsa-info.txt.z0nZ4pew67
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/669224/+attachment/1719696/+files/alsa-info.txt.z0nZ4pew67
--
Headphone jack not working in Asus K60I
https://bugs.launchpad.net/bugs/669224
Sorry, I can'f figure out where those settings are. They don't seem to
be either in System Settings or in alsamixer. Is that perhaps something
in gnome that isn't in Kubuntu? The System tab in the K menu has
nothing for preferences.
--
Headphone jack not working in Asus K60I
Independent HP shows up as OFF, and M has no effect. I'm attaching
two screenshots showing the alsamixer settings (including the greyed-out
headphone setting). It took me a while to find Independent HP because
even after scrolling, it's labelled just as Independent.
** Attachment added:
** Attachment added: snapshot1.png
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/669224/+attachment/1720132/+files/snapshot1.png
--
Headphone jack not working in Asus K60I
https://bugs.launchpad.net/bugs/669224
You received this bug notification because you are a member of
The bug is much worse and more complex than I realized:
1. ubuntu-bug alsa-base hangs on Collecting Information, with the
progress bar set at the beginning, and cannot be cancelled. The only
way to stop it is to exit the shell.
2. kmix refuses to unmute or display its window.
3. I have no
I just installed the latest updates. The built-in sound now works --
but the headphone still does not. I don't see how to report that with
ubuntu-bug, since i do get sound -- just not *all* the sound.
--
No sound after Maverick Meerkat upgrade
https://bugs.launchpad.net/bugs/647539
You
Public bug reported:
I have an Asus K60 laptop using the VT1708S sound chip. Until the
update about a week ago, all sound features worked correctly, and 10.10
had been in use for several weeks. After the last update, the headphone
jack became disabled, and is now shown as greyed out in
--
Headphone jack not working in Asus K60I
https://bugs.launchpad.net/bugs/669224
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
** Attachment added: alsa-base.conf
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/669224/+attachment/1718641/+files/alsa-base.conf
--
Headphone jack not working in Asus K60I
https://bugs.launchpad.net/bugs/669224
You received this bug notification because you are a member of
Same problem with an Acer K60I laptop. I tried to use ubuntu-bug
audio but got this:
Please use the report bug feature, available in the menu of the application,
or use ubuntu-bug packagename to report a bug against the particular
package.
There is no obvious application for this bug, and I
One symptom in my case is that the column for the headphone in alsamixer
shows up in grey (and cannot be unmuted).
--
[Acer aspire 7736] Playback not working due to incorrect SKU override
https://bugs.launchpad.net/bugs/617647
You received this bug notification because you are a member of Ubuntu
ubuntu-bug audio is useless here. It gives the message:
Please use the report bug feature, available in the menu of the application,
or use ubuntu-bug packagename to report a bug against the particular
package.
I have no idea what the appropriate application is, and what would
packagename be
I just followed David Henningsson's advice as to how to report this bug
for different hardware. So what is the right way to do that? I've
discovered that the soundchip in my Asus K60 laptop is a VIA82xx, which
I guess is diffferent from the Intel chips.
--
No sound after Maverick Meerkat
Public bug reported:
Binary package hint: base-installer
When my Kubuntu system was installed, /etc/fstab was created as part of
the installation process. I'm running a multi-boot system that includes
Windows 7. The fstab line for Windows 7 was:
/dev/sda2
I had the problem after upgrading from 10.04 to 10.10. In my case I got
past it by dumping wicd and going over to knetworkmanager, even though
in the past I've done better with wicd.
This is a particularly irksome bug (in the latest wicd, I assume) since
there's no way to verify absolutely that
Public bug reported:
Binary package hint: plasma-desktop
If I open the K menu, right-click on an application, and select Add to
Desktop, it appears that nothing is being added to the desktop. But in
fact the correct item is being added -- to a different desktop! In
other words, if I choose Add
Public bug reported:
Binary package hint: xorg
Before upgrading to kernel level 2.6.32-24, I was unable to get screen
resolution better than 1024x768. After the upgrade I can get what I
want via System Settings / Display: 1280 x 1024. But the resolution
setting is lost after a reboot; after
** Attachment added: BootDmesg.txt
https://bugs.launchpad.net/bugs/630320/+attachment/1543505/+files/BootDmesg.txt
** Attachment added: CurrentDmesg.txt
https://bugs.launchpad.net/bugs/630320/+attachment/1543506/+files/CurrentDmesg.txt
** Attachment added: Dependencies.txt
This problem has resurfaced in 10.04 Lucid. Until the 2.6.32-24 kernel
release I was unable to get resolutions greater than 1024x768. This
later kernel release solved that problem -- but now I still get sent
back to the lower resolution after a reboot.
--
Screen and Graphics lose resolution
See also bug #493542 and possibly others.
--
Webcam image flipped - libv4l issue or kernel?
https://bugs.launchpad.net/bugs/561957
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
Same problem on an Asus K60IJ laptop. There are numerous posts about
this and many laptops affected by it. Windows had the same problem but
it was fixed there by using updated Chacony drivers. There is a fix
described in
http://ubuntuforums.org/showthread.php?p=8925031#post8925031, but that's
Public bug reported:
There is a constellation of bugs relating to the difficulty in Kubuntu
9.10 in getting the screen resolution above 800x640.
1. The Live CD for Kubuntu 9.10 is stuck in low resolution, with no
obvious way to change it.
2. The programs Nvidia X Configuration Settings and
The problem does not lie in the drivers from Nvidia, which are perfectly
capable of producing high resolutions.
This problem is apparently new to Karmic Koala, since I haven't
encountered it in earlier versions of Kubuntu.
--
Inability to set high screen resolutions in nvidia-xconfig, Systems
The Launchpad bug system provides no clear way of reporting bugs in the
installation process. These bugs are not associated with packages in
any obvious way since the packages haven't even been installed.
--
Provide central application to file bugs
https://bugs.launchpad.net/bugs/521703
You
Public bug reported:
Binary package hint: mount
When my system starts up, my /mediavault file does not get mounted
initially, though I can mount it explicitly later on. The /etc/fstab
entry for it is:
//hpmediavault/FileShare /mediavault cifs
users,auto,rw,nodev,noexec,_netdev,guest 0 0
After changing the user of /mediavault to pwa as you suggested, the
unprivileged mount works. But since users is in the fstab line, that
shouldn't matter.
--
_netdev not working; other mount.cifs problems
https://bugs.launchpad.net/bugs/380938
You received this bug notification because you are
Here is the output you requested:
p...@lepiota:~$ umount /mediavault
umount: /mediavault is not mounted (according to mtab)
p...@lepiota:~$ mount | grep mediavault
p...@lepiota:~$ ls -ld /mediavault
drwxrwxrwx 2 root root 4096 2009-05-06 00:35 /mediavault
p...@lepiota:~$ ls -l $(which mount.cifs)
After changing the user of /mediavault to pwa as you suggested, the
unprivileged mount works. But since users is in the fstab line, that
shouldn't matter.
--
_netdev not working; other mount.cifs problems
https://bugs.launchpad.net/bugs/380938
You received this bug notification because you are
Public bug reported:
I'm running the Jaunty kde3.5 remix (Ubuntu 9.04). I have several
related problems with automount of a cifs share, shown by the following
transcript:
p...@lepiota:~$ mount /mediavault
mount error: permission denied or not superuser and mount.cifs not installed
SUID
I have the same problem under OpenSUse 11.1. Firefox simply disappears
without warning and with no apparent cause. It even happens when I'm
working in a different window, or when I leave the computer idle. I
don't even know where to locate any diagnostic information. Typing
about:crashes,
I'm having that problem also. In fact, Firefox sometime closes when the
computer is just sitting idle. It happens very often.
I wish there was a logfile somewhere that might give an indication of
the cause. Does anyone know of such? /var/log/messages has nothing.
--
Firefox closes
The NFS mount problem has been around now for quite a while. I think I
first reported it (under another number) a couple of years ago. It must
be a bug since it should not be possible for a user to provoke an
internal error no matter what he or she does. And it's been encountered
by quite a
Perhaps if no one can determine the cause of the error, it might be
worthwhile to modify the code in order to produce a more revealing (to
the code author, anyway) error message.
--
8.04 8.10 nfs clients report internal error when attempting to mount NFS
exports
Just got it again (Kubuntu 8.041). There are many chicken soup fixes
around that work for particular people in particular installations, but
I have yet to see a clear explanation of the cause of the error and a
universal fix for it. There is clearly a bug here.
--
Kde error message on kubuntu:
Automount of memory sticks just started working for me, but I don't know
why. The last thing I did was to remove the entry for /dev/sdb1 from
/etc/fstab -- but I had tried working without that entry previously,
without success. I now can mount two sticks simultaneously and I get
the new medium
It happens with multiple memory sticks as well:
[EMAIL PROTECTED]:/etc/kubuntu-default-settings# mount /dev/sdc1 /media/USB1
[EMAIL PROTECTED]:/etc/kubuntu-default-settings# ls -ld /media/USB1
drwxr-xr-x 8 root root 16384 1969-12-31 19:00 /media/USB1
[EMAIL
Public bug reported:
I'm running Kubuntu Hardy 8.04.1. When I insert a memory stick into my
machine, it doesn't automount. It is possible to mount it explicitly
with mount /dev/sdb1 /media/usb0, but even then it has the wrong
permissions: read-only for anyone other than root (and chmod fails to
The problem is that since the relationship between sources.list and the
listings in adept isn't documented in an obvious place, it's difficult
to know the full effect of modifying one or the other. Since there
doesn't seem to be a help file for adept, this information could
usefully be inserted
I'm having similar problems, running Kubuntu Hardy Heron 8.04.1. I've
installed usbmount, and now my USB memory sticks automount just fine --
except that I don't get any notifications. Systems settings /
Notifications / Storage Media Notifications shows the expected triplet
of Open in New
I now find that if I install automount, automounting works perfectly --
except that I get no notifications, even though I've specified them in
Systems Settings / Notifications. (Kubuntu Hardy 8.04.1, fully
updated.)
--
usb stick does not automount in Ubuntu 8.04 RC
The trouble is that I haven't been able to locate a copy of the
distributed hal.conf, so I can't say what deny lines were in it. I
actually deleted them rather than just commenting them out.
Meanwhile I've been hunting in vain for some explanation of the contents
of hal.conf.
--
package hal
I suppose the central point here is that errors in an existing hal.conf
prevent hal from being reinstalled. That in itself is probably a bug,
since if you reinstall a package, the reinstallation shouldn't in any
case be disrupted by the previous version of that package.
--
package hal
I found the fix to this, thanks to another post that I cannot locate at
the moment. The file /etc/dbus-1/system.d/hal.conf has contradictory
information. Removing the deny lines enables the hal installation to
work. The incorrect hal.conf file is a bug in its own right, but I
don't know how to
Public bug reported:
Binary package hint: hal
The file /etc/dbus-1/system.d/hal.conf contains contradictory policies
-- the denys don't agree with the allows. Unfortunately, after
fixing the problem in my system, I haven't figured out how to retrieve
the distributed version of that file to cite
The problem lies in contradictory policies in the file
/etc/dbus-1/system.d/hal.conf -- the deny's don't agree with the allow's
and shouldn't be there. Unfortunately, after fixing the problem, I
haven't been able to retrieve the original hal.conf to cite the error
more specifically.
--
package
That doesn't work because of the ubiquitous hal install problem:
[EMAIL PROTECTED]:~# apt-get install sysv-rc=2.86.ds1-14.1ubuntu45
Reading package lists... Done
Building dependency tree
Reading state information... Done
sysv-rc is already the newest version.
0 upgraded, 0 newly installed, 0 to
I just got the error exit 1 after attempting to reinstall hal. No other
configuration problems I'm aware of right now. (Kubuntu 8.04).
--
package hal 0.5.11~rc2-1ubuntu3 failed to install/upgrade: subprocess
post-installation script returned error exit status 1
101 - 200 of 229 matches
Mail list logo
