I have the same problem with eboard 1.1.3 on Debian Buster. The program
build is quite old (2016), hence it seems that the problem is with some
high-level library.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I can also confirm it in Ubuntu Gnome 17.04
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1650395
Title:
Strange large grey border around gnome-terminal when transparency is
enabled
To manage
It definitely could be. Personally, I think many of the issues mentioned
above are completely unrelated to Network Manager. Those cases should be
excluded from a bug report. Therefore I suggest that everyone who's
having problems check their beacon interval settings.
--
You received this bug
All of you who are affected by this bug, try the following: Change the
beacon interval on your router to the lowest value possible.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1589401
Title:
@anders-frisk650
Well done! Now we're getting somewhere.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1589401
Title:
cannot view wifi networks after re-enabling wifi
To manage notifications
@ghuisman:
I tried WICD for a few of weeks. My experiences were the same as yours.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1589401
Title:
cannot view wifi networks after re-enabling wifi
To
If people keep whining about bugs in network-manager, without even
trying WICD (or the like) for a couple of weeks, this thread is
meaningless!
I'm still not sure that the problems I experience are completely
unrelated to network-manager. I seem to have a more stable connection
with WICD, so far.
I'm eager to hear other members of this thread sharing their experience
with WICD (see #109 for installation intructions). Especially those with
a Intel wifi chip. If the the same connectivity issues remain in WICD, I
assume we could abandon the idea that these issues are to be derived to
I'm starting to doubt that network-manager is the root of all this mess.
Have any of you tried using WICD instead (an alternative network
manager)? I seem to have the same connectivity issues there. And just as
with network-manager, they appear at random.
Here's an instruction:
Just made a fresh installation of Ubuntu 16.04 and then upgraded to
16.10 through APT. I'm running kernel 4.8 and see no improvement
whatsoever in 16.10.
This bug is not fixed in any way, shape or form.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
'sudo iw dev wlan0 scan' (or in my case wlp13s0 instead of wlan0)
doesn't work for me. Here's the output:
command failed: Device or resource busy (-16)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I have Intel Wireless 3165 (rev 81)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1589401
Title:
cannot view wifi networks after re-enabling wifi
To manage notifications about this bug go to:
I still have the same issue, even after enabling static IP.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1589401
Title:
cannot view wifi networks after re-enabling wifi
To manage notifications
Thanks for the input about 16.10, Christian. I was considering an
upgrade to get rid of the problem, but now I will think twice before
doing so.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1589401
Have any of you tried using static IP adressess for your system?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1589401
Title:
cannot view wifi networks after re-enabling wifi
To manage
The arrows are gone for me too now (after reinstalling, I think), but
there are still connectivity issues. Either one has to wait a minute or
two for a wifi connection after bott up or put it in suspend mode (close
the lid) to establish a wifi connection.
--
You received this bug notification
It keeps working after reboot and suspend. I'm not sure exactly which
kernel version I used to run before re-installing, but this one is
called 4.4.0-34-generic.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
A complete re-installation of the entire operating system seems to have
done the trick for me (call it a workaround if you want)! I used the
exact same source (i.e. Ubuntu 16.04.1 LTS 64 bit from a USB stick) and
connecteded my wifi during installation. I also restored my home folder
(including
*** This bug is a duplicate of bug 1589401 ***
https://bugs.launchpad.net/bugs/1589401
** This bug is no longer a duplicate of bug 1576747
Network manager applet unable to control wifi after suspend in 16.04
** This bug has been marked a duplicate of bug 1589401
cannot view wifi
*** This bug is a duplicate of bug 1589401 ***
https://bugs.launchpad.net/bugs/1589401
** This bug has been marked a duplicate of bug 1589401
cannot view wifi networks after re-enabling wifi
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
*** This bug is a duplicate of bug 1589401 ***
https://bugs.launchpad.net/bugs/1589401
** This bug is no longer a duplicate of bug 1576747
Network manager applet unable to control wifi after suspend in 16.04
** This bug has been marked a duplicate of bug 1589401
cannot view wifi
*** This bug is a duplicate of bug 1576747 ***
https://bugs.launchpad.net/bugs/1576747
** This bug has been marked a duplicate of bug 1576747
Network manager applet unable to control wifi after suspend in 16.04
--
You received this bug notification because you are a member of Ubuntu
*** This bug is a duplicate of bug 1576747 ***
https://bugs.launchpad.net/bugs/1576747
** This bug has been marked a duplicate of bug 1576747
Network manager applet unable to control wifi after suspend in 16.04
--
You received this bug notification because you are a member of Ubuntu
This temporary solution seems to work for me:
sudo systemctl restart network-manager.service
Got it from http://askubuntu.com/questions/761180/wifi-doesnt-work-
after-suspend-after-16-04-upgrade
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
Public bug reported:
dont know
ProblemType: Package
DistroRelease: Ubuntu 13.04
Package: libreoffice-core 1:4.0.2-0ubuntu1
ProcVersionSignature: Ubuntu 3.8.0-32.47-generic 3.8.13.10
Uname: Linux 3.8.0-32-generic i686
NonfreeKernelModules: nvidia
ApportVersion: 2.9.2-0ubuntu8.4
Architecture: i386
Public bug reported:
Happened during boot.
ProblemType: Package
DistroRelease: Ubuntu 13.10
Package: udev 204-0ubuntu15
ProcVersionSignature: Ubuntu 3.11.0-11.17-generic 3.11.3
Uname: Linux 3.11.0-11-generic x86_64
ApportVersion: 2.12.5-0ubuntu1
Architecture: amd64
Date: Wed Oct 2 20:49:56 2013
Public bug reported:
While looking at zoomable pictures in Chromium, the cursor with the
magnifying glass is surrounded by a black or messy square. The square is
a about twice as big as the cursor.
To reproduce, paste this address in Chromium (resolution 1280 x 1024) and put
the mouse over the
After my saucy update today it seems to work! Good work!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1218815
Title:
[radeon] Graphic glitches and screen corruption (vertical lines) on
XMir
It seems to work together with the proprietary fglrx drivers, though.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1218815
Title:
[radeon] Graphic glitches and screen corruption (vertical lines)
Does merely installing this package cause banshee to hang, or must the
extension be enabled first?
Installing is no problem, enabling it causes banshee to hang a few minutes
later.
Banshee will hang again after a few seconds when killed and restarted.
Changing Addin
** Package changed: linux (Ubuntu) = ubuntu
** Changed in: ubuntu
Assignee: (unassigned) = Peter S (peter-sevemark)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/931168
Title:
14e4:4727
I had exactly the same issue, tried to make compat-wireless without success.
However this simple solution solved my problem: http://blog.homelinux.org/?p=327
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
just booted up and got the crash message
ProblemType: KernelOops
DistroRelease: Ubuntu 10.10
Package: linux-image-2.6.35-17-generic 2.6.35-17.23
Regression: Yes
Reproducible: No
ProcVersionSignature: Ubuntu 2.6.35-18.24-generic 2.6.35.3
Uname: Linux 2.6.35-18-generic x86_64
** Attachment added: AcpiTables.txt
https://bugs.launchpad.net/bugs/623710/+attachment/1516897/+files/AcpiTables.txt
** Attachment added: AlsaDevices.txt
https://bugs.launchpad.net/bugs/623710/+attachment/1516898/+files/AlsaDevices.txt
** Attachment added: AplayDevices.txt
Public bug reported:
Binary package hint: radiotray
As I add new stations in Radiotray with names with Swedish characters in
them (like å, ä and ö) the program crashes and the stations are not
added. If I first add a station without these characters and put the
foreign characters in the title
Seems like it was a program I installed that was keeping the CPU
working... I removed an extremly cpu intensive program called 'boinc'
and went back to normal. Too bad it didn't show up in the System
Monitor. If you want to see ALL the processes you're running, installi
htop. Open a terminal and
** Attachment added: Dependencies.txt
https://bugs.launchpad.net/bugs/616842/+attachment/1486198/+files/Dependencies.txt
** Attachment added: ProcMaps.txt
https://bugs.launchpad.net/bugs/616842/+attachment/1486199/+files/ProcMaps.txt
** Attachment added: ProcStatus.txt
I too am seeing crashes with gnome-power-manager:
(gnome-power-manager:2355): GLib-GObject-WARNING **:
/build/buildd/glib2.0-2.25.13/gobject/gsignal.c:2275: signal `proxy-status' is
invalid for instance `0x1406230'
12
Gdk-ERROR **: The program 'gnome-power-manager' received an X Window System
I too am seeing crashes in gnome-power-management:
(gnome-power-manager:2355): GLib-GObject-WARNING **:
/build/buildd/glib2.0-2.25.13/gobject/gsignal.c:2275: signal `proxy-status' is
invalid for instance `0x1406230'
12
Gdk-ERROR **: The program 'gnome-power-manager' received an X Window System
Public bug reported:
booted up and got the crash report
ProblemType: KernelOops
DistroRelease: Ubuntu 10.10
Package: linux-image-2.6.35-14-generic 2.6.35-14.20
Regression: Yes
Reproducible: No
ProcVersionSignature: Ubuntu 2.6.35-14.20-generic 2.6.35
Uname: Linux 2.6.35-14-generic x86_64
** Attachment added: AcpiTables.txt
http://launchpadlibrarian.net/53295006/AcpiTables.txt
** Attachment added: AlsaDevices.txt
http://launchpadlibrarian.net/53295007/AlsaDevices.txt
** Attachment added: AplayDevices.txt
http://launchpadlibrarian.net/53295008/AplayDevices.txt
**
** Attachment added: CoreDump.gz
http://launchpadlibrarian.net/53295219/CoreDump.gz
** Attachment added: Dependencies.txt
http://launchpadlibrarian.net/53295220/Dependencies.txt
** Attachment added: Disassembly.txt
http://launchpadlibrarian.net/53295221/Disassembly.txt
** Attachment
Public bug reported:
Binary package hint: mythexport
just upgraded from karmic to lucid. mythexport upgrade failed
ProblemType: Package
DistroRelease: Ubuntu 10.04
Package: mythexport 2.1.5-0ubuntu1
ProcVersionSignature: Ubuntu 2.6.32-24.39-generic 2.6.32.15+drm33.5
Uname: Linux
** Attachment added: Dependencies.txt
http://launchpadlibrarian.net/53204233/Dependencies.txt
** Attachment added: Df.txt
http://launchpadlibrarian.net/53204234/Df.txt
** Attachment added: Dmesg.txt
http://launchpadlibrarian.net/53204235/Dmesg.txt
** Attachment added:
Public bug reported:
got crash report right after boot up
ProblemType: KernelOops
DistroRelease: Ubuntu 10.10
Package: linux-image-2.6.35-14-generic 2.6.35-14.19
Regression: Yes
Reproducible: No
ProcVersionSignature: Ubuntu 2.6.35-14.19-generic 2.6.35
Uname: Linux 2.6.35-14-generic x86_64
** Attachment added: AcpiTables.txt
http://launchpadlibrarian.net/53022161/AcpiTables.txt
** Attachment added: AlsaDevices.txt
http://launchpadlibrarian.net/53022162/AlsaDevices.txt
** Attachment added: AplayDevices.txt
http://launchpadlibrarian.net/53022163/AplayDevices.txt
**
Public bug reported:
just surfing the web and got the report
ProblemType: KernelOops
DistroRelease: Ubuntu 10.10
Package: linux-image-2.6.35-11-generic 2.6.35-11.16
Regression: Yes
Reproducible: No
ProcVersionSignature: Ubuntu 2.6.35-11.16-generic 2.6.35-rc5
Uname: Linux 2.6.35-11-generic x86_64
** Attachment added: AcpiTables.txt
http://launchpadlibrarian.net/52617399/AcpiTables.txt
** Attachment added: AlsaDevices.txt
http://launchpadlibrarian.net/52617400/AlsaDevices.txt
** Attachment added: AplayDevices.txt
http://launchpadlibrarian.net/52617401/AplayDevices.txt
**
** Attachment added: CoreDump.gz
http://launchpadlibrarian.net/52617567/CoreDump.gz
** Attachment added: Dependencies.txt
http://launchpadlibrarian.net/52617568/Dependencies.txt
** Attachment added: Disassembly.txt
http://launchpadlibrarian.net/52617569/Disassembly.txt
** Attachment
** Attachment added: CoreDump.gz
http://launchpadlibrarian.net/52617603/CoreDump.gz
** Attachment added: Dependencies.txt
http://launchpadlibrarian.net/52617604/Dependencies.txt
** Attachment added: Disassembly.txt
http://launchpadlibrarian.net/52617605/Disassembly.txt
** Attachment
Public bug reported:
got the crash report just after start up - sitting idle.
ProblemType: KernelOops
DistroRelease: Ubuntu 10.10
Package: linux-image-2.6.35-10-generic 2.6.35-10.15
Regression: Yes
Reproducible: No
ProcVersionSignature: Ubuntu 2.6.35-11.16-generic 2.6.35-rc5
Uname: Linux
** Attachment added: AcpiTables.txt
http://launchpadlibrarian.net/52570204/AcpiTables.txt
** Attachment added: AlsaDevices.txt
http://launchpadlibrarian.net/52570205/AlsaDevices.txt
** Attachment added: AplayDevices.txt
http://launchpadlibrarian.net/52570206/AplayDevices.txt
**
** Visibility changed to: Public
--
npviewer.bin crashed with SIGSEGV
https://bugs.launchpad.net/bugs/609771
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
** Visibility changed to: Public
--
npviewer.bin crashed with SIGSEGV
https://bugs.launchpad.net/bugs/604995
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
Public bug reported:
just sitting idle after boot up.
ProblemType: KernelOops
DistroRelease: Ubuntu 10.10
Package: linux-image-2.6.35-10-generic 2.6.35-10.15
Regression: Yes
Reproducible: No
ProcVersionSignature: Ubuntu 2.6.35-10.15-generic 2.6.35-rc5
Uname: Linux 2.6.35-10-generic x86_64
** Attachment added: AcpiTables.txt
http://launchpadlibrarian.net/52489420/AcpiTables.txt
** Attachment added: AlsaDevices.txt
http://launchpadlibrarian.net/52489421/AlsaDevices.txt
** Attachment added: AplayDevices.txt
http://launchpadlibrarian.net/52489422/AplayDevices.txt
**
Public bug reported:
just booted up - don't know how to replicate
ProblemType: KernelOops
DistroRelease: Ubuntu 10.10
Package: linux-image-2.6.35-8-generic 2.6.35-8.13
Regression: Yes
Reproducible: No
ProcVersionSignature: Ubuntu 2.6.35-8.13-generic 2.6.35-rc5
Uname: Linux 2.6.35-8-generic
** Attachment added: AlsaDevices.txt
http://launchpadlibrarian.net/52045878/AlsaDevices.txt
** Attachment added: AplayDevices.txt
http://launchpadlibrarian.net/52045879/AplayDevices.txt
** Attachment added: BootDmesg.txt
http://launchpadlibrarian.net/52045880/BootDmesg.txt
**
Public bug reported:
just sitting idle after boot up and got the crash report
ProblemType: KernelOops
DistroRelease: Ubuntu 10.10
Package: linux-image-2.6.35-8-generic 2.6.35-8.13
Regression: Yes
Reproducible: No
ProcVersionSignature: Ubuntu 2.6.35-8.13-generic 2.6.35-rc5
Uname: Linux
** Attachment added: AlsaDevices.txt
http://launchpadlibrarian.net/52046178/AlsaDevices.txt
** Attachment added: AplayDevices.txt
http://launchpadlibrarian.net/52046179/AplayDevices.txt
** Attachment added: BootDmesg.txt
http://launchpadlibrarian.net/52046180/BootDmesg.txt
**
Public bug reported:
just booted up and got this crash message.
ProblemType: KernelOops
DistroRelease: Ubuntu 10.10
Package: linux-image-2.6.35-8-generic 2.6.35-8.13
Regression: Yes
Reproducible: No
ProcVersionSignature: Ubuntu 2.6.35-8.13-generic 2.6.35-rc5
Uname: Linux 2.6.35-8-generic x86_64
** Attachment added: AlsaDevices.txt
http://launchpadlibrarian.net/52012073/AlsaDevices.txt
** Attachment added: AplayDevices.txt
http://launchpadlibrarian.net/52012074/AplayDevices.txt
** Attachment added: BootDmesg.txt
http://launchpadlibrarian.net/52012075/BootDmesg.txt
**
Public bug reported:
Just sitting idle. Don't know how to replicate.
ProblemType: KernelOops
DistroRelease: Ubuntu 10.10
Package: linux-image-2.6.35-7-generic 2.6.35-7.12
Regression: Yes
Reproducible: No
ProcVersionSignature: Ubuntu 2.6.35-7.12-generic 2.6.35-rc4
Uname: Linux 2.6.35-7-generic
** Attachment added: AlsaDevices.txt
http://launchpadlibrarian.net/51867758/AlsaDevices.txt
** Attachment added: AplayDevices.txt
http://launchpadlibrarian.net/51867759/AplayDevices.txt
** Attachment added: BootDmesg.txt
http://launchpadlibrarian.net/51867760/BootDmesg.txt
**
Public bug reported:
just got the report of a crash - sitting idle.
ProblemType: KernelOops
DistroRelease: Ubuntu 10.10
Package: linux-image-2.6.35-7-generic 2.6.35-7.12
Regression: Yes
Reproducible: No
ProcVersionSignature: Ubuntu 2.6.35-7.12-generic 2.6.35-rc4
Uname: Linux 2.6.35-7-generic
** Attachment added: AlsaDevices.txt
http://launchpadlibrarian.net/51898200/AlsaDevices.txt
** Attachment added: AplayDevices.txt
http://launchpadlibrarian.net/51898201/AplayDevices.txt
** Attachment added: BootDmesg.txt
http://launchpadlibrarian.net/51898202/BootDmesg.txt
**
Public bug reported:
just surfing the web and got the crash report.
ProblemType: KernelOops
DistroRelease: Ubuntu 10.10
Package: linux-image-2.6.35-7-generic 2.6.35-7.12
Regression: Yes
Reproducible: No
ProcVersionSignature: Ubuntu 2.6.35-7.12-generic 2.6.35-rc4
Uname: Linux 2.6.35-7-generic
** Attachment added: AlsaDevices.txt
http://launchpadlibrarian.net/51899757/AlsaDevices.txt
** Attachment added: AplayDevices.txt
http://launchpadlibrarian.net/51899758/AplayDevices.txt
** Attachment added: BootDmesg.txt
http://launchpadlibrarian.net/51899759/BootDmesg.txt
**
/sign
I also wasted a lot of time trying to figure out what's wrong.
Stoto
Sent from my iPhone.
On 2010.06.14., at 10:00, Otto Kekäläinen o...@sange.fi wrote:
I just wasted some time trying to figure out why what I am doing wrong
in passing the timeout parameter to notify-send.
Could you
However I wonder if xtide is past it's time
Considering that the link you provided uses xtide as backend, that's
funny! ;-)
--
xtide transparent in Ubuntu
https://bugs.launchpad.net/bugs/332778
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Thanks!
--
void variable with ctypes.el
https://bugs.launchpad.net/bugs/162954
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
V33.5 is released upstream.
--
m-x debian-bug doesn't point to ubuntu instead
https://bugs.launchpad.net/bugs/58241
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
However i am able to control the brightness width the following command:
sudo echo 180 | sudo tee
/sys/devices/platform/applesmc.768/leds/smc::kbd_backlight/brightness
Where 180 is the brightness, it goes from 0 to 255.
Any way to bind it to the keyboard backlight keys?
--
[Jaunty] MacBook
I found a solution:
I made a script, with that i can control the brightness:
st...@stoto-laptop:~$ cat backlight.sh
#!/bin/bash
$act
act=`cat /sys/devices/platform/applesmc.768/leds/smc::kbd_backlight/brightness`
echo $1
case $1 in
inc)
if [[ $act -lt 255 ]]; then
I had to make a little modification for the script so it will work after
reboot too:
st...@stoto-laptop:~$ cat backlight.sh
#!/bin/bash
if [ `ls -al
/sys/devices/platform/applesmc.768/leds/smc::kbd_backlight/brightness | awk
{'print $1'}` != -rwxrwxrwx ]; then
gksudo chmod 777
I attached the script.
** Attachment added: backlight.sh
http://launchpadlibrarian.net/48162134/backlight.sh
--
[Jaunty] MacBook 5.1 keyboard backlight not supported
https://bugs.launchpad.net/bugs/337945
You received this bug notification because you are a member of Ubuntu
Bugs, which is
I have a fresh install of 10.4 and the problem still exists. nvidia-bl
package fixed my screen backlight control but, i still cant activate my
keyboard backlight on my macbook 5.1. I will attach a report.
** Tags added: apport-collected
--
[Jaunty] MacBook 5.1 keyboard backlight not supported
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.21.
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: stoto 1467 F pulseaudio
CRDA: Error: [Errno 2] No such file or directory
Card0.Amixer.info:
Card hw:0 'NVidia'/'HDA NVidia at
apport information
** Attachment added: AlsaDevices.txt
http://launchpadlibrarian.net/48051263/AlsaDevices.txt
--
[Jaunty] MacBook 5.1 keyboard backlight not supported
https://bugs.launchpad.net/bugs/337945
You received this bug notification because you are a member of Ubuntu
Bugs, which is
apport information
** Attachment added: AplayDevices.txt
http://launchpadlibrarian.net/48051264/AplayDevices.txt
--
[Jaunty] MacBook 5.1 keyboard backlight not supported
https://bugs.launchpad.net/bugs/337945
You received this bug notification because you are a member of Ubuntu
Bugs, which
apport information
** Attachment added: ArecordDevices.txt
http://launchpadlibrarian.net/48051265/ArecordDevices.txt
--
[Jaunty] MacBook 5.1 keyboard backlight not supported
https://bugs.launchpad.net/bugs/337945
You received this bug notification because you are a member of Ubuntu
Bugs,
apport information
** Attachment added: BootDmesg.txt
http://launchpadlibrarian.net/48051286/BootDmesg.txt
--
[Jaunty] MacBook 5.1 keyboard backlight not supported
https://bugs.launchpad.net/bugs/337945
You received this bug notification because you are a member of Ubuntu
Bugs, which is
apport information
** Attachment added: Card0.Amixer.values.txt
http://launchpadlibrarian.net/48051287/Card0.Amixer.values.txt
--
[Jaunty] MacBook 5.1 keyboard backlight not supported
https://bugs.launchpad.net/bugs/337945
You received this bug notification because you are a member of Ubuntu
apport information
** Attachment added: Card0.Codecs.codec.0.txt
http://launchpadlibrarian.net/48051289/Card0.Codecs.codec.0.txt
--
[Jaunty] MacBook 5.1 keyboard backlight not supported
https://bugs.launchpad.net/bugs/337945
You received this bug notification because you are a member of
apport information
** Attachment added: CurrentDmesg.txt
http://launchpadlibrarian.net/48051290/CurrentDmesg.txt
--
[Jaunty] MacBook 5.1 keyboard backlight not supported
https://bugs.launchpad.net/bugs/337945
You received this bug notification because you are a member of Ubuntu
Bugs, which
apport information
** Attachment added: IwConfig.txt
http://launchpadlibrarian.net/48051305/IwConfig.txt
--
[Jaunty] MacBook 5.1 keyboard backlight not supported
https://bugs.launchpad.net/bugs/337945
You received this bug notification because you are a member of Ubuntu
Bugs, which is
apport information
** Attachment added: Lspci.txt
http://launchpadlibrarian.net/48051308/Lspci.txt
--
[Jaunty] MacBook 5.1 keyboard backlight not supported
https://bugs.launchpad.net/bugs/337945
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
apport information
** Attachment added: Lsusb.txt
http://launchpadlibrarian.net/48051312/Lsusb.txt
--
[Jaunty] MacBook 5.1 keyboard backlight not supported
https://bugs.launchpad.net/bugs/337945
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
apport information
** Attachment added: PciMultimedia.txt
http://launchpadlibrarian.net/48051314/PciMultimedia.txt
--
[Jaunty] MacBook 5.1 keyboard backlight not supported
https://bugs.launchpad.net/bugs/337945
You received this bug notification because you are a member of Ubuntu
Bugs, which
apport information
** Attachment added: ProcCpuinfo.txt
http://launchpadlibrarian.net/48051315/ProcCpuinfo.txt
--
[Jaunty] MacBook 5.1 keyboard backlight not supported
https://bugs.launchpad.net/bugs/337945
You received this bug notification because you are a member of Ubuntu
Bugs, which is
apport information
** Attachment added: ProcInterrupts.txt
http://launchpadlibrarian.net/48051317/ProcInterrupts.txt
--
[Jaunty] MacBook 5.1 keyboard backlight not supported
https://bugs.launchpad.net/bugs/337945
You received this bug notification because you are a member of Ubuntu
Bugs,
apport information
** Attachment added: ProcModules.txt
http://launchpadlibrarian.net/48051319/ProcModules.txt
--
[Jaunty] MacBook 5.1 keyboard backlight not supported
https://bugs.launchpad.net/bugs/337945
You received this bug notification because you are a member of Ubuntu
Bugs, which is
apport information
** Attachment added: UdevDb.txt
http://launchpadlibrarian.net/48051341/UdevDb.txt
--
[Jaunty] MacBook 5.1 keyboard backlight not supported
https://bugs.launchpad.net/bugs/337945
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
apport information
** Attachment added: WifiSyslog.txt
http://launchpadlibrarian.net/48051360/WifiSyslog.txt
--
[Jaunty] MacBook 5.1 keyboard backlight not supported
https://bugs.launchpad.net/bugs/337945
You received this bug notification because you are a member of Ubuntu
Bugs, which is
apport information
** Attachment added: UdevLog.txt
http://launchpadlibrarian.net/48051354/UdevLog.txt
--
[Jaunty] MacBook 5.1 keyboard backlight not supported
https://bugs.launchpad.net/bugs/337945
You received this bug notification because you are a member of Ubuntu
Bugs, which is
V33.5 of debian-el will have a debian-bug.el that supports an alternate
BTS using either the Bugs field in the control file for a given PACKAGE,
or the Send-To field in the file /usr/share/bug/PACKAGE/control.
See http://bugs.debian.org/222392
Does that work for Ubuntu?
(Pretty quiet here... I
The Debian version of emacs-goodies-el should fix Miia's problem.
Jack's problem isn't with emacs-goodies-el.
Peter
--
package emacs-snapshot 1:20080919-1 failed to install/upgrade: subprocess
post-installation script returned error exit status 1
https://bugs.launchpad.net/bugs/272810
You
I have left the empty file in emacs-goodies-el as a reminder, but the
autoloads are gone, so it shouldn't be a problem anymore.
Peter
** Changed in: emacs-goodies-el (Ubuntu)
Status: Confirmed = Fix Released
** Changed in: emacs-goodies-el (Ubuntu)
Status: Fix Released = In
Opps. Meant fixed upstream. I don't really understand the system here
so will leave it alone.
** Changed in: emacs-goodies-el (Ubuntu)
Status: Confirmed = Fix Released
** Changed in: emacs-goodies-el (Ubuntu)
Status: Fix Released = Confirmed
--
void variable with ctypes.el
Fixed upstream and uploaded to Debian in version 33.0
--
egocentric.el customizations mismatch
https://bugs.launchpad.net/bugs/109132
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
1 - 100 of 113 matches
Mail list logo
