This should only be a packaging issue as all of the correct dependencies
get marked for installation but the versions are incorrectly read as
being older not newer than the minimum version requirements.
--
E17 is not installible due to unmet depends
https://bugs.launchpad.net/bugs/613271
You
Public bug reported:
Lubuntu Maverick 10.10 beta with all current updates.
When launching programs from the applications menu that use gksu for
sudo privileges, invalid password is always returned regardless of the
password being correct or not. If the exec line in the .desktop file is
changed
on running gksu-properties I found that authentication mode was set to
su. Once changed to sudo everything was back to normal. This was a
fresh install of the Lubuntu 10.10 Beta iso with updates applied so
perhaps something needs changed?
--
Invalid password on applications starting through gksu
possible duplicate of bug 624095
--
Invalid password on applications starting through gksu
https://bugs.launchpad.net/bugs/643690
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 am experiencing the same issue in Lubuntu 10.10 beta. Running gksu-
properties and changing authentication mode to sudo fixes the problem
for me. Why is this not default?
--
gksu will not recognize password for administrative tasks in Maverick
https://bugs.launchpad.net/bugs/624095
You
I can confirm the bug also in 9.10 i386 with netbook remix.
--
epiphany-extensions-more is not up to date in Karmic
https://bugs.launchpad.net/bugs/452845
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
This has been confirmed in a thread on the ubuntu forums by several
individuals. It affects the system anytime x is running and the nvidia
restricted drivers are being used, including shutdown.
** Changed in: linux-meta (Ubuntu)
Status: New = Confirmed
** Changed in:
Public bug reported:
guidance-powermanager and gnome-power-manager are not updating the
battery state. The state is sometimes updated when the AC power state is
changed, but not consistantly. This was happening with the last update
to kernel 2.6.24-8 and is still present in 2.6.24-10.
**
** Changed in: hal (Ubuntu)
Sourcepackagename: linux-meta = hal
--
battery state not updating
https://bugs.launchpad.net/bugs/196606
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
Sorry, I have found this bug is a duplicate of #194719
--
battery state not updating
https://bugs.launchpad.net/bugs/196606
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
Sorry... I thought I included it.
http://ubuntuforums.org/showthread.php?t=668414
--
virtual terminals and dpms resume video scrambled
https://bugs.launchpad.net/bugs/181114
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
Public bug reported:
Running Kubuntu Hardy 8.04 alpha 2.6.24-8 generic kde 3.5 on everex
st5340T laptop.
After recent updates kde-guidance-powermanager does not update battery
state or time remaining/time to charge. When I issue the command:
cat /proc/acpi/battery/BAT0/state
I can watch see
Public bug reported:
Binary package hint: kima
Running Kubuntu Hardy 8.04 alpha 2.6.24-8 generic kde 3.5 on everex
ST5340T laptop.
The tool tip for Kima stops working after a period of time. I can find
no pattern for this problem.
** Affects: kima (Ubuntu)
Importance: Undecided
Everything is working great under Hardy for me here. I have an RT73
built into my laptop. Hidden essid is no longer an issue. I have not had
the disconnects. I no longer need to use wlassistant for certain
networks. TKIP and AES are both good on WPA networks. WEP is working
fine as well. My only
Issue is fixed in Hardy 8.04 alpha with kernel 2.6.24-2-generic and
2.6.24-3-generic. At least on my Everex where I have been running Hardy.
--
Brightness key stopped working after update [Gutsy]
https://bugs.launchpad.net/bugs/145337
You received this bug notification because you are a member
Public bug reported:
I am running Hardy Alpha on an amd x2 Turion notebook with geforce 6100
Go chipset. Kernel version is 2.6.24-2-generic. Using nvidia restricted
drivers. The video is scrambled on all of the virtual consoles and they
are unusable. Xorg is fine except when resuming from DPMS
I have been running Hardy since alpha1 and am now using 2.6.24 kernel. I
haven't had a chance in the last couple of weeks to try the wireless due
to the holiday season, but will do so in the next couple of days and
report back.
--
rt73 disconnects and crashes usb
I can confirm this bug on Everex StepNote ST5340T (same as Averatec 2300
series).
AMD x2 cpu
SATA HD
Nvidia chipset
--
2.6.22-14-rt halts during boot on some computers, without the nosmp noapic
nolapic kernel options
https://bugs.launchpad.net/bugs/175227
You received this bug notification
I have confirmed the bug
** Changed in: linux-source-2.6.22 (Ubuntu)
Status: New = Confirmed
--
2.6.22-14-rt halts during boot on some computers, without the nosmp noapic
nolapic kernel options
https://bugs.launchpad.net/bugs/175227
You received this bug notification because you are a
I have confirmed the bug
** Changed in: ubuntustudio
Status: New = Confirmed
--
2.6.22-14-rt halts during boot on some computers, without the nosmp noapic
nolapic kernel options
https://bugs.launchpad.net/bugs/175227
You received this bug notification because you are a member of Ubuntu
Almost forgot... I'm running a Kubuntu Gutsy install, not Ubuntu Studio. Kernel
with problem is 2.6.22-14-rt amd64.
32bit generic and rt run fine. 64bit generic runs fine.
--
2.6.22-14-rt halts during boot on some computers, without the nosmp noapic
nolapic kernel options
Luka: I retested the dcop calls and they work fine.
--
Brightness key stopped working after update [Gutsy]
https://bugs.launchpad.net/bugs/145337
You received this bug notification because you are a member of Kubuntu
Team, which is a bug contact for kdebase in ubuntu.
--
kubuntu-bugs mailing
Just tried the rebuilt packages. Brightness down works but not
brightness up.
--
Brightness key stopped working after update [Gutsy]
https://bugs.launchpad.net/bugs/145337
You received this bug notification because you are a member of Kubuntu
Team, which is a bug contact for kdebase in ubuntu.
1. Everex StepNote ST5340T
2. The dcop commands work
3. brightness up = 212
brightness down = 101
Just in case it helps: lsmod -m
platform_i8042_i8042_KBD_port_logicaldev_input condition ButtonPressed =
brightness-up
platform_i8042_i8042_KBD_port_logicaldev_input condition
I can confirm that the bug is also present in kpowersave in addition to
kpowermanager.
--
Brightness key stopped working after update [Gutsy]
https://bugs.launchpad.net/bugs/145337
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
Kubuntu Gutsy 7.10 amd64 generic kernel.
Same problem in kde here. I have an Everex StepNote ST5340T, it is
identical to an Averatec 2370 and the Averatec's are experiencing the
same problem. Key presses register correctly as above posts indicate.
The turn backlight off key works, but is a
Ok, now I'm puzzled. I have installed Gutsy on my new laptop and the
storage media kicker applet works fine on it. I still have problems on
my desktop computer though. The desktop is an amd64 x2 with nvidia
6100/nforce 4 chipset. The laptop is an amd64 Turion x2 with nvidia
6100go/nforce 4go
Just a dmesg log from when it locked earlier today.
** Attachment added: dmesg.txt
http://launchpadlibrarian.net/10050798/dmesg.txt
--
rt73 disconnects and crashes usb
https://bugs.launchpad.net/bugs/152456
You received this bug notification because you are a member of Ubuntu
Bugs, which is
I have reproduced the problem.
** Changed in: ubuntu
Status: New = Confirmed
--
rt73 disconnects and crashes usb
https://bugs.launchpad.net/bugs/152456
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs
Everex ST5340T notebook
Kubuntu Gutsy Beta amd64 Generic kernel
I had this happen to me today and a few days ago. I have an Everex
ST5340T laptop... it is identical to the Averatec 2370. The first time
it happened I noticed that my usb trackball quit working... yes wireless
was on at the time.
I have reproduced this again. This time uptime was 1hr 52min so that is
unrelated. I confirmed that usb devices continued working after this
occurs. wlan0 is not listed when doing an ifconfig. wlan0 is listed when
doing an iwconfig but didn't show an essid, ip, etc. I also found a
thread in the
*** This bug is a duplicate of bug 149106 ***
https://bugs.launchpad.net/bugs/149106
** Attachment added: Dependencies.txt
http://launchpadlibrarian.net/9739530/Dependencies.txt
** Attachment added: DpkgTerminalLog.gz
http://launchpadlibrarian.net/9739531/DpkgTerminalLog.gz
--
*** This bug is a duplicate of bug 149106 ***
https://bugs.launchpad.net/bugs/149106
Public bug reported:
Binary package hint: cupsys
Kubuntu Gutsy beta amd64 generic kernel.
This failure holds up all other updates from installing unless you
manually disable it. Once this package is
The above fix is for i386 installs only.
For amd64 installations the temporary fix dpkg command should be:
dpkg -i --force-overwrite
/var/cache/apt/archives/cupsys_1.3.2-1ubuntu4_amd64.deb
Dragon
--
package cupsys 1.3.2-1ubuntu4 failed to install/upgrade: trying to overwrite
If a disk or network share is unmounted or mounted the media icons will
also show up then.
--
Kubuntu storage media applet in Gutsy beta not showing drives
https://bugs.launchpad.net/bugs/148154
You received this bug notification because you are a member of Kubuntu
Team, which is a bug contact
Public bug reported:
Kubuntu Gutsy beta amd64
Qtparted crashes when trying to access PATA drive. Can access SATA drive
on same system fine. Found the following entry in /var/log/messages
Oct 3 12:30:37 x2-3800 kernel: [ 8161.937857] qtparted[18770]: segfault
at 7fff790b7370 rip
Also reproduced using Kubuntu Gutsy beta amd64 with both generic and
realtime kernel.
--
gparted crashed with SIGSEGV in Glib::SignalProxyNormal::slot0_void_callback()
https://bugs.launchpad.net/bugs/136485
You received this bug notification because you are a member of Ubuntu
Bugs, which is the
Public bug reported:
Gparted in Kubuntu Gutsy beta amd64 is extremely slow. Taskbar shows
scanning available drives. Randomly crashes. Found the following in
/var/log/messages
Oct 3 11:17:25 x2-3800 kernel: [ 5957.645642] end_request: I/O error, dev fd0,
sector 0
Oct 3 11:17:37 x2-3800
** Attachment added: qtparted-20071003-12h21m40s.log
http://launchpadlibrarian.net/9711805/qtparted-20071003-12h21m40s.log
--
Qtparted crashes when trying to access PATA drive.
https://bugs.launchpad.net/bugs/148641
You received this bug notification because you are a member of Ubuntu
Bugs,
** Attachment added: qtparted-20071003-12h29m56s.log
http://launchpadlibrarian.net/9711807/qtparted-20071003-12h29m56s.log
--
Qtparted crashes when trying to access PATA drive.
https://bugs.launchpad.net/bugs/148641
You received this bug notification because you are a member of Ubuntu
Bugs,
Public bug reported:
Binary package hint: kicker-applets
Kubuntu Gutsy beta amd64.
The storage media kicker applet does not show mounted drives on login
even though they are mounted and enabled in the configure dialog. If a
cd or other removable media is inserted all other selected drives will
Public bug reported:
In Kubuntu 7.10 Gutsy Beta amd64 the Knetdockapp does not show
throughputs or byte counts. It does show packets received/transmitted
but they look like they are way off. This happens with both the generic
kernel and the realtime kernel.
** Affects: knetdockapp (Ubuntu)
42 matches
Mail list logo
