Fixed for me with today's update.
Thanks for everyone who worked on it.
--
Intrepid: WLAN LED blinks incessantly on iwl3945 | iwl4965 laptop
https://bugs.launchpad.net/bugs/250211
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubun
Here are the 3 files.
The only customizations I have made to xorg are through nvidia-settings,
I did not make them manually so I do not know exactly what it did.
** Attachment added: "lspci -vvnn.txt"
http://launchpadlibrarian.net/19498700/lspci%20-vvnn.txt
--
nvidia-graphics-drivers-177 cra
** Attachment added: "xorg.conf"
http://launchpadlibrarian.net/19498712/xorg.conf
--
nvidia-graphics-drivers-177 crashes clickable desktop with dual monitors
https://bugs.launchpad.net/bugs/278710
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
** Attachment added: "Xorg.0.log"
http://launchpadlibrarian.net/19498702/Xorg.0.log
--
nvidia-graphics-drivers-177 crashes clickable desktop with dual monitors
https://bugs.launchpad.net/bugs/278710
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribe
Oh, I also have to add, when I try to launch the Preferences>Screen
Resolution it does not open. I see it appear in the bottom panel but
then it dissappears. I do not know it that is related, but I thought I
would add as it may be.
--
nvidia-graphics-drivers-177 crashes clickable desktop with d
I agree with Nick B. above me, it is a LOT worse, actually un-useable to
some extent so I will be going to 173 until I hear something is fixed
with this.
Dell D630
As I posted in ubuntu forums:
I have been using intrepid since sunday and had no problems, but with the new
version, every time I go
I have a dell D630 and the same thing happens after upgrading to
Intrepid.
I have to say that I like the Hardy way of having it completely off
after seeing this.
--
Intrepid: WLAN LED blinks incessantly on iwl3945 | iwl4965 laptop
https://bugs.launchpad.net/bugs/250211
You received this bug noti
Public bug reported:
I have 2 monitors and when I use both since upgrading to the intrepid
beta, the screen will crash and not allow me to click on anything. The
buttons do not work, the panel does not work, and clicking on a window
does not work.
I must use the keyboard to navigate.
To fix it,
Sorry, that was a mistake.
After updating to the new kernel (-11) it seemed to stop blinking. The
blinking stopped for 2 days but it now back (strange, I know).
--
Intrepid: WLAN LED blinks incessantly on iwl3945 | iwl4965 laptop
https://bugs.launchpad.net/bugs/250211
You received this bug noti
I just updated to nvidia's latest stable driver, 180.22, and this has
been fixed.
--
nvidia-graphics-drivers-177 crashes clickable desktop with dual monitors
https://bugs.launchpad.net/bugs/278710
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to U
really? that does not change it for me, I just restarted and it still
does the same as in my screenshot above.
--
Maximizing ignores docked panles with Xinerama
https://bugs.launchpad.net/bugs/58977
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
This affects me also.
It also does it with twinview which I was using previously to upgrading to
Jaunty.
I agree with what Conan posted above, any non-extreme edge panel is
ignored from my experience.
I am using a Dell D630 laptop with the main screen being the bottom.
I have attached a screens
*** This bug is a duplicate of bug 58977 ***
https://bugs.launchpad.net/bugs/58977
** This bug has been marked a duplicate of bug 58977
Maximizing ignores docked panles with Xinerama
--
vertical dual-monitors, gnome ignores the bottom panel space when maximising
https://bugs.launchpad.net
*** This bug is a duplicate of bug 58977 ***
https://bugs.launchpad.net/bugs/58977
** This bug is no longer a duplicate of bug 120818
vertical dual-monitors, gnome ignores the bottom panel space when maximising
** This bug has been marked a duplicate of bug 58977
Maximizing ignores dock
Also affects me.
Running the jaunty beta on a dell D630, I have yet to figure out how to
get it to print using an Epson stylus CX4800.
I have installed the "foomatic" packages from synaptic as it seems that
a few recommended that in the forums.
I did what was listed above... when entering "sudo
Strange, after re-installing everything and restarting it did not work.
I opened up the foomatic control panel (in applications>system tools)
and installed it from there using the "simple" foomatic driver and it
worked.
--
Printer (HWModel Name) May Not Be Connected
https://bugs.launchpad.net/bu
*** This bug is a duplicate of bug 120896 ***
https://bugs.launchpad.net/bugs/120896
** This bug has been marked a duplicate of bug 120896
inhibit the screensaver when playing a video
--
[i945] Fullscreen Flash contenton external display does not inhibit power
management
https://bugs.lau
This still affects me. Let me know if there is anything you would like
me to provide so we can get this fixed.
--
Facebook Contacts do not show up
https://bugs.launchpad.net/bugs/540325
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
Public bug reported:
I am trying to use a static IP for my computer as I remote desktop to it
regularly. When trying to set the static IP it does not save, and even
more so, every time I try to save it to all users, the editor completely
crashes. Others in the forum have been having this issue,
** Attachment added: "Dependencies.txt"
http://launchpadlibrarian.net/32998126/Dependencies.txt
** Attachment added: "Gconf.txt"
http://launchpadlibrarian.net/32998128/Gconf.txt
** Attachment added: "IpAddr.txt"
http://launchpadlibrarian.net/32998129/IpAddr.txt
** Attachment added: "Iw
It is similar to that, and it does crash at the same time when using the
"allow all users", but it is more as it also does not save even when it
does not crash.
Basically:
For duplicate - It crashes just like in the other bug
Against duplicate - It does not save even when it does not crash
So thi
Carlos, now that you say that, I realize mine has been the same way.
Did not think about it until now, but it is true.
--
gnome-screensaver --poke functionality does no longer inhibit screen blanking
https://bugs.launchpad.net/bugs/428884
You received this bug notification because you are a membe
Thanks for that link Reinhard. I want to help out, if you dont mind
letting me know which of the packages in those ppa are the ones I would
install, I will do so. gnome-screensaver or vlc? or both? (want to
make sure I am doing it correctly so we can get proper results.)
--
Vlc does not inhib
*** This bug is a duplicate of bug 1693334 ***
https://bugs.launchpad.net/bugs/1693334
Public bug reported:
Was exiting the install from USB thumb drive, it took awhile then the
error report appeared and prompted me to report this.
ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: in
Hi Masahiro. Thank you for following up. I want to let you and Aaron
know that I also tried 6.8.0-39-generic just today, and suspend works.
I wanted to rule out the chance that the issue was caused by my machine
having any defect in updating the kernel as 6.8.0-38 was so far the only
one that wo
Public bug reported:
`lsb_release -rd`
Output:
`No LSB modules are available.
Description:Linux Mint 22.1
Release:22.1`
Expected behavior:
That computer will suspend when clicking 'Suspend'.
What happens:
Screen goes black for a split second then immediately the computer wakes and
g
I want to add that I think it is an issue with the Ethernet interface
and Wake-on-LAN. After a lot of back and forth with ChatGPT, I was able
to (at least temporarily) get the device to suspend on 6.8.0-52.
$ sudo ethtool enp0s31f6 | grep "Wake-on"
Supports Wake-on: pumbg
Wake-on:
Hello Masahiro. Thank you very much for your reply. I have a Lenovo
ThinkPad E14 Gen6 with an Intel processor.
I rebooted into 6.8.0-52-generic and can confirm the problem still
exists. One thing I forgot to mention was that 6.8.0-38 is what was
initially installed with Mint 22.0, and any kerne
I see a line in the kernel changelog under 6.8.0-40-generic.
- e1000e: change usleep_range to udelay in PHY mdic access
I think this may have to do with the following errors:
sudo dmesg | grep -i suspend
[1.106374] Low-power S0 idle used by default for system suspend
[1.502944] nvme
29 matches
Mail list logo
