Brian Burch wrote:
> Yes, I understand what is required. Leave it with me for now and I'll do
> some traces on intrepid over the weekend. I will let you know what I've
> found asap. Once I have a good grasp of the protocol issues, then it
> will be time to start looking
Thanks for your helpful comments, Colin.
I was the original poster and you are quite correct, my comment number
33 closed the issue as far as I was concerned. It didn't fix the bug,
but I reported an acceptable bypass as far as I was concerned.
There is something funny about installing a new in
Stefan Bader wrote:
> Thanks you for your report. However I think you should create a new one
> against
> cups. The bug here was about some TCP/IP issues that could not be solved with
> an increased timeout.
>
> That said, Brian, how are you feeling about this? As the exact reason could
> not
I know it is off-topic, but a lot of people are coming here because they
are suffering from this bug. I have attached a quick-n-dirty checklist
on how to get back to your multi-boot setup after a successful install
of intrepid as a self-contained system.
** Attachment added: "recovery of grub mult
The crash reports for my failed installations. Is the problem related to
the boot partition having been setup under hardy (0.97-29ubuntu21) while
intrepid install is using 0.97-29ubuntu45?
** Attachment added: "crash on system with residual intrepid alpha partition"
http://launchpadlibrarian.ne
** Attachment added: "crash on system with only hardy multiboot partition"
http://launchpadlibrarian.net/19176759/crash2.tar.gz
--
ubiquity crashed with InstallStepError in configure_bootloader()
https://bugs.launchpad.net/bugs/260001
You received this bug notification because you are a membe
I just tried installing intrepid to a spare partition on a disk that
already has a windows system and a working hardy system. The install
appears to have worked OK, but it has reported the same or very similar
crash in os-prober. The crash reporter fails because the component is
not a valid package
So far as I know, the inode=256 issue is no longer significant. It was
the way to deal with the problem when I first encountered it on intrepid
alpha 4.
With the intrepix release, again as far as know, there is ONLY one way
to go forward. You must install a self-contained intrepid partition,
compl
Joao - this has been my assumption from the outset. I've done several
intrepid alpha installs as self-contained systems because it was the
only way I could install it. I've tried multi-boot installs on 3
different machines so far and hit the same problem. I think that is why
we are the only people
I think this problem might be caused by the existing grub multiboot
partition being back-level compared to the expectations of the intrepid
installer, but I don't know enough to investigate further.
I noticed that when I merged the intrepid grub menu.lst boot lines back
into my existing hardy-base
I have just spent the last 3 hours trying different installation paths
using the intrepid desktop CD released yesterday. So far, each install
has failed with the same superficial symptoms (reported in the title of
this bug).
However, to my surprise, the inode=128 bytes bypass did NOT work for me
t
Well... the housekeeping didn't help - the install still crashed. I
guess the failure is due to trying to use an existing grub boot
partition. I have some crash reports to append tomorrow.
I have just run a successful install onto an inode=128 partition, but it
was necessary to let the installer p
How disappointing that no-one contributed to this bug. There are many
pleas for help from people with similar printing problems... and none of
them are very conclusive.
I ran a wireshark trace of the LPD protocol exchange between cups and my
network printer. The trace was big, but the later stages
put this line anywhere in /etc/sysctl.conf to preserve the bypass across
system boots:
net.ipv4.tcp_frto=0
--
No print output after upgrade to hardy
https://bugs.launchpad.net/bugs/225603
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Leann Ogasawara wrote:
> The best approach to isolating patches which resolved the issue for
> Intrepid would be to do a git bisect. This is obviously not something
> we expect you to know how to do so this is completely at your own
> discretion if you'd like to try. The following link describes
Colin Watson wrote:
> Actually, we added 256-byte inode support to grub a while back:
>
> grub (0.97-29ubuntu19) hardy; urgency=low
>
> [ David Futcher ]
> * debian/presubj: Fixed spelling mistake (LP: #177540)
>
> [ Tormod Volden ]
> * debian/update-grub: use >> instead of > when writin
Sorry about calling you "Steve", Colin - I was in a hurry and must have
been thinking of the person I was going to play at squash as soon as I
finished the email!
The problem still exists with intrepid beta, but it looks as if the
details might have changed. At this stage, I don't think the har
Stefan Bader wrote:
> For Hardy there is currently a test kernel (smb3) building in my PPA at
> https://launchpad.net/~stefan-bader-canonical/+archive
> (since that is based on the latest kernel in -proposed this might require to
> enable -proposed in the installation sources as well)
>
> If you
Stefan Bader wrote:
> no you should not see more than two, all the other binary packages mentionen
> on that page are just udeb packages (which I personally have never used, they
> are just automatically created). You will just see a new kernel (and maybe
> the kerneloops package).
> One thing
Leann Ogasawara wrote:
> I'm just adding the two upstream git commit id's for the kernel team to
> reference that seem to have resolved the debian bug -
> http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=478062 . Also, it
> appears these patches are already in the Intrepid kernel. If anyone
> wou
Stefan Bader wrote:
> I wonder how you get to those -di versions. Unfortunately I can only say
> what I can see here (with update-manager) and my system also had
> -proposed active before. So maybe try two steps:
Thanks very much for the instructions, Stefan. I followed them carefully
and THINK
Stefan Bader wrote:
> this is bad new, sorry. The problem here is, that as much as you are
> unfamiliar with kernels and packaging,
Don't worry, I think it is quite good news - although (of course) it
could have been better!
You seem to be convinced that I am running your new kernel, so at leas
Leann Ogasawara wrote:
> The Ubuntu Kernel Team is planning to move to the 2.6.27 kernel for the
> upcoming Intrepid Ibex 8.10 release. As a result, the kernel team would
> appreciate it if you could please test this newer 2.6.27 Ubuntu kernel.
> There are one of two ways you should be able to tes
Leann Ogasawara wrote:
> Now regarding the backports for Hardy. Brian, will you still be willing
> to help and test? Possibly run a git-bisect to narrow down the specific
> patches we'd need to backport? I can try to give you some pointers to
> docs to help with this. Let us know. Thanks.
I w
Public bug reported:
Binary package hint: cupsys
I did the official release internet upgrade from feisty to hardy. My
network server HP Laserjet has worked fine for years using LPD protocol.
The upgrade took cupsys to 1.3.7-1ubuntu3. I encountered "the usual
perplexing mess" reported by many peop
** Attachment added: ":/etc/apparmor.d/ usr.sbin.cupsd"
http://launchpadlibrarian.net/14084162/usr.sbin.cupsd
--
No print output after upgrade to hardy
https://bugs.launchpad.net/bugs/225603
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubu
Oh yes, I turned on server diagnostic logging. There doesn't seem to be
any difference whether I use aa-complain or not - the log seems to me to
show a successful print operation. I can attach them if you think they
are useful, but they are big.
** Attachment added: "/etc/cups/printers.conf"
ht
Thanks for your advice, Chris. I've been messing around with modelines,
etc, whenever I've found a spare hour. I'm fairly sure the answer lies
with the vertical frequency, but I'm new to this stuff and am on a steep
learning curve.
I've been concentrating on the Dell optimal mode, which is also th
Got some black screens, but now I realise this happens whenever I run
"Xorg -config -retro" and then Ctl/C. I MUST reboot after I get this
message "NOUVEAU(0): failed to destroy server context" - if I try an
different mode I lose the entire display, including the text-mode
console session. I guess
Well, that is a surprise! I thought this would be the best mode line because it
had the same synch polarity as the specification:
Modeline "2048x1152_60.00_h_plus" 197.97 2048 2184 2408 2768 1152 1153 1156
1192 +HSync -Vsync
... but the vertical alignment is wrong - I lose at least one pixel
I've been messing around with lots of different programs to calculate
the best modeline, but all of them seem to wrong in some way. (Perhaps
the authors never tested resolutions and scan frequencies in the range
of this particular monitor?)
I found an "obsolete" web page that seems to tell me ever
I really don't think this problem is related to the nouveau driver,
because I get the same symptoms using the binary nVidia drivers. I have
also connected the monitor to a system running Hardy LTS on the VIA
chipset (X.Org X Server 1.4.0.90 and CHROME driver). The EDID data looks
the same and is in
I went back to karmic to run gtf and cvt - they produced slightly
different modelines, but I was more concerned about them selecting
197.97 mHz as the pixel clock rate when the Dell specification and the
EDID modeline says 156.75. I ran "cvt --reduced 2048 1152 60" and was
astonished to see that it
I worked on the original hardy bug, which was fixed in the kernel for
jaunty. I have now been running the same printer under karmic for 6
months. I have just upgraded to lucid and the printer is still working
fine. I have not needed to set "net.ipv4.tcp_frto = 0" on ANY kernel
except hardy.
Based
I got hold of a DVI-D cable and tried it with nouveau, KMS enabled and
NO xorg.conf (i.e. using the EDID). The screen came up perfectly at
2048x1...@60.
I need to compare the drm kernel xorg log messages for the two best
cases (VGA and DVI) to see whether I can find a significant difference.
--
I agree with you Stefan, but don't see any reason for you to have
regrets!
When this bug was "hot", it was because a new kernel had just been
released for Hardy LTS. It broke a lot of stable printing systems and so
we knew we would have to live with the bug for the next 18 months. Our
bypass seeme
Sorry about the delay, Matthias. Thank you for the wiki link: I built
the schroot lucid system relatively easily. I then hit a several of
snags getting the system to work properly with me as a user (off topic:
cryptfs, non-standard uid/gid for ldap, etc).
Currently, my /etc/apt/sources.list contai
I expect that I am being stupid, but please be patient!
I installed karmic and am in the process of trying to migrate all my
development to it... I noticed maven was broken a month ago, but didn't
have time to investigate and kept using my old hardy LTS system when
necessary. I've now reached the
Matthius - I think you are telling me to install the entire lucid
system. Is that right? I think you suggested chroot or a VM as
alternative platforms?
I already have a multi-boot system and have even converted to grub2 on
my boot partition. I recently eliminated jaunty (hence my desire to
elimina
Installed karmic maven in fresh schroot system. Very slow where I am at
the moment. Just a quick note to say it worked on my 1st sample project,
which was a complete surprise! Will test some more...
--
[FFe] Sync libmaven packages from Debian unstable
https://bugs.launchpad.net/bugs/427539
You re
I think I understand my problem, and also have a bypass.
When I created the clean karmic maven schroot system, I was surprised to
find that it responded OK to "mvn --help", because this simple command
would always crash on my "production" karmic system.
I went back to my production karmic system
Just happened for me - running nautilus as sudo command, working fine,
exit and then it crashes.
--
nautilus crashed with SIGSEGV in g_type_check_instance_is_a()
https://bugs.launchpad.net/bugs/436459
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
I apologise for not opening a new bug, but I think my observations of a
clean karmic install would be helpful because I had the same symptoms -
both usb memory stick and greyed-out admin-users authenticate. Following
this particular bug helped me because I found a different entry in
/var/log/daemon
Public bug reported:
Binary package hint: xorg
This monitor has a preferred resolution of 2048x1152 @ 60Hz. The desktop
does not fill the display and leaves a 2 cm black strip on the left
margin. The monitor manual adjustments do not permit the image to be
moved or expanded to fill the screen. So
** Attachment added: "get-edid binary from lucid beta"
http://launchpadlibrarian.net/44259049/get-edid
** Attachment added: "BootDmesg.txt"
http://launchpadlibrarian.net/44256685/BootDmesg.txt
** Attachment added: "CurrentDmesg.txt"
http://launchpadlibrarian.net/44256686/CurrentDmesg.tx
** Attachment added: "ddcprobe from lucid beta"
http://launchpadlibrarian.net/44259377/ddcprobe
--
Invalid EDID for Dell SP2309W in VGA mode
https://bugs.launchpad.net/bugs/563774
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
u
** Attachment added: "xrandr from lucid beta"
http://launchpadlibrarian.net/44259480/xrandr
--
Invalid EDID for Dell SP2309W in VGA mode
https://bugs.launchpad.net/bugs/563774
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubunt
Please note that lucid beta is running from an unmodified CD downloaded
as ubuntu-10.04-beta2-desktop-i386.iso. That means the /etc/X11/
directory does NOT contain an xorg.conf file.
According to the X.Org web site, X Server 1.7.6 is the up-coming next
stable release.
** Attachment added: "Xorg.0
I found several reports of this monitor not working properly on its hdmi
interface (particularly the mythbuntu faq), and tried all the work-
arounds proposed, but none of them seemed to make an improvement (some
were disastrous!). My screen is attached via the vga interface: I am not
sure whether t
lucid beta uses KMS (kernel mode setting) and this is reported in the
log. my karmic system is still using xorg for configuration. I think
this means the problem is attributable to the monitor's EDID data,
rather than the nvidia driver or the dynamic configuration logic.
p.s. I do not have a windo
I forgot to mention that I tested under lucid with-and-without the kvm
switch. There was no visible difference in the screen images, but the
files I have attached to this bug report were collected WITHOUT the kvm
switch. I conclude the switch is not contributing to the problem.
--
Invalid EDID fo
This is very frustrating because my changes have not been reproducible
because the monitor is too clever for its own good - it "auto-adjusts"
the image and apparently remembers the "optimal" alignment for that
particular resolution.
I've discovered (the hard way) that I can only be sure my test mo
Works fine when lucid upgraded from karmic, and also with a clean
install of lucid. As far as I am concerned, this problem has "gone
away"
--
UK keyboard layout has gone wrong
https://bugs.launchpad.net/bugs/492874
You received this bug notification because you are a member of Ubuntu
Bugs, wh
Something really strange is going on...
My SVGA Xlog shows: Display dimensions (510, 290) mm and DPI set to
(101,100). The Dell specification says the display area is (509.95,
286.84) mm (confirmed by ruler to be more-or-less right). The Dell spec
also gives the pixel pitch as 0.249 mm, which corr
Works fine for me! Thanks for the quick response.
--
No Sound from Head phone Jack on Dell Studio 1558
https://bugs.launchpad.net/bugs/568600
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.
Excellent news! I installed maven2 from the lucid universe repository. I
then copied two sample maven-based projects to the new schrooted system.
They both built and tested successfully. Because the original maven bug
was so fundamental (it failed to run even without a maven project), I am
happy to
I will try to set the system up, but please don't expect to hear
anything soon because I'll have poor internet access for a while.
--
[FFe] Sync libmaven packages from Debian unstable
https://bugs.launchpad.net/bugs/427539
You received this bug notification because you are a member of Ubuntu
Bugs
I have now built and tested several maven projects under all of my three
systems: karmic production, minimal karmic schroot and lucid schroot.
All of them worked exactly as expected. As far as I am concerned, the
latest maven2 distributions are acceptable. My evidence suggests that
the original bu
Still not clear what the pattern is... howver, whenever I've had a
system that hung in boot because swap was "wrong", I've got out of it by
doing a boot in recovery mode. It appears that a recovery boot
serialises well enough that the system waits until swap/cryptswap is
formatted properly.
--
Se
Workaround (tongue in cheek): if your system hangs and the disk activity
light stays on for 10 minutes or more - press the power button and hold
it down for 5 seconds!!!
My symptoms look more like a race condition caused by an implicit
assumption about how long it takes to format the swap partitio
I have the same problem... the system works fine when I boot hardy or
jaunty, but not with a clean install of karmic. I tried bill's
circumvention, but it hasn't made any difference for me. Incidentally,
whatever I change I still get the wrong keyboard mapping in the "try it"
box of the keyboard pr
I have 32-bit ubuntu (I realise this isn't relevant, but I don't want
people to get the idea it is a 64-bit problem).
The killer on my own system was bind - when it didn't start all my
custom services on the system were completely wrecked. I am surprised
bind9 wasn't mentioned by anyone else...
T
I sort-of agree with everyone here...
a) I have a 100% raid server running karmic (without cryptswap). I don't trust
automated tools on this system and always verify that /etc/fstab points to the
correct swap md partition after any significant change and before I reboot.
b) I have a laptop with h
Thanks for your comment, Kai-Heng, but I did try the latest upstrem
kernel at the weekend. Please refer to my post #8.
Is there a good reason to try a kernel more recent than:-
linux-image-
unsigned-4.17.0-041700-lowlatency_4.17.0-041700.201806041953_amd64.deb
... along with its associated heade
** Tags added: kernel-bug-exists-upstream
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1776443
Title:
iwlwifi-29 kernel timeout queue active on fifo 2 and stuck
To manage notifications about this
Things are much improved now on cosmic 18.04 ubuntu studio:-
/sys/class/power_supply/BAT0/capacity:100
/sys/class/power_supply/hid-34:88:5d:87:92:8c-battery/capacity:85
Linux 4.18.0-11-lowlatency #12-Ubuntu SMP PREEMPT Tue Oct 23 21:12:42
UTC 2018 x86_64 x86_64 x86_64 GNU/Linux
[The mouse is OK
Sorry for the delay. The problem still exists under 19.10 desktop, but
does not occur quite as often. However, it is slightly harder to escape
from... I either need to wait 20+ seconds uselessly pressing keys I will
have to subsequently delete, or tab to another command prompt, type
something in ea
apport information
** Attachment added: "ProcEnviron.txt"
https://bugs.launchpad.net/bugs/1838919/+attachment/5331423/+files/ProcEnviron.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1838919
apport information
** Attachment added: "GsettingsChanges.txt"
https://bugs.launchpad.net/bugs/1838919/+attachment/5331421/+files/GsettingsChanges.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs
apport information
** Attachment added: "Dependencies.txt"
https://bugs.launchpad.net/bugs/1838919/+attachment/5331420/+files/Dependencies.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1838919
On 24/2/20 3:12 pm, Daniel van Vugt wrote:
> Actually I should have just continued from comment #27. To do that
> please run:
>
>mv ~/.local/share/gnome-shell/extensions ~/old-extensions
Oops! I had already run the "dconf reset"!
Never mind, I was not aware of having changed the settings fro
apport information
** Attachment added: "ShellJournal.txt"
https://bugs.launchpad.net/bugs/1838919/+attachment/5331424/+files/ShellJournal.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1838919
apport information
** Attachment added: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/1838919/+attachment/5331422/+files/ProcCpuinfoMinimal.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/
Excellent news! The bluetooth dock battery status started working
properly a couple of weeks ago. I can't be sure which update fixed the
bug, but here is the latest system status:-
ubuntu 19.10 eoan Desktop
5.3.0-26-generic x86_64 kernel
Bluez-* 5.50-0ubuntu4
gnome-bluetooth 3.34.0-1
udev 242-
On 17/5/19 1:14 am, Kai-Heng Feng wrote:
> Sorry for the late reply. Does this happen on generic kernel?
>
It is so good to hear from anyone on this problem, so I welcome your
"late reply"!
My laptop runs ubuntu studio 19.04, but studio stopped including the
linux-generic package many releases
On 15/5/19 6:34 pm, Dylan Aïssi wrote:
> ** Also affects: pdftk (Ubuntu Bionic)
> Importance: Undecided
> Status: New
>
> ** Changed in: pdftk (Ubuntu)
> Status: Confirmed => Fix Released
Thanks, Dylan
I installed the pdftk package from the disco 19.04 repository and ran
one
Public bug reported:
This was a fresh amd64 installation with 18.10 desktop, upgraded to
19.04 as soon as available. It has been getting worse over the last few
weeks and is now so bad I can hardly type an email (or this bug report!)
without having to fix many typos.
journalctl shows many differe
Daniel post #2. That was exactly how I opened this bug report, so what
exactly are you missing?
Daniel post #3. I don't use Chromium, by preferred browser is stock
vanilla Chrome from their own repository. I did not think Chrome was
delivered as a snap - are you sure your comment is relevant?
--
apport information
** Attachment added: "ProcEnviron.txt"
https://bugs.launchpad.net/bugs/1838919/+attachment/5281061/+files/ProcEnviron.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1838919
apport information
** Attachment added: "ShellJournal.txt"
https://bugs.launchpad.net/bugs/1838919/+attachment/5281062/+files/ShellJournal.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1838919
apport information
** Tags added: apport-collected
** Description changed:
This was a fresh amd64 installation with 18.10 desktop, upgraded to
19.04 as soon as available. It has been getting worse over the last few
weeks and is now so bad I can hardly type an email (or this bug report!)
apport information
** Attachment added: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/1838919/+attachment/5281060/+files/ProcCpuinfoMinimal.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/
Thanks for explaining Daniel #5. You will see I ran the command again.
However... It is interesting to see that even the apport-collect command
from a new terminal session triggered the canberra error.
brian@schizo:~$ apport-collect 1838919
(apport-gtk:21631): Gtk-WARNING **: 08:30:48.771: GTK+
apport information
** Attachment added: "GsettingsChanges.txt"
https://bugs.launchpad.net/bugs/1838919/+attachment/5281059/+files/GsettingsChanges.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs
Also, I will attach journalctl -xb log taken as soon as I booted the
system and logged on this morning. It seems to me that as soon as
systemd started the gnome terminal server unit, related error messages
began to be generated.
Chrome/chromium had not been started at the time - it was autostarted
What can I do to help you diagnose the problem further, Daniel?
I think something changed recently, and that must have been an update. I
do not believe I have installed any new packages that might have called
for GTK2, so my guess is that it has been there since the clean 18.10
install and not bee
Hi Daniel, thanks for not giving up! First, here is snap list:-
Name Version Rev Tracking Publisher
Notes
core 16-2.39.3 7270 stablecanonical✓
core
core18201907231074 stable
top on 4 second intervals rotates the same 5 or 6 threads, so I set the
interval to 20 seconds and copied the output to a file, which I have
attached. I have also attached the dpkg list.
** Attachment added: "top interval 20 seconds"
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1
dpkg list next...
** Attachment added: "dpkg list"
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1838919/+attachment/5281101/+files/schizo-2019-08-06-allpackages-txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
htt
I had a bit of a brainwave this morning - or perhaps just awoke from my
stupidity!
I also have a laptop which runs ubuntu studio 19.04 amd64. At the
moment, my desktop which is suffering has the 5.0.0-23-generic kernel.
The laptop has the 5.0.0-21-lowlatency kernel, BUT does not have all
these pro
Thank you very much for your suggestion #21, Traumflug. I read the issue
you quoted and to be honest, I was quite disappointed in the responses
so far.
The symptoms sound very similar to those I reported here. I compared the
wayland packages on my desktop (slow or lost mouse and keyboard events)
w
On 14/8/19 8:22 pm, Traumflug wrote:
> Installed packages don't matter if their content isn't in use. It does
> matter whether you run an X11 or a Wayland session.
>
> To switch between both, log out to get to the login screen. There is a
> gears icon right above the password entry field, click on
I didn't see any problems logging on with gnome on xorg, or starting the
first terminal session.
However, as soon as I started the second terminal, the GTK2/GTK3 error
messages poured out. Opening a new tab on the same window does not
generate the messages.
This sounds like your gnome bug report
I installed the 5.0.0-15-generic kernel and removed iwlwifi from the
/etc/modprobe.d/blacklist. The system was stable and ran very well for 4
or 5 hours.
When I booted it (still generic kernel) this morning, it failed after
about 20 minutes. I rebooted and teed journalctl for documentation. The
fa
I upgraded both my Ubuntu Desktop and UbuntuStudio systems to 19.10 Eoan
(with gnome mostly at 3.34). The symptoms have not changed... my desktop
still hangs, loses keyboard events, and the log fills with the GTK 2/3
conflict messages. Meanwhile my Studio system behaves perfectly!
The log messages
Daniel
I am Brian's wife, Jane
I am devastated to let you know that Brian succumbed to his prostate
cancer and died a few weeks ago
Please let everyone know
Thanks
Jane Burch
On 7/8/20 7:50 pm, Daniel van Vugt wrote:
> Thank you for reporting this bug to Ubuntu.
> Ubuntu 19.10 (eoan) reached
After upgrading to 19.04 disco, the system is still too unstable to be
useful. The current kernel is 5.0.0-13-lowlatency
(buildd@lcy01-amd64-020).
I note the Intel driver has not changed after the upgrade from 18.10
cosmic, i.e. still iwlwifi-7265D-29.ucode, packaged within linux-
firmware version
Oops! My post #56 should have said the other synaptics mouse is also OK
on 18.04.1 LTS (not 17.10). I also got the release of cosmic wrong - it
is 18.10, of course!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad
I suspect I need to open a new bug for the ASUS docking station
(detachable bluetooth keyboard with touchpad) under 18.04.1 LTS.
This system is completely up to date, but it still reports 0% charge all
the time.
I checked the directory tree for /sys/class/power_supply/AC0 (the mouse
is blah/BAT0)
Public bug reported:
dell inspiron 15 3565 and intel 3165. Difficult to report when wifi is
down!
Happens sometimes after a few minutes, never more than 30 minutes. Easy
to capture journalctl when the network connection hangs. Intel fails on
2.4 GHz or 5 GHz, using several different AP's.
The sa
1 - 100 of 210 matches
Mail list logo
