Seems something is going wrong with intel hardware the last month or so:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=859639
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=884001
Apparently switching to use the intel driver (instead of modeset) did
not fix anything, just made it worse.
What seems to cause the issue is using Firefox + having a second
instance of Firefox open (using a "Dev" profile, I use this for web
development work) + having a private browsing
I've reported a similar issue here
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=859639
Having the same problems here on a Lenovo T520. It used to happen only
if I had the internal screen and an external monitor both active. Now it
happens randomly with only and external monitor hooked up since the
upgrade to 4.9.0-4-amd64 #1 SMP Debian 4.9.65-3 (2017-12-03) x86_64
GNU/Linux.
I
to my twitter account fine.
I compared the source files between the currently installed debian
version and the upstream 1.6 version. I did not see any difference in
how the form was handled so I don't know if upstream is still effected
or not, and I have no way to test 1.6 as I don't have QT5 libs
y opinion, icedove should
probably have a requirement dependency on libcanberra and should
probably have a suggest dependency on libcanberra-pulse. I am not even
sure if its current dependency on libasound2 is even valid in its
current state.
Regards,
Samuel Smith
--- System information. ---
Package: laptop-mode-tools
Version: 1.69.2-1
Hi,
I just bought a new (used) Thinkpad T520. I thought laptop-mode-tool was
working, but on closer inspection they were not. I too had the same
issue when using a docking station.
Change events from a docking event:
# udevadm monitor
monitor
I tried building 1.13 in sid and installing it on stable. Still similar
issues.
I ended up reinstalling the default asterisk packages on stable (after a
purge of everything for about the 20th time), and found that most of the
symbol errors above meant nothing. The apps that were mentioned in
Same issue with me as well after an upgrade from Wheezy to Jessie:
[Jan 10 06:01:31] Asterisk 11.13.1~dfsg-2+b1 built by buildd @ brahms on
a x86_64 running Linux on 2015-01-05 21:34:10 UTC
[Jan 10 06:01:31] NOTICE[23936] cdr.c: CDR simple logging enabled.
[Jan 10 06:01:32] NOTICE[23936]
I might add, that since I have a new access point coming in, I would be
more than happy to donate this wifi card and WG102 access point to
anyone that would really want to troubleshoot it. Nonetheless, I am also
fine with keeping it.
--
To UNSUBSCRIBE, email to
I have installed a wifi card from a T500 into my T61, the issues are
still the same: wext works, but nl80211 does not.
I could try booting the Wheezy live CD again with this card, but I don't
see the point since it worked with the other card. Clearly since
everything worked fine at work,
I booted a Wheezy 7.8 live CD and everything is working fine on my t61
laptop connecting to my home router. Attached logs of:
wpa_supplicant -i wlan0 -ddd -Dnl80211 -c wpa.conf nl80211aa.log
wpa_supplicant -i wlan0 -ddd -Dwext -c wpa.conf wextaa.log
wpa_supplicant v1.0
random: Trying to read
Just some more info.
I took the t61 laptop to work, and using wpa_supplicant I was able to
connect to the wirless here using either wext or nl80211. This points to
an issue with my home router which is a netgear WG102 with an atheros
chip: http://support.netgear.com/product/WG102
I have a
At work I tested on my other laptop ( a newer T520) that is still Wheezy.
Running: wpa_supplicant -iwlan0 -dd -c wpa.conf seems to show that at least
on the version in Wheezy, the default is to use the wext driver. I forced
it to use nl80211 with: wpa_supplicant -iwlan0 -dd -Dnl80211 -c wpa.conf
Package: rsnapshot
Version: 1.3.1-4
Severity: normal
I use rsnapshot with a custom setting for ssh_args in order to improve
speed as follows (rsnapshot.conf):
backup root@10.38.38.5:/ xen/ssh_args=-c arcfour
This has worked fine for years. On Aug. 16 I updated
Package: mdadm
Version: 3.2.5-5
--- Please enter the report below this line. ---
I was bitten by this too. Looks like another person here too:
http://tinyurl.com/pqrkx2c
Not sure where to point the blame. I was thinking initramfs too but when
I ran reportbug-ng to generate this against
I recently performed an upgrade from squeeze to wheezy and was bitten
by this bug. I don't know why it isn't tagged as release critical but
imo it should be.
Regards,
Samuel Smith
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble
I was bit by this too from the update in wheezy. None of my events were
listed in korganizer and trying to add a new one ended up with No
calenders found error. I clicked the + in the bottom left pane and
added the akonadi calender and everything works now and it seems to have
restored all of
18 matches
Mail list logo
