I have a Vostro 1500 and the same problems.
"gconftool-2 --get /apps/gnome_settings_daemon/keybindings/eject"
gives me
XF86Eject
and
sudo showkey -k
returns:
(FN+F1) keycode 205 press
(FN+F3) keycode 236 press
(FN+F10) keycode 162 press
Worked fine in Hardy before, though.
--
Hotkeys stopped fu
Public bug reported:
Binary package hint: linux-image-2.6.24-18-generic
The kernel module RTL8187 fails to load (not sure since which kernel).
Loading with sudo modprobe rtl8187 returns:
FATAL: Error inserting rtl8187
(/lib/modules/2.6.24-18-generic/kernel/drivers/net/wireless/rtl8187.ko):
Unk
Seems to be connected to https://bugs.launchpad.net/ubuntu/+source
/linux-meta/+bug/200953 somehow?
--
[regression] Realtek 8187L does not work
https://bugs.launchpad.net/bugs/237457
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ub
Might this one here be related to this bug?
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/237457
I am not sure, can anyone just modprobe rtl8187 and see if there are the same
errors? You don't even need the card, I get these errors immediately, though
the module is there...
--
rtl8180 an
Might this one here be related to this bug?
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/237457
I am not sure, can anyone just modprobe rtl8187 and see if there are the same
errors? You don't even need the card, I get these errors immediately, though
the module is there...
--
rtl8180 an
*** This bug is a duplicate of bug 194887 ***
https://bugs.launchpad.net/bugs/194887
Just realised this bug is a duplicate. Would like to see it fixed in
backports, though.
** This bug has been marked a duplicate of bug 194887
[hardy] rtl8187 doesn't load on 2.6.24 along with mac80211 and
Sorry for inconvenience, just realized this is another bug
(incompatibility of iwlwifi and rtl8187-stack).
--
rtl8180 and rtl818x disabled in kernel Makefile
https://bugs.launchpad.net/bugs/184788
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to U
Just filed an own bug only to realize this one reflects the same problem. Now
marked as duplicate.
If there is no chance to fix it, you might try the driver based on the older
stack ieee80211. Compiled fine here and works, however, I do not see this as
satisfying solution.
--
[hardy] rtl8187
*** This bug is a duplicate of bug 194887 ***
https://bugs.launchpad.net/bugs/194887
Well, now, after my iwlwifi-modules are unloaded, the module loads fine. That's
after I realized that this one is a duplicate.
Module loads even when device not connected - the errors reported here even
kep
The hal-update that arrived lately (yesterday?) fixes this, it seems.
However, unblacklisting the video-module breaks FN-F8 (CRT/LCD-Switcher) for
me.
Brightness-control works fine again, even with video-module loaded.
--
Multiple key presses being reported after pressing an Fn key only once
h
The hal-update that arrived lately (yesterday?) fixes this, it seems.
However, unblacklisting the video-module breaks FN-F8 (CRT/LCD-Switcher) for me.
Brightness-control works fine again, even with video-module loaded.
--
[hardy] [regression] LCD brightness control (Dell) no longer works
https://
The hal-update that arrived lately (yesterday?) fixes this, it seems.
However, unblacklisting the video-module breaks FN-F8 (CRT/LCD-Switcher) for me.
Brightness-control works fine again, even with video-module loaded.
--
Screen brightness double level changes
https://bugs.launchpad.net/bugs/2074
The hal-update that arrived lately (yesterday?) fixes this, it seems.
However, unblacklisting the video-module breaks FN-F8 (CRT/LCD-Switcher) for me.
Brightness-control works fine again, even with video-module loaded.
Still, it would be nice if gnome-power-manager would have prevented it.
--
F
Sympy: Yes, I am. That was the name I had lost ^^. For me, blacklisting the
video-module fixed everything, and since the hal-info-update, I tried
unblacklisting video again.
Reboot proved brightness control was still working for me.
However, the FN-F8 to switch from CRT to DFP/LCD is gone.
Har
*** This bug is a duplicate of bug 220917 ***
https://bugs.launchpad.net/bugs/220917
** This bug has been marked a duplicate of bug 220917
iwl4965 firmware missing in alternate installer
--
[Gutsy Alternate CD] IWL4965 firmware not included for install.
https://bugs.launchpad.net/bugs/139
Works here with
Dell Vostro 1500
nVidia 8600 M GT (using the Beta-Driver)
Intel PRO/Wireless 4965 AGN
Same as before, maybe even faster.
Maybe only Intel-Graphic-Adapters are affected?
--
[Hardy] [Regression] 2.6.24-17-generic breaks suspend
https://bugs.launchpad.net/bugs/235186
You received t
Public bug reported:
Binary package hint: wodim
After upgrade to hardy (from gutsy), I can't burn any CD anymore.
Tried K3B, Brasero, gnome-baker and Nautilus so far.
Braseros log is attached.
Already tried:
Kernel option: combined_mode=ide => no changes
Possibly relevant information:
[EMAI
** Attachment added: "brasero-session.log"
http://launchpadlibrarian.net/14820010/brasero-session.log
** Also affects: brasero (Ubuntu)
Importance: Undecided
Status: New
** Also affects: k3b (Ubuntu)
Importance: Undecided
Status: New
** Also affects: nautilus-cd-burner (U
Problem of wodim / cdrkit, thus only affecting brasero - no brasero-bug!
** Changed in: brasero (Ubuntu)
Status: New => Invalid
--
Regression: All burn-apps based on wodim are broken since hardy-upgrade
https://bugs.launchpad.net/bugs/236065
You received this bug notification because you
Problem of wodim / cdrkit, thus only affecting nautilus-cd-burner - no
n-c-b-bug!
** Changed in: nautilus-cd-burner (Ubuntu)
Status: New => Invalid
--
Regression: All burn-apps based on wodim are broken since hardy-upgrade
https://bugs.launchpad.net/bugs/236065
You received this bug notif
Problem of wodim / cdrkit, thus only affecting k3b - no k3b-bug!
** Changed in: k3b (Ubuntu)
Status: New => Invalid
--
Regression: All burn-apps based on wodim are broken since hardy-upgrade
https://bugs.launchpad.net/bugs/236065
You received this bug notification because you are a member
Same behaviour with Windows (just tried a live-cd).
So it must be hardware or - far more likely - media related. Thus, this bug can
be closed.
** Changed in: cdrkit (Ubuntu)
Status: New => Invalid
** Visibility changed to: Private
--
Regression: All burn-apps based on wodim are broken
Can confirm this bug with an older Toshiba-Notebook and xUbuntu. Was
just wondering why everything was so slow, found this bug, changed
default depth and everything is fast again.
** Changed in: xserver-xorg-video-neomagic (Ubuntu)
Status: Invalid => Confirmed
--
default depth too high in
I experienced this problem, too, using the same setup.
Installing Pulseaudio 0.9.13 fixed it for me (there is a Jaunty-Backport for
Intrepid here: https://launchpad.net/~racb/+archive ).
Before installing it, please understand that installing from an external
package-source is on your own risk.
Public bug reported:
Binary package hint: ntfs-3g
Source-package: ntfs-3g
Version: 1:1.2506-1ubuntu2
Ubuntu-Version: 8.10 (Intrepid)
What I did:
Copying some 100 files to an NTFS-Partition. Suddenly, copying stopped with the
error: "Operation not supported" and showed that error for all files
Similar problems here.
Sound began to stutter after Upgrade Gutsy => Hardy in all SDL-applications
(most noticeable in Frozen-Bubble 2 which switched of eye-candy).
My temporary solution:
Remove "libsdl1.2debian-pulseaudio" and replace with "libsdl1.2debian-all".
Everything works perfect now,
Temporary workaround:
Remove "libsdl1.2debian-pulseaudio" and replace with "libsdl1.2debian-all".
However, this will bypass PulseAudio. I'm looking forward to a fix!
--
sdl patch for better pulseaudio support
https://bugs.launchpad.net/bugs/216397
You received this bug notification because you
*** This bug is a duplicate of bug 216397 ***
https://bugs.launchpad.net/bugs/216397
** This bug has been marked a duplicate of bug 216397
sdl patch for better pulseaudio support
--
PulseAudio driver for SDL does not work properly.
https://bugs.launchpad.net/bugs/225467
You received this
*** This bug is a duplicate of bug 216397 ***
https://bugs.launchpad.net/bugs/216397
** This bug has been marked a duplicate of bug 216397
sdl patch for better pulseaudio support
--
libsdl1.2debian-pulseaudio sound software mixing
https://bugs.launchpad.net/bugs/219893
You received this b
*** This bug is a duplicate of bug 216397 ***
https://bugs.launchpad.net/bugs/216397
** This bug has been marked a duplicate of bug 216397
sdl patch for better pulseaudio support
--
patch to fix sound problems when using pulse backend
https://bugs.launchpad.net/bugs/210423
You received th
Confirmed to work! Thank you very much, now I can play multiple things
at the same time again - finally.
--
sdl patch for better pulseaudio support
https://bugs.launchpad.net/bugs/216397
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
This is not limited to Firefox, but affects all applications using Java
6. The problem does not occur with Java 7, however.
** Also affects: sun-java6 (Ubuntu)
Importance: Undecided
Status: New
--
Maximizing most applications gives a black window.
https://bugs.launchpad.net/bugs/112568
*** This bug is a duplicate of bug 215702 ***
https://bugs.launchpad.net/bugs/215702
** This bug has been marked a duplicate of bug 215702
Hardy: fglrx not working for ATI card
--
[fglrx] Ubuntu 8.04 alpha 4 - restricted driver (ATI) causes low graphics mode
and touchpad double click er
*** This bug is a duplicate of bug 215702 ***
https://bugs.launchpad.net/bugs/215702
** This bug has been marked a duplicate of bug 215702
Hardy: fglrx not working for ATI card
--
ATI driver enabled 8.04 don't start
https://bugs.launchpad.net/bugs/207108
You received this bug notificatio
*** This bug is a duplicate of bug 415101 ***
https://bugs.launchpad.net/bugs/415101
** This bug has been marked a duplicate of bug 415101
Karmic: emacs22-gtk generated menus do not update (GTK only)
--
LaTeX menu doesn't open in emacs
https://bugs.launchpad.net/bugs/456875
You received t
*** This bug is a duplicate of bug 415101 ***
https://bugs.launchpad.net/bugs/415101
Not a bug in auctex, but in emacs-gtk, it seems. I manually upgraded auctex and
the problem remained.
Thus, I marked this as a duplicate of the emacs-gtk-menu-bug.
--
LaTeX menu doesn't open in emacs
https
Debian has just released a fixed package version, lua-posix 33.4.0-3:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=891541#34
It would be best if this could be synced before Bionic Beaver LTS is
released with the currently broken version.
** Bug watch added: Debian Bug tracker #891541
http
Thanks for searching out this info!
I grepped through all logs for "inot" and found no match (only the initial
inotify setup). So it seems sssd was not notified via inotify of the change.
That matches the behaviour that "strace" showed that "127.0.0.1" instead of
"127.0.0.53" was queried.
So
I'll test tomorrow if try_inotify=false in the [sssd] section also works
around this issue, unless someone beats me to it...
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1723350
Title:
sssd offline
Another issue appears to be...
When starting sssd in highest debug level, and then changing resolv.conf once
by doing:
$ touch foo
$ mv foo /run/systemd/resolve/stub-resolv.conf
(that's where the link target is pointing to), I see the expected:
(Tue Jun 12 00:16:57 2018) [sssd] [resolv_conf_inoti
@renbag: Do you see "sssd[be[896]: Backend is offline" in "systemctl status
sssd"?
Is your backend server given as hostname / fqdn in sssd.conf?
@ahasenack: try_inotify=false did not change the issue at all. With strace, I
can still see 127.0.0.1 being queried. IMHO this can only be an ugly r
@renbag: It might be that in terms of timing, the DHCP server is also involved,
since it defines the time network-online.target takes to start. Our setup is
relatively slow, since we have a DHCP server under high load (several 1
leases) and are using a dhcrelay in between.
Potentially, you
After setting try_inotify to false, I see that the message that an
inotify was set up does not show up anymore, but no message that polling
is used instead is shown in the logs. If I understand the code
correctly, that's just right - a message will only be shown if
try_inotify is true and it actual
> For me, installing libcanberra-pulse worked.
So many thanks for this!
This is still required to fix things on Ubuntu 18.04!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/736349
Title:
"Test speak
Since it's still in proposed and a day is mostly over (and Europe is
asleep again) - could somebody outline / point me to the conditions for
a package to be moved from proposed to released?
This would be good to know to understand what is missing (and
potentially help?) instead of entering a lengt
@Ads2 Thanks for the link. Sadly, gdm3 is neither in the
autopkgtest-list, nor update-excuses, nor update-list, so it seems
things are stuck at an earlier stage and the documentation does not
clarify where to find out at which point help could be needed.
My intention was not to spam this repor
Could somebody please add Bionic back?
We observe this on Bionic, it's pretty random, mostly machines with fast root
devices (e.g. NVMEs) are affected. Backend is offline on boot and stays
offline.
Since it's so random and I don't want to enable debug information on all
machines we have, I can
@jakub-hrozek: When activating debug_level on some machines, which level
is high enough?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1723350
Title:
sssd offline on boot, stays offline forever
To
@ahasenack: Even in case things "work", I observe the following:
Jun 11 14:41:15 cip000 systemd[1]: Starting System Security Services Daemon...
Jun 11 14:41:24 cip000 sssd[920]: Starting up
Jun 11 14:41:25 cip000 sssd[be[998]: Starting up
Jun 11 14:41:28 cip000 sssd[1021]: Starting up
Jun 11 14:41
I've now had a machine with actual failure and debug_level=9 in sections sssd,
pam and nss.
No more information was produced, just tons of
org.freedesktop.sssd.Error.DataProvider.Offline .
Seems that official manual is outdated, will try with bitmasks next.
--
You received this bug notificat
I tried wiht 0x7770 now in all sections, but I don't get more info.
Now, sssd.log shows:
(Mon Jun 11 15:10:34:313118 2018) [sssd] [sss_ini_call_validators] (0x0020):
[rule/allowed_sssd_options]: Attribute 'debug_devel' is not allowed in section
'sssd'. Check for typos.
for each section :-(.
So
Argh! My fault, with the typo fixed, I see the following:
Jun 11 15:36:27 exp006 sssd[be[918]: Backend is offline
[...]
(Mon Jun 11 15:36:31 2018) [sssd] [message_type] (0x0200): netlink Message
type: 24
(Mon Jun 11 15:36:31 2018) [sssd] [route_msg_debug_print] (0x1000): route idx 2
flags 0 fami
Is this an inotify race due to the symlink-magic of systemd-resolved?
sssd.log:(Mon Jun 11 15:36:23 2018) [sssd] [_snotify_create] (0x0400):
Added a watch for /etc/resolv.conf with inotify flags 0x8D88 internal
flags 0x1 using function resolv_conf_inotify_cb after delay 1.0
# ls -la /etc/resolv.c
That's interesting.
strace'ing the sssd_be process, it seems that it's trying to contact 127.0.0.1
as DNS server, and fails.
systemd-resolved is running on 127.0.0.53 and works just fine.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubun
Needless to say, resolv.conf is:
nameserver 127.0.0.53
search OUR.INSTITUTION
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1723350
Title:
sssd offline on boot, stays offline forever
To manage noti
I can confirm that adding the described override, all works fine.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1723350
Title:
sssd offline on boot, stays offline forever
To manage notifications ab
This also mostly applies to us:
* Bionic, installed via network installer.
* We did not configure network explicitly, AFAICT, this means networkd is used.
However, we run with DHCP.
* sssd.conf uses FQDNs for the kerberos and ldap servers (I guess you meant
that)?
* We also provide backup serv
@monochromec:
If your motherboard really has a bios and your are not running in (U)EFI-mode,
you are hit by another bug likely unrelated to this one.
Please check your motherboard-datasheet whether you are using a BIOS or an
EFI-based system.
--
You received this bug notification because you
@monochromec:
If a search for the motherboard model and (U)EFI reveals nothing, and you have
no BIOS-emulation-options in the EFI-setup, I am not sure how to check.
Maybe a "dmesg | grep -i efi" could give an answer.
--
You received this bug notification because you are a member of Ubuntu
Bugs
Is this version also queued for Cosmic and Bionic?
I can only see it arrived for Disco, but on Bionic LTS and Cosmic, Axiom is
still completely unusable, and no fix has been released yet.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubunt
** Tags added: bionic cosmic
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1729601
Title:
binaries in /usr/lib/axiom-20170401/bin are missing
To manage notifications about this bug go to:
https://b
This can still be reproduced with more recent libxmlb (testted with
0.3.6 on Gentoo).
I have reported the issue to Gwyddion upstream with a proposed patch to remove
the broad matching:
https://sourceforge.net/p/gwyddion/mailman/gwyddion-devel/thread/9e1f6694-c39b-6131-796b-667f6e25f7e9%40googlema
62 matches
Mail list logo
