Bug#905377: kontact: Kontact opens introduction in konqueror on each start
Package: kontact Version: 4:17.12.3-1 Severity: normal Dear Maintainer, On upgrade kontact:amd64 4:17.08.3-1 to 4:17.12.3-1 I am now getting the Konqueror introduction page on each start. I am unable to dismiss it as the 'Skip this introduciton' button throws an error 'Could not find any application or handler for exec:/switch'. So I close the Konqueror window only to have it open again. My other machine does not have Konqueror installed and on each load I am met with 'File not found: data:text/html;charset=UTF-8,%3C%3Fxml version%3D%221.0%22...' Is there a way to disable the introduction outright in an rc file somewhere? It's a pain to have to close this each time. Thanks, Matt -- System Information: Debian Release: buster/sid APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 4.17.0-1-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages kontact depends on: ii kdepim-runtime 4:17.12.3-2 ii kio 5.47.0-1 ii libc62.27-5 ii libgcc1 1:8.2.0-2 ii libkf5completion55.47.0-1 ii libkf5configcore55.47.0-1 ii libkf5configgui5 5.47.0-1 ii libkf5configwidgets5 5.47.0-1 ii libkf5coreaddons55.47.0-1 ii libkf5crash5 5.47.0-1 ii libkf5grantleetheme-plugins 17.12.3-1 ii libkf5grantleetheme5 17.12.3-1 ii libkf5i18n5 5.47.0-1 ii libkf5iconthemes55.47.0-1 ii libkf5kcmutils5 5.47.0-1 ii libkf5kdepimdbusinterfaces5 4:17.12.3-1 ii libkf5kiowidgets55.47.0-1 ii libkf5kontactinterface5 17.12.3-1 ii libkf5libkdepim-plugins 4:17.12.3-1 ii libkf5libkdepim5 4:17.12.3-1 ii libkf5parts5 5.47.0-1 ii libkf5service-bin5.47.0-1 ii libkf5service5 5.47.0-1 ii libkf5widgetsaddons5 5.47.0-1 ii libkf5windowsystem5 5.47.0-1 ii libkf5xmlgui55.47.0-1+b1 ii libqt5core5a 5.11.1+dfsg-6 ii libqt5dbus5 5.11.1+dfsg-6 ii libqt5gui5 5.11.1+dfsg-6 ii libqt5webengine5 5.11.1+dfsg-5 ii libqt5webenginewidgets5 5.11.1+dfsg-5 ii libqt5widgets5 5.11.1+dfsg-6 ii libstdc++6 8.2.0-2 Versions of packages kontact recommends: ii accountwizard 4:17.12.3-1 ii akregator 4:17.12.3-1 ii kaddressbook 4:17.12.3-1 ii kmail 4:17.12.3-1 ii knotes 4:17.12.3-1 ii korganizer 4:17.12.3-2 Versions of packages kontact suggests: pn gnokii -- no debconf information
Bug#903135: intel-microcode: Kabby Lake microcode rev 0x84 instead of rev 0x8e
On Sunday, July 8, 2018 1:40:34 PM PDT Henrique de Moraes Holschuh wrote: > On Fri, 06 Jul 2018, Matt Stamp wrote: > > After applying an update to my UEFI/BIOS my microcode is rev 0x8e. A > > package seperate for your, needrestart said that the available > > microcode did not match my currently applied version 0x84. Though > > even after the recent update from Intel I am still getting that > > message. > > That's a limitation in the needsrestart logic, which isn't easy to fix > at all. The kernel doesn't help (it doesn't tell you the BIOS microcode > revision on Intel, only the current revision), and Intel doesn't help > (they sometimes downgrade or recall microcode updates so you can't > assume it will just go up on intel-microcode updates), so it can't do a > perfect job. > > Maybe it can be improved, but that would be something to explore in a > bug report against needrestart, not intel-microcode. > > > Is this correct? Is the revision in intel-microcode-3.20180703.2 for > > Kabby Lake really 0x84? According to some of my reading Intel > > Yes, it is really 0x84, unfortunately(?) > > This information can be found in /usr/share/doc/intel-microcode/ > changelog.gz, although it can be a bit cryptic unless you've read the > README or tried running "iucode_tool -Sv" to know your processor's > signature. > > > released the 0x8e version and so I thought it would be included in > > their recent release. > > We wish. No, it isn't. From the Debian changelog of intel-microcode: > > --8<-- > + First batch of fixes for: Intel SA-00115, CVE-2018-3639, CVE-2018-3640 > + SSBD support (Spectre-v4 mitigation) and fix Spectre-v3a for: Sandybridge > server, Ivy Bridge server, Haswell server, Skylake server, Broadwell > server, a few HEDT Core i7/i9 models that are actually gimped server dies. > --8<-- > > As you can see, the vast majority of the processors affected, Kaby lake > included, are still missing in the public update release of 2018-07-03. > > > If this is some issue with the needrestart package or perl within than > > no big deal and please feel free to close this ticket. > > I will close the bug report when we get a Kabi Lake update with revision > 0x8e or higher. > > If you want to ask the needrestart package to improve their detection, > please open a bug against that package. I am not sure much can be done > on that regard without kernel changes, though. Thank you kindly for explaining that in detail. It is much appreciated.
Bug#903135: intel-microcode: Kabby Lake microcode rev 0x84 instead of rev 0x8e
Package: intel-microcode Version: 3.20180703.2 Severity: normal Dear Maintainer, After applying an update to my UEFI/BIOS my microcode is rev 0x8e. A package seperate for your, needrestart said that the available microcode did not match my currently applied version 0x84. Though even after the recent update from Intel I am still getting that message. The currently running processor microcode revision is 0x8e which is not the expected microcode revision 0x84. Is this correct? Is the revision in intel-microcode-3.20180703.2 for Kabby Lake really 0x84? According to some of my reading Intel released the 0x8e version and so I thought it would be included in their recent release. If this is some issue with the needrestart package or perl within than no big deal and please feel free to close this ticket. I'm just looking for confirmation I suppose. processor : 0 vendor_id : GenuineIntel cpu family : 6 model : 142 model name : Intel(R) Core(TM) i7-7600U CPU @ 2.80GHz stepping: 9 microcode : 0x8e cpu MHz : 1152.470 cache size : 4096 KB physical id : 0 siblings: 4 core id : 0 cpu cores : 2 apicid : 0 initial apicid : 0 fpu : yes fpu_exception : yes cpuid level : 22 wp : yes flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx pdpe1gb rdtscp lm constant_tsc art arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc cpuid aperfmperf tsc_known_freq pni pclmulqdq dtes64 monitor ds_cpl vmx smx est tm2 ssse3 sdbg fma cx16 xtpr pdcm pcid sse4_1 sse4_2 x2apic movbe popcnt tsc_deadline_timer aes xsave avx f16c rdrand lahf_lm abm 3dnowprefetch cpuid_fault epb invpcid_single pti ssbd ibrs ibpb stibp tpr_shadow vnmi flexpriority ept vpid fsgsbase tsc_adjust bmi1 hle avx2 smep bmi2 erms invpcid rtm mpx rdseed adx smap clflushopt intel_pt xsaveopt xsavec xgetbv1 xsaves dtherm ida arat pln pts hwp hwp_notify hwp_act_window hwp_epp bugs: cpu_meltdown spectre_v1 spectre_v2 spec_store_bypass bogomips: 5808.00 clflush size: 64 cache_alignment : 64 address sizes : 39 bits physical, 48 bits virtual power management: -- System Information: Debian Release: buster/sid APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 4.16.0-2-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages intel-microcode depends on: ii iucode-tool 2.3.1-1 Versions of packages intel-microcode recommends: ii initramfs-tools 0.130 intel-microcode suggests no packages. -- no debconf information
Bug#876220: libglvnd0:amd64: KDE will not start due to undefined symbol
My apologies. I have fixed the problem. I didn't think anything of libglvnd0-nvidia since it claimed to be vendor neutral. After looking at another system I have I noticed I didn't have that installed. So I swapped these. The following packages will be REMOVED: libglvnd0-nvidia The following NEW packages will be installed: libglvnd0 And the issue appears to be resolved. root@fusion:/home/matt# ldd -r /usr/lib/x86_64-linux-gnu/libGL.so.1 linux-vdso.so.1 (0x7ffc74dd4000) libGLX.so.0 => /usr/lib/x86_64-linux-gnu/libGLX.so.0 (0x7fd9034be000) libGLdispatch.so.0 => /usr/lib/x86_64-linux-gnu/libGLdispatch.so.0 (0x7fd903208000) libdl.so.2 => /lib/x86_64-linux-gnu/libdl.so.2 (0x7fd903004000) libpthread.so.0 => /lib/x86_64-linux-gnu/libpthread.so.0 (0x7fd902de7000) libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x7fd902a4a000) libX11.so.6 => /usr/lib/x86_64-linux-gnu/libX11.so.6 (0x7fd90270a000) libXext.so.6 => /usr/lib/x86_64-linux-gnu/libXext.so.6 (0x7fd9024f8000) /lib64/ld-linux-x86-64.so.2 (0x7fd90397b000) libxcb.so.1 => /usr/lib/x86_64-linux-gnu/libxcb.so.1 (0x7fd9022d) libXau.so.6 => /usr/lib/x86_64-linux-gnu/libXau.so.6 (0x7fd9020cc000) libXdmcp.so.6 => /usr/lib/x86_64-linux-gnu/libXdmcp.so.6 (0x7fd901ec6000) libbsd.so.0 => /lib/x86_64-linux-gnu/libbsd.so.0 (0x7fd901cb1000) librt.so.1 => /lib/x86_64-linux-gnu/librt.so.1 (0x7fd901aa9000) If you could please resolve and close this ticket. Thanks On Wednesday, September 20, 2017 5:10:20 PM PDT Timo Aaltonen wrote: > On 19.09.2017 22:10, Matt Stamp wrote: > > Package: libglvnd0 > > Version: 0.2.999+git20170802-4 > > Severity: normal > > > > Dear Maintainer, > > > > An upgrade of libgl1:amd64 broken XServer and it cannot start. > > > > [32.012] (EE) Failed to load > > /usr/lib/xorg/modules/extensions/libglx.so: / > > usr/lib/x86_64-linux-gnu/libGL.so.1: undefined symbol: _glapi_tls_Current > > [32.012] (EE) Failed to load module "glx" (loader failed, 7) > > > > undefined symbol: _glapi_tls_Current > > (/usr/lib/x86_64-linux-gnu/libGL.so.1) > do you have the nvidia driver installed?
Bug#876220: libglvnd0:amd64: KDE will not start due to undefined symbol
I do not. I am using a Radeon card and the Xserver 'radeon' driver. [32.012] (II) LoadModule: "radeon" [32.013] (II) Loading /usr/lib/xorg/modules/drivers/radeon_drv.so [32.013] (II) Module radeon: vendor="X.Org Foundation" 01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Cedar [Radeon HD 5000/6000/7350/8350 Series] root@fusion:~$ dpkg -l | egrep 'nvidia|radeon' ii libdrm-radeon1:amd64 2.4.82-1 amd64Userspace interface to radeon-specific kernel DRM services -- runtime ii libglvnd0-nvidia:amd64375.82-3 amd64Vendor neutral GL dispatch library -- libGLdispatch ii xserver-xorg-video-radeon 1:7.9.0-1 amd64X.Org X server -- AMD/ATI Radeon display driver On Wednesday, September 20, 2017 5:10:20 PM PDT Timo Aaltonen wrote: > On 19.09.2017 22:10, Matt Stamp wrote: > > Package: libglvnd0 > > Version: 0.2.999+git20170802-4 > > Severity: normal > > > > Dear Maintainer, > > > > An upgrade of libgl1:amd64 broken XServer and it cannot start. > > > > [32.012] (EE) Failed to load > > /usr/lib/xorg/modules/extensions/libglx.so: / > > usr/lib/x86_64-linux-gnu/libGL.so.1: undefined symbol: _glapi_tls_Current > > [32.012] (EE) Failed to load module "glx" (loader failed, 7) > > > > undefined symbol: _glapi_tls_Current > > (/usr/lib/x86_64-linux-gnu/libGL.so.1) > do you have the nvidia driver installed?
Bug#876220: libglvnd0:amd64: KDE will not start due to undefined symbol
Package: libglvnd0 Version: 0.2.999+git20170802-4 Severity: normal Dear Maintainer, An upgrade of libgl1:amd64 broken XServer and it cannot start. [32.012] (EE) Failed to load /usr/lib/xorg/modules/extensions/libglx.so: / usr/lib/x86_64-linux-gnu/libGL.so.1: undefined symbol: _glapi_tls_Current [32.012] (EE) Failed to load module "glx" (loader failed, 7) root@fusion:/home/matt# ldd -r /usr/lib/x86_64-linux-gnu/libGL.so.1 linux-vdso.so.1 (0x7ffdc5b64000) libGLX.so.0 => /usr/lib/x86_64-linux-gnu/libGLX.so.0 (0x7f810f231000) libGLdispatch.so.0 => /usr/lib/x86_64-linux-gnu/libGLdispatch.so.0 (0x7f810ef63000) libdl.so.2 => /lib/x86_64-linux-gnu/libdl.so.2 (0x7f810ed5f000) libpthread.so.0 => /lib/x86_64-linux-gnu/libpthread.so.0 (0x7f810eb42000) libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x7f810e7a5000) libX11.so.6 => /usr/lib/x86_64-linux-gnu/libX11.so.6 (0x7f810e465000) libXext.so.6 => /usr/lib/x86_64-linux-gnu/libXext.so.6 (0x7f810e253000) /lib64/ld-linux-x86-64.so.2 (0x7f810f6ee000) libxcb.so.1 => /usr/lib/x86_64-linux-gnu/libxcb.so.1 (0x7f810e02b000) libXau.so.6 => /usr/lib/x86_64-linux-gnu/libXau.so.6 (0x7f810de27000) libXdmcp.so.6 => /usr/lib/x86_64-linux-gnu/libXdmcp.so.6 (0x7f810dc21000) libbsd.so.0 => /lib/x86_64-linux-gnu/libbsd.so.0 (0x7f810da0c000) librt.so.1 => /lib/x86_64-linux-gnu/librt.so.1 (0x7f810d804000) undefined symbol: _glapi_tls_Current(/usr/lib/x86_64-linux-gnu/libGL.so.1) -- System Information: Debian Release: buster/sid APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.12.0-2-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages libglvnd0:amd64 depends on: ii libc6 2.24-17 libglvnd0:amd64 recommends no packages. libglvnd0:amd64 suggests no packages. -- no debconf information
Bug#836226: bug resolved
I would like to confirm that this is now resolved with the newest version of network-manager (1.4.2-1). You can close this bug.
Bug#660068: upower: wrong battery percentage after power is unplugged
Hello Tomas, My apologies for not following up sooner on this bug. I am currently using the sid version of upower and it is working well for me now. ii upower 0.99.1-3.1 amd64abstraction for power management I have not experienced any further issues with upower reporting the incorrect battery percentage. -Matt -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#711227: broadcom-sta-dkms: fails to build dkms module on linux 3.9
Package: broadcom-sta-dkms Version: 5.100.82.112-10 Severity: important Dear Maintainer, When using kernel 3.9, linux-image-3.9-1-amd64 and linux-headers-3.9-1-amd64, the dkms modules fails to compile. It was working previously on kernel 3.8 linux-image-3.8-2-amd64. DKMS make.log for broadcom-sta-5.100.82.112 for kernel 3.9-1-amd64 (x86_64) Tue Jun 4 17:34:05 PDT 2013 /bin/sh: 1: [: Illegal number: /bin/sh: 1: [: Illegal number: Wireless Extension is the only possible API for this kernel version Using Wireless Extension API KBUILD_NOPEDANTIC=1 make -C /lib/modules/3.9-1-amd64/build M=/var/lib/dkms/broadcom-sta/5.100.82.112/build make[1]: Entering directory `/usr/src/linux-headers-3.9-1-amd64' CFG80211 API is prefered for this kernel version Using CFG80211 API Kernel architecture is X86_64 LD /var/lib/dkms/broadcom-sta/5.100.82.112/build/built-in.o CC [M] /var/lib/dkms/broadcom-sta/5.100.82.112/build/src/shared/linux_osl.o CC [M] /var/lib/dkms/broadcom-sta/5.100.82.112/build/src/wl/sys/wl_linux.o CC [M] /var/lib/dkms/broadcom-sta/5.100.82.112/build/src/wl/sys/wl_iw.o CC [M] /var/lib/dkms/broadcom-sta/5.100.82.112/build/src/wl/sys/wl_cfg80211.o /var/lib/dkms/broadcom-sta/5.100.82.112/build/src/wl/sys/wl_cfg80211.c:1668:2: warning: initialization from incompatible pointer type [enabled by default] /var/lib/dkms/broadcom-sta/5.100.82.112/build/src/wl/sys/wl_cfg80211.c:1668:2: warning: (near initialization for ‘wl_cfg80211_ops.set_tx_power’) [enabled by default] /var/lib/dkms/broadcom-sta/5.100.82.112/build/src/wl/sys/wl_cfg80211.c:1669:2: warning: initialization from incompatible pointer type [enabled by default] /var/lib/dkms/broadcom-sta/5.100.82.112/build/src/wl/sys/wl_cfg80211.c:1669:2: warning: (near initialization for ‘wl_cfg80211_ops.get_tx_power’) [enabled by default] /var/lib/dkms/broadcom-sta/5.100.82.112/build/src/wl/sys/wl_cfg80211.c: In function ‘wl_update_bss_info’: /var/lib/dkms/broadcom-sta/5.100.82.112/build/src/wl/sys/wl_cfg80211.c:2118:3: warning: passing argument 1 of ‘cfg80211_put_bss’ from incompatible pointer type [enabled by default] In file included from /var/lib/dkms/broadcom-sta/5.100.82.112/build/src/wl/sys/wl_cfg80211.c:27:0: /usr/src/linux-headers-3.9-1-common/include/net/cfg80211.h:3302:6: note: expected ‘struct wiphy *’ but argument is of type ‘struct cfg80211_bss *’ /var/lib/dkms/broadcom-sta/5.100.82.112/build/src/wl/sys/wl_cfg80211.c:2118:3: error: too few arguments to function ‘cfg80211_put_bss’ In file included from /var/lib/dkms/broadcom-sta/5.100.82.112/build/src/wl/sys/wl_cfg80211.c:27:0: /usr/src/linux-headers-3.9-1-common/include/net/cfg80211.h:3302:6: note: declared here make[4]: *** [/var/lib/dkms/broadcom-sta/5.100.82.112/build/src/wl/sys/wl_cfg80211.o] Error 1 make[3]: *** [_module_/var/lib/dkms/broadcom-sta/5.100.82.112/build] Error 2 make[2]: *** [sub-make] Error 2 make[1]: *** [all] Error 2 make[1]: Leaving directory `/usr/src/linux-headers-3.9-1-amd64' make: *** [all] Error 2 -- System Information: Debian Release: jessie/sid APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.9-1-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages broadcom-sta-dkms depends on: ii dkms 2.2.0.3-1.2 Versions of packages broadcom-sta-dkms recommends: ii wireless-tools 30~pre9-8 broadcom-sta-dkms suggests no packages. -- Configuration Files: /etc/modprobe.d/broadcom-sta-dkms.conf changed [not included] -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#660068: upower: wrong battery percentage after power is unplugged
Subject: upower: wrong battery percentage after power is unplugged Package: upower Version: 0.9.15-2 Severity: important Dear Maintainer, It is possible that this is a duplicate bug regarding battery percentage but I wanted to submit my experience in case it sheds more light as to what is going on. I am having an issue with my laptop (Dell Inspiron 6400) where once the battery is fully charged and the power is unplugged the battery percentage will go from 100% to 77% almost immediately. If I run acpi -b, that reports the correct battery percentage and time left. If I were to run dpkg- reconfigure upower the battery percentage is corrected until the next charge. If I plug and unplug the power at any other percentage the issue does not present itself. After a little further looking I have found this. According to /sys/devices/LNXSYSTM:00/device:00/PNP0C0A:00/power_supply/BAT0/ charge_full = 6177000 and is static charge_full_design = 780 and is static charge_now is acting a bit weird. When the laptop is on battery the value is that of what ever the charge is, somewhere below 6177000, but when the charge reaches 100% it becomes 780. Then when the charge drops for the first time it changes from 780 to what ever the charge may be. I know this problem is with the kernel, the issue I have with upower is that when the battery becomes fully charged energy, energy-full and energy- full-design all become charge_full_design's value. Then when on battery power the kernel updates /sys and the energy value gets updated with upower but the energy-full value remains that of energy-full-design making the battery instantly look discharged. The value in /sys for charge_full never changes so I don't know why upower would need to changing it. Full charge, plugged in [18:50:50.367] device changed: /org/freedesktop/UPower/devices/battery_BAT0 native-path: /sys/devices/LNXSYSTM:00/device:00/PNP0C0A:00/power_supply/BAT0 vendor: Sanyo model:DELLJN1490 serial: 911 power supply: yes updated: Wed Feb 15 18:50:50 2012 (0 seconds ago) has history: yes has statistics: yes battery present: yes rechargeable:yes state: fully-charged energy: 86.58 Wh energy-empty:0 Wh energy-full: 86.58 Wh energy-full-design: 86.58 Wh energy-rate: 0.0111 W voltage: 12.484 V percentage: 100% capacity:79.1923% technology: lithium-ion History (charge): 1329360648 100.000 fully-charged 1329360646 77.949 charging 1329360637 78.026 discharging History (rate): 1329360648 0.011 fully-charged 1329360637 25.375 discharging Full charge, just unplugged [18:51:56.371] device changed: /org/freedesktop/UPower/devices/battery_BAT0 native-path: /sys/devices/LNXSYSTM:00/device:00/PNP0C0A:00/power_supply/BAT0 vendor: Sanyo model:DELLJN1490 serial: 911 power supply: yes updated: Wed Feb 15 18:51:56 2012 (0 seconds ago) has history: yes has statistics: yes battery present: yes rechargeable:yes state: discharging energy: 67.488 Wh energy-empty:0 Wh energy-full: 86.58 Wh energy-full-design: 86.58 Wh energy-rate: 24.531 W voltage: 12.328 V time to empty: 2.8 hours percentage: 77.9487% capacity:79.1923% technology: lithium-ion History (charge): 1329360712 77.949 discharging 1329360648 100.000 fully-charged 1329360646 77.949 charging 1329360637 78.026 discharging History (rate): 1329360712 24.531 discharging 1329360648 0.011 fully-charged 1329360637 25.375 discharging Full charge, just after dpk-reconfigure upower [18:52:22.366] device changed: /org/freedesktop/UPower/devices/battery_BAT0 native-path: /sys/devices/LNXSYSTM:00/device:00/PNP0C0A:00/power_supply/BAT0 vendor: Sanyo model:DELLJN1490 serial: 911 power supply: yes updated: Wed Feb 15 18:52:22 2012 (0 seconds ago) has history: yes has statistics: yes battery present: yes rechargeable:yes state: discharging energy: 67.2882 Wh energy-empty:0 Wh energy-full: 68.5647 Wh energy-full-design: 86.58 Wh energy-rate: 37.0518 W voltage: 12.291 V time to empty: 1.8 hours percentage: 98.1383% capacity:79.1923% technology: lithium-ion History (charge): 1329360738 98.138
Bug#544814: amarok: symbol lookup error: /usr/lib/libamaroklib.so.1: undefined symbol: _ZTIN6TagLib9TrueAudio4FileE
Package: amarok Version: 2.1.1-4 Severity: important I get no window when running from KDE. When run from console I get the error above. -- System Information: Debian Release: squeeze/sid APT prefers stable APT policy: (500, 'stable'), (400, 'testing'), (200, 'unstable'), (199, 'experimental') Architecture: i386 (i686) Kernel: Linux 2.6.29 (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages amarok depends on: ii amarok-common 2.1.1-4 architecture independent files for ii amarok-utils 2.1.1-4 utilities for Amarok media player ii kdebase-runtime4:4.3.1-1 runtime components from the offici ii kdelibs5 4:4.3.1-1 core libraries for all KDE 4 appli ii libc6 2.9-26GNU C Library: Shared libraries ii libcurl3-gnutls7.19.5-1.1Multi-protocol file transfer libra ii libgcc11:4.4.1-3 GCC support library ii libgcrypt111.4.4-4 LGPL Crypto library - runtime libr ii libglib2.0-0 2.20.5-1 The GLib library of C routines ii libgpod4 0.7.2-1.1 library to read and write songs an ii libgtk2.0-02.16.6-1 The GTK+ graphical user interface ii libloudmouth1-01.4.3-4 Lightweight C Jabber library ii libmtp80.3.7-7 Media Transfer Protocol (MTP) libr ii libphonon4 4:4.5.2-2 Qt 4 Phonon module ii libplasma3 4:4.3.1-1 library for the KDE 4 Plasma deskt ii libqt4-dbus4:4.5.2-2 Qt 4 D-Bus module ii libqt4-network 4:4.5.2-2 Qt 4 network module ii libqt4-script 4:4.5.2-2 Qt 4 script module ii libqt4-sql 4:4.5.2-2 Qt 4 SQL module ii libqt4-svg 4:4.5.2-2 Qt 4 SVG module ii libqt4-webkit 4:4.5.2-2 Qt 4 WebKit module ii libqt4-xml 4:4.5.2-2 Qt 4 XML module ii libqtcore4 4:4.5.2-2 Qt 4 core module ii libqtgui4 4:4.5.2-2 Qt 4 GUI module ii libqtscript4-core 0.1.0-3 Qt Script bindings for the Qt 4 Co ii libqtscript4-gui 0.1.0-3 Qt Script bindings for the Qt 4 Gu ii libqtscript4-network 0.1.0-3 Qt Script bindings for the Qt 4 Ne ii libqtscript4-sql 0.1.0-3 Qt Script bindings for the Qt 4 SQ ii libqtscript4-uitools 0.1.0-3 Qt Script bindings for the Qt 4 Ui ii libqtscript4-xml 0.1.0-3 Qt Script bindings for the Qt 4 XM ii libstdc++6 4.4.1-3 The GNU Standard C++ Library v3 ii libstreamanalyzer0 0.7.0-1+b2streamanalyzer library for Strigi ii libstreams00.7.0-1+b2streams library for for Strigi Des ii libtag-extras0 0.1.6-1 TagLib extras library - support fo ii libtag1c2a 1.5-7 TagLib Audio Meta-Data Library ii libxml22.7.3.dfsg-2.1GNOME XML library ii phonon 4:4.5.2-2 Qt 4 Phonon module metapackage ii phonon-backend-gstream 4:4.3.1-4 Phonon GStreamer 0.10.x backend ii phonon-backend-xine [p 4:4.3.1-4 Phonon Xine 1.1.x backend ii zlib1g 1:1.2.3.3.dfsg-15 compression library - runtime Versions of packages amarok recommends: ii kdemultimedia-kio-plugins 4:4.3.1-1 transparent audio CD access for KD Versions of packages amarok suggests: ii libqt4-sql-mysql 4:4.5.2-2 Qt 4 MySQL database driver pn libqt4-sql-psql none (no description available) ii libqt4-sql-sqlite 4:4.5.2-2 Qt 4 SQLite 3 database driver Versions of packages amarok is related to: ii phonon-backend-gstreamer [pho 4:4.3.1-4 Phonon GStreamer 0.10.x backend ii phonon-backend-xine [phonon-b 4:4.3.1-4 Phonon Xine 1.1.x backend -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#474251: yasr: should this package be orphaned?
I would like to help although I am not a Debian maintainer. I would be interested in whatever you would need any help with. Thanks, Matt -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#440688: ksensors: Cannot read from acpi/THM
Package: ksensors
Version: 0.7.3-16
Severity: normal
Tags: patch
-- System Information:
Debian Release: lenny/sid
APT prefers oldstable
APT policy: (500, 'oldstable'), (400, 'testing'), (200, 'unstable'), (199,
'experimental')
Architecture: i386 (i686)
Kernel: Linux 2.6.18.1 (PREEMPT)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Versions of packages ksensors depends on:
ii kdelibs4c2a 4:3.5.7.dfsg.1-6 core libraries and binaries for al
ii libc6 2.6.1-1+b1 GNU C Library: Shared libraries
ii libgcc1 1:4.2.1-4GCC support library
ii libqt3-mt 3:3.3.7-7Qt GUI Library (Threaded runtime v
ii libsensors3 1:2.10.4-1 library to read temperature/voltag
ii libstdc++6 4.2.1-4 The GNU Standard C++ Library v3
ii lm-sensors 1:2.10.4-1 utilities to read temperature/volt
Versions of packages ksensors recommends:
pn hddtemp none (no description available)
-- debconf information:
ksensors/v6:
Ksensors is set up to only read from /proc/acpi/thermal_zone/THRM. On my
motherboard the bios maker is using THM instead.
I have included a patch to read from both THRM and THM.
diff -urN ./ksensors-0.7.3.orig/src/procinfo.cpp ./ksensors-0.7.3/src/procinfo.cpp
--- ./ksensors-0.7.3.orig/src/procinfo.cpp 2003-10-26 14:45:41.0 -0800
+++ ./ksensors-0.7.3/src/procinfo.cpp 2007-08-27 18:42:27.0 -0700
@@ -84,11 +84,13 @@
{
char buf[128];
-if(read_file(/proc/acpi/thermal_zone/THRM/temperature, buf, sizeof(buf))= 0) return -1;
+if((read_file(/proc/acpi/thermal_zone/THRM/temperature, buf, sizeof(buf)) 0) || (read_file(/proc/acpi/thermal_zone/THM/temperature, buf, sizeof(buf)) 0))
+{
+ sscanf(buf, temperature: %lf C, cpuTemp);
+ return 0;
+}
-sscanf(buf, temperature: %lf C, cpuTemp);
-
-return 0;
+return -1;
}
